This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Module | Feature | Notes |
---|---|---|---|
03 MAR 2023 | 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.
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 |
|
||
Automate the migration of plans from source to target environments by leveraging the ESS processes to export the plans from the source environment and import the exported files in the target environment. The files are exported to the UCM server. Download the files from the source environment and upload them into the UCM server in the target environment. Submit the ESS jobs by invoking the SubmitESSJobRequest operation in the ERP integrations rest service.
Export job process name : ExportPlans
Export job parameters:
Parameter | Mandatory/Optional | Example |
---|---|---|
Business Unit ID | Mandatory | 204 |
Mode | Mandatory | Single |
Plan Name | Mandatory | 2022 Sales Plan |
Import job process name : ImportPlans
Import job parameters:
Parameter | Mandatory/Optional | Example |
---|---|---|
Business Unit ID | Mandatory | 204 |
Conflict Resolution Option | Mandatory | CREATE |
UCM File Identifier | Mandatory | UCMFA00005432 |
Replace | Optional | FY21 |
With | Optional | FY22 |
Prefix | Optional | 2022 |
Suffix | Optional | 2022 |
Start Date | Optional | 2022-01-01 |
End Date | Optional | 2022-12-31 |
Automate migration of plans instead of doing it manually.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- To call the SubmitESSJobRequest operation in the ERPIntegrations rest service, the user needs to have the Financial Integration Specialist role.
- Avoid submitting multiple plan import requests simultaneously if the plans share any components, measures, expressions, rate tables or rate dimensions. However if the plans don't share any of these entities, you can submit imports simultaneously.
Key Resources
See the "Plan Validation, Approval, Export, and Import" chapter in the Using Incentive Compensation guide.
Role And Privileges
- Incentive Compensation Plan Administrator
-
Financial Integration Specialist
Use Default Rate for String-based Rate Tables.
Associate a default rate to rate tables with string-type rate dimension. Use this default tier to associate a rate when the formula doesn't find a match in any of the other tiers.
Example: If your rate depends on the country and you have a default rate for all countries except 5 where you have special rates, the input expression no longer has to parse the input data to figure out if the input is not one of the 5 countries and then name it as default like DECODE (ATTRIBUTE1, 'US', 'US', 'CANADA', 'CANADA', 'MEXICO', 'MEXICO', 'JAPAN', 'JAPAN', 'GERMANY', 'GERMANY', DEFAULT). Instead of this you can just have your input expression be the country name and use the default rate tier to assign rates.
Reduced complexity in plan configuration.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- If you do not want a default rate, delete the default tier when you are creating a string-type rate dimension.
- Existing rate dimensions built before this release will not be affected. However you can add the default tier to existing rate dimensions if needed.
Key Resources
See the "Rate Tables" chapter in the Using Incentive Compensation guide.
Role And Privileges
- Incentive Compensation Plan Administrator