Dear All
My client has a highly customised version of the Travel Management
WebDynpro Java applications and are still running at version ESS 1.0 SP16.
sap.com/ess~tra/AllMyTrips
sap.com/ess~tra~tre/Expenses
sap.com/ess~tra~tre~trs/DeleteExpenses
sap.com/ess~tra~tri/ChangePersNo
The backend server used to run the ESS services has been upgraded to
ECC6.0 EHP5 and would like to take advantage of the new WebDynpro ABAP
applications introduced in business package FIN_TRAVEL_1, FIN_TRAVEL_2
and FIN_TRAVEL_3.
We would like to take the following approach to achieve this aim:
Phase 1) Technical activation of FIN_TRAVEL_1/2/3
System Regression Test
Promote to Production
Continue to use WebDynpro Java ESS applications
Phase 2) Replace the WebDynpro Java AllMyTrips, Create Expense Report
and Change Personnel number applications with customised version of
the WebDynpro ABAP.
In short, ignoring the homepage navigation, can the WebDynpro Java applications
continue to run if FIN_TRAVEL_1, FIN_TRAVEL_2 and FIN_TRAVEL_3 have been
activated. My initial testing has confirmed no adverse results, however I am very interested
to know any other experiences.
There is a very good reason for considering this approach. The deployment window
between HRSP releases is small and considered too small to try a big bang approach where the business packages
are activated, customisation for 50 countries created for WebDynpro ABAP applications Create Expense, POWL,
change employee number , test, deploy to Production and retire the WebDynpro Java applications.
The preferred approach will allow for system stability for an irreversable switch and allow more time to
create the country specific modifications.
Kind regards
Mike