WIP Material Transaction Upload  Help

WIP Material Transaction Upload issues components to, and returns components from, WIP work orders in bulk from Excel. The download gives you one row per component requirement of the work orders you select, with the operation, department, supply subinventory and locator already filled in and the required, issued and still open quantities shown. Enter a transaction type and a quantity on the rows you want to transact, leave the rest blank, and upload.

When to use it

• Issue components to many work orders at once instead of transacting them one at a time in the WIP Material Transactions form.
• Issue push components, or pull components that were not backflushed automatically.
• Return components from a work order to stores – for example after an over-issue, or when a job is cancelled.
• Clear open requirements across a range of work orders after a picking or kitting run.
• Issue a component that is not on the work order bill, as the form allows.

Before you start

• You are signed in to a responsibility with access to the inventory organization and to the upload in Blitz Report.
• The work orders are discrete jobs, lot based jobs or maintenance work orders. Repetitive schedules are not supported and must be transacted in the form.
• Each work order is at status Released or Complete. Material transactions are not allowed at any other status.
• The transaction date falls in an open inventory period.
• The components are on hand in the subinventory you issue from, unless your organization allows negative balances.
• Normal item controls apply – a revision, lot number, serial number range or locator is required wherever the component item or subinventory is under that control.

Step 1 – Set the parameters

Open WIP Material Transaction Upload in Blitz Report and set the download filters. The parameters narrow which component requirements come back – they do not restrict what you may transact.

Step 2 – Run to download the Excel file

Click Run. The Excel file downloads and opens with one row per component requirement. The context columns are read-only and help you decide what to transact: Job, Job Type, Job Status, Assembly, Component Description, Supply Type, Date Required, Required Quantity, Quantity Issued and Open Quantity.

Step 3 – Enter the transactions

Only rows where you enter a Transaction Type and a Quantity are transacted. Leave every other row untouched – there is no need to delete them.

• Transaction Type – WIP Issue to issue components to the work order, WIP Return to return them to stores, or one of your own WIP issue or return transaction types.
• Quantity – always a positive number in the UOM shown. The transaction type decides the direction, so a return is not entered as a negative quantity.
• Subinventory and Locator – the stores side of the transaction. The supply subinventory and locator of the requirement are already filled in; change them if you issue from somewhere else.
• Operation Seq Num – the operation the component is issued to. Required for work orders that have a routing.
• Transaction Date – downloaded as today’s date; it must fall in an open inventory period.
• Revision, Lot Number, Lot Expiration Date, Lot Quantity, From Serial Number and To Serial Number – required wherever the component item is revision, lot or serial controlled. The lot quantity must equal the transaction quantity.
• Reason and Transaction Reference – optional, and carried onto the transaction.
• Source Project, Source Task, Expenditure Type and Expenditure Org – for project manufacturing.

To transact a component that was not downloaded, add a row with the Organization, Job, Operation Seq Num, Component, Transaction Type, Quantity, UOM, Subinventory and Transaction Date.

Step 4 – Validate and Save

Click Validate and Save. This checks for missing required values and runs the upload’s own checks – the work order type and status, the transaction type, the quantity, item and locator control requirements, a return against the quantity already issued, the operation, the department and subinventory, and whether the transaction date is in an open period – and saves the file. Correct any rows it flags before uploading.

Step 5 – Upload the file

In Blitz Report click Upload and select the saved file. This submits the upload request, which passes the rows to the inventory transaction manager.

Step 6 – Review the result report

When the request completes, a result report opens listing every uploaded row with its status and message, and with the quantity issued and open quantity of the requirement after the transaction.

What’s produced

• Inventory material transactions against the work orders, processed by the inventory transaction manager. They are identical to those the WIP Material Transactions form creates and relieve the work order requirement in the same way.
• A result report listing every row with a status (success or error) and a message – the reason a row was rejected, or a note when a component is not on the work order bill.

Common questions

Do I enter a negative quantity to return a component?
No. Always enter a positive quantity and set the Transaction Type to WIP Return. A zero or negative quantity is rejected.

Can I issue a component that is not on the work order bill?
Yes. Any transactable component item may be entered, as the WIP Material Transactions form allows. The row is flagged in the result report with “Component is not on the work order bill.” so that unintended entries are easy to spot.

Why is my work order not in the download?
Check the filters first – Job Status defaults to Released, and Open Requirements Only defaults to Yes, which hides requirements that are already fully issued. Also confirm the work order is a discrete job, lot based job or maintenance work order; repetitive schedules are not supported.

I want to return components but the rows are not there.
Clear Open Requirements Only. A fully issued requirement has no open quantity left, so it is filtered out by default.

Can I return more than was issued?
No. The return quantity is checked against the quantity already issued to that component, both in Validate and Save and again during the upload, which prevents driving the issued quantity negative.

What about non-WIP inventory transactions?
Use the INV Transaction Upload for miscellaneous issues and receipts, subinventory transfers and similar transactions.

Troubleshooting

Errors raised by the inventory transaction manager itself, such as insufficient on-hand quantity, are shown in the result report as the error code followed by its explanation.