Payments Wallet Configuration and Migration to another environment in Oracle Fusion Cloud

Let's see how to configure the Payments Wallet in Oracle Fusion Cloud as well as the steps to Migrate the wallet from one environment to another. Migration steps are to be performed in case P2T or T2T refresh activities are being performed and there's need to migrate the wallet from one POD to another.

Steps to create Payments Wallet:

- Navigate to Setup and Maintenance

- Search for Manage System Security Options 

- Find out 'Apply Quick Defaults' button

- If this button is Disabled, that means the wallet has already been created and no further action is needed

- If this button is Enabled, then you can create a new wallet by clicking on Apply Quick Defaults button

- Once the pop-up is shown, select the first option to Create empty wallet 

- Save

This will create the Payments Wallet and system key in Fusion Cloud.

The wallet information can be checked by querying IBY_SYS_SECURITY_OPTIONS table which should contain one record pointing to the payment wallet.

Output:

Steps to Migrate Payments Wallet from one environment to another:


Steps to be performed in the Source Environment:

- Run ESS job named 'Import Security Credential Job'

- Specify the 'Credential File Type' parameter as 'Export Payments Wallet'

- Leave all other parameters as blank

- One the ESS job completes, a file with the name 'IBY_OPSS_contents.ks' will be generated in the fin/payments/import folder in UCM.

- To see this, navigate to File Import and Export option

- Download and save this file on your machine.

Steps to be performed in the Target Environment:


- We need to upload aforementioned .ks file on the Target environment in fin/payments/import UCM folder.

- Navigate to File Import and Export page and upload the file 'IBY_OPSS_contents.ks' from local machine to the fin/payments/import Account

- Run the ESS Job 'Import Security Credential Job' 

- Specify the 'Credential File Type' parameter as 'Import Payments Wallet'

- Leave all other parameters as blank

- Once the ESS job completes, the wallet contents are imported into the target environment

- The newly imported wallet information can be checked by querying IBY_SYS_SECURITY_OPTIONS table which should contain one record pointing to the payment wallet, as shown in first section of this blog.

Read More

How to use SOAP APIs to Automate Migration of BIP Reports to another environment in Oracle Fusion

In the previous post, we saw how to manually migrate various reports in Oracle Fusion Cloud to another environments.

In this blog, let's see how we can automate migration of BI Publisher reports using BI Publisher SOAP APIs offered by Oracle Fusion Cloud.

We need to use below SOAP API provided by Fusion/ERP Cloud in order to download/upload various BIP components.

Catalog Service WSDL for creating connections:
https:// <SourceServer/DestinationServer>.fa.us2.oraclecloud.com/xmlpserver/services/v2/CatalogService?wsdl


Source Report to be migrated:

Request Payload to Download the BIP report from source instance:

<x:Envelope

    xmlns:x="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:v="http://xmlns.oracle.com/oxp/service/v2">
    <x:Header/>
    <x:Body>
        <v:downloadObject>
            <v:reportAbsolutePath>Your report path </v:reportAbsolutePath>
            <v:userID>username</v:userID>
            <v:password>password</v:password>
        </v:downloadObject>
    </x:Body>
</x:Envelope>

Response Payload will contain the Encoded base64 data:

Request Payload to Upload the BIP report to destination instance:

The above returned encoded data need to be passed as input to the below along with report absolute path:

<x:Envelope

    xmlns:x="http://schemas.xmlsoap.org/soap/envelope/"

    xmlns:v="http://xmlns.oracle.com/oxp/service/v2">

    <x:Header/>

    <x:Body>

        <v:uploadObject>

 <v:reportObjectAbsolutePathURL>/Custom/Financials/Payables/TestUpload/</v:reportObjectAbsolutePathURL>

            <v:objectType>xdoz</v:objectType>

            <v:objectZippedData>[base64Binary?]</v:objectZippedData>

            <v:userID>?</v:userID>

            <v:password>?</v:password>

        </v:uploadObject>

    </x:Body>

</x:Envelope>

Result:

More operations offered by BI Publisher SOAP API:


Create Folder:

This operation lets you create a new custom folder in the desired path.

Payload:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v2="http://xmlns.oracle.com/oxp/service/v2">

   <soapenv:Header/>

   <soapenv:Body>

      <v2:createFolder>

         <v2:folderAbsolutePath>/Custom/Financials/Payables/TestUpload/Custom Folder</v2:folderAbsolutePath>

         <v2:userID>username</v2:userID>

         <v2:password>password</v2:password>

      </v2:createFolder>

   </soapenv:Body>

</soapenv:Envelope>

Result:

Rename Report:

This operation lets you rename an existing report to a new name.

Payload:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v2="http://xmlns.oracle.com/oxp/service/v2">

   <soapenv:Header/>

   <soapenv:Body>

      <v2:renameObject>

         <v2:objectAbsolutePath>/Custom/Financials/Payables/CUSTOM_INVOICES.xdo</v2:objectAbsolutePath>

         <v2:newName>NEW_CUST_INV</v2:newName>

         <v2:userID>username</v2:userID>

         <v2:password>password</v2:password>

      </v2:renameObject>

   </soapenv:Body>

</soapenv:Envelope>

Result:

Delete Report:

This operation lets you delete any existing report.

Payload:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v2="http://xmlns.oracle.com/oxp/service/v2">

   <soapenv:Header/>

   <soapenv:Body>

      <v2:deleteObject>

         <v2:objectAbsolutePath>/Custom/Financials/Payables/NEW_CUST_INV.xdo</v2:objectAbsolutePath>

         <v2:userID>username</v2:userID>

         <v2:password>password</v2:password>

      </v2:deleteObject>

   </soapenv:Body>

</soapenv:Envelope>

Result:

Read More