This website is not affiliated with, sponsored by, or approved by SAP AG.

Transports When Upgrading to EHP6

Basis (Basis Technology Modules: Basis Component/System Administration, GUIs)

Moderators: Snowy, thx4allthefish

Transports When Upgrading to EHP6

Postby vdmron » Thu May 23, 2013 7:58 am

Hi All

We are looking at upgrading to EHP6, and have a question about current transports.
If we have config or workbench transports currently in the dev system which are not ready to move what is the standard procedure for these when upgrading the Enhancement Package
Do we have to transport these through, or will they still be there after the Upgrade. Previously we always made sure that all transports were moved prior to applying an EHP.

Posts: 50
Joined: Fri Apr 04, 2003 8:53 am

Re: Transports When Upgrading to EHP6

Postby Snowy » Mon May 27, 2013 3:49 pm

they will still be there, but importing them AFTER EHP6 upgrade involves risks.

test import these out on an upgraded QA boxes before risking to put them on PROD.
SapFans Moderator

Posts: 28785
Joined: Mon Oct 21, 2002 2:33 pm
Location: 3.1415926535

Re: Transports When Upgrading to EHP6

Postby bpandey1959 » Fri May 31, 2013 4:36 am

It is very risky to import request after ehp6 upgrade because component level will mismatch.
Better to release all pending requests.

Bhagawati Pandey
Posts: 3
Joined: Fri May 31, 2013 3:47 am

Re: Transports When Upgrading to EHP6

Postby bcchap » Fri Jun 07, 2013 7:32 am

If the transport is still in the Dev systrem like you say and unreleased then its fine. You can release them after the upgrade and they will then take the EHP6 version so there is no risk of table/customizing inconsistency as long as they have not been released yet.
However as Snowy said .... you do need to ensure than any changes that were made at a lower release and saved into a transport are tested before they go into production and I have to assume that you do fully test everything in such a way as requested by SAP.

However... this then begs the question... why does SAP recommend to release everything before the upgrade?

The reason is that doing so means you are just testing upgrade changes in QAS rather than testing upgrade and functional change at once. Its not a big issue and I say feel free to release after the ehp
Posts: 6
Joined: Fri Jun 07, 2013 6:53 am

Return to Basis

Who is online

Users browsing this forum: No registered users and 5 guests

This website is not affiliated with, sponsored by, or approved by SAP AG.