Oracle Order Management - Setup Steps

Step 1: Define Flexfields

Define key and descriptive flexfields to capture additional information about orders and transactions.
This step is required for Key Flexfields, and optional if you plan on using the
functionality surrounding Descriptive Flexfields. Several defaulting values are
provided.

Step 2: Multiple Organizations

Define multiple organizations in Oracle Inventory. This step is optional.

Step 3: Inventory Organizations

Define inventory organizations (warehouses), parameters, subinventories, and
picking rules in Oracle Inventory. You must define at least one item validation organization and at least one organization that acts as an inventory source for orders fulfilled internally.

If you plan to drop ship some orders, you must also define at least one logical
organization for receiving purposes. Your item validation organization can be the same as your inventory source or your logical receiving organization, but you cannot use one organization for all three purposes.

This step is required.

Step 4: Profile Options

Define profile options to specify certain implementation parameters, processing options, and system options. This step is required.

Step 5: Parameters

Set your Order Management Parameters to validate items, enable customer
relationships, and operating unit defaults. This step is required.

Step 6: Invoicing

Define invoicing information, including payment terms, invoicing and accounting rules, Autoaccounting parameters, territories, and invoice sources.
This step is required if you plan on transferring invoicing information to Oracle
Receivables. Several defaulting values are provided.

Step 7: Salespersons

Define information on your sales representatives. This step is optional.

Step 8: Tax

Define tax features, such as codes, rates, exceptions, and exemptions.
This step is required.

Step 9: QuickCodes

Define QuickCodes that provide custom values for many lists of values throughout Order Management. This step is required if you plan on creating user defined Quickcodes for utilization within Order Management. Defaulting values are provided.

Step 10: Workflow

Define order and line processing flows to meet different order and line type
requirements. This step is required.

Step 11: Document Sequences (Order Numbering)

Define Document Sequences for automatic or manual numbering of orders. This step is required.

Step 12: Order Import Sources

Define sources for importing orders into Order Management. This step is required if you plan on importing orders or returns into Order Management.

Step 13: Units of Measure

Define the units of measure in which you supply items. This step is required.

Step 14: Item Information

Define item information, including item attribute controls, categories, and statuses. This step is required.

Step 15: Items

Define the items that you sell, as well as container items. This step is required.

Step 16: Configurations

Define the configurations that you sell. This step is required if you plan on generating orders or returns for configured items. Several defaulting values are provided.

Step 17: Pricing

Define price lists for each combination of item and unit of measure that you sell. Optionally, you can define pricing rules and parameters to add flexibility. This step is required.

Step 18: Customer Classes

Define customer profile classes. This step is required if you plan on using the functionality surrounding Customer Profiles. Several defaulting values are provided.

Step 19: Customers

Define information on your customers. This step is required.

Step 20: Item Cross References

Define item cross references for ordering by customer part number, UPC, or any generic item number. This step is required if you plan on using the functionality surrounding item cross referencing. Several defaulting values have been provided.

Step 21: Sourcing

Define your sourcing rules for scheduling supply chain ATP functions. This step is optional.

Step 22: Order Management Transaction Types (Order and Line Types)

Define Order Management transaction types to classify orders and returns. For each order type, you can assign a default price list, defaulting rules, order lines, return lines, line types, workflow assignments, payment terms, and freight terms. This step is required.

Note: Order Management provides NO seeded OM transaction types. For existing Oracle Order Entry customers, Order Management will update existing Order Types to OM transaction type during the upgrade process.

Step 23: Cost of Goods Sold (COGS)

Set up your Cost of Goods Sold Accounting Flexfield combination (COGS Account) in Oracle Inventory. This step is required if you plan on utilizing the functionality surrounding COGS.

Step 24: Processing Constraints

Define processing constraints to prevent users from adding updating, deleting,
splitting lines, and cancelling order or return information beyond certain points in your order cycles. Use the constraints Order Management provides, which prevent data integrity violations, or create your own. This step is optional. Several default values for processing constraints have been defined.

Step 25: Defaulting Rules

Define defaulting rules to determine the source and prioritization for defaulting
order information to reduce the amount of information you must enter manually in the Sales Orders window. This step is optional. Several Defaulting rules and corresponding values for have been defined.

Step 26: Credit Checking

Define your credit checking rules. This step is required if you plan on performing any type of order credit checking.

Step 27: Holds

Define automatic holds to apply to orders and returns. This step is required if you plan on performing automatic hold for orders or returns.

Step 28: Attachments

Define standard documents to attach automatically to orders and returns. This step is optional.

Step 29: Freight Charges and Carriers

Define freight charges and freight carriers to specify on orders. This step is required if you plan on charging customers for freight or additional order charges.

Step 30: Shipping

Define shipping parameters in Oracle Shipping Execution. This step is required.

Oracle Order Management - Credit Checking Setup in Order Management

Credit Checking Setup in Order Management

In order to trigger automatic Credit checking on sales orders it is necessary that the credit checking is enabled for the order type, customer profile and payment terms associated with the transaction.
Credit check set up involves the following setup steps:

Step1:Credit Check Rules Setup
Step2:Customer Profiles Setup
Step3:Payment Terms Setup
Step4:Order Types Setup

