Considerations for Flexfield Mapping in Position Synchronization
You map position descriptive flexfields to assignment descriptive flexfields using the Manage Assignment Flexfield Mapping task in Oracle Fusion Functional Setup Manager.
Use this mapping to automatically populate values for those assignment flexfields mapped to the position flexfields, when position synchronization is enabled. This topic describes what to consider when you're mapping flexfields.
Enterprise or Legal Entity Levels
Before you map flexfields, you must decide whether you want the mapping to be available for the enterprise or for specific legal entities only. You can reuse a mapping across different legal entities. Settings at the legal employer level takes precedence over enterprise settings, if both are specified.
Context Specific or Global
You must decide whether to map context specific or global flexfield segments because you can't map a context specific flexfield segment to a global flexfield segment. You can't map two or more segments of different contexts or multiple position segments to the same assignment segment.
When you change the position value in an assignment, all synchronized global segments inherit the value from the new position. You can manually update those segments that have a blank value in the position.
When you change the position value in an assignment, all context specific segments inherit the value from the new position. If the new position has similar values to the old position and additional contexts defined, the assignments retain the same values and inherit the additional values from the new position.
Selecting and removing a position in an assignment makes the context and segments editable but the current values aren't removed if they're synchronized from the position.
Numeric or Character
You can map flexfields of the same type (for example, numeric-to-numeric or character-to-character only), same precision, and the same value set (same value set ID).