New features in TRANSACTION version 10.6/10.7 > Programs used with TRANSACTION > Winshuttle DIRECT

Back to

Programs used with TRANSACTION

Winshuttle DIRECT

Recording scripts from Winshuttle DIRECT

To record a new script from a DIRECT template

  1. Click New.
  2. On the Record pane, click Select fields from a DIRECT template.

    The DIRECT templates page appears. Select a template from the Winshuttle template repository, or browse to a locally-stored template. If not templates are listed, click Get/Refresh list to load available templates.

    Enter info in any fields you require. You must add a title and you must add the time it takes for this business process to add one record by using the SAP GUI. The time setting is used by TRANSACTION for ROI calculation.

    The SAP metadata details are filled from the DIRECT metadata details. Therefore, the creator for the TRANSACTION script is the same as the creator of the DIRECT template it is based on.

  3. On the Import Direct file page, select from the fields as required.
  4. Select individual fields as desired.

    You can use Select all or Clear all for bulk selection or omission of fields in the currently loaded category and section. Fields marked "Mandatory" cannot be cleared.

  5. Select groups of contiguous or noncontiguous fields by clicking CTRL and then clicking each row. Right-click the selected fields, and then click Select Row(s) or Deselect Rows(s).

    Note: Fields marked "Mandatory" cannot be cleared.

  6. Click Finish to save the file as a new TRANSACTION script. The Mapping pane appears. You are ready to map the template.

Note that loops are created automatically around table categories, but you must set properties.

All tab

The All tab displays all fields available in the imported DIRECT script for a selected category, regardless of its MR80 designation.

Mapping DIRECT scripts

The mapping for TRANSACTION scripts that were created by using DIRECT templates is similar to that for scripts that are created through the recording process. For basic information about mapping, see The TRANSACTION Getting Started Guide.

Here are some ways in which DIRECT scripts differ from TRANSACTION scripts:

Adding fields to a TRANSACTION script that was created in DIRECT

After a DIRECT-based script is created, you may need to add fields. Fields can be added from the TRANSACTION Mapper.

To add fields in a DIRECT-based script from within TRANSACTION

  1. Open the script in the Mapper. Select a row. The new rows will be inserted above the selected row.

    For field insertion to work correctly, the top rows should be field rows, and not log fields, table, do-while or if rows.

  2. Click the Edit tab, and then click Add New Field.
  3. Log on to SAP.
  4. From the field list, select the new fields and select the padding type. If a parent category has multiple tables or structures, you can select any of the available fields.

    Only unique fields that are not already included in the mapper can be selected. Duplicate fields result in an error message.

    The MRD specification that is required in DIRECT is not required in TRANSACTION. Mouse over the newly-added field to see the padding type that is displayed on the Properties pane.

Support for scripts without input

Sometimes BAPIs require pre- and post-BAPIs to execute completely. For example, BAPI_BUS2001_CREATE must be preceded by BAPI_PS_INITIALIZATION. The problem, however, is that BAPI_PS_INITIALIZATION does not require input and, therefore, cannot run in TRANSACTION.

To overcome this difficulty, Winshuttle offers the BapiRule.xml file. The file is installed automatically when you install TRANSACTION, in the default location of C:\Program Files (x86)\Winshuttle\TRANSACTION\BapiRule.xml.

Also in this section

A1 Dataloader

Using TRANSACTION with Virsa Firefighter