If any one of order type, customer profile and payment terms does not have credit checking enabled, the sales order will not be credit checked . Sales orders that pass credit check at all the three points are allowed to progress normally. Those that fail will have credit check failure hold placed on either the order header or order lines.

Step 1 : Credit Check Rules Setup
(N) Setup->Rules->Credit

In the rules window enter Name of Credit Check Rule .
In the effective dates field enter today’s date(optional) as the starting date and leave the end date as blank.
In the credit check level drop down list, Select Sales order.
In the Credit hold level drop down list select the Sales order option.
Choose the conversion type as corporate.
Accept all other defaults and save your rule and close the window.

Step 2 : Customer Profiles Setup
(N) Customer->Standard

Enter the customer name or Number and Click on OK to open the customer.
In the Addresses tab, select the address for the bill to site that you want to enable credit checking and click on the Open button.

As per Note 365866.1, the conditions for the site level credit
check is as follows
After 11.5.10 CU2.
* If Credit Check not enabled(site level) => No Credit Check
* If Credit Check is enabled and both credit limit and order credit limit are NULL/BLANK => Go for Customer level
* If Credit Check is enabled and either credit limit or order credit limit is NOT NULL => Use them
In (T) Profile: Transaction ensure the Credit Check box is checked

In (T) Profile: Amounts, '''select the currency USD''' and change the order credit limit to 5000

Step 3 :Payment Terms Setup
(N) Setup->Orders->Payment Terms

Query for the Payment Term 30 Net and ensure that the credit check check box is selected.
Save your work and exit the form.

Step 4 :Order Types Setup
(N) Setup->Transaction Types->Define

Query for the Transaction Type Mixed and once the record is retrieved choose the credit check rule
Enter the name of credit check rule created in the previous step in the credit check rule region in the ordering field.
This indicates that when the order is booked, the credit check rule will be applied and when the order amount exceeds the credit limit then a hold will be applied.Save your work and close the window.

To release the credit check hold, go to Actions->Release Holds, enter a Reason,
and click on Release.

Oracle Order Management - Header and Line Statuses for Normal , Dropship and Back to back Orders

Statuses of

A.   Normal Order

B.    Drop shipment

C.    Back to back orders in Order management

NORMAL SALES ORDER STATUSES

STEP1:-ENTER THE DETAILS THEN SAVE
   
       HEADER STATUS      -->     ENTERED
       LINE STATUS        -->     ENTERED
STEP2:-BOOK THE ORDER

       HEADER STATUS      -->     BOOKED
       LINE STATUS        -->     AWAITING SHIPPING

STEP3:-GOTO SHIPPABLE->TRANSACTIONS
                     ->LINES/LPN       ACTIONS:AUTO CREATE DELIVERY      -->     GO
                     ->DELIVERY        ACTIONS:LAUNCH PICK RELEASE       -->     GO      -->     OK
                     ->REQUESTS->FIND      -->     PICK SELECTION GENERATION
                                        PICK SLIP RTEPORT
                                        SHIPPING EXCEPTION REPORT

       HEADER STATUS      -->     BOOKED
       LINE STATUS        -->     PICKED

STEP4:-GOTO SHIPPING->TRANSACTIONS
                     ->DELIVERY        ACTIONS:SHIP CONFORM      -->     GO--OK
                     ->REQUESTS->FIND      -->     BILL OF LOADING
                                                                     PACKING SHIP REPORT
                                                                             COMMERCIAL INVOICE
                                                                             VEHICLE LOAD SHETT DETAILS
                                                                             INTERFACE TRIP STAFF

       HEADER STATUS      -->     BOOKED
       LINE STATUS        -->     SHIPPED

STEP5:-NOW RUN THE WORKFLOW BACKGROUND PROCESS
                       ITEMTYPE:-OM ORDER LINE

       HEADER STATUS      -->     BOOKED
       LINE STATUS        -->     CLOSED
----------------------------------------------------------------
HEADER STATUS:-ENTERED        LINE STATUS:-ENTERED
HEADER STATUS:-BOOKED         LINE STATUS:-AWAITING SHIPPING
HEADER STATUS:-BOOKED         LINE STATUS:-PICKED
HEADER STATUS:-BOOKED         LINE STATUS:-SHIPPED
HEADER STATUS:-BOOKED         LINE STATUS:-CLOSED
----------------------------------------------------------------

DROP SHIPMENT STATUSES:

STEP1:-ENTER THE DETAILS THEN SAVE(IN SHIPPING TAB SOURCETYPE=EXTERNAL)
   
       HEADER STATUS      -->     ENTERED
       LINE STATUS        -->     ENTERED

STEP2:-BOOK THE ORDER

       HEADER STATUS      -->     BOOKED
       LINE STATUS        -->     BOOKED

STEP3:-NOW RUN THE WORKFLOW BACKGROUND PROCESS(PARAM:ITEMTYPE NULL,YES,YES)

       HEADER STATUS      -->     BOOKED
       LINE STATUS        -->     Awaiting Receipt
       (THE DETAILS MUST BE PRESENT IN REQUISITION INTEFACE TABLE)

