1. HCM Data Loading Business Objects
  2. Guidelines for Loading Locations

Guidelines for Loading Locations

A location is the physical address of a place where you conduct business or that's of interest to your business. The Location object records the address and other details, such as the location name, description, phones, and billing and shipping information.

This topic describes aspects of the Location object that you must understand to load locations successfully.

Changing Logical Start and End Dates for Locations

You can't change either the first effective start date or last effective end date for an existing location. Create location records with effective start dates on or before the start dates of other objects, such as Organization, that refer to your locations.

Loading Translated Location Names

Supply location names and descriptions in the language of the user who's loading them. You supply a LocationTranslation.dat file to translate location names and descriptions into other enabled languages once the locations exist. This example translates the name and description of an existing location. It identifies the location by its source key.

METADATA|LocationTranslation|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Language|LocationName|Description
MERGE|LocationTranslation|VISION|LOC_RD_UK|1951/01/01|FR|Vision Corporation Recherche et Developpement|Centre de recherche et de developpement

Deleting Locations

You can't delete Location objects using HCM Data Loader. However, you can make locations inactive. This example Location.dat file makes a location inactive as of 01/01/15. The location is identified by its source key.

METADATA|Location|SourceSystemOwner|SourceSystemId|EffectiveStartDate|ActiveStatus
MERGE|Location|VISION|LOC_UK_100|2015/01/01|I

Loading Legal Employer- Location Association

You can associate legal employers with a location using the Legal Employers Operating At This Location extensible flexfield (EFF) context. First, you need to add this context and then associate the legal employers with the location. This example loads the EFF for a location.

METADATA|Location|FLEX:PER_LOCATIONS_DF|LocationId|SetId|SetCode|LocationImageURL|ActiveStatus|MainphoneAreaCode|MainphoneCountryCode|MainphoneExtension|MainphoneSubscriberNumber|FaxAreaCode|FaxCountryCode|FaxExtension|FaxSubscriberNumber|OtherphoneAreaCode|OtherphoneCountryCode|OtherphoneExtension|OtherphoneSubscriberNumber|OfficialLanguageCode|EmailAddress|ShipToSiteFlag|ShipToLocationSetCode|ShipToLocationCode|ShipToLocationId|ReceivingSiteFlag|BillToSiteFlag|OfficeSiteFlag|DesignatedReceiverId|DesignatedPersonNumber|InventoryOrganizationId|InventoryOrganizationName|GeoHierarchyNodeId|GeoHierarchyNodeCode|LocationCode|LocationName|Description|AddressLine1|AddressLine2|AddressLine3|AddressLine4|Building|Country|FloorNumber|LongPostalCode|PostalCode|Region1|Region2|Region3|TimezoneCode|TownOrCity|AddlAddressAttribute1|AddlAddressAttribute2|AddlAddressAttribute3|AddlAddressAttribute4|AddlAddressAttribute5|EffectiveStartDate|EffectiveEndDate|CategoryCode|ActionReasonCode|SourceSystemOwner|SourceSystemId|GUID|SourceRefTableName=(source-table-name)|SourceRef001=(source-column-001)|SourceRef002=(source-column-002)|SourceRef003=(source-column-003)|SourceRef004=(source-column-004)|SourceRef005=(source-column-005)|SourceRef006=(source-column-006)|SourceRef007=(source-column-007)|SourceRef008=(source-column-008)|SourceRef009=(source-column-009)|SourceRef010=(source-column-010)|locglobal(PER_LOCATIONS_DF=Global Data Elements)|locationcntx(PER_LOCATIONS_DF=location_extra info)
METADATA|LocationOtherAddress|LocAddressUsageId|EffectiveStartDate|EffectiveEndDate|AddressUsageType|LocationId(SourceSystemId)|LocationSetCode|LocationCode|AddressLine1|AddressLine2|AddressLine3|AddressLine4|Building|TownOrCity|FloorNumber|Country|PostalCode|LongPostalCode|Region1|Region2|Region3|TimezoneCode|SourceSystemOwner|SourceSystemId|GUID|SourceRefTableName=(source-table-name)|SourceRef001=(source-column-001)|SourceRef002=(source-column-002)|SourceRef003=(source-column-003)|SourceRef004=(source-column-004)|SourceRef005=(source-column-005)|SourceRef006=(source-column-006)|SourceRef007=(source-column-007)|SourceRef008=(source-column-008)|SourceRef009=(source-column-009)|SourceRef010=(source-column-010)METADATA|LocationLegislative|FLEX:PER_LOCATION_LEG_EFF|EFF_CATEGORY_CODE|LocationLegId|EffectiveStartDate|EffectiveEndDate|LocationId(SourceSystemId)|ActionOccurrenceId|LegislationCode|LleInformationCategory|SequenceNumber|SourceSystemOwner|SourceSystemId|GUID|SetId|SetCode|LocationCode|locationsegment1(PER_LOCATION_LEG_EFF=Location_Context)|locationsegment2(PER_LOCATION_LEG_EFF=Location_Context)
METADATA|LocationExtraInfo|FLEX:PER_LOCATION_INFORMATION_EFF|EFF_CATEGORY_CODE|LocationExtraInfoId|EffectiveStartDate|EffectiveEndDate|LocationId(SourceSystemId)|InformationType|ActionOccurrenceId|LeiInformationCategory|SequenceNumber|LegislationCode|SourceSystemOwner|SourceSystemId|GUID|SetId|SetCode|LocationCode|testseg(PER_LOCATION_INFORMATION_EFF=Test_HDL)

