11g Release 6 (11.1.6)
Part Number E20373-06
Home
Contents
Book
List
Contact
Us
|
Oracle® Fusion
Applications Sales Implementation Guide 11g Release 6 (11.1.6) Part Number E20373-06 |
Home |
Contents |
Book List |
Contact Us |
 Previous |
 Next |
This chapter contains the following:
Import objects represent the application and attribute information for business objects that can be imported using external source files.
This topic describes the following:
Import object management options
Custom objects
A single import object can have multiple associated components that are considered objects by themselves. An object and associated objects that can be imported within the same source file are grouped together within the application module class.
Note
Each object includes the Import Activity object (MktImpJobs1). The Import Activity object is a required component of the application module but is not mapped to a source file. All values for this object are derived from the Import Activity definition. Consequently, do not update the Map, Required, and Default Value settings for the Import Activity object.
The following table includes information about the import object:
|
Option |
Description |
|---|---|
|
Attributes |
A view-only listing of object attributes that represent each column in the interface table for the object. |
|
Length |
A view-only listing of widths for the columns in the interface tables. If the source file values for the attribute have more characters than the attribute length, the source file row will not be imported. |
|
Default Value |
Optionally, specify an attribute value to use if a value is not available from the source file or Import Activity constant value. |
|
Map |
Enable the list of attributes that can be mapped to a source file or constant value in the Import Mapping and Import Activity Map Fields step. |
|
Required |
Specify the list of attributes that must be mapped to source file columns. Consequently, if you have selected an attribute as required, you must also enable the Map option for that attribute. When mapping the external source file, the required target attribute defined for the object are displayed with an asterisk. |
To use the file-based import feature for custom objects, you must first generate the artifacts required for import. You generate these required artifacts within Oracle Fusion CRM Application Composer, after making your object model extensions.
Import mapping enables you to predefine a mapping between the columns provided in a source file and the attributes pertaining to the objects being imported. Once you create a mapping, it can be reused in the Import Activity definition.
This topic contains the following sections:
Import options
Source file options
Target options
The following attributes pertain to the import mapping.
|
Attribute |
Description |
|---|---|
|
Object |
The business object to be imported. |
|
Name |
The name that identifies the mapping in the Import Mapping and Import Activity UIs. If the mapping was initially created while mapping fields directly in the Import Activity user interface and automatically saved without providing a user-defined mapping name, the mapping name is derived from the Import Activity name and date. |
|
Decimal Separator |
The format of the fractional portion of numerical values in columns mapped to attributes with a decimal attribute type. |
|
Date Format |
The format of values in columns mapped to attributes with a date attribute type. |
|
Timestamp Format |
The format of values in columns mapped to attributes with a time stamp attribute type. |
|
Lock |
If selected, prevents any user, other than the creator of the mapping, from editing the mapping. |
Map each column that the source file is expected to contain with a specific attribute.
The following table describes the details pertaining to columns provided in the source file:
|
Source Column |
Description |
|---|---|
|
Sequence |
The sequence number in which the columns are expected to be provided in the source file. Two rows cannot have the same sequence number. |
|
Column Name |
The column name expected in the source file if a header row is included, or more generic values such as Column A, Column B, and so on, if the header row is not included for Text file types. The tagging structure is represented for XML file types. |
|
Column Width |
Use when the delimiter value is fixed width for Text file types only. |
|
Ignore |
Ignore the source file column to exclude the data from being imported. |
|
Required |
If selected, a value must exist in the source file or the row will not be imported. |
The following table describes the details pertaining to corresponding attributes in the target application table:
|
Target Attributes |
Description |
|---|---|
|
Object |
The group of import objects that represent the components of the business object being imported. |
|
Attribute |
The attribute name that represents the corresponding interface table column for the object. |
|
Duplicate Validation |
If selected, the attribute, along with other selected attributes, determines what constitutes a duplicate object when comparing objects in the interface tables and existing objects in the target application tables. For example, to validate the uniqueness of an object in the target application tables by the combination of an object's name and date, select Duplicate Validation for both attributes in the mapping. |
File-based import supports the import of data from an external text or xml file to interface tables and then from interface tables to target application tables.
File-based import includes the following:
Source files with import data
Import objects with available import attributes
Mappings between source files and interface table columns
Import Activities to define import options, a processing schedule, and monitor progress
External data can be obtained in various ways and formatted in a text or xml file. The source file data is mapped to interface table columns using a Mapping. The source file is identified on an Import Activity, along with other import processing details. The file processing component of the file-based data import consists of reading the source file, parsing the data, and inserting the data into the appropriate interface tables.
Import Objects are defined where interface tables exist and external files can be used to import data into the interface tables. Import Object for Oracle objects that support file-based import are predefined. The list of objects is displayed based on the data security privileges for your role. Individual object attributes represent the interface table columns and are used to map source file data or constant values in Mappings and Import Activity definitions. Use the Import Object definition to manage the display of attributes that can be mapped, to indicate required mapping, and to set site level default values as needed.
Import mapping enables you to predefine a mapping between the columns provided in a source file and the attributes pertaining to the objects being imported. Once you create a mapping, it can be reused in the Import Activity definition.
An Import Activity definition provides the instructions for the import processing. It includes the source file or file location and mapping, plus import processing options and schedule. You can monitor the progress of the Import Activity processing and view completion reports for both successful records and errors.
The file-based data import process includes processing the source file data and inserting it into the interface tables, moving the interface table data into the destination application tables, and then processing the attachments for the imported objects. Processing factors are subject to the settings defined for the Import Activity, Mapping, and Import Object. You can monitor the processing steps and view process reports for each Import Activity.
This topic describes the following:
Inserting Data in the Interface Tables
Interface Table Data Validation and Error Counts
Interface Table to Destination Application Table Processing
Importing Attachments
Viewing Import Results
Data exists in various sources and in various formats. The file import processing starts with reading the source data, parsing the data, and inserting into the appropriate interface tables. The source of the data comes from the following:
Source file values mapped to target object attributes in the Import Activity.
Constant values defined for target object attributes in the Import Activity.
Default values defined for target object attributes in the Import Object.
The data is initially validated against the predefined Import Mapping and the Import Object settings as the interface tables are being populated by the initial file import process. The interface table data is validated again before importing into the destination application tables.
Validation includes:
Missing required values
Values that exceed the attribute length
Invalid values
Duplicates to existing records in the destination application tables based on the combination of attributes selected for duplicate validation in the predefined Import Mapping.
Note
For the Lead import object, the duplicate checking is only done for existing leads created within the look back days setting of the Import Activity.
Duplicates to existing records in the destination application tables for Customer Data Management objects based on Matching Configurations.
Errors
Most validation issues are recorded as errors, with the exception of Customer Data Management duplicates found during the Matching Configuration process. In this case, matched records are only considered as errors if:
Customer Management Duplicates option is set to Do Not Import for the Import Activity and
The main object of the Import Activity is a consumer, customer, or legal entity object
Allowable Error Count Threshold
The validation of the interface table occurs before any records are imported into the destination application tables. Once the validation process has completed, the count of records with errors is compared to the Allowable Error Count Threshold value specified for the Import Activity. A count above the threshold will stop the import process for all records. If the count is below the threshold, records without errors will import. In either case, records with errors will be reported in the Error and Exception files.
The import process orchestrates the import for each of the component objects that make up the overall main objects of the Import Activity.
Once the objects have imported successfully, the attachments are processed. The import process matches the source file attachment name to the file name included in the compressed file entered on the Import Activity. The attachment file is imported into Universal Content Manager and then associated as an attachment to the imported object.
You can monitor all file-based Import Activities that are currently scheduled to run, have completed successfully, or failed with errors. For each Import Activity, you can view the details pertaining to each underlying process. Once an Import Activity process has completed, the following processing reports are added as attachments to the process:
Log file. Includes the records that were successfully imported plus the unique destination application table identifiers for the objects.
Exception file. Includes the records that were not imported plus a reference to an error for each record that failed validation.
Error file. Includes all the errors for each record that failed validation.
You can create new opportunities or update existing opportunities by importing data through interface tables. To populate the interface tables you provide the data details in a source file and use the file-based import feature. Having a good understanding of the import entities, interface tables, and destination tables will help you prepare your import data.
Consider the following when importing opportunities:
File-based import
Import object entities, interface tables, and destination tables
The file-based import process reads the data included in your XML or text file, populates the interface tables, and imports the data into the application destination tables. The File-Based Data Import Setup and Maintenance task list includes the tasks needed to configure the opportunity import object, create source file mappings, and schedule the import activities.
Note
If using a text file, one row of data in your source file represents a single opportunity. Consequently, if you have a one-to-many scenario for some of the opportunity's details, you must repeat each set of data in the source file on the same row. For example, if the opportunities in your source file typically include up to two contacts, create a set of data for contact one, and an additional set of data for contact two to include on the same row as your opportunity.
You can use the same source file to import both extensible custom attributes and the standard opportunity object attributes. First, design your object model extensions in Oracle Fusion CRM Application Composer and generate the required artifacts to register your extensions and make them available for importing. When complete, the import object is updated with the extensible attributes, which can then be mapped to your source file data.
Opportunity notes, interactions, appointments, and tasks are imported independently using separate source files and import activities for each. Include the data that will identify the associated opportunity in the notes, interactions, appointments, and tasks source files.
Note
To obtain unique IDs for the opportunities you have just imported, you can view the log file of successful records in the opportunity's import activity by navigating to Setup and Maintenance and selecting the Manage File Import Activities task. When the opportunity import activity is complete, select the Schedule Status link to access the log file containing the opportunity IDs.
You can import attachments to your import object by including the file names in your opportunity source file and selecting the files when defining your import activity.
The opportunity import object consists of entities that form the opportunity. Since interface tables are tied to import object entities and the opportunity object consists of many entities, there are multiple interface tables included in importing opportunities. You map your source file data to import entity attributes that correspond to the interface table columns. The import activity process will populate the interface tables based on the mapping and your source file. If you need the unique IDs of existing application data for your import data, use the Define Data Export Setup and Maintenance task list to export the information.
Note
Spreadsheets containing detailed information about each interface table, including the import attributes, corresponding interface table columns, defaults, and validations, are available from the Oracle Enterprise Repository by searching on a specific interface table name or initiating a search using the FusionApps: Interface Table asset type.
The following table lists the object entities, tables, and resulting application objects:
|
File-Based Import Entities |
Interface Tables |
Destination Tables |
Application Object |
|---|---|---|---|
|
Opportunity |
MOO_IMP_OPTY |
MOO_OPTY |
Opportunity |
|
OpportunityCompetitor |
MOO_IMP_OPTY_COMPETITORS |
MOO_OPTY_COMPETITORS |
Opportunity competitor |
|
OpportunityContact |
MOO_IMP_OPTY_CON |
MOO_OPTY_CON |
Opportunity contact |
|
OpportunityLead |
MOO_IMP_OPTY_LEADS |
MOO_OPTY_LEADS |
Opportunity lead |
|
OpportunityReference |
MOO_IMP_OPTY_REFERENCES |
MOO_OPTY_REFERENCES |
Opportunity reference |
|
OpportunityResource |
MOO_IMP_OPTY_RESOURCES |
MOO_OPTY_RESOURCES |
Opportunity resource |
|
OpportunityResponse |
MOO_IMP_OPTY_RESPONSES |
MOO_OPTY_RESPONSES |
Opportunity response |
|
OpportunityRevenue |
MOO_IMP_REVN |
MOO_REVN |
Opportunity revenue |
|
OpportunityRevenueLineSet |
MOO_IMP_REVN_LINE_SET |
MOO_REVN |
Opportunity revenue line set |
|
OpportunityRevenuePartner |
MOO_IMP_REVN_PARTNER |
MOO_REVN_PARTNER |
Opportunity revenue partner |
|
OpportunitySource |
MOO_IMP_OPTY_SRC |
MOO_OPTY_SRC |
Opportunity source |
The following table lists the note, interaction, appointment, and task object entities, tables, and resulting application objects:
|
File-Based Import Entities |
Interface Tables |
Destination Tables |
Application Object |
|---|---|---|---|
|
NoteImport NoteImportForQuery |
ZMM_IMP_NOTES |
ZMM_NOTES |
Opportunity note |
|
InteractionAssociationImport InteractionImport InteractionParticipantImport |
ZMM_IMP_INT_ASSOCIATIONS ZMM_IMP_INT_INTERACTIONS ZMM_IMP_INT_PARTICIPANTS |
ZMM_INTER_ASSOCIATIONS ZMM_INTER_INTERACTIONS ZMM_INTER_PARTICIPANTS |
Opportunity interaction |
|
ActivityAssigneeImport ActivityAssociationImport ActivityContactImport AppointmentImport NoteImport |
ZMM_IMP_ACT_ASSIGNMENTS ZMM_IMP_ACT_ASSOCIATIONS ZMM_IMP_ACT_CONTACTS ZMM_IMP_ACTIVITIES ZMM_IMP_NOTES |
ZMM_ACT_ASSIGNMENTS ZMM_ACT_ASSOCIATIONS ZMM_ACT_CONTACTS ZMM_ACTIVITIES ZMM_NOTES |
Opportunity appointment and appointment notes |
|
TaskAssigneeImport TaskContactImport TaskImport NoteImport |
ZMM_IMP_WF_ASSIGNEES ZMM_IMP_TASK_CONTACTS ZMM_IMP_WF_TASK ZMM_IMP_NOTES |
WF_ASSIGNEES ZMM_ACT_CONTACTS CRM_FUSION_SOAINFRA.WFTASK ZMM_NOTES |
Opportunity task and opportunity task notes |
You can create new notes by importing data through interface tables. To populate the interface table, you provide the data details in a source file and use the file-based import feature. Having a good understanding of the import entity, interface table, and destination table will help you prepare your import data.
Consider the following when importing notes:
File-based import
Import object entity, interface table, and destination table
The file-based import process reads the data included in your XML or text file, populates the interface table, and imports the data into the application destination table. The File-Based Data Import Setup and Maintenance task list includes the tasks needed to configure the note import object, create source file mappings, and schedule the import activities.
You can use the same source file to import both extensible custom attributes and the standard note object attributes. First, design your object model extensions in Oracle Fusion CRM Application Composer and generate the required artifacts to register your extensions and make them available for importing. When complete, the import object is updated with the extensible attributes, which can then be mapped to your source file data.
You can import attachments to your import object by including the file names in your note source file and selecting the files when defining your import activity.
The note import object consists of one entity that forms the note. Since interface tables are tied to import object entities, there is only one interface table for importing notes. You can map your source file data to the import entity attributes that correspond to the interface table columns. The import activity process populates the interface table based on the mapping and your source file. If you need the unique IDs of existing application data for your import data, use the Define Data Export Setup and Maintenance task list to export the information.
Note
Spreadsheets containing detailed information about each interface table, including the import attributes, corresponding interface table columns, defaults, and validations, are available from the Oracle Enterprise Repository by searching on a specific interface table name or initiating a search using the FusionApps: Interface Table asset type.
The following lists the object entity, tables, and resulting application object:
|
File-Based Import Entity |
Interface Table |
Destination Table |
Application Object |
|---|---|---|---|
|
NoteImport |
ZMM_IMP_NOTES |
ZMM_NOTES |
Note |
You can create new tasks by importing data through interface tables. To populate the interface table you provide the data details in a source file and use the file-based import feature. Having a good understanding of the import entities, interface tables, and destination tables will help you prepare your import data.
Consider the following when importing tasks:
File-based import
Import object entities, interface tables, and destination tables
The file-based import process reads the data included in your XML or text file, populates the interface tables, and imports the data into the application destination tables. The File-Based Data Import Setup and Maintenance task list includes the tasks needed to configure the task import object, create source file mappings, and schedule the import activities.
Note
If using a text file, one row of data in your source file represents a single task. Consequently, if you have a one-to-many scenario for some of the task's details, you must repeat each set of data in the source file on the same row. For example, if the tasks in your source file typically include up to two contacts, create a set of data for contact one and an additional set of data for contact two to include on the same row as your task. The file-based import process supports up to ten sets of data per entity per row in the text file.
You can use the same source file to import both extensible custom attributes and the standard task object attributes. First, design your object model extensions in Oracle Fusion CRM Application Composer and generate the required artifacts to register your extensions and make them available for importing. When complete, the import object is updated with the extensible attributes, which can then be mapped to your source file data.
You can import attachments to your import object by including the file names in your task source file and selecting the files when defining your import activity.
The task import object consists of entities that form the task. Since interface tables are tied to import object entities and the task object consists of many entities, there are multiple interface tables included in importing tasks. You map your source file data to import entity attributes that correspond to the interface table columns. The import activity process populates the interface tables based on the mapping and your source file. If you need the unique IDs of existing application data for your import data, use the Define Data Export Setup and Maintenance task list to export the information.
Note
Spreadsheets containing detailed information about each interface table, including the import attributes, corresponding interface table columns, defaults, and validations, are available from the Oracle Enterprise Repository by searching on a specific interface table name or initiating a search using the FusionApps: Interface Table asset type.
The following table lists the object entities, tables, and resulting application objects:
|
File-Based Import Entities |
Interface Tables |
Destination Tables |
Application Object |
|---|---|---|---|
|
TaskImport |
ZMM_IMP_WF_TASK |
CRM_FUSION_SOAINFRA.WFTASK |
Task |
|
TaskAssigneeImport |
ZMM_IMP_WF_ASSIGNEES |
WF_ASSIGNEES |
Task Assignee |
|
TaskContactImport |
ZMM_IMP_TASK_CONTACTS |
ZMM_ACT_CONTACTS |
Task Contact |
|
NoteImport |
ZMM_IMP_NOTES |
ZMM_NOTES |
Task Note |
You can create new interactions by importing data through interface tables. To populate the interface tables, you provide the data details in a source file and use the file-based import feature. Having a good understanding of the import entities, interface tables, and destination tables will help you prepare your import data.
Consider the following when importing interactions:
File-based import
Import object entities, interface tables, and destination tables
The file-based import process reads the data included in your XML or text file, populates the interface tables, and imports the data into the application destination tables. The File-Based Data Import Setup and Maintenance task list includes the tasks needed to configure the interaction import object, create source file mappings, and schedule the import activities.
Note
If using a text file, one row of data in your source file represents a single interaction. Consequently, if you have a one-to-many scenario for some of the interaction's details, you must repeat each set of data in the source file on the same row. For example, if the interactions in your source file typically include up to two contacts, create a set of data for contact one and an additional set of data for contact two to include on the same row as your interaction. The file-based import process supports up to ten sets of data per entity per row in the text file.
You can use the same source file to import both extensible custom attributes and the standard interaction object attributes. First, design your object model extensions in Oracle Fusion CRM Application Composer and generate the required artifacts to register your extensions and make them available for importing. When complete, the import object is updated with the extensible attributes, which can then be mapped to your source file data.
The interaction import object consists of entities that form the interaction. Since interface tables are tied to import object entities and the interaction object consists of many entities, there are multiple interface tables included in importing interactions. You can map your source file data to the import entity attributes that correspond to the interface table columns. The import activity process populates the interface tables based on the mapping and your source file. If you need the unique IDs of existing application data for your import data, use the Define Data Export Setup and Maintenance task list to export the information.
Note
Spreadsheets containing detailed information about each interface table, including the import attributes, corresponding interface table columns, defaults, and validations, are available from the Oracle Enterprise Repository by searching on a specific interface table name or initiating a search using the FusionApps: Interface Table asset type.
The following table lists the object entities, tables, and resulting application objects:
|
File-Based Import Entities |
Interface Tables |
Destination Tables |
Application Object |
|---|---|---|---|
|
InteractionImport |
ZMM_IMP_INT_INTERACTIONS |
ZMM_INTER_INTERACTIONS |
Interaction |
|
InteractionAssociationImport |
ZMM_IMP_INT_ASSOCIATIONS |
ZMM_INTER_ASSOCIATIONS |
Interaction associations |
|
InteractionParticipantImport |
ZMM_IMP_INT_PARTICIPANTS |
ZMM_INTER_PARTICIPANTS |
Interaction resources and contacts |
You can create new appointments and update existing appointments by importing data through interface tables. To populate the interface table, you provide the data details in a source file and use the file-based import feature. Having a good understanding of the import entities, interface tables, and destination tables will help you prepare your import data.
Consider the following when importing appointments:
File-based import
Import object entities, interface tables, and destination tables
The file-based import process reads the data included in your XML or text file, populates the interface tables, and imports the data into the application destination tables. The File-Based Data Import Setup and Maintenance task list includes the tasks needed to configure the appointment import object, create source file mappings, and schedule the import activities.
Note
If using a text file, one row of data in your source file represents a single appointment. Consequently, if you have a one-to-many scenario for some of the appointment's details, you must repeat each set of data in the source file on the same row. For example, if the appointments in your source file typically include up to two contacts, create a set of data for contact one and an additional set of data for contact two to include on the same row as your appointment. The file-based import process supports up to ten sets of data per entity per row in the text file.
You can import attachments to your import object by including the file names in your appointment source file and selecting the files when defining your import activity.
The appointment import object consists of entities that form the appointment. Since interface tables are tied to import object entities and the appointment object consists of many entities, there are multiple interface tables included in importing appointments. You can map your source file data to the import entity attributes that correspond to the interface table columns. The import activity process populates the interface tables based on the mapping and your source file. If you need the unique IDs of existing application data for your import data, use the Define Data Export Setup and Maintenance task list to export the information.
Note
Spreadsheets containing detailed information about each interface table, including the import attributes, corresponding interface table columns, defaults, and validations, are available from the Oracle Enterprise Repository by searching on a specific interface table name or initiating a search using the FusionApps: Interface Table asset type.
The following lists the appointment object entities, tables, and resulting application objects:
|
File-Based Import Entities |
Interface Tables |
Destination Tables |
Application Object |
|---|---|---|---|
|
AppointmentImport |
ZMM_IMP_ACTIVITIES |
ZMM_ACTIVITIES |
Appointment |
|
ActivityAssigneeImport |
ZMM_IMP_ACT_ASSIGNMENTS |
ZMM_ACT_ASSIGNMENTS |
Appointment participants |
|
ActivityContactImport |
ZMM_IMP_ACT_CONTACTS |
ZMM_ACT_CONTACTS |
Appointment contact |
|
NoteImport |
ZMM_IMP_NOTES |
ZMM_NOTE |
Appointment note |
You can create new promotions by importing data through interface tables. There are two options for populating the interface tables: using the tool of your preference to load the data or an automated pull from a data file. If you plan to provide the data details in a source file, use the file-based import feature. If you will populate the interface tables directly, use scheduled processes to import the data. Having a good understanding of the import entities, interface tables, and destination tables will help you prepare your import data.
Consider the following when importing promotions:
File-based import option
Scheduled process import option
Import object entities, interface tables, and destination tables
The file-based import process reads the data included in your XML or text file, populates the interface tables, and imports the data into the application destination tables. The File-Based Data Import Setup and Maintenance task list includes the tasks needed to configure the promotion import object, create source file mappings, and schedule the import activities.
Note
If using a text file, one row of data in your source file represents a single promotion. Consequently, if you have a one-to-many scenario for some of the promotion's details, you must repeat each set of data in the source file on the same row. For example, if the promotions in your source file typically include up to two coupons, create a set of data for coupon one and an additional set of data for coupon two to include on the same row as your promotion.
Navigate to Scheduled Processes, after you have populated the interface tables, to schedule the import of data from the interface tables to the destination tables.
The following displays the process you can schedule to import promotions and related information:
|
Process Name |
Process Display Name |
|---|---|
|
BulkImportProcess_PROMOTION_LOAD_ALL |
Import Promotions and Associated Coupons |
The promotion import object consists of entities that form the promotion. Since interface tables are tied to import object entities and the promotion object consists of many entities, there are multiple interface tables included in importing promotions. If you are using file-based import, you can map your source file data to import entity attributes that correspond to the interface table columns. The import activity process will populate the interface tables based on the mapping and your source file. If using scheduled processes, populate the tables directly using your preferred tool. If you need the unique IDs of existing application data for your import data, use the Define Data Export Setup and Maintenance task list to export the information.
Note
Spreadsheets containing detailed information about each interface table, including the import attributes, corresponding interface table columns, defaults, and validations, are available from the Oracle Enterprise Repository by searching on a specific interface table name or initiating a search using the FusionApps: Interface Table asset type.
The following table lists the object entities, tables, and resulting application objects:
|
File-Based Import Entities |
Interface Tables |
Destination Tables |
Application Object |
|---|---|---|---|
|
PromotionBulkImport |
MOP_IMP_PROMOTIONS |
MOP_PROMOTIONS_B MOP_PROMOTIONS_TL |
Promotion |
|
PromotionCouponBulkImport |
MOP_IMP_PROMO_COUPONS |
MOP_PROMO_COUPONS |
Promotion Coupon |
You can create new product groups by importing data through interface tables. To populate the interface table, you provide the data details in a source file and use the file-based import feature. Having a good understanding of the import entities, interface tables, and destination tables will help you prepare your import data.
Consider the following when importing product groups:
File-based import
Import object entities, interface tables, and destination tables
The file-based import process reads the data included in your XML or text file, populates the interface tables, and imports the data into the application destination tables. The File-Based Data Import Setup and Maintenance task list includes the tasks needed to configure the product group import object, create source file mappings, and schedule the import activities.
Note
If using a text file, one row of data in your source file represents a single product group. Consequently, if you have a one-to-many scenario for some of the product group's details, you must repeat each set of data in the source file on the same row. For example, if the product groups in your source file typically include two associated products, create a set of data for product one and an additional set of data for product two to include on the same row as your product group.
You can use the same source file to import both extensible custom attributes and the standard product group object attributes. First, design your object model extensions in Oracle Fusion CRM Application Composer and generate the required artifacts to register your extensions and make them available for importing. When complete, the import object is updated with the extensible attributes, which can then be mapped to your source file data.
The product group import object consists of entities that form the product group. Since interface tables are tied to import object entities and the product group object consists of many entities, there are multiple interface tables included in importing product groups. You map your source file data to import entity attributes that correspond to the interface table columns. The import activity process populates the interface tables based on the mapping and your source file. If you need the unique IDs of existing application data for your import data, use the Define Data Export Setup and Maintenance task list to export the information.
Note
Spreadsheets containing detailed information about each interface table, including the import attributes, corresponding interface table columns, defaults, and validations, are available from the Oracle Enterprise Repository by searching on a specific interface table name or initiating a search using the FusionApps: Interface Table asset type.
The following table lists the object entities, tables, and resulting application objects:
|
File-Based Import Entities |
Interface Tables |
Destination Tables |
Application Object |
|---|---|---|---|
|
ProductGroupBulkImport |
QSC_IMP_PROD_GROUPS |
QSC_PROD_GROUPS_B QSC_PROD_GROUPS_TL QSC_PROD_GRP_DETAILS |
Product group |
|
ProductGroupItemBulkImport |
QSC_IMP_PROD_GROUP_ITEMS |
QSC_PROD_GROUP_ITEMS |
Product group products |
|
ProductGroupRelationBulkImport |
QSC_IMP_PROD_GROUP_REL |
QSC_PROD_GRP_REL_B QSC_PROD_GRP_REL_TL |
Related product groups |
You can create new or update existing marketing budgets by importing data through interface tables. To populate the interface table you provide the data details in a source file and use the file-based import feature. Having a good understanding of the import entities, interface tables, and destination tables will help you prepare your import data.
Consider the following when importing marketing budgets:
File-based import
Import object entities, interface tables, and destination tables
The file-based import process reads the data included in your XML or text file, populates the interface tables, and imports the data into the application destination tables. The File-Based Data Import Setup and Maintenance task list includes the tasks needed to configure the marketing budget import object, create source file mappings, and schedule the import activities.
You can use the same source file to import both extensible custom attributes and the standard marketing budget object attributes. First, design your object model extensions in Oracle Fusion CRM Application Composer and generate the required artifacts to register your extensions and make them available for importing. When complete, the import object is updated with the extensible attributes, which can then be mapped to your source file data.
Marketing budget notes are imported independently using a separate source file and import activity. Include the data that will identify the associated budget in the note's source file.
Note
To obtain unique IDs for the marketing budgets you have just imported, you can view the log file of successful records in the budget's import activity by navigating to Setup and Maintenance and selecting the Manage File Import Activities task. When the budget import activity is complete, select the Schedule Status link to access the log file containing the budget IDs.
You can import attachments to your import object by including the file names in your marketing budget source file and selecting the files when defining your import activity.
The marketing budget import object consists of one entity that forms the budget. Since interface tables are tied to import object entities, there is only one interface table for importing budgets. You map your source file data to import entity attributes that correspond to the interface table columns. The import activity process will populate the interface tables based on the mapping and your source file. If you need the unique IDs of existing application data for your import data, use the Define Data Export Setup and Maintenance task list to export the information.
Note
Spreadsheets containing detailed information about each interface table, including the import attributes, corresponding interface table columns, defaults, and validations, are available from the Oracle Enterprise Repository by searching on a specific interface table name or initiating a search using the FusionApps: Interface Table asset type.
The following table lists the object entity, tables, and resulting application object:
|
File-Based Import Entities |
Interface Tables |
Destination Tables |
Application Object |
|---|---|---|---|
|
ImportBudgets1 |
MKT_IMP_BDT_BUDGETS |
MKT_BDT_BUDGETS_B MKT_BDT_BUDGETS_TL |
Marketing Budget |
The following table lists the note object entity, tables, and resulting application object:
|
File-Based Import Entities |
Interface Tables |
Destination Tables |
Application Object |
|---|---|---|---|
|
NoteImport |
ZMM_IMP_NOTES |
ZMM_NOTES |
Marketing budget note |
