Manage Processing Constraints for Drop Ship

Learn about the predefined processing constraints that Oracle Order Management uses to help keep your drop ship flows running smoothly.

Examine the predefined constraints. Assume you want to get details about the predefined DOO_CREATE_PURCHASE_REQUEST_VALIDATION constraint:

1. Go to the Setup and Maintenance work area, then go to the task.
   • Offering: Order Management
   • Functional Area: Orders
   • Task: Manage Processing Constraints
2. On the Manage Processing Constraints page, search for the value.

   Attribute	Value
   Constraint Name	DOO_CREATE_PURCHASE_REQUEST_VALIDATION

3. Examine the attribute values. Notice that they prevent you from doing a validation operation on the fulfillment line, for example, when the arrival dates on the fulfillment line don’t contain a value.
4. Examine the Message attribute to view the message that this constraint displays at run time.

For details about how constraints work, see Processing Constraints.

Predefined Constraints That You Can Enable

These constraints come predefined as disabled. Order Management applies them in your drop ship flows. You can enable them, but you can’t modify them. You must not delete them.

Constraint Name	Description
DOO_CREATE_PURCHASE_REQUEST_VALIDATION Display Name: Create Purchase Request Validation	If the Scheduled Arrival Date attribute on the fulfillment line is empty, then this constraint makes sure: The Requested Arrival Date or the Scheduled Arrival Date on the fulfillment line contains a value. The ordered quantity on the fulfillment line is greater than zero. The Record Set contains the values that the Update Purchase Request fulfillment task requires. If you Don't Use Global Order Promising, and if you: Enable the buyer to manage transportation for the supplier agreement, then Order Management requires the ship date. Don't enable the buyer to manage transportation for the supplier agreement, then Order Management requires the arrival date. Order Management makes sure the required date contains a value when you submit the sales order.
DOO_UPDATE_PURCHASE_REQUEST_VALIDATION Display Name: Update Purchase Request Validation	If the Scheduled Arrival Date attribute on the fulfillment line is empty, then this constraint makes sure: The Requested Arrival Date or the Scheduled Arrival Date on the fulfillment line contains a value. The ordered quantity on the fulfillment line is greater than zero. The Record Set contains the values that the Update Purchase Request fulfillment task requires. If you Don't Use Global Order Promising, and if you: Enable the buyer to manage transportation for the supplier agreement, then Order Management requires the ship date. Don't enable the buyer to manage transportation for the supplier agreement, then Order Management requires the arrival date. Order Management makes sure the required date contains a value when you submit the sales order.
DOO_DS_FULFILLMENT_LINE_CANCEL Display Name: Cancel Fulfillment Line That Drop Ships DOO_DS_FULFILLMENT_LINE_UPDATE Display Name: Update Fulfillment Line That Drop Ships	Prevents you from updating or canceling the fulfillment line when the purchase request in Oracle Procurement is at the Purchase Order stage. For example, if you attempt to update, then Order Management displays a message. Order management can't update the fulfillment line because the purchase request in the procurement application is at the Purchase Order stage. Order Management applies these constraints until the received quantity or invoiced quantity equals the quantity on the order line. These constraints help to keep the sales order in Order Management and the purchase order in Oracle Procurement synchronized with each other. If you disable these constraints but Procurement can't accept an update or cancel because the supplier rejects the change, then you must create and enable your own constraint that prevents you from updating or canceling the line at runtime. If you must allow your users to cancel a fulfillment line that's at the Awaiting Shipping status, and if DOO_DS_FULFILLMENT_LINE_CANCEL is enabled, then tell your users to cancel the purchase order, wait until Order Management receives the updated status for the purchase order, revise the sales order, cancel the order line, and then submit the revision. If you disable DOO_DS_FULFILLMENT_LINE_CANCEL, and if you haven't created your own constraint that prevents you from canceling, then you can use the Order Management work area to cancel a fulfillment line that's at the Awaiting Shipping status in a drop shipment. Procurement will also cancel the purchase order and the purchase requisition for the fulfillment line.

Predefined Constraints That You Can’t Disable

These constraints come predefined as enabled. Order Management applies them in your drop ship flows. You can’t disable them or modify them. They help to make sure you don’t inadvertently introduce errors into your drop ship flow.

Attribute	Value
DOO_FULFILLMENT_LINE Display Name: Fulfillment Line Update	If the order line’s status is Requisition Created, then you can’t revise the line, but you can cancel the line.
DOO_FULFILLMENT_LINE_CANCEL Display Name: Cancel Fulfillment Line	If the order line’s status is Requisition Created, and if it’s part of a configured item or shipment set, then you can’t cancel the line. Instead, you must return the line in Procurement, and then reschedule or cancel it in Order Management.
DOO_SUPPLIER_SITE_CHANGE Display Name: Change Supplier Site	If Procurement splits a fulfillment line during a change, then you can’t modify the supplier site on that line.
DOO_SUPPLIER_CHANGE Display Name: Change Supplier	If Procurement splits a fulfillment line during a change, then you can’t modify the supplier on that line.
DOO_FulfillmentLine_DropShip_PO_Received_Cancel Display Name: Cancel Fulfillment Line When Purchase Order Isn't Available	Prevents you from cancelling a fulfillment line when any of these conditions exist: The purchase order for the line is frozen or is on hold. The quantity that Order Management shipped doesn't match the quantity that Procurement received or billed.
DOO_FulfillmentLine_DropShip_PO_ReceiveD_Update Display Name:Update Fulfillment Line When Purchase Order Isn't Available	Prevents you from revising a fulfillment line when any of these conditions exist: The purchase order for the line is frozen or is on hold. The quantity received or the quantity billed doesn't equal the quantity shipped. You ship part of a line and your customer returns some or all of the quantity on the shipped line. If the quantity that Order Management shipped doesn't match the quantity that Procurement received or billed, then you can't change the value for: Any attribute that's eligible for a constraint. An attachment, extensible flexfield, tax determinant, payment term, or accounting detail. An attribute in Order Management that isn't mapped to Procurement, but that's eligible for a constraint. This condition applies until the quantity that Order Management shipped matches the quantity that Procurement received or billed. Order Management prevents these changes at run time on order lines that it has shipped and on lines that it hasn't shipped. You can modify the value of an attribute that isn't eligible for a constraint regardless of whether it’s mapped between Order Management and Procurement.
DOO_UPDATE_EFF_FULFILLMENTLINE_DROPSHIP Display Name: Submit Changes to Extensible Flexfield on Fulfillment Line During Requisition	Prevents you from modifying an extensible flexfield on a fulfillment line when the line is at the requisition stage in Procurement.