17.08.2013 Views

Data Interfaces

Data Interfaces

Data Interfaces

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Technical Implementation<br />

Roll area 1 Roll area 2<br />

REPORT ... .<br />

DATA: BEGIN OF OCCURS ... .<br />

INCLUDE STRUCTURE BDC_DATA.<br />

DATA: END OF .<br />

:<br />

:<br />

PERFORM GENERATE_BDC_DATA.<br />

CALL TRANSACTION <br />

USING <br />

MODE <br />

UPDATE <br />

:<br />

:<br />

CASE SY-SUBRC.<br />

:<br />

:<br />

© SAP AG<br />

The system opens a second roll area for the called transaction. There, it processes the individual screens<br />

and copies the data from the table. When the transaction has finished, the second roll area is released<br />

and the processing continues in the first roll area.<br />

Notes:<br />

In contrast to batch input, there is no error logging. Whether the called transaction is processed depends<br />

on the authorizations of the calling user. The BDC table can only accept data for a single transaction.<br />

This means that before the next transaction call, you must perform a REFRESH on the BDC table and<br />

refill it with data.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!