STEP4:-NOW RUN THE REQUISITION IMPORT(PARAM:ITEMTYPE=ORDER ENTRY,ITEM,NO,YES)
       TO LOAD THE DATA INTO REQUISITION BASE TABLES

       HEADER STATUS      -->     BOOKED
       LINE STATUS        -->     Awaiting Receipt
       (THE DETAILS MUST BE PRESENT IN REQUISITION BASE TABLE)

STEP5:-NOW COPY THE SALES ORDER NUMBER
       GOTO      -->     PURCHASING      -->     REQUISITION SUMMAY->RELATEC DOCUMENTS->SALES ORDER               NUMBER->FIND->COPY REQUISITION NUMBER

       GOTO      -->     PURCHASE ORDERS->AUTO CREATE->DELETE SEARCH CRITIRIAA->ENTER REQUISITION             NUMBER->AUTOMETIC->ENTER SUPPLIER NAME->CREATE->PURCHASE ORDER WILL BE               CREATED->COPY PO NUM&APPROVE THE PURCHASE ORDER

       GOTO      -->     RECIEVING->RECIEPTS->ENTER PONUM->FIND->SUB:STORES->SAVE

       HEADER STATUS      -->     BOOKED
       LINE STATUS        -->     SHIPPED


STEP6      -->     NOW RUN THE WORKFLOW BACKGROUND PROCESS
           
       HEADER STATUS      -->     BOOKED
       LINE STATUS        -->     CLOSED
----------------------------------------------------------------
HEADER STATUS:-ENTERED        LINE STATUS:-ENTERED
HEADER STATUS:-BOOKED         LINE STATUS:-BOOKED
HEADER STATUS:-BOOKED         LINE STATUS:-AWAITING RECIEPT
HEADER STATUS:-BOOKED         LINE STATUS:-SHIPPED
HEADER STATUS:-BOOKED         LINE STATUS:-CLOSED
----------------------------------------------------------------

BACK TO BACK ORDER

STEP1:-ENTER THE DETAILS THEN SAVE(IN SHIPPING TAB SOURCETYPE=EXTERNAL)
   
       HEADER STATUS      -->     ENTERED
       LINE STATUS        -->     ENTERED

STEP2:-BOOK THE ORDER

       HEADER STATUS      -->     BOOKED
       LINE STATUS        -->     SUPPLY ELIGIBLE

STEP3:- NOW      -->     ->RIGHT CLICK ON SUPPLY ELIGIBLE->PROGESS ORDER->OK

       HEADER STATUS:BOOKED
       LINES STATUS :External Req Requested
       (THE SALES ORDER DETAILS MUST BE PRESENT IN REQUISITION INTERFACE TABLE)

STEP4:-NOW RUN THE REQUISITION IMPORT(PARAM:ITEMTYPE=CTO(CONFIGURE TO ORDER),ITEM,NO,YES)
       TO LOAD THE DATA INTO REQUISITION BASE TABLES
 
       HEADER STATUS      -->     BOOKED
       LINE STATUS        -->     External Req Open
       (THE DETAILS MUST BE PRESENT IN REQUISITION BASE TABLE)

STEP5:-NOW COPY THE SALES ORDER NUMBER
       GOTO      -->     PURCHASING      -->     REQUISITION SUMMAY->RELATEC DOCUMENTS->SALES ORDER                      NUMBER->FIND->COPY REQUISITION NUMBER

       GOTO      -->     PURCHASE ORDERS->AUTO CREATE->DELETE SEARCH CRITIRIAA->ENTER REQUISITION             NUMBER->AUTOMETIC->ENTER SUPPLIER NAME->CREATE->PURCHASE ORDER WILL BE                      CREATED->COPY PO NUM&APPROVE THE PURCHASE ORDER

       HEADER STATUS      -->     BOOKED
       LINE STATUS        -->     PO OPEN

STEP6:- GOTO      -->     RECIEVING->RECIEPTS->ENTER PONUM->FIND->SUB:STORES->SAVE

       HEADER STATUS      -->     BOOKED
       LINE STATUS        -->     AWAITING SHIPPING
STEP7:-PICKING
STEP8:-SHIPPING
STEP9:-CLOSED
----------------------------------------------------------------
HEADER STATUS:-ENTERED        LINE STATUS:-ENTERED
HEADER STATUS:-BOOKED         LINE STATUS:-SUPPLY ELIGIBLE
HEADER STATUS:-BOOKED         LINE STATUS:-External Req Requested
HEADER STATUS:-BOOKED         LINE STATUS:-External Req Open
HEADER STATUS:-BOOKED         LINE STATUS:-PO OPEN
HEADER STATUS:-BOOKED         LINE STATUS:-AWAITING SHIPPING
HEADER STATUS:-BOOKED         LINE STATUS:-PICKED
HEADER STATUS:-BOOKED         LINE STATUS:-SHIPPED
HEADER STATUS:-BOOKED         LINE STATUS:-CLOSED
----------------------------------------------------------------

Oracle Order Management - Data flow for Order-to-Cash cycle

1. Order Entry: 

