Real Scenarios in SAP: End-to-End Business Process Walkthroughs Every Consultant Must Master

🌍 Why Real Scenarios in SAP Matter

🛒 Procure-to-Pay (P2P) — Full Purchasing Cycle

The Procure-to-Pay process is the most commonly discussed real scenario in SAP MM interviews and implementations. It covers the complete journey from the moment a business identifies a need for goods or services all the way through to the payment of the vendor invoice. all Understanding every step of this cycle — including which SAP documents are created, which tables are updated, and which T-codes are used — is essential for any MM consultant or ABAP developer working in the procurement space.

In a real company scenario, imagine a manufacturing plant in Mumbai that needs to purchase 500 units of raw material (Steel Sheets — Material STEEL-001) from a vendor. The stores manager create a request, procurement processes it into a purchase order, goods are received from the vendor, and finally the finance team pays the vendor invoice. Here is exactly how this work out in SAP:

🚚 Order-to-Cash (O2C) — Complete Sales Cycle

The Order-to-Cash process is the mirror image of Procure-to-Pay but on the sales side. It covers everything from the customer placing an order all the way through to receiving payment for the goods or services delivered. O2C is the core scenario for all SAP SD consultants and is always tested in SAP SD interviews. In a real company, imagine a pharmaceutical company receiving a bulk order from a hospital chain for 1,000 boxes of medicines.

📒 Record-to-Report (R2R) — Month-End Financial Close

The Record-to-Report process covers everything from recording daily financial transactions to generating the final financial statements at the end of an accounting period. This is the core scenario for SAP FICO consultants and is directly linked to every business transaction in other modules — every goods receipt, every customer invoice, every payroll run creates accounting entries that must be reconciled and reported. Let us walk through a real month-end close scenario for an Indian manufacturing company.

Step 1 — Daily Transaction Recording

Throughout the month, every business transaction in MM, SD, HR, and PP automatically creates FI accounting documents. A GR in MIGO creates a BKPF/BSEG entry. A billing document in VF01 creates a BKPF/BSEG entry. A payroll run creates salary postings. Manual journal entries are posted using FB01 for items like bank charges, depreciation provisions, and accruals. All of these entries flow into the General Ledger using transaction code FB50.

Step 2 — Account Payables and Receivables Reconciliation

Before month-end close, the finance team reconciles all open items. For Accounts Payable, the team uses FBL1N to list all vendor open items and checks that every purchase invoice (posted via MIRO) has a corresponding payment or is within its payment terms. For Accounts Receivable, FBL5N is used to check all customer open items and chase overdue invoices. The reconciliation account balance in the G/L (SKA1/SKB1) must match the sub-ledger totals exactly — this is a critical SAP control.

Step 3 — Asset Depreciation Run — AFAB

Fixed asset depreciation is calculated and posted automatically using transaction AFAB. SAP reads all asset master records from the Asset Accounting module (AA), calculates depreciation according to the depreciation key configured for each asset, and posts a journal entry: Debit Depreciation Expense, Credit Accumulated Depreciation. This posting appears in BKPF/BSEG and affects the G/L balances for the period.

Step 4 — Foreign Currency Revaluation — FAGL_FC_VAL

For any open items in foreign currencies (customer invoices in USD, vendor invoices in EUR), SAP revalues these at the month-end exchange rate using FAGL_FC_VAL. Exchange rate gains and losses are posted automatically. This is a critical step for any company with international transactions.

Step 5 — Period Close and Financial Statements — S_ALR_87012284

Once all transactions are recorded and reconciled, the period is closed using OB52 (close posting periods for normal postings). The financial statements are generated using S_ALR_87012284 (Balance Sheet) and S_ALR_87012285 (Profit and Loss). The SAP system produces these reports directly from the G/L balances stored in FAGLFLEXA (S/4HANA) or GLT0 (ECC).

👥 Hire-to-Retire (H2R) — Employee Lifecycle in SAP

The Hire-to-Retire process covers the complete lifecycle of an employee in SAP — from the moment they are hired until they retire or leave the organisation. This scenario is essential for SAP HR (HCM) consultants and is increasingly important as organisations move to SAP SuccessFactors integrated with core HR. Let us walk through a real scenario of hiring a new Finance Manager at a large Indian conglomerate.

🏭 Plan-to-Produce (P2P) — Manufacturing Order Cycle

The Plan-to-Produce process covers the full manufacturing cycle in SAP PP — from demand planning and Material Requirements Planning (MRP) through production order execution and goods receipt of the finished product into stock. This scenario is essential for any SAP PP consultant or ABAP developer working in manufacturing industries. Let us walk through a real scenario at an automotive parts manufacturer producing 200 units of a gearbox assembly.

Step 1 — Sales & Operations Planning (SOP) — MC81

