Ansicht
Dokumentation

MMPUR_SOA_SESDLT_MXI - BAdI: Customized XML Mapping before SES Deletion (SOA Inbound)

ABAP Short Reference   CPI1466 during Backup  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the Service Entry Sheet (MM-PUR-SRV-SES) component. You can use this BAdI to replace the standard mapping with your own customized XML mapping. The BAdI is called before the standard mapping, i.e. before deleting a service entry sheet. Be aware that if you set the flag to ABAP_TRUE( CV_SKIP_STANDARD MAPPING) to skip the standard mapping and replace it with your own XML mapping, the BAdI Data Processing before SES Deletion will also be skipped. For more information, see section Requirements.

• BAdI method: MAP_XML_DATA_IN (Customize Mapping before SES Deletion)

Note: Read the documentation of the BAdI method Customize Mapping before SES Deletion (IF_SOA_SES_DELIN_MAP_XML_IN~MAP_XML) in detail before implementing custom logic. This method provides you with instructions on how to do this without breaking standard application logic.

Note: We recommend taking a look at the implementation example class: CL_EXMP_SESDLTIN_MAP_XML_IN (also see section Example).

You must create and activate your own implementation of this BAdI and give the implementation a short text. To do this you will need the following authorizations:

• Administrator Role for Custom Fields app

To implement the BAdI follow these steps: Go to Custom Fieldsapp > Custom Logic tab > Click + to add your implementation > Select Procurement: Service Entry Sheet Header as Business Context > Select the BAdI you want to implement > Enter a short description of your implementation > Click on Create > Choose whether you want to use the example implementation.

It is also a mandatory step for all implementations to move the

• the reference ID of the importing parameter (is_inbound_message-service_entry_sheet_request_ms-message_header-reference_id-content) to the reference ID of the changing parameter (cs_header-purgdocexternalreference) as well as

• the external sender system ID (is_inbound_message-service_entry_sheet_request_ms-message_header-sender_business_system_id) to the external sender system ID of the changing parameter (cs_header-purgdocexternalsystem).

Note: To replace the standard mapping with your XML mapping, skip the standard mapping by setting the flag to ABAP_TRUE (changing parameter CV_SKIP_STANDARD MAPPING). Otherwise, the standard mapping will be called nevertheless.

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

• IS_INBOUND_MESSAGE

This importing parameter contains the SOA Request.

• CV_SKIP_STANDARD_MAPPING

This changing parameter allows you to skip the standard mapping before deleting a service entry sheet. To skip insert: ABAP_TRUE. To call the standard mapping, nevertheless, insert: ABAP_FALSE (default setting).

• CS_HEADER

This changing parameter allows you to adjust the service entry sheet header data.

• CT_MESSAGES

This changing parameter allows you to adjust the messages that were defined in the standard mapping of the service entry sheet.

You can find example implementations in the BAdI Builder on the Enhancement Spot Element Definitions tab in the Implementation Example Classes section.

The following example implementations are available:

• CL_EXMP_SESDLTIN_MAP_XML_IN

You can use this example implementation to implement specific use cases depending on the supplier and purchasing group in the service entry sheet. In detail, you can append error messages to service entry sheets that contain items of supplier 1000000001. As a result, the service entry sheet is not deleted. Further, the standard mapping will be skipped for purchasing group 001. Otherwise, the standard mapping is called.

For information about the implementation of BAdIs in the context of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

For detailed information on the BAdI method see: Customize Mapping before SES Deletion

Fill RESBD Structure from EBP Component Structure   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 6394 Date: 20240606 Time: 232510     sap01-206 ( 187 ms )