Mastering Automated Reprocessing Role Authorization Management, and Interface Determination

Consider the following:

A message is processed and ends with an error message. A user is required to check the problem and reprocess the message if possible. Some problems are solved without requiring the user to do anything other than restart the message, for example, update of an object and the object was locked. It's a problem if the user spends a lot of time analyzing errors that are already solved.

Solution: Restart the messages automatically.

Configure automatic reprocessing for errors that can be solved automatically via transactions:/AIF/REP_AC_DEF and /AIF/REP_AC_ASGN.

Example: "Object is locked by user &1". The following settings are possible:

• Define a reprocessing action and maintain a function module (/AIF/RESTART_MSG with SAP Application Interface Framework).
• Define for each interface in which error case the message should automatically be restarted.
• Define the maximum number of retries.
• Define a maximum and minimum waiting time.
• Define a Runtime Configuration Group with Run Active and Run Scheduled/AIF/PERS_CGR.

Trace Levels are defined in theApplication Interface Framework Customizing → Error Handling → Global Features.There you define the following:

• Which messages are added to the application log.
• By default, trace level 0 is used.
• Set trace level for interface in view /AIF/V_FINF_TL.
• Then restart with a higher trace level from Monitoring and Error Handling.
• Restart the message with a higher trace level for error analysis.

SAP Application Interface Framework displays the component names of a structure in the Monitoring and Error Handling Data Structure and the Data Content view. Those names are not always easy to understand for a business user.

With structure labels, it's possible to display a different text instead of the component name. Two options are possible:

• Use the text from the dictionary.
• Define your own text.

In SAP Application Interface Framework, you can restrict authorizations on at least the namespace level. In some places, you can also restrict the authorization on the interfaces level.

In addition, you can restrict the authorization for the Monitoring and Error Handling on the data content level. To restrict the authorization on data content level, a corresponding single key field is needed.

For example, if business user A should only be able to see messages of VKORG 1 (VKORG à Sales Organization) and business user B should only be able to see messages of VKORG 2, you can set the permissions up in Monitoring and Error Handling.

SAP Application Interface Framework delivers the following role templates:

• SAP_AIF_ADMIN – AIF Administrator
• SAP_AIF_ALL – AIF All Authorizations
• SAP_AIF_ARCHITEXT – AIF Architect
• SAP_AIF_DEVELOPER – AIF Developer
• SAP_AIF_POWER_USER – AIF Power User
• SAP_AIF_PROCESSING – AIF Processing
• SAP_AIF_TEST_TEMPL – AIF Test Template (Non-Productive)
• SAP_AIF_USER – AIF Business User

Detailed information about SAP Application Interface Framework roles can be found in the master guide and application help.

The figure illustrates the three authorization objects:

The interface determination feature in the SAP Application Interface Framework allows the assignment of a specific interface to process a data message. It's crucial in scenarios where multiple interfaces share similar structures or identifiers, requiring a manual selection to ensure accuracy.

Usage of Interface Determination:

• Proxy interfaces: Interface determination is only available for inbound messages coming from a PI proxy, meaning that interfaces are using the local integration engine/proxy framework.
• IDoc interfaces: Interface determination is only available for IDoc inbound messages. To use the IDoc interface determination, the basic type and message type must be maintained either in the interface definition or in Customizing for the SAP Application Interface Framework. If the standard IDoc runtime is used, the interface determination for IDoc interfaces is not available.
• XML interfaces: Interface determination is available for inbound and outbound messages coming from the persistence layer.
• Customer-Specific engines: You've created a customer-specific interface determination class. This class has to implement the interface /AIF/IF_INF_DET_ENGINE. Alternatively, the class can inherit it from /AIF/CL_INF_DET_ENGINE_BASE. In addition, you've maintained your customer-specific interface determination class in Customizing for the SAP Application Interface Framework.