iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
When one legacy position code represents multiple records, do not use that code as the only identifier in an Oracle HCM conversion. Profile the source data, define the target position record grain, and maintain a crosswalk from every source record to a distinct Oracle record. For HDL loads, Oracle’s source key—SourceSystemOwner plus SourceSystemId—provides a record identifier separate from the position code.
Why a legacy position code may not identify one Oracle position
Oracle defines a position as a single occurrence of a job in a department, potentially restricted by location. A source code alone may therefore be insufficient if it is reused for different departments, locations, organizational contexts, or periods. Whether a particular legacy system reuses codes is a source-data question; Oracle’s documentation describes the target model, not how often this occurs in legacy systems.
Separate three concepts in the conversion design:
- Source record: the distinct record in the legacy system, interpreted in its source context and, where relevant, effective date.
- Oracle position: the target occurrence of a job in the applicable department and organizational context.
- Position code: a workforce-structure code that may be manually entered or generated. It is not necessarily the durable technical identifier used to connect conversion records.
Oracle HDL supports source keys made from SourceSystemOwner and SourceSystemId. Oracle recommends source keys because user-key values can change; source keys can also identify records referenced by other objects. See Oracle’s Create and Maintain Data with HCM Data Loader.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →How to design the position crosswalk
1. Profile the source codes
Identify duplicate codes, codes reused over time, and values whose meaning depends on the source system, business unit, department, location, or effective date. This is a conversion control, not an Oracle-mandated procedure. Preserve enough source context to distinguish records that share the same displayed code.
2. Confirm the target record grain
Decide what constitutes a distinct Oracle position in the organization being converted. Check the job, department, location restrictions, and effective-dated structure rather than assuming that one old code always equals one target row. Confirm the design with the HCM implementation team and tenant configuration.
3. Assign distinct target identities and preserve the mapping
Create a crosswalk that maps each distinct source record to its Oracle target record. Where HDL source keys are appropriate, populate SourceSystemOwner and a distinct SourceSystemId for each target record. Do not reuse an identifier simply because two records share a legacy position code. Retain the crosswalk for later loads, reconciliation, and references from related objects.
Rank #2
- Unstoppable You Oracle Card: Working with the Unstoppable You Oracle This deck is a devotion to your fire. A love letter to the part of you that dares, dreams, gets knocked down, and rises again—stronger, louder, and more aligned than before. These cards are your inner cheerleader, your motivational spark, your boldest self in mirror form.
- Oracle cards with guide book: Each card delivers a message that’s short enough to stand alone—but within the guidebook, that message unfolds into layered meaning, emotional depth, and grounded action. Expect equal parts inspiration and ignition. This deck is not passive—it asks you to move, to choose, to rise.
- Oracle Cards For Beginners: Unlike traditional tarot, this oracle isn’t about ancient archetypes or fixed systems. It’s a conversation with your most courageous self. Each card delivers a straight-talking, soul-stirring truth to help you cut through the noise of doubt and reconnect with your power. You don’t need to be perfect to work with these cards. You don’t even need to feel ready. You only need to show up. Whether you’re chasing a dream, navigating a transition, rebuilding after a fall, or simply trying to believe again—this deck meets you where you are and helps you take the next step.
- Oracle Deck Specification: Comprising 47 exquisitely designed oracle cards, each measuring 2.74*4.72 inches, The deck is making it a perfect tool for meditation, daily inspiration, or spiritual readings. It can be used in conjunction with tarot cards, other oracle decks or simply on their own.
- Perfect for Gifting: Beautifully packaged, these cards make a thoughtful gift for anyone interested in spirituality, mindfulness, or personal growth. Whether it's Thanksgiving, Christmas, Easter, Independence Day or Halloween, it's the best for your friends.
This is implementation guidance, not a universal mapping architecture prescribed by Oracle. The correct identifiers and mapping grain depend on the source data and the organization’s effective-dated design.
Choose a position-code policy before loading
Decide whether target position codes will be manually assigned or automatically generated. The code policy and the HDL source key solve different problems: one is the position code, while the other identifies the record for data loading and references.
| Decision | Manual position codes | Oracle-generated position codes |
|---|---|---|
| What it controls | The code is supplied as part of the position data. | Oracle assigns the code according to the configured generation approach. |
| HDL consideration | Confirm that each supplied value is valid and appropriate for the target. | Oracle recommends leaving the position code blank in the HDL file to avoid duplicate generated codes. See Guidelines for Loading Positions. |
| Changeover consideration | Existing manually assigned values establish the current range. | Oracle’s common-features guidance recommends setting the initial generated code above existing manual codes when moving from manual to automatic generation. Automatically generated position or job codes cannot be edited after generation; confirm the method and initial sequence before production loading. See Using Common Features for HCM. Verify the guidance against the release deployed in the tenant. |
Do not assume every legacy code can be loaded unchanged as PositionCode, or that the code is a safe sole reference between objects. Oracle’s generated-code recommendation applies when codes are generated; it does not establish a universal rule for every manual-code conversion.
Load prerequisites and positions in dependency order
Oracle’s position-loading guidance says the business unit must exist, and Job and Department are required. Referenced locations and valid grades must also exist. Position and child components need the same effective start date. Check the relevant details in Oracle’s position-loading guidance.
Rank #4
- Load or verify the business unit, jobs, departments, referenced locations, and valid grades required by the position records.
- Prepare HDL position records with the agreed source keys, crosswalk mappings, code policy, and effective dates.
- Load positions and their child components using matching effective start dates.
- Reconcile the loaded records against the source-to-target crosswalk, checking for missing, duplicate, or incorrectly mapped target records.
Account for position synchronization on assignments
If position synchronization is configured, assignment values may inherit from positions. Oracle’s documented HDL/API flow requires synchronization to be enabled before assignments are loaded, Synchronize from Position (Position Override) to be set to Y on the relevant employment terms or assignment, and the Synchronize Person Assignments from Position process to be run. Configuration changes after assignments already exist also require the process to apply changes. See Oracle’s Position Synchronization and How Assignment Values Are Inherited from Position documentation.
For the target tenant, verify which assignment attributes synchronize and the required setup and process sequence for its release. Reconcile assignment results after synchronization; do not assume that loading a position alone updates every existing assignment value.
Quick Recap
Conversion checks before sign-off
- Each distinct source record has an unambiguous crosswalk entry and target identity.
- Reused codes have been examined in their source, organizational, and effective-date contexts.
- The target position grain reflects the organization’s job, department, and location design.
- The manual or automatic position-code policy is confirmed before the load.
- Required business units, jobs, departments, locations, and grades exist, and effective start dates align for positions and child components.
- Any configured position synchronization has been applied and its assignment effects reconciled.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
