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. Dynode Software11 March 2021 at 04:23

    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. Balan Logistics Movers and Packers5 May 2021 at 06:39

    This comment has been removed by the author.

    ReplyDelete
  3. KITS Technologies6 June 2021 at 21:05

    oracle sql plsql online training
    go langaunage online training
    azure online training
    java online training
    salesforce online training
    hadoop online training
    Data Science online training
    linux online training
    etl testing online training
    web methods online training

    ReplyDelete
  4. PrasannaNareshIT12 July 2023 at 03:35

    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

[SAP EWM] Batch job to reprocess the failed queues in SMQ1 and SMQ2

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than  < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.
Post a Comment
Read more

[SAP SD] Mass deletion of deliveries in SAP

If there is the requirement for collective deletion of Outbound deliveries in standard, the following can be performed. Transaction VL10* with corresponding user role settings can meet this requirement. Go to VL10*, only flag indicator 'With Deliveries' in 'Data Selection' column in User Role After flagging above indicator, go into the following screen. Then flag indicator of 'Add to delivery', and fill the delivery numbers or other parameters into corresponding fields and then execute In the display screen, select the lines and click 'Delete' button
Post a Comment
Read more

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...
1 comment
Read more