OKL Rules

You might also like

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 12

OKL - OKC Rules

Architecture
February 04, 2004
Agenda

 Rules Overview
 Architecture
 Defining Rules
 Rules Rendering
 Rules Public APIs
 Examples of Rules
 Questions & Answers
Overview
 Rule and Rule Group
– The rule group is used to group together related rules
– The rule group determines the rules to be mandatory
or optional.
– The rule group instance references the contract or line
ID.
– Some rules are included in more than one rule group
– Using OKC set up screens, you can relate rule group
definitions to a contract category as well as a contract
line/subline styles.
Overview (contd…)

 Rule Sources
Rule values can be derived through a reference of
any of the following:
– Master Lease Agreements
– Vendor Agreements
– Products (OKL Financial Products)
– Deal Contract Interfaces
– Profile Options
Architecture
Profile Option Product
(OKL Financial Product)

Contracts

Operating Rule Groups Rules (values)


Agreement
Rule Group
Rule Definition
Definition
Program Deal Contract Master Lease
Agreement Header Agreement

Lines

Contract Line

Contract Sub-Line
Defining Rule and Rule Group

 The lookup type OKC_RULE_GROUP_DEF is used to define the


rule groups.
 The lookup type OKC_RULE_DEF is used to define the rules.
 Define a Descriptive flex field for the table OKC_RULES_B.
 OKC_RULES_B contains the rules that are included in the rule
groups.
– Each rule has a value set (which may contain a single or
multiple values)
– The values may be a constant which applies to all instances
of the rule, a set of possible values from which the user will
choose a single value
Rendering Rules

 OKC_RULE_GROUPS_B stores the association of rule group


with contract header and contract line.
– ID - Primary Key
– RGD_CODE - Rule Group Code
– CHR_ID - Populated for rule group associated with
Contract Header
– CLE_ID - Populated for rule group associated with
Contract Lines
– DNZ_CHR_ID - De-normalized contract ID
Rendering Rules (contd…)

 OKC_RULES_B stores the association of rule with rule group.


– ID – Primary Key
– RGP_ID – FK to OKC_RULE_GROUPS_B.ID
– DNZ_CHR_ID - De-normalized contract ID
– object(x)_id1, object(x)_id2, jtot_object(x)_code
– RULE_INFORMATION_CATEGORY – Rule Name
– RULE_INFORMATION(x)
Rules Public APIs

 OKL_RULE_PUB
– create_rule_group
– create_rule
– update_rule_group
– update_rule
– delete_rule_group
– delete_rule
Example

Rule Rule Rule Value Definition Rule Values


Group
Fee Fee Expense rule_information1 = Periods 5
Expense (LAFEXP)
(LAFEXP)
rule_information2 = Periodic 5000
Amount
Frequency OBJECT1_ID1 M, Q, S, A
(LAFREQ)
Q&A

You might also like