How To Fix >0172 - Cross-company postings not permitted for document type &1

SAP Error Message - Details

• Message type: E = Error

• Message class: >0 - General Basis texts

• Message number: 172

• Message text: Cross-company postings not permitted for document type &1

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 >0172 - Cross-company postings not permitted for document type &1 ?

  The SAP error message 0172 ("Cross-company postings not permitted for document type &1") typically occurs when you attempt to post a financial document that involves multiple company codes using a document type that does not allow cross-company postings. This is a common issue in SAP's Financial Accounting (FI) module.
  Cause:
  
  Document Type Configuration: The document type you are using is configured to restrict cross-company postings. Each document type in SAP can be set up with specific rules regarding whether it allows postings between different company codes.
  Company Code Settings: The company codes involved in the transaction may not be set up to allow cross-company transactions.
  Transaction Type: The type of transaction you are trying to perform (e.g., certain types of journal entries, invoices, etc.) may not support cross-company postings.
  
  Solution:
  
  
  Check Document Type Configuration:
  
  Go to the transaction code OBAY (or SPRO -> Financial Accounting -> Financial Accounting Global Settings -> Document -> Document Types -> Define Document Types).
  Find the document type indicated in the error message and check its settings. Ensure that it is configured to allow cross-company postings if that is your intention.
  
  
  
  Use a Different Document Type:
  
  If the current document type does not allow cross-company postings, consider using a different document type that does permit such transactions.
  
  
  
  Review Company Code Settings:
  
  Ensure that the company codes involved in the transaction are set up correctly to allow cross-company transactions. This can be checked in the configuration settings for each company code.
  
  
  
  Transaction Type:
  
  Verify that the transaction you are trying to perform is appropriate for cross-company postings. If it is not, you may need to adjust your approach or use a different transaction.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with your SAP support team for specific guidance related to your organization's configuration and policies regarding cross-company postings.
  
  
  
  Related Information:
  
  Cross-Company Code Transactions: These transactions typically involve transferring assets, liabilities, or expenses between different company codes within the same client.
  Document Types: Document types in SAP are used to categorize financial transactions and can have specific rules associated with them, including whether they allow cross-company postings.
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions related to this error message.
  
  If the issue persists after checking the above points, it may be beneficial to engage with your SAP support team or a consultant who can provide more tailored assistance based on your specific SAP environment and configuration.