Selected Order Management Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle Order Management works. This isn't a full list of all the bug fixes in this update. This list includes the bug fixes that can cause a noticeable change in application behavior.

Validate Business Units for Referenced Return Lines

Before Update 25A, if you submitted a sales order that had a referenced return line, then you had to make sure the business unit for that line matched the business unit on the original order line. You could set the Allow Business Unit Mismatch Between Referenced Return and Original Order profile option to Yes to turn off this validation.

Starting in Update 25A, you can’t turn off this validation, so you must make sure the business unit on the return line matches the business unit from the original line.

For background, see Return Sales Orders.

Oracle reference: 37117883

Prevent Buyers from Ordering Configured Items

Before Update 25A, if a buyer ordered a configured item, then the buyer encountered an error during order fulfillment.

Starting in Update 25A, Order Management prevents the buyer from ordering a configured item.

For background, see Overview of Configure-to-Order.

Oracle reference: 36106037

Make Sure Identifiers for Source Lines Are Unique

Before Update 25A, if your sales order contained more than one order line that referenced the same identifier for the source line, and if you revised the order, then the revision might have failed or the order might have gotten stuck during fulfillment.

Starting in Update 25A, you must make sure that the identifier for each source line in your import payload is unique. If it isn't, and if you create the sales order on or after Update 25A, then Order Management will prevent you from submitting the order or a revision.

For background, see Overview of Importing Orders Into Order Management.

Oracle reference: 36873961

Use New and Revised Methods in Your Order Management Extensions

Starting in Update 25A, you can use these new and revised methods in your order management extensions. You no longer have to explicitly code them:

Method	Object	Description
isFirstDraftOrder. Revised.	Order Header	See whether the sales order is in draft status.
isRevisionDraftOrder	Order Header	See whether the sales order is an order revision that's in draft status.
canApplyHold. Revised	Order Header	Make sure you haven’t already applied a specific hold on the order header.
	Order Line	Make sure the order line isn’t a child line of a configured item or kit, and that you haven’t already applied a specific hold on the order line.
holdExists. Revised.	Order Header	See whether you already applied a specific hold on the order header.
	Order Line	See whether you already applied a specific hold on the order line.
isNewLineInDraftOrder	Order Line	See whether the order line is a new line that you added to a draft order.
isRootLine	Order Line	See whether the order line is the root line of a configured item or kit.
isChildLine. Revised.	Order Line	See whether the order line is the child of a configured item or kit.
getRowFromPVO	Public View Object	Get the first row that your query finds in a public view object according to filters that you specify.
getRowsFromPVO	Public View Object	Get more than one row that your query finds in a public view object according to filters that you specify. You can specify the maximum number of rows that you want the query to return.
getDataFromPVO	Public View Object	Get the first row that your query finds in a public view object according to filters that you specify. You can specify the attribute values that you want to get from that row.

Oracle reference: 36891726

Steps to Enable

You don't need to do anything to enable this feature.