WIP_MOVE_TXN_INTERFACE Common Errors In Pending Move Transactions With Possible Causes And Action Plan To Process Them [ID

457066.1] Modified 31-JUL-2011 Type HOWTO Status MODERATED

In this Document Goal Solution Error 1: No charges allowed for this job/schedule Error 2: No open period found for date entered Error 3: The transaction quantity exceeds the overcompletion tolerance set for the Job, Repetitive Line/Assembly, or the Organization Error 4: Transaction quantity must be less than or equal to quantity available to move Error 5: TRANSACTION_ID not valid. Please re-enter Error 6: TRANSACTION_QUANTITY must be greater than zero Error 7: You cannot move assemblies within the same operation and step.Cause:You tried to perform a shop floor move within a single operation and intraoperation step. You can only move assemblies between distinct operations or between dist Error 8: The value for PRIMARY_QUANTITY either does not correspond to the value for TRANSACTION_QUANTITY or does not uniquely specify a value for TRANSACTION_QUANTITY. Please change PRIMARY_QUANTITY or TRANSACTION_QUANTITY Error 9: WIP_BATCH_MOVE_ERROR References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:
Oracle Work in Process - Version: 11.5.10.0 to 11.5.10.2 - Release: 11.5 to 11.5 Information in this document applies to any platform. Checked for relevance 19-MAR-2010

Goal
Some Common Errors in pending move transactions along with their possible causes and action plan to process them.

Script to identify the errored rows in pending move transactions: select * from WIP_MOVE_TXN_INTERFACE where process_status = 3; Script to identify the actual errors associated with the errored tranactions: select * from wip_txn_interface_errors where TRANSACTION_ID in (select TRANSACTION_ID from WIP_MOVE_TXN_INTERFACE where process_status = 3); Apart from the action plans provided for the errors below, it is recommended to apply the Move Processing Patch 5038886. This patch fixes some critical issues related to move processing in work in process module.

Solution

Error 1: No charges allowed for this job/schedule

Possible Causes: These will be transactions where the job is not in Released or Completed status. You can perform transactions only against jobs which have status of Released or Complete. This issue mainly occurs for OSP jobs when a OSP item is received against a Closed Job with a charge type of PO Move for that corresponding OSP Resource. You can verify it by checking the source_code in WIP_MOVE_TXN_INTERFACE. It will show as 'RCV' Another cause of this is data being inserted into WIP_MOVE_TXN_INTERFACE for a job that is not in Released or Complete status and then trying to process it. Solution: Check the status of the corresponding job. Change the status of the job to either Released or Complete. If the job is closed, then unclose the job. Then resubmit the transaction. However, if the period in which the job is closed is also closed, then you cannot unclose the job and hence cannot process these transactions. In this case, you need to delete these transactions from the pending move transactions form. Resubmit the transactions through forms only. To prevent this issue, please make sure that no receipt is done against a job that is closed.

Error 2: No open period found for date entered

Possible Causes: The Inventory period of the transaction date is not opened yet. The transaction date would be in closed period. This can happen if data is being inserted into WIP_MOVE_TXN_INTERFACE with transaction date in a closed period and then trying to process it. Solution: Open the corresponding inventory period and resubmit the transactions. However, if the transaction date is in a closed period, then go to pending move transactions form and change the transaction date to a date in a open period and then resubmit. Resubmit the transactions through forms only.

Error 3: The transaction quantity exceeds the overcompletion tolerance set for the Job, Repetitive Line/Assembly, or the Organization

Possible Causes: The transaction quantity exceeded the overcompletion tolerance defined in the 'More' tab of the Discrete Jobs form or the overcompletion tolerance set in the WIP Parameters. This is also a bug where performing multiple receive/deliver transactions would wrongly populate overcompletion_primary_quantity in wip_move_txn_interface.

Solution: Go to pending move transactions form and reduce the transaction quantity to a quantity that is within overcompletion tolerance limit and also change the overcompletion quantity accordingly and then resubmit. This bug is addressed through the 4232649. Apply the Patch 5760695 to update file version WIPDSFMB.pls 115.24.11510.6 or higher and then resubmit. Resubmit the transactions through forms only.

