SAP S/4HANA Data Objects and Tables: A Deep-Dive by Business Process Stream

Understanding the structure of data in SAP S/4HANA is critical for enterprise data management, analytics, system integration, and transformation planning. SAP uses a layered metadata architecture: Data Elements (semantics), Tables (storage), and increasingly, CDS Views (virtualization). This document explores these objects in detail, organized by functional business process stream.

1. Plan-to-Produce (P2P – Manufacturing)

The Plan-to-Produce process covers the entire lifecycle of manufacturing: from planning and scheduling to actual production execution and confirmation.

Example 1: Bosch receives a customer order for brake pads. Based on MRP results, SAP creates a planned order in table MDKP, which is converted into a production order (AUFNR, stored in AFKO). This order is linked to a MATNR (Material Number, from MARA) and a WERKS_D (Plant, from T001W). The bill of materials (STLNR, header in STKO, items in STPO) and routing (PLNNR, operations in AFVC) define required materials and steps. During execution, component reservations (RESB) are issued, and confirmations against operations (AFVV) are posted by work center (ARBPL, master in CRHD).

Example 2: Siemens schedules preventive maintenance of turbine equipment through a production order with AUFNR. Components are staged using RESB, routed via work centers (ARBPL), and monitored via capacity loads (CRHD).

Example 3: A bicycle manufacturer creates a new BOM for a custom bike frame. The BOM is defined in STKO/STPO, routing is created in PLKO/PLPO, and a simulation run in MD02 generates planned orders in MDKP that are later converted to production orders in AFKO.

Example 4: Philips uses batch-specific manufacturing. Production order in AFKO is linked to batch master (CHVW), and goods receipt is posted to MSEG against the order with batch number captured.

Data Objects

• MATNR: Material Number
• WERKS_D: Plant
• AUFNR: Production Order Number
• ARBPL: Work Center
• VORNR: Operation Number
• GAMNG: Order Quantity
• MEINH: Unit of Measure
• STLNR: Bill of Materials Number
• PLNNR: Routing Group Number

Tables

• AFKO: Order Header Data
• AFVC: Operations
• AFVV: Operation Quantities and Times
• RESB: Component Allocations
• CRHD: Work Center Master
• STKO: BOM Header
• STPO: BOM Items
• MARC: Material Master (Plant-specific)
• MDKP: Planning Header
• CHVW: Batch Master Record
• PLKO/PLPO: Routing Header/Operations

CDS Views

• I_ProductionOrderItem: Tracks order status, material, plant, and actual vs. planned quantity.
• I_MaterialBOMComponent: Enables BOM analysis across levels, validity, and usage context.

2. Order-to-Cash (O2C)

Order-to-Cash is the customer fulfillment process from receiving a sales order to collecting payment.

Example 1: Grainger receives an online order from a customer. A sales order is created in VBAK (header) and VBAP (items) linked to KNA1 (Customer Master) and KNVV (Sales Area data). Delivery is initiated with LIKP/LIPS, and quantities are confirmed in VBEP. Invoice documents are posted in VBRK/VBRP, and accounting entries are updated in ACDOCA. Profitability segments and payment data are tracked using customer master and document flow (VBFA).

Example 2: DHL processes B2B logistics services and issues a billing document (VBRK/VBRP) linked to freight order in VTTK. The customer master in KNA1 is assigned payment terms and dunning procedures tracked via BSID/BSAD.

Example 3: An electronics company issues a credit memo using reference to a previously billed invoice (VBRK). The credit memo is linked in VBFA to the original invoice and reduces open AR balance in BSEG.

Example 4: A customer uses a scheduling agreement. Sales data is stored in VBAK/VBAP, deliveries are scheduled via VBEP, and goods issue posted through VLO1N, updating LIPS and ACDOCA.

Data Objects

• KUNNR: Customer Number
• VKORG: Sales Organization
• VTWEG: Distribution Channel
• SPART: Division
• VBTYP: Document Type
• AEDAT: Document Date
• NETWR: Net Order Value
• FAKSK: Billing Block
• POSNR: Sales Item Number
• VKBUR: Sales Office

Tables

• KNA1: Customer Master – General
• KNVV: Customer Master – Sales Area
• VBAK: Sales Order Header
• VBAP: Sales Order Items
• VBEP: Schedule Lines
• VBFA: Document Flow
• LIKP: Delivery Header
• LIPS: Delivery Items
• VBRK: Billing Header
• VBRP: Billing Items
• ACDOCA: Universal Journal
• BSID/BSAD: AR Open/Cleared Items

CDS Views

