Ansicht
Dokumentation

MMPUR_SOA_SESDLT_POP - BAdI: Data Processing after SES Deletion (SOA Inbound)

PERFORM Short Reference   ROGBILLS - Synchronize billing plans  
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 deletion of a service entry sheet (ServiceEntrySheetRequest_In) and before the data commit. You can use this BAdI to modify the data processing after deleting a service entry sheet. By implementing this BAdI, you can change the default behavior.

• BAdI method: POST_PROCESSING (Modify Data Processing after SES Deletion)

Note: Read the documentation of the BAdI method Modify Data Processing after SES Deletion (IF_SOA_SES_DELIN_POST_PROC~POST_PROCESSING) 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_POST_PROC (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 >.

It is also a mandatory step for all implementations to move the importing parameter IT_MESSAGES to the changing parameters.

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_CHG

This importing parameter contains the service entry sheet header data.

• IT_MESSAGES

This importing parameter contains the messages that were defined in the mapping of the service entry sheet as well as the messages caused during the deletion of the service entry sheet.

• CT_MESSAGES

This changing parameter allows you to adjust the messages that were defined in the mapping of the service entry sheet as well as the messages caused during the deletion 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_POST_PROC

You can use this example implementation to append an error message to the changing parameter CT_MESSAGES even if only a warning message was raised. If an error is triggered, the service entry sheet won't be 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 after SES Deletion

rdisp/max_wprun_time - Maximum work process run time   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 4712 Date: 20240523 Time: 192151     sap01-206 ( 131 ms )