Skip to Content

Error during upgrade

Hi all,

We are currently upgrading our pre-production system. As per the format in which upgrade is done, we initially upgraded our dev system (had different TRs for SPDD and SPAU phase). Now, when pre-production is being upgraded, we are importing our SPAU TR and we're facing issue there. The error is relating to SNOTE and error is given below:

" Internal error: unable to find data block DESC at position 8.759"


Along with this, I also noticed that when we execute SPAU in our new pre-prod system, the SNOTEs that need to be adjusted are less than those we encountered in SPAU in DEV system.

And our new upgraded dev system was a copy of old dev system. Whereas, our new pre-prod system is a copy of the current production system.

I'm unable to solve the error above.

The upgrade is from ECC 4.6 to ECC 6.0

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Sep 29, 2015 at 06:42 AM

    Hi,

    Could you show expanded transport log, the part preceding the error message (SCWN 021, if I understand correctly)? That might give some idea as to where the error is happening and what is going on.

    You'll have to open OSS incident, I'm afraid. The one and only note related to SCWN 021 I find in OSS is dated 2002: 567362 - Note Assistant: Return code 8 for import postprocessing

    cheers

    Jānis

    Add comment
    10|10000 characters needed characters exceeded

    • The second error looks like a "simple", unrelated generation error - type zip_map_cl needs to be re-transported from the development (if I understand the message correctly 😊) or the user exit implementation needs to be cleaned up (via proper deletion transport from development), if it's not available on the development system anymore.

      For the Note post processing messages I'd open OSS incident (under software component BC-UPG-NA). Note 167795, for example, is not released for customers (anymore). 316773 looks rather old. I don't think the Note post-processing messages will impair functioning of the system. I would not attempt to reset these obsolete notes directly in (pre)production, however... unless SAP advises so.

      cheers

      Jānis

      Message was edited by: Jānis B

  • Sep 29, 2015 at 05:46 AM

    Were some/many transport requests of the old dev never transported in production, maybe you transported some correction in a system where they were not required/not suitable ?

    (Often the new dev is created from production, with exception of versioning refreshed from development)

    Regards,

    Raymond

    Add comment
    10|10000 characters needed characters exceeded

    • I've taken hold quite recently. Possibly there might be a few transport requests that were not transported to production system. However, we are also facing errors in a few programs where the necessary changes have been maintained but they weren't moved to pre-prod system or production system.