Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

As outlined in the previous chapters Solution Documentation provides two different object types to describe data exchange: Interfaces and Composite Interfaces. The main differences between the two types are as follows.

Interface

Composite Interface

  • Consists of a sender, receiver and an (optional) middleware LCG.
  • No interface steps can be maintained.
  • No interface graphic is at hand.
  • Interface technology must be provided, and it’s possible to attach an Interface Details element to document interface attributes.
  • Can consist of 1…n LCGs.
  • Allows to provide interface steps.
  • Can include interfaces.
  • Interface graphic can be created.
  • No interface technology can be assigned, and consequently no Interface Documentation can be attached directly.

The purpose of an Interface is to describe a point-to-point connection (and for simple cases also three-component interfaces) with all technical and functional attributes using the Interface Documentation functionality. A Composite Interface, however, is the preferred solution to document complex interfaces and integration scenarios running over multiple components, using different point-to-point data exchanges between the single components, and having additional processing logic which can be described with interface steps. Interface and Composite Interface complement one another and can be integrated with each other seamlessly.

Creation of Composite Interfaces and Interface Graphics

To create a new Composite Interface add the corresponding element from the context menu using New -> Composite Interface in the desired place in Interface Library. Name the Composite Interface and save.

 

Next you can add Interfaces and Interface Steps via New -> Interface or Interface Step to the Composite Interface, to create the processing logic in your integration scenario

When you have created all elements you should also draw an interface graphic. Switch to the Composite Interface level and select entry New -> Interface Diagrams -> Interface Diagram


This opens the graphical editor where you can arrange the Interface Steps in the desired sequence, draw connection lines between the respective Interface Steps, and assign Interfaces to Intermediate Message Events (see next chapter).


 Integration between Interfaces and Composite Interfaces via Intermediate Message Events

The graphical editor in Solution Documentation is based on the Business Process Model and Notation (BPMN) concept. For more information about BPMN in general, see http://www.bpmn.org. You can obtain more details about the graphical editor in Solution Documentation from the respective end user guide.

The connection between two Interface Steps running on two separate LCGs – which represents a point-to-point interface – can be achieved by adding so-called Intermediate Message Events (IME) to the graphic. The IME is the anchor point for further elements and thus can be used to attach Interfaces to the Composite Interface. Click the Assign (                         ) button next to the IME to open a dialog box. All Interfaces from the current Interface Library show up which have the right sender and receiver LCG. You can create multiple assignments to realize variants of the integration scenario. Already assigned Interfaces are listed, and you can remove them if necessary.

  


You can assign both Interfaces and Composite Interfaces to business processes in the Business Processes section of Solution Documentation.


Often it’s not desired to have all technical details of the data exchange on interface level visible in the process diagram directly. Therefor you can assign Interface and Composite Interface IMEs in the process diagram which “hides” the technical interface details from the process flow. Still all interface data is available, and you access it via forward-navigation if needed.

How to Document Integration Scenarios

As already described in the previous chapters there are two main objects to document interfaces and integration scenarios, Interfaces and Composite Interfaces. In addition, the Middleware Logical Component on Interface level provides some more flexibility for simple 3-component integration scenarios. However, if it comes to complex integration scenarios including more than two components it’s sometimes not easy to find the best way to document the flow in the system. In the following a few sample scenarios are described, to give you some guidance for ambiguous cases. Note that this list only contains examples and makes no claim to be complete.

Sample scenario 1: Synchronous retrieval of Business Partner data from an external system, including middleware system

An SAP ECC system needs business partner information from a non-SAP component. To facilitate the message transfer SAP PI/PO is used as a middleware component. The data is retrieved in synchronous manner, which means the caller (SAP ECC) requests the data from the non-SAP system and awaits the response in the same session. As it’s synchronous processing this scenario should be regarded as a single “interface” (or better: integration scenario) and should be documented accordingly. There are two options to achieve the same in Solution Documentation.

Composite interface with two LCGs (sender and receiver):

Use a Composite Interface and hide the PI system behind two Interfaces. These two Interfaces represent the request and the response track of the integration scenario. In an Interface diagram in Solution Documentation this could look like the following:

The Interfaces have the two business systems as sender and as receiver component, respectively, and SAP PI as a middleware LCG. Of course, the roles need to be set accordingly: for request, the SAP system is the sender and the non-SAP system the receiver, for response it’s vice versa. 


