Flow logic is a technique with which the process logic of the application is completely administered by the ITS. The only connection to the SAP backend system is through RFC-enabled function modules.
This technique is no longer supported by the integrated ITS. You need to redevelop services that are based on this technique, or migrate them to Internet Application Components (IACs), as described in this document.
The process of the migration of flow logic services to IACs consists of the following steps:
In the ABAP Workbench, create a new ABAP program, which will later contain the screen control, in accordance with the flow logic. To do this, you define a screen for each flow logic file. These screens contain only the Okcode field.
Create and adjust an Internet service
If the relevant service does not yet exist in the system, you have two options: Either use report SIAC_UPLOAD to upload it into the system, or create it manually.
You then generate the screens defined in step 1 for these service templates. You can transfer the HTMLBusiness code from the templates of the old flow logic service.
In this step, you create an ICF service that links your Internet service with an HTTP access path, so that your service can later be called using the browser.
The actual migration of the flow logic takes place in this step. The flow logic is implemented in such a way that it runs as an ABAP program in the integrated ITS.
Activate the ABAP program and publish the Internet service
The final migration step is to activate the ABAP program and publish the Internet service for use in the integrated ITS.
If you have performed all of the steps above, the flow logic is executed as an ABAP program in the integrated ITS.
The advantages of this procedure are:
The existing HTML templates of the flow service can be transferred without changes
The utilized RFC function modules can also be reused
No changes with regard to the appearance or function of the service result.