SAP S/4HANA End-to-End Lab

How to check in SM37 whether a monthly batch job finished correctly: the selection screen, the numbers and buttons on the job overview, how to read the job log, how a periodic job creates its next run, background-only variants that do not appear on the selection screen, and DB02 SQL for checking. Note: screens, menus and settings can differ by SAP release and system configuration. Screen labels are given with their English GUI names. SQL results are from a demo system. 1. SM37 selection screen (Simple Job Selection) Field Example Meaning Job name part of the name + * * means "any characters". If you know only part of the name, put * before and after it User name * The default is your own user ID. Jobs created by other users appear only after you change it to * Job status all except Sched. Released (waiting), Ready, Active (running), Finished (completed), Canceled (stopped with an error) Job start condition today to t...

When a CO-PA drilldown report (KE30) suddenly shows different numbers, the first question is whether someone changed the report definition (KE32) or the form (KE35). This post shows two ways to find the creator and the last person who changed each object: from the GUI, and by reading the tables TKEB1 and TKES1 directly. Note: screens, menus and settings can differ by SAP release and system configuration. 1. Report and form A drilldown report is made of two objects. The columns (period, actual/cumulative and so on) and the rows (P&L lines) are defined in the form . The report takes a form and adds characteristics, variables and output options. Item Detail Report KE31 create / KE32 change / KE33 display. Table TKEB1 Form KE34 create / KE35 change / KE36 display. Table TKES1 When values changed Column definitions (period variables, plan/actual flag, value-field formulas) live in the form, so check the form first One form, many reports ...

Who created the CO-PA value fields (VV010, VV020, ...) and when. HANA SQL for DB02 → Diagnostics → SQL Editor. Verified on an S/4HANA sandbox (client 100, operating concerns OC10 and JNC2) on 2026-08-27. 0. Before you start — find the table that stores the value fields (CE1xxxx) Case Company code → controlling area → operating concern (TKA02 / TKA01) What it does Value fields (VVxxx) are created as columns of the operating concern line item table CE1<ERKRS>. Starting from the company code, TKA02 gives the controlling area (KOKRS) and TKA01 gives the operating concern (ERKRS), which names the table. Watch out On this system: CC10 → CA10 → OC10 (CE1OC10) and JNC2 → JNC2 → JNC2 (CE1JNC2). Each company code ends up in a different table. Result 2 rows (CC10 → OC10, JNC2 → JNC2) SELECT k.BUKRS, k.KOKRS, a.ERKRS FROM TKA02 k INNER JOIN TKA01 a ON a.MANDT = k.MANDT AND a.KOKRS = k.KOKRS WHERE k.MANDT = '100' AND k.BUKRS IN ('CC10', 'JNC2') ...

Give it a controlling area (KOKRS) and it returns every cost center underneath with all CSKS columns, plus the names from CSKT. Plain HANA SQL for DB02/ST04 → Diagnostics → SQL Editor; an S/4HANA version and an ECC version are both included. Verified on an S/4HANA sandbox: controlling area JNC2 (JNC #2 Controlling Area), client 100. Written 2026-08-31. 1. Result — 5 cost centers in JNC2 Case Cost centers under controlling area JNC2 (output of the query in section 6) What it does The five cost centers of JNC2 with the CSKT name, category, functional area and standard hierarchy node. The full query returns all 84 CSKS columns; the grid below shows the columns that carry the meaning. Result 5 rows Result — 5 rows (KOKRS = JNC2) KOSTL | KTEXT (CSKT) | KOSAR | FUNC_AREA | KHINR (std hierarchy node) ---------+------------------------+-------+----------------------+--------------------------- JNC21010 | SG&A | 2 | JNCS (SG&A) ...