To create a new interface, go to the AIF Customizing and start the Define Interfaces activity, which can be found under the Interface Development node. As stated before, interfaces are namespace dependent and, therefore, you have to enter the namespace.

 

An interface requires a name and a version. The interface name is a 10 digit CHAR field. You can create different versions of an AIF interface. Every AIF interface also requires a version number. The purpose of the interface should be described in the Description field. In addition to the interface name, version, and description, you have to define at least the raw data structure and the SAP data structure for the interface.

 

Facts About the Interface Version:

• An interface can have several versions. The unique identifier for an interface is the combination of namespace, interface name, and version.
• When is it useful to create a new version of an interface?
  • If the processing of an interface requires some changes but the purpose of the interface is unchanged.
  • If changes to an interface are required for a defined target date and changes to the general Customizing of the interface are not possible.
• In AIF processing, the highest interface version is selected by default.

 

To use the latest version of an interface is the default provided by AIF. It is also possible to do an Interface determination and find the version to use from rules. This rules can also be dependant from the content of an interface.

 

The figure What Happens in an Interface? shows how interfaces can be used by AIF.

 

Data is sent to an interface. The incoming data is transferred to the source structure used in the AIF interface. In the next step, the structure mappings, checks, and value mappings defined for the interface are executed. After the data has been successfully mapped into the defined destination structure, the actions are executed. Within an action, the processing of the data via standard processing functions, BAPIs, or customer functions is started.

 

Source and Destination Structure

 

Whether the RAW or the SAP structure is the source or destination structure depends on the interface's direction. The following are further explanations:

 

RAW Structure

Defines the name of the raw data structure for an interface in the SAP Application Interface Framework.

 

For inbound interfaces, the components of the structure are defined by the format of the data sent by the sending system. The raw data structure is the source structure for inbound interfaces. During runtime, the data of the raw data structure is mapped to the destination structure (SAP structure).

 

For outbound interfaces, the components of the structure are defined by the data required by the external system. The raw data structure is the destination structure for outbound interfaces. During runtime, the data of the source structure is mapped to the raw data structure (destination structure).

 

SAP Structure

Defines the name of the SAP data structure for an interface in the SAP Application Interface Framework.

 

For inbound interfaces, the components of the structure are usually defined by the class's methods or function modules to be executed in the system. For inbound interfaces, the SAP data structure is the destination structure. During runtime, the data of the source structure is mapped to the SAP data structure.

 

For outbound interfaces, the components of the structure are usually defined by the format of the data stored in the system or by the data available in the function, report, etc., that triggers the processing. For outbound interfaces, the SAP data structure is the source structure. During runtime, the data of the SAP data structure is mapped to the destination structure.

 

The raw and the SAP structure used must exist in the ABAP dictionary.

 

Source Structure

The source structure is the structure send to AIF. In an Inbound interface it is the RAW Structure in an outbound Interface the SAP Structure.

 

Outbound Interface