For partners that build or integrate commercially available applications and service solutions with the Oracle Cloud Platform
For partners that provide implementation or managed services around Oracle Cloud Applications
Hi,
I am trying to setup B2B Collaboration messaging using a service provider to send Purchase Order. Jaggaer is our middleware vendor. I am using web service provided by Jagger however they mentioned that they don’t any authentication on webservice and no userid and password should be passed. When I configure a service provider in "Manage Collaboration Messaging Service Providers" under tools -> Collaboration Messaging without a userid and password, I am getting error Userid is required. Please see attached screenshot for my setup and error message.
Any idea on how i can deal with this situation?
Regards,
Raj
Is there an API or webservice or an ESS Job that can be used to bulk delete incomplete purchase orders?
Hi
We have a client who will be implementing Cloud Procurement for managing purchase orders and use EBS for all receiving and AP invoicing. In the cloud they will not manage any inventory. Hence when the receipts are done against the PO in EBS, we want to update the same in cloud against that PO. Any suggestions on can we meet this requirement?
Thanks
Rajesh
Hi, We have 2 Oracle Cloud Fusion environments. We are using PurchaseOrderServiceV2 Webservice to create/edit POs.
I see a small difference when I compare wsdl files for PurchaseOrderServiceV2 Websrvice from 2 environments we have.
One of the environment have following 3 extra entries.
When Importing an expense PO using FBDI Template, if we provide requestor information on the template, will the charge account default from the employee expense account setttings?
Hi all,
Is there any Doc IDs/Link/ whitepapers or any other Detailed Documentation on understanding how Purchasing Module interacts with other Oracle modules in Procurement, SCM, Financials..etc, from data flow perspective.
Regards,
Harshith E S
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.
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)
Oracle Supplier Network setup (needed for inbound messages)
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.
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.
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.
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.
Hello,
I am trying to create purchase order through soapui tool but when I have imported the respective wsdl into soapui I have seen all request payload elements are optional. how do I find mandatory element to get response.