OM Defaulting Rules

1
OM Defaulting Rules
Save Order Entry Effort With OM Defaulting Rules
Jake Penne NCOAUG February 13, 2002
2
Agenda

• OE standard value rule sets
• OM defaulting framework
• Functional design and setup
• Examples of defaulting strategy
• Imbed custom PL/SQL to enforce business rules
• Summary

3
OE Standard Value Rule Sets

• Limited by OE architecture
• Tied to a specific Order Type
• Hard coded list of source values
• Difficult to extend functionality

4
OE Standard Value Rule Sets Example

5
Defaulting Framework

• Take advantage of expanded OM architecture
• Expanded beyond context of an Order Type
• Increased flexibility
• Can extend rules and customize
• Generic solution that will be expanded to other
  modules in the future

6
Functional Design and Setup

• Entities
• Attributes versus fields
• Conditions / Validation Templates
• Sources of values
• Rule sequence
• Dependencies and constraints

7
Functional Design and Setup Example
8
Functional Design and Setup Example
9
Examples of Defaulting Strategies

• Default from the user
• Enforce security
• Drive basic pricing logic
• Make decisions

10
Imbed PL/SQL Code

• Use a Source value type of PL/SQL API
• Must be a PL/SQL function defined within a custom
  package.
• Function definition must match standard
  definition (signature)
• Can reference related entity attribute values
  from within the custom function code.

11
Imbed PL/SQL Code Example
12
Imbed PL/SQL Code Example
13
Summary