Purchasing

Get Involved. Join the Conversation.

Topic

    Jagan Bakkiyanathan
    [Declined Idea] Min Max Planing - Supplier details are not...Answered
    Topic posted March 1, 2019 by Jagan BakkiyanathanRed Ribbon: 250+ Points, last edited March 11, 2019 by Suman GuhaGold Trophy: 10,000+ Points, tagged Requisition Processing, Supply & Distribution Planning Cloud 
    138 Views, 7 Comments
    Title:
    [Declined Idea] Min Max Planing - Supplier details are not taken from Sourcing rule
    Summary:
    Min Max Planing - Supplier details are not taken from Sourcing rule
    Content:

    Create ASL for an Item. donot provide any BPA/CPA details in ASL.

    Create Sourcing rule for the same Item and add the sourcing rule to assignment set

    When MIN Max is run the requisition would be created. In the requisition the Supplier details are not getting populated from Sourcing rule. This functionality was standard functionality in EBS. In fusion the functionality is not available

    Version:
    R13

    Best Comment

    Suman Guha

    Am not sure why you would not pursue full automation here when the items that are being procured are repetitive buys. Best practice is for buyers/procurement to have done the upfront work in identifying the source suppliers and negotiating pricing agreements and let the system handle incoming requirements in a touchless mode.

    If you still want manual intervention from the buyers, agreements in fusion have the necessary control to either allow buyers to manually process the requisitions into orders or have the system create the orders but require buyers to review and submit them manually.

    Am declining this idea as I don't see any additional business requirement being met with this idea.

    Comment

     

    • Suman Guha

      You don't need sourcing rules nor do you need ASLs in Fusion for your scenario. What you need for sure is a BPA that lists the item and has the pricing information in order to have it sourced to a supplier and a Purchase order to be issued out in a touchless manner.

      So you may try your scenario again after you have a BPA for your item and either get rid of the ASL entry or add the BPA reference to the ASL.

       

       

       

      • Jagan Bakkiyanathan

        For the Min Max planned item there is no BPA available. User want to create Requisition and buyer would check and process into PO.The requirement is to user Sourcing rule to derive supplier as in EBS

    • Suman Guha

      Am not sure why you would not pursue full automation here when the items that are being procured are repetitive buys. Best practice is for buyers/procurement to have done the upfront work in identifying the source suppliers and negotiating pricing agreements and let the system handle incoming requirements in a touchless mode.

      If you still want manual intervention from the buyers, agreements in fusion have the necessary control to either allow buyers to manually process the requisitions into orders or have the system create the orders but require buyers to review and submit them manually.

      Am declining this idea as I don't see any additional business requirement being met with this idea.

    • Jagan Bakkiyanathan

      It dosent work that way

      Here the Price of Item which is purchased are very fluctuating. If the Price is fluctuating we cannot consider BPA to be available. That is why in EBS they provided Sourcing rule for same Scenario.

      How to achive the same functionality if there is not BPA ?

    • Suman Guha

      Saw another post from you where you made the same comment about fluctuating prices. Could you please respond to the follow-up questions there?

      • Jagan Bakkiyanathan

        The Price is decided at the time of Placing Purchase order

        • Suman Guha

          Thanks. That's helpful. Do you know how?

          - Buyer negotiating with supplier for every order?

          - Daily negotiated Price list ?

          - Market Index?

          - Market Index + Prenegotiated margin?

          - Something else?

          The above would help us perform a fit analysis with what we support in the apps today and make a implementation approach recommendation and/or recognize the gap that should be addressed in the product.