Troubleshooting the "RUN0000050" Error in Logs for EnterpriseOne Batch Applications (Related to API AllocatePOVersionData)

Purpose of Document

This document is intended to help troubleshoot the RUN0000050 error in the jde.log in running Batch Applications. This error, in general, occurs when a batch application is copied to modify certain routine(s) and when a special version is not created for the original batch application.  This error occurs when the batch application is designed to call a business function that retrieves Processing Option data from a specific object and version in the F983051 Versions List table.

Example of Error message in jde.log

RUN0000050 - Unable to retrieve DB Record for Application R42800, Version TEST03 from F983051.

What Causes the Error?

This error occurs when a batch application calls a business function that retrieves Processing Option data from a specific object and version. When this batch application is copied to a new object name in order to modify the application, if a version is not created for the original batch application, this error will occur when the application attempts to retrieve the processing option information through the business function. For example, if a new version CUST001 is created for the new batch application, but this version does not exist for the original, copied application, the application will fail with the RUN0000050 error.

How does EnterpriseOne Get the Version Data?

EnterpriseOne gets the version data through the API AllocatePOVersionData as below,

For this example,

• return type is LPDST4210
• lpdsProcOptions is long pointer which contains processing option data structure

What is the Default Version when an Input Version is not Specified?

ZJDE0001

What are the Error Codes and Messages?

• 1243 - Invalid Version
• 3143 - File can not be accessed.
• 4363 - Null Pointer
• 0001 - Action Invalid
• 0002 - Record Invalid
• 016K - Version is not available to client
• 072J - Processing Option Version is Invalid
• 080S - Version Invalid

How is the Error Set?

• bError = TRUE
• bExit= (BOOL) TRUE
• eReturn=ER_ERROR
• ErrorProcessing
• idErrorFlag = 2
• idReturn = ER_ERROR
• idReturnCode = ER_ERROR
• jdeStrcpy (lpDS->szErrorMessageID, _J("0002"))
• lpDS->cErrorFlag = _J('2')
• return ER_ERROR
• return ER_ERROR

How do I Resolve the Error?

To resolve the error caused by copying a standard batch application that meets this criteria, define a version with the same name and appropriate processing option values for the standard object. (For example if you have copied R12807 and named it R5512807):

1. Study the version you have created for R5512807 (if the Version ID is CUST001)
2. Create the exact same version ID for the source application (R12807)
3. Synchronize the processing options between R12807|CUST001 and R5512807|CUST001

What are the List of Applications which May End in Error when Copied?

The following table contains standard EnterpriseOne batch applications which have been designed to get processing option template information through a business function.