My Oracle Support Banner

E1: 42: Sales Order Edit Line SOEF String Functions (B4205101) and szSOEMBFInternalFlags (Doc ID 1375749.1)

Last updated on MARCH 12, 2021

Applies to:

JD Edwards EnterpriseOne Sales Order Processing - Version XE and later
Information in this document applies to any platform.

Purpose

This note is to explain possible issue you come across in Sales Order processing. Through this note we may understand inquiries,

 

Note:
  • Information describes here is different from Sales Order flag described at  <Note 1268884.1> - E1: 42: Sales Order Flags in F4211 (P4210/P42101/R42565/F4211/F49211)
  • Business function B4205101 which is heavily used during sales order processing, which may call before Edit Line or inside Edit Line routine which validates/defaults/creates cache/workfile for sales order detail information.
  • Global variables and static variables should not be used in BSFN code. These constructs are not threadsafe because they can be modified and accessed by multiple threads simultaneously. Instead, state information should be made temporary (stored in local variables and passed via function parameters), stored in JDECACHE, or simply removed. Here are a few ways that globals and statics are often used as well as some suggestions on how to remove the need for them.
  • And this method is economical because we do not have to define multiple variables or multiple parameters in calling master business functions

 



Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

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


In this Document
Purpose
Troubleshooting Steps
 B4205101
 B4205102
 B4205103
 B4205104
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.