Hello,
We are currently working on a BW refresh and during the BDLS we get the following dump:
Category ABAP Programming Error
Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED
ABAP Program SAPLRSBK_AFTER_IMPORT
Application Component BW-WHM-DST
Date and Time 10.04.2014 01:47:55
Access via 'NULL' object reference not possible.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLRSBK_AFTER_IMPORT" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component (variable: " ").
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
How to correct the error
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"OBJECTS_OBJREF_NOT_ASSIGNED" " "
"SAPLRSBK_AFTER_IMPORT" or "LRSBK_AFTER_IMPORTF02"
"DTP_CONVERT_AFTER_LS_CHANGE"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP Release..... 702
SAP Basis Level. 0009
Application server... " "
Network address...... " "
Operating system..... "Windows NT"
Release.............. "6.1"
Hardware type........ "2x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... " "
Database type..... "MSSQL"
Database name..... "WV1"
Database user ID.. "wv1"
Terminal.......... " "
Char.set.... "C"
SAP kernel....... 720
created (date)... "May 7 2010 02:47:09"
create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"
Database version. "SQL_Server_9.00 "
Patch level. 46
Patch text.. " "
Database............. "MSSQL 9.00.2047 or higher"
SAP database version. 720
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows NT 6.0, Windows NT 6.1"
Memory consumption
Roll.... 0
EM...... 125693760
Heap.... 0
Page.... 204800
MM Used. 21725312
MM Free. 3409648
User and Transaction
Client.............. 200
User................
Language key........ "E"
Transaction......... "BDLS "
Transaction ID...... "FFFABFE3FA43F128BEA5005056B349F8"
EPP Whole Context ID.... "005056B349F81EE3AFFF1C89DB1E7EA5"
EPP Connection ID....... 00000000000000000000000000000000
EPP Caller Counter...... 0
Program............. "SAPLRSBK_AFTER_IMPORT"
Screen.............. "SAPMSSY0 1000"
Screen Line......... 6
Debugger Active..... "none"
Information on where terminated
Termination occurred in the ABAP program "SAPLRSBK_AFTER_IMPORT" - in
"DTP_CONVERT_AFTER_LS_CHANGE".
The main program was "RBDLSMAP ".
In the source code you have the termination point in line 74
of the (Include) program "LRSBK_AFTER_IMPORTF02".
We found some SAP Notes but they are specific for different SAP versions or SP level.
Any help will be really appreciated.