Purchasing

Get Involved. Join the Conversation.

Posts

  • Boyuan Zhu
    Sample Payloads for Purchase Order SOAP Web Service164.6
    Topic posted October 5, 2017 by Boyuan ZhuBronze Trophy: 5,000+ Points, tagged FAQ, Orders, Web Services 
    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

  • Boyuan Zhu
    How to Exchange Messages through Oracle Supplier Network...95.0
    Topic posted 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)
  • Janak Mehta
    Difference in WSDL for PurchaseOrderServiceV2 between 2...9
    Topic posted May 21, 2019 by Janak MehtaGreen Ribbon: 100+ Points, tagged Web Services 
    Title:
    Difference in WSDL for PurchaseOrderServiceV2 between 2 environments
    Summary:
    Difference in WSDL for PurchaseOrderServiceV2 between 2 environments
    Content:

    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.

    <sp:Header Name="SignatureConfirmation" Namespace="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd"/>
    <sp:Header Name="SignatureConfirmation" Namespace="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd"/>
    <sp:Header Name="SignatureConfirmation" Namespace="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd"/>
     
    Does anyone know what could be the reason ? 
     
  • RNeha
    Does Employee (Requestor) Expense account default on...75.0
    Topic posted July 4, 2019 by RNehaBlue Ribbon: 750+ Points, tagged How-To, Orders, Web Services 
    Title:
    Does Employee (Requestor) Expense account default on PO (in Charge account) when Importing via FBDI?
    Summary:
    Charge Account default from Employee(Requestor) Expense account on PO during FBDI Import
    Content:

    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?

  • sameer ashturkar
    How to know SOAP request mandatory fields55.0
    Topic posted February 27, 2019 by sameer ashturkarBronze Medal: 1,250+ Points, tagged Fusion, Web Services 
    Title:
    How to know SOAP request mandatory fields
    Summary:
    In SOAP request how to know mandatory fields if it contain many elements
    Content:

    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. 

    Image:
  • Caio Zioli
    Is it possible to convert a Requisition into a Purchase...Answered4
    Topic posted October 9, 2019 by Caio ZioliGold Trophy: 10,000+ Points, tagged Web Services 
    Title:
    Is it possible to convert a Requisition into a Purchase order through an web service ?
    Content:

    Hi all, please, i've being reviewing the soap web service "Purchase Order Service Version 2" in order to figure out if it's possible to create a purchase order with backing requisition using an web service. I couldn't find any attribute to input the backing requisition details while invoking the create the purchase order operation.

    Is it even feasible ? Or the only way to convert it is through the UI ?

    Tks  a lot

    Kind Rgds

     

    Soap WS - Purchase Order Service Version 2 : https://docs.oracle.com/en/cloud/saas/procurement/19d/oeswp/business-object-services.html#purchaseorderserviceversion2-d17112e1605

     

    Tks a lot

    Kind Rgds

  • Nagesh Manda
    Web / REST Service details for searching BPSAnswered4
    Topic posted May 15, 2019 by Nagesh MandaGold Medal: 3,500+ Points, tagged Agreements, Web Services 
    Title:
    Web / REST Service details for searching BPS
    Content:

    Hi All,

    i am looking for a web / rest service to search for BPA details.

    After looking a the purchasing documentation i could see that we do have PurchaseAgreementService web service available but it doesnt seem to provide an option for querying the details or get method.

    Could you kindly let me know if there are any other services available to enable the searching on BPA details.

    Thanks,

    Nagesh.

  • Boyuan Zhu
    How to Import Orders and Agreements Using the ERP...45.0
    Topic posted November 1, 2018 by Boyuan ZhuBronze Trophy: 5,000+ 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:
  • Raj Kamal
    B2B PO Export using Collabration Message framework3
    Topic posted November 11, 2019 by Raj KamalGreen Ribbon: 100+ Points, tagged Orders, Setup, Supplier Communication, Web Services 
    Title:
    B2B PO Export using Collabration Message framework
    Summary:
    B2B PO Export using Collabration Message framework
    Content:

    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

  • DIEGO SCHENQUERMAN
    PO and PO changes import- FBDI vs Purchasing Web Services3
    Topic posted March 8, 2019 by DIEGO SCHENQUERMANBlue Ribbon: 750+ Points, tagged Approvals, Orders, Web Services 
    Title:
    PO and PO changes import- FBDI vs Purchasing Web Services
    Summary:
    PO and PO changes import- FBDI vs Purchasing Web Services
    Content:

    Hi,

    We need to import Purchase Order and Purchase Order changes from JDE to Oracle Cloud. Customer is making a lot of changes in the Purchase Order and I want to know what could be the best option: a) FBDI, b) Purchasing Web Services (I read the Oracle Fusion Purchasing Web Services Examples (Doc ID 2466289.1))

    Second, Can we process PO Changes using FBDI?