This is first stage when Order in enter in system.When the order is entered it basically create a record in order headers and Order Lines table.
Enter header details: Once you enter details on the order header and save it or move it to lines, record goes to one table oe_order_headers_all flow_status_code = ENTERED, booked_flag = N), Primary key=HEADER_ID
No record exist in any other table for this order till now.
Enter Line details for this order: Enter different item numbers, quantity and other details in line tab. When the record gets saved, it goes to one table. Order header details will be linked with line details by order HEADER_ID. oe_order_lines_all (flow_status_code = ENTERED, booked_flag = N, open_flag = Y) Primary key= LINE_ID 

2.Order Booking:

This is next stage, when Order is booked then the Flow status changed from Entered to Booked. At this stage, these below table get affected.
oe_order_headers_alL (flow_status_code as BOOKED, booked_flag updated to Y)
oe_order_lines_all (flow_status_code as AWAITING_SHIPPING, booked_flag updated Y)
wsh_delivery_details (DELIVERY_DETAIL_ID is assigned here, released_status ‘R’ ready to release, LINE_ID comes as SOURCE_LINE_ID)
wsh_delivery_assignments (DELIVERY_ASSIGNMENT_ID is assigned for DELIVERY_DETAIL_ID present in wsh_delivery_details, DELIVERY_ID remains blank till this stage)
*In shipping transaction form order status remains “Ready to Release”.
At the same time, Demand interface program runs in background And insert into inventory tables mtl_demand, here LINE_ID come as a reference in DEMAND_SOURCE_LINE3. Reservation :

This step is required for doing reservations SCHEDULE ORDER PROGRAM runs in the background and quantities are reserved. Once this program get successfully get completed, the mtl_demand and mtl_reservations table get updated. LINE_ID gets updated in DEMAND_SOURCE_LINE_ID in both the tables.4. Pick Release :

Pick Release is the process of putting reservation on on-hand quantity available in the inventory and pick them for particular sales order.
Pick release can be done from ‘Release Sales Order’ form or ‘Pick release SRS’ program can be scheduled in background. In both of these cases all lines of the order gets pick released depending on the Picking rule used. If specific line/s needs to be pick release it can be done from ‘Shipping Transaction form. For this case Pick Release is done from ‘Release Sales Order’ form with Pick Confirm=NO.
Once pick release is done these are the tables get affected:
If step 3 is not done then MTL_RESERVATIONS gets updated now.
wsh_new_deliveries (one record gets inserted with SOURCE_HEADER_ID= order header ID, status_code=OP =>open)
wsh_delivery_assignments (DELIVERY_ID gets assigned which comes from wsh_new_deliveries) wsh_delivery_details (released_status ‘S’ ‘submitted for release’)
MTL_TXN_REQUEST_HEADERS
MTL_TXN_REQUEST_LINES (LINE_ID goes as TXN_SOURCE_LINE_ID)
(move order tables. Here request is generated to move item from Source (RM or FG) sub-inventory to staging sub-inventory)
Mtl_material_transactions_temp (link to above tables through move_order_header_id/line_id, this table holds the record temporally)
MTL_SERIAL_NUMBERS_TEMP (if item is serial controlled at receipt then record goes in this table)
MTL_SERIAL_NUMBERS (enter value in GROUP_MARK_ID )
*In shipping transaction form order status remains “Released to Warehouse” and all the material still remains in source sub-inventory. We need to do Move Order Transaction for this order. Till this no material transaction has been posted to MTL_MATERIAL_TRANSACTIONS5.Pick Confirm/ Move Order Transaction:Items are transferred from source sub-inventory to staging Sub-inventory. Here material transaction occurs.
Order line status becomes ‘Picked’ on Sales Order and ‘Staged/Pick Confirmed’ on Shipping Transaction Form.
MTL_MATERIAL_TRANSACTIONS_TEMP (Record gets deleted from here and gets posted to MTL_MATERIAL_TRANSACTIONS)
oe_order_lines_all (flow_status_code ‘PICKED’ )
MTL_MATERIAL_TRANSACTIONS (LINE_ID goes as TXN_SOURCE_LINE_ID)
mtl_transaction_accounts
wsh_delivery_details (released_status becomes ‘Y’ => ‘Released’ )
wsh_delivery_assignments
MTL_ONHAND_QUANTITIES
MTL_SERIAL_NUMBERS_TEMP (record gets inserted after putting details for the item which are serial controlled at ‘Sales order issue’)
MTL_SERIAL_NUMBERS (record gets inserted after putting details for the item which are serial controlled at ‘Sales order issue’)
* This step can be eliminated if we set Pick Confirm=YES at the time of Pick Release

6.Ship Confirm:

Here ship confirm interface program runs in background. Data removed from wsh_new_
deliveries.
The items on the delivery gets shipped to customer at this stage.
oe_order_lines_all (flow_status_code ‘shipped’)
wsh_delivery_details (released_status ‘C’ ‘Shipped’, SERIAL_NUMBER if quantity is ONE)
WSH_SERIAL_NUMBERS (records gets inserted with the DELIVERY_DETAIL_ID reference, only in case of shipped quantity is two or more)
mtl_transaction_interface
mtl_material_TRANSACTIONS (linked through Transaction source header id)
mtl_transaction_accounts
Data deleted from mtl_demand, MTL_reservations
Item deducted from MTL_ONHAND_QUANTITIES
MTL_SERIAL_NUMBERS_TEMP (records gets deleted from this table)
MTL_SERIAL_NUMBERS (Serial number stauts gets updated CURRENT_STATUS=4 , ‘Issued out of store’)

