Technical Name of Business Function |
FIN_TRAVEL_PLANNING_EXTERNAL |
Type of Business Function |
Enterprise business function |
Available As Of |
SAP enhancement package 4 for SAP ERP 6.0 |
Technical Usage |
Human Capital Management |
Application Component |
Travel Management (FI-TV) |
Prerequisite Business Function |
Travel Management (FIN_TRAVEL_1) |
This business function enables you to use third-party online booking systems for booking travel services instead of using SAP Travel Planning.
This business function improves and simplifies the travel management process for customers who use SAP ERP 6.0 in their back-end system.
If, in addition to the SAP system, you have used a third-party online booking system up to now for your travel planning, then this business function offers the following benefits:
Optimization of the travel management process
Savings of direct and indirect costs
Reduction of manual interfaces
Reduced costs for Sarbanes-Oxley compliance, which is provided by SAP Expense Reports
The new features are available only with the Web Dynpro ABAP-based user interface of SAP Travel Management.
You can send the general data from an SAP travel request to a third-party online booking system and transfer booking data from a third-party online booking system to an SAP expense report. You also can make calling a third-party online booking system dependent on the status of the travel request.
You can use this business function to use the following features for integrating the GetThere online booking system by Sabre:
An example implementation of the Business Add-In BAdI: Define Exit for Third-Party Travel Planning, which illustrates how you can integrate the GetThere online booking system:
You can copy the example implementation and adapt it to meet your requirements.
An example implementation of the Business Add-In BAdI: Mapping for TravelPlanningArrangementEmployeeNotification, which extends the mapping of master data to meet the specific requirements of GetThere
You can copy the example implementation and adapt it to meet your requirements.
The integration of GetThere in SAP NetWeaver Portal requires that the user names in GetThere must be the same as those in SAP NetWeaver Portal.
You have installed the following components as of the specified version (or higher):
Type of Component |
Component |
Only Needed for the Following Functions |
---|---|---|
Software component |
EA-HRGxx 604 and SAP_HRGxx 604 |
|
Portal content |
Business Package for Employee Self-Service 1.41 SP 04 |
If you use SAP NetWeaver Portal. |
You have activated the Travel Management Extension (EA-TRV) enterprise extension in your back-end system.
You have configured the Travel Management (FI-TV) application component.
You have activated the Travel Management (FIN_TRAVEL_1) business function in your back-end system.
You have activated this Travel Management, Third-Party Travel Planning (FIN_TRAVEL_PLANNING_EXTERNAL) business function in your back-end system.
This business function contains the following new and enhanced features:
Before you can integrate a third-party online booking system with SAP Travel Management, you need to implement the Business Add-In BAdI: Define Exit for Third-Party Travel Planning (PTRM_EXTERNAL_TP_BADI_DEF). The main purpose of this BAdI is to redirect all navigation links that point to SAP Travel Planning to a third-party online booking system. The BAdI constructs the URL for accessing the third-party online booking system. The BAdI uses URL parameters to send the data for identifying the user and the SAP system. When applicable, the BAdI also uses URL parameters to send the trip number and the data of an underlying travel request.
The enhancement spot PTRM_EXTERNAL_TP_ENHSPOT contains example implementation PTRM_EXT_TP_ENHSPOT_GETTHERE, which illustrates how you can integrate the GetThere online booking system. You can copy the example implementations and adapt them to meet your requirements.
For more information, see Customizing for Travel Management under
.You can use the enterprise service Travel Planning Arrangement Out with service operation TravelPlanningArrangementEmployeeNotification_Out to provide master data from SAP Travel Management to third-party online booking systems. You can use the Business Add-In BAdI: Mapping for TravelPlanningArrangementEmployeeNotification to control the mapping of the outbound interface.
This business function includes the example implementation PTRM_SE_PROXY_GETTHERE, which adapts the mapping of master data to meet the requirements of GetThere. You can copy the example implementation and adapt it to meet your requirements.
For more information about this enterprise service, see SAP Library on SAP Help Portal at help.sap.com
.SAP NetWeaver Portal contains a new page and a new iView, which enables the system to launch an online booking system. The Employee Self-Service role has been enhanced accordingly.
Note
For technical reasons, the portal content for third-party travel planning resides in the content administration of SAP NetWeaver Portal under
.Single Sign-On (SSO) is a mechanism that spares users the trouble of entering a password for each system they log on to. With SSO, a user identifies him- or herself only once and afterwards can log on to all systems that are part of the SSO environment.
In SAP NetWeaver Portal, the system can use SSO to log on the users of SAP Travel Management automatically to a third-party online booking system.
Before you can use Single Sign-On, you need to provide the public certificate (SAPLogonTicketKeypair-cert.pse
) of your SAP NetWeaver Portal for the third-party travel planning system.
For more information, see Single Sign-On to Non-SAP Systems and Applications.
Third-Party Travel Planning