Import Your Marketing Development Funds (MDF) Budget Data
You can use import management to create or update MDF Budget records.
To import MDF Budget 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 Marketing Development Funds (MDF) Budget 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 Budgets. 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 Budget object, the attributes are Budget Id and Owner 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 Budget object, the attributes are Owner Party Number and Company Party Number.
Required Attributes and Validations for MDF Budget 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 Budget records, required attributes for updating MDF Budget records, prerequisite setup tasks for the attributes, and specific validations, if any, for MDF Budget import:
Attribute |
Description |
Prerequisite Setup Task/ Import Validations |
Creating a MDF Budget Record |
Updating an Existing MDF Budget Record |
---|---|---|---|---|
BudgetID |
System generated unique identifier. |
None |
Not required |
Required MDF budgets can be imported if they're in the following status: Draft, Active, or Inactive. |
Start Date |
The date after which the MDF budget can be activated any time. |
If provided, this must be before the end date. |
Required |
Not required |
Claim Deadline |
Specifies the date by which claims should be submitted. |
If provided, this must be equal to or greater than the end date. |
Required |
Not required |
Request Deadline |
Specifies the date by which fund requests should be submitted. |
If provided, this must be between the start date and the end date. |
Required |
Not required |
OwnerID |
Identifies the owner of the MDF budget |
None |
Required |
Required |
Owner |
Identifies the owner name of the MDF budget |
None |
Not required |
Not required |
Partner |
Identifies the partner associated with the MDF budget |
This is applicable only when the MDF budget type is "Discretionary- Single Partner". |
Not required |
Not required |
OwnerPartyNumber |
Identifies the owner's party number of the MDF budget |
None |
Not required |
Not required |
PartnerCompanyNumber |
The unique identifier of the partner associated with the MDF Budget |
This is applicable only when the MDF budget type is "Discretionary- Single Partner". |
Not required |
Not required |
Name |
Specifies the name of the MDF budget. |
None |
Required |
Not required |
Currency |
Specifies the transaction currency for MDF budget amounts |
If providing a value, the value must exist in the CURRENCY_CODE column of the FND_CURRENCIES_VL table. You can view valid currency codes. Navigate to the following in the Setup and Maintenance work area:
|
Required |
Not required |
Initial Amount |
Specifies the initial amount allocated to the MDF budget. |
None |
Required |
Not required |
Status |
Current status for the Budget such as Draft , Active, or Inactive. |
None |
Required |
Not required |
Code |
Unique identifier of an MDF budget. |
None |
Conditionally required, if you're providing a budget name for a new MDF budget. |
Required if updating an existing budget and you aren't providing the unique Id of the MDF budget. |
You can view the MDF Budget 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 Budget 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 Budget 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.