7.Enter Invoice:

After shipping the order the order lines gets eligible to get transfered to RA_INTERFACE_LINES_ALL. Workflow background engine picks those records and post it to RA_INTERFACE_LINES_ALL. This is also called Receivables interface, that mean information moved to accounting area for invoicing details. Invoicing workflow activity transfers shipped item information to Oracle Receivables. At the same time records also goes in the table RA_INTERFACE_SALESCREDITS_ALL which hold details of sales credit for the particular order.
ra_interface_lines_all (interface table into which the data is transferred from order management) Then Autoinvoice program imports data from this table which get affected into this stage are receivables base table. At the same time records goes inra_customer_trx_all (cust_trx_id is primary key to link it to trx_lines table and trx_number is the invoice number)ra_customer_trx_lines_all (line_attribute_1 and line_attribute_6 are linked to order number and line_id of the orders)
8.Complete LineIn this stage order line level table get updated with Flow status and open flag.oe_order_lines_all (flow_status_code ‘shipped’, open_flag “N”)9.Close Order:

This is last step of Order Processing. In this stage only oe_order_lines_all table get updated. These are the table get affected in this step.
oe_order_lines_all (flow_status_code ‘closed’, open_flag “N”)
oe_order_HEADERS_all

Oracle Order Management - Shipping Interface Trip Stop

Interface Trip Stop

In the processing of the sales order after Shipping Execution ships the delivery, Shipping module needs to interface the information back to Oracle Order Management and Oracle Inventory Management Modules also. This is done via the Interface Trips Stop Concurrent Program.   OM Interface occurs first,  then Inventory Interface

You can also run Interfaces Individually for Order Management and Inventory.  However, the system will not allow you to run Inventory Interface until Order Management has completed successfully.

The Delivery Detail status becomes Staged/Picked after Pick Release is successful. 
Thereafter when you ship confirm the delivery to which this Delivery Detail  belongs,  there are the following cases that could happen:

Case 1:
======

If you ship confirm the delivery and do not run the interface (you Checked the Defer Interface Flag in the Confirm Delivery window before ship confirm), the delivery detail status would become "Shipped". This signifies that the shipment has left the Warehouse and therefore the Delivery Detail status become "Shipped".  However, the data is still not interfaced to OM and Inventory;  which means that information such has quantity shipped is not reflected in inventory on-hand and transactable quantities for the item in question.  If delivery details exist in this status,  shipping transactions have not completed (there are unprocessed shipping transactions),  and you will not be able to close the current month inventory period until the interfacing is performed.

Case 2:
=======

If you ship confirm the delivery and RUN the interface (you did NOT Check the Defer Interface Flag in the confirm delivery window), the delivery detail status would become "Interfaced". This signifies that not only has the shipment has left the Warehouse,  but also the data related to the delivery has been interfaced to Order Management and Inventory.

Note:
Please note that the Delivery Detail status will remain "Shipped" till both Order Management Interface and Inventory Interface have completed successfully. Even with Order Management Interface completed successfully and Inventory Interface Pending, the Delivery Detail status will remain as "Shipped" 

The significance of the new RELEASE_STATUS is that it lets the users know whether the delivery details has been interfaced to Order Management and Inventory or not .

What is the ship confirm process of move a sales order issue to inventory?

For a SO Issue, the trip stop program (WSHINTERFACE) inserts the record into the open interface with a transaction mode of 3- Background but the trip stop remembers the transaction id and continues to process it through to completion using an online transaction process routine unless you use the profile option WSH: Defer Inventory Process Online as noted below.  The flow is something like this:

STEP 1: Create book and pick an order
STEP 2: Run the Ship Confirm.
STEP 3: within the ship confirm process, order management runs the trip stop program.
STEP 4: The trip stop program inserts into the transaction open interface
STEP 5: The trip stop processes the transaction and runs the inventory transaction manager.

Here are some more details about routines being called while these steps are executed:

STEP 1: Create book and pick an order
STEP 2: Run the Ship Confirm.
STEP 3: within the ship confirm process, order management runs the trip stop program.
Trip Stop (WSH_SHIP_CONFIRM_ACTIONS.interface_all)
om_Interface_Trip_Stop
Inv_Interface_Trip_Stop
Interface_Delivery_to_Inv
interface_detail_to_inv
wsh_trx_handler.insert_row
STEP 4: The trip stop program inserts into the transaction open interface
insert into mtl_transactions_interface
STEP 5: The trip stop processes the transaction and runs the inventory transaction manager.
Inv_Interface_Trip_Stop (We were already here from step 2c. Now we continue.)
process_inv_online
mtl_online_transaction_pub.process_online
Locks the interface transaction
inv_txn_manager_pub.process_Transactions -- This routine does all the validation.

You can set up and run Interface Trip Stop - SRS by the following navigation path:
1.OM Super User Responsibility-->Shipping-->Interfaces-->Run-->
2.Select Interface Trip Stop - SRS from the Name field
3.Set the Mode to All and keep all parameter as defaulted value is recommended.
4.Click OK
5. If you want to run it periodically, click on the Schedule button. 
On the Schedule window you can set this job to be run:
 a) As soon as Possible
  b) Once
  c) Periodically
  d) On specific days

