WIP Move Transaction Upload – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.

Overview

Creates move transactions as in the Move Transactions form: moves between operations and intraoperation steps, including moves into and out of Reject and Scrap, Move and completion transactions and Return and move transactions, for discrete jobs and for the repetitive schedules of a line and assembly. Each row is posted immediately, with backflush, completion, outside processing and autocharge resources as for a move entered in the form.

Upload Mode Create opens an empty sheet. Create, Update downloads the Queue, Run and To move steps of the selected jobs and schedules that hold a quantity, with their Available quantity, as new move rows: enter To Step and Quantity on the rows to move, rows left unchanged are not uploaded. An existing move is never updated; correct it with another move, for example a backward move or a Return and move transaction.

Completions, returns and overcompletions follow the Transaction Types and Allow Overcompletion parameters, not the function Move Transactions is launched from. A .csv or plain .xlsx file, and an add-in upload of a sheet another user downloaded, run with the parameter defaults of the template named in the upload, else with the parameter defaults.

With E-Records and E-Signatures set to Yes, discrete job moves create e-records as in the Move Transactions form, also where the move or material processing profiles are set to background, where the form creates none. A move that needs an e-signature is refused and has to be entered in the form. With the parameter cleared, moves are posted without e-records, as through the WIP move interface.

Not supported: operations added on the fly, manual resource transactions, serialized jobs and backflush lot and serial entry. A move fails when a backflush component is serial controlled, or lot controlled with a lot that cannot be derived; derived lots are not verified. Mandatory quality collection plans are not enforced, as by the WIP move interface, and No Move shop floor statuses always apply, also for users of the form function that overrides them.

To enter descriptive flexfield values, add the Move Attribute Category and Move Attribute1-15 columns, which show the segment prompts, to a template of your own.

Run this report in Excel in seconds: download Blitz Report™ free (your first 30 reports are free) or try it in the online demo.

Report Parameters

Upload Mode, Organization Code, Sales Order, Order Line, Line, Assembly, Job, Transaction Types, Allow Overcompletion, E-Records and E-Signatures

Oracle EBS Tables Used

wip_operations, mtl_parameters, wip_discrete_jobs, wip_entities, mtl_system_items_vl, bom_standard_operations, bom_departments, org_access_view, wip_repetitive_schedules, wip_lines

Report Categories

Enginatics, Upload

CAC WIP Resource Efficiency, WIP Entities, MRP Pegging, CRP Resource Plan, WIP Job Upload, WIP Discrete Job Shortage, WIP Required Components

Running This SQL Without Blitz Report

The SQL source can be run in any SQL client. Some Oracle EBS SQL reports in this library use functions from the utility package xxen_util – install it first. Blitz Report™ adds parameters, Excel output with pivots, scheduling and security on top.

Download & Import Options

Resource Link
Excel Example Output WIP Move Transaction Upload 15-Oct-2026 194318.xlsx
Blitz Report™ XML Import WIP_Move_Transaction_Upload.xml
SQL Source WIP Move Transaction Upload.sql
Full Report on Enginatics www.enginatics.com/reports/wip-move-transaction-upload/

Case Study & Technical Analysis: WIP Move Transaction Upload

Executive Summary

WIP Move Transaction Upload creates move transactions in Oracle Work in Process, the transactions that move completed quantities from one operation or intraoperation step to the next along a discrete job or repetitive schedule. It mirrors the Move Transactions form for moves between operations, moves into and out of Reject and Scrap, move and completion transactions, and return and move transactions. Shop floor supervisors, production planners and manufacturing accountants use it to post large volumes of moves at the end of a shift, or to post moves for a set of jobs in one spreadsheet, while keeping backflush, completion and resource charging consistent with the form.

Business Challenge

The Solution

Technical Architecture (High Level)

Primary Tables

Logical Relationships

  1. Discrete jobs in WIP_DISCRETE_JOBS are joined to their entity in WIP_ENTITIES and to their assembly in MTL_SYSTEM_ITEMS_VL.
  2. Operations in WIP_OPERATIONS are joined to each job and to their standard operation and department.
  3. Each operation is expanded with a row generator into one row for each intraoperation step, queue, run and to move, and the quantity for that step is chosen by decode.
  4. The next operation of the job, the to step, is found by a correlated subquery for the first count point that follows the current operation.
  5. Repetitive schedules in WIP_REPETITIVE_SCHEDULES are joined to WIP_LINES and to their operations in the same way, with the quantities summed across the schedule’s operations.
  6. The discrete and repetitive branches are combined with UNION ALL, and each row is numbered to give the upload row.

Parameters & Filtering

Performance & Optimization

FAQ

Q: Can I update a move I entered earlier with this upload? A: No. An existing move is never updated. Correct it with another move, such as a backward move or a Return and move transaction.

Q: Which rows are uploaded? A: Only rows where To Step and Quantity have been entered are uploaded. Rows left unchanged are not uploaded.

Q: Are operations added on the fly supported? A: No. The description lists operations added on the fly as not supported, along with manual resource transactions and serialized jobs.

© Enginatics GmbH