9Import Your Data
This chapter contains the following:
Import Your Account Data
You can use Import Management to create, update, or delete your account data.
You can import account records using these steps:
-
Map your source account data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the account data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
You import account data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.
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 steps are complete, such as understanding what attributes are required for importing your objects.
-
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
To better manage your account information, the account object has the following child objects:
-
Address
-
Classification
-
Relationship
-
Sales Team Member
If you want to import only a few records, then you can create a single CSV file for all account attributes. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the account child objects. Note that you must have imported the CSV file for account object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects. For more information, see the related topics section.
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. For example, when using source system reference information to identify your account records, the source system of the account object should be enabled for parties using the Manage Trading Community Source Systems task.
-
You have all parent records in place before importing child records. For example, when importing the address of an account, ensure the account exists.
Select a Unique Identifier for Your Records
All records must be unique in the application. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For account object, the attribute is PartyNumber and shows up in the UI as Party Number. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new accounts or are updating accounts that have source system reference data, then provide the source system and source system reference values. For account object, these are SourceSystem and SourceSystemReferenceValue and show up as Party Source System and Party Source System Reference Value in the UI.
Review Required Attributes and Validations for Account Object
To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Make sure that you provide valid values for these attributes so that they pass import validations inbuilt into the application.
This table lists the required attributes for account records, prerequisite setup tasks and specific validations, if any:
Attribute | Description | Prerequisite Setup Tasks or Import Validations | Creating an Account Record | Updating an Existing Account Record | Deleting an Existing Account Record |
---|---|---|---|---|---|
SourceSystem |
The source system for the sales account. |
Know the source system. To view source systems, use the Manage Trading Community Source System task. |
Conditionally Required To identify an account record, use one of these:
|
Conditionally Required To identify an account record, use one of these:
|
Conditionally Required To identify an account record, use one of these:
|
SourceSystemReferenceValue |
The reference number or text representing the source system unique ID for the party (account or contact) to which the sales profile belongs. |
Know the source system reference value. To view the source systems reference, use the Manage Trading Community Source System task. |
Conditionally Required To identify an account record, use one of these:
|
Conditionally Required To identify an account record, use one of these:
|
Conditionally Required To identify an account record, use one of these:
|
PartyNumber |
The public unique identifier of the party. |
The party must exist. You get a list of all party IDs and party numbers by exporting the Party object. |
Conditionally Required |
Conditionally Required |
Conditionally Required |
OrganizationName |
The name of the party of the Organization party type. |
Organization names are listed in the Resource Directory. |
Required |
Conditionally Required |
Conditionally Required |
Go to Navigator > Tools > Import Management > Import Objects to see all the attributes of the account object. The page also lists attribute information like type, length, description, and so on.
Create the Source CSV File
You include the data that you want to import into CX Sales and B2B 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 Account object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the account 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 Account 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 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.
When importing accounts using optimized data import, you can now load the account hierarchy data. Use the following attributes to import accounts using optimized data import:
-
ParentAccountPartyId
-
ParentAccountPartyNumber
-
ParentAccountSourceSystem
-
ParentAccountSourceSystemReferenceValue
You can load account hierarchy data. To load the account hierarchy data:
-
Load the account data without providing values for the parent attributes mentioned above.
-
Load the account hierarchy using the Hierarchy and Hierarchy Member import objects.
Import Your Action Data
You can use the import functionality to create, update, or delete your action data.
You can import action records using these steps:
-
Map your source data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the action data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
You import action data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.
Before you create the source data file, you should:
-
Know how your source data attributes map to the target object attributes in Oracle Applications Cloud. Match each column from the source file to an attribute in the action import object.
-
Finish all prerequisite steps, such as understanding what attributes are required for importing your objects.
-
Know how you can uniquely identify the records.
-
Check the target object attributes required in the CSV file for a successful import.
To better manage your action information, the action object has the following child objects:
-
Action Attribute
-
Action Condition
If you want to import only a few records, then you can create a single CSV file for all action attributes. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the action child objects. Note that you must have imported the CSV file for action object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects. For more information, see the related topics section.
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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new actions or are updating actions that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Action Object
To import data successfully into Oracle Applications Cloud, your .csv file must include the required attributes. Make sure that you provide valid values for these attributes so that they pass import validations inbuilt into the application.
This table lists the required attributes for action records, prerequisite setup tasks and specific validations, if any:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating an Action record | Updating an Existing Action record |
---|---|---|---|---|
Action |
The name of the action that's associated associated with an action plan template or action plan instance. |
None |
Required |
Not required |
Action Id |
The unique Id of the existing Action record in the Oracle Fusion destination table. |
Identify the Action ID value by exporting the Action object. Navigate to the following in the Setup and Maintenance work area:
|
Required |
A value is required if you're updating an existing Action and you're not providing the Action Number. The Action ID is autogenerated in Oracle Fusion applications, if you don't specify a value. |
ActionNumber |
The unique ID for the existing Action record in the Oracle Fusion destination table. |
None |
Optional |
A value is required if you're updating an existing Action and you're not providing the Action Id. |
Parent Entity Name |
The entity name of the object for which the action can be used in an action plan. |
None If providing a value, it must be ServiceRequest. |
Conditionally required A value is required only when you're inserting a parent entity name. However, a value isn't required when you delete or update an existing parent entity name. |
Conditionally required A value is required only when you're inserting a parent entity name. However, a value isn't required when you delete or update an existing parent entity name. |
Duration |
The estimated time to complete the action. |
None |
Required |
Required |
Duration Unit |
The unit of measurement for lead time. |
None If you intend to specify a value, select a value from the list of valid values in the lookup type ORA_SVC_AP_LEAD_TIME_UNIT. |
Required |
Required |
Object Entity Name |
Entity name of the object on which the action is based. |
None |
Conditionally required A value is required only when you're inserting an object entity name. However, a value isn't required when you delete or update an existing object entity name. |
Conditionally required A value is required only when you're inserting an object entity name. However, a value isn't required when you delete or update an existing object entity name. |
Original System Reference |
Specifies the original system reference if this record was imported. |
Identify the original system and system reference values from your source system that were imported when you imported the resource. |
Optional |
Optional |
Object Entity Type |
The entity type of the object on which the action is based. |
The valid values are ServiceRequest, Task, and Appointment. |
Required |
Not required A value is required only when you're inserting an object entity type. However, a value isn't required when you delete or update an existing object entity type. |
Visibility |
Indicates the visibility level of the action. |
If you intend to specify a value, select a value from the list of valid values in the lookup type ORA_SVC_AP_VISIBILITY_CD. |
Required |
Not required |
Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the action object. The page also lists attribute information like type, length, description, and so on...
Create the Source CSV File
You include the data that you want to import into CX Sales and B2B 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 Action object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the action information. To create an import activity:
-
Go to Navigator > Tools > Import Management > Import Queue.
-
On the Manage Imports page, click Create Import Action.
-
In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Action 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.
Note: Click Validate Data to validate the mapping of the source file for unmapped columns and to check for data format issues. -
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 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.
Import Your Action Attribute Data
You can use the import functionality to create, update, or delete action attribute data.
You can import action attribute records using these steps:
-
Map your source data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the action condition data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
You import action attribute data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.
Before you create the source data file, you should:
-
Know how your source data attributes map to the target object attributes in Oracle Applications Cloud. Match each column from the source file to an attribute in the action import object.
-
Finish all prerequisite steps, such as understanding what attributes are required for importing your objects.
-
Know how you can uniquely identify the records.
-
Check the target object attributes required in the CSV file for a successful import.
If you want to import only a few records, then you can create a single CSV file for all action conditions. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the action child objects. Note that you must have imported the CSV file for action object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects. For more information, see the related topics section.
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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new actions or are updating actions that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Action Attribute 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 action attribute records, prerequisite setup tasks and specific validations, if any:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating an Action Attribute record | Updating an Existing Action Attribute record |
---|---|---|---|---|
Action Attribute Id |
The unique Id of the existing Action Attribute record in the Oracle Fusion destination table. |
Identify the Action Attribute ID value by exporting the Action object using Setup and Maintenance, Manage Bulk Data Export, Schedule Export Processes task |
Not required |
A value is required if you're updating an existing Action attribute and you're not providing the Action source system (original system) |
Action Code |
Indicates the operation to be performed on a row, such as insert, update, and so on |
If a value isn't provided, records are matched to determine if a record is updated (if it already exists) or inserted (if it doesn't exist). |
Not required |
A value is required, if you're deleting an action attribute. |
Action Id |
Specifies the foreign key that references the Action ID to which the action is assigned. |
Identify the Action ID value by exporting the Action object using Setup and Maintenance, Manage Bulk Data Export, Schedule Export Processes task. |
Not required |
A value is required, if you're updating an existing Action Id and you're not providing the Action Id source system code and reference Action OSR. |
ActionOSR |
Specifies the action original system reference, if the record was imported. |
Identify the original system and system reference values from your source system which were imported when you imported the resource. |
Required |
A value is required if you're updating an existing Action Id record and you're not providing the record's unique ID (ActionId) |
AttributeName |
Attribute from the entity object of the associated action. |
None |
Not Required |
Not Required |
AttributeValue |
The value to be set on the Action attribute. |
None |
Not Required |
Not Required |
AttributeValueContextCd |
The context of how the attribute value should be interpreted (for example, as an attribute of the parent action's object, an attribute of the parent action, or a custom value). |
The valid values provided by the lookup type ORA_SVC_AP_CONTEXT_CD. |
Required |
Not required |
Deleted |
Indicates whether the service request is to be deleted. If the value is Y, then the service request is deleted. The default value is N. |
None |
Not required |
Not required |
ErrorMessage |
This column displays the error messages, if any. |
None |
Not required |
Not required |
ErrorMessage |
This column displays the error messages, if any. |
None |
Not required |
Not required |
InternalOvn |
This is meant for internal use. |
None |
Not required |
Not required |
JobDefinitionName |
Indicates the name of the job that created or last updated the row. |
None |
Not required |
Not required |
JobDefinitionPackage |
Indicates the package name of the job that created or last updated the row. |
None |
Not required |
Not required |
UsageCd |
Indicates when the attribute is to be used. |
The valid value is ORA_SVC_CREATE. |
Required |
Not required |
You can view the Action Attribute 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 CX Sales and B2B 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 Action Attribute object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the action attribute 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 Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Action Attribute 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 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.
Import Your Action Condition Data
You can use the import functionality to create, update, or delete your action condition data.
You can import action condition records using these steps:
-
Map your source data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the action condition data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
You import action condition data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.
Before you create the source data file, you should:
-
Know how your source data attributes map to the target object attributes in Oracle Applications Cloud. Match each column from the source file to an attribute in the action import object.
-
Finish all prerequisite steps, such as understanding what attributes are required for importing your objects.
-
Know how you can uniquely identify the records.
-
Check the target object attributes required in the CSV file for a successful import.
If you want to import only a few records, then you can create a single CSV file for all action conditions. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the action child objects. Note that you must have imported the CSV file for action object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects. For more information, see the related topics section.
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. You can use one of these to identify records:
The preferred option to uniquely identify an object record is through the 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 Action Condition Object, the attributes are Action ConditionId and ActionId:
Required Attributes and Validations for Action Condition 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 action condition records, prerequisite setup tasks and specific validations, if any:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating an Action Condition record | Updating an Existing Action Condition record |
---|---|---|---|---|
ActionCode |
Indicates the operation to be performed on a row, such as insert, update, and so on |
If a value isn't provided, records are matched to determine if a record is updated (if it already exists) or inserted (if it doesn't exist). |
Not required |
A value is required, if you're deleting an action condition. |
Action ConditionId |
The unique Id of the existing Action Condition record in the Oracle Fusion destination table. |
Identify the Action Condition ID value by exporting the Action object. Navigate to the following in the Setup and Maintenance work area:
|
Not required |
A value is required if you're updating an existing Action Condition attribute and you're not providing the Action source system (original system) |
Action Id |
Specifies the foreign key that references the Action ID to which the action is assigned. |
Identify the Action ID value by exporting the Action object. Navigate to the following in the Setup and Maintenance work area:
|
Not required |
A value is required, if you're updating an existing Action Id and you're not providing the Action Id source system code and reference Action OSR. |
ActionStatus |
Indicates the status to set an action if the condition is met. |
Valid values provided by the lookup type ORA_SVC_AP_STATUS_CD. |
Required |
Not required |
ActionNumber |
Specifies the action original system reference, if the record was imported. |
Identify the original system and system reference values from your source system which were imported when you imported the resource. |
Required |
A value is required only if you're not specifying the Action ID. |
You can view the Action Condition 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 CX Sales and B2B 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 Action Condition object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the action condition 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 Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Action Condition 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 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.
Import Your Action Plan Data
You can use Import Management to create or update Action Plan records.
To import Action Plan records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Target Object Attributes
To import your Action Plan 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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new action plans or are updating action plans that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Action Plan 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 Action Plan records, required attributes for updating Action Plan records, prerequisite setup tasks for the attributes, and specific validations, if any, for Action Plan import:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating a Action Plan Record | Updating an Existing Action Plan Record |
---|---|---|---|---|
ActionPlanId |
The unique identifier of the action plan. |
A valid primary key for the action plan record in the destination system is required. Either the ActionPlanNumber or the ActionPlanId is required. If both are present, then the ActionPlanId is preferred. |
Not Required Auto-generated in the destination system |
Optional Either the ActionPlanNumber or the ActionPlanId is required to update the row. |
CalendarId |
The calendar identifier associated with the action plan. |
A valid calendar record in the destination system. |
Required |
Not Required |
ObjectEntityName |
The parent entity object name of the action plan. |
A valid value from the ORA_SVC_AP_OBJ_ENTITY_NAME lookup in the destination system. |
Required |
Not Required |
ObjectId |
The object identifier of the action plan. |
A valid primary key for the parent record in the destination system. |
Required |
Not Required |
StatusCd |
The status of the action plan. |
A valid value from the ORA_SVC_AP_PROCESS_CD lookup in the destination system. |
Optional If no value is passed, then the default value ORA_SVC_CREATE is used. |
Optional |
TemplateNumber |
The reference number of the action plan template. |
A valid PUID for action plan template row in the destination system. It is optional if the action plan is created without an action plan template. |
Optional Required only when there is a Template ID for the action plan in the source system. |
Not Required |
ActionPlanNumber |
The reference number of the action plan. |
A valid PUID for the action plan row in the destination system. |
Optional The PUID can be provided if it needs to be maintained between the source and destination systems. |
Required |
You can view the Action Plan 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 CX Sales and B2B 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 Action Plan object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
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 Action Plan.
-
Click Create Import Activity in the Manage Imports page.
-
In the Enter Import Options page, provide a name for the import activity, and select Action Plan 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 Action Plan.
-
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.
Import Your Action Plan Action Data
You can use Import Management to create or update Action Plan Action records.
To import Action Plan Action records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Target Object Attributes
To import your Action Plan Action 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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new action plan actions or are updating action plan actions that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Action Plan Action 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 Action Plan Action records, required attributes for updating Action Plan Action records, prerequisite setup tasks for the attributes, and specific validations, if any, for Action Plan Action import:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating a Action Plan Action Record | Updating an Existing Action Plan Action Record |
---|---|---|---|---|
SkipFlag |
Contains the values, Y or N. If Y is used, then the action for the action plan is skipped. If N is used, then the action for the action plan isn't skipped. |
The default value is 'N'. |
Optional |
Optional |
TemplateNumber |
The reference number of the action plan template. |
A valid PUID for action plan template row in the destination system. It is optional if the action plan is created without an action plan template. |
Optional Required only when there is a Template ID for the action plan action in the source system. |
Not Required |
ActionId |
The unique identifier of the action. |
A valid action Id in the destination system. |
Optional |
Not Required |
ActionNumber |
The reference number of the action. |
A valid PUID action value in the destination system. Either the ActionId or the ActionNumber is required. If both are present, then the ActionId is preferred. |
Required Either the ActionId or the ActionNumber is required to create the action row in the destination system. |
Not Required |
ActionPlanActionId |
The action identifier of the action plan. |
A valid primary key for the action plan action record in the destination system is required. Either the ActionPlanActionNumber or the ActionPlanActionId is required. If both are present, then the ActionPlanActionId is preferred. |
Not Required |
Optional Either the ActionPlanNumber or the ActionPlanId is required to update the row. |
DeletedFlag |
Contains the values, Yes or No. If Yes is used, then the action in the action plan is deleted. If No is used, then the action in the action plan isn't deleted. |
A valid value from the YES_NO lookup. |
Optional |
Optional |
MandatoryFlag |
Contains the values, Yes or No. If Yes is used, then the action in the action plan is mandatory. If No is used, then the action in the action plan isn't mandatory. |
A valid value from the YES_NO lookup. |
Optional |
Optional |
ActionPlanNumber |
The reference number of the action plan. |
A valid PUID for the action plan row in the destination system. |
Required Either the ActionPlanId or the ActionPlanNumber is required to create the action row in the destination system. |
Not Required |
ActionPlanId |
The unique identifier of the action plan. |
A valid primary key for the action plan record in the destination system is required. Either the ActionPlanNumber or the ActionPlanId is required. If both are present, then the ActionPlanId is preferred. |
Optional |
Not Required |
ActionPlanActionNumber |
The reference number of the action plan action object. |
A valid action plan action PUID in the destination system. |
Optional |
Required |
You can view the Action Plan Action 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 CX Sales and B2B 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 Action Plan Action object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
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 Action Plan Action.
-
Click Create Import Activity in the Manage Imports page.
-
In the Enter Import Options page, provide a name for the import activity, and select Action Plan Action 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 Action Plan Action.
-
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.
Import Your Action Plan Action Relation Data
You can use Import Management to create or update Action Plan Action Relation records.
To import Action Plan Action Relation records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Target Object Attributes
To import your Action Plan Action Relation 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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new action plan action relations or are updating action plan action relations that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Action Plan Action Relation 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 Action Plan Action Relation records, required attributes for updating Action Plan Action Relation records, prerequisite setup tasks for the attributes, and specific validations, if any, for Action Plan Action Relation import:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating a Action Plan Action Relation Record | Updating an Existing Action Plan Action Relation Record |
---|---|---|---|---|
DeletedFlag |
Contains the values, Yes or No. If Yes is used, then the dependency record is deleted. If No is used, then the then the dependency record isn't deleted. |
A valid value from the YES_NO lookup. |
Optional |
Optional |
RelationId |
The relation identifier between actions in an action plan. |
A valid primary key for the action plan action relation record in the destination system is required. |
Not Required |
Required |
DepActionPlanActionNumber |
The relation identifier between action plan action rows for an action plan. |
A valid action plan action PUID in the destination system is required. The combination of ActionPlanActionNumber and DepActionPlanActionNumber should be unique for a Action Plan. |
Optional A Null value is accepted. |
Optional A Null value is accepted. |
DepActionPlanActionId |
The dependent action identifier of an action plan. |
A valid primary key for the action plan action record in the destination system is required. Either the DepActionPlanActionId or the DepActionPlanActionNumber is required. If both are present, then the DepActionPlanActionId is preferred. |
Optional A Null value is accepted. Either DepActionPlanActionNumber or DepActionPlanActionId is required to locate a ActionPlanAction row. |
Optional A Null value is accepted. |
ActionPlanActionId |
The action identifier of the action plan. |
A valid primary key for the action plan action record in the destination system is required. Either the ActionPlanActionNumber or the ActionPlanActionId is required. If both are present, then the ActionPlanActionId is preferred. |
Optional Either ActionPlanActionNumber or ActionPlanActionId is required to locate a Action Plan Action row. |
Optional |
ActionPlanActionNumber |
The reference number of the action plan action object. |
A valid action plan action PUID in the destination system. |
Required |
Optional |
You can view the Action Plan Action Relation 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 CX Sales and B2B 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 Action Plan Action Relation object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
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 Action Plan Action Relation.
-
Click Create Import Activity in the Manage Imports page.
-
In the Enter Import Options page, provide a name for the import activity, and select Action Plan Action Relation 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 Action Plan Action Relation.
-
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.
Import Your Activity Data
You can use Import Management to create, update, or delete your activity data.
You can import activity records using these steps:
-
Map your source activity data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the activity data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
You import activity data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.
You must 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 steps are complete, such as understanding what attributes are required for importing your objects.
-
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
To better manage your activity information, the activity object has the following child objects:
-
Activity Assignee
-
Activity Contact
-
Activity Objectives
If you want to import only a few records, then you can create a single CSV file for all activity attributes. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the activity child objects. Note that you must have imported the CSV file for activity object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects. For more information, see the related topics section.
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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new activities or are updating activities that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Activity Object
To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Make sure that you provide valid values for these attributes so that they pass import validations inbuilt into the application.
This table lists the required attributes for activity records, prerequisite setup tasks and specific validations, if any:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating an Activity record | Updating an Existing Activity record |
---|---|---|---|---|
AccountId |
The internal identifier of the account associated with the activity. Examples of account are: customer, organization, person, partner. |
The party must exist. You can determine the PartyId of the party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
Not Required |
If during update, you associate the activity with an account party, then you must provide either the internal ID, such as AccountId, or the public unique value, such as AccountPartyNumber, or the combination of original system and original system reference, such as AccountOrigSystem and OsrAccountId. |
AccountOrigSystem |
The code representing the source system for the account associated with the activity. |
The party must exist. Identify the source system code that was used when you imported the party in a prior batch. |
Not Required |
If during update, you associate the activity with an account party, then you must provide either the internal ID, such as AccountId, or the public unique value, such as AccountPartyNumber, or the combination of original system and original system reference, such as AccountOrigSystem and OsrAccountId. |
AccountPartyNumber |
The public unique identifier of the account associated with the activity. |
The party must exist and be a valid party unique identifier |
Not Required |
If during update, you associate the activity with an account party, then you must provide either the internal ID, such as AccountId, or the public unique value, such as AccountPartyNumber, or the combination of original system and original system reference, such as AccountOrigSystem and OsrAccountId. |
ActionCode |
Indicates explicitly the operation to be performed on a row: INSERT to create a new record in the destination tables, UPDATE to update an existing record in the destination table, DELETE to delete the record. |
The valid values are INSERT, UPDATE, and DELETE. If not provided, record matching is used to determine whether a record is updated (if it already exists) or inserted (if it doesn't exist). |
Not Required |
To delete a record, you must provide the value as DELETE. It is optional to provide values for insert and update as the framework internally decides the action as INSERT if it's a new record or UPDATE if it's an existing record. |
ActivityEndDate |
The date and time when an appointment ends or the time when a task is completed. |
This must be a valid date and should not be less than the ActivityStartDate. |
A value is required if you're creating a new activity having ActivityFunctionCode as APPOINTMENT. |
Optional |
ActivityFunctionCode |
Identifies the activity as an appointment or a task. This attribute is for internal use only and the value is set based on the user's navigation to the activity. |
Valid values are APPOINTMENT, TASK, and CALLREPORT. Lookup type used is ZMM_ACTIVITY_FUNCTION_TYPE_CD. |
A value is required while creating an activity. |
Not Required |
ActivityId |
The internal identifier of the activity. |
Automatically generated by the import process if creating a new activity record. |
Not Required |
A value is required if you're updating an existing activity and you're not providing other values to identify the activity record. To update an existing activity, choose one of the following options to identify the record:
|
ActivityNumber |
The public unique identifier of the activity. Indicates a default system-generated number for the activity. |
If a value is provided while creating a new activity, the value must be unique. For update, you can determine the existing unique value of the object by exporting the Activity object. Navigate to the following in the Setup and Maintenance work area:
The table ZMM_ACTY_ACTIVITIES with column ACTIVITY_NUMBER holds the existing value. |
Required |
A value is required if you're updating an existing activity and you're not providing other values to identify the activity record. To update or delete an existing activity you must choose one of the following options to identify the record:
|
ActivityStartDate |
The starting date and time of an appointment or a task. The default value for an appointment is null. The default value for a task is the date and time at which the task is created. |
If no value is provided, the corresponding value from Activity production table is used. |
A value is required if you're creating a new activity having ActivityFunctionCode as APPOINTMENT. |
Optional |
ActivityTypeCode |
The channel through which communication has taken place. |
If no value is provided, the corresponding value from Activity production table is used. If the ActivityFunctionCode is 'APPOINTMENT' and the action is 'INSERT' then the default value is set to 'MEETING'. |
If no value is provided, the corresponding value is used from the Activity production table. If the ActivityFunctionCode is APPOINTMENT and the action is INSERT, the default value is set to MEETING. |
Optional |
CampaignId |
The internal identifier of the related campaign. |
You can determine the public unique value of the object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an Activity, if you associate the Activity with a campaign, then you must provide either the internal ID, such as CampaignId, or the public unique value, such as CampaignNumber. |
When updating an Activity, if you associate the Activity with a campaign, then you must provide either the internal ID, such as CampaignId, or the public unique value, such as CampaignNumber. |
CampaignNumber |
The public unique identifier of the related campaign. |
You can determine the public unique value of the object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an Activity, if you associate the Activity with a campaign, then you must provide either the internal ID, such as CampaignId, or the public unique value, such as CampaignNumber. |
When updating an Activity, if you associate the Activity with a campaign, then you must provide either the internal ID, such as CampaignId, or the public unique value, such as CampaignNumber. |
ClaimCode |
The public unique identifier for claim. |
You can determine the public unique value of the object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an Activity, if you associate the Activity with a claim, provide either the internal ID, such as claim ID, or the public unique value, such as claim code. Ensure that this is a valid claim code from MKT_BDT_CLAIMS. |
Optional. Ensure that this is a valid claim code from MKT_BDT_CLAIMS. |
ClaimId |
The internal identifier of the claim. |
You can determine the public unique value of the object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an activity, if you associate the activity with a claim, then you must provide either the internal ID, such as claim ID, or the public unique value, such as claim code. Ensure that this is a valid claim ID from the MKT_BDT_CLAIMS table. |
Optional. Ensure that this is a valid claim ID from the MKT_BDT_CLAIMS table. |
CorpCurrencyCode |
The corporate currency used by the activity. |
If no value is provided, the corresponding value from Activity production table is used. |
If no value is provided, the corresponding value is used from the Assignee production table. |
If no value is provided, the corresponding value is used from the Assignee production table. |
CurcyConvRateType |
The rate of currency conversion for an activity. |
If no value is provided, the corresponding value from Activity production table is used. |
If no value is provided, the corresponding value is used from the Assignee production table. |
If no value is provided, the corresponding value is used from the Assignee production table. |
CurrencyCode |
The corporate currency used by the activity. |
If no value is provided, the corresponding value from Activity production table is used. |
If no value is provided, the corresponding value is used from the Assignee production table. |
If no value is provided, the corresponding value is used from the Assignee production table. |
CustomerAccountId |
The internal identifier of the customer account related to the activity. It is the sales activity identifier from ZCA_SALES_ACCOUNTS table. |
If no value is provided, the corresponding value from Activity production table is used. |
The internal identifier of the customer account related to the activity. It is the sales account identifier from ZCA_SALES_ACCOUNTS table. |
This should be a valid sales account identifier from the ZCA_SALES_ACCOUNTS table. |
DealId |
The internal identifier of the related deal registration. |
You can determine the public unique value of the object. Navigate to the following in the Setup and Maintenance work area:
|
Optional When creating an activity, if you associate the activity with a deal, you must provide either the internal ID, such as dealId, or the public unique value, such as DealNumber. |
Optional When creating an activity, if you associate the activity with a deal, you must provide either the internal ID, such as dealId, or the public unique value, such as DealNumber. |
DealNumber |
The public unique identifier of the deal associated with the activity. The identifier can also be generated from an external source. |
You can determine the public unique value of the object. Navigate to the following in the Setup and Maintenance work area:
|
Optional When creating an activity, if you associate the activity with a deal, you must provide either the internal ID, such as dealId, or the public unique value, such as DealNumber. |
Optional When creating an activity, if you associate the activity with a deal, you must provide either the internal ID, such as dealId, or the public unique value, such as DealNumber. |
DelegatorId |
The internal identifier of the activity resource that delegated activity ownership to another resource. |
The party must exist. You can determine the PartyId of the party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
Optional The party must exist. You can determine the PartyId of the party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
Optional The party must exist. You can determine the PartyId of the party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
DelegatorOrigSystem |
The source system reference to the delegator of original system identifier. |
The party must exist. Identify the source system code that was used when you imported the party in a prior batch. |
The party must exist. Identify the source system code that was used when you imported the party in a prior batch. |
Optional |
DirectionCode |
The direction options for an activity. The options are inbound, outbound, or optional. The default value is null. |
If no value is provided, the corresponding value from Activity production table is used. |
This should be a valid lookup code corresponding to ZMM_ACTIVITY_DIRECTION from fnd_lookups. |
This should be a valid lookup code corresponding to ZMM_ACTIVITY_DIRECTION from fnd_lookups. |
DueDate |
The date the activity is due to be completed. |
If no value is provided, the corresponding value from Activity production table is used. |
This should be a valid date. |
This should be a valid date |
Duration |
The actual duration of the activity in the appropriate unit of measure. |
If no value is provided, then the corresponding value from Activity production table is used. If the ActivityFunctionCode is 'APPOINTMENT' and the Duration is NULL then the default value is the duration of days between the Activity Start Date and the Activity End Date. |
This is a derived field. Any value provided is ignored. |
This is a derived field. Any value provided is ignored |
EnrollmentId |
The internal identifier of the related program enrollment. |
You can determine the public unique value of the object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an activity, if you associate the activity with a program enrollment, then you must provide either the internal ID, such as EnrollmentId, or the public unique value, such as EnrollmentNumber. This must be a valid value in the ZPM_PROGRAM_ENROLLMENTS table. |
If during update, you associate the activity with a program enrollment, then you must provide either the internal ID, such as EnrollmentId, or the public unique value, such as EnrollmentNumber. |
EnrollmentNumber |
The public unique identifier of the related program enrollment. |
You can determine the public unique value of the object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an activity, if you associate the activity with a program enrollment, then you must provide either the internal ID, such as EnrollmentId, or the public unique value, such as EnrollmentNumber. This must be a valid value in the ZPM_PROGRAM_ENROLLMENTS table. |
If during update, you associate the activity with a program enrollment, then you must provide either the internal ID, such as EnrollmentId, or the public unique value, such as EnrollmentNumber. |
FundRequestCode |
The foreign key to FUND_REQUEST_CODE of the MKT_BDT_FUND_REQUESTS table. |
You can determine the public unique value of the object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an activity, if you associate the activity with a fund request, you must provide either the internal ID, such as FundRequestId, or the public unique value, such as FundRequestCode. This must be a valid value in the MKT_BDT_FUND_REQUESTS table. |
When updating an activity, if you associate the activity with a fund request, you must provide either the internal ID, such as FundRequestId, or the public unique value, such as FundRequestCode. This must be a valid value in the MKT_BDT_FUND_REQUESTS table. |
FundRequestId |
The internal identifier of the fund request. |
You can determine the public unique value of the object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an activity, if you associate the activity with a fund request, you must provide either the internal ID, such as FundRequestId, or the public unique value, such as FundRequestCode. This must be a valid value in the MKT_BDT_FUND_REQUESTS table. |
When updating an activity, if you associate the activity with a fund request, you must provide either the internal ID, such as FundRequestId, or the public unique value, such as FundRequestCode. This must be a valid value in the MKT_BDT_FUND_REQUESTS table. |
LeadId |
The internal identifier of the related lead. |
You can determine the public unique value of the object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an activity, if you associate the activity with a lead, then you must provide either the internal ID, such as LeadId, or the public unique value, such as LeadNumber. Must be valid in the MKL_LM_LEADS table. |
If during update, you associate the activity with a lead, then you must provide either the internal ID, such as LeadId, or the public unique value, such as LeadNumber. |
LeadNumber |
The public unique identifier of the related lead. |
You can determine the public unique value of the object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an activity, if you associate the activity with a lead, then you must provide either the internal ID, such as LeadId, or the public unique value, such as LeadNumber. Must be valid in the MKL_LM_LEADS table. |
If during update, you associate the activity with a lead, then you must provide either the internal ID, such as LeadId, or the public unique value, such as LeadNumber. |
ObjectiveId |
The internal identifier of the objective. |
You can determine the public unique value of the object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an activity, if you associate the activity with a sales objective, you must provide either the internal ID, such as ObjectiveId, or the public unique value, such as ObjectiveNumber. It must be a valid value in the ZCA_OBJECTIVES table. |
When updating an activity, if you associate the activity with a sales objective, you must provide either the internal ID, such as ObjectiveId, or the public unique value, such as ObjectiveNumber. It must be a valid value in the ZCA_OBJECTIVES table. |
ObjectiveNumber |
The public unique identifier of the related objective. |
You can determine the public unique value of the object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an activity, if you associate the activity with a sales objective, you must provide either the internal ID, such as ObjectiveId, or the public unique value, such as ObjectiveNumber. It must be a valid value in the ZCA_OBJECTIVES table. |
When updating an activity, if you associate the activity with a sales objective, you must provide either the internal ID, such as ObjectiveId, or the public unique value, such as ObjectiveNumber. It must be a valid value in the ZCA_OBJECTIVES table. |
OpportunityId |
The internal identifier of the related opportunity. |
You can determine the public unique value of the object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an activity, if you associate the activity with an opportunity, you must provide either the internal ID, such as OpportunityId, or the public unique value, such as OpportunityNumber. This must be a valid value in the MOO_OPTY table. |
If during update, you associate the activity with an opportunity, then you must provide either the internal ID, such as OpportunityId, or the public unique value, such as OpportunityNumber. |
OpportunityNumber |
The internal identifier of the related opportunity. |
You can determine the public unique value of the object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an activity, if you associate the activity with an opportunity, you must provide either the internal ID, such as OpportunityId, or the public unique value, such as OpportunityNumber. This must be a valid value in the MOO_OPTY table. |
If during update, you associate the activity with an opportunity, then you must provide either the internal ID, such as OpportunityId, or the public unique value, such as OpportunityNumber. |
OrigEntityCode |
The code indicating the original source of the record. |
Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION. If the record was created in the Activity Management component, the value is ACTIVITY. |
Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION. If the record was created in the Activity Management component, the value is ACTIVITY. |
One of the following must be provided while updating an activity:
|
OrigEntityNumber |
The original unique identifier of the existing task, appointment, or interaction in the source system. |
If the internal action code is 'INSERT' and OrigEntityNumber and ActivityNumber are NULL then it's defaulted to the provided value. If no value is provided, the corresponding value from Activity production table is used. |
If the internal action code is "INSERT" and OrigEntityNumber and ActivityNumber are NULL, it's defaulted to the provided value. |
One of the following must be provided while updating an activity:
|
OsrAccountId |
The internal identifier (reference number or text) of the account party in the original source system. |
The party must exist. You can determine the Original System Reference for the party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
Optional When creating an activity, if you associate the activity with an account party, then you must provide either the internal ID, such as AccountId, or the public unique value, such as AccountPartyNumber, or the combination of original system and original system reference, such as AccountOrigSystem and OsrAccountId |
If during update, you associate the activity with an account party, then you must provide either the internal ID, such as AccountId, or the public unique value, such as AccountPartyNumber, or the combination of original system and original system reference, such as AccountOrigSystem and OsrAccountId. |
OsrDelegatorId |
The source system reference to the Delegator ID. |
The party must exist. You can determine the Original System Reference for the party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
Optional The party must exist. You can determine the Original System Reference for the party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
Optional The party must exist. You can determine the Original System Reference for the party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
OsrOwnerId |
The internal identifier (reference number or text) of the person who owns the activity in the original source system. |
The party must exist. You can determine the Original System Reference for party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
One of the following must be provided while creating an activity:
|
The party must exist. You can determine the Original System Reference for the party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
OsrPrimaryContactId |
The internal identifier (reference number or text) of the contact party in the original source system. |
The party must exist. You can determine the Original System Reference for the party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
Optional When creating the activity, if you associate the activity with a contact party, then you must provide either the internal ID, such as PrimaryContactId, or the public unique value, such as PrimaryContactPartyNumber, or the combination of original system and original system reference, such as PrimaryContactOrigSystem and OsrPrimaryContactId. |
When updating an activity, if you associate the activity with a contact party, then you must provide either the internal ID, such as PrimaryContactId, or the public unique value, such as PrimaryContactPartyNumber, or the combination of original system and original system reference, such as PrimaryContactOrigSystem and OsrPrimaryContactId. |
OsrReferenceCustomerId |
The internal identifier (reference number or text) of the customer in the original source system. |
The party must exist. You can determine the Original System Reference for the party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an activity, you associate the activity with a referenced customer party, then you must provide either the internal ID, such as ReferenceCustomerId, or the public unique value, such as RefCustPartyNumber, or the combination of original system and original system reference, such as RefCustOrigSystem and OsrReferenceCustomerId. |
When updating an activity, if you associate the activity with a referenced customer party, then you must provide either the internal ID, such as ReferenceCustomerId, or the public unique value, such as RefCustPartyNumber, or the combination of original system and original system reference, such as RefCustOrigSystem and OsrReferenceCustomerId. |
OutlookFlag |
Indicates whether the activity is created in Outlook. If the value is Y, then the activity is created in Outlook and synchronized. |
If no value is provided, the corresponding value from Activity production table is used. If the ActivityFunctionCode is 'APPOINTMENT' and the Action is 'INSERT' then the value is set to 'N'. |
If the ActivityFunctionCode is APPOINTMENT and the action is INSERT, the value is set to N. Possible values are Y and N. |
Optional Possible values are Y and N. |
OwnerId |
The internal identifier of the activity owner. The owner has to be an existing party (person) in system. |
The party must exist. You can determine the PartyId of a person by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
Provide one of the following while creating an activity: (OwnerId, OwnerResourceNumber, or a combination of OwnerOrigSystem and OsrOwnerId) |
Optional Provide one of the following while updating an activity: (OwnerId, OwnerResourceNumber, or a combination of OwnerOrigSystem and OsrOwnerId) |
OwnerOrigSystem |
The code representing the source system for the party (person) who owns the activity. |
The party must exist. You can determine the PartyId of a person by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
Provide one of the following while creating an activity: (OwnerId, OwnerResourceNumber, or a combination of OwnerOrigSystem and OsrOwnerId) |
Optional Provide one of the following while updating an activity: (OwnerId, OwnerResourceNumber, or a combination of OwnerOrigSystem and OsrOwnerId) |
OwnerResourceNumber |
The public unique identifier of the party (person) who owns the activity. |
The party must exist. You can determine the PartyId of a person by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
Provide one of the following while creating an activity: (OwnerId, OwnerResourceNumber, or a combination of OwnerOrigSystem and OsrOwnerId) |
Optional Provide one of the following while updating an activity: (OwnerId, OwnerResourceNumber, or a combination of OwnerOrigSystem and OsrOwnerId) |
ParentActivityId |
The related activity identifier and only applicable if the record is a follow up activity. |
Conditionally Required only for follow-up activity. One of the following options to identify the parent record must be provided:
|
A value is required if you're creating a follow-up activity. While creating an activity, choose one of the following options to identify the record:
|
Optional While updating an activity, choose one of the following options to identify the record: The unique ID for the ParentActivityId. The parent activity number (ParentActivityNumber). The source system code and source reference code (ParentOrigEntityNumber and ParentOrigEntityCode). |
ParentActivityNumber |
The public unique identifier of the related activity and only applicable if the record is a follow up activity. |
Conditionally Required only for follow-up activity. One of the following options to identify the parent record must be provided:
|
A value is required if you're creating a follow-up activity. While creating an activity, choose one of the following options to identify the record:
|
Optional While updating an activity, choose one of the following options to identify the record: The unique ID for the record (ParentActivityId). The parent activity number (ParentActivityNumber). The source system code and source reference code (ParentOrigEntityNumber and ParentOrigEntityCode). |
ParentOrigEntityCode |
The source of the activity record that indicating whether it's coming from Task entity, Interaction entity, or Appointment entity. |
Conditionally Required only for follow-up activity. One of the following options to identify the parent record must be provided:
|
A value is required if you're creating a follow-up activity. While creating an activity, choose one of the following options to identify the record:
|
Optional While updating an activity, choose one of the following options to identify the record: The unique ID for the record (ParentActivityId). The parent activity number (ParentActivityNumber). The source system code and source reference code (ParentOrigEntityNumber and ParentOrigEntityCode) |
ParentOrigEntityNumber |
The entity number of the parent entity in the original system to which the activity is related |
Conditionally Required only for follow-up activity. One of the following options to identify the parent record must be provided:
|
A value is required if you're creating a follow-up activity. While creating an activity, choose one of the following options to identify the record:
|
Optional While updating an activity, choose one of the following options to identify the record: The unique ID for the record (ParentActivityId). The parent activity number (ParentActivityNumber). The source system code and source reference code (ParentOrigEntityNumber and ParentOrigEntityCode). |
PartnerProgramId |
The internal identifier of the related partner program. |
You can determine the public unique value of the object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
For partner programs, export the Program Enrollments object. |
When creating an activity, if you associate the activity with a partner program, you must provide either the internal ID, such as PartnerProgramId, or the public unique value, such as PartnerProgramNumber. |
When updating an activity, if you associate the activity with a partner program, then you must provide either the internal ID, such as PartnerProgramId, or the public unique value, such as PartnerProgramNumber. |
PartnerProgramNumber |
The public unique identifier of the related partner program. |
You can determine the public unique value of the object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
For Partner programs, export the Program Enrollments object. |
When creating an activity, if you associate the activity with a partner program, then you must provide either the internal ID, such as PartnerProgramId, or the public unique value, such as PartnerProgramNumber. |
When updating an activity, if you associate the activity with a partner program, then you must provide either the internal ID, such as PartnerProgramId, or the public unique value, such as PartnerProgramNumber. |
PrimaryContactId |
The internal identifier of the activity contact. |
The party must exist. You can determine the PartyId of the party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
If no value is provided, the corresponding value from Activity production table is used. |
Optional When creating an activity, if you associate the activity with a contact party, then you must provide either the internal ID, such as PrimaryContactId, or the public unique value, such as PrimaryContactPartyNumber, or the combination of original system and original system reference, such as PrimaryContactOrigSystem and OsrPrimaryContactId. |
When updating an activity, if you associate the activity with a contact party, then you must provide either the internal ID, such as PrimaryContactId, or the public unique value, such as PrimaryContactPartyNumber, or the combination of original system and original system reference, such as PrimaryContactOrigSystem and OsrPrimaryContactId. |
PrimaryContactOrigSystem |
The code representing the source system for the activity contact. |
The party must exist. Identify the source system code that was used when you imported the party in a prior batch. You can determine existing source system codes and create new ones. Navigate to the following in the Setup and Maintenance work area:
|
Optional When creating an activity, if you associate the activity with a contact party, then you must provide either the internal ID, such as PrimaryContactId, or the public unique value, such as PrimaryContactPartyNumber, or the combination of original system and original system reference, such as PrimaryContactOrigSystem and OsrPrimaryContactId. |
When updating an activity, if you associate the activity with a contact party, then you must provide either the internal ID, such as PrimaryContactId, or the public unique value, such as PrimaryContactPartyNumber, or the combination of original system and original system reference, such as PrimaryContactOrigSystem and OsrPrimaryContactId. |
PrimaryContactPartyNumber |
The public unique identifier of the activity contact. |
The party must exist. You can determine the PartyNumber of a party by exporting either the Person object or the Organization object. Navigate to the following in the Setup and Maintenance work area:
|
Optional When creating an activity, if you associate the activity with a contact party, then you must provide either the internal ID, such as PrimaryContactId, or the public unique value, such as PrimaryContactPartyNumber, or the combination of original system and original system reference, such as PrimaryContactOrigSystem and OsrPrimaryContactId. |
When updating an activity, if you associate the activity with a contact party, then you must provide either the internal ID, such as PrimaryContactId, or the public unique value, such as PrimaryContactPartyNumber, or the combination of original system and original system reference, such as PrimaryContactOrigSystem and OsrPrimaryContactId. |
PriorityCode |
The priority of the activity. The default value is 2. The possible values are 1, 2, 3. |
If no value is provided, the corresponding value from Activity production table is used. |
Not required The default value is 2 (Medium). To change this value during create, you must pass this value. Valid values are 1, 2, and 3 |
When updating an activity, if you must modify the priority of an Activity, provide a valid value for PriorityCode. |
PrivateFlag |
Indicates whether the activity is private. |
If no value is provided, the corresponding value from Activity production table is used. |
Optional When creating an Activity, if you must mark an Activity as private, set this variable to 'Y'. |
When updating an activity, if you must mark an Activity as private, set this variable to 'Y'. |
RecurSerOrigEntityNumber |
The entity number of the recurring appointment in the original system, to which this activity is related |
If no value is provided, the corresponding value from Activity production table is used. |
A value is required if you're creating a recurring activity (appointment). While creating an activity, choose one of the following options to identify the record:
|
Optional |
RecurSeriesActivityNumb |
The activity number of an instance of a series. |
If no value is provided, the corresponding value from Activity production table is used. |
A value is required if you're creating a recurring activity (appointment). While creating an activity, choose one of the following options to identify the record:
|
Optional |
RecurSeriesId |
The internal identifier for the series that links instances of a series together. |
If no value is provided, the corresponding value from Activity production table is used. |
A value is required if you're creating a recurring activity (appointment). While creating an activity, choose one of the following options to identify the record:
|
Optional |
RecurWeekday |
The activity that recurs on every weekday such as Monday to Sunday, Weekday, Weekend, and so on. |
If no value is provided, the corresponding value from Activity production table is used. |
Conditionally required for a weekly recurring appointment. Must be a valid value from ZMM_ACTIVITY_RECUR_DAYWEEK_CD lookup. |
Conditionally required for a weekly recurring appointment. Must be a valid value from ZMM_ACTIVITY_RECUR_DAYWEEK_CD lookup. |
RefCustOrigSystem |
The source system code for the reference customer. |
The party must exist. Identify the source system code that was used when you imported the party in a prior batch. You can determine existing source system codes and create new ones. Navigate to the following in the Setup and Maintenance work area:
|
The party must exist. Identify the source system code that was used when you imported the party in a prior batch. You can determine existing source system codes and create new ones. Navigate to the following in the Setup and Maintenance work area:
|
When updating an activity, if you associate the activity with a referenced customer party, then you must provide either the internal ID, such as ReferenceCustomerId, or the public unique value, such as RefCustPartyNumber, or the combination of original system and original system reference, such as RefCustOrigSystem and OsrReferenceCustomerId. |
RefCustPartyNumber |
The public unique identifier of the reference customer who's associated with the activity. |
The party must exist. Identify the source system code that was used when you imported the party in a prior batch. You can determine existing source system codes and create new ones. Navigate to the following in the Setup and Maintenance work area:
|
The party must exist. Identify the source system code that was used when you imported the party in a prior batch. You can determine existing source system codes and create new ones. Navigate to the following in the Setup and Maintenance work area:
|
When updating an activity, if you associate the activity with a referenced customer party, then you must provide either the internal ID, such as ReferenceCustomerId, or the public unique value, such as RefCustPartyNumber, or the combination of original system and original system reference, such as RefCustOrigSystem and OsrReferenceCustomerId. |
ReferenceCustomerId |
The internal identifier of the reference customer who's associated with the activity. |
The party must exist. Identify the source system code that was used when you imported the party in a prior batch. You can determine existing source system codes and create new ones. Navigate to the following in the Setup and Maintenance work area:
|
The party must exist. Identify the source system code that was used when you imported the party in a prior batch. You can determine existing source system codes and create new ones. Navigate to the following in the Setup and Maintenance work area:
|
When updating an activity, if you associate the activity with a referenced customer party, then you must provide either the internal ID, such as ReferenceCustomerId, or the public unique value, such as RefCustPartyNumber, or the combination of original system and original system reference, such as RefCustOrigSystem and OsrReferenceCustomerId. |
SrId |
The foreign key to SR_ID in the SVC_SERVICE_REQUESTS table. |
You can determine the public unique value of this object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an activity, if you associate the activity with a service request, then you must provide either the internal ID, such as SrId, or the public unique value, such as SrNumber. This must be a valid value in SVC_SERVICE_REQUESTS. |
When updating an activity, if you associate the activity with a service request, then you must provide either the internal ID, such as SrId, or the public unique value, such as SrNumber. This must be a valid value in SVC_SERVICE_REQUESTS. |
SrNumber |
The foreign key to SR_NUMBER in the SVC_SERVICE_REQUESTS table. |
You can determine the public unique value of this object by exporting the object. Navigate to the following in the Setup and Maintenance work area:
|
When creating an activity, if you associate the activity with a service request, then you must provide either the internal ID, such as SrId, or the public unique value, such as SrNumber. This must be a valid value in SVC_SERVICE_REQUESTS. |
When updating an activity, if you associate the activity with a service request, then you must provide either the internal ID, such as SrId, or the public unique value, such as SrNumber. This must be a valid value in SVC_SERVICE_REQUESTS. |
StatusCode |
The status of the activity. The default value is Not Started. |
If no value is provided, the default is NOT_STARTED. The lookup Type used is ZMM_ACTIVITY_STATUS_CD. |
If no value is provided, the default is NOT_STARTED. The lookup Type used is ZMM_ACTIVITY_STATUS_CD. |
Optional The lookup Type used is ZMM_ACTIVITY_STATUS_CD. |
Subject |
The unique subject, name, or title of the activity. |
No validation |
A value is required if you're creating a new activity. |
Not Required |
SubmittedBy |
The user who submitted the call report. |
Conditionally required for a call report in Submitted status. |
Conditionally required for a call report in Submitted status. It must be a valid value in the HZ_PARTIES table. |
Optional Conditionally required for a call report in Submitted status. It must be a valid value in the HZ_PARTIES table. |
SubmittedDate |
The date and time when the call report was submitted. |
None |
Conditionally required for a call report in Submitted status. This must be a valid date. |
Conditionally required for a call report in Submitted status. This must be a valid date. |
Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the activity object. The page also lists attribute information like type, length, description, and so on.
Create the Source CSV File
You include the data that you want to import into CX Sales and B2B 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 Activity object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the activity 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 Activity 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 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.
Import Your Activity Assignee Data
You can use Import Management to create, update, or delete your activity assignee data.
You can import activity assignee records using these steps:
-
Map your source activity assignee data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the activity assignee data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
You import activity assignee data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.
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 steps are complete, such as understanding what attributes are required for importing your objects.
-
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
If you want to import only a few records, then you can create a single CSV file for all activity assignee attributes. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the activity assignee child objects. Note that you must have imported the CSV file for activity assignee object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects. For more information, see the related topics section.
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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new accounts or are updating accounts that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Activity Assignee Object
To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Make sure that you provide valid values for these attributes so that they pass import validations inbuilt into the application.
This table lists the required attributes for activity assignee records, prerequisite setup tasks and specific validations, if any:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating an Activity Assignee record | Updating an Existing Activity Assignee record |
---|---|---|---|---|
ActivityId |
The internal identifier of the activity to which the assignee is associated. |
Automatically generated by the import process if creating a new activity record. |
Optional |
A value is required if you're updating an existing activity and you're not providing other values to identify the activity record. To update an existing activity, choose one of the following options to identify the record:
|
ActivityNumber |
The public unique identifier of the activity to which the assignee is associated |
If a value is provided while creating a new activity, the value must be unique. For update, you can determine the existing unique value of the object by exporting the Activity object. Navigate to the following in the Setup and Maintenance work area:
The table ZMM_ACTY_ACTIVITIES with column ACTIVITY_NUMBER holds the existing value. |
A value is required if you're creating a new activity. |
A value is required if you're updating an existing activity and you're not providing other values to identify the activity record. To update an existing activity, choose one of the following options to identify the record:
|
AssigneeId |
The internal identifier of the HZ_PARTY record having PARTY_USAGE as Resource. |
If no value is provided, the corresponding value from Assignee production table is used. |
A value is required if you're associating a new assignee to an activity. One of the following must be provided while creating an assignee:
|
To update or delete an existing activity assignee you must choose one of the following options to identify the record:
|
AssigneeOrigSystem |
The source system reference to the assigned resource organization. |
None |
A value is required if you're associating a new assignee to an activity. One of the following must be provided while creating an assignee:
|
Not Required |
AssigneeResourceNumber |
The resource number associated with an assignee. |
None |
A value is required if you're associating a new assignee to an activity. One of the following must be provided while creating an assignee:
|
Not Required |
OrigEntityCode |
The code indicating the original source of the activity the activity to which the assignee is associated. |
Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION. If the record was created in the Activity Management component, the value is ACTIVITY. |
Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION. If the record was created in the Activity Management component, the value is ACTIVITY. |
A value is required if you're updating or deleting an existing activity and you're not providing other values to identify the activity record. To update or delete an existing activity you must choose one of the following options to identify the record:
|
OrigEntityNumber |
The original unique identifier of the existing task, appointment, or interaction in the source system. |
If the internal action code is 'INSERT' and OrigEntityNumber and ActivityNumber are NULL then it will be defaulted to the provided value. If no value is provided, the corresponding value from Assignee production table is used. |
If the internal action code is 'INSERT' and OrigEntityNumber and ActivityNumber are NULL, the value will be set to the value provided by the user. If no value is provided, the corresponding value is used from the Assignee production table. |
A value is required if you're updating or deleting an existing activity and you're not providing other values to identify the activity record. To update or delete an existing activity you must choose one of the following options to identify the record:
|
OsrAssigneeId |
The source system reference of the assignee.. |
The party must exist. You can determine the Original System Reference for the party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
A value is required if you're associating a new assignee to an activity. One of the following must be provided while creating an assignee:
|
Not Required |
Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the activity assignee object. The page also lists attribute information like type, length, description, and so on.
Create the Source CSV File
You include the data that you want to import into CX Sales and B2B 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 Activity Assignee object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the activity assignee 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 Activity Assignee 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 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.
Import Your Activity Contact Data
You can use Import Management to create, update, or delete your activity contact data.
You can import activity contact records using these steps:
-
Map your source activity contact data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the activity contact data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
You import activity contact data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.
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 steps are complete, such as understanding what attributes are required for importing your objects.
-
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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new activity contacts or are updating activity contacts that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Activity Contact Object
To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Make sure that you provide valid values for these attributes so that they pass import validations inbuilt into the application.
This table lists the required attributes for activity contact records, prerequisite setup tasks and specific validations, if any:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating an Activity Contact record | Updating an Existing Activity Contact record |
---|---|---|---|---|
ActivityId |
The internal identifier of the activity to which the contact is associated. |
Automatically generated by the import process if creating a new activity record. |
The value is generated automatically by the import process if creating a new activity record. |
A value is required if you're updating an existing activity and you're not providing other values to identify the activity record. To update an existing activity, choose one of the following options to identify the record:
|
ActivityNumber |
The public unique identifier of the activity to which the contact is associated |
If a value is provided while creating a new activity, the value must be unique. For update, you can determine the existing unique value of the object by exporting the Activity object. Navigate to the following in the Setup and Maintenance work area:
The table ZMM_ACTY_ACTIVITIES with column ACTIVITY_NUMBER holds the existing value. |
A value is required if you're creating a new activity. |
A value is required if you're updating an existing activity and you're not providing other values to identify the activity record. To update an existing activity, choose one of the following options to identify the record:
|
ContactId |
The party of type person who's involved with this appointment.. |
If no value is provided, the corresponding value from the Contacts production table is used. |
A value is required if you're associating a new contact to an activity. One of the following must be provided while creating a contact:
|
To update or delete an existing activity contact, select one of the following options to identify the record:
|
ContactOrigSystem |
The source system for the activity with which the contact is associated. |
No Validation |
A value is required if you're associating a new contact to an activity. One of the following must be provided while creating a contact:
|
Not Required |
ContactPartyNumber |
The party number of the contact. |
This must be a valid party in the HZ_PARTIES table. |
A value is required if you're associating a new contact to an activity. One of the following must be provided while creating a contact:
|
This must be a valid party in the HZ_PARTIES table |
CorpCurrencyCode |
The corporate currency used by the activity to which the contact is associated. |
If no value is provided, the corresponding value from the Contacts production table is used. |
If no value is provided, the corresponding value is used from the Contacts production table. |
If no value is provided, the corresponding value is used from the Contacts production table. |
OrigEntityCode |
The code indicating the original source of the activity the activity to which the contact is associated. |
Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION. Note: If the record was created in the Activity Management
component, the value is ACTIVITY.
|
Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION. Note: If the record was created in the Activity Management
component, the value is ACTIVITY.
|
A value is required if you're updating or deleting an existing activity and you're not providing other values to identify the activity record. To update or delete an existing activity you must choose one of the following options to identify the record:
|
OrigEntityNumber |
The ID that identifies the entity record in the original system.. |
If the internal action code is 'INSERT' and OrigEntityNumber and ActivityNumber are NULL then it will be defaulted to the provided value. If no value is provided, the corresponding value from Contacts production table is used. |
If the internal action code is 'INSERT' and OrigEntityNumber and ActivityNumber are NULL, the value will be set to the value provided by the user. If no value is provided, the corresponding value is used from the Contacts production table. |
A value is required if you're updating or deleting an existing activity and you're not providing other values to identify the activity record. To update or delete an existing activity you must choose one of the following options to identify the record:
|
OsrContactId |
The source system reference of the contact.. |
The contact must exist in system. You can determine the original system reference for the Contact by exporting the Contacts object. Navigate to the following in the Setup and Maintenance work area:
|
A value is required if you're associating a new contact to an activity. One of the following must be provided while creating an assignee:
|
The contact must exist in system. You can determine the original system reference for the Contact by exporting the Contacts object. Navigate to the following in the Setup and Maintenance work area:
|
OsrContactOrgId |
The source system reference to the contact organization. It is used to update the RELATIONSHIP_ID in the interface table (ZMM_IMP_ACTY_CONTACTS) based on HZ_PARTIES. |
This must be a valid organization type in the HZ_PARTIES table. |
This must be a valid organization type in the HZ_PARTIES table. |
This must be a valid organization type in the HZ_PARTIES table. |
Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the activity contact object. The page also lists attribute information like type, length, description, and so on.
Create the Source CSV File
You include the data that you want to import into CX Sales and B2B 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 Activity Contact object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the activity contact 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 Activity Contact 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 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.
Import Your Activity Objective Data
You can use Import Management to create, update, or delete your activity objective data.
You can import activity objective records using these steps:
-
Map your source activity objective data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the activity objective data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
You import activity objective data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.
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 steps are complete, such as understanding what attributes are required for importing your objects.
-
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
If you want to import only a few records, then you can create a single CSV file for all activity objective attributes. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the activity objective child objects. Note that you must have imported the CSV file for activity objective object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects. For more information, see the related topics section.
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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new activity objectives or are updating activity objectives that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Activity Objective Object
To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Make sure that you provide valid values for these attributes so that they pass import validations inbuilt into the application.
This table lists the required attributes for activity objective records, prerequisite setup tasks and specific validations, if any:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating an Activity Objective record | Updating an Existing Activity Objective record |
---|---|---|---|---|
ActionCode |
Indicates explicitly the operation to be performed on a row: INSERT to create a new record in the destination tables, UPDATE to update an existing record in the destination table, DELETE to delete the record. |
If value isn't provided, record matching is used to determine whether a record is updated (if it already exists) or inserted (if it doesn't exist). The valid values are INSERT, UPDATE, and DELETE. |
Optional |
To delete a record, you must provide the value as DELETE. It is optional to provide values for insert and update as the framework internally decides the action as INSERT if it's a new record or UPDATE if it's an existing record. |
ActivityId |
The internal identifier of the activity to which the Objective is associated. |
Automatically generated by the import process if creating a new activity record. |
A value is required if you're updating or deleting an existing activity and you're not providing other values to identify the activity record. To update or delete an existing activity you must choose one of the following options to identify the record:
A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:
|
A value is required if you're updating or deleting an existing activity and you're not providing other values to identify the activity record. To update or delete an existing activity you must choose one of the following options to identify the record:
A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:
|
ActivityNumber |
The public unique identifier of the activity to which the Objective is associated |
If a value is provided while creating a new activity, the value must be unique. For update, you can determine the existing unique value of the object by exporting the Activity object. Navigate to the following in the Setup and Maintenance work area:
The table ZMM_ACTY_ACTIVITIES with column ACTIVITY_NUMBER holds the existing value. |
A value is required if you're:
To update or delete an existing activity you must choose one of the following options to identify the record:
|
A value is required if you're updating an existing activity and you're not providing other values to identify the activity record. To update or delete an existing activity you must choose one of the following options to identify the record:
|
ObjectiveCode |
The set of predefined objectives defined by the administrator |
A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:
|
A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:
|
A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:
|
ObjectiveFreefmtText |
The objective in free form text as provided by the user. |
A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:
|
A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:
|
A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:
|
ObjectiveId |
The internal identifier of the objective associated with the activity. |
If no value is provided, the corresponding value from the Objectives production table is used. |
A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:
|
A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:
|
OrigEntityCode |
The code indicating the original source of the activity the activity to which the Objective is associated. |
Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION. If the record was created in the Activity Management component, the value is ACTIVITY |
Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION. If the record was created in the Activity Management component, the value is ACTIVITY. |
Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION. If the record was created in the Activity Management component, the value is ACTIVITY. |
OrigEntityNumber |
The original unique identifier of the existing task, appointment, or interaction in the source system. |
Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION. If the record was created in the Activity Management component, the value is ACTIVITY |
Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION. If the record was created in the Activity Management component, the value is ACTIVITY. |
Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION. If the record was created in the Activity Management component, the value is ACTIVITY. |
Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the activity objective object. The page also lists attribute information like type, length, description, and so on.
Create the Source CSV File
You include the data that you want to import into CX Sales and B2B 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 Activity Objective object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the activity objective 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 Activity Objective 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 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.
Import Your Additional Name Data
Use this topic to import Additional Name data into Oracle Applications Cloud. You can use the import functionality to create, update, or delete Additional Name records.
To import Additional Name records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Object Attributes
To import your Additional Name 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 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 need to set certain options for some attributes in the application before you can populate them. When importing a child record, ensure that its parent record exists in the database.
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 option to uniquely identify an object record is through the 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 Additional Name object, the attributes are NameID and RegistryID.
Required Attributes and Validations
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. The following table lists the required attributes for importing new Additional Name records, required attributes for updating Additional Name records, prerequisite setup tasks for the attributes, and specific validations, if any, for Additional Name import:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating an Additional Name Record | Updating an Existing Additional Name Record |
---|---|---|---|---|
NameId |
Unique identifier of the address record as the primary key |
No Validation |
Not required |
Optional Either the NameId or a combination of Source System and Source System Reference can be passed. |
StatusFlag |
The status of the additional name |
Defaults to Y during creation. |
Not required |
To inactivate an existing active Additional Name record, provide the value as "N". |
NameType |
Additional Name Type |
This must be a valid name type. The name types can be managed in Manage Name Types. |
Required |
If you don't provide the primary key, provide the existing additional name type. |
PartyNumber |
The public unique identifier of the party record to which the Additional Name is associated. |
The party number should exist. |
Conditionally required Provide reference information to identify the existing party. The reference information can be:
|
Not required |
PartySourceSystem |
The code representing the source system for the party (account, contact, household, or legal entity) to which the Additional name belongs. |
Identify the source system code that was used when you imported the party in a prior batch, or identify the source system code that you will use when importing the party in the same batch as this Additional Name. |
Conditionally required Provide one of the following :
|
Not required |
PartySourceSystemReferenceValue |
The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the Additional Name belongs. |
Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference that you will use when importing the party in the same batch as this Additional Name. |
Conditionally required Provide one of the following :
|
Not required |
PartyId |
The unique identifier as primary key of the party record to which the additional name is associated. |
Identify the party ID value by exporting the relevant Party object such as Account, Contact, and so on. |
Conditionally required Provide one of the following :
|
Not required |
SourceSystem |
Name of external source system of the account, contact or household with which the address is associated. |
The source system should exist. You can manage source systems from the Manage Source Systems task. |
Optional If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values. |
Not required |
SourceSystemReferenceValue |
Specifies the identifier in the original source system |
No validation |
Provide a valid value. |
Not required |
You can view the Additional Name object 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
The CSV file is provided as input to the file-based data import process. You must populate the CSV file with the data you want to import into Oracle Applications Cloud.
You can either create a CSV file on your own or use templates available in preexisting mappings. To download a template, do the following:
-
In the Navigator, under Tools, click Import Management.
-
Click Import Objects tab to open the Import Object Details page.
-
Select the object you're interested in the Import Object Details page and click the Download icon next to that object name.
-
Save the template CSV file to a location on your desktop.
You must edit the template CSV file and provide valid values for the required attributes. You can attach different types of files, giving each file a specific description.
PartyNumber | NameType | AdditionalName |
---|---|---|
RN_PTY_06_MAR_19_A1 |
LEGAL |
Test_Addname_A1 |
RN_PTY_06_MAR_19_A2 |
LEGAL |
Test_Addname_A2 |
RN_PTY_06_MAR_19_A3 |
LEGAL |
Test_Addname_A3 |
RN_PTY_06_MAR_19_A4 |
LEGAL |
Test_Addname_A4 |
RN_PTY_06_MAR_19_A5 |
LEGAL |
Test_Addname_A5 |
Create the Import Activity
To import data into Oracle Applications Cloud, you need to create an import activity and provide the CSV file as an input to the activity.
To create an import activity, do the following:
-
In the Navigator, under Tools, click Import Management.
-
On the Manage Imports page, click Create Import Activity.
-
In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Additional Name from the Object drop-down list.
-
In File Name, browse and upload the required .CSV file, and click Next.
-
In the Create Import Activity: Map Fields page edit the attribute mappings if required, and click Next.
Note: Click Validate Data to validate the mapping of the source file for unmapped columns and to check for data format issues. -
In the Create Import Activity: Review and Submit page, click Submit.
Review the Import Results
You can review the import results by checking for the import activity in the Manage Import Activity page. A file import activity is said to be successful when its status displays as Completed. To check the status of the import activity, do as follows:
-
In the Navigator, under Tools, click Import Management.
-
On the Manage Imports page, search for the import activity that you created using one of the search criteria, such as status, name, object, and so on.
-
Check the Status column for the import activity. The import is successful if the status displays as Completed. The other valid values for the import activity status are Queued for import, Preparing data for import, Importing data, Completed with errors, and Unsuccessful.
Import Your Additional Identifier Data
You can use Import Management to create or update Additional Identifier records.
To import Additional Identifier records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Object Attributes
To import your Additional Identifier 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 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
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 to uniquely identify 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. Use this option only if you're updating Additional Identifiers. 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 Additional Identifier object, the attributes are PartyIdentifierID and PartyID.
-
Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the Additional Identifier object, the attribute is PartyNumber.
Required Attributes and Validations for the Additional Identifier 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. The following table lists the required attributes for importing new Additional Identifier records, required attributes for updating Additional Identifier records, prerequisite setup tasks for the attributes, and specific validations, if any, for Additional Identifier import:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating a Additional Identifier Record | Updating an Existing Additional Identifier Record |
---|---|---|---|---|
PartySourceSystem |
The code representing the source system for the party (account, contact, household, or legal entity) to which the Additional identifier belongs |
Identify the source system code that was used when you imported the party in a prior batch, or identify the source system code that you will use when importing the party in the same batch as this Additional identifier. |
Conditionally required Provide reference information to identify the existing party. The reference information can be:
|
Not required |
PartySourceSystemReferenceValue |
The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the Additional identifier belongs. |
Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference that you will use when importing the party in the same batch as this Additional identifier. |
Conditionally required Provide reference information to identify the existing party. The reference information can be:
|
Not required |
PartyIdentifierID |
Unique identifier of the additional identifier of the party |
No validation |
Not required |
Required |
StatusCode |
The status of the additional identifier |
Not required This defaults to Y during creation. |
Not required |
To inactivate existing active Additional Name record, provide the value as N. |
PartyIdentifierType |
The type of the Additional Identifier import |
The Identifier Type must exist. You can manage additional types using the Manage Additional Name Types task. |
Required |
Not required |
PartyIdentifierValue |
Value to be imported for the Identifier Type |
Mandatory field |
Required |
Not required |
PartyNumber |
The public unique identifier of the party record to which the Additional identifier is associated. |
The party number should exist. |
Conditionally required Provide reference information to identify the existing party. The reference information can be:
|
Not required |
PartyID |
The unique identifier as primary key of the party record to which the additional identifier is associated. |
Identify the party ID value by exporting the relevant Party object such as Account, Contact, and so on. |
Conditionally required Provide reference information to identify the existing party. The reference information can be:
|
Not required |
SourceSystem |
Name of external source system of the account, contact or household with which the Additional identifier is associated. |
The source system should exist. You can manage source systems from the Manage Source Systems task. |
Optional If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values. |
Not required |
SourceSystemReferenceValue |
Specifies the identifier in the original source system. |
The combination of Source System and Source System Reference Value should be unique. |
Optional If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values. |
Not required |
You can view the Additional Identifier object 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 CX Sales and B2B 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 Additional Identifier object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
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 Additional Identifier from the Object drop-down list.
-
Select the CSV file in the File Name field, and click Next.
-
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 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.
Import Your Address Data
You can use the import functionality to create, update, or delete address records.
You can import address records using these steps:
-
Map your source data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the address data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
You import address data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.
Before you create the source data file, you should:
-
Know how your source data attributes map to the target object attributes in Oracle Applications Cloud. Match each column from the source file to an attribute in the address import object.
-
Finish all prerequisite steps, such as understanding what attributes are required for importing your objects.
-
Know how you can uniquely identify the records.
-
Check the target object attributes required in the CSV file for a successful import.
-
Ensure that you don't insert duplicate addresses while importing, to avoid redundant data.
If you want to import only a few records, then you can create a single CSV file for all address attributes. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the address child objects. Note that you must have imported the CSV file for address object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects.
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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new address or are updating address that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Address 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 address records, prerequisite setup tasks and specific validations, if any:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating an Address record | Updating an Existing Address record |
---|---|---|---|---|
PartyId |
The internal ID for the party (account, contact, household, or legal entity) to which the address belongs |
Identify the party ID value by exporting the relevant Party object such as Account, Contact, and so on. |
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
PartyNumber |
The code representing the source system for the party (account, contact, household, or legal entity) to which the address belongs. |
Identify the party ID value by exporting the relevant Party object such as Account, Contact, and so on. |
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
PartySourceSystem |
The code representing the source system for the party (account, contact, household, or legal entity) to which the address belongs. |
Identify the source system code that was used when you imported the party in a prior batch, or identify the source system code that you will use when importing the party in the same batch as this address |
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
PartySourceSystemReferenceValue |
The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the address belongs. |
Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference that you will use when importing the party in the same batch as this address. |
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
PrimaryFlag |
Identifies the primary address for the parent party record. |
Only one of the child records can be Primary. |
Optional |
Optional Pass Y to set Primary and N to reset an existing primary record. |
Status |
Indicates the current status of the address record. |
Not required Defaults to A (Active) |
Not required Defaults to A (Active) |
Optional Pass A to set the status to Active and I to set the status to Inactive. |
AddressId |
Unique identifier of the address record as primary key. |
No validation |
Not required |
Optional Either the AddressId or the AddressNumber can be passed. |
Country |
The country code component of the postal address. |
Identify valid country codes. |
Required |
Not required. |
LocationId |
The unique ID for the existing location record in the destination table. |
Identify the LOCATION_ID for an existing location by exporting the Location object. |
Optional |
Optional |
StartDateActive |
The date on which the address becomes valid. |
No validation |
This is a PUID for Address. If a value is passed, it will be imported. Otherwise, it will be auto-generated. |
The Address record can be updated by passing the Address Number. |
AddressNumber |
The address internal unique identifier that's internally generated when creating an address |
None |
This is a PUID for Address. If a value is passed, it will be imported. Otherwise, it will be auto-generated. |
The Address record can be updated by passing the Address Number. |
SourceSystem |
Name of external source system of the account, contact or household with which the address is associated. |
The source system should exist. You can manage source systems from the Manage Source Systems task. |
Optional If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values. |
Not required |
SourceSystemReferenceValue |
Specifies the identifier in the original source system |
Combination of Source System and Source System Reference Value should be unique. |
Optional If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values. |
Not required |
Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the address object. The page also lists attribute information like type, length, description, and so on.
Create the Source CSV File
You include the data that you want to import into CX Sales and B2B 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 Address object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the address information. To create an import activity:
-
Go to Navigator > Tools > Import Management > Import Queue.
-
On the Manage Imports page, click Create Import Activity.
-
In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Address 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 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.
-
Validate Geographies of Addresses against Master Geographies: This job helps you validate an address against master geography data and generates geography naming references. For more information about the Validate Geographies of Addresses against Master Geographies post processing job, see the section "Validate Geographies of Addresses against Master Geographies" in the
Understanding Scheduled Processes
guide. -
Populate Location Latitude and Longitude Information: You job helps you select and geocode newly created or updated addresses at regular time intervals. For more information about the Populate Location Latitude and Longitude Information post processing job, see the section "Populate Location Latitude and Longitude Information" in the
Understanding Scheduled Processes
guide.
Import Your Address Purpose Data
You can use the import functionality to create or update Address Purpose records.
You can import Address Purpose records using these steps:
-
Map your source data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the Address Purpose data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
You import Address Purpose data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.
Before you create the source data file, you should:
-
Know how your source data attributes map to the target object attributes in Oracle Applications Cloud. Match each column from the source file to an attribute in the Address Purpose import object.
-
Finish all prerequisite steps, such as understanding what attributes are required for importing your objects.
-
Know how you can uniquely identify the records.
-
Check the target object attributes required in the CSV file for a successful import.
-
Ensure that you don't insert duplicate Address Purposes while importing, to avoid redundant data.
If you want to import only a few records, then you can create a single CSV file for all Address Purpose attributes. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the Address Purpose child objects. Note that you must have imported the CSV file for Address Purpose object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects.
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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing a new Address Purpose or are updating Address Purpose records that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Address Purpose 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 Address Purpose records, prerequisite setup tasks and specific validations, if any:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating an Address Purpose record | Updating an Existing Address Purpose record |
---|---|---|---|---|
SiteSourceSystem |
The name of the external source system for the Address record to which the Address Purpose is associated. |
A combination of a valid SiteSourceSystem and SiteSourceSystemReferenceValue which are already imported |
Either the AddressId, Address Number or the combination of SiteSourceSystem and SiteSourceSystemReferenceValue is required. |
Not required |
SiteSourceSystemReferenceValue |
The identifier of the source system for the address record to which the Address Purpose is associated. |
A combination of a valid SiteSourceSystem and SiteSourceSystemReferenceValue, which are already imported |
Either the AddressId, Address Number or the combination of SiteSourceSystem and SiteSourceSystemReferenceValue is required. |
Not required |
PrimaryPerType |
This specifies the record that's imported as the primary key for a site use type. Specify Y for a record to set the specified site use type as the primary key. |
Y, N, or NULL Enter Y or N. Alternatively, don't enter any value. The default value is N. |
Not required |
Not required |
AddressPurposeId |
The primary key of the Address Purpose record |
No validation |
Not required |
Required Either the AddressPurposeId or the combination of SiteSourceSystem and SiteSourceSystemReferenceValue is required. |
Purpose |
The site codes such as SHIP_TO and BILL_TO that identify the Address Purpose |
The values are validated against the Lookup values for Site use codes. |
Required |
Not required |
StartDate |
The start date of the Address Purpose |
The date can't be earlier than the Address start date. |
Not required |
Not required |
EndDate |
The end date of the Address Purpose |
This date can't be later than the Address end date. |
Not required |
Not required |
AddressId |
The primary key of the Address record |
No validation |
Either the AddressId, Address Number or the combination of SiteSourceSystem and SiteSourceSystemReferenceValue is required. |
Not required |
AddressNumber |
The public unique identifier of the address |
Valid Address Number (Party Site Number) |
Either the AddressId, Address Number or the combination of SiteSourceSystem and SiteSourceSystemReferenceValue is required. |
Not required |
SourceSystem |
Name of external source system of the address purpose for the address that's associated with the account, contact, or household. |
The source system should exist. You can manage source systems from the Manage Source Systems task. |
Optional If your data source data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values. |
Required Either the AddressPurposeId or the combination of SiteSourceSystem and SiteSourceSystemReferenceValue is required. |
SourceSystemReferenceValue |
Specifies the identifier in the original source system for the Address Purpose record. |
The combination of Source System and Source System Reference Value should be unique. |
Optional If your data source is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values. |
Required Either the AddressPurposeId or the combination of SiteSourceSystem and SiteSourceSystemReferenceValue is required. |
Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the Address Purpose object. The page also lists attribute information like type, length, description, and so on.
Create the Source CSV File
You include the data that you want to import into CX Sales and B2B 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 Address Purpose object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the Address Purpose information. To create an import activity:
-
Go to Navigator > Tools > Import Management > Import Queue.
-
On the Manage Imports page, click Create Import Activity.
-
In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Address Purpose 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 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.
Import Your Asset Data
You can use the Import Management to create, update, or delete asset records.
You can import asset records using these steps:
-
Map your source asset data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the asset data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
To import your asset 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 must 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 steps are complete, such as understanding what attributes are required for importing your objects.
-
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
To better manage your asset information, the asset object has the following child objects:
-
Asset Contact
-
Asset Resource
If you want to import only a few records, then you can create a single CSV file for all asset attributes. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the asset child objects. Note that you must have imported the CSV file for asset object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects. For more information, see the related topics section.
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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new assets or are updating assets that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Asset 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 asset records, prerequisite setup tasks and specific validations, if any:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating an Asset record | Updating an Existing Asset record |
---|---|---|---|---|
AssetNumber |
The unique ID for the existing asset record in the destination table. |
None |
Required |
Required |
AssetOrigSystem |
A source system code that identifies the original source system of the asset. |
None |
Not required |
Not required |
AssetOrigSystemReference |
A source system reference that's the unique ID of the asset in your legacy or external system. |
None |
Not required |
Not required |
CustomerId |
The unique ID for the existing customer party record in the destination table. |
The party must exist. |
Required |
Not required |
Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the asset object. The page also lists attribute information like type, length, description, and so on.
Create the Source CSV File
You include the data that you want to import into CX Sales and B2B 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 Asset object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the asset 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 Asset 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 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.
Import Your Asset Contact Data
You can use Import Management to create, update, or delete your asset contact data.
You can import asset contact records using these steps:
-
Map your source asset contact data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the asset contact data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
You import asset contact data into Oracle Applications Cloud from a CSV file with your source data that's mapped to target object attributes.
Before you create the source data file, you should:
-
Know how your source data attributes map to the target object attributes in Oracle Applications Cloud. Match each column from the source file to an attribute in the asset import object.
-
Finish all prerequisite steps, such as understanding what attributes are required for importing your objects.
-
Know how you can uniquely identify the records.
-
Check the target object attributes 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 each attribute in your source data. For example, when using source system reference information to identify your asset records, the source system of the asset object should be enabled for parties in the Manage Trading Community Source Systems task.
-
You have all the parent records in place before importing child records. For example, when importing the asset contact, ensure the asset exists.
Select a Unique Identifier for Your Records
All records must be unique in the application. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For asset object, the attribute is AssetNumber and shows up in the UI as Asset Number. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new accounts or are updating accounts that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Asset Contact Object
To import data into Oracle Applications Cloud, your CSV file must include the required attributes. Make sure that you provide valid values for these attributes so that they pass import validations inbuilt into the application. This table lists the required attributes for asset contact records, prerequisite setup tasks for the attributes, and specific validations, if any.
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating an Asset Contact record | Updating an Existing Asset Contact record |
---|---|---|---|---|
ContactPartyId |
Unique party identifier representing a contact. |
The party must exist. |
Required |
Required |
AssetId |
The unique ID for the existing asset record in the destination table. |
An asset record with the Asset ID should exist. |
Conditionally required when you don't provide the Asset Number. |
Conditionally required when you don't provide the Asset Number. |
AssetNumber |
The unique ID for the existing asset record in the destination table. |
An asset record with the Asset Number should exist. |
Conditionally required when you don't provide the Asset ID. |
Conditionally required when you don't provide the Asset ID. |
Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the account object. The page also lists attribute information like type, length, description, and so on.
Create the Source CSV File
You include the data you want to import into Oracle Applications Cloud in a CSV file.
You can use the templates available in the Import Object Details page to create the source CSV file. To download a template:
-
Go to Navigator > Tools > Import Management > Import Objects.
-
Select the Asset Contact object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
AssetNumber | ContactPartyId | ContactFunctionCode |
---|---|---|
900546 |
300000018487543 |
ORA_ZCM_ASSET_MANAGER |
900604 |
300000018487544 |
ORA_ZCM_MAINTENANCE_ENGINEEER |
Create the Import Activity
After you have the CSV file ready, create an import activity to import the asset information.
To create an import activity:
-
Go to Navigator > Tools > Import Management > Import Queue.
-
Click Create Import Activity button on the Manage Imports page.
-
In the Enter Import Options page, provide a name for the import activity, and select Asset Contact 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. Click Next.
-
Check the file for unmapped columns or data format issues by clicking Validate Data.
-
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 Import Activity page. This page has 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. The Import Status column shows the status of the import activity.
-
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.
Import Your Asset Resource Data
You can use Import Management to create, update, or delete your Asset Resource data.
To import asset resource records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (.csv) file for import.
-
Create the import activity.
-
Review the import activity.
How You Map Your Source Data to Target Object Attributes
You import Asset Resource data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.
You must 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 steps are complete, such as understanding what attributes are required for importing your objects.
-
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
To better manage your Asset Resource information, the Asset Resource object has the following child objects:
-
Address
-
Classification
-
Relationship
-
Sales Team Member
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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new Asset Resources or are updating Asset Resources that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for the Asset Resource Object
To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Make sure that you provide valid values for these attributes so that they pass import validations inbuilt into the application.
This table lists the required attributes for Asset Resource records, prerequisite setup tasks and specific validations, if any:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating an Asset Resource record | Updating an Existing Asset Resource record |
---|---|---|---|---|
AssetId |
The unique ID for the existing asset record in the destination table. |
An asset record with the Asset ID should exist |
Conditionally required when you don't provide the Asset Number |
Conditionally required when you don't provide the Asset Number |
AssetNumber |
The unique ID for the existing asset record in the destination table. |
An asset record with the Asset Number should exist |
Conditionally required when you don't provide the Asset ID |
Conditionally required when you don't provide the Asset ID |
Resource Party ID |
Unique party identifier representing a resource |
The party must exist. |
Required |
Required |
Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the Asset Resource object. The page also lists attribute information like type, length, description, and so on.
Create the Source CSV File
You include the data that you want to import into CX Sales and B2B 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 Asset Resource object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the Asset Resource 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 Asset Resource 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 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.
Import Your Attachment Data
You can use Import Management to create, update, or delete Attachment records.
You can import attachment records using these steps:
-
Map your source attachment data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the attachment data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
You import attachment data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.
Before you create the source data file, you should:
-
Know how your source data attributes map to the target object attributes in Oracle Applications Cloud. Match each column from the source file to an attribute in the attachment import object.
-
Finish all prerequisite steps, such as understanding what attributes are required for importing your objects.
-
Know how you can uniquely identify the records.
-
Check the target object attributes 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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For attachment object, the attribute is PartyNumber and shows up in the UI as Party Number. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new attachments or are updating attachments that have source system reference data, then provide the source system and source system reference values. For attachment object, these are SourceSystem and SourceSystemReferenceValue and show up as Party Source System and Party Source System Reference Value in the UI.
Required Attributes and Validations for Attachment 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 attachment records, prerequisite setup tasks and specific validations, if any:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating an Attachment record | Updating an Existing Attachment record |
---|---|---|---|---|
PK!Value |
This is the primary key of the record to which the attachment is being associated. |
When creating or updating attachments, the parent record to which the attachment is associated must exist in the database. |
Either Pk1Value or PUID is mandatory. |
Either Pk1Value or PUID is mandatory. |
ObjectPUID |
This is the public unique identifier of the record to which the attachment is being associated. |
When creating or updating attachments, the parent record to which the attachment is associated must exist in the database. |
Either Pk1Value or PUID is mandatory. |
Either Pk1Value or PUID is mandatory. |
Category |
Category to which the attachment belongs. If you don't specify a value, the default is considered. For example, the default attachment category for lead is MKL_LEAD_CATEGORY.A source system reference that's the unique ID of the Attachment in your legacy or external system. |
If passing the category, it should be a valid category for that object. |
Not required If you don't provide a value, the default is used. |
Not required If you don't provide a value, the default is used. |
Description |
A brief description of the attachment. |
This can be any string of specified length. |
Not Required |
Not required |
FileName |
Name of the attachment file in which the attachment is stored. |
This can be any string of specified length. |
Either the File name or the URL is mandatory. |
Either the File name or the URL is mandatory. |
PK2 Value |
This is the primary key of the record to which the attachment is being associated. |
This is useful when the object has a composite primary key. |
This is useful when the object has a composite primary key. |
This is useful when the object has a composite primary key. |
PK3 Value |
This is the primary key of the record to which the attachment is being associated. |
This is useful when the object has a composite primary key. |
This is useful when the object has a composite primary key. |
This is useful when the object has a composite primary key. |
PK4 Value |
This is the primary key of the record to which the attachment is being associated. |
This is useful when the object has a composite primary key. |
This is useful when the object has a composite primary key. |
This is useful when the object has a composite primary key. |
PK5 Value |
This is the primary key of the record to which the attachment is being associated. |
This is useful when the object has a composite primary key. |
This is useful when the object has a composite primary key. |
This is useful when the object has a composite primary key. |
URL |
If the attachment type is url, this specifies the url. |
The URL format is validated. |
Either the file name or the URL is mandatory. |
Either the file name or the URL is mandatory. |
Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the attachment object. The page also lists attribute information like type, length, description, and so on.
Create the Source CSV File
You include the data that you want to import into CX Sales and B2B 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 Attachment object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the attachment 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 Attachment 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 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.
Import Your Business Plan Data
You can use Import Management to create, update, or delete your business plan data.
You can import business plan records using these steps:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (.csv) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Target Object Attributes
To import your Business Plan 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 steps are complete, such as understanding what attributes are required for importing your objects.
-
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. For example, when importing the address of an account, ensure the account exists.
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 to uniquely identify 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 Business Plan object, this attribute is BusinessPlanId.
-
Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the BusinessPlan object, the attribute is BusinessPlanNumber.
Review Required Attributes and Validations for Business Plan 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.
The following table lists the required attributes for importing new Business Plan records, required attributes for updating Business Plan records, prerequisite setup tasks for the attributes, and specific validations, if any, for Business Plan import:
Attribute | Description | Data Type | Data Length | Prerequisite Setup Task/ Import Validations | Creating a Business Plan record | Updating an Existing Business Plan record |
---|---|---|---|---|---|---|
BusinessPlanId |
Unique Identifier |
Long |
18 |
None |
Not required |
Required |
BusinessPlanNumber |
Public Unique Identifier |
String |
64 |
None |
Not required |
A value is required either for BusinessPlanId or for BusinessPlanNumber. |
PeriodTypeCode |
Period Type such as Year, Quarter, or Period |
String |
30 |
Use the Manage Calendar Profile Option task to set a value for ZCA_COMMON_CALENDAR. |
Required |
Not Required |
StatusCode |
Status of the BusinessPlan such as ORA_DRAFT, ORA_APPROVED |
String |
30 |
None |
Required |
Not required. |
PeriodEndDisplayName |
End Period Display Name |
String |
60 |
None |
Required |
Not required. |
PeriodStartDisplayName |
Start Period Display Name |
String |
60 |
None |
Required |
Not required. |
Name |
Unique name of the business plan |
String |
60 |
Enter a unique value. |
Required |
Not required. |
BusinessPlanClassCode |
Class of the business plan such as Account or Partner |
String |
20 |
Navigate to the following in the Setup and Maintenance Work area:
The default value is PARTNER. |
Required |
Not required. |
PartnerId |
Internal identifier of the Partner |
Long |
18 |
Enter the PartnerId if you select the BusinessPlanClassCode as PARTNER. |
A value is required, if you don't specify the PartnerNumber. |
Not required |
PartnerNumber |
Public unique identifier of the Partner |
String |
30 |
Enter the PartnerId if you select the BusinessPlanClassCode as PARTNER. |
A value is required, if you don't specify the PartnerId. |
Not required |
CustomerId |
Internal identifier of the Account |
Long |
18 |
Enter the PartnerId if you select the BusinessPlanClassCode as PARTNER. |
A value is required, if you don't specify the CustomerNumber. |
Not required |
CustomerNumber |
Public unique identifier of the Account |
String |
30 |
Enter the CustomerId or the CustomerNumber, if you select the BusinessPlanClassCode as ACCOUNT. |
A value is required, if you don't specify the CustomerId. |
Not required |
You can view the Business Plan 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 CX Sales and B2B 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 Contact object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
To import data into Oracle Applications Cloud, you need to create an import activity and provide the CSV file as an input to the activity.
To create an import activity, do the following:
-
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 Business Plan 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 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.
Import Your Business Plan SWOT Data
You can use Import Management to create, update, or delete your business plan SWOT data.
To import Business Plan SWOT records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (.csv) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Target Object Attributes
To import your Business Plan SWOT 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 steps are complete, such as understanding what attributes are required for importing your objects.
-
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. For example, when importing the address of an account, ensure the account exists.
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 to uniquely identify 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 Business Plan SWOT object, this attribute is SWOTId.
-
Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the BusinessPlan SWOT object, the attribute is SWOTNumber.
Required Attributes and Validations for Business Plan SWOT 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.
The following table lists the required attributes for importing new Business Plan SWOT records, required attributes for updating Business Plan SWOT records, prerequisite setup tasks for the attributes, and specific validations, if any, for Business Plan SWOT import:
Attribute | Description | Data Type | Data Length | Prerequisite Setup Task/ Import Validations | Creating a Business Plan SWOT Record | Updating an Existing Business Plan SWOT Record |
---|---|---|---|---|---|---|
SWOTTypeCode |
Identifies one of the four seeded and not extensible SWOT type codes:
|
String |
30 |
None |
Required |
Not required |
SWOTDescription |
A brief description of the SWOT types |
String |
2000 |
None |
Required |
Not required |
SWOTId |
Unique identifier of the SWOT |
Long |
18 |
None |
Not required |
Required |
SWOTNumber |
A unique number that identifies the SWOT record |
String |
64 |
None |
Not required |
Either the SWOTNumber or the SWOTId is required to update the records. |
BusinessPlanId |
The primary key of the parent record |
Long |
18 |
None |
A value is required to define to which business plan this child record of the SWOT belongs. |
Not required. |
BusinessPlanNumber |
A unique number that identifies the business plan |
String |
64 |
None |
A value is required either for the BusinessPlanId or for the BusinessPlanNumber. |
Not required. |
You can view the Business Plan SWOT 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
The .CSV file is provided as input to the file-based data import process. You must populate the .CSV file with the data you want to import into Oracle Applications Cloud.
You can either create a CSV file on your own or use templates available in preexisting mappings. To download a template, do the following:
-
In the Navigator, under Tools, click Import Management.
-
Click Import Objects tab to open the Import Object Details page.
-
Select the object you're interested in the Import Object Details page and click the Download icon next to that object name.
-
Save the template CSV file to a location on your desktop.
You must edit the template CSV file and provide valid values for the required attributes. You can attach different types of files, giving each file a specific description.
Description | SWOTTypeCode | BusinessPlanNumber |
---|---|---|
swot description |
THREAT |
myBP_0173 |
Create the Import Activity
To import data into Oracle Applications Cloud, you need to create an import activity and provide the CSV file as an input to the activity.
To create an import activity, do the following:
-
In the Navigator, under Tools, click Import Management.
-
On the Manage Imports page, click Create Import Activity.
-
In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Business Plan SWOT from the Object drop-down list.
-
In File Name, browse and upload the required .CSV file, and click Next.
-
In the Create Import Activity: Map Fields page edit the attribute mappings if required, and click Next.
Note: Click Validate Data to validate the mapping of the source file for unmapped columns and to check for data format issues. -
In the Create Import Activity: Review and Submit page, click Submit.
Review the Import Results
You can review the import results by checking for the import activity in the Manage Import Activity page. A file import activity is said to be successful when its status displays as Completed. To check the status of the import activity, do as follows:
-
In the Navigator, under Tools, click Import Management.
-
On the Manage Imports page, search for the import activity that you created using one of the search criteria, such as status, name, object, and so on.
-
Check the Status column for the import activity. The import is successful if the status displays as Completed. The other valid values for the import activity status are Queued for import, Preparing data for import, Importing data, Completed with errors, and Unsuccessful.
Import Your Business Plan Team Data
Use this topic to import Business Plan Team data into Oracle Applications Cloud. You can use the import functionality to create or update Business Plan Team records.
To import Business Plan Team records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (.csv) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Target Object Attributes
To import your Business Plan Team 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 steps are complete, such as understanding what attributes are required for importing your objects.
-
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 need to set certain options for some attributes in the application before you can populate them. When importing a child record, ensure that its parent record exists in the database.
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 to uniquely identify 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 Business Plan Team object, this attribute is BusinessPlanResourceId.
-
Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the Business Plan Team object, the attribute is BusinessPlanResourceNumber.
Required Attributes and Validations
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.
The following table lists the required attributes for importing new Business Plan Team records, required attributes for updating Business Plan Team records, prerequisite setup tasks for the attributes, and specific validations, if any, for Business Plan Team import:
Attribute | Description | Data Type | Data Length | Prerequisite Setup Task/ Import Validations | Creating a Business Plan Team Record | Updating an Existing Business Plan Team Record |
---|---|---|---|---|---|---|
ResourceId |
Specifies the resource added to the business team plan |
Long |
18 |
None |
Required |
Not required |
BusinessPlanId |
Specifies the parent record ID for which this child record is being created |
Long |
18 |
None |
Required |
Not required |
BusinessPlanResourceNumber |
A unique number that identifies the business plan |
String |
230 |
None |
Not required |
Required |
ResourceNumber |
A unique identifier that identifies the resource (team member) number |
String |
30 |
None |
Either the ResourceNumber or the ResourceId is required when creating a record. |
Not required. |
BusinessPlanResourceId |
The unique identifier of the business plan |
Long |
18 |
None |
Not required |
Either the BusinessPlanResourceId or the BusinessPlanResourceNumber is required to update the records. |
BusinessPlanNumber |
A unique number that identifies the business plan |
String |
64 |
None |
Either the BusinessPlanResourceId or the BusinessPlanResourceNumber is required to create the records. |
Not required. |
You can view the Business Plan Team 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
The .CSV file is provided as input to the file-based data import process. You must populate the .CSV file with the data you want to import into Oracle Applications Cloud.
You can either create a CSV file on your own or use templates available in preexisting mappings. To download a template, do the following:
-
In the Navigator, under Tools, click Import Management.
-
Click Import Objects tab to open the Import Object Details page.
-
Select the object you're interested in the Import Object Details page and click the Download icon next to that object name.
-
Save the template CSV file to a location on your desktop.
You must edit the template CSV file and provide valid values for the required attributes. You can attach different types of files, giving each file a specific description.
MemberFunctionCode | ResourceId | BusinessPlanNumber |
---|---|---|
ORA_BUS_DEVELOPMENT |
100010032635399 |
myBP_0173 |
Create the Import Activity
To import data into Oracle Applications Cloud, you need to create an import activity and provide the CSV file as an input to the activity.
To create an import activity, do the following:
-
In the Navigator, under Tools, click Import Management.
-
On the Manage Imports page, click Create Import Activity.
-
In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Business Plan Team from the Object drop-down list.
-
In File Name, browse and upload the required .CSV file, and click Next.
-
In the Create Import Activity: Map Fields page edit the attribute mappings if required, and click Next.
Note: Click Validate Data to validate the mapping of the source file for unmapped columns and to check for data format issues. -
In the Create Import Activity: Review and Submit page, click Submit.
Review the Import Results
You can review the import results by checking for the import activity in the Manage Import Activity page. A file import activity is said to be successful when its status displays as Completed. To check the status of the import activity, do as follows:
-
In the Navigator, under Tools, click Import Management.
-
On the Manage Imports page, search for the import activity that you created using one of the search criteria, such as status, name, object, and so on.
-
Check the Status column for the import activity. The import is successful if the status displays as Completed. The other valid values for the import activity status are Queued for import, Preparing data for import, Importing data, Completed with errors, and Unsuccessful.
Import Your Campaign Data
You can use Import Management to create or update Campaign records.
To import Campaign records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Target Object Attributes
To import your Campaign 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. 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 Campaign 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 Campaign records, required attributes for updating Campaign records, prerequisite setup tasks for the attributes, and specific validations, if any, for Campaign import:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating a Campaign Record | Updating an Existing Campaign Record |
---|---|---|---|---|
CreatedByModule |
The module used to create the campaign. |
By default, Web Service module is used to create the campaign. |
Not Required |
Not Required |
OwnerId |
The unique identifier of the campaign owner. |
The party must exist. Export the Party object to determine the PartyId of a person. |
Not Required |
Not Required |
OwnerPartyName |
The party name of the owner. |
The party must exist. Export the Party object to determine the PartyName of a person. |
Not Required |
Not Required |
OwnerPartyNumber |
The party number of the owner. |
The party must exist. Export the Party object to determine the PartyNumber of a person. |
Not Required |
Not Required |
ParentCampaignNumber |
The public unique identifier of the parent campaign. |
Export the Campaign records to identify the CampaignNumber of the parent campaign. |
Not Required |
Not Required |
Status |
The status of the campaign. |
The default value is Draft. |
Not Required |
Not Required |
CampaignId |
The unique identifier of the campaign. |
No validation |
Not Required |
Either CampaignId or CampaignNumber is required. |
CampaignName |
The name of the campaign. |
No validation |
Required |
Not Required |
CampaignNumber |
The PUID of the campaign. |
No validation |
Not Required |
Required |
You can view the Campaign 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 CX Sales and B2B 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 Campaign object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
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 Campaign 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 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.
Import Your Campaign Member Data
You can use Import Management to create or update Campaign Member records.
To import Campaign Member records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Target Object Attributes
To import your Campaign Member 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. 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 Campaign Member 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 Campaign Member records, required attributes for updating Campaign Member records, prerequisite setup tasks for the attributes, and specific validations, if any, for Campaign Member import:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating a Campaign Member Record | Updating an Existing Campaign Member Record |
---|---|---|---|---|
CampaignMemberId |
The primary key of the campaign member. |
No Validation |
Required Auto-generated |
Either CampaignMemberId or CampaignMemberNumber is required. |
CreatedByModule |
The module used to create the campaign member. |
No Validation |
Not Required |
Not Required |
CampaignCampaignNumber |
The Campaign PUID associated with the campaign member row. |
Identify the Campaign Number by exporting the Campaign objects. |
Not Required |
Not Required |
MemberResponseDate |
The date when the campaign member responded to the campaign. |
No Validation |
Required |
Required |
ContactPartyNumber |
The contact party number of the campaign member. |
Identify the Party Number for Contact by exporting the Contact party associated with the campaign member. Either provide the Lead Number or Contact Number value. |
Required |
Required |
LeadLeadNumber |
The lead number for the campaign member. |
Identify the Party Number for Lead by exporting the Lead party associated with the campaign member. Either provide the LeadNumber or the Contact Number. |
Required |
Required |
CampaignId |
The unique identifier of the campaign. |
Identify the Campaign Id by exporting the Campaign objects. |
Required |
Required |
CampaignNumber |
The PUID of the campaign. |
Identify the Campaign Number by exporting the Campaign objects. |
Not Required |
Not Required |
CampaignMemberNumber |
The PUID of the campaign member. |
No Validation |
Not Required |
Required |
You can view the Campaign Member 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 CX Sales and B2B 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 Campaign Member object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
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 Campaign Member 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 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.
Import Your Classification Data
You can use Import Management to create, update, or delete your classification data.
You can import classification records using these steps:
-
Map your source classification data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the classification data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
You import classification data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.
You must 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 steps are complete, such as understanding what attributes are required for importing your objects.
-
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
If you want to import only a few records, then you can create a single CSV file for all classification attributes. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the classification child objects. Note that you must have imported the CSV file for classification object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects. For more information, see the related topics section.
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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new classifications or are updating classifications that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Classification Object
To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Make sure that you provide valid values for these attributes so that they pass import validations inbuilt into the application.
This table lists the required attributes for classification records, prerequisite setup tasks and specific validations, if any:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating a Classification Record | Updating an Existing Classification Record |
---|---|---|---|---|
PartySourceSystem |
The code representing the source system for the party(account, contact, household, or legal entity) to which the Classification belongs. |
Identify the source system code that was used when you imported the party in a prior batch, or identify the source system code that you will use when importing the party in the same batch as this Classification. |
Conditionally required Provide one of the following :
|
Optional |
PartySourceSystemReferenceValue |
The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the classification belongs. |
Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference that you will use when importing the party in the same batch as this classification. |
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
Optional |
PrimaryFlag |
Identifies primary classification for the parent party record. |
Only one of the child records can be Primary. |
Optional |
Optional Pass Y to set Primary and N to reset an existing primary record. |
CodeAssignmentId |
The unique identifier for the customer classification assignment. |
It should be a valid existing value. |
Not required |
Either the Code assignment Id or a combination of Source System and Source System Reference is required. |
ClassCategory |
The classification category name |
The class category must exist. You can manage class categories from the Manage Class Categories task. |
Required A value is required if creating a new classification association record. |
Not Required |
ClassCode |
The classification code, within the classification category, assigned to the party. |
The value must be a valid code for the classification category. You can only assign one code if the category definition isn't enabled for multiple code assignments to a party within the same category. The code assignment must not already exist within the same time period. You can obtain classification codes for a classification category. |
Conditionally required A value is required if creating a new classification association record. |
Not Required |
StartDateActive |
The date on which the classification becomes valid. |
This should be a valid date. |
This defaults to the current date. |
Not required |
PartyId |
The internal ID for the party (account, contact, household, or legal entity) to which the address belongs |
Identify the party ID value by exporting the relevant Party object such as Account, Contact, and so on. |
Conditionally required Provide reference information to identify the existing party. The reference information can be:
|
Not required |
PartyNumber |
The public unique identifier of the party record to which the classification category and classification code are associated. |
The party number must exist. |
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
Not required |
EndDateActive |
The date on which the classification code is no longer valid. |
This should be a valid date. |
Optional |
Not required |
SourceSystem |
Name of external source system of the account, contact or household with which the address is associated. |
The source system should exist. You can manage source systems from the Manage Source Systems task. |
Optional If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values. |
Not required |
SourceSystemReferenceValue |
Specifies the identifier in the original source system |
The combination of Source System and Source System Reference Value should be unique. |
Optional If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values. |
Not required |
Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the classification object. The page also lists attribute information like type, length, description, and so on.
Create the Source CSV File
You include the data that you want to import into CX Sales and B2B 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 Classification object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the classification 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 Classification 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 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.
Import Your Classification Code Data
You can use Import Management to create or update Classification Code records.
To import Classification Code records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Object Attributes
To import your Classification Code 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 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:
-
Complete all the prerequisites for importing each attribute in your source data.
-
Have all parent records in place before importing child records.
Required Attributes and Validations for the Classification Code 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. The following table lists the required attributes for importing new Classification Code records, prerequisite setup tasks for the attributes, and specific validations, if any, for Classification Code import:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating a Classification Code Record | Updating an Existing Classification Code Record |
---|---|---|---|---|
ClassCategory |
User-defined classification category |
No validation |
Required |
You can't update the ClassCategory. However, it's required to identify the existing data. |
ClassCode |
User defined class codes for the user defined class category |
No validation |
Required |
You can't update the ClassCode. However, it's required to identify the existing data. |
Description |
Brief description of the classification code |
No validation |
Required |
Required |
Meaning |
The meaning of the classification code |
No validation |
Required |
Required |
ModifyHierarchy |
Option to indicate if the parent and child hierarchies of the classification codes are to be modified |
No validation |
Optional |
Not required |
ParentClassCode |
If there is a hierarchy set between the classification codes, then provide the parent classification code to which the child classification code belongs. |
User- defined ClassCategory via the "Manage Classification Categories" UI. |
Optional |
Not required |
You can view the Classification Code object 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 CX Sales and B2B 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 Classification Code object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
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 Classification Code from the Object drop-down list.
-
Select the CSV file in the File Name field, and click Next.
-
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 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.
Import Your Competitor Data
You can use Import Management to create or update Competitor records.
To import Competitor records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Object Attributes
To import your Competitor 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 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:
-
Complete all the prerequisites for importing each attribute in your source data.
-
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.
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 Competitor object, the attributes are Party Id and Registry Id.
Required Attributes and Validations for the Competitor 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. The following table lists the required attributes for importing new Competitor records, prerequisite setup tasks for the attributes, and specific validations, if any, for Competitor import:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating a Competitor Record | Updating an Existing Competitor Record |
---|---|---|---|---|
Organization Name |
Competitor Name - The name that identifies the competitor object |
Not Applicable |
Required |
Conditionally Required |
Name |
Competitor Name - The name that identifies the competitor object |
Not Applicable |
Conditionally Required |
Conditionally Required |
Party Type |
Competitor Party Type -Type of party record |
Not Applicable |
Conditionally Required The default value is ORGANIZATION. |
Do not provide a value. |
Party ID |
PartyId -The unique ID for the existing competitor record. |
A list of all party IDs is obtained by exporting the Competitor object. |
Do not provide a value. |
Required |
Registry ID |
Registry ID (PartyNumber) - The public unique identifier of the Competitor. |
Not Applicable |
Do not provide a value. |
Conditionally Required |
You can view the Competitor object 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 CX Sales and B2B 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 Competitor object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
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 Competitor from the Object drop-down list.
-
Select the CSV file in the File Name field, and click Next.
-
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 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.
Import Your Contact Data
You can use the Import Management to create, update, or delete contact records.
You can import contact records using these steps:
-
Map your source contact data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the contact data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
To import your contact 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 must 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 steps are complete, such as understanding what attributes are required for importing your objects.
-
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
To better manage your contact information, the contact object has the following child objects:
-
Address
-
Classification
-
Relationship
-
Sales Team Member
If you want to import only a few records, then you can create a single CSV file for all contact attributes. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the contact child objects. Note that you must have imported the CSV file for contact object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects. For more information, see the related topics section.
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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new contacts or are updating contacts that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for the Contact 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 contact records, prerequisite setup tasks and specific validations, if any:
Attribute | Description | Prerequisite Setup Task or Import Validations | Creating a Contact Record | Updating an Existing Contact Record | Deleting an Existing Contact Record |
---|---|---|---|---|---|
|
The code representing the source system for the contact. |
Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Applications Cloud using the Source System Reference import object. |
Conditionally Required For uniquely identifying a contact record, provide one of the following reference information:
|
Conditionally Required For uniquely identifying a contact record, provide one of the following reference information:
|
Conditionally Required For uniquely identifying a contact record, provide one of the following reference information:
|
|
The reference number or text representing the source system unique ID for the contact. |
Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Applications Cloud using the Source System Reference import object. |
Conditionally Required For uniquely identifying a contact record, provide one of the following reference information:
|
Conditionally Required For uniquely identifying a contact record, provide one of the following reference information:
|
Conditionally Required For uniquely identifying a contact record, provide one of the following reference information:
|
PartyNumber |
The public unique identifier of the contact. |
No prerequisite tasks |
Conditionally Required |
Conditionally Required |
Conditionally Required |
FirstName |
First name of a person party. |
No prerequisite tasks |
Required |
Not required |
Not required |
LastName |
Last name of a person party. |
No prerequisite tasks |
Required |
Not required |
Not required |
Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the contact object. The page also lists attribute information like type, length, description, and so on.
Create the Source CSV File
You include the data that you want to import into CX Sales and B2B 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 Contact object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the contact 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 Contact 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 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.
Import Your Contact Member Data
You can use the Import Management to create, update, or delete contact member records.
You can import contact member records using these steps:
-
Map your source contact member data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the contact member data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
To import your contact member 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 must 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 steps are complete, such as understanding what attributes are required for importing your objects.
-
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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new contact members or are updating contact members that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Contact Member 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 contact member records, prerequisite setup tasks and specific validations, if any:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating a Contact Member record | Updating an Existing Contact Member record |
---|---|---|---|---|
MemberId |
The unique ID for the existing member record in the Oracle Fusion destination table. |
The unique Id for the existing account Id record in the Oracle Fusion destination table. |
Not required |
Conditionally required A value is required if you're updating an existing Member ID and you're not providing the Service Request ID and Party ID. |
PartyId |
The unique ID for the existing party record in the Oracle Fusion destination table. |
Do not provide a value if creating a new party in the same import batch as this additional party name. If you provide the value for an existing party, the value must exist in the HZ_PARTIES table, column PARTY_ID. You can obtain the PARTY_ID for an existing party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:
|
Not required |
Not required |
Relationship Type Code |
Indicates relationship with the contact, such as ALTERNATE, FOLLOWER, or THIRD_PARTY. |
If providing a value, the value must exist in the FND_LOOKUPS table with LOOKUP_TYPE='ORA_SVC_CONTACT_REL_TYPE_CD'. |
Required |
Required |
Service Request ID |
Indicates the service request Id to which the contact member belongs. |
No validation |
Not required |
Conditionally required A value is required if you're updating an existing contact and you're not providing the SRNumber. |
SRNumber |
The unique number used to identify a service request. You can configure the service request number to a format that's best suitable to your organizational requirements. |
No validation |
Conditionally required A value is required if you're updating an existing record and you're not providing the Service Request ID.. |
Conditionally required A value is required if you're updating an existing record and you're not providing the Service Request ID. |
Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the contact member object. The page also lists attribute information like type, length, description, and so on.
Create the Source CSV File
You include the data that you want to import into CX Sales and B2B 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 Contact Member object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the contact member 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 Contact Member 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 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.
Import Your Contact Point Data
You can use Import Management to create update, or delete Contact Point records.
To import Contact Point records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Target Object Attributes
To import your Contact Point 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.
-
Ensure that you don't insert duplicate addresses while importing, to avoid redundant data.
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. You can use one of these to identify records:
-
Public unique identifiers: 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. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new contacts or are updating contacts that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Contact Point 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 Contact Point records, required attributes for updating Contact Point records, prerequisite setup tasks for the attributes, and specific validations, if any, for Contact Point import:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating a Contact Point Record | Updating an Existing Contact Point Record |
---|---|---|---|---|
ContactPointType |
Type of the contact point that's imported or updated |
This has to be a lookup_code in HZ_LOOKUPS with a lookup_type as COMMUNICATION_TYPE |
Provide one of these values:
|
Not required |
PartyId |
The internal ID for the party to which the contact point belongs |
No validation |
Provide one of the following :
|
Not required |
PartyNumber |
Specifies the PUID of the party |
No validation |
Provide one of the following :
|
Not required |
PartySourceSystem |
Specifies the original source system of the party |
This has to be in HZ_ORIG_SYSTEMS_B with the status "A". |
Provide one of the following :
|
Not required |
PartySourceSystemReferenceValue |
Specifies the party's source system reference in the original source system |
No validation |
Provide one of the following :
|
Not required |
SourceSystem |
Specifies the original source system name |
This has to be in HZ_ORIG_SYSTEMS_B with the status "A". |
Provide a valid value. |
Not required |
SourceSystemReferenceValue |
Specifies the identifier in the original source system |
No validation |
Provide a valid value. |
Not required |
ContactPointId |
System generated unique identifier. This is the primary key. |
No validation |
Not required |
If you can export the existing contact point, provide this primary key to identify the record for further updates. |
Status |
The status of the contact point. |
Not required This defaults to Y during creation. |
Not required |
To inactivate the existing active contact point record, provide the value "N". |
DoContactPreferenceFlag |
Add or update a contact's preference to receive e-mail or phone calls on the contact, account or household contact points. This attribute identifies if a contact has made a choice to be contacted. |
Don't set both this attribute and DoNotContactPreferenceFlag to Y simultaneously. Set either this attribute or DoNotContactPreferenceFlag to "Y". These are non-mandatory values. However, you can set both this attribute and DoNotContactPreferenceFlag to "N". |
Not required |
Not required |
DoNotContactPreferenceFlag |
Add or update a contact's preference not to receive e-mail or phone calls on the contact, account or household contact points. This attribute identifies if a contact has made no choice to be contacted. |
Don't set both this attribute and DoContactPreferenceFlag to Y simultaneously. Set either this attribute or DoContactPreferenceFlag to "Y". These are non-mandatory values. However, you can set both this attribute and DoContactPreferenceFlag to "N". |
Not required |
Not required |
DoNotContactReason |
Add or update the reason for a contact not to receive e-mail or phone calls on the contact, account or household contact points. |
This is used for DoNotContactPreferenceFlag. It is a non-mandatory field. |
Not required |
Not required |
You can view the Contact Point 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 CX Sales and B2B 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 Contact Point object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
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 Contact Point 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 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.
Import Your Contract Data
You can use Import Management to create or update Contract records.
To import Contract records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Object Attributes
To import your Contract 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 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:
-
Complete all the prerequisites for importing each attribute in your source data.
-
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.
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 Contract object, the attributes are Contract Id and Id.
Required Attributes and Validations for the Contract 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. The following table lists the required attributes for importing new Contract records, prerequisite setup tasks for the attributes, and specific validations, if any, for Contract import:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating a Contract Record | Updating an Existing Contract Record |
---|---|---|---|---|
ContractNumber |
The number that identifies the contract. |
No validation |
Required |
Not required |
ContractPuid |
The unique PUID that identifies the contract. |
This number identifier must be unique across contracts of all types. |
Required |
Required |
ContractTypeId |
The unique ID of the contract type. The contract type sets various properties for the contract such as the type of permitted contract lines, party roles, contract validation checks, and the contract acceptance and signature requirements. |
You can determine and manage contract types. Navigate to the following in Setup and Maintenance:
|
Required if ContractTypeName isn't entered. |
Not required |
ContractTypeName |
The name of the contract type. The contract type sets various properties for the contract such as the type of permitted contract lines, party roles, contract validation checks, and the contract acceptance and signature requirements. |
You can determine and manage contract types. Navigate to the following in Setup and Maintenance:
|
Required if ContractTypeId isn't entered. |
Not required |
Currency |
The name of the currency in which contract amounts are entered. |
This must be a valid currency. |
Required if CurrencyCode isn't entered |
Not required |
CurrencyCode |
The code of the currency in which contract amounts are entered. |
This must be a valid currency. |
Required if Currency isn't entered |
Not required |
InvOrganizationId |
The unique Id representing the item master organization |
This must be a valid ORGANIZATION_ID from the HR_ALL_ORGANIZATION_UNITS_F table. |
Required if the InvOrgName isn't entered |
Not required |
InvOrgName |
The name representing the item master organization. |
This must be a valid ORGANIZATION_ID from the HR_ALL_ORGANIZATION_UNITS_F table. |
Required if the InvOrganizationId isn't entered |
Not required |
LegalEntityId |
The unique Id of the legal entity to which the contract belongs. |
This must be a valid record as per GL_LEDGER_LE_V. |
Required if the LegalEntityName isn't entered. |
Not required |
LegalEntityName |
The name of the legal entity to which the contract belongs. |
This must be a valid record as per GL_LEDGER_LE_V. |
Required if the LegalEntityId isn't entered. |
Not required |
OrgId |
The unique Id of the business unit to which the contract belongs. |
This must be a valid business unit Id. |
Required if the OrgName isn't entered |
Not required |
OrgName |
The name of the business unit to which the contract belongs. |
This must be a valid business unit name. |
Required if the OrgId isn't entered |
Not required |
StartDate |
The date on which the contract comes into effect. |
No validation |
Required |
Not required |
StsCode |
The code of the contract status. Examples are ACTIVE, DRAFT, CLOSED, and CANCELED. |
Navigate to the following in Setup and Maintenance:
Search for the Contract Statuses lookup. |
Required |
Not required |
You can view the Contract object 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 CX Sales and B2B 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 Contract object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
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 Contract from the Object drop-down list.
-
Select the CSV file in the File Name field, and click Next.
-
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 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.
Import Your Contract Header Descriptive Flexfield Data
You can use Import Management to create or update Contract Header Descriptive Flexfield records.
To import Contract Header Descriptive Flexfield records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Object Attributes
To import your Contract Header Descriptive Flexfield 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 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:
-
Complete all the prerequisites for importing each attribute in your source data.
-
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 to uniquely identify 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 Contract Header Descriptive Flexfield object, the attribute is Contract Id.
-
Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the Contract Header Descriptive Flexfield object, the attribute is Contract PUID.
Required Attributes and Validations for the Contract Header Descriptive Flexfield 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. The following table lists the required attributes for importing new Contract Header Descriptive Flexfield records, prerequisite setup tasks for the attributes, and specific validations, if any, for Contract Header Descriptive Flexfield import:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating a Contract Header Descriptive Flexfield Record | Updating an Existing Contract Header Descriptive Flexfield Record |
---|---|---|---|---|
ContractId |
The Id of the contract. |
This must be a valid contract Id. |
Not required |
Not required |
ContractPuid |
The unique PUID that identifies the contract. |
This must be a valid contract PUID. |
Required |
Required |
AttributeCategory |
Attribute category of the descriptive flexfield |
No validation |
Not required |
Not required |
Attribute1 |
Attribute 1 of the descriptive flexfield |
No validation |
Required |
Not required |
Attribute2 |
Attribute 2 of the descriptive flexfield |
No validation |
Not required |
Not required |
Attribute3 |
Attribute 3 of the descriptive flexfield |
No validation |
Not required |
Not required |
Attribute4 |
Attribute 4 of the descriptive flexfield |
No validation |
Not required |
Not required |
Attribute5 |
Attribute 4 of the descriptive flexfield |
No validation |
Not required |
Not required |
You can view the Contract Header Descriptive Flexfield object 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 CX Sales and B2B 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 Contract Header Descriptive Flexfield object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
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 Contract Header Descriptive Flexfield from the Object drop-down list.
-
Select the CSV file in the File Name field, and click Next.
-
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 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.
Import Your Contract Line Data
You can use Import Management to create or update Contract Line records.
To import Contract Line records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Object Attributes
To import your Contract Line 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 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:
-
Complete all the prerequisites for importing each attribute in your source data.
-
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 to uniquely identify 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 Contract Line object, the attributes are Line Id and Id.
-
Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the Contract Line object, the attribute is Line PUID.
Required Attributes and Validations for the Contract Line 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. The following table lists the required attributes for importing new Contract Line records, prerequisite setup tasks for the attributes, and specific validations, if any, for Contract Line import:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating a Contract Line Record | Updating an Existing Contract Line Record |
---|---|---|---|---|
ContractPuid |
The unique PUID that identifies the contract |
No validation |
Required |
Not required |
ItemName |
The item name for an item type of line |
This must be a valid inventory item. |
Required for an item type of line |
Not required |
ItemNameTxt |
The item name for a free form type of line |
No validation |
Required for a free form type of line |
Not required |
ItemQuantity |
The line quantity. |
No validation |
Required for an item type of line |
Not required |
LineAmount |
The line amount. |
No validation |
Required for a free form type of line |
Not required |
LineNumber |
The number of the contract line. |
This must be a unique number within a contract. |
Required |
Not required |
LinePuid |
The unique PUID that identifies the contract line. |
This must be a unique PUID across all contract line records. |
Required |
Required |
LineStatus |
The line status |
This must be one of Active, Draft, Closed, or Canceled. |
Required if StsCode isn't entered |
Not required |
LineTypeId |
The Id that represents the line type. |
This must be valid as per OKC_CONTRACT_TYPE_LINES. |
Required if LineTypeName isn't entered |
Not required |
LineTypeName |
The name of the line type. |
This must be valid as per OKC_CONTRACT_TYPE_LINES. |
Required if LineTypeId isn't entered |
Not required |
StartDate |
The date from which the contract line becomes effective. |
No validation |
Required |
Not required |
StsCode |
The code that represents the line status |
This must be one of ACTIVE, DRAFT, CLOSED, or CANCELED |
Required if LineStatus isn't entered |
Not required |
UnitOfMeasure |
The unit of measure of the contract line. |
This must be a valid unit of measure in INV_UNITS_OF_MEASURE_TL.UNIT_OF_MEASURE. |
Required if the UOMCode isn't entered |
Not required |
UnitPrice |
The unit price of the line. |
No validation |
Required for an item type of line |
Not required |
UOMCode |
The UOM code of the contract line. |
This must be a valid unit of measure in INV_UNITS_OF_MEASURE_B.UOM_CODE. |
Required if the UnitOfMeasure isn't entered |
Not required |
You can view the Contract Line object 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 CX Sales and B2B 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 Contract Line object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
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 Contract Line from the Object drop-down list.
-
Select the CSV file in the File Name field, and click Next.
-
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 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.
Import Your Contract Line Descriptive Flexfield Data
You can use Import Management to create or update Contract Line Descriptive Flexfield records.
To import Contract Line Descriptive Flexfield records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Object Attributes
To import your Contract Line Descriptive Flexfield 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 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:
-
Complete all the prerequisites for importing each attribute in your source data.
-
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 to uniquely identify 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 Contract Line Descriptive Flexfield object, the attribute is Line Id.
-
Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the Contract Line Descriptive Flexfield object, the attribute is Line PUID.
Required Attributes and Validations for the Contract Line Descriptive Flexfield 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. The following table lists the required attributes for importing new Contract Line Descriptive Flexfield records, prerequisite setup tasks for the attributes, and specific validations, if any, for Contract Line Descriptive Flexfield import:
Attribute | Description | Prerequisite Setup Task/ Import Validations | Creating a Contract Line Descriptive Flexfield Record | Updating an Existing Contract Line Descriptive Flexfield Record |
---|---|---|---|---|
LineId |
The Id of the contract line. |
This must be a valid contract line Id. |
Not required |
Not required |
LinePuid |
The unique PUID that identifies the contract line. |
This must be a valid contract line PUID. |
Required |
Required |
AttributeCategory |
Attribute category of the descriptive flexfield |
No validation |
Not required |
Not required |
Attribute1 |
Attribute 1 of the descriptive flexfield |
No validation |
Required |
Not required |
Attribute2 |
Attribute 2 of the descriptive flexfield |
No validation |
Not required |
Not required |
Attribute3 |
Attribute 3 of the descriptive flexfield |
No validation |
Not required |
Not required |
Attribute4 |
Attribute 4 of the descriptive flexfield |
No validation |
Not required |
Not required |
Attribute5 |
Attribute 5 of the descriptive flexfield |
No validation |
Not required |
Not required |
You can view the Contract Line Descriptive Flexfield object 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 CX Sales and B2B 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 Contract Line Descriptive Flexfield object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
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 Contract Line Descriptive Flexfield from the Object drop-down list.
-
Select the CSV file in the File Name field, and click Next.