Professional Documents
Culture Documents
a) Example query for linking move orders with the pending table:
SELECT mmtt.transaction_temp_id,
tol.organization_id,
toh.request_number,
toh.header_id,
tol.line_number,
tol.line_id,
tol.inventory_item_id,
toh.description,
toh.move_order_type,
tol.line_status,
tol.quantity,
tol.quantity_delivered,
tol.quantity_detailed
FROM mtl_txn_request_headers toh,
mtl_txn_request_lines tol,
mtl_material_transactions_temp mmtt
WHERE toh.header_id = tol.header_id
AND toh.organization_id = tol.organization_id
AND tol.line_id = mmtt.move_order_line_id;
Move order can be treated as a demand in the Min-max planning, and Purchase
Requisition can be created based on the Move order requisition demand.
This feature will be useful, if the Move order is created by the end user and the
material-issuing authority wants to convert the move order into a P.R
automatically, when supply is not available for this Move order. But, there won't
be any link between the Move order number & the Purchase requisition number
The drawbacks of Move order arei) During Move order approval, the approver has
to approve line by line. This will be a tiresome process, if there are more than
100 lines in the Move order
ii) There can be only one move order approver (planner) assigned for one item.
This will be a problem, if the same item has to be used in different departments
& the Move order for this item - from each department has to be approved by the
respective department head
iii) There is no approval-hierarchy for move-order.