How To Fix C+355 - Step: Delete purchase order history in additional currencies

SAP Error Message - Details

• Message type: E = Error

• Message class: C+ -

• Message number: 355

• Message text: Step: Delete purchase order history in additional currencies

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 C+355 - Step: Delete purchase order history in additional currencies ?

  The SAP error message C+355, which occurs during the step "Delete purchase order history in additional currencies," typically indicates an issue related to the deletion of historical data for purchase orders that involve multiple currencies. This error can arise due to various reasons, including data inconsistencies, configuration issues, or authorization problems.
  Causes:
  
  Data Inconsistencies: There may be inconsistencies in the purchase order history data, especially if there are multiple currencies involved.
  Configuration Issues: The system configuration for handling purchase order history in additional currencies may not be set up correctly.
  Authorization Problems: The user executing the deletion may not have the necessary authorizations to perform this action.
  Open Purchase Orders: If there are open purchase orders or related documents that reference the historical data, the system may prevent deletion.
  Custom Code or Enhancements: If there are custom developments or enhancements in the system, they might interfere with the standard deletion process.
  
  Solutions:
  
  Check Data Consistency: Use transaction codes like SE16 or SE11 to check the relevant database tables for inconsistencies. Ensure that all related entries are correct and complete.
  Review Configuration: Verify the configuration settings related to purchase order history and currency handling in the SAP system. This may involve checking settings in the Materials Management (MM) module.
  User Authorizations: Ensure that the user has the necessary authorizations to delete purchase order history. This can be checked in transaction SU53 or by consulting with your security team.
  Close Open Purchase Orders: If there are open purchase orders that reference the historical data, consider closing or deleting those orders before attempting to delete the history.
  Check for Custom Code: If there are any custom programs or enhancements that might affect the deletion process, review them for potential issues.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or provide additional guidance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME22N (Change Purchase Order), ME23N (Display Purchase Order), and ME2N (Purchase Orders by PO Number) to analyze the purchase orders in question.
  SAP Documentation: Refer to the official SAP documentation for detailed information on handling purchase order history and currency settings.
  Support Community: Engage with the SAP Community or forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis or technical team for further investigation.