Processing Pending Move Transactions
You can view, update, delete, and resubmit move transaction records that have failed validation and remain in the Open Move Transaction Interface table (WIP_MOVE_TNX_INTERFACE). You can also resubmit transactions whose concurrent process has failed and have a processing phase of Complete and process status of Error. You can view error messages associated with failed records. Error messages can assist you in updating failed records before resubmission.
Prerequisites
To find pending move transactions:
- For each pending record displayed, you can view the following information using the Pending Move Transactions window's alternative regions:
Processing: Group ID, processing Phase, processing Status
Source: Source Code, Source Line (if applicable), Created By
Concurrent Request: Request ID, Phase, Status, Message
Job or Schedule Name: Organization, Job or Schedule Name, Line
Operations: From Operation Sequence, Department, and Step and To Operation Sequence, Department, and Step
Transaction: UOM, Quantity, Date and time, Type
Comments and Scrap Account: Reason, Reference, and Scrap Account
1. In the Pending Move Transactions window, select the failed record.
All errors for the selected record are displayed. Column indicates the name of the column in the move interface table that failed validation. Message indicates why the transaction failed. Using these messages you can determine what fields need to be updated.
Messages that are not specific to a Column, for example processing errors, may also be displayed. In such cases, a Message but no Column is shown.
1. Select the record to update.
You can update records with a processing status of Error.
When you insert records into the Open Move Transaction Interface table, you can optionally identity a record's source using the source code and source line. For example, you can enter a different source code and source line for records from a bar code reader versus those from a radio frequency device.
The name of the user that created the transaction is displayed. This field can be updated.
4. In the Job or Schedule Name alternative region, select the Organization.
5. Select the Job or Schedule Name.
If you select a schedule name, you must enter a production line. If you select a discrete job, and the line field contains a value the system prompts you to delete the line value.
6. In the Operations alternative regions, select the From Operation Sequence.
You can enter any operation defined for your job or schedule.
7. Select the From Operation Step.
You can update this field with any intraoperation step currently enabled for your organization. See: Intraoperation Steps.
8. Select the To Operation Sequence. You can enter any operation sequence that has a valid department for your organization and job or repetitive schedule.
9. Select the To Operation Step.
You can select any operation step that is enabled for your organization. If you select the Scrap intraoperation step and the WIP Require Scrap Account parameter is set, you must enter a scrap account. If you update the To Operation step from Scrap to another, non-scrap step and the scrap account field has a value, you must clear the scrap account field.
10. Select the move transaction Type: Move transaction, move and Complete, Return and move. See: Move Transaction Types.
11. In the Transaction alternative region, select the UOM.
If you enter an alternate unit of measure for the assemblies, you must enter the quantity in the alternate unit of measure. You can update this field with any number.
The date and time must fall within an open accounting period and cannot be greater than the current date or less than the release date of the job or the earliest valid repetitive schedule.
15. Enter the transaction Reference.
References can be used to identify transactions on standard reports. They can be up to 240 characters of alpha numeric text.
16. If the To intraoperation step is Scrap and the WIP Require Scrap Account parameter is set, you must enter a scrap account Number or an account Alias. If you do not specify that a scrap account is required, it is optional. See: Move Transaction Parameters and Defining Account Aliases.
If you subsequently change the To intraoperation step from Scrap to an intraoperation step other than Scrap, you must clear the Scrap Account number or Account Alias.
1. In the Pending Move Transactions window, check the transaction's Resubmit check box.
You can resubmit transactions of any processing status. If you leave the check box unchecked you can still update your transaction record but the transaction manager does not process it again when polling the move interface table.
2. Save your work to resubmit the transaction.
When you resubmit a record, the system nulls the Transaction ID, Group ID, and concurrent Request ID and changes the processing status to Pending. The resubmit level of the Move Transaction Manager determines at what specific start date and time or at what specific intervals transactions are processed.
You can deselect selected transactions as required.
2. Save your work to resubmit the transactions.
When you resubmit transactions, the system nulls their Transaction IDs, Group IDs, and concurrent Request IDs and changes their processing Statuses to Pending. The resubmit level of the Move Transaction Manager determines at what specific start date and time or at what specific intervals transactions are processed.
1. In the Pending Move Transactions window, select the transaction.
2. Choose Delete from the Edit Menu
You can delete failed records that have a processing status of Error regardless of their processing phase. When you delete transaction records, their corresponding error messages are also deleted.
See Also
Open Move Transaction Interface, Oracle Manufacturing Open Interfaces Manual, Release 11
Open Move Transaction Interface
Performing Move Transactions
Performing Move Completion Transactions