| 1 |
Effective Date |
To default the effective date in the When and Why section of
employment flows. |
Object Defaulting |
When and Why |
- The defaulting by the rule takes precedence over the default
value that's set by the ORA_PER_EMPL_DEFAULT_EFFECTIVE_DATE
profile option.
- The effective date will be defaulted only the first time
when the user visits the When and Why section of these
employment update flows: Promote, Local and Global Transfer,
Transfer, Change Assignment, Change Location, and Change
Manager.
- If the ORA_PER_EMPL_DEFAULT_EFFECTIVE_DATE profile option
value is set to Y and no autocomplete rule is defined, the
effective date will be defaulted to the current system
date.
- The ORA_PER_EMP_RETAIN_CHANGES profile option value is set
to N and the autocomplete rule is defined to default the
effective date. In this case, if the user manually changes
the effective date in the employment flow, the new date
value will be retained.
- You can’t default the effective date by using an
autocomplete rule based on a modified field in the
employment transaction page. This is because each time the
transaction date is modified in the page or the
ORA_PER_EMP_RETAIN_CHANGES profile option value is enabled
(set to Y), the transaction is rolled back and the changes
are re-populated.
- The effective date won’t be defaulted when you resume an
employment transaction after saving it, or when the
employment transaction is edited by an approver.
- The defaulting by the autocomplete rule isn’t supported in
HCM Data Loader and REST API.
- You can’t default the effective date for the Create Work
Relationship and Convert Pending Worker flows.
|