Skip to main content

Move Order transaction in Oracle Apps


  Q1. What is a Move Order transaction?

 A1. Move Order is a request for a subinventory transfer or an account issue
 also known as an account transfer. Move Orders allow planners and facility
 managers to request the movement of material within the warehouse or facility
 for replenishment, material storage relocations and quality handling, etc. 
 For all Move Orders the final result will be one of two supported transactions:
 subinventory or account transfer. Subinventory transfer transactions may still
 be initiated without utilizing the Move Order function if desired.

 Q2. What Move Order source types are available?

 A2. There are three Move Order source types:

 A.  Move Order Requisition
     Generated by:
 *   Manually generated request inside Inventory
     Navigation  Inventory->Transactions->Move Orders

 The requisition is a manually generated request for a Move Order.
 May optionally utilize the approval processing - the requisition can
 optionally go through an Oracle Workflow approval process before it becomes
 a Move Order. If no approval process is used, the requisition becomes a move
 order immediately.

 B. Replenishment Move Order
     Generated by:      
 *   Kanban Cards when pull sequence calls for subinventory transfer
     (intra-org Kanbans)
 *   Min Max Planning Report planned at the Subinventory Level
 *   Replenishment Counts

 Replenishment Move Orders are pre-approved and ready to be transacted.

 C. Wave Pick Move Order
     Generated by:      
 *   Sales Order picking
 *   Internal Sales Order picking

 The Order Management pick release process generates move orders to bring
 material from its source location in Inventory to a staging location, which is
 defined as a subinventory. In other words, a subinventory transfer. 

 Wave Pick Move Orders are pre-approved and ready to transact. Pick slips can
 also be generated for these Move Orders from Inventory with the release of the
 Oracle Order Management module.

 Q3. What are the components of a Move Order?
 A3.  The Move Order has three components:

 *Move Order Header:             Order Type      Default Source
                                 Order Number    Default Destination

 * Move Order Lines:             Item            Source
                                 Project/Task    Destination
                                 Request Qty     Completed Qty

 * Move Order Line Detail:       Item    Destination Details
                                 Lot/Serial/Locator
                                 Quantity/UOM
                                 Source Details

 Move Order Header - Oracle inventory uses the Move Order header to store the
 Move Order source type which refers to the entity that created the Move Order.
 An Order could be a pick wave, sales order pick, a replenishment type (Kanban,
 Min-Max, Replenishment Count) or  a requisition. The Move Order header also
 stores the default source and destination location in the event of a subinventory
 transfer, or an account in the event of an account transfer. The header also
 stores the Move Order number and the requested date.

 Move Order Lines - Move Order Lines are the requests on a Move Order. They store
 the item, requested quantity, completed quantity (for partially fulfilled Move
 Order), a source and destination if known. The Move Order lines also include
 any project and task references, if the organization is project manufacturing
 enabled.

 Move Order Lines Details - Move Order Lines Details contain the information
 necessary to fulfill a particular request line. For instance, the material
 locator, lot or serial control information will be contained at the line detail
 level.  These details are automatically populated by Oracle Inventory when
 picking rules and item transaction defaults for destination locators have been
 setup, or the user can manually fill in the details.  It is highly recommended
 that the item transaction defaults feature be set up in Release 11i:
 Inventory->Setup->Transactions->Item Transaction Defaults


 Q4. What is the basic process flow of a Move Order Requisiton?

 A4. The Move Order process  deploys the following steps:

 *   Create the Move Order for required material. You can manually create the
     requisition or it may be automatically generated at Pick Release, Kanban
     Replishment, Min-Max or Replishment Count reports.

 *   Approve the Move Order if required. There is a seeded Oracle Workflow for
     Move Order Approvals. If  approval is required then the Item Planner must
     approve the Move Order Lines. All automatically generated Move Orders are
     created with an automatic approval.  If you do not desire to require
     approvals in your Inventory Organization for manual Move Order Requisitions
     then you must set your Time Out period parameter to '0' and the Time-Out
     Action parameter to 'Approve'. 
     Navigation:  Inventory->Setup->Organizations->Parameters
     Choose the Inventory Parameters Tab.

 *   Detail the Move Order. Detailing is the process that uses Oracle Inventory
     picking rules to determine where to source the material to fulfill a request
     line. The detailing process fills in the Move Order Line Details with the
     actual transactions to be performed and allocates the material to the Move
     Order. You should not detail a Move Order too soon in the business process
     because the detailing process for a Move Order creates pending transactions
     and removes that quantity from an availability picture. Detailing should not
     be done until you are ready to print a pick slip and actually move the
     material.

 *   Print a pick slip if desired or push the Move Order Line Details to mobile
     devices for transaction through the Move Order API - Move Orders
     INV_Move_Order_PUB.

 *   You are now ready to transact the Move Order. You can transact all the order
     lines at once or one detail line at a time as the items are moved.  If you
     transact less than the requested quantity, the Move Order will stay open
     until the total quantity is transacted, or the Move Order is closed
     or cancelled.

 Q5. What new tables, forms or profile options are used with the Move Order
     function?

 A5.
 TABLES
      MTL_TXN_REQUEST_HEADERS
      MTL_TXN_REQUEST_LINES

 FORMS
      Move Orders (INVTOMAI)
      This form allows you to create and  approve Move Orders by specifying
      items, source and destination locations, quantities and other order
      information.

      This form includes the following windows:
         Find Move Orders
         Move Order Header Summary
         Move Order Lines Summary

      Transact Move Orders (INVTOTRX)
      This form allows you to transact Move Orders and to view and update
      sourcing information.

      This form includes the following windows:
      Find Move Order Lines
      Transact Move Orders
      Transact Move Order Line Details

 PROFILE OPTION
      TP:INV Move Order Transact Form
      This profile option allows the Move Order transaction mode to be set as
      either online, background or concurrent request.

Comments

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 been d

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 finishing process are pla

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                                          Define Receiving Options