Knowledge Base / ERP

SAP S/4HANA

Vendor: SAP · Enterprise

Accounts Payable (AP)

Vendor invoices, payments, settlements

Activities

• Create Purchase Requisition - Purchase requisition is raised via Purchase Requisition Entry (PRE) for goods or services. Requisition enters the approval workflow. Timestamp from REQUISITION.CREATE_DTTM.
• Approve Purchase Requisition - Purchase requisition passes multi-level approval via DAG-based approval workflow. Approval level advances until all required stages are complete. Timestamp from REQUISITION.APPROVED_DTTM.
• Reject Purchase Requisition - Purchase requisition is rejected by an approver with a reason code. Requisition must be amended and resubmitted for approval. Timestamp from requisition rejection event.
• Convert Requisition to Purchase Order - Approved purchase requisition is converted into a purchase order. PO reference is assigned and linked back to the requisition. Timestamp from PURCH_ORDER.CREATE_DTTM.
• Create Purchase Order - Purchase order is created via Purchase Order Entry (POE) or SSC PurchaseOrder. Header and line items are entered with supplier, quantities, and prices. Timestamp from PURCH_ORDER.CREATE_DTTM.
• Approve Purchase Order - Purchase order passes multi-level approval controlled by PBS and PTS settings. Operators in Data Access Groups (DAG) approve based on value limits and codes. Timestamp from PURCH_ORDER.APPROVED_DTTM.
• Reject Purchase Order - Purchase order is rejected by an approver with a reason code. PO must be amended and re-submitted for approval. Timestamp from PO rejection event.
• Unapprove Purchase Order - Purchase order approval is reversed with a reason code. The Reapprove if Path Change setting may trigger automatic unapproval. Approval workflow must restart. Timestamp from unapproval event.
• Receive Goods (GRN) - Goods receipt note is recorded against purchase order lines in Order Fulfilment. Quantities received are matched against ordered quantities. Used in 3-way matching (PO-GRN-Invoice). Timestamp from PURCH_RECEIPT.CREATE_DTTM.
• Enter Purchase Invoice (OF) - Purchase invoice is entered via Purchase Invoice Entry (PIE) in Order Fulfilment. Can be generated from PO matching via Generate/Match form. Posts journal to unified ledger via Ledger Interface. Timestamp from PURCH_INVOICE.CREATE_DTTM.
• Approve Purchase Invoice (OF) - Purchase invoice passes multi-level approval in Order Fulfilment. Line-level or header-level approval depending on Purchase Type configuration. Timestamp from PURCH_INVOICE.APPROVED_DTTM.
• Reject Purchase Invoice (OF) - Purchase invoice is rejected by an approver with a reason code. Invoice must be corrected and re-submitted for approval.
• Create Invoice Batch - Invoice batch is created in AP for grouping invoices (AP25). Timestamp from APBATCH.APB-BATCH-DATE.
• Receive Invoice - Purchase invoice received and recorded in the system. In Infor LN: tfacp1500m000 session, status set to Draft.
• Enter Creditor Invoice (Ledger) - Creditor/purchase invoice is entered directly via Ledger Entry (LEN) in SunSystems Financials against a creditor account. Journal type controls validation. Allocation marker is set to blank (unallocated). Timestamp from JNLT.ORIGINATED_DATE or LDG_DETAIL.CREATE_DTTM.
• Import Creditor Invoice (LIM) - Creditor invoice journal is imported via Ledger Import (LIM) from external system or integration. Transactions load to PSTG_WRK_TBL for validation before posting. Timestamp from PSTG_HDR.POSTING_DTTM.
• Express Invoice Entry - Invoice is entered via express entry (APEXPINV) for quick PO matching. IEX-CREATE-DATE timestamp.
• Post Creditor Invoice to Ledger - Creditor invoice journal is posted to the unified ledger. Transaction moves from PSTG_WRK_TBL to LDG_DETAIL. Journal number and voucher number assigned. Timestamp from JNLT.POSTED_DATE or PSTG_HDR.POSTING_DTTM.
• Authorize Journal - Journal entry requires authorization before posting (when Authorization Required is set in Ledger Setup). Approver reviews and authorizes via Authorization Set. Timestamp from authorization event.
• Hold Journal - Journal entry is written to the Hold File (HELD_JRNL) instead of being posted. Held transactions are excluded from standard reports. Must be released before posting. Timestamp from held journal creation.
• Release Held Journal - Previously held journal is released from the Hold File, making it available for posting to the ledger. Timestamp from release event.
• Vendor Creates Invoice - Vendor submits an invoice to initiate payment processing. Timestamp from BKPF.BLDAT (document date). Source: BKPF JOIN BSEG WHERE KOART='K' AND BLART IN ('KR','KG','KA').
• Register Invoice - Purchase invoice is officially registered in the AP system with a document number. In Infor LN: tfacp2600m000 session, status becomes Registered.
• Assign Voucher Number - Voucher number is assigned to registered invoice (automatic or manual per APCOMPANY settings).
• Assign Authority Code - Authority code is assigned to invoice for approval routing (AP20.1). Required before release when INV-APPROVAL is Y.
• Generate Self-Billed Invoice - System auto-generates a purchase invoice based on receipt data (self-billing). No supplier invoice needed.
• Release Invoice Batch - Invoice batch is released for processing, making invoices eligible for payment scheduling.
• Enter in SAP - Invoice is entered/posted in the SAP system. Timestamp from BKPF.CPUDT+CPUTM (entry date/time). Resource from BKPF.USNAM, user type from USR02.USTYP. Source: BKPF JOIN BSEG LEFT JOIN USR02.
• Match Creditor Transactions (TRM) - Transaction Matching (TRM) automatically matches creditor invoice and payment transactions. Sets allocation markers to Allocated or Paid. Settlement discounts are applied per matching rules. Timestamp from LDG_DETAIL.MODIFY_DTTM.
• Allocate Creditor Transactions (ACA) - Account Allocations (ACA) manually matches creditor transactions (invoices to payments, credit notes to invoices). Updates allocation markers. Can amend transaction details during allocation. Timestamp from LDG_DETAIL.MODIFY_DTTM.
• Create Distribution Lines - GL distribution lines are created for the invoice (APDISTRIB records). Assigns accounting to expense items.
• Update Allocation Marker - Allocation marker on a creditor transaction is manually updated. Markers: blank (unallocated), Force, Withhold, 0-9 (user-defined), Allocated, Paid, Correction. Timestamp from LDG_DETAIL.MODIFY_DTTM.
• Apply Settlement Discount - Settlement discount is applied during transaction matching for creditor account. Discount amount is calculated from payment terms and posted to discount account. Timestamp from discount journal posting.
• Post Distribution to GL - Invoice distributions are posted to the General Ledger. APDISTRIB.APD-REC-STATUS is updated.
• Match Invoice to PO - Purchase invoice is matched against purchase order lines. Verifies quantities and prices match the original order.
• Match Invoice to Receipt - Purchase invoice is matched against warehouse receipt/packing slip lines. Verifies goods were actually received.
• Unmatch Invoice - Previously matched invoice is unmatched, reverting status to Registered with Matching Errors.
• Change Payment Method - Payment method on the invoice line item is modified. Tracked via CDHDR/CDPOS where OBJECTCLAS='BELEG', TABNAME='BSEG', FNAME='ZLSCH'. Timestamp from CDHDR.UDATE+UTIME. Resource from CDHDR.USERNAME.
• Approve Price Difference - Price difference between invoice and purchase order is approved or rejected. Triggers additional cost posting if approved.
• Approve Invoice - Purchase invoice is approved after matching. Status changes from Matched to Approved. All matching errors resolved.
• Change Payment Term - Payment terms on the invoice are updated. Tracked via CDHDR/CDPOS where FNAME='ZTERM'. Timestamp from CDHDR.UDATE+UTIME.
• Unapprove Invoice - Previously approved invoice is unapproved, reverting status from Approved back to Matched or Registered.
• Cancel Invoice - Distributed invoice is cancelled. APINVOICE.API-CANCEL-SEQ is assigned (first=9999).
• Authorize Payment - Invoice is authorized for payment by an authorized approver. Required when payment authorization is active.
• Create Credit Note - A credit note is created against an existing purchase invoice, reducing the amount owed.
• Change Baseline Date - Baseline date for payment due date calculation is changed. Tracked via CDHDR/CDPOS where FNAME='ZFBDT'. Timestamp from CDHDR.UDATE+UTIME.
• Change Payment Days 1 - Cash discount days 1 on the invoice is changed. Tracked via CDHDR/CDPOS where FNAME='ZBD1T'. Timestamp from CDHDR.UDATE+UTIME. Found in Kaustav extraction only.
• Set Payment Block - A payment block is applied to hold the invoice from payment. Tracked via CDHDR/CDPOS where FNAME='ZLSPR' AND VALUE_OLD IS NULL AND VALUE_NEW IS NOT NULL. Timestamp from CDHDR.UDATE+UTIME.
• Set Hold Reason - A hold reason (blocking code) is assigned to the invoice, preventing it from being paid or processed further.
• Remove Hold Reason - Hold reason is removed from the invoice, allowing it to proceed through payment processing.
• Set Withhold Marker - Withhold allocation marker is set on a creditor transaction to prevent it from being selected by Payment Run. Used to hold disputed invoices. Timestamp from LDG_DETAIL.MODIFY_DTTM.
• Remove Withhold Marker - Withhold allocation marker is removed from a creditor transaction, making it eligible for Payment Run selection. Timestamp from LDG_DETAIL.MODIFY_DTTM.
• Calculate Withholding Tax (WHT) - Withholding tax is calculated on creditor invoice or payment. Journal source WHTAX. Notional tax posted at invoice point, actual tax at payment point (configurable). Cumulative or per-transaction calculation. Timestamp from WHT journal posting.
• Post Withholding Tax (PWT) - Post Withheld Taxes (PWT) function posts accumulated withholding tax to the actual tax liability account. Transfers from notional to actual tax account. Timestamp from PWT execution.
• Void Withholding Tax - Withholding tax transaction is voided. If calculation type is cumulative, cumulative amount and tax are reduced accordingly. Timestamp from void event.
• Revalue Creditor Balances - Ledger Revaluation (LER) revalues open creditor balances for foreign currency fluctuations. Generates unrealized exchange gain/loss postings. Uses Ledger Revaluation Profile settings. Timestamp from revaluation run.
• Reverse Journal (AP) - AP journal is reversed via Journal Reversal and Copy (JRC). Creates a new reversing journal with opposite debit/credit entries. Used for corrections and period-end adjustments. Timestamp from reversal posting.
• Remove Payment Block - Payment block is removed to allow invoice payment processing. Tracked via CDHDR/CDPOS where FNAME='ZLSPR' AND VALUE_OLD IS NOT NULL AND VALUE_NEW IS NULL. Timestamp from CDHDR.UDATE+UTIME.
• Create Payment Profile - Payment profile (PYP) is created defining selection criteria for Payment Run. Specifies account ranges, currency thresholds, payment method, bank account, and document format. Timestamp from profile creation.
• Run Cash Requirements - AP150 - Cash Requirements is run to schedule invoices for payment based on due dates and selection criteria.
• Execute Payment Run (PYR) - Payment Run (PYR) is executed to settle outstanding creditor transactions. Selects transactions matching payment profile criteria, generates payment journals to the unified ledger, and produces payment data. Timestamp from PYMT_RUN.CREATE_DTTM.
• Select Invoice for Payment - Invoice is selected into a payment batch during the payment run. In Infor LN: tfcmg1220m000 session creates pro-forma payment batch.
• Print Payment Forms - AP155 - Payment forms (checks) are printed for scheduled invoices.
• Produce Payment Documents (PYD) - Payment Documents (PYD) produces cheques, bank transfer files, or remittance advice. Appears automatically after Payment Run or runs independently. Supports draft (watermark) and final printing. Timestamp from PYMT_DOC.CREATE_DTTM.
• Generate Bank Transfer File - Electronic bank transfer file (BACS/EFT) is generated for transmission to the bank. Created when Payment Method is Bank. File format determined by Document Format Code in Payment Profile. Timestamp from file generation.
• Create Payment Tape - AP160 - Electronic payment tape/file is created for bank transmission.
• Create Electronic Payment File - AP161 - Electronic payment file (EFT/ACH) is created for bank transmission.
• Assign Bank to Payment - Bank relation is assigned to the payment batch for processing. Can be automatic or manual.
• Process Payment - Payment is executed and financial transactions posted. Payment batch is finalized and bank file generated.
• Close Payment Cycle - AP170 - Payment cycle is closed, finalizing all payments and updating balances.
• Clear Invoice - Invoice is cleared through payment or other settlement. Timestamp from BKPF_CLEAR.CPUDT+CPUTM if clearing date matches BSEG.AUGDT, otherwise BSEG.AUGDT + 23:59:59. Excludes reversals (BKPF.XREVERSAL NOT IN ('1','2')). Resource from clearing document BKPF.USNAM.
• Void Payment - Payment is voided after processing. APPAYMENT.APP-VOID-SEQ and APP-VOID-DATE are populated.
• Create Bill of Exchange - Bill of exchange (draft) is created for vendor payment. APDRAFTS record is created with status 0 (Unreleased).
• Release Bill of Exchange - Bill of exchange is released for vendor acceptance. APDRAFTS status changes to 1 (Released).
• Accept Bill of Exchange - Bill of exchange is accepted by vendor. APDRAFTS status changes to 2 (Accepted).
• Cash Bill of Exchange - Bill of exchange is cashed by bank. APDRAFTS status changes to 3 (Cashed).
• Dishonor Bill of Exchange - Bill of exchange is dishonored by bank. APDRAFTS status changes to 4 (Dishonored).
• Reconcile Payment - Payment is reconciled against bank statement. APPAYMENT.APP-RECON-STMT-NBR is populated.
• Run Accrual Reconciliation - AP260 - Invoice accrual reconciliation is run for the company. APRECON record created.
• Run Ledger Cleardown (AP) - Ledger Cleardown (LCL) removes fully allocated/paid creditor transactions from the live ledger and summarizes balances. Transactions must be fully matched before cleardown. Archive transactions stored in SALFLDG tables. Timestamp from cleardown execution.
• Reconcile Creditor Account - Creditor account is reconciled by reviewing open items, matching transactions, and resolving discrepancies. Uses Account Inquiry and Financial Analysis reports. Timestamp from reconciliation completion.
• Generate Creditor Aging Report - Financial Analysis report is generated for creditor/payables aging. Shows open items by aging bucket. Uses FIN_ANL_RPT interface table. Timestamp from report generation.
• Cash Discount Due Date passed - Cash discount period has expired without payment. Calculated: BSEG.ZFBDT + BSEG.ZBD1T days. Only when ZBD1P > 0 (discount percentage exists). System event - no user resource.
• Due Date passed - Invoice net due date has passed without payment. Calculated: BSEG.ZFBDT + MAX(ZBD3T, ZBD2T, ZBD1T) days. Falls back to ZFBDT if all terms are zero. System event - no user resource.
• Change Item Text - Line item text (SGTXT) on the invoice is modified. Tracked via CDHDR/CDPOS where FNAME='SGTXT'. Timestamp from CDHDR.UDATE+UTIME.
• Change Dunning Block - Dunning block indicator on the invoice is changed. Tracked via CDHDR/CDPOS where FNAME='MANSP'. Timestamp from CDHDR.UDATE+UTIME.

Case attributes

• Company Code (Text) - Company or entity code
• Cost Center (Text) - Cost center responsible
• Document Type (Text) - Type of financial document
• GL Account (Text) - General ledger account
• Status (Text) - Current status
• Amount (Currency) - Monetary value
• Currency (Text) - Transaction currency
• Created By (Text) - User who created the record
• Document Number (Text) - Unique identifier for the document
• Vendor/Customer (Text) - Business partner ID
• Document Date (Date) - Date of the document
• Due Date (Date) - Payment or completion due date

Data tables

• ACDOCA - Universal Journal Entry
• BKPF - Accounting Document Header
• BSEG - Accounting Document Line Item
• BSIK - Vendor Open Items
• LFA1 - Vendor Master - General Data
• LFB1 - Vendor Master - Company Code Data
• RBKP - Invoice Document Header
• RSEG - Invoice Document Item
• BSAK - Vendor Cleared Items
• CDHDR
• CDPOS
• LFM1 - Vendor Master - Purchasing Organization
• REGUH - Settlement Data from Payment Program
• REGUP - Payment Advice Items
• SWWWIHEAD - Workflow Work Item Header
• T001
• USR02
• T003 - Document Types
• T003T - Document Type Texts
• T005 - Countries
• T008 - Blocking Reasons for Automatic Payment
• T008T - Payment Block Texts
• T040 - Dunning Keys
• T040T - Dunning Block Texts
• T042Z - Payment Methods for Automatic Payment
• T042ZT - Payment Method Texts
• T052 - Payment Terms Configuration
• T052U - Payment Terms Text
• TBSLT - Posting Key Texts
• TCURF - Conversion Factors
• TCURR - Exchange Rates
• TCURX - Currency Decimals
• TSTCT - Transaction Code Texts
• TTYP - Reference Transaction Types

Accounts Receivable (AR)

Customer invoices, receipts, collections

Activities

