Runtime Messages in jde.log from Interactive Applications

Purpose of Document

The purpose of this document is to explain the runtime message in jde.log retrieved by call object kernel in your running the EnterpriseOne Interactive Applications.

Certain business functions such as B4200310 (F4211FSBeginDoc), may call a JDE API as below:

API: AllocatePOVersionData()
Prototype: void * AllocatePOVersionData(HUSER hUser,NID szApplication,NID szVersion,unsigned int uSizeOf )
Example: lpdsProcOptions = (LPDST4210) AllocatePOVersionData (hUser,_J("P4210"), lpDS->szCMVersion,sizeof(DST4210));

The following tables are related with this validation:

F983051 - Versions List Table (cf., F98306 for the processing option template text)
F9860 - Object Librarian Master File

The API will read the dstmpl specification during runtime of a certain application. In addition, the following columns are related with this API

F983051.VRPID, VRVERS, VRDSTNM and VRFRMTSTR
F9860.SIOBNM and SIMID1

Note: VRFRMTSTR is blob format file which is stored as Unicode format (so the size of a character is to be 2 bytes memory)

In running an application that calls this type of business function the following error/warning/information messages can occur:

Message in Log	Description
RUN0000038	hUser passed in has a NULL value
RUN0000041	Open Table F983051 fails
RUN0000040	Open Table F9860 fails
RUN0000039	Requested Application - "szApplication" does not exist in Object Librarian
RUN0000066	Warning - ProcOpt Data Size Mismatch: Requested 'size requested' is less than Retrieved 'size retrieved' for App 'szApplication',Version 'szVersion'. Data Structure allocated successfully
RUN0000067	For Batch application. Same with RUN0000066
RUN0000043	Out Of Memory: Allocation Fails for 'szApplication' and Version 'szVersion'.
RUN0000044	Error - ProcOpt Data Size Mismatch: Requested 'uSizeOf' is greater than Retrieved 'nDsLen' for App 'szApplication',Version 'szVersion'. Data Structure NOT allocated
RUN0000045	Unable to retrieve Processing Option Template for Application 'szApplication'.
RUN0000046	Application 'szApplication' does not have a Processing Option Template Attached

The possible causes of these message are:

Message	Possible cause	Others
RUN0000041 - Open Table F983051 fails	API AllocatePOVersionData() in a certain Business Function fails to open Table F983051 - 'Versions List'
RUN0000040 - Open Table F9860 fails	JDE API AllocatePOVersionData() in a certain Business Function fails to open Table F9860 - 'Object Librarian Master File'
RUN0000039 - Requested Application - "szApplication" does not exist in Object Librarian.	F9860.SIOBNM='szApplication' fails to return value
RUN0000066 - Warning - ProcOpt Data Size Mismatch	Requested 'size requested' is less than Retrieved 'size retrieved' for App 'szApplication',Version 'szVersion'.Data Structure allocated successfully	This usually means items have been added to the template and existing business function will function correctly. Set a warning when sizeof is greater than data structure size. To debug this warning message, refer to <Document 779449.1> E1: DSTR: How to Debug Message RUN0000066/RUN0000067 - Warning - ProcOpt Data Size Mismatch
RUN0000043 - Out Of Memory	Allocation Fails for 'szApplication' and Version 'szVersion'. lpProcOptData from COMMON_POOL (global area cache) is NULL	To fix this, 1. Go to work with server job 2. Highlight 'Logic Server' and (row exit) to Reset Cache 3. Tick 'Processing Option' and click OK to refresh it
RUN0000044 - Error - ProcOpt Data Size Mismatch	Requested 'uSizeOf' is greater than Retrieved 'nDsLen' for App 'szApplication',Version 'szVersion'.Data Structure NOT allocated. This usually means an item has been REMOVED from the template. This business function needs to be rebuilt against this new template definition.Set on an error when sizeof is less than data structure size. This is hard error as memory overflow may take place	Case study can be found at <Document 1319499.1> - E1: BSFN: RUN0000044 - Error - ProcOpt Data Size Mismatch Message Clarification
RUN0000045 - Unable to retrieve Processing Option Template for Application	When DataStructure template spec (dstmpl) is null The issue may be occurred across system because the table F9860 - Object Librarian Master Table is sitting in Object Librarian data source General cause of this error is that F9860.simid1 is blank or contains wrong template ID In jdedebug.log trace how table F98743 - DSTMPL has column F98743.obnm	So to fix this error, verify F9860.simid1 column value for the interactive application which shows this error. Most of this issue is caused by update of F9860 from outside EnterpriseOne. <Document 626569.1> - E1: DSTR: Frequently Asked Questions on Processing Option Templates and Data Structures
RUN0000046 - Application 'szApplication' does not have a Processing Option Template Attached	When F9860.simid1 is null/blank. RUN0000046 may come when data in the table F9860 is modified by a custom application so before any column value is updated in F9860, back up the data first.

Note: Oracle is not responsible for any error which results from the customization of standard tables or applications.

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the Design Tools & Output Technologies - JDE1 Community.

To look at upcoming or archived Advisor Webcasts please see Advisor Webcast Details <Document 548764.1>. If your topic is not currently scheduled please suggest it.