Order Management

Get Involved. Join the Conversation.

Topic

    Shyam Singh Patel
    Generate Order ESS with Sales Order Number ParameterAnswered
    Topic posted January 9, 2019 by Shyam Singh PatelGold Medal: 3,500+ Points, last edited January 9, 2019, tagged Order Management, Order Management Analytics 
    104 Views, 6 Comments
    Title:
    Generate Order ESS with Sales Order Number Parameter
    Summary:
    Generate Order ESS with Sales Order Number Parameter
    Content:

    Development is delivering support for the order number parameter on the ESS job in 19A.  They believe this will resolve the issue for dropship orders with less than 500 lines (since each batch is a single order). however, the 500-line limit is still a significant issue even with the parameterized ESS job.  

    Version:
    19A

    Best Comment

    Shyam Singh Patel

    Now we can create single purchase Order for More than 1000 Lines. Development provides us one custom Profile Solution. 
    Still SO -PO Line Number Sync an issue.( SO Line 1 "Generate Order ESS" change to PO Line 6, this SO-PO lines still not in sync)
    SR 3-19992198581: Dropship Purchase Order Line Should Be in Sync with Order Management Line

    Comment

     

    • Afaq Baig

      Hi Shyam,

          Thanks for let us know.

      Regards

    • Prasad Kinkar

      Thanks Shyam.

      So, in case we import a heavy order having more than 500 lines say 800 then does the system creates 2 orders or just 1 with 500 lines and ignore the rest 300 lines?  Alternatively, can we setup transformation rule to auto-create next order with 300 lines. Parts businesses might run with this workaround till a permanent fix is available.

      Thanks to help.

      Cheers,

      Prasad.

       

      • Shyam Singh Patel

        Hi Prasad,

        Long Story, in short, we had a long discussion with the Product development team on this issue. in our business, we had every sales order with more than 500 lines and it goes to 1600 lines per sales order and this was not agreed by the business which is running on EBS R12.2.4 and had a custom solution there. 

        This SR was for Dropship SO  and PO and see the important conversation we had with Oracle.
        Final Solution: Development working on this solution and in next 1-2 version release we get this functionality. interim solution development gave to include sales order as a parameter in Generate orders program which we will get in 19.01 1st Feb 2019 release.

        unable to group multiple requisitions to single PO in Drop Ship (Doc ID 2398453.1) ----- this start from here since we are using SO -PO mapper
        SR 3-18962131531 : Generate Orders program created drop ship PO for only half of the SO lines
        Enh 28937159 - INCREASE THE LIMIT OF PO LINES ON GENERATE ORDERS PROGRAM

        The Behavior seen is expected as the generate orders process requisitions in batches of 500 lines. 
         
        For the Enh 28937159 - INCREASE THE LIMIT OF PO LINES ON GENERATE ORDERS PROGRAM we have to wait and see whether the ER will be approved to ask what will be the new limit. 
         
        Question: As discussed yesterday we had a sales order with 1200 lines and all the lines were picked in the same request of Generate Orders program. How did the program pick 1200 lines together if the limit was 500?  As mentioned earlier 3 different POs had got created for the order with 500, 500 and 200 lines but still, all were picked by the same program request. 
         
        Currently, this is the seeded functionality. 
        The system picks up all the lines of the Sales Order and creates the Requisition. If your case the Requisition has more then 1000 lines and the system split them in a maximum 500 line per batch for the PO's created. 
         
         
        Question: So you mean that within a single request of the Generate Orders program the requisitions are picked up in multiple batches and max size of each batch is 500 requisition lines? If above is true then what is the limitation on the total number of requisition lines that can be processed per request i.e. including all the batches of thatrequest? 
         
        Answer: There is no limit on the number of batches one request can process: 
         
        1. If in current batch 500 lines are processed then the logic will check if there more lines to be processed 
        2. If in current batch less than 500 lines are processed then the request is moved to completed status 
         
        One Batch will process maximum 500 lines and create as many POs that are identified to be created, based on several parameters. 
        If all 500 requisition lines picked in the batch satisfy criteria to be grouped in one PO then the single PO will be created for all those line. 
        The # Lines/Schedule in PO is again dependent on conditions that needs to be satisfy for Line Level grouping further. 
         
        ===================================
        then we asked what is the internal sorting attibute logic of generate order ESS to pick the batch 

         
        Shyam, 
         
        Here are the answers to the recent questions: 
         
        Last step in each Batch Processing is to create POs for all the Requisition Lines that were identified to be eligible for Touchless PO Creation in that batch. 
        Looks like there is some confusion about batch processing which needs to be clarified. 
         
        Following are more details on how are available lines split in to batches. 
        The available lines (in this case 1000) are split in batches of 500 lines after sorting them based on following attribute with same order as preference from 1-6: 
        1. Requisition BU ID 
        2. Supplier ID 
        3. Supplier Site ID 
        4. Interface Source Code (determined based on source of Requisition) 
        5. Requisition Number 
        6. Requisition Line Number
         
         
    • Prasad Kinkar

      Thanks Shyam for the deeper insights. It really helps.

    • Shyam Singh Patel

      Now we can create single purchase Order for More than 1000 Lines. Development provides us one custom Profile Solution. 
      Still SO -PO Line Number Sync an issue.( SO Line 1 "Generate Order ESS" change to PO Line 6, this SO-PO lines still not in sync)
      SR 3-19992198581: Dropship Purchase Order Line Should Be in Sync with Order Management Line

    • Shyam Singh Patel

      Old SR : SR 3-19073898291  Dropship SO and PO Line numbers not in sync - Need information on req extraction logic
                     BUG 26951761
       

      The Logic I have mentioned above is applicable when GROUP_REQUISITION_LINES = Y.

      When GROUP_REQUISITION_LINES = N, then the PO Line Number is determined in order of Requisition Line ID. 

      Feedback from development 
      ======================== 

      The line determining logic for Touchless PO creation sorts the interface lines with several attributes and logic is not always straight forward, some attributes are considered based on setups and agreement controls. 

      Following is the list of attributes and order in which lines are sorted and ranked accordingly: 

      1. ITEM_ID, 
      2. ITEM_DESCRIPTION, 
      3. CATEGORY_ID, 
      4. If Group Requisition Lines is 'N' then REQUISITION_LINE_ID, 
      5. If Requisition Lines is FIXED PRICE then REQUISITION_LINE_ID, 
      6. Based on setup NEED_BY_DATE, 
      7. Based on setup SHIP_TO_LOCATION_ID, 
      8. Based on setup SHIP_TO_ORGANIZATION_ID, 
      9. LINE_TYPE_ID, 
      10. ITEM_REVISION, 
      11. UOM_CODE, 
      12. FROM_HEADER_ID (Blanket Agreement Header ID), 
      13. FROM_LINE_ID (If Line Price Override is Not-Allowed then Blanket Agreement Line ID should match; Else Grouping not allowed), 
      14. OKE_CONTRACT_HEADER_ID, 
      15. OKE_CONTRACT_VERSION_ID, 
      16. VENDOR_PRODUCT_NUM, 
      17. CONTRACT_ID (Contract Agreement Header ID), 
      18. SUPPLIER_REF_NUMBER, 
      19. NOTE_TO_VENDOR, 
      20. NEGOTIATED_BY_PREPARER_FLAG, 
      21. WORK_ORDER_PRODUCT, 
      22. EXTERNAL_ATTACHMENT_ID 

      SELECT 
      /* SR# 3-19073898291 */ 
      prh.requisition_number 
      , prl.line_number req_line_number 
      , prl.line_status 
      , ph.segment1 AS po_number 
      , prl.requisition_header_id 
      , prh.creation_date req_creation_date 
      , prl.requisition_line_id 
      , pl.unit_price 
      , pl.line_num po_line_number 
      , pl.FROM_CO_SEQ 
      , prl.creation_date req_line_creation_date 
      , ph.document_creation_method 
      , ph.prc_bu_id AS po_prc_bu 
      , ph.document_status 
      , ph.po_header_id 
      , pl.po_line_id 
      , pl.from_header_id 
      , prl.req_po_instance_id 
      , ph.document_status 
      , ph.vendor_id 
      , ph.vendor_site_id 
      FROM 
      fusion.po_headers_all ph 
      , fusion.po_lines_archive_all pl 
      , fusion.por_requisition_lines_all prl 
      , fusion.por_requisition_headers_all prh 
      WHERE 
      +ph.po_header_id(+) = pl.po_header_id+ 
      +AND prl.po_line_id = pl.po_line_id(+)+ 
      AND prl.requisition_header_id = prh.requisition_header_id 
      AND ph.segment1 in ('P101104935','P101104928') 
      AND pl.FROM_CO_SEQ = 0 
      ORDER BY 
      ph.po_header_id 
      , prl.requisition_line_id 
      , pl.line_num; 
      NEW SR 3-19992198581 : Drop ship Purchase Order Line Should Be in Sync with Order Management Line  where Oracle need to work on Bug 26951761