• Execute Transaction - Main transaction processing
• Post to System - Record posted to system
• Complete Review - Final review performed
• Close Process - Process marked complete
• Create Sales Order - Sales order is created in Order Fulfilment module for a customer
• Acknowledge Sales Order Line - Sales order line is acknowledged/confirmed
• Create Customer - New customer record is created in ARCUSTOMER via AR10
• Hold Sales Order Line - Sales order line is placed on hold preventing further processing
• Release Sales Order Line - Held sales order line is released for processing
• Change Customer - Customer master data is modified (tracked in ARAUDIT)
• Change Debtor Account Status - Debtor account status is changed (active, suspended, deleted)
• Update Debtor Payment Terms - Payment terms are updated on a debtor account
• Inactivate Customer - Customer status is set to Inactive in ARCUSTOMER
• Place Customer Hold - Hold code is applied to customer preventing new orders
• Remove Customer Hold - Hold code is removed from customer allowing orders
• Update Debtor Credit Limit - Credit limit is updated on a debtor account
• Review Customer Credit - Credit analyst reviews customer credit limit and status
• Generate Invoice from Sales Order - Sales invoice is automatically generated from a sales order via Order Fulfilment
• Enter Invoice Batch - Invoice batch is entered via AR43 Transaction Entry
• Release Invoice Batch - Invoice batch is released from temporary to open items
• Create Invoice - Customer invoice is created in the system
• Post Sales Invoice Journal - Sales invoice journal is posted to the unified ledger via Ledger Entry (LEN) or Ledger Import (LIM)
• Interface Transaction from Billing - Transaction is interfaced from Billing via AR560
• Import Journal via SSC - Journal is imported through SunSystems Connect (SSC) API from an external system
• Compose Invoice - Sales invoice is composed from billable lines in the Invoicing module (cisli)
• Post Provisional Journal - Journal is posted as provisional (pending review before becoming permanent)
• Cancel Invoice - Invoice is cancelled creating a reversing credit memo
• Release Provisional Journal - Provisional journal is confirmed and posted as a permanent ledger entry
• Hold Journal - Journal is placed on hold for review before posting
• Print Invoice - Sales invoice is printed and sent to the customer
• Release Held Journal - Held journal is released and posted to the ledger
• Post Invoice to AR - Invoice is posted from Invoicing to AR, creating open entry in tfacr200
• Post Order Fulfilment Journal - Order Fulfilment ledger posting creates a journal in Financials with analysis mapping
• Generate Monthly Billing Invoice - Consolidated monthly billing invoice is generated for customer
• Print Monthly Billing Invoice - Monthly billing invoice document is printed
• Enter in SAP - Invoice is posted/entered into SAP
• Clear Invoice - Invoice is cleared through payment or settlement
• Clear Credit Memo - Credit memo is cleared against open items
• Invoice Cleared - Invoice clearing is confirmed and complete
• Payment received from customer - Customer payment is received and recorded
• Create Cash Batch - Cash batch header is defined via AR20
• Enter Cash Payment - Cash payment is entered via AR30.1 Entry and Application
• Interface Lockbox Payment - Lockbox payment is interfaced via AR570 from bank BAI file
• Interface Non-Lockbox Payment - Non-lockbox payment is interfaced via AR575/AR580
• Process Receipt Transaction - Customer receipt is processed via bank transaction in Cash Management (tfcmg)
• Enter Prepayment - Prepayment is recorded before invoice exists
• Create Anticipated Receipt - Anticipated receipt is created before actual bank confirmation
• Reconcile Receipt with Bank - Anticipated receipt is matched with actual bank statement entry
• Process Unallocated Receipt - Unallocated receipt is recorded when payment cannot be matched to specific invoice
• Allocate Unallocated Receipt - Previously unallocated receipt is applied to specific invoices
• Process Direct Debit - Direct debit procedure is executed to collect payment from customer bank
• Run Payment Collection - Payment Collection Run (PYC) is executed to collect amounts from debtor accounts via direct debit
• Generate Payment Collection File - Bank transfer file is generated from Payment Collection Run for electronic transmission
• Match Electronic Bank Statement - Imported bank statement line is automatically matched to open AR items
• Import Bank Statement - Bank statement is imported for matching against AR receipts
• Void Payment Collection - Payment collection entry is voided and allocation markers are reversed
• Reconcile Bank Statement Entry - Bank statement entry is reconciled against an AR receipt transaction
• Accept Trade Note - Trade note (bill of exchange/promissory note) is accepted from customer
• Collect Trade Note - Trade note reaches maturity and is collected through bank
• Apply Cash Manually - Payment is manually applied to open items via AR30.1
• Run Transaction Matching - Automated Transaction Matching (TRM) allocates debtor invoices against receipts
• Apply Cash Automatically - Payments are auto-applied to open items via AR130
• Perform Account Allocation - Manual Account Allocation (ACA) matches specific invoices and payments on debtor account
• Set Allocation Marker Allocated - Allocation marker is set to Allocated on matched invoice/receipt set
• Apply Prepayment to Invoice - Prepayment is applied to matching invoice via AR129
• Set Allocation Marker Paid - Allocation marker is set to Paid by Payment Collection Run (PYC)
• Set Allocation Marker Correction - Allocation marker is set to Correction for erroneous transactions
• Transfer Payment to Customer - Payment is transferred from one customer to another
• Set Allocation Marker Withhold - Allocation marker is set to Withhold to prevent transaction from payment selection
• Set Allocation Marker Force - Allocation marker is set to Force to ensure transaction is included in payment run
• Remove Allocation Marker - Allocation marker is reset to blank (e.g., after payment voiding)
• Generate Settlement Discount - Settlement discount is calculated and posted during Transaction Matching
• Generate Exchange Gain Loss - Exchange gain or loss is generated during multi-currency matching
• Payment received on bank - Payment is confirmed on the bank statement
• Change Payment Method - Payment method on the document is modified
• Run Aging Analysis - Aging analysis is executed to classify open items by overdue periods
• Set Invoice Doubtful - Invoice is marked as doubtful when collection is uncertain
• Remove Doubtful Status - Doubtful status is removed when invoice is expected to be paid
• Generate Debtor Search Set - Debtor search set criteria are defined for collection activity
• Generate Debtor To-Do List - Daily to-do list is generated for credit controller based on search set results
• Create Reminder Diary Entry - Follow-up diary entry is created for credit collection activity tracking
• Record Customer Contact Note - Contact note is recorded against a debtor account or transaction during collection
• Schedule Follow-Up Action - Follow-up action is scheduled for debtor collection activity
• Generate Interest Invoice - Interest invoice is generated for overdue receivable amounts
• Link Problem Code to Invoice - Problem code is assigned to a disputed or problematic invoice
• Remove Problem Code - Problem code is removed from invoice after issue is resolved
• Create Dispute - Dispute record is created for an open item
• Resolve Dispute - Dispute is resolved and resolution date is recorded
• Send Dunning Letter - Dunning/past due notice is generated and sent to customer
• Assess Finance Charge - Finance charge is calculated and posted for overdue items
• Send Customer Statement - Customer statement is printed and sent
• Generate Automated Statement - Debtor statement is automatically generated and dispatched via Collect module
• Generate Automated Reminder - Reminder letter is automatically generated and dispatched via Collect module
• Post AR to General Ledger - AR distributions are posted to GL via AR194/AR196
• Run Ledger Revaluation - Ledger Revaluation is run to revalue open debtor items at current exchange rates
• Interface AR to AP - Open AR transactions are offset against AP via AR48
• Run Aging Report - Aging analysis report is generated
• Change Payment Term - Payment terms on the document are updated
• Factor Invoice With Recourse - Invoice is sold to factor with recourse (risk retained)
• Factor Invoice Without Recourse - Invoice is sold to factor without recourse (risk transferred)
• Change Payment Days 1 - First payment days field is modified
• Change Payment Days 2 - Second payment days field is modified
• Change Payment Days 3 - Third payment days field is modified
• Change Dunning Block - Dunning block indicator is changed
• Create Credit Memo - Credit memo is created for the customer
• Assign Credit Note to Invoice - Credit note is linked to specific sales invoices for settlement
• Write Off Payment Difference - Small payment difference is written off to the general ledger
• Write Off Bad Debt - Uncollectible amount is written off as bad debt
• Write Off Currency Difference - Currency difference on receipt is written off to GL
• Correct Sales Invoice - Sales invoice correction is posted via AR correction transaction
• Create Chargeback - Chargeback debit memo is created for underpayment
• Apply Discount Adjustment - Discount adjustment is recorded during cash application
• Create Short/Overage Adjustment - Short or overage adjustment is recorded during application
• Review Exceeded Adjustment - Adjustment exceeding limit is reviewed via AR36
• Set Dunning Block - Dunning block is applied to prevent dunning
• Remove Dunning Block - Dunning block is removed to allow dunning
• Record Goods Issue - Goods issue is recorded for the delivery
• Cash Discount Due Date passed - Cash discount period has expired without payment
• Due Date passed - Invoice net due date has passed without payment
• Change Baseline Date - Baseline date for payment calculation is changed
• Change Cash Discount Percentage 1 - First cash discount percentage is modified
• Change Cash Discount Percentage 2 - Second cash discount percentage is modified
• Change Item Text - Line item text on the document is modified
• Send 1st Overdue Notice - First dunning notice is sent to customer
• Send 2nd Overdue Notice - Second dunning notice is sent to customer
• Send 3rd Overdue Notice - Third dunning notice is sent to customer
• Send 4th Overdue Notice - Fourth dunning notice is sent to customer
• Send 5th Overdue Notice - Fifth dunning notice is sent to customer
• Send 6th Overdue Notice - Sixth dunning notice is sent to customer
• Send 7th Overdue Notice - Seventh dunning notice is sent to customer
• Send 8th Overdue Notice - Eighth dunning notice is sent to customer
• Send 9th Overdue Notice - Ninth dunning notice is sent to customer
• Reverse Invoice - Invoice is reversed/cancelled in the system
• Run Period-End Update - Period-end totals are updated via AR199
• Run Period Cleardown - Period cleardown compresses matched transactions into summary balances by period
• Run Year Cleardown - Year-end cleardown summarizes annual transactions to final period balances
• Archive Cleared Transactions - Cleared/matched transactions are archived during Ledger Cleardown
• Delete Cleared Transactions - Cleared/matched transactions are permanently deleted during Ledger Cleardown
• Archive Fully Paid Invoice - Fully paid sales invoice is archived from live to history company
• Delete Reminder Diary - Reminder diary entries are purged for archived invoices

Case attributes

• Company Code (Text) - Company or entity code
• Cost Center (Text) - Cost center responsible
• Document Type (Text) - Type of financial document
• GL Account (Text) - General ledger account
• Status (Text) - Current status
• Amount (Currency) - Monetary value
• Currency (Text) - Transaction currency
• Created By (Text) - User who created the record
• Document Number (Text) - Unique identifier for the document
• Vendor/Customer (Text) - Business partner ID
• Document Date (Date) - Date of the document
• Due Date (Date) - Payment or completion due date

Data tables

• BKPF - Accounting Document Header
• BSEG - Accounting Document Line Item
• BSID - Customer Open Items
• KNA1 - Customer Master - General Data
• KNB1 - Customer Master - Company Code Data
• KNKK - Customer Credit Management
• MHNK - Dunning History
• BSAD - Customer Cleared Items
• BSIH - Historical Customer Line Items (Archived)
• CDHDR
• CDPOS
• KNB5 - Customer Dunning Data
• KNBK - Customer Bank Details
• KNVP - Customer Partner Functions
• KNVV - Customer Sales Area Data
• SWWWIHEAD - Workflow Work Item Header
• T001
• USR02
• T003 - Document Types
• T005 - Countries
• T052 - Payment Terms Configuration
• TCURF - Conversion Factors
• TCURR - Exchange Rates
• TCURX - Currency Decimals

Budgeting (BUDGET)

Budget planning, forecasting, variance analysis

Data tables

• FMBDT - FM Budget Data
• FMIT - FM Budget Line Items
• FM01 - FM Area Master
• FMFCTR - Funds Centers

Cash Management (CASH)

Bank reconciliation, cash positioning, treasury

Data tables

• FQM_FLOW - One Exposure Table - Central repository for all cash-relevant transactions
• FQCUSTOM - Cash Flow Customizing
• T012 - House Banks
• T012K - House Bank Accounts

Customer Master Data (CMD)

Complete lifecycle of customer records from creation through maintenance

Activities

• Create Customer - New customer master record is created in the system
• Create Customer Order - First sales order is created for the customer
• Change Name - Customer name is changed in the master record
• Change Street - Customer street address is updated in the master record
• Change City - Customer city is updated in the master record
• Set Delivery Block - Delivery block is placed on the customer master
• Change Account Number - Customer account number or reconciliation account is changed
• Remove Delivery Block - Delivery block is removed from the customer master
• Change Bank Code - Customer bank routing code is updated
• Change Credit Limit - Customer credit limit is adjusted in the credit management area
• Change Delivery Block - Delivery block reason is changed on the customer master
• Approve Credit Check - Credit check for the customer is approved
• Deny Credit Check - Credit check for the customer is denied
• Partially Approve Credit Check - Credit check is partially approved with conditions
• Record Goods Issue - Goods issue is posted against a customer order
• Cancel Goods Issue - Previously posted goods issue for the customer is reversed
• Clear Invoice - Customer invoice is cleared by incoming payment
• Send First Overdue Notice - First dunning notice is sent to the customer
• Send Dunning Notices - General dunning run generates notices for the customer
• Send Second Overdue Notice - Second dunning notice is sent to the customer
• Send Third Overdue Notice - Third dunning notice is sent to the customer
• Send Fourth Overdue Notice - Fourth dunning notice is sent to the customer
• Send Fifth Overdue Notice - Fifth dunning notice is sent to the customer
• Send Sixth Overdue Notice - Sixth dunning notice is sent to the customer
• Send Seventh Overdue Notice - Seventh dunning notice is sent to the customer
• Send Eighth Overdue Notice - Eighth dunning notice is sent to the customer
• Send Ninth Overdue Notice - Ninth dunning notice is sent to the customer
• Delete Customer - Customer master record is flagged for deletion

Data tables

• BKPF - Accounting Document Header
• BSEG - Accounting Document Line Item
• BSID - Customer Open Items
• KNA1 - Customer Master - General Data
• KNB1 - Customer Master - Company Code Data
• KNKK - Customer Credit Management
• LIPS - Delivery Item
• MSEG - Material Document Segment
• VBAK - Sales Order Header
• VBFA - Sales Document Flow
• VBUK - Sales Document Header Status
• CDHDR
• CDPOS
• KNBK - Customer Bank Details
• KNVP - Customer Partner Functions
• KNVV - Customer Sales Area Data
• USR02
• T005 - Countries

Controlling (CO)

Cost centers, cost elements, internal orders, profitability analysis

Data tables

• COBK - CO Document Header
• COEP - CO Line Items
• COSP - CO External Postings
• COSS - CO Internal Postings
• CSKS - Cost Center Master
• CSKA - Cost Element Master

Core HR (CORE_HR)

Employee master data, organizational structure

Activities

• Create Employee Record - New employee record created via HR11.1. Initial creation of EMPLOYEE and PAEMPLOYEE records with demographic, pay, and organizational data.
• Assign Position - Employee assigned to a position via PA02/HR11. Links employee to position record in PAPOSITION via PAEMPPOS.
• Assign Department - Employee assigned to a department. EMPLOYEE.DEPARTMENT populated or changed.
• Assign Job Code - Employee assigned a job code via HR11. EMPLOYEE.JOB_CODE set, determining pay ranges and EEO classification.
• Assign Supervisor - Employee assigned to a supervisor via HR11. EMPLOYEE.SUPERVISOR set linking to HRSUPER.
• Set Pay Rate - Employee pay rate established or changed. EMPLOYEE.PAY_RATE, SALARY_CLASS, and PAY_FREQUENCY set.
• Set Employee Status - Employee status code set via HR11. EMPLOYEE.EMP_STATUS determines pay eligibility (links to EMSTATUS).
• Enroll in Benefits - Employee enrolled in benefit plans (health, dental, vision, life, retirement). May be triggered by new hire or open enrollment period.
• Submit Personnel Action - Hire - Personnel action submitted for new hire via PA52 (Individual Action). PERSACTION record created with ACTION_TYPE=A.
• Hire Applicant - Applicant record converted to employee record. System automatically creates employee_mst record from applicant_mst data upon hire decision.
• Approve Personnel Action - Personnel action approved (PERSACTION.APPROVAL_FLAG set to Y). Required before action update can proceed.
• Execute Action Update - PA100 (Action Update) processes the personnel action, applying changes to EMPLOYEE, PAEMPLOYEE, and creating HRHISTORY records.
• Register Project Hours - Employee registers hours worked on a project activity via bptmm1111m000 session
• Register Production Order Hours - Employee registers hours worked on production orders via bptmm1120m000 session
• Register Service Order Hours - Employee registers hours worked on service orders via bptmm1130m000 session
• Register General Task Hours - Employee registers hours for general tasks (not project-specific) via bptmm1111m200 session
• Approve Hours and Expenses - Authorized employee approves registered hours and expenses before financial processing
• Process Hours to Financials - Approved hours are financially processed, creating journal entries and updating cost records
• Archive Hours History - Processed hours are moved to the detailed history (bptmm200) for long-term retention
• Submit Time Off Request - Employee submits a time off request via Employee Self Service portal. Creates a record in the time off request table for supervisor approval.
• Approve Time Off Request - Supervisor approves or denies an employee time off request submitted through Employee Self Service. Updates request status and notifies employee.
• Assign Skill to Employee - A skill or competency is linked to an employee record via tcppl0120m000
• Assign Role to Employee - An organizational role is assigned to an employee via tcppl0170m000
• Assign Employee to Team - Employee is added to a team via tcppl0150m000 for group-based resource management
• Assign Working Time Schedule - Working time schedule assigned to employee defining regular hours and overtime patterns
• Update Employment Hours - Employee employment hours per period modified (e.g., full-time to part-time change)
• Set Employment Contract Type - Employee employment contract type established or changed (full-time, part-time, temporary)
• Update Contract End Date - Employment contract end date modified, extending or terminating the contract period
• Create Employee Budget - Budgeted hours and costs defined for an employee for a specific period via bptmm300
• Create Department Budget - Budgeted hours and costs defined for a department for a specific period via bptmm310
• Compare Actual vs Budget - Actual hours and costs compared against budgeted values for employee or department
• Change Department - Employee department changed. HRHISTORY FLD_NBR=15 records the change. Tracked as a transfer event.
• Change Job Code - Employee job code changed. HRHISTORY FLD_NBR=19 records the change. May affect pay rate and EEO classification.
• Change Employee Status - Employee status changed. HRHISTORY FLD_NBR=20 records the change. May affect pay eligibility.
• Change Pay Rate - Employee pay rate modified. PRRATEHIST records the old and new rates with effective date and reason.
• Change Supervisor - Employee reporting relationship changed. EMPLOYEE.SUPERVISOR updated, logged to HRHISTORY.
• Change Process Level - Employee moved to a different process level (organizational entity). EMPLOYEE.PROCESS_LEVEL updated.
• Change Location - Employee work location changed. PAEMPLOYEE.LOCAT_CODE updated.
• Change Position - Employee position assignment changed. PAEMPPOS updated with new position and dates.
• Submit Personnel Action - Change - Personnel action submitted for employee change via PA52. PERSACTION record created with ACTION_TYPE=E.
• Mass Change Action - Mass change personnel action affecting multiple employees via PA100. PERSACTION.ACTION_TYPE=M.
• Mass Pay Change - Mass pay change action affecting compensation for a group. PERSACTION.ACTION_TYPE=P.
• Update User Fields - Employee user-defined fields updated. HREMPUSF values changed via HR11.
• Update Employee Self Service Profile - Employee updates personal information (address, phone, emergency contact) through the Employee Self Service web portal.
• Add Dependent - New dependent added to employee record via EMDEPEND.
• Change Benefits Enrollment - Employee benefits enrollment modified due to qualifying life event (marriage, birth, divorce) or annual open enrollment.
• Update Emergency Contact - Emergency contact information added or modified in PAEMERGCNT.
• Record Attendance Event - Attendance incident recorded in ATTENDHIST with appropriate attendance code.
• Record Workplace Accident - Workplace accident or injury reported and recorded in the workers compensation system. Initiates claim tracking and OSHA compliance workflow.
• File Workers Compensation Claim - Workers compensation claim filed for a workplace injury. Tracks claim details, medical treatment, lost time, and claim costs.
• Record Grievance - Employee grievance or disciplinary action formally recorded in the HR system. Initiates resolution workflow.
• Conduct Performance Review - Performance review completed and recorded in REVIEW table via PA22. Includes rating, reviewer, and next review date.
• Schedule Next Review - Next performance review date set. PAEMPLOYEE.NEXT_REVIEW updated.
• Create Position - New position record created in PAPOSITION via PA02. Defines organizational slot with department, job code, and pay information.
• Activate Position - Position status set to Active (PAPOSITION.POSIT_STATUS=1).
• Freeze Position - Position status set to Frozen (PAPOSITION.POSIT_STATUS=3). Position temporarily unavailable for assignment.
• Inactivate Position - Position status set to Inactive (PAPOSITION.POSIT_STATUS=5). Position no longer available.
• Change Position Attributes - Position attributes modified (department, pay rate, supervisor, etc.). Change logged to PAPOSCHG.
• Apply Position Defaults - Position defaults applied to employee record via HR11 Fill Defaults button. Controlled by HR10.1 PO topic.
• Run Position Defaulting Update - PA102 run to mass-update employees with changed position defaults (e.g., new supervisor on position).
• Create Job Requisition - New job requisition opened in PAJOBREQ. Specifies position, job code, department, and headcount.
• Approve Job Requisition - Job requisition approved. PAJOBREQ approval date and approver recorded.
• Record Interview - Interview conducted and results recorded in the applicant tracking system. Includes interview notes, interviewer, and outcome.
• Fill Job Requisition - Job requisition filled by hiring an employee into the position. PAJOBREQ fill date set.
• Close Job Requisition - Job requisition closed. PAJOBREQ close date set.
• Submit Personnel Action - Termination - Personnel action submitted for employee termination via PA52.
• Set Termination Date - Employee termination date set. EMPLOYEE.TERM_DATE populated.
• Set Termination Status - Employee status changed to a termination status code (no pay). EMSTATUS.PAY_STATUS = TN or TB.
• End Position Assignment - Employee position assignment ended. PAEMPPOS.END_DATE set to termination effective date.
• Archive Employee Record - Employee record retained in system with inactive status for historical reporting and compliance.
• Generate HR Writer Report - HR170 (HR Writer) report generated using data from HRHISTORY, EMPLOYEE, PAEMPLOYEE, and related tables.
• Generate Employee Audit Report - Employee audit report produced listing all data item changes from HRHISTORY for compliance review.
• Generate EEO Report - EEO (Equal Employment Opportunity) report generated using PAEMPLOYEE demographic data and JOBCODE classifications.
• Run Payroll Calculation - Payroll generation executed for the current pay period. Calculates gross pay, deductions, taxes, and net pay for all active employees.
• Post Payroll - Payroll transactions posted to GL and payroll history. Moves transactions from prtrx_mst to prtrxp_mst and creates GL journal entries.
• Generate Payroll Checks - Payroll checks or direct deposit payments generated for the current pay period. Creates payment records and ACH files.
• Close Payroll Period - Payroll period closed after all transactions are posted. Prevents further modifications to the closed period.

Data tables

• PA0000 - HR Master - Actions (Infotype 0000)
• PA0001 - HR Master - Org Assignment (Infotype 0001)
• PA0002 - HR Master - Personal Data (Infotype 0002)
• AGR_1251 - Authorization Profile Values
• AGR_USERS - Role-to-User Assignments
• HRP1000 - HCM Infotype 1000 (Object)
• PA0006 - HR Master - Addresses (Infotype 0006)
• USR02

Fixed Assets (FA)

Asset lifecycle, depreciation, acquisition, retirement

Data tables

• ANLA - Asset Master - General
• ANLB - Depreciation Terms
• ANLC - Asset Value Fields
• ANEK - Asset Document Header
• ANLZ - Asset Time-Dependent Data

General Ledger (GL)

Journal entries, chart of accounts, financials

Activities

