CREATION OF INTERNAL SALES ORDERS

Once you approve inventory sourced requisition lines, Purchasing translates the
requisition into an internal sales order.
You run two separate batch processes to create the internal sales order from the
approved requisition:
Create Internal Sales Orders.
Order Import.
Purchasing uses location associations to create internal sales orders from internal
requisitions for a given deliver-to location. When you associate a customer and customer
site with a location and then enter an internal requisition with that location as the
deliver-to point, Purchasing uses the associated customer and customer site on the
internal sales order that it creates. The associated customer site becomes the ship-to
site for Order Management's ship confirmation.
Note: You should not drop-ship internal sales orders. See: Drop Shipments.
CREATE INTERNAL SALES ORDERS PROCESS:
Use the Create Internal Sales Orders process to send requisition information from
approved, inventory-sourced requisition lines to the Order Management interface tables.
Then the Order Import process is run from within Order Management to generate the
internal sales orders. You can set the Create Internal Sales Orders and Order Import
processes to run automatically at specified intervals.
Internal orders are automatically scheduled by setting the Schedule Ship Date on the
sales order to the Need-by Date from the requisition. If you specify a sub-inventory on
the internal requisition line, Order Management reserves the goods and uses only the
specified sub-inventory for allocation. If the goods do not exist at the specified
sub-inventory, Order Management backorders them, even if they do exist in another
sub-inventory.
The Create Internal Sales Orders process loads the Order Management open interface,
Order Import, using the order type you define in the Purchasing Options window. See:
Defining Internal Requisition Options. Order Import creates internal sales orders from
the records in the interface table, and determines the order cycle and defaults values
based on the order type.
To run the Create Internal Sales Orders process:
1. Navigate to the Submit Requests window.
2. Select Requests in the first field.
3. Select Create Internal Sales Orders in the Name field.

4. Choose Submit to begin the process

DEFINING INTERNAL REQUISITION OPTIONS:
To define internal requisition options:
1. Navigate to the Internal Requisition tabbed region in the Purchasing Options
window.
Attention: The following two fields are enterable only when the form
is accessed from the Purchasing menu.
2. Select the default Order Type for internal requisitions.
Attention: The Order Type field is visible only if the application Oracle
Order Management is installed. Order types are defined in Order
Management. The order type you choose here is the type that Purchasing
uses to create sales orders from internal requisitions.
3. Select the default Order Source for internal requisitions. Purchasing defaults
and only uses Internal.
This is the source. Order Import uses to transfer internal requisitions
from Purchasing to Order Management.
4. Save your work.
ORDER IMPORT:
Prior to this release, Order Management would analyze Order Import interface tables for
related records to determine the optimum record processing order; the analysis used to
occur each time the Order Import concurrent program was submitted. With this release
of Order Management, the analysis of the Order Import interface tables no longer occurs
for each submission of the Order Import concurrent program; you must manually submit
the Order Import Statistics concurrent program prior to submitting the Order Import
concurrent program if you wish to optimize interface record processing. See: Order
Import Concurrent Program.
Order Import is an Order Management Open Interface that consists of open interface
tables and a set of APIs. Order Import can import new, change, and completed sales
orders or returns from other applications such as a legacy system. The orders may come
from any source such as EDI transactions that are processed by the Oracle
e-Commerce Gateway or internal orders created for internal requisitions developed in
Oracle Purchasing or returns.
Order Import features include validation and defaulting, processing constraint checks,
applying and releasing of order holds, scheduling of shipments, then ultimately inserting,
updating or deleting the orders in the base Order Management tables. Order
Management checks all the data during the import process to ensure its validity within

Order Management. Valid transactions are then converted into orders with lines,
reservations, price adjustments, and sales credits in the base Order Management tables.
You can use the Order Import Correction Payments window to examine the order and
optionally correct data if it fails the import process. You can use the Error Message
window to determine if your data failed to import.
Each time you run Order Import, Order Management produces a summary log file
(concurrent request form) of information letting you know of the total number of orders
that Order Import evaluates, and succeeded or failed.
Prerequisites and Set-Up:
Before using this program to import orders, you should:
Set up every aspect of Order Management that you want to use with imported
orders, including customers, pricing, items, and bills
Define and enable your Order Import sources using the Order Import Sources
window
Determine if you should submit the Order Import Statistics concurrent program
Order Management System Parameter:
The following parameter affects the operation of the Order Import program:
OM: Item Validation Organization: Determines the organization used for
validating items and bill of material structures
Profile Options:
OM: Reservation Time Fence: This profile option controls automatic reservations
during scheduling
OM: Apply Automatic Attachments: This profile option determines whether
rule-based attachments are applied without user intervention
Defaulting Rules:
You can setup your defaulting rules which allow you to default columns in the same way
as for orders entered on-line. You can pass the column value Null to Order Import if you
want the defaulting rules to populate the column. However, if the column is defined as
Not Null or Mandatory column and the defaulting rules fail to default the column, for any
reason, Order Import displays an error message without importing the order.
Internal Sales Orders:
Oracle Purchasing uses Order Import to transfer requisitions for internally sourced
products to Order Management. Once imported, the internal sales orders are processed
similar to regular sales orders.
Note: When importing internal sales orders that contain order line items that require
serial numbers, Order Import requires the associated items serial control attribute be set

