The Transaction Control 

Purpose

The Transaction control is an OCX control that allows you to execute R/3 Batch Input transactions from external programs.

You can use the Transaction control to enter data into R/3 by executing R/3 transactions.

Implementation Considerations

The Transaction control can be used in COM-compliant applications, such as those programmed in Visual Basic, C++, and so on.

Features

The Transaction control provides an object oriented view of the R/3 transactions, in that it uses a hierarchy of transactions, screens, and fields collections and objects. You use these objects to enter data into R/3 transactions that accept batch input.

The Transaction control simplifies the use of batch input transactions from external programs in that it eliminates the need to populate the fields of the BDC table and then send the BDC table to the R/3 system. With the Transaction control you need only assign values to fields on R/3 screens. The Transaction control takes care of the data transfer.

Constraints

The Transaction control only enables transaction calls in batch input mode. External programs can send screen values to the transaction, but the interface does not return output field values.

For complete transaction execution (with data transfer in both directions), use the SAP Automation GUI Library.

Activities

To use the Transaction control, you must be very familiar with the R/3 transaction you are calling: you need to know the sequence of screens it contains, and for each screen you need to know the fields it contains and what values those fields can take.

Using the Transaction control you create a transaction and all of its screens, and then you assign values to every field you wish use for data entry. You then call the transaction to perform the batch input.