Real Company Scenario Walkthrough – GlobalTech Innovations SAP End‑to‑End Project Simulation | Part-15 | FreeLearning365

 

Real Company Scenario Walkthrough – GlobalTech Innovations SAP End‑to‑End Project Simulation

It’s 9:00 AM on a Monday in July. The conference room at GlobalTech Innovations smells of coffee and anxiety. The CFO, Priya Sharma, leans forward and says, “We bought SAP to run our business, not just to print invoices. Show me how a customer order turns into cash, and why my balance sheet last month was off by 12 lakhs.” As the lead SAP consultant, this is your moment. This is not a demo. This is a real company with real problems, and you have exactly four weeks to make their SAP system tell the truth.

This article is the capstone of the Business Process First series. It is a complete, immersive walkthrough of a single month inside GlobalTech Innovations – a mid‑sized manufacturer and distributor of IT networking hardware. You will sit with the management team, map their processes, configure the system, execute transactions, solve crises, and finally present the financial statements to the board. Every character, every problem, and every solution is drawn from real‑world implementations. By the end, you will have lived through a full project lifecycle in the safety of your sandbox, and you will be ready to do it for real.

This is the final exam. Let’s walk into the company together.

1. The Company – GlobalTech Innovations at a Glance

GlobalTech Innovations is headquartered in Bangalore, India, with a manufacturing plant (Plant 1100) and a separate warehouse and sales office in Mumbai (Plant 1200). They produce the ProSwitch 24‑Port Gigabit Switch (MAT‑IT‑001), assemble a high‑end router (MAT‑IT‑002) from imported components, and trade in third‑party cables and accessories. They sell to domestic retailers like TechMart Retail, export to Germany through their subsidiary GlobalTech GmbH, and occasionally act as a subcontractor for a large OEM.

The SAP landscape is a single client with two company codes: 1000 (India) and 2000 (Germany). Modules implemented: SD, MM, PP, FI, CO, HCM, and basic QM. The project went live three months ago, but the finance team still doesn’t trust the numbers. Your job is to run May 2026 perfectly – from order to cash, procure to pay, plan to produce, and record to report – and then present the results. This walkthrough is that story.

2. The Cast of Characters – People Drive Processes

Every SAP system has human stories behind the T‑codes. These are the people you’ll work with:

• Priya Sharma – CFO: Demands a P&L that ties to the bank balance. She’s the project sponsor and your ultimate audience.
• Ravi Kumar – Production Manager: Lives on the shop floor. He trusts physical stock, not system stock. Your biggest challenge in inventory accuracy.
• Anjali Desai – Purchasing Manager: Negotiates with vendors under pressure. She needs MRP to work flawlessly so she’s not blamed for stockouts.
• Sameer Joshi – Sales Director: Wants credit checks and pricing to be invisible – he just wants to close deals.
• Lakshmi Nair – HR Head: Needs payroll to pay people correctly and on time, and she wants the cost to flow to the right cost centers automatically.
• Vikram Singh – Warehouse Supervisor: Manages the physical stock. He’s overworked and sometimes posts goods receipts after the shift ends, causing timing differences.
• You – The SAP Consultant: The bridge between their world and the system.

3. The Business Challenges – Why We Are Here

During the blueprint sessions, the team laid out their pain points. These are the exact issues we will solve in this walkthrough:

1. Sales orders were being booked for products that were out of stock, causing delivery delays and customer complaints. Sameer wanted availability checks that actually worked.
2. Procurement was reactive. Anjali was buying raw materials based on phone calls from the shop floor, not MRP. She wanted the system to trigger purchase orders automatically.
3. Production cost was a mystery. Ravi knew how many units he made, but not what they actually cost. The CFO couldn’t compute accurate gross margins.
4. Inventory records were unreliable. Vikram’s manual counts rarely matched the system, and every month‑end was a scramble to adjust.
5. Financial close took two weeks because Priya’s team had to reconcile GR/IR, AR, AP, and inventory with spreadsheets. She wanted a one‑day close.
6. Tax compliance was at risk. A wrong customer tax classification had caused an export invoice to charge GST, which had to be reversed.
7. Payroll costs were not flowing to the production cost. The HR department’s salary postings hit a generic administration cost center, not the assembly work center. Ravi’s product cost was missing 40% of the labor.

These are the seven battles we will fight and win in May 2026. Let’s begin.

