SAP S/4HANA IMG Configuration Reference — From Enterprise Structure to Module Settings

IMG (SPRO) settings configured while building up an S/4HANA sandbox for end-to-end testing, organized from Enterprise Structure down to module settings. Updated whenever a new setting is added.

Each table: Item / IMG path (SPRO) / T-code / Contents (the actual values configured in this system). Last updated: 2026-08-13

1. Enterprise Structure — Definition

Item IMG path (SPRO) T-code Contents / values in this system
Company code Enterprise Structure > Definition > Financial Accounting > Edit, Copy, Delete, Check Company Code OX02 CC10 'Company Code 10 #JNC' / JNC2 'JNC #2 Company Code' — both KR/KRW; charts of accounts COA1 / JNC respectively
Plant Enterprise Structure > Definition > Logistics - General > Define, copy, delete, check plant OX10 PT10 'Plant 10 #JNC' / JNC2 'JNC #2 Plant'
Storage location Enterprise Structure > Definition > Materials Management > Maintain storage location OX09 PT10: SL10/SL20/SL30 (+SL13/23/33) — split by ROH/HALB/FERT. JNC2: JNC1 (raw)/JNC2 (packaging)/JNC3 (semi-finished)/JNC4 (finished)
Purchasing org. Enterprise Structure > Definition > Materials Management > Maintain purchasing organization OX08 PO10 'Purcha. Org 10 #JNC' / JNC2 'JNC #2 Purch. Org.'
Sales org. Enterprise Structure > Definition > Sales and Distribution > Define, copy, delete, check sales organization OVX5 CY10 / JNC2 — both KRW
Distribution channel Enterprise Structure > Definition > Sales and Distribution > Define, copy, delete, check distribution channel OVXI DE·DL (for CY10) / JN (for JNC2)
Division Enterprise Structure > Definition > Logistics - General > Define, copy, delete, check division OVXB DN (for CY10) / JN (for JNC2)
Controlling area Enterprise Structure > Definition > Controlling > Maintain Controlling Area OX06 CA10 'Controlling Area 10 #JNC' / JNC2 — both KRW, fiscal year variant K4, chart of accounts matching the company code (COA1/JNC)
Operating concern Enterprise Structure > Definition > Controlling > Create operating concern KEA0 OC10 / JNC2 — costing-based CO-PA. Line item tables are generated separately as CE1OC10 / CE1JNC2

2. Enterprise Structure — Assignment

Item IMG path (SPRO) T-code Contents / values in this system
Plant → company code Enterprise Structure > Assignment > Logistics - General > Assign plant to company code OX18 PT10→CC10, JNC2→JNC2 (verified via valuation area table T001K)
Sales org. → company code Enterprise Structure > Assignment > Sales and Distribution > Assign sales organization to company code OVX3 CY10→CC10, JNC2→JNC2
Dist. channel → sales org. Enterprise Structure > Assignment > Sales and Distribution > Assign distribution channel to sales organization OVXK CY10: DE·DL / JNC2: JN
Sales area setup Enterprise Structure > Assignment > Sales and Distribution > Set up sales area OVXG CY10-DE-DN, CY10-DL-DN / JNC2-JN-JN
Purch. org. → company code Enterprise Structure > Assignment > Materials Management > Assign purchasing organization to company code OX01 PO10→CC10, JNC2→JNC2
Company code → controlling area Enterprise Structure > Assignment > Controlling > Assign company code to controlling area OX19 CC10→CA10, JNC2→JNC2 (TKA02) — our report ZCO0030 follows this assignment to find the CO-PA table dynamically
Controlling area → operating concern Enterprise Structure > Assignment > Controlling > Assign controlling area to operating concern KEKK CA10→OC10, JNC2→JNC2 (TKA01-ERKRS)

3. FI (Financial Accounting)

Item IMG path (SPRO) T-code Contents / values in this system
Chart of accounts Financial Accounting > General Ledger Accounting > Master Data > G/L Accounts > Preparations > Edit Chart of Accounts List / Assign Company Code to Chart of Accounts OB13 / OB62 COA1 (CC10) / JNC (JNC2). G/L accounts created with FS00 — mass creation via Excel upload with our ZFI0020
Financial statement version (FSV) Financial Accounting > General Ledger Accounting > Periodic Processing > Document > Define Financial Statement Versions OB58 FSV1 (chart of accounts COA1) — our ZFI0030 (P&L tree) / ZFI0031 (BS tree) read this hierarchy through the standard FMs. FSV9 also exists. The hierarchy is stored in the RFDT cluster, not readable by a direct SELECT on T011
Functional area Enterprise Structure > Definition > Financial Accounting > Define Functional Area FM_FUNCTION JNCM 'Manufacturing' / JNCS 'SG&A' (older FA10/FA20 also exist) — stored as RFAREA on documents; ZFI0030 splits the P&L into these two views
Currency decimals SAP NetWeaver > General Settings > Currencies > Set Decimal Places for Currencies OY04 KRW is a zero-decimal currency — showing amounts in ALV without a currency reference (cfieldname) makes them appear divided by 100