• Create Journal Voucher - Journal voucher created via GLS100/GLS120 for manual entries, reservations, or adjustments. FAM function determines panel layout and processing rules.
• Create Internal Journal Voucher - Internal journal voucher created via CAS100 for internal cost accounting transactions between divisions or cost centers.
• Create Finance Interface Batch - Finance interface batch header created in FGLINH via GLS840MI AddBatchHead API for importing external GL transactions (e.g., payroll, external systems).
• Add Finance Interface Lines - Transaction lines added to finance interface batch in FGLINL (position-based) or FGLINF (field-based) via GLS840MI AddBatchLine/AddBatchLineFld.
• Import Journal Entries - Journal entries imported from CSV or XML files via Import Journal Entries form. CSV format: Date, Account, Unit Code 1-4, Debit, Credit, Reference, AnalysisAttributes 01-15. XML format uses journal_entry tags with nested Date, Account, UnitCode1-4, Debit, Credit, Ref, AnalysisAttribute01-15 elements.
• Enter Accounting Lines - Individual accounting lines entered on voucher via GLS120 coding panel, specifying account dimensions, amounts, currency, and VAT codes.
• Create User-Defined Journal Entry - Transaction entered in a user-defined journal. User-defined journals are custom writeable journals created to store, retrieve, and track entries specific to business needs beyond the standard General journal.
• Apply Standard Voucher Template - Standard voucher template with predefined accounting lines applied via GLS015 to auto-populate recurring journal entry patterns.
• Create Auto-Reverse Voucher - Journal voucher with auto-reverse date (SHDT) for temporary/accrual entries that reverse automatically at the specified date.
• Reset Sequence Numbers - Transaction sequence numbers reset on the Journal Entries form via Sequence Reset action. Required when adding a new transaction between two consecutive existing transactions to maintain proper ordering.
• Validate Finance Interface Batch - Finance interface batch validated via GLS840MI CtrlBatch. Status changes from 10 (New) to 14 (Verified) or 13 (Verified with errors).
• Screen Transaction in Work File - Transaction screened by GLS036 program in FCR040 work file. Validates accounting string, date, and voucher balance before GL posting.
• Flag Erroneous Voucher - Voucher flagged as erroneous (FCR040 status 8) by GLS040 when accounting lines contain invalid values or voucher does not balance.
• Correct Erroneous Voucher - Erroneous voucher corrected via GLS037/GLS038/GLS039. Error code 1 = invalid accounting values, error code 2 = unbalanced voucher.
• Post to General Ledger - Transaction posted to FGLEDG by GLS040 program. Simultaneously updates sub-ledgers (FSLEDG for AR, FPLEDG for AP). Core milestone event.
• Mass Post Journals - Multiple journals posted to the ledger simultaneously via the Mass Journal Posting utility. Posts transactions from one or more journals to the ledger in batch. A fiscal year must be defined for each transaction. The only way to get transactions into the ledger from any journal is by posting them.
• Enter Journal via Ledger Entry - Journal transaction entered manually via Ledger Entry (LEN) form in SunSystems. LEN provides customizable journal types and supports preset templates for recurring entry patterns. Analysis dimensions are populated based on journal type.
• Update GL Balance File - GL balance file (FBAVAL) updated by GLS050 program using FCR050 transaction table. Aggregates posted transactions into period-level balances per balance key.
• Import Journal via Ledger Import - Journal transactions loaded and validated via Ledger Import (LIM) from external sources (other SunSystems BUs, Order Fulfilment, third-party systems). Transactions are validated before acceptance; invalid lines are rejected. Loading can be done without posting (LoadOnly mode).
• Auto-Generate Journal from Subsystem - Journal automatically generated by a SunSystems subsystem function: Corporate Allocation Run (CAL), Payment Run (PYR), Payment Collection Run (PYC), Ledger Revaluation (LER), Account Allocations (ACA), Transaction Matching (TRM), Asset Disposal (FAD), or Depreciation Calculation (FDC). Auto-journals are posted via Ledger Import.
• Compress Journal - Journal transactions compressed by account and date via Journal Compress action. Reduces the number of journal records by consolidating entries for the same account on the same date. WARNING: Journal control numbers are deleted during compression.
• Apply Journal Preset - Journal preset applied during Ledger Entry (LEN) to predefine some or all transaction details for the journal. Presets speed up recurring entries by pre-populating account, analysis codes, amounts, and descriptions.
• Compress Ledger - Ledger transactions compressed by account and date. Reduces the number of ledger records. WARNING: Ledger control numbers are deleted during compression.
• Load to Posting Table - Transaction lines loaded into the posting work table (PSTG_WRK_TBL) during import without validation or posting. Lines receive a PostingHeaderId but no journal number. Must use Ledger Import (LIM) to locate and post.
• Create Accounting Journal - Accounting journal created by GLS041 program after GL posting. Assigns journal number and sequence numbers to each transaction for audit trail.
• Delete from Transaction Work File - Successfully posted transactions deleted from FCR040 work file after journal creation. Completes the posting cycle.
• Update Finance Interface to GL - Finance interface batch updated to GL via GLS840MI UpdBatch. Batch status changes to 20 (Updated in General Ledger). VONO/VSER/YEA4 written back to FGLINF.
• Display Voucher - Voucher displayed via GLS200 for review. Shows all transactions in the voucher with drill-down to sub-ledger records and VAT details.
• Print Journal Transaction Report - Journal Transaction Report printed for audit purposes. Must be printed before posting becomes available. Report can be sorted by sequence number (default) or by account then date and sequence. Shows date, GL account, description, reference, and debit/credit amounts with totals.
• Print GL Transaction Report - General Ledger Transaction Report printed showing posted ledger transactions. Provides detail of all transactions in the ledger for a specified date range or account range. Used for audit trail and financial review.
• Display GL Transactions - GL transactions displayed via GLS210/GLS211 with detailed information including FAM function, accounting dimensions, and amounts.
• Print GL Worksheet Report - General Ledger Worksheet Report printed showing account balances in worksheet format. Provides trial balance data with beginning balance, period activity, and ending balance for each account.
• Print Financial Statement - Financial statement printed using a predefined report definition from gl_rpt_mst. Supports balance sheet, income statement, and custom financial statement formats. Multi-currency translation can be applied.
• Query GL Posted Transactions - GL posted transactions queried using the G/L Posted Transactions form or Query form. Allows filtering by multiple criteria including account, date range, reference, and journal. All fields except Analysis Attributes are display-only.
• Display GL Balance - GL balance file displayed via GLS215 for a selected range of periods and balance keys. Shows aggregated balances with period analysis.
• Reverse Voucher - Voucher reversed via GLS900. Creates new voucher with reversed amounts and same date. AP/AR transactions reopened. RVST status set to 20 or 90.
• Enter Reversing Journal Entry - Reversing journal entry created in the General journal. Since posted ledger transactions cannot be changed or deleted, the only way to correct an incorrect entry is by entering a reversing entry with an opposite amount and the same date as the original transaction.
• Reverse Voucher Date Only - Voucher date corrected via GLS900 with Voucher on new accounting date option. Creates two new vouchers to move transaction to correct period.
• Create Corrective Voucher - Corrective voucher created to adjust accounting lines on an existing voucher without full reversal.
• Change VAT Information - VAT code, VAT account type, base country, or from/to country changed on GL transaction via GLS211/G option 7.
• Create GL Allocation Proposal - GLS130 creates accounts allocation proposal for a period range using allocation templates. Can preview before updating.
• Update GL Allocation to Ledger - GLS130 updates the allocation proposal to GL. Creates vouchers for allocated amounts across cost centers/dimensions.
• Create Period Accounting Entry - GLS140 moves costs from balance accounts to expense accounts (period accounting/accrual release).
• Post Cross-Division Voucher - Transaction from one division posted to another division via coding panel GLS120. Creates intercompany/cross-division entries.
• Allocate Across Divisions - GLS130 allocation across divisions - costs apportioned from one division to another using MUC (Multiple Unit Coordination).
• Reconcile GL Control Accounts - GL control accounts reconciled against sub-ledger balances (AR/AP). Validates that FGLEDG GL balances match FSLEDG/FPLEDG totals.
• Reconcile GL Balance File - GL balance file (FBAVAL) analyzed and repaired via GLS940/GLS941. Detects discrepancies between FGLEDG transactions and FBAVAL aggregates per balance key and period.
• Validate Journal Lines - Transaction lines validated against account setup, period restrictions, analysis code validity, and balance rules. Invalid lines are rejected with error messages stored in PSTG_ERR. ValidateOnly mode checks without posting.
• Authorize Journal - Journal authorized by an authorized operator when Authorization Required is set in Ledger Setup (LES). Unauthorized journals cannot be posted. Authorization levels and amount limits are defined in the authorization setup.
• Check Unbalanced Vouchers - Unbalanced vouchers detected via GLS975 report. All vouchers must balance before period close.
• Write Journal to Hold File - Journal transaction written to the Held Journals file instead of being posted immediately. Held transactions are excluded from standard reports but appear in the Held Journal Listing. Must be released before posting.
• Release Held Journal - Held journal released from the hold file, making it available for validation and posting to the ledger. Transitions from held status to ready-for-posting status.
• Check Transaction Work File - FCR040 work file checked via GLS970 to ensure no interrupted or erroneous jobs remain before period close. Prints list of transactions by status.
• Restart Interrupted Job - Interrupted GL update job restarted via GLS047. Jobs with FCR040 status 0 (active) or 9 (GL updated, no journal) can be restarted.
• Enter Budget - Budget values entered via BUS100 for specified accounts, periods, and dimensions. Stored in FBUDET table.
• Allocate Budget - Budget allocated across periods and dimensions via BUS180/BUS190 using accounts allocation templates.
• Compare Budget vs Actual - Budget vs. actual comparison performed using GLS215 column templates showing budget (FBUDET) and actual (FBAVAL) values side by side.
• Close Accounting Period - Accounting period closed via GLS990 by adjusting FAM function date ranges. Prevents transaction entry in closed periods. Critical period-end milestone.
• Update Current Period - Current accounting period updated on the Accounting Periods form. Must be maintained manually by users. The system either prompts for dates or uses current period dates for posting and reporting.
• Update Current Fiscal Year - Current Fiscal Year field updated on the General Parameters form to the next fiscal year. Required before posting journals for the next fiscal year and closing the previous year. Must be manually updated during year-end close.
• Open New Accounting Period - New accounting period opened via GLS990 or CRS406. Sets new from-date allowing transaction entry in the new period.
• Post Journal to Unified Ledger - Journal transactions posted to the SunSystems unified ledger (LDG_DETAIL). All financial data - GL, AR, AP, assets - posts to a single integrated ledger simultaneously. No separate subledger reconciliation needed. Journal and line numbers are assigned for audit trail.
• Generate Journal Listing on Post - Journal Listing report generated automatically at time of posting when Force Journal Listing is enabled in Ledger Setup (LES). Provides immediate audit trail documentation of posted transactions.
• Print Balance Lists - Trial balance and balance lists printed via GLS510 for the period/year. Validates debit/credit totals before period finalization.
• Update Balance File - Balance table (BAL) updated with period-level aggregated balances after transactions are posted. Calculates opening balance, period debits/credits, and closing balance for each account/analysis dimension combination.
• Create Internal Account Entries - Internal account entries created via CAS950 for cost accounting reconciliation at period end.
• Calculate Profit and Loss Transfer - Annual profit/loss transfer calculated via GLS995. Transfers P/L result to balance sheet account. Must run after all year-end adjustments.
• Generate Year-End Closing Journal Entries - Year End Closing Journal Entries utility creates debit and credit entries to close all revenue and expense accounts for the date range specified. Entries are placed in the General Journal and must then be posted to the GL. Must be run after all entries for the fiscal year are posted. If adjusting entries are made after this procedure, it must be run again. System-generated references must not be changed.
• Create Opening Balance - Opening balance created via GLS905 (GL Balance File Start Annual Run). Creates opening transaction in period 00 of the new fiscal year.
• Generate Daybook Listing - Daybook Listing generated sequencing transactions by date and period. Similar to Journal Listing but allows custom audit trail reports with flexible sorting and filtering options.
• Generate Account Listing - Account Listing generated showing transactions within specific accounts. Used for account-level audit verification and reconciliation.
• Generate Multi-FSB Year-End Closing Entries - Multi-FSB Year End Closing Journal Entries utility creates closing entries for multi-FSB ledgers independently of the standard GL. Multi-FSB ledgers close independently and manually.
• Close Fiscal Year Definitively - Fiscal year closed definitively via GLS985/GLS986. Irreversible action that prevents any further posting to the closed year.
• Generate Trial Balance Report - Trial Balance report generated showing all account balances in debit/credit format for a specified period. Key period-end reconciliation report.
• Archive GL Transactions - GL transactions archived via GLS800. Moves fully reconciled transactions from FGLEDG to FGLHST and FGLEDX to GLHSX. Reduces active table size.
• Archive Cost Accounting Transactions - Internal account entries archived via CAS970. Moves old CINACC and CRACTR records with error code blank, 0, or 9 to archive tables.
• Run Corporate Allocation - Corporate Allocation Run (CAL) executed to reallocate costs and revenue across cost centers, departments, or business units according to predefined allocation templates. Generates and posts journals via Ledger Import. Supports inter-company and cross-division allocations.
• Run Account Allocation - Account Allocation (ACA) executed to manually match selected debit and credit transactions. Calculates settlement discounts and exchange gains/ losses during the matching process. Can also amend non-financial details on posted transactions (description, analysis codes, dates).
• Archive Finance Interface Data - Finance interface data archived via GLS816. Moves FGLINH header records and related FGLINL/FGLINF/FFIHSD data to FFIHST history tables.
• Run Ledger Revaluation - Ledger Revaluation (LER) executed to recalculate target currency values on outstanding transactions using current exchange rates. Generates revaluation adjustment postings for unrealized exchange gains/losses. Selection criteria defined in Ledger Revaluation Profiles (LEP). Consolidation options: by period, asset, account, or analysis dimension.
• Enter Currency Period Rate - Period exchange rate entered for a currency pair. Period rates apply for an entire accounting period and are used for standard currency conversion during posting and reporting.
• Enter Currency Daily Rate - Daily exchange rate entered via Currency Daily Rates (CND) for a specific date range and optionally an account range. Daily rates take precedence over period rates when available.
• Change Current Period - Current accounting period changed via Change Period (CPD) function. Affects Financials, Inventory, Purchasing, and Sales modules independently. Period format: pppyyyy. Should be changed when no users are logged in. Audit trail reports should be generated before transitioning.
• Restrict Period Posting - Period posting restrictions configured globally in Ledger Setup and refined by operator group in security configuration. Users can be restricted to posting only within their open range of periods.
• Transfer Profit/Loss to Balance Sheet - Year-end profit/loss transfer posting created to move the P&L result to an appropriately named balance sheet account. P&L account balances do not carry forward annually - this transfer must be posted manually.
• Create Opening Balances - Opening balances created for the new fiscal year by carrying forward balance sheet account balances. P&L accounts start at zero. Opening entries posted to period 000 of the new fiscal year.
• Run On-Demand Consolidation - On-demand consolidation executed to aggregate financial data from child business units into the parent/consolidated entity. Uses consolidation mappings for account and analysis code translation. Supports multi-currency conversion and intercompany eliminations.
• Run Summary Consolidation - Summary consolidation executed to create aggregated balances from child units without individual transaction detail. Faster than transactional consolidation for period-end reporting.
• Run Transactional Consolidation - Transactional consolidation executed to copy individual transaction lines from child business units to the parent entity. Preserves full transaction detail for drill-down and audit purposes.
• Run Ledger Cleardown - Ledger Cleardown executed to archive completed transactions from the active LDG_DETAIL table to the archive. Creates an archive for each processing year. Reduces active database size while preserving audit trail.
• Run Data Audit Maintenance - Data Audit Maintenance (DAM) executed to manage audit trail data. Configurable to track insertions, updates, and deletions on static data records. Retention period set in days, months, or years. Audit data can be extracted to Excel (XLS) format.
• Run Transaction Matching - Transaction Matching (TRM) executed to automatically match debit and credit transactions using predefined matching criteria. Calculates settlement discounts and exchange gains/losses. Updates allocation markers on matched transactions.
• Run Reconciliation Manager - Reconciliation Manager (RCM) executed for automated bank reconciliation and account matching. Uses configurable matching criteria to automatically match transactions. More sophisticated than manual ACA matching.
• Post Cross-Business-Unit Journal - Journal posted across multiple business units using SunSystems multi-BU capabilities. Entries are posted simultaneously to the unified ledger in both the source and target business units.
• Create Consolidation File - GL150 creates consolidation file by aggregating balances from child companies into parent company GLCONSOL table based on GLCHMAP and GLPERIODMP mappings.
• Consolidate Budgets - Budget Consolidation utility consolidates all previously unconsolidated site budgets and plans from subordinate sites to the parent financial entity through the cutoff date.
• Run Currency Translation - GL135 translates account balances from one currency to another using defined translation codes and exchange rates. Creates translation adjustment entries.
• Run Currency Revaluation - GL195 revalues non-base currency account balances using current exchange rates. Creates gain/loss entries for unrealized currency differences.
• Process Recurring Journals - GL100 processes released recurring journal entries (RJCONTROL/RJTRANS) for current period, creating regular GLTRANS entries from templates.
• Run Cost Allocation - CA110 runs released allocations (CAHEADER) creating CATRANS records and posting allocation journal entries to GLTRANS.
• Generate Financial Report - RW program generates financial reports (trial balance, balance sheet, income statement) using RWHEADER definitions and GL data.
• Delete GL Transaction History - GL300 purges historical transactions from GLTRANS where status=9 (History). Reduces active table size after archiving.
• Delete Material Transactions - Material transaction history records deleted via housekeeping utility. Once deleted, the audit trail for inventory transactions is lost and references from ledger/journal transactions to deleted material transactions are cleared. System displays a message if detail is not available.
• Rebuild GL Balance File - GL905/GL910 rebuilds the GLAMOUNTS balance file from GLTRANS transaction records. Used to correct balance discrepancies.
• Run Budget Entry - FB20.1 enters budget amounts/units for accounts by period. Creates FBTRANS records with budget version tracking.
• Run Budget Interface - FB165 loads budget data from external sources into FBTRANS via the budget interface table.
• Quick Post Journal Entry - GL40.1 with Quick Post option immediately posts a journal entry bypassing the separate release and post steps. Status goes directly to 4 (Quick Posted).
• Hold Journal Entry - Journal entry placed on hold via hold code in GL40.1. Prevents release and posting until hold is removed.
• Remove Journal Entry Hold - Hold code removed from journal entry allowing it to proceed through release and posting.
• Change Posted Journal Entry - Posted journal entry backed out and modified via GL40.1 when GLS-CHG-POST-TRAN=Y. Creates offsetting entries.
• Unrelease Journal Entry - Released journal entry returned to unreleased status via GL40.1 when GLS-CHG-REL-TRAN=Y. Allows modifications.
• Enter Multi-FSB Journal Entry - Journal entry created for a multi-FSB ledger. Multi-FSB journal entries can only be entered into the General Journal. Multi-FSB budgets and plans must be entered separately.
• Post Multi-FSB Journal - Multi-FSB journal entries posted to the multi-FSB ledger via Multi-FSB Ledger Posting for Journal form. No multi-FSB transactions are posted to the standard General Ledger or to other multi-FSB ledgers.
• Export Ledger to External System - Ledger transactions exported via ExtFinLedgerPosting through the EXTFIN replication category. Exports data from the SyteLine ledger table to external financial systems using XML documents with batch sequence information.
• Export Analytical Ledger to External System - Analytical ledger transactions exported via ExtFinAnaLedgerPosting through the EXTFIN replication category. Exports data from the SyteLine ana_ledger table to external financial systems.

Data tables

• ACDOCA - Universal Journal Entry
• BKPF - Accounting Document Header
• BSEG - Accounting Document Line Item
• SKA1 - GL Account Master (Chart of Accounts)
• SKB1 - GL Account Master (Company Code)
• ACDOCT - Universal Journal Entry Texts
• FAGLFLEXT - GL Totals Table
• NSDM_V_JOURNAL - New GL Journal Entry View (S/4HANA)
• T001
• USR02
• T003 - Document Types

Inventory Management (INV)

Stock movements, transfers, adjustments, valuation

Activities

