How To Split Sales Order Line through AdvancedSODetailLineSplit (B4200450, Advanced SO Detail Line Split)

Purpose of Document

The purpose of this document is to explore the possible way to split sales order through add-on batch routine.

Possibly there is 3rd Party Logistics company who performs distribution of goods on behalf of client based on sales order given by client. The business process:-

1. Outbound: Sales Order from EnterpriseOne to 3rd party system (through system integration)
2. Inbound: Then after 3rd party picks the order we need an inbound integration which can update the sales order with lot, location information which can be multiple lots against one F4211 (Sales Order Detail) line.
3. Inventory Commitment in EnterpriseOne: So that subsequent inbound shipment confirmation integration can do shipment confirmation line by line because we know that R42500 (Ship Confirm Batch Application) and R47500 (Inbound Transaction Processor) doesn't support line splitting likewise P42053 (Select Multiple Locations) in P4205 (Shipment Confirmation).

Business requirement

: Currently there are order quantity 11 which is to be labeled 3 lots quantity with 2, 3 and 4, which in return written into exiting sales order line.

 As - Is data from 3rd party

 
As - Is data from F4211 in EnterpriseOne

 
To-Be Data from F4211 in EnterpriseOne

Functional Design:

Split the existing Sales Order line

1st split: 

UORG1 = 11 - (a = Quantity of LOT-A) = 9

2nd split: 

UORG2 = 9 - (b = quantity of LOT-B) = 6

3rd split: 

 UORG3 = 6 - 4  ( c  = Quantity of LOT-C)

Pre-requisite:

• Table/repository to hold order information along with itm, mcu, locn and lotn which can be used for your add-on UBE and status can be updated accordingly
• On hand quantity (or availability) from F41021 has to be populated to commit it
• Then your report can run based on this table (after splitting update a certain flag)
• Inventory commitment can be implemented in same report or call other inventory commitment report or ship confirm
• Set Order activity rule with additional steps involved

Possible implementation:

Simplified routine:

1. Set record reservation whenever order number changes
2. Get Sales Order information B4200210 (F4211 Get Sales Detail Row) which returns pointer for detail line
3. (Optional) get audit information to populate information was created by your own routine (not standard)
4. Call B4200450 (Advanced SO Detail Line Split) and set cBypassUpdateOnOriginalLine = 1 (otherwise the original line will be committed which may give you trouble for subsequent split)
5. Update original line for columns lttr, nxtr, uorg, soqs, aexp, ecst, pqor, sqor,itwt, itvl and so on
6. Release data pointer from step 2 through B4000460 (Memory, Free Ptr To Data Structure)
7. Remove Record Reservation when it finishes a single order

 Example of event rule:

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 and Pre-requisites:
• 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 structures.  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 parameter 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 input parameter

This note is created based on E1 application release 9.1