Do you have any question about this error?
Message type: E = Error
Message class: FH - General ledger module messages
Message number: 216
Message text: Make an entry in the "Cost Element Category" field
You have not specified a cost element category for cost account &V1&/
&V2&.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
When you create a new cost account, this is possible if the G/L account
is locked for posting at the same time.
In all other cases, the following restrictions apply:
For G/L accounts of type <ZH>Secondary Costs</>, you must specify a cost
element category.
For G/L accounts of type <ZH>Primary Costs or Revenues</>, you can
configure the system behavior.
If you leave this system message as an error message, it ensures that
when a G/L account is created or changed, a cost element category is
always specified and thus also the data in the controlling area is
always written. This is the standard SAP configuration.
If you issue the message as a warning or deactivate it entirely, the
cost element category does not have to be specified when a G/L account
is created or changed. This changes the semantics of the G/L account
type. <ZH>Primary Costs or Revenues</> then means maximum use of the G/L
account. The account can, however, also be used as a G/L account of type
<ZH>Nonoperating Expense and Income</> for the controlling
areas/company codes in which the cost element category was left empty.
If you want to subsequently maintain the controlling area data (in
particular, the cost element category) for a larger number of primary
cost elements, you can do this by using transaction <DS:TRAN.OB_GLACC14>
G/L Accounts > Collective Processing > Controlling Area Data</>.
INCLUDE 'CUSTOMIZED_MESSAGE_INFO' OBJECT DOKU ID TX
Error message extract from SAP system. Copyright SAP SE.
FH216
- Make an entry in the "Cost Element Category" field ?The SAP error message FH216, which states "Make an entry in the 'Cost Element Category' field," typically occurs when you are trying to post a transaction that requires a cost element, but the system cannot find a valid cost element category associated with the entry.
Cause:
- Missing Cost Element Category: The cost element category field is not filled in the transaction you are trying to execute. This can happen if the cost element is not defined properly in the system.
- Configuration Issues: The cost element may not be configured correctly in the system, or the relevant settings in the controlling area may not be set up.
- Transaction Type: The transaction type you are using may require a specific cost element category that is not being provided.
Solution:
Check Cost Element Configuration:
- Go to the transaction code KA01 (Create Cost Element) or KA02 (Change Cost Element) to verify if the cost element is defined correctly.
- Ensure that the cost element has a valid category assigned to it.
Fill in the Cost Element Category:
- When entering the transaction, make sure to fill in the "Cost Element Category" field if it is not automatically populated.
Review Transaction Settings:
- Check the settings for the transaction you are trying to execute. Ensure that all required fields, including the cost element category, are filled out correctly.
Consult with Configuration Team:
- If you are unsure about the configuration or if the cost element category is missing, consult with your SAP configuration team or a functional consultant who specializes in Controlling (CO) to ensure that everything is set up correctly.
Testing:
- After making the necessary changes, try to execute the transaction again to see if the error persists.
Related Information:
By following these steps, you should be able to resolve the FH216 error and successfully complete your transaction.
Get instant SAP help. Start your 7-day free trial now.
FH215
G/L account type cannot be changed because transaction data exists
What causes this issue? You want to change the G/L account type from &V1& to &V2& although there are already postings to G/L account ...
FH214
You cannot use the secondary costs account type without Controlling
What causes this issue? You created an account with account type secondary costs. You can only post to these accounts within Controlling. However, co...
FH217
You are not authorized to lock primary cost elements in CO area &1
What causes this issue? You are not authorized to lock primary cost elements in controlling area &V1&. INCLUDE NA_AUTH_K_CSKB OBJECT DOKU ID ...
FH218
You are not authorized to lock secondary cost elements in CO area &1
What causes this issue? You are not authorized to lock secondary cost elements in controlling area &V1&. INCLUDE NA_AUTH_K_CSKB OBJECT DOKU I...
Click on this link to search all SAP messages.