Sap s4 hana 1709 op sap api-master guide

Master Guide CUSTOMER
SAP Application Interface Framework 3.0
Document Version: 4.0 – 2017-09-29
Master and Upgrade Guide for SAP Application
Interface Framework

Content
1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Useful Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 Related Master Guides. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4 Related Operations Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.5 Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2 Implementation of SAP Application Interface Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
2.1 SAP Application Interface Framework Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2 Software Units of SAP Application Interface Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.3 Software Component Matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
2.4 System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.5 Overall Implementation Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.6 Media List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3 Security for SAP Application Interface Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
3.1 Authorization Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Authorization Object for Interface Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Authorization Object for Customizing Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Authorization Objects for Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Authorization Object for Technical Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Authorization Object for Emergency Corrections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Authorization Objects for Custom Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Authorization Objects for Custom Hints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Authorization Object for Interface Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Authorization Object for Value Mapping Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Authorization Object for File Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Authorization Object for Serialization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Authorization Object for Change Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Authorization Objects for Custom Message Texts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Authorization Objects for Custom Data Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Authorization Object for AIF Persistence Messages Deletion. . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Authorization Object for Processor Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.2 Role Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
AIF Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
AIF All Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
AIF Architect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
2 C U S T O M E R
Master and Upgrade Guide for SAP Application Interface Framework
Content

AIF Developer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
AIF Business User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
AIF Power User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
AIF Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
AIF Test Template (Non-Productive). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.3 Set Up Interface-Specific and Key Field-Specific Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.4 Considerations about Data Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
4 Uninstallation of SAP Application Interface Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Content C U S T O M E R 3

Document History
Caution
Before you start the implementation, make sure that you have the latest version of this document that is
available on SAP Help Portal at http://help.sap.com/aif .
Table 1:
Version Date Change
4.0 2017-09-29 Added chapter Uninstallation of SAP
Application Interface Framework [page
62].
3.0 2017-01-20 Added chapter Authorization Object for
Processor Assignment [page 36].
2.1 2016-09-07 Added chapter Authorization Object for
AIF Persistence Messages Deletion
[page 36].
2.0 2016-05-12 Added chapter SAP Application Inter
face Framework Licensing [page 11].
1.1 2015-11-19 Changed the title of the guide to make
clear that it covers new installations of
SAP Application Interface Framework
3.0 and upgrades from version 2.0.
1.0 2014-10-15 First release of this Master Guide.
4 C U S T O M E R
Document History

1 Getting Started
This section describes how to get started with SAP Application Interface Framework.
1.1 About this Document
Purpose
This Master Guide provides a central starting point for the technical implementation or upgrade of the SAP
Application Interface Framework. You can find cross-scenario implementation and upgrade information as well
as scenario-specific information in this guide.
In addition, this Master Guide contains security information about SAP Application Interface Framework.
Use the Master Guide to get an overview of the SAP Application Interface Framework, its software units, and its
scenarios from a technical perspective. The Master Guide is a planning tool that helps you to design your
system landscape. It refers you to the required detailed documentation, mainly:
● Installation instructions for single software units
● Important SAP Notes
● Configuration documentation
● Operations documentation
● Application help
The Master Guide consists of the following main sections:
● Getting Started [page 5]
Explains how to use this document and related information (documentation and SAP Notes) that is crucial
to the installation, upgrade, configuration, operations, and security of SAP Application Interface
Framework.
● Implementation of SAP Application Interface Framework [page 11]
Provides essential information about the supported scenarios, the installable software units, software
component matrix, as well as how to plan your system landscape. This section provides an overall
implementation sequence with related information (documentation and SAP Notes) and provides the
information about how to install the SAP Application Interface Framework by referring to the relevant SAP
Notes.
● Security for SAP Application Interface Framework [page 20]
Provides the security information that is specific to the SAP Application Interface Framework
(authorization objects, roles, and so on). This section also provides a collection of links to SAP’s various
security topics.
Getting Started C U S T O M E R 5

Constraints
● The business scenarios that are presented here serve as examples of how you can use SAP software in
your company. The business scenarios are only intended as models and do not necessarily run the way
they are described here in your customer-specific system landscape.
Ensure to check your requirements and systems to determine whether these scenarios can be used
productively at your site. Furthermore, we recommend that you test these scenarios thoroughly in your
test systems to ensure they are complete and free of errors before going live.
● This Master Guide primarily discusses the overall technical implementation, upgrade, and security of the
SAP Application Interface Framework, rather than its subordinate components. This means, that additional
software dependencies may exist without being mentioned explicitly in this document.
1.2 Useful Links
The following table contains links to other useful resources.
Table 2:
Resource Where to Find It
User assistance for SAP Application Interface Framework http://help.sap.com/aif
Information about creating customer incidents http://support.sap.com/incident
SAP Notes search http://support.sap.com/notes
SAP Software Download Center http://support.sap.com/swdc
Product Availability Matrix http://support.sap.com/pam
Early Knowledge Transfer and role-specific learning maps http://support.sap.com/ekt
Sizing http://service.sap.com/sizing
Performance http://service.sap.com/performance
Information about support package stacks, latest software
versions and patch level requirements
http://support.sap.com/sp-stacks
Information about Unicode technology http://www.sdn.sap.com/irj/sdn/i18n
6 C U S T O M E R
Getting Started

1.3 Related Master Guides
In this Master Guide, the following SAP applications are frequently referred to, particularly for explaining topics
such as integration scenarios, planning of the system landscape, and so on. You can find more information
about the relevant applications in the following documents:
Table 3:
Title Location
Master Guide SAP NetWeaver 7.0 http://help.sap.com/nw70
Installation and Upgrade Master Guide
Master Guide SAP NetWeaver PI 7.1 http://help.sap.com/nwpi
Master Guide SAP ERP 6.0 http://help.sap.com/erp600
Master Guide SAP Customer Relationship Management 7.0 http://help.sap.com/crm70
1.4 Related Operations Information
The SAP Application Interface Framework is based on an SAP NetWeaver 7.0 system. Therefore, the general
operations information for the following areas is covered in the Operations Guide of SAP NetWeaver:
● Technical system landscape
● Overview of technical runtime scenarios, which result from setting up the corresponding business
scenarios
● Backup and recovery
● High availability concept
● Starting and stopping (by which means and in which sequence)
● Scenario administration concept (possible dependencies between scenario components)
● Concept for data archiving and management of outdated technical data
● Software change management
● Scenario maintenance concept
● Concept for handling customer development
● Support desk management
● Troubleshooting
You can find more information about the corresponding Operations Guides for SAP NetWeaver in http://
help.sap.com/nw70 under Operations.

The operations information that is specific to SAP Application Interface Framework is included in the
Application Help of the SAP Application Interface Framework. There, the following topics are covered:
● Data Archiving
● Performance Analysis
● Index Table Overview
● Interface Objects Summary
● Application Log Content
● Error Handling Changes Log
● Data Correction
● Generation and Display of Snapshots
1.5 Important SAP Notes
You must read the following SAP Notes before you start the installation or the upgrade. These SAP Notes
contain the most recent information about the installation and upgrade, as well as corrections to the
documentation.
Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Support Portal at
http://support.sap.com/notes .
Installation Notes of SAP Application Interface Framework
Table 4:
SAP Note Number Title Description
2071823 ABAP Add-On AIF 702: Installation, up
grade, CSPs
See this note for the detailed informa
tion about installing the main compo
nent AIF 702 of SAP Application Inter
face Framework 3.0.
2071952 ABAP Add-On AIFX 702: Installation,
upgrade, CSPs
tion about installing the optional com
ponent AIFX 702 of SAP Application In
terface Framework 3.0.
2288871 ABAP Add-on AIFGEN 700: Installation,
CSPs
tion about installing the optional com
ponent AIFGEN 700 of SAP Application
Interface Framework 3.0.
8 C U S T O M E R
Getting Started