• Create Planned Inventory Transaction - A planned inventory transaction is created by an originating module (purchase, production, sales) indicating expected future inventory movement
• Connect Item to Warehouse - An item is connected to a warehouse, creating a MITBAL record with initial balance and planning parameters via MMS002
• Connect Item to Facility - An item is connected to a facility, creating a MITFAC record with planning method, order type, and cost values via MMS003
• Update Planned Inventory Transaction - A planned inventory transaction is modified (quantity, date, or other attribute changed) before conversion to a warehousing order
• Delete Planned Inventory Transaction - A planned inventory transaction is removed because the originating order was cancelled or modified
• Create Warehousing Order - A warehousing order is created to initiate an inventory movement (receipt, issue, transfer, or WIP transfer)
• Create Inbound Order Line - An inbound order line is created on a warehousing order for goods to be received into a warehouse
• Create Outbound Order Line - An outbound order line is created on a warehousing order for goods to be issued from a warehouse
• Block Warehousing Order - A warehousing order is blocked, preventing further processing until the block is removed
• Unblock Warehousing Order - A blocked warehousing order is released for further processing
• Create Receipt Header - A warehouse receipt header is created to begin the goods receiving process
• Link Inbound Order to Receipt - One or more inbound order lines are linked to a receipt, generating receipt lines
• Confirm Receipt Line - A receipt line is confirmed with the actual quantity received, triggering inventory update
• Create Balance Identity - A new balance identity record is created in MITLOC when stock is first placed at a location/lot combination
• Register Lot on Receipt - Lot codes are registered for lot-controlled items during the receipt process
• Register Lot Expiration Date - An expiration date is registered or calculated for a lot in the lot master (MILOMA), based on manufacturing date and shelf life settings
• Register Serial on Receipt - Serial numbers are registered for serialized items during the receipt process
• Reject Receipt Line - A receipt line is rejected due to quality or quantity issues, inventory is placed in quarantine
• Complete Receipt - The receipt is fully completed -- all lines confirmed and inventory updated in the system
• Generate Outbound Advice - The system generates advice lines for outbound order lines indicating which locations/lots/serials to pick from
• Allocate Inventory Automatically - The auto-allocation batch job (MMS920) allocates stock from MITLOC balance identities to demand orders, creating MITALO records
• Release Outbound Order Line - An outbound order line is released for picking and shipment processing
• Deallocate Inventory - Previously allocated stock is deallocated from an order line, removing the MITALO record and restoring available quantity
• Pick Inventory - Inventory is physically picked from the warehouse based on outbound advice
• Approve Picked Quantity - The picked quantity is approved after inspection or verification
• Create Shipment - A shipment record is created to group outbound order lines for transport
• Compose Shipment - Shipment lines are split, moved, or added to organize the shipment contents
• Confirm Shipment - The shipment is confirmed, updating inventory with actual shipped quantities
• Print Bill of Lading - A bill of lading document is printed for the confirmed shipment
• Print Packing Slip - A packing slip document is printed for the shipment
• Create Transfer Order - A warehousing order of type Transfer is created to move goods between warehouses or locations
• Execute Inventory Transfer - An inventory transfer movement is physically executed, moving stock between locations or warehouses
• Move Balance Identity - A balance identity is physically moved between stock locations within the same warehouse using MMS130 or MMS850MI.AddMove
• Complete Transfer - The transfer is completed and both source and destination inventories are updated
• Create Cycle Count Order - A cycle counting order is created to verify registered versus actual inventory quantities
• Print Cycle Count Order - The cycle count order is printed for physical counting in the warehouse
• Enter Cycle Count Results - The physical count results are entered into the system for comparison with registered quantities
• Approve Cycle Count Variance - Cycle count variances are reviewed and approved before inventory adjustment
• Process Cycle Count - The cycle count is processed, updating registered inventory to match counted quantities
• Create Adjustment Order - An inventory adjustment order is created to manually correct registered inventory quantities
• Perform Quick Inventory Adjustment - A quick physical inventory (MMS310) is performed to immediately correct on-hand balances for individual items without a full counting round
• Enter Adjustment Line - An adjustment order line is entered specifying the target inventory quantity for a specific stock point
• Approve Adjustment Order - The inventory adjustment order is approved by an authorized user when approval is required
• Process Adjustment Order - The approved adjustment order is processed, updating inventory quantities to the specified target values
• Perform Inventory Valuation - Inventory value is calculated for items and warehouses using the configured valuation method (FIFO, LIFO, MAUC, etc.)
• Perform Inventory Revaluation - Inventory is revalued to market value, creating revaluation transactions that update the inventory cost basis
• Perform Inventory Aging Analysis - An aging analysis is performed to classify inventory into time-based buckets for obsolescence review
• Perform Slow-Moving Analysis - A slow-moving analysis is calculated to identify items with turnover rates below the defined threshold
• Inspect Received Goods - Inbound goods are inspected for quality conformance upon warehouse receipt
• Move to Quarantine - Rejected or suspect inventory is moved to quarantine pending disposition decision
• Reclassify Lot Status - A lot is reclassified from one status to another (e.g., Inspection to Approved, or Approved to Rejected) in MILOMA/MITLOC
• Release from Quarantine - Inventory is released from quarantine after re-inspection or disposition approval
• Expire Lot Automatically - The system night run (MMS978) automatically reclassifies expired lots from Approved to Rejected status based on expiration date
• Scrap Inventory - Defective or obsolete inventory is scrapped, removing it from the system
• Complete Warehousing Order - A warehousing order is fully completed, all lines processed and inventory updated
• Update Inventory Statistics - Stock transaction statistics (MITSTA) are updated based on CRS205 settings when a stock transaction is recorded in MITTRA
• Rebuild Inventory Statistics - Inventory statistics in MITSTA are rebuilt from MITTRA transaction history using MMS091
• Cancel Warehousing Order Line - A warehousing order line is cancelled before completion
• Archive Inventory Transactions - Completed inventory transactions are archived for historical storage, removing them from active tables
• Archive Stock Transactions - Historical stock transactions in MITTRA are archived or deleted via MMS195 based on configured retention rules
• Assign LPN on Receipt - A License Plate Number (LPN) is assigned to received inventory, creating the LOTXLOCXID record that tracks the container through the warehouse
• Validate Lottable Attributes - Lot attributes (Lottable01-Lottable12) are validated against the item's lottable validation configuration during receipt processing
• Release for Putaway - Received inventory is released for putaway, triggering the putaway algorithm to evaluate location selection rules and direct the inventory to optimal storage
• Execute Putaway - Inventory is physically moved from the receiving area to the assigned storage location via RF-directed or task manager putaway
• Confirm Putaway - The putaway task is confirmed, updating the LOTXLOCXID record with the final storage location
• Record Catch Weight on Receipt - Actual catch weight is recorded for a lot during goods receipt, capturing the true weight vs. the nominal quantity for food items
• Verify Catch Weight Variance - The variance between nominal and actual catch weight is verified against tolerance limits. Exceeding tolerance may block the receipt
• Assign Temperature Zone - Inventory is assigned to a specific temperature zone location (cold/frozen/ambient) based on item storage requirements for food safety
• Calculate Best-Before Date - The best-before date is calculated for a received lot based on manufacturing date and the item's configured best-before offset
• Calculate Sales Expiry Date - The last permitted sales date is calculated for a lot based on the item's sales time setting, which is earlier than the expiration date
• Create Wave - Orders are grouped into a wave for batch processing of allocation, pick release, and task generation
• Pre-Allocate Inventory - Inventory is soft-allocated (pre-allocated) to an order, reserving stock at a high level without creating specific pick instructions. Creates DemandAllocation records
• Allocate by FEFO - Inventory is allocated using First Expired First Out logic, selecting lots with the nearest expiration date first to minimize waste and ensure food freshness
• Create Pick Task - A pick task is created in the task manager when firm allocation generates PickDetail and TaskDetail records for task-directed picking
• Release Wave - A wave is released for picking, generating pick tasks for all allocated orders in the wave
• Pack Inventory - Picked inventory is packed into shipping cartons during the packing process, updating cartonization records with dimensions and contents
• Stage for Shipping - Packed inventory is moved to the staging area at the assigned dock door in preparation for loading and shipment
• Trigger Replenishment - Pick location stock falls below minimum threshold in SKULOC, triggering a replenishment task to move stock from bulk/reserve to the pick location
• Execute Replenishment - Replenishment task is executed, moving inventory from bulk storage to the pick face location to support ongoing order fulfillment
• Transfer Ownership - In a 3PL environment, inventory ownership is transferred from one storer to another, updating the STORERKEY on affected inventory records
• Reclassify Item Number - The item number on existing inventory is changed (reclassified), creating withdrawal and deposit transactions in ITRN
• Exchange Pallet - A pallet exchange is performed, transferring inventory from one LPN to another without changing the location
• Initiate Lot Blending - A lot blending operation is initiated for a tank or silo location, combining multiple lots of the same item into a single blended lot
• Complete Lot Blending - The lot blending operation is completed. MILOMA is updated with the blended lot characteristics and MIWLAL records the blending transaction (type 99)
• Create Sublot - A sublot is created from a parent lot during food processing, maintaining traceability from raw material lot through to finished product sub-portions
• Perform RF Inventory Inquiry - An RF-based inventory inquiry is performed to check real-time stock levels at a specific location, lot, or LPN
• Place Quality Hold on Lot - A quality hold is placed on a specific lot, preventing it from being allocated or shipped until the hold is resolved. Critical for food safety recalls
• Release Quality Hold on Lot - A quality hold is removed from a lot after investigation or re-testing confirms the lot meets food safety requirements
• Trigger Reinspection on Lot - A lot reaches its reinspection date and is automatically reclassified from Approved (status 2) to Under Inspection (status 1) by the night run
• Expire Sales Date Automatically - A lot reaches its sales date and is automatically reclassified from Approved to Rejected by the night run, preventing further sales
• Purge Inventory Records - Zero-quantity inventory records are automatically purged from LOTXLOCXID based on the configured purge settings

Data tables

• MARA - Material Master - General Data
• MARC - Material Master - Plant Data
• MATDOC - Material Document (S/4HANA)
• MBEW - Material Valuation
• MKPF - Material Document Header
• MSEG - Material Document Segment
• T001W - Plants
• MAKT - Material Master - Descriptions
• MARD - Material Master - Storage Location
• T006 - Units of Measure
• T156 - Movement Types

Meter to Cash (M2C)

End-to-end meter reading through billing to payment collection

Activities

• Create Reading Document - A new meter reading document is created to capture consumption data
• Conduct Meter Reading - Meter reading is performed to record consumption at the installation
• Receive MSCONS - MSCONS IDoc message is received with meter reading data from external systems
• Change Meter Reading Type - The meter reading type classification is changed on the reading document
• Lock Reading Document - Meter reading document is locked for processing to prevent concurrent edits
• Release Reading Document - Meter reading document is released after review for downstream processing
• Change Meter Reading Zero Consumption - A zero-consumption meter reading is changed or corrected
• Change Meter Reading Other - A non-zero meter reading value is changed or corrected
• Change Billed Meter Reading Zero - A previously billed zero-consumption reading is corrected
• Change Billed Meter Reading Other - A previously billed non-zero meter reading is corrected
• BPEM Meter Reading Created - Business Process Exception Management case created for meter reading issue
• BPEM Meter Reading In Progress - BPEM meter reading exception case is being investigated
• BPEM Meter Reading Completed - BPEM meter reading exception case has been resolved
• Clearing via Incoming Payment - Open item is cleared by an incoming customer payment
• Clearing via Outgoing Payment - Open item is cleared via an outgoing payment or refund
• Create Billing Document - Utility billing document is created from validated meter readings
• BPEM Billing Created - BPEM exception case created for a billing issue
• BPEM Billing In Progress - BPEM billing exception case is being worked on
• BPEM Billing Completed - BPEM billing exception case has been resolved
• Qualify Billing Document - Billing document passes quality checks and validation rules
• Cancel Billing Document - Previously created billing document is reversed
• Create Invoicing Document - Invoice document is created from the billing document for the customer
• BPEM Invoicing Created - BPEM exception case created for an invoicing issue
• BPEM Invoicing In Progress - BPEM invoicing exception case is being worked on
• BPEM Invoicing Completed - BPEM invoicing exception case has been resolved
• Qualify Invoicing Document - Invoicing document passes quality checks before printing
• Cancel Invoicing Document - Previously created invoicing document is reversed
• Print Invoicing Document - Invoicing document is printed and sent to the customer
• Due Date Passed - Payment due date has passed without customer payment

Data tables

• DFKKOP - FI-CA Clearing Documents
• EABL - Meter Reading Documents
• EABLG - Meter Reading Results
• ERCH - Billing Document Header
• ERCHC - Billing Document Items
• ERDK - Invoice Document Header
• CDHDR
• CDPOS
• DBERCHZ2 - Reading-Billing Links
• EANL - Installation Master Data
• EDIDC - IDoc Control Records
• EGERH - Device History
• EMMA_CASE - BPEM Workflow Cases
• ERCHO - Billing Document Operations
• ERDB - Invoice Document Items
• ERDO - Invoice Document Operations
• EVER - Contract Master Data
• USR02

Plant Maintenance (MAINTENANCE)

Equipment maintenance management. Covers preventive maintenance, work orders, and spare parts management.

Activities

• Create Order - Production order created
• Check Materials - Material availability checked
• Reserve Materials - Materials reserved
• Release Order - Order released to production
• Issue Materials - Materials issued to floor
• Start Production - Production started
• In-Process Check - In-process quality check
• Complete Operations - Production operations completed
• Final Inspection - Final quality inspection
• Report Production - Production reported
• Receive to Inventory - Goods received to inventory
• Close Order - Production order closed
• Notification Created - A maintenance notification is created to report an issue or request
• System Status: Created - Maintenance work order has been created in the system
• Create Work Order - A maintenance work order is formally created from notification
• System Status: Released - Work order is released for scheduling and execution
• Change Basic Start Date - The planned basic start date of the work order is modified
• Notification Required Start - Required start date/time specified on the notification
• Notification Required End - Required end date/time specified on the notification
• Notification Actually Completed - Notification is marked as actually completed in the field
• System Status: Partially Confirmed - Work order has at least one operation confirmed but not all
• System Status: Confirmed - All operations on the work order are confirmed as completed
• System Status: Technically Completed - Work order is technically completed, no further time or cost postings
• System Status: Closed - Work order is closed, final settlement and archiving eligible

Case attributes

• Order Type (Text) - Type of production order
• Plant (Text) - Production plant
• Priority (Text) - Production priority
• Quantity (Number) - Quantity to produce
• Status (Text) - Order status
• Work Center (Text) - Production work center
• Batch Number (Text) - Production batch
• Material Description (Text) - Product description
• Material Number (Text) - Product being produced
• Production Order (Text) - Unique order identifier
• Planned End (Date) - Planned completion date
• Planned Start (Date) - Planned start date

Data tables

• AFIH - Maintenance Order Header
• AUFK - Order Master Data
• JCDS - Status Change Documents
• QMEL - Quality Notification
• CDHDR
• CDPOS
• ILOA - PM Object Location and Account Assignment
• QMIH - Maintenance Notification Header
• USR02
• EQKT - Equipment Short Texts
• T003P - Order Types (PM)
• TJ02T - System Status Texts

Material Master Data (MMD)

Material master record lifecycle from creation through deletion

Activities

• Create Material - New material master record is created with basic data views
• Change Material - Material master record fields are changed (description, units, etc.)
• Set Material Settings - Material organizational settings are configured (MRP, purchasing, sales views)
• Delete Material - Material master record is flagged for deletion or archiving

Data tables

• MARA - Material Master - General Data
• MARC - Material Master - Plant Data
• MBEW - Material Valuation
• CDHDR
• CDPOS
• MAKT - Material Master - Descriptions
• MARD - Material Master - Storage Location
• MARM - Material Units of Measure
• MVKE - Material Sales Data
• USR02
• DD02T - Table/Structure Texts
• DD03M - Table Field Texts
• T006 - Units of Measure

Material Requirements Planning (MRP)

Material planning, demand forecasting

Activities

• Create Order - Production order created
• Check Materials - Material availability checked
• Reserve Materials - Materials reserved
• Release Order - Order released to production
• Issue Materials - Materials issued to floor
• Start Production - Production started
• In-Process Check - In-process quality check
• Complete Operations - Production operations completed
• Final Inspection - Final quality inspection
• Report Production - Production reported
• Receive to Inventory - Goods received to inventory
• Close Order - Production order closed
• Generate Demand Forecast - Demand forecast generated from historical data using forecasting algorithms (moving average, exponential smoothing)
• Update Demand Forecast - Demand forecast manually adjusted or updated by planner based on market intelligence or special events
• Enter Special Demand - Special/ad-hoc demand quantity entered with reason code for items without or supplementing master plans
• Copy Sales Budget to Forecast - Sales budget data copied to demand forecast or extra demand fields in item master plan
• Initialize Scenario - Planning scenario initialized with plan period definitions, master plan settings, and default parameters
• Generate Master Plan - Master planning simulation run for range of items, computing production plan, purchase plan, and inventory plan by period
• Update Item Master Plan - Item master plan manually maintained or regenerated with updated demand forecast and supply plans
• Convert Master Plan to Planned Orders - Production plan and/or purchase plan from master plan converted into planned orders
• Roll Scenario - Scenario rolled forward to new plan period, updating horizon dates and regenerating expired period data
• Generate Order Planning - Order planning run executed to generate planned production, purchase, distribution, and schedule orders based on net requirements
• Generate Order Planning (Net Change) - Incremental net-change order planning run processing only items with plan-affecting changes since last full run
• Generate Order Planning (Item) - Single-item or narrow-range order planning run for targeted replanning of specific plan items
• Generate Pegging Relations - Demand-supply pegging relationships generated showing which supply orders cover which demand orders across planning levels
• Create Planned Order - New planned order created (production, purchase, or distribution) from the order planning run
• Firm Planned Order - Planned order status changed to Firm Planned, freezing its position in the plan against automatic replanning changes
• Confirm Planned Order - Planned order confirmed, locking it so subsequent planning runs do not move or remove it
• Change Planned Order Quantity - Planned order quantity manually modified by planner based on capacity constraints or business decisions
• Change Planned Order Date - Planned order start or finish date manually rescheduled by planner
• Cancel Planned Order - Planned order deleted or cancelled by planner or auto-processed exception message
• Reschedule Planned Order In - Planned order rescheduled to an earlier date based on exception message recommendation
• Reschedule Planned Order Out - Planned order rescheduled to a later date based on exception message recommendation
• Generate Exception Messages - Exception messages generated during planning run for inventory signals, order anomalies, capacity issues, and pegging conflicts
• Review Exception Message - Planner reviews and evaluates exception message for a specific item/order
• Auto-Process Exception Message - Exception message automatically processed (Cancel, Reschedule In, Reschedule Out) based on planner configuration
• Resolve Exception Message - Planner takes corrective action and marks exception message as processed/resolved
• Review Capacity Utilization - Planner reviews capacity use by planned order or resource to identify overloads/underloads
• Review Resource Master Plan - Resource master plan reviewed showing critical capacity requirements vs available capacity by period
• Adjust Capacity Plan - Capacity plan adjusted by modifying planned order quantities, dates, or routing to resolve capacity conflicts
• Select Orders for Transfer - Planned orders selected for transfer from Enterprise Planning to execution-level modules
• Transfer Planned Production Order - Planned production order transferred to Shop Floor Control (SFC) as an actual production order
• Transfer Planned Purchase Order - Planned purchase order transferred to Purchase Control as an actual purchase order
• Transfer Planned Distribution Order - Planned distribution order transferred to Warehousing as a warehouse transfer or purchase order
• Transfer Production Plan - Production plan bulk-transferred to SFC, with LN converting plan quantities into planned production orders before transfer
• Transfer Purchase Plan - Purchase plan bulk-transferred to Purchase Control as actual purchase orders
• Check Available to Promise - ATP check performed for plan item showing uncommitted supply available for customer order promising
• Check Capable to Promise - CTP check performed considering component availability and capacity to determine if additional supply can be produced
• Check Channel ATP - Channel-specific ATP check performed for distribution channel demand allocation

Case attributes

• Order Type (Text) - Type of production order
• Plant (Text) - Production plant
• Priority (Text) - Production priority
• Quantity (Number) - Quantity to produce
• Status (Text) - Order status
• Work Center (Text) - Production work center
• Batch Number (Text) - Production batch
• Material Description (Text) - Product description
• Material Number (Text) - Product being produced
• Production Order (Text) - Unique order identifier
• Planned End (Date) - Planned completion date
• Planned Start (Date) - Planned start date

Data tables

• MARC - Material Master - Plant Data
• MDKP - MRP Document Header
• MDTB - MRP Table (Planning Results)
• MARD - Material Master - Storage Location
• MDTC - MRP Table Cluster

Order-to-Cash (O2C)

Full sales cycle from quote through payment receipt

Activities

