cancel
Showing results for 
Search instead for 
Did you mean: 

My Trips and Expenses - tab refresh functionality

Former Member
0 Kudos

Hi Experts,

Only one tab from My trips and Expenses screen is getting refreshed after clicking 'My trips and Expense' link. I found SAP note 1542417, which says after implementation of note 1495681 or corresponding support package, the refresh of POWL query in WDA version of Travel application is not done for all tabstrip in the same time for performance reason.

After implementing SAP note 1542417, manual setting is required in IMG to set URL parameter &SAP_FITV_REFRESHA=X, to refresh of POWL query parallel for all tabstrip. I followed the steps given in the note to make the refresh functionality parallel, but still only active tab is getting refreshed. Please let me know if any action is required after maintaining the URL parameter.

Kindly help me in this.

Thanks,

Siva Sankar

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

I have the exact same problem on EHP4.

I've set the extra parameter SAP_FITV_REFRESHA=X on the resource EMPLOYEE_TRAVEL_ALLMYTRIPS_SRV_12 but only the "All my trips" Query is refreshed.

The rest of the tabs are untouched.

This is especially frustrating when you know how easy this task is in EHP5++.

Can anyone help?

Lukas_Weigelt
Active Contributor
0 Kudos

Hi Lasse,

I can't directly relate to the problem because I'm on EHP6. But I've taken a look at the note and the coding. You should debug WDYN FITV_POWL_TRIPS Eventhandler "HANDLE_DEFAULT" of Window "TRAVELLER" around. Serach for "*OCA 1542417", set an external breakpoint there.

Maybe the parameter isn't correctly retrieved from the URL. Alternatively maybe the subsequently fired plug and the Init-Hooks handle the parameter incorrectly.

I hope this helps a bit with the analysis.

I wouldn't be surprised if this simply is a standard problem, there have been tons of standard problems with POWL...

Cheers, Lukas

Former Member
0 Kudos

Hi Lukas, thanks for the details. I've actually created an SAP Incident for this issue, so I'm hoping they will return with something useful.

Else I will definitely hit the debugger

BR
Lasse