How To Fix FH198 - &1 not permitted for secondary costs

FH198 - Overview

• Message type: E = Error

• Message class: FH - General ledger module messages

• Message number: 198

• Message text: &1 not permitted for secondary costs

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FH198 - &1 not permitted for secondary costs ?

  The SAP error message FH198 typically indicates that a certain operation is not permitted for secondary costs in the context of controlling (CO) or financial accounting (FI). This error often arises when trying to post or process secondary cost elements in a way that is not allowed by the system configuration or business rules.
  
  Cause:
  
  
  Secondary Cost Elements: The error usually occurs when you attempt to post a transaction that involves secondary cost elements (like internal activity allocations, assessments, or distributions) in a manner that is not allowed. Secondary cost elements are used for internal cost allocations and cannot be used for direct postings like primary cost elements.
  
  
  
  Configuration Issues: There may be configuration settings in the controlling module that restrict the use of secondary cost elements for certain types of transactions.
  
  
  Transaction Type: The transaction you are trying to execute may not support secondary costs, or you may be using the wrong transaction