Oracle R12 Order
Management – Defaulting Rules Setup:
Oracle Order Management Defaulting rules is used to
default certain fields on sales order headers or sales order lines level.
Order Management Defaulting Rules reduce the amount of
data input required when users enters the orders or returns. Business rules can be
defined for defaulting values and prioritize how conditions and validation
rules are implemented.
Oracle Apps R12 provide both seeded and user defined
defaulting rules. Defaulting condition templates can be used to build user’s own
rules and conditions to default these fields.
Defining Defaulting Rule:
Navigation:
India Local Order Management Responsibility > Oracle
Order Management > Setup > Rules > Defaulting
Defaulting Setup:
Application: Application
field displays the application context for the entity displayed.
Entity: Entity field displays the name of the object
for which defaulting rules and conditions are being defined such as the order
line. Order Management have the following options:
Order Header
Order Line
Order Payment
Line Payment
Defaulting
Condition Templates: Defaulting conditions enables to define conditions
that can be used to dictate when an attribute is sourced and defaulted. Select
an existing condition name if needed to update the associated validation rules
or add a new condition name with associated validation rules.
Attributes Block:
Defaulting Sequence: This field enables a user to assign the
sequence (priority) number in which this attribute should be defaulted.
Attribute: This field stores the name of available
attributes. Values are currently displayed based upon the entity selected.
Include in Building Defaulting Conditions
check box: This check box indicates
whether an attribute can be used in defining conditions for the entity
selected. This check box is for display purposes only, and is
non-updateable.
Defaulting Rules:
Defaulting
Condition Block:
Precedence: Enter
a value in the Precedence field to determine the precedence when resolving
multiple TRUE defaulting conditions.
Defaulting
Condition: Select a condition from the LOV and then enter the defaulting
rules to be used if this defaulting condition is TRUE.
Enabled: If the check box is enabled to enable the
defaulting condition. If not selected, the defaulting condition is disabled and
the rules and condition associated with this condition are not used in default possessing.
Seeded: This check
box is for the field Seeded cannot be updated.
Default Sourcing
Rules:
Sequence: Select
the priority sequence in which to retrieve the default for this attribute.
Source Type: Select
the Source Type from the LOV. Defaulting source type determines data entry in
the Default Source/Value field.
OM Source Types
& Actions
Source
Type
|
Actions
|
Constant
Value
|
Enter the default constant value.
|
Application
Profile
|
Select the profile option from where
you want to retrieve the default value.
|
Same
Record
|
Select the attribute on the same
record from where you want to retrieve the default value.
|
Related
Record
|
Object--Select the related object.
Attribute--Select the attribute on the related object from where you want to
retrieve the default value.
|
System
Variable
|
Expression--Enter the system
expression to be evaluated to obtain the default value. (E.g. System Date.)
|
PL/SQL
API
|
You can write a custom API to obtain
a default value if the value cannot be obtained using other source types such
as, the default order number from a sequence.
|
WAD
|
Attribute
|
WAD
|
Object Attribute
|
Example:
A defaulting rule to be defined, for a specific Price
List should default to the Sales Order Header window. Define a sequence
(priority) in which Order Management to search for a Price List.
Sequence to be defined, so that order management will look
for the price list from an Agreement for a Price List, followed by the Ship To
Location and then the Order Type.
Default Sourcing Rules Setup for the example
Sequence
|
Defaulting
Sources
|
Source
Field or Value
|
1
|
Related Record
|
Agreement.Price List
|
2
|
Related Record
|
Ship To Location.Price List
|
3
|
Related Record
|
Order Type.Price List
|
very useful article. explanatory and detailed
ReplyDelete