How To Fix /PRA/ADV085 - Company code & locked for post simulate for doc type & system source &.

SAP Error Message - Details

• Message type: E = Error

• Message class: /PRA/ADV -

• Message number: 085

• Message text: Company code & locked for post simulate for doc type & system source &.

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 /PRA/ADV085 - Company code & locked for post simulate for doc type & system source &. ?

  The SAP error message /PRA/ADV085 indicates that a specific company code is locked for posting simulation for a particular document type and system source. This typically occurs in the context of the SAP system's financial or controlling modules, where certain configurations or locks prevent users from simulating postings.
  Cause:
  
  
  Company Code Lock: The company code may be locked for posting simulations due to various reasons, such as:
  
  Maintenance activities or system upgrades.
  Configuration settings that restrict posting for certain document types.
  User authorizations that do not allow posting simulations for the specified company code.
  
  
  
  Document Type Restrictions: The document type specified may have restrictions that prevent simulation postings.
  
  
  System Source Issues: The source system may have specific settings or locks that affect the ability to simulate postings.
  
  
  Solution:
  
  
  Check Company Code Status:
  
  Verify if the company code is indeed locked for posting simulations. This can be done by checking the configuration settings in the SAP system.
  If the company code is locked, consult with your SAP administrator or relevant team to understand the reason for the lock and if it can be lifted.
  
  
  
  Review Document Type Settings:
  
  Check the configuration for the document type in question. Ensure that it allows for posting simulations.
  If necessary, modify the document type settings to enable posting simulations.
  
  
  
  User Authorizations:
  
  Ensure that the user attempting to perform the posting simulation has the necessary authorizations. This can be checked in the user roles and profiles.
  
  
  
  Consult SAP Notes:
  
  Look for any relevant SAP Notes that may address this specific error message. SAP Notes often provide solutions or workarounds for known issues.
  
  
  
  Contact SAP Support:
  
  If the issue persists and cannot be resolved through the above steps, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like OBY6 (for company code settings) or OBD2 (for document type settings) to check and modify configurations.
  Authorization Objects: Review authorization objects related to financial postings to ensure users have the correct permissions.
  System Logs: Check system logs for any additional error messages or warnings that may provide more context about the lock.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.