BDC

[Former Member]

Hi,

I have one query regarding BDC.

I am using call transaction method to upload the data in MM01 TRANSACTION.

I recorded the transaction & wrote the logic.

I am interested to upload the 1000 data. I would like to ask that for every time i have to press enter to upload the data in MM01 screen??

[former_member206396]

hai,

you can run the program in background for 1000 data. no need to enter "ENTER"...

any queries do reply...

Rama krishna S

[Former Member]

Hello Salil,

U can do this when ur calling the transaction ie.

Use The FM POPUP_TO_CONFIRM before call the Transaction asn if the answer is 1 update the material else roll back.

If useful reward

Vasanth

[Former Member]

Hi,

I am asking for call transaction method.

I m giving the processing mode A & update mode A.

For dealing for multiple record every time I have to press enter or any alternative is available??

Will u send me sample coding for fm popup_to_confirm to do proper coding???

[abdul_hakim]

give mode N.

Cheers,

Abdul Hakim

[Former Member]

Hi Salil,

CALL TRANSACTION 'MM01'

USING it_bdcdata
<b>MODE   'N'</b>                     "No Screen Mode
<b>UPDATE 'S'</b>                     "Sync Update
MESSAGES INTO it_bdcmsgcoll.   "Messages Internal table

Let the update be Synchronous if there are 1000 records, it is little bit slow, because it waits for the DB update to happen before continuing with the next record.

For the Dispaly Options <b>MODE</b> can be specified.

<b>... MODE mode</b>

Effect

The processing mode can take the following values:

'A' Display screen

'E' Display only if an error occurs

'N' Do not display

'P' Do not display; debugging possible

If the MODE addition is omitted, then the processing mode is 'A'.

If a screen is displayed in processing mode 'E' because the system reached the end of the BDC data, the system automatically switches to processing mode 'A'.

If breakpoints are set in a transaction tcod called using the CALL TRANSACTION tcod USING itab variant, these are not actually reached in 'N' mode. The system tries to insert data in the Debugger screen; the call ends with SY-SUBRC = 1001 and the message "Batch input data is not available for screen SAPMSSY3 0131" (S 00 344).

Conversely, in 'P' mode, transaction screens are processed in the background (as in 'N' mode) and debugging is possible.

Regards,

Arun Sambagri.

[andreas_mann3]

hi,

pay attention to these alternatives:

1) abap RMDATIND

2) fm MATERIAL_MAINTAIN_DARK

advantage : few or no changes by change of sap-release

Andreas

[Former Member]

Hi Andreas,

Will u send me some sample code???