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

Program is not executed when transaction code is called

Former Member
0 Likes
1,681

Gurus,

I granted transaction code ZBIM to some BIM-program for maintaining HR master data so that a user can exceute that BIM-programa without authorization for tcode SA38.

User autorization includes

- calling ZBIM

- maintain master datain HCM

However, it is not working. When user calls tcode ZBIM, the selection-screen shows up. But when he tries to execute the program with F8, SAP returns immediately back to the menu. Authorization check U53 really doesn't provide any relevant information.

What's the problem?

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
968

I guess you would have gone wrong in choosing the radio button

if its a dialog transaction you need to choose the first option in the start object ( If its a module pool programming ).

You can the change that in change mode by click on edit ->change transaction type.

4 REPLIES 4
Read only

Former Member
0 Likes
969

I guess you would have gone wrong in choosing the radio button

if its a dialog transaction you need to choose the first option in the start object ( If its a module pool programming ).

You can the change that in change mode by click on edit ->change transaction type.

Read only

Former Member
0 Likes
968

Hi,

Even we faced the same issue with some BDC Program even though the transaction is created with correct paramters.

We have deleted the existing Tcode, recreated it.

For our surprise it worked.

Regards

Manasa

Read only

Former Member
0 Likes
968

Hi ,

Try debugging the program and check if the code is executed when you run the transaction.

Also check if all the Check boxes in the GUI Support Subscreen are checked.

Regards

Arun

Read only

Former Member
0 Likes
968

Thanks Karthik, indeed it was a dialog transaction. As I changed it into report transaction the problems were solved.