SAP ABAP Data Element APB_LPD_SYSTEM_ALIAS (System Alias)
Hierarchy
☛ SAP_UI (Software Component) User Interface Technology
   ⤷ BC-MUS-LP (Application Component) Launchpad
     ⤷ APB_LAUNCHPAD (Package) Launchpad (generic functions)
Basic Data
Data Element APB_LPD_SYSTEM_ALIAS
Short Description System Alias  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type APB_LPD_SYSTEM_ALIAS    
Data Type CHAR   Character String 
Length 100    
Decimal Places 0    
Output Length 100    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 SysAlias 
Medium 15 System Alias 
Long 20 System Alias 
Heading 55 System Alias 
Documentation

Definition

Specifies the name of the system that has been determined as the target system in the Enterprise Portal or in transaction SM59 (Configuration of RFC Connections), in which the application is to be called.

System aliases and connections are created by system administrators.

Use

SAP NetWeaver Business Client (NWBC) Environment

In the SAP NWBC environment, you create the system connections in transaction SM59 of the back-end system that starts the SAP NWBC. For most application types, a type H connection (HTTP Connections to ABAP System) is required which points to the back-end system. This is explained in further detail below:

  • For SAP NetWeaver BI 7.x based application types, such as BI Query, BI Web Template, BI Enterprise Report, and Xcelsius Dashboard, where normally the SAP_BI system alias is used, a type H (HTTP Connections to ABAP System) connection is required that points to the BI Enterprise Portal.

  • For SAP BW 2.x/3.x based application types, such as BW Query and Template, where normally the SAP_BW system alias is used, a type H (HTTP Connections to ABAP System) connection is required that points to the BW backend.

  • For Crystal Reports based application types, the following connections are required:

  • SAP_BW is a type H connection (HTTP Connections to ABAP System) that points to the BI back-end system.
  • SAP_BW_BOE is a type H connection (HTTP Connections to ABAP System) that points to the Business Object Enterprise Server.
  • SAP_BW_RFC is a type 3 connection (ABAP Connections) that points to the BI back-end system.

Note that the names of the connections are dependent upon the name you enter as the system alias; for example, the names for the connections above arise if you enter the system alias SAP_BW for a Crystal Report in the Launchpad Customizing.

The system alias, SAP_LocalSystem, points to the back-end system from which the SAP NWBC is called, and which is without an explicit connection.

The following table describes example connections:

Application Type    System Alias        Connection    Example

            Type

WebDynpro ABAP    SAP_ECC_Financials        H    Target Host: backend.wdf.sap.corp, Service No.50000

Report Writer    SAP_ECC_Financials        H    Target Host: backend.wdf.sap.corp, Service No.50000

Transaction    SAP_ECC_Financials        H    Target Host: backend.wdf.sap.corp, Service No.50000

Infoset Queries    SAP_ECC_Financials        H    Target Host: backend.wdf.sap.corp, Service No.50000   

BEx Analyzer    SAP_BW        H    Target Host: BW-backend.wdf.sap.corp, Service No.50000

BW Template 2.x/3.x    SAP_BW        H    Target Host: BW-backend.wdf.sap.corp, Service No.50000

BW Query 2.x/3.x    SAP_BW        H    Target Host: BW-backend.wdf.sap.corp, Service No.50000

BI Queries 7.x    SAP_BI        H    Target Host: BIPortal.wdf.sap.corp, Service No.50000

BI Templates 7.x    SAP_BI        H    Target Host: BIPortal.wdf.sap.corp, Service No.50000

BI Enterprise Reports    SAP_BI        H    Target Host: BIPortal.wdf.sap.corp, Service No.50000

Xcelsius Dashboards    SAP_BI        H    Target Host: BIPortal.wdf.sap.corp, Service No.50000

Crystal Reports    SAP_BW        H    Target Host: BW-backend.wdf.sap.corp, ServiceNo.50000

Crystal Reports    SAP_BW_BOE        H    Target Host: Business_Object_Enterprise.wdf.sap.corp, Service No.50000

Crystal Reports    SAP_BW_RFC        3    Target System: ABC, Client 000

Enterprise Portal Environment

In the Portal, the system connections are defined by creating system connection iViews in the system configuration.


For most application types, you must define the Web Application Server (Web AS) property of the system iView. This connection points to the back-end system in which the application is called, as detailed below:

  • For SAP NetWeaver BI 7.x based application types, such as BI Query, Template, Enterprise Report, Xcelsius Dashboard, where normally the SAP_BI system alias is used, the Web Application Server (Web AS) property must be defined. This connection points to the BI Enterprise Portal.

  • For Web Dynpro Java, the Web Application Server (Web AS) property must be defined. This connection points to the Enterprise Portal where the WD Java application is deployed.

  • For BW 2.x/3.x based application types, such as BW Query, and Template, where normally the SAP_BW system alias is used, the Web Application Server (Web AS) property must be defined. This connection points to the BW back-end system. You must also define the Connector property of the iView.

  • For Crystal Reports, you use the same configurations that are used for BW 2.x/3.x based applications. You must also define the Crystal Enterprise Server category of the iView.

The following table describes example connections:

Application Type    System Alias    Property Category    Example

WebDynpro ABAP    SAP_ECC_Financials    Web Application Server    Web AS Host Name: backend.wdf.sap.corp:50000, Web AS Protocol

WebDynpro Java    SAP_XSS    Web Application Server    Web AS Host Name: portal.wdf.sap.corp:50000, Web AS Protocol

Report Writer    SAP_ECC_Financials    Internet Transaction Server, Connector    ITS Host Name: backend.wdf.sap.corp, Service No.50000, ITS Path: /sap/bc/gui/sap/its/webgui/, SAP System ID (SID)=ABC, SAP client=000

Transaction    SAP_ECC_Financials    Internet Transaction Server, Connector     ITS Host Name: backend.wdf.sap.corp, Service No.50000, ITS Path:/sap/bc/gui/sap/its/webgui/, SAP System ID (SID)=ABC, SAP client=00

Infoset Queries    SAP_ECC_Financials    Internet Transaction Server, Connector    ITS Host Name: backend.wdf.sap.corp, Service No. 50000, ITS Path: /sap/bc/gui/sap/its/webgui/, SAP System ID (SID)=ABC, SAP client=000

BEx Analyzer    SAP_BW    Internet Transaction Server, Connector    ITS Host Name: backend.wdf.sap.corp, Service No. 50000, ITS Path: /sap/bc/gui/sap/its/webgui/, SAP System ID (SID)=ABC, SAP client=000,...

BW Template 2.x/3.x    SAP_BW    Web Application Server, Connector    Web AS Host Name: bwbackend.wdf.sap.corp:50000, Web AS Protocol, SAP System ID (SID)=ABC, SAP client=000

BW Query 2.x/3.x    SAP_BW    Web Application Server, Connector    Web AS Host Name: bwbackend.wdf.sap.corp:50000, Web AS Protocol, SAP System ID (SID)=ABC, SAP client=000

BI Queries 7.x    SAP_BI    Web Application Server    Web AS Host Name: BIPortal.wdf.sap.corp:50000, Web AS Protocol

BI Templates 7.x    SAP_BI    Web Application Server    Web AS Host Name: BIPortal.wdf.sap.corp:50000, Web AS Protocol

BI Enterprise Reports    SAP_BI    Web Application Server    Web AS Host Name: BIPortal.wdf.sap.corp:50000, Web AS Protocol

Xcelsius Dashboards    SAP_BI    Web Application Server    Web AS Host Name: BIPortal.wdf.sap.corp:50000, Web AS Protocol

Crystal Reports    SAP_BW    Web Application Server, Connector, Crystal Enterprise server    Web AS Host Name: bwbackend.wdf.sap.corp:50000, Web AS Protocol, SAP System ID (SID)=ABC, SAP client=000

Dependencies

Example

History
Last changed by/on SAP  20130604 
SAP Release Created in 710