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

相关文章

MybatisGenerator文件生成不出对应文件的问题

《MybatisGenerator文件生成不出对应文件的问题》本文介绍了使用MybatisGenerator生成文件时遇到的问题及解决方法,主要步骤包括检查目标表是否存在、是否能连接到数据库、配置生成... 目录MyBATisGenerator 文件生成不出对应文件先在项目结构里引入“targetProje

C#使用HttpClient进行Post请求出现超时问题的解决及优化

《C#使用HttpClient进行Post请求出现超时问题的解决及优化》最近我的控制台程序发现有时候总是出现请求超时等问题,通常好几分钟最多只有3-4个请求,在使用apipost发现并发10个5分钟也... 目录优化结论单例HttpClient连接池耗尽和并发并发异步最终优化后优化结论我直接上优化结论吧,

Java内存泄漏问题的排查、优化与最佳实践

《Java内存泄漏问题的排查、优化与最佳实践》在Java开发中,内存泄漏是一个常见且令人头疼的问题,内存泄漏指的是程序在运行过程中,已经不再使用的对象没有被及时释放,从而导致内存占用不断增加,最终... 目录引言1. 什么是内存泄漏?常见的内存泄漏情况2. 如何排查 Java 中的内存泄漏?2.1 使用 J

numpy求解线性代数相关问题

《numpy求解线性代数相关问题》本文主要介绍了numpy求解线性代数相关问题,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一定的参考学习价值,需要的朋友们下面随着小编来一起学习学习吧... 在numpy中有numpy.array类型和numpy.mat类型,前者是数组类型,后者是矩阵类型。数组

解决systemctl reload nginx重启Nginx服务报错:Job for nginx.service invalid问题

《解决systemctlreloadnginx重启Nginx服务报错:Jobfornginx.serviceinvalid问题》文章描述了通过`systemctlstatusnginx.se... 目录systemctl reload nginx重启Nginx服务报错:Job for nginx.javas

Oracle数据库使用 listagg去重删除重复数据的方法汇总

《Oracle数据库使用listagg去重删除重复数据的方法汇总》文章介绍了在Oracle数据库中使用LISTAGG和XMLAGG函数进行字符串聚合并去重的方法,包括去重聚合、使用XML解析和CLO... 目录案例表第一种:使用wm_concat() + distinct去重聚合第二种:使用listagg,

Redis缓存问题与缓存更新机制详解

《Redis缓存问题与缓存更新机制详解》本文主要介绍了缓存问题及其解决方案,包括缓存穿透、缓存击穿、缓存雪崩等问题的成因以及相应的预防和解决方法,同时,还详细探讨了缓存更新机制,包括不同情况下的缓存更... 目录一、缓存问题1.1 缓存穿透1.1.1 问题来源1.1.2 解决方案1.2 缓存击穿1.2.1

vue解决子组件样式覆盖问题scoped deep

《vue解决子组件样式覆盖问题scopeddeep》文章主要介绍了在Vue项目中处理全局样式和局部样式的方法,包括使用scoped属性和深度选择器(/deep/)来覆盖子组件的样式,作者建议所有组件... 目录前言scoped分析deep分析使用总结所有组件必须加scoped父组件覆盖子组件使用deep前言

解决Cron定时任务中Pytest脚本无法发送邮件的问题

《解决Cron定时任务中Pytest脚本无法发送邮件的问题》文章探讨解决在Cron定时任务中运行Pytest脚本时邮件发送失败的问题,先优化环境变量,再检查Pytest邮件配置,接着配置文件确保SMT... 目录引言1. 环境变量优化:确保Cron任务可以正确执行解决方案:1.1. 创建一个脚本1.2. 修

Linux Mint Xia 22.1重磅发布: 重要更新一览

《LinuxMintXia22.1重磅发布:重要更新一览》Beta版LinuxMint“Xia”22.1发布,新版本基于Ubuntu24.04,内核版本为Linux6.8,这... linux Mint 22.1「Xia」正式发布啦!这次更新带来了诸多优化和改进,进一步巩固了 Mint 在 Linux 桌面