How To Fix /PRA/OWNERSHIP158 - Transfer will reset CI check - Check Number:&1 status from &2 to 35

SAP Error Message - Details

• Message type: E = Error

• Message class: /PRA/OWNERSHIP -

• Message number: 158

• Message text: Transfer will reset CI check - Check Number:&1 status from &2 to 35

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/OWNERSHIP158 - Transfer will reset CI check - Check Number:&1 status from &2 to 35 ?

  The SAP error message /PRA/OWNERSHIP158 Transfer will reset CI check - Check Number:&1 status from &2 to 35 typically relates to issues in the context of the SAP Public Sector Management (PSM) module, particularly in the area of ownership and transfer of assets or funds.
  Cause:
  This error message indicates that a transfer operation is attempting to reset the status of a check (or a similar financial document) from its current status (denoted by &2) to a new status (in this case, 35). The status 35 usually indicates that the check is being marked as "canceled" or "voided." This can happen due to various reasons, such as:
  
  Inconsistent Data: There may be inconsistencies in the data related to the check or the transfer process.
  Business Logic Violations: The transfer operation may violate certain business rules or logic defined in the system.
  Configuration Issues: There may be configuration settings in the system that are not aligned with the expected behavior for transfers and checks.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check the Status of the Check: Review the current status of the check referenced by &1. Ensure that it is in a state that allows for the transfer operation you are attempting.
  
  
  Review Transfer Logic: Ensure that the transfer logic you are using is correct and adheres to the business rules defined in your organization. This may involve checking the configuration settings related to ownership and transfers.
  
  
  Data Consistency: Verify that all related data (e.g., ownership records, financial documents) is consistent and correctly maintained in the system.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the /PRA/OWNERSHIP module for any specific guidelines or known issues that may pertain to this error.
  
  
  Debugging: If you have access to debugging tools, you may want to trace the execution of the transfer process to identify where the logic is failing.
  
  
  Contact SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP support for assistance. Provide them with the error message details and any relevant context to help them diagnose the issue.
  
  
  Related Information:
  
  SAP Notes: Check for any SAP Notes related to the /PRA/OWNERSHIP module that may address this specific error or provide additional context.
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help you navigate the ownership and transfer processes in SAP.
  User Forums: Engage with SAP user communities or forums where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.