WIP Move Transaction Upload enters move transactions from Excel the way the Move Transactions form does: moves between operations and intraoperation steps, including 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.
When to use it
- Move many jobs through their routings at once instead of entering each move in the Move Transactions form.
- Complete assemblies into stores at the last operation, or return completed assemblies to the shop floor.
- Reject or scrap assemblies at an operation, with a scrap account and a reason.
- Overcomplete a job or schedule within its overcompletion tolerance.
- Move the repetitive schedules of a production line and assembly.
Before you start
- You are signed in to a responsibility with access to the inventory organization and to the upload in Blitz Report.
- The jobs are discrete jobs at status Released or Complete, or repetitive schedules of a line and assembly. Serialized jobs and operations added on the fly are not supported.
- The transaction date falls in an open period and is not before the release date of the job or schedule.
- For completions and returns, the job or schedule has an active completion subinventory.
Choose a template
The default template is Move.
| Template | Use it for |
|---|---|
| Move (default) | Moves, completions and returns with the main fields of the Move Transactions form. |
| Move Only | Moves without completions and returns: Transaction Types is locked to Move only. To restrict users or responsibilities to moves, share a copy of the template as restricted with them. |
Step 1 – Set the parameters
Open WIP Move Transaction Upload in Blitz Report, choose the template and set the parameters. The download filters only decide which operation steps come back; Transaction Types, Allow Overcompletion and E-Records and E-Signatures also apply to the rows you upload.
| Parameter | Meaning |
|---|---|
| Upload Mode | Create (default) gives you an empty sheet for new moves. Create, Update downloads the Queue, Run and To move steps of the selected jobs and schedules that hold a quantity, as new move rows. |
| Organization Code | The inventory organization. Defaults to your current organization. |
| Sales Order, Order Line | Restrict the download to the jobs reserved to the sales order or order line. |
| Line | Restricts the download to the repetitive schedules of the production line. |
| Assembly | Restricts the download to the jobs and repetitive schedules of the assembly. |
| Job | Restricts the download to the job. |
| Transaction Types | Move, Complete and Return (default) allows all three transaction types. Move only refuses Move and completion and Return and move transactions. |
| Allow Overcompletion | Yes (default) allows rows with Overcompletion. No refuses them, as the Move Transactions form does without the Allow Overcompletions function. |
| E-Records and E-Signatures | Yes raises the e-record event for each discrete job move, as the Move Transactions form does: an e-record is created where your e-record rules require one, and a move that needs an e-signature is refused. It applies only when the profile option EDR: E-records and E-signatures is Yes, and then defaults to Yes. Blank posts the moves without e-records and without e-signature checks. |
Step 2 – Run to download the Excel file
Click Run. With Create, Update, the file has one row per operation step that holds a quantity, with the From Seq, From Department, From Step, the next count point operation as To Seq, the To Department and the Available quantity filled in, and Transaction Type Move transaction. Assembly Description, Job Description, the departments and Available are read-only. With Create, the sheet is empty.
Step 3 – Enter the moves
On the rows you want to move, enter the To Step and the Quantity, and change the To Seq if needed. Rows you leave unchanged are not uploaded. To add a move, fill a new row; the descriptions, departments and Available fill in as you enter the job and the operation.
- Job – or Line and Assembly for a repetitive schedule. Sales Order and Order Line help find the job reserved to an order line; they are not stored with the move.
- Transaction Type – Move transaction, Move and completion transaction or Return and move transaction. It defaults to Move and completion when the profile option WIP:Move Completion Default is Yes.
- From Seq and From Step – where the assemblies are. From Step defaults to the only step of the operation that holds a quantity, and to To move for a return.
- To Seq and To Step – where they go. To Seq defaults to the next count point operation, or to the last operation for a completion.
- Quantity – in the UOM shown. It defaults, as in the form, from the profile option TP:WIP Move Transaction Quantity Default to the available quantity or to the operation’s minimum transfer quantity.
- Overcompletion – Yes moves the quantity above Available as an overcompletion.
- Transaction Date – defaults to the time of the download.
- Scrap Account Alias and Scrap Account Number – for moves into or out of Scrap. The alias fills the account number.
- Reason and Reference – optional, stored with the move.
Step 4 – Validate and Save
Click Validate and Save. This checks for missing required values, values not in their lists, a job together with a line, an assembly that does not belong to the job, the completion subinventory and locator of completions and returns, kanban replenishment, returns dated before the first completion and scrap accounts on moves that do not involve Scrap, 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. The upload request posts the rows one by one through Oracle’s move processing.
Step 6 – Review the result report
When the request completes, a result report opens listing every uploaded row with its status and message: the number of the posted move transaction, with the e-record number where one was created, or the reason the row was refused.
What’s produced
- One move transaction per row, processed as a move entered in the Move Transactions form: backflush of pull components, charges of autocharge resources and overheads, completion or return material transactions, scrap transactions to the scrap account and outside processing.
- Each row is committed on its own. A row that fails leaves nothing behind and does not affect the other rows.
- E-records for discrete job moves where your e-record rules require them, when E-Records and E-Signatures is Yes.
- A result report listing every row with a status (success or error) and a message.
Common questions
Does Create, Update change existing moves?
No. It downloads the open operation steps as new move rows. A posted move is never updated; correct it with another move, for example a backward move or a Return and move transaction.
Why does the download have no Reject or Scrap rows?
It lists only the Queue, Run and To move steps. To move assemblies out of Reject or Scrap, add a row with that From Step.
How do I move a repetitive schedule?
Enter the Line and Assembly instead of a Job.
Can I restrict users to moves only?
Yes. With Blitz Report Access Developer or System, copy the Move Only template, share the copy with those users or responsibilities and tick Restrict on their sharing rows, in the Templates window or the web page template editor. Use a copy, as an upgrade resets the shipped templates and removes sharing added to them. To refuse overcompletions as well, run the copy with Allow Overcompletion No, choose Save Template Parameter Defaults and tick Locked on that row.
Why is a move refused because it needs an e-signature?
Your e-record rules require a signature for that move, and only the Move Transactions form can collect one. Enter the move in the form or, where your procedures allow a move without an e-record, in a sheet downloaded with E-Records and E-Signatures blank, which posts it without an e-record and without the signature check.
Are lot and serial controlled backflush components supported?
A move fails when a backflush component is serial controlled, or lot controlled with a lot that cannot be derived. Enter those moves in the form.
Are mandatory quality collection plans and shop floor statuses enforced?
Mandatory collection plans are not enforced, as with Oracle’s move interface. No Move shop floor statuses always apply.
How do I 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.
How do I review posted moves?
Run WIP Move Transactions.
Troubleshooting
| Message | Cause | What to do |
|---|---|---|
| Missing values for required field/s: … | A required column is blank. | Fill in the columns named. |
| Job/Schedule is required / Enter either a Job or a Line and Assembly. | Neither a job nor a line and assembly was entered, or both were. | Enter a Job, or a Line and an Assembly. |
| Move and completion transaction needs Transaction Types Move, Complete and Return. / Transaction Type is invalid | Transaction Types is Move only, for example in the Move Only template. | Use a template that allows completions and returns, or enter the move in the form. |
| Overcompletion needs Allow Overcompletion. / Overcompletion is invalid | Allow Overcompletion is No. | Use a template that allows overcompletions. |
| transaction quantity must be less than or equal to quantity available to move | The quantity is larger than the quantity at the From step. | Reduce the quantity, or set Overcompletion to Yes. |
| For overcompletion, transaction quantity must be greater than available quantity. | Overcompletion is Yes but the quantity does not exceed Available. | Clear Overcompletion. |
| The transaction quantity exceeds the overcompletion tolerance set for the Job, Repetitive Line/Assembly, or the Organization. | The overcompletion is above the tolerance. | Reduce the quantity or raise the tolerance. |
| Total transaction quantity must be less than or equal to job complete quantity | A return is larger than the quantity completed. | Reduce the return quantity. |
| Job/Schedule does not have default completion subinventory/locator … / The default completion subinventory … is inactive … | The job or schedule has no completion subinventory, or it is inactive. | Set an active completion subinventory on the job or schedule. |
| Invalid transaction date. Backdated assembly return transaction is not allowed. | The return is dated before the first completion of the job. | Use a later transaction date. |
| Transaction date precedes release date for the job/schedule | The transaction date is before the release date. | Use a date on or after the release date. |
| No balance exists for the appropriate period for the job/schedule | The transaction date is not in an open period. | Use a date in an open period. |
| Status at this operation step disallows transactions | A No Move shop floor status is assigned to the step. | Remove the shop floor status, or move from another step. |
| Scrap Account Number is only used for moves into or out of Scrap. | A scrap account was entered on another move. | Clear the Scrap Account Alias and Scrap Account Number. |
| The move requires an e-signature, which only the Move Transactions form can collect. | The e-record rules require a signature for the move. | Enter the move in the Move Transactions form or, where your procedures allow it, in a sheet downloaded with E-Records and E-Signatures blank. |
| Move transaction … has already been processed. | The row comes from a result report and was posted before. | Remove the row, or enter a new move. |
Other messages come from Oracle’s move processing, such as a backflush component without enough on-hand quantity or serial numbers, and are shown in the result report as Oracle returns them.