FAGLFLEXT table — New GL Totals Table

A row in FAGLFLEXT is a summarized balance for one combination of ledger, fiscal year, company code, account and whatever additional dimensions that ledger's scenario assignment activated, such as cost center, profit center, segment or business area. It is not a document line. Multiple postings to the same account and same combination of characteristics in the same fiscal year accumulate into the same row, spread across period buckets. This table exists because New General Ledger needed a totals structure that could carry entity-level dimensions like profit center and segment directly, something the classic GLT0 totals table could not do without a separate special ledger. Reporting programs read FAGLFLEXT for fast balance display instead of summing thousands of line items on the fly.

Always restrict RLDNR and RYEAR before anything else; a ledger with segment, profit center and cost center all active produces one row per unique combination of those values, not one row per account, so an unrestricted select against a mature company code can return an enormous result set. RBUKRS and RACCT should follow immediately as second-tier filters. RCLNT is handled by the client field automatically in most access paths. Do not sum HSL fields across ledgers unless the intent is genuinely a cross-ledger comparison, since parallel ledgers hold independent balances for the same document. Watch RRCTY and RVERS when a planning ledger shares the table structure with actuals.

Symptom: a profit center report shows a different total than the trial balance for the same account and company code. Select FAGLFLEXT with RLDNR equal to the ledger in question, RYEAR equal to the year, RBUKRS and RACCT fixed, sum the relevant HSL period columns grouped by PRCTR, and compare against FAGLFLEXA summed the same way. If PRCTR comes back blank on every row, the ledger's scenario does not carry profit center as an activated characteristic, and the apparent gap is a configuration fact, not missing data.

On S/4HANA, actual postings no longer write to FAGLFLEXT; the universal journal table ACDOCA is the single line-item source, and totals are derived from it on the fly rather than persisted separately. FAGLFLEXT may still exist as a physical table holding historic pre-migration data, and compatibility views built on ACDOCA can redirect older reports that still select from it. Custom reports or interfaces reading FAGLFLEXT directly need to be checked for whether they will see current-period data at all after go-live, since the table is effectively frozen for new business.

Interpretation of what FAGLFLEXT balances mean belongs to whoever configured the ledger, specifically the scenario and field assignment, typically the FI general ledger lead. Basis owns table growth and archiving decisions. When a reconciliation question comes up, start with the ledger configuration owner rather than assuming a data extraction or interface fault.

FAGLFLEXA is the line-item counterpart carrying the same dimensions at document level. BKPF and BSEG remain the ultimate source documents behind any FAGLFLEXT total. ACDOCA is the S/4HANA successor that eliminates the separate totals table entirely. SKB1 and SKAT supply account master data for the RACCT field, and CSKS supplies cost center master data for RCNTR. Postings that update FAGLFLEXT come from standard FI document entry and period-end closing transactions rather than any direct maintenance transaction.