1530212 SAP Application Interface Framework
FAQ
See this note for frequently asked ques
tions about the SAP Application Inter
face Framework.
Relevant Notes of SAP NetWeaver
Table 5:
1844763 ALE: Integration of
SAP Application
Interface Frame
work
Implement this note to enable IDoc monitoring
with the SAP Application Interface Framework.
1828776 AIF support in
proxy inbound
processing
Implement this note to enable inbound proxy mon
itoring with the SAP Application Interface Frame
work.
1989168 Missing DB In
dexes causing Per
formance Issues
Only needed if you configure interfaces for the
Process Observer.
1994183 Performance Im
provements for
metrics engine
and event process
ing
Process Observer.
2009539 Performance Im
provements for
Event Processing
Process Observer.
2035226 Changing the se
quence of logging
entries into DB
Process Observer.
1684718 WDA: Transaction
WDYID – Configu-
ration ID is lost
Only needed if you install the optional component
AIFX 702 and use Monitoring and Error Handling
(Web) from the SAP Easy Access menu.
1241303 Dynamic docu
ments: Multiple
registration of
events
In a dynamic document, as it is used in the
Interface Overview transaction of the SAP Applica
tion Interface Framework, form elements such as
pushbuttons, input fields, selection lists, and hy
perlinks respond several times to an event.

1726101 Tables with more
than five key ele
ments are not sup
ported
This note is only needed if you install the optional
component AIFX 702 and use the Service Imple
mentation Workbench (SIW) template.
1705786 SIW: Language
conflict with LO
CAL packages
component AIFX 702 and use the SIW template.
1698269 SIW: Misleading
error message
1718473 SIW: Dump after
leaving ungener
ated project
10 C U S T O M E R
Getting Started

2 Implementation of SAP Application
Interface Framework
The SAP Application Interface Framework enables you to develop and monitor interfaces as well as execute
error handling in a single framework residing in your SAP backend system.
Possible sources of demand for SAP Application Interface Framework are:
● You have a complex, heterogeneous system landscape
● You want to decouple technical and business aspects of your interfaces, thus enabling business users to
perform error handling
● You use different technologies to implement interfaces, so you have duplicate efforts for implementing the
same logic in multiple technologies
● You have to use multiple monitoring tools for different basis technologies and would like to use one tool to
simplify the monitoring and error handling
● You experience difficulties in enforcing interface implementation guidelines
● You need to restrict access to interface data to fulfill your regulatory or company compliance rules
SAP Application Interface Framework enables you to:
● Implement interfaces in an easy and structured way mainly based on Customizing
● Re-use interface building blocks (checks, structure mappings, value mappings, actions, functions) inside of
multiple interfaces and for different basis technologies
● Do functional instead of technical monitoring
● Restrict interface data and error monitor access by flexible authorization rules
● Enforce interface implementation guidelines
SAP Application Interface Framework provides you with the following functions:
● A powerful framework for the implementation of interfaces
● A user-friendly transaction for interface monitoring and error handling
● Tools for configuration and operations
The following chapters give an overview of the software components that are required within the SAP
Application Interface Framework and its business scenarios, as well as an overview of the implementation
process.
2.1 SAP Application Interface Framework Licensing
The licensing distinguishes the following basic usages of SAP Application Interface Framework:
● As stand-alone product for developing, processing and monitoring your own custom interfaces. For this
usage, you need to purchase the full SAP Application Interface Framework license and have the AIFGEN
software component installed in addition to the AIF component.
Implementation of SAP Application Interface Framework C U S T O M E R 11

● As a supporting component for only processing and monitoring the AIF interfaces shipped with other SAP
products, for example, SAP S/4HANA or SAP Advanced Track and Trace for Pharmaceuticals. For this
usage, a limited runtime license of SAP Application Interface Framework is included in the licenses of the
other products and AIFGEN is not required.
For more information about the SAP Application Interface Framework license check using AIFGEN, see SAP
Note 2293938 .
For more information about SAP Application Interface Framework system measurement, see System
Measurement Engine , measurement ID 3250.
2.2 Software Units of SAP Application Interface Framework
The following table contains the basic software units that you require to set up your SAP Application Interface
Framework system landscape:
Table 6:
Software Unit Release
SAP Application Interface Framework 3.0 (component AIF) 702
SAP NetWeaver 700, SP17 or above
If you want to use the Web-based Monitoring and Error Handling transaction, the Service Implementation
Workbench (SIW) to generate AIF interfaces, or the integration with the Error and Conflict Handler (ECH), the
minimum requirements are the following:
Table 7:
SAP Application Interface Framework (component AIF) 702
SAP Application Interface Framework Extension (compo
nent AIFX)
702
SAP NetWeaver 731, SP01 or above
If you have purchased the full SAP Application Interface Framework license and want to develop SAP
Application Interface Framework interfaces in your own custom namespaces, you require the following
software unit in addition:
Table 8:
Aifgen 700 (component AIFGEN) 700
12 C U S T O M E R
Implementation of SAP Application Interface Framework

Caution
Make sure all the relevant and available support packages (SPs) and enhancement packages (EHPs) are also
applied when any of the above software units are installed. For the latest component version and patch level
requirements, see http://support.sap.com/sp-stacks .
2.3 Software Component Matrix
The SAP Application Interface Framework can be used on any SAP application system based on SAP
NetWeaver 7.0 SP17 (or above). This is why the Master Guide cannot cover all possible integration scenarios.
Only a limited number of common integration scenarios are covered:
● Integration scenario SAP ERP
● Integration scenario SAP SRM
● Integration scenario SAP ERP + SAP CRM
● IDoc integration scenarios
With the SAP Application Interface Framework, you can use one or multiple interface technologies (for
example, proxy messages or IDocs) for integration and monitoring. For any integration scenario you are using,
you need to make sure that the systems you want to connect are capable of handling the chosen interface
technology. You also need to make sure to use one of the interface technologies supported by the SAP
Application Interface Framework or to implement the support for the chosen interface technology in the SAP
Application Interface Framework using a custom engine.
The table below shows the mapping of the software units to each of the integration scenarios to build a system
landscape with the SAP Application Interface Framework. You can see which software units are mandatory and
which other software units are optional to realize each integration scenario.
Integration Scenario SAP ERP
Table 9:
Software Unit Installation Obligatory or Optional
SAP Application Interface Framework add-on based on SAP
NetWeaver 7.0
Obligatory
SAP NetWeaver 7.0 or the Enhancement Packages for 7.0 Obligatory
SAP NetWeaver PI 7.0 Optional
SAP ERP 6.0 or the Enhancement Packages for 6.0 Obligatory

