1000062 SAP OSS Note - 70SP13: Conversion of the logical system name

SAP OSS Note 1000062 version 0004 contains details of a know issue related to 70SP13: Conversion of the logical system name . This includes any associated symptoms and instructions on how to fix it, see below for full details. Also check out the comments section to view/add related contributions, questions or screen shots, based on real life experience of this oss note and problem.

...For more information about the SAP support system known as OSS please check out the SAP OSS NOTES SECTION, whih includes how to download & implement them onto your SAP system using transaction code SNOTE.

Note 1000062 Details:

When does this problem occur

Data transfer processes (DTPs) are not converted correctly. During the
conversion, short dump OBJECTS_OBJREF_NOT_ASSIGNED occurs in program

Description of problem

Transaction BDLS

Cause of the problem and Pre-requisites

This problem is caused by a program error.

Solution instructions

Implement the correction instructions or import 7.00 Support Package 13.
If you use transaction SNOTE to implement the correction instructions,
you must first call transaction SE38 and create an executable report,
'RSBK_REPAIR_BDLS', so that SNOTE can copy the source code of the
correction instructions.

You must always execute report RSBK_REPAIR_BDLS before you execute
transaction BDLS again.
  • SAP NetWeaver 2004s BI

  • Import Support Package 13 for SAP NetWeaver 2004s BI (BI Patch 13 or
    SAPKW70013) into your BI system.

In urgent cases, you can implement the correction instructions.

You must first implement Notes 932065, 935140, 948389, 964580,
969846 and 975510, which provide information about transaction
SNOTE. Otherwise, problems and syntax errors may occur when you
deimplement certain notes.

To provide information in advance, the notes mentioned above may already
be available before the Support Package is released. In this case, the
short text of the note still contains the words "Preliminary version".

Before you implement an advance correction (if one exists and you want
to implement it), see Note 875986. It contains notes regarding the SAP
Note Assistant. These notes prevent problems during the implementation.

Solution instructions

Please import the corrections attached to this OSS note into your SAP system using SNOTE.

You can also view the full details of this OSS note and download it to your SAP system ready for implementation using transaction code SNOTE. Once it has been downloaded you can read the full details, check out any installation instructions including manual changes and see if there are any pre-requisites.

You can also check if a new version of note 1000062 has been released as well as see if the note is valid for your current SAP system landscape.

Check if SAP OSS note 1000062 has already been downloaded and is valid

To check if this note has already been download, what status it has and if it is valid for your system first execute t-code SNOTE and click on the SAP Note Browser icon
Icon used to execute SAP Note Browser report within SNOTE

From here you can just enter the note number 1000062 and press execute. If the note already exists it's details will be displayed. See here for full step by step instructions on how to check if an SAP note has been downloaded and is valid for your system.

If note 1000062 does not exist on your system you will receive the message "Unable to find SAP Note that meets specified criteria"
Icon used to execute SAP Note Browser report within SNOTE

If this is the case you will need to download the note to you SAP system also using transaction SNOTE. For further details see Download note using SNOTE. Even if it does exist you may still want to check if you have downloaded the latest version of the note.

Alternatively you can find full details of this note on the SAP service market place(SNumber / Service market place login will be required)