1.必須向CST_COMP_SNAP_INTERFACE表中插入此工單全部工序的數據（也就是說相同的工單插入多條，僅僅是工序號不一樣）

標準文檔：

Note: If there are multiple operation sequences then,

Insert multiple records in CST_COMP_SNAP_INTERFACE, one record for each
OPERATION_SEQ_NUM in WIP_OPERATIONS for the appropriate WIP_ENTITY_ID (with the
same transaction_interface_id).

否則會出現故障：

（1）工單通過mtl_transactions_interface接口表，完工入庫了。可是沒有扣減最後一站移動站(to move站)數量
“接口表提交後，沒有錯誤信息，數據成功提交了。； 查詢物料交易事務處理表，此工單已有完工入庫記錄（庫存也有添加）。但就是沒有扣減最後一站移動站(to move站)數量（同一時候工單已完工量也沒有對應添加）。

CST_COMP_SNAP_INTERFACE 表中的數據一點都不動（成本管理器正常）”

（2）報錯：

2.完工入庫之前先移動工單至最後一道工序的move狀態

3.完工退回之前先移動工單至第一道工序的排隊狀態

報錯信息：

解決：

metalink上的一些解決的方法

Wip Assembly Completion For A Job Through MTL_TRANSACTIONS_INTERFACE Is Not Updating Job Completed Quantity [ID 745112.1]
改動時間 11-SEP-2010 類型 PROBLEM 狀態 MODERATED

In this Document
Symptoms
Cause
Solution
References

Platforms: 1-914CU;

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.9 to 12.0.4 - Release: 11.5 to 12
Information in this document applies to any platform.
Checked for relevance 11-SEP-2010
Symptoms
On 12.0.4 in Production:
Find that when WIP Assembly Completion transaction is performed for a Discrete job through
mtl_transaction_interface, the transaction is getting processed successfully but the completed
quantity is not getting updated in the Discrete job also quantity still remaining in To Move of
last operation.

EXPECTED BEHAVIOR
Expect that the quantity should get updated in the discrete jobs.

STEPS
The issue can be reproduced at will with the following steps:
1. Create a discrete job, release it
2. Perform Move transaction to the last operation to move step.
3. Perform WIP Assembly Completion through the MTI, it gets processed successfully
4. Verify the job header infoformation, still the quantity is not completed.

BUSINESS IMPACT
The issue has the following business impact:
Due to this issue, there is lot of discrepancy in the job.


.
Cause

The cause of the issue is invalid / incorrect data in cst_comp_snap_interface table.


The cause for this invalid data has been determined as the data in cst_comp_snap_interface corresponding
to completion record in MTI (linked with transaction_interface_id) was not populated with the correct op_seq_num.

This has explained in the following bug.
Bug 5746008 ‘CSTPACMS:VALIDATE_SNAP_INTERFACE 30‘ ERROR IN TRANSACTION OPEN INTERFACE

Customer was incorrectly populating the interface data.
cst_comp_snap_interface corresponding to completion record in MTI (linked with
transaction_interface_id) was not populated with the op_seq_num.

In the current scenario, user populated the op_seq_num but it is wrong value.

For any reference related to WIP Assembly Completion through MTI, can refer Note 458801.1




Solution

To implement the solution, please execute the following steps:

1. Insert the correct operation sequence number in to cst_comp_snap_interface table which corresponds
to the operation sequence of that particular job.

Note: If there are multiple operation sequences then,

Insert multiple records in CST_COMP_SNAP_INTERFACE, one record for each
OPERATION_SEQ_NUM in WIP_OPERATIONS for the appropriate WIP_ENTITY_ID (with the
same transaction_interface_id).

2. Retest the issue.






References
NOTE:458801.1 - Standard API/Interface Needed to Perform Work Order Completion: WIP Assembly Completion Transaction For Discrete Jobs Can Be Performed Through Mtl_Transactions_Interface Table
SR 7174967.993

顯示相關信息 相關的
產品

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

keyword
CST_COMP_SNAP_INTERFACE; DISCRETE JOB; OPEN INTERFACES; COMPLETION TRANSACTIONS
錯誤
30 ERROR

WIP完工入庫及完工退回的幾個重要問題