topic Re: BDC Screen SAPMSSY0 0120 selection flag issue ECC6.0 in Application Development and Automation Discussions

BDC Screen SAPMSSY0 0120 selection flag issue ECC6.0

Former Member — Tue, 05 May 2009 13:51:51 GMT

Hello,

i ´am having following issue, we are currently in the upgrade phase from 4.6C to ECC6.0, and of course we have to adjust some Reports.

We are having a Report which is making a call transaction and having as a parameter a BDC table.

The problem is that those BDC is working under 46C but not anymore in ECC6.0.

The called transaction is QC20 Quailty certificates for deliveries. First screen is the selection screen and the second then a listing(SAPMSSY0). There you can select then, for which lines you wanna have a printout.

under 46C the selection was working that way:

SAPMSSY0 0120 X

0000 BDC_CURSOR 04/03

0000 BDC_OKCODE /00

0000 7/03 X

0000 8/03 X

The Report which is making the call transaction has some logic which determine which lines should be flagged and printed out as you can see in the example: 7/03 and 8/03 those lines will be selected

under ECC6.0 those selection is not working anymore, does someone of you have an idea how to flag those lines in the new ECC6.0 environment?

Thx and Regards

Sven

Re: BDC Screen SAPMSSY0 0120 selection flag issue ECC6.0

Former Member — Tue, 05 May 2009 19:01:03 GMT

Try doing a fresh recording in ECC 6.0

Re: BDC Screen SAPMSSY0 0120 selection flag issue ECC6.0

Former Member — Wed, 06 May 2009 06:13:32 GMT

Hi,

have done a new recording already in the new system, but the selection(checkbox) of lines will not be recorded!

Regards

Sven

Re: BDC Screen SAPMSSY0 0120 selection flag issue ECC6.0

Former Member — Mon, 11 May 2009 09:30:09 GMT

close the thread issue is solved.

Re: BDC Screen SAPMSSY0 0120 selection flag issue ECC6.0

Former Member — Tue, 26 Jul 2011 11:48:12 GMT

Hi Sven,

I am having the similar issue on uploading the data via BDC call transaction in ECC6.0. Its is working fine in 4.6c but not in ECC6.0.

Kindly share the way you solved this issue.

Thanks.