to: Dynamic at Sales Order Issue. You can create requisitions (with same number) in two
different operating units.
Returns:
Returns can be imported like a regular sales order. Once imported, RMAs orders and
lines are processed using the Return specific Oracle Workflows.
Configurations:
Order Management provides you with the ability to import ATO and PTO configurations.
You must supply an order line for the model and an order line for each option you want
selected. Top model line ref need to be populated for all lines including the model line for
importing configurations.
For more information on importing Configurations, see Oracle Order Management APIs
and Open Interfaces Manual.
For EDI orders, you can import valid and invalid configurations, however, you will not be
able to book orders with invalid configurations.
Changes:
You can import changes to orders that have been imported by passing all changed data
through Order Import or simply make changes in the Order Pad. You can update or
delete orders, order lines, price adjustments, and sales credits. You can use change
sequence numbers to control the sequence of changes you want to make to orders.
Line Sets:
You can import grouped order lines, called sets, based on certain common attributes for
a new or existing orders. You can also add a line to an existing set. You will need to
provide the set ID or name in the Order Import tables. If that set already exists, the line
will be included in the set.
However, if the set does not already exist, a new set will be created and the line will be
added to the set. In addition, if any line attribute, which is also a set attribute, does not
match with the set attribute value, the set attribute value will overwrite the line attribute.
Order Status:
You can import new, booked or closed orders. If an order is imported with an entry status
of Booked, the order is automatically eligible to progress to the next step in the workflow
cycle.
Order Import ensures that all required fields for entry or booking are validated
appropriately as the orders are imported. Order Import imports the order in as Entered
and attempts to book it. If any of the required fields for a booked order are not supplied,
Order Management retains the order in the Entered status and notifies you of the error.

Workflows:
You can import an order within any valid order workflow activity. The order must be at
the initial activity of Entered, Booked, or Closed. Orders imported using Order Import
cannot be in the middle of a workflow activity.
Items and Bills:
Order Management uses the same customer, item pricing, and bill attribute validation
and logic for imported orders as for orders entered in the Sales Orders window.
You need to define items using Oracle Inventory for items to be orderable via Order
Import. You also need to define bills of material in Oracle Bills of Material for models if
you have any complex items that customers can order in various configurations.
Order Import provides the ability to import an item specified in the following supplier,
customer or generic formats:
Supplier Specific Internal Part number
Customer Specific Item number
Generic (depending on what you have set up in Oracle Inventory as
cross-references):
CLEI (Common Language Equipment Identifier)
EAN (European Article Number) code
ISBN (International Standard Book Number)
JAN (Japanese Article Number) code
UPC (Universal Product code) code
Processing Constraints:
Order Import checks the processing constraints you have defined in Order Management
to assure that any operation such as insert, update, and delete are acceptable by your
security standards. Order Import displays an error message if it encounters a processing
constraint that has been violated.
Corrected Data:
Once the data is corrected, the ERROR_FLAG for the record is updated to N. You can
set the REJECT_FLAG to Y for headers and line in case your data cannot be corrected
by using the Order Import Corrections window.
Importing from External Systems:
You can import orders with any external source defined in the Order Import Sources
form. Order Import allows you to capture order information and import data into Oracle
Order Management for processing. You can import orders with any entry status.

Imported orders can be queried and modified using the Sales Order window in Order
Management.
Importing Order Statistics:
If you wish to import order statistics, submit the Order Import statistics concurrent
program.
See: Order Import Statistics Concurrent Program.
Key Change Project:
Sold To Org Id, Sold To Org, and Change Sequence are now parameters for running the
Order Import Concurrent program. This will allow users to import all the Orders for a
specific Customer and also enable users to import an order with a specific Change
Sequence for a given Customer and Reference. These new parameters to the
Concurrent program will be enabled, but will not be displayed by default.
The functionality is controlled via a new profile option called OM: Unique Order Source,
Orig Sys Document Ref Combination For Each
Customer. If this profile is set to Yes the new functionality will be turned on and the
customer will become a part of the order import key. If this profile is set to No or not set
at all (default) order import will function as it did previously.
Performance Enhancement:
With the introduction of the new queueing method, Order Import will now only assign an
order to a child request once that request has finished processing its previous order.
This will help to maximize throughput as available child processes will always be
assigned orders to process. Previously, while other processes may have completed
already, orders could still be waiting in the queue of a child request that was taking
longer to complete processing (perhaps because of a particularly large order). Now an
order will only be assigned to a particular child request once that request is ready to
process it.
The default behavior of Order Import will be the new functionality, but customers will be
able to revert to the old functionality when importing orders through the Order Import
Concurrent Program form by enabling the display of the new parameter "Enable Single
Line Queue" and changing the value from the default of Yes to No.
To import Orders or Returns:
1. Navigate to the Import Orders Concurrent Program Parameters window.
2. The Order Import Parameters window displays. Order Source, Choose a specific
Order Import source that you have defined in the Order Import Sources window
so that only records with that source are processed, or leave this parameter
blank so that all enabled sources are processed for data existing in the interface
tables. This field is optional.