Integration Scenario SAP SRM
Table 10:
NetWeaver 7.0
Obligatory
SAP SRM 7.0 Obligatory
Integration Scenario SAP ERP + SAP CRM
Table 11:
NetWeaver 7.0
Obligatory
SAP ERP 6.0 or the Enhancement Packages for 6.0 Obligatory
SAP CRM 7.0 Obligatory
IDoc Integration Scenarios
There are multiple interface integration scenarios which can be built using IDoc technology. Depending on the
integration scenario used, different features of the SAP Application Interface Framework are available. It is
possible to use multiples of these integration scenarios for different interfaces.
The following four different scenarios, in which you can process and monitor IDocs, are available:
● IDoc Scenario 1: Monitoring of existing IDocs in Monitoring and Error Handling
● IDoc Scenario 2: Processing IDocs using AIF and calling an IDoc function module in an action
● IDoc Scenario 3: Processing IDocs using AIF and calling a BAPI in an action
● IDoc Scenario 4: Processing IDocs using ALE and writing index tables with the AIF enabler
Based on your integration scenario, you can implement various business processes. The SAP Application
Interface Framework does not provide standard business processes. Instead, you have to implement your own
business processes and corresponding interfaces using the SAP Application Interface Framework.
14 C U S T O M E R

2.4 System Landscape
The SAP Application Interface Framework offers various system landscape options depending on the
customers’ business requirements and possible system deployments. In the following section, exemplary
system deployments are presented with the characteristics and restrictions of each case.
Caution
We strongly recommend that you use a minimal system landscape for test and demo purposes only. For
performance, scalability, high availability, and security reasons, do not use a minimal system landscape as
your production landscape.
General
The integration scenarios involve at least 2 systems, that is, a legacy system and an SAP backend system that
contains the SAP Application Interface Framework. The integration scenarios can optionally involve an SAP
NetWeaver PI. The legacy system can be any system that is able to exchange information directly with the SAP
backend system or with the SAP NetWeaver PI system. Every SAP application system based on SAP NetWeaver
7.0 SP17 (and above) is supported as the SAP backend system.
For any integration scenario you are using, you need to make sure that the systems you want to connect are
capable of handling the chosen interface technology.
In your business processes, the legacy system can act as sender or receiver of information.
As a sender, the legacy system is the data source and sends data directly to the SAP backend system or to the
SAP NetWeaver PI system.
If you choose to use direct integration between the legacy system and the SAP backend system, data is sent
directly from the legacy system to the SAP backend system.
If you choose to use SAP NetWeaver PI for integration, SAP NetWeaver PI can act as the information broker,
provide security features, and offer many other technical integration capabilities. Here, the technical mapping
of the data structures or technical format conversions (for example, using existing adapters) can be executed.
If the communication channel in your SAP NetWeaver PI is correctly configured, the message is sent to your
SAP backend system. The SAP Application Interface Framework resides within the SAP backend system and
provides different additional features depending on the chosen integration scenario.

If data is sent through the SAP NetWeaver PI system, you have the option to use different interface
technologies for communication between the legacy system and SAP NetWeaver PI and between SAP
NetWeaver PI and the SAP backend system. In this case, a technical format conversion needs to be done in
SAP NetWeaver PI to translate from one interface technology to the other.
In both scenarios, the SAP Application Interface Framework in the SAP backend system provides the
monitoring and error handling functionality.
Note
Note that the interface setting, mapping, interface variants, and error handling settings in the SAP
Application Interface Framework are client-dependent. You have to make sure that message processing and
error handling is executed in the correct client.
As a receiver, the legacy system is the consumer of information sent by the SAP backend system using the
SAP Application Interface Framework. When triggered manually or by an application, the SAP Application
Interface Framework executes the mapping from the internal to the external structure and sends the
information in the external format directly to the legacy system or to SAP NetWeaver PI.
If you choose to use direct integration between the SAP backend system and the legacy system, data is sent
directly from the SAP backend system to the legacy system.
If you choose to use SAP NetWeaver PI for integration, SAP NetWeaver PI can act as the information broker,
provide security features, and offer many other technical integration capabilities. Here, the technical mapping
of the data structures or technical format conversions (for example, using existing adapters) can be executed.
If the communication channel in your SAP NetWeaver PI is correctly configured, the message is sent to the
legacy system.
If data is sent through the SAP NetWeaver PI system, you have the option to use different interface
technologies for communication between the SAP backend system and SAP NetWeaver PI and between SAP
NetWeaver PI and the legacy system. In this case, a technical format conversion needs to be done in SAP
NetWeaver PI to translate from one interface technology to the other.
Example 1: SAP Application Interface Framework installed on SAP ERP
In this example, an SAP ERP system acts as the SAP backend system as described in the general scenario
above.
16 C U S T O M E R

Example 2: SAP Application Interface Framework installed on SAP SRM
In this example, an SAP SRM system acts as the SAP backend system as described in the general scenario
above.
Example 3: SAP Application Interface Framework installed on SAP ERP and
SAP CRM
In this example, there is more than one SAP backend system. Every SAP backend system requires its own
installation of the SAP Application Interface Framework.

2.5 Overall Implementation Sequence
The following table describes the overall implementation sequence for SAP Application Interface Framework.
This table contains all available software units.
Table 12:
Step Action
Required Documentation
Remarks
1 Perform the installation of component
AIF 702 with the latest available sup
port package.
SAP Note 2071823
2 Perform the (optional) installation of
component AIFX 702 with the latest
available support package.
SAP Note 2071952
3 Perform the (optional) installation of
component AIFGEN 700 with the latest
available support package.
SAP Note 2288871
4 Transport the delivered default Cus
tomizing into target clients.
The delivered Customizing will be im
ported only into client 000; from there
you can copy it into your target clients.
5 Use transaction /AIF/SETUP for all
other post-installation steps
With transaction /AIF/SETUP, all other
post-installation steps (for example,
number ranges) can be performed au
tomatically.
6 Read the FAQ for the SAP Application
Interface Framework.
SAP Note 1530212
See this note for frequently asked ques
tions about the steps that are neces
sary after the installation of the SAP
Application Interface Framework.
7 Customize settings for the SAP Appli
cation Interface Framework.
Application Help on SAP Help Portal at
http://help.sap.com/aif
-
18 C U S T O M E R

2.6 Media List
All deliverables for the SAP Application Interface Framework 3.0 are shipped electronically and no shipment is
made via DVDs (or similar kind of data carrier media).

3 Security for SAP Application Interface
Framework
Use
The SAP Application Interface Framework is built on a SAP NetWeaver system. Therefore, the corresponding
security settings also apply to the SAP Application Interface Framework.
This section provides an overview of the security considerations that are specific to the SAP Application
Interface Framework.
Features
The SAP Application Interface Framework uses flexible authorization rules to allow you to restrict access to
data and to monitoring and error handling. This security feature enforces compliance by following the need-to-
know principle when restricting access to interface data.
When you have given users the authorization to change and correct interface data, the system tracks all
changes that are made and allows you to trace which user made which change.
The configuration of security and authorizations in the SAP Application Interface Framework includes the
following objects, roles, and data:
● Standard authorization objects (see Authorization Objects [page 20])
● Predefined role templates (see Role Templates [page 37])
● The integration of custom-defined authorization objects (see Set Up Interface-Specific and Key Field-
Specific Authorizations [page 59])
● Personal data
To secure your data properly, it is also required that you understand the personal data stored by the SAP
Application Interface Framework (see Considerations about Data Protection [page 60])
3.1 Authorization Objects
The SAP Application Interface Framework allows you to specify various authorization settings. In this section,
each authorization object is explained with its description, technical attributes, and use.
20 C U S T O M E R
Security for SAP Application Interface Framework

