Oracle 工单完工退回,WIP完工入库及完工退回的几个重要问题

2024-02-25 00:40

本文主要是介绍Oracle 工单完工退回,WIP完工入库及完工退回的几个重要问题,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

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)报错:

CSTPACMS:validate_snap_interface 30 : OPERATION_SEQ_NUM in CST_COMP_SNAP_INTERFACE is missing or incorrect.

应为 不需要投料的工序也是要计算成本的,所以工单所有工序都必须插值,工序来自wip_operations

2.完工入库之前先移动工单至最后一道工序的move状态

3.完工退回之前先移动工单至第一道工序的排队状态

报错信息:

Serial number &TOKEN does not exist for the given item; and you cannot dynamically create a new one for this item.

解决:

0818b9ca8b590ca3270a3433284dd417.png

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 关键字 CST_COMP_SNAP_INTERFACE; DISCRETE JOB; OPEN INTERFACES; COMPLETION TRANSACTIONS 错误 30 ERROR

这篇关于Oracle 工单完工退回,WIP完工入库及完工退回的几个重要问题的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/743903

相关文章

Redis中的数据一致性问题以及解决方案

《Redis中的数据一致性问题以及解决方案》:本文主要介绍Redis中的数据一致性问题以及解决方案,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录一、Redis 数据一致性问题的产生1. 单节点环境的一致性问题2. 网络分区和宕机3. 并发写入导致的脏数据4. 持

vscode不能打开终端问题的解决办法

《vscode不能打开终端问题的解决办法》:本文主要介绍vscode不能打开终端问题的解决办法,问题的根源是Windows的安全软件限制了PowerShell的运行,而VSCode默认使用Powe... 遇到vscode不能打开终端问题,一直以为是安全软件限制问题,也没搜到解决方案,因为影响也不大,就没有管

Python与Java交互出现乱码的问题解决

《Python与Java交互出现乱码的问题解决》在现代软件开发中,跨语言系统的集成已经成为日常工作的一部分,特别是当Python和Java之间进行交互时,编码问题往往会成为导致数据传输错误、乱码以及难... 目录背景:为什么会出现乱码问题产生的场景解决方案:确保统一的UTF-8编码完整代码示例总结在现代软件

使用easy connect之后,maven无法使用,原来需要配置-Djava.net.preferIPv4Stack=true问题

《使用easyconnect之后,maven无法使用,原来需要配置-Djava.net.preferIPv4Stack=true问题》:本文主要介绍使用easyconnect之后,maven无法... 目录使用easGWowCy connect之后,maven无法使用,原来需要配置-DJava.net.pr

解决tomcat启动时报Junit相关错误java.lang.ClassNotFoundException: org.junit.Test问题

《解决tomcat启动时报Junit相关错误java.lang.ClassNotFoundException:org.junit.Test问题》:本文主要介绍解决tomcat启动时报Junit相... 目录tomcat启动时报Junit相关错误Java.lang.ClassNotFoundException

解决Maven项目报错:failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.13.0的问题

《解决Maven项目报错:failedtoexecutegoalorg.apache.maven.plugins:maven-compiler-plugin:3.13.0的问题》这篇文章主要介... 目录Maven项目报错:failed to execute goal org.apache.maven.pl

MySQL主从同步延迟问题的全面解决方案

《MySQL主从同步延迟问题的全面解决方案》MySQL主从同步延迟是分布式数据库系统中的常见问题,会导致从库读取到过期数据,影响业务一致性,下面我将深入分析延迟原因并提供多层次的解决方案,需要的朋友可... 目录一、同步延迟原因深度分析1.1 主从复制原理回顾1.2 延迟产生的关键环节二、实时监控与诊断方案

SQLyog中DELIMITER执行存储过程时出现前置缩进问题的解决方法

《SQLyog中DELIMITER执行存储过程时出现前置缩进问题的解决方法》在SQLyog中执行存储过程时出现的前置缩进问题,实际上反映了SQLyog对SQL语句解析的一个特殊行为,本文给大家介绍了详... 目录问题根源正确写法示例永久解决方案为什么命令行不受影响?最佳实践建议问题根源SQLyog的语句分

解决IDEA报错:编码GBK的不可映射字符问题

《解决IDEA报错:编码GBK的不可映射字符问题》:本文主要介绍解决IDEA报错:编码GBK的不可映射字符问题,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录IDEA报错:编码GBK的不可映射字符终端软件问题描述原因分析解决方案方法1:将命令改为方法2:右下jav

MyBatis模糊查询报错:ParserException: not supported.pos 问题解决

《MyBatis模糊查询报错:ParserException:notsupported.pos问题解决》本文主要介绍了MyBatis模糊查询报错:ParserException:notsuppo... 目录问题描述问题根源错误SQL解析逻辑深层原因分析三种解决方案方案一:使用CONCAT函数(推荐)方案二: