What is the correct order for implementing these items?

You are implementing Oracle Fusion HCM for a customer. What is the correct order for
implementing these items?

You are implementing Oracle Fusion HCM for a customer. What is the correct order for
implementing these items?

A.
Action, Action Type, Action Reason

B.
Action, Action Reason, Action Type

C.
Action Type, Action, Action Reason

D.
Action Type, Action Reason, Action

Explanation:

Note:
* (not A, not B): Action types are predefined and can contain one or more actions. You may associate
your actions with the predefined action types but not create your own action types.
* Action Reason
You can optionally associate reasons with actions, for example, a generic action of termination could
have reasons such as voluntary retirement or involuntary layoff. The primary reason for doing this is
for analysis and reporting purposes. You can view the action and reason details in the Employee
Termination Report. Line managers can view predictions about who is likely to leave voluntarily,
which are based on existing and historical terminations data. The process that generates the
predictions uses the action and reason data to identify whether a termination is voluntary or
involuntary. When managers allocate compensation to their workers, they can select from a list of
action reasons that help identify the type of or reason for the compensation allocation.
Oracle Fusion Applications Coexistence for HCM Implementation Guide, Action Reason



Leave a Reply 0

Your email address will not be published. Required fields are marked *