FI Report Custom development ALV report

General Ledger Consistency and Trading Partner / Transaction Type Check Report

Short answer: A check report run before period-end close. It compares G/L account balances with the line items and the line items with the open item indexes; it lists postings on intercompany accounts with a missing trading partner and items on accounts that need a transaction type (fixed assets, equity) with a missing or wrong transaction type. Every item to correct before consolidation is shown with its document number.

Estimated effort
M · 8–12 working days
System
ECC and S/4HANA
Tables
11
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

The standard has separate tools for balance-to-item consistency: FINS_RECON_RC1 in S/4HANA, SAPF190 and RFINDEX in ECC, FAGLF03 and TFC_COMPARE_VZ in new G/L. They find technical inconsistencies but do not flag intercompany postings with an empty trading partner or equity and fixed asset postings with a missing transaction type. These errors usually surface in consolidation as matching differences and require corrections after the fact.

Who uses it? General ledger and closing teams, the consolidation team, finance managers and internal audit.

Closest standard alternatives

  • FAGLF03 General Ledger Reconciliation. Compares new G/L totals with line items; does not check trading partner or transaction type.
  • FAGLL03 G/L Account Line Items (New). Can list line items with trading partner and transaction type; does not flag missing values by rule.
  • FS10N Balance Display. Shows the account balance; performs no consistency check.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
ACDOCAUniversal Journal Entry Line ItemsUniversal Journal items: account, trading partner, transaction type, amount (S/4HANA driving table)—S/4HANA only
BKPFAccounting Document HeaderDocument header: document type, posting date, userBKPF-BUKRS = ACDOCA-RBUKRS AND BKPF-BELNR = ACDOCA-BELNR AND BKPF-GJAHR = ACDOCA-GJAHRECC + S/4
BSEGAccounting Document SegmentDocument items, trading partner and transaction type (ECC)BSEG-BUKRS = BKPF-BUKRS AND BSEG-BELNR = BKPF-BELNR AND BSEG-GJAHR = BKPF-GJAHRECC only
FAGLFLEXTNew General Ledger: TotalsNew G/L period totals (ECC)FAGLFLEXT-RBUKRS = BSEG-BUKRS AND FAGLFLEXT-RACCT = BSEG-HKONTECC only
GLT0G/L Account Transaction FiguresClassic G/L totals (ECC, when new G/L is not active)GLT0-BUKRS = BSEG-BUKRS AND GLT0-RACCT = BSEG-HKONTECC only
BSISG/L Account Open Items (Secondary Index)G/L open item indexBSIS-BUKRS = BKPF-BUKRS AND BSIS-BELNR = BKPF-BELNR AND BSIS-GJAHR = BKPF-GJAHRECC + S/4
BSASG/L Account Cleared Items (Secondary Index)G/L cleared item indexBSAS-BUKRS = BKPF-BUKRS AND BSAS-BELNR = BKPF-BELNR AND BSAS-GJAHR = BKPF-GJAHRECC + S/4
SKB1G/L Account Master (Company Code)Open item management and reconciliation account flag of the accountSKB1-BUKRS = ACDOCA-RBUKRS AND SKB1-SAKNR = ACDOCA-RACCTECC + S/4
KNA1Customer Master (General Section)Customer's trading partner in master dataKNA1-KUNNR = ACDOCA-KUNNRECC + S/4
LFA1Vendor Master (General Section)Supplier's trading partner in master dataLFA1-LIFNR = ACDOCA-LIFNRECC + S/4
T001Company CodesCompany code, currency and chart of accountsT001-BUKRS = ACDOCA-RBUKRSECC + S/4

S/4HANA notes

  • FAGLFLEXT → ACDOCA: In S/4HANA totals tables are no longer updated separately; FAGLFLEXT is read as a compatibility view that aggregates ACDOCA line items.
  • GLT0 → ACDOCA: In S/4HANA GLT0 is not updated; reads go through a compatibility view that aggregates ACDOCA line items.
  • BSIS → ACDOCA: In S/4HANA BSIS is no longer filled as a separate index table; it is read through a compatibility view of the same name. New developments should use ACDOCA or the related CDS views.
  • BSAS → ACDOCA: In S/4HANA BSAS is not filled as a separate table; it is read through a compatibility view of the same name. New developments should prefer ACDOCA or the related CDS views.

BAPIs and functions used

  • BAPI_GL_GETGLACCPERIODBALANCESGet G/L Account Period Balances. Reads the period balances of a G/L account
  • SO_NEW_DOCUMENT_ATT_SEND_API1SAPoffice: Send New Document with Attachments. Sends the summary to the people responsible for the close

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_BUKRSCompany codeRange / multipleACDOCA-RBUKRSYes1000
P_GJAHRFiscal yearSingle valueACDOCA-GJAHRYes2026
S_POPERPeriodRange / multipleACDOCA-POPERYes010 – 011
S_RACCTG/L accountRange / multipleACDOCA-RACCTNo100000 – 899999
P_CHK1Balance vs. line item checkCheckbox—NoX
P_CHK2Line item vs. open item checkCheckbox—NoX
P_CHK3Trading partner checkCheckbox—NoX
P_CHK4Transaction type checkCheckbox—NoX

