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.

Copying <strong>Data</strong> to Screens<br />

© SAP AG<br />

Sessions<br />

TCODE<br />

=<br />

TFBA’<br />

Customer no. 1<br />

Location Berlin<br />

PostCode11111<br />

Tel. 123<br />

TCODE<br />

=<br />

TFBA’<br />

Customer no. 21 21<br />

Location Hof<br />

Post.code 93333<br />

Tel. _<br />

Screens<br />

Customer no. 1<br />

Name Hess<br />

PostCode 11111<br />

Location Berlin<br />

Tel. 123<br />

Customer no. 21 21<br />

Name M ller<br />

Post.code 93333<br />

Location Hof<br />

Tel. _<br />

. . . . . .<br />

Customer<br />

master recs.<br />

Name Hess<br />

Post.code 87342<br />

Location Ulm<br />

Tel. _<br />

Name M ller<br />

Post.code 60000<br />

Location Frankf.<br />

Tel. _<br />

When you process a session with Transaction SM35, the system uses the transaction code (TFBA in<br />

this case) to search for the start screen. Only the relevant session data is copied to this start screen.<br />

The subsequent screen is then processed. First the data is read from the SAP database and then the<br />

session data is copied to the screen.<br />

When the transaction has been processed, the system searches for the next transaction code in the<br />

session and starts the transaction.<br />

. . .

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

Saved successfully!

Ooh no, something went wrong!