How To Fix 67190 - Client &1, CoCd &2, contract &3, cond.type &: posting control not allowed

SAP Error Message - Details

• Message type: E = Error

• Message class: 67 - Loans Messages - Financial Assets Management

• Message number: 190

• Message text: Client &1, CoCd &2, contract &3, cond.type &: posting control not allowed

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 67190 - Client &1, CoCd &2, contract &3, cond.type &: posting control not allowed ?

  The SAP error message 67190 typically indicates that there is an issue with the posting control for a specific condition type in a contract. This error can occur in various scenarios, particularly in the context of pricing and billing in SAP SD (Sales and Distribution) or MM (Materials Management) modules.
  Cause:
  The error message "posting control not allowed" suggests that the system is trying to post a condition type that is not allowed for the specified client, company code, or contract. This can happen due to several reasons:
  
  
  Configuration Issues: The condition type may not be configured correctly in the system. This includes settings related to pricing procedures, condition records, or account determination.
  
  
  Authorization Issues: The user may not have the necessary authorizations to post the specific condition type.
  
  
  Contract Status: The contract associated with the error may be in a status that does not allow posting (e.g., it may be inactive or closed).
  
  
  Client/Company Code Settings: The client or company code may have specific settings that restrict certain postings.
  
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Configuration:
  
  Go to the SPRO transaction and navigate to the relevant configuration for pricing procedures and condition types.
  Ensure that the condition type in question is correctly configured and allowed for the relevant client and company code.
  
  
  
  Review Condition Records:
  
  Check if there are valid condition records for the condition type in question. If there are no records, the system may not allow posting.
  
  
  
  Verify Contract Status:
  
  Check the status of the contract associated with the error. Ensure that it is active and open for posting.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to perform the posting. This can be checked in the user roles and profiles.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific condition type and posting control to understand any additional restrictions or requirements.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the process to identify the exact point of failure. This may require assistance from a technical consultant.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like VK11 (Create Condition), VK12 (Change Condition), or VK13 (Display Condition) to manage condition records.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on this error.
  Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.