ONT Order Upload – Enginatics

ONT Order Upload Help

ONT Order Upload creates new sales orders, updates existing orders, adds lines, splits lines into shipments, books orders and cancels orders in Oracle Order Management from Excel, through the standard Oracle Order Management process order API. Each spreadsheet row is one order line; rows with the same Upload Order Identifier belong to one order.

When to use it

Mass-create new sales orders from a spreadsheet, with one or many lines per order.
Add lines to existing orders in bulk.
Bulk-update header or line fields (quantities, dates, prices, addresses, shipping, salesperson) on existing orders.
Split order lines into separate shipments, for example to ship part later, from another warehouse or to another address.
Book many entered orders at once.
Cancel orders and all their lines in bulk, with a recorded change reason.
Apply line-level discounts or price overrides with a price adjustment as audit trail.

Before you start

A responsibility with Blitz Report and access to the operating unit, typically an Order Management responsibility.
The customer account is active and has ship-to and bill-to sites in the operating unit.
The items are customer orderable in the warehouse, and the order types and line types exist for the operating unit.

Step 1 – Set the parameters

Open ONT Order Upload in Blitz Report and set the parameters. All parameters except Upload Mode only restrict which existing orders are downloaded:

Parameter	Meaning
Upload Mode	Create opens an empty sheet for new orders; Create, Update (default) downloads existing order lines for editing and lets you add new orders and lines.
Operating Unit	The operating unit of the orders. Defaults to your current operating unit.
Order Number	Downloads one specific order.
Customer PO	Downloads the orders with this customer PO number on the order header; a different PO number entered on individual lines is not searched.
Customer Name, Account Number	Downloads the orders of a customer.
Order Type, Line Type	Restricts the download to these order and line types.
Open only, Exclude Cancelled	Skip closed orders and cancelled lines. Both default to Yes unless you enter an Order Number or Order Status.
Order Status, Line Status	Restricts the download to orders or lines in this status.
Order Action	Pre-sets the Order Action column on every downloaded row: Book (for entered orders) or Cancel.
Shippable Flag, Order Category, Line Category, Item, Item Type	Restricts the download by line attributes.
Creation Date From/To, Line Creation Date From/To, Schedule Ship Date From/To, Request Date From/To, Cancelled Date From/To	Date ranges. Each To date defaults to the end of the month of its From date.
Debug	Order Management debug level written to the request log, for diagnosing API errors. Leave it blank.

Step 2 – Run to download the Excel file

Click Run. The Excel file downloads and opens with one row per order line of the selected orders, or an empty sheet in Create mode.

Step 3 – Enter or change the orders

To change an existing order, edit the downloaded rows: for example Ordered Quantity, Line Request Date, Unit Selling Price or any header column such as Header Cust Po Number. Header columns are taken from the first row of each order. To add a line to an existing order, add a row with the order number in Upload Order Identifier and leave Line empty.

To create a new order, add rows with a reference such as new1 in Upload Order Identifier, repeated on every line of the order, and enter the Operating Unit, Customer, Customer Number, Header Ship To, Header Bill To and Order Type, and on each line the Item, Ordered Quantity and Line Request Date. Most other columns, such as Ordered Date, Currency, price list, warehouse, UOM, tax handling, line ship-to and bill-to, default from the customer, order type and item when left empty.

Set Order Action to Book to book the order after the upload, or to Cancel to cancel the order and all its lines; cancelling requires a Header Change Reason.

Customer Contact lists the active contacts of the customer account that are valid for the operating unit. Customer Contact Number is only needed when several contacts of the customer share the Customer Contact name; without it, such a name resolves to an account level contact before a site level one, and then to the contact created first. On a line, Override ATP = Yes schedules the line on the Schedule Ship Date without checking availability. It requires a Schedule Ship Date and the profile OM: Authorized To Override ATP, and Yes is offered only when that profile is Yes. On an order with date type Arrival, scheduling is driven by the Schedule Arrival Date and the Schedule Ship Date cannot be changed.

Split a line: add a row for the order with the line to split in Split From Line and the new shipment’s quantity in Ordered Quantity. Optionally give the new shipment its own Line Request Date, Line Warehouse or Line Ship To; all other values are copied from the original line, as in the Split Line window. The original line is reduced by the split quantity, unless its own row sets its new quantity, in which case the quantities must add up to the original quantity. For example, line 1.1 with 10 units and a new row with Split From Line 1.1 and Ordered Quantity 4 results in line 1.1 with 6 units and a new line 1.2 with 4 units. Add one row per further shipment with the same Split From Line.