Issue:Failure to regularly gather schema statistics will place unwanted additional
processing loads on application jobs and concurrent programs 
. Frequent house-keeping and refreshing of schema
statistics will ensure all meta-data for application process is current and
timely.

Solution

1. As "Sys Administrator" responsibility
2. Run Reports
3. Select "Gather Schema Statistics"
4. Enter required parameters, including WSH and INV schema names.



ISSUE:The Interface Trip Stop process does not launch automatically when pick confirming sales orders through a custom concurrent program.

How do I get the Interface Trip Stop to run automatically when Ship Confirming ?

Solution:

This behavior is controlled by the - Defer Interface - Attribute in the Shipping parameters or Global Parameters setup in Shipping.

To check the Ship Confirm Rule setup:

Navigate to Shipping --> Setup --> Ship Confirm Rules.
NB - you need to confirm that you are in the correct shipping organization when doing the following
Search for the Ship Confirm Rule that you are using then view the following attributes:

Set Delivery In-Transit
Close Trip
Defer Interface --- this should be deselected

To check the Global Parameters setup:

Navigate to Shipping --> Setup --> Global Parameters

View the - Defer Interface - attribute --- this should be deselected.

Oracle Order Management - Data flow for Order-to-Cash cycle

1. Order Entry: 

This is first stage when Order in enter in system.When the order is entered it basically create a record in order headers and Order Lines table.
Enter header details: Once you enter details on the order header and save it or move it to lines, record goes to one table oe_order_headers_all flow_status_code = ENTERED, booked_flag = N), Primary key=HEADER_ID
No record exist in any other table for this order till now.
Enter Line details for this order: Enter different item numbers, quantity and other details in line tab. When the record gets saved, it goes to one table. Order header details will be linked with line details by order HEADER_ID. oe_order_lines_all (flow_status_code = ENTERED, booked_flag = N, open_flag = Y) Primary key= LINE_ID 

2.Order Booking:

This is next stage, when Order is booked then the Flow status changed from Entered to Booked. At this stage, these below table get affected.
oe_order_headers_alL (flow_status_code as BOOKED, booked_flag updated to Y)
oe_order_lines_all (flow_status_code as AWAITING_SHIPPING, booked_flag updated Y)
wsh_delivery_details (DELIVERY_DETAIL_ID is assigned here, released_status ‘R’ ready to release, LINE_ID comes as SOURCE_LINE_ID)
wsh_delivery_assignments (DELIVERY_ASSIGNMENT_ID is assigned for DELIVERY_DETAIL_ID present in wsh_delivery_details, DELIVERY_ID remains blank till this stage)
*In shipping transaction form order status remains “Ready to Release”.
At the same time, Demand interface program runs in background And insert into inventory tables mtl_demand, here LINE_ID come as a reference in DEMAND_SOURCE_LINE3. Reservation :

This step is required for doing reservations SCHEDULE ORDER PROGRAM runs in the background and quantities are reserved. Once this program get successfully get completed, the mtl_demand and mtl_reservations table get updated. LINE_ID gets updated in DEMAND_SOURCE_LINE_ID in both the tables.4. Pick Release :

Pick Release is the process of putting reservation on on-hand quantity available in the inventory and pick them for particular sales order.
Pick release can be done from ‘Release Sales Order’ form or ‘Pick release SRS’ program can be scheduled in background. In both of these cases all lines of the order gets pick released depending on the Picking rule used. If specific line/s needs to be pick release it can be done from ‘Shipping Transaction form. For this case Pick Release is done from ‘Release Sales Order’ form with Pick Confirm=NO.
Once pick release is done these are the tables get affected:
If step 3 is not done then MTL_RESERVATIONS gets updated now.
wsh_new_deliveries (one record gets inserted with SOURCE_HEADER_ID= order header ID, status_code=OP =>open)
wsh_delivery_assignments (DELIVERY_ID gets assigned which comes from wsh_new_deliveries) wsh_delivery_details (released_status ‘S’ ‘submitted for release’)
MTL_TXN_REQUEST_HEADERS
MTL_TXN_REQUEST_LINES (LINE_ID goes as TXN_SOURCE_LINE_ID)
(move order tables. Here request is generated to move item from Source (RM or FG) sub-inventory to staging sub-inventory)
Mtl_material_transactions_temp (link to above tables through move_order_header_id/line_id, this table holds the record temporally)
MTL_SERIAL_NUMBERS_TEMP (if item is serial controlled at receipt then record goes in this table)
MTL_SERIAL_NUMBERS (enter value in GROUP_MARK_ID )
*In shipping transaction form order status remains “Released to Warehouse” and all the material still remains in source sub-inventory. We need to do Move Order Transaction for this order. Till this no material transaction has been posted to MTL_MATERIAL_TRANSACTIONS5.Pick Confirm/ Move Order Transaction:Items are transferred from source sub-inventory to staging Sub-inventory. Here material transaction occurs.
Order line status becomes ‘Picked’ on Sales Order and ‘Staged/Pick Confirmed’ on Shipping Transaction Form.
MTL_MATERIAL_TRANSACTIONS_TEMP (Record gets deleted from here and gets posted to MTL_MATERIAL_TRANSACTIONS)
oe_order_lines_all (flow_status_code ‘PICKED’ )
MTL_MATERIAL_TRANSACTIONS (LINE_ID goes as TXN_SOURCE_LINE_ID)
mtl_transaction_accounts
wsh_delivery_details (released_status becomes ‘Y’ => ‘Released’ )
wsh_delivery_assignments
MTL_ONHAND_QUANTITIES
MTL_SERIAL_NUMBERS_TEMP (record gets inserted after putting details for the item which are serial controlled at ‘Sales order issue’)
MTL_SERIAL_NUMBERS (record gets inserted after putting details for the item which are serial controlled at ‘Sales order issue’)
* This step can be eliminated if we set Pick Confirm=YES at the time of Pick Release

