How To Fix PYC_CONT073 - Posting deletion started

SAP Error Message - Details

• Message type: E = Error

• Message class: PYC_CONT -

• Message number: 073

• Message text: Posting deletion started

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 PYC_CONT073 - Posting deletion started ?

  The SAP error message PYC_CONT073, which states "Posting deletion started," typically occurs in the context of the SAP Controlling (CO) module, particularly when dealing with the deletion of postings in the system. This message indicates that a process to delete a posting has been initiated, but it may not have completed successfully or may require further action.
  Cause:
  
  Incomplete Deletion Process: The deletion process may have been started but not completed due to various reasons, such as system errors, user interruptions, or data inconsistencies.
  Authorization Issues: The user may not have the necessary authorizations to complete the deletion process.
  Data Locking: Other processes or users may be locking the data that is being attempted for deletion, preventing the operation from completing.
  Configuration Issues: There may be configuration settings in the system that are preventing the deletion from being processed correctly.
  
  Solution:
  
  Check Deletion Status: Verify if the deletion process is still running or if it has been interrupted. You can check the status in transaction codes like SM37 (Job Monitoring) or SM21 (System Log).
  Review Authorizations: Ensure that the user attempting the deletion has the necessary authorizations to perform this action. You may need to consult with your SAP security team.
  Release Locks: If data locking is an issue, identify and release any locks that may be preventing the deletion. You can use transaction code SM12 to check for and delete locks.
  Retry Deletion: If the deletion process was interrupted, you may need to retry the deletion. Ensure that all prerequisites are met before doing so.
  Check Configuration: Review the configuration settings related to posting and deletion in the CO module to ensure they are set up correctly.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SM37: Job Monitoring
  SM21: System Log
  SM12: Lock Entries
  SE38: ABAP Program Execution (to run specific programs related to deletion)
  
  
  SAP Documentation: Refer to SAP Help documentation for detailed information on posting and deletion processes in the CO module.
  SAP Community: Engage with the SAP Community forums for insights and experiences shared by other users who may have encountered similar issues.
  
  If the problem persists after following these steps, it may be necessary to involve your SAP Basis or technical support team for further investigation.