Do you have any question about this error?
Message type: E = Error
Message class: FKKFMCHK_CUSTOM - Customizable Messages for Funds Management
Message number: 001
Message text: G/L account &1 does not have any default commt items in company code &2
To ensure a correct update of <LS>Contract Accounts Receivable and
Payable</> in <LS>Funds Management</>, when you post a document,
the system checks whether the financial transaction of the commitment
item entered in <LS>Contract Accounts Receivable and Payable</>
corresponds to the financial transaction of the commitment item assigned
in the general ledger account.
In this case, no commitment item is defined in the general ledger
account assigned.
The document is not posted.
Assign an appropriate commitment item to the general ledger account and
repeat the posting.
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.
FKKFMCHK_CUSTOM001
- G/L account &1 does not have any default commt items in company code &2 ?The SAP error message FKKFMCHK_CUSTOM001 indicates that a General Ledger (G/L) account does not have any default commitment items assigned in the specified company code. This error typically arises in the context of Financial Accounting (FI) and Controlling (CO) when dealing with commitment accounting, particularly in Public Sector or similar environments where commitment items are used.
Cause:
The error occurs due to the following reasons:
- Missing Configuration: The G/L account specified in the error message has not been configured with any default commitment items in the specified company code.
- Incorrect Account Assignment: The account being used in a transaction does not have the necessary commitment item settings, which are required for the transaction to proceed.
- Data Entry Error: There may be a mistake in the account number or company code being referenced in the transaction.
Solution:
To resolve this error, you can take the following steps:
Check G/L Account Configuration:
- Go to the transaction code OBYC or FS00 to check the configuration of the G/L account.
- Ensure that the G/L account has the appropriate commitment items assigned for the relevant company code.
Assign Commitment Items:
- If the commitment items are missing, you will need to assign them. This can typically be done in the configuration settings for the G/L account.
- Navigate to the relevant configuration path in SPRO:
- Public Sector Management > Commitment Accounting > Define Commitment Items.
- Ensure that the commitment items are correctly linked to the G/L account.
Review Company Code Settings:
- Ensure that the company code settings are correctly configured to allow for commitment accounting.
- Check if the company code is active and properly set up in the system.
Test the Configuration:
- After making the necessary changes, perform a test transaction to ensure that the error no longer occurs.
Consult Documentation:
- If you are unsure about the configuration steps, refer to SAP documentation or consult with your SAP support team for guidance.
Related Information:
By following these steps, you should be able to resolve the FKKFMCHK_CUSTOM001 error and ensure that your G/L accounts are properly configured for commitment accounting.
Get instant SAP help. Start your 7-day free trial now.
FKKFMCHK_CUSTOM000
Do not use
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FKKFMCHK100
The interval was processed with no errors
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FKKFMCHK_CUSTOM002
Fin. trans. for commit. item &1 in acct &2 and commit. item &3 are diff.
trados = docu -> fi -> ficaWhat causes this issue? To ensure a correct update of <LS>Contract Accounts Receivable and Payable</> i...
FKKFMCHK_CUSTOM003
Down payment/payment on account not relevant for update
What causes this issue? Payments on account and down payments must always have a commitment item with financial transaction 30 in the business partne...
Click on this link to search all SAP messages.