• Execute Transaction - Main transaction processing
• Post to System - Record posted to system
• Complete Review - Final review performed
• Close Process - Process marked complete
• Stage 0 - Order Entered - Order initially entered into SX.e with stagecd=0 before processing
• Create Quotation - Sales quotation is created as an initial offer to the customer
• Print Quotation - Sales quotation document is printed and sent to the customer for review
• Record Quotation Response - Customer's response to the quotation is recorded (Won/Lost/Canceled)
• Convert Quotation to Order - Accepted quotation lines are copied to create a new sales order
• Copy Quotation to Order - Accepted quotation is copied to create a customer order using OIS106
• Copy Order to New Order - Existing order copied to create a new order using OEET copy function
• Create Counter Sale - Counter sale (CS) order created for walk-in customer at point of sale
• Create Direct Order - Direct order (DO) created for drop-ship from vendor to customer
• Create Sales Order - Sales order header is created to capture customer demand
• Create Sales Order Item - Individual line item is added to the sales order
• Enter Order via EDI/Batch - Customer order entered automatically via EDI, e-business, or batch entry (OIS276/OIS278)
• Set Order to Preliminary - Customer order is set to status 10 (Preliminary) requiring approval before further processing
• Approve Sales Order - Sales order is approved as a mandatory step in the order procedure
• Modify Sales Order - Approved sales order is modified requiring re-approval
• Print Order Acknowledgement - Sales order acknowledgement is printed and sent to customer as confirmation
• Create Purchase Order - Purchase order is created for third-party or drop-ship scenarios
• Process Credit Hold Check - System runs automatic credit hold check evaluating customer credit limit against order amount
• Release E Hold - Order released from E (EDI/electronic) hold after credit check verification
• Assign Warehouse - Warehouse assignment determined for order fulfillment from available stock locations
• Block Sales Order - Sales order or line is blocked due to credit check, margin, EDI, or other reason
• Firm Release Block - Blocked order is firm-released so it is not blocked again for the same reason
• Soft Release Block - Blocked order is soft-released and may be blocked again at the next phase
• Reject Order Line - Order line is rejected due to credit/availability/ATP failure, setting status 22 or 99
• Auto-Close Backorder - Automatic closing/backorder prevention sets order line to status 29 or 99 based on ATP check
• Release for Allocation - Order is released for inventory allocation via MWS410 dispatch toolbox
• Allocate Inventory - Inventory is allocated to the customer order line, setting status to 33/44
• Release to Warehousing - Sales order is released to the warehouse module creating a warehousing order
• Send to TWL - Order transmitted from SX.e to Total Warehouse Logistics via wlet/wleh communication files
• Create Outbound Order - Outbound warehousing order is created from the sales order for picking
• Release for Picking - Allocated delivery is released for picking in MWS410, setting RIP flag
• Generate Pick Advice - Picking advice is generated for warehouse operators
• Print Pick Ticket - Pick ticket document printed from oeeh/oeel for warehouse operators
• Print Picking List - Picking list is printed for warehouse operators, setting order status to 44/50
• Create Picking - Warehouse picking task is initiated for the delivery
• Picking Created - Picking document has been generated and is ready for execution
• Confirm Picking - Warehouse confirms picked quantities, updating MITALO with actual picked amounts
• Report Pick Deviation - Pick deviation reported via MHS850MI when picked quantity differs from allocated
• Pack Delivery - Items are packed into shipping containers/packages in MWS420/MWS423
• Create Delivery - Outbound delivery document is created for the shipment
• Print Delivery Documents - Delivery documents (packing slip, bill of lading) are printed via MWS410/DRS100
• Print Delivery Note - Delivery note document printed from oeeh/oeel for customer
• Print Bill of Lading - Bill of lading shipping document printed from oeeh/oeel
• Issue Goods from Warehouse - Goods are issued from warehouse inventory, reducing stock balance in MITBAL
• Create Shipment - Shipment document is created to plan the transport
• Record Goods Issue - Goods issue is posted, reducing inventory and triggering revenue recognition
• Cancel Goods Issue - Previously posted goods issue is reversed
• Receive from TWL - Shipping/picking confirmation received back from TWL into SX.e via wlet/wlel
• Confirm Shipment - Shipment is confirmed in the warehouse, recording actual delivery
• Confirm Delivery Receipt - Delivery receipt is confirmed by the recipient, completing delivery tracking
• Set Initial Billing Block - Initial billing block is set when order is created
• Set Billing Block - Billing block is applied to prevent premature invoicing
• Change Billing Block - Billing block reason is modified on the sales document
• Remove Billing Block - Billing block is removed to allow billing document creation
• Set Initial Credit Block - Initial credit block is applied during order creation based on credit check
• Set Initial Delivery Block - Initial delivery block is set when the order is created
• Set Delivery Block - Delivery block is applied to prevent goods issue
• Remove Delivery Block - Delivery block is removed to allow shipment processing
• Set Credit Hold - Order is placed on credit hold due to credit limit breach
• Pass Credit - Order passes the credit check and is released for processing
• Remove Credit Hold - Credit hold is removed after credit review or limit increase
• Release Credit Hold - Credit department explicitly releases the credit hold on the order
• Set Reason for Rejection - Rejection reason is set on the sales order item
• Change Reason for Rejection - Rejection reason on the sales order item is modified
• Change Price - Pricing conditions on the sales document are modified
• Change Material - Material number on the sales order header is changed
• Change Material (Item Level) - Material number on a specific sales order item is changed
• Change Sales Order Quantity - Order quantity on the sales document is modified
• Change Delivery Amount - Delivery quantity is adjusted on the sales order
• Change Delivery Date (Header) - Requested delivery date at the header level is changed
• Change Delivery Date (Item) - Requested delivery date at the item level is changed
• Release to Invoicing - Sales order data is released from Sales to the Invoicing module
• Approve Delivery for Invoicing - Delivered order is approved for invoicing when CO type requires delivery approval
• Create Advance Invoice - Advance invoice is created before delivery, recorded in OOPINV
• Create Billing Request - Billing request is created to initiate the invoice composition process
• Compose Invoice - Invoice is composed from billable lines creating a draft invoice document
• Print Invoice - Composed invoice is printed
• Run Invoice Processing (OEEPI) - Sales Entry Invoice Processing Report executed to batch-invoice shipped orders
• Post Invoice - Invoice amounts are posted to Financials creating AR open entries
• Transfer Invoice to GL - Invoice accounting entries (OINACC) are transferred to General Ledger (FGLEDG) and AR (FSLEDG)
• Post to GL from AR - AR invoice amounts posted to General Ledger accounts via glet/gleb
• Create Corrective Invoice - Corrective invoice (credit note/debit note) is created via OIS380, updating OINREF
• Create Billing Document - Billing document (invoice) is created from the delivery
• Material Availability Date passed - The material availability date has passed without fulfillment
• Post Cash Receipt (ARECE) - Customer cash receipt posted in ARECE function recording payment against customer account
• Receive Customer Payment - Customer payment is received and recorded in the AR ledger (FSLEDG TRCD=20)
• Apply Unapplied Cash - Previously unapplied cash (UC transaction) applied to specific outstanding invoices
• Apply Payment to Invoice - Payment is matched and applied to specific invoices, updating OINVOH outstanding amount
• Process Partial Payment - Partial payment is applied, updating payment document status to 25 in ODHEAD
• Clear Invoice - Customer payment is applied and the invoice is cleared
• Clear Credit Memo - Credit memo is cleared against the customer account
• Create Return Merchandise - Return merchandise (RM) order created for customer product returns
• Issue Credit Memo - Credit memo is issued to the customer for returns or adjustments
• Send Order Confirmation - Order confirmation document is sent to the customer
• Process Delivered Order - Completed sales order is processed and transferred to history
• Transfer Order to History - Customer order with status 90/95 is filed and moved to history tables via OIS701
• Archive Sales Order - Sales order data is archived and removed from active tables

Case attributes

• Company Code (Text) - Company or entity code
• Cost Center (Text) - Cost center responsible
• Document Type (Text) - Type of financial document
• GL Account (Text) - General ledger account
• Status (Text) - Current status
• Amount (Currency) - Monetary value
• Currency (Text) - Transaction currency
• Created By (Text) - User who created the record
• Document Number (Text) - Unique identifier for the document
• Vendor/Customer (Text) - Business partner ID
• Document Date (Date) - Date of the document
• Due Date (Date) - Payment or completion due date

Process-mining benefits (historical)

• Where credit holds quietly stretch your cycle [Cash]: See how often orders drop onto a credit hold and how many days they sit there before release. Mining the block-and-release events across every order turns 'credit is slow sometimes' into a measured number of days and dollars added to your order-to-cash cycle.
• Delivery and billing blocks as hidden bottlenecks [Efficiency]: Rank your delivery-block and billing-block reasons by how many days each one costs. You find which block reasons are routine and harmless versus the few that repeatedly stall high-value orders.
• Manual rework loops on price, quantity and dates [Efficiency]: Surface orders that are changed again and again after entry - repeated price changes, quantity edits, and delivery-date pushes on the same order. Each change is touch time and a chance for error; the pattern points straight at pricing gaps and unreliable promise dates.
• Order rejections and the reasons behind them [Service]: Concentrate rejected lines by reason code to see where revenue leaks before it is ever shipped, and which customers or materials drive the rejections.
• Promise date versus what you actually shipped [Service]: Compare the date you confirmed to the customer against the date goods actually left the dock, order by order, and trace the late ones back to the step that caused the slip.
• How many orders actually follow the standard flow [Efficiency]: Measure what share of orders run the clean path - order, delivery, goods issue, invoice, cash - versus the variants that loop back or skip steps. The 'touchless' rate is your baseline for automation and the variants are your improvement backlog.

Process-mining benefits (action)

• Break high-value credit holds before they age [Cash]: Every day, flag the largest orders that have just landed on a credit hold and route them to the credit team, so a five-figure order does not sit blocked for a week because nobody was watching.
• A daily worklist of orders stuck on a block [Efficiency]: Produce a live list of orders sitting on a delivery or billing block longer than your threshold, sorted by value and promised date, so the team clears the costly ones first instead of oldest-first.
• Catch shipments that are billed late or not at all [Cash]: Spot deliveries that have been goods-issued but not yet billed and push them into the billing run the same day - protecting DSO by turning shipped goods into invoices without delay.
• Watch at-risk deliveries against the promise date [Service]: Trigger a notification when an open order's confirmed ship date starts slipping past what the customer was promised, so you can act before the customer calls.
• A guardrail on repeated order changes [Cost]: Alert when a single order accumulates repeated price, quantity or date changes - an early signal of a pricing error, a difficult customer, or maverick discounting that deserves a second look.
• Prioritise overdue invoices for collection [Cash]: Feed invoices past their due date straight into a prioritised collections worklist so cash chasing is aimed at the biggest, oldest balances first.

Data tables

• LIKP - Delivery Header
• LIPS - Delivery Item
• MKPF - Material Document Header
• MSEG - Material Document Segment
• VBAK - Sales Order Header
• VBAP - Sales Order Item
• VBFA - Sales Document Flow
• VBRK - Billing Document Header
• VBRP - Billing Document Item
• VBUK - Sales Document Header Status
• VBUP - Sales Document Item Status
• CDHDR
• CDPOS
• KONV - Pricing Conditions (ECC)
• NAST - Message Status
• PRCD_ELEMENTS - Pricing Conditions (S/4HANA)
• SWWWIHEAD - Workflow Work Item Header
• USR02
• VBEP - Sales Order Schedule Line
• VBKD - Sales Document Business Data
• T006 - Units of Measure
• T156 - Movement Types
• TCURF - Conversion Factors
• TCURR - Exchange Rates
• TCURX - Currency Decimals

Procure-to-Pay (P2P)

Full procurement cycle from requisition through invoice payment

Activities

• Create Planned Purchase Order - MRP or manual planning creates a planned purchase order proposal in MPOPLP. Triggers the procurement process from demand planning.
• Release Planned Purchase Order - Planned purchase order is released from MPOPLP, creating a real PO header in MPHEAD and lines in MPLINE. Status advances to 15.
• Create Purchase Order via Batch Entry - Purchase order is created via batch entry (PPS376/APS450MI) through staging tables MXHEAD/MXLINE before transfer to MPHEAD/MPLINE.
• Transfer Batch PO to Production - Batch purchase order is transferred from staging tables (MXHEAD/MXLINE) to production tables (MPHEAD/MPLINE). Validates data and creates real PO.
• Create Purchase Agreement - Purchase agreement is created with supplier via PPS100. Defines blanket, schedule, or volume-based terms in MPAGRT/MPAGRL.
• Release Against Purchase Agreement - Purchase order is created as a release/call-off against an existing purchase agreement. Links PO line to MPAGRL agreement line.
• Create Purchase Quotation Request - Request for purchase quotation is created via PPS130/PPS133. Sent to one or more suppliers for competitive bidding.
• Create Requisition - Supply requisition is created
• Evaluate Purchase Quotations - Received purchase quotations are compared and evaluated to select the best supplier offer. Analysis via PPS580.
• Approve Requisition - Supply requisition is approved
• Confirm Delivery Date - Supplier confirms delivery date for PO line. Status advances to 31 (delivery date confirmed). Recorded in MPLIND.
• Confirm Purchase Price - Supplier confirms purchase price for PO line. Status advances to 32 (price confirmed). Recorded in MPLIND.
• Confirm Price and Delivery Date - Supplier confirms both price and delivery date. Status advances to 33 (confirmed but not approved) or 35 (confirmed and approved). Recorded in MPLIND.
• Report Shipment Advice - Supplier reports shipment advice / advance shipping notice. PO line status advances to 40 (shipment advised). Recorded in MPLIND.
• Report Transport Notification - Transport notification received for incoming shipment. PO line status advances to 45 (transport notified). Recorded in MPLIND.
• Create Item Lot for Receipt - Item lot is created during goods receipt via PPS315 for lot-controlled items. Assigns lot number to received quantity.
• Create Purchase Order - Purchase order is created from requisition
• Inspect Quality of Received Goods - Quality inspection is performed on received goods via PPS310. Status may advance to 60 (partial QI), 65 (QI complete), or 64/69 (rejected).
• Reject Goods at Quality Inspection - Received goods are rejected during quality inspection. Status advances to 64 (no action determined) or 69 (action determined). May trigger claim.
• Put Away Received Goods - Received goods are put away to final storage location via PPS320. Status advances to 70 (partial) or 75 (complete). MITLOC balance updated.
• Create Purchase Order Claim - Purchase order claim is created via PPS820 for quality issues, short delivery, or damage. Creates MPCLAH header and MPCLAL lines.
• Resolve Purchase Order Claim - Purchase order claim is resolved - goods returned to supplier, credit note issued, or replacement ordered. MPCLAL claim resolution updated.
• Select Invoice for Matching - Supplier invoice is selected for matching against PO and/or goods receipt via APS350. Prepares invoice lines for 2-way or 3-way matching.
• Send Purchase Order to Vendor - PO is transmitted to vendor
• Match Invoice to Goods Receipt Line - Invoice line is matched to goods receipt line via APS360. Verifies quantities and prices. Updates CFIN matching status on MPLINE.
• Reconcile Received Not Invoiced - Reconciliation of received-but-not-invoiced items via APS370. Identifies discrepancies between goods receipts and invoices.
• Authorize Supplier Invoice - Supplier invoice is authorized/approved by authorized user via APS115. Updates approval status in FPLLOG and FPAPCD.
• Recode Supplier Invoice - Supplier invoice accounting entries are recoded to correct accounts or cost centers via APS110/APS112.
• Reject Supplier Invoice - Supplier invoice is rejected during batch processing or authorization. Recorded in FAPIBR reject history.
• Create Payment Proposal - Automatic payment proposal is created for approved supplier invoices via APS130. Selects invoices based on due date and payment terms.
• Receive Supplies - Supplies are received from vendor
• Verify Payment Proposal - Payment proposal is verified and reviewed before execution via APS130. May be adjusted to include/exclude specific invoices.
• Approve Payment Proposal - Payment proposal is approved for execution. Required when APS905 parameter for payment proposal approval is activated.
• Execute Supplier Payment - Payment is executed against the approved payment proposal. Creates payment transaction (TRCD 50) in FPLEDG and updates FGLEDG.
• Inspect Received Items - Received items are inspected for quality
• Confirm Payment via Bank Statement - Bank statement confirms payment execution via ABS100/APS188. Matches FABLIN bank lines to FPLEDG payment records.
• Update Purchase Statistics - Purchase statistics (MPURST) and vendor statistics (MVENST) are updated when PO reaches status 85. Used for supplier performance evaluation.
• Archive Purchase Order - Fully processed purchase order is archived via PPS920. Moves MPHEAD, MPLINE, MPLIND records to archive tables. PO status set to 99.
• Put Away Supplies - Supplies are put away in storage location
• Issue Supplies to Department - Supplies are issued to requesting department
• Record Patient Charge - Supply usage is charged to patient
• Perform Cycle Count - Inventory cycle count is performed
• Adjust Inventory - Inventory adjustment is made
• Create Purchase Requisition Item - Purchase requisition line item is created to request procurement of material or service
• Process Return to Vendor - Items are returned to vendor
• Receive Vendor Invoice - Vendor invoice is received
• Match Invoice to PO - Invoice is matched to purchase order and receipt
• Process Vendor Payment - Payment is processed to vendor
• Release Purchase Requisition - Purchase requisition is approved and released for conversion to purchase order
• Refuse Purchase Requisition - Purchase requisition is rejected and sent back to the requestor
• Create Purchase Contract - Long-term purchase contract/blanket agreement is created with a supplier for agreed items and prices
• Create Contract - Outline agreement (contract) is created with the vendor for long-term procurement
• Create Request for Quotation - Request for quotation (RFQ) is created and linked to item requirements for bidding
• Send Request for Quotation - RFQ is transmitted to selected bidders/suppliers for price and terms quotation
• Record RFQ Response - Vendor response/bid to RFQ is received and recorded with offered price and delivery terms
• Evaluate RFQ Responses - Received RFQ bids are compared and evaluated to select the best supplier offer
• Accept RFQ Response - Best vendor bid is accepted and marked for conversion to purchase order or contract
• Convert RFQ to Purchase Order - Accepted RFQ response is converted into a purchase order for the selected supplier
• Convert Requisition to Purchase Order - Approved purchase requisition is converted directly to a purchase order
• Create Purchase Order Item - Purchase order line item is created to procure material or service from vendor
• Release Against Contract - Purchase order is created as a release/call-off against an existing purchase contract
• Create Purchase Schedule - Purchase schedule (blanket delivery schedule) is created for repetitive item deliveries from a supplier
• Generate Schedule Release - Schedule release is generated for a purchase schedule to trigger delivery of specific quantities
• Release Purchase Order - Purchase order is approved and released for transmission to vendor
• Print Purchase Order - Purchase order document is printed for transmission to the supplier via mail or EDI
• Release Purchase Order to Warehousing - Approved purchase order is released to the warehousing module to create inbound warehouse orders for receipt
• Block Purchase Order - Purchase order is blocked to prevent further processing until the block is released
• Unblock Purchase Order - Block on purchase order is removed to allow processing to continue
• Send Purchase Order - Purchase order is transmitted to the vendor via output (print, EDI, email)
• Send Purchase Order Update - Updated purchase order is re-sent to the vendor after changes
• Receive Order Confirmation - Vendor order confirmation is received and recorded against the PO
• Record Goods Receipt - Goods receipt is posted for materials received against the purchase order
• Confirm Receipt in Procurement - Goods receipt recorded in warehousing is confirmed back to the procurement module with final quantities
• Begin Quality Inspection - Quality inspection lot is created and inspection process begins
• Quality: Accepted - Quality inspection result is accepted and stock is released
• Quality: Not Evaluated - Quality inspection usage decision recorded but not evaluated (neither accepted nor rejected). Source: QAVE where VBEWERTUNG is not A or R.
• Record Service Entry Sheet - Service entry sheet is created to confirm services rendered by vendor
• Vendor Creates Invoice - Vendor submits an invoice for goods or services delivered
• Match Invoice to Purchase Order - Purchase invoice is matched to purchase order lines during two-way or three-way matching process
• Match Invoice to Goods Receipt - Purchase invoice is matched to warehouse receipt lines during three-way matching verification
• Generate Self-Billing Invoice - Self-billed purchase invoice is automatically generated from confirmed goods receipts
• Record Invoice Receipt - Vendor invoice is entered and posted in the SAP system
• Approve Invoice for Payment - Matched purchase invoice passes authorization checks and is approved for payment processing
• Change Payment Terms - Payment terms on the purchase order or invoice are modified
• Remove Payment Block - Payment block is removed to allow invoice payment processing
• Set Payment Block - Payment block is applied to hold invoice payment pending review
• Send Message - Generic output message sent for the purchasing document (not NEU, MAHN, or AUFB). Source: NAST with KAPPL=EF, KSCHL not in standard types. Activity name dynamically appended with T685T.VTEXT.
• Refuse Purchase Order - Purchase order is rejected during the approval workflow
• Reactivate Purchase Order Item - Previously blocked or deleted PO item is reactivated for processing
• Delete Purchase Order Item - Purchase order line item is flagged for deletion
• Update Order Confirmation - Existing vendor order confirmation is updated with new dates or quantities
• Dun Order Confirmation - Dunning notice is sent to vendor requesting overdue order confirmation
• Receive Advanced Shipment Notice (ASN) - Advanced shipment notice is received from vendor with shipment details
• Quality: Rejected - Quality inspection result is rejected and stock is blocked or returned
• Select Invoice for Payment - Due purchase invoice is selected for inclusion in a payment batch in Cash Management
• Process Payment Batch - Payment batch is processed and anticipated payment documents are generated for selected invoices
• Clear Invoice - Invoice is cleared through payment execution or other settlement
• Process Delivered Purchase Order - Delivered purchase order with all receipts and invoices complete is processed and transferred to history
• Calculate Vendor Rating - Vendor rating scores are calculated based on delivery, quality, and price performance criteria
• Send Overdue Notice - Overdue notice is sent to vendor for late delivery or missing confirmation
• Change Price - Net price on the purchase order item is modified
• Change Quantity - Order quantity on the purchase order item is changed
• Change Material Number - Material number on the purchase order item is replaced
• Change Material Group - Material group classification on the PO item is modified
• Change Vendor - Vendor assignment on the purchase order is changed
• Change Storage Location - Storage location for goods receipt is modified on the PO item
• Set Requested Delivery Date - Initial requested delivery date is set on a PO schedule line. Source: CDHDR/CDPOS with TABNAME=EKET, FNAME=EINDT, VALUE_OLD IS NULL.
• Change Requested Delivery Date - Requested delivery date on the purchase order is updated
• Set Confirmed Delivery Date - Initial confirmed delivery date is set by vendor. Source: CDHDR/CDPOS with TABNAME=EKES, FNAME=EINDT, VALUE_OLD IS NULL.
• Change Confirmed Delivery Date - Vendor-confirmed delivery date on the PO is updated
• Change Contract - Reference contract on the purchase order item is changed
• Change Currency - Document currency on the purchase order is modified
• Change Plant - Receiving plant on the purchase order item is changed
• Change Short Text Description - Short text description on the purchase order item is modified
• Change Approval for Purchase Order - Approval status or approver on the purchase order is changed
• Change Deletion Flag for Purchase Order Item - Deletion indicator on the purchase order item is toggled
• Change Delivery Indicator - Delivery completed indicator on the PO item is modified
• Change Final Invoice Indicator - Final invoice indicator on the purchase order item is changed
• Change Outward Delivery Indicator - Outward delivery (returns) indicator on the PO item is modified
• Change Rejection Indicator - Rejection indicator on the purchase order item is toggled
• Increase Contract Target Quantity - Target quantity on the outline agreement item is increased
• Decrease Contract Target Quantity - Target quantity on the outline agreement item is decreased
• Increase Contract Target Value - Target value on the outline agreement item is increased
• Decrease Contract Target Value - Target value on the outline agreement item is decreased
• Increase Contract Net Price - Net price on the outline agreement item is increased
• Decrease Contract Net Price - Net price on the outline agreement item is decreased
• Increase Effective Contract Item Value - Effective value of the contract item is increased after release orders
• Decrease Effective Contract Item Value - Effective value of the contract item is decreased after adjustments
• Block Purchase Order Item - Purchase order item is blocked to prevent further processing
• Cancel Goods Receipt - Previously posted goods receipt is reversed
• Cancel Service Entry Sheet - Previously accepted service entry sheet is cancelled
• Cancel Invoice Receipt - Previously posted vendor invoice is reversed