Composite interface with three LCGs (sender, receiver, middleware):

Here the SAP PI system is directly contained in the Composite Interface. In addition, you have to create 4 simple interfaces, to cover the communication SAP->PI, PI->non-SAP, and backwards, accordingly.

For those Interfaces no middleware LCG is needed. However, it’s questionable what to provide as an Interface Technology: the communication between ECC and PI is only a part of the whole PI interface, as well as the communication between PI and non-SAP. So, it’s not fully correct to provide Interface Technology SAP PI/PO to all Interfaces in this approach since redundant information would be maintained if you like to provide interfaces attributes, too.

In this case the first option might be favourable as it is less effort to maintain the data in the system, and interface attributes can be provided in a proper manner. The second option can make sense if you need to maintain additional processing logic on the different LCGs using interface steps.

Sample scenario 2: Asynchronous exchange of Business Partner data between two systems, including a middleware system

Basically, this is the same integration scenario as scenario 1), however, this time the data is exchanged in asynchronous manner. In this case, request and response are two different interfaces (one running from sender to receiver, one from receiver to sender). If additional processing logic is at hand (like Interface steps in the middleware) two Composite Interfaces have to be created for request and response. Otherwise it’s recommended to create two Interfaces for request and response and add the middleware system as a middleware LCG. Finally, you can still bind the whole integration scenario (the interfaces for request and response) in a Composite Interfaces, to visualize that those two tracks belong together.


In the following you can find a list of all Technical Attributes and Routing Attributes provided in standard per interface technology and subtype. In case of interface technology PI the adapter types are listed, too. Besides it is listed if an attribute is system-dependent or not, if it allows multiple entries, and if it provides a value help. If a value help is based on a domain the fixed values are indicated, too. The Functional Attributes are common for all interface technologies.


Functional attributes

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Business   Object

The business object   transferred in the interface

 

 

 

 

Average   Number of Interface Executions / Hour

Self-explanatory

X

 

 

 

Maximum   Number of Interface Executions / Hour

Self-explanatory

X

 

 

 

Average   Number of Interface Executions / Day

Self-explanatory

X

 

 

 

Maximum   Number of Interface Executions / Day

Self-explanatory

X

 

 

 

Average   Number of Interface Executions / Week

Self-explanatory

X

 

 

 

Maximum   Number of Interface Executions / Week

Self-explanatory

X

 

 

 

Average   Number of Interface Executions / Month

Self-explanatory

X

 

 

 

Maximum   Number of Interface Executions / Month

Self-explanatory

X

 

 

 

Required   Response Time (in ms)

Time in which one instance of the interface should   be processed

X

 

 

 

Peak Hour(s)

Self-explanatory

X

X

X

  • 01 - 02   am
  • 02 - 03   am
  • 03 - 04   am
  • 04 - 05   am
  • 05 - 06   am
  • 06 - 07   am
  • 07 - 08   am
  • 08 - 09   am
  • 09 - 10   am
  • 10 - 11   am
  • 11 - 12   am
  • 12 - 01   am
  • 01 - 02   pm
  • 02 - 03   pm
  • 03 - 04   pm
  • 04 - 05   pm
  • 05 - 06   pm
  • 06 - 07   pm
  • 07 - 08   pm
  • 08 - 09   pm
  • 09 - 10   pm
  • 10 - 11   pm
  • 11 - 12   pm
  • 12 - 01   pm

Peak Day(s)

Self-explanatory

X

X

X

  •   Monday
  •   Tuesday
  •   Wednesday
  •   Thursday
  •   Friday
  •   Saturday
  • Sunday

Peak Month(s)

Self-explanatory

X

X

X

  • January
  • February
  • March
  • April
  • May
  • June
  • July
  • August
  • September
  • October
  • November
  •   December

 

Attributes for Interface Technologies: “Application Link Enabling / IDoc” and “EDI Using IDocs”

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

IDoc Message Type

Self-explanatory

 

 

X

 

Technology   Object (IDoc Basic Type)

IDoc basic type

 

 

X

 

IDoc   Type Extension

Customer extension of basic IDoc type

 

 

X

 

Caller   Program

Program that triggers the   interface

 

 

X

 

Package Size

Size of IDoc packets to be sent (unit: IDoc)

X

 

 

 

Serialization Type

Used to determine the   order of IDocs during inbound processing

 

 

