Posted by [IP Address: 192.83.224.17] 'marty' on July 24, 2001 at 21:40:15 EST:
In Reply to: ABAP - Session BDC posted by [IP Address: 192.83.224.17] 'RaviMcJohn' on July 20, 2001 at 00:56:03 EST:
: Hi everybody
: Please explain what is advantage of session BDC. Diffirence between Session BDD/Call Transaction Method.
: Johan
R2 and R3 follow similar prinicples. BDC lets you run a job in background (or batch in the R2 MVS case) that creates a batch of transactions. The major purpose we use it for (on R2) is to interface with other systems.
An R2 example, to update names and addresses: We read an MVS dataset, and use the data to create a series of PA31s
basic requrements. You can execute this batch from transaction SBDC, or in R2's case, useing T1SA and a BATCH / CICS interface.
You need to:
define and populate a signon screen
define and populate the screens you're writing to
ALL the OK codes
* dynpro declarations
DYNPROS:
D00001,
SAPMP50G_1000 ALIAS D1000,
MP000200_2013 ALIAS D0002.
* constants
DATA:
CD_TRANS_PA31 LIKE SY-TCODE VALUE 'PA31',
CD_SYNC_POINT(1) TYPE C VALUE 'S',
CD_PFKEY_CHANGE(4) TYPE C VALUE '12',
CD_PFKEY_SAVE(4) TYPE C VALUE '13',
CD_INFTY_PERSONAL_DATA(5) TYPE C VALUE '=0002'.
.....
.,...
*process D00001 once only
REFRESH DYNPRO D00001.
D00001-MANDT = SY-MANDT.
D00001-BNAME = SY-REPID.
TRANSFER-DYNPRO D00001.
LOOP.
REFRESH DYNPRO D1000.
MOVE: CD_TRANS_PA31 TO D1000-TC,
CD_SYNC_POINT TO D1000-SP,
DATA_TAB-PERNR TO D1000-RP50G-PERNR,
CD_INFTY_PERSONAL_DATA TO D1000-RP50G-CHOIC,
CD_PFKEY_CHANGE TO D1000-FCODE.
TRANSFER-DYNPRO D1000.
REFRESH DYNPRO D0002.
MOVE: DATA_TAB-VORNA TO D0002-P0002-VORNA,
DATA_TAB-NAME2 TO D0002-P0002-NAME2,
DATA_TAB-NACHN TO D0002-P0002-NACHN,
DATA_TAB-INITS TO D0002-P0002-INITS,
CD_PFKEY_SAVE TO D0002-FCODE.
TRANSFER-DYNPRO D0002.
ENDLOOP.