🏗️ Setup SAP MM Org Structure — Pakistani Company Guide

🧱 Layer 1 — FI Foundation (Module: FI · "the company's books")

🔗 Layer 2 — MM↔FI Integration (Module: MM-IM/LIV + CO-ML · "goods movements become accounting")

🏠 Layer 3 — Org Units & Master Data (Module: MM · "rooms and furniture you use daily")

What this does: Creates the bare CC record in table T001 with its identity — code, name, country, currency, language, address. Nothing else yet; no variants linked.

Why direct create (and NOT EC01 / Copy CC): EC01 ("Copy Company Code") brings dependent customizing (number ranges, variants, etc.) from the source CC. Sounds convenient — but in learning you don't know what got copied silently, so when something fails later, you can't pinpoint why. Direct create via OX02 = you explicitly own every assignment. Recommended for learning. Real projects often use EC01 for speed.

Action sequence:

1. Run OX02
2. You'll see two options — click "Edit Company Code Data" (NOT "Copy, delete, check")
3. Click "New Entries" (or Ctrl+F4)
4. Fill the 6 identity fields below
5. Click the "Address" button (icon at top) → fill the address screen → Enter to confirm
6. Back on the main row, save (Ctrl+S) → save as Local Object ($TMP) for learning, or to a Transport Request for real projects
7. Repeat for CC PSAE (UAE entity, AED currency)

Identity fields:

Address fields (click Address button):

Common errors at 1A:

Verify 1A: Run SE16N → table T001 → BUKRS = PSPK → execute. One row should appear with BUTXT (name), LAND1 (country), WAERS (currency) populated. KTOPL/PERIV/FSTVA will still be empty — they get filled in 1E.

What this does: Creates just the name of the variant (e.g., "PSPK"). Think of it as creating an empty folder — the actual period rules get added in 1C via OB52.

Why it's a separate object: Multiple CCs can share one Posting Period Variant. E.g., if PSPK and PSAE both follow the same monthly close calendar, they can share one variant. SAP stores it independently from the CC so it's reusable.

Action sequence (primary — OBBP):

1. Run OBBP
2. Click "New Entries"
3. Posting Period Variant: PSPK
4. Name: PakSteel PK Periods
5. Save
6. Repeat for PSAE / "PakSteel UAE Periods"

If OBBP shows no "New Entries" button (restricted view in S/4HANA):

1. Run SM30
2. Table/View name: V_T010O
3. Click Maintain → New Entries → same fields as above
4. Save

💡 SM30 universal fallback: Whenever a T-code restricts editing in S/4, SM30 on the underlying view name almost always works. Useful views: V_T010O (period variant), V_T001B (period rules), V_T004V (field status), V_001S (plants).

What this does: Now that variant PSPK exists (from 1B), tells SAP "for variant PSPK, periods 1-12 of years 2025-2030 are OPEN for posting." Without this, every posting fails with "period not open."

Why so many years: Closing periods is a real business decision (month-end close). For learning, open broadly so nothing blocks you. Real projects open only current + previous month.

Action sequence:

1. Run OB52
2. Click "New Entries"
3. Add 6 rows (one per Account Type) — see table below
4. Save

The 6 rows to add for variant PSPK:

Field meanings:

Common error: "Do not enter an account for a masked account type" → you typed numbers in From/To Account when A = +. Clear those fields.

Verify 1C: SE16N → table T001B → variant PSPK → 6 rows visible.

Repeat for variant PSAE (6 more rows).

What this does: Field Status Variant (FSV) = the master rulebook saying "for this type of G/L, field X is mandatory, field Y is optional, field Z is hidden." Every FI posting checks against this.

Why COPY from 0001 (not create blank): SAP-delivered variant 0001 contains 80+ field status groups (G001 bank, G003 material consumption, G007 inventory, G030 reconciliation, etc.). Building these from scratch = days of work, easy to break. Copy gives you the full SAP-blessed template ready to use, and you can tweak individual groups later if business demands.

Action sequence:

1. Run OBC4
2. Select existing variant 0001
3. Click "Copy As..." (F6) — small copy icon in toolbar
4. Change variant key to PSPK, name to PakSteel PK FSV
5. Press Enter → popup asks "Copy all dependent entries?" → click Copy all (this copies all 80+ groups in one go)
6. Save
7. Repeat: copy 0001 → PSAE, name "PakSteel UAE FSV"

If variant 0001 not in your client (rare in IDES; common in fresh customizing clients):

• Ask Basis to copy from client 000 via SCC1
• OR copy any other variant present (they all have the same field status groups)

Verify 1D: OBC4 → double-click variant PSPK → 80+ field status groups visible.

What this does: ONE screen that shows ALL the CC's financial assignments. Connects PSPK to: Chart of Accounts, Fiscal Year Variant, Posting Period Variant (from 1B/1C), Field Status Variant (from 1D), and a few smaller settings.

Why one screen, not 5: You COULD use OB62 (chart), OB37 (FY), OBBP_ASSIGN (period variant), OBC5 (field status) separately. OBY6 collapses them all into one view — easier to verify and faster to set up.

Action sequence:

1. Run OBY6
2. Select CC PSPK → click 🖉 Details (or double-click the row)
3. Fill the fields below
4. Save
5. Repeat for PSAE

Common errors at 1E:

Verify 1E: Re-open OBY6 → PSPK → all fields above show your values. Or SE16N → T001 → fields KTOPL, PERIV, XPERV, FSTVA all populated for PSPK.

What this does: Every FI document (vendor invoice, payment, GR posting, GI, journal) needs a unique number. Number ranges = the "pools" SAP draws from. Without these, FI postings fail with "Document number not in range XX defined for CC YYYY."

Why this is the #1 missed step: Number ranges are NOT auto-created with a new CC. OX02 only writes to T001; ranges in table NRIV stay empty. SAP delivers them for CC 0001 — your new CC starts empty.

Why OBH1 (copy from 0001) often does nothing in S/4HANA: Modern S/4 restricts cross-CC copy of number ranges for transport safety. The transaction "succeeds" silently without copying. Manual FBN1 is more reliable.

Action sequence (manual — 7 ranges):

1. Run FBN1
2. Company Code: PSPK
3. Click "Change Intervals" (NOT "Maintain Groups")
4. For each of the 7 ranges below, click "Insert Interval" (Shift+F1) → enter values → Enter
5. Save (truck icon) → dismiss "Transport Number Range Intervals" info popup with ✓
6. Repeat all 7 ranges for CC PSAE

The 8 ranges to create (use Year 9999 for evergreen — no future maintenance):

⚠️ Why range 39 is included: Many IDES installations map doc type SA (G/L journal) to range 39 instead of 51 via OBA7. To be safe, create BOTH ranges. To verify which range your SA actually uses: OBA7 → SA → check "Number range" field.

Field meanings in each FBN1 row:

⚡ IMPORTANT — Year column behavior: The Year column is YEAR-SPECIFIC, not "valid through." If you enter 2030, the range is ONLY valid for fiscal year 2030 — postings in 2026 will fail with "number range XX missing for year 2026".

Best practice: use Year 9999 — SAP treats this as "valid for ALL fiscal years" (evergreen). One row covers every year forever. Real projects either:

• Year 9999 — evergreen, no maintenance needed (recommended for learning/test)
• Year-specific entries (2025, 2026, 2027...) — when finance wants strict per-year audit control

For your IDES learning: use Year 9999 in all ranges to avoid the trap of "FY year mismatch" errors when posting in any year.

Popups you'll see (and how to handle):

Verify 1F: FBN1 → CC PSPK → Change Intervals → all 8 ranges visible with Year 9999.
Or SE16N → table NRIV → SUBOBJECT = PSPK → 8 rows.

What this does: Sets posting authority limits per user. SAP needs to know "how much can this user post in a single document, and what payment differences are acceptable?" The blank group is the default catch-all for any user not assigned to a specific group.

Why mandatory: Without ANY tolerance group, users either get blocked entirely OR can post unlimited amounts (audit nightmare).

Action sequence:

1. Run OBA4
2. Click "New Entries"
3. Fill all fields below
4. Save
5. Repeat for PSAE (currency AED)

How users get assigned to a tolerance group: SU01 → user → Parameters tab → parameter TGR. If blank, user falls into the blank default group automatically.

💡 Real-world tiering: Junior buyer = 1M PKR/doc · Manager = 10M · Director = 100M · CFO = unlimited. Each tier = its own group, assigned per user via SU01.

Verify 1G: SE16N → table T043T → CC PSPK → one row with all your values.

What this does: S/4HANA uses the Universal Journal (table ACDOCA) — a single unified ledger replacing the separate FI + CO + ML tables from ECC. Every Company Code must be:

1. Assigned to a Ledger (default Leading Ledger = 0L)
2. Linked to an Accounting Principle (IFRS, Local GAAP, etc.)

Why mandatory: ACDOCA stores every posted line with a ledger + accounting principle reference. Without these for your CC, the Universal Journal engine rejects all postings.

Action sequence:

1. Run FINSC_LEDGER (or SPRO → FI → FA Global Settings → Ledgers → Ledger → Define Settings for Ledgers and Currency Types)
2. On the Ledger overview, click on row OL (Leading Ledger) to highlight it
3. In LEFT tree, double-click "Company Code Settings for the Ledger"
4. You see CCs already assigned (0001, 1000, 2000, etc.). Check if PSPK is already there.
5. If PSPK is NOT in list → New Entries, add row with values below
6. If PSPK IS in list but Accounting Principle column is BLANK → click into the cell → type 60 → Enter
7. Save (Ctrl+S) → Local Object / TR
8. Repeat for PSAE (or use EC01 copy method — see 1L)

Required fields:

Common errors at 1H:

Verify 1H: Run SE16N → table FINSC_LD_CMP → BUKRS = PSPK → execute. One row should show with RLDNR = 0L and ACCOUNT_PRINCIPLE filled.

What this does: Document Splitting splits every FI doc by characteristics (Profit Center, Segment, Business Area) for fine-grained reporting. To work, every G/L account must be classified into an Item Category (Cash, Vendor, Customer, Material, Asset, Expense, Revenue, etc.). The splitter uses the category to decide HOW to allocate the line.

