FAGLFLEXA table — New GL Actual Line Items Table

One row in FAGLFLEXA represents one line of an actual accounting document as posted into a specific ledger under classic New General Ledger accounting. The table exists because New GL needed to carry reporting dimensions that BSEG did not natively hold at the same granularity per ledger, such as profit center, segment and business area, and because a company code can run more than one parallel ledger with different fiscal year variants or valuation approaches. Each row ties back to exactly one accounting document line but is duplicated per ledger if the line is relevant to more than one ledger. It is the actual-postings counterpart to FAGLFLEXT, which holds the aggregated totals derived from these line items.

Always restrict by RCLNT implicitly via the logon client, then by RLDNR first since a document can appear once per relevant ledger and pulling all ledgers when only the leading ledger is needed multiplies rows and skews totals. After ledger, restrict by RBUKRS and GJAHR, then by a posting date or period range rather than scanning the whole fiscal year. The table can be large in any company that has run New GL for several years, so an account range on RACCT combined with the period restriction is the difference between a query that returns in seconds and one that times out. Avoid selecting on WSL or HSL as a filter; always filter on the identifying fields and read the amounts.

To prove that a specific document line was posted to a non-leading ledger with a different profit center than the leading ledger, select FAGLFLEXA for the RBUKRS, GJAHR, BELNR of the document with no restriction on RLDNR, and compare PRCTR and HSL across the returned rows. Rows with the same BELNR but different RLDNR and different PRCTR or amount confirm a ledger-specific adjustment, such as a parallel valuation posting, that will not be visible in BSEG alone.

FAGLFLEXA belongs to the classic New General Ledger data model used before S/4HANA. In S/4HANA the actual line items and totals across FI and CO are unified into the Universal Journal table ACDOCA, and FAGLFLEXA is retained, where present, mainly as a compatibility view for existing reports and interfaces rather than as a table receiving new physical postings. New custom development on S/4HANA should read from ACDOCA directly rather than from FAGLFLEXA.

Questions about what FAGLFLEXA contains for a given ledger sit with the FI general ledger lead, since ledger configuration and parallel accounting setup drive which rows exist. Discrepancies between FAGLFLEXA and FAGLFLEXT are a reconciliation topic for FI/CO integration, and any migration mapping to ACDOCA on an S/4HANA conversion is a data migration and finance functional workstream decision, not a basis or ABAP call.

FAGLFLEXT holds the aggregated totals derived from FAGLFLEXA and is the table most GL reports actually query for performance reasons. BKPF and BSEG hold the underlying accounting document that FAGLFLEXA references by BELNR and BUZEI. Postings arrive through standard FI document entry and period-end transactions; account and company code master data come from SKA1, SKB1 and T001. On S/4HANA the successor for both actual line items and totals is ACDOCA.