生产订单修改记录的跟踪方法!
2016-06-01 15:42
429 查看
方法一:系统标准方法
如何查找到production order的修改记录呢?因为有很多用户 "赖皮",明明自己修改过某些资料,如qty or component,可就是不承认,并且还大骂SAP大大的有问题 ,真会气死人,所以想记录下来.
HEHE,这里我就摘录一段SAP的NOTES给大家看看,如何去整这玩意.
Note 390635 - Change documents for production and process order
Summary
Symptom
You cannot activate the creation of change documents for production orders and process orders.
Customizing table T399X (parameters dependent on order type) contains field FLG_DOC but you cannot maintain it using the Customizing transactions for production or process orders.
Other terms
Production order, process order
T399X-FLG_DOC
SPRO, BADI
Reason and Prerequisites
It is not intended to use the SAP standard tool for the creation of change documents for production or process orders in the SAP standard system. The indicator in table T399X is only interpreted by maintenance orders and networks.
The reason for this is that the tool cannot determine dependencies of changes and thus would log too many changes that would have a negative effect on the runtime.
Example: A production order contains 10 operations and 1000 components
Case 1: You change the requirements quantity for a component manually.
The system creates a change document for the changed component.
Case 2: You change the planned quantity in the order header manually.
The change causes that the quantites are changed automatically for all operations and components. The system would create
a change document for the changed header quantity,
ten change documents for the automatically changed operation quantities (if defined) and
thousand change documents for automatically changed component quantities.
Solution
Use the SAP enhancement PPCO0007 that is processed when you save order changes. You can find the SAP enhancement in Customizing under the menu path "Shop Floor Control or Production Planning for Process Industries -> Process Order -> System Modifications
-> Enhancements for Order Maintenance -> Enhancement when Saving an Order (Header Fields)".
Here you can define additional logic to decide whether or not the system creates change documents.
For this, you can access either the SAP standard tool for creating change documents or your own tool.
The call of the customer exit takes place in function module CO_ZV_ORDER_POST when you save. The current data of an order header is supplied via parameter HEADER_IMP. For collective orders the exit can be called several times - once for each order in the collective
order.
Remember that a dialog box must not be accessed and a message must not be issued from the exit.
You can use the attached source code as a template for accessing the creation of change documents.
You can also see in the source code how the current and original data of the different order objects can be provided by internal tables.
The example source code uses function module ORDER_WRITE_DOCUMENT that logs - for the ORDER change document object - the changes for the tables transferred to the module.
It may be appropriate to define a separate object for change documents for orders, for example ZZORDER. If required, you can use the ORDER standard object as a template.
The following tables of the order may have to be taken into ac_countfor this type of change document object:
Table Description Production
Process order
AFAB Relationships X
AFFH Production resource/tool X
AFFL Work order sequence X X
AFFT Process instructions X
AFFV Process instruction values X
AFKO Order header data PP
如何查找到production order的修改记录呢?因为有很多用户 "赖皮",明明自己修改过某些资料,如qty or component,可就是不承认,并且还大骂SAP大大的有问题 ,真会气死人,所以想记录下来.
HEHE,这里我就摘录一段SAP的NOTES给大家看看,如何去整这玩意.
Note 390635 - Change documents for production and process order
Summary
Symptom
You cannot activate the creation of change documents for production orders and process orders.
Customizing table T399X (parameters dependent on order type) contains field FLG_DOC but you cannot maintain it using the Customizing transactions for production or process orders.
Other terms
Production order, process order
T399X-FLG_DOC
SPRO, BADI
Reason and Prerequisites
It is not intended to use the SAP standard tool for the creation of change documents for production or process orders in the SAP standard system. The indicator in table T399X is only interpreted by maintenance orders and networks.
The reason for this is that the tool cannot determine dependencies of changes and thus would log too many changes that would have a negative effect on the runtime.
Example: A production order contains 10 operations and 1000 components
Case 1: You change the requirements quantity for a component manually.
The system creates a change document for the changed component.
Case 2: You change the planned quantity in the order header manually.
The change causes that the quantites are changed automatically for all operations and components. The system would create
a change document for the changed header quantity,
ten change documents for the automatically changed operation quantities (if defined) and
thousand change documents for automatically changed component quantities.
Solution
Use the SAP enhancement PPCO0007 that is processed when you save order changes. You can find the SAP enhancement in Customizing under the menu path "Shop Floor Control or Production Planning for Process Industries -> Process Order -> System Modifications
-> Enhancements for Order Maintenance -> Enhancement when Saving an Order (Header Fields)".
Here you can define additional logic to decide whether or not the system creates change documents.
For this, you can access either the SAP standard tool for creating change documents or your own tool.
The call of the customer exit takes place in function module CO_ZV_ORDER_POST when you save. The current data of an order header is supplied via parameter HEADER_IMP. For collective orders the exit can be called several times - once for each order in the collective
order.
Remember that a dialog box must not be accessed and a message must not be issued from the exit.
You can use the attached source code as a template for accessing the creation of change documents.
You can also see in the source code how the current and original data of the different order objects can be provided by internal tables.
The example source code uses function module ORDER_WRITE_DOCUMENT that logs - for the ORDER change document object - the changes for the tables transferred to the module.
It may be appropriate to define a separate object for change documents for orders, for example ZZORDER. If required, you can use the ORDER standard object as a template.
The following tables of the order may have to be taken into ac_countfor this type of change document object:
Table Description Production
Process order
AFAB Relationships X
AFFH Production resource/tool X
AFFL Work order sequence X X
AFFT Process instructions X
AFFV Process instruction values X
AFKO Order header data PP
相关文章推荐
- 2.2 层次闭包性质 练习 2.17 2.20
- java并发编程入门:synchronized 与 Lock 的那点事
- 关于抗锯齿效果与硬件加速的关系
- Android Studio 使用技巧总结
- WPF 之 实现TextBox输入文字后自动弹出数据(类似百度的输入框)
- 如何控制订单发料后不能删除组件
- 关于SharedPreferences的一次问题
- angularjsService
- 我的解决org.apache.commons.lang.xwork.StringUtils异常的方法
- LeetCode:Kth Smallest Element in a BST
- Java8的CompletableFuture之二
- oracle 字段类型详解
- iOS 基于CATransition实现翻页、旋转等动画效果 —— HERO博客
- fehaoa dasheng
- Memcached的MemCachedClient设置过期时限
- 奋斗吧,程序员——第四十九章 死生契阔,与子成说
- smokeping告警配置
- cell圆角效果的绘制
- 敏捷宣言
- Android编程四大组件分别是什么