Configuring Oracle CX Fusion Service

This chapter describes the Oracle Fusion CX Service configuration required to enable the integrations described in this document. It includes the following sections:

Integration User and Required Access

Create a dedicated integration user in CX. This account is used by the CX connection described in Importing, Configuring, and Testing Integration Connections.

Complete the following setup:

  1. Create the integration user.

    Create the user through My Team, following Create an Integration User Account in Prerequisites for Creating a Connection, in Using the Oracle CX Sales and B2B Service Adapter with Oracle Integration 3. Before saving, verify the following details for this provisioning flow:

    • User details: First Name and Last Name identify the integration account, Email is valid, and User Name is the name to be used by the integration.

    • Employment details: Person Type is Employee; Legal Employer and Business Unit are selected from your organization's configured values.

    If you use the predefined Service role provisioning rules, assign the Service Representative resource role and verify that Customer Service Representative and Resource have been provisioned. See Role Provisioning.

  2. Verify integration roles and privileges.

    In Tools > Security Console, verify that the integration user has the following access. Provide any missing access through the appropriate role assignments. For instructions, follow Assign Integration Roles in Prerequisites for Creating a Connection.

    Role or privilegePurpose
    Integration Specialist (ORA_FND_INTEGRATION_SPECIALIST_JOB)Standard application job role used for enterprise integration activities. See Integration Specialist.
    SOA Operator (SOAOperator)Enables the integration user to receive business events through the CX adapter.
    FND_MANAGE_CATALOG_SERVICE_PRIVProvides access to manage the web services catalog.
  3. Refresh Security Console data.

    Verify that Security Console reflects the user and role assignments. If its security data needs to be refreshed, run Import User and Role Application Security Data from Tools > Scheduled Processes and confirm that it completes successfully. See Configure the Security Console.

  4. Verify functional permissions and record access.

    Verify that the integration user has permission to perform the API operations required for Accounts, Contacts, their child objects used by the integration mappings, and Service Requests. Ensure that the user can access the records processed by the integration, including contact points and source-system references.

    If using access groups, ensure that the integration user is a CX resource and belongs to groups that grant the required record access. Publish any new or changed object sharing rules and run Perform Object Sharing Rule Assignment Processing. If group membership is rule-based, run Run Access Group Membership Rules to update membership. For instructions, see Create an Access Group.

  5. Verify API access.

    Using the integration user account, verify that the API operations used by the integrations succeed for Accounts, Contacts, their required child objects, and Service Requests.

    See the lookup parameter definition for integration.service.account in Configuring Lookups, Error Handling, and Email.

Source System Code

Verify that the source-system code used by the integration is defined in CX under Setup and Maintenance > Manage Trading Community Source Systems. The integration uses this code to identify the records it creates in CX. Use the same code for source.system.in.CX, described in Chapter 6.

For setup instructions, follow Verify the Source System Record and, if a new source system is needed, Create the Source System Record in Prerequisites for Creating a Connection, using your source-system code.

Contact Point Purpose Values

The Phone, Email, and Web purpose mappings require valid purpose codes from the customer's CX environment. Locate the enabled codes in Setup and Maintenance > Manage Standard Lookups using the following lookup types:

CX fieldCX lookup type
PhonePurposeCONTACT_POINT_PURPOSE
EmailPurposeCONTACT_POINT_PURPOSE
WebPurposeCONTACT_POINT_PURPOSE_WEB

These associations are documented in the Contact Points REST API. For instructions to locate and maintain lookup codes, see How do I change lookup values after my sales implementation.

Use the applicable codes from the target environment when configuring the purpose mappings described in Configuring Lookups in Configuring Lookups, Error Handling, and Email.

Standard and Extended Fields

Ensure that the Contact, Account, and Service Request fields used in the integration mappings are included in the corresponding API schemas. Use each field's API name when defining its mapping in Configuring Lookups, Error Handling, and Email.

Review existing standard and custom fields in Application Composer. When a mapping requires an additional field, create it on the corresponding object in a sandbox and publish the sandbox. For instructions, see Define Fields and Publish Sandboxes.

For standard API attributes and their properties, see the REST references for Contacts, Accounts, and Service Requests.

Service Request Configuration

Case Sync creates or updates a Service Request in CX from a Case in CCS. Ensure that the category and status codes referenced by the Case mappings are available in the target CX environment.

CX configurationWhere to locate the valuesOracle instructions
Service Request categorySetup and Maintenance > Service > Service Request > Manage Service Request Categories. Select an active category and obtain its Category Code for the applicable business unit.How do I manage categories
Service Request statusSetup and Maintenance > Service > Service Request > Manage Service Request Status Values. Obtain the status codes applicable to the customer's Service Request lifecycle.How do I change lookups

Use these CX codes in the Case Type, Case Status, and Case Condition mappings described in Configuring Lookups in Configuring Lookups, Error Handling, and Email. Follow the linked Oracle instructions when additional categories or status values are required.