How do I import service request data?
You can use the Import Management to create, update, or delete service request records.
You can import service request records using these steps:
-
Map your source service request 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 service request 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 service request 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 service request information, the service request object has the following child object:
-
Service Request Reference
If you want to import only a few records, then you can create a single CSV file for all service request 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 service request child objects. Note that you must have imported the CSV file for service request 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 service requests or are updating service requests that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Service Request 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 service request records, prerequisite setup tasks and specific validations, if any:
Attribute |
Description |
Prerequisite Setup Task/ Import Validations |
Creating a Service Request record |
Updating an Existing Service Request record |
---|---|---|---|---|
Account ID |
The unique Id for the existing account Id record in the Oracle Fusion destination table. |
Do not provide a value if creating a new service request. If updating an existing service request, the value must exist in the SVC_SERVICE_REQUESTS table, column ACCOUNT_PARTY_ID. |
Not required |
Conditionally required A value is required if you're updating an existing Account ID. |
AssetID |
The unique internal ID for the existing service request record.. |
Do not provide a value if creating a new service request. If updating an existing service request, the value must exist in the ZCA_ASSET table, column ASSET_ID. |
Not required |
Conditionally required A value is required if you're updating an existing service request for this service request. |
Business Unit |
The unique ID of the business unit name associated with the service request. |
No validation |
Required |
Required |
Category ID |
Unique ID of a means of grouping service objects to enable easy identification and downstream reporting. |
If providing a value, the value must exist in the table SVC_SR_CATEGORIES (CATEGORY_ID). |
Not required |
Conditionally required A value is required if you're updating an existing Category ID for this service request. |
Inventory Item ID |
The unique internal Id for the existing sales catalog product (item) record. |
If providing a value, the value must exist in the EGP_SYSTEM_ITEMS_B table, column INVENTORY_ITEM_ID. The identified product must be defined for the sales catalog (QSC_PROD_GRP_ITEMS_TREE_V view). You can obtain the InventoryItemId for an existing product (item) by exporting the Product Group Products object. Navigate to the following in the Setup and Maintenance work area:
You can add products (items) to the sales catalog. Navigate to the following in the Setup and Maintenance work area:
|
Conditionally required A value is required if you're creating a new item inventory. |
Conditionally required A value is required if you're updating an item inventory and you're not providing the product's ID (InventoryItemId). |
Inventory Organization ID |
The unique internal Id for the existing product item organization's record in the destination table. |
If providing a value, the value must exist in the EGP_SYSTEM_ITEMS_B table, column ORGANIZATION_ID. The identified item organization must be the same organization defined for profile QSC_SALES_PRODUCTS_INVENTORY_ORG_ID. You can view the profile value. Navigate to the following in the Setup and Maintenance work area:
You can obtain the InventoryOrgId for an existing product (item) by exporting the Product Group Products object. Navigate to the following in the Setup and Maintenance work area:
|
Conditionally required A value is required if you're creating a new item inventory. |
Conditionally required A value is required if you're updating an item inventory and you're not providing the product's ID (InventoryItemId). |
Partner Account Party ID |
Foreign key that references HZ_PARTIES (PARTY_ID). |
Do not provide a value if creating a new partner account 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 |
Conditionally required A value is required if you're updating an existing Partner Account for this service request. |
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 |
Conditionally required A value is required if you're updating an existing party ID and you're not providing the party ID. |
Primary Contact ID |
The initial reported by contact and ongoing primary customer contact of the service request. |
Do not provide a value if creating a new Primary Contact Id in the same import batch as this additional party name. If you provide the value for an existing primary contact, 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 |
Conditionally required A value is required if you're updating an existing Primary Contact ID for this service request. |
Reference Number |
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 |
Not required |
Conditionally required A value is required if you're updating an existing reported by record and you're not providing the service request ID. |
Service Request ID |
The unique Id for the existing Service Request record in the Oracle Fusion destination table. |
No validation |
Not required |
Conditionally required A value is required if you're updating an existing Service Request Id and you're not providing the Service Request Number. |
Go to
, to see all the attributes of the service request 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 Sales and Fusion Service in a source CSV file.
You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:
-
Go to
. -
Select the Service Request 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 service request information. To create an import activity:
-
Go to
. -
Click Create Import Activity in the Manage Imports page.
-
In the Enter Import Options page, provide a name for the import activity, and select Service Request 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
. -
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.