This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 17 JUNE 2022 | Created initial document. |
HAVE AN IDEA?
We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.
NOTE ABOUT DOCUMENTATION AVAILABILITY
Some of the documentation referenced in this article may not be available until after general availability of the release update on July 1. Check back after general availability for complete information.
DISCLAIMER
The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
Control Calculation Order for Transactions with Same Event Date |
||||||
Control Calculation Order for Transactions with Same Event Date
Control the calculation order for transactions with the same event date. Choose any numeric attribute or the transaction number on the transaction to decide the order the transactions get calculated in when they have the same event date. This is applicable only to transactions that get calculated individually.
Choose this parameter using the Order Transactions with Same Date By field under Earning Calculation Parameters in the Manage Parameters page under Setup and Maintenance.
Example: If you're calculating transactions individually and you have these three transactions with the same event date:
| Transaction Number | Event Date | Calculation_order (ATTRIBUTE_NUMBER5) |
|---|---|---|
| ABC-1002 | 1/5/2022 | 1 |
| ABC-1001 | 1/5/2022 | 2 |
| ABC-1000 | 1/5/2022 | 3 |
- If you select Transaction Number as the field to order transactions by for calculation, then the order in which the transactions get calculated is: (i) ABC-1000 (ii) ABC-1001 (iii) ABC-1002.
- However, if you select the numeric attribute, Calculation Order (in this example ATTRIBUTE_NUMBER5), as the field to order transactions by for calculation, then the order in which transactions get calculated is: (i) ABC-1002 (ii) ABC-1001 (iii) ABC-1000.
This feature gives you more control over how calculation processes transactions when they have the same date.
Steps to Enable
- Navigate to Setup and Maintenance.
- Go to the Manage Parameters task for the specific BU.
- Choose a value in the Order Transactions with Same Date By field under Earning Calculation Parameters. The default value is blank.
- You may get a warning about certain formulas being generated. Click OK.
- Click Save.
- Navigate to Scheduled Processes to check whether the formula regeneration process is complete before you run calculations again.
Tips And Considerations
This parameter is only applicable in scenarios where incentive calculations are done separately for each individual transaction and not when transactions are grouped by an interval and then calculated. So only choose a value in this parameter if:
- You're calculating and paying transactions individually;
- And you expect multiple transactions with the same date;
- And you want to control which order those transactions with the same date are calculated in.
Key Resources
See this content:
- "Configuration for a Business Unit" chapter in the Implementing Incentive Compensation guide
- "Calculation Processing" chapter in the Using Incentive Compensation guide.
Role Information
- Incentive Compensation Administrator
- Incentive Compensation Analyst
- Incentive Compensation Manager
Use Expanded Participant Detail Descriptive Flexfields
Store more participant detail information with additional descriptive flexfields. The participant detail object has been expanded to include an additional 20 character attributes, 20 number attributes, and 10 date attributes.
This feature lets you:
- Store more participant information
- Access additional descriptive flexfields:
- 20 Character Attributes
- 20 Number Attributes
- 10 Date Attributes
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See the "Tables and Columns" chapter in the Implementing Incentive Compensation guide.
Role Information
- Compensation Administrator
- Compensation Manager
- Compensation Analyst
Use Efficient Calculations for Improved Performance
Use faster calculations that selectively recalculate only specific measures and components. Depending on the formula of the performance measures, the plan components, and any changes in credits, the calculation engine makes an intelligent decision whether to recalculate a performance measure and plan component. This improves performance by only processing the required data changes.
This feature gives you efficient and faster calculations.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See the "Calculation Processing" chapter in the Using Incentive Compensation guide.
Role Information
- Incentive Compensation Analyst
- Incentive Compensation Manager