1. CRM Integration to Oracle FLEXCUBE Universal Banking Implementation Guide
  2. Solution Assumptions and Constraints

Solution Assumptions and Constraints

The following are the Integration solution assumptions and constraints:

  • The files provided by the Integration to allow the batch synchronization of data support Oracle Database only.

  • For customer address data the following applies:

    • Only the primary customer address is synchronized between Oracle FLEXCUBE Universal Banking and Siebel CRM.

    • Nonprimary addresses in Siebel CRM are not deleted or updated.

  • If the lengths defined for corresponding columns in Siebel CRM and Oracle FLEXCUBE Universal Banking differ, then the data in the longer column is truncated during the synchronization process if the target column is smaller than the source column.

  • Siebel CRM is the master application for the following data:

    • Customer

    • Service request

    • Activity

    • Offers

    • Leads

    • Customer relationships

  • Oracle FLEXCUBE Universal Banking is the master application for the following data:

    • Products and prices

    • Branch

    • Financial account

    • Limit

    • Mandate

    • Standing instructions

    • Contracts

    • Transactions

  • A limited set of Oracle FLEXCUBE Universal Banking bank branch information is stored in Siebel CRM as an internal division.