Skip to end of metadata
Go to start of metadata

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

 

IDoc Message CodeMessage code (variant) used in the IDoc



IDoc Message FunctionMessage function used in the IDoc



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: "SAP Cloud Platform Integration"

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Integration Runtime Artifact ID

ID of the Runtime Artifact of the Integration Flow in the SAP CPI tenant

 

 


 

Integration Runtime Artifact Name

Name of the Runtime Artifact of the Integration Flow in the SAP CPI tenant

 

 



Integration Runtime Artifact Status

Status of the Runtime Artifact of the Integration Flow in the SAP CPI tenant


 



Integration Runtime Artifact TypeType of the Runtime Artifact of the Integration Flow in the SAP CPI tenant



Routing Attributes
Sender ProtocolProtocol used by the sender of the Integration Flow



Receiver ProtocolProtocol used by the receiver of the Integration Flow



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

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

Attributes for Interface Technology: “Remote Function Call”

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

 

Caller Program

Program that triggers the   interface

 

 

X

 

Queue Name1)

Pattern for the RFC queue (like R3A*)

 

 

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

Trigger Mode

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

X

 

X

  •   Dialog
  •   Background
  •   Dialog/Background

Routing Attributes

RFC Destination

Self-explanatory

X

 

X

 

Logon/Server Group

The server group a   function call is addressed to

X

 

X

 

1)  Only for subtype: qRFC

Attributes for Interface Technology: “SAP Workflow”

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Workflow Name

ID of the respective workflow as maintained in   Workflow Builder (SWDD)

 

 

 

 

Technology Object (Task Name)

Name of the task as   maintained in Workflow Builder (SWDD)

 

 

 

 

Step   Type

Type of the workflow step that executes the task

 

 

X

  •   Dialog
  •   Background
  •   Dialog/Background

No.   of Dialog Steps

No. of dialog steps   contained in the workflow

 

 

 

 

No. of Background Steps

No. of background steps contained in the workflow

 

 

 

 

Task   ID

ID of the task as   maintained in Workflow Builder (SWDD)

 

 

 

 

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: “Remote Database Access”

Specific Attributes for interface technology SQL, subtype ADBC

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (SQL)

SQL request

 

 

X

  •   SQL Request

DB Connection Name

Name of the remote   database connection (as maintained in DBACOCKPIT)

X

 

X

 

Schema Name

Schema addressed on the remote database (as   maintained in DBACOCKPIT)

 

 

X

 

DBMS Type

Type of remote database   (as maintained in DBACOCKPIT)

 

 

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
Specific Attributes for interface technology SQL, subtype JDBC

Interface Attribute

Description

Syst.-dep.

Mult. Values

Value help

Fixed values

Technical Attributes

Technology Object (SQL)

SQL request

 

 

X

  •   SQL Request

SQL Statement

Native SQL statement   triggered against the remote database

 

 

 

 

Data Source Name

Name of the data source as maintained in Netweaver   Administrator -> JMS   Server Configuration

 

 

 

 

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

Routing Attributes

Database URL

URL to call the remote database

X

 

 

 

 

PI_NAMESPACE_REC

Receiver Interface Namespace

 

 

X

 

PI_NAMESPACE_SEN

Sender   Interface Namespace

 

 

X

 

  • No labels