Assigned Payroll: Exceptions and Adaptations
There are situations when the Assigned Payroll object doesn't conform according to the general principles of Autocomplete Rules.
In such situations, you can adapt the rules by adding a unique additional condition or coding style, in some cases.
Exceptions
This table lists rules that can't be currently implemented for the Assigned Payroll business object.
Rule |
Rule Type |
Actions Impacted |
Sections Impacted |
Fields Impacted |
Comments |
---|---|---|---|---|---|
Default on entry into region, Default on tab-out and validation on tab-out not supported |
Object Defaulting, Field Modification, Field Validation |
|
Payroll section |
Payroll |
NA |
Adaptations
This table lists rules where you can vary the rule logic to achieve the result.
Rule |
Rule Type |
Actions Impacted |
Sections Impacted |
Fields Impacted |
Comments |
---|---|---|---|---|---|
Identify the required flow that you want to validate payroll with. |
Business Object Validation |
All |
Payroll section |
Payroll |
For example, in the new hire flow, you can validate the payroll based on HR attributes, such as job. |
Identify the required flow that you want to default payroll with. You can always default payroll based on HR attribute. |
Business Object Defaulting |
All |
Payroll section |
Payroll |
For example, in the new hire flow, you can default the payroll based on HR attributes, such as job. For more information on Global Transfer, see https://blogs.oracle.com/fusionhcmcoe/post/default-validate-payroll-autocomplete-rule. |