Posts

Posts

  • Manavalan Ethirajan
    Purchasing Cloud New Features in Release 13 (update...35.0
    Topic posted 11:34 AM by Manavalan EthirajanSilver Medal: 2,000+ Points, tagged Fusion, Orders in Procurement > Purchasing public
    Title:
    Purchasing Cloud New Features in Release 13 (update 20A)
    Content:

    The following new features will be available in Release 13 (update 20A):

    • Configure Page Number Display for Purchasing Document PDFs
    • Retroactive Pricing for Configure-to-Order Purchase Orders
    • Add New Approved Requisitions to Existing Open Purchase Orders
    • Capture Supplier Discounts on Purchase Order Lines
    • Review and Recover B2B Electronic Supplier Communication Exceptions Using the Transaction Administration Console

    You can review these new features in the following release readiness material and documentation.

    Oracle Procurement Cloud Release Readiness

  • Nagaraj VinayakaRao
    PO CLOSE SCHEDULE has a limitation of 5000 schedules (or...13
    Topic posted October 31, 2019 by Nagaraj VinayakaRaoGreen Ribbon: 100+ Points, tagged Orders in Procurement > Purchasing public
    Title:
    PO CLOSE SCHEDULE has a limitation of 5000 schedules (or lines) in the spreadsheet.
    Summary:
    PO CLOSE SCHEDULE has a limitation of only 5000 schedules (or lines) in the spreadsheet. Clients in Retail industry have more than 5000 PO schedules to action on. Why this restriction?
    Content:

    Ability to close/Final close POs  through a spreadsheet is available in Fusion R13. CLOSE SCHEDULE SPREADSHEET has a limitation of 5000 schedules (or lines)  to action on in the spreadsheet. Clients in Retail industry have more than 5000 PO schedules to download and action on them.  Want to know WHY oracle has limited it to only 5000 lines? Why this restriction?

    As per Oracle help, there are options to create smaller batches of less than 5000 lines by selecting different criteria. However, downloading POs at one go and then action on them in the same spreadsheet would be easier to manage than to create multiple batches.

  • Ivan Pena
    How to enable sourcing of purchase orders to future dated...25.0
    Topic last edited November 29, 2019 by Ivan PenaBronze Crown: 15,000+ Points, tagged Agreements, How-To, Orders, Setup in Procurement > Purchasing public
    Title:
    How to enable sourcing of purchase orders to future dated agreements
    Content:

    Business case

    When a purchase order sourced  to a purchasing agreement is submitted for approval, Oracle Purchasing Cloud validates that the requested delivery dates on the purchase order schedules fall between the effective dates of the source agreement. Instead, you may want to enable the use of future dated agreements, so that a purchase order can be sourced to a purchase agreement that is not yet effective.

    Solution

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

    When this profile option is disabled (i.e, set to No) you can allow submission of purchase orders having purchase order schedules with requested delivery date before the source agreement's start 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 the Manage Purchasing Profile Options page, select the profile option PO_REQUESTED_DELIVERY_DATE_VALIDATION, set the value to No, and save. Refer to the screenshot for an example. 

    Image:
  • Jennifer Pole
    Batching Purchase Orders to Supplier35.0
    Topic last edited December 8, 2019 by Jennifer Pole, tagged Approvals/Notification, Fusion, How-To, Notifications, Orders in Procurement > Purchasing public
    Title:
    Batching Purchase Orders to Supplier
    Summary:
    How to batch POs to Supplier via Communciate Purchasing Documents function.
    Content:

    My client wishes to batch POs to the Supplier.

    The Oracle documentation states that "you can communicate documents to your supplier in batch by scheduling Communicate Purchasing Documents process. The process sends the communication using the method specified on the purchasing document".

    I wish this to be sent via email as set on the POs.

    How do I stop the application from automatically emailing out each PO individually to the Supplier once each PO has been approved, and instead only send one communication for particular suppliers through this process?

     

    Version:
    19C
  • Kumar
    Populate Buyer name automatically through BPM2
    Topic last edited December 10, 2019 by Kumar, tagged Approvals, Approvals/Notification, Orders in Procurement > Purchasing public
    Title:
    Populate Buyer name automatically through BPM
    Summary:
    Populate Buyer name automatically through BPM
    Content:
    Business would like to populate Buyer name automatically on Purchase order through BPM rules. Business Case: Business creates PO automatically once requisition is approved. PO approval rules created with Terms approval First Responder Win. For this approval rules are created. If any of the person approves PO, that person name should populate as "Buyer" on purchase orders. Is it possible to create BPM rules meet business requirements? Ex Approval Groups created with person A, B and C. If B approves PO, B name should populate in PO automatically. We suggested buyer assignments rules but customer is expecting the solution to BPM rules
  • Boyuan Zhu
    Sample Payloads for Purchase Order SOAP Web Service174.6
    Topic last edited October 5, 2017 by Hemal KapasiBronze Trophy: 5,000+ Points, tagged FAQ, Orders, Web Services in Procurement > Purchasing public
    Title:
    Sample Payloads for Purchase Order SOAP Web Service
    Content:

    The purchase order SOAP web service allows buyers to take actions, such as create, change, or cancel, on purchase orders. Sample payloads for different operations can be found in this topic. 

    More details about the purchase order SOAP web service can be found here: https://docs.oracle.com/cloud/latest/procurementcs_gs/OESWP/Purchase_Order_Service_Version_2_PurchaseOrderService_svc_3.htm

  • Max Basandrai
    Close Purchase Order Status45.0
    Topic posted October 11, 2018 by Max BasandraiBlue Ribbon: 750+ Points, tagged Create Requisition, Financials, Fusion, Orders, Payables, Requisition Processing, Setup in Procurement > Purchasing public
    Title:
    Close Purchase Order Status
    Summary:
    Change status of Open PO to Closed
    Content:

    In Cloud R12, we were able to close a PO (change status from Open to Closed) and no AP Invoices were able to match.

    Now in R13 when the PO status changes from "Open to Closed", an AP Invoice can still be matched?

    Version:
    Revision 13.18.05 (11.13.18.05.0)
  • Jon Kelly
    How to default the ship-to location on XML order placed...15.0
    Topic posted December 5, 2019 by Jon KellySilver Trophy: 7,500+ Points, tagged How-To, Orders, Setup in Procurement > Purchasing public
    Title:
    How to default the ship-to location on XML order placed through OSN
    Content:

    We are in the process of creating a punchout catalog where we want to only have one specific ship-to location. Regardless of what the user chooses on the requisition, the order should always ship to a specific site. In the XML, I can see the ShipToLocationId value, and I'm trying to find a way to default that. We are on 19D and using OSN for the first time. Has anyone done this and able to provide some guidance? Thanks for your help!

    <ns1:ShipToLocationId>300000006760780</ns1:ShipToLocationId>

    Jon

  • Leigh Holling
    Attachments to Purchase Order5
    Topic posted December 2, 2019 by Leigh HollingRed Ribbon: 250+ Points, tagged Orders, Public Sector, Setup in Procurement > Purchasing public
    Title:
    Attachments to Purchase Order
    Content:

    When Purchase orders are been created on the system it is attaching any attachment that is atttached to the site of the supplier the Order is raised for.

     

    How do we disable attaching anything from Suppliers to Purchase Orders.


    Thank you

    Version:
    19C
  • Rain Tsui
    How to enable requested delivery date validation against...45.0
    Topic last edited December 5, 2019 by Rain TsuiRed Ribbon: 250+ Points, tagged Agreements, Approvals, How-To, Orders in Procurement > Purchasing public
    Title:
    How to enable requested delivery date validation against agreement's effective dates
    Content:

    Business Case

    You want to enforce the agreement's start and end dates based on delivery 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 dates. 

    Example

    You have created the  following agreement:

    Agreement Number

    Start Date

    End Date

    123 01-FEB-2019 30-MAR-2019

    A PO with requested delivery date of 01-JAN-2019 will fail submission validation if the agreement 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=1552919682000&api=v2