Standard Value Rule Sets
You can create rules to determine the source and prioritization for defaulting order information to the Sales Orders window. These standard value rules reduce the amount of information you must type in. You can even define a constant for most fields to be used when all other sources do not contain values.
Blocks and Fields
Blocks include regions on the Sales Orders and Returns windows such as Order, Line, Option, Return, Return Line, and so on. Fields include individual fields of a particular Block, such as Warehouse, Ship To Location, or Agreement. These are the same blocks and fields you use when defining Order Entry/Shipping security rules.
A standard value is a default value that Oracle Order Entry/Shipping automatically places in an order field. You can base the standard value for a field on values of other fields, such as values you have previously entered for the order, the customer, or the order type.
A standard value rule set is a collection of standard value sources for blocks and their fields. You can define several different rule sets to use in different order processing situations. You can define a different rule set for each order type, since you associate a rule set with an order type.
A standard value rule set is made up of the following components:
Assign a Sequence
You specify the priority sequence in which you want to search for a field's standard value. Oracle Order Entry/Shipping looks at the lowest number first to begin searching for a standard value. It continues to the next highest number until it finds a value. So if your first and second sources are null, but your third source does contain a value, Oracle Order Entry/Shipping uses your third source.
Identify Sources
A standard value source is the location from which you obtain a standard value; usually the location is another block and field. For most fields, you can assign at least one block/field standard value source, in addition to using the Profile Option and Value sources.
For example, you may want to define a rule to automatically provide the Price List on an order from a variety of different sources. In this case, the block of the rule is Order and the field is Price List. Potential sources consisting of blocks and fields include the customer agreement, the customer, and the order type, which are all blocks, and the price list is the field for all three of these blocks. You can choose which sources you want to use, and your choice may depend on your business practices, whether those sources exist for a particular order, and whether those sources have a price list defined for them. For the customer, you may have defined separate price lists for the bill-to and ship-to addresses in addition to the customer itself. All three of these fields are available as sources.
Profile Option
You can have other types of source blocks that you specify a value for instead of a field. The Profile Option source allows you to use a profile option, either system or user-defined, as a standard value source. You must then indicate the value of that profile option to be used as the default value in the rule. This source allows for greater standard value tailoring flexibility without complex customizations.
Suggestion: If you intend to use a profile option as a standard value source, you must make sure that it is defined before attempting to reference it in a standard value rule.
Value
The Value source option allows you to specify a constant value instead of a field that contains a value. This is especially useful if you always want the default to be the same value, or to use as a last resort if it so happens that none of the other sources you have defined for your rule set can actually provide values. For example, if all items in your organization are sold with the unit of measure Each, you could define a standard value rule to default the value of Each for the Unit field of the Line block.
Set Override Permissions
You can set the override permission fields to control whether users can override the default values that your rules provide, and whether Oracle Order Entry/Shipping can override manually entered values using your standard value rules.
Override Allowed
For most fields, you will probably want your users to be able to override a default value at order entry time when necessary. However, for some sources, such as Agreement, you may not feel it is appropriate to allow users to override the fields that use Agreement as a source; you can use the Override Allowed field to prevent this.
Override User-Specified Values
Some defaulting may not take place until after the user has entered some values on an order manually. For example, a user may change the agreement, and that agreement may be a standard value rule source for other fields, which would result in different defaulting; or the user may want to enter the warehouse for the order, but they have already entered a specific warehouse for an order line. In these cases, you may or may not want to have your rules override the manually entered values in the Sales Orders window. You can control this using the Override User-Specified Value field.
For example, your order entry clerk enters an order over the phone. After manually entering a price list, the clerk quotes the price of the order to the customer on the phone. Later, an agreement is added to the order, which affects the standard value defaulting for the Price List field. If you want to allow the price list designated for the agreement to replace the one that the clerk originally entered, then you must have checked the Override User-Specified Value check box for the Price List field (Order block). If you want the original price list to prevail, then the Override User-Specified Value check box must be unchecked. Additionally, if the Override Allowed check box for the Price List field is checked for the Agreement source, then the order entry clerk can go back and reenter the price list to match the original. If the Override Allowed check box for the Price List field for the Agreement source is unchecked, then the clerk would not be able to replace the designated price list for the agreement.
Assign to an Order Type
Assign the standard value rule set to an order type. You can assign the same one to many order types.
The order type does not default. Once you enter the order type on an order, the standard value rule set for the order type is used to default information to all appropriate fields on the Sales Orders window.
See Also
Defining Standard Value Rule Sets
Duplicating Data From a Previous Record
Standard Value Rules Examples
Here is an example of a standard value rule that you can define for the Price List to default to the Sales Orders window. You may want to define a priority sequence in which you want Oracle Order Entry/Shipping to search for a Price List. The default sequence could be: look on an Agreement for a Price List, followed by the Invoice To Location, then Ship To Location, then Customer, and finally the Order Type. If Oracle Order Entry/Shipping still does not find a price list in any of those source locations, you can have a Value default, such as 1994 USA Prices, which you enter in the Value field of the Standard Value Rule Sets window. The table below represents this example.
| Agreement (1)
| Price List
| Override Allowed: Yes
|
|
|
| Override User-Specified Value: Yes
|
| Invoice To Location (2)
| Price List
| Override Allowed: Yes
|
|
|
| Override User-Specified Value: No
|
| Ship To Location (3)
| Price List
| Override Allowed: Yes
|
|
|
| Override User-Specified Value: No
|
| Customer (4)
| Price List
| Override Allowed: Yes
|
|
|
| Override User-Specified Value: No
|
| Order Type (5)
| Price List
| Override Allowed: Yes
|
|
|
| Override User-Specified Value: No
|
| Value (6)
| 1994 USA Prices
| Override Allowed: Yes
|
|
|
| Override User-Specified Value: No
|
Suggestion: We do not recommend that you define any overly complex or cyclical standard values. If your rules are too convoluted Oracle Order Entry/Shipping generates an error.
Effects of Modifications to Orders and Rules
Modifications to orders may cause Oracle Order Entry/Shipping to reapply the defaulting from your standard value rule set. This reapplication of defaults may also lead to changes that trigger another reapplication. If you entered any fields manually, these values are not overriden, even if they are affected by a reapplication, unless you checked the Override User-specified Value option when you defined your standard value rule set. Values are not overriden if a reapplication results in potential changes that would violate security rules.
If reapplication changes a value and results in inconsistent information on the order, Oracle Order Entry/Shipping prevents users from committing the order and provides messages to assist in correcting the data. For example, depending on the standard value rule set, changing the warehouse on the order could change the warehouse on the order lines. If the line items are not in the new warehouse, Oracle Order Entry/Shipping prevents you from committing the order and issues instructions.
Modifications to standard value rule sets go into effect once you logout and login again for any new orders that use the modified standard value rule set. Existing orders are only affected if you update a field on the order that was involved in the modification (also after you logout and login again). If you never make a change to an existing order that uses the modified standard value rule set, thus activating validation of defaulting, then the order is not affected by the modification.
See Also
Defining Standard Value Rule Sets
