Do you have any question about this error?
Message type: E = Error
Message class: GLT1 - Split processor: Maintain control tables
Message number: 405
Message text: Die Aktivierung der Belegaufteilung kann zu Inkonsistenzen führen.
In a <ZH>production system</>, activating document splitting
subsequently in the company code can cause <ZH>serious inconsistencies
</> in document processing. Note that the changes to the Customizing
settings do not make corresponding adjustments to any transaction data
already present prior to the activation of document splitting.
&DEPENDENCIES&
If you activate document splitting subsequently, document splitting is
only applied <ZH>as of the point in time when the change is made</>. If
there is transaction data for this company code either in the current
system or in the target system for the changes to the Customizing
settings, the following points must be considered:
Since there has not been an account assignment projection corresponding
to the defined document splitting characteristics for the documents
posted previously, account assignments cannot be made completely for the
documents already entered in the company code. The actual changes to the
Customizing settings do not make corresponding adjustments to any
transaction data already present prior to the activation of document
splitting. Consequently, the follow-on processes for documents that
already exist do not have complete account assignments either.
If the <ZH>check on the required entry fields</> is activated for one or
more of the document splitting characteristics, the subsequent
activation of document splitting in the company code can cause error
messages to be issued in follow-on processes involving documents that
have already been posted but contain insufficient account assignments.
The subsequent activation of document splitting in the company code with
a check on the required entry fields may only be occur for this company
code as part of migration.
Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.
<ZH>Example:</>The document splitting characteristics and the rules for document
splitting need to be configured completely before document splitting is
activated and before a company code is used productively. It is
difficult to correct incomplete settings after the productive start.
<ZH>If production data has already been entered in the company code, we
recommend not subsequently activating document splitting in the company
code if possible</>. However, if the change is required, you need to
perform a check on the data posted previously to ensure that subsequent
problems do not occur in production systems.
Check whether the desired changes to the Customizing settings are
<ZH>essential</>. Ensure that the changes you make to the Customizing
settings do not have any critical consequences. For detailed information
on this subject, see <ZH>SAP Note 891144</>.
Any transaction data present must also be converted accordingly. Note
that there are currently no standardized migration tools available for
converting transaction data that has already been posted. For detailed
and up-to-date information on this subject, see <ZH>SAP Note 812919</>.
Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
GLT1404 Die Aktivierung der Belegaufteilung kann zu Inkonsistenzen führen.
Was verursacht dieses Problem? In a <ZH>production system</>, act...
GLT1403 Geben Sie für die Standardkontierung eine Konstante an.
Selbsterklärende Nachricht Da SAP der Meinung ist, dass diese spezielle Fehlerm...
GLT1406 Die nachträgliche Änderung der Merkmale kann zu Inkonsistenzen führen
Was verursacht dieses Problem? In a <ZH>production system</>, the...
GLT1407 Nachrichten der Customizingprüfung
Selbsterklärende Nachricht Da SAP der Meinung ist, dass diese spezielle Fehlerm...
SAP-Meldungen fallen in 3 verschiedene Kategorien:
Fehlermeldungen (Meldungstyp = E), Warnungen (W) oder
Informationsmeldungen (I).
Eine Fehlermeldung hindert Sie daran, Ihre Arbeit fortzusetzen – es ist ein harter Stopp und Sie müssen den Fehler beheben, bevor Sie fortfahren können. Eine Warnmeldung stoppt Ihre Arbeit, Sie können die Warnung jedoch umgehen, indem Sie die Eingabetaste auf Ihrer Tastatur drücken. Dennoch ist es empfehlenswert, die Ursache der Warnmeldung zu untersuchen und zu beheben. Eine Informationsnachricht wird Ihre Arbeit nicht stoppen und dient wirklich nur zu Informationszwecken.
Klicken Sie auf diesen Link, um alle SAP-Meldungen durchsuchen.