How do I import product group data?
You can use the import management to create or update Sales Catalog Product Group or Product Group records.
To import Product Group/Sales Catalog Product Group records:
-
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 Product Group 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 Product Group object, this attribute is ProdGroupId.
-
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 Product Group object, the attribute is ProductGroupReferenceNumber.
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.
This table lists the required attributes for importing new Product Group records, required attributes for updating Product Group records, prerequisite setup tasks for the attributes, and specific validations, if any, for Product Group import:
Attribute |
Description |
Data Type |
Data Length |
Prerequisite Setup Task/ Import Validations |
Creating a Product Group Record |
Updating an Existing Product Group Record |
---|---|---|---|---|---|---|
ProdGrpDetailsId |
The unique identifier of the product group details. |
Long |
18 |
No validation |
Not required |
Not required |
StartDate |
The date and time from when the product group is available in the catalog. |
Time stamp |
The start date can't be later than the end date. |
Not required |
Optional |
|
EndDate |
The date and time when the product group is no longer available in the catalog. |
Time stamp |
The end date has to be later than the start date. |
Not required |
Optional |
|
InternalName |
The product group's unique name |
String |
150 |
Enter a unique name. |
Required |
This can't be updated. |
ProdGroupName |
The product group name displayed in the catalog. |
String |
250 |
No validation |
Required |
Optional |
ActiveFlag |
Indicates whether the product group is active or inactive. |
String |
1 |
Enter either Y or N. |
Defaults to Y |
Optional |
AllowDuplicateContentFlag |
Indicates whether products or product groups are allowed to be added to the product group hierarchy more than once. |
String |
Required |
Optional |
Defaults to N |
Optional |
ProdGroupId |
Unique identifier of the product group |
Long |
18 |
No validation |
A value is auto generated. |
Required |
ProductGroupReferenceNumber |
The unique value used to identify the product group. |
String |
50 |
Setup the on prefix and radix. Navigate to the following in the Setup and Maintenance work area:
|
A value is auto generated. You can also enter a value. |
Required |
RevenueRoleCode |
The code indicating the revenue role associated with the product group. For example, Sales revenue line set or Sales revenue line set member. |
String |
30 |
FCL validated against MOO_REVENUE_ROLE lookup |
Not required |
Optional |
RevenueCategoryCode |
The code indicating the revenue category associated with the product group. For example, Software, Maintenance, Service, Training, Hardware, or Back Maintenance. |
String |
30 |
FCL validated against MOO_REVN_CATEGORY lookup |
Not required |
Optional |
AllowSelectionFlag |
Indicates whether the product group is available for selection |
String |
1 |
Enter either Y or N. The import operation fails, if updating a record results in:
|
Defaults to Y |
Optional |
ModelName |
Unique name of the model |
String |
1000 |
No validation |
Not required |
Optional |
ModelConfigAttributes |
Model attributes |
String |
4000 |
No validation |
Not required |
Optional |
ProdGroupDescription |
Brief description of the product group |
String |
1000 |
No validation |
Not required |
Optional |
UsageRootFlag |
Indicates whether the product group is the root product group in a hierarchy. |
String |
1 |
Enter either Y or N. |
Defaults to N |
Optional |
AttachmentEntityName |
Unique name of the Attachment Entity |
String |
255 |
No validation |
Not required |
Optional |
You can view the Product Group 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 provide the .CSV file as input during 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:
-
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.
ProductGroupReferenceNumber |
InternalName |
ProdGroupName |
ProdGroupDescription |
UsageRootFlag |
ActiveFlag |
AllowDuplicateContentFlag |
StartDate |
EndDate |
---|---|---|---|---|---|---|---|---|
PGSIImport_001 |
PGSIImport_001 InternalName |
Display name of PGSIImport_001 |
Description of PGSIImport_001 |
Y |
Y |
Y |
05/10/2019 10:10 |
06/11/2019 11:11 |
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:
-
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 Product Group 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.