6.Ship Confirm:

Here ship confirm interface program runs in background. Data removed from wsh_new_
deliveries.
The items on the delivery gets shipped to customer at this stage.
oe_order_lines_all (flow_status_code ‘shipped’)
wsh_delivery_details (released_status ‘C’ ‘Shipped’, SERIAL_NUMBER if quantity is ONE)
WSH_SERIAL_NUMBERS (records gets inserted with the DELIVERY_DETAIL_ID reference, only in case of shipped quantity is two or more)
mtl_transaction_interface
mtl_material_TRANSACTIONS (linked through Transaction source header id)
mtl_transaction_accounts
Data deleted from mtl_demand, MTL_reservations
Item deducted from MTL_ONHAND_QUANTITIES
MTL_SERIAL_NUMBERS_TEMP (records gets deleted from this table)
MTL_SERIAL_NUMBERS (Serial number stauts gets updated CURRENT_STATUS=4 , ‘Issued out of store’)

7.Enter Invoice:

After shipping the order the order lines gets eligible to get transfered to RA_INTERFACE_LINES_ALL. Workflow background engine picks those records and post it to RA_INTERFACE_LINES_ALL. This is also called Receivables interface, that mean information moved to accounting area for invoicing details. Invoicing workflow activity transfers shipped item information to Oracle Receivables. At the same time records also goes in the table RA_INTERFACE_SALESCREDITS_ALL which hold details of sales credit for the particular order.
ra_interface_lines_all (interface table into which the data is transferred from order management) Then Autoinvoice program imports data from this table which get affected into this stage are receivables base table. At the same time records goes inra_customer_trx_all (cust_trx_id is primary key to link it to trx_lines table and trx_number is the invoice number)ra_customer_trx_lines_all (line_attribute_1 and line_attribute_6 are linked to order number and line_id of the orders)
8.Complete LineIn this stage order line level table get updated with Flow status and open flag.oe_order_lines_all (flow_status_code ‘shipped’, open_flag “N”)
9.Close Order:

This is last step of Order Processing. In this stage only oe_order_lines_all table get updated. These are the table get affected in this step.
oe_order_lines_all (flow_status_code ‘closed’, open_flag “N”)
oe_order_HEADERS_all

Order Management - Back Order and handling

What is Back order? When it occurs?

In the Back Order the material gets unreserved. .  Backorders caused by Pick Releasing (PR) 

order lines when there is no or not enough stock available.  And backorders caused by shipping less,  at Ship confirm, than what was released.

How are Backorders handled /processed?

As in previous releases, Order Management and Shipping Execution has two types of   Backorders.

 Backorders caused by Pick Releasing (PR) order lines when there is no or not enough stock available.  And backorders caused by shipping less, at Ship confirm, than what was released.

 A. Backorders after Pick Releasing with Insufficient Stock

Pick Release will process all order (more correctly shipping) lines that you selected when 

submitting PR.  It will create move order lines for each line, whether there is stock available or not.  You (or the system) will however, not be able to (auto) detail and (auto) Pick Confirm the lines where there is not enough stock available.  In R11i, you cannot switch off reservations for PR.  Also, the system will not print pick slips for lines that are not detailed.

The delivery line, which was 'Ready to Release' before running PR will be split into a quantity

 that was available for picking and a unavailable quantity.  The first delivery line will become 

status ‘Released’ (Pick Confirmed), the second 'Submitted for Release' (Move Order created, but not confirmed).  In the latter case, the ‘Details Required' status is checked.  The order line will not split at this point, but receives a 'Picked partial' status.  After Ship Confirming the Released delivery line, the original order line will be split into a 'Shipped' and a 'Submitted for Release' line  (unless the shipped quantity falls within the under shipment tolerance).  The latter will be available  for Pick Release as a 'Backorder' as soon as there is stock available.  On the sales order, there is no order or workflow status called 'Backorder'.  You will not really see any difference between a scheduled order line that was never released and a backordered line. Pick Release is able to distinguish between the two, because it allows you to release them separately.

B. Backorders Caused by shipping less than what was Released

