How BPT Packaged Apps Kit Creates Components when Learning SAP GUI Flows

Available for BPT Packaged Apps Kit Users

When BPT Packaged Apps Kit learns a flow or a business process test, it creates a new business component for each screen or sub-screen through which you navigate in your SAP GUI app. Each screen or sub-screen within a particular transaction is represented as a separate business component.

The name of a learned component is of the form <Transaction code>-<Screen name>. If the transaction code or screen name contains spaces or characters that are not valid in the names of business components, these characters are replaced by underscores (_). For example, if a learned component corresponds to the screen Create Sales Order: Initial Screen in the VA01 transaction, the component is named VA01-Create_Sales_Order_Intial_Screen.

If you navigate from one screen to a different screen or tab, and then return to the original screen, a new component is created with the same name as the component corresponding to the original screen, with a numerical suffix appended to differentiate between the components. For example, suppose the component corresponding to a screen is named VA01_Test. If you return to the screen, a new component is created named VA01_Test_01. Reusing existing components in your learned flow or business process test minimizes the number of learned components for similar or identical screens.

For each user operation within a screen that requires data specified by the user, an input component parameter is created for that step. the input component parameters that are created during the Learn process are automatically set as flow parameters. The value input during the Learn process is used as the default parameter value. For example, a parameter would be created for a value entered in a text field.

The name of an automatically generated parameter is the same as the name of the relevant field in the application. For example, in a Display Sales Order transaction, the parameter name of the order number would be Order. If a flow contains several components that have the same parameter name, an incremental suffix is added to subsequent parameter names (for example, Order_1, Order_2) in order to differentiate between them.

The description of a generated parameter includes the type of control and the name of the screen in which it appears, for example, "The 'Order' control is of type 'Edit Box'. The control is a part of the 'Display Sales Order: Initial Screen' screen."

If you add data to a table in your SAP app while learning a component, a component table parameter is created. Table parameters enable you to use one parameter for an entire table, rather than using separate parameters for each table cell. For details on working with table parameters, see Specify a table value (for BPT Packaged Apps Kit users).


  • During the Learn process the table parameter saves the data only after you move the focus out of the table. If the table data is the last step in a learn process, ensure that you move the focus out of the table before stopping the learn.
  • To create table parameters during the Learn process, you must enable UFT to create table parameters. In UFT, and a GUI test to the solution and select Tools > Options > GUI Testing > SAP > General node. Under SAP GUI for Windows > Record settings ensure that the Auto-parameterize table and grid controls check box is checked. For details, see Specify a table value (for BPT Packaged Apps Kit users).

If a screen contains a tab strip, one component is created for the common area on the screen, and a separate component is created for each tab opened. The status bar is included in each component created for the screen. For example, consider the screen below:

When you learn a flow or business process test, containing this screen, operations performed on the upper area of the screen containing the menus, toolbars, and common fields (such as Standard Order and Net value) comprise a single business component. Operations performed in each of the Sales, Item overview, Item detail, Ordering party, Procurement, Shipping, and Reason for rejection tabs result in the creation of separate business components.