Internal Sales Orders

8/17/2019 Internal Sales Orders

1/9

CREATION OF INTERNAL SALES ORDERS

Once you approve inventory sourced requisition lines, Purchasing translates therequisition into an internal sales order.

You run two separate batch processes to create the internal sales order from theapproved requisition:

Create Internal Sales Orders. Order Import.

Purchasing uses location associations to create internal sales orders from internalrequisitions 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 thedeliver-to point, Purchasing uses the associated customer and customer site on theinternal sales order that it creates. The associated customer site becomes the ship-tosite 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 fromapproved, inventory-sourced requisition lines to the Order Management interface tables.Then the Order Import process is run from within Order Management to generate theinternal sales orders. You can set the Create Internal Sales Orders and Order Importprocesses 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 onthe internal requisition line, Order Management reserves the goods and uses only thespecified sub-inventory for allocation. If the goods do not exist at the specifiedsub-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 fromthe records in the interface table, and determines the order cycle and defaults valuesbased 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.


2/9

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 Optionswindow.

Attention: The following two fields are enterable only when the formis 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 OracleOrder Management is installed. Order types are defined in Order Management. The order type you choose here is the type that Purchasinguses to create sales orders from internal requisitions.

3. Select the default Order Source for internal requisitions. Purchasing defaultsand only uses Internal.

This is the source. Order Import uses to transfer internal requisitionsfrom 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 tooccur each time the Order Import concurrent program was submitted. With this releaseof Order Management, the analysis of the Order Import interface tables no longer occursfor each submission of the Order Import concurrent program; you must manually submitthe Order Import Statistics concurrent program prior to submitting the Order Importconcurrent 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 interfacetables and a set of APIs. Order Import can import new, change, and completed salesorders or returns from other applications such as a legacy system. The orders may comefrom any source such as EDI transactions that are processed by the Oracle

e-Commerce Gateway or internal orders created for internal requisitions developed inOracle 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


3/9

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 andoptionally correct data if it fails the import process. You can use the Error Messagewindow 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 ordersthat 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 importedorders, including customers, pricing, items, and bills

Define and enable your Order Import sources using the Order Import Sourceswindow

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 reservationsduring 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 wayas for orders entered on-line. You can pass the column value Null to Order Import if youwant the defaulting rules to populate the column. However, if the column is defined asNot Null or Mandatory column and the defaulting rules fail to default the column, for anyreason, Order Import displays an error message without importing the order.

Internal Sales Orders:

Oracle Purchasing uses Order Import to transfer requisitions for internally sourcedproducts to Order Management. Once imported, the internal sales orders are processedsimilar to regular sales orders.

Note: When importing internal sales orders that contain order line items that requireserial numbers, Order Import requires the associated items serial control attribute be set


4/9

to: Dynamic at Sales Order Issue. You can create requisitions (with same number) in twodifferent 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 wantselected. 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 APIsand Open Interfaces Manual.

For EDI orders, you can import valid and invalid configurations, however, you will not beable to book orders with invalid configurations.

Changes:

You can import changes to orders that have been imported by passing all changed datathrough 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 changesequence 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 toprovide the set ID or name in the Order Import tables. If that set already exists, the linewill be included in the set.

However, if the set does not already exist, a new set will be created and the line will beadded to the set. In addition, if any line attribute, which is also a set attribute, does notmatch 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 statusof Booked, the order is automatically eligible to progress to the next step in the workflowcycle.

Order Import ensures that all required fields for entry or booking are validatedappropriately as the orders are imported. Order Import imports the order in as Enteredand 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.


5/9

Workflows:

You can import an order within any valid order workflow activity. The order must be atthe initial activity of Entered, Booked, or Closed. Orders imported using Order Importcannot be in the middle of a workflow activity.

Items and Bills:

Order Management uses the same customer, item pricing, and bill attribute validationand 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 Managementto 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 processingconstraint that has been violated.

Corr ected 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 correctedby using the Order Import Corrections window.

Importing from External Systems:

You can import orders with any external source defined in the Order Import Sourcesform. Order Import allows you to capture order information and import data into OracleOrder Management for processing. You can import orders with any entry status.


6/9

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 theOrder Import Concurrent program. This will allow users to import all the Orders for aspecific Customer and also enable users to import an order with a specific ChangeSequence for a given Customer and Reference. These new parameters to theConcurrent 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 thecustomer will become a part of the order import key. If this profile is set to No or not setat 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 anorder 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 beassigned orders to process. Previously, while other processes may have completedalready, orders could still be waiting in the queue of a child request that was takinglonger to complete processing (perhaps because of a particularly large order). Now anorder will only be assigned to a particular child request once that request is ready toprocess it.

