Split Sales Order and Line Number Assignment

Purpose of Document

This note discusses how a sales order detail line gets split and what is the incrementer by analyzing the business function B4200450 - AdvancedSODetailLineSplit (Advanced SO Detail Line Split).

Disclaimer: This document is intended for someone with developer level knowledge.

This note is created based on E1 application release 9.0

The sales order line split can be performed via:

• B4200450 - AdvancedSODetailLineSplit (Advanced SO Detail Line Split)
• B4200060 is Obsolete (via SAR 2036699)
• B4201780 - ProcessConfigItemSplitLineCache (Process Configured Item Split Line Cache), ProcessKitSplitLineCache (Process Kit Split Line Cache)

Objects Calling B4200450

The following objects can call B4200450 to split a sales order detail line. The split may take place during inventory commitment.

• Inventory Commitment
• Partial Receipt
• Partial Shipment
• Partial completion
• Multiple location
• Release backorder

How To Call B4200450

1. B4200210 - VerifyandGetSalesDetail (F4211 Get Sales Detail Row)
2. B4200450 - AdvancedSODetailLineSplit (Advanced SO Detail Line Split)
3. Insert a new line
3. Update F4211 (multiple BSFNs)

• B4200310 / B4200311 for Edit Line, Edit Doc and End Doc
• N4600455 (Change F4211 SO Detail File)

Default Incrementer (When mnLineIncrementer is not Specified)

When calling B4200450 - AdvancedSODetailLineSplit (Advanced SO Detail Line Split), if you do not specify mnLineIncrementer, the following values are applied:

• Kit/Parent: 0.1
• Component/Child: 0.01
• Others: 0.001

All the values can be overridden when calling B4200450 (AdvancedSODetailLineSplit). Check for the valid routine based on the application where the split occurs.

For instance, Sales Order detail lines can be split either through Sales Order Entry (when you hard commit and you have turned on back order) or Ship Confirmation as below,

• Sales Order Entry (P4210) : When F4211FSEndDoc is calling AdvancedSODetailLineSplit, the parameter mnLineIncrementer is not specified so rules mentioned above is to be applied so line for back order quantity shows .001
• Ship Confirmation (P4205) :
  • Without calling Multiple Location: When ShipConfirmEndDoc is calling AdvancedSODetailLineSplit, the parameter mnLineIncrementer is specified with value .100 for line to be backordered
  • With calling Multiple Location (P42053): When ShipConfirmEndDoc is calling AdvancedSODetailLineSplit, the parameter mnLineIncrementer is specified with value .001 for line to be committed and sets .100 to hold balance quantity

Example of Split Through Back Order Release

Place order with two different items without having any available quantity on hand
[As - Is] Sales Order Detail

[1st Split]

[3rd Split]

[10th Split]

[1st split for 2nd item]

B4200450 - AdvancedSODetailLineSplit (Advanced SO Detail Line Split) Detail

Purpose: Use this function to split the ship quantity from the backorder/cancel quantities in a sales order detail line (F4211). After the split, the original line will contain the backorder/cancel quantities while a new line is created for the ship quantity. The new line will essentially be a mirror image of the original line with some slight differences (e.g.., status codes). You can optionally supply a split line quantity which will allow this function to write the new line with this quantity and leave any remaining quantities in the original line.

Setup Notes and Prerequisites:

• In order to call this function, you must pass to it a row pointer that points to the Sales Order Detail record. Use a business function to fetch and create this pointer.
• If you are splitting the new line to a different item location, your calling application or function must ensure that the inventory committed to the original location as well as the new location are properly adjusted.
• If splitting line to a different item location, the branch, location, and lot passed will be used to write the new detail line. However, this function will not validate the value in these passed parameters. Therefore, the calling application or function is responsible for editing the branch, location, and lot fields before passing them into the function.

Data Structure: D4200450 : Advanced Sales Order Detail Line Split
Parameters:

Detail Routine:

• Insert New Record to Table (F4211)

