1927793 ME_PROCESS_PO_CUST (or user exits) not triggered at custom field in ME21n

原创已于 2022-10-28 17:13:55 修改 · 796 阅读

0 ·

本内容遵循CC 4.0 BY-SA版权协议

收录于

SAP-ABAP

于 2022-10-28 17:09:35 首次发布

博客围绕在BADI ME_PROCESS_PO_CUST实现方法或用户出口更新自定义和标准字段时出现的问题展开。症状一是更改自定义字段时ME_PROCESS_PO_CUST未触发，症状二是复制采购订单项目时自定义字段未复制。分析了原因并给出解决办法，还提醒增强系统时需接受系统逻辑差异。

You implemented PROCESS_ITEM and/or PROCESS_HEADER method in BADI ME_PROCESS_PO_CUST or user-exits in enhancement MM06E005 to update custom and standard fields.

Symptom 1: You change only a custom field, but ME_PROCESS_PO_CUST not triggered
Symptom 2: If you copy an item of the PO (or create a new PO with reference), custom field not copied to the new item / new PO

Environment

Materials Management (MM)
SAP ERP Core Component
SAP ERP
SAP enhancement package for SAP ERP
SAP enhancement package for SAP ERP, version for SAP HANA

Cause

BADI ME_PROCESS_PO_CUST is not designed to be triggered on changing the values of custom fields.

Resolution

For Symptom 1:
PROCESS_ITEM and PROCESS_HEADER methods are triggered only if there was a change in any of the standard fields. But not triggered if only a custom field changed
For Symptom 2:
In standard, we do not copy custom fields since the business logic behind the filling of these fields is not known in standard process. The reference document data is available in structure REKPO and you need to implement the user-exits in enhancement MM06E005 if you expect the values to be copied. For example user-exit EXIT_SAPMM06E_016 to copy reference data to the new item.

All in all take into account that standard SAP system's logic is built on standard system elements, if you extend or enhance the system the system not every case react to the custom applied solution as it react to the standard system element's usage, like in the above case on the fields change - this you have to accept when you try to enhance the standard system.

标签

#abap