How To Fix PYC_CONT091 - Cannot open DME generation job

SAP Error Message - Details

• Message type: E = Error

• Message class: PYC_CONT -

• Message number: 091

• Message text: Cannot open DME generation job

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_CONT091 - Cannot open DME generation job ?

  The SAP error message PYC_CONT091: Cannot open DME generation job typically occurs in the context of the DME (Data Medium Exchange) process, which is used for generating payment files for bank transfers or other financial transactions. This error indicates that the system is unable to open or access the job that is responsible for generating the DME file.
  Possible Causes:
  
  Job Not Scheduled: The DME generation job may not have been scheduled or may have been deleted.
  Authorization Issues: The user may not have the necessary authorizations to access the job or the related transaction.
  Job Status: The job may be in a status that prevents it from being opened (e.g., it may be finished, canceled, or in error).
  Technical Issues: There could be underlying technical issues with the SAP system, such as database connectivity problems or issues with the job scheduling system.
  Configuration Issues: Incorrect configuration settings for DME in the payment program or related settings may lead to this error.
  
  Solutions:
  
  
  Check Job Status:
  
  Go to transaction SM37 (Job Monitoring) and check the status of the DME generation job. Look for any jobs related to DME and see if they are finished, canceled, or in error.
  If the job is not found, you may need to re-schedule it.
  
  
  
  Re-schedule the Job:
  
  If the job is missing, you can re-schedule the DME generation job through the appropriate transaction (e.g., F110 for automatic payment transactions).
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to access the DME generation job. This may involve checking roles and authorizations in transaction PFCG.
  
  
  
  Review Configuration:
  
  Verify the DME configuration settings in the payment program. Ensure that the settings are correct and that the DME format is properly defined.
  
  
  
  Check for Technical Issues:
  
  If there are underlying technical issues, consult with your SAP Basis team to check for any system errors or connectivity issues.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates that resolve known issues.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F110 (Automatic Payment Transactions), SM37 (Job Monitoring), and OBPM1 (DME Configuration).
  Documentation: Review SAP documentation related to DME and payment processing for best practices and troubleshooting steps.
  SAP Community: Engage with the SAP Community 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 support team or consult with SAP directly for further assistance.