Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing
Message number: 385
Message text: Customizing is inconsistent: Postings of journal entries not possible
Currently the customizing settings are not yet consistent.
<ZH>As long as inconsistencies exists, the posting of journal entries
will not be possible in the affected company codes and ledgers.</>
Note: Within customizing activities, the system sends only warning
message instead of error messages for the detected inconsi
stencies in order to enable saving the customizing settings despite
inconsistencies exist. But if you try to post a journal entry, the
system will regard the inconsistencies as errors.
Correct your customizing settings to solve the existing inconsistencies.
As soon as the inconsistencies are solved, the posting of journal
entries will be possible.
You can check the consistency of the customizing settings using
either transaction
<DS:TRAN.FINS_CUST_CONS_CHK>FINS_CUST_CONS_CHK</> for all company codes
and ledgers
or transaction
<DS:TRAN.FINS_CUST_CONS_CHK_P>FINS_CUST_CONS_CHK_P</> for a single
company code and ledgergroup.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
FINS_ACDOC_CUST385
- Customizing is inconsistent: Postings of journal entries not possible ?The SAP error message FINS_ACDOC_CUST385 indicates that there is an inconsistency in the customizing settings related to the posting of journal entries. This error typically arises when the system detects that certain configurations required for posting financial documents are not aligned or are missing.
Causes:
- Missing Configuration: The necessary customizing settings for the document types, account types, or other related financial settings may not be properly configured.
- Inconsistent Document Types: The document types used in the journal entries may not be correctly defined or linked to the appropriate ledger or account types.
- Missing or Incorrect Account Assignment: The accounts assigned to the journal entries may not be valid or may not exist in the system.
- Authorization Issues: The user may not have the necessary authorizations to post journal entries, leading to this error.
- Inconsistent Settings Across Company Codes: If the settings are not consistent across different company codes, it can lead to this error.
Solutions:
Check Customizing Settings:
- Go to the SAP Customizing Implementation Guide (SPRO) and verify the settings for Financial Accounting (FI) and General Ledger (G/L) accounting.
- Ensure that all necessary configurations for document types, account types, and other related settings are correctly defined.
Review Document Types:
- Check the document types used in the journal entries to ensure they are correctly configured and linked to the appropriate accounts and ledgers.
Validate Account Assignments:
- Ensure that the accounts used in the journal entries are valid and exist in the system. Check for any missing accounts or incorrect account assignments.
Check User Authorizations:
- Verify that the user attempting to post the journal entries has the necessary authorizations. This can be done by checking the user roles and profiles in the system.
Consistency Across Company Codes:
- If you are working with multiple company codes, ensure that the customizing settings are consistent across all relevant company codes.
Consult SAP Notes:
- Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates that resolve known issues.
Testing in a Development Environment:
- If possible, replicate the issue in a development or test environment to identify the specific configuration causing the inconsistency.
Related Information:
OBY6
(for company code settings), OBD2
(for document types), and OB52
(for posting periods) to check and adjust the relevant settings.By following these steps, you should be able to identify and resolve the inconsistency causing the error message FINS_ACDOC_CUST385.
Get instant SAP help. Sign up for our Free Essentials Plan.
FINS_ACDOC_CUST384
Internal error in ML currency configuration for company code &1
What causes this issue? An internal error occurred when querying the material ledger currency configuration for company code &V1&. Technical ...
FINS_ACDOC_CUST383
Valuation view &2 is not allowed for the leading ledger &1
What causes this issue? In the IMG activity <DS:SIMG.FINSVC_LEDGER>Define Settings for Ledgers and Currency Types</> you have assigned th...
FINS_ACDOC_CUST386
Ledgergoup &1 does not contain ledger &3; company code &2
What causes this issue? In the Customizing activity <ls>Set Up Integration with G/L for Parallel Cost of Goods Manufactured</> you have e...
FINS_ACDOC_CUST387
Segmentation unit field &1 does not exist in table &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.