3721544 - Duplicate Journal Entries in Ledger with a shifted fiscal year

In Display Line Items in General Ledger (App ID  F2217)/ Manage Journal Entries (App ID F0717A) duplicate journal entries document numbers exist for Company Code and Fiscal Year of Ledger. The Fiscal Year is different.

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

SAP S/4HANA Cloud Public Edition 

Example In App Display Line items in General Ledger following entries shown for Ledger 2L 

Each combination of ledger and company code can have its own fiscal year variant.  

During posting, the fiscal year is derived from the representative ledger in the ledger group, usually this is the leading ledger. If the posting is without a ledger group, the fiscal year is derived through the leading ledger.

The fiscal year of another ledger involved may differ. The Fiscal Year (GJAHR) field is the fiscal year of the leading ledger/representative ledger, whereas the Fiscal Year of Ledger (RYEAR) field is the fiscal year of the current ledger.

Each posting affecting multiple ledgers uses a single journal-entry number. i.e. The accounting document number is a universal document number which is the same in all ledgers updated by the document. Because the number is tied to a fiscal year and ledgers can use different fiscal-year variants, the journal number follows the fiscal year of the leading ledger when fiscal year variants differ. Accordingly, the data model records the leading ledger’s fiscal year and uses it for document numbering in cross-ledger postings. 

For ledger group specific documents (e.g. asset depreciation, CO settlement, foreign currency revaluation, manual document assigned to a ledger group) the universal document number is derived from the number range and fiscal year of the representative ledger of the ledger group, which is the fiscal year in field Fiscal Year of the Ledger (RYEAR) = The Fiscal Year (GJAHR) in such documents.

Therefore there can be a duplicate number in the year of the shifted ledger. This is be design. 

As there can be a duplicate number in the year of the shifted ledger. It is necessary to take the Fiscal Year of the leading ledger also in the non leading ledger to have a unique number.

In order to get a unique number you can concatenate the fiscal year of leading ledger with the journal entry document number. 

Fiscal Year and Fiscal Year Variant

In-Depth with SAP S/4HANA – Ledger Scoping Q&A  -  see section: fiscal year and posting period variants: 

non leading ledger, acdoca, bkpf, GJAHR, RYEAR, General Ledger Fiscal Year,  different fiscal year variants  , KBA , FI-GL-GL-2CL , Basic Functions (Public Cloud) , How To