3.1.1 Authorization Object for Interface Processing
Definition
The authorization object /AIF/PROC is used by the system to check the user’s authorization for processing a
data message of a given interface in the SAP Application Interface Framework.
Authorization Fields
Table 13:
Field Name Heading Authorization Object Setting
ACTVT Activity You can enter the following activities:
Import (60)
Export (61)
Resubmit (A4)
/AIF/NS Namespace This field refers to a namespace in the
/AIF/IF Interface Name This field refers to an interface name in
the SAP Application Interface Frame
work
/AIF/IFVER Interface Version This field refers to an interface version
in the SAP Application Interface Frame
work
/AIF/VNS Variant Namespace This field refers to a variant namespace
name in the SAP Application Interface
Framework
/AIF/VNAME Name of Interface Variant This field refers to a variant name in the
Use
Messages are processed by a specific user. This user requires the authorization to (re-) process data messages
in the SAP Application Interface Framework.
Example
The user PIAPPL is assigned the authorization to process data messages for all namespaces, interface names,
interface versions, and, if applicable, variant namespace and name.
Security for SAP Application Interface Framework C U S T O M E R 21

3.1.2 Authorization Object for Customizing Steps
Definition
The authorization object /AIF/CUST is used by the system to check the user’s authorization for a Customizing
activity in the SAP Application Interface Framework.
Table 14:
Change (02)
Display (03)
/AIF/MC Customizing view For the available values, see the table
below
Use
The Namespace (/AIF/NS) field can contain any namespace name. By entering a value in the namespace field,
you can limit the user’s authorization for Customizing activities to the specified namespaces.
Example
An interface developer is authorized to create, edit, and delete interfaces in namespace X but not Y.
Allowed Values for the Namespace Field
For the Namespace (/AIF/MC) field, the following values are allowed:
Table 15:
Value Description
/AIF/ACTIONS Define Actions
/AIF/ALERT Define Recipients
/AIF/BDC_V_CONF Define Pre-Interface Determination for Batch Input
/AIF/CFUNC Define Custom Functions
22 C U S T O M E R

Value Description
/AIF/CHECKS Define Checks
/AIF/CLINK Define Custom Data Link
/AIF/CTEXT Define Custom Message Text
/AIF/ERROR_GLB Global Features
/AIF/ERROR_HDL Define Applications
/AIF/ERROR_IF Define Interface-Specific Features
/AIF/ERROR_NS Define Namespace-Specific Features
/AIF/FIXVALUES Define Fix Values
/AIF/LFA_SETTINGS Settings for AIF File Adapter
/AIF/POC Configuration for POC Integration
/AIF/SMAP Define Structure Mapping
/AIF/VALMAPS Define Value Mappings
/AIF/VARIANT_MAPPINGS_ALL Define Variant Mappings
/AIF/VC_SERIAL Define Serialization Settings
/AIF/VC_TJ_CONF Configure Data Transfer
/AIF/VREP_AC_ASG Assign Automatic Reprocessing Action
/AIF/VREP_AC_DEF Define Automatic Reprocessing Action
/AIF/V_ALRT_USR2 Define Recipients of Other Users
/AIF/V_ALRT_USR3 Define Recipients of Own User
/AIF/V_BDC_IF Assign Batch Input Session and Creator
/AIF/V_ENGINES Define Custom-Specific Engines
/AIF/V_FINF Define Interfaces
/AIF/V_FINF_ENG Define Interfaces (Engine Fields)
/AIF/V_FINF_IDOC Define Interfaces (IDoc fields)
/AIF/V_FINF_TL Define Trace Level
/AIF/V_HINTS Define Custom Hints

Value Description
/AIF/V_IDOCSTAT Mapping of IDoc Status to AIF Status
/AIF/V_IFKEY Define Interface Key Fields for Variants
/AIF/V_NS Define Namespace
/AIF/V_PERS_RTCG Define Runtime Configuration Group
/AIF/V_RFC_FCOL Define RFC Function Module Collection
/AIF/V_RFC_FUNCS Assign Functions to RFC Function Module Collection
/AIF/V_SYSNAMES Define Business Systems
/AIF/V_VALID_PER Define Validity Period
3.1.3 Authorization Objects for Error Handling
Definition
The authorization object /AIF/ERR is used by the system to check the user’s authorization for error handling
in the SAP Application Interface Framework.
24 C U S T O M E R

Table 16:
Execute (16) (means selecting from in
dex tables)
Archive (24) (means starting the ar
chiving report using SARA)
Reload (25) (means restoring archived
data using SARA)
Read (33) (means reading message
content from persistence)
Write (34) (means updating message
content in persistence)
Display archive (56)
Administer (70) (means starting an ex
ternal technical monitoring tool like
qRFC for PI messages)
Analyze (71) (means displaying applica
tion log messages)
Remove (75) (means canceling a mes
sage)
Resubmit (A4) (means restarting a
message)
General overview (GL) (means starting
external monitoring like XML monitor
ing for PI messages or WE02 for IDocs)
work
work
Use
Using the activity field, you specify the actions that a user can execute in the system. For example, you might
want to specify a user who only has read access to the transaction. You can further limit the authorization by

namespace, interface name, and interface version. As a result, the user can execute the specified activities only
for the defined namespace/interface name/interface version combination.
3.1.4 Authorization Object for Technical Error Handling
Definition
The authorization object /AIF/TECH is used by the system to check the user’s authorization for the technical
mode of error handling in the SAP Application Interface Framework.
Table 17:
ACTVT Activity You can enter the following activity: Ac
tivate (63)
Use
This authorization object does not have any parameters or activities. If a user does not have the authorization,
the Technical Mode checkbox in the selection screen and the Technical Mode pushbutton in the main screen of
the Monitoring and Error Handling transaction are hidden.
3.1.5 Authorization Object for Emergency Corrections
Definition
The authorization object /AIF/EMC is used by the system to check the user’s authorization for emergency
corrections in the error handling of the SAP Application Interface Framework.
26 C U S T O M E R

Table 18:
ACTVT Activity You can enter the following activities
(see description for authorization ob
ject /AIF/ERR for details):
Execute (16)
Read (33)
Write (34)
Administer (70)
Analyze (71)
Remove (75)
Resubmit (A4)
General overview (GL)
Use
Using the activity field, you specify the actions the user can execute in emergency correction mode in the
Monitoring and Error Handling transaction. You can further limit the authority to execute the actions in
emergency correction mode based on the interface namespace.
When executing the Monitoring and Error Handling transaction, the user first has to enter a namespace and
press the ENTER key. The system then checks the authorization for emergency corrections and displays the
Emergency Correction Mode checkbox, if applicable.
3.1.6 Authorization Objects for Custom Functions
Definition
The authorization object /AIF/CFUNCis used by the system to check the user’s authorization for custom
functions for error handling in the SAP Application Interface Framework.

Table 19:
Create or generate (01)
Change (02)
Display (03)
Delete (06)
Execute (16) (means executing in the
Monitoring and Error Handling transac
tion)
work
work
/AIF/NSREC Namespace of Recipient Not used at the moment; enter *
/AIF/VISI Visibility Specifies for which users the custom
function is visible. You can enter the fol
lowing values:
A means “Just for current user”
B means “For a list of users” (main
tained in transaction /AIF/CUST_FUNC
Define Custom Functions Assign
Users )
C means “For all users”
/AIF/OTHUS Authorization for other users Not used at the moment; enter *
Use
Using the activity field, you specify the actions the user can execute in custom functions in the Monitoring and
Error Handling transaction and the corresponding maintenance views for custom functions.
28 C U S T O M E R

