This topic describes how to get you started with importing additional party names. It includes the following information:
• An example of how to identify and associate records • The minimum data required and the prerequisite tasks
• How to use Oracle Enterprise Repository assets to evaluate optional attributes • Additional tips
With an additional party name, you can capture other names for an account, contact, household, or legal entity. For example, a person may have a maiden name, and an organization may also be known by a brand name. You can import new additional
names or update existing additional name records, using the File-Based Data Import feature. The following table lists the file- based import objects and target objects. You can import additional names, using these file-based objects.
Import Object Party Type Target Object
Contact
Person AdditionalName
Account
Organization AdditionalName
Contact
Person (a contact for an account) AdditionalName Household
Group AdditionalName
Legal Entity
Organization AdditionalName
Legal Entity
Person (a contact for a legal entity) ContactAdditionalName
Identifying and Associating Records with Each Other
To add additional names to a party or to update existing additional party name assignments using file-based import, your source file must contain information about the organization, person, or household party to which the additional name is being assigned. You map your source file data to the organization, person, or group profile target object and to the additional party name target object.
If you're creating the party and the additional party name assignment in the same import activity, then group the party and additional party name data together in your source file. The import process can import the party, and then identify the party record so that it can import the associated additional party name.
To add an additional party name to an existing party, or to update an existing additional party name record, your source file must include values that enable the import process to identify the existing records. These values will be either source system and source system reference value combination, Oracle Sales Cloud internal ID, or PUIDs, such as business keys or external IDs.
If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file. The file-based data import process stores a cross-reference between the source system information and Oracle Sales Cloud internal ID. The import process uses the combination of source system and source system reference value to identify the existing record.
Minimum Data Required and the Prerequisite Setup Tasks
The minimum data that is required to import additional name information depends on the following:
• The purpose of the import. The data requirements are different when you're creating both the party and the
additional party name in the same import batch, adding new additional names to an existing party, or updating an additional party name record.
• Organization and group names compared with person names. A variety of components that make up a person's
• Identifying and associating records. In some cases, you can choose which attributes you want to provide to the
import process when identifying and associating records.
The following table lists the attributes (minimum data) that are required or conditionally required in your import file to create or update an additional party name record. You can optionally include attributes that are available for import in your import file but that aren't listed in the table. For each attribute, the prerequisite setup task before importing that attribute is listed.
Attribute Description Prerequisite
Setup Task Creating Partyand Additional Party Name Records in the Same Batch
Creating
Additional Party Name Record for an Existing Party
PartyId
The Oracle SalesCloud internal ID for the party (account, contact, household, or legal entity) to which the additional party name belongs.
Identify the party ID value by exporting the Party object using the Setup and Maintenance, Manage Bulk Data Export, Schedule Export Processes task. The attribute is neither required nor conditionally required. Conditionally required. Provide reference information to identify the existing party. The reference information can be: • PartyId (Oracle Sales Cloud internal ID). • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile. PartyOrigSystem
The coderepresenting the source system for the party (account, contact, household, or legal entity) to which the additional party name belongs.
Identify the source system code that was used when you imported the party in a prior batch, or identify the source system code that you'll use when importing the party in the same batch
Conditionally required. If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same
Conditionally required. Provide reference information to identify the existing party. The reference information can be: • PartyId (Oracle
Attribute Description Prerequisite
Setup Task Creating Partyand Additional Party Name Records in the Same Batch
Creating
Additional Party Name Record for an Existing Party
as this additional party name.
system, provide the original source system and source system reference values. Sales Cloud internal ID). • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile. PartyOrigSystem Reference The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the additional party name belongs.
Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference that you'll use when importing the party in the same batch as this additional party name. Conditionally required. If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values. Conditionally required. Provide reference information to identify the existing party. The reference information can be: • PartyId (Oracle Sales Cloud internal ID). • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.
The following table lists the attributes (minimum data) that are required or conditionally required in your import file to create or update an additional party name record. You can optionally include attributes that are available for import in your import file but that aren't listed in the table. For each attribute, the prerequisite setup task before importing that attribute is listed
Attribute Description Prerequisite
Setup Task Creating Partyand Additional Party Name Records in the Same Batch
Creating
Additional Party Name Record for an Existing Party AdditionalName OrigSystem The code representing the source system for the additional name.
When you predefine your source system code in the Setup and Maintenance, Manage Trading Community Source Systems task, select the Enabled for Trading Community Members check box. Conditionally required. If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values. Conditionally required. If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values.
AdditionalName
The referencenumber or text representing the source system unique ID for the additional name.
Identify or
generate reference values for each additional party name record. The reference value must be unique for all additional party names for the source system. Conditionally required. If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values. Conditionally required. If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values.
ObjectKey
The Oracle SalesCloud internal ID for the additional name. Identify the additional party name ID value by exporting the Additional Party Name object, using the Setup and Maintenance, The attribute is neither required nor conditionally required. The attribute is neither required nor conditionally required.
Attribute Description Prerequisite
Setup Task Creating Partyand Additional Party Name Records in the Same Batch
Creating
Additional Party Name Record for an Existing Party
Manage Bulk Data Export, Schedule Export Processes task.
NameType
The name typeto categorize the name.
Review or define the name types for each party type (person, organization, or household), using the Setup and Maintenance, Manage Additional Name Types task.
Required
Required
Name
The additionalname value for an organization or group. No prerequisite tasks Required Required
The following figure depicts a sample attribute mapping to import an additional name for an existing party. In this scenario, we have used the OrigSystem and OrigSystemReference values to identify the party.
Mapping of Source and Target Objects
Using Oracle Enterprise Repository Assets to Evaluate Optional Attributes
Information about all available attributes is included in a reference file located in Oracle Enterprise Repository. Review the reference file to explore other additional party name attributes that are available to import and the possible prerequisite tasks for those attributes.
This reference file includes the following information:
• All additional name attributes available for importing.
• The attribute descriptions. If the attribute is exposed in the UI, then the corresponding UI display name is included
with the description.
• The data type, length, and validation logic. The validation information includes the task or work area where you can
view or define valid values before importing data.
• Default values, if these values aren't provided in your source file.
To access the reference file for additional party names.
1. Using your browser, enter http://fusionappsoer.oracle.com. Sign in as a user or a guest to Oracle Enterprise
Repository.
2. Enter any of the following search criteria, then click Search.
Note: You can further refine any of the following criteria by choosing File Based Data Import from the Type list or a release number from the Version list
◦
If you know the name of the specific spreadsheet reference file, then enter a piece of the beginning of its file name, such as HZ_IMP_ADDTNLPARTYNAMES to find the HZ_IMP_ADDTNLPARTYNAMES _T_Reference.xls reference file.◦
If you know an object to which the spreadsheet applies, then enter the name of the object, such as Contact.3. The results include a set of assets. The assets that apply to file-based import are typically titled <Object name>
Import, such as the Contact Import. Within the asset, click the link to the reference file in the Details tab. The file opens in Excel or in another application of your choice.
Note: The results of a search on the beginning of the reference file name might also include the interface table, such as the HZ_IMP_ADDTNLPARTYNAMES _T This asset isn't a reference file. It's a description of each row in the interface table, and doesn't provide the same guidance for importing data as does a reference file.
Additional Tips
Tip: You can explore related topics by entering the following keywords in Oracle Sales Cloud Help Application.
• Importing additional party names • Importing accounts
• Importing contacts • Importing households
Tip: If your data isn't from a source system, then you can emulate a system by defining a source system and manually generating reference values for your data. For example, if you periodically gather information at sales events or through sales calls, then you might define a source system, using a code of SALES_ACTIVITY. The format of your reference numbers might concatenate the date, salesperson name, and sequence number, such as 01_Jan_2014_Jackson_01.
Tip: The Name Type is defined for particular party types. For example, if you're importing an organization profile, ensure that the name type definition allows assignment to the Organization party type.