Purchasing

Get Involved. Join the Conversation.

Topic

    Ekansh Jain
    Auto-population of need-by/promise date on PR/PO based on...
    Topic posted June 6, 2019 by Ekansh JainBronze Medal: 1,250+ Points, tagged Agreements, Create Requisition, Fusion, How-To, Manage Procurement Catalog, Notifications, Orders, Requisition Processing, Setup, Supply & Distribution Planning Cloud, White Paper 
    89 Views, 1 Comment
    Title:
    Auto-population of need-by/promise date on PR/PO based on Lead time setup for an item corresponding to ship-to location
    Summary:
    Auto-population of need-by/promise date on PR/PO based on Lead time setup for an item corresponding to ship-to location
    Content:

    Hi,

    Please let me know if there is any workaround or custom solution to achieve the below requirements in Oracle Purchasing Cloud.

    Scenario: Auto-population of need-by/promise date on PR/PO based on Lead time setup for an item corresponding to ship-to location

    Use Cases

    1. Manual Purchase requisition: Requestor selects the ship-to location and Catalogue item, the system automatically populates the need-by date as <SysDate+Lead Time>. This data flows to the PO as Promise Date
    2. Min-Max Planning based Purchase Requisitions: Min-Max planning is run at Org/Sub Inventory level which automatically populates the need-by date as <SysDate+Lead Time>. This data flows to the PO as Promise Date

    As-Is Business Process: Client maintains BPA for each catalogue item with the supplier but doesn’t use ship-to location on the BPA. Lead time is separately managed in custom form for each Item-Ship-to combination. When the user enters PR or min-max planning triggers a PR, customization calculated the need-by date as <SysDate+Lead Time> (as maintained in the mentioned custom form), and populates on PR. This need-by date flows to the PO as the promised date. Buyer can override this date if there are concerns with the promise date from the supplier side.

     

    Why is it critical:

    1. To make sure the right expectations are set up with the requestor about the availability of purchases
    2. To make sure inventory specialists sees correct Supply/Demand picture as promise date is used as supply cut-off date. This helps in avoiding the inventory stock-out situations
    3. To enforce the SLA agreements with vendors, and vendor’s performance can be measured
    4. Extra work to override the populated promise date which will be sysdate if this solution is not in place. Separate communication needs to happen to change this as per SLA agreement which is extra work

    Requirements:

    1. Show end user what is the lead time for that ship-to location for the item?
    2. Auto-populate <SysDate + Lead time> as the promise date on PR/PO. This should be applicable to both manual as well as planning (Min-max) based PR
    3. Supply and Demand report should be able to use the Lead time while calculating the demand/supply based on the cut-off date
    4. Ability to see/review updates on PO promise data by supplier

    Comment