Output columns

#ColumnSource
1CheckCalculated Balance vs. item, item vs. open item, trading partner or transaction type
2Company codeACDOCA-RBUKRS
3G/L accountACDOCA-RACCT
4PeriodACDOCA-POPER
5DocumentACDOCA-BELNR
6Amount (LC)ACDOCA-HSL
7Trading partnerACDOCA-RASSC
8Expected partnerCalculated VBUND from customer/supplier master data
9Transaction typeACDOCA-RMVCT
10DifferenceCalculated Difference between totals and item/index totals in the balance checks
11SuggestionCalculated Suggested correction

Sample output

CheckCompany codeG/L accountPeriodDocumentAmount (LC)Trading partnerExpected partnerTransaction typeDifferenceSuggestion
Trading partner10001205000101400002345185,0002000Add trading partner 2000 to the document
Transaction type10005000000101700000112-2,500,000Enter the transaction type for the capital increase
Item vs. open item1000320900011510000441712,45012,450Open item index missing; check with support
Trading partner20003201000115100000981-76,30030001000Trading partner contradicts master data
Balance vs. item300015300001100No difference
A view built with fictional sample data; not real system data.

How does the report work?

  1. Check 1 – balance vs. line items: in S/4HANA, ACDOCA period totals per account and period are compared with the result of the G/L balance query (BAPI_GL_GETGLACCPERIODBALANCES). In ECC, FAGLFLEXT (or GLT0 in classic G/L) totals are compared with BSEG/BSIS/BSAS item totals.
  2. Check 2 – line items vs. open items: on open-item-managed accounts (SKB1-XOPVW) the BSIS and BSAS index amounts are compared with the line item amounts; items missing from or surplus in the index are listed.
  3. Check 3 – trading partner: on accounts flagged as intercompany during installation, or on postings to customers/suppliers that carry a trading partner in master data (KNA1/LFA1-VBUND), the item is flagged when ACDOCA-RASSC (BSEG-VBUND in ECC) is empty or contradicts the master data.
  4. Check 4 – transaction type: on accounts that feed the equity and fixed asset movement schedules, the item is flagged when ACDOCA-RMVCT (BSEG-BEWAR in ECC) is empty or not in the list of transaction types allowed for the account. Transaction types are validated against T856 and intercompany companies against T880.
  5. The result is grouped by check type; every line shows company code, account, document, amount and the suggested correction. Clicking the document number opens FB03.
  6. Optionally the result is emailed as a summary to the people responsible for the close.

Performance notes

Restrict ACDOCA by company code, fiscal year and period; in the trading partner and transaction type checks read only the accounts flagged during installation. Compare balances on account and period totals, not at line item level. For large company codes run the report in the background overnight.

Features

  • ALV list (sort, filter, subtotals)
  • Double-click drill-down to the document Drill down from the document number to FB03.
  • Runs as a background job Runs as an overnight job before the closing calendar.
  • Send the result by email
  • Export to Excel

Authorization objects

  • F_BKPF_BUKDisplay of accounting documents by company code
  • F_SKA1_BUKDisplay of G/L accounts by company code

Frequently asked questions

Does this report replace the standard consistency programs?

No. If a technical inconsistency is found, the standard programs (FINS_RECON_RC1 in S/4HANA, SAPF190 and RFINDEX in ECC) and, if needed, SAP support are used for the correction. The report brings their result together with the trading partner and transaction type checks in one list.

How do we correct a posting with a missing trading partner?

It depends on the posting: for items not yet cleared, a document change or a reversal and new posting is made. For a lasting fix, the trading partner field should be filled in customer and supplier master data and made mandatory on intercompany accounts.

How is it decided which accounts need a transaction type?

During installation a mapping table defines account ranges and the transaction types allowed for them (equity, fixed asset, provision accounts and so on). The report uses this table; the consolidation team can maintain the list itself.

Related reports

FI Program Custom Mass upload

Mass G/L Journal Entry Upload from Excel

A custom program that posts multi-line G/L documents (accruals, reclassifications, allocation entries) in bulk from Excel or CSV rows. It checks every …

BKPF · BSEG · SKB1 · CSKS

FI Report Custom ALV report

Intercompany Open Items Reconciliation Report

A custom ALV report that matches receivable and payable open items between group companies by trading partner and reference number. Before the …

BSID · BSIK · KNA1 · LFA1

Let us build this report for your system

Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.

Related report: General Ledger Consistency and Trading Partner / Transaction Type Check Report