Show TOC

Migration ExampleLocate this document in the navigation structure

Use

In the SAP system you find the ITS service EXAMPLE_FLOW_M as a simple example for migrating a flow logic service.

In this example service, BAPI_FLIGHT_GETLIST is used to read a list of flights and display the list in a table.

Prerequisites

For the table on the HTML page to be filled with data, you require the corresponding display authorization. To do this, your user must be assigned authorization object S_FLBOOK with activity 03.

Initial Data

  • You can find the corresponding ITS service in the SAP system. Call the ABAP Workbench (transaction SE80). In package S_ITSP, choose Start of the navigation path ITS Services Next navigation step EXAMPLE_FLOW_M End of the navigation path. Both the new migrated templates and the non-migrated files for the service are available here.

  • To view the flow logic service on your external ITS, you need to publish the ITS service on your external ITS, which is no longer possible with IACOR in releases above SAP Web AS 6.40. For the example case, this means that you need to transfer the service files to the external ITS. To do this, select a temporary directory in transaction SE80 by choosing Start of the navigation path Utilities Next navigation step Settings Next navigation step ITS Next navigation step Publish Next navigation step To Local Directory End of the navigation path. The service file EXAMPLE_FLOW_M.srvc is then stored on your external ITS in the service directory ( <ITS_INSTALL_DIR>\<instance name>\services), for example C:\Program Files\SAP\ITS\6.20\IT1\services. The templates are correspondingly stored in the template directory ( <ITS_INSTALL_DIR>\<instance name>\services), for example, C:\Program Files\SAP\ITS\6.20\IT1\templates.

  • The migration example contains the following files:

    • EXAMPLE_FLOW_M.srvc

    • EXAMPLE_FLOW_M_en.htrc

    • Initial.html

    • Initial.flow

    • Template1.html

    • Template1.flow

    • Template2.html

    • Template2.flow

    • display_items.html

    • display_items.flow

    • empty.html

    • empty.flow

  • The migration example uses the following flow logic elements:

    • MODULE element: Module types BAPI, RFC

    • EVENT statement with properties next_state, next_template

    • RESULT Element

    • INPUTMAPPING/OUTPUTMAPPING Element

    • PERSISTENT Element

Process

In the initial template, Initial, you can enter the maximum number of rows that can be used for the call of BAPI_FLIGHT_GETLIST.

The further processing is determined by selecting do1 or do2.

  • If you select do1, the system branches to the template template1, in which, after the call of the function module BAPI_FLIGHT_GETLIST has been processed and the input/output mapping, the list of flights read is displayed on the HTML page in a table.

  • If you select do2, the flight list is initially output in template2. However, you can also branch to another template. In this case, by entering a number, the RESULT element is used, depending on the result of the check, to branch to the template display_items, which displays the fight list, or to the template empty, in which only the transferred parameters are displayed. The set persistent parameters are also displayed in display_items.

Migrated Service

You can find the converted flow logic in the SAP system in the ABAP Workbench (transaction SE80), in package S_ITSP under the program EXAMPLE_FLOW_M.

To view the corresponding ITS service, choose Start of the navigation path Services Next navigation step EXAMPLE_FLOW_M End of the navigation path. In addition to the non-migrated templates and flow files (as mentioned above), the new migrated templates are available here:

  • EXAMPLE_FLOW_M 100

  • EXAMPLE_FLOW_M 200

  • EXAMPLE_FLOW_M 300

  • EXAMPLE_FLOW_M 400

  • EXAMPLE_FLOW_M 500

You can find the SICF node for the new service in transaction SICF under the path sap/bc/gui/sap/its/sample/EXAMPLE_FLOW_M.