4. CO (Controlling)

Item IMG path (SPRO) T-code Contents / values in this system
Maintain controlling area Controlling > General Controlling > Organization > Maintain Controlling Area OKKP CA10/JNC2 — activate components (cost center accounting, order management, ...), currency KRW
Number ranges / versions Controlling > General Controlling > Organization > Maintain Number Ranges for Controlling Documents / Maintain Versions KANK / OKEQ CO document number ranges and plan/actual version (0) — basic per-controlling-area setup
Cost centers Controlling > Cost Center Accounting > Master Data > Cost Centers KS01 (OKEON) CA10: CC1010/CC7010/CC8010~8022/CC9010, JNC2: JNC21010/27010/28010/29010/29020 — senders/receivers of the allocation cycles
Activity types Controlling > Cost Center Accounting > Master Data > Activity Types KL01 CA10: AT8020/8030/8040, JNC2: AT8010/8020 — used for standard cost E items (activity cost) and as allocation bases
Cost elements (S/4HANA) merged with G/L accounts — cost element category set in FS00 FS00 Primary: category on P&L accounts. Secondary (5140 for allocations, 8020/8030 for activities, ...): G/L account type 'Secondary Costs'
Planner profile Controlling > Cost Center Accounting > Planning > Manual Planning > Define User-Defined Planner Profiles KP04 PP10 — layout for KP06 plan entry. Our ZCO0010 (KP06 plan upload) sets this profile automatically inside its BDC
Assessment cycle Controlling > Cost Center Accounting > Actual Postings > Period-End Closing > Assessment > Define Assessment KSU1 JNC2AA1010 (sender JNC28010 / cost element 5140 → receiver JNC29010, allocation base LSTAR AT8010) — definitions viewed with our ZCO0040
Distribution cycle Controlling > Cost Center Accounting > Actual Postings > Period-End Closing > Distribution > Define Distribution KSV1 JNC2AD1010 (sender JNC27010 / cost element 5140 → receiver JNC28010 portion 100), CA90EADIST, ... — detail view with our ZCO0041. Definitions stored in T811C/S/K/L/F

5. CO-PA (Profitability Analysis)

Item IMG path (SPRO) T-code Contents / values in this system
Maintain operating concern Controlling > Profitability Analysis > Structures > Define Operating Concern > Maintain Operating Concern KEA0 OC10 / JNC2 — costing-based. After defining characteristics and value fields, activation generates the CE1~CE4 tables
Characteristics / value fields Controlling > Profitability Analysis > Structures > Define Operating Concern > Maintain Characteristics / Value Fields KEA5 / KEA6 9 value fields: VV010 Sales, VV020 COGS (+VV021~024 detail), VV030/040/090 SG&A detail — OC10 and JNC2 have identical layouts (verified by comparing DD03L); our ZCO0030 displays them as-is
Value field mapping Controlling > Profitability Analysis > Flows of Actual Values > Transfer of Billing Documents > Assign Value Fields KE4I SD condition types → value fields (billing creates CE1 line items with record type 'F')
COGS revaluation Controlling > Profitability Analysis > Master Data > Valuation > Set Up Valuation Using Material Cost Estimate KE40 Costing key links the standard cost estimate — KE27 (periodic revaluation) splits COGS by cost component (VV021 Raw / VV022 Labor / VV023 Depreciation). Setup and execution documented separately

6. Product Cost Planning

Item IMG path (SPRO) T-code Contents / values in this system
Costing variant Controlling > Product Cost Controlling > Product Cost Planning > Material Cost Estimate with Quantity Structure > Define Costing Variants OKKN Standard cost estimates use costing type KALKA '01' — create with CK11N, mark/release with CK24 (KEKO-FREIG='X')
Cost component structure Controlling > Product Cost Controlling > Product Cost Planning > Basic Settings for Material Costing > Define Cost Component Structure OKTZ Splits cost into material / labor / depreciation etc. — linked to the KE27 revaluation value-field split (VV021~023)
Price control (Material master, Accounting view) price control S = standard / V = moving average MM02 Finished and semi-finished goods use S (standard price, refreshed by CK24 release); raw materials use V — our ZCO0020 values its subcontracting BOM explosion with these prices

7. MM / SD Settings