Why mandatory: Without classification, the splitter doesn't know what kind of account a G/L is → rejects the posting.

Important — this is CHART-LEVEL config: Once you classify a G/L for chart INT, it applies to ALL CCs using INT chart. So you do this ONCE for the chart, not per CC. PSAE will benefit automatically.

Action sequence:

1. Run SPRO → click SAP Reference IMG button
2. Navigate (expand each ▶):
   • Financial Accounting
   • → General Ledger Accounting
   • → Business Transactions
   • → Document Splitting
   • → Classify G/L Accounts for Document Splitting
3. Click 🕓 execute icon
4. Chart of Accounts: INT → Enter
5. Click New Entries
6. Add classifications (ranges save lots of time):

Recommended classification ranges for INT chart:

Save (Ctrl+S) → Local Object / TR.

If category codes differ: Press F4 in the Category field — different IDES/S4 versions use different category numbering. Pick by NAME ("Cash Account", "Vendor", "Material" etc).

Common errors at 1I:

Verify 1I: SE16N → table T8G17A → KTOPL = INT → your classifications visible. Better: try F-02 (Step 2) — if it posts, classifications are working.

What this does: G/L accounts exist at TWO levels:

When you create a new CC via OX02, its SKB1 is EMPTY. You must extend chart-level G/Ls down to your CC before any FI posting can use them. FS00 is the T-code.

How many G/Ls to extend now:

• Minimum for F-02 smoke test (Step 2): just 2 (bank/cash)
• For full MM journey: ~15-20 (cash, vendor recon, customer recon, GR/IR, inventory, consumption, revenue)

Action sequence (per G/L):

1. Run FS00
2. G/L Account: 100000 · Company Code: PSPK
3. Click "Create with Template" icon (paper-with-pencil at top toolbar)
4. Reference popup:
   • G/L Account: 100000 (same)
   • Company Code: 0001 — or try 1000, 2000 if 0001 doesn't have it
5. Press Enter → all tabs auto-populate from source
6. Quick review:
   • Type/Description: name, account group (auto)
   • Control Data: Account currency PKR or blank, Line Item Display ✓, Sort Key 001
   • Create/bank/interest: Field Status Group = G005 (Bank) or G001 (General)
7. Save (Ctrl+S) → Local Object / TR
8. Success: "Account 100000 was created in PSPK"

Minimum 2 G/Ls for F-02 (do these now):

Full set for all MM scenarios (extend as you reach each scenario):

Bulk method (for 15+ G/Ls): FS15 (Send G/L Master via ALE) or copy all SKB1 entries from source CC. Saves hours.

Common errors at 1J:

Verify 1J: SE16N → table SKB1 → BUKRS=PSPK → rows visible for extended G/Ls.

What this does: OMSY sets the CURRENT period for Materials Management (per CC, per year). This is separate from FI posting periods (OB52) — MM tracks its own "current month" for material valuation, stock movements, period closing.

Why it's separate from OB52: MM has its own monthly closure cycle (MMPV) and needs its own period state per CC. Without OMSY, MM doesn't know "what month is open" for the CC → blocks ALL material activity (creation, GR, GI, valuation).

Action sequence:

1. Run OMSY (or SPRO → MM → Logistics General → Material Master → Basic Settings → Maintain Company Codes for Materials Management)
2. Find your CC in the list. PSPK is likely NOT initialized yet (no Year/Period set)
3. Click on PSPK row → enter values directly OR click New Entries if PSPK not in list
4. Fill these fields:

Repeat for PSAE — same year + period (and same ABp/DBp settings).

Save (Ctrl+S) → Local Object / TR.

Common errors at 1K:

Verify 1K: Run MMRV → enter CC PSPK → shows current period + previous period status. Or SE16N → table MARV → BUKRS=PSPK → row exists with PERYR and PERIO set.

Run these 10 checks IN ORDER. If all pass, CC is ready for plant creation (Step 3). If any fails, the table tells you which sub-step to revisit.

Quick database-level sanity check: Run SE16N → table T001 → BUKRS = PSPK. The row should show all these populated:

• BUKRS = PSPK · BUTXT = PakSteel Industries · LAND1 = PK · WAERS = PKR
• KTOPL = INT · PERIV = K4 · XPERV = PSPK · FSTVA = PSPK

If all 10 checks pass → CC is FULLY FUNCTIONAL for both FI AND MM. Move to Step 2 (F-02 smoke test if not done) or directly to Step 3 (Plants).

Why use EC01: You just spent ~75-90 minutes configuring PSPK through 11 sub-steps. Doing it all again for PSAE is painful. EC01 is SAP's official "Copy Company Code" transaction that brings 80% of customizing in one click. You then change only the country-specific essentials (currency, country, address, tax IDs).

