Import Your Service Request Resource Data

You can use the Import Management to create or update service request resource records.

You can import service request resource records using these steps:

Map your source service request resource data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
Create source Comma Separated Values (CSV) file for import.
Create the import activity.
Check the import results.

How You Map Your Source Data to Target Object Attributes

To import your service request resource 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 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:

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 Service Request Resource object, the attributes are MemberID, ServiceRequestID, and ServiceRequestTeamMemberResourceID.
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 Service Request Resource object, the attributes are ResourceNumber and ServiceRequestNumber.

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

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Service Request Resource record	Updating an Existing Service Request Resource record
Member ID	The unique ID for the existing member record in the Oracle Fusion destination table.	This is auto generated.	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 and SrId).
ResourceNumber	Unique resource number that identifies the party Id.	If providing a value to update an existing service request resource, the value must exist in the HZ_PARTIES table, column PARTY_NUMBER.	Conditionally required A value is required if you're creating a service request resource record and not providing the Service Request Team Member Resource ID.	Conditionally required A value is required if you're adding a new resource to a service request or updating an existing service request resource record and you're not providing the record's unique Id (PartyId).
Service Request ID	Specifies the service request to which the service request resource member belongs.	No validation	Conditionally required A value is required if you're creating a service request resource record and not providing the service request number.	Conditionally required A value is required if you're updating an existing service request team and you're not providing the service request number (the public unique identifier of the service request).
Service Request Team Member Resource ID	The unique Id of the resource being added/updated to the service request team.	If providing a value to update an existing account, the value must exist in the HZ_PARTIES table, column PARTY_ID.	Conditionally required A value is required if you're adding a new resource to a service request and you're not providing the Resource Number (public unique identifier of the resource).	Conditionally required A value is required if you're adding a new resource to a service request or updating an existing service request resource record and you're not providing the record's public unique Id (Party Number).
Name	The name of the resource added as the service request resource member.	No validation	Not required	Not required
Service Request 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	Conditionally required A value is required if you're adding a 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.
Assigned To	Specifies the resource to which the service request is assigned.	No validation If the service request is assigned to the resource, this field can be set to Y.	Not required	Not required

You can view the Service Request Resource 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 Sales and Fusion Service in a source CSV file.

You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:

Go to Navigator > Tools > Import Management > Import Objects.
Select the Service Request Resource object in the table and click Download.

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

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

After you have the CSV file ready, create an import activity to import the service request 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 Service Request 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.