Functional Prerequisites and Constraints

The following prerequisites and constraints must be acknowledged for the Enterprise Resource Planning (ERP) Cloud Centralised AR Business Accelerator:

Prerequisites

• All customers are first created in Oracle Fusion Accounts Receivables and are then integrated with OPERA Cloud using this Accelerator. This Accelerator considers the smallest amount of data required to create a customer in both systems.

• All configurations for Oracle Fusion Financials in General Ledger and Accounts Receivable applications (as required for customer creation, invoices creation, and account balance/credit status check) must be completed and validated.

• Initial loads for customer migration must be done prior to using the Accelerator. This Accelerator is not intended for mass processing of existing customer data for the first time.

• For pre-existing data, you must ensure that Account Numbers are identical in Oracle Fusion Accounts Receivables and OPERA Cloud.

• External system references have been created in Oracle Fusion Accounts Receivables for Customers, Accounts, and Bill To Sites. You must create an external system in Oracle Fusion Accounts Receivables before creating such external system references.

• Oracle Fusion Accounts Receivables Party ID must be entered as an external reference ID against the profile in OPERA Property Management System.

• An Account Bill-To Site in Oracle Fusion Accounts Receivables must be associated with at least one Business Unit for the customer and account to be created in OPERA Property Management System using this Accelerator. Business Units are associated to the site through the Reference Data Set selected during account creation.

• The Credit limit and Conversion Rate Type are provided at the customer account level in Oracle Fusion Accounts Receivables. It is recommended that the credit limit is in functional currency.

• The Currency conversion type should be set to “Corporate” at customer account level in Oracle Fusion Accounts Receivables. This cannot be modified to any other type.

• For each property in OPERA, a unique Transaction Source should be created in Oracle Fusion Accounts Receivables

• In Oracle Fusion Accounts Receivables, tax setups are set to ‘No’ while importing Invoices.

• OIC Accelerator lookups contain many Oracle Fusion Accounts Receivables and OPERA artifact references, such as Transaction Source, Hotel Code, Business Unit, and so on. Before activating the integrations, all respective Oracle Integration Cloud lookups should be validated and updated to reflect the environment where the accelerator runs.

• A File Storage location should be created as part of the OPERA system for invoice export and error reporting by OIC. A folder structure should be created with necessary read/write access for users performing operations over FTP.

• It is assumed that Fusion Custom Job Names, Parameter Names, BIP report names, and related artifacts are not modified and used as is. If any are modified, all respective references, such as Oracle Integration Cloud lookups, must be updated to reflect the same.

Constraints

• ERP Integration does not reflect changes made in OPERA Cloud to AR Account communication, address, or credit limit and any changes in OPERA Cloud are overwritten when next updated by ERP Integration.

• A Customer account in Oracle Fusion Accounts Receivables can have only one site. This restriction is imposed to cater to a similar constraint in OPERA Property Management System.

• When end dating a site or site usage in ERP, wait for the site changes to be implemented in OPERA Cloud (typically the next calendar day) before creating a new site in ERP for the account.

• The system effects of an end dated site can be reversed by creating a new site in ERP after the accelerator has processed the end date of the previous site.

• Account and site end dates cannot be reversed once processed.

• A site should not have multiple lines with a ‘Bill-to’ usage.

• The Oracle Hospitality Integration Platform (OHIP) user for the Oracle OPERA Cloud Connection will have access to all properties in the hotel chain that is in scope for the Accelerator.

• For each Invoice line sent from OPERA against one property, the accelerator creates one Invoice Transaction in Oracle Fusion Accounts Receivables.

• Booking details present in the OPERA invoices are captured in Invoice Line Flex-field Segments.

• The Property code from OPERA is captured as a cross reference field in Oracle Fusion Accounts Receivables.

• There is only one Payment Terms configured for each customer account in Oracle Fusion Accounts Receivables. The same Payment Terms could be shared across multiple customer accounts in Oracle Fusion Accounts Receivables.

• Maintenance of the file server, such as monitoring space availability and cleaning up files, is not performed by this accelerator. It is recommended that the file server admin performs the server maintenance activities in the required timeframe based on the usage.

• OPERA Property Management System Invoice exports must be in the format specified in this guide.

  For each invoice line, the current version of the accelerator queries OPERA Cloud to fetch the respective customer account address ID to be populated in Oracle Fusion Accounts Receivables. It is assumed that any Oracle Hospitality Integration Platform infrastructure requirements to support this are addressed before implementation of the accelerator.