4. The Master Data Foundation – Building the Digital Twin

The first week of our project is dedicated to cleansing and completing master data. We’ll extend existing records and create new ones where needed. I’ll describe the final state of each critical record.

4.1 Customer Master – TechMart Retail (100001)

• General: Name, address, GSTIN updated.
• Company Code (1000): Reconciliation account 140000, payment terms 0002, tolerance group blank.
• Sales Area (1000/10/00): Tax classification IN = 1 (taxable), customer pricing procedure 1, customer account assignment group 01, delivery priority 02, shipping conditions 01.

4.2 Customer Master – GlobalTech GmbH (200001)

• Company Code: 1000 (for inter‑company reconciliation). In sales area, tax classification IN = 0 (exempt for export).

4.3 Vendor Master – TechSupply Inc. (200001)

• Company Code (1000): Reconciliation account 160000, payment terms 0002, GR‑Based IV ticked. Tax classification 1 (taxable).
• Purchasing org 1000: Schema group 01, Inco terms FOB, currency INR.

4.4 Material Master – ProSwitch (MAT‑IT‑001)

• Sales: item category group NORM, tax classification 1, account assignment group 01.
• Accounting: valuation class 7910 (Finished Goods), standard price 3,500 INR (we will run a new standard cost estimate).
• MRP: type PD, procurement type E, lot size EX, safety stock 50. In‑house production time 3 days.
• Plant data: Storage location FG01.

4.5 Material Master – Aluminum Enclosure (MAT‑RM‑001)

• Accounting: valuation class 7920 (Raw Materials), standard price 800 INR.
• MRP: type PD, procurement type F, lot size EX, safety stock 20.
• Purchasing: tax classification 1.

4.6 Production Master Data

• BOM for MAT‑IT‑001: 1 PC MAT‑RM‑001, 1 PC MAT‑SF‑001 (Circuit Board, purchased), 1 PC MAT‑PKG‑001 (Packaging, consignment from vendor).
• Routing: 3 operations at work centers ASM-001 and TST-001, with activity times and cost centers assigned.
• Production version 0001 linking BOM and routing.
• Cost estimate (CK11N) run and released, confirming standard price 3,500 INR.

4.7 HR Master Data

• Ravi Kumar (PERNR 500001), position Assembly Operator, linked to cost center 1100 (Assembly). Basic pay 18,000 INR, allowances, PF, etc. Infotype 0001 updated.
• Work center ASM-001 linked to cost center 1100, with activity price calculated from cost center plan.

All condition records for pricing (PR00, K004, FRA1, MWST, JINP) are created and validated. We also set up the automatic account determination (OBYC, VKOA, OB40) as per the integration blueprint. Master data is now ready. The system is clean.

5. The Month Begins – May 2026, Day 1 to Day 7

On May 2, Sameer receives a large purchase order from TechMart Retail: 500 units of ProSwitch for delivery by May 25. The sales order (VA01) is created: OR type, customer 100001, material MAT‑IT‑001, quantity 500, requested delivery 25.05.2026. Pricing calculates 10,000 INR per unit net, 2% freight, 18% tax. Total order value = 500 * 10,000 = 5,000,000 + 100,000 freight = 5,100,000 + 18% tax = 6,018,000 INR. The availability check (ATP) shows only 10 pieces in unrestricted stock (leftover from last month). 490 are not confirmed. Sameer calls Priya, alarmed.

