EHP3 dependency to XSS package in the EP

[Former Member]

Hi,

it sounds a bit strange but we would like to implement EHP3 but on the portal site would like to leave it with the standard XSS 1.0 (the version you use without any EHPs) and don't upgrade to XSS 1.3.1 version.

Some background. My question is related to an HCM system where we use several ESS apps like change of address, Personal information, pay slip etc.

The EHP3 we would like to implement because of the new travel expense module. Due to the travel module could be used since EHP2/3 standalone without any iviews in the portal (Webdynpro for ABAP) we would like to implement to EHP3 in the backend and the portal the XSS (former ESS) we would like to continue on the old version due to this version is havily customized. And to adjust the XSS1.3.1 would increase the effort tremendous.

Does anybody know if this a supported combination?

thx

Hans Georg

[siddharthrajora · Accepted solution]

Hans

This can be used but it can lead to issues once you start patching in near future, So its better

you start off with correct patch levels I have seen customer having the same patch level as yours

but SAP wont recommend this !

Have a look at the notes or service.sap.com/erp-ehp

[Former Member · Accepted solution]

Hi,

I give this answer my self because it may help other struggeling the same way.

We got an official answer by SAP that this combination is a supported status.

The intention of an EHP is that you could implement and EHP without switching on any new func and this should not impact the existing environment. (If this make sense is a other question)

Due to we would like to swich on only the travel func. and we haven't used it before and it is WEB dynpro for ABAP it should also have no impact. (this will not retain testing)

But if you would like to use new (which requires Portal component) or already used funcinalities out of the EHP (like ESS) this will require an update on the portal side as well.

This dependency will move more and more away as soon SAP switches more into direction of webDynpro for ABAP which will happen with EHP5.

[stuart_campbell]

Hi Guys

What you are saying is that if you plan to use Travel EHP3 and meet the EHP3 pre-reqs there should be no problems

certainly in this case you are upgrading EHP3 AND meeting the pre-reqs therefore fufilling the core purpose of EHP

implementation for Travel only

However...EA_HR 603 is a core dependancy of ESS

Is one of the pre-reqs for Travel EHP3 activating EA_HR 603?

Best regards

Stuart

[stuart_campbell]

Hi Hans Georg

In theory it may be possible to run BP ESS 1.0 with EA_HR 603, SAP_ESS 600 (or 603) however if we check the scenarios listed at www.service.sap.com/scl we see it is not a recommended combination - based on this URL I would not therefore recommend it

If you plan to implement this environment you would need to test extensively before running productively- you also need to be aware that

1) If you activate specific extension sets or business functions this may change ESS functionality and IMG customizing

this could have an affect on existing ERP 6.0 environment (for example you activate something that can only be

used by 1.31 BP AND it replaces existing 1.0 IMG functions)

2) This environment is not guaranteed, therefore what works now might not work during future patching, SPs or delivery

I hope this helps

Best wishes

Stuart