Item IMG path (SPRO) T-code Contents / values in this system
Valuation level Enterprise Structure > Definition > Logistics - General > Define valuation level OX14 Valuation area = plant (TCURM-BWKRS_CUS='1') — MBEW is keyed by material + plant (BWKEY)
Automatic account determination Materials Management > Valuation and Account Assignment > Account Determination > Account Determination Without Wizard > Configure Automatic Postings OBYC BSX (inventory) / GBB (offsetting) / WRX (GR/IR) / PRD (price difference) / FRL (subcontracting fee) etc. — traceable via BSEG-KTOSL (our ZFI0040 has an account-determination-key column). Subcontracting processing fees post to ACDOCA under FRL
Movement types Materials Management > Inventory Management and Physical Inventory > Movement Types > Copy, Change Movement Types OMJJ Standard movement types used: 101/102 (GR), 261/262 (issue to production), 541/543/544 (subcontracting components) — the basis of the E2E document flow
Sales document types Sales and Distribution > Sales > Sales Documents > Sales Document Header > Define Sales Document Types VOV8 CY10: ZOR1 (orders 2000000xxx range), JNC2: JN10 (orders 5000000000 range) — visible in our ZSD0010 (sales order list)

Values shown are from a personal sandbox used for end-to-end practice; object names (CC10, PT10, CA10, OC10, ...) are specific to that system.

Where these documents come from
Everything on this blog comes from one small dumpling factory built end-to-end in an S/4HANA sandbox — one plant, one product, one month, every document number real. The whole build is written up in two books.
· Free 16-page sample — the opening chapters, no email required
· How Sarah Joined a K-Dumpling Company and Became an SAP Genius — the business novel, 53 pages, $25
· The Dumpling Factory: Building a Complete SAP S/4HANA Company from Scratch — the build manual, 85 pages, $50

Comments

Post a Comment

Popular posts from this blog

Modern ABAP Syntax Notes — Patterns and Pitfalls from Real Development

ABAP syntax actually used while developing our custom Z reports, organized by topic. Examples come from working sources, together with the pitfalls we actually hit. Structure: syntax item → explanation → example code. Last updated: 2026-08-13 1. Data Declarations and Types ▷ Inline declarations DATA(...) / @DATA(...) — Declare and assign in one statement. SELECT result tables land directly in @DATA(lt_...) — the structure is derived from the SELECT list SELECT matnr, maktx FROM makt INTO TABLE @DATA(lt_makt) WHERE spras = @sy-langu. DATA(lv_qty) = ls_stpo-menge * iv_losgr / lv_bmeng. LOOP AT lt_mat INTO DATA(ls_mat). " loop variable inline too ENDLOOP. ▷ FIELD-SYMBOLS / ASSIGNING — Modify internal table rows in place without copying. ASSIGN COMPONENT lets you pick the column name at runtime (used for dynamic logic such as auto-hiding empty columns) LOOP AT gt_list ASSIGNING FIELD-SYMBOL(<ls_list>) WHERE typps = 'M'. <ls_list...
Read more

SAP S/4HANA Table Reference — Tables I Actually Query, by Topic

SAP tables I actually queried while building custom reports and running end-to-end tests on an S/4HANA sandbox, grouped by topic. Updated continuously as development goes on. Each table: Table / Description / Key fields / T-codes / Used in our custom reports. Last updated: 2026-08-13 1. CO — Allocation Cycles (Assessment / Distribution) Table Description Key fields T-codes Used in our reports T811C Allocation cycle header ※ Distribution = ALART 'V', assessment = ALART 'U'. Classic CO-OM uses TAB='CCSS' TAB / CYCLE / SDATE KSU3, KSV3 ZCO0040 (allocation cycle report), ZCO0041 (distribution cycle detail) T811S Cycle segments ※ SRULE (sender rule) / RRULE (receiver rule) / SPERCENT / RCDATA (variable portion type) / NEGTEST (negative tracing factors — stored value differs from the screen code) TAB / CYCLE / SDATE / SEQNR KSU3, KSV3 ZCO0040, ZCO0041 T811K Selection criteria per segment ※ SETKIND: 0=cycle, 1=sender control, 2=sender, 3=rece...
Read more

A 36% margin became 6% at month-end, and every posting was correct

On the day we shipped, the billing document said the margin was 36% . Three weeks later, after the close, the same sale carried a margin of 6% . Nobody made a mistake. No posting was reversed. Every document in between was correct. This is the part of SAP that spreadsheets never prepare you for, so it is worth walking through with real numbers. Everything below comes from a small dumpling factory I built from an empty S/4HANA client and drove through one complete business month. 1. The sale looked great A sales order for 20,000 KRW of dumplings, delivered and billed: Step Transaction Effect Sales order VA01 Revenue 20,000 · standard cost of goods 12,800 → expected margin 7,200 (36%) Goods issue VL01N → PGI Cost of goods sold hits the P&L for the first time — at standard Billing VF01 Revenue 20,000, receivable 22,000 (incl. tax) If you stop reading the system here — and a lot of people do, because t...
Read more