Guidelines for Loading Person Names

The Person Name component of the Worker object holds both common and legislation-specific components of a person's name. This topic describes some decisions you must make when loading person names using HCM Data Loader.

Local and Global Names

Person names are always created with both a global and a local version. The name is created based on the name type that you supply, and the other name is derived automatically. For example, if you set the NameType attribute to GLOBAL, then the local name is derived. Alternatively, if you set NameType to FR, for example, then the global name is derived. Typically, only the global name is required and the application copies it to the local name automatically. However, if the person's name must be held in two different character sets, then supply the local name.

A core name field may not be available for a legislation. For example, Last Name Kanji isn't available for the Japanese legislation. In this case, the data is stored in one of the NameInformation1 through NameInformation14 attributes. NameInformation1 through NameInformation14 are reserved for this purpose. The person name styles table stores the mapping of the name style to the name attributes. The name style is the same for both the global and local-name records.

Name Attributes for Specific Legislations

To supply a name attribute for a specific legislation, use one of the NameInformation15 through NameInformation30 attributes. For example, to define the name attribute Doing Business As for the United States, you could use the NameInformation15 attribute. You don't have to define flexfields for this requirement.

Supplying Date-Effective History

If you're loading date-effective history for a person name, then you must use source keys to identify the component. Otherwise, you can use the PersonNumber, EffectiveStartDate, and NameType user-key components.