2019-06-07
891144
891144 - General Ledger Accounting (new)/document
splitting: Risks of subsequent changes
Version
Language
Priority
Release Status
Component
15
English
Recommendations / Additional Info
Released for Customer
FI-GL-FL ( Flexible Structures )
Type
Master Language
Category
Released On
SAP Note
German
Consulting
23.04.2018
Please find the original document at https://launchpad.support.sap.com/#/notes/ 891144
Symptom
You want to make subsequent changes in Customizing for General Ledger Accounting
(new). In particular, these changes affect document splitting, which is used in
the context of General Ledger Accounting (new).
Making changes of this type carries certain risks, it should be noted.
Other Terms
Online splitter, Customizing, General Ledger Accounting (new), document split,
NewGL, GLT0002, GLT0 002
Reason and Prerequisites
In contrast with the special ledger or EC-PCA, subsequent changes are not
planned in General Ledger Accounting (new) since the ledgers in General Ledger
Accounting (new) are not comparable with a special ledger or EC-PCA. In fact,
General Ledger Accounting (new) is a general ledger from a business point of
view and is therefore legally comparable with the classic general ledger (GLT0
ledger 00). Thus, there is an auditing requirement.
This auditing requirement means that, prior to planned changes in Customizing
for General Ledger Accounting (new) or with regard to changes in Customizing for
document splitting, you must consider the possible business effects in terms of
the documents that have already been posted.
Such business effects also bring technical restrictions with them, which, viewed
in combination, usually forbid many subsequent changes, even if they are not
intercepted by error messages in the relevant Customizing path. Through this,
you can link your requirement to subsequently implement or change functions in
General Ledger Accounting (new) with a migration project.
Solution
As a result, the following is explicitly prohibited:
1. Unlike in the special ledger, you cannot delete or subsequently post
documents in the live General Ledger Accounting (new).
(However, in exceptional cases due to program errors, you can correct the
inconsistencies using SAP Support). Should the situation arise (for example,
when the fiscal year is closed), the external auditor must be involved from
the very start.
© 2019 SAP SE or an SAP affiliate company. All rights reserved
1 of 5
2019-06-07
891144
2. You are not allowed to subsequently change the ledger definitions or
temporarily deactivate/activate an assigned scenario or customer field (for
example, subsequent FIN_PCA assignment).
The relevant fields (characteristics) are updated in the database tables of
General Ledger Accounting (new) only after you assign a scenario to a
ledger. In the case of subsequent activation, the account assignments for
the relevant characteristics would be missing from General Ledger Accounting
(new) for documents posted previously. This is of particular relevance if
characteristics from this scenario are used in document splitting.
Background information:
a) If the characteristics are defined as mandatory in document splitting,
the fields contained in the scenario are checked the first time a scenario
is assigned. This means that subsequent processes for documents, posted
previously without being checked, may lead to an error, because account
assignments cannot be passed on from the previous processes.
b) If the general ledger characteristics are defined as financial statement
characteristics in document splitting, the generated clearing lines are only
updated in the ledgers of General Ledger Accounting (new) if the
corresponding account assignment objects are also contained in the assigned
scenarios of the ledger.
3. You cannot change the ledger definition from leading to non-leading, or
the other way around.
Compared to other applications (Controlling, Asset Accounting, and so on),
the leading ledger represents the leading valuation view. Switching the
leading ledger and another setting (for example, assignment of the
accounting principle, or the ledger group derivation from the valuation area
or from the variant of the real-time integration, or also change of the
value of BAdIs) may lead to an amalgamation of the valuation views.
4. If you want to use document splitting, Customizing for this must be
complete and correct before the posting start date.
a) You are not allowed to subsequently activate or temporarily deactivate
document splitting (either generally or for individual company codes). If
such subsequent changes were made, the system would react to certain
subsequent processes with a termination (MESSAGE_TYPE_X Class GLT0 Number
000 - Termination Point: CLEARING_BALANCE) or, as of ERP 2005, with the
error message GLT0 002 'Document splitting: Items for clearing not found'.
You cannot pay or clear documents posted before Customizing was changed. If
you want to subsequently activate document splitting, this must take place
solely as part of a very complex migration project. To meet your requirement
for subsequently activating document splitting in General Ledger Accounting
(new), a migration scenario is available to subsequently activate document
splitting 'Scenario 6: Subsequent implementation of document splitting'.
This migration scenario supports only general subsequent activation of
document splitting. Special cases, such as converting documents during
temporary deactivation or converting documents that were posted using a
temporarily different setting for document splitting, are not supported by
Support or by the migration scenario mentioned. Furthermore, this migration
scenario does not allow you to subsequently change the Customizing for
active document splitting (for example, subsequent implementation of
required entry fields for document splitting); a migration scenario of this
type has not (yet) been developed. For more information about migration, see
www.service.sap.com/glmig or contact NewGLMigration@sap.com directly.
b) You are not allowed to temporarily deactivate or subsequently activate
required entry fields in document splitting (Customizing view
V_FAGL_SPLIT_FLD). Background information: The subsequent definition of a
general ledger characteristic as a required entry field may result in the
error message GLT2 201 with regard to this characteristic, if documents
without this definition were already posted and subsequent processes
(clearing, reversal, invoice reference) were processed afterwards.
Example 1: The gross invoice (vendor, G/L account, tax) was posted
beforehand without required entry field control for a characteristic in
© 2019 SAP SE or an SAP affiliate company. All rights reserved
2 of 5
2019-06-07
891144
document splitting. At the time of posting, the G/L account was not assigned
with the characteristic that is now declared as a required entry field. The
required account assignment of the vendor line item, which is referenced in
the subsequent process (for example, clearing or reversal), is missing. The
subsequent process cannot be posted as a result of the error message.
Example 2: A document type is regulated with splitting on the basis of the
current account balance of an account to be split. If there is a balance
with initial account assignment, the document cannot be posted. The system
issues error message GLT2 201. A balance of this type with initial account
assignment is caused by a document posted before the definition was changed
(document therefore unchecked).
5. You are not permitted to subsequently activate open item management for
an account.
In particular, the conversion of documents already posted using RFSEPA02 or
ZFSEPA02 (or similar) is not permitted. The information required for
document splitting is not created, which means that items now open in this
account cannot be cleared. As of SAP Enhancement Package 3 for SAP ERP 6.0
(6.0 EHP 3), the activation of the business function FIN_GL_CI_1 makes
transaction FAGL_ACTIVATE_OP available. This enables the switchover of G/L
accounts to open item management if document splitting is used, too, as long
as certain prerequisites are met. This report cannot be used for SFIN. A
follow-on report is not delivered in the standard system at present.
6. A subsequent change to the local currency in FI, the parallel currencies,
and their value views (legal valuation, profit center valuation or group
valuation) is not permitted or is only possible in the context of an SLO
currency changeover package. Furthermore, user-selected currencies in
S/4HANA must not be added or changed without enriching or converting the
data posted. These user-selected currencies also force the implementation as
part of a currency conversion project with suitable tools for handling
historical data. S/4HANA has another restriction whereby the currency of the
controlling area must not be changed subsequently. The same also applies to
the new assignment of a company code to a controlling area or a change to
the controlling area assigned to the company code (especially with regard to
its currency).
In addition, some document splitting settings have certain side effects that you
should take into consideration:
7. Subsequent addition or change of document splitting characteristics
The document splitting characteristics are taken into account only after you
activate or transport the change. This new characteristic is not filled in
the case of newly posted subsequent processes for documents posted before
the change.
This also applies to the additional characteristics for Controlling and
reactivation of fixed assets. A subsequent activation of the Zero Balance
Creation for a document splitting characteristic takes effect only once you
have activated or transported the change. Before the activation, make sure
that the financial statement for this characteristic balances to zero by
means of a transfer posting.
8. Changing the classification of G/L accounts (item category assignment)
may lead to errors in document splitting.
Because of the change to the classification, usage of this account may be
prevented by an error message in certain business transactions.
Certain business transactions require specific item categories. For example,
the Payment business transaction requires the Cash Account item category
(04000) in the standard system. If the classification of the bank account is
changed, the business transaction can no longer be posted using this
account. When you change the classification, rule-based handling of this
account in document splitting changes in the business processes.
© 2019 SAP SE or an SAP affiliate company. All rights reserved
3 of 5
2019-06-07
891144
For this reason, a line item previously assigned by document splitting leads
to an error because it remains unprocessed after the change.
9. A subsequent change of the classification for the document types may lead
to inconsistent account assignment.
If the original account assignment of the document that is to be reversed is
not restored during a reversal (inverse posting), the system derives the
currently assigned rule in document splitting. If the assignment was
changed, the account assignment determined may deviate from that of the
document to be reversed. This leads to the reversal document and the
document to be reversed coming apart in terms of their account assignment.
As a result of the reversal document, the balances for the account
assignments are not reduced correctly in this case. The same effect may
occur if the rule assigned to the business transaction is changed.
10. Changing the zero balance clearing accounts or the account key may lead
to inconsistencies when you carry out a reversal.
Since account determination also takes place for the clearing accounts in
the case of reversal postings, in the case of a reversal, posting takes
place to an account other than that for the original document. 10. The first
definition of a scenario or customer field in the ledger update activates
the validation (check of required entry fields) in document splitting as
long as these are defined as characteristics in document splitting and
validation is active. This can mean that business transactions can no longer
be posted. Background information: Document splitting checks only those
fields that the current document also updates in the general ledger. For
example, if you post a document for a ledger group, the system checks only
the fields that are also assigned to the ledgers affected.
Software Components
Software Component
Release
SAP_APPL
500 - 500
SAP_APPL
600 - 600
SAP_APPL
602 - 602
SAP_APPL
603 - 603
SAP_APPL
604 - 604
SAP_APPL
605 - 605
SAP_FIN
617 - 617
SAP_FIN
618 - 618
SAP_FIN
700 - 700
SAP_FIN
720 - 720
SAP_FIN
730 - 730
S4CORE
100 - 100
© 2019 SAP SE or an SAP affiliate company. All rights reserved
4 of 5
2019-06-07
891144
S4CORE
101 - 101
S4CORE
102 - 102
This document refers to
SAP Note/KBA
Title
1655209
Error F5234 Fiscal year variant is incorrect when using transaction FB50L
1619168
Overview of the different migration scenarios
1086181
Subsequent implementation of document splitting
1085921
Document split
1039346
Q&A: RCIPE00/RPCIPE01 - distribution of liabilities
This document is referenced by
SAP
Note/KBA
Title
1812498
SAP FI: error in program RFUMSV50: "Balancing field "YYY" in line item XXX not filled"
2721469
Business Area is not displayed in General Ledger View
2721527
Business Area is not updated to specific ledger
2707834
Error message GLT2201 or GLT2001, or unexpected document splitting results in transaction
PRRW
2216212
Error GLT2201 Balancing field not filled on MR8M Reversal
1727802
Business area missing in sales/ purchase tax items
2580138
Splitting Rule for Residual Item Posting in Invoice Currency
2442923
BADI ACTIVATE_CC_SPLIT - Partner assignments on company code clearing lines
1085921
Document split
1039346
Q&A: RCIPE00/RPCIPE01 - distribution of liabilities
1619168
Overview of the different migration scenarios
© 2019 SAP SE or an SAP affiliate company. All rights reserved
5 of 5