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

相关文章

SpringBoot启动报错的11个高频问题排查与解决终极指南

《SpringBoot启动报错的11个高频问题排查与解决终极指南》这篇文章主要为大家详细介绍了SpringBoot启动报错的11个高频问题的排查与解决,文中的示例代码讲解详细,感兴趣的小伙伴可以了解一... 目录1. 依赖冲突:NoSuchMethodError 的终极解法2. Bean注入失败:No qu

MySQL新增字段后Java实体未更新的潜在问题与解决方案

《MySQL新增字段后Java实体未更新的潜在问题与解决方案》在Java+MySQL的开发中,我们通常使用ORM框架来映射数据库表与Java对象,但有时候,数据库表结构变更(如新增字段)后,开发人员可... 目录引言1. 问题背景:数据库与 Java 实体不同步1.1 常见场景1.2 示例代码2. 不同操作

如何解决mysql出现Incorrect string value for column ‘表项‘ at row 1错误问题

《如何解决mysql出现Incorrectstringvalueforcolumn‘表项‘atrow1错误问题》:本文主要介绍如何解决mysql出现Incorrectstringv... 目录mysql出现Incorrect string value for column ‘表项‘ at row 1错误报错

如何解决Spring MVC中响应乱码问题

《如何解决SpringMVC中响应乱码问题》:本文主要介绍如何解决SpringMVC中响应乱码问题,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录Spring MVC最新响应中乱码解决方式以前的解决办法这是比较通用的一种方法总结Spring MVC最新响应中乱码解

pip无法安装osgeo失败的问题解决

《pip无法安装osgeo失败的问题解决》本文主要介绍了pip无法安装osgeo失败的问题解决,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一定的参考学习价值,需要的朋友们下面随着小编来一... 进入官方提供的扩展包下载网站寻找版本适配的whl文件注意:要选择cp(python版本)和你py

SpringBoot整合jasypt实现重要数据加密

《SpringBoot整合jasypt实现重要数据加密》Jasypt是一个专注于简化Java加密操作的开源工具,:本文主要介绍详细介绍了如何使用jasypt实现重要数据加密,感兴趣的小伙伴可... 目录jasypt简介 jasypt的优点SpringBoot使用jasypt创建mapper接口配置文件加密

解决Java中基于GeoTools的Shapefile读取乱码的问题

《解决Java中基于GeoTools的Shapefile读取乱码的问题》本文主要讨论了在使用Java编程语言进行地理信息数据解析时遇到的Shapefile属性信息乱码问题,以及根据不同的编码设置进行属... 目录前言1、Shapefile属性字段编码的情况:一、Shp文件常见的字符集编码1、System编码

Spring MVC使用视图解析的问题解读

《SpringMVC使用视图解析的问题解读》:本文主要介绍SpringMVC使用视图解析的问题解读,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录Spring MVC使用视图解析1. 会使用视图解析的情况2. 不会使用视图解析的情况总结Spring MVC使用视图

Oracle存储过程里操作BLOB的字节数据的办法

《Oracle存储过程里操作BLOB的字节数据的办法》该篇文章介绍了如何在Oracle存储过程中操作BLOB的字节数据,作者研究了如何获取BLOB的字节长度、如何使用DBMS_LOB包进行BLOB操作... 目录一、缘由二、办法2.1 基本操作2.2 DBMS_LOB包2.3 字节级操作与RAW数据类型2.

Redis解决缓存击穿问题的两种方法

《Redis解决缓存击穿问题的两种方法》缓存击穿问题也叫热点Key问题,就是⼀个被高并发访问并且缓存重建业务较复杂的key突然失效了,无数的请求访问会在瞬间给数据库带来巨大的冲击,本文给大家介绍了Re... 目录引言解决办法互斥锁(强一致,性能差)逻辑过期(高可用,性能优)设计逻辑过期时间引言缓存击穿:给