Purchasing

Get Involved. Join the Conversation.

Posts

  • TEANG MM
    PO Promised Delivery Date should be defaulted based on...2
    Topic posted October 10, 2019 by TEANG MMRed Ribbon: 250+ Points, tagged Agreements, Orders 
    Title:
    PO Promised Delivery Date should be defaulted based on BPA's lead time days
    Summary:
    PO Promised Delivery Date should be defaulted based on BPA's lead time days
    Content:

    Currently PO created source to BPA will have empty Promised Delivery Date.

    Please consider to auto populate the  PO Promised Delivery Date with the BPA's lead time days if there is value in this field

  • Sandeep Kumar
    Categories Restricted by Supplier Wise15.0
    Topic posted September 23, 2019 by Sandeep KumarSilver Medal: 2,000+ Points, tagged Agreements, Create Requisition, Manage Procurement Catalog, Orders, Requisition Processing 
    Title:
    Categories Restricted by Supplier Wise
    Content:

    Can we restrict the categories by supplier wise let's say, we have assigned some categories to supplier and when we create PR/PO, Only Those Categories appear  or when we select a category on PR, only those suppliers appear where category is assigned

  • Dev Thota
    Terminated users are getting removed on requisition even...25.0
    Topic posted September 25, 2019 by Dev ThotaGold Trophy: 10,000+ Points, tagged Agreements, Approvals, Approvals/Notification, Approved Supplier List, BI Publisher Reports, Business Intelligence, Create Requisition, FAQ, Financials, Fusion, General Ledger, How-To, Manage Procurement Catalog, Notifications, Orders, OTBI, Payables, Public Sector, Requisition Processing, Security, Setup, Supplier Communication, Supply & Distribution Planning Cloud, Tip, Web Services 
    Title:
    Terminated users are getting removed on requisition even though the user is PO requester and the user is on inactive state
    Summary:
    Terminated users are getting removed on requisition even though the user is PO requester and the user is on inactive state
    Content:

    Hi all,

    Terminated users are getting removed on requisition even though the user is PO requester and the user is on the inactive state.

    Report Subject Area: Procurement - Purchasing Real Time.

    Thanks,

    Dev Thota.

    Version:
    19C
  • Rain Tsui
    How to enable requested delivery date validation against...45.0
    Topic posted March 28, 2019 by Rain TsuiGreen Ribbon: 100+ Points, tagged Agreements, Approvals, How-To, Orders 
    Title:
    How to enable requested delivery date validation against agreement's effective dates
    Content:

    Business Case

    You want to enforce the agreement's start/end dates for any purchases made against those agreements.

    Solution

    You can use the profile option "PO_REQUESTED_DELIVERY_DATE_VALIDATION" to validate that the requested delivery date is within the source agreement's effective dates. This applies to both contract purchase agreements (CPA) and blanket purchase agreements (BPA).

    With this option enabled, you can prevent submission of POs whose requested delivery date falls outside the agreement's start and end date. 

    Example

    You have created the  following agreements for the same supplier, item, and UOM:

    Agreement Number
    Start Date
    End Date
    123 01-JAN-2019 30-JUN-2019
    456 01-JUL-2019 31-DEC-2019

    A PO with requested delivery date of 01-AUG-2019 will fail submission validation if agreement 123 is referenced, regardless of the profile option setting.

    A PO with requested delivery date of 01-MAY-2019 will fail submission validation if agreement  456 is referenced and the profile option is enabled, but will pass submission validation if the option is disabled. 

    How to set up

    You can go to Manage Purchasing Profile Options and search by PO_REQUESTED_DELIVERY_DATE_VALIDATION.

    Screen%20Shot%202019-03-18%20at%202.32.51%20PM.png?version=1&modificationDate=1552944882000&api=v2

     
  • Niamath Jeddy
    BPA backed PO Creation (FBDI) : Line Price Logic11
    Topic posted July 17, 2019 by Niamath JeddyGold Trophy: 10,000+ Points, tagged Agreements, Orders 
    Title:
    BPA backed PO Creation (FBDI) : Line Price Logic
    Summary:
    BPA backed PO Creation (FBDI) : Line Price Logic
    Content:

    Hi,

    • I am using the FBDI method to create a PO
    • PO is backed by a BPA (source agreement columns are populated at PO line level)
    • When the PO is created, it is observed that the
      • PO Line price specified in PO line FBDI template is not used
      • The PO Line price is also not taken as per the quantity price breaks
      • The PO line price is taken from BPA line.

    Shouldn't the price be taken as per the slab instead of BPA line price?

    Also, in case the 'Allow price override' flag of BPA is 'Y', then shouldn't the price specified in PO line FBDI template be used ?

    If anyone has loaded legacy POs (referencing BPA with price breaks), can you share your experience?

    Also requesting some points from product management on this feature.

    Please refer below snapshot.

    Regards,

    Niamath

     

     

    Image:
  • Sandeep Kumar
    One agreement but two different currencies5
    Topic last edited September 20, 2019 by Sandeep KumarSilver Medal: 2,000+ Points, tagged Agreements 
    Title:
    One agreement but two different currencies
    Content:

    We have one purchase agreement but two different currencies

    lets say, There is hotel agreement and this agreement is related to per room changes, For Local is 1000 AED but for Foreign 500 USD per room charges

    shall we create two agreement? because per unit is in different currency, what would be the best way for this

     

  • Sandeep Kumar
    DFF for PO and AgreementAnswered85.0
    Topic posted September 10, 2019 by Sandeep KumarSilver Medal: 2,000+ Points, tagged Agreements, Orders 
    Title:
    DFF for PO and Agreement
    Content:

    We have defined DFF for Purchase agreement but those are appearing on Purchase order also, we want to hide those DFF, how can I achieve this?

     

     

  • Harshith Eshwar Shaila
    Need to restrict Buyer from creating a Purchase Order...Answered5
    Topic last edited September 18, 2019 by Harshith Eshwar ShailaBronze Medal: 1,250+ Points, tagged Agreements, Fusion, Orders, Security 
    Title:
    Need to restrict Buyer from creating a Purchase Order without Requisition.
    Content:

    Hi all,

    We have a requirement to restrict Buyer from creating a PO without requisition.

    In other way, we need to disable the "Create Order" task under the "Orders" section in task carousel under Purchase Orders Work Area. (Keeping rest of the tasks enabled)

    So can you guys suggest me which are the specific privileges/roles that needs to be removed from Buyer job role.

     

    I'm open to other suggestions or work around which might achieve this expectation.

    Note: Similar method to restrict tasks related to Agreements is also expected, any info on this would also help.

     

    Regards,

    Harshith E S

  • 2019-07-04
    19C Patch Testing - How to Prevent Notification Emails going...1
    Topic posted September 10, 2019 by 2019-07-04Red Ribbon: 250+ Points, tagged Agreements 
    Title:
    19C Patch Testing - How to Prevent Notification Emails going out?
    Content:

    Hi,

    We are testing 19C at the moment (19C (11.13.19.07.0)). I updated a BPA in Purchasing on the test system, and a notification was sent out to the Buyer linked to the BPA to say it had been changed - screenshot below.

    The notification was sent to the Buyer's real email address - so they didn't understand why they had received this notification.

    On R12 / 11.5.10 it was possible to set an override email address to prevent this type of issue from happening.

    Is there a similar option in ERP Cloud?

    Thanks

    Jim

     

     

    Version:
    19C (11.13.19.07.0)
    Document:
  • Vineet Gangwar
    Hide/Make DFF mandatory based on PO document type25.0
    Topic posted April 23, 2019 by Vineet GangwarBlue Ribbon: 750+ Points, tagged Agreements, Fusion, How-To, Setup, White Paper 
    Title:
    Hide/Make DFF mandatory based on PO document type
    Summary:
    Requirement is to make DFF mandatory at PO header for type lookup code as "Contract Purchase Agreement" only
    Content:

    The requirement was to make a DFF mandatory (PO Headers) for Contract Purchase Agreement only. We have achieved this requirement through personalisation by using following EL expression -

    #{bindings.TypeLookupCode=='CONTRACT'?true:false}

    Note - same expression can be used to hide the segment

    Is there any other method to achieve the said requirement as personalisation may get removed post upgrade?