Problem adding SAPKH60007 - ECC6.0 upgrade

[Former Member]

Hi all,

I am right now upgrading 4.6C (4.6D) to ECC 6.0 SR2. Currently in the 4.6C (4.6D Kernel), we have SAP_APPL (SP 53) and the equivalent for that during the PREPARE phase is SAP_APPL SP7 (SAPKH60007) but, the delivery DVDs comes with SAPKH60006. So, in the BIND_PATCH phase, I added SAPKH60007 and SAPKH60008. Surprisingly, when I verified in the subsequent steps, I didn't see them added to the list of support packs. I tried this several times but, didn't work and as we were on a time bound project and having so much pressure and with only only man handling the whole show, I just went ahead without SAPKH60007. Of Course, this support pack is required by note '983757'. I have completed upgrading to ECC 6.0 SR2 in Development system.

Now, I want to upgrade SAP_APPL to SP7 but, when I go to SPAM, and load the support pack through application server (as SAPKH60007 is 57 MB approx.), and when I go to define the support pack for import queue, I don't see anything in the EPS_ROOT.

Can somebody help me as what needs to be done here?

Thank you.

[Former Member · Accepted solution]

Markus,

Thank you for the prompt response.

I think there is a lack of clarification on the question I have posted. Here is what it is.

I am not trying to use the SPAM on 4.6D. I am trying to apply the support pack SAPKH60007 using SPAM on ECC 6.0 and kernel is 7.00. As I had mentioned in my previous post, I have completed the upgrade to ECC 6.0 SR2 with KERNEL 7.00.

And one more information to share with you again is, I did try to apply the target system's support pack SAPKH60007 during the PREPARE process in the BIND_PATCH phase. But, at that point, the SAPup did not detect this Support Pack either. So, I just went ahead with the upgrade without the SAPKH60007. I thought it should work after the upgrade is done. Unfortunately it is not working now, either.

Thank you.

[markus_doehr2 · Accepted solution]

Ok... but if SAPup said, that SP7 was REQUIRED to get equivalency, you may have lost some data now...

That SP may have prerequisites, check in SPAM with "New Supportpackages" if you see it there and drill down and check if you have all prereqs.

--

Markus

[markus_doehr2]

The import for the target system is not done in SPAM but later during SAPup. Uncar the files there, SAPup will check for them and display them.

You can't add a support package for ECC into a SPAM running on 4.6D.

--> Read the upgrade guide!

--

Markus

[Former Member]

OK, an addition to my earlier message above.

While trying to load the support pack through Application Server in SPAM, I went through the list of 'ATT' and 'PAT' files in the /EPS/in. I am surprised I could see the following:

-

---

CSR0120031469_0024944.PAT SAPKH60007 @EB\QUpload Already Occurred@ 0004 OCS file already exists in inbox. Upload not required.

-

---

CSN0120061532_0025572.PAT SAPKH60008 @EB\QUpload Already Occurred@ 0004 OCS file already exists in inbox. Upload not required.

-

---

But, when I select the button 'Display / Define' for import queue, and when I choose, 'SAP_APPL', I wouldn't get any support packs waiting to import. Added to this, one more thing I thought would be more informative is, when I downloaded the SAPKH60007 and uncar the KH60007.CAR, I get a message that 'ATT' and 'PAT' files are moved to /EPS/in.

-

---

This is what I see as output when I uncar KH60007.CAR

x EPS/in/CSR0120031469_0024944.ATT

x EPS/in/CSR0120031469_0024944.PAT

-

---

This is what I see as output when I uncar KH60008.CAR

x EPS/in/CSN0120061532_0025572.ATT

x EPS/in/CSN0120061532_0025572.PAT

-

---

Can someone help me findout why is this not being detected by 'Display / Define' even though both the files are there in /EPS/in ?

Your timely help is highly appreciated.

Thank you.