• I_SalesOrderItem: Includes status, pricing, delivery info, and credit check result.
• I_BillingDocumentItem: Tracks billing type, amount, payer, sales area, and financial accounting posting

3. Source-to-Pay (S2P)

Example 1: Unilever requires palm oil. A purchase requisition (EBAN) is created referencing material (MATNR) and vendor (LIFNR). The requisition converts into a purchase order in EKKO/EKPO, linked to vendor master data (LFA1/LFB1) and plant (WERKS_D). Goods receipt posts a material document (MKPF/MSEG), and PO history (EKBE) updates. The invoice is entered in RBKP/RSEG and cleared via BSIK/BSIS.

Example 2: A multinational automotive company manages consignment stock. Purchase orders are created for consignment materials in EKKO/EKPO, with special stock indicators. Goods receipts are posted to consignment stock, reflected in tables like MSEG with special stock indicators. Invoice verification ensures payment only for consumed materials, tracked in RBKP/RSEG.

Example 3: A retailer conducts a supplier evaluation process. Vendor master data in LFA1 and purchasing info records (EINA/EINE) are analyzed. Purchase order history (EKBE) tracks vendor delivery performance and invoice accuracy, supporting procurement decisions.

Data Objects

• LIFNR: Vendor Number
• EKORG: Purchasing Organization
• MATNR: Material Number
• WERKS_D: Plant
• BSART: Purchasing Document Type
• LGORT: Storage Location
• NETPR: Net Price

Tables

• LFA1: Vendor Master – General
• LFB1: Vendor Master – Company Code
• EKKO: Purchase Order Header
• EKPO: Purchase Order Item
• EBAN: Purchase Requisition
• EKBE: PO History
• MKPF/MSEG: Material Document Header/Items
• RBKP/RSEG: Invoice Document Header/Items

CDS Views

• I_PurchaseOrderItem
• I_SupplierInvoiceItem

4. Recruit-to-Retire (R2R – HR/Organizational Management)

Example 1: Accenture hires a new consultant. Personnel number (PERNR) is assigned in PA0000 (actions) and organizational assignment (PA0001) links the employee to position (PLANS) and organizational unit (ORGEH). Time worked is captured in CATSDB, feeding cost center (KOSTL) allocations.

Example 2: A pharmaceutical company manages employee benefits changes via personnel infotype updates in PA0002 (personal data) and payroll results integration with SuccessFactors. Organizational relationships in HRP1000/HRP1001 reflect changes in department hierarchies.

Example 3: A global bank performs headcount and turnover analytics. Employee data from PA0001/PA0002 is combined with organizational master data (HRP1000) and time sheet data (CATSDB) in CDS views for workforce planning dashboards.

Data Objects

• PERNR_D: Personnel Number
• PLANS: Position
• STELL: Job
• ORGEH: Organizational Unit
• GESCH: Gender
• GBDAT: Date of Birth

Tables

• PA0000: Actions
• PA0001: Org Assignment
• PA0002: Personal Information
• HRP1000: Organizational Objects
• HRP1001: OM Relationships
• CATSDB: Time Sheet Data

CDS Views

• Custom HR analytics views built on employee master data and organizational structures, often consumed in SAP Analytics Cloud.

5. Record-to-Report (R2R – Finance and Controlling)

Example 1: Nestlé posts a vendor invoice using transaction FB60. Document header and line items are saved in BKPF and BSEG, impacting GL accounts (HKONT), company codes (BUKRS), cost centers (KOSTL), and profit centers (PRCTR). These are reflected in the Universal Journal (ACDOCA). Month-end depreciation runs post in ANEP and ACDOCA.

Example 2: A telecom company performs cost allocations at month-end. Original postings in ACDOCA are distributed to other cost centers using COSP/COEP. These allocations flow into profitability analysis modules and reporting.

Example 3: A manufacturing firm performs financial close activities. Journal entries for accruals, asset postings, and currency revaluations are stored in BKPF/BSEG and consolidated in ACDOCA. Reporting via CDS views enables real-time finance insights.

Data Objects

• BUKRS: Company Code
• HKONT: G/L Account
• BUDAT: Posting Date
• WRBTR: Amount in Document Currency
• BELNR: Document Number
• BLART: Document Type
• KOSTL: Cost Center
• PRCTR: Profit Center

Tables

• BKPF: Accounting Document Header
• BSEG: Accounting Document Line
• ACDOCA: Universal Journal
• COSP/COEP: CO Totals and Line Items
• ANEP: Asset Line Items (Depreciation)
• SKA1/SKB1: G/L Master Data

CDS Views

• I_JournalEntryItem
• I_GLAccountLineItemCube