Case attributes

• Company Code (Text) - Company or entity code
• Cost Center (Text) - Cost center responsible
• Document Type (Text) - Type of financial document
• GL Account (Text) - General ledger account
• Status (Text) - Current status
• Amount (Currency) - Monetary value
• Currency (Text) - Transaction currency
• Created By (Text) - User who created the record
• Document Number (Text) - Unique identifier for the document
• Vendor/Customer (Text) - Business partner ID
• Document Date (Date) - Date of the document
• Due Date (Date) - Payment or completion due date

Process-mining benefits (historical)

• Off-contract and maverick buying [Cost]: Find purchase orders raised with no requisition in front of them or against no contract at all. Quantified across a year of history, this is the spend that escaped your negotiated pricing - usually a bigger number than anyone expects.
• Manual PO changes that delay and add risk [Efficiency]: Surface POs that are edited repeatedly after release - price, quantity, vendor, delivery date and payment-term changes on the same order. Each one adds cycle time and audit exposure.
• Three-way match failures [Efficiency]: Measure how often supplier invoices fail to line up with the PO and the goods receipt, and which vendors and buyers drive the exceptions that your AP team has to work by hand.
• The GR/IR reconciliation backlog [Compliance]: Expose goods received but not yet invoiced (and the reverse) sitting in the GR/IR clearing account, and how long items age there - a recurring month-end clean-up that mining makes visible year-round.
• Payment blocks and discounts left on the table [Cost]: See how long invoices sit on a payment block and how many early-payment discounts were lost by paying late - straight, recoverable money.
• Supplier delivery performance, from your own data [Service]: Compare each vendor's confirmed delivery date and shipping notice against the actual goods receipt to rank suppliers on reliability using the record you already hold - no vendor scorecard survey required.

Process-mining benefits (action)

• Stop maverick spend at the point of order [Cost]: Flag new POs that have no requisition or no contract behind them for review before they are sent, so off-contract spend is caught while it can still be redirected.
• A daily worklist of invoices blocked on match [Efficiency]: List invoices held on a three-way-match exception, sorted by value and by the discount about to expire, so AP clears the ones that matter today.
• Capture early-payment discounts before the cutoff [Cost]: Flag approved invoices whose discount window is about to close but that are still unpaid, so finance can pull them into the next payment run and keep the discount.
• Release aging payment blocks [Cash]: Produce a daily list of payments held on a block past your threshold, so nothing quietly ages into a late payment or a strained supplier relationship.
• Duplicate-invoice and duplicate-payment watch [Compliance]: Screen incoming invoices for likely duplicates - same vendor, amount and reference - and flag them before the payment run, not after the money has gone out.
• Chase suppliers before they make you late [Service]: Trigger a follow-up when a PO passes its confirmed delivery date with no goods receipt yet, so vendors are chased proactively instead of being discovered short at receiving.

Data tables

• BKPF - Accounting Document Header
• BSEG - Accounting Document Line Item
• BSIK - Vendor Open Items
• EBAN - Purchase Requisition
• EKBE - Purchase Order History
• EKKO - Purchase Order Header
• EKPO - Purchase Order Item
• LFA1 - Vendor Master - General Data
• LFB1 - Vendor Master - Company Code Data
• MARA - Material Master - General Data
• MARC - Material Master - Plant Data
• MKPF - Material Document Header
• MSEG - Material Document Segment
• QALS - Inspection Lot Record
• QAVE - Inspection Usage Decision
• RBKP - Invoice Document Header
• RSEG - Invoice Document Item
• T001W - Plants
• BSAK - Vendor Cleared Items
• CDHDR
• CDPOS
• EINA - Purchasing Info Record - General
• EINE - Purchasing Info Record - Purch Org
• EKES - Vendor Confirmations
• EKET - Schedule Lines
• ESLL - Lines of Service Package
• ESSR - Service Entry Sheet
• LFM1 - Vendor Master - Purchasing Organization
• MAKT - Material Master - Descriptions
• NAST - Message Status
• REGUH - Settlement Data from Payment Program
• REGUP - Payment Advice Items
• SWWWIHEAD - Workflow Work Item Header
• T001
• USR02
• T001L - Storage Locations
• T006 - Units of Measure
• T023T - Material Group Descriptions
• T024 - Purchasing Groups
• T024E - Purchasing Organizations
• T052 - Payment Terms Configuration
• T156 - Movement Types
• T161 - Purchasing Document Types
• T161G - Reasons for Rejection
• T163 - Item Categories in Purchasing Document
• T163I - Account Assignment Category Texts
• T163K - Account Assignment Categories in Purchasing
• T163Y - Item Category Texts
• T685T - Conditions: Texts for Output Types
• TBSLT - Posting Key Texts
• TCURF - Conversion Factors
• TCURR - Exchange Rates
• TCURX - Currency Decimals

Payroll (PAYROLL)

Pay processing, deductions, tax withholding

Activities

• Set Up Employee Payroll Record - Employee payroll master record created in EMPLOYEE table via HR11.1 with pay rate, frequency, salary class, and department assignment
• Assign Pay Frequency - Pay frequency set for employee (Weekly, Biweekly, Semimonthly, Monthly) determining payroll cycle eligibility
• Configure Direct Deposit - Employee ACH account set up in EMACHDEPST via PR33.1 with bank ID, account number, deposit amount/percentage
• Assign Employee Deductions - Employee deductions configured in EMDEDMASTR via PR35.1 with codes, amounts, effective dates, and priorities
• Set Up Garnishment - Court-ordered garnishment created in PREMPGARN via PR36.1 with case number, exempt wages parameters, and arrears tracking
• Configure Distribution Override - GL distribution override set in EMDISTMAST via PR23.1 for splitting wages across multiple accounts/departments
• Assign Tax Withholding - Employee state tax setup in PREMPSTATE with work state, disability plan, and geographic area codes
• Create Standard Time Record - Standard/recurring time record template created in STANDTIME for automatic time generation by PR134
• Generate Automatic Time Records - PR134 generates time records in TIMERECORD from STANDTIME templates for salaried/fixed-schedule employees
• Enter Time Record Manually - Time record entered directly in TIMERECORD via PR30.1 or Excel import with pay code, hours, rate
• Submit Web Time Entry - Employee enters time via Self-Service portal creating PRPENDTIME pending records with hours and pay codes
• Approve Web Time Entry - Manager approves pending time records in PRPENDTIME, updating status and manager ID
• Release Time Records to Payroll - Approved pending time records released from PRPENDTIME to TIMERECORD for payroll processing
• Create Time Record Batch - Time records grouped into batch in PRBATCH with control totals for reconciliation
• Enter One-Time Deduction - One-time deduction override created in ONETMDED via PR39.1 for single pay period processing
• Open Payroll Cycle - Payroll cycle status initialized in PR00.1 marking cycle as open for processing
• Calculate FLSA Overtime - PR132 calculates Fair Labor Standards Act overtime for eligible employees
• Run Earnings and Deductions Calculation - PR140 calculates gross wages, all deductions (tax, benefit, garnishment), and net pay for all employees with current time records
• Create Payment Master Record - PR140 creates PAYMASTR record linking all time cards with like check groups into a single payment
• Calculate Tax Withholdings - PR140 calculates federal, state, local tax withholdings based on DEDCODE tax authority settings and BSI tax tables
• Calculate Benefit Deductions - PR140 processes benefit deductions from EMDEDMASTR including health, dental, retirement per DEDCODE rules
• Calculate Garnishment Deductions - PR140 processes garnishment deductions per PREMPGARN rules, calculating disposable income and exempt wages
• Generate Payroll Register - PR141 generates the payroll register report for review before payment printing
• Print Payments - PR160 creates PRCHECK records (system payments and direct deposits) from PAYMASTR records calculated by PR140
• Generate Direct Deposits - PR160 creates ACH payment records in PRCHECK for employees with EMACHDEPST direct deposit accounts
• Generate Payment Register - PR162 produces the payment register listing all checks and ACH transactions for the cycle
• Reserve Manual Payment Number - PR81.1 reserves check number in PRCHECK for manual payment or void processing
• Process Manual Payment - PR80.1 converts reserved payment to system payment and links to manual PAYMASTR record
• Void Payment - PR81.1 voids a payment in PRCHECK, creating void reversal record with status update
• Run Payroll Close - PR197 closes payroll cycle, creates labor distribution records in PRDISTRIB per GM10.2 templates, rolls data to QUARTWAGE
• Create Labor Distribution Records - PR197 generates PRDISTRIB records with GL account distributions for each employee payment
• Update Quarterly Wage History - PR199 rolls payment data from PAYDEDUCTN into QUARTWAGE for quarterly tax reporting and W-2 production
• Update Deduction History - PR199 rolls deduction data into PREMDEDHST and QUARTDED for monthly/quarterly tracking
• Update Garnishment History - PR199 creates PRGARNHIST records tracking disposable income and exempt wages for compliance reporting
• Delete Processed Time Records - PR199 deletes processed TIMERECORD entries and clears cycle indicators in PR00.1
• Update Payroll Hours - PR188 updates PRHOURS with accumulated hours for the cycle
• Post to General Ledger - PR198 creates GL and Activity (AC) transactions from PRDISTRIB records and relieves salary encumbrances
• Post Salary Encumbrance - GM110 processes salary encumbrance adjustments after payroll cycle completion
• Generate W-2 Forms - Year-end process produces W-2 forms from QUARTWAGE and QUARTDED quarterly history data
• Generate Quarterly Tax Reports - Quarterly reporting from QUARTWAGE and QUARTDED for 941, state unemployment, and other tax filings
• Close Payroll Year - Annual close process that finalizes yearly totals and prepares system for new payroll year

Case attributes

• Department (Text) - Employee department
• Job Title (Text) - Employee job title
• Location (Text) - Work location
• Request Type (Text) - Type of HR request
• Salary Grade (Text) - Salary grade level
• Status (Text) - Request status
• Employee ID (Text) - Unique employee identifier
• Employee Name (Text) - Full name of employee
• Manager (Text) - Direct manager
• Effective Date (Date) - When action takes effect
• Hire Date (Date) - Employee hire date
• Submission Date (Date) - Date request submitted

Data tables

• PA0008 - HR Master - Basic Pay (Infotype 0008)
• USR02

Project Management (PM)

Project definition, WBS elements, networks, costs

Activities

• Register Service Call - A customer call or internal request for maintenance is registered in the call management system with problem details
• Classify Call Problem - Support engineer assesses and classifies the expected problem and expected solution based on call details
• Assign Support Engineer - A support engineer is assigned to handle the service call and investigate the issue
• Resolve Call - The support engineer resolves the call directly without creating a service order or work order
• Transfer Call to Service Order - The call is transferred to a service order for field service execution
• Transfer Call to Work Order - The call is transferred to a work order for depot repair execution
• Generate Maintenance Plan - Planned maintenance activities are generated from maintenance scenarios for installation groups based on time/usage patterns
• Create Planned Activity - An individual planned activity is created for a serialized item within an installation group
• Transfer Planned Activity to Service Order - A planned preventive maintenance activity is transferred to a service order for execution
• Transfer Planned Activity to Work Order - A planned maintenance activity is transferred to a work order for depot execution
• Create Service Order - A new service order is created for field service maintenance with installation group, item, and customer data
• Set Service Order Status Free - The service order is in Free status allowing full modification of all order data
• Assign Service Engineer to Order - A service engineer is assigned to the service order activities for resource planning
• Plan Service Order - The service order is planned with start/finish dates, material allocation, and resource scheduling
• Release Service Order - The service order is released for execution with materials released from warehouse stock
• Start Service Order Execution - The service engineer begins work on the service order activities
• Register Service Order Hours - Hours spent on service order activities are registered for costing and invoicing
• Register Service Order Materials - Materials consumed during service order execution are registered
• Complete Service Order - All service activities are finished and the order is marked as completed
• Cost Service Order - All costs and expenses are booked to the service order for auditing and invoice calculation
• Invoice Service Order - The service order invoice is generated and sent to the customer
• Close Service Order - The service order is fully processed including invoicing and can be closed
• Cancel Service Order - The service order is canceled with a reason code before completion
• Interrupt Service Order - The service order is temporarily interrupted due to parts unavailability or other reasons
• Block Service Order - The service order is blocked from further processing
• Create Work Order - A new work order is created for depot repair or internal maintenance with item and department data
• Set Work Order Status Free - The work order is in Free status allowing full modification
• Add Work Order Activity - A maintenance activity is added to the work order from reference activities or manual definition
• Add Work Order Material - Material resources are added to the work order specifying expected consumption
• Plan Work Order - The work order is planned with start/finish dates and capacity scheduling
• Release Work Order - The work order is released for execution allowing material issue and hours accounting
• Start Work Order Execution - Work begins on the work order with actual start time recorded
• Register Work Order Hours - Hours spent by maintenance personnel on work order activities are registered
• Issue Work Order Materials - Materials are physically issued from warehouse to the work order
• Process Work Order Subassembly - Disassembled components are processed as outgoing subassemblies
• Complete Work Order - All maintenance activities are finished and the work order is completed
• Close Work Order - Financial results are calculated and the work order is closed
• Cancel Work Order - The work order is canceled with a reason code
• Sign Off Work Order Activity - A work order activity is signed off by an engineer with required skills
• Create Maintenance Sales Order - A maintenance sales order is created for customer-facing depot repair with pricing and invoicing data
• Link MSO to Work Order - A work order is created from the maintenance sales order part line for execution
• Cost Maintenance Sales Order - Costs from work order execution are posted to the maintenance sales order
• Invoice Maintenance Sales Order - The maintenance sales order is invoiced to the customer
• Close Maintenance Sales Order - The maintenance sales order is fully processed and closed
• Check Warranty Coverage - The system checks whether the service order or work order is covered by warranty terms
• Apply Warranty to Order - Warranty coverage is applied to cost lines reducing customer charges
• Record Warranty Transaction - Actual costs incurred under warranty are recorded in warranty transactions
• Check Service Contract Coverage - The system checks whether the item/installation group has an active service contract
• Create Field Change Order - A field change order is raised for global replacement of defective items across installation groups
• Generate Field Change Order Lines - FCO lines are generated listing all affected serialized items requiring replacement
• Generate Orders from FCO - Service orders or work orders are generated from field change order lines for execution
• Create Serialized Item - A new serialized item is registered with unique serial number for lifecycle tracking
• Create Installation Group - A new installation group is defined grouping serialized items for maintenance management
• Add Installation to Group - A physical installation is added to an installation group linking a top-level serialized item
• Update Serialized Item Status - The status of a serialized item is updated in its physical breakdown structure
• Assign Maintenance Scenario - A preventive maintenance scenario is assigned to a serialized item for automated plan generation
• Record Measurement - A measurement reading is recorded for a serialized item used in usage-based maintenance scheduling

Data tables

• AFKO - Network Header
• AFVC - Network Activity
• PROJ - Project Definition
• PRPS - WBS Element
• JEST - Object Status

Production/Manufacturing (PROD)

Production orders, BOM, routing, shop floor execution

Activities