3. Order References: You can enter the System Document Reference if you want to
run Order Import for a specific order. This field is optional.
4. Validate Only (Yes/No): Choose whether to validate only the data in the interface
tables. If Yes, the order will be validated, but not imported into the base orders
tables. The default value is No. This field is required.
5. Instances: This field is optional.
6. Select Ok, then Submit.
Processing Results:
Each time you run Order Import, Order Management automatically generates an Order
Import processing results summary log which identifies the total number of successful
and failed imported orders.
Multi-Org: Creation of Internal Sales Orders Across Operating Units:
A Multi-Org implementation of Purchasing enables separate operating units within an
organization to operate independently of each other. However, you may still need to
obtain goods from another operating unit, and Purchasing supports this. You can create
an internal sales order for an item in another operating unit. When creating this internal
sales order, you must create it in the destination organization's operating unit, and all
Order Management activity must take place within that destination operating unit. For
example, the following table lists the generalized steps involved and indicate the
organization in which they take place.
Operating Unit
Inventory Org A

Step Action
approve

1 Operating Unit
Inventory Org B

Create
and
requisition.

Run Create Internal Sales Orders.

Run Order
Management

Order.

Perform pick release and ship

confirm in Order Management.

Receive goods.

Import

in

internal X
X

When you use internal sales orders to transfer goods from another operating unit, the
items' transfer cost is posted to the intercompany payables and receivables accounts as
defined in the shipping network and an intercompany invoice can be generated. See:
Inter-Organization Shipping Network, Oracle Inventory User's Guide.

Minimum Order Management Setup for Internal Requisitions:

You use standard sales order functionality to define transaction types for internal
sales orders. You also need to use the Purchasing Options window to specify the order
type you use for internal requisitions. See: Defining Internal Requisition Options.

You must perform the following setups in Order Management to use the internal
requisition features. You may choose to take advantage of other Order Management
features which require additional setups. See: Oracle Order Management
Recommended Setup, Oracle Order Management Implementation Manual.

Define Order Management Profile Options:

Set the profile option OM: Item Flexfield. This profile option defines which structure of the
item flexfield to use. See: Order Management Profile Options, Oracle Order
Management Implementation Manual.
Note that Order Management uses the same set of books as defined in the System
Options window in Oracle Receivables. See: Accounting System Options.
Use the Parameters window in Order Management to define the Item Master
organization for this installation.
Suggestion: Set the Item Validation Organization to the same Item Master organization
as your purchasing reference organization (set in the Financials Options window). See:
About Financials Options.
Define Transaction Types:
Use the Transaction Types window to define order and line types. Order Management
provides default order cycle workflows that you must associate with each order and line
type. See: Defining Transaction Types, Oracle Order Management Implementation
Manual.
Define an Order Management Number Source For Internal Requisitions:
Define order number sources to automatically number internal sales orders as you
import them. You can use a single order number source to assign unique numbers to all
your orders, or you can use a different order number source within each order type. See:
Defining Order Number Sources, Oracle Order Management Implementation Manual.
Define a Price List For Internal Requisition:
Although internal requisitions use the item's cost as the price, Order Management
requires price lists to process all sales orders. Define a price list for use with the internal
requisition order type. You do not need to add any lines to the price list. See: Defining a
Price List, Oracle Order Management Implementation Manual.
Decide which Default Value Rules to Use:
Default value rules define the defaulting that occurs as orders are entered or imported.
Order Management provides default value rules that you can use for internal sales
orders. Confirm that the default value rules that Order Management provides suit your

enterprise needs. If not, use the Defaulting Rules window to modify them. See: Defining
Default Value Rules, Oracle Order Management Implementation Manual.
Define Inventory Accounting (Account Generator):
Order Management can dynamically create the Cost of Goods Sold (COGS) Account for
each shipped or returned item based on rules you define. Order Management provides a
default Account Generator process to be used in determining the COGS Account during
the Inventory Interface process.
You can either accept the default COGS Account Generator process or customize it to
suit your enterprise needs. For more information on how to accept or customize this
feature, see the Oracle Order Management documentation.
Internal Sales Orders Processing Constraints (Optional):
Order Management processing constraints apply to all your sales orders, including
internal sales orders imported from Purchasing. Processing constraints prevent users
from adding, updating, deleting and canceling order information beyond certain points in
the order cycles. You can use the System rules Order Management provides, which
prevent data integrity violations, or define your own, stricter, rules. See: Defining
Processing Constraints, Oracle Order Management Implementation Manual.