X

  • Timestamp
  • Message   Type
  • Object   Canal
  • qRFC

Is   ALE Audit Used?

If enabled ALE audit logs confirmation messages from   the receiver system on sender side

 

 

X

  •   Yes
  •   No

Transfer Mode

The way data is   transferred (always full set of data, or only the delta compared to the last   load)

X

 

X

  • Full
  • Delta
  • Full/Delta

Trigger Mode

The way the interface is triggered (in dialog or in   batch mode)

X

 

X

  •   Dialog
  •   Background
  •   Dialog/Background

Routing Attributes

Sender Partner Port

As maintained in IDoc partner profile (WE20)

X

 

X

 

Sender Partner Number

As maintained in IDoc   partner profile (WE20)

X

 

X

 

Sender Partner Type

As maintained in IDoc partner profile (WE20)

 

 

X

 

Sender Partner Role

As maintained in IDoc   partner profile (WE20)

 

 

 

 

Receiver Partner Port

As maintained in IDoc partner profile (WE20)

X

 

X

 

Receiver Partner Number

As maintained in IDoc   partner profile (WE20)

X

 

X

 

Receiver Partner Type

As maintained in IDoc partner profile (WE20)

 

 

X

 

Receiver Partner Role

As maintained in IDoc   partner profile (WE20)

 

 

 

 

RFC Destination

RFC destination used in the ALE port

X

 

X

 

Logon/Server Group

Server group for   immediately processed IDocs

X

 

X

 

Attributes for Interface Technology: “Batch Input”

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology   Object (Batch Session Name)

Name of the batch input session (SM35)

 

 

X

 

Creation Program

Name of the calling program (in externally called batch input   procedures), otherwise name of the current program

 

 

X

 

Called Transactions

Transaction called during batch input processing

 

 

X

 

Session Creator

User which created the   batch input session (‚Created By‘ in SM35)

X

 

X

 

Is Parallelization Allowed?

Can the interface process data in parallel?

 

 

X

  •   Yes
  •   No

Is Parallelization Used?

Does the interface process data in parallel?

 

 

X

  • Yes
  • No

Transfer Mode

The way data is transferred (always full set of   data, or only the delta compared to the last load)

X

 

X

  •   Full
  •   Delta
  •   Full/Delta

Trigger Mode

The way the interface is   triggered (in dialog or in batch mode)

X

 

X

  • Dialog
  • Background
  • Dialog/Background

Routing Attributes

Path   to Processed File(s)

File directory

X

 

 

 

 

Attributes for Interface Technology: “Business Documents”

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (BDoc Type)

BDoc Type (generation name)

 

 

X

 

CRM Site Name

Site name on CRM side used   for processing BDocs

 

 

X

 

ERP Site Name

Site name on ERP side used for processing BDocs

X

 

 

 

Transfer Mode

The way data is   transferred (always full set of data, or only the delta compared to the last   load)

X

 

X

  • Full
  • Delta
  • Full/Delta

Routing   Attributes

RFC   Destination from CRM to ERP

Self-explanatory

X

 

X

 

RFC   Destination from ERP to CRM

Self-explanatory

X

 

X

 

 

Attributes for Interface Technology: “Direct Input”

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology   Object (Program Name/Transaction)

Name of the program or transaction that is called

 

 

X

 

Is Parallelization Allowed?

Can the interface process   data in parallel?

 

 

X

  • Yes
  • No

Transfer Mode

The way data is transferred (always full set of   data, or only the delta compared to the last load)

X

 

X

  •   Full
  •   Delta
  •   Full/Delta

Attributes for Interface Technology: “General File-based Interface”

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (File Type)

File format used

 

 

X

  •   Flat File
  •   CSV
  •   XML
  •   Others

File Name

Self-explanatory

X

 

 

 

File Pattern

Recurring pattern in the file names of a file   interface

X

 

 

 

File Creator

User who created the file   in the system

X

 

X

 

File Size (in kB)

Self-explanatory

X

 

 

 

Transfer Program Name

Program that creates the   file

 

 

X

 

Is Parallelization Allowed?

Can the interface process data in parallel?

 

 

X

  •   Yes
  •   No

Transfer Mode

The way data is   transferred (always full set of data, or only the delta compared to the last   load)

X

 

X

  • Full
  • Delta
  • Full/Delta

Routing Attributes

Path   to Processed File(s)

File directory

X

 

 

 

 

Attributes for Interface Technology: “HTTP / WebService”

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (Service Name)

Name of the called service / web service

 

 

 

 

Transfer Mode

The way data is   transferred (always full set of data, or only the delta compared to the last   load)

X

 

X

  • Full
  • Delta
  • Full/Delta

Method /Operation1)

Name of the service method which is called

 

 

 

 

REST   Method (e.g. GET / POST)2)

Type of HTTP operation

 

 

 

 

Routing Attributes

URL / ICF Path

URL of the service / name   of the ICF (Internet Communication Framework) path that is called

X

 

 

 

Consumer Proxy1)

Name of the consumer proxy

 

 

 

 

HTTPS Required?2)

Is secure communication   needed for this interface?

 

 

X

  • Yes
  • No

Logical Port1)

Name of the Logical Port which is used to call the   consumer proxy

X

 

 

 

1) Only for subtypes: ABAP, JAVA, GENERAL

2) Only for subtype: ODATA

 

 Attributes for Interface Technology: “Java Message Service”

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (JMS   Message)

Used JMS message type

 

 

 

 

Routing Attributes

JMS Queue

Name of the JMS queue which is addressed on receiver   side

 

 

 

 



Attributes for Interface Technology: “Other, Not Listed Technology”

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object

Generic attribute for all interface technologies   where no dedicated technology object can be provided per default

 

 

 

 

Transfer Mode

The way data is   transferred (always full set of data, or only the delta compared to the last   load)

X

 

X

  • Full
  • Delta
  • Full/Delta

 

Attributes for Interface Technology: “SAP Process Integration / Process Orchestration”

 

Interface technology SAP Process Integration / Process Orchestration deals with different entities. The subtype refers to the PI installation type which can be a dual-stack or JAVA-only installation. In addition, per installation type a number of adapter types are defined. Some of the interface attributes are specific per adapter type and are thus listed in additional tables. However, most interface attributes are the same for all adapter types. Those common attributes are listed below.

 

Common attributes for all adapter types for interface technology PI | Specific attributes for 3rd-Party Adapter | Specific attributes for AribaNetwork Adapter | Specific attributes for B2B AS2 Adapter | Specific attributes for B2B EDI Adapter | Specific attributes for B2B OFTP Adapter | Specific attributes for B2B x400 Adapter | Specific attributes for Business Connector Adapter | Specific attributes for Chemical Industry Data Exchange Adapter | Specific attributes for File Adapter | Specific attributes for HTTP Adapter | Specific attributes for HTTP Adapter (ABAP)1) | Specific attributes for HTTP Adapter (ODATA) | Specific attributes for HTTP Adapter (REST) | Specific attributes for Intermediate Document Adapter (JAVA) | Specific attributes for Intermediate Document Adapter (ABAP)1) | Specific attributes for JAVA Database Connector Adapter | Specific attributes for JAVA Messaging Services Adapter | Specific attributes for JAVA Proxy | Specific attributes for Mail Adapter | Specific attributes for Master Data Management Adapter | Specific attributes for Marketplace Adapter | Specific attributes for Remote Function Call Adapter | Specific attributes for RosettaNet Implementation Framework Adapter | Specific attributes RosettaNet Implementation Framework 11 Adapter | Specific attributes for SFTP Adapter | Specific attributes for Simple Object Application Protocol Adapter | Specific attributes for SuccessFactors Adapter | Specific attributes for WebService Reliable Messaging Adapter (JAVA) | Specific attributes for WebService Reliable Messaging Adapter (ABAP)1) | Specific attributes for XI Adapter (ABAP Proxy)

 

Common attributes for all adapter types for interface technology PI

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Routing Attributes

PI Scenario Name

Name of the Process Integration Scenario as defined   in Enterprise Services Builder

 

 

 

 

Sender Schema

Message structure for   inbound processing as defined in Enterprise Service Repository (like WSDL,   XSD, or DTD)

 

 

X

 

Sender Party

Communication party: Usually represents a company   unit that is to be involved and addressed in message exchange

 

 

X

 

Sender Service

Service: usually used to   represent a technical or business unit that represents part of the features   provided by a communication party

 

 

X

 

Sender Interface Name

Name of the interface used in inbound processing

 

 

X

 

Sender Interface Namespace

Namespace used in inbound   processing

 

 

X

 

Sender Agreement1)