Before Ship Confirming a Released (Pick Confirmed) delivery line, you have the option to update the shipped quantity.  If the shipped quantity is less than the picked quantity, you have can either designate the remaining quantity as 'Backordered' (meaning the quantity was lost somewhere along the picking/staging process) or leave it in staging in to assign it to a different delivery (i.e. truck was full and wait for next pick up). At Ship Confirm, any staged quantities will be split off in a separate delivery line that is immediately ready to be shipped in a subsequent delivery.  A backordered quantity will remain noted on the same delivery line.  Only when the original delivery line is interfaced through Inventory Interface/Order Management Interface, will the order line be split into a line for the shipped quantity and a new line for the backordered quantity (Awaiting shipping).  This enables you to pick the remaining quantity again in order to fulfill the complete order quantity.  This split will only happen if the backordered quantity is greater than the Under Shipment Tolerance.

Oracle Order Management - Core Tables

Entered
OE_ORDER_HEADERS_ALL	1 record created in header table
OE_ORDER_LINES_ALL	Lines for particular records
OE_PRICE_ADJUSTMENTS	When discount gets applied
OE_ORDER_PRICE_ATTRIBS	If line has price attributes then populated
OE_ORDER_HOLDS_ALL	If any hold applied for order like credit check etc
Booked
OE_ORDER_HEADERS_ALL	Booked_Flag=Y, Order booked.
WSH_DELIVERY_DETAILS	Released_Status Ready to release
Pick Released
WSH_DELIVERY_DETAILS	Released_Status=Y Released to Warehouse (Line has been released to Inventory for processing)
WSH_PICKING_BATCHES	After batch is created for pick release
MTL_RESERVATIONS	This is only soft reservations. No physical movement of stock
Full Transaction
MTL_MATERIAL_TRANSACTIONS	No records in MTL_MATERIAL_TRANSACTIONS
MTL_TXN_REQUEST_HEADERS
MTL_TXN_REQUEST_LINES
WSH_DELIVERY_DETAILS	Released to warehouse
WSH_NEW_DELIVERIES	If Auto-Create is Yes then data populated
WSH_DELIVERY_ASSIGNMENTS	Deliveries get assigned
Pick Confirmed
WSH_DELIVERY_DETAILS	Released_Status=Y Hard Reservations. Picked the stock. Physical movement of stock
Ship Confirmed
WSH_DELIVERY_DETAILS	Released_Status=C ;Shipped ;Delivery Note get printed Delivery assigned to trip stop quantity will be decreased
MTL_MATERIAL_TRANSACTIONS	On the ship confirm form, check Ship all box
WSH_NEW_DELIVERIES	If Defer Interface is checked then OM & inventory not updated. If Defer Interface is not checked: Shipped
OE_ORDER_LINES_ALL	Shipped_Quantity get populated
WSH_DELIVERY_LEGS	1 leg is called as 1 trip.1 Pickup & drop up stop for each trip.
OE_ORDER_HEADERS_ALL	If all the lines get shipped then only flag N
Auto Invoice
WSH_DELIVERY_DETAILS	Released_Status=I Need to run workflow background process.
RA_INTERFACE_LINES_ALL	Data will be populated after work flow process.
RA_CUSTOMER_TRX_ALL	After running Auto Invoice Master Program for
RA_CUSTOMER_TRX_LINES_ALL	Specific batch transaction tables get populated

Customer Information
HZ_PARTIES	Get Customer information include Name,  Contacts, Address and Phone
HZ_PARTY_SITES
HZ_LOCATIONS
HZ_CUST_ACCOUNTS
HZ_CUST_ACCOUNT_SITES_ALL
HZ_CUST_SITE_USES_ALL
RA_CUSTOMERS
Price Details
QP_LIST_HEADERS_B	To Get Item Price Details.
QP_LIST_LINES
Items On Hand Qty
MTL_ONHAND_QUANTITIES	To check On Hand Qty Items.
Payment Terms
RA_TERMS	Payment terms
Sales Order Holds
OE_HOLD_DEFINITIONS	Order Hold and Managing Details
OE_HOLD_AUTHORIZATIONS
OE_HOLD_SOURCES_ALL
OE_ORDER_HOLDS_ALL
Hold Release
OE_HOLD_RELEASES_ALL	Hold released Sales Order
Credit Check Details
OE_CREDIT_CHECK_RULES	To get the Credit Check Against Customer.
Cancel Orders
OE_ORDER_LINES_ALL	Cancel Order Details.
Automatic Numbering System
AR_SYSTEM_PARAMETES_ALL	You can check Automatic Numbering is enabled/disabled
Document Sequence
FND_DOCUMENT_SEQUENCES	Document Sequence Numbers
FND_DOC_SEQUENCE_CATEGORIES
FND_DOC_SEQUENCE_ASSIGNMENTS
Default Rules For Price List
OE_DEF_ATTR_DEF_RULES	Price List Default Rules
OE_DEF_ATTR_CONDNS
AK_OBJECT_ATTRIBUTES
End User Details
CSI_T_PARTY_DETAILS	To capture End user Details
Sales Credit
OE_SALES_CREDITS	Sales Credit Information
Attaching Documents
FND_ATTACHED_DOCUMENTS	Attached Documents and Text information
FND_DOCUMENTS_TL	Fnd documents short text
Blanket Sales Order
OE_BLANKET_HEADERS_AL	Blanket Sales Order Information.
OE_BLANKET_LINES_ALL
Processing Constraints
OE_PC_ASSIGNMENTS	Sales order Shipment schedule Processing Constraints
OE_PC_EXCLUSIONS