The planning team creates a demand plan for 200 gearbox assemblies (GEAR-ASSY-001) for the next month using Sales and Operations Planning (MC81). This creates a Planned Independent Requirement (PIR) in table PBIM. The PIR tells MRP that 200 units will be needed and triggers the planning run.

Step 2 — Material Requirements Planning (MRP) — MD01N

The MRP controller runs the planning run using MD01N. SAP explodes the Bill of Materials (BOM from STKO/STPO) and checks current stock levels (MARD) against the requirements. For items below the reorder point, SAP automatically creates Planned Orders for production and Purchase Requisitions for purchased components. The planning result can be viewed in MD04 (Stock/Requirements List).

Step 3 — Production Order Creation — CO01

The production supervisor converts the Planned Order into a Production Order using CO01 or CO40. The production order contains all the routing operations (from PLPO) and the complete component list from the BOM (STPO). The production order is stored in tables AUFK (order header) and AFKO (order-specific data). Components are reserved in warehouse using table RESB.

Step 4 — Goods Issue to Production Order — MIGO (261)

Before production starts, the warehouse issues all raw material components to the production order using MIGO with movement type 261. For example, 200 gear shafts, 400 bearings, and 200 gear housings are issued. Each goods issue creates a material document (MKPF/MSEG) and reduces stock in MARD. The cost of the issued materials is charged to the production order.

Step 5 — Production Confirmations — CO11N

As production progresses, the machine operator confirms completed quantities at each work centre operation using CO11N. This records the actual labour time and machine time spent. The actual costs (labour, machine, overhead) are posted to the production order using the activity type rates configured in CO. The order status changes from REL (Released) to CNF (Confirmed) as operations are completed.

Step 6 — Goods Receipt of Finished Goods — MIGO (101)

When all 200 gearboxes are assembled, the production team performs a Goods Receipt against the production order using MIGO (movement type 101). The finished goods stock in MARD increases by 200 units. An accounting document is created: Debit Finished Goods Inventory, Credit Production Order (settling the production costs). The production order is then settled and closed using KO88.

💻 Real ABAP Development Scenario — Custom Report

In every SAP implementation, standard reports do not always meet every business requirement. A very common real scenario in SAP ABAP development is building a custom Purchase Order aging report that shows all open purchase orders along with how many days each PO has been open, the total value, and the GR status. This type of report is requested in almost every MM implementation. Here is the real ABAP code pattern used for this scenario:

"Real Scenario: Purchase Order Aging Report
"Shows all open POs with days open and GR status

REPORT zpo_aging_report.

TYPES: BEGIN OF ty_po,
         ebeln  TYPE ekko-ebeln,   "PO Number
         lifnr  TYPE ekko-lifnr,   "Vendor
         bedat  TYPE ekko-bedat,   "PO Date
         matnr  TYPE ekpo-matnr,   "Material
         menge  TYPE ekpo-menge,   "Order Qty
         wemng  TYPE eket-wemng,   "GR Qty
         netpr  TYPE ekpo-netpr,   "Net Price
         days_open TYPE i,           "Days PO is open
       END OF ty_po.

DATA: lt_po  TYPE TABLE OF ty_po,
      ls_po  LIKE LINE OF lt_po,
      lv_today TYPE sy-datum.

lv_today = sy-datum.

"Step 1: Read open purchase orders from EKKO + EKPO
SELECT ekko~ebeln ekko~lifnr ekko~bedat
       ekpo~matnr ekpo~menge ekpo~netpr
  FROM ekko
  JOIN ekpo ON ekpo~ebeln = ekko~ebeln
  INTO TABLE @lt_po
  WHERE ekko~bstyp = 'F'       "Purchase Orders only
    AND ekko~loekz = ' '      "Not deleted
    AND ekpo~elikz = ' '.    "Delivery not completed

"Step 2: Calculate days open and add GR qty from EKBE
LOOP AT lt_po INTO ls_po.
  ls_po-days_open = lv_today - ls_po-bedat.

  "Get total GR quantity from purchasing history
  SELECT SUM( menge ) FROM ekbe
    INTO @ls_po-wemng
    WHERE ebeln = @ls_po-ebeln
      AND   vgabe = '1'.    "Goods Receipt transactions

  MODIFY lt_po FROM ls_po.
ENDLOOP.

"Step 3: Display using ALV Grid
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
  EXPORTING
    i_structure_name = 'ZTY_PO'
  TABLES
    t_outtab         = lt_po.

This pattern of joining EKKO and EKPO then enriching with EKBE data is used in almost every real SAP MM project. The same approach can be extended to check vendor performance, procurement analytics, or budget consumption reporting. In a real project, you would also add selection screen parameters (company code, plant, date range, vendor) and use a field catalogue for the ALV display.