Defines the technical details for inbound processing   of a message

 

 

 

 

Sender Channel Name

Defines how an adapter   transforms a message inbound processing

 

 

 

 

Receiver Schema

Message structure for outbound processing as defined   in Enterprise Service Repository (like WSDL, XSD, or DTD)

 

 

X

 

Receiver Party

Communication party: Usually   represents a company unit that is to be involved and addressed in message   exchange

 

 

X

 

Receiver Service

Service: usually used to represent a technical or   business unit that represents part of the features provided by a   communication party

 

 

X

 

Receiver Interface Name

Name of the interface used   in outbound processing

 

 

X

 

Receiver Interface Namespace

Namespace used in outbound processing

 

 

X

 

Receiver Agreement1)

Defines the technical   details for outbound processing of a message

 

 

 

 

Receiver Channel Name

Defines how an adapter transforms a message during   outbound processing

 

 

 

 

Integration   Flow / Integrated Object identifier2)

Self-explanatory

X

 

 

 

Routing Logic Used

Logical routing defines the flow of message in a   system landscape

 

 

X


  •   Static Routing
  •   Content-Based Routing
  •   Extended Receiver   Determination

Module Name

Name of the module(s)   used in the interface. Modules equip the adapter with additional functions

 

X

 

 

Complex Mapping Used?

Self-explanatory

 

 

X

  •   Yes
  •   No

Mapping Name

Mapping is used to   transform the data structure and format used by the sender into the structure   and format the receiver can handle

 

X

 

 

Mapping Technology

Mapping program as defined in the Enterprise   Services Builder

 

 

X

  •   Graphical
  •   ABAP
  •   JAVA
  •   XSLT
  •   Value Mapping

Message Split Used?

Is the message sent to   multiple recipients?

 

 

X

  • Yes
  • No

Business Process Engine /   ccBPM Used?1)

ccBPM: cross-component Business Process Management

 

 

X

  •   Yes
  •   No

NetWeaver   Business Process Management Used?2)

NetWeaver Business Process   Management is used to compose executable processes using standardized   notation

 

 

X

  • Yes
  • No

Pattern   Used for Netweaver BPM Process2)

An interface pattern describes the type of   communication that is to be executed on the message when the interface is   used. It determines what kind of operations can be defined for a service   interface. The selected interface pattern has an impact on the activities   related to the programming of the business logic in the related back-end   system

 

 

 

 

Payload Encryption Required?

Self-explanatory

 

 

X

  • Yes
  • No

1) Only for subtype: Dual stack

2) Only for subtype: JAVA-only

 

In the following you can find all additional attributes which are specific for a particular PI adapter type.

 

Specific attributes for 3rd-Party Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object

Generic attribute for all interface technologies   where no dedicated technology object can be provided per default

 

 

 

 

3rd Party Adapter Type

Self-explanatory

 

 

 

 

 

 

Specific attributes for AribaNetwork Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object

Generic attribute for all interface technologies   where no dedicated technology object can be provided per default

 

 

 

 

Ariba Backend System Type

Self-explanatory

 

 

X

  • Buyer
  • Supplier

 

 

Specific attributes for B2B AS2 Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object

Generic attribute for all interface technologies   where no dedicated technology object can be provided per default

 

 

 

 

 

 

Specific attributes for B2B EDI Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object

Generic attribute for all interface technologies   where no dedicated technology object can be provided per default

 

 

 

 

EDI Message Protocol

Protocol used during EDI   transmission

 

 

X

  • ANSI   X.12
  • Edifact
  • EANCOM
  • Odette
  • VDA
  •   Tradacom
  •   Plain
  • XML

 

 

Specific attributes for B2B OFTP Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object

Generic attribute for all interface technologies   where no dedicated technology object can be provided per default

 

 

 

 

 

Specific attributes for B2B x400 Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object

Generic attribute for all interface technologies   where no dedicated technology object can be provided per default

 

 

 

 

 

 

Specific attributes for Business Connector Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (SOAP)

SOAP   message used

 

 

X

  •   SAP PI SOAP Message

 

Specific attributes for Chemical Industry Data Exchange Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (SOAP)

SOAP   message used

 

 

X

  •   SAP PI SOAP Message

 

 

Specific attributes for File Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (File   Type)

File format used

 

 

X

  • Flat File
  • CSV
  • XML
  • Others

File Content Conversion   Used?

To bring incoming file content into a different   format

 

 

X

  • Yes
  • No

Chunked File Transfer Used?

Split   large files in several chunks to avoid memory issues during PI message   processing

 

 

X

  • Yes
  • No

Routing   Attributes

Path to Processed   File(s)

File directory

X

 

 

 

FTP   Server Name

Name of the FTP server that processes the files

X

 

 

 

Is   Parallelization Allowed?

Can   the interface process data in parallel?

 

 

X

  • Yes
  • No

 

 

Specific attributes for HTTP Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (SOAP)

SOAP   message

 

 

X

  •   SAP PI SOAP Message

 

 

Specific attributes for HTTP Adapter (ABAP)1)

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (SOAP)

SOAP   message

 

 

X

  •   SAP PI SOAP Message

1) Only for subtype: Dual stack

 

Specific attributes for HTTP Adapter (ODATA)

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (SOAP)

SOAP   message

 

 

X

  •   SAP PI SOAP Message

Routing Attributes

RFC   Destination

Self-explanatory

X

 

X

 

OData   Operation Type

Type of call for the OData service

 

 

X

  • CREATE
  • DELETE
  • MERGE
  • QUERY
  • READ
  • UPDATE

 

 

Specific attributes for HTTP Adapter (REST)

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (SOAP)

SOAP   message

 

 

X

  •   SAP PI SOAP Message

 

 

Specific attributes for Intermediate Document Adapter (JAVA)

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (IDoc Basic Type)

Self-explanatory

 

 

X

 

Routing Attributes

Is ALE Audit Used?

If   enabled ALE audit logs confirmation messages from the receiver system on   sender side

 

 

X

  • Yes
  • No

Package   Size

Size of IDoc packets to be sent (unit: IDoc)

X

 

 

 

Application   Server (Running Gateway)

The   application server that is addressed

X

 

 

 

 

 

Specific attributes for Intermediate Document Adapter (ABAP)1)

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (IDoc   Basic Type)

Self-explanatory

 

 

X

 

Routing Attributes

Is ALE Audit Used?

If   enabled ALE audit logs confirmation messages from the receiver system on   sender side

 

 

X

  • Yes
  • No

Package   Size

Size of IDoc packets to be sent (unit: IDoc)

X

 

 

 

1) Only for subtype: Dual stack

 

 

Specific attributes for JAVA Database Connector Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (SQL)

SQL request

 

 

X

  •   SQL Request

Is Parallelization Used?

Does the interface process data in parallel?

 

 

X

  • Yes
  • No

Routing   Attributes

Remote DB Provider and   Version

Name + provider of the remote database (like   Oracle 10)

 

 

 

 

Remote   DB Host

Host   name of the remote database

X

 

 

 

 

 

Specific attributes for JAVA Messaging Services Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (JMS   Message)

Used JMS message type

 

 

 

 

Queue Manager Name

Name of the JMS queue manager which administers   the JMS queues in scope

 

 

 

 

Routing Attributes

JMS   Provider Type

Name of the JMS Service provider

 

 

 

 

Provider   Server Name

Server   name which is addressed

X

 

 

 

 

 

Specific attributes for JAVA Proxy

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (SOAP)

SOAP   message

 

 

X

  •   SAP PI SOAP Message

Routing Attributes

Standard   Content?

Is   the interface definition based on SAP-defined content, or custom   configuration?

 

 

X

  • Yes
  • No

HTTPS Required?

Is secure communication needed for this   interface?

 

 

X

  • Yes
  • No

 

 

Specific attributes for Mail Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object

Generic attribute for all interface technologies   where no dedicated technology object can be provided per default

 

 

 

 

Routing Attributes

Mailserver   Host

Host   name of the mail server

X

 

 

 

Protocol   Used

Protocol for mail processing

 

 

X

  • IMAP
  • POP3
  • SMTP

 

 

 

Specific attributes for Master Data Management Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object

Generic attribute for all interface technologies   where no dedicated technology object can be provided per default

 

 

 

 

 

 

Specific attributes for Marketplace Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object

Generic attribute for all interface technologies   where no dedicated technology object can be provided per default

 

 

 

 

Routing Attributes

Document   Destination ID

Marketplaces   based on the MML (MarketSet Markup Language) message format use a DDID   (Document Destination ID) to address senders and receivers

 

 

 

 

 

 

Specific attributes for Remote Function Call Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (Called   Function)

Function   module that is called on receiver side

 

 

X

 

Program ID (Registered at Gateway)

Name of the server program registered at SAP   Gateway

 

 

 

 

Maximum Connections (1-X)

Maximum   number of connections which can be used in parallel

 

 

 

 

Routing Attributes

RFC   Destination

Self-explanatory

X

 

X

 

Port   Name

Communication port used in the message processing

 

 

 

 

Gateway   Host

Host   name of the gateway used

X

 

 

 

 

 

Specific attributes for RosettaNet Implementation Framework Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

RosettaNet Service Message

Name   of the RosettaNet Service Message

 

 

 

 

Technology Object (Protocol   Type)

 

 

 

X

  • HTTP
  • HTTPS

Single or Double Action Used?

Single   action message: only request; double-action message: request and response

 

 

X

  • Single Action
  • Double Action

 

 

Specific attributes RosettaNet Implementation Framework 11 Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

RosettaNet Action Message

Name   of the RosettaNet Action Message

 

 

 

 

Technology   Object (Protocol Type)

 

 

 

X

  • HTTP
  • HTTPS

Single or Double Action   Used?

Single   action message: only request; double-action message: request and response

 

 

X

  • Single Action
  • Double Action

 

 

Specific attributes for SFTP Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (File   Type)

File format used

 

 

X

  • Flat File
  • CSV
  • XML
  • Others

File Content Conversion   Used?

To bring incoming file content into a different   format

 

 

X

  • Yes
  • No

Chunked File Transfer Used?

Split   large files in several chunks to avoid memory issues during PI message   processing

 

 

X

  • Yes
  • No

Routing   Attributes

Path to Processed File(s)

File   directory

X

 

 

 

FTP   Server Name

Name of the FTP server that processes the files

X

 

 

 

Is   Parallelization Allowed?

Can   the interface process data in parallel?

 

 

X

  • Yes
  • No

 

 

Specific attributes for Simple Object Application Protocol Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (SOAP)

SOAP   message

 

 

X

  •   SAP PI SOAP Message

Routing Attributes

Protocol   Used

Type   of the SOAP protocol

 

 

X

  • XI 3.0 Protocol
  • SOAP
  • Axis

URL   / ICF Path

URL of the service / name of the ICF (Internet   Communication Framework) path that is called

X

 

 

 

HTTPS   Required?

Is   secure communication needed for this interface?

 

 

X

  • Yes
  • No

 

 

Specific attributes for SuccessFactors Adapter

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object

Generic attribute for all interface technologies   where no dedicated technology object can be provided per default

 

 

 

 

 

Specific attributes for WebService Reliable Messaging Adapter (JAVA)

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object

Generic attribute for all interface technologies   where no dedicated technology object can be provided per default

 

 

 

 

Routing Attributes

URL   / ICF Path

URL   of the service / name of the ICF (Internet Communication Framework) path that   is called

X

 

 

 

 

 

Specific attributes for WebService Reliable Messaging Adapter (ABAP)1)

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object

Generic attribute for all interface technologies   where no dedicated technology object can be provided per default

 

 

 

 

Routing Attributes

URL   / ICF Path

URL   of the service / name of the ICF (Internet Communication Framework) path that   is called

X

 

 

 

1) Only for subtype: Dual stack

 

 

Specific attributes for XI Adapter (ABAP Proxy)

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (SOAP)

SOAP   message

 

 

X

  • SAP PI SOAP Message

Routing Attributes

Standard Content?

Is   the interface definition based on SAP-defined content, or custom   configuration?

 

 

X

  • Yes
  • No

HTTPS Required?

Is secure communication needed for this   interface?

 

 

X

  • Yes
  • No

 

 

Find below the mapping between interface technologies in Solution Manager 7.1 and the corresponding interface technologies in Solution Manager 7.2. The number of interface technologies in Solution Manager 7.2 is reduced significantly, instead subtypes are introduced. Interface technology SAP Process Integration / Process Orchestration provides a third level below the subtype to detail the adapter types used in the interface.


Interface Technology (old)

Interface Technology (new)

Subtype

Adapter Type (for SAP PI / PO)

Application   Link Enabling / IDoc

Application Link Enabling /   IDoc

 

 

Batch   Input

Batch Input

 

 

Business   Documents

Business Documents

 

 

Direct   Input

Direct Input

 

 

EDI   using IDocs

EDI Using IDocs

 

 

General   file-based interface

