Import Your MDF Claim Settlement Data
You can use import management to create or update MDF Claim Settlement records.
To import MDF Claim Settlement 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 MDF Claim Settlement 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
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 MDF Claim Settlements. 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 MDF Claim Settlement object, the attributes are Claim Settlement ID and Claim 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 MDF Claim Settlement object, the attribute is ClaimSettlementCode.
Required Attributes and Validations for MDF Claim Settlement 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 MDF Claim Settlement records, required attributes for updating MDF Claim Settlement records, prerequisite setup tasks for the attributes, and specific validations, if any, for MDF Claim Settlement import:
Attribute |
Description |
Prerequisite Setup Task/ Import Validations |
Creating a MDF Claim Settlement Record |
Updating an Existing MDF Claim Settlement Record |
---|---|---|---|---|
Claim Settlement ID |
System generated unique claim settlement identifier |
This is automatically derived from the import process when importing a new MDF claim settlement. |
Not required |
A value is required if you're not providing another identifier for the MDF claim settlement. |
Type |
Specifies the type of transaction for the MDF claim settlement |
None |
Required |
Not required |
Accounting Type |
Specifies the type of MDF claim settlement - Credit or Debit. This is for reference only, as the MDF claim settlements doesn't have any effect on the available budget. |
This is derived when the payment type is selected. Accounting Type = Credit if Payment Type is Payment. |
Not required |
Not required |
Status |
Specifies the current status of the MDF claim settlement |
The default value is Incomplete. |
Required |
Not required |
Currency |
Transaction currency for the claim amount |
If providing a value, the value must exist in the CURRENCY_CODE column of the FND_CURRENCIES_VL table. You can view the valid currency codes. Navigate to the following in the Setup and Maintenance work area:
|
A value is required when importing a new MDF claim with any Status Code. |
A value is required when updating an MDF claim with Status Code Draft or Returned. |
Amount |
Specifies the amount being settled in the MDF claim settlement |
This amount can't exceed the outstanding claim liability. |
Required |
A value is required if updating an existing MDF claim settlement with the Status Code Incomplete. |
Claim ID |
System generated unique identifier |
If provided, the Status Code must be either Approved or Terminated. |
A value is required when importing an MDF claim settlement with any Status Code. |
Not required |
Claim Code |
Specifies a unique claim identifier |
If provided, the Status Code of the Claim Code must be either Approved or Terminated. |
A value is required when importing a new MDF claim settlement and you're not providing the unique identifier of the MDF claim. |
Not required |
Claim Settlement Code |
Specifies the unique identifier for MDF claim settlements |
None |
Not required |
A value is required if updating an existing MDF claim settlement and you're not providing any other identifier for the MDF claim settlement. |
You can view the MDF Claim Settlement 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
. -
Select the MDF Claim Settlement 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
. -
Click Create Import Activity in the Manage Imports page.
-
In the Enter Import Options page, provide a name for the import activity, and select MDF Claim Settlement 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.