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

相关文章

oracle 11g导入\导出(expdp impdp)之导入过程

《oracle11g导入导出(expdpimpdp)之导入过程》导出需使用SEC.DMP格式,无分号;建立expdir目录(E:/exp)并确保存在;导入在cmd下执行,需sys用户权限;若需修... 目录准备文件导入(impdp)1、建立directory2、导入语句 3、更改密码总结上一个环节,我们讲了

Vue3绑定props默认值问题

《Vue3绑定props默认值问题》使用Vue3的defineProps配合TypeScript的interface定义props类型,并通过withDefaults设置默认值,使组件能安全访问传入的... 目录前言步骤步骤1:使用 defineProps 定义 Props步骤2:设置默认值总结前言使用T

Web服务器-Nginx-高并发问题

《Web服务器-Nginx-高并发问题》Nginx通过事件驱动、I/O多路复用和异步非阻塞技术高效处理高并发,结合动静分离和限流策略,提升性能与稳定性... 目录前言一、架构1. 原生多进程架构2. 事件驱动模型3. IO多路复用4. 异步非阻塞 I/O5. Nginx高并发配置实战二、动静分离1. 职责2

解决升级JDK报错:module java.base does not“opens java.lang.reflect“to unnamed module问题

《解决升级JDK报错:modulejava.basedoesnot“opensjava.lang.reflect“tounnamedmodule问题》SpringBoot启动错误源于Jav... 目录问题描述原因分析解决方案总结问题描述启动sprintboot时报以下错误原因分析编程异js常是由Ja

MySQL 表空却 ibd 文件过大的问题及解决方法

《MySQL表空却ibd文件过大的问题及解决方法》本文给大家介绍MySQL表空却ibd文件过大的问题及解决方法,本文给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴价值,需要的朋友参考... 目录一、问题背景:表空却 “吃满” 磁盘的怪事二、问题复现:一步步编程还原异常场景1. 准备测试源表与数据

解决Nginx启动报错Job for nginx.service failed because the control process exited with error code问题

《解决Nginx启动报错Jobfornginx.servicefailedbecausethecontrolprocessexitedwitherrorcode问题》Nginx启... 目录一、报错如下二、解决原因三、解决方式总结一、报错如下Job for nginx.service failed bec

SysMain服务可以关吗? 解决SysMain服务导致的高CPU使用率问题

《SysMain服务可以关吗?解决SysMain服务导致的高CPU使用率问题》SysMain服务是超级预读取,该服务会记录您打开应用程序的模式,并预先将它们加载到内存中以节省时间,但它可能占用大量... 在使用电脑的过程中,CPU使用率居高不下是许多用户都遇到过的问题,其中名为SysMain的服务往往是罪魁

MySQ中出现幻读问题的解决过程

《MySQ中出现幻读问题的解决过程》文章解析MySQLInnoDB通过MVCC与间隙锁机制在可重复读隔离级别下解决幻读,确保事务一致性,同时指出性能影响及乐观锁等替代方案,帮助开发者优化数据库应用... 目录一、幻读的准确定义与核心特征幻读 vs 不可重复读二、mysql隔离级别深度解析各隔离级别的实现差异

C++ vector越界问题的完整解决方案

《C++vector越界问题的完整解决方案》在C++开发中,std::vector作为最常用的动态数组容器,其便捷性与性能优势使其成为处理可变长度数据的首选,然而,数组越界访问始终是威胁程序稳定性的... 目录引言一、vector越界的底层原理与危害1.1 越界访问的本质原因1.2 越界访问的实际危害二、基

Python多线程应用中的卡死问题优化方案指南

《Python多线程应用中的卡死问题优化方案指南》在利用Python语言开发某查询软件时,遇到了点击搜索按钮后软件卡死的问题,本文将简单分析一下出现的原因以及对应的优化方案,希望对大家有所帮助... 目录问题描述优化方案1. 网络请求优化2. 多线程架构优化3. 全局异常处理4. 配置管理优化优化效果1.