Purchasing

Get Involved. Join the Conversation.

Posts

  • Boyuan Zhu
    How to Share Saved Searches with Other Users25.0
    Topic posted November 30, 2018 by Boyuan ZhuGold Medal: 3,500+ Points, tagged How-To 
    Title:
    How to Share Saved Searches with Other Users
    Content:

    Oracle Purchasing Cloud users can create personal saved searches to store queries for future use. As a procurement administrator, you can create saved searches that are available to all users of that page. You can use this ability to share common queries important to your organization and to save your users the need to enter criteria manually. In this example, you will add a new saved search to the Manage Orders page and make the saved search available to all users.  

    1. Enter a sandbox and navigate to the page that you want to configure. 
    2. In the Settings and Actions menu in the top right corner, click Edit Page. 
    3. Make sure that the editor is in Design mode (View dropdown top left of the page).
    4. Set up your search criteria and save the search. 
    5. Publish the sandbox, and the saved search will be available for all users.
    Document:
  • Boyuan Zhu
    How to Create Change Orders with a Script5.0
    Topic posted November 1, 2018 by Boyuan ZhuGold Medal: 3,500+ Points, tagged Orders, Web Services 
    Title:
    How to Create Change Orders with a Script
    Content:

    You can call the Purchase Order Service V2 to create change orders to keep your orders up to date. For example, you can use change orders to correct attribute values that have been defaulted to an undesired value or migrated from a legacy system with the wrong value. If you need to modify only a few orders, you can use the sample payloads in our previous post and a client like SoapUI. If you want to create many change orders, it is easier to do so using a script. In the following use case, orders have been created with the invoice match option set to Receipt, but now the business would like to set the option to Order for each schedule. 

    1. To use the script, you need to feed it data on the orders/lines/schedules/distributions you want to change. You can generate this data by running a data model on BI Publisher. The example code below will output an XML of all the schedules you need to update by selecting the schedules with invoice match option as Receipt and no receiving or invoicing has taken place. The XML also includes the desired new invoice match option (Order) for each schedule and the change order description for the header. You can save the output as data.xml in the script directory.

    SELECT pll.po_header_id AS HEADERID,
    pll.po_line_id AS LINEID, 
    pll.line_location_id AS SCHEDULEID,
    'Change match option' AS CHANGEORDERDESC,
    'Order' AS MATCHOPTION
    FROM po_line_locations_all pll, 
     po_distributions_all pod 
    WHERE
    pll.SCHEDULE_STATUS = 'OPEN' 
    AND pll.match_option = 'R' 
    AND pod.line_location_id = pll.line_location_id 
    AND NOT EXISTS 
     (SELECT 'txnexists' 
     FROM rcv_transactions rt 
     WHERE rt.po_line_location_id = pll.line_location_id) 
    AND NOT EXISTS 
     (SELECT 'invoiceexists' 
     FROM AP_INVOICE_DISTRIBUTIONS_ALL ap 
     WHERE ap.PO_DISTRIBUTION_ID = pod.PO_DISTRIBUTION_ID)
    

    2. To run the script (createChangeOrder.py attached below), you need the zeep SOAP library. You can install it using pip, or change the script to use your preferred SOAP library. 

    3. When you run the script, it reads the data.xml file and make a web service call for each order changed. For each order, the invoice match option on the selected schedules is updated to the desired invoice match option. You can change or add new attributes to the payload by changing BI Publisher SQL, and then parsing and referencing the output data in the script. Supported attributes can be found in the service definition

    Document:
  • Boyuan Zhu
    How to Import Orders and Agreements Using the ERP...45.0
    Topic posted November 1, 2018 by Boyuan ZhuGold Medal: 3,500+ Points, tagged Agreements, How-To, Orders, Web Services 
    Title:
    How to Import Orders and Agreements Using the ERP Integration Service
    Content:

    You can use the ERP Integration Service to automate file based data import (FBDI) between your system and Oracle Procurement Cloud. For example, you can create a program to convert import data from your system into the FBDI CSV format, encode the resulting ZIP file into the SOAP payload, and invoke the integration web service with the payload. The following section contains example payloads for importing purchase orders, blanket purchase agreements and contract purchase agreements. 

    Each payload includes a ParameterList of parameters for the import job. The examples below explain, in order, what each parameter is and what values are valid. Note that the parameters and the order of the parameters differ for each job. To figure out the value for id based parameters, you can look at the values for previous jobs on the Scheduled Processes Page, as seen in the screenshot below.

    Import SPO 

    Payload:

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/types/" xmlns:erp="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/">
     <soapenv:Header/>
     <soapenv:Body>
     <typ:importBulkData>
     <typ:document>
     <erp:Content>INSERT YOUR ZIP FILE IN BASE64 ENCODING HERE</erp:Content>
     <erp:FileName>PoImportOrders.zip</erp:FileName>
     </typ:document>
     <typ:jobDetails>
     <erp:JobName>/oracle/apps/ess/prc/po/pdoi,ImportSPOJob</erp:JobName>
     <erp:ParameterList>204,100010026863783,NONE,204,2021,N,#NULL,N</erp:ParameterList>
     </typ:jobDetails>
     </typ:importBulkData>
     </soapenv:Body>
    </soapenv:Envelope>
    

    Parameters: 

    Procurement BU: Specify the id of the Procurement business unit that these documents should be imported into.

    Buyer: Specify the id of the buyer to be used when one is not included in the import data.

    Approval Action: NONE - Imports the document in Incomplete status requiring manual interaction. SUBMIT - Imports the document and submits it to the approval process after the document is imported. BYPASS - Imports the document in Open (approved) status without going through the approval process.

    Default Requisitioning BU: Specify the id of the Requisitioning business unit to be used when one is not included in the import data.

    Batch ID: Enter the value for your import data from the file-based data import template, to select the interface table data to be processed in the current run. For example: Batch ID = 123. Use it in conjunction with Import Source to identify the documents to be loaded to the application tables.

    Create or Update Item: Y to create an item that does not exist or update an existing item. N to not create or update any items. 

    Import Source: Enter the value for your import data from the file-based data import template, to select the interface table data to be processed in the current run. For example: Import Source = External Contracts. Use it in conjunction with Batch ID to identify the documents to be loaded to the application tables.

    Communicate Document: Y to have imported purchasing documents communicated to the supplier. N to not have imported purchasing documents communicated to the supplier.

     

    Import BPA 

    Payload:

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/types/" xmlns:erp="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/">
     <soapenv:Header/>
     <soapenv:Body>
     <typ:importBulkData>
     <typ:document>
     <erp:Content>INSERT YOUR ZIP FILE IN BASE64 ENCODING HERE</erp:Content>
     <erp:FileName>PoImportBlanketAgreements.zip</erp:FileName>
     </typ:document>
     <typ:jobDetails>
     <erp:JobName>/oracle/apps/ess/prc/po/pdoi,ImportBPAJob</erp:JobName>
     <erp:ParameterList>204,100010026863783,N,NONE,2021,#NULL,N</erp:ParameterList>
     </typ:jobDetails>
     </typ:importBulkData>
     </soapenv:Body>
    </soapenv:Envelope>
    

    Parameters: 

    Procurement BU: Specify the id of the Procurement business unit that these documents should be imported into.

    Buyer: Specify the id of the buyer to be used when one is not included in the import data.

    Create or Update Item: Y to create an item that does not exist or update an existing item. N to not create or update any items. 

    Approval Action: NONE - Imports the document in Incomplete status requiring manual interaction. SUBMIT - Imports the document and submits it to the approval process after the document is imported. BYPASS - Imports the document in Open (approved) status without going through the approval process.

    Batch ID: Enter the value for your import data from the file-based data import template, to select the interface table data to be processed in the current run. For example: Batch ID = 123. Use it in conjunction with Import Source to identify the documents to be loaded to the application tables.

    Import Source: Enter the value for your import data from the file-based data import template, to select the interface table data to be processed in the current run. For example: Import Source = External Contracts. Use it in conjunction with Batch ID to identify the documents to be loaded to the application tables.

    Communicate Document: Y to have imported purchasing documents communicated to the supplier. N to not have imported purchasing documents communicated to the supplier.

     

    Import CPA

    Payload:

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/types/" xmlns:erp="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/">
     <soapenv:Header/>
     <soapenv:Body>
     <typ:importBulkData>
     <typ:document>
     <erp:Content>INSERT YOUR ZIP FILE IN BASE64 ENCODING HERE</erp:Content>
     <erp:FileName>PoImportContractAgreements.zip</erp:FileName>
     </typ:document>
     <typ:jobDetails>
     <erp:JobName>/oracle/apps/ess/prc/po/pdoi,ImportCPAJob</erp:JobName>
     <erp:ParameterList>204,100010026863783,NONE,2021,#NULL,N</erp:ParameterList>
     </typ:jobDetails>
     </typ:importBulkData>
     </soapenv:Body>
    </soapenv:Envelope>
    

    Parameters: 

    Procurement BU: Specify the id of the Procurement business unit that these documents should be imported into.

    Buyer: Specify the id of the buyer to be used when one is not included in the import data.

    Approval Action: NONE - Imports the document in Incomplete status requiring manual interaction. SUBMIT - Imports the document and submits it to the approval process after the document is imported. BYPASS - Imports the document in Open (approved) status without going through the approval process.

    Batch ID: Enter the value for your import data from the file-based data import template, to select the interface table data to be processed in the current run. For example: Batch ID = 123. Use it in conjunction with Import Source to identify the documents to be loaded to the application tables.

    Import Source: Enter the value for your import data from the file-based data import template, to select the interface table data to be processed in the current run. For example: Import Source = External Contracts. Use it in conjunction with Batch ID to identify the documents to be loaded to the application tables.

    Communicate Document: Y to have imported purchasing documents communicated to the supplier. N to not have imported purchasing documents communicated to the supplier.

    Document:
  • Aditya Singh
    How to Default Custom Accrual and Charge account on...Answered44.8
    Topic posted September 22, 2018 by Aditya SinghBronze Trophy: 5,000+ Points, tagged Setup 
    Title:
    How to Default Custom Accrual and Charge account on Purchasing Documents (Inventory and Expense)
    Summary:
    How to Default Custom Accrual and Charge account on Purchasing Documents (Inventory and Expense)
    Content:

    Hi All,

    Usually many of us come across the scenario where we need to defaults account on requisition or purchasing documents.

    Here in fusion there is good structured SLA setup to do the same.

    I have created a document which will walk you through the SLA of purchasing and the setups need to be done to default accrual and charge account on purchasing documents.

    Thanks

    Aditya Singh

  • Manavalan Ethirajan
    How to reassign POs when buyer left the organization5.0
    Topic posted December 31, 2018 by Manavalan EthirajanSilver Medal: 2,000+ Points, tagged How-To, Orders 
    Title:
    How to reassign POs when buyer left the organization
    Content:

    Requirement: Buyer has left the organization and there are volume of Purchase Orders that have not been changed to finally close. Need to provide additional rights to some other user to make the changes to the eligible Purchase Orders.

    Option 1:

    You can run a process to reassign purchasing documents from one buyer to another, including purchase agreements, contract agreements and purchase orders. To run the process use the Reassign Purchasing Documents task, from the Purchase Agreements or Purchase Orders work area. To use the Reassign Purchasing Documents task you must have a role with the Reassign Purchasing Document privilege. For example, Procurement Manager, Category Manager or Buyer. Refer the attached 'Reassign Purchasing Documents' image.

    Option 2:

    Set the other agent’s access to ‘Full’ for Purchase Orders in procurement agent setup. With this setup, other agents can access Purchase Orders created by buyers who left the organization. Please refer 'Manage Procurement Agents' image.

    Image:
    Document:
  • Manjula Evans
    Oracle Cloud Applications Enterprise Structures Whitepaper55.0
    Topic posted September 18, 2018 by Manjula EvansBlue Ribbon: 750+ Points, tagged How-To, White Paper 
    Title:
    Oracle Cloud Applications Enterprise Structures Whitepaper
    Content:

    This whitepaper provides an overview of the principal Oracle Cloud Applications enterprise structures common to all product families including charts of accounts, ledgers, business units and legal entities. Included is an explanation of how Oracle Cloud Application business units relate to each other and the implications for transaction flows between them. Lastly, this paper documents some best practices to ensure a smooth and fully supported Oracle Cloud Applications implementation.

    Please refer to Doc ID 2415848.1 for more details.

  • Ivan Pena
    How to Import Purchase Orders with Attachments45.0
    Topic posted June 14, 2018 by Ivan PenaBronze Crown: 15,000+ Points 
    Title:
    How to Import Purchase Orders with Attachments
    Content:

    When you import orders, you may want to include attachments as well. The ability to add attachments to a purchase order using the ERP web service is planned for a future release. In the meantime, you can take the following approach:

    1. Navigate to the Configure Requisitioning Business Function page and disable the "Create orders immediately option after requisition import" option
    2. Fill in the Import Requisitions FBDI template with data for the Purchase Orders to be imported. Populate the emergency PO number in the template with the desired number for the  PO being imported. 
    3. The requisitions will be created, but not yet converted to orders. At this point, you can call the UploadAttachment operation of the ErpObjectAttachmentSoap web service to add attachments to the requisitions. Please review Uploading Attachments to Requisitions Using ERP Object Attachment Service (Doc ID 2261597.1)
    4. After adding the attachments, you can convert the requisitions to purchase orders by submitting the Generate Orders process , The attachments added to the requisitions will be copied over to the newly created purchase orders.
     
  • Manavalan Ethirajan
    Oracle Procurement Cloud White Papers15.0
    Topic posted January 18, 2018 by Manavalan EthirajanSilver Medal: 2,000+ Points, tagged White Paper 
    Title:
    Oracle Procurement Cloud White Papers
    Content:

    You can review the latest list of white papers for Oracle Procurement Cloud in the Support Note 2177707.1.

    Please feel free to post any questions or comments here.

     

  • Boyuan Zhu
    How to Exchange User-Defined cXML Messages via Oracle...5.0
    Topic posted July 29, 2019 by Boyuan ZhuGold Medal: 3,500+ Points, tagged How-To, Orders, Supplier Communication 
    Title:
    How to Exchange User-Defined cXML Messages via Oracle Supplier Network
    Content:

    As of release 19B, you can exchange user-defined cXML messages with your trading partners via Oracle Supplier Network. You can use this capability to customize your messages to meet your partners' requirements. To send a user-defined cXML message, you need to define a cXML message with custom mapping, create a custom service provider pointing to OSN, and use this service provider and message when setting up trading partners on your supplier sites.

    1. First, define a new message by going to Manage Collaboration Message Definitions in the Collaboration Messaging Workarea. For the message you want to customize, download the existing transformation file by taking the Export Transformation Package action. You can then customize the transform file as you wish. 
    2. Duplicate the existing cXML message and upload your customized transform file. This is now the message you will be using in the future steps. 
    3. Create a service provider in the Manage Collaboration Service Providers task. If you have different customizations for different trading partners, you will need to create a separate message and service provider for each case.
    4. For the service provider, add a Delivery Method, using the delivery method type as “Web Service”. In the Service Name field, select the Service Name as CollaborationMessageV2.Process. Specify the following: 
      • Endpoint: https://osn.oracle.com/HTTPService/ProcessSOAPCollaborationMessage or https://osn-prod.oracle.com/HTTPService/ProcessSOAPCollaborationMessage.
      • User Name: The Oracle Supplier Network buyer account user name
      • Password: The Oracle Supplier Network buyer account password 
      ​​
    5. Add the message from earlier and use the delivery method you created. Set the status as Active and save. 
    6. Make sure that the correct documents are set up on OSN and that your supplier site is using the new service provider and message. The Collaboration Messaging Framework will transform your message into cXML using your defined mapping before invoking OSN.
    Document:
    Document:
    Document:
    Document:
  • Boyuan Zhu
    How to Exchange Messages through Oracle Supplier Network...35.0
    Topic posted July 29, 2019 by Boyuan ZhuGold Medal: 3,500+ 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)