STATE, MODULE

Use

STATE

STATE defines a logical state.

Within the STATE element, you can define one or more modules (MODULE) and make data persistent ( PERSISTENT). You use STATE statements to read data by RFC and to write it to the ITS context.

MODULE

MODULE defines a module that calls RFC function modules, Business APIs (BAPIs), or other external components.

A MODULE element contains:

One or more RESULT or EXCEPTION elements
Zero or one DEFAULT elements
Zero or more INPUTMAPPING and/or OUTPUTMAPPING elements
Zero or more PERSISTENT elements
Zero or more CONVERTER elements
Zero or more FILEMAPPING elements

Property	Description
`stateful`	Determines whether a module call is `stateful` or `stateless`.
`pooled`	Specifies a connection of the type `Pool`.
`cache`	Specifies a connection of the type `Cache`.

Module	Description
RFC	Supports RFC function modules.
BAPI	Supports BAPIs methods of a business objects.
SCRIPT	Calls a local HTMLBusiness script.

Integration

The attributes stateful, pooled, or cache are no longer required.

The RFC and BAP module types can be called directly in ABAP.

Example

Syntax in the Standalone ITS

In the flow file in the standalone ITS, the syntax is as follows:

<state name="state1" >
  <module name="BAPI_FLIGHT_GETLIST" type="RFC" stateful="0" />
</state>

Syntax in the Integrated ITS

In ABAP in the integrated ITS, the syntax could be as follows:

CALL FUNCTION 'BAPI_FLIGHT_GETLIST'
  exporting
    max_rows     = maxrows
  tables
    flight_list  = flight_list.