Implementing Order Management (2024)

Sales order in the Order Management work area

• As an option, set the Order Typeattribute to Drop Ship Orders on the order header.

• Set the Supplier attribute and Supplier Site attribute on the Supply tab of the order line. If you don't specify a value for supplier site, then Oracle Procurement sets it according to rules in Procurement.

Sourcing rule in the Order Promising work area

Use the Manage Sourcing Rules page in the Order Promisingwork area. Set the attributes.

• Supplier

• Supplier Site

REST API

Use the salesOrdersforOrderHub REST resource. In the request payload, provide.

• SupplierId

• SupplierName (optional)

• SupplierSiteId

• SupplierSiteName (optional)

• TransactionType or TransactionTypeCode

For example:

{ "SourceTransactionNumber":"87956", "SourceTransactionSystem":"GPR", "SourceTransactionId":"87956", "BusinessUnitName":"Vision Operations", "BuyingPartyName":"Computer Service and Rentals", "BuyingPartyContactName":"Brian Smith", "TransactionType":"Standard Orders", "RequestedShipDate":"2019-10-19T20:49:12+00:00", . . . "SupplierId" : 11176859, "SupplierName" : "Green Bytes Inc.", "SupplierSiteId" : 76846573869, "SupplierSiteName" : "Denver Distribution Center" "TransactionType" : "Dropship Orders" "TransactionTypeCode" : "STD_DS" . . .}

For details and examples, go to REST API for Oracle Supply Chain Management Cloud, expand Order Management, then click Sales Orders for Order Hub.

File-Based Data Import

Use the SourceSalesOrderImportTemplate.xlsm file.

On the DOO_ORDER_HEADERS_ALL_INT worksheet, set theTransaction Type Code to STD_DS.

On the DOO_ORDER_ADDRESSES_INT worksheet.

• Set the Address Use Type attributeto SUPPLIER.

• Specify a value for at least oneof these attributes.

  • Requested Supplier Code

  • Requested Supplier Number

  • Requested Supplier Name

• Specify a value in the RequestedSupplier Site Identifier attribute.

Web Service

• Specify TransactionType or TransactionTypeCodeon the order header in a web service payload.

• Specify RequestedSupplierName andSupplierSiteCode on the order line.

• Use the Create Order Operationof the OrderImportService web service.

For example:

<ns2:Order> . . . <ns2:TransactionType>Dropship Orders</ns2:TransactionType> . . . <ns2:Line> . . . <ns2:RequestedSupplierName>Green Bytes Inc.</ns2:RequestedSupplierName> <ns2:SupplierSiteCode>76846573869</ns2:SupplierSiteCode> . . .

• You can revise the promised ship date, promised delivery date, or shipment method. You can cancel the order or split the schedule for a line that has a pick-to-order item or has an item that's part of shipment set or kit in a purchase order. You can do these actions even when the supplier shipped part of the line.
• You can change the shipment date, delivery date, or shipment method only if the new value that you provide on the purchase order line is the same for all components that are part of the pick-to-order item, all items that are part of a kit, or all items that are part of a shipment set.
• if the item is a pick-to-order configured item, a kit, or if it's part of a shipment set, then you can't cancel the purchase order schedule or purchase order line.
• Don't use a shipment set to group sales order lines into a single purchase order. Procurement doesn't support shipment sets for this usage.

Modify purchase requisition.

The buyer must not:

• Modify or split a requisition line.

• Modify a pick-to-order or assemble-to-orderconfigured item.

• Modify a kit.

If Order Management applies a hold on a sales order, then Procurement also applies a hold on the corresponding purchase order. If the buyer has the PO_RELEASE_PO_REQ_INIT_HOLD_FREEZE_PRIV (Release Purchase Order Hold and Freeze Initiated by Requester) privilege, then the buyer can use the Purchase Orders work area to remove the hold.

Modify other attributes

The buyer can change values in attributes that don'taffect the drop ship flow.

Split the schedule.

The buyer can split the schedule, but don't split the schedule and also change the supplier at the same time.

Combine sales orders into one purchase order.

If the flow creates one purchase order for requisitionlines that reference more than one sales order, and if you revisethese sales orders, then the flow places a hold on one of the salesorders and revises the purchase order. It doesn't revise the othersales orders and they fail.

To fix this problem, go to the Order Management workarea, delete the sales order revisions that failed, wait for OrderManagement to finish processing the sales order it placed on hold,then revise the other sales orders.

You can only combine sales orders for the same customeror for the same supplier site. You can't consolidate sales ordersacross customers or across supplier sites.

Combine sales order lines into purchase orders.

Manually combine sales order lines into one or morepurchase orders. You can create one purchase order for each orderline, resulting in several purchase orders for one sales order.

Modify the quantity.

If you split the purchase order schedule across morethan one delivery date, then make sure the total quantity across yoursplit schedules equals the ordered quantity on the fulfillment line.

If shipping has received the ASN, then you can'tmodify the quantity.

Set the quantity for advance shipment notice.

Make sure you use a single order line to specifythe quantity for an advance shipment notice. Don't split the quantityacross more than one line.

Modify the receipt quantity.

The drop ship flow creates a receipt when it receivesan invoice from accounts payable or an advance shipment notice. Theflow then moves to the next orchestration process step in Order Management.Order Management won't display a subsequent change you make to thereceipt quantity.