Error 4: Transaction quantity must be less than or equal to quantity available to move

Possible Causes: This issue generally comes up for OSP job when you do a manual move transaction for the OSP operation even with 'PO Move' charge type for the OSP resource. You can verify it by checking the source_code in WIP_MOVE_TXN_INTERFACE. It will show as 'RCV' This also happens when you try to process a move transaction from say op 20 to op 30 even before the transaction from op 10 to op 20 got processed. The cause is that data being in WIP_MOVE_TXN_INTERFACE for a job has transaction quantity which is less than the quantity present in the from operation sequence and from intraoperation step.

Solution: Make sure that enough quantity is present in the from operation sequence and from intraoperation step and then resubmit the errored transaction. For OSP jobs with 'PO Move' charge type you should not do any manual move transaction for the OSP operation. Resubmit the transactions through forms only.

Error 5: TRANSACTION_ID not valid. Please re-enter

Possible Causes: The transaction_id would have been populated too while inserting data into WIP_MOVE_TXN_INTERFACE. This can lead to duplicate transaction_id and hence fail since transaction_id must be unique. Solution: Resubmit the transaction. When you resubmit, system will generate a new transaction_id and process it. Resubmit the transactions through forms only.

Error 6: TRANSACTION_QUANTITY must be greater than zero

Possible Causes:

TRANSACTION_QUANTITY would have been populated as zero when data was being inserted into WIP_MOVE_TXN_INTERFACE Solution: Go to pending move transactions form and enter the transaction quantity you actually want to move instead of zero and then resubmit. Resubmit the transactions through forms only.

Error 7: You cannot move assemblies within the same operation and step.Cause:You tried to perform a shop floor move within a single operation and intraoperation step. You can only move assemblies between distinct operations or between dist

Possible Causes: You tried to perform a shop floor move within a single operation and intraoperation step. Solution: You can only move assemblies between distinct operations or between distinct intraoperation step of the same operation. So you need to change the operation seq/intraoperation step appropriately and then resubmit the transactions. Resubmit the transactions through forms only.

Error 8: The value for PRIMARY_QUANTITY either does not correspond to the value for TRANSACTION_QUANTITY or does not uniquely specify a value for TRANSACTION_QUANTITY. Please change PRIMARY_QUANTITY or TRANSACTION_QUANTITY

Possible Causes: 1.When the quantity in the pending move transaction screen was changed, only the transaction qty got changed. The primary qty remains the same. 2. This happens for OSP items with inter-class conversion rates. Transaction_Quantity and Primary_quantity are being compared without the decimal places getting rounded off to the same digit. Solution: The above causes are bugs which are addressed through Bugs 4751892 and 4909848 and their fix is included in Consolidated fix 4969536. Apply the Patch 4969536 and then resubmit the errored transactions. Resubmit the transactions through forms only.

Error 9: WIP_BATCH_MOVE_ERROR
Possible Causes:

The records picked by move worker were treated as a batch. If backflush component transaction fails validation, all the records in the same batch fails. Solution: The fix for this issue is included as part of Consolidated Bug 5038886. Apply the Patch 5038886 and then resubmit the errored transactions. Only the transaction for which backflush validation fails will error out and the rest will process. Resubmit the transactions through forms only.

References
NOTE:363963.1 - WIP_BATCH_MOVE_ERROR Is Unacceptable Functionality PATCH:4969536 - CONSOLIDATE ARU FOR BUGFIXES BETWEEN DATES 20-JAN-06 TO 03-MAR-06 PATCH:5038886 - This patch fixes some critical issues related to move processing in work in process module. Related

Products

Keywords

Oracle E-Business Suite > Manufacturing > Discrete Manufacturing > Oracle Work in Process

MOVE TRANSACTIONS; OSP; PERIOD CLOSE RECONCILIATION REPORT; WIP_MOVE_TXN_INTERFACE; WIP_TXN_INTERFACE_ERRORS Errors ERROR 6; ERROR 7; ERROR 5; ERROR 8; ERROR 2; ERROR 9; ERROR 1; ERROR 4; ERROR 3