Import Your SmartText User Variable Data

You can use Import Management to create, update, or delete SmartText User Variable records.

To import SmartText User Variable records, perform the following tasks:

  1. Map your source data to Oracle Applications Cloud object attributes.

  2. Create source Comma Separated Values (CSV) file for import.

  3. Create the import activity.

  4. Review the import results.

How You Map Your Source Data to Object Attributes

To import your SmartText User Variable data into Oracle Applications Cloud, you must 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 any prerequisite setups are completed.
  • 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

To import data into Oracle Applications Cloud, your CSV file must include some specific attributes that enable the import process to uniquely identify the records. The file import process uses the attribute values to automatically map your source data to the target object attributes in Oracle Applications Cloud.

The preferred options for uniquely identifying an object record are as follows:

  • Internal ID: If you're identifying a record that already exists in Oracle Applications Cloud, then you can use the internal ID of the record, a system-generated unique identifier Attributes with "Id" in the attribute name are typically internal IDs. You can determine the internal ID of a record by exporting Oracle Applications Cloud object data, or by doing a transactional database query. Using an internal ID typically provides better performance and reduces the import duration. For the SmartText User Variable object, this attributes is VariableId.

  • Public unique identifiers: If you are creating new records, then you can provide a user-friendly public unique identifier (PUID) which is an attribute denoted with 'Number'. For the SmartText object, the attribute is VariableUniqueNumber. If you update a record for which you have previously provided a VariableUniqueNumber, you can use the VariableUniqueNumber attribute to identify the record.

Required Attributes and Validations for SmartText User Variable 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 SmartText User Variable records, required attributes for updating SmartText User Variable records, prerequisite setup tasks for the attributes, and specific validations, if any, for SmartText User Variable import:

Attribute

Description

Data Type

Data Length

Prerequisite Setup Task/ Import Validations

Creating a SmartText User Variable Record

Updating an Existing SmartText User Variable Record

VariableId

The unique Id for the existing SmartText User Variable record in the Oracle Fusion destination table.

Number

18

No Validation

Not required

Conditionally required

A value is required if you're updating an existing SmartText User Variable and you're not providing the Variable Unique Number.

Variable

Name of the SmartText User Variable

Varchar

50

Validation is performed for the creation of a SmartText user variable to ensure the following combination of values doesn't exist:

  • Variable

  • Context

  • StripeCd

  • BuOrgId

Required

Not required

VariableUniqueNumber

The unique number used to identify a SmartText user variable. You can configure the variable unique number to a format that's best suitable to your organizational requirements.

Varchar

30

Validation performed for the creation of a SmartText user variable, ensuring the SmartText user variable unique number isn't already in use.

Not required

You can accept system generated values or provide a unique value according to your organizational business needs.

Conditionally required

A value is required if you're updating an existing SmartText User Variable and you're not providing the SmartText User Variable Identifier (VariableId).

StripeCd

The stripe to which this SmartText user variable is associated

Varchar

30

A value is defaulted based on the application context. However, if a value is populated, validation is performed against the list of valid values in the lookup type ORA_SVC_STRIPE_CD.

Not Required

A value is defaulted based on the application context.

Not required

Object

Specifies the business object to which the SmartText user variable is associated.

Varchar

30

No default value is provided. The value provided should be a value of the VIEW_OBJECT_CODE from the SVC_STD_TXT_OBJECTS table. For instance, ServiceRequestVO.

Not required

Not required

Context

Specifies the context to which the SmartText user variable is associated.

Varchar

50

A default value of ORA_SVC_SR is provided. However, if a value is populated, validation is performed against the list of valid values in the lookup type ORA_SVC_STDTXT_TYPE_CD.

Not required

Not required

BuOrgId This is the business unit organization ID. If multiple business unit support is enabled using the HZ_ENABLE_MULTIPLE_BU_CRM profile option, this value will allow segregation of data accordingly. Numver 18

Not Required

A value is defaulted based on the application context.

Not Required

A value is defaulted based on the application context.

You can view the StandardTextUserVariable object and attributes in the Manage Import Objects page of the Import Management flow. You can find attribute information like type, length, and description 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:

  1. Go to Navigator > Tools > Import Management > Import Objects.

  2. Select the StandardTextUserVariable object in the table and click Download.

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

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:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click Create Import Activity in the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select StandardTextUserVariable from the Object drop-down list.

  4. Select the CSV file in the File Name field, and click Next.

  5. You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

  6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

  7. Review the import details on the Review and Submit page, and click Submit to complete the request.

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:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click All Imports and search for the import activity that you created earlier.

  3. 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.