Oracle Fusion Data Mapping

Data mapping enables you to pre-seed data in an Intelligent Advisor interview from Oracle Fusion and to save outcomes from the interview back to Oracle Fusion. To do this, data in Intelligent Advisor needs to be mapped to corresponding objects and fields in Oracle Fusion. Input mappings are used to load values, and output mappings are used for updating and saving values.

Before you can set up data mappings for your Intelligent Advisor interview, ensure that the project uses an Oracle Fusion connection.

Data mapping is done at three levels, and in this order.

  1. Mapping the Global entity in Intelligent Advisor to the equivalent objects in Oracle Fusion. The global entity instance in Intelligent Advisor can be bound to two objects in Oracle Fusion:
  2. Mapping the non-global entities in Intelligent Advisor to the equivalent objects in Oracle Fusion. For more information, see:

    This also binds the link between the objects in Oracle Fusion to the Intelligent Advisor containment relationship.

  3. Mapping reference relationships in Intelligent Advisor to the equivalent links in Oracle Fusion. For more information, see:
  4. Mapping individual attributes in Intelligent Advisor to fields in the tables of Oracle Fusion. For more information, see:

When designing an Intelligent Advisor interview that uses an Oracle Fusion connection, be aware of the access permissions needed by intended users of the interview. When an interview starts, data is read from each mapped-in table, and when the interview is submitted data is written (updated or created) in each mapped-out table. If the interview user does not have the correct read, write or update access to any of the mapped business objects then the interview will display an error.

To grant interview users the required access to business objects, use the access group capabilities of Oracle Fusion. For more information: