Finding BADI in a screen

At times, you might require finding a BADI on a screen and in this situation, we can leverage of

Object Type - 'CL_EXITHANDLER' to find the list of BADI's available on the screen.

In order to access this object type, we need to use T.Code - SE24 class builder.

Click on display and select method 'GET_INSTANCE' to enter the method.

put a breakpoint at 'CALL METHOD cl_exithandler=>get_class_name_by_interface'

Then go to the required screen where exit needs to be identified. For instance, here I have executed T.Code VA01 then BADI's relevant to the initial screen will be displayed . To view the relevant BADI's click on Exit_Name parameter of Method.

Then click on F8 or execute to go to the next available BADI on the screen and if no BADI exist then the screen will be displayed.

Ensure to remove breakpoint upon completion of the required task else breakpoint will be triggered for all screens which are displayed.

Thank you.

Comments

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1> VBAK-<Custom Field 2> VBAK-<Custom Field 3> ENDCHAIN. Thank you.

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...

SAP Logistics

Search This Blog