In the domain of SAP Application Interface Framework interface development, the creation and management of interfaces within designated namespaces play a crucial role. It includes defining interfaces, assigning unique identifiers, and managing versions efficiently in SAP Application Interface Framework. The framework offers essential insights into interface versions, featuring the following key details:
- Defined interfaces within designated namespaces, setting up RAW and SAP data structures, mappings, and actions.
- Assigned unique names, versions, and descriptions to each interface, with the option to create multiple versions for updates.
- SAP Application Interface Framework automatically selects the highest interface version as the default choice and offers interface determination based on predefined rules.
What Happens During the Processing of a Message?
Data is sent to an interface. The incoming data is transferred to the source structure used in the SAP Application Interface Framework 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 happens via standard processing functions, BAPIs, or customer functions is started.
What happens in an outbound interface?SAP wants to send data. Instead of sending it directly to the partner it is sent to SAP Application Interface Framework. The data is transferred to the source structure used in the SAP Application Interface Framework 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 message has to be sent to the partner.
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 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, and so on, 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 sent to SAP Application Interface Framework. In an Inbound interface, it's the RAW Structure. In an outbound Interface, it's the SAP Structure.
For an outbound interface, the source structure is the internal structure. Usually, you have to create the structure in the ABAP dictionary. How the structure should look depends on the data that you have to pass to SAP Application Interface Framework in order to be able to derive all the necessary information required by the receiver. For example, you have a report that triggers the sending of data. The user can fill some fields on a selection screen. These fields then have to be passed to SAP Application Interface Framework, and your source structure has to contain those fields.
For an inbound interface, the destination structure is usually predefined since it has to fit to the data received from the external system. For example, for an ABAP proxy, the source structure is the type of INPUT parameter of the proxy class method.
Target Structure
The target Structure is sent from SAP Application Interface Framework to the final destination. In an Inbound Interface, it's the SAP Structure. In an outbound Interface, it's the RAW Structure.
For an outbound interface, the destination structure is usually predefined, since it has to fit to the data required by the external system. For example, for an outbound proxy interface, the structure is defined by the proxy class method's OUTPUT parameter. The raw data structure is the destination structure.
For an inbound interface, you usually have to create the destination structure in the ABAP dictionary. How the structure should look, depends on the functions you want to call in your actions. The SAP data structure is the destination structure. In our example, we'll create customers and flight bookings by calling the corresponding BAPIs. Therefore, the destination structure has to contain the BAPIs' structures.