Given Oracle Revenue Management Cloud has predefined integration with Oracle E-Business Suite Financials, which two steps are NOT part of the steps…

The integration between Oracle E-Business Suite (EBS) and Oracle Revenue Management Cloud relies on specific, predefined configuration steps. Applying necessary patches, setting the source system profile option in EBS, and configuring the Revenue Management tab in Receivables System Options are all required steps. However, "Run the Deploy System Options process" is not a standard, named process for this integration. Furthermore, a direct, manual mapping of the entire EBS Chart of Accounts to the Cloud General Ledger is not performed; the integration leverages Subledger Accounting (SLA) rules within the Cloud to handle accounting transformations.

A. Applying patches is a mandatory prerequisite to enable the integration functionality and ensure compatibility between EBS and the Cloud application.

C. This profile option is essential for Revenue Management Cloud to identify and process transactions coming from a specific EBS instance.

E. This dedicated tab in EBS Receivables System Options contains the critical parameters required to enable and control the integration.

1. Oracle E-Business Suite Financials, Oracle E-Business Suite and Oracle Revenue Management Cloud Integration Implementation Guide, Release 12.1 and 12.2, Chapter 2, "Setting Up the Integration". This guide details the required setup steps, which include applying patches (Doc ID 2139599.1), setting the profile option AR: Source System Value for Revenue Management, and configuring the Revenue Management tab in AR System Options. It does not mention a "Deploy System Options" process or a manual COA mapping task.