E1: 12: Clicking OK In P1201 Writes a Warning Message to the Log (Doc ID 1637654.1)

Last updated on FEBRUARY 04, 2016

Applies to:

JD Edwards EnterpriseOne Capital Asset Management - Version 9.1 to 9.1 [Release 9.1]
JD Edwards EnterpriseOne Fixed Assets - Version 9.1 to 9.1 [Release 9.1]
Information in this document applies to any platform.

Symptoms

9.1 version, Equipment and Plant Maintenance P1201.  

ProcOpt Data Size Mismatch message.    

When we ran P1201, we get "ProcOpt Data Size Mismatch message" message in jde.log.  Here is the exact message.  We believe that this may cause to crash P1201. The business functions you need to check are B1200220 and B1200221.  When using the P1204, select a record to go into P1201 and click OK to re-save it.  
 
STEPS TO REPRODUCE
==================
Here are the steps to duplicate the issue.
1) Run P1204 with any version
2) Press "Find" button on Work With Asset form
3) Highlight any asset record in the grid
4) Take the row exit to Asset Master
5) Once you are in Asset Master Revisions form, press "OK" button to update the asset master record.  
6) Close all the applications
7) Check jde.log file, you will see the message above.  
 
DESIRED OUTCOME
===============
Research why this is being written to the log and correct it.

ERROR
-----------------------
Error:  RUN0000066

"RUN0000066 - Warning - ProcOpt Data Size Mismatch: Requested 204 is less than Retrieved 206 for App P1201,Version ZJDE0001.
Data Structure allocated successfully.  This usually means items have been added to the template and existing
business function will function correctly."

The following warning message appears in the jde.log:  
 
10653/-258733168WRK:JO399283_09C1A2B8_P1201 Wed Mar 5
17:17:32.826098rtk_frms.c648RUN0000066 - Warning - ProcOpt Data Size
Mismatch: Requested 204 is less than Retrieved 206 for App P1201,Version
ZJDE0001.Data Structure allocated successfully.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot always trust the diagnostic info in the JDE.log, when warnings and errors are written for non error conditions.  We believe that this may cause to crash P1201.      
.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms