Purchasing

Get Involved. Join the Conversation.

Topic

    Boyuan Zhu
    How to Import Orders and Agreements Using the ERP...
    Topic posted November 1, 2018 by Boyuan ZhuGold Medal: 3,500+ Points, last edited November 1, 2018, tagged Agreements, How-To, Orders, Web Services 
    531 Views, 4 Comments
    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:

    Comment