The default behavior of Order Import will be the new functionality, but customers will beable to revert to the old functionality when importing orders through the Order ImportConcurrent Program form by enabling the display of the new parameter "Enable SingleLine 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 windowso 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 interfacetables. This field is optional.

http://yashapps.myyash.com:8000/pls/VIS/fndgfm/fnd_help.get/US/ont/@p_impstat#p_impstathttp://yashapps.myyash.com:8000/pls/VIS/fndgfm/fnd_help.get/US/ont/@p_impstat#p_impstat


7/9

3. Order References: You can enter the System Document Reference if you want torun Order Import for a specific order. This field is optional.

4. Validate Only (Yes/No): Choose whether to validate only the data in the interfacetables. If Yes, the order will be validated, but not imported into the base orderstables. 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 successfuland failed imported orders.

Multi-Org: Creation of Internal Sales Orders Across Operating Units:

A Multi-Org implementation of Purchasing enables separate operating units within anorganization to operate independently of each other. However, you may still need toobtain goods from another operating unit, and Purchasing supports this. You can createan internal sales order for an item in another operating unit. When creating this internalsales order, you must create it in the destination organization's operating unit, and allOrder Management activity must take place within that destination operating unit. For example, the following table lists the generalized steps involved and indicate theorganization in which they take place.

Step ActionOperating Unit 1Inventory Org A

Operating Unit 2Inventory Org B

1 Create and approve internalrequisition.

X

2 Run Create Internal Sales Orders. X

3 Run Order Import in Order.Management

X

4 Perform pick release and shipconfirm in Order Management.

X

5 Receive goods. X

When you use internal sales orders to transfer goods from another operating unit, theitems' transfer cost is posted to the intercompany payables and receivables accounts asdefined 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 internalsales 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.

http://rapidyash.myyash.com:8000/pls/VIS/fndgfm/fnd_help.get/US/PO/@t_dpoint@PSA_US#t_dpoint@PSA_UShttp://rapidyash.myyash.com:8000/pls/VIS/fndgfm/fnd_help.get/US/PO/@t_dpoint@PSA_US#t_dpoint@PSA_US


8/9

You must perform the following setups in Order Management to use the internalrequisition features. You may choose to take advantage of other Order Managementfeatures which require additional setups. See: Oracle Order ManagementRecommended 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 theitem 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 SystemOptions 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 organizationas 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 Managementprovides default order cycle workflows that you must associate with each order and linetype. See: Defining Transaction Types, Oracle Order Management ImplementationManual .

Define an Order Management Number Source For Internal Requisitions:

Define order number sources to automatically number internal sales orders as youimport them. You can use a single order number source to assign unique numbers to allyour 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 Managementrequires price lists to process all sales orders. Define a price list for use with the internalrequisition order type. You do not need to add any lines to the price list. See: Defining aPrice 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 salesorders. Confirm that the default value rules that Order Management provides suit your

http://rapidyash.myyash.com:8000/pls/VIS/fndgfm/fnd_help.get/US/ar/@t_actops@PSA_US#t_actops@PSA_UShttp://rapidyash.myyash.com:8000/pls/VIS/fndgfm/fnd_help.get/US/PO/..@PSA_US#@PSA_UShttp://rapidyash.myyash.com:8000/pls/VIS/fndgfm/fnd_help.get/US/PO/..@PSA_US#@PSA_UShttp://rapidyash.myyash.com:8000/pls/VIS/fndgfm/fnd_help.get/US/ar/@t_actops@PSA_US#t_actops@PSA_US


9/9

enterprise needs. If not, use the Defaulting Rules window to modify them. See: DefiningDefault 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 adefault Account Generator process to be used in determining the COGS Account duringthe Inventory Interface process.You can either accept the default COGS Account Generator process or customize it tosuit your enterprise needs. For more information on how to accept or customize thisfeature, see the Oracle Order Management documentation.

Internal Sales Orders Processing Constraints (Optional):

Order Management processing constraints apply to all your sales orders, includinginternal sales orders imported from Purchasing. Processing constraints prevent usersfrom adding, updating, deleting and canceling order information beyond certain points in

the order cycles. You can use the System rules Order Management provides, whichprevent data integrity violations, or define your own, stricter, rules. See: DefiningProcessing Constraints, Oracle Order Management Implementation Manual .

Documents

Internal Sales Orders