This example associates legal employers for a specific location context.

MERGE|Location||||COMMON||A||||||||||||||||||||||||||||Location_{{xs}}_021|Location_{{xs}}_021|Description|ABC|AddressLine2|AddressLine3|AddressLine4|Building|US|FloorNumber||10001|New York|NY|||Manhattan||||||2000/01/01|2004/12/31|||HCMQA-001|Location_{{xs}}_021||||||||||||||
MERGE|Location||||COMMON||I||||||||||||||||||||||||||||Location_{{xs}}_021|Location_{{xs}}_021|Description|DEF|AddressLine2|AddressLine3|AddressLine4|Building|US|FloorNumber||10001|New York|NY|||Manhattan||||||2005/01/01|2009/12/31|||HCMQA-001|Location_{{xs}}_021||||||||||||||
MERGE|Location||||COMMON||A||||||||||||||||||||||||||||Location_{{xs}}_021|Location_{{xs}}_021|Description|DEF|AddressLine2|AddressLine3|AddressLine4|Building|US|FloorNumber||10001|New York|NY|||Manhattan||||||2010/01/01|4712/12/31|||HCMQA-001|Location_{{xs}}_021||||||||||||||
MERGE|LocationOtherAddress||2000/01/01|2004/12/31|MAILING|Location_{{xs}}_021|||AddressLine1|AddressLine2|AddressLine3|AddressLine4|Building|Atlantic|1st floor|US|16111||Crawford|PA|Region3||HCMQA-001|LocationAddr_{{xs}}_021||||||||||||
MERGE|LocationOtherAddress||2005/01/01|2009/12/31|MAILING|Location_{{xs}}_021|||AddressLine1Updated|AddressLine2 Updated|Updated AddressLine3|AddressLine4 Updated|Building|Atlantic|1st floor|US|16111||Crawford|PA|Region3||HCMQA-001|LocationAddr_{{xs}}_021||||||||||||
MERGE|LocationOtherAddress||2010/01/01|4712/12/31|MAILING|Location_{{xs}}_021|||AddressLine1|AddressLine2|AddressLine3|AddressLine4|Building|Atlantic|1st floor|US|16111||Crawford|PA|Region3||HCMQA-001|LocationAddr_{{xs}}_021||||||||||||
MERGE|LocationLegislative|Location_Context|HCM_LOC_LEG||2000/01/01|2004/12/31|Location_{{xs}}_021||US|||HCMQA-001|LocationLeg_{{xs}}_021|||COMMON|Location_{{xs}}_021|abc|123
MERGE|LocationLegislative|Location_Context|HCM_LOC_LEG||2005/01/01|2009/12/31|Location_{{xs}}_021||US|||HCMQA-001|LocationLeg_{{xs}}_021|||COMMON|Location_{{xs}}_021|def|456
MERGE|LocationLegislative|Location_Context|HCM_LOC_LEG||2010/01/01|4712/12/31|Location_{{xs}}_021||US|||HCMQA-001|LocationLeg_{{xs}}_021|||COMMON|Location_{{xs}}_021|ghi|789
MERGE|LocationExtraInfo|Test_HDL|HCM_LOC||2000/01/01|2004/12/31|Location_{{xs}}_021|Test_HDL||Test_HDL||US|HCMQA-001|LocationEIT_{{xs}}_021|||COMMON||abc
MERGE|LocationExtraInfo|Test_HDL|HCM_LOC||2005/01/01|2009/12/31|Location_{{xs}}_021|Test_HDL||Test_HDL||US|HCMQA-001|LocationEIT_{{xs}}_021|||COMMON||
MERGE|LocationExtraInfo|Test_HDL|HCM_LOC||2010/01/01|4712/12/31|Location_{{xs}}_021|Test_HDL||Test_HDL||US|HCMQA-001|LocationEIT_{{xs}}_021|||COMMON||xyz

Prevent Inflight Location Updates

You can prevent inflight location updates when it's updated using the update and correct flows, or when a date effective location record is deleted, when approvals are pending. You need to create and set the HR_DISABLE_PENDING_APPROVALS_CHECK_IN _HCM_DATA_LOADER profile option to No, if it's not already created to prevent inflight location updates.

Related Topics