Move Order Source
Types
Move Order transaction from multiple sub-inventories
Before doing multiple sub-inventory Move Order transaction the on hand availabilities are below.
Oracle Inventory provides three types of move orders:
·
Move Order Requisitions
·
Replenishment Move Orders
·
Pick Wave Move Orders
The move order type refers to the entity that created the
move order. For all move orders, the final result is one of the two supported
transactions: subinventory or move order issue.
Move Order Requisition
The requisition is a manually generated request for a move order.
You can generate requests for subinventory transfers or move order issues. 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.
Replenishment Move
Order
These move orders are generated automatically. For example,
kanban cards can create a replenishment move order where the pull sequence
calls for a subinventory transfer
(intra-organization kanbans), or by min-max planned items where the item’s replenishment source (set at the item-subinventory level) is another subinventory. In this case, the min-max or replenishment count report automatically generates a move order. Replenishment move orders are pre-approved and ready to be transacted.
(intra-organization kanbans), or by min-max planned items where the item’s replenishment source (set at the item-subinventory level) is another subinventory. In this case, the min-max or replenishment count report automatically generates a move order. Replenishment move orders are pre-approved and ready to be transacted.
The type of move order generated depends on the replenishment
source:
·
If the replenishment source is a supplier, then a move order
requisition is created.
·
If the replenishment source is another inventory
organization, then an internal requisition is created.
·
If the replenishment source is a subinventory then a
replenishment move order is created. Note that the source subinventory must be
set up at the item subinventory level. For the min-max report to generate a
move order, the report must be generated at the subinventory level.
For kanban to generate a move order, the pull sequence source
type must be set to Intra-org.
Pick Wave Move Order
The pick release process generates move orders to bring the
material from its source location in stores to a staging location, which you
define as a subinventory in Oracle Inventory. This transaction is a
subinventory transfer.
These move orders are generated automatically by the Oracle
Shipping Execution pick release process.
These orders are pre-approved and ready to transact. Pick
slips and other shipping and inventory reports will also be available with
Oracle.
WIP Issue Move Orders
An optional process
in Oracle WIP allows you to run pick release for the components of a range of
jobs or schedules. This process creates move orders to either directly issue
the material to WIP, or to move the material to the backflush locator. These
orders are automatically approved, the picking rules are sued to allocated
material for the job, and pick slips can be printed for warehouse users.Move Order transaction from multiple sub-inventories
Before doing multiple sub-inventory Move Order transaction the on hand availabilities are below.
Navigation: MCR INV > Move Orders > Move Orders
Enter the values as per the below screen shot and save the
changes.
Click on Approve and status become as Approved.
Now Allocate the Move order go to below navigation
Navigation: MCR INV > Move
Orders > Transact Move Orders
Give the Move Order number as 116 and click on Find button.
Check the select check box and click on Allocate. When the
latest transacted sub-inventory does not have in-sufficient stock, system will
get the stock from other sub-inventory to full fill the required quantity at
that time allocation field will display as Multiple.
Click on View/Update Allocation and we can observe that
system Split the 600 Qty into 300 qty from MIH-S1 and MIH-S2 sub-inventories
like below screen shot. At MIH-S1 the on hand availability was only 300. For
rest of 300 quantities system will allocate from MIH-S2 based on latest
transacted sub-inventory.
Now
if we generate Move Order Pick Slip report through Toolbar View > Request > Submit View a New
Request with below screen shot details and click on Submit.
Enter the Parameters as Move Order Number From and to 118.
If we require sending notification to source warehouse/sub-inventory in-charger/Manager we can specify the in-charger/Manager at below navigation.
At the time of generating Move Order Pick Slip report we have button called Options and click on Options and enter the name of source warehouse/sub-inventory in-charger/Manager to send the pick slip notification.
Click on OK button and submit the request.
The Task status of the move order will be pending in Report
output.
Now Check the check box and click on Transact button.
Now if we generate Move Order Pick Slip report through
Toolbar View à
Request à Submit View a New Request with below screen shot details with
Notify the Name as CHARAN and click on Submit. The Task status of the move
order will be completed in Report output.
CHARAN has got Move Order Pick Slip notification.
If we click on notification link we will get the details like
below and click on OK.
Backend Table for Move Order Transactions:
SELECT * FROM MTL_TXN_REQUEST_HEADERS WHERE REQUEST_NUMBER='110'
SELECT * FROM MTL_TXN_REQUEST_LINES WHERE HEADER_ID='3909028'
No comments:
Post a Comment