How to Debug the Value Returned by B4205100 (Sales Order ALPH String Functions)

Purpose of Document

The audience for this note is someone with developer level knowledge.

This note is the first part of internal flag in Sales Order Processing:-

• B4205100 - Sales Order ALPH String Functions (refer to <Document 983617.1> - E1: 42: How to Debug the Value Returned by B4205100 (Sales Order ALPH String Functions)
• B4205101 - Sales Order Edit Line SOEF String Functions <Document 1375749.1> - E1: 42: Sales Order Edit Line SOEF String Functions (B4205101) and szSOEMBFInternalFlags
• B4205102 - Sales Order End Doc SOEF String Functions
• B4205103 - Sales Order Begin Doc SOEF String Functions
• B4205104 - Sales Order PreProcessor SOEF String Functions

Note: These flags are to be understood in the context of how sales order master business function handles data and for some cases the value may not be appeared in table or logs

983617.1_B4205100_ALPHIn Sales Order Module, based on a flag defined in ALPH, it may yield different result. This document is mainly for users on how to determine the settings and the result based on returned value in jdedebug.log. Note that the macro defined can be updated if a new functionality is implemented. The flag written in ALPH string is internal usage only so the value is not related with the value you are getting from SO01, SO02 and so on from F4211 - Sales Order Detail File.

Global variable may cause memory issue so pre-defined argument can be assigned in calling B4200310/B4200311 - F4211FSEditLine with parameter szSalesOrderFlags (located at 82nd parameter). So before F4211FSEditLine (F4211  Edit Line) this value will be defined by calling relevant business function as described below.

Disclaimer: Oracle will not be responsible for the changes made to standard programs due to this implementation and Oracle will not maintain any of these custom changes or be responsible for any problems arising from these changes.

Actual Implementation:
Example (based on jdedebug)), possible input value for parameter szSalesOrderFlags : IN->[ 82] szSalesOrderFlags [         8       2  0           0   10 0]

How to interpret above example:

• szSOALPHString[9] = 8 (8 - MANUAL_OVERRIDE_8_ALPH09)
• szSOALPHString[16] = 2 (refer below note)
• szSOALPHString[19] = 0 (0- DONT_SUPPRESS_0_ALPH19)
• szSOALPHString[32] = 0 (refer below note)
• szSOALPHString[36] = 0 (refer below note)
• szSOALPHString[38] = 0 (0 - FALSE_0_ALPH)

Note: szSOALPHString[16], szSOALPHstring[32] and szSOALPHstring[36] is handled by BSFN B4002410 - ChangeStringElement (String, Change String Element). For example,

If SV Form_ Mode is equal to CO COPY_MODE Or SV Form_ Mode is equal to CO ADD_MODE
       String, Change String Element
              GC ALPH - SO Detail Flags (wf) <> BF szString
              "16" -> BF nPosition
              "1" -> BF cCharacter
End If

From below table if there is no value defined specifically (blank, 0 and 1 are to be used),

• FALSE_BL_ALPH                 _J(' ')
• FALSE_0_ALPH                  _J('0')
• TRUE_1_ALPH                   _J('1')

Mapping Table:

<Internal_Only>describe missing alpha values based on P4210 because it is handled by </Internal_Only> bsfn

List of BSFNs:

InitializeSOALPHString

• Function: This function is to initialize string variable (which is character array) with _J("0000000000000000000000000000000000000000")
• Parameter:
• Data Structure: D4205100B - ALPH String Initilization Datastructure

• Detail Routine:

Other Business functions

• Function: All the functions referenced above is implemented with data structure defined here. Firstly it gets existing character for a specific index and if needed set/replace it based on input value defined.
• Parameter:
• Data Structure: D4205100A - ALPH String Get and Set Datastructure

• Detail routine: