cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with transaction button in screen personas SP02

Former Member
0 Kudos

Hi Expert,

I am facing issue with transaction button in screen personas sp02.

I have created a test flavor, I have one transaction button with transaction code IE01 and also i have authorization for transaction IE01.

Now when i save and exit the flavor, and click on button then it does not jump to the respective transaction .

Now if i use a script in the same button then it is working fine.

Can you please help me because if have feature of direct entering into respective transaction then how will it work.

regards,

Vipul

Accepted Solutions (0)

Answers (3)

Answers (3)

0 Kudos

Hello,

I had the same exact issue.  It was resolved by implementing OSS Note 2148349

Former Member
0 Kudos

Dear all,

we have the same issue with transaction button in screen personas sp02.

We created a flavor, We have one transaction button with transaction code va03 and also we have authorization for transaction va03.

Now when we save and exit the flavor, and click on button then it does not jump to the va03 transaction .

Do you got a solution from SAP OSS ?

Former Member
0 Kudos

No Till now i have not got the solution.

Alternate i am running a script to make this happen.

regards,

Vipul

0 Kudos

hello,

have you implemented all the "Required" ITS notes as mentioned in Note 2222773?

specially Note

  • 2148349 - SAP Screen Personas Call transaction variant

Regards,
Sushant

tamas_hoznek
Product and Topic Expert
Product and Topic Expert
0 Kudos

Are you sure you are on Personas 3.0 SP02? Just asking because there was an issue with transaction buttons in SP01 that was corrected with a note but the same should not happen with SP02.

If you are indeed on SP02, is your system fully up-to-date with all notes according to main note 2222773 implemented?

Former Member
0 Kudos

Yes Tamas ,

We are running SP02.

regards,

Vipul

tamas_hoznek
Product and Topic Expert
Product and Topic Expert
0 Kudos

Then, if you are certain that all applicable notes are implemented, I'd suggest opening an OSS incident.