How To Fix /SAPPO/ACR122 - &1: Initial change user in case of set change time stamp

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPPO/ACR -

• Message number: 122

• Message text: &1: Initial change user in case of set change time stamp

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 /SAPPO/ACR122 - &1: Initial change user in case of set change time stamp ?

  The SAP error message /SAPPO/ACR122 &1: Initial change user in case of set change time stamp typically occurs in the context of the SAP Purchase Order (PO) or related documents when there is an issue with the change log or change history of a document. This error indicates that the system is trying to set a change timestamp for a document, but it cannot find the initial change user, which is necessary for maintaining the change history.
  Cause:
  
  Missing Initial Change User: The error usually arises when the system is unable to determine who made the initial change to the document. This could happen if the document was created or modified in a way that did not properly record the user information.
  Data Inconsistency: There may be inconsistencies in the database or in the change log tables that prevent the system from retrieving the necessary information.
  Custom Development: If there are custom developments or enhancements in the system that manipulate the change log or user information, they might not be functioning correctly.
  
  Solution:
  
  Check Change Log: Review the change log for the document in question to see if the initial change user is recorded. You can do this by navigating to the document and checking its change history.
  Data Consistency Check: Run consistency checks on the relevant tables to ensure that there are no inconsistencies. You can use transaction codes like SE11 or SE16 to inspect the relevant tables.
  User Existence: Ensure that the user who is supposed to be the initial change user exists in the system and is active.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error. SAP frequently releases notes that provide fixes or workarounds for known issues.
  Debugging: If you have access to debugging tools, you can analyze the program logic to see where the error is being triggered and why the initial change user is not being set.
  Consult SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for assistance. They may have additional insights or patches available.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like ME23N (Display Purchase Order) or ME22N (Change Purchase Order) to view and manage purchase orders.
  Change Documents: Understand how change documents work in SAP and how they are logged. This can help in troubleshooting issues related to change history.
  User Management: Ensure that user management practices are in place to maintain accurate records of who makes changes to documents.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.