ESS Travel request

[Former Member]

Hi

How do i setup ESS travel request ? on ECC 6.

Thanks

Rendani

[Former Member · Accepted solution]

As you are on ECC6 TRIP instead of using trip transaction use the travel workset availabel in ESS.

This is also availabe in abap webdynpro and proivdes better functionality then TRIP transaction.

ESS user should use the new functionality provided in ESS instead of old transactions.

Check the link below for details

http://help.sap.com/erp2005_ehp_02/helpdata/en/2c/1ec6e9352c4766a4eb1ed0b924309c/content.htm

Message was edited by:

Barin Desai

[Former Member · Accepted solution]

TRIP transaction is a reflection of the happenings on ESS. The records created are visible on ESS too. For easy testing, TRIP will help to go through the business process. Later on, one can start testing on ESS using the UWL.

Thanks

Narasimha

[Former Member · Accepted solution]

TRIP is again ITS based and it has common view for travel plan and requst.

The wendynpro based delivery has different screens for both.

My advise is check both and use the one that suits your requirement.

[Former Member]

Hi

Functionally there are various approaches. Standard SAP provides three components

1.Travel request

2.Travel Plan

3.Travel expenses.

Out of these 3, Travel plan is complex as it includes configuring all type of travels ( air, rail, hotel etc), integrate with Global travel agencies, mapping etc.

To start with, users would prefer to raise a simple travel request, which triggers a w/flow for approval, once approved go for an external site for travel booking ( travel plan in SAP terms). On completion of trip, raise expenses through ESS.

Use, TRIP transaction to play around with travel requests and Expense reports.

Another imp step is to copy standard Travel schema to customize as per yr company's business.

A combination of R/3 & ESS roles will help access to Travel on Portal.

If this helps, pl do reward.

Thanks

Narasimha

[Former Member]

1. Setup travel management in R/3 a

2. Setup ESS

3. Do the required config for the user