📋 What EC01 COPIES automatically (you don't redo)

⚠️ What you MUST CHANGE after EC01 copy (mandatory edits)

🔄 EC01 Action Sequence (5-10 min)

1. Run EC01
2. Copy button → enter:
   • Source Company Code: PSPK (your working CC)
   • Target Company Code: PSAE
3. Press Enter → confirmation popup with copy options. Tick (✅):
   • ✅ Copy G/L master records (copies all SKB1 from PSPK to PSAE)
   • ✅ Copy number ranges
   • ✅ Copy tax codes
   • ✅ Copy account assignments
   • ☐ Copy customer master (skip — usually empty)
   • ☐ Copy vendor master (skip — usually empty)
4. Execute → wait 1-2 minutes → success message lists what was copied
5. Save (Ctrl+S) → Local Object / TR

🛠️ Post-Copy Adjustments (5-10 min)

1. Change identity fields via OX02:
   • OX02 → select PSAE → click Edit Company Code Data
   • Change Currency: AED · Country: AE · City: Dubai · Name: PakSteel Trading FZ-LLC
   • Click Address button → update street, postal, region (Emirate), phone, tax numbers (TRN instead of NTN/STRN)
   • Save
2. ⚡ Run FINSC_LEDGER for PSAE (this DOESN'T auto-copy):
   • FINSC_LEDGER → Ledger 0L → Company Code Settings for the Ledger
   • New Entries → CC = PSAE, FYV = K4, PPV = PSAE (or PSPK if sharing), Acctg Principle = 60, 1st FI Currency = 10
   • Save
3. Decide on Posting Period Variant:
   • Option A (simple): Keep PSAE using PSPK's posting period variant → no new variant needed
   • Option B (independent): Create new PSAE variant via OBBP → OB52 to open periods → OBY6 reassign
4. Verify Field Status Variant:
   • Usually OK to share PSPK's FSV — most companies in same group use identical FSV
5. Update tax numbers properly:
   • UAE uses TRN (Tax Registration Number) for VAT — STCD1 = your UAE VAT registration if applicable
   • STCD2 — blank or other UAE-specific code

✅ Verify PSAE after EC01 copy

⚠️ Note: Even with EC01, the S/4HANA-specific FINSC_LEDGER step (1H) must be done manually for each new CC. Doc splitting classifications (1I) are chart-level so apply automatically.

Why this is critical: Tolerance keys control price/quantity variance checks in MM transactions. When you create a NEW CC (like PSPK), default tolerance keys are NOT auto-copied. First PO/MIGO/MIRO transaction will fail with errors like:

This step PREVENTS those errors.

📋 All MM Tolerance Keys — what each controls

🛠️ Configuration Path — Two T-codes for Different Tolerances

📋 Step-by-Step Configuration

Sub-step 1N.1 — Configure PE (Price Variance for PO) via SPRO

1. /oSPRO → click SAP Reference IMG
2. Navigate: Materials Management → Purchasing → Purchase Order → Set Tolerance Limits for Price Variance
3. Click the 🕒 Activity icon
4. New Entries → fill:
   • Tolerance Key: PE
   • Company Code: PSPK
   • Amounts in: PKR (or auto-derived)
   • Lower Limit → Absolute → Check Limit ✓ → Value 50000
   • Lower Limit → Percentage → Check Limit ✓ → % 20
   • Upper Limit → Absolute → Check Limit ✓ → Value 50000
   • Upper Limit → Percentage → Check Limit ✓ → % 20
5. Save → Local Object
6. Repeat for SE if needed (same values)

Sub-step 1N.2 — Configure PP, BD, DQ, VP (Invoice Verification) via OMR6

1. /oOMR6
2. For each key, click New Entries and add:

Sub-step 1N.3 — Configure GR Tolerances (B1, B2, VP) via OMC0

1. /oOMC0
2. New Entries → add B1, B2, VP for company code PSPK with relaxed limits

🪂 ALTERNATIVE — OMRM Workaround (Change Error to Warning)

If you can't configure tolerances properly (e.g., F4 dropdown issues, "Enter values for non-key fields" errors), use OMRM to change message severity from Error to Warning. PO/MIRO will save with warning instead of blocking.

1. /oOMRM (Configure System Messages — MM)
2. Change Area at top to relevant area (M8, 06, ME, etc.)
3. New Entries → fill:
   • MsgNo: 215 (for PE tolerance)
   • User Name: blank (applies to all)
   • Online: W
   • BatchI: W
   • Standard: W
4. Save → Local Object

🚨 Troubleshooting Common Errors

🇵🇰 Pakistani Industry Recommended Tolerances

🎓 Interview-Ready Q&A

📚 Source: Verified against saponlinetutorials.com — Tolerance Limits + SAP Community — PE Tolerance F4 Issue + SAP Help — Tolerance Limits for Invoice Postings.

Why does S/4HANA force this? In old ECC, Material Ledger was optional. In S/4HANA it's mandatory because stock values now live inside the Universal Journal (ACDOCA) in multiple currencies — and the Material Ledger is the engine that feeds it. No engine = no postings.

🛠️ The fix is 3 layers, IN THIS ORDER (each unlocks the next)

Layer 1 — Assign an ML "Type" to your plants — OMX3

Plain words: the ML Type is the diary's format (which currencies it tracks). Without a type assigned, the activation checkbox in OMX1 is GREYED OUT — this confused us for 10 minutes!

1. OMX3 (Assign Material Ledger Types to Valuation Area)
2. Rows PK01 / PK02 / PK03 / AE01 → Mat. Ledger Type = Y001 (same type all working IDES plants use — proven compatible)
3. Save → Local Object

Layer 2 — Activate ML — OMX1

1. OMX1 → your plant rows now show the ML Type → checkbox is editable
2. Tick ML Act. ✓ for each plant
3. Price Deter. = 2 (Transaction-Based — the simple mode: works like classic moving average. Mode 3 = Actual Costing needs month-end CKMLCP runs — skip for learning)
4. Save → warning "live data must be converted" → confirm

Layer 3 — The "opening ceremony" — CKMSTART

Plain words: activation is just a flag. CKMSTART actually converts the data and flips the productive switch. Run it twice: test first, then real.

1. CKMSTART → Plant: PK01 (use multi-select ➡️ to add all plants at once)
2. Exchange Rate Type: blank · Background Processing: ☐ UNTICK (online is instant for new plants) · Test Run: ✓
3. Execute → log must show "Plant can be set as productive" + 0 errors
4. F3 back → UNTICK Test Run → Execute again
5. Log now says "Plant is now productive" ✅ — done forever (irreversible, but that's fine — it's mandatory anyway)

🚨 Gotchas we hit live (so you don't)

📚 Verified: SAP Community — CKMSTART preparation steps · saponlinetutorials — Activate ML for Valuation Areas

🚪 Gate 1 — Invoice Verification parameters: the TWIN tables T169P + T169V — OMRG + OMR2

❌ M7 001 — "Check table 169P: entry PSPK does not exist" (hits at MIGO)
❌ M8 100 — "Table T169V: entry PSPK does not exist" (hits later at MIRO!)

Plain words: two tiny one-row-per-company "rulebook" tables for invoice verification. T169P = checking rules (duplicate invoices, amount checks) — even a goods receipt reads it. T169V = default values (which tax code MIRO pre-fills). New CC = no rows = blocked. Fix BOTH at once — they fail at different transactions, days apart, and confuse everyone.

1. T169P: OMRG (or SM30 → view V_169P_S) → New Entries → CoCd PSPK (+ PSAE) — leave Threshold/Percentage blank → Save
2. T169V: OMR2 (Maintain Default Values for Tax Codes) → New Entries → CoCd PSPK (+ PSAE) · Default tax code = I0 → Save. Bonus: MIRO now pre-fills the tax code for you

🚪 Gate 2 — Stock-posting tolerances — OMC0

❌ M8 215 — "Maintain tolerance limits for tolerance key VP (CoCode PSPK)"

Plain words: VP = "how much may this goods receipt move my material's average price before SAP complains?" A new CC has NO rules — and for SAP, no rules doesn't mean 'anything goes', it means 'nothing goes'.

⚠️ Read the error's small print: for stock postings it's OMC0 (Inventory Management) — NOT OMR6 (invoices). Same M8215 number, different config place!

1. OMC0 → New Entries → 3 rows for the CC:

Remember the radio-button rule from 1N: every section with a typed value needs its "Check Limit" radio selected — else "Enter values in work area" error.

🚪 Gate 3 — G/L accounts must exist IN the company code — FS00

❌ M7 055 — "G/L account 300000 does not exist in company code PSPK"

Plain words: The chart of accounts (INT) is like a song catalog — the song exists, but each company code must add it to its own playlist. OBYC points your GR to accounts 300000 (inventory) and 191100 (GR/IR) — BOTH must be extended to the CC, because one GR posts to both at once.

1. FS00 → G/L 300000 · CC PSPK → With Template button (don't press Enter first — "does not exist" on Enter is normal, it's why you're here!)
2. Template: 300000 / CC 0001 (or 1000 if 0001 lacks it) → Enter
3. Repeat for 191100

⚠️ The 2 checkbox gotchas that bite later:

Pre-extend checklist for a new CC (do all at once, 2 min each): 300000 Inventory RM · 191100 GR/IR · 160000 AP recon (done in BP step) · PRD price-difference account (e.g., 231000) · bank/cash (113100/100000) for payments.

🚪 Gate 4 — FI document number ranges — FBN1

❌ NR751 — "Interval 45/Subobject PSPK To Year 2026 does not exist for object RF_BELEG"

Plain words: every FI document takes a numbered ticket from a ticket roll. Each document type pulls from a specific roll (our WE goods-receipt doc → roll 45). New CC = missing rolls = no ticket = no document. This error appearing is actually GOOD news — it means everything else works and SAP reached the very last step: numbering your document.

1. FBN1 → CC PSPK → Change Intervals → note what exists
2. Insert the missing rolls (standard pattern NN → NN00000000–NN99999999):

⚠️ Three FBN1 gotchas:

• Year 2026 vs 9999: year-specific intervals DIE on 1-Jan of next year (NR751 returns for everything!). Use 9999 on test systems. Real companies maintain new-year intervals as a year-end closing task.
• "Copy intervals from CC" only works into an EMPTY company code. If even one interval exists, copy refuses → insert the missing rows manually.
• Your system's doc-type→range mapping may be NON-STANDARD. Our IDES maps MIRO's RE doc to range 36 (standard is 51!). Proactive check: OBA7 → double-click each doc type you'll use (WE, RE, KR, KZ, ZP, SA) → note its "Number range" → make sure every one exists in FBN1. The error itself (NR751 / F5150) always names the missing interval — read it, insert it, move on.

🏆 The complete 9-Gate Gauntlet — quick reference (what we survived live)

Plain words: a brand-new company code in S/4HANA must pass ALL of these before its first complete P2P posting. SAP shows them ONE AT A TIME — bookmark this table and fix all 9 up front instead.

✅ After gate 9: "Material document posted" (GR works) — and after gate 10's repeats, MIRO and F-53 post too = the complete P2P cycle. Dr 300000 Inventory / Cr 191100 GR/IR at GR → GR/IR cleared against vendor at invoice → vendor cleared against bank (−2% cash discount!) at payment. Every config piece fires automatically. That's MM-FI integration working end-to-end.

📚 Verified: SAP Community — T169P fix · T169P per-CC requirement · Tolerance limits

What: Sales Org = the SD equivalent of Purch Org — represents the legal selling entity. Stored in TVKO.

SPRO Path: Enterprise Structure → Definition → Sales and Distribution → Define, copy, delete, check sales organization

Action:

1. Run OVX5 → New Entries
2. Create 2 sales orgs (one per CC):

What: Distribution Channel = HOW you sell (direct, wholesale, retail, intercompany). Stored in TVTW.

SPRO Path: Enterprise Structure → Definition → Sales and Distribution → Define, copy, delete, check distribution channel

For STO learning, create:

What: Division = product category (e.g., Steel Products, Cement, Services). Stored in TSPA.

SPRO Path: Enterprise Structure → Definition → Logistics – General → Define, copy, delete, check division

For learning:

SPRO Path: Enterprise Structure → Assignment → Sales and Distribution → Assign sales organization to company code

Assignments:

What: Sales Area = unique combination of (Sales Org + Distribution Channel + Division). It's the SD equivalent of "Purch Org + Plant" — defines what a sales unit can sell.

SPRO Path: Enterprise Structure → Assignment → Sales and Distribution → Set up sales area

Create these sales areas:

What: Tells SAP which plants can ship for which sales orgs. CRITICAL for STO — supplying plant must be linked to supplying CC's sales org.

SPRO Path: Enterprise Structure → Assignment → Sales and Distribution → Assign sales organization → Distribution Channel → Plant

Assignments for STO:

What: Shipping Point = the loading dock / shipping desk that processes outbound deliveries. Required for any SD delivery (STO or sales).

SPRO Path: Enterprise Structure → Definition → Logistics – Execution → Define, copy, delete, check shipping point

For learning, create:

SPRO Path: Enterprise Structure → Assignment → Logistics – Execution → Assign shipping point to plant

Assignments:

What: Each plant in an inter-co STO needs a representation in the OTHER CC's books:

• Receiving plant becomes a CUSTOMER in supplying CC (so supplier can bill it)
• Supplying plant becomes a VENDOR in receiving CC (so receiver has AP)

Action:

1. Run BP
2. Create Customer (role FLCU01) representing AE01 plant in PSPK CC + sales area PKSO/20/10
3. Create Vendor (role FLVN01) representing PK03 plant in PSAE CC + Purch Org AELO
4. Document the customer # and vendor # — used in OMGN (Step 14) and OBYA

What: When PSPK posts a CR (sale to PSAE) and PSAE posts a DR (purchase from PSPK), SAP needs a clearing G/L to balance the two CCs' books. OBYA defines these G/Ls per CC-pair.

SPRO Path: Financial Accounting (New) → General Ledger Accounting → Business Transactions → Prepare Cross-Company Code Transactions

Action:

1. Run OBYA
2. Enter CC pair: PSPK + PSAE
3. Fill clearing accounts:
   • Receivables side (PSPK side): G/L for "Receivable from PSAE" (e.g., 149xxx)
   • Payables side (PSAE side): G/L for "Payable to PSPK" (e.g., 159xxx)
   • Posting Keys: typically 01 (Customer Dr) and 31 (Vendor Cr)
4. Save

What: Work Center = where production happens (machine, assembly line, manual workstation). Holds capacity, scheduling, costing data.

SPRO Path: Master data, not config. Run T-code directly.

Action:

1. Run CR01
2. Plant: PK01 · Work Center: WC-MIL01 (Milling Center 1) · Category: 0001 (Machine)
3. Basic Data tab: Description, Person Responsible, Usage = 009 (Routings + Networks)
4. Default Values tab: Setup time, machine time, labor time
5. Capacities tab: Capacity category (machine/labor), available capacity
6. Costing tab: Cost Center (e.g., PKKHI-PROD), Activity Type
7. Save

Repeat for other work centers as needed (WC-WLD01 welding, WC-PCK01 packing, etc.)

What: BOM = the recipe — what components and quantities are needed to make 1 unit of a finished product.

Already covered in p2p-scenarios.html Scenario 9 (Subcontracting) — same T-code.

Quick action:

1. Run CS01
2. Material: finished product (e.g., FERT-REBAR-01) · Plant: PK01 · BOM Usage: 1 (Production)
3. Component: raw material (e.g., HALB-BILLET-01) · Quantity per output
4. Save → BOM number assigned

What: Routing = the production process steps. Defines WHICH work center does WHAT operation in WHAT sequence with WHAT time.

Action:

1. Run CA01
2. Material: FERT-REBAR-01 · Plant: PK01 · Group/Counter auto
3. Header data: Usage 1, Status 4 (Released)
4. Operations:
   • Op 0010: Work Center WC-MIL01 · Standard text "Mill Billet" · Time 30 min/TO
   • Op 0020: Work Center WC-WLD01 · "Weld rebar" · 15 min/TO
5. Save → Routing # assigned

What: Production Order Type = like PO Doc Type but for production. Standard delivered = PP01.

SPRO Path: Production → Shop Floor Control → Master Data → Order → Define Order Types

For learning: Use standard PP01 — no custom needed.

What: Creates a Production Order — the document that tracks one production run from start to finish.

Action:

1. Run CO01
2. Material: FERT-REBAR-01 · Plant: PK01 · Order Type: PP01
3. Quantity: 100 TO · Dates auto-calculated from routing
4. Save → Production Order # (e.g., 100001234)
5. Release: CO02 → Functions → Release
6. NOW you can do GI mvt 261 to this order (Scenario 3 in p2p-scenarios.html)

What: Define number range intervals for Business Partners — different ranges for different BP types.

SPRO Path: Cross-Application Components → SAP Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings → Define Number Ranges

Action:

1. Run BUCF
2. Click Change Intervals
3. Add intervals (or use existing):

Save → Local Object.

What: Grouping = which type of BP gets which number range. Each grouping links to ONE number range and defines whether numbers are internal/external + same as customer/vendor.

SPRO Path: Cross-Application Components → SAP Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings → Define Groupings and Assign Number Ranges

Action:

1. Run BUC2
2. Click New Entries
3. Define groupings:

Save → Local Object.

💡 "Same Number" flag is critical — when checked, BP # matches LFA1's LIFNR (vendor) or KNA1's KUNNR (customer). Makes data migration cleaner.

What: Defines which roles exist (Vendor, Customer, Employee, Bank, etc.). SAP delivers ~30 standard roles. You can create custom Z-roles (your IDES had YTM-VENDOR, YTM-CUSTOMER, etc.).

SPRO Path: Cross-Application Components → SAP Business Partner → Business Partner → Basic Settings → Business Partner Roles → Define BP Roles

Standard Vendor Roles (you'll see these in BP dropdown):

Standard Customer Roles (same pattern):

What: CVI ensures that when you create a BP, the system AUTO-creates the corresponding entry in classic LFA1 (vendor) or KNA1 (customer) tables. Without CVI, your BP exists but vendor/customer record doesn't — POs would fail.

This is CRITICAL in S/4HANA — without it, MM/SD don't work because they still query LFA1/KNA1.

Configuration:

1. Run SM30
2. For Customer integration: View V_TBC001 → Maintain
3. Add row: BP Grouping BPKD → Customer Account Group KUNA (or your customer group)
4. For Vendor integration: View V_TBD001 → Maintain
5. Add row: BP Grouping BPVK → Vendor Account Group LIEF (or your vendor group)
6. Save

Sync direction (V_T100C or BUCSC):

📚 Source: Verified against saplogisticsexpert.com + SAP Community Complete BP Config Guide

What: Controls which fields are required, optional, or hidden when maintaining each BP role.

SPRO Path: Cross-Application Components → SAP Business Partner → Business Partner → Basic Settings → Field Groupings → Configure Field Attributes per BP Role

For learning, accept SAP defaults. Customize only in real projects where business demands specific field mandatories.

Why: Every vendor needs a Payment Term in FLVN01 (Vendor — Finance) role. Defines when invoices are due + early payment cash discount terms. Standard SAP ships 0001-0009 — usable immediately. Custom terms (e.g., Pakistani LC, advance payment) need configuration.

SPRO Path: Financial Accounting → Accounts Receivable and Accounts Payable → Business Transactions → Incoming Invoices/Credit Memos → Maintain Terms of Payment

📋 Standard SAP Payment Terms (already in IDES — no config needed)

✅ For learning: Just use 0003 for standard B2B vendors. It teaches cash discount mechanics (a tested interview topic) without any config work.

🇵🇰 Custom Pakistani Payment Terms (optional — OBB8 creation)

If you want terms matching real Pakistani business reality, create custom codes:

🛠️ Create Custom Payment Term (Example: PK30)

1. Run OBB8
2. Click New Entries
3. Fill header:
   • Payt Terms: PK30
   • Sales Text: Pakistan Net 30 Days
   • Own Explanation: (auto-filled by SAP based on Term settings)
4. Account type: ✓ Vendor (also tick Customer if same code used for SD)
5. Default for baseline date: Select Document Date (most common in Pakistan — invoice date is the trigger)
   💡 Baseline date options: Document Date (invoice date) · Posting Date · Entry Date · No Default. Most Pakistani companies use Document Date — payment clock starts from the invoice date printed by vendor.
6. Payment Terms section → Term 1:
   • Percentage: 0.000 (no cash discount)
   • No. of days: 30
7. Leave Term 2 and Term 3 empty (no tiered discount)
8. Save → Local Object (or Transport if production)

🛠️ Create LC30 (Letter of Credit, 30 days from BL date)

1. OBB8 → New Entries
2. Payt Terms: LC30 · Sales Text: LC 30 days from BL date
3. Account type: ✓ Vendor
4. Default for baseline date: Document Date (BL date entered in MIRO)
5. Term 1: 0% / 30 days net
6. Save

🛠️ Create ADV100 (100% Advance Payment)

1. OBB8 → New Entries
2. Payt Terms: ADV100 · Sales Text: 100% Advance — pay before delivery
3. Account type: ✓ Vendor
4. Default for baseline date: Document Date
5. Term 1: 0% / -1 days (negative = pay BEFORE document date)
   ⚠️ Negative days = due before the baseline date. Some SAP versions reject this — alternative: use Term 1 = 0% / 0 days (due immediately) and handle advance via Down Payment Request (F-47).
6. Save

📊 Real Vendor → Payment Term Mapping

🎓 Interview-Ready Q&A — Payment Terms

📚 Source: Verified against help.sap.com — Terms of Payment + saponlinetutorials.com — OBB8 Tutorial

What: When CVI creates the vendor record in LFA1 alongside BP, SAP needs to know which number range to use. If you want BP # = Vendor # (e.g., BP 21 → Vendor 21), the linked vendor account group must use an EXTERNAL numeric range.

🛠️ Step 1 — Create Vendor Number Range (XKN1)

1. Run XKN1 (Vendor Number Range)
2. Click Change Intervals
3. Click Insert Interval (Shift+F1)
4. Two range patterns to choose from:

Save → Local Object.

🛠️ Step 2 — Assign Number Range to Vendor Account Group (OBAS)

1. Run OBAS (Assign Number Ranges to Vendor Account Groups)
2. Find row for your vendor account group (e.g., LIEF external, KRED internal)
3. Change "Number Range" column to your created range (e.g., 02 for alphanumeric, 03 for numeric)
4. Save

🛠️ Step 3 — Tick Same Number flag (V_TBD001)

1. Run SM30 → Table V_TBD001 → Maintain
2. Find row for your BP Grouping (e.g., GPEX) ↔ Account Group LIEF
3. Tick Same Nos. ✓ column
4. Save (will work only if account group's number range is EXTERNAL — verify via OBAS + XKN1)

📊 Alphanumeric vs Numeric — which to choose?

✅ For learning IDES (recommended): Skip XKN1/OBAS config. Just type alphanumeric vendor codes (MUGHAL21, AISHA22, etc.) when BP save prompts for external vendor number. Document the convention and move on. CVI Same-Number config is FI consultant territory.

📚 Source: saponlinetutorials.com — Vendor Number Ranges + SAP Blogs — BP CVI Overview

What: The "container" for cost objects — like the Company Code is for FI. We use the simplest model: controlling area = company code (1:1).

1. Run OKKP → select/maintain controlling area → New Entries (or Details on PSPK)
2. Fill Basic Data:

Ctrl+S → if prompted "standard hierarchy PSPKHIER does not exist, create?" → Yes.

What: Switches ON the CO functions per fiscal year. Select the PSPK row first (the left-tree folders stay greyed until a row is selected), then double-click "Activate components/control indicators" → New Entries.

Ctrl+S.

What: Links PSPK (company code) ↔ PSPK (controlling area). Without it: error KI105 "No company code assigned to controlling area" when you try to create a cost center.

1. OX19 (or OKKP → select PSPK → "Assignment of company codes") → New Entries → Company Code PSPK

Verify: FINS_CUST_CONS_CHK_P (PSPK / 0L) all green · SE16N → TKA02 shows PSPK ↔ PSPK. Then MIGO/account-assigned POs post. (The greyed "CoCd → CO Area" on OBY6 auto-displays PSPK — don't set it there.)

Initial screen: Controlling Area PSPK · Cost Center PKKHI-PROD · Valid From today · To 31.12.9999 · Reference fields = leave BLANK (only for copying an existing CC) → press Enter (no Save button here — click Master Data / Enter to reach the detail screen).

Basic Data screen (✓ = mandatory):

Ctrl+S → "Cost Center PKKHI-PROD created". Verify with KS03.

Minimum cost-center set for the scenarios:

In ECC you ran KA01 for separate cost-element masters. In S/4HANA's Universal Journal, G/L accounts ARE cost elements — set the Cost Element Category on the expense G/L in FS00 → "Edit cost element" / Control Data.

Expense G/Ls used by account-assigned POs need Cost Element Category 1, else the PO can't post to a cost center.

Safety net: if a user leaves the cost center blank on a PO line, SAP auto-fills the default set here. OKB9 → New Entries → CC PSPK + Cost Element 470000 + Cost Center PKADM-IT → Save.

⚠️ Use sparingly — silent defaulting hides user errors. Often better to make the cost center mandatory via field status.