4 Configuration Process for Oracle Cloud ERP Integration

This section describes the necessary configurations for Oracle Integration Cloud, OPERA Cloud, and Oracle Cloud ERP Integration. Before proceeding, ensure you have the required minimum versions of the three Oracle Cloud services as described in this guide. You must have a user with administration privileges in both Oracle Cloud ERP Integration and OPERA Cloud. These users should not be shared with other functions of the cloud services. They should only be used in the context of this accelerator.

Overview of Configuration Process

  1. Create an Integration Administration user in Oracle Fusion Accounts Receivables. This user will be used exclusively for the Oracle Integration Cloud to perform operations in the Oracle Fusion Accounts Receivables using Oracle Integration Cloud ERP Cloud Adapter. For example, name this user ‘Fusion AR Integration Administrator.’ You will assign this user with the following roles: Attachments User Copy, Financial Integration Specialist, ISC Integration Role, Integration Specialist, and Application Implementation Consultant.

  2. Create an OHIP Integration account in Oracle Hospitality Shared Security Domain. This user will be used exclusively for the Oracle Integration authorization activity in the REST Adapter and configuration. For more information, refer to the Using the Oracle Hospitality APIs topic in the Hospitality Integration Platform User Guide.

  3. Create an Integration Developer user in Oracle Integration Cloud. This user will be used exclusively for the Oracle Integration Cloud to perform Oracle Integration cloud operations, such as lookup updates and invoking other integrations in the runtime. For example, name this user ‘Fusion_Opera_Accelerator OIC Service User.’ You will assign this user with the following roles: Service Developer.

  4. Create an Integration Administrator user in File server. This user is used exclusively for the Oracle Integration Cloud to perform File Operations over FTP in the File server using the Oracle Integration Cloud FTP Adapter. For example, name this user ‘Integration Cloud Service User.’ You will assign this user with the following roles: Read/Write Files.

Before proceeding with any configurations, analyze the following table to understand your situation based on the type of deployment.

Table 4-1 Deployments

OPERA Cloud Deployment Oracle Cloud ERP Integration Deployment Comments

New Deployment

New Deployment

  • All customer authoring should be done only in Oracle Fusion Accounts Receivables.

  • Customer Accounts to be synchronized to OPERA Cloud must have the designated "Customer class" associated with them.

  • Depending on data volume, consider initially scheduling the Accelerator to run at a shorter frequency.

New Deployment

Existing Deployment

  • All customer authoring should be done only in Oracle Fusion Accounts Receivables.

  • Customer Accounts to be synchronized to OPERA Cloud must have the designated "Customer class" associated with them.

  • Depending on data volume, consider initially scheduling the Accelerator to run at a shorter frequency.

Existing Deployment

New Deployment

  • DO NOT activate this Accelerator before completing the data migration from OPERA to Oracle Fusion Accounts Receivables.

  • Extract Customer account invoices data from the OPERA Property Management System.

  • Create Customer, Account, and Invoices data in Oracle Fusion Accounts Receivables either manually or using the file upload feature.

  • Create external system references for each Customer (Party), Account, and Site created in Oracle Fusion Accounts Receivables.

    • Company Profile ID from OPERA Property Management System is used as the External System Ref for Party ID.

    • AR Address ID is used as the External System Ref for Bill-To Site ID.

    • A concatenated value (<ERP BU ID>-<OPERA AR Account ID>_<OPERA_HOTEL_ID>) is used as external system references for ACCOUNT ID in Oracle Fusion Accounts Receivables.

      Note:

      For one Account in Oracle Fusion Accounts Receivables, there might be multiple accounts in OPERA Cloud.

  • For each Profile in OPERA Cloud, the Oracle Fusion Accounts Receivables Party ID must be entered as an external reference ID against the Profile.

  • Depending on data volume, consider initially scheduling the Accelerator to run at a shorter frequency for credit status update.

  • For further technical details, refer to Appendix A in this guide.

Existing Deployment

Existing Deployment

  • DO NOT activate this Accelerator before completing the data migration from OPERA to Oracle Fusion Accounts Receivables.

  • Extract Customer account and invoices data from the OPERA Property Management System.

  • Extract Customer account data from Oracle Fusion Accounts Receivables.

  • Carry out a duplication activity to create a list of OPERA Cloud Profiles that must be created in Oracle Fusion Accounts Receivables.

  • Create Customer, Account, and Invoices data in Oracle Fusion Accounts Receivables either manually or using the file upload feature.

  • Create external system references for each Customer (Party), Account, and Site created in Oracle Fusion Accounts Receivables.

    • Company Profile ID from OPERA Property Management System is used as the External System Ref for Party ID.

    • AR Address ID is used as the External System Ref for Bill-To Site ID.

    • A concatenated value (<ERP BU ID>-<OPERA AR Account ID>_<OPERA_HOTEL_ID>) is used as the external system references for ACCOUNT ID in Oracle Fusion Accounts Receivables.

      Note:

      For one Account in Oracle Fusion Accounts Receivables, there might be multiple accounts in OPERA Cloud.

  • For each Profile in OPERA Cloud, the Oracle Fusion Accounts Receivables Party ID must be entered as an external reference ID against the Profile.

  • Customers to be synchronized to OPERA Property Management System must have the designated ‘Customer class’ associated with them. For more information, see Configure Oracle Fusion Accounts Receivables.

  • Depending on data volume, consider initially scheduling the Accelerator to run at a shorter frequency for credit status update.

  • For further technical details, refer to Appendix A in this guide.