Supplier Rebates and Supplier Annual Rebates are both part of Oracle’s Supplier Channel Management. While both types of rebates are incentives offered by suppliers to encourage purchases, they differ in how they are accumulated. Supplier Rebates are typically tied to specific purchases or transactions1. On the other hand, Supplier Annual Rebates are accumulated across multiple orders over a specified time period, often a year21. This allows organizations to track and manage cumulative purchasing volumes over the effectivity of a program2.

To change the status of a pricing strategy from “In progress” to “Approved”, you must click the Approve button on the Edit Pricing Strategy page. The Approve button is only enabled when the pricing strategy is complete and valid. A pricing strategy is complete when it has at least one pricing segment and one pricing rule.A pricing strategy is valid when it has no errors or conflicts1. By clicking the Approve button, you submit the pricing strategy for approval. The approval process depends on the approval life cycle that you have defined for the pricing strategy. The approval life cycle can include one or more approvers, who can approve or reject the pricing strategy.Once the pricing strategy is approved by all the approvers, the status changes to “Approved” and the pricing strategy becomes effective2.

Rule conditions are the Oracle Business Rule component that determines the specific rule that will be used to transform the imported orders.Oracle Business Rules are a set of logic statements that define the behavior of an application or a process, such as order transformation, order orchestration, or order approval1. A rule consists of two parts: a condition and an action. A rule condition is a statement that evaluates to true or false based on the input data, such as order attributes, order lines, or order status.A rule action is a statement that performs a specific task or operation when the rule condition is true, such as updating order attributes, creating order lines, or changing order status2.You can use the Manage Order Transformation Rules task to define the rule conditions and actions for transforming the imported orders from a legacy system into Oracle Order Management Cloud3.

The IMPLIES keyword is used to create a configurator rule that specifies a logical implication between two expressions. The syntax of the IMPLIES keyword is:

expression1 IMPLIES expression2

This means that if expression1 is true, then expression2 must also be true.However, if expression1 is false, then expression2 can be either true or false1. In the Configurator runtime UI, the IMPLIES keyword can be used to show or hide options based on the selection of features. For example, the following rule:

'LX-Luxury Package' IMPLIES '8-way Power Driver Seat'

means that if the LX-Luxury Package feature is selected, then the 8-way Power Driver Seat option must also be selected. However, if the LX-Luxury Package feature is not selected, then the 8-way Power Driver Seat option can be either selected or not selected.

Therefore, when the LX-Luxury Package option is selected, all the options after the IMPLIES keyword will be selected, according to the constraint rules. This means that the 8-way Power Driver Seat, the 8-way Power Passenger Seat, and the Cloth options will be selected.

https://docs.oracle.com/en/clou d/saas/supply-chain-management/r13-update17d/fascp/manage-order-promising-rules.html#FASCP1127104

ATP Rule Promising Modes: Explained

The promising mode of an available-to-promise (ATP) rule determines which set of attributes the order promising logic evaluates when determining ATP results. When creating an ATP rule on the Manage ATP Rules page, the first thing that you must specify is which of the three promising modes is applicable to the ATP rule.

These are the three promising modes:

Supply chain availability search

Lead time based

Infinite availability based

http://docs.oracle.com/cloud/latest/scmcs_gs/FASCP/FASCP2577133.htm#FASCP2577137