• Create Recipe/Formula (PDS001) - Recipe or formula product structure created in PDS001 with PCLT=11 (Formula BOM). Defines the base recipe for food production.
• Define Formula Output Items (PDS029) - Output items defined for a formula via PDS029 (Output Items. Open). Specifies actual manufactured items from the recipe.
• Define Recipe Ingredients (PDS002) - Materials/ingredients connected to a recipe via PDS002 (Product. Connect Materials/Operations). Includes quantities, waste, potency compensation references.
• Define Process Operations (PDS002) - Routing operations defined for a recipe in PDS002. Specifies production steps (mixing, heating, cooling, filling) with work centers, times, and auto-report settings.
• Scale Recipe/Batch Size - Recipe quantities scaled to match the manufacturing order quantity. Ingredient amounts recalculated based on batch scaling factors.
• Create Production Order - Production order is manually created or generated from Enterprise Planning (planned order transfer)
• Create Planned Manufacturing Order - Planned MO created by MRP/MPS or manually via PMS170 (Planned MO. Open). Status 10 (Preliminary) or 20 (Definite).
• Consolidate Planned Orders - Multiple planned MOs consolidated into a single order via PMS172 (Planned MO. Consolidate) based on MO Consolidation Method (MOCM).
• Firm Planned Manufacturing Order - Planned MO status changed from 10 (Preliminary) to 20 (Definite/Firm). Order will not be replanned by MRP.
• Set Default Production Order Data - Default data (routing, warehouse, backflush settings) applied from order series configuration
• Check Allergen Compliance - Allergen verification performed against product characteristics and ingredient allergen codes to ensure food safety compliance.
• Generate BOM Explosion - Bill of material is exploded to generate estimated material requirements for the production order
• Generate Routing Operations - Routing operations are generated from item routing master, defining the sequence of manufacturing steps
• Calculate Estimated Costs - Estimated end-item unit costs are calculated from BOM materials and routing operations
• Status: Created - Production order has been created in the system
• Plan Production Order (Forward) - Forward scheduling calculates operation start/end dates from order start date
• Work Center Schedule (PMS230) - Operations sequenced and scheduled on work centers via PMS230 (Work Center Schedule. Open). Load balanced against capacity.
• Plan Production Order (Backward) - Backward scheduling calculates operation start/end dates from delivery date
• Change Production Order Quantity - Order quantity is modified, triggering recalculation of estimated materials and hours
• Change Production Order Dates - Planned start or delivery date is modified, triggering operation replanning
• Create Production Order Item - A new production order item is created for a material
• Print Production Order Documents - Order documents (routing sheet, material list, covering note) are printed
• Print MO Documents (PMS240) - Manufacturing order documents (routing sheet, material list, covering note) printed via PMS240.
• Status: Documents Printed - Production order status changes to Documents Printed after order documents are generated
• Release Planned Manufacturing Order - Planned MO released to become a manufacturing order. Order category changes from 100 (Planned MO) to 101 (MO). Status becomes 30 (Released).
• Release Production Order - Production order is released to the shop floor via Release Production Orders session (tisfc0204m000), enabling material issue and hours posting
• Check Component Availability - Material availability check performed via PMS040 (Manufact Order. Check Comp Availability). Materials are allocated from MITALO.
• Create Inspection Orders - Quality management inspection orders are created for end products, materials, or operations at production order release
• Stage Manufacturing Order - MO staged after material availability confirmed. Status set to 40 (Staged). Manufacturing orders without material shortages receive this status.
• Initiate Inventory Issue - Warehouse order lines are unblocked to initiate material issue from warehouse to shop floor
• Status: Released - Production order is released for execution on the shop floor
• Clean-in-Place (CIP) Completed - Clean-in-place cycle completed on production equipment/line before next production run. Relevant for scheduling and food safety compliance.
• Report Material Issue (PMS060) - Material issued from warehouse to MO via PMS060 (Manufact Order. Report Issue). Creates stock transaction in MITTRA and updates MWOMAT.
• Record Potency/Concentration (PDS004) - Potency or concentration value recorded for an active substance material. Triggers quantity compensation for the ingredient based on actual potency vs. standard.
• Adjust for Potency Compensation - Material quantity adjusted based on actual potency/concentration versus standard. Rate compensators applied from MWORCO.
• Report Catch Weight (PMS060) - Actual catch weight recorded during material issue for variable-weight food items. Catch weight value stored in MWOMAT/MITTRA.
• Issue Material to Production - Material is issued from warehouse to shop floor for the production order
• Scheduled start time - Planned start date/time for the production order operation
• Backflush Material Issue - Materials automatically consumed via backflushing (SPMT=1) when operation is reported. Issue quantity calculated from manufactured quantity.
• Material Backflush - Materials are automatically consumed based on quantity completed (backflushing)
• Return Material from MO (PMS060) - Excess material returned from MO to warehouse via PMS060 sort option 8 (Return). Creates negative issue transaction.
• Start Operation - Production operation begins at the work center/machine
• Report Operation (PMS070) - Operation time and quantity reported via PMS070 (MO Operation. Report). Updates MWOOPE and creates transaction in MWOPTR.
• Post Production Hours - Labor and/or machine hours are registered against a production order operation via People module
• Auto-Report Operation - Operation automatically reported based on AURP=3 setting when manufactured quantity is reported on receipt (PMS050).
• Report Employee Time (PMS075) - Employee-level time reported against operation via PMS075 (WO Operation. Report Employee) when multiple employees work on same operation.
• Hours Backflush - Labor hours are automatically posted based on reported completion quantities
• Start Labor Time Registration (PMS426) - Shop floor start-time registration for an operation via PMS426 (Start/Stop Register Labor Time).
• Stop Labor Time Registration (PMS426) - Shop floor stop-time registration for an operation via PMS426. Calculates elapsed time for the operation.
• Report Operation Completed - An operation is reported as completed with quantity completed, rejected, and scrapped
• Report Operation Scrap - Scrap quantity (SCQA) reported against an operation in PMS070. Updates operation status and scrap statistics.
• Report Operation Rejected - Quantities from an operation are reported as rejected with a rejection reason code
• Hold Manufacturing Order - MO placed on hold (short or long term) via PMS100 or PMS230. Status second digit becomes 2 (e.g., 22, 32, 42).
• Release Held Manufacturing Order - Previously held MO released to resume processing. Hold indicator removed from status.
• Block Operation - An operation is blocked with a blocking reason, preventing further processing
• Split Manufacturing Order - MO split into child orders for parallel processing. Split information stored in MWOSPL table.
• Monitor Production (PMS095) - Production monitoring and overview via PMS095 (Monitoring Production) to track MO progress and identify problems.
• Manage MO Problems (PMS101) - Manufacturing order problems identified and managed via PMS101 (Managing Manufacturing Order Problems).
• Unblock Operation - A previously blocked operation is unblocked to resume processing
• Status: Active - Production order status changes to Active when the first WIP transaction (material issue or hours posting) occurs
• Move Material to Quarantine - Rejected items from an operation are moved to quarantine inventory
• Scheduled finish time - Planned finish date/time for the production order operation
• Return Material to Warehouse - Excess or unused material is returned from shop floor to warehouse
• Subcontracting Issue - Materials and/or subassemblies are sent to subcontractor for external operation processing
• Receive from Subcontractor - Completed items are received back from subcontractor after external operation
• Record Co-Product Output (PMS090) - Co-product quantity reported for a process manufacturing order operation. Co-product data stored in MWOCPN table with share percentage and lot number.
• Report By-Product (PMS080) - By-product quantity reported from a manufacturing operation. By-product is a secondary output captured separately from the main product and co-products.
• Report Yield Variance - Actual yield compared against expected yield percentage from product structure (MPDHED.YLPC). Yield material quantities evaluated.
• Lot Blending in Tank (MWS157) - Bulk materials blended in a tank or silo. MIWLAL transaction type 99 recorded. MILOMA lot characteristics updated for the blended lot.
• Split Production Order - Production order is split into child orders for parallel or partial processing
• Scheduled Production End - Planned end date for the entire production order
• Actual start time - Actual start date/time when production began on the shop floor
• Perform Quality Inspection - Quality inspection is performed on produced items per inspection order test procedures
• Create QI Request for Manufactured Lot (QMS300) - Quality inspection request created for a manufactured lot via QMS300. Timing based on QIRT setting in manufacturing order type (MWORDT) -- at release or at receipt.
• Perform Supplier Certificate Check - Supplier quality certificates checked against incoming raw material lots before they can be issued to production.
• Create QI Request (QMS300) - Quality Inspection request created for manufactured lot via QMS300 (QI Request. Open). Timing based on QIRT setting in PMS120.
• Record Inspection Result - Inspection test results (pass/fail) are recorded with measured values and tolerances
• Quality Inspect Manufactured Item (PMS130) - Quality-inspected item put away via PMS130 (Quality Inspected Item. Put-away). Lot balance ID status updated (approved/rejected).
• Record Specification Test (QMS400) - Individual specification test results entered for a QI request in QMS400. Results stored in QMSTRE with pass/fail determination against specification limits.
• Record QI Test Results (QMS400) - Test results entered for QI request via QMS400 (QI Test Results. Open). Results stored in QMSTRE table.
• Complete Inspection Order - Quality inspection order is completed, determining quantity to deliver vs reject
• Approve QI Request - QI request approved after all test results pass. Lot status updated to approved for delivery to inventory.
• Auto-Approve QI Request - QI request automatically approved when all test results pass. Triggered by auto-approval setting in quality plan (QMS009). Lot status updated to approved for delivery.
• Reject QI Request - QI request rejected due to failed test results. Lot status updated to rejected, may require rework or disposal.
• Put Away Quality-Inspected Item (PMS130) - Quality-inspected manufactured item put away to approved inventory location via PMS130. Lot balance ID status updated.
• Archive QI Request (QMS900) - Completed QI request archived with all related records (QMSRQH, QMSRQS, QMSRQT, QMSTRE) for long-term retention.
• Actual finish time - Actual finish date/time when production work was completed
• Status: To be Completed - Production order status changes to To be Completed, awaiting warehouse inbound completion
• Assign Production Lot (MMS235) - Production lot/batch number assigned to manufactured output. Lot attributes set including expiration date, best-before date, potency, and catch weight. Stored in MILOMA.
• Set Lot Expiration Date - Expiration/shelf-life date calculated and set on the production lot based on item shelf life days (SLDY) from manufacturing date.
• Set Lot Best-Before Date - Best-before date set on the production lot in MILOMA. May differ from expiration date based on product and regulatory rules.
• Report Manufacturing Receipt (PMS050) - Product receipt reported via PMS050 (Manufacturing Order. Report Receipt). Posts manufactured quantity to inventory. Creates lot in MWOPOL.
• Record Aging Start (PMS055) - Aging start date and time recorded for manufactured products requiring maturation (e.g., cheese, wine). Based on AGIG parameter in manufacturing order type.
• Reclassify Aged Product - Product reclassified after aging period completes. Lot status and item category updated based on aging rules. Manual or automatic reclassification date applied.
• Auto Receipt on Last Operation - Manufacturing receipt automatically triggered when last operation is reported, based on Automatic Receipt W/C setting in PDS010.
• Report Order Completed - Production order is reported as completed, posting completed quantity to inventory via Report Orders Completed session (tisfc0520m000)
• Record Lot Traceability - Full traceability chain recorded linking raw material lots (ingredients) consumed to production lot(s) created. Uses MITTRA transaction records linking MO material issues to receipts.
• Deliver to Inventory - Finished goods are received into inventory warehouse with lot/serial number assignment
• Report Order Completed Globally - Multiple production orders are mass-completed via global completion session
• Bulk Redistribution (PMS155) - Bulk quantities redistributed from parent process order to child orders via PMS155 (Bulk Redistribution. Open) for costing.
• Output Balancing (PMS150) - Pack variant quantities balanced across output items for packaged-item product structures via PMS150 (Output Balancing).
• Calculate Financial Results - Final cost calculation compares estimated vs actual costs for materials, hours, and overhead
• First confirmation - First time confirmation (goods movement or operation) is posted
• Create Internal Account Entry (CAS950) - Internal account entries created for production transactions (material issues, operation reporting) via CAS950. Updates WIP.
• Post WIP Settlement - Work-in-process amounts are settled to financial accounts with variance postings
• Close Production Order - Production order is closed via Close Production Orders session (ticst0201m000), finalizing all financial postings
• Archive Production Order - Closed production order data is archived to history company for long-term storage
• Reset Production Order Status - Production order status is reset for correction purposes (requires authorization)
• Last confirmation - Final confirmation posted, marking order operations as complete
• Status: Technically Complete - Production order is technically completed, no further postings

Data tables

• AFKO - Network Header
• AFPO - Order Item Detail
• AFRU - Order Completion Confirmations
• AFVC - Network Activity
• AUFK - Order Master Data
• JCDS - Status Change Documents
• MARA - Material Master - General Data
• MARC - Material Master - Plant Data
• MBEW - Material Valuation
• T001W - Plants
• AFVV - Order Operation Values
• CAUFV - View: Order Header (AUFK + AFKO + AFPO)
• MAKT - Material Master - Descriptions
• PLPO - Routing Operations
• RESB - Reservation/Dependent Requirements
• STPO - BOM Items
• USR02
• T006 - Units of Measure
• TJ02T - System Status Texts
• TJ30T - User Status Texts

Quality Management (QM)

Quality control, inspections, non-conformance

Activities

• Create Specification - Define quality requirements for an item or quality group with effective dates, status, and auto-attach settings
• Approve Specification - Set specification status from preliminary to approved, enabling it for use in auto-attach and QI requests
• Deactivate Specification - Deactivate a specification that is no longer in use, preventing auto-attachment
• Create Test Template - Define a reusable test template with default values for test type, limits, sampling, and measurement method
• Create Quality Test Set - Group related tests into a reusable set for items with similar characteristics (e.g., microbiology set)
• Define Quality Group - Create a quality group to classify items sharing similar quality specifications
• Configure Quality Plan - Set quality plan approval rules including lot auto-approval, spec auto-approval, and test frequency
• Configure Reinspection Plan - Set up reinspection schedules for shelf-life items requiring periodic quality retesting
• Set Item Warehouse Quality Plan - Assign a quality plan to a specific item/warehouse combination with reinspection and DO test settings
• Auto-Attach Specification to Order - System automatically attaches applicable specifications and tests to PO/CO/MO/DO lines based on entity rules
• Create QI Request from Purchase Receipt - System automatically creates a QI request when purchased goods are received into stock
• Create QI Request from Manufacturing Receipt - System automatically creates a QI request when manufactured goods are reported as received
• Create QI Request from Customer Return - System creates a QI request when goods are returned by customer
• Create QI Request Manually - Inspector manually creates a QI request for ad-hoc inspection
• Create Reinspection QI Request - System generates a reinspection QI request for lots in stock based on reinspection plan schedule
• Record Test Result - Enter actual test result value (quantitative, qualitative, or numeric qualitative) for a QI request test
• Calculate Test Result - System evaluates formula for calculated test using CRS975 when all component test results are specified
• Approve QI Request - Approve the QI request changing lot status from under-inspection to approved
• Reject QI Request - Reject the QI request changing lot status to rejected
• Complete QI Request - Set QI request status to Complete (status 3) after all tests are evaluated and approved/rejected
• Replace QI Request - Replace an existing QI request with a new one (status 4-Replaced) for subsequent receipts
• Cancel QI Request - Cancel a QI request (status 5-Canceled)
• Archive QI Request - Archive completed/replaced/canceled QI requests and related tables via QMS900
• Update Item Attributes from QI - System updates MIATTR table with test result values based on QI request origin and balance identity
• Print Lab Order Request - Generate and print lab order request document for external or internal laboratory testing
• Print Certificate of Analysis - Generate COA document including test results from QMSOTS and QMSRQT for customer shipments
• Approve Lot Through Put-Away - Auto-approve lot quality status through the put-away process when lot auto-approval is enabled
• Reclassify Lot - Reclassify a lot to a different status (e.g., from rejected to approved with conditions) via MMS130
• Block Lot for Quality Hold - Place a quality hold on a lot preventing it from being allocated, picked, or shipped
• Release Lot from Quality Hold - Release a quality hold on a lot after inspection completion or waiver approval
• Create Pre-Shipment QI Request - Create a QI request for test-at-pre-shipment with three specification retrieval options
• Perform Allergen Verification Test - Execute allergen verification testing on a lot to confirm allergen declarations match actual content
• Perform Microbiological Test - Execute microbiological testing (plate count, pathogen detection) for food safety compliance
• Calibrate Measurement Instrument - Perform calibration on a measurement instrument and record results with next calibration date
• Copy QI Request - Copy an existing QI request to create a new one with the same specifications and tests
• Delete QI Request - Delete a QI request that was created in error
• Inherit Specification from Bulk Item - Package item inherits quality specifications from its bulk component item
• Create Grower Agreement QI Request - Generate QI request linked to grower agreement at line level for raw material quality during growing period
• Run MMS975 Reclassification Autojob - Execute autojob MMS975 to monitor and process planned lot reclassification dates for shelf-life management
• Define Characteristic - Create or modify a quality characteristic (measurable property like weight, length, color) with data type and value determination method
• Define Aspect - Create or modify an aspect (part/section of an item) and link characteristics to it
• Define Test - Create a quality test and link it to characteristics with result type (Quantitative/Qualitative) and instruments
• Create Standard Test Procedure - Define a reusable test plan grouping quality standards, tests, sampling rules, and characteristics with effective/expiry dates
• Link Characteristic to Test Procedure - Associate a characteristic with a standard test procedure specifying limits, tolerances, and norm values
• Create Test Group - Define a test group linked to a standard test procedure with sampling method, sample size, and acceptable quality level (AQL)
• Define Testing Combination - Configure which standard test procedure is triggered for a given order origin, item/quality group, and business partner combination
• Set Item Quality Data - Configure quality settings for an individual item including quality group, FAI requirements, and default test procedures
• Define Sampling Rule - Create a sampling rule specifying sample size and accept/reject criteria per inspection standard
• Register Instrument - Register a quality testing instrument with calibration interval tracking
• Define First Article Inspection Rule - Create an FAI trigger rule specifying item, revision, business partner, and warehouse combination for first article inspections
• Create Inspection Order - Generate an inspection order automatically (from purchase receipt, production order, or warehouse transfer) or manually
• Activate Inspection Order - Set inspection order status from Created to Active, enabling test data entry
• Assign Inspector - Assign an employee/inspector to an inspection order via resource assignment
• Create Inspection Sample - Define a sample with specific size and date/time for an inspection order
• Enter Test Data - Record measured values for inspection order test lines by characteristic or by sample
• Enter Test Data by Serial Number - Record measured values organized by serial number rather than by characteristic
• Evaluate Test Result - System automatically evaluates measured values against limits and determines Pass/Fail result per line
• Complete Inspection Order Line - Set an inspection order line status to Completed after all test data is specified
• Complete Inspection Order - Set entire inspection order status to Completed when all lines are complete
• Process Inspection Order - Process the completed inspection order to determine accepted/rejected quantities based on AQL comparison
• Skip Lot Accept - Accept an inspection order lot without full inspection (skip lot acceptance)
• Close Inspection Order - Close the processed inspection order, finalizing all quality results
• Block Origin Order - Block the originating purchase/production/sales order pending inspection results
• Release Origin Order Block - Release the block on the originating order after inspection completion
• Generate Storage Inspection - Generate a storage inspection for items in inventory that require periodic quality checks
• Block Inventory for Inspection - Block inventory items for use during active storage inspection
• Complete Storage Inspection - Complete a storage inspection and release or reject inventory items
• Create FAI Document - Generate a First Article Inspection document triggered by FAI rules for purchase or production orders
• Perform First Article Inspection - Execute the first article inspection to verify engineering and specification requirements
• Complete FAI Document - Complete the FAI document recording pass/fail results
• Create Non-Conformance Report - Create an NCMR manually or auto-generate from a failed inspection, with status Open
• Submit Non-Conformance Report - Submit the NCMR for review, changing status from Open to Submitted
• Assign Non-Conformance Report - Assign the NCMR to an owner/MRB for investigation, status changes to Assigned
• Investigate Non-Conformance - Owner investigates the material non-conformance and identifies the cause
• Set NCMR Disposition - Set the disposition action (Rework/Reclassify/Scrap/Use As-Is) for the non-conforming material, status changes to Dispositioned
• Create Disposition Order - Generate a disposition order for rework, reclassification, or scrap processing
• Split Non-Conformance Report - Split an NCMR into parent-child relationship for traceability when quantities must be handled differently
• Link Lots/Serials to NCMR - Associate specific lot numbers and serial numbers with the non-conformance report
• Request Waiver - Request a waiver from the customer or supplier for the non-conforming material
• Receive Waiver - Record receipt of waiver approval from business partner
• Close Non-Conformance Report - Close the NCMR after disposition is complete, status changes to Closed
• Cancel Non-Conformance Report - Cancel the NCMR (e.g., No Fault Found disposition), status changes to Cancelled
• Reset Non-Conformance Report - Reset the NCMR status back to a prior state for re-investigation
• Move to Quarantine Inventory - Move non-conforming material to quarantine inventory location pending disposition
• Create Corrective Action Plan - Create a CAP manually or generate from an NCMR to address the root cause of non-conformance
• Define CAP Tasks - Create task lines within the CAP with action categories (Containment/Corrective/Preventive/General) and due dates
• Submit Corrective Action Plan - Submit the CAP for approval, changing status from Created to Submitted
• Approve Corrective Action Plan - Approver approves the CAP, changing status to Approved
• Start CAP Task - Start a containment, corrective, or preventive action task, changing task status to In Progress
• Complete CAP Task - Complete a CAP task recording the actual completion date and results
• Verify CAP Task - Verify that a completed CAP task has effectively addressed the non-conformance
• Verify CAP Effectiveness - Verify overall CAP effectiveness after all tasks are completed and closed
• Close Corrective Action Plan - Close the CAP after all tasks are verified and effectiveness is confirmed
• Create Root Cause Analysis - Generate an RCA document from within a CAP using 5-Why, Fishbone, or Checklist methodology
• Perform 5-Why Analysis - Execute 5-Why root cause analysis by specifying progressive why questions to drill down to the root cause
• Perform Fishbone Analysis - Execute fishbone (Ishikawa) analysis categorizing potential causes by Material/Machine/Environment/Method/Manpower/Measurement
• Complete Root Cause Analysis - Complete the RCA document with identified root cause findings
• Calibrate Instrument - Perform calibration on a quality testing instrument and record results in calibration history
• Record Calibration Result - Record pass/fail calibration result with date, employee, and notes
• Generate Quality Report - Print or generate inspection order reports, 8D reports, or A3 problem-solving reports
• Review Quality Statistics - Review aggregated item quality statistics per period and origin for trend analysis
• Generate Vendor Quality Rating - Calculate and review vendor quality ratings based on inspection results per business partner

Data tables

• QALS - Inspection Lot Record
• QAMR - Characteristic Results
• QAVE - Inspection Usage Decision
• QMEL - Quality Notification
• QAMV - Characteristic Specifications
• QMSM - Task for Quality Notification

Record-to-Report (R2R)

The financial close and reporting process. Covers journal entries, period-end close activities, consolidation, and financial statement preparation.

Activities