⚠️ Real Error Scenarios in SAP — How to Resolve Them

One of the most practical aspects of understanding real scenarios in SAP is knowing how to handle real errors that occur in live systems. Every SAP consultant will encounter these errors repeatedly in their career. Understanding why they occur and how to fix them is what makes a good consultant great.

Error 1 — "No Goods Receipt Possible" When Creating MIRO

This error occurs when the finance team tries to post an invoice in MIRO but the GR has not yet been posted against the Purchase Order. The root cause is that the PO has the GR-Based Invoice Verification flag (WEBRE) set in EKPO, meaning SAP requires a goods receipt before an invoice can be posted. The solution is to first post the GR in MIGO (movement type 101) referencing the PO, and then post the invoice in MIRO.

Error 2 — Credit Block on Sales Order (VA01)

In a real O2C scenario, when the sales team tries to create a sales order for a customer who has exceeded their credit limit, SAP automatically places a credit block. The sales order is saved but cannot proceed to delivery. The credit block must be released by an authorised person using VKM3 (Release Sales Orders). In the meantime, the customer's finance controller should review the overdue invoices and either collect payment or request a temporary credit limit increase via FD32 (Change Customer Credit Data).

Error 3 — "Account Determination Error" in MIGO or VF01

This is one of the most common real errors in SAP FI integration. It occurs when SAP cannot find the correct G/L account to post to because the account determination configuration in OBYC (for MM transactions) or VKOA (for SD billing) is incomplete. The fix requires an FI/MM or FI/SD consultant to go to the relevant configuration transaction, identify the missing combination of valuation class, transaction key, and chart of accounts, and add the correct G/L account assignment.

Error 4 — Payroll Not Running — Locked Infotype

During a monthly payroll run, if an employee record is locked (the lock indicator is set in PA0003 — Payroll Status), the payroll program will skip that employee and log an error. This commonly happens when an HR administrator is in the middle of editing an infotype for an employee while payroll is running. The solution is to have the administrator unlock the record in PA0003 or wait until the next payroll run after the infotype change is saved and completed.

🔗 Real SAP Cross-Module Integration Scenarios

The true power of SAP is how all modules work together seamlessly. In a real SAP implementation, no module works in isolation. Understanding cross-module integration scenarios is what separates a module-specialist consultant from a true SAP solution architect. Here are the most important cross-module integration points that occur in every real SAP project.

MM-FI Integration — Automatic Account Determination

Every goods movement in SAP MM (MIGO) automatically creates a financial accounting document in SAP FI without any manual intervention. When you post a Goods Receipt (movement type 101), SAP uses the account determination configuration to automatically identify the correct G/L accounts to debit and credit. The valuation class of the material (stored in MBEW-BKLAS) is combined with the transaction/event key in table T030 to find the G/L account. This automatic integration means that the warehouse team can post goods movements without any knowledge of financial accounting — SAP handles all accounting automatically.

SD-FI Integration — Billing to Accounting

When a billing document is released to accounting in VF01, SAP automatically posts a financial accounting document. The revenue G/L account is determined from the condition type in the pricing procedure (table VKOA). The customer's reconciliation account (stored in KNB1-AKONT) is automatically used as the accounts receivable posting account. No manual journal entry is needed — the entire FI impact of a customer sale is handled automatically by the SD-FI integration.

PP-CO Integration — Production Order Costing

Every production order in SAP PP is automatically costed in CO. When a Goods Issue is posted to the production order (movement type 261), the cost of the materials is charged to the order. When a confirmation is posted (CO11N), the actual labour and machine time costs are charged. At month-end, the production order variance (difference between planned cost and actual cost) is settled to the product cost collector using KO88. All of this happens automatically through the PP-CO integration without any separate journal entry.

HR-FI Integration — Payroll Posting

After the payroll run is completed and approved, the payroll results are posted to Financial Accounting using transaction PC00_M40_CIPE (for India). This creates accounting entries for salary expense per cost centre (from IT 0001), deductions payable, and net pay payable to the bank. The cost centre information from HR Infotype 0001 is directly used to distribute payroll costs across different departments in CO — this is the HR-CO integration that allows management to see exact departmental labour costs.

🎯 Real SAP Scenario-Based Interview Questions

SAP interviews — especially for mid-to-senior level consultant positions — heavily focus on real scenarios. Interviewers do not want to know if you can define what a Purchase Order is. They want to know if you can handle a real business situation in SAP. Here are the most commonly asked scenario-based interview questions and how to approach each answer.

📋 SAP Real Scenarios — Master Reference Table

The table below is your complete quick reference for all major SAP end-to-end real scenarios. Use it as a revision guide before interviews, as a reference during implementation projects, and as a training resource when learning a new SAP module.

📘 Related SAP Tutorials

🔗 Important Related Links