Finance Tables in SAP S/4HANA

Finance Tables (ACDOCA)

ECC
S/4HANA
bseg
Detailed line-item level Financial Accounting data
different role/data granularity - for backward compatibility
bkpf
Financial accounting documents header
for backward compatibility
fagflexa
Detailed line-item level financial data for New General Ledger accounting
acdoca
Universal Journal - Combines financial and controlling data consolidates line item details across General Ledger (GL), Controlling (CO), Asset Accounting (AA), and Material Ledger (ML)

Role of bseg

SAP ECC:

  • Primary Line Item Table for Financial Accounting:
    • The bseg table is used to store line-item details of financial accounting documents (e.g., GL, accounts payable, accounts receivable).
  • Core Table in ECC Reporting:
    • Queries often rely on bseg in combination with bkpf for detailed financial and accounting information.

SAP S/4HANA:

💡

Core financial reporting and analysis now rely on acdoca. The bseg table is used mainly for transactional processing and open-item management but no longer supports comprehensive reporting.

Reduced Data Granularity:

Most detailed financial line-item information is stored in acdoca. The bseg table now contains less granular data.

  • Retained for Compatibility and Certain Transactions:
    • bseg remains in S/4HANA primarily for backward compatibility with legacy programs, custom reports, and scenarios like open item management.
  • Limited to Specific Use Cases:
    • bseg is not the primary source for most financial data in S/4HANA; its scope is reduced compared to ECC.

Why Does bseg Still Exist in S/4HANA?

  • Backward Compatibility:
    • Many legacy custom reports, programs, and business processes still depend on bseg. SAP retained it to ensure compatibility during migration to S/4HANA.
  • Transactional Integrity:
    • For open item management (e.g., clearing accounts payable and receivable), bseg is still used. These processes are highly transactional and require detailed line-item tracking.
  • Legal and Regulatory Needs:
    • In some jurisdictions, maintaining detailed transactional data in its original structure (e.g., bseg) is necessary for compliance.

Role of bkfp

💡

For reporting and financial analysis, the focus has shifted from bkpf to acdoca, which consolidates both header-like and line-item details for real-time, HANA-optimized reporting.

SAP S/4HANA:

  • bkpf provides header-level details such as document type, company code, posting date, and fiscal year.
  • acdoca stores the corresponding line-item details, often referencing bkpf for header-level attributes when necessary.
  • For example, while posting a financial document:
    • bkpf: Captures the overarching metadata (e.g., document date, user ID).
    • acdoca: Captures the line-item entries, profit center, and segment data, consolidating details from both bseg and faglflexa in ECC.

Role of fagflexa

SAP ECC:

  • Line Item Table for the New GL:
    • Stores detailed line-item financial data for General Ledger accounting, including profit center, cost center, segment, and other dimensions introduced with the New GL functionality in ECC.
    • It works in conjunction with the faglflext table (totals table) for reporting and reconciliation.
  • Enhanced Financial Reporting:
    • Supports multi-dimensional reporting by including fields like PRCTR (Profit Center), SEGMENT, and RACCT (GL Account).
    • Essential for reconciliation between financial and managerial accounting, as it integrates controlling (CO) dimensions.
  • Dependency on Joins:
    • To get a complete view, queries often join faglflexa with other tables such as bseg, bkpf, and faglflext.

SAP S/4HANA: The faglflexa table is no longer used. Its functionality and data are fully absorbed into the Universal Journal (acdoca)

Return to SAP ECC → S/4HANA Migration