Importing Sales Orders and/or Returns [ID 199281.

1]
Modified 21-JUN-2010 Type BULLETIN Status PUBLISHED
"Checked for relevance on 21-JUN-2010"
PURPOSE:
To aid the users of Oracle Order Management.
SCOPE & APPLICATION:
To assist all users of Order Import within Oracle Order Management
IMPORTING SALES ORDERS AND/OR RETURNS :
Order Import is an open interface owned by Oracle Order Management. Order Impor
t
consists of interface tables and a set of APIs. You can import new, change and
completed sales orders or returns from legacy applications, EDI Transactions
processed through the Gateway, or internal orders created from Oracle Purchasing
's
internal requisitions, or returns. In addition, Order Import provides forms
that allow you to query orders from the interface tables, make corrections or
changes to the date, and re-initiate the import process. Messages are provided
to give you the details why the order did not import.

The features of Order Import include validation and defaulting, processing

constraint checks, applying and releasing of order holds, shipment scheduling,
then ultimately inserting, updating or deleting the orders in the base Order
Management tables. All data is checked for validity during the import process.
Order Import uses the Process Orders API to validate and process order date in
the interface tables. Valid transactions are converted into orders with lines,
reservations, price adjustments and sales credits.

You can use the Error Message window to determine if your data failed the import
process. If the data failed to import, you can use the Order Import Corrections
window, a new feature in release 11i, to examine and correct the data.

The following parameter and profile options must be defined in order to use
Order Import.

Order Management System Parameter:

- OM: Item Validation Organization

Order Management Profile Options:

- OM: Reservation Time Fence
- OM: Apply Automatic Attachments

You can import orders in an entered, booked or closed status. If an order is

imported as booked, the order is automatically eligible to progress to the next
step the the workflow. If any of the fields required for a booked order are not
supplied then Order Management places the order in an entered states and notifie
s
you of the error.
You can indicate whether you want to manually enter prices for imported orders
or allow Order Management to automatically price the order.
If you want to use automatice pricing, set the column OE_LINES_INTERFACE.
CALCULATE_PRICE_FLAG to Calculate Price. All pricing information must be
set up in Oracle Pricing and Order Management.
If you want to use manual pricing, set the column OE_LINES_INTERFACE.
CALCULATE_PRICE_FLAG to Freeze Price.
If you want the system to only calculate Freight Charges, set the column
OE_LINES_INTERFACE.CALCULATE_PRICE_FLAG to Partial Price.
Order Import can also perform a price comparison on your imported orders. For
example, you can provide a selling price and also have the system calculate a
price. Order Import will WARN you of any differences. Please see table 24-1
in the Oracle Order Management Implementation Manual for examples of differences
in the customer price and system price and how the Calculate Price Flag affects
the process.
You can run the Order Import process in validation-only mode. This mode allows
the transaction to be validated against all of the Order Management rules but
does not pass any valid transactions into the Order Management tables.
The Order Import window consists of the Find and Summary windows. The Find
window allows you to find orders to be imported based on certain attributes
such as Request ID, Order Source, Original System, Document Reference and Change
sequence.
The summary window displays order headers, lines, sales credits, price
adjustments, lot serial numbers, reservations and action requests. You can
use Oracle Application Folder functionality to limit or display fields.
You can perform the following actions from this form:
- modify orders.
- insert, update and delete the orders and lines in the interface tables.
- update one or multiple orders or lines at the same time using the
multi-select functionality.
- mark an order or line to be rejected by setting the rejected flag.
- submit a request by selecting Order Import Request and select the
appropriate parameter and choose Submit.
Order Import has the following paramters
1. Order Source
2. Order Reference
3. Validate Only
4. Processing Results
Customer items numbers or UPC numbers can be entered in Order Import the same
way as a manually entered sales order as long as all cross-reference data is
defined before the order import process is run. Set the OE_LINES_IFACE_ALL.
CUSTOMER_ITEM_NAME to the 'item ordered'. If you know what kind of item
number it is (for example customer or inventory), you can set the
OE_LINES_IFACE_ALL.CUSTOMER_ITEM_TYPE.
You can import changes and cancellations to existing imported orders by setting
the OPERATION_CODE in each of the interface tables. A NULL value is equivalent
to INSERT. If you want to make changes, use an OPERATION_CODE of UPDATE. To
cancel a line set the OPERATION_CODE to UPDATE and make ordered quantity = 0.
To cancel an order in its entirety, set the OPERATION_CODE at the Header to
UPDATE and set the CANCEL_FLAG to Y.
Import sales order returns just like you import standard orders choosing an
order type that supports return line types. You can also import mixed orders,
orders which have both standard sales order lines and return order lines.
To import orders you will need to load the Order Import Interface Tables.
In most situations, you will develop a program or script to convert data from
the feeder system into the standard format that Order Import is expecting. You
can import orders with any external source defined in the Define Document
Sequences window.
Oracle Purchasing contains a program, Create Internal Sales Orders, that takes
the data from the Purchasing schema for internal requisitions and loads the
Order Import tables. The eCommerce Gateway also provides a program, Purchase
Order Inbound, that loads the import tables for the Inbound Purchase Order EDI
transactions set.
It is recommended that you set up Defaulting Rules in Order Management that will
default as much of the order and line information as possible for you
environment. This will reduce the amount of data that needs to be populated
into the Order Management Interface tables. Please review Note 198900.1 for
comprehensive information detailing the definition of Defaulting Rules.
Please tables 2-1 through 2-10 for all required columns and settings.