topic Re: BDC SYNTAX ERROR and it going to Dump in Application Development and Automation Discussions

BDC SYNTAX ERROR and it going to Dump

Former Member — Wed, 29 Sep 2010 06:01:26 GMT

Hi All,

I got an requirement in 4.7version it is fine to work both the Call transaction and Skip first screen is working fine ,after upgaradation to ECC 6.0 both Call Transaction and Skip First screen are not working simultaneously and it is going to DUMP can any one suggest me both the statements have to work simultaneously ,

The below statement which they have decalared in Z Function module.

CALL TRANSACTION 'VA12' USING BI MODE 'E' AND SKIP FIRST SCREEN.

LEAVE TO TRANSACTION 'ZA02' AND SKIP FIRST SCREEN.

Regards,

Venkat

Re: BDC SYNTAX ERROR and it going to Dump

Former Member — Wed, 29 Sep 2010 06:08:01 GMT

Hi Venkat,

This problem will come because of the screen changes from 4.7 to ECC 6. Screen no in previous version and new version

will not be same always. You can compare the 'VA12' screen in 4.7 and ECC 6 and modify your BDCDATA table accordigly.

Thanks,

Pawan

Re: BDC SYNTAX ERROR and it going to Dump

amit_khare — Wed, 29 Sep 2010 06:11:41 GMT

Is it possible to simulate AND SKIP FIRST SCREEN using BDC?

You can use CALL TRANSACTION ... AND SKIP FIRST SCREEN without USING, but you can't use it with CALL TRANSACTION ... USING.

You can simulate AND SKIP FIRST SCREEN by recording the first screen + Enter key, and call it using display mode 'E' so that the screen remains displayed (otherwise the transaction terminates at the end of the BDC data).

Moreover, you need to add the same first screen + the exit command to the BDC data, so that when the user returns to this first screen, it is not displayed and the transaction terminates.

~ From SDN Wiki

Re: BDC SYNTAX ERROR and it going to Dump

Former Member — Wed, 29 Sep 2010 06:19:15 GMT

Thanks for ur information,

CALL TRANSACTION 'VA12' USING BI MODE 'E' AND SKIP FIRST SCREEN.

Please suggest me how to write the statement with both Call transaction and using have to work ?

Regards,

venkat

Re: BDC SYNTAX ERROR and it going to Dump

Former Member — Wed, 29 Sep 2010 06:28:03 GMT

If you are knowing the screen name while recording why dont you use BDC_CURSOR and pass the screen no and field value which will make things easy. Other than that in your case while upgradation these screen numbers might have been changed and thatsy it is going to dump. Check it again. Hope this is useful.

Regards

Vinodh A

Re: BDC SYNTAX ERROR and it going to Dump

Former Member — Wed, 29 Sep 2010 07:02:33 GMT

HI,

I Found one function module whether it works r not ? but any one can suggest me with this below code how to pass it to the Function module.

CALL TRANSACTION 'VA12' USING BI MODE 'E' AND SKIP FIRST SCREEN.

In the below function module how to pass BI Mode 'E' and Skip First screen ,please suggest me.

The Function module is

CALL FUNCTION 'ABAP4_CALL_TRANSACTION'

EXPORTING

TCODE =

SKIP_SCREEN = ' '

MODE_VAL = ' '

UPDATE_VAL = 'A'
IMPORTING
SUBRC =
TABLES
USING_TAB =
SPAGPA_TAB =
MESS_TAB =
EXCEPTIONS
CALL_TRANSACTION_DENIED = 1
TCODE_INVALID = 2
OTHERS = 3

IF SY-SUBRC <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

Re: BDC SYNTAX ERROR and it going to Dump

Former Member — Wed, 29 Sep 2010 07:19:15 GMT

See demo code. SAPBC420_TRAD_DEBI_CREATE_1

Regards,

Amitava