Manage Geographies

Manage Geographies:
This example illustrates how to prepare a set of customer records for file-based import.
1. Scenario
As a part of implementing Oracle Fusion Applications, you need to migrate customer

records from a legacy system into the Oracle Fusion database.
2. Existing Customer Data
The customer data in a legacy system comprises the following:
 Basic customer information, such as name, classification, and party usage

 Address
 Contact information, such as Web site URL, e-mail, and phone.
A legacy system lets you export the customer records to a CSV file.
3. Analysis
Analyze whether the data in the CSV file is compatible with the Oracle Fusion Customer
Data Model to avoid importing errors. You can easily find information on the Oracle
Fusion Customer Data Model from the Oracle Enterprise Repository (OER) for Oracle
Fusion Applications.
The OER contains detailed information on Oracle Fusion database tables used to import
and store different types of customer data objects. The database tables used to import
customer data are called source or interface tables. Imported data is stored in target or
destination tables.
The following interface tables are typically used to import customer data:
Interface Table Description
HZ_IMP_PARTIES_T Used to import basic customer information such as name, classification, and party
usage.
HZ_IMP_RELSHIPS_T Used to import customer relationship information.
HZ_IMP_LOCATIONS_T Used to import location information.
HZ_IMP_PARTYSITES_T Used to import site information.
HZ_IMP_PARTYSITEUSES_T Used to import site use information.
HZ_IMP_CONTACTPTS_T Used to import contact point information.
HZ_IMP_CONTACTS_T Used to import contacts and related information.
You can search for each of these interface tables used in Files-based import of
customer data on the OER. The OER contains the following information for each
interface table:
 Description of the interface table that list the target tables populated by the
interface table.
 Interface table column or attribute name and description and its data type,
length, and precision.
 Corresponding File-based import parent object name, entity object name, and
attribute display name.
 Validations performed before saving the data into the target or destination
tables.
While some of this information is stored directly in the OER interface, the rest is
available from attached spreadsheets.
Skim through the OER information, especially the File-based import parent object name, entity
object name, and attribute display name for each interface table. This will help you identify the
interface tables that are applicable for the customer data that you want to import. For example, to
import basic customer address and contact information you need to use only a few interface
tables:
Interface Table Columns (Attributes) Used in this Scenario
HZ_IMP_PARTIES_T Organization Name, PartyOrigSystem, PartyOrigSystemReference, and

PartyType
HZ_IMP_LOCATIONS_T Address1, City, Country
HZ_IMP_CONTACTPTS_T Email Address and Phone Number
Use the OER information about interface tables applicable to your import scenario to
create or verify and validate your CSV data file. For example, you can use the
information on validations performed before saving the data into the target or
destination tables, to verify if the data in the CSV file passes those validations. In case
the data does not pass the validation checks, you can modify the data to ensure that it
will pass those checks.
You must also ensure that you have the correct original system or source system
(PartyOrigSystem) identifier and original system reference (PartyOrigSystemReference)
information in the CSV file for the customers you want to import. If you do not provide
any original system and original system reference information in the file, the import
process assigns default values for PartyOrigSystem and PartyOrigSystemReference in
those use cases.
However, the default value mechanism works only for very simple one-off import
scenarios. In complex import scenarios that involve multiple import jobs, say one each
for importing customer, contact, and contact address, the PartyOrigSystem and
PartyOrigSystemReference information pieces together the data imported using
different jobs into complete customer records. The PartyOrigSystem and
PartyOrigSystemReference information is also required for updating existing customer
records. For example, to import contact address for an existing customer, you need to
provide PartyOrigSystem and PartyOrigSystemReference information for the contact,
the customer, and for the relationship between the contact and the customer. If you
miss the PartyOrigSystem and PartyOrigSystemReference information for the
relationship, File-based import will create a new relationship for the set of contact and
customer. However, in the absence of the PartyOrigSystem and
PartyOrigSystemReference information for the contact, the import process will fail
because it won't know with whom to attach the address.
In this example scenario, we do not have the exact original system or source system
identifier value. In such a case, we can treat the comma separated file as the original
system or source system and so the value of the attribute PartyOrigSystem would be
CSV.
Importing customer data using file-based import requires you to map the columns of
the CSV files to Oracle Fusion database table columns using the mapping interface.
While sometimes you may be able to reuse a predefined import mapping, at other times
you may have to create custom mappings. Sometimes it may not be possible to map
the data without reorganizing the CSV files columns. You can use the interface table
column and corresponding file-based import attribute information to create import
mapping as well as to verify if the columns of the CSV files can be mapped to Oracle
Fusion database table columns using the mapping interface. If complete mapping is not
possible, you may decide to add new columns, or merge, or delete some existing
columns.
4. Data File and Import Mapping for File-Based Import
After analyzing and modifying the existing basic customer address and contact information,
organize it into a CSV file similar to the one shown here.
Organizati PartyOrigSyste PartyOrigSystemRefere Party Type Addres City Countr Email Phone
on Name m nce s y
Customer1 CSV ORG00001 ORGANIZATI Addres Redwoo USA [email protected] +1234567

ON s d m 8
Shores
Customer2 CSV ORG00002 ORGANIZATI Addres Redwoo USA [email protected] +2134567

ON s d m 8
Shores
To import the CSV file using a file-based import activity, you also need to create an import
mapping similar to the one shown here.
Column Header Object Attribute
Organization Name OrganizationProfile OrganizationName
PartyOrigSystem OrganizationProfile PartyOrigSystem
PartyOrigSystemReference OrganizationProfile PartyOrigSystemReference
Party Type OrganizationProfile PartyType
Address ContactPrimaryAddress Address1
City ContactPrimaryAddress City
Country ContactPrimaryAddress Country
Email ContactEmail EmailAddress
Phone ContactPrimaryPhone PhoneNumber

Manage Geographies

Uploaded by

Copyright:

Available Formats

Manage Geographies

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manage Geographies

Uploaded by

Copyright:

Available Formats

Manage Geographies:

As a part of implementing Oracle Fusion Applications, you need to migrate customer

2. Existing Customer Data

The customer data in a legacy system comprises the following:

 Basic customer information, such as name, classification, and party usage

Interface Table Description

HZ_IMP_RELSHIPS_T Used to import customer relationship information.

HZ_IMP_LOCATIONS_T Used to import location information.

HZ_IMP_PARTYSITES_T Used to import site information.

HZ_IMP_PARTYSITEUSES_T Used to import site use information.

HZ_IMP_CONTACTPTS_T Used to import contact point information.

HZ_IMP_CONTACTS_T Used to import contacts and related information.

Interface Table Columns (Attributes) Used in this Scenario

HZ_IMP_PARTIES_T Organization Name, PartyOrigSystem, PartyOrigSystemReference, and

HZ_IMP_LOCATIONS_T Address1, City, Country

HZ_IMP_CONTACTPTS_T Email Address and Phone Number

4. Data File and Import Mapping for File-Based Import

Customer1 CSV ORG00001 ORGANIZATI Addres Redwoo USA [email protected] +1234567

Customer2 CSV ORG00002 ORGANIZATI Addres Redwoo USA [email protected] +2134567

Column Header Object Attribute

Organization Name OrganizationProfile OrganizationName

PartyOrigSystem OrganizationProfile PartyOrigSystem

PartyOrigSystemReference OrganizationProfile PartyOrigSystemReference

Party Type OrganizationProfile PartyType

Address ContactPrimaryAddress Address1

City ContactPrimaryAddress City

Country ContactPrimaryAddress Country

Email ContactEmail EmailAddress

Phone ContactPrimaryPhone PhoneNumber

You might also like