3.1.7 Authorization Objects for Custom Hints
Definition
The authorization object /AIF/HINTS is used by the system to check the user’s authorization for custom hints
for error handling in the SAP Application Interface Framework.
Table 20:
Change (02)
Display (03)
Delete (06)
work
work
/AIF/NSREC Namespace of Recipient Not used at the moment; enter *
hint is visible. You can enter the follow
ing values:
B means “For a list of users” (not used
at the moment)
C means “For all users”
Use
Using the activity field, you specify the actions the user can execute in custom hints in the Monitoring and Error
Handling transaction and the corresponding maintenance views of the custom hints.

3.1.8 Authorization Object for Interface Determination
Definition
The authorization object /AIF/IFDET is used by the system to check the user’s authorization for maintaining
interface determination in the SAP Application Interface Framework.
Table 21:
/AIF/IDTY Application Engine Identifier Type of application engine:
000: Proxy
001: IDoc
002: XML
003: Test File
004: ECH
/AIF/NS Namespace Namespace of a customer-specific en
gine
/AIF/IDCTY Identifier for a Customer-Specific AIF
Interface Type
Identifier of a customer-specific engine
/AIF/IDN1 Name 1 of Interface Type First key field of an engine
/AIF/IDN2 Name 2 of Interface Type Second key field of an engine
ACTVT Activity You can enter the following activity:
Change (02)
Display (03)
Delete (06)
Use
Using the activity field, you specify the actions the user can execute in the corresponding maintenance views of
interface determination.
30 C U S T O M E R

3.1.9 Authorization Object for Value Mapping Maintenance
Definition
The authorization object /AIF/VMAP is used by the system to check the user’s authorization to display and/or
update value mappings in the Value Mapping transaction of the SAP Application Interface Framework.
Table 22:
Change (02)
Display (03)
/AIF/VMAP Value Mapping This field refers to a value mapping
name in the SAP Application Interface
Framework
/AIF/BSKEY Key Name of Business System This field refers to a business system
name
Use
The authorization object protects the display/update of value mappings.
Caution
The authorization is only checked in the Value Mapping transaction /AIF/VMAP (and derived transaction
variants) and not in the Define Value Mappings Customizing activity.
3.1.10 Authorization Object for File Adapter
Definition
The authorization object /AIF/LFA is used by the system to check the user’s authorization to access files in
the directories of the application server. This can be done in the file adapter transactions (/AIF/
LFA_UPLOAD_FILE and /AIF/LFA_CHECK_SEND) of the SAP Application Interface Framework.

Table 23:
Display (03) – display file content in the
File Adapter
Delete (06) – delete files from applica
tion server after successful upload
Read (33) – read files from application
server to AIF
Write (34) – write files from AIF to ap
plication server
Analyze (71) – display file list in F4 help
/AIF/FDIR Directory on Application Server This field refers to a directory on the
application server, for example, /usr/
temp
/AIF/FNAM Interface File Name This field refers to the file name, for ex
ample, A*.xml
Use
The authorization object protects the access to files on the application server.
Caution
The authorization is checked only in the file adapter transactions for files which are located on the
application server. For accessing the local PC (the front end, presentation server), this standard
authorization concept for accessing files from SAP GUI takes care of security aspects (for example, display
the Allow/deny popup to the user).
3.1.11 Authorization Object for Serialization
Definition
The authorization object /AIF/SER is used by the system to check the user’s authorization to display/change
the current external index of a serialization object (for example, change index of a specific purchase order
number). This can be done in the Manual Change of External Index transaction (transaction code /AIF/
SERIAL_INDEX) of the SAP Application Interface Framework.
32 C U S T O M E R

Table 24:
Change (02) – update the external in
dex
Display (03) – display the external in
dex
/AIF/NS Namespace This field refers to the namespace of
the serialization object
/AIF/SEROB Serialization Object This field refers to the name of the seri
alization object.
Use
The authorization object protects the access to the external index of a serialization object.
3.1.12 Authorization Object for Change Log
Definition
The authorization object /AIF/CDLOG is used by the system to check the user’s authorization to display the
user name in the Error Handling Change Log (transaction code /AIF/EDCHANGES).
Table 25:
Administer (70) – Display the Modified
By field
Use
The authorization object protects the access to the user name of log entry in the Error Handling Change Log.

3.1.13 Authorization Objects for Custom Message Texts
Definition
The authorization object /AIF/CTEXT is used by the system to check the user’s authorization for custom
message texts for error handling in the SAP Application Interface Framework.
Table 26:
Change (02)
Display (03)
Delete (06)
work
work
message text is visible. You can enter
the following values:
at the moment)
C means “For all users” (not used at the
moment)
Use
Using the activity field, you specify the actions the user can execute in custom message texts in the Monitoring
and Error Handling transaction and the corresponding maintenance views for custom message texts.
34 C U S T O M E R

3.1.14 Authorization Objects for Custom Data Links
Definition
The authorization object /AIF/CLINK is used by the system to check the user’s authorization for custom data
links for error handling in the SAP Application Interface Framework.
Table 27:
Change (02)
Display (03)
Delete (06)
work
work
data link is visible. You can enter the fol
lowing values:
at the moment)
C means “For all users” (not used at the
moment)
Use
Using the activity field, you specify the actions the user can execute in custom data links in the Monitoring and
Error Handling transaction and the corresponding maintenance views for custom data links.

3.1.15 Authorization Object for AIF Persistence Messages
Deletion
Definition
The authorization object /AIF/PERSD is used by the system to check the administrator’s authorization to
authorize another user to irreversibly delete messages from the AIF persistence using the AIF Persistence
Messages Deletion (transaction /AIF/PERS_DEL).
Table 28:
Create in DB (40)
Delete in DB (41)
Use
The authorization object protects the access to the maintenance view (transaction /AIF/PERS_DEL_AUTH) for
granting authorizations for the AIF Persistence Messages Deletion.
For executing the AIF Persistence Messages Deletion, there is a two-person authorization concept in place. An
administration user can authorize another user (but not himself) to execute the report for a specific interface
at a specific date.
3.1.16 Authorization Object for Processor Assignment
Definition
The authorization object /AIF/DPA is used by the system to check the user’s authorization to assign,
unassign, or change the assignment of processors in the Details and Processor Assignment. In addition, it
checks the authorization to create or change the processing status and the comments.
36 C U S T O M E R

Table 29:
work
work
/AIF/NSREC Namespace This field refers to a namespace in the
/AIF/RECIP Alert Management Recipient This field refers to a recipient in the
SAP Application Interface Framework.
/AIF/OTHUS Authorization for Other Users This field allows the user to change as
signments, statuses, and comments
also for other processors. An empty
value means no authorization, while X
means that the user has the authoriza
tion.
● Change (02)
● Display (03)
Use
Using the activity field, you specify the actions the user can execute in Details and Processor Assignment in the
Interface Monitor.
3.2 Role Templates
Definition
The SAP Application Interface Framework provides predefined template roles that you can use in order to
define roles for your specific requirements.

Features
Role Templates
The following role templates are delivered with the SAP Application Interface Framework 3.0:
● SAP_AIF_ADMIN: AIF Administrator [page 40]
● SAP_AIF_ALL: AIF All Authorizations [page 43]
● SAP_AIF_ARCHITECT: AIF Architect [page 44]
● SAP_AIF_DEVELOPER: AIF Developer [page 48]
● SAP_AIF_USER: AIF Business User [page 52]
● SAP_AIF_POWER_USER: AIF Power User [page 54]
● SAP_AIF_PROCESSING: AIF Processing [page 58]
● SAP_AIF_TEST_TEMPL: AIF Test Template (Non-Productive) [page 59]
Use of Role Templates
When creating your own roles, you can add the SAP Application Interface Framework-specific authorizations
based on the role templates in Role Maintenance (transaction code PFCG) when you maintain the authorization
data (in the Authorizations tab).
● When no authorization data exists, you are asked for a template
● When authorization data exists, you can add the SAP Application Interface Framework-specific
authorizations in the command Edit – Insert authorization(s) – From template…
Content of the Role Templates
Each role templates contains a set of authorizations which typical users of the SAP Application Interface
Framework would need.
Note
This is only a proposal that you might need to adapt to your specific situation.
Most of the authorizations need to be granted by more specific values, for example, namespace and
interface.
Example
You use the template SAP_AIF_USER to create the roles for your business users doing the monitoring and error
handling. For a business user role, you can restrict the authorizations to the interfaces the business users are
allowed to see.
You use template SAP_AIF_DEVELOPER to create the roles for the users developing the interfaces of the SAP
Application Interface Framework.
38 C U S T O M E R

More Information
Obsolete Roles
In version 2.0, the SAP Application Interface Framework provided predefined single and composite roles that
could be used as a template in order to define roles for specific requirements.
With version 3.0, role templates are delivered, which simplifies the implementation significantly. Thus, the
following single and composite roles are obsolete and are only provided for compatibility:
Recommendation
Use the role templates described in this section and not these obsolete roles.
Obsolete Single Roles
● /AIF/CORRECT_DATA
● /AIF/CUST_CHANGE
● /AIF/CUST_DISPLAY
● /AIF/ERRHDL_CHANGE
● /AIF/ERRHDL_CHANGE_EMC
● /AIF/ERRHDL_DISPLAY
● /AIF/ERRHDL_DISPLAY_EMC
● /AIF/LOG_DISPLAY
● /AIF/MESSAGE_NOTIFICATION
● /AIF/MSG_STAT_SNAP_SHOT
● /AIF/PERFORMANCE_ANALYSIS
● /AIF/PROCESS_INB
● /AIF/PROCESS_OUTB
● /AIF/PROCESS_RES
● /AIF/SWITCH_FRAMEWORK
● /AIF/TEST_TOOL
● /AIF/VMAP_CHANGE
● /AIF/VMAP_DISPLAY
● /AIF/ARC_CREATE
● /AIF/ARC_DISPLAY
● /AIF/ARC_RELOAD
Obsolete Composite Roles
● /AIF/ADMINISTRATOR
● /AIF/DATA_FIXER
● /AIF/INTERFACE_DEVELOPER
● /AIF/KEY_USER
● /AIF/BUSINESS_USER
● /AIF/ALL

3.2.1 AIF Administrator
An AIF Administrator is responsible for advanced system configuration like “publishing” custom functions/
hints/message texts, interface determination, archiving, correction report, and so on.
For these tasks, an AIF Administrator is provided with the following authorizations:
Table 30:
Authorization Object Activity Activity Description
/AIF/CFUNC 1 Create or generate
/AIF/CFUNC 2 Change
/AIF/CFUNC 3 Display
/AIF/CFUNC 6 Delete
/AIF/CFUNC 16 Execute
/AIF/CLINK 1 Create or generate
/AIF/CLINK 2 Change
/AIF/CLINK 3 Display
/AIF/CLINK 6 Delete
/AIF/CTEXT 1 Create or generate
/AIF/CTEXT 2 Change
/AIF/CTEXT 3 Display
/AIF/CTEXT 6 Delete
/AIF/CUST 3 Display
/AIF/ERR 16 Execute
/AIF/ERR 24 Archive
/AIF/ERR 25 Reload
/AIF/ERR 33 Read
/AIF/ERR 56 Display archive
/AIF/ERR 70 Administer
/AIF/ERR 71 Analyze
/AIF/ERR GL General overview
40 C U S T O M E R

/AIF/HINTS 1 Create or generate
/AIF/HINT 2 Change
/AIF/HINT 3 Display
/AIF/HINT 6 Delete
/AIF/IFDET 1 Create or generate
/AIF/IFDET 2 Change
/AIF/IFDET 3 Display
/AIF/IFDET 6 Delete
/AIF/LFA 3 Display
/AIF/LFA 6 Delete
/AIF/LFA 33 Read
/AIF/LFA 34 Write
/AIF/LFA 71 Analyze
/AIF/SER 2 Change
/AIF/SER 3 Display
/AIF/TECH 63 Activate
/AIF/VMAP 2 Change
/AIF/VMAP 3 Display
In addition, an AIF Administrator is provided with the authorization to the following transaction codes:
Table 31:
Transaction Code Description
/AIF/CORRECTIONS Correction Report
/AIF/CUST Customizing
/AIF/CUST_FUNC Define Custom Functions
/AIF/CUST_HINTS Define Custom Hints
/AIF/CUST_LINK Define Custom Data Link

/AIF/CUST_TEXT Define Custom Message Texts
/AIF/DEL_STRUC_CACHE Delete Structure Cache
/AIF/DISPMSGSNAP AIF Display Snapshot
/AIF/DOCU Interface Documentation Tool
/AIF/EDCHANGES Error Handling Changes Log
/AIF/ERR Monitoring and Error Handling
/AIF/ERR_BASE Error Handling Base
/AIF/GENMSGSNAP AIF Generate Snapshot
/AIF/IDOC_IMPORT AIF IDOC Import
/AIF/IDXTBL Index Table Overview
/AIF/IF_TRACE AIF Interface Trace Level
/AIF/IFMON Interface Monitor
/AIF/LFA_CHECK_SEND Read Files from folder; Send to AIF
/AIF/LFA_UPLOAD_FILE Upload File to AIF
/AIF/LOG Interface Logs
/AIF/MYRECIPIENTS Recipients of Current User
/AIF/PERFORMANCE Performance Tracking
/AIF/PERS_CGR Runtime Configuration Group
/AIF/PERS_TEST Test Persistence with Flight Booking
/AIF/RECIPIENTS Recipients of a User
/AIF/REP_AC_ASGN AIF Reprocessing Action Assignment
/AIF/REP_AC_DEF AIF Reprocessing Action Definition
/AIF/SERIAL_INDEX Manual Change of External Index
/AIF/TEXT_HINTS Transport Text of Hints
/AIF/TJ_CONFIG Configure Data Transfer
/AIF/TOPICDEF AIF Topic Definition
42 C U S T O M E R

/AIF/TOPICSTATUS Maintain Topic ID Status
/AIF/TRANSFER Transfer into AIF Persistence
/AIF/VMAP Value Mapping
/AIF/VMAP_BASE Base Transaction for Value Mappings
/AIF/VPN Maintain Validity Periods
In addition, an AIF Administrator is provided with the change authorization to the following views:
Table 32:
View/View Cluster Description
/AIF/VC_TJ_CONS Configure Data Transfer
3.2.2 AIF All Authorizations
This role template contains all SAP Application Interface Framework authorization objects with all activities
and also all SAP Application Interface Framework transactions. It should only be used for test purposes.

3.2.3 AIF Architect
An AIF Architect is responsible for planning and coordinating the development of interfaces.
For these tasks, an AIF Architect is provided with the following authorizations:
Table 33:
/AIF/CFUNC 2 Change
/AIF/CFUNC 6 Delete
/AIF/CLINK 2 Change
/AIF/CLINK 6 Delete
/AIF/CTEXT 2 Change
/AIF/CTEXT 6 Delete
/AIF/CUST 2 Change
/AIF/CUST 3 Display
/AIF/ERR 16 Execute
/AIF/ERR 33 Read
/AIF/ERR 34 Write
/AIF/ERR 71 Analyze
/AIF/ERR 75 Remove
/AIF/ERR A4 Resubmit
44 C U S T O M E R

/AIF/HINTS 2 Change
/AIF/HINTS 3 Display
/AIF/HINTS 6 Delete
/AIF/IFDET 2 Change
/AIF/IFDET 6 Delete
/AIF/LFA 3 Display
/AIF/LFA 6 Delete
/AIF/LFA 33 Read
/AIF/LFA 34 Write
/AIF/LFA 71 Analyze
/AIF/PROC 60 Import
/AIF/PROC 61 Export
/AIF/PROC A4 Resubmit
/AIF/SER 2 Change
/AIF/SER 3 Display
/AIF/VMAP 2 Change
/AIF/VMAP 3 Display
In addition, an AIF Architect is provided with the authorization to the following transaction codes:
Table 34:
/AIF/BDC_GEN Batch Input Structure Generator

/AIF/CUST_COPY AIF Customizing Copy
/AIF/CUST_SMAP_COPY Copy Customizing
/AIF/IDOC_GEN IDoc Structure Generator
/AIF/IDOC_TEST Generate Test IDocs
/AIF/IFB Interface Builder
/AIF/IFTEST Interface Test Tool
46 C U S T O M E R

/AIF/MSGNOTI Message Overview Notification
/AIF/RECIPIENTS Recipients of a User
/AIF/RFC_FUNC_GEN RFC Function Generator
/AIF/RFC_MASS_GEN Mass RFC Function Generator
/AIF/TEXT_HINTS Transport Text of Hints
In addition, an AIF Architect is provided with the change authorization to the following views:
Table 35:
/AIF/ALERT Define Recipients
/AIF/ERROR_GLB Global Features
/AIF/ERROR_HDL Define Applications
/AIF/V_IDOCSTAT Mapping of IDoc Status to AIF Status
/AIF/V_NS Define Namespace

/AIF/V_RFC_FCOL Define RFC Function Module Collection
/AIF/V_RFC_FUNCS Assign Functions to RFC Function Module Collection
/AIF/V_SYSNAMES Define Business Systems
3.2.4 AIF Developer
An AIF Developer is responsible for the development of interfaces.
For these tasks, an AIF Developer is provided with the following authorizations:
Table 36:
/AIF/CFUNC 2 Change
/AIF/CFUNC 6 Delete
/AIF/CLINK 2 Change
/AIF/CLINK 6 Delete
/AIF/CTEXT 2 Change
/AIF/CTEXT 6 Delete
/AIF/CUST 2 Change
/AIF/CUST 3 Display
48 C U S T O M E R

/AIF/ERR 16 Execute
/AIF/ERR 33 Read
/AIF/ERR 34 Write
/AIF/ERR 71 Analyze
/AIF/ERR 75 Remove
/AIF/HINTS 2 Change
/AIF/HINTS 6 Delete
/AIF/IFDET 2 Change
/AIF/IFDET 6 Delete
/AIF/LFA 3 Display
/AIF/LFA 6 Delete
/AIF/LFA 33 Read
/AIF/LFA 34 Write
/AIF/LFA 71 Analyze
/AIF/PROC 60 Import
/AIF/PROC 61 Export
/AIF/SER 2 Change
/AIF/SER 3 Display

/AIF/VMAP 2 Change
/AIF/VMAP 3 Display
In addition, an AIF Developer is provided with the authorization to the following transaction codes:
Table 37:
/AIF/BDC_GEN Batch Input Structure Generator
/AIF/CUST_COPY AIF Customizing Copy
/AIF/CUST_SMAP_COPY Copy Customizing
/AIF/IDOC_GEN IDoc Structure Generator
/AIF/IDOC_TEST Generate Test IDOCs
50 C U S T O M E R

/AIF/IFB Interface Builder
/AIF/IFTEST Interface Test Tool
/AIF/RFC_FUNC_GEN RFC Function Generator
/AIF/RFC_MASS_GEN Mass RFC Function Generator
/AIF/TRANSFER Transfer into AIF persistence
In addition, an AIF Developer is provided with the change authorization to the following views:
Table 38:
/AIF/ACTIONS Define Actions
/AIF/CHECKS Define Checks
/AIF/ERROR_IF Define Interface-Specific features

/AIF/ERROR_NS Define Namespace-Specific features
/AIF/FIXVALUES Define Fix Values
/AIF/SMAP Define Structure Mapping
/AIF/VALMAPS Define Value Mappings
/AIF/VARIANT_MAPPINGS_ALL Define Variant Mappings
/AIF/VC_SERIAL Define Serialization Settings
/AIF/V_ENGINES Define Custom-Specfic Engines
/AIF/V_FINF Define Interfaces
/AIF/V_FINF_ENG Define Interfaces (Engine Fields)
/AIF/V_FINF_IDOC Define Interfaces (IDOC fields)
/AIF/V_IFKEY Define Interface Key Fields for Variants
3.2.5 AIF Business User
An AIF Business User is responsible for monitoring interfaces and error handling. This includes editing fields (if
allowed in the Customizing of the interface), restarting and canceling data messages, and so on.
52 C U S T O M E R

For these tasks, an AIF Business User is provided with the following authorizations:
Table 39:
/AIF/CFUNC 2 Change
/AIF/CFUNC 6 Delete
/AIF/CLINK 2 Change
/AIF/CLINK 6 Delete
/AIF/CTEXT 2 Change
/AIF/CTEXT 6 Delete
/AIF/CUST 3 Display
/AIF/ERR 16 Execute
/AIF/ERR 33 Read
/AIF/ERR 34 Write
/AIF/ERR 71 Analyze
/AIF/ERR 75 Remove
/AIF/HINTS 2 Change
/AIF/HINTS 6 Delete
/AIF/LFA 6 Delete

/AIF/LFA 33 Read
/AIF/LFA 34 Write
/AIF/LFA 71 Analyze
/AIF/PROC 60 Import
/AIF/PROC 61 Export
/AIF/SER 3 Display
/AIF/VMAP 2 Change
/AIF/VMAP 3 Display
In addition, an AIF Business User is provided with the authorization to the following transaction codes:
Table 40:
In addition, an AIF Business User is provided with the change authorization to the following views:
Table 41:
3.2.6 AIF Power User
An AIF Power User is responsible not only for monitoring and error handling but also for advanced functions, for
example, archiving, correction reports, message snapshots, scheduling file uploads from application server,
performance tracking, runtime configuration groups, defining automatic reprocessing, and configuring data
transfer (for example, qRFC interfaces).
54 C U S T O M E R

