You can define holds to halt processing of your orders, returns, and their lines.  Because orders and returns are not affected by holds until they are applied, you can define all the holds you use in your business at once. You can define holds that are effective only at certain steps of the order or line workflow and holds that apply regardless of the stage in the order’s flow.

For example, you may want to apply an item hold to prevent order lines for a particular item to be released for shipment. Any orders that are not ready for shipment or any orders that have already been shipped are not affected by this hold. You can also define a hold that affects all orders, no matter where the order is in its cycle. When this type of hold is applied, it is effective regardless of the order’s position in the cycle.

The Order Management seeded Hold Names and their descriptions are:
Configurator Validation Hold: Automatically applied to order lines that fail Configurator Validation.
Credit Card Authorization Failure: Automatically applied to orders if credit card authorization request to iPayment fails.
Credit Card High Risk: Automatically applied to orders if risk score determined by iPayment is greater than the value of profile OM: Risk Factor Threshold for Electronic Payments.
Credit Check Failure: Automatically placed if credit check rule evaluation fails on orders setup to be credit checked.
GSA Violation: Automatically placed on orders, which are in violation of GSA.
Promotion Limit Hold:  Automatically placed on orders, which exceed a soft modifier promotional limit. (Promotional Limit Hold functionality is only available if you have licensed and installed Oracle Advanced Pricing.)

Additionally, there is one more seeded hold, but it does not have a Hold Name. This hold has a Hold Type of Order Administration Hold and it is reserved for you to define administration holds based on your business processes.

In addition to the seeded holds, you can define activity-specific holds.

Here is an outline of the steps you will need to follow:
1. When you define the activity-specific hold, you can determine if the hold will be placed on the order header or the order line. This is done via the field Workflow Item in the Holds form. If you want the hold to be placed on the order header, you select OM Order Header; if you want the hold to be placed on the order line, you select OM Order Line.
2. Enter the Workflow Item where you want to stop processing of orders with this hold. The hold activates as soon as the workflow item has a status for the applicable order. For example, you can define a hold that prevents an order from being released for picking by entering Pick Release in this field. The hold takes effect as soon as an order that meets your hold criteria is eligible for Pick Release. If you leave this field blank, the hold prevents the order from processing as soon as it is applied regardless of workflow item.
3. Enter the Workflow Activity for the hold.

The workflow activity determines where in the order cycle the hold will be placed. All other lines will be processed except for the line against which the hold is effective.
4. Optionally, enter the Effective Dates for the activity-specific hold to control when you can use this hold.
5. Optionally, determine which user responsibilities have authority to apply or release activity-specific holds by entering combinations of responsibilities, authorized actions, and effective dates.

You can give some responsibilities the authority to apply a hold, other    responsibilities the authority to release it, and others the authority to do both. If you do not specify a responsibility for an activity-specific hold, anyone can apply or release it.


Mohammad Hossein Ebrahimzadeh
محمد حسین ابراهیم زاده