E1: 42: Case Study - Inconsistent Work Center Message (F01131) in Running R42500
(Doc ID 2340030.1)
Last updated on MARCH 16, 2020
JD Edwards EnterpriseOne Sales Order Management - Version 9.2 and later Information in this document applies to any platform.
The purpose of this document is to go through as-is outcome in writing Work Center Message upon running R42500. Note that this note can be used for other batch application to determine the way it writes work center message. Work Center message can be written in two different kernels, one is call object kernel by calling PPAT function explicitly and the other is ube kernel. The latter work center message is depending on UBESendMessage stanze in the section [UBE] of JDE.INI where batch is running.
In short, there are two different methods to writes work center when a certain batch ends in error,
UBE Kernel: the value of UBESendMessage in JDE.INI affects globally (regardless the UBE you call)
Call Object Kernel: Application specific. There is no specific rule how to write work center message.
The error routine of R42500 is unique because it may give you different errors.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!