Ansicht
Dokumentation

MMPUR_SOA_SESREV_POP - BAdI: Data Processing after SES Revocation (SOA Inbound)

MMPUR_SOA_SESREV_POP - BAdI: Data Processing after SES Revocation (SOA Inbound)

ROGBILLS - Synchronize billing plans   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the Service Entry Sheet (MM-PUR-SRV-SES) component. It is called after the revocation of a service entry sheet (ServiceEntrySheetRequest_In) and before the data commit. You can use this BAdI to modify the data processing after revoking a service entry sheet. By implementing this BAdI, you can change the default behavior.

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

Note: Read the documentation of the BAdI method Modify Data Processing after SES Revocation 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_SESREVKIN_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 > Choose + 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 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.
  • IV_POSTING_DATE
This importing parameter contains the posting date of the offset of the goods receipt.
  • IV_SES_ID
This importing parameter contains the ID of the service entry sheet.
  • 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 revocation 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 revocation 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_SESREVKIN_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 revoked.

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 Revocation






PERFORM Short Reference   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 4881 Date: 20240523 Time: 203336     sap01-206 ( 137 ms )