Import Your SmartText Data

How You Map Your Source Data to Object Attributes

To import your SmartText 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 object, this attributes is StdTxtId.
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 StdTxtUniqueNumber. If you update a record for which you have previously provided a StdTxtUniqueNumber, you can use the StdTxtUniqueNumber attribute to identify the record.

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

Attribute	Description	Data Type	Data Length	Prerequisite Setup Task/ Import Validations	Creating a Smart Text Record	Updating an Existing Smart Text Record
StdTxtId	The unique Id for the existing SmartText 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 Smart Text and you're not providing the Standard Text Unique Number.
StdtxtName	Name of the SmartText	Varchar	50	Validation is performed for the creation of a SmartText to ensure the following combination of values doesn't exist: StdtxtName Registry ID Domain StripeCd BuOrgId	Required	Not required
StdTxtUniqueNumber	The public unique identifier (PUID) used to identify a SmartText. You can configure the standard text unique number to a format that is most suitable to the need of your organization.	Varchar	30	Validation performed for the creation of a smarttext, ensuring the smart text 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 Smart Text and you're not providing the Smart Text Identifier (`StdTxtId`).
StripeCd	The stripe to which this SmartText 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
HtmlFlag	A Y/N value indicating if the SmartText contains HTML.	Varchar	1	A default value of "N" is provided. If a value is populated, validation is performed against the list of valid values in the lookup type YES_NO.	Not required The value "N" is defaulted, if no value is provided.	Not required
Scope	Indicates if the SmartText is private or public	Varchar	20	A default value of "ORA_SVC_USER" is provided. If a value is populated, validation is performed against the list of valid values in the lookup type ORA_SVC_STDTXT_SCOPE_CD.	Not required The value "ORA_SVC_USER" is defaulted, if no value is provided.	Not required
Domain	Specifies the domain to which the SmartText is assigned	Varchar	30	No default value is provided. If a value is populated, validation is performed against the list of valid values in the lookup type ORA_SVC_STDTXT_DOMAIN_CD.	Not required	Not required
Object	Specifies the business object to which the SmartText is associated.	Varchar	150	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.	Required	Not required
StartDate	Allows you to specify a date when the SmartText is valid.	Date		The system date is used, if no value is specified.	Not required	Not required
EnabledFlag	Specifies if the SmartText is available for use.	Varchar	1	A default value of "Y" is provided. If a value is populated, validation is performed against the list of valid values in the lookup type YES_NO.	Not required	Not required
UserPartyId	The foreign key value to the Parties table	Number	18	Import any new parties into the database.	Conditionally Required. If the Scope is set to ORA_SVC_USER, either the UserPartyId or the Registry ID is required.	Not required
Registry ID	This is the public unique identifier of the user assigned to this private SmartText.	Varchar	30	Import any new parties into the database.	Conditionally Required. If the Scope is set to ORA_SVC_USER, either the UserPartyId or the Registry ID is required.	Not required
Folder ID	The foreign key value to the SmartText folders table	Number	18	Import any new SmartText folders into the database.	Conditionally Required. If the Scope is set to ORA_SVC_GLOBAL, either the Folder ID or the FolderUniqueNumber is required.	Not required
FolderUniqueNumber	This is the public unique identifier of the user assigned to the folder of this SmartText.	Varchar	30	Import any new SmartText folders into the database.	Conditionally Required. If the Scope is set to ORA_SVC_GLOBAL, either the Folder ID or the FolderUniqueNumber is 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.	Number	18	No Validation	Not Required A value is defaulted based on the application context.	Not Required A value is defaulted based on the application context.
Text	This is the text of the SmartText record.	Long Text		No Validation	Required	Not required
Language	This is the language code for which the text is associated.	Varchar	4	No Validation The value must exist in the LANGUAGE_CODE from FND_LANGUAGES_VL.	Required	Not required

You can view the SmartText 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:

Go to Navigator > Tools > Import Management > Import Objects.
Select the StandardText 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:

Go to Navigator > Tools > Import Management > Import Queue.
Click Create Import Activity in the Manage Imports page.
In the Enter Import Options page, provide a name for the import activity, and select StandardText from the Object drop-down list.
Select the CSV file in the File Name field, and click Next.
You will 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 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:

Go to Navigator > Tools > Import Management > Import Queue.
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.