1. Use the GENLNG to retrieve data from the Sales Order Detail data structure (F4211).
2. If SDSOQS <= 0, set error code to '1' and exit function. (Exit function if zero or negative ship quantity)
3. If IVI-parm == ' ', fetch the Inventory Interface flag (LFIVI) from Line Type Master (F4205) using SDLNTY as the key. Store the LFIVI to IVI in the parameter data strucutre. If a record is not found, assign 'N' to IVI-parm.
4. If UORG-parm != 0 and UORG-parm < SDSOQS
RemainingQty (WF) = SDSOQS - UORG-parm;
SDUORG = UORG-parm;
SDSOQS = UORG-parm;
else
SDUORG = SDSOQS;
RemainingQty (WF) = 0;
: If the split line's order quantity is specified and it is less than the original detail line's ship qty, use it (save the remaining qty to a work field which will later on be updated to the original detail line); else, use the entire ship quantity of the original line to write the new detail line.
5. If RemainingQty (WF) > 0 or SDSOBK != 0 or SDSOCN != 0, line should be split. (Use a work field to indicate line splitting or use best C technique)
6. If line splitting, save SDSOBK, SDSOCN, SDLNID, SDLTTR, SDNXTR, SDMCU, SDLOCN, SDCNID, SDADDJ, SDCARS, SDSO02, and SDLOTN to save fields.
7. If EV04-parm == '1',
SDMCU = MCU-parm;
SDLOCN = LOCN-parm;
SDLOTN = LOTN-parm;
: If updating to a different item location, use the branch, location, and lot passed
8. If line splitting, branch to the logic for splitting a sales detail line.
9. Execute the logic for adjusting the original sales detail line.

• Split Sales Detail Line

1. Zero out SDSOBK and SDSOCN.
2. Calculate the line number of the split line.

The new line number is the current line number plus the line increment (RLLN) passed. (i.e., SDLNID = SDLNID + RLLN)
else
Calculate the new line number by adding the Kit Master Line Number and the line increment. (i.e., SDLNID = LNID + RLLN).
3. Validate against F4211 to make sure the new line number is unique. Use an existing business function. If not unique, repeat step 2b-3.
4. Using the original F4211 record as a copy, map all fields to a new F4211 record. (Use the best technique in C)
5. Assign the current line number (SDLNID) to LNID in the paramater data structure.
6. Call GetItemUOMConversionFactor and update the following fields:
7. If the Override Cost field (SDCSTO) != '1' and EV03=='1',
a) Retrieve the unit cost by calling GetItemCost (XF4105.C)
b) Then call GetItemCostInformation (XF4105.C) and free F4105 pointer after the call:
c) If SDFUC != 0, use CurrencyConvForAndDom (B0000027.C) to convert domestic cost to foreign.
: Recalculate the extended cost if the quantity shipped has changed and this is not a kit component.
8. If (RemainingQty (WF) > 0 and SDRLIT == ' ') or ((SDCSTO != '1' and EV03=='1') and SDRLIT == ' ')
a) If SDFUC != 0 and SDSOQS != 0, calculate the foreign extended cost using ComputeUnitOrExtendedAmount (B4002000.C)
b) If SDSOQS != 0, calculate the domestic extended cost by calling ComputeUnitOrExtendedAmount (B4002000.C)
: If the shipping amount of the new line is adjusted and this is not a kit component line, recalculate the price and cost extensions in foreign and domestic using the new ship quantity.
9. If RemainingQty (WF) > 0 and SDSOQS != 0 and SDRLIT == ' '
If SDFUP != 0
Calculate the foreign extended price using ComputeUnitOrExtendedAmount
Calculate the domestic extended price by calling ComputeUnitOrExtendedAmount
10. SDLTTR = LTTR (override last status in input parameter).
:If an override next status is passed, validate it before using it.
11. If NXTR-parm != ' ' and NXTR-parm != SDNXTR then assign intput parameter

Line Numbering for the Free Good lines in P4210

The additional free good line(s) in Add/Update Mode in P4210 does not make use of the business function AdvancedSODetailLineSplit (B4200450, Advanced SO Detail Line Split) described above. Rather, the business function F4072CalculatePriceAdjustments (B4500050, F4072 Calculate Price Adjustments) sets hard coded value ".01" for free good lines. As a result, the line number for free good lines will be 1.010 (when the free good is attached to 1.000) and 1.020 (it appends a new free good line because of update in the line number 1.000).

If the current line number for free good line is 1.100, and changing quantity or request date, the new free good line number = the line number of base order line + 0.01. In case this number is in use which will be 1.000 + 0.1 + 0.1 + ... till it finds the to-be free good line number is available. Because the incrementer for Free Good's line number remains same which is 0.1.

Considerations: any tables which clone F4211 must have same line number: there are tables (F49211, F42199, F4211TX, F4211DT, F4211B, F4211AU and so forth) which share same primary key with F4211, need to manipulated whenever there is manipulation on F4211.