Defining Security Rules
You can assign security rules to your order information. You can specify the steps in the order process where you no longer allow users to add, delete, modify or cancel order or return lines. You can use the default rules, which provide the minimum limits to maintain data integrity, or define your own stricter rules to reflect your order and return maintenance policies.
To define a security rule for a block:
1. Navigate to the Security Rules window.
2. Select the Block name for which to define the security rule.
3. Choose Block Rules. The Security Rules (Block Name) window appears.
4. Select the operation you want your security rule to prevent.
Insert: Prevent a user from inserting data.
Update: Prevent a user from modifying data for all attributes within the Block you chose. This option effectively applies a blanket attribute-level rule, which you can then edit using the Update option from the Security Rules (Field Name) window.
Delete: Prevent a user from deleting data.
Cancel: Prevent a user from cancelling data.
5. Create And/Or conditions between rows by entering a number or accepting the sequential default.
You can define an And condition by using the same number in this field for multiple rows in the condition. You can define an Or condition by using different numbers. Conditions with the same number must both be true for the security rule to apply. For conditions with different numbers, at least one must be true for the security rule to apply.
Attention: You cannot enter a number equal to any number for a predefined security rule in Oracle Order Entry/Shipping (rules with System Rules check box toggled on). This would, in effect, create an And statement with a System security rule, and could endanger data integrity.
6. Check Modifier to define a negative condition.
A modifier allows you to define a security rule to be effective for any condition except for the one you enter in the Condition Name field.
7. Enter a condition name.
ATO Component: Prevent operation when you enter an order line for an ATO (assemble-to-order) component.
ATO Configuration Item: Prevent operation when Oracle Work in Process has created an ATO configuration item for an ATO model or item.
ATO Model: Prevent operation when you enter an order line for an ATO model.
Cycle Status: Prevent operation when an order, return, order line or return line achieves a particular cycle status. If you choose this option you must enter a cycle action in the Action field. Choose appropriate cycle actions for orders or returns, depending on the Block for which you are defining rules.
Internal Sales Order: Prevent operation if the order is an internal sales order imported from Oracle Purchasing.
Line Closed: Prevent operation if the order line or return line is closed.
Order Closed: Prevent operation if the order or return is closed.
Prorated Prices Exist: Prevent operation if prorated discounts were used on the order and at least one order line has interfaced to Receivables.
Schedule Group: Prevent operation if the order line is in a schedule group. A schedule group can be all the lines in a ship set, in an ATO configuration, or in a Ship Together model (a configuration with the top model's Ship Model Complete inventory item attribute set to Yes).
Scheduling Exists: Prevent operation if the items on the order line have been demanded or reserved.
Supply Reservation Exists: Prevent operation if the item on the order line has a work order opened, and the schedule status for the line is Supply Reserved. When Work in Process completes the work order and changes the status to Reserved, this condition no longer applies.
8. If you entered Cycle Status in the Condition Name field, enter a specific cycle action and result for your security rule
Oracle Order Entry/Shipping automatically allows only those results that you have defined to correspond with the action you chose. If you leave the Result field blank, your condition holds true when the Block (line or order) has any result for the cycle action you entered in the Action field, except Eligible and Not Applicable.
9. Enter the scope of the condition. The scope determines which lines to test the condition against when evaluating the security rule.
A condition holds true if any line within the scope meets the condition. If you chose Cycle Status in the Condition Name field, and you chose a line-level cycle action in the cycle Action field, then you must enter a scope. If you are defining a security rule based on an order action, such as Enter, then Oracle Order Entry/Shipping automatically displays Order in this field.
ATO Configuration: Evaluates the condition against all lines in an ATO configuration.
Configuration: Evaluates the condition against all lines in a configuration.
Line: Evaluates the condition only against the line on which you attempt the operation of your security rule.
Order: Evaluates the condition against all lines in an order.
Schedule Detail: Evaluates the condition only against the schedule detail on which you attempt the operation of your security rule.
Ship Set: Evaluates the condition against all lines in a ship set.
Shipment Schedule: Evaluates the condition against all lines in a shipment schedule.
Subconfiguration: Evaluates the condition against all option lines for a configuration, including the configuration line.
To define security rules for fields in a block:
1. Navigate to the Security Rules window.
2. Check Field Security for the Block.
3. Select the Field name for which to define the security rule.
4. Choose Field Rules. The Security Rules (Field Name) window appears.
Since Field Name security rules can only prevent update, Oracle Order Entry/Shipping automatically toggles the Update operation on in the window.
5. The fields on this window function the same as the fields on the Security Rules (Block Name window). See steps 4-9 in the previous task for more information on these fields.
See Also
Defining Discounts
Defining Order Cycles
Assigning Cycle Action Results