This is where MRP must work. We run MD02 for MAT‑IT‑001 with processing key NETCH. The system reads the demand (500 PIR + sales order? Actually, strategy 40 makes the sales order consume the PIR. We have a PIR of 500 for May already, so the sales order reduces the PIR. Net requirement: 500 – stock 10 = 490. MRP creates a planned order for 490 units, scheduled to start on May 15 to meet delivery. It also explodes the BOM and creates dependent requirements for MAT‑RM‑001 (490 PC), MAT‑SF‑001 (490), MAT‑PKG‑001 (490). MRP then plans these components: MAT‑RM‑001 has zero stock and a safety stock of 20, so net requirement = 490 + 20 = 510. The system generates a purchase requisition for 510 PC. MAT‑SF‑001 is also externally procured, generating another PR. MAT‑PKG‑001 is under consignment; MRP creates a delivery schedule line for the consignment vendor.

Anjali receives the PRs in her MD04 list. She converts the PR for MAT‑RM‑001 into a purchase order (ME21N) for vendor 200001, 510 PC at 850 INR. The PO gross value is 510 * 850 = 433,500 + tax 78,030 = 511,530 INR. Release strategy: the PO value exceeds 100,000 INR, so it goes to the procurement manager for release (ME29N). Same for the MAT‑SF‑001 PO, which we also create. Consignment demand is communicated to the vendor, but no PO value. Production is now planned.

6. The Procurement Crisis – Day 8 to Day 10

TechSupply delivers 510 enclosures on May 12. Vikram posts the goods receipt (MIGO 101) in the system, but he is busy and doesn’t count the pallets – he trusts the delivery note. The system posts: Dr Raw Material Inventory (142000) 408,000 INR (510 * 800), Dr Price Difference (670000) 25,500 INR (since PO price 850 vs std 800), Cr GR/IR (210000) 433,500 INR. Later that day, the invoice arrives via email. Anjali enters it via MIRO: 433,500 net + 18% tax 78,030 = 511,530. The system clears GR/IR and posts the vendor payable. However, when the warehouse later physically counts, only 480 enclosures are in the bin. 30 pieces are missing. Vikram swears he posted the GR correctly. A delivery note error by the vendor. This discrepancy will surface during physical inventory later. For now, the system believes stock is 510. Production is about to consume based on this stock.

7. Production – Where the Factory Runs (Day 12 to Day 18)

The planned order for 490 units is converted to production order 1000010 by Ravi. He releases it. The material availability check for MAT‑RM‑001 shows stock 510, so 490 available – no problem (system doesn’t know the physical shortage yet). Goods issue to production (MIGO, movement 261) consumes 490 enclosures. FI: Dr Production Cost (GBB‑AUF) 392,000 INR (490 * 800), Cr Raw Material Inventory 392,000. The shop floor begins assembly. During production, an operator reports that 10 units of the circuit board (MAT‑SF‑001) are defective. Ravi calls Anjali; she creates a return delivery to vendor (MIGO 122) for 10 pieces, reversing the goods receipt for those and creating a credit memo expectation. Simultaneously, a rush purchase order for 10 additional circuit boards is created. The production order is short, but Ravi decides to complete 480 units first and later produce the remaining 10.

Confirmation (CO15) for 480 units is posted on May 18. Labor and machine times are recorded. Ravi’s actual hours (including overtime on Saturday) are captured via time management (PA61) and fed into payroll, which will post salary expense to cost center 1100. The production order absorbs activity costs at the standard rate, but Ravi’s overtime pay will cause a small variance later. Goods receipt of 480 finished units (MIGO 101 for order) posts: Dr Finished Goods Inventory (141000) 1,680,000 INR (480 * 3,500), Cr Production Output 1,680,000. The production order now has a debit balance for the unconsumed raw material and the outstanding 10 units. The variance will be settled after final delivery.

8. The Quality Gate and a Billing Block (Day 19)

The quality inspector finds that 5 of the 480 units have a cosmetic defect. The entire batch is placed in quality inspection (movement 322? No, it was already in unrestricted after GR. He uses MIGO to transfer 5 units to blocked stock (movement 321) and the remaining 475 remain available. A quality notification (QM01) is created. The sales delivery for TechMart was planned for 500 units; but we only have 475 good units plus 10 from the previous stock, total 485. Sales order still demands 500, so we do a partial delivery. Delivery (VL01N) for 485 units is created. Goods issue posts: Dr COGS 1,697,500 (485 * 3,500), Cr Finished Goods Inventory 1,697,500. But the sales order value is based on 500 units, so the billing must be partial. Sameer is not happy.

Billing (VF01) for the delivery: 485 units * 10,000 = 4,850,000, freight 2% = 97,000, net 4,947,000, plus 18% tax = 890,460, total invoice 5,837,460 INR. FI document posts correctly. The remaining 15 units will be delivered later after the quality issue is resolved and the 10 backordered units are produced.

9. The Inventory Nightmare – Day 22 to Day 25

It’s month‑end preparation. Priya demands a physical inventory of high‑value raw materials before close. Vikram and team count the Aluminum Enclosures: they find only 20 pieces left (after the GR of 510, issue of 490 should leave 20). But because the GR was short 30 pieces physically, the count should be -10? Wait, system stock: 510 – 490 = 20. Physical count: 20 – (30 missing from GR) = -10, impossible. Actually, if the GR posted 510 but only 480 arrived, physical stock after issue of 490 would be -10. But because the issue was 490, the system stock before issue is 510, after issue 20. Physical count after issue: 480 arrived – 490 issued = -10, which cannot be. So the warehouse would have noticed the shortage before issue? In reality, they issued from the 480 physical, so there should be -10? No, they can only issue what they have. They probably issued 490 from the 480 physical? That would be impossible – they would have run out. So the scenario must adjust: the GR was posted as 510, but physically 480 delivered. Before issue, system showed 510, physical was 480. They attempted to issue 490, but physically they could only issue 480. The system allowed it (negative stock not allowed? we said we disabled negative stock). So the goods issue would have failed with a shortage. Ah! That's a better integration. Let's use that.

Rewrite: GR of 510 posted, but physical stock only 480. When trying to issue 490 for production, the system blocks it because stock is insufficient (negative stock not allowed). The system shows stock 510, but upon physical picking, Vikram finds only 480. He calls Anjali; they realize the GR was over‑posted. They reverse the GR for 30 pieces (MIGO 102), which reverses the inventory and GR/IR. The vendor is notified and sends a credit note. Then the goods issue proceeds for 480. This is a realistic inventory adjustment during operation. This scenario will appear later in the audit trail.

10. The Month‑End Close – Day 26 to Day 31

Now the real stress begins. We’ll follow Priya’s team through the close steps we detailed in the Record to Report article, but this time with all the complexity of real operations.

10.1 Open Items and Reconciliation

• Customer open items: FBL5N shows TechMart invoice 5,837,460 due. Payment received on May 30 via bank transfer for the full amount. F-28 clears the AR. Customer account zero.
• Vendor open items: FBL1N shows TechSupply payable from the enclosure invoice (511,530) and the credit note for the return of 30 enclosures (30 * 850 = 25,500 less tax?). The credit note was posted via MIRO as a credit memo, reducing the liability. Net payable is lower. Additionally, the circuit board vendor has an open invoice. Payments are run via F110 on May 31, clearing all except one disputed invoice.
• GR/IR clearing: MB5S shows a small balance from the rush PO for circuit boards where GR was posted but invoice not yet received. This is regrouped via F.19 into a “Goods delivered, not invoiced” liability account.

10.2 Physical Inventory Adjustment

The physical count of MAT‑RM‑001 after all movements reveals a shortage of 5 units (normal pilferage). MI07 posts the difference: Dr Inventory Difference Expense (GBB‑INV) 4,000, Cr Raw Materials 4,000. Priya signs off.

10.3 Production Order Settlement

The production order for 480 units is still open for the missing 10 units. Ravi decides to close it (TECO) and settle. The order has actual costs: raw material (480 enclosures), circuit boards (480 plus scrap?), and activities. The total debit is compared to the credit from goods receipt. A variance of 12,000 INR (unfavorable) is posted via KO88 to the production variance account. This variance will reduce the gross margin on the P&L.

10.4 Payroll Accrual and Posting

Lakshmi runs payroll for May. Ravi’s salary and overtime are calculated. The posting run transfers the expense to cost center 1100 (Dr Salary Expense, Cr Salary Payable). The activity price used in the production order was based on the standard cost of labor, but actual salary cost is slightly higher due to overtime. This difference will appear as an under‑absorption in cost center accounting, which is later allocated to COGS via assessment. This is a subtle PP‑CO‑HCM integration that Priya notices.

10.5 Tax Reconciliation

The output tax collected from all sales is 890,460 (from TechMart) plus other sales. Input tax from purchases is 78,030 (from enclosures) plus others. The net tax payable is calculated. The balance in the output tax GL and input tax GL are verified against the tax returns. Everything ties, thanks to the correct tax classifications.

11. The Financial Statements – The Board Presentation

On June 1, Priya runs the financial statements (F.01) for May. The P&L shows:

• Revenue: 4,947,000 (from 485 units) + freight 97,000 + other smaller sales.
• COGS: 1,697,500 (485 units * 3,500).
• Gross profit: approx 3,346,500.
• Less: Production variance 12,000, inventory write‑off 4,000, salary expense (including overtime), rent, depreciation, etc.
• Net profit: around 2,800,000 INR.

The balance sheet balances, with total assets equaling liabilities and equity. Bank balance reconciled. AR zero. Inventory values match MM. GR/IR regrouped.

Priya presents to the board. The CEO asks: “Why did our gross margin improve compared to April?” The answer: the standard cost update from 3,200 to 3,500 INR reduced COGS per unit because April’s standard was outdated. The production variance also tells a story of efficiency. Because we can trace the numbers, the board is satisfied.

12. Integration Map – The Full Picture

Let’s now draw the complete picture of every integration moment in this scenario:

• Sales order → MRP → Planned order (SD to PP/MM)
• Purchase requisition → Purchase order → Goods receipt → Invoice → Payment (MM to FI)
• Goods issue to production → Work center activity → Payroll posting to cost center (PP to MM to HCM to CO)
• Production order variance → Settlement to FI (PP to FI)
• Quality inspection → Stock transfer to blocked → Scrap (QM to MM)
• Physical inventory difference → FI posting (MM to FI)
• Sales delivery → Goods issue → COGS and inventory reduction (SD to MM to FI)
• Billing → Revenue, tax, and customer receivable (SD to FI)
• Payment → Bank and AR clearing (FI internal)
• Month‑end accruals, GR/IR regrouping, payroll posting (FI and CO)

This map is your mental model. Whenever a process breaks, you can walk the chain and find the broken link.

13. The 12 Consultant Lessons from GlobalTech

1. Master data is never done. The GR‑Based IV flag on a vendor saved us from a lakh‑sized mistake, but a missing tax classification on a new customer almost killed billing.
2. Physical inventory is not just a count; it’s a system of truth. The missing 30 enclosures would have been hidden if we hadn’t enforced negative stock checks.
3. MRP works only if master data is perfect. A missing safety stock caused a stockout of circuit boards; we fixed it immediately.
4. Production variance must be settled before month‑end. Delaying KO88 by one day would have misstated May’s P&L.
5. Inter‑company billing requires configuration and discipline. The German subsidiary’s internal invoice was almost missed because the clerk didn’t know the VF01 with IV type.
6. GR/IR is the most dangerous account in SAP. Unreconciled balances can hide fraud, loss, or simple process failures.
7. Tax integration is unforgiving. A single wrong tax classification cascades into compliance risk and financial restatement.
8. Payroll integration with cost centers and activity types is essential for accurate product cost. Ravi’s overtime had to hit the production cost, not administration.
9. Always test with real volumes. Our sandbox test with 10 units didn’t reveal the capacity overload; the 500‑unit order did.
10. Build a reconciliation culture. Priya now runs S_ALR_87012085 every Friday, not just at month‑end.
11. Trust the system, but verify physically. Vikram’s initial trust in the delivery note cost us 30 enclosures; now every GR is physically counted.
12. You are the bridge. Your ability to translate a shop floor problem into a GL impact is what makes you an SAP consultant, not a data entry operator.

14. Interactive “Try It Now” – Reproduce the GlobalTech Month

In your sandbox, execute this full scenario step by step. Use your own materials, but follow the logic:

1. Set up a material with BOM and routing, MRP, standard cost.
2. Create a customer and vendor, ensure all master data fields are populated correctly.
3. Create a PIR and sales order for 100 units.
4. Run MRP, observe planned orders and purchase reqs.
5. Procure components, post GR, post invoice, pay.
6. Produce, issue components, confirm, receive finished goods, settle order.
7. Deliver, post goods issue, bill, receive payment.
8. Introduce an error: post a GR without physical stock, try goods issue, see the block. Correct it.
9. Do a physical inventory and post a difference.
10. Run month‑end close: GR/IR regroup, depreciation, accruals, financial statements.
11. Print the P&L and Balance Sheet. Explain every number to a colleague.

15. Closing Thoughts – You Are Now a Business Process Consultant

You just experienced a complete SAP implementation month, from blueprint to boardroom. You saw how a single order rippled through every module, how master data errors became financial disasters, and how systematic reconciliation turned chaos into clarity. This is the real job. The T‑codes are easy; the thinking is hard. But now you have the map, the stories, and the confidence. Go build your own GlobalTech in your sandbox, break it, fix it, and then walk into your next interview ready to lead the blueprint session – not just attend it.

This concludes the 15‑part Business Process First series. From O2C to R2R, from shop floor to balance sheet, you have traveled the full SAP value chain. Keep learning, keep building, and remember: a consultant who understands the business process will always have a seat at the table.

– FreeLearning365, in tech partnership with @techbook24