Activity Based Holds Are Not Working At Booking Nor At Scheduling (Doc ID 340086.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Order Management - Version 11.5.10.2 and later
Information in this document applies to any platform.
FORM:OEXOEORD.FMB - Sales Orders
***Checked for relevance on 04-AUG-2015***


Goal

How is this example setup incorrect, since with it user is permitted to book the sales order?
Why do activity based holds require a hold source?
What is the setup needed for activity based holds so that order is placed on hold during booking?
How is it recommended to implement hold sources to lessen the number that need to be created?

Example setup Activity specific hold at Order Header level and Order line level.
1. order for header activity - on Booking activity.,
type = Order Administrative Hold
workflow item = OM Order Header
workflow activity = Book Order
responsibility: Authorized Action:
Order Management Super User Apply Holds
Order Management Super User Remove Holds

2. order and line for line activity - on Schedule activity

type = Order Administrative Hold
workflow item = OM Order Line
workflow activity = Line Scheduling
responsibility: Authorized Action:
Order Management Super User Apply Holds
Order Management Super User Remove Holds

One responsibility is assigned to apply and release the holds.
Order Management SuperUser> Setups > Holds
Order Management SuperUser> Order, Returns> Sales Order

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms