SAP Application Interface Framework provides its own runtime and persistence layer. The data is stored in XML format on the persistence layer.
You can trigger processing in SAP Application Interface Framework using a report or a function module. The processed data is stored on the SAP Application Interface Framework persistence layer. The data is available in the SAP Application Interface Framework monitoring and error handling transaction.
Pass Single Message to SAP Application Interface Framework
- The Method TRANSFER_TO_AIF triggers the processing of a single message.
- Messages processed using TRANSFER_TO_AIF can use all functionalities of SAP Application Interface Framework.
To use the TRANSFER_TO_AIF method, the IS_ANY_STRUCTURE parameter is mandatory. This parameter contains the RAW structure of the SAP Application Interface Framework interface.
To use the method /AIF/CL_ENABLER_XML=>TRANSFER_TO_AIF or TRANSFER_TO_AIF_MULT, the Application Engine for that Interface has to be set to XML.
Pass Multiple Messages to SAP Application Interface Framework
To use the method /AIF/CL_ENABLER_XML=>TRANSFER_TO_AIF or TRANSFER_TO_AIF_MULT, the Application Engine for that Interface has to be set to XML.
- The Method TRANSFER_TO_AIF_MULT triggers the processing of multiple messages at one time.
- Messages processed using TRANSFER_TO_AIF_MULT can use all functionality of SAP Application Interface Framework.
To use the TRANSFER_TO_AIF method, the IT_ANY_STRUCTURE parameter is mandatory. This parameter contains a table of RAW structures. For each entry in IT_ANY_STRUCTURE one SAP Application Interface Framework message is created.
Even if you use the method TRANSFER_TO_AIF_MULT, the messages in the table that is handed over to SAP Application Interface Framework are handled one by one. They will be seen as single messages in the monitoring, and it's possible to have successful and faulty messages in one call.
Facts About the Runtime Configuration Group:
- To process XML messages using Application Interface Framework, a runtime configuration group is required.
- A runtime configuration group is identified by:
- The namespace
- A three-digit identifier
- The runtime configuration group specifies:
- The number of messages the be executed per packet
- The number of messages to be executed per run
- If a run/packet is processed synchronously or asynchronously
- The created runs are executed automatically (Active checkbox)
- If you want to create your own runtime configuration group, use the transaction /AIF/PERS_CGR.
- To use your own runtime configuration group, use parameters IV_QUEUE_NS and IV_QUEUE_NAME in TRANSFER_TO_AIF and TRANSFER_TO_AIF_MULT.
- If no specific runtime configuration group is defined, SAP Application Interface Framework uses the default, where one run contains 100 messages and each packet in the run contains 20 messages.
- The SAP Application Interface Framework runtime environment creates persistence runs. Within the runs, the messages will be processed by run packets. The number of runs and the number of run packets created depends on the Runtime Configuration Group.
Default Configuration and Customization:
SAP Application Interface Framework is shipped with a default configuration for the Runtime Configuration Group, defining 100 messages per run and 20 messages per packet.
Execution Control and Job Management:
- Runs and packets are executed based on the defined configuration, with the user's authorizations being crucial for job execution.
- Jobs can be run either synchronously or asynchronously, with options to schedule packets separately using checkboxes.
- The jobs can be monitored using transaction SM37.
Runtime Group Activation and Message Processing:
- Runtime configuration groups can be activated or deactivated, affecting the automatic processing of messages and runs.
- Deactivated groups store messages in the queue, awaiting processing triggered by the /AIF/PERS_RUN_EXECUTE report or manual job scheduling.
