Support Package pre-requistis accross different landscapes

[Former Member]

I am struggling with which landscape but be patched before another since adding PI 711 into the mix.

I am supporting ECC6 EHP4 with NW701, BI 70 at Netweaver 70, Solution Manager 70 Ehp1 and now PI 71 ehp1.

I have been told PI must lead all other landscapes support package level but with it being at a later version of Netweaver than all other landscapes it is a far comparison or does it already lead them?

My immediate need is to begin planning for a support package project on the ECC6 EHP4 landscape in the fall. Since this landscape was last patch, about one year ago we add the PI landscape.

It is a pretty safe bet I will be struggling with this same question in about 6 months when I start looking at a BI support package project.

Any help that could be provided on this would be most appriciated.

Bill

[Former Member · Accepted solution]

Historically our strategy has been to patch BI during the first quarter of each year and ECC6 during the third.

Solution manager is done on more of a adhoc basis but does get patched at least once a year.

Our dilemma is how PI fits in to this mix. PI is now our Master SLD and updates the other SLDs on our different landscapes including Solution Manager and NWDI.

BTW NWDI is patched at the same time as ECC6.

Question comes back to PI: Do we need to patch it just prior to any other system meaning I am applying the latest patches to it a couple times a year.

With PI, ECC6 and BI all being at different versions, how do I compare support package levels.

As the landscape grows it seems Basis is always in a support package project.

[sunny_pahuja2 · Accepted solution]

Hi,

I would prefer below strategy:

1) Upgrade ECC system (Since in your case ECC system is already on latest level, then go to second one)

2) BI upgrade.

3) PI upgrdae (PI upgrade you have to plan carefully as it is your Master SLD and feeds other SLD.)

4) Solution Manager upgrade.

Thanks

Sunny

[stuart_campbell]

I think we need to understand more why you feel certain systems need to be patched first or in a certain order

- from what you say there must be technical concerns across more than one product area

Perhaps it could be that --->

Generally systems that interact with one another should be on the same BASIS level and SP stack - the general rule of thumb

Products such as SLD definately have to be on systems with equivalent or higher BASIS version and SP stack than systems

they interact with because the content created for a Netweaver 700 SLD

may not be able to cope data supplier information from a Netweaver EHP1 system (this also raise other concerns regarding

exporting data between SLDs - again equivalency - or higher for target system is recommended, sometimes with SLD lower BASIS version source systems may have limited export options as well)

Products such a Solution Manager also as a rule of thumb have to be on equivalent or higher BASIS version or SP levels

than the systems they interact with

But PI also may have similiar concerns because they manage communication between systems e.g business systems

However lets take say Payroll in ECC without any ESS or Legacy Systems, ALE

- totally standalone payroll system - the only rules that apply there are that it works, has the latest fixes and required legal changes and follows a recommended stack - no BASIS equivalency level between other systems may exist in order for payroll to carry out its purpose

Does this help clarify further ?

Best wishes

Stuart

[JPReyes]

I have been told PI must lead all other landscapes support package level but with it being at a later version of Netweaver than all other landscapes it is a far comparison or does it already lead them? 

I think the important thing here is that patching is done consistently without leaving one of the systems unattended for too long... I don't think you'll have any issue if one of your systems is a couple of stacks up or down, but try to keep them at the same level. Usually I patch ECC then the other systems.

Regards

Juan

[sunny_pahuja2]

Hi,

PI is very important because it connects ECC system from legacy systems and also SLD resides on this system. As per my recommendation, you should patch BI first as you BI system is on 700 basis release but your ECC system is on 701 basis release.

So first patch BI system and the patch ECC system.

Thanks

Sunny

[Former Member]

Hi,

>PI is very important because it connects ECC system from legacy systems and also SLD resides on this system

Well, that may be the case in your company but it is not a universal truth. We don't use PI to connect ECC to legacy systems and we don't run SLD on it...

Regards,

Olivier

[sunny_pahuja2]

Hi,

> >PI is very important because it connects ECC system from legacy systems and also SLD resides on this system

>

> Well, that may be the case in your company but it is not a universal truth. We don't use PI to connect ECC to legacy systems >and we don't run SLD on it...

>

True, I have given example as per my experience.

Thanks

Sunny