Skip to Content
0
Feb 23, 2011 at 01:35 PM

General Question concerning ESS implementations (Mapping, Linking, etc.)

27 Views

Hi Experts,

we have set up our "company-ESS" Role(Portal) in a way of using the original content provided by SAP as templates only, this means for every Ressource we did a Z_Ressource, for every Area we did a Z_Area, all iViews are deltalinked and so on; meaning all SAP original content is untouched. Up until now we never had problems with this but now we are at the point of implementing Travel Management.

Szenarios like Payslip, Bankdata, Leave Request or the like always have One Ressource with no relations whatsoever...

The "Problem" occuring with, for example, "All my trips" which I created a Z_ressource, etc. (see above) is, the buttons on the WD are all pointing to the original ressources. These ressources don't have a PCD mapping to the frontend, because we want to leave them untouched, so we get 404-errors of course.

My question is: Is there an elegant way to change these Button-Mappings? (enhancing hundreds of feeder-class methods isn't elegant..) or would you advice to use deltalinks in Portal Frontend but use the Original ressources by SAP in the Backend to eliminate this "Mapping-Issue"?

advice would be appreciated

best regards, Lukas