Skip to main content

FAQ: Sales Order Processing within Inventory / Drop Ship Transactions Hungup In Transaction Open Interface

How do SO Lines flow into inventory?

Two separate flows are used depending if you perform a Pick release or Sales Order Issue.  For pick release, the pick list generation program creates a move order for the order line.  When the move order is "allocated", it inserts a record into the pending transaction table (MTL_MATERIAL_TRANSACTIONS_TEMP).  When the move order is transacted, the record is moved to the transaction history table (MTL_MATERIAL_TRANSACTIONS).  For sales order issues, the ship confirm / trip stop process sends information to inventory through the transaction open interface table (MTL_TRANSACTIONS_INTERFACE). The ship confirm process then runs the inventory transaction worker -- depending on the profile "WSH: Defer Inventory Process Online" -- see later questions.  The inventory transaction worker validates the data inserting it into the pending transaction table (MTL_MATERIAL_TRANSACTIONS_TEMP), then into the transaction history table (MTL_MATERIAL_TRANSACTIONS).

What is the Profile Option: "TP: INV Transaction processing mode"?

The profile option "TP: INV Transaction processing mode" can be set to Online processing, immediate concurrent processing, background processing, or form level processing. This is not used by the pick release or sales order issue processes.  The sales order issue process uses the profile option "WSH: Defer Inventory Process Online" -- see later questions.  The profile option enables transactions like a miscellaneous transaction to either be processed directly or wait for a concurrent program to process them. If the processing mode is set to background, then the Transaction Manager must run in order for the transactions to process from the transaction open interface table. 

What happens when I schedule the Transaction Manager?

The Transaction Manager is also called the Material Manager or Material Transaction Manager.  The Transaction Manager is run via the following navigation: Goto Inventory > Setup > Transactions > Interface Managers.  Ensure the Material Transactions manager is Active. The Transaction Manager runs a concurrent program called the "Process transaction interface" that in turn runs the "Inventory transaction worker" concurrent program if any transactions exist to process.

Does the Profile Option: "TP: INV Transaction processing mode" impact sales orders?

No, the profile is not used by the pick release or sales order issue processes. 

Why are only SO Lines with DropShip items stuck in the Inventory Open Transaction Interface table when the Transaction Manager is not running?

The drop ship records are being inserted into the open interface table (MTL_TRANSACTIONS_INTERFACE) with transaction mode of Background Processing. This means that the records will not process until the Transaction Manager is run. As of the time that this note was written, the drop ship transactions are hard-coded to use background mode and do not use a profile option.  More details are noted in the next question / answer.

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.

Is there a way to process the shipment of drop ship orders online?

A:-- No, drop ships should be processed by running the inventory transaction / material manager. The auto-processing of the drop ship was removed for performance reasons in December 2000 by Patch 1531929 (11.5.5 and above). Here are some more details:
Purchasing calls a drop ship routine (OE_DS_PVT) that processes the inventory transaction upon release. This routine is contained within the file, OEXVDSRB.pls. In OEXVDSRB.pls 115.17.153.6 and lower, the transaction was inserted into the
inventory transaction interface table, and then immediately processed using an inventory API (mtl_online_transaction_pub.process_online). The feature of processing automatically was removed in Patch 1531929 for performance reasons. It is not included in code from 115.17.153.9 onward. Patch 1531929 ISSUES WITH PROCESS ONLINE API IN DROP SHIP FLOW

What is the profile option WSH: Defer Inventory Process Online?

This profile option was introduced in 11.5.9 with Patch 4008601 "Need An Option To Defer Processing Sales Order Issue Records When Running Inventory Interface".  Possible values are Yes and No with the default value of NULL being read as No. The internal profile name is WSH_DEFER_INV_PR_ONLINE.  Setting the profile to No or Null uses normal processing where the ship confirm / trip stop immediately runs a transaction worker to process the sales order issue.  Setting the profile to Yes causes the sales order issue to sit in the transaction open interface until the Transaction Manager runs.

Pending (MMTT) transaction error: 'Fails in OE_DROP_SHIPMENT'?

Although Drop Shipments are 'Pass Through' transactions and do not require any balance OnHand to process, the inventory module expects onhand quantity to be at least zero (not negative). This is currently a limitation in the application and Drop Ship Receipts will fail with the "Fails in OE_DROP_SHIPMENT" error message in the Pending Transaction table if quantity is negative.
If you see the "Fails in OE_DROP_SHIPMENT" error on pending transactions, make sure that you review the onhand quantity. Receive enough quantity, using the Misc Receipts form so that they get the OnHand balance to at least 0. Then you can resubmit the Pending Transaction.
Labels:

Comments

Post a Comment

Popular posts from this blog

General Ledger FAQ

1.  What responsibility should I use when doing the set up for General Ledger? Use a seeded responsibility like 'Oracle General Ledger Super User'. You may also need to use the System Administrator responsibility. 2.  What are the pre-requisites required to define a new calendar? According to your business needs you need to decide the calendar type required i.e. monthly, weekly or biweekly, the number of periods, adjusting periods and the maximum number of periods within a fiscal year. 3. What are the pre-requisites required to define a new Ledger? Define a Calendar, Chart of Accounts and enable the functional Currency  and convention of subledger accounting method. 4. Why must I check the calendar definition before assigning to a Ledger? The calendar definition cannot be changed once it is assigned to a set of books so it is very important to check that the calendar definition is suitable to the specific business needs, has ...
Post a Comment
Read more

Difference Between MTS, ATO, MTO ,PTO ,CTO and ETO.

 Make-to-stock (MTS) In MTS environments, products are created before receipt of a customer order. Customer orders are then filled from existing stock, and then those stocks are replenished through production orders. MTS environments have the advantage of decoupling manufacturing processes from customer orders. Theoretically, this enables customer orders to be filled immediately from readily available stock. It also allows the manufacturer to organize production in ways that minimize costly changeovers and other disruptions. However, there are risks associated with placing finished goods into inventory without having a firm customer order or an established need. These risks tend to limit MTS environments to simple, low-variety, or commodity products whose demand can be forecasted readily.  Assemble-to-order (ATO) In ATO environments, products are assembled from components after the receipt of a customer order. The key components in the assembly or f...
Post a Comment
Read more

Accounting entries in Oracle Purchasing and Payables

This document gives in detail different accounts used and the accounting impact of various transactions that take place in Oracle Purchasing and Oracle Payables. Both Standard costing and Average costing methods are considered. The accounts are Oracle Applications specific and might differ from the conventional accounting names. Examples are given wherever required for better understanding of the concept. The sources of these accounts are given. PURCHASING:  Receiving – For Accrual Process for perpetual Accruals Receipts for inventory purchases are always accrued upon receipt. And also use perpetual accruals for expense purchases you want to record uninvoiced purchase liabilities immediately upon the receipt of the expense goods. Receiving Account (Receiving Account) To record the current balance of the material in receiving and inspection. Where to define in Apps: Define Organization           ...
Post a Comment
Read more