欢迎您访问程序员文章站本站旨在为大家提供分享程序员计算机编程知识!
您现在的位置是: 首页

SAP CRM的订单模型移植到S/4HANA后,在订单保存功能上作出的改进 SAP成都研究院S/4HANACloudC4CABAP 

程序员文章站 2022-07-08 10:46:44
...

Once an order is saved, our new event callback CRM_SRVO_H_SAVE_EC will be called:

SAP CRM的订单模型移植到S/4HANA后,在订单保存功能上作出的改进
            
    
    
        SAP成都研究院S/4HANACloudC4CABAP 

Main logic is in this tool class, method save_header:

SAP CRM的订单模型移植到S/4HANA后,在订单保存功能上作出的改进
            
    
    
        SAP成都研究院S/4HANACloudC4CABAP 

In save_header, header and item save is done separately within a LOOP:

SAP CRM的订单模型移植到S/4HANA后,在订单保存功能上作出的改进
            
    
    
        SAP成都研究院S/4HANACloudC4CABAP 

A new term "Global Update Buffer"

(1) I introduce a terminology “Global Update Buffer", which consists of three internal table where the corresponding insertion, update and deletion operation for CURRENT ORDER is included.

(2) The "Global update buffer" will be passed into a new update function module for Order Header.

Example, suppose I have made changes on Order description:

SAP CRM的订单模型移植到S/4HANA后,在订单保存功能上作出的改进
            
    
    
        SAP成都研究院S/4HANACloudC4CABAP 

the GUB looks like below:

SAP CRM的订单模型移植到S/4HANA后,在订单保存功能上作出的改进
            
    
    
        SAP成都研究院S/4HANACloudC4CABAP 

save_single_header consists of three steps

Step1 - Each convert class is responsible to merge its own part of change into GUB.

SAP CRM的订单模型移植到S/4HANA后,在订单保存功能上作出的改进
            
    
    
        SAP成都研究院S/4HANACloudC4CABAP 

 

How can each convert class know whether there is any change in current transaction for its responsible component?

I use the function module CRM_ORDER_UPDATE_TABLES_DETERM to detect the change.

SAP CRM的订单模型移植到S/4HANA后,在订单保存功能上作出的改进
            
    
    
        SAP成都研究院S/4HANACloudC4CABAP 

 

Step2 for those component which does not have any change in current transaction, its object buffer must also be merged into GUB.

Consider this scenario, you changes header shipping data ( set SHIPPING ) but no change in ORDERADM_H. If you don't merge the object buffer of ORDERADM_H to GUB, the corresponding field for ORDERADM_H will be initial. So when finally update function module is called, the initial fields of ORDERADM_H will be stored into new header table.

This is done in this method:

SAP CRM的订单模型移植到S/4HANA后,在订单保存功能上作出的改进
            
    
    
        SAP成都研究院S/4HANACloudC4CABAP 

I add a new method GET_OB in convert class' interface. The supported component are looped, to merge its object buffer to GUB.

SAP CRM的订单模型移植到S/4HANA后,在订单保存功能上作出的改进
            
    
    
        SAP成都研究院S/4HANACloudC4CABAP 

Step3 - call new update function module with merged GUB

SAP CRM的订单模型移植到S/4HANA后,在订单保存功能上作出的改进
            
    
    
        SAP成都研究院S/4HANACloudC4CABAP 

Item save has exactly the same logic.

Since it is possible that one order can have different item with different item object type,

SAP CRM的订单模型移植到S/4HANA后,在订单保存功能上作出的改进
            
    
    
        SAP成都研究院S/4HANACloudC4CABAP SAP CRM的订单模型移植到S/4HANA后,在订单保存功能上作出的改进
            
    
    
        SAP成都研究院S/4HANACloudC4CABAP 

Here below is an example, I have made changes on item shipping data:

SAP CRM的订单模型移植到S/4HANA后,在订单保存功能上作出的改进
            
    
    
        SAP成都研究院S/4HANACloudC4CABAP 

And this is how GUB for item looks like:

 

SAP CRM的订单模型移植到S/4HANA后,在订单保存功能上作出的改进
            
    
    
        SAP成都研究院S/4HANACloudC4CABAP SAP CRM的订单模型移植到S/4HANA后,在订单保存功能上作出的改进
            
    
    
        SAP成都研究院S/4HANACloudC4CABAP