Step 4 – Validate and Save

Click Validate and Save. This checks for missing required values and the upload’s rules (change reason for a cancel, tax exempt reason for exempt tax handling, discount modifier for a price override) and saves the file. Correct any rows it flags before uploading.

Step 5 – Upload the file

In Blitz Report click Upload and select the saved file. This submits the upload request, which creates, updates, splits, books or cancels each order. All rows of one order are processed together.

Step 6 – Review the result report

When the request completes, a result report opens listing every uploaded row with its status and message, and the order number and line number of new orders and lines.

What’s produced

New sales orders with their lines, and updated orders; lines split, orders booked or cancelled as requested.
A result report listing every row with a status (success or error) and a message. A new shipment shows its new line number, for example 1.2.

Common questions

How do I put several lines on one order?
Give all those rows the same Upload Order Identifier. The header columns are read from the first row of the order.

What happens if one line of an order fails?
The whole order is rolled back and all its rows show the Oracle error message, so no partial order is left. Correct the data and upload the order again.

Why did the selling price change after I changed the quantity?
With Calculate Price set to Calculate Price, Oracle reprices the line when it changes, applying the price list and automatic modifiers for the new quantity, as in the Sales Orders form.

Why must I enter a Discount Modifier when I change the selling price?
A manual price override must be backed by a price adjustment so it is auditable, as the Sales Orders form requires. Choose the modifier in Discount Modifier and, if it has several lines, the line in Discount Line.

How do I cancel an order?
Set Order Action to Cancel and enter a Header Change Reason. This cancels the order and all its lines. Orders are never deleted.

Which lines can be split?
Open lines of standard, model and kit items that are not yet shipped; Split From Line lists them. As in the Sales Orders form, Oracle does not split a line that is already pick confirmed or staged.

Can a new shipment get a different request date, warehouse or ship-to?
Yes, on Oracle EBS R12. On EBS 11i a new shipment always takes these from the original line; change them with a normal update after the split.

Troubleshooting

Message	Cause	What to do
Operating Unit “…” not found	The operating unit name is not recognised.	Pick the Operating Unit from the list.
Header Change Reason is required when Order Action is Cancel.	Cancel without a reason.	Enter a Header Change Reason, and optionally Header Change Comments.
Header Tax Exempt Reason is required when Header Tax Handling is Exempt. Line Tax Exempt Reason is required when Line Tax Handling is Exempt.	Tax handling Exempt without a reason.	Enter the corresponding Tax Exempt Reason.
Discount Modifier is required when Unit Selling Price differs from Unit List Price (price override needs an audit trail).	A manual price override without a modifier.	Choose a Discount Modifier, or set the selling price equal to the list price.
Discount Line does not identify a single modifier line of Discount Modifier …	The modifier has several lines and none or a wrong one is selected.	Pick the line from the Discount Line list.
Unit List Price cannot be zero when the Discount Modifier line applies a percentage.	A percentage discount on a zero list price.	Use an amount or new price modifier line, or enter the list price.
Line … does not exist on this order. Leave Line empty for a new line, or enter the line to split in Split From Line.	A Line number typed on a row that does not match an existing line.	Clear Line for a new line, or use Split From Line to split.
Line … is updated by more than one row. To split it, enter … in Split From Line on the rows for the new shipments.	A copied row still updates the same line.	Enter the line in Split From Line on the copied row.
The split quantity … of line … must be less than its ordered quantity …	The new shipments together are as large as the original line or larger.	Reduce the split quantities so that some quantity remains on the original line.
Split quantities must sum up to orginal quantity.	The original line’s row sets a new quantity that does not add up with the new shipments to the original quantity.	Correct the quantities, or leave the original row unchanged so it is reduced automatically.
You are not allowed to split … because: …	Oracle does not split a line once it is pick confirmed or staged.	Split lines before they are pick released.
Processed, but … failed: …	The order was saved but the Book action failed, for example because a required booking field is missing.	Complete the field named in the message and upload again with Order Action Book.
Any other Oracle Order Management message	The API rejected the order data, for example an invalid item, customer or site.	Read the message, correct the field and upload the order again; the order was rolled back.