SAP Knowledge Base Article - Public

3016757 - Balance Carryforward Postings

Symptom

You would like to understand the background of balance carryforward postings.

Image/data in this document is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Environment

SAP S/4HANA Cloud

Reproducing the Issue

From backend, you will find these entries in table ACDOCA with Transac. Type = ‘RFBC’ and Doc.status / BSTAT = ‘C’.

From frontend, you should not see these balance carryforward entries as these entries are only to be used by the totals display and they are aggregated on the fly by the database. Only the aggregation has a meaning. Unexpected, there is a chance for user to see those entries in case they use API or CDS view (e.g. I_GLAccountLineItem) to get the data from S/4HC system when missing restrictions. In the special case, please do not use these document numbers and see the resolution part below.

Cause

Please see details below.

Resolution

These entries are not "normal" FI documents, they are technical entries (with some sequence number in Document Number/Line Item). Please see some examples below:
Field Label >>  Ledger Company Code Fiscal Year Document Number  Line Item  Bus. Transac. Type Posting Period Doc.status
Field Name >> BLDNR RBUKRS           GJAHR       BELNR                   DOCLN     BTTYPE                  POPER            BSTAT

                      0L     1010                2021          B000000087          000001     RFBC                     000               C          
                      0L     1010                2021          B000000087          000002     RFBC                     000               C          
                      0L     1010                2021          B000000087          000003     RFBC                     000               C

In general, the 'Artificial' Document numbers are typically with first letters B. In other words, table ACDOCA-BELNR: B* refers to balance carry forward. However, when there are already documents with external numbering that (by chance) start with B. The system automatically uses a fixed different letter.

All balance carry forward entries have PostingPeriod/POPER =‘000’ and Doc. status/BSTAT = ‘C’ (In general, only documents with BSTAT = space, L or U are "normal" FI documents). Hence in case you get the data unexpected when using CDS views, you can either use PostingPeriod/POPER <> ‘000’ or use Doc. status/BSTAT <> ‘C’ to exclude the balance carry forward entries.

In case someone Reset the Balance Carryforward, these entries are deleted and rebuild. 
For example, if the BCF job scheduled for company code 1010/ ledger 0L is canceled finally(please see the status in app "Balance Carryforward Status"), then the entry B000000087 will be deleted accordingly.

See Also

3014633 - Technical Background to Automatic Scheduling of Balance Carryforward Runs

Balance Carryforward

Keywords

Balance Carry Forward Entries, RFBC, ACDOCA, B*, PostingPeriod, POPER, 000, Balance Carry Forward Status, Doc.status, BSTAT, F4683 , KBA , FI-FIO-GL , Fiori UI for General Ledger Accounting , How To

Product

SAP S/4HANA Cloud all versions