Save Data to Oracle Fusion

This topic contains information specific to saving data to Oracle Fusion using output mappings in Policy Modeling. For more general information on how to set up an Intelligent Advisor interview to save data, see Save Data When an Interview Completes.

Oracle Fusion objects can be both updated and created. There is no delete operation.

The creation of third level deep relationships is not supported except on some limited objects. For example, you cannot load an account and have Intelligent Advisor create a new contact and a new opportunity if opportunity is a child of the contact . You can only create both contact and opportunity if both are direct children of the account object. Some objects (for example, household) do support this. For more information, see the full list of supported relationships in Objects Supported for Oracle Fusion.

When saving Intelligent Advisor data to custom fields in Oracle Fusion, be aware that there is a limit to the number of fields that can be created per object and per data type. For more information, see Define Fields.

Generated forms (decision letters, application forms, quotes and so on) and uploaded attachments can be saved to standard and custom objects in Oracle Fusion. While audit reports are not yet supported for Intelligent Advisor interviews in Oracle Fusion, you can put explanations in forms and attach them as a PDF or other file format to the Oracle Fusion record. For more information, see Save a Generated Form to a Connected Application.

The following table lists the mandatory fields that are required for creating a record in Oracle Fusion. These fields must be output mapped from attributes in Intelligent Advisor.

Table 1. Mandatory fields required for creating a record in Oracle Fusion
Object Name Field Required Comments
Account OrganizationName  
Activity Subject
ActivityFunctionCode=[APPOINTMENT, TASK]
ActivityStartDate
ActivityEndDate		 ActivityEndDate should be greater then ActivityStartDate date
Case CaseCategoryId
Title		 See Set the CaseCategoryID below
Contact First Name
Last Name
Type = [ZCA_CUSTOMER, ZCA_CONTACT]		 When ZCA_CUSTOMER is used, you should pass value to the Primary Address of the Contact too which is supported as a relationship (Contact→PrimaryAddress) in Intelligent Advisor
Household HouseholdName  
Lead Name  
Note SourceObjectCode=[OPPORTUNITY, ACTIVITY, LEAD, PROGRAMENROLLMENTS etc]
NoteTypeCode=GENERAL
NoteTxt		 SourceObjectCode should contain object name of immediate parent in uppercase
Opportunity Name  
Opportunity → Lead Name
LeadNumber		 LeadNumber need to be mapped out, no need to provide value
Primary Address Country  
Product IsSelected
RevnAmount
OrganizationId
InventoryItemId		 For Opportunity & Lead at top level: Selected Product will be added to revenue line of loaded Opportunity and Lead
For Opportunity & Lead at second level: Selected Product will be added to revenue line of new Opportunity and Lead
Service Request Title
StripeCd*		 *StripeCd only required when using HRHD. See Set the Service Request stripe code below.
Service Request → Contact FirstName
LastName
PartyId*		 *PartyId only required when Service Request Account is not empty
Service Request → Message MessageContent
MessageTypeCd = []
StatusCd = []
MessageVisibilityCd = []		  

Set the CaseCategoryID

When creating the Case object, you need to set the CaseCategoryId. To do this:

  1. Create a child entity (of the Global Case entity) called "the category". This entity should have conditions that define when instances of Category are loaded. For example, contains(CategoryName, "AgentUX").
  2. Create an attribute called "the category name" (with name "CategoryName).
  3. Create the following input mappings:
    • Map in "the category" attribute (that was auto-created when "the category" entity was created) from the CategoryId field in Oracle Fusion.
    • Map in "the category name" attribute from the CategoryName field in Oracle Fusion.
  4. Create a one-to-one relationship from the global Case entity to "the category" entity called "the selected category".
  5. Collect "the selected category" relationship on a screen. Make the question text meaningful, for example, "Please select a category". Make the answer text the category name (that is, %CategoryName%). For more information, see Define a Screen for Collecting Members of a Relationship.
  6. Write a rule:

    • the case's category ID = For(the selected category, the category)

  7. Map out "the case's category ID" attribute to the CaseCategoryId in Oracle Fusion.

Note that you may get a warning in Policy Modeling that "Test connector data may be required to debug and test this project effectively". This occurs because the Debugger cannot load category data from Oracle Fusion in order to display input values when testing the interview in the Debugger. To remove this message, Create a Sample Data File to supply example category values.

Set the Service Request stripe code

Note that when using Oracle Human Resources Help Desk (HRHD) to create a new Service Request, you need to additionally set the stripe code. To do this:

  1. Write a rule:

    • the stripe code = "ORA_SVC_HCM"

  2. Map out 'the stripe code' attribute in Policy Modeling to the StripeCd field in Oracle Fusion.
Related Topics