Skip to main content

[SAP] Easy way to identify customer EXIT or BADI

 At times, We find difficult to identify exits for a program. 

This post will explain you an easy way to find list of  Customer Exits and BADI's available for a program.

Below are the process steps to be followed :

Step 1 : Goto T.Code : SE16N, Enter transaction code 


Step 2 : Fetch program name


Step 3 : Collect Program Name and pass it to TADIR table to fetch development class




Step 4 : Pass Development class again into TADIR table by passing OBJECT as SMOD to fetch all customer exit's and OBJECT as SXSD to fetch BADI's related to the program.

In this case, I have passed SMOD to fetch customer exits.


Step 5 : All Customer exits related to the program are displayed


Step 6 : Once EXIT is identified. To get description related to it, Pass Exits into table MODSAPT and SXS_ATTRT to get descriptions corresponding to them.






Thank you.
 








Comments

  1. Thanks for sharing such a nice post.

    Dynode Software is a high-end software product engineering and consulting company providing Ecommerce web design in Patna for enterprises and startups. We build, improve and scale software products across platforms leveraging disruptive technologies in mobile, web, cloud, analytics, AI and block chain.

    ReplyDelete
  2. This comment has been removed by the author.

    ReplyDelete
  3. Hi
    Nice Post,
    Thanks for Sharing This Article.Thanks for Sharing this Post Linux Online Training - NareshIT

    ReplyDelete

Post a Comment

Popular posts from this blog

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.

Determinations in SAP SD

Plant Determination in Sales Order 1st Preference: System fetches Delivering plant from Customer Material Info Record if Plant is not found at this level then system will look into 2nd Preference:   Delivering plant from Customer Master data if Plant is not found at this level then system will look into 3rd Preference : the Delivering plant for Material Master data If business user overwrites Plant at sales document level then this will be given highest preference. Shipping Point Determination Delivering Plant (Based on above conditions) + Shipping Conditions ( Sales Document Type or  Customer Master Data) + Loading Group ( Material Master ) Storage Location Determination Plant + Shipping Point + Storage Conditions ( Material Master )  ( MALA) Plant + Shipping Point + Situation  ( RETA) Route Determination Departure Zone or Country of the Delivering Plant + Destination Zone or Country of the Ship to Party + Shipping Condition from the Customer Master + Transport