How To Fix CO270 - Access control is currently being processed (display only)

SAP Error Message - Details

• Message type: E = Error

• Message class: CO - PPC order processing messages

• Message number: 270

• Message text: Access control is currently being processed (display only)

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 CO270 - Access control is currently being processed (display only) ?

  The SAP error message CO270, which states "Access control is currently being processed (display only)," typically occurs in the context of controlling and cost accounting modules, particularly when dealing with internal orders, cost centers, or other controlling objects. This message indicates that the system is currently processing access control checks, and as a result, the user is restricted to display-only mode for the relevant data.
  Cause:
  
  Concurrent Processing: The error often arises when another user or process is currently accessing or modifying the same data. This can lead to a lock situation where the system prevents other users from making changes until the first process is completed.
  Authorization Issues: The user may not have the necessary authorizations to perform the action they are attempting, leading to a restriction in access.
  System Configuration: Certain configurations in the SAP system may enforce display-only access under specific conditions, such as during a period-end closing process.
  
  Solution:
  
  Wait and Retry: If the issue is due to concurrent processing, waiting for a few moments and then retrying the action may resolve the issue.
  Check Locks: Use transaction code SM12 to check for any locks on the relevant objects. If you find locks that are no longer needed, you may be able to delete them (if you have the necessary authorizations).
  Review Authorizations: Ensure that the user has the appropriate authorizations to perform the desired action. This can be checked using transaction code SU53 to analyze authorization failures.
  Consult with Basis Team: If the issue persists, it may be necessary to consult with your SAP Basis team to investigate any underlying system issues or configurations that may be causing the display-only restriction.
  Check for Background Jobs: Sometimes, background jobs may be running that affect the data you are trying to access. Check transaction SM37 to see if any relevant jobs are running.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CO01 (Create Production Order), CO02 (Change Production Order), CO03 (Display Production Order), and KOB1 (Order Line Items) to understand where the error might occur.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for CO270 in the SAP Support Portal.
  Documentation: Review SAP documentation related to controlling and access control to understand the context in which this error may arise.
  
  If the problem continues after trying the above solutions, it may be beneficial to escalate the issue to your SAP support team for further investigation.