Assigning Contingencies


You can define defaulting rules for automatic contingency assignment.

Note: You must define defaulting rules to enable automatic contingency assignment. However, do not define defaulting rules to address revenue policy violations, because Receivables automatically
assigns the appropriate revenue contingencies if any revenue policy is violated.

For each rule that you define, you can specify one or more matching criteria. If the rule's stated criteria is matched, then Receivables assigns the contingency that you select.
For example, you might want to require Customer ABC to always manually accept an item before revenue on its transactions can be recognized. To enforce this scenario, create a new rule, select the revenue contingency that is the desired result (in this case, Explicit Acceptance), select Bill To Customer as the rule parameter, and enter the customer condition.

With this defaulting rule in place, Receivables will assign the Explicit Acceptance contingency to all Customer ABC's transaction lines, and revenue will be deferred until customer acceptance is manually recorded.

You can define multiple rules with different matching criteria that return the same contingency. And, you can define multiple rules with the same matching criteria that return multiple  contingencies.

Rule parameters that you can use during rule definition include:

  1. Accounting Rule
  2. Batch Source
  3. Bill To Customer
  4. Bill To Site
  5. Customer Profile Class
  6. Inventory Item
  7. Memo Lines
  8. Operating Unit
  9. Ship To Customer
  10. Ship to Site
  11. Transaction Type

Note: You cannot assign contingencies to transaction lines that have deferred account rules.

Oracle Applications Fusion Cloud - Inventory

Oracle Cloud/Fusion Procurement training will help you develop the fundamental skills required to set up and use the Procurement module. This training covers all the tasks, setups, forms and reports used in Procurement and related modules