Ansicht
Dokumentation

MMPUR_SOA_SESDLT_MAI - BAdI: Data Processing before SES Deletion (SOA Inbound)

General Data in Customer Master   General Material Data  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the Service Entry Sheet (MM-PUR-SRV-SES) component. It is called after the standard mapping of the API Service Entry Sheet - Create, Delete (Lean Services) (ServiceEntrySheetRequest_In). Before deleting a service entry sheet, you can use this BAdI to modify the data processing after the standard mapping. By implementing this BAdI, you can change the default behavior.

• BAdI method: MAP_APPLICATION_DATA_IN (Modify Data Processing before SES Deletion)

Note: We recommend taking a look at the documentation of the BAdI method Modify Data Processing before SES Deletion (IF_SOA_SES_DLTIN_MAP_APL_ IN~MAP_APPLICATION_DATA_IN) 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_APL_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 Fieldsapp

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 importing parameters IS_HEADER and IT_MESSAGES to the changing parameters.

Note: To use this BAdI, don't skip the standard mapping. This BAdI depends on the BAdI implementation Customized XML Mapping before SES Deletion (SOA Inbound) (MMPUR_SOA_SESDLTIN_MAP_XML_IN) as the standard mapping can be skipped through the changing parameter CV_SKIP_STANDARD_MAPPING (ABAP_BOOL). In this case, you should stick to the default setting ABAP_FALSE.

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.

• IS_HEADER

This importing parameter contains the service entry sheet header data.

• IT_MESSAGES

This importing parameter contains the messages that were defined in the standard mapping of the service entry sheet.

• 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_APL_IN

You can use this example implementation to append error messages to the changing parameter CT_MESSAGES (BAPIRETTAB). If an error message is triggered, the service entry sheet won't be deleted. In detail, you define that service entry sheets from supplier 1000000001 are not deleted. After the implementation, an error message occurs if a service entry sheet of supplier 1000000001 is chosen and the service entry sheet is not deleted.

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: Modify Data Processing before SES Deletion

Fill RESBD Structure from EBP Component Structure   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 5712 Date: 20240523 Time: 190831     sap01-206 ( 158 ms )