Import Your Self-Service Role Data

How You Map Your Source Data to Target Object Attributes

To import your Self-Service Role data into Oracle Applications Cloud, you need to populate a CSV file with your source data and map that source data to target object attributes in Oracle Applications Cloud.

You need to do the following before creating the CSV file for data import:

Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.
Ensure prerequisite setups are done, if applicable.
Understand your options for uniquely identifying the records.
Ensure parent records exist before importing child records.
Identify the target object attributes that are required in the CSV file for a successful import.

Before You Start

You must do some basic checks before starting your import. For example, make sure that:

You have completed all the prerequisites for importing each attribute in your source data.
You have all parent records in place before importing child records.

Select a Unique Identifier for Your Records

All records must be unique in the application. If you're creating records, then you can provide an easily understandable public unique identifier. These are, usually, denoted with 'Number' and visible in the business object's UI. PUID attributes are usually named <object> Number. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.

Required Attributes and Validations for Self-Service Role Object

To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Ensure that you provide valid values for the attributes. This table lists the required attributes for importing new Self-Service Role records, prerequisite setup tasks for the attributes, and specific validations, if any, for Self-Service Role import:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Self-Service Role Record	Deleting an Existing Self-Service Role Record
ContactPartyId	The party ID of the contact record of the self-service user associated with the role.	The contact must exist.	Provide a valid value if the ContactPartyNumber isn't specified.	Not Required
RequestTypeCd	The code that indicates the Registration Request type. The list of accepted values is defined in the ORA_SVC_CSS_REQ_TYPE_CD lookup type.	No Validation	Provide one of the following values: ORA_CSS_REQ_TYPE_CONTACT ORA_CSS_REQ_TYPE_CONSUMER	Not Required
RelationshipTypeCd	The code that indicates the role type. The list of accepted values is defined in the ORA_SVC_CSS_REL_TYPE_CD lookup type. The following values can be assigned: ORA_CSS_USER: Corresponds to the Digital Customer Service User role. ORA_CSS_ACC_MGR: Corresponds to the Digital Customer Service Account Manager role. ORA_CSS_ACC_ADMIN: Corresponds to the Digital Customer Service Account Administrator role. Multiple roles can be assigned to a user and must be concatenated with the character, '&'. For example, ORA_CSS_USER&ORA_CSS_ACC_ADMIN	No Validation	Provide one or more of the following values: ORA_CSS_USER ORA_CSS_ACC_MGR ORA_CSS_ACC_ADMIN	Not Required
ContactPartyNumber	The party number of the contact record of the self-service user associated with the role.	The contact must exist.	Provide a valid value if the ContactPartyId isn't specified.	Not Required
AccountPartyNumber	The party number of the account of the self-service user associated with the role.	An account must exist.	Provide a valid value if the AccountPartyId isn't specified.	Not Required
RoleId	The unique identifier of the self-service user role.	A user role must exist.	The RoleId should not be provided.	Required
LoginId	The login Id of the self-service user associated with the role. If the SVC_CSS_IMP_SIGN_IN_ATTR_NAME profile option is set, then the LoginId is optional.	Login ID should be unique to each user.	Provide a valid value if the SVC_CSS_IMP_SIGN_IN_ATTR_NAME profile option isn't set.	Not Required
AccountPartyId	The party ID of the account of the self-service user associated with the role.	An account must exist.	Provide a valid value if the AccountPartyNumber isn't specified.	Not Required

Note: You can only create and delete self-service role records. You can't update self-service role records.

You can view the Self-Service Role object along with all its child objects and attributes in the Manage Import Objects page of the Import Management flow. You can find attribute information like type, length, description, and so on, on this page.

Create the Source CSV File

You include the data that you want to import into Sales and Fusion Service in a source CSV file.

You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:

Go to Navigator > Tools > Import Management > Import Objects.
Select the Self-Service Role object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Consider the following points:

Role Id should be removed.
Either the contact party ID or the contact party number is required.
Either the account party ID or the account party number is required.

Examples

Example 1: Party ID is used for creating self-service users

AccountPartyId,ContactPartyId,RelationshipTypeCd,RequestTypeCd

300100110957452,300100156316610,ORA_CSS_USER&ORA_CSS_ACC_ADMIN,ORA_CSS_REQ_TYPE_CONTACT
Example 2: Party Number is used for creating self-service users

AccountPartyNumber,ContactPartyNumber,RelationshipTypeCd,RequestTypeCd

CDRM_67617,CDRM_743628,ORA_CSS_USER,ORA_CSS_REQ_TYPE_CONTACT

CDRM_67617,CDRM_743711,ORA_CSS_USER&ORA_CSS_ACC_ADMIN,ORA_CSS_REQ_TYPE_CONTACT

CDRM_67617,CDRM_743651,ORA_CSS_USER &ORA_CSS_ACC_MGR,ORA_CSS_REQ_TYPE_CONTACT
Example 3: Login ID is explicitly provided for creating self-service users

AccountPartyNum,ContactPartyNum,LoginId,RelationshipTypeCd,RequestTypeCd

CDRM_67617,CDRM_743628,Mary.Smith,ORA_CSS_USER,ORA_CSS_REQ_TYPE_CONTACT

CDRM_67617,CDRM_743711,John.Rogers,ORA_CSS_USER&ORA_CSS_ACC_ADMIN,ORA_CSS_REQ_TYPE_CONTACT CDRM_67617,CDRM_743651,Pat.Williams,ORA_CSS_USER&ORA_CSS_ACC_MGR,ORA_CSS_REQ_TYPE_CONTACT
Example 4: Consumer request type is provided for creating self-service users

ContactPartyId,RelationshipTypeCd,RequestTypeCd

300100194440555,ORA_CSS_USER,ORA_CSS_REQ_TYPE_CONSUMER
Example 5: RoleId is provided for deleting self-service users

300100194434646

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

After you have the CSV file ready, create an import activity to import the information. To create an import activity:

Go to Navigator > Tools > Import Management > Import Self-Service Role.
Click Create Import Activity in the Manage Imports page.
In the Enter Import Options page, provide a name for the import activity, and select Self-Service Role from the Object drop-down list.
Select the CSV file in the File Name field, and click Next.

You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.
Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.
Review the import details on the Review and Submit page, and click Submit when you're ready.

Review the Import Results

Check if your import succeeded on the Manage Imports page. This page shows the status of all active, completed, and unsuccessful imports. To check the status of the import activity:

Go to Navigator > Tools > Import Management > Import Self-Service Role.
Click All Imports and search for the import activity that you created earlier.
Check the Status column for the import activity. The import is successful if the status displays as Completed. You can drill down on the import activity to go to the Import Status page which provides the status details of the import activity.