Overview of When and Why

The When and Why business object contains action date, action name, and action reason information based on the PER_ACTION_OCCURRENCES table.

This object is typically used in these cases:

• Validate global transfers and promotions that occur on any date other than the 1st or 16th of a future month.

• Restrict promotions or transfers to be effective on any date other than the start of a future payroll cycle.

• Default pay period start date as the effective date.

The When and Why business object impacts these responsive flows:

• Add Assignment

• Add Contingent Worker

• Add Nonworker

• Add Pending Worker

• Additional Assignment Info

• Cancel Work Relationship

• Change Assignment

• Change Location

• Change Manager

• Change Salary

• Change Working Hours

• Create Job Offer

• Create Work Relationship

• Edit Job Offer

• Edit Work Relationship

• Employment Contracts

• Employment Information

• Hire an Employee

• Local and Global Transfer

• Manage Eligible Jobs

• Manage Seniority Dates

• Promote

• Salary History

• Transfer

The sections within the responsive flows, that use the When and Why business object (Entry, Tab-out, Exit) may be named differently. The naming convention is based on the action, such as Assignment Details, Employment Details, Offer Details, Location, Manager, Working Hours, Contract Information, Transfer, Promote, and so on.

For more information about the When and Why attributes, refer to the Tables and Views for HCM guide on the Oracle Help Center.