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

SAP Error Message - Details

• Message type: E = Error

• Message class: /PRA/RD -

• Message number: 059

• Message text: Company code & locked for post 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/RD059 - Company code & locked for post for doc type & system source &. ?

  The SAP error message /PRA/RD059 Company code & locked for post for doc type & system source & typically indicates that the specified company code is locked for posting transactions related to a specific document type and system source. This can occur for various reasons, and understanding the cause is essential for resolving the issue.
  Causes:
  
  
  Company Code Locking: The company code may be locked for posting due to various reasons, such as:
  
  Year-end closing activities.
  Period-end closing activities.
  Manual locking by a user or administrator.
  Configuration settings that restrict posting for certain document types.
  
  
  
  Document Type Restrictions: The document type specified in the error message may have specific restrictions that prevent postings during certain periods or under certain conditions.
  
  
  System Source Issues: The system source may refer to a specific configuration or environment that is not allowing postings, possibly due to settings in the configuration.
  
  
  Solutions:
  
  
  Check Company Code Locking:
  
  Navigate to the transaction code OB52 (or OB53 for special periods) to check if the posting period is open for the company code in question.
  If the period is closed, you may need to open it temporarily to allow postings or consult with your finance team regarding the closing process.
  
  
  
  Review Document Type Settings:
  
  Check the configuration for the document type in transaction code OBA7 to ensure that it is allowed for posting in the current period.
  Make sure that the document type is not restricted for the company code in question.
  
  
  
  Consult with System Administrator:
  
  If the issue persists, consult with your SAP system administrator or finance team to understand if there are any specific locks or configurations that need to be addressed.
  
  
  
  Check for User Locks:
  
  Ensure that no user has locked the company code for posting. This can be checked in transaction SM12 (for user locks).
  
  
  
  Review Configuration Settings:
  
  Review any custom configurations or enhancements that may affect posting behavior for the company code and document type.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  OB52: Change Posting Periods
  OBA7: Document Type Configuration
  SM12: Display and Delete Locks
  OB53: Special Periods Configuration
  
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search the SAP Support Portal for relevant notes.
  
  
  Documentation: Review SAP documentation related to financial closing processes and posting periods for more detailed guidance.
  
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it.