Production Order Status

控制工单状态的几个TCODE

JSTO:Status object information(可输入order type的status profile查询)
JEST:Individual Object Status(输入OR00000+工单号可查询工单的所有状态Number)
TJ01:user status(自定义status)
JJ01T:user status text(自定义status文本)
TJ02:System status
TJ02T:System status text(系统状态文本)
从JEST关联到TJ02查看Order status 。
相关Tcode(有兴趣的可研究研究这些Tcode):
BS02/BS03:建立/显示 status profile
BS22/BS23:系统status维护/显示
BS32/BS33:维护transaction和status关系.
BS42/BS43:建立显示Status selection schema
BS52/BS53:建立Status对应的授权Key

 

Tell the difference between TECHO and CLOSED.

TECO means Technically completed order, means with out full completion of order. That production order stopped because of some reasons. CLOSED means after completion of confirmation and settlement the order is fully closed for further processing.

How to delete released production orders?

In the prodcution order, select Functions --> Deletion flag -->Active to delete production order. This method can be used for production orders having CRTD (ie created) and REL (released) status. However, it is not possible to delete a production order with REL and GMPS (ie. after the withdrawl of materials for the order) status.

You can TECO the production orders with REL and GMPS status.

CO13 is used to cancel the confirmation of a production order.

Once Final Goods Receipt is post & Order is completed n it is Technically Completed it should not allow any goods movement against that order but this is not happening & one can issue goods even if the order is TECO.

When order status is Teco, system allow us to do the posting against the order. Once order status is closed, then only order treated as closed for execution.

In TECO status you can post the remaining activity/goods movement. Like if you have one order that contains the 5 operation and out of 5, 3 you are confirming in the current period and suppose, rest you are doing in the next period. So at the time of settlement for current period, order status should be Teco cause you will do some operation is the next period and cost for next period should be settle on next period. after that you have to close the order.

So TECO allows the postings.

If the requirement is not allowing any goods movement while system status TECO is active, pls try this approach in the config:
1. go to tcode BS22 (Maintain: System Status)
2. look for the system status TECO.
3. Double click the field "TECO".
4. in the transaction control tab look for the business transaction "RMWA" or goods movement (you can type it in the lower left corner buttom box).
5. select the radio button from "Allowed" to Disallowed".
6. save your changes.

 

不允许工单在已发料后再删除该物料

Tcode: OPJB 修改750的Category.

 

控制工作单的需求数不能小于已发料数

方法一:

修改原程序:LCOMKF5H

MESSAGE I752(CN) WITH RESBD-MATNR AFELD_1 AFELD2.

方法二:

出口PPC00023

INCLUDE ZXCO1U23.

if IS_COMPONENT-BDMNG < IS_COMPONENT-enmng.
* message 'xxxx' type 'E'.
raise NO_CHANGES_ALLOWED.
endif.

 

工单cost balance不为0的处理方法

该订单以前结算了在产品。你需要检查:
1.该订单是否已完成-订单状态是否DLV?
2.如果是DLV,你需要重新运行KGI2(overhead), KKAX(wip),KKS2(variance)and KO88
(settlement)。
3.如果不是DLV,但你仍然要关闭订单,你要将订单设为TECO(technical complete技术性关闭)。
同样运行上述tcode.

 

不能收货或不能建BOM

不能收货或不能建BOM时提示

Material type ROH cannot be used with item category L

原因是OMS2中物料类型的Quantity/Value updating下对应的PLANT没有选中这两项


 

当 MySQL 中的数据量较大时,如何优化 update 查询的执行速度,可以考虑以下几个方面: 1. 索引优化:在 update 操作时,MySQL 会对表进行写锁,如果更新的数据行很多,会导致其他查询请求等待锁释放,从而影响性能。可以通过在 mes_production_order 和 sap_sale_order_more 表中创建 PRO_CODE 和 AUFNR 的联合索引来加快查询速度。 2. 分批更新:将更新操作分批执行,每次只更新一部分数据,可以避免表锁定所带来的性能问题。可以使用 limit 关键字和循环语句来实现分批更新操作。 3. 避免全表扫描:在 update 操作中,避免全表扫描是很重要的。可以通过查询执行计划来查看 MySQL 是否使用了索引,如果没有使用索引,可以考虑增加索引或者优化查询语句来避免全表扫描。 4. 内存调优:在 MySQL 中,内存配置对于数据库的性能来说至关重要。可以考虑调整 MySQL 的内存配置参数,如 innodb_buffer_pool_size 等,来提高查询性能。 综上所述,可以尝试以下优化方案: ``` 1. 在 mes_production_order 和 sap_sale_order_more 表中创建 PRO_CODE 和 AUFNR 的联合索引: ALTER TABLE mes_production_order ADD INDEX idx_pro_code (PRO_CODE); ALTER TABLE sap_sale_order_more ADD INDEX idx_aufnr (AUFNR); 2. 分批更新: DECLARE start INT DEFAULT 0; DECLARE limit INT DEFAULT 1000; SET @total = (SELECT COUNT(*) FROM mes_production_order); WHILE start < @total DO UPDATE mes_production_order, sap_sale_order_more SET mes_production_order.ZSTATUS = sap_sale_order_more.ZSTATUS WHERE mes_production_order.PRO_CODE = sap_sale_order_more.AUFNR LIMIT start, limit; SET start = start + limit; END WHILE; 3. 避免全表扫描: 通过 EXPLAIN 查询执行计划来查看是否使用了索引,如果没有使用,可以考虑增加索引或者优化查询语句。 4. 内存调优: 根据实际情况,适当调整 MySQL 的内存配置参数,如 innodb_buffer_pool_size 等。 ```
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值