bdc

[Former Member]

Hi

experts can please tell me what r the option i should check in recoding va02 through

call transaction method.

1.default size

2 cont. after commit

3 not a batch input session

4 simulate background mode.

thanx in advance.

[Former Member]

1. DEFAULT SIZE

reagrds,

anju

[Former Member]

Hi,

Defualt size: Is the Screen size while recording transaction

Cont. Aftr Commit: Call Transaction is not completed by Commit.

Not a bactch input session: It will not create a batch, No session Method.

Simulate background mode: No Screens will be displayed while uploading

Reward if useful!

[Former Member]

Hi Gaurav,

Checking 'Default Size' option alone is enough for recording.

Default Size: It specifies the no of line items visible on screen, before doing a page down so as to

provide us the option to write BDC logic correctly.

Regards,

Dilli

[Former Member]

<b>Call transaction.</b>

1) asynchronous processing 
2) can transfer small amount of data 
3) processing is faster. 
4) errors need to be handled explicitly 
5) data is updated automatically

Solution: Use CALL TRANSACTION 'ME21N'  OPTIONS FROM w_ctu_params.( type CTU_PARAMS) 

This structure contains the follwing. 

" DISMODE :  Display mode (like the MODE addition) 
" UPDMODE:  Update mode (like the UPDATE addition) 
 " CATTMODE: CATT mode (controls a CATT) 
"     CATT mode can have the following values: 
            ' ' No CATT active 
            'N' CATT without single-screen control 
            'A' CATT with single-screen control 

" DEFSIZE : Use default window size (Here we are handling those transaction by giving default window size) 
" RACOMMIT: Do not end transaction at COMMIT WORK 
" NOBINPT  : No batch input mode (that is, SY-BINPT = SPACE) 
" NOBIEND : No batch input mode after the end of BDC data.

The components DEFSIZE , RACOMMIT, NOBINPT, and NOBIEND always take the following values:

'X' Yes

reward points if it is usefull ...

Girish