Call Transaction or Leave to Transaction not working with PID BAN

[Former Member]

Hi, I am currently working in 5.0 and have tried CALL TRANSACTION CODE 'ME53N' after setting BAN to the proper PR #. What is actually being returned is the last one saved in all instances.

Is there any way around this problem.

Any assistance would be greatly appreciated.

Thanks

John

[Former Member]

Hi John,

DATA LV_ORDER TYPE EBAN-BANFN VALUE '10021237'.

SET PARAMETER ID 'BAN' FIELD LV_ORDER.

CALL TRANSACTION 'ME53N' AND SKIP FIRST SCREEN.

Should work.

Regards,

Suman Jagu

[Former Member]

Hi Suman, you are right it should but it does not. I've tried all flavors of the call transaction and the leave to transaction but neither of them work.

Thanks for you input.

John

[Former Member]

I don't have access to the transaction, but on your selection screen for BANFN, is a PID declared for the data element. Use F1-technical details and be sure the PID is actually utilized on the screen.

Also, debug and be sure that PID is not reset before your actual transaction call. Are you doing a transaction call or submit?

[Former Member]

I've already debugged to ensure the PID was correctly set. It's the same PID that shows up on technical details when I do an F1 go to the wrench. I've also put a break in the badi open and it is set there as well. But when it goes to get the PR it pulls up the last one saved.

[Former Member]

hello

Ihave the same promlem

did you find a way to get the right purchase req?

thanks

shachar

[Former Member]

Hi Shachar,

I did not. I've tried freeing all memory and reseting the PID and nothing different. It confusing but I have left the code in there because when you hit the pencil it changes from display to change mode and locks the PR so right now they get kicked back to the original PR.

It's frustrating.

Will post if I find something down the road.