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

相关文章

解决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函数(推荐)方案二:

Redis 热 key 和大 key 问题小结

《Redis热key和大key问题小结》:本文主要介绍Redis热key和大key问题小结,本文给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴价值,需要的朋友参考下吧... 目录一、什么是 Redis 热 key?热 key(Hot Key)定义: 热 key 常见表现:热 key 的风险:二、

IntelliJ IDEA 中配置 Spring MVC 环境的详细步骤及问题解决

《IntelliJIDEA中配置SpringMVC环境的详细步骤及问题解决》:本文主要介绍IntelliJIDEA中配置SpringMVC环境的详细步骤及问题解决,本文分步骤结合实例给大... 目录步骤 1:创建 Maven Web 项目步骤 2:添加 Spring MVC 依赖1、保存后执行2、将新的依赖

Spring 中的循环引用问题解决方法

《Spring中的循环引用问题解决方法》:本文主要介绍Spring中的循环引用问题解决方法,本文给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴价值,需要的朋友参考下吧... 目录什么是循环引用?循环依赖三级缓存解决循环依赖二级缓存三级缓存本章来聊聊Spring 中的循环引用问题该如何解决。这里聊

Spring Boot中JSON数值溢出问题从报错到优雅解决办法

《SpringBoot中JSON数值溢出问题从报错到优雅解决办法》:本文主要介绍SpringBoot中JSON数值溢出问题从报错到优雅的解决办法,通过修改字段类型为Long、添加全局异常处理和... 目录一、问题背景:为什么我的接口突然报错了?二、为什么会发生这个错误?1. Java 数据类型的“容量”限制

关于MongoDB图片URL存储异常问题以及解决

《关于MongoDB图片URL存储异常问题以及解决》:本文主要介绍关于MongoDB图片URL存储异常问题以及解决方案,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐... 目录MongoDB图片URL存储异常问题项目场景问题描述原因分析解决方案预防措施js总结MongoDB图

SpringBoot项目中报错The field screenShot exceeds its maximum permitted size of 1048576 bytes.的问题及解决

《SpringBoot项目中报错ThefieldscreenShotexceedsitsmaximumpermittedsizeof1048576bytes.的问题及解决》这篇文章... 目录项目场景问题描述原因分析解决方案总结项目场景javascript提示:项目相关背景:项目场景:基于Spring

解决Maven项目idea找不到本地仓库jar包问题以及使用mvn install:install-file

《解决Maven项目idea找不到本地仓库jar包问题以及使用mvninstall:install-file》:本文主要介绍解决Maven项目idea找不到本地仓库jar包问题以及使用mvnin... 目录Maven项目idea找不到本地仓库jar包以及使用mvn install:install-file基

usb接口驱动异常问题常用解决方案

《usb接口驱动异常问题常用解决方案》当遇到USB接口驱动异常时,可以通过多种方法来解决,其中主要就包括重装USB控制器、禁用USB选择性暂停设置、更新或安装新的主板驱动等... usb接口驱动异常怎么办,USB接口驱动异常是常见问题,通常由驱动损坏、系统更新冲突、硬件故障或电源管理设置导致。以下是常用解决