Setup Step 1 — Create & Configure Company Code

🧱 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 from the source CC. Convenient — but in learning you do not know what got copied silently, so when something fails later you cannot 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. Two options appear — 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 (full fixes in the Issues section): "Company code already exists" → pick another code or delete via OX02 · "Currency XXX not defined" → OY03 (PKR/AED usually pre-delivered) · "Country XX not maintained" → table T005, rare in IDES · "Choose Transport Request" → click Local Object ($TMP) for learning.

Verify 1A: Run SE16N → table T001 → BUKRS = PSPK → one row with BUTXT, LAND1, WAERS populated. KTOPL/PERIV/FSTVA are still empty — they get filled in 1E.

What this does: Creates just the name of the variant (e.g., "PSPK"). Think of it as 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. If PSPK and PSAE follow the same close calendar, they can share one. 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.

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 (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): 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 into one view — easier to verify, 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: "Chart of Accounts INT not defined" → OB13 (delivered in IDES) · "Fiscal Year Variant K4 not defined" → OB29 (SAP standard) · "Posting Period Variant PSPK not defined" → you skipped 1B · "Field Status Variant PSPK not defined" → you skipped 1D.

Verify 1E: Re-open OBY6 → PSPK → all fields 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):

1. Run FBN1
2. Company Code: PSPK
3. Click "Change Intervals" (NOT "Maintain Groups")
4. For each range below, click "Insert Interval" (Shift+F1) → enter values → Enter
5. Save (truck icon) → dismiss "Transport Number Range Intervals" info popup with ✓
6. Repeat all 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. To verify which range your SA actually uses: OBA7 → SA → check "Number range" field.

⚡ 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 fail with "number range XX missing for year 2026". Best practice: use Year 9999 — SAP treats this as "valid for ALL fiscal years" (evergreen).

Field meanings: No. = range key (must match doc type's OBA7 mapping) · Year = use 9999 evergreen · From/To Number = 10-digit pool boundaries · Current Number = leave 0 · Ext (External Flag) = leave UNCHECKED for MM (SAP auto-assigns).

Popups you'll see: "Define Selection Options" (OBH1) → click = · "Variant Attributes" (OBH1) → F3 to back out, do NOT save · "Transport Number Range Intervals" (info) → dismiss with ✓ (ranges deliberately do NOT transport, to protect production's current-number counter).

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 → 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), and (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 row 0L (Leading Ledger) to highlight it
3. In the LEFT tree, double-click "Company Code Settings for the Ledger"
4. Check if PSPK is already in the list (0001, 1000, 2000 etc. usually are)
5. If PSPK is NOT listed → New Entries, add row with values below
6. If PSPK IS listed but Accounting Principle is BLANK → click the cell → type 60 → Enter
7. Save (Ctrl+S) → Local Object / TR
8. Repeat for PSAE (or use EC01 copy method — see 1M)

Common errors at 1H: "Accounting principle 60 not defined" → F4 in cell, pick from your IDES (may be 01, IFRS, LGAAP) · "Posting period variant empty" → 1B not done · "Consistency check warnings about other CCs" → pre-existing IDES issues, dismiss with ✓ · "Customizing is inconsistent: Postings of journal entries not possible" → Acctg Principle missing/wrong.

Verify 1H: Run SE16N → table FINSC_LD_CMP → BUKRS = PSPK → one row 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. You do this ONCE for the chart, not per CC. PSAE benefits automatically.

Action sequence:

1. Run SPRO → click SAP Reference IMG
2. Navigate: 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 → add classifications (ranges save time):

Save (Ctrl+S) → Local Object / TR. If category codes differ: press F4 in the Category field — different IDES/S4 versions use different numbering. Pick by NAME ("Cash Account", "Vendor", "Material").

Common errors at 1I: "View V_FAGL_SPLITGL not in directly" → use the SPRO IMG path (view name varies by release) · "Category 04000 not defined" → F4, pick valid code · Document Splitting node missing → expand "Business Transactions" first, or try Financial Accounting → FA Global Settings → Document → Document Splitting.

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

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 the F-02 smoke test (Step 2) = just 2 (bank/cash); for the 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)
4. Reference popup: G/L Account 100000 (same) · Company Code 0001 (or 1000, 2000 if 0001 lacks it)
5. Press Enter → all tabs auto-populate from source
6. Quick review: Type/Description (name, account group) · 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) → 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 (15+ G/Ls): FS15 (Send G/L Master via ALE) or copy all SKB1 entries from a source CC.

Common errors at 1J: "Account XXXXXX does not exist in chart INT" → not in SKA1; SE16N → SKA1 → KTOPL=INT to see what exists · "Account XXXXXX does not exist in source CC 0001" → try a different source CC (SE16N → SKB1 → SAKNR=XXXXXX shows which CCs have it) · "Field Status Group G005 not defined in variant PSPK" → re-copy FSV from 0001 via OBC4.

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" → blocks ALL material activity.

Action sequence:

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

Repeat for PSAE — same year + period (and same ABp/DBp settings). Save (Ctrl+S) → Local Object / TR.

Common errors at 1K: "This combination of entries does not make sense" → both ABp and DBp checked; uncheck DBp · "Period 6 not allowed" → must match current calendar month + valid year · "Entry already exists" → OMSY run before, check Display mode · "Cannot save with no posting period variant" → OBY6 (1E) didn't assign PPV.

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

Run these 10 checks IN ORDER. If all pass, the 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: SE16N → table T001 → BUKRS = PSPK. The row should show: BUKRS=PSPK · BUTXT=PakSteel Industries · LAND1=PK · WAERS=PKR · KTOPL=INT · PERIV=K4 · XPERV=PSPK · FSTVA=PSPK.

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

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

📋 What EC01 COPIES automatically

⚠️ What you MUST CHANGE after EC01 copy

🔄 EC01 Action Sequence (5-10 min)

1. Run EC01
2. Copy button → Source Company Code PSPK, Target Company Code PSAE
3. Press Enter → confirmation popup with copy options. Tick ✅: Copy G/L master records · Copy number ranges · Copy tax codes · Copy account assignments. Leave unticked ☐: Copy customer master · Copy vendor master (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: select PSAE → Edit Company Code Data → Currency AED, Country AE, City Dubai, Name PakSteel Trading FZ-LLC → Address button → update street, postal, region (Emirate), tax numbers (TRN instead of NTN/STRN) → Save
2. ⚡ Run FINSC_LEDGER for PSAE (does NOT auto-copy): Ledger 0L → Company Code Settings → 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: keep PSAE on PSPK's variant (simple), or create a new PSAE variant via OBBP → OB52 → reassign in OBY6 (independent)
4. Update tax numbers: UAE uses TRN for VAT → STCD1 = UAE VAT registration; STCD2 blank

⚠️ 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. A NEW CC has no keys, so the first PO/MIGO/MIRO fails with errors like M8 215 "Maintain tolerance limits for tolerance key PE (CoCode PSPK)" at PO save, or M8 462 "Tolerance key PP not maintained" at MIRO. This step PREVENTS them.

📋 All MM Tolerance Keys — what each controls

🛠️ Configuration Path — Three T-codes for different tolerances

1N.1 — Configure PE (PO Price Variance) via SPRO

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

1N.2 — Configure PP, BD, DQ, VP, AN, AP (Invoice Verification) via OMR6

1. /oOMR6 → for each key, New Entries:

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

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

🪂 ALTERNATIVE — OMRM Workaround (change Error to Warning)

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

1. /oOMRM (Configure System Messages — MM)
2. Change Area at top (M8, 06, ME…)
3. New Entries → MsgNo 215 (PE) · User Name blank · Online W · BatchI W · Standard W → Save

Severity reference: M8 215 (PE), M8 462 (PP), M8 463 (BD), 06 207 (tolerance variant) — all default E, change to W only in a training environment. For production, never bypass via OMRM — configure proper tolerances.

🇵🇰 Pakistani industry recommended tolerances

📚 Verified against saponlinetutorials — Tolerance Limits · SAP Community — PE Tolerance F4 · SAP Help — Tolerance Limits for Invoice Postings.

Why does S/4HANA force this? In old ECC, Material Ledger was optional. In S/4HANA it is 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.

1. OMX3 (Assign Material Ledger Types to Valuation Area)
2. Rows PK01 / PK02 / PK03 / AE01 → Mat. Ledger Type = Y001 (the 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 — 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 it's mandatory anyway)

🚨 Gotchas hit live

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

🚪 Gate 1 — Invoice Verification: 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

🚪 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 means 'nothing goes'. ⚠️ Read the 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 a song catalog — the song exists, but each company code must add it to its own playlist. OBYC points your GR to 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) → Enter
3. Repeat for 191100

⚠️ The 2 checkbox gotchas that bite later:

Pre-extend checklist for a new CC (2 min each): 300000 Inventory RM · 191100 GR/IR · 160000 AP recon · 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 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 (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 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" → ensure each exists in FBN1.

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