Application Development 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: 

BDC initial screen for PA30 different from normal transaction call

Former Member
0 Kudos

Hi,

The inital screen for PA30 transaction call is SAPMP50A , 1100. I have done recording for pa30 and I see that the initial screen is SAPMP50A , 1000. I see that both the screens are different and the user is expecting the bdc call to be similar to PA30 direct call.The bdc is in all screen mode.

Please let me know how I could correct this.

Thanks in advance.

2 REPLIES 2

Former Member
0 Kudos

Hi,

The initial screen would be SAPMP50A & 1000 .. please do the recording once again ...

for ex:

PERFORM bdc_dynpro USING 'SAPMP50A' '1000'.

PERFORM bdc_field USING 'BDC_OKCODE'

lv_okcode. " <--- INS ....

PERFORM bdc_field USING 'RP50G-PERNR'

it_pernr-pernr.

PERFORM bdc_field USING 'RP50G-TIMR6'

'X'.

PERFORM bdc_field USING 'BDC_CURSOR'

'RP50G-CHOIC'.

PERFORM bdc_field USING 'RP50G-CHOIC'

lv_infty. " <-- infotype name

Regards,

Srini.

Former Member
0 Kudos

In SHDB, check the checkbox "Not a Batch Input Session" when recording. In the code, Call the "Call transaction options from" variant and pass the LS_CTU_PARAMS-NOBINPT = 'X'.