Purchasing

Get Involved. Join the Conversation.

Topic

    Shyam Singh Patel
    Grouping PO lines based on a Requisition DFF valueAnswered
    Topic posted May 20, 2019 by Shyam Singh PatelGold Medal: 3,500+ Points, tagged Create Requisition, Orders, Setup 
    82 Views, 8 Comments
    Title:
    Grouping PO lines based on a Requisition DFF value
    Summary:
    Grouping PO lines based on a Requisition DFF value
    Content:

    Is there a way to group PO based on Requisition DFF. We have a requirement to create different POs based on an attribute in requisition line

    SR 3-20100069221 : Grouping PO lines based on a Requisition DFF value
    Version:
    19B

    Best Comment

    Suman Guha

    Understand from the SR that this has to do with Drop Ship Purchase Orders.

    Options for you to consider:

    1) Investigate if it's possible to manipulate the Customer Sales Order number interfaced to procurement using the SO-PO mapper so that it can be a Sales Order Deal number combo not just a sales order number.

    2) Explore using ship sets in the OM side for each deal within the Sales Order so that a single req is created for each deal which can them become a single PO.

    Of course, splitting the quote from the external quoting system into separate fulfillment orders with unique sales order number by deal would be the simplest if it's acceptable to the business.

    Comment

     

    • Suman Guha

      Understand from the SR that this has to do with Drop Ship Purchase Orders.

      Options for you to consider:

      1) Investigate if it's possible to manipulate the Customer Sales Order number interfaced to procurement using the SO-PO mapper so that it can be a Sales Order Deal number combo not just a sales order number.

      2) Explore using ship sets in the OM side for each deal within the Sales Order so that a single req is created for each deal which can them become a single PO.

      Of course, splitting the quote from the external quoting system into separate fulfillment orders with unique sales order number by deal would be the simplest if it's acceptable to the business.

      • Shyam Singh Patel

        Hi Suman,

        Thanks for the reply.we are exploring Option 1 as Option2 is not feasible for our business case.

        Regards
        Shyam

      • Shyam Singh Patel

        Hi Suman,

        we explored the first option but there is no field at Req Header/Line in mapper Entity. hence we can not map this.
        Any Other thoughts or Input on this?

        Regards
        Shyam

        • Suman Guha

          No Shyam. Can't think of any other options here.

          What I mentioned before still remains to be the best option if possible:

          Of course, splitting the quote from the external quoting system into separate fulfillment orders with unique sales order number by deal would be the simplest if it's acceptable to the business.

          • SIMANTA DATTA

            Hi Suman,

            This is Simanta, honestly your idea seemed like an excellent one and I was really hoping that this field "Customer Sales Order number" was present in the SO-PO mapper ! 

            But now that we know it's not present there, I'm wondering if it is out of question to even think if we could enable this field inside the SO-PO mapper inside the Requisition Line object? Sorry I am not sure if it s an OM question or PO question, but I am sure both teams are involved/impacted.

            The main question is whether the SALES_ORDER_NUMBER on the POR_REQUISITION_LINES_ALL need to be "real" sales order from PO or OM point of view, or can it have a custom number like a quote number or deal number as we pass from OM mapper (if we could)? We know that SO number doesn't have a hyperlink on the PO/Requisition page to open the SO details (like we have for item number, customer etc), which made me think there is no hard-integration by the SO number on POR_REQUISITION_LINES_ALL table itself?

            Let me know what you think.

            Regards, Simanta

            • Suman Guha

              Simanta,

              It would be for OM to review.

              For the customer sales order question, its a freeform text field. Primary purpose is for communication to the supplier to use for packaging and for buyers to use as a reference field for querying purchase orders. 

              Regards,

              Suman.

              • SIMANTA DATTA

                Suman - had a call with Shrikant Nene today and he mentioned that any field that OM is internally populating is NOT exposed in the mapper, and that's why customer sales order is not present in the mapper.

                We will work with an ER for this.

                But just to re-validate 2 points

                1. When PO is calling any OM service for all events originated from PO (e.g. Promise date update, Shipping etc), it's using which field to get to the SO number? Is it using the DOO_DOCUMENT_REFERENCES.DOC_ID ? Because surely it's not using SALES_ORDER_NUMBER  on POR_REQUISITION_LINES_ALL as it's a freetext field. I believe so, but just trying to confirm.

                2. This is a futuristic question, but even with the ER, could changing the SALES_ORDER_NUMBER  on POR_REQUISITION_LINES_ALL via mapper create any issue in future when there would potentially be functionality to view an SO from PO ? For example, if on the PO page the SO number field had a hyperlink to go the PO, conceptually, should it use the SALES_ORDER_NUMBER value (which is changed by mapper), or should it use the same uniform reference mentioned above (say DOO_DOCUMENT_REFERENCES.DOC_ID). I think the latter, but wanted to confirm before we pursue the ER. Or if this question is too futuristic to answer now, let me know too.

                I think these 2 would be the last of our question, post this we would see how to (and if) pursue the ER.

                Regards,

                Simanta

                • Suman Guha

                  Simanta,

                  1. PO's not calling any OM service at this time. Rather OMs listening to business events and compensating for po changes based on PO references that are carried on the sales order.

                  2. If we do introduce drilldown capabilities in the future, it would be based off some internal system key and not a business key/free form text field like Customer Sales Order number is.

                  Regards,

                  Suman.