General File-based Interface

 

 

HTTP - ABAP   Webservice (Internet Communication Manager)

HTTP / WebService

ABAP

 

HTTP - General Webservice

HTTP /   WebService

General

 

HTTP - Java   Webservice (HTTP J2EE dispatcher)

HTTP / WebService

JAVA

 

Java Message Service

Java   Message Service

 

 

Manual procedure

Other, Not Listed Technology

 

 

Other, not listed   technology

Other,   Not Listed Technology

 

 

Asynchronous RFC

Remote Function Call

Asynchronous RFC

 

Background RFC - queued   units

Remote Function   Call

Background   RFC (Queued Units)

 

Background RFC -   transactional units

Remote Function Call

Background RFC (Transactional Units)

 

Queued RFC

Remote   Function Call

Queued   RFC

 

Synchronous RFC

Remote Function Call

Synchronous RFC

 

Transactional RFC

Remote   Function Call

Transactional   RFC

 

SAP Workflow

SAP Workflow

 

 

SQL - ADBC Connection

Remote   Database Access

ABAP   Database Connectivity

 

SQL - Java Database   Connectivity (direct call to external data base)

Remote Database Access

JAVA Database Connectivity

 

PI - 3rd Party adapter

SAP   Process Integration / Process Orchestration

Dual   Stack

3rd-Party   Adapter

PI - B2B AS2 Adapter

SAP Process Integration / Process   Orchestration

Dual Stack

B2B AS2 Adapter

PI - B2B OFTP Adapter

SAP   Process Integration / Process Orchestration

Dual   Stack

B2B   OFTP Adapter

PI - B2B X400   Adapter

SAP Process Integration / Process   Orchestration

Dual Stack

B2B x400 Adapter

PI - Business Connector   adapter

SAP   Process Integration / Process Orchestration

Dual   Stack

Business   Connector Adapter

PI - Chemical   Industry Data Exchange adapter

SAP Process Integration / Process   Orchestration

Dual Stack

Chemical Industry Data Exchange Adapter

PI - File Adapter

SAP   Process Integration / Process Orchestration

Dual   Stack

File   Adapter

PI - Intermediate   Document adapter

SAP Process Integration / Process   Orchestration

Dual Stack

Intermediate Document Adapter (ABAP)

PI - Java Database   Connector adapter

SAP   Process Integration / Process Orchestration

Dual   Stack

JAVA   Database Connector Adapter

PI - Java Messaging   Services adapter

SAP Process Integration / Process   Orchestration

Dual Stack

JAVA Messaging Services Adapter

PI - Mail adapter

SAP   Process Integration / Process Orchestration

Dual   Stack

Mail   Adapter

PI - Marketplace   adapter

SAP Process Integration / Process   Orchestration

Dual Stack

Marketplace Adapter

PI - Master Data   Management Adapter

SAP   Process Integration / Process Orchestration

Dual   Stack

Master   Data Management Adapter

PI - Remote Function   Calls adapter

SAP Process Integration / Process   Orchestration

Dual Stack

Remote Function Call Adapter

PI - Rosettanet   Implementation Framework

SAP   Process Integration / Process Orchestration

Dual   Stack

RosettaNet   Implementation Framework

PI - Rosettanet   Implementation Framework 11

SAP Process Integration / Process   Orchestration

Dual Stack

RosettaNet Implementation Framework 11

PI - SFTP Adapter

SAP   Process Integration / Process Orchestration

Dual   Stack

SFTP   Adapter

PI - Simple Object   Application Protocol adapter

SAP Process Integration / Process   Orchestration

Dual Stack

Simple Object Application Protocol Adapter

PI - WebService Reliable   Messaging Adapter

SAP   Process Integration / Process Orchestration

Dual   Stack

WebService   Reliable Messaging Adapter (ABAP)

PI - SAP Exchange   Infrastructure adapter

SAP Process Integration / Process   Orchestration

Dual Stack

XI Adapter (ABAP Proxy)

PI - HTTP adapter

SAP   Process Integration / Process Orchestration

Dual   Stack

HTTP   Adapter (ABAP)

PI - ABAP Proxy

SAP Process Integration / Process   Orchestration

Dual Stack

XI Adapter (ABAP Proxy)

PI - JAVA Proxy

SAP   Process Integration / Process Orchestration

Dual   Stack

JAVA Proxy



 




 

 

  • No labels