Purchasing

Get Involved. Join the Conversation.

Posts

  • 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 
    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 
    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
  • Akash Jadhao
    Change Order Cost Center manager Approval at line level14
    Topic posted November 6, 2019 by Akash JadhaoRed Ribbon: 250+ Points, tagged Approvals, Approvals/Notification, Fusion, How-To, Setup 
    Title:
    Change Order Cost Center manager Approval at line level
    Summary:
    Whenever there is change order happens against PO and changes done at line level the change order should follow newly added line cost center manager approval hierarchy not the existing lines
    Content:

    There is change order(XX)exist against PO (***) and which are having status either Incomplete/Pending Approvals or Approved.

    Requirement : If new line are been added in to change order(XX) then it should always follow the newly added lines (cost center) approval hiearachy. 

    Rules are written on amount changed at header level including the cost center numbers with respect cost center manger approvals and which is working fine.

    User needs that,if there is additonal line added in the change order then it should only follow the added lines cost center manager approvals not the exisiting lines cost center approvers.

    Is there any attributes where We can compare the cost center with existing lines cost center and build approval hieararchy around it.

    Can any one help on the same.

     

     

    Version:
    Fusion 19C
    Image:
  • 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 
    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

  • 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 
    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

     
  • Eren Göktepe
    PO or PR Approvals - Same Approvers need to be passed65.0
    Topic posted December 5, 2019 by Eren GöktepeRed Ribbon: 250+ Points, tagged Approvals, Approvals/Notification, How-To, Orders, Requisition Processing 
    Title:
    PO or PR Approvals - Same Approvers need to be passed
    Summary:
    Same Approvers shouldnt approve or reject for PO or PR. One approve must be enoughf
    Content:

    Hi,

    I used 3 stage for PO and PR basicly. Like;

    Manager of Requester > Manager of Business > Project Manager

    These can be same users. Like Eren G. > Eren G. > Eren G

    When we faced like this case. I want to terminate with first stage. Its not necessary to send approval message again and again.

    How we can pass same users ?

     

    Thanks

    E.

     

     

     

     

     

    Version:
    Oracle Cloud Application 19C (11.13.19.07.0)
  • Boyuan Zhu
    How to Exchange Messages through Oracle Supplier Network...95.0
    Topic last edited July 29, 2019 by Boyuan ZhuBronze Trophy: 5,000+ Points, tagged How-To, Orders, Supplier Communication, Web Services 
    Title:
    How to Exchange Messages through Oracle Supplier Network Using a Web Service
    Content:

    You can now set up Collaborative Messaging Framework to exchange messages with your suppliers through Oracle Supplier Network (OSN) using a web service. Routing messages using a web service simplifies message exchange between Fusion Applications and OSN. Messages will no longer be routed through Oracle B2B and you will not need to do any setup in Oracle B2B. This guide covers the configuration you need to perform in Fusion Applications and OSN to support message exchange using a web service. 

    Fusion Applications setup (needed for outbound messages)

    1. In the Manage Collaboration Service Provider task, select the OracleSN or OracleSNTest service provider. 
    2. If you are updating your test pod: 
      1. Select the ORA_B2BMessageTestService delivery method.
      2. Set the endpoint to https://osn.oracle.com/HTTPService/ProcessSOAPCollaborationMessage
      3. User Name: The buyer account user name that was used for the HTTP connection
      4. Password: The buyer account password that was used for the HTTP connection
    3. If you are updating your production pod, follow the same steps in 2, but set the endpoint to https://osn-prod.oracle.com/HTTPService/ProcessSOAPCollaborationMessage
    4. In the Outbound Collaboration Messages tab, change the status of all messages to “Inactive”, then update the Delivery Method from ORA_OracleSNOneWayHTTP to ORA_B2BMessageTestService. Note that this step is not applicable for new customers. 
    5. Change the status of all outbound messages to Active (applicable for all customers).


    Oracle Supplier Network setup (needed for inbound messages)

    1. Login as the buyer to OSN and select Messaging Setup. 
    2. Under Communication Parameters, add a new SOAP Service delivery method 
    3. Specify the endpoint URL for the service that Oracle Supplier Network will invoke to send messages to the Collaboration Messaging Framework. The URL is https://<host>/soa-infra/services/default/CmkCollaborationMessagingInboundServiceComposite/CollaborationMessageServiceV2. Replace <host> with the appropriate values from your test and production pod.
    4. Specify a user name and password for your test and production pods. Note that the user specified here must be a valid Fusion user and must have the Invoke Collaboration Message Inbound Service privilege (CMK_INVOKE_INBOUND_COLLAB_DOC_SERVICE_PRIV) in the respective pod.
    5. Once you have specified the appropriate values, select Submit. The dialog is closed and the Communication Parameters table now shows the newly added delivery method.
    6. In the Transaction Management table, edit the Transactions with “Receive” action – these are the ones that OSN is going to send to Fusion Applications. If you are a new customer setting up OSN for the first time, this table will not have any records. Update the delivery method to the new method you created. 

     

    Document:
    Document:
    Document:
    EditOSN.png (127KB)
  • Daniel Clancy
    Rolling over open purchase orders fiscal year end process2
    Topic posted November 27, 2019 by Daniel ClancyGreen Ribbon: 100+ Points, tagged How-To, Public Sector 
    Title:
    Rolling over open purchase orders fiscal year end process
    Summary:
    Looking for a step by step guide to rolling over open purchase orders from one fiscal year into the next
    Content:

    Hi, we've attempted to roll over the purchase orders, but are receiving this error message "The funds reserved on this purchase order cannot be released. Contact the procurement application administrator"

    Does procurement have to manually change the budget dates on all open POs?

     

    Version:
    19D
  • Ivan Pena
    How to disable approved supplier validation for BPA
    Topic posted November 29, 2019 by Ivan PenaBronze Crown: 15,000+ Points, tagged Agreements, Approved Supplier List, How-To, Orders, Setup 
    Title:
    How to disable approved supplier validation for BPA
    Content:

    Business Case

    You want to create a blanket purchase agreement (BPA) that include items for which Use Approved Supplier is enabled, and then use it to create approved supplier lists (ASLs) for those items. However, you are not able to submit the BPA for approval because the supplier is not on the approved supplier list for those items. 

     

    Solution

    You can use the profile option "PO_ASL_VALIDATION_FOR_BPA" to skip the blanket purchase agreement submission validation that verifies if the supplier is approved for all items that use approved supplier.

    When this option is disabled, the application will no longer prevent you submitting for approval a BPA that includes items that use approved supplier, even if the supplier is not yet in the list approved suppliers for those items. You can then add the new agreement to an existing ASL or create a new ASL from the agreement using the ESS process "Create ASL Entries."

    How to set up

    You can go to Manage Purchasing Profile Options, select the profile option PO_ASL_VALIDATION_FOR_BPA, set the value to No, and save. Refer to the screenshot below for an example. 

    Image:
  • Anil Nair
    Approved Supplier List (ASL)45.0
    Topic posted December 13, 2018 by Anil NairBronze Medal: 1,250+ Points, tagged Agreements, Approvals, Approvals/Notification, Approved Supplier List, Create Requisition, FAQ, Fusion, How-To, Manage Procurement Catalog, Orders, Requisition Processing, Setup, Supplier Communication, Supply & Distribution Planning Cloud, Tip, White Paper 
    Title:
    Approved Supplier List (ASL)
    Summary:
    Approved Supplier List (ASL)
    Content:

    Hi,

    We have a requirement to restrict any purchasing (Req/Orders) for specific suppliers (Blacklisted).

    The approved supplier list functionality doesn't allow any restriction on Order creation when category and supplier from ASL is used.

    There are no Inventory items for now only categories.

    Also, i'm unable to find the source document - Blanket Purchase Agreements, there is only Contract Purchase Agreement in the drop down list under ASL source documents.The Generate Approved supplier list also doesn't show any agreement numbers.

    Please share if you have come across customers with similar requirement.

    Many thanks.

    Anil