• Execute Transaction - Main transaction processing
• Post to System - Record posted to system
• Complete Review - Final review performed
• Close Process - Process marked complete
• Period Opening - Fiscal period is opened for posting in the target company code
• Create Profile and Instance - Financial Closing Cockpit profile and instance are created for the closing run
• Job - Background job is scheduled and executed as part of the closing task list
• Flow Definition - Closing task flow definition is triggered within the FCC instance
• Transaction - SAP transaction is executed as a closing task step
• Note - Manual note or documentation step is recorded in the closing task list
• Program - ABAP program is executed as part of the closing process
• SAP CPS - SAP Central Process Scheduling task is executed for closing automation
• Remote Transaction - Transaction is executed on a remote SAP system as part of closing
• Remote Program - Program is executed on a remote system during the closing run
• Remote Job - Background job is executed on a remote system during closing
• External Job - Job is executed on an external non-SAP system as part of the closing process
• Remote Flow Definition - Flow definition is triggered on a remote system during closing
• Create Journal Entry - Manual or recurring journal entry is created for period-end adjustments
• Post GL Document - General Ledger document is posted to record financial transactions
• Park Document - Document is parked for later review and approval before posting
• Release Parked Document - Previously parked document is reviewed, approved, and released for posting
• Reverse Document - Posted document is reversed to correct errors or adjust entries
• Run Depreciation - Asset depreciation run is executed to calculate and post depreciation amounts
• Execute Allocation Cycle - Cost allocation cycle is executed to distribute costs across cost centers
• Currency Revaluation - Foreign currency open items and balances are revalued at period-end rates
• Execute Reconciliation - Intercompany or subledger-to-GL reconciliation is executed
• Run Trial Balance - Trial balance report is generated to verify debit-credit equality
• Period Closing - Fiscal period is closed to prevent further postings in the completed period
• Generate Financial Statement - Final financial statements are generated for the reporting period

Case attributes

• Company Code (Text) - Company or entity code
• Cost Center (Text) - Cost center responsible
• Document Type (Text) - Type of financial document
• GL Account (Text) - General ledger account
• Status (Text) - Current status
• Amount (Currency) - Monetary value
• Currency (Text) - Transaction currency
• Created By (Text) - User who created the record
• Document Number (Text) - Unique identifier for the document
• Vendor/Customer (Text) - Business partner ID
• Document Date (Date) - Date of the document
• Due Date (Date) - Payment or completion due date

Data tables

• ACDOCA - Universal Journal Entry
• BKPF - Accounting Document Header
• BSEG - Accounting Document Line Item
• COEP - CO Line Items
• FCC_AUTO_STATHIS - FCC Status History
• FCC_INST_HDR - Financial Closing Cockpit Instance Headers
• FCC_INST_ITEM - Financial Closing Cockpit Tasks
• SKA1 - GL Account Master (Chart of Accounts)
• SKB1 - GL Account Master (Company Code)
• ANEK - Asset Document Header
• CDHDR
• CDPOS
• FAGLFLEXA - GL Actual Line Items
• FAGLFLEXT - GL Totals Table
• NSDM_V_JOURNAL - New GL Journal Entry View (S/4HANA)
• T001
• USR02
• T001B - Permitted Posting Periods
• TBTCO - Background Job Overview

Service/Case Management (SERVICE)

Support tickets, SLAs, resolution

Activities

• Place Radiology Order - Radiology/imaging order is placed
• Schedule Imaging Study - Imaging study is scheduled
• Check In for Imaging - Patient checks in for imaging appointment
• Prepare Patient - Patient is prepared for imaging procedure
• Begin Imaging Study - Imaging study begins (exam started)
• Complete Imaging Study - Imaging study is completed (exam ended)
• Upload Images to PACS - Images are uploaded to PACS system
• Assign Study to Radiologist - Study is assigned for interpretation
• Begin Dictation - Radiologist begins dictation of report
• Complete Dictation - Radiologist completes dictation
• Transcribe Report - Report is transcribed
• Preliminary Report Available - Preliminary report is available
• Sign Final Report - Radiologist signs the final report
• Addend Report - Addendum is added to finalized report
• Critical Finding Notification - Critical finding is communicated to provider
• Submit Guest Service Request - Guest or staff submits a new service request through PMS, mobile app, or front desk
• Categorize Service Request - Request is categorized by type (housekeeping, maintenance, amenity, complaint)
• Set Request Priority - Priority level assigned based on request type and guest VIP status
• Route Request to Department - Request automatically or manually routed to responsible department
• Assign Request to Staff - Specific staff member assigned to handle the service request
• Acknowledge Service Request - Staff acknowledges receipt and begins work on request
• Begin Service Delivery - Staff begins executing the requested service
• Update Service Request Status - Status updated during service delivery (in progress, waiting, etc.)
• Escalate Service Request - Request escalated due to SLA breach, complexity, or guest dissatisfaction
• Reassign Service Request - Request reassigned to different staff member or department
• Complete Service Request - Service delivered and request marked as complete
• Confirm Guest Satisfaction - Staff or system confirms guest satisfaction with service delivery
• Close Service Request - Request formally closed after completion and satisfaction confirmation
• Cancel Service Request - Service request cancelled by guest or staff
• Run Auto Housekeeping Assignment - System automatically assigns rooms to housekeepers based on occupancy, points, and availability
• Assign Room to Housekeeper - Room manually or automatically assigned to specific housekeeper
• Set Room Service Type - Service type set for room (full cleaning, light cleaning, turndown, no service)
• Mark Room as Priority Clean - Room flagged for priority/rush cleaning
• Set Do Not Disturb - Guest sets Do Not Disturb flag preventing room servicing
• Clear Do Not Disturb - Do Not Disturb flag cleared allowing room servicing
• Start Room Cleaning - Housekeeper enters room and begins cleaning (attendant in room)
• Complete Room Cleaning - Housekeeper finishes cleaning and updates room status
• Update Room Status - Room status updated (dirty to clean, inspect, pickup)
• Request Room Inspection - Room submitted for supervisor inspection
• Inspect Room - Supervisor inspects cleaned room for quality
• Pass Room Inspection - Room passes supervisor inspection and marked clean
• Fail Room Inspection - Room fails inspection and sent back for recleaning
• Mark Room Out of Service - Room taken out of service for maintenance or deep cleaning
• Return Room to Service - Room returned to active inventory after maintenance
• Process Turndown Service - Turndown service completed for VIP or requested rooms
• EOD Housekeeping Room Status - End-of-day process sets housekeeping service types for next business day
• Create Work Order - New maintenance work order created for repair or preventive task
• Categorize Work Order - Work order categorized by type (plumbing, electrical, HVAC, etc.)
• Set Work Order Priority - Priority assigned based on urgency and impact
• Assign Work Order to Technician - Maintenance technician assigned to the work order
• Schedule Work Order - Work order scheduled with planned start and end dates
• Place Room on Hold - Room placed on hold/out of service during maintenance
• Start Maintenance Work - Technician begins work on the maintenance task
• Order Parts for Work Order - Parts or materials ordered for the repair
• Update Work Order Progress - Progress notes and status updated during work
• Complete Maintenance Work - Maintenance work completed and work order closed
• Release Room from Hold - Room released from hold and returned to inventory after maintenance
• Record Work Order Cost - Actual costs (labor, parts, vendor) recorded on work order
• Close Work Order - Work order formally closed after completion and cost recording
• Create Concierge Task - New concierge task created for guest request (restaurant, transport, tickets)
• Assign Concierge Task - Concierge staff member assigned to handle the task
• Complete Concierge Task - Concierge task completed and guest notified
• Post Concierge Charge - Charge for concierge service posted to guest folio
• Log Found Item - Item found by housekeeping or staff logged into system
• Report Lost Item - Guest reports a lost item
• Match Lost and Found Item - Found item matched to guest report
• Return Item to Guest - Found item returned to guest (in person or shipped)
• Dispose of Unclaimed Item - Unclaimed item disposed after retention period
• Schedule Amenity Delivery - Amenity delivery scheduled for guest arrival or special occasion
• Deliver Room Amenities - Amenities delivered and placed in guest room
• Post Sundry Charge - Sundry/minibar consumption charged to guest folio
• Restock Minibar - Minibar restocked and consumption recorded
• Generate Amenities Report - Amenities report generated for operational analysis
• Send Pre-Arrival Communication - Pre-arrival email/SMS sent to guest with stay details
• Send In-Stay Message - Message or alert delivered to guest during stay
• Send Post-Stay Survey - Post-stay satisfaction survey sent to guest
• Receive Guest Feedback - Guest feedback/survey response received and recorded
• Create Guest Trace - Trace/alert/locator created for guest profile
• Acknowledge Guest Message - Staff acknowledges and acts on guest message or trace
• Create Guest Profile - New guest profile created in centralized system
• Update Guest Preferences - Guest preferences updated in profile
• Merge Guest Profiles - Duplicate guest profiles automatically or manually merged
• Calculate Guest Lifetime Value - EOD process calculates total historical revenue for guest
• Export GDPR Guest Data - Guest data exported for GDPR compliance request

Data tables

• CRMS4D_SERV_H - S/4HANA Service Transaction Header
• CRMS4D_SERV_I - S/4HANA Service Transaction Items
• IBIB - Installed Base Header
• PMSDO - PM Organizational Data for SD Documents
• VEDA - Contract Data (Validity/Cancellation)
• BGMK - Master Warranty Header
• BGMP - Master Warranty Item
• CRMS4D_BTX_H - S/4HANA Business Transaction Index
• IBIN - Installed Base Components

Tax Management (TAX)

Tax calculation, reporting, compliance

Data tables

• BSET - Tax Data Document Segment
• J_1BTXD - Tax Declaration Header (Brazil)
• T007A - Tax Keys Master
• T007S - Tax Codes per Country

Time & Attendance (TIME)

Time tracking, leave management, scheduling

Data tables

• CATSDB - Cross-Application Time Sheet
• PA0007 - HR Master - Planned Working Time (Infotype 0007)
• PA2001 - HR Time Record: Absences (Infotype 2001)
• PA2002 - HR Time Record: Attendances (Infotype 2002)
• PA2005 - HR Time Record: Overtime (Infotype 2005)
• PA2006 - HR Time Record: Absence Quotas (Infotype 2006)
• PA2007 - HR Time Record: Attendance Quotas (Infotype 2007)
• PTEX2000 - Interface Table for Attendances/Absences

Vendor Master Data (VMD)

Complete lifecycle of vendor records from creation through maintenance

Activities

• Create Vendor - New vendor master record is created at the general data level
• Create Vendor on Company Code Level - Vendor master record is extended to a company code
• Create Vendor on Purchasing Org Level - Vendor master record is extended to a purchasing organization
• Set Posting Block - Posting block is set on the vendor to prevent financial transactions
• Set Purchasing Block - Purchasing block is set on the vendor to prevent new purchase orders
• Change General Vendor Data - General data fields on the vendor master are changed (name, address, etc.)
• Remove Posting Block - Posting block is removed from the vendor master
• Remove Purchasing Block - Purchasing block is removed from the vendor master
• Change Company Code Data - Company code level data is changed (payment terms, reconciliation account, etc.)
• Change Purchasing Org Data - Purchasing organization level data is changed (order currency, incoterms, etc.)
• Change Account Number - Vendor reconciliation account number is changed
• Change Bank Code - Vendor bank routing code is updated
• Change Bank Details - Vendor bank account details are updated
• Delete Vendor - Vendor master record is flagged for deletion at the general level
• Delete Company Code Data - Vendor master company code segment is flagged for deletion
• Delete Purchasing Org Data - Vendor master purchasing organization segment is flagged for deletion

Data tables

• LFA1 - Vendor Master - General Data
• LFB1 - Vendor Master - Company Code Data
• CDHDR
• CDPOS
• LFB5 - Vendor Dunning Data
• LFBK - Vendor Bank Details
• LFM1 - Vendor Master - Purchasing Organization
• USR02
• T005 - Countries

Warehouse Management (WH)

Warehouse operations, picking, packing, shipping

Activities

• Create Transfer Order Item (Picking) - Transfer order item created for picking goods from storage
• Create Transfer Order Item (Production) - Transfer order item created for production supply or put-away
• Create Transfer Requirement Item (Production) - Transfer requirement item created to request material movement for production
• Create Warehousing Order (Inbound) - A new warehousing order of type Receipt is created from purchase order, production order, or transfer order
• Activate Inbound Order - Inbound warehousing order is activated from Planned to Open status, ready for processing
• Process ASN (Advance Shipment Notice) - Advance shipment notice from supplier is received and processed to pre-populate receipt information
• Receive Goods (Create Receipt) - Goods are physically received at the warehouse and a receipt record is created linking inbound order lines
• Print Receiving Label - Receiving label is printed for inbound LPN identification during receipt processing
• Confirm Receipt - Receipt is confirmed with actual quantities, updating cumulated received quantity on order lines
• Inbound Inspection - Received goods are inspected for quality/quantity conformance; items approved, rejected, or scrapped
• Generate Inbound Advice - System generates put-away instructions indicating target storage locations for received goods
• System-Direct Putaway - System generates putaway task with system-directed target location based on putaway strategy configuration
• Create Storage List - Storage list document is generated grouping put-away instructions by run number and storage mission
• Confirm Putaway Task - Putaway task is confirmed via RF or workstation; inventory is placed at the target location and LOTXLOCXID is updated
• Confirm Storage (Put Away) - Physical put-away is confirmed; goods are stored in target locations and inventory is updated
• Assign Task to Operator - Task is assigned to a specific warehouse operator based on zone, equipment, and priority rules
• Interleave Tasks - System interleaves pick and putaway tasks for the same operator to minimize empty travel time
• Confirm Transfer Order Item (Picking) - Transfer order item for picking is confirmed as executed
• Confirm Transfer Order Item (Production) - Transfer order item for production movement is confirmed
• Confirm Transfer Order Item with Difference - Transfer order item confirmed with quantity difference from expected
• Create Warehousing Order (Outbound) - A new warehousing order of type Issue is created from sales order, production order, or transfer order
• Activate Outbound Order - Outbound warehousing order is activated from Planned to Open status, ready for processing
• Create Wave - Wave is created grouping selected outbound orders for batch processing based on wave template criteria (route, carrier, priority)
• Release Wave - Wave is released triggering allocation and pick task generation for all orders in the wave
• Generate Outbound Advice - System generates outbound advice indicating pick locations, quantities, and lot/serial assignments
• Allocate Order (Firm) - Firm allocation is executed creating PickDetail and TaskDetail records reserving specific inventory locations for the order
• Allocate Order (Soft) - Soft/dynamic allocation is executed creating DemandAllocation records reserving inventory without firm pick assignments
• Deallocate Order - Previously allocated pick records are deallocated returning reserved inventory to available status
• Release Outbound Advice - Outbound advice is released enabling picking list generation; order line status changes to Released
• Generate Picking List - Picking list document is generated showing locations from which goods must be collected
• Start RF Pick Task - Warehouse operator starts an RF-directed pick task on mobile device, acknowledging source location and item
• Print Wave Label - Wave label is printed showing pick details including order, storer, customer, carton type, route, and stop
• Confirm RF Pick - Operator confirms pick via RF device scanning location check digit, item, and quantity picked
• Short Pick - Operator reports a short pick (less than allocated quantity available at the location), triggering reallocation or backorder
• Confirm Picking (Pick Complete) - Picking is confirmed; order line status changes to Staged, goods moved to loading area
• Complete Wave - All picks in the wave are confirmed complete and the wave status is set to Complete
• Outbound Inspection - Picked goods are inspected before shipment; items approved, rejected, or scrapped
• Assign Carton - Cartonization assigns a carton type to the pick based on item dimensions and carton group rules
• Confirm Packing - Packing is confirmed for a carton/case; all picks are packed and carton weight/dimensions are recorded
• Compose Shipment - Outbound order lines are composed into shipment records linking to carriers and routes
• Close Container - LPN/container is closed and sealed, preventing further items from being added and triggering shipping label print
• Print Shipping Label - Shipping label with carrier tracking information is printed for the packed container
• Freeze Shipment - Shipment is frozen preventing further modifications; shipping documents can be printed
• Print Packing Slip - Packing slip document is printed for the shipment listing items, quantities, and packaging
• Print Bill of Lading - Bill of lading is printed for carrier documentation and legal proof of shipment
• Confirm Shipment - Shipment is confirmed as dispatched; inventory is decreased and goods leave the warehouse
• Create Transfer Order - Transfer warehousing order is created for inter-warehouse or intra-warehouse stock movement
• Activate Transfer Order - Transfer order is activated from Planned to Open status
• Issue Transfer (Outbound) - Goods are issued from source warehouse as outbound leg of the transfer
• Receive Transfer (Inbound) - Goods are received at destination warehouse as inbound leg of the transfer
• Confirm Transfer - Transfer is confirmed; both source and destination inventory quantities are updated
• Generate Replenishment Task - Replenishment task is generated to refill a forward pick location from reserve/bulk storage based on min/max or demand trigger
• Confirm Replenishment - Replenishment task is confirmed complete; inventory is moved from reserve to forward pick location
• Generate Cycle Count Order - Cycle count order is generated based on ABC classification and counting schedule for stock verification
• Print Counting List - Counting list document is printed for warehouse personnel to perform physical count
• Enter Count Results - Physical count results are entered recording counted quantities against registered quantities
• Approve Cycle Count Variance - Variance between counted and registered quantities is reviewed and approved with reason code
• Process Cycle Count Order - Cycle count order is processed; inventory adjustments are applied based on approved variances
• Create Adjustment Order - Manual inventory adjustment order is created to correct registered inventory quantities
• Create Inventory Adjustment - Manual inventory adjustment is created to correct on-hand quantities with a reason code
• Approve Adjustment Order - Adjustment order is reviewed and approved by authorized personnel
• Approve Inventory Adjustment - Inventory adjustment is reviewed and approved by authorized personnel before application
• Process Adjustment Order - Adjustment order is processed; inventory quantities are updated with the corrected values
• Apply Inventory Adjustment - Approved adjustment is applied updating LOTXLOCXID on-hand quantities and creating ITRN transaction record
• Create Cross-Dock Order - Cross-dock order is created linking inbound receipt directly to outbound order bypassing storage
• Identify Cross-Dock Opportunity - System identifies opportunistic cross-dock match between inbound receipt and open outbound demand
• Execute Cross-Dock - Cross-docked goods are moved directly from receiving to shipping area without intermediate storage
• Confirm Cross-Dock Move - Cross-docked goods are physically moved from receiving to shipping area and the cross-dock task is confirmed
• Plan Load - Shipments are grouped into loads for transport planning with carrier and route assignment
• Confirm Load - Load is confirmed as dispatched; all contained shipments are updated
• Create Handling Unit - Handling unit is created to physically group and track goods through warehouse operations
• Pack Handling Unit - Items are packed into a handling unit during inbound, storage, or outbound processing
• Place Inventory on Hold - Inventory at a location/lot/LPN is placed on quality hold preventing allocation and shipment pending review
• Release Inventory from Hold - Inventory hold is released making the inventory available again for allocation and shipment
• Create Move Task - Inventory move task is created to relocate inventory from one location to another within the warehouse
• Unpack Handling Unit - Items are unpacked from a handling unit for inspection, repacking, or individual processing
• Confirm Move Task - Move task is confirmed; inventory is relocated from source to destination location and LOTXLOCXID records are updated
• Create Work Order - Work order is created for kit assembly, value-added services, or light manufacturing within the warehouse
• Issue Components to Work Order - Component materials are issued from inventory to the work order for assembly or processing
• Complete Work Order - Work order is completed; finished goods are received into inventory at the target location
• Execute Direct Material Supply - Materials are supplied directly from warehouse to production line or work center bypassing normal issue procedures
• Calculate Billing Charges - 3PL billing charges are calculated for a storer based on storage, handling, and VAS billing rules
• Generate Billing Invoice - Billing invoice is generated for a storer summarizing calculated charges for the billing period
• Send Order to WMS - Warehousing order is published to external Warehouse Management System for execution
• Receive WMS Confirmation - External WMS returns execution confirmation with actual pick/receipt quantities and lot/serial data
• Block Warehousing Order - Warehousing order or order line is blocked preventing further processing
• Unblock Warehousing Order - Block on warehousing order or order line is removed, resuming processing
• Cancel Warehousing Order - Warehousing order is cancelled; remaining unprocessed quantities are released
• Remove Warehousing Order - Completed or cancelled warehousing order is removed from active orders and optionally archived
• Cancel Transfer Order Item - A previously created transfer order item is cancelled
• Create Delivery Item - An outbound delivery item is created for shipment
• Create Sales Order Item - A sales order item triggers warehouse demand
• Create Production Order - A production order is created generating warehouse requirements
• Confirm Production Order - Production order confirmation triggers goods receipt in warehouse
• Release Production Order - Production order released, component reservations activate in warehouse
• Delivery Picking Completely Processed - All picking activities for the delivery are completed
• Delivery Packing Completely Processed - All packing activities for the delivery are completed

Data tables

• /SCWM/AQUA - Available Stock for Task Creation
• /SCWM/LAGP - Storage Bins
• /SCWM/ORDIM_O - Warehouse Tasks Open
• /SCWM/QUAN - Physical Stock Attributes
• LTAK - Transfer Order Header
• LTAP - Transfer Order Items
• T001W - Plants
• /SCWM/HUHDR - Handling Unit Header
• /SCWM/ORDIM_C - Warehouse Tasks Confirmed
• LAGP - Storage Bins
• LQUA - Quant (Warehouse Stock)
• LTBK - Transfer Requirement Header
• LTBP - Transfer Requirement Items
• USR02
• T300 - WM Warehouse Numbers
• T301 - WM Storage Types

Explore this interactively in the mindzie Knowledge Base.