Do you have any question about this error?
Message type: E = Error
Message class: CK - Product Costing Messages
Message number: 387
Message text: No G/L account for & on &
The G/L account determined automatically for external activities for
material &V3& does not exist for the date &V2& specified.
Check the settings for automatic account determination for 'FRL'
(external activity).
Error message extract from SAP system. Copyright SAP SE.
CK387
- No G/L account for & on & ?The SAP error message CK387 ("No G/L account for & on &") typically occurs in the context of cost accounting and material management when the system cannot find a General Ledger (G/L) account for a specific transaction or posting. This error can arise during various processes, such as when trying to post a goods movement, create a cost center, or perform a valuation.
Cause:
- Missing G/L Account Assignment: The most common cause is that the G/L account has not been assigned in the relevant configuration settings for the material or cost element.
- Incorrect Configuration: The configuration for the account determination may not be set up correctly in the system.
- Inactive Account: The G/L account may be inactive or not available for the specific transaction type.
- Missing Account Assignment in Master Data: The material master or cost center may not have the necessary account assignment details filled in.
- Transaction Type Not Defined: The transaction type being used may not have a corresponding G/L account defined in the configuration.
Solution:
Check Account Determination:
- Go to the configuration settings for account determination in the SAP system (Transaction code: OBYC).
- Ensure that the appropriate G/L accounts are assigned for the relevant transaction types (e.g., stock postings, consumption, etc.).
Review Material Master Data:
- Check the material master record (Transaction code: MM03) for the material in question.
- Ensure that the accounting view is correctly set up and that the G/L accounts are assigned.
Check Cost Element Configuration:
- If the error is related to cost accounting, check the cost element configuration (Transaction code: KA01/KA02) to ensure that the cost elements are correctly defined and assigned to the appropriate G/L accounts.
Verify G/L Account Status:
- Ensure that the G/L account is active and not blocked for postings. You can check this in the G/L account master data (Transaction code: FS00).
Consult with Finance Team:
- If you are unsure about the correct G/L account to use, consult with your finance or accounting team to ensure that the correct accounts are being used for the transactions.
Testing:
- After making the necessary changes, perform a test transaction to ensure that the error no longer occurs.
Related Information:
Transaction Codes:
Documentation: Refer to SAP Help documentation for detailed guidance on account determination and material master configuration.
Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error message.
By following these steps, you should be able to identify and resolve the CK387 error in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
CK386
A routing of type & cannot be costed
What causes this issue? Costing with quantity structure can only take routings into account if they refer to a material.System Response Routings of ...
CK385
Enter a routing group for routing type &
What causes this issue? You entered a routing that does not refer to a material. For the system to be able to identify the routing, you have to ente...
CK388
Process cannot be costed with the cost estimate
What causes this issue? According to the material type, the object to be costed is a process.System Response Processes cannot be costed in material ...
CK389
Only the planned prices can be updated
What causes this issue? Costing variant &V1& only allows the planned prices to be updated.System Response The system issues an error message...
Click on this link to search all SAP messages.