Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Underlying Program Differences

Former Member
0 Likes
2,141

Please excuse me if this is not the right forum for this question as this is my first posting here and I am relatively new to SAP.  I am trying to figure out what the difference is between executing a transaction and viewing the status to see the underlying program versus accessing table TSTC to find the underlying program.  When I execute transaction code F.21 and view the status it tells me the underlying program is RFDEPL00 however when I access F.21 via the TSTC table it tells me the underlying program is SAPMS38M.  I am just trying to figure out why I am getting two different programs and what is the main difference in determining the underlying program in the two scenarios mentioned above.   I have viewed several threads but have been unsuccessful in finding an explanation.  Thank you.

1 ACCEPTED SOLUTION
Read only

gouravkumar64
Active Contributor
0 Likes
1,830

Hi,

As per I think,this is a one to many relationship between Any program & tcode.

You can create as many as tcode for a program.

If you check that program name on se80. You will see the difference.

See the screen shot here.

Hope it helps a little.

Thanks

Gourav.

5 REPLIES 5
Read only

former_member392866
Active Participant
0 Likes
1,830

Hi Jason,

The program name which is showing in TSTC table is for global i.e for multiple related tcodes like F.21 , F.22 , F.23.......... are used for same program(you can find all tcodes for this program by goto SE80 and select program and give program name and by click on Transactions codes - it's module pool program)

But in Status of particular tcode (F.21) program is related to this tcode only...

you can find difference by seeing status of F.21 and F.22 program names.. it should be different

Hope you got clear idea about this . Thank you .

Regards,

Balaji.

Read only

gouravkumar64
Active Contributor
0 Likes
1,831

Hi,

As per I think,this is a one to many relationship between Any program & tcode.

You can create as many as tcode for a program.

If you check that program name on se80. You will see the difference.

See the screen shot here.

Hope it helps a little.

Thanks

Gourav.

Read only

0 Likes
1,830

Hi Jason,

SAPMS38M-

This program covers the ABAP/4 program development and ABAP/4 reporting functions.

  • ABAP/4 program development provides functions for developing ABAP/4 programs. ABAP/4 reporting is a part of this program.
  • ABAP/4 reporting enables end-users to access reports

This is a Module pool Program- more on module pool program http://wiki.scn.sap.com/wiki/display/WDABAP/MODULE+POOL+PROGRAMMING

This module pool program is assigned to many sap FI tcodes. It sets screen properties common to all these reporting transactions. And finally it calls the actual program RFDEPL00.

This is the actual program which gets executed when you run F.21.

Hence u find SAPMS38M in TSTC and RFDEPL00 from status for F.21.

Hope this helps!

br,

Maju

Read only

Former Member
0 Likes
1,830

F.27 is a parameter transaction.

TSTC entry, or checking in transaction SE93 would give you the program to run, and parameter passed to it.

So, F.27 starts another transaction SA39, give parameter RFKORK00 in selection screen and skips the initial screen.

On the other hand, WE02 is a report transaction. It runs the report, taking your to default selection screen 1000.

Read only

Former Member
0 Likes
1,830

Thank you all for such a quick response.  In my opinion you all had the right answer.  I was just trying to educate myself a little more in the differences and you all added some clarity.  However I am actually an auditor so when I gain access to a clients SAP system I am sometimes very limited in the Tcodes in which I can access.  SE80 and SE93 are two in which I wish I had access to but unfortunately I typically do not.