Do you have any question about this error?
Message type: E = Error
Message class: GI - FI-SL update
Message number: 231
Message text: Cost element & not created in company code &
You have activated plan integration of CO with FI-GL (general ledger)
and want to transfer planning data from primary cost element &V1& to the
general ledger. CO object &V3& for which you are currently transferring
the planning data is assigned to company code &V2&. However, your
primary cost element &V1& has not been created in this company code.
This is essential before you can transfer your primary cost planning
from CO to the general ledger.
The planning record is not transferred because the integration of CO
with the general ledger cannot be guaranteed for primary cost planning.
Create account &V1& in company code &V2&.
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.
GI231
- Cost element & not created in company code & ?The SAP error message GI231 indicates that a cost element has not been created in the specified company code. This error typically arises when you attempt to post a transaction that requires a cost element that does not exist in the system for the specified company code.
Cause:
- Missing Cost Element: The cost element you are trying to use has not been created in the system for the specified company code.
- Incorrect Configuration: The cost element may exist but is not properly configured for the company code in question.
- Data Entry Error: There may be a typo or incorrect entry in the transaction that references the cost element.
Solution:
Create the Cost Element:
- Navigate to the SAP Easy Access screen.
- Go to the transaction code KA01 (Create Primary Cost Element) or KA06 (Create Secondary Cost Element) depending on the type of cost element you need.
- Enter the required details, including the cost element number and the company code.
- Save the entry.
Check Existing Cost Elements:
- Use transaction code KA03 to display existing cost elements and verify if the cost element exists for the specified company code.
- If it exists but is not active, you may need to activate it or adjust its settings.
Review Configuration:
- Ensure that the cost element is properly configured in the controlling area and linked to the relevant company code.
- Check the settings in the controlling area (transaction code OKKP) to ensure that the cost element is assigned to the correct controlling area.
Correct Data Entry:
- Double-check the transaction data for any typos or incorrect references to the cost element.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in controlling (CO) to further investigate the issue.
Get instant SAP help. Start your 7-day free trial now.
GI230
User exit in ledger selection not found: &
What causes this issue? When posting directly into General Ledger, a ledger selection is used for a ledger. The selection condition contains a user e...
GI223
Update problem in totals table &
What causes this issue? An exception of class CX_SY_OPEN_SQL_DB was triggered while posting (UPDATE) to the totals table &V1&. The cause of t...
GI240
Caution when generating GLU1 - Please read long text (F1=Help)
What causes this issue? You can regenerate the internal structure GLU1 using this program. To determine the required fields, this program reads the s...
GI241
Transfer of planning data with over 53 periods not currently supported
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.