Automatically Import Source Orders into Order Management

You can use the Order Import Template to manually import orders from your source system into Order Management. This topic describes how to do it automatically.

You use the ERP Integration Service to upload your completed import template to the server that hosts Oracle WebCenter Content, and to run a scheduled process that imports the uploaded file to interface tables, processes them, and imports each interface record as a sales order. For background details about this service, see Using the Oracle ERP Cloud Adapter with Oracle Integration.

Summary of the Set Up

  1. Prepare and import your payload.

  2. Load interface tables.

Prepare and Import Your Payload

  1. Prepare the payload that you will import.

    Use the same format that you apply when you use the Order Import Template. For details, see Overview of Importing Orders Into Order Management.

  2. Save your payload as a zip file. For this example, use my_file.zip.

    This is the file you create when you click Generate CSV File in the template. For details, see Import Orders Into Order Management.

  3. Use your favorite utility to encode my_file.zip to the BASE64 encoding format.

  4. Prepare the erpIntegrationService payload.

    Here's an example payload.

    <soapenv:Envelope xmlns:erp="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/types/">
       <soapenv:Header>
          <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
             <wsu:Timestamp wsu:Id="TS-F2664B61E2C11459A614776888804392">
                <wsu:Created>2016-10-28T21:08:00.439Z</wsu:Created>
                <wsu:Expires>2016-10-28T21:09:00.439Z</wsu:Expires>
             </wsu:Timestamp>
             <wsse:UsernameToken wsu:Id="UsernameToken-3DCAF6FF7D37834B0714678327222631">
                <wsse:Username>XXXXXXX</wsse:Username>
                <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">ZZZZZZZZ</wsse:Password>
             </wsse:UsernameToken>
          </wsse:Security>
       </soapenv:Header>
       <soapenv:Body>
          <typ:uploadFileToUcm>
             <typ:document>
                <erp:Content>UEsDBAoAAAAAAHywWkkAAAAAAAAAAAAAAAAKAAAATkVXIEVSUk9SL1BLAwQUAAAACABqsFpJ46UaP4sCAAC8BgAAGQAAAE5FVyBFUlJPUi9JTlZfUmVxdWVzdC50eHStVd9vmzAQfp+0/wFlz2BDSdIggtZk6RZ1qzaF7qEvkwu3YBVsZps09K+fSfgRUrRJ3SJFwnfffb7v7jh8yUkObOet2A5SnoOxz1Imvdo8HyVK5R5CMkogI9LS3splcbFF1QOCOg6N6khV5m3UwaKxJErBiniGSJ5LzZUhqsOY4qJEGVEgKEmvdoSm5IGmVJWIs4Sw+FtBmKKKguwbyg2IHY3gu4P0bdo7Ct6+MQyjFfMJSAziaKzsT1KCt4GoEDrYaFBZIdUd00CpNPd8ZDcSKnirIeaRlkAklaaWyQ7KNQA5GLsI2+joqk7YNrWj+tc3mfoB9sq0LWztZdzRF69l77EX6lCslr7Ve5RceCHNQGvLcqM6rbXEcGO6y9lq4i7H2L10l6vJYvXBdqfT6jiZzvDEuezxNFRLAbpPceBge2La2HQmoX3pYdvDU0tH3fvoFDVAsNrnVIDsCKahjT33jKBBnSpBPSk916GvdxIEIxmE/BFYq7Rn/avo6YDoE+pA0OcnwoiVEBHzkqTvyZamUGTVUPuojz0haom+EimfuIiNUM/r65tf1HeY6qAqF/ynTqMagHfNDaEeuFFww1MuM67fJrCdizrDBjKY4S1nERgrFvGYsu2/pVm9YKbulyRbMNtxrbJcEAkTd0EZEeUoeE7uZ8l1sru7Thx386twx4/p7dV87qMupf86jDVxbza6LYF6a6JeKWhop7SLZsHjsiPQy8j7VYAoW1Nj1SUjjD4TRTlb8hiCm+XnH9cffTTo/FP0Og4u8PFn45k9dp2XJOv4BUW7b9cKslMO3TY8nvloCHROogTAlypB20e98zlQFg8tVzVKwYWPBu1d7c9q56OzEneG5ksV/AZQSwMEFAAAAAgAdLBaSaddoJiUAQAAcQQAABoAAABORVcgRVJST1IvSU5WX1Jlc3BvbnNlLnR4dKVUwU6DQBC9m/gPG86WQT1JthxqMGrUmlaNnsx2GSnNskt2t7T9e4EWSltqNF4I+2bevNk3DBRl7ocyR6EyJMtUSOMXUN+ZWpv5AIZPMWXGLSJGscxVOobyBXDDASc4PSGEVIVukUWooYUMVLRaH2vkhs2FbaAS/SoRriIMyvgYdY6awhY9yDVWJzIO7gfD3sWV53k+eZW4zJBbjAguOWY2UZJwNo+n1iczljNXMBm7T3MhnlUiLeqwTjsjqYn7soj4pHxulAuNUqOtHaFliWhDJWqlqXpOOIZaK/2IxrC49rKINl5WSOEg4wJdrlJg0ReYnAOWPAPOhrM0ScNZLBbu4rKy/cLzzuH98WFcjaSXSGOZ5OjsNVT3VFlX2UOhOXenpuuW/2Lorwyl0K7erW2wmHZiV8E4fAtHdy8fn+FoNBxR2Al2c9cDIYVfvl1l2HeOzKLDon/K1/TGm2vBjHliKQYz9pM5FI7QDm8I2yt2RI+U2Xxds4ly7yfqr7IUjji4swew1xSFvb2m0Fr99aH+xQTfUEsBAh8ACgAAAAAAfLBaSQAAAAAAAAAAAAAAAAoAJAAAAAAAAAAQAAAAAAAAAE5FVyBFUlJPUi8KACAAAAAAAAEAGAAqIGJSsy/SASogYlKzL9IBIGmkTLMv0gFQSwECHwAUAAAACABqsFpJ46UaP4sCAAC8BgAAGQAkAAAAAAAAACAAAAAoAAAATkVXIEVSUk9SL0lOVl9SZXF1ZXN0LnR4dAoAIAAAAAAAAQAYAFCWKj2zL9IBB0NWNrMv0gEHQ1Y2sy/SAVBLAQIfABQAAAAIAHSwWkmnXaCYlAEAAHEEAAAaACQAAAAAAAAAIAAAAOoCAABORVcgRVJST1IvSU5WX1Jlc3BvbnNlLnR4dAoAIAAAAAAAAQAYAJEiBEmzL9IBeiQmQLMv0gEHQ1Y2sy/SAVBLBQYAAAAAAwADADMBAAC2BAAAAAA=</erp:Content>
                <erp:FileName>E:\WIP\errors.zip</erp:FileName>
                <!--Optional:-->
                <erp:ContentType>zip</erp:ContentType>
                <!--Optional:-->
                <erp:DocumentTitle>PCTitle002</erp:DocumentTitle>
                <!--Optional:-->
                <erp:DocumentAuthor>Diane Cho</erp:DocumentAuthor>
                <!--Optional:-->
                <erp:DocumentSecurityGroup>FAFusionImportExport</erp:DocumentSecurityGroup>
                <!--Optional:-->
                <erp:DocumentAccount>scm$/sourceSalesOrder$/import$</erp:DocumentAccount>
                <!--Optional:-->
                <erp:DocumentName>PCName002</erp:DocumentName>
                <!--Optional:-->
                <erp:DocumentId>002</erp:DocumentId>
             </typ:document>
          </typ:uploadFileToUcm>
       </soapenv:Body>
    </soapenv:Envelope>
    

    Note

    Code

    Value

    UsernameToken

    Add this token while you're creating the payload in SOAP UI.

    1. Open your payload in SOAP UI.

    2. Click Auth.

    3. In the Authorization area, enter your user name and password.

    4. Position your cursor in the payload where you need to add the token. In this example, position it immediately after the Timestamp tag.

    5. Right-click in the payload, then click Add WSS Username Token.

      SOAP UI adds the entire UsernameToken tag to your payload.

    For details, see How to Use SoapUI to Invoke a Web Service (Doc ID 2234114.1).

    erp:content

    Insert the BASE64 content that you encoded earlier in this procedure into erp:content.

    erp:content stores the details of the file that you're importing in BASE64. This BASE64 content represents the sales order data that you created through file-based data import.

    FileName

    If your upload fails, examine the errors.zip file. It contains details about why the upload failed.

    DocumentTitle

    Use PCTitle002.

    DocumentAuthor

    Enter your name. You can use it later when you verify the upload. For this example, assume your name is Diane Cho.

    erp:DocumentAccount

    Use scm$/sourceSalesOrder$/import$ because it identifies the account you use when you run the scheduled process that imports sales orders later in this procedure.

    DocumentName

    Enter any alphanumeric value. Use a maximum value of 30 characters.

    This example uses PCName002.

    Learn about the attributes in this payload. For details, go to SOAP Web Services for Financials, then expand Business Object Services > ERP Object Descriptive Flexfield Update Service > Document Information.

  5. Use this URL to access the WSDL for the service.

    https://servername/fscmService/ErpIntegrationService?WSDL
  6. Use the uploadFiletoUcm operation to upload and submit your payload.

    go to SOAP Web Services for Financials, then search for uploadFiletoUcm.

  7. Notice the document Id that the submit returns. You use it when you verify the scheduled process.

  8. Verify the import.

    • Sign into Oracle Applications, then go to the File Import and Export work area.

    • On the Overview page, enter Diane Cho in the Owner attribute, then click Search.

    • Examine the search results and verify that it contains the errors.zip file and the sourceSalesOrder file.

      File

      Account

      Owner

      errors.zip

      scm/sourceSalesOrder/import

      Diane Cho

      sourceSalesOrder

      scm/sourceSalesOrder/import

      Diane Cho

      The sourceSalesOrder file is now on the server. You will reference next when you run the scheduled process.

