SAP S/4HANA T-Code Reference — Ordered by End-to-End Process Flow

T-codes I actually used while running an end-to-end test cycle on an S/4HANA sandbox (master data → standard costing → purchasing/subcontracting → production → sales → month-end closing), organized in process order. I keep adding to this document as testing continues.

Each table: T-code / Description / Related tables / How it is used in our E2E tests and custom developments. Last updated: 2026-08-13

1. Master Data Preparation

T-code Description Related tables In our E2E / developments
FS00 G/L account master (centrally maintained) SKA1, SKB1, SKAT Mass creation of test accounts — ZFI0020 (G/L account mass creation via Excel upload BDC); inquiry via ZFI0010 (G/L account list)
BP Business Partner (unified customer/vendor)
※ Customer/vendor company-code assignment links to KNB1/LFB1 through the CVI link tables		 BUT000, KNB1, LFB1 Prepare customer and vendor masters — list report ZBP0010 (BP list)
MM01 / MM02 / MM03 Material master create/change/display MARA, MARC, MBEW, MAKT Prepare materials from raw materials to finished goods — ZMM0010 (material list with info record/BOM/routing/production version status lights)
CS01~03 / CA01~03 / C223 BOM / routing / production version maintenance MAST·STKO·STPO / MAPL / MKAL Prepare production master data — drill-down from ZMM0010 status lights; BOM explosion for subcontracted materials in ZCO0020 (standard cost vs actual)
KS01~03 / KA01~03 / KL01~03 Cost center / cost element / activity type masters CSKS·CSKT / CSKB / CSLA·CSLT Prepare CO master data (cost centers JNC27010/8010/9010, activity types AT8010/8020, ...) — names looked up in ZCO0041 (distribution cycle detail)
GS01~03 / KSH1~3 / KAH1~3 Sets / cost center groups / cost element groups SETHEADER(T), SETLEAF Define sender/receiver groups for allocation cycles — expanded via G_SET_GET_ALL_VALUES in ZCO0041

2. Planning / Standard Costing

T-code Description Related tables In our E2E / developments
KP06 Cost center primary cost element planning
※ Planner profile (PP10) must be set first		 COSP family Enter plan amounts — ZCO0010 (KP06 plan upload) posts an Excel upload via BDC
KP26 Activity type planning (quantity / rate) COST family Prepare activity rates — the basis of the E items (activity cost) in the standard cost estimate
CK11N / CK13N Create / display standard cost estimate
※ Standard cost estimates use KALKA='01'		 KEKO, CKIS Calculate standard cost for products and semi-finished goods — ZCO0020 (standard cost vs actual) unfolds the itemization and compares it with actuals
CK24 Mark / release standard cost estimate KEKO(FREIG), MBEW Only released estimates become the standard price — ZCO0020 reads only FREIG='X' (released) estimates

3. Purchasing / Subcontracting

T-code Description Related tables In our E2E / developments
ME51N / ME53N Create / display purchase requisition EBAN, EBKN PR→PO conversion flow — list and conversion status in ZMM0050 (purchase requisition list)
ME21N / ME23N Create / display purchase order
※ Subcontracting POs have no production order; GR, component consumption, and processing fees all post against the PO (EBELN)		 EKKO, EKPO Raw material purchases and subcontracting POs — list and status in ZMM0030 (purchase order list)
ME1M Purchasing info record list EINA, EINE Check prices such as the subcontracting purchase price — drill-down from ZMM0010 status lights
MIGO Goods movements (GR/GI by movement type)
※ MB03 is deprecated in S/4HANA (SAP Note 2210569)		 MKPF, MSEG Purchase GR (101), subcontracting component issue (541/543), ... — document list in ZMM0040 (material document list), display via MIGO_DIALOG
MIRO Invoice verification
※ EKPO-EREKZ (final invoice flag) must NOT be used to judge whether an invoice was received		 RBKP, EKBE Process purchase/subcontracting invoices — ZMM0030 derives invoice status from the existence of EKBE VGABE='2' lines
MB52 / MMBE Warehouse stock list / stock overview MARD Verify stock during testing, check negative stock — ZMM0060 (negative stock list)

4. Production

T-code Description Related tables In our E2E / developments
CO01 / CO02 / CO03 Production order create/change/display AUFK, AFKO Produce semi-finished and finished goods — list in ZPP0010 (production order list); ZCO0020 aggregates actuals by order
MIGO (261/101) Component issue to production order (261) / goods receipt from production (101)
※ When reading with FOR ALL ENTRIES, include the document key in the SELECT list (implicit duplicate removal trap)		 MSEG The source of actuals in ZCO0020 — consumption (261/262/543/544 offset), receipts (101/102 offset)
COOIS Production order information system (list) AUFK, AFKO The model for ZPP0010 (production order list)

5. Sales

T-code Description Related tables In our E2E / developments
VA01 / VA03 Create / display sales order
※ S/4HANA removed the status tables (VBUK/VBUP) — status fields are merged into VBAK/VBAP		 VBAK, VBAP Start of the sales process — list with delivery/billing status in ZSD0010 (sales order list)
VL01N / VL02N Create delivery / post goods issue (PGI) LIKP, LIPS COGS posts at goods issue — tracked via delivery status (LFSTA) in ZSD0010
VF01 / VF03 Create / display billing document VBRK, VBRP Billing creates CO-PA line items — double-click in ZCO0030 (CO-PA line items) jumps to VF03

6. Month-End Closing / CO Actuals

T-code Description Related tables In our E2E / developments
KSV5 / KSU5 Execute actual distribution / assessment cycles
※ Distribution (V) keeps the original cost elements; assessment (U) moves under secondary cost elements		 T811* + ACDOCA Move costs between cost centers — definitions viewed with ZCO0040 (allocation cycle report) / ZCO0041 (distribution cycle detail, incl. execution-history filter)
KSV1~3 / KSU1~3 Define distribution / assessment cycles (create/change/display) T811C/S/K/L/F ZCO0040 (segment summary) / ZCO0041 (group-expanded detail) — double-click jumps to KSV3/KSU3
KE24 CO-PA actual line item display
※ Without a PALEDGER='01' filter every line shows up twice		 CE1xxxx Verify billing actuals — the model for ZCO0030 (CO-PA line items)
KE27 CO-PA periodic COGS revaluation CE1xxxx Revalue COGS with the standard cost component split — setup and execution documented separately
F.01 Financial statements (FSV-based, RFBILA00) FSV(RFDT), ACDOCA Check closing results — ZFI0030 (P&L tree) / ZFI0031 (BS tree)
FBL3N / FB03 G/L line items / display accounting document BSIS_VIEW, BKPF, BSEG Document-level verification (tracing account determination keys KTOSL, ...) — ZFI0040 (G/L line item report)

7. Verification / Development Tools

T-code Description Related tables In our E2E / developments
SE16N Table data browser - General verification of stored data at every E2E step
SE38 / SE93 / SE11 / SE51 ABAP editor / T-code registration / DDIC / Screen Painter TRDIR, TSTC, DD02L, D020S Develop and register Z reports (T-codes and screens can also be created via abapGit)
SE09 Transport Organizer E070, E071 Release deployment transports (unlock objects before an abapGit pull)
SHDB BDC recording - Analyze screen sequences — this is how the BP entry point (SAPLBUS_LOCATOR) used by ZBP0010 was found
SM30 / SMW0 Table maintenance / web repository (MIME) TVDIR / WWWDATA Registry maintenance (ZJNC0050V) and the launchpad logo (ZJNC_LOGO)

All Z reports mentioned above are custom developments built on the same sandbox; each will get its own post.

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