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: 

Message tab not getting filled.

0 Kudos

Hi,

here in below statement:

CALL TRANSACTION 'VAP1' USING bdcdata MESSAGES INTO messtab MODE l_mode UPDATE 'S'.

the messages are not getting filled into MESSTAB.but the document is getting updated.

Thanks in Advance.

V V.

2 REPLIES 2

Former Member
0 Kudos

statement should be

CALL TRANSACTION tcode

USING bdcdata

MODE l_mode

UPDATE 'S'

MESSAGES INTO messtab .

and data type for messtab is

data: messtab type BDCMSGCOLL occurs 0 with header line.

Former Member
0 Kudos

hi,

CALL TRANSACTION <transaction code>

USING <bdc table>

MODE <display mode>

UPDATE <UPDATE MODE>

MESSAGES INTO messtab

DISPLAY MODE:

A :display all(default setting)

E :Display only error

N :No display

Update mode

S : continue processing when update is completed(synchronous)

A : continue processing immediately.

Note: messtab,an internal table must have a structure BDCMSGCOLL.

->To make your BDC run on standard screen size SAP has come up with a new option from 4.7 onwards

CALL TRANSACTION <transaction code>

USING <bdc table>

OPTION FROM <opt>

MESSAGES INTO messtab

<opt> has structure of CTU_PARAMS

<opt>-dismode = Same as display mode explained earlier

<opt>-updmode = Same as update mode explained earlier

<opt>-defsize = set this to ‘X’ to make the bdc execute in standard screen size. So whatever is the screen size of the users front-end, the BDC will execute in standard screen size

Checking if Call transaction is successful or not

->Checking sy-subrc may not be always reliable as it can return values like .001 even if the transaction is successful

Best way to check this is to check for the success message in the message table.

-> All transactions give a success message if the transaction is successful. SAP guarantees that these message numbers wont change in any release of SAP.

-> First get the message number, id etc of the success message of the transaction you are trying to call, then check this message number and id in the message table that the call transaction returns. If you find the entry in the message table, the call transaction is successful.

reward if helpful

regards,

sravanthi