Load Interface Tables

  1. Make a SOAP call.

    Here's an example payload you can use when you use the submitESSJobRequest operation in your SOAP UI call.

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/types/">
       <soapenv:Header>
          <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
             <wsu:Timestamp wsu:Id="TS-F2664B61E2C11459A614776898797693">
                <wsu:Created>2016-10-28T21:24:39.768Z</wsu:Created>
                <wsu:Expires>2016-10-28T21:25:39.768Z</wsu:Expires>
             </wsu:Timestamp>
             <wsse:UsernameToken wsu:Id="UsernameToken-3DCAF6FF7D37834B0714678327222631">
                <wsse:Username>XXXXXXX</wsse:Username>
                <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">ZZZZZZZ</wsse:Password>
             </wsse:UsernameToken>
          </wsse:Security>
       </soapenv:Header>
       <soapenv:Body>
          <typ:submitESSJobRequest>
             <typ:jobPackageName>/oracle/apps/ess/financials/commonModules/shared/common/interfaceLoader</typ:jobPackageName>
             <typ:jobDefinitionName>InterfaceLoaderController</typ:jobDefinitionName>
             <typ:paramList>72</typ:paramList>
             <typ:paramList>24131</typ:paramList>
          </typ:submitESSJobRequest>
       </soapenv:Body>
    </soapenv:Envelope>
    

    Note

  2. Use the getESSJobStatus operation in your SOAP UI call to get the status of your scheduled process.

    Here's an example payload.

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/types/">
       <soapenv:Header>
          <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
             <wsu:Timestamp wsu:Id="TS-F2664B61E2C11459A614776903991084">
                <wsu:Created>2016-10-28T21:33:19.108Z</wsu:Created>
                <wsu:Expires>2016-10-28T21:34:19.108Z</wsu:Expires>
             </wsu:Timestamp>
             <wsse:UsernameToken wsu:Id="UsernameToken-3DCAF6FF7D37834B0714678327222631">
                <wsse:Username>XXXXXXX</wsse:Username>
                <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">ZZZZZZZ</wsse:Password>
             </wsse:UsernameToken>
          </wsse:Security>
       </soapenv:Header>
       <soapenv:Body>
          <typ:getESSJobStatus>
             <typ:requestId>55562</typ:requestId>
          </typ:getESSJobStatus>
       </soapenv:Body>
    </soapenv:Envelope>
    

    typ:requestId>55562 identifies the scheduled process that runs when you submit the submitESSJobRequest operation.