For these tasks, an AIF Power User is provided with the following authorizations:
Table 42:
/AIF/CFUNC 2 Change
/AIF/CFUNC 6 Delete
/AIF/CLINK 2 Change
/AIF/CLINK 6 Delete
/AIF/CTEXT 2 Change
/AIF/CTEXT 6 Delete
/AIF/CUST 3 Display
/AIF/ERR 16 Execute
/AIF/ERR 33 Read
/AIF/ERR 34 Write
/AIF/ERR 56 Display archive
/AIF/ERR 71 Analyze
/AIF/ERR 75 Remove
/AIF/HINTS 2 Change

/AIF/HINTS 6 Delete
/AIF/LFA 3 Display
/AIF/LFA 6 Delete
/AIF/LFA 33 Read
/AIF/LFA 34 Write
/AIF/LFA 71 Analyze
/AIF/PROC 60 Import
/AIF/PROC 61 Export
/AIF/SER 2 Change
/AIF/SER 3 Display
/AIF/VMAP 2 Change
/AIF/VMAP 3 Display
In addition, an AIF Power User is provided with the authorization to the following transaction codes:
Table 43:
56 C U S T O M E R

In addition, an AIF Power User is provided with the change authorization to the following views:
Table 44:

3.2.7 AIF Processing
This template contains the minimal authorization for processing SAP Application Interface Framework
messages (for example, for system users). It contains the following authorizations:
Table 45:
/AIF/LFA 6 Delete
/AIF/LFA 33 Read
/AIF/LFA 34 Write
/AIF/PROC 60 Import
/AIF/PROC 61 Export
58 C U S T O M E R

3.2.8 AIF Test Template (Non-Productive)
This role template contains not only SAP Application Interface Framework authorizations and transactions but
also several other authorizations and transactions that are needed for some test scenarios.
Recommendation
Do not use this template in a productive or a “real” development environment.
3.3 Set Up Interface-Specific and Key Field-Specific
Authorizations
Use
In the SAP Application Interface Framework, you can set up interface-specific and key-field-specific
authorizations in Customizing for the SAP Application Interface Framework (transaction code AIF/CUST). This
enables you to specify authorizations on the basis of a single message’s content. You can assign interface-
specific authorizations that allow or deny users certain activities depending on data received by the interface.
Example
A data message includes a plant and a business system identifier. A business user is responsible only for a
specific combination of a plant and a business system. You should only authorize them to display and
change messages for the specific combination that is relevant to them.
Process
1. You specify the fields that are relevant for authorizations as key fields and include them in a custom single
index table. You do this in Customizing for the SAP Application Interface Framework under Error Handling
Interface-Specific Features .
2. You create a custom authorization object in Maintain the Authorization Objects (transaction code SU21).
The authorization object needs to fulfill the following requirements:
○ It requires a field called ACTVT.
○ The available activities in the ACTVT field must be the same as for the /AIF/ERR authorization object.
○ It requires one field for each key field that serves as the basis for the authorization.
3. In Customizing for the SAP Application Interface Framework under Error Handling Interface-Specific
Features , you assign the authorization object to an interface, you specify a field sequence number, and
you link the key fields to the fields of the authorization object.

Note
When entering a field sequence number, you must enter the corresponding field sequence number from
the definition of the key fields.
Result
You have defined the key fields, created the authorization object, assigned the authorization object to an
interface, and linked the key fields to the fields of the authorization object.
Example: Interface-Specific Authorizations
The interface-specific authorization can be used, for example, if you want to specify that users are only able to
display or change data if the data was received from a particular business system.
● Interface
INTERFACE01
● Users
USER01 and USER02
● Systems
SYSTEM01 and SYSTEM02
The INTERFACE01 interface can receive data from either SYSTEM01 or SYSTEM02. USER01 is only responsible
for data received from SYSTEM01 and USER02 is only responsible for data received form SYSTEM02. The
interface-specific authorization is used, for example, to ensure that USER01 is not able to change data received
from SYSTEM02.
3.4 Considerations about Data Protection
As a technical framework that enables changes to be made to business-critical interface data, the SAP
Application Interface Framework is required to save user-related information that could be marked as personal,
private, or confidential. The SAP Application Interface Framework provides you with authorizations you can use
to limit access to this information.
The following sections describe user-related or potentially confidential data that is saved and that could be
accessed using the SAP Application Interface Framework.
60 C U S T O M E R

Single or Multi Message Index Table
The single or multi message index tables, which record aggregated information on a per-data-message-level,
contain fields for the following:
● The user name of the user that processed the message along with the date and time of the initial message
processing
● The user name of the user that last changed the message (restarted or canceled it) along with the date and
time of the action
Data in the single or multi index tables is not visible on any screen in the SAP Application Interface Framework.
It can only be accessed through direct database query or the ABAP dictionary.
Log of Changes in Error Handling
Changes to a data message’s field values, which originated from the Monitoring and Error Handling transaction,
are recorded in a log table. The following information is saved:
● The name and path of the changed field along with the old and new value
● The user name of the user who initiated the change along with the date and time of the change
The change log data can be viewed in the Error Handling Changes Log (transaction code /AIF/EDCHANGES),
which you can access from the SAP Easy Access menu by choosing Cross-Application Components SAP
Application Interface Framework Administration Log Error Handling Changes Log . The transaction
enables the user to see a list of changes. It is only when the user selects a change log entry and chooses to view
the details that the user name of the user who made the change is displayed. For this functionality (display the
user name), a separate authorization is needed (the /AIF/CDLOG authorization object).
Note
This transaction is protected by authorization object S_TCODE.
Information Contained in Interface Data
Depending on your interfaces, message data can contain personal, private, or confidential information. This
information can be accessed by all users who have the authorization to display or change messages of the
interface in the Monitoring and Error Handling transaction. If you identify such information and do not want the
information to be available for error handling, you can define the corresponding structures as Hide Structures.
You do this in Customizing for SAP Application Interface Framework under Error Handling Namespace-
specific Features .

4 Uninstallation of SAP Application
Interface Framework
If you do not want to use SAP Application Interface Framework any more, you can remove the software
components AIF, AIFX and AIFGEN from your system using the add-on Installation tool (transaction SAINT).
Caution
Before performing the uninstallation procedure, consider the following:
● You need to perform several preparation actions to enable a safe uninstallation. Otherwise, the
uninstallation of the add-ons may lead to loss of data.
● We strongly recommend that you do not uninstall SAP Application Interface Framework if there are
compliance or auditing obligations to retain the messages data.
For more information about the preparation steps and the uninstallation procedure, see 2497991
62 C U S T O M E R
Uninstallation of SAP Application Interface Framework

Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however,
does not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of
SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as
"sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun
does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any
damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for
transparency (see: http://help.sap.com/disclaimer).
Important Disclaimers and Legal Information C U S T O M E R 63

go.sap.com/registration/
contact.html
© 2017 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company. The information contained herein may
be changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company products and services
are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of
SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.

Sap s4 hana 1709 op sap api-master guide

More Related Content

What's hot (20)

Similar to Sap s4 hana 1709 op sap api-master guide (20)

Recently uploaded (20)

Sap s4 hana 1709 op sap api-master guide