We are running ERP 6.0 SPS 5 on our ERP 6.0 system and running the corresponding components on the NW 7.0 portal. We are planning to upgrade only SAP_BASIS and SAP_ABAP to SP 13 that are part of SPS 11. We do not want to upgrade the portal components at all as we think it might affect the code as well as underlying base components of the portal which becomes a larger effort. Does anybody know if this is going to cause any problems in the future? Please let us know. Thanks.
Agreed. But we have a ERP 6.0 ABAP only backend and the front end is the Portal based on J2EE. We just want to avoid the portal upgrade if at all possible because of the pain involved. Is that possible.
> Agreed. But we have a ERP 6.0 ABAP only backend and the front end is the Portal based on J2EE. We just want to avoid the portal upgrade if at all possible because of the pain involved. Is that possible.
If the Java part is installed as Addin it's not possible. If it's a separate instance you can just update the ABAP.
Ok. It seems like it defeats the SAP's purpose of SP stacks. But, in reality it is hard to upgrade all the components in one shot and incur a long effort and downtime. That is why we are taking this approach of applying the bare minimum required support packs. But does SAP support this kind of effort or ask us to upgrade by stack only?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.