Error while starting data loading on InfoPackage

Question

Hi everybody,
I'm new at SAP BW and I'm working in the "Step-By-Step: From Data Model to the BI Application in the web" document from SAP.
I'm having a problem at the (Chapter 9 in the item c - Starting Data Load Immediately).
If anyone can help me:
Thanks,
Thiago
Below are the copy of the error from my SAP GUI.
<><><><><><><><><><<><><><><><><><><><><><><><><><><><><><><><>
Runtime Errors         MESSAGE_TYPE_X
Date and Time          19.01.2009 14:41:22
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
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
Short text of error message:
Batch - Manager for BW Processes ***********
Long text of error message:
Technical information about the message:
Message class....... "RSBATCH"
Number.............. 000
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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:
"MESSAGE_TYPE_X" " "
"SAPLRSBATCH" or "LRSBATCHU01"
"RSBATCH_START_PROCESS"
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 701
Application server... "sun"
Network address...... "174.16.5.194"
Operating system..... "Windows NT"
Release.............. "5.1"
Hardware type........ "2x Intel 801586"
Character length.... 8 Bits
Pointer length....... 32 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "localhost"
Database type..... "ADABAS D"
Database name..... "NSP"
Database user ID.. "SAPNSP"
Terminal.......... "sun"
Char.set.... "English_United State"
SAP kernel....... 701
created (date)... "Jul 16 2008 23:09:09"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQLDBC 7.6.4.014 CL 188347 "
Patch level. 7
Patch text.. " "
Database............. "MaxDB 7.6, MaxDB 7.7"
SAP database version. 701
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 8112
EM...... 11498256
Heap.... 0
Page.... 65536
MM Used. 6229800
MM Free. 1085264
User and Transaction
Client.............. 001
User................ "THIAGO"
Language key........ "E"
Transaction......... "RSA1 "
Transactions ID..... "CD47E6DDD55EF199B4E6001B782D539C"
Program............. "SAPLRSBATCH"
Screen.............. "SAPLRSS1 2500"
Screen line......... 7
Information on where terminated
Termination occurred in the ABAP program "SAPLRSBATCH" - in
"RSBATCH_START_PROCESS".
The main program was "RSAWBN_START ".
In the source code you have the termination point in line 340
of the (Include) program "LRSBATCHU01".
Source Code Extract
Line
SourceCde
310
endif.
311
l_lnr_callstack = l_lnr_callstack - 1.
312
endloop.      " at l_t_callstack
313
endif.
314
315
*---- Eintrag für RSBATCHHEADER -
316
l_s_rsbatchheader-batch_id    = i_batch_id.
317
call function 'GET_JOB_RUNTIME_INFO'
318
importing
319
jobcount        = l_s_rsbatchheader-jobcount
320
jobname         = l_s_rsbatchheader-jobname
321
exceptions
322
no_runtime_info = 1
323
others          = 2.
324
call function 'TH_SERVER_LIST'
325
tables
326
list           = l_t_server
327
exceptions
328
no_server_list = 1
329
others         = 2.
330
data: l_myname type msname2.
331
call 'C_SAPGPARAM' id 'NAME'  field 'rdisp/myname'
332
id 'VALUE' field l_myname.
333
read table l_t_server with key
334
name = l_myname.
335
if sy-subrc = 0.
336
l_s_rsbatchheader-host   = l_t_server-host.
337
l_s_rsbatchheader-server = l_myname.
338
refresh l_t_server.
339
else.
>>>>>
message x000.
341
endif.
342
data: l_wp_index type i.
343
call function 'TH_GET_OWN_WP_NO'
344
importing
345
subrc    = l_subrc
346
wp_index = l_wp_index
347
wp_pid   = l_s_rsbatchheader-wp_pid.
348
if l_subrc <> 0.
349
message x000.
350
endif.
351
l_s_rsbatchheader-wp_no           = l_wp_index.
352
l_s_rsbatchheader-ts_start        = l_tstamps.
353
l_s_rsbatchheader-uname           = sy-uname.
354
l_s_rsbatchheader-module_name     = l_module_name.
355
l_s_rsbatchheader-module_type     = l_module_type.
356
l_s_rsbatchheader-pc_variant      = i_pc_variant.
357
l_s_rsbatchheader-pc_instance     = i_pc_instance.
358
l_s_rsbatchheader-pc_logid        = i_pc_logid.
359
l_s_rsbatchheader-pc_callback     = i_pc_callback_at_end.

Answer 1

Hi,
i am also getting related this issue kindly see this below short dump description.
Short text
    The current application triggered a termination with a short dump.
What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
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
    Short text of error message:
    Variant RSPROCESS0000000000705 does not exist
    Long text of error message:
     Diagnosis
         You selected variant 00000000705 for program RSPROCESS.
         This variant does not exist.
     System Response
     Procedure
         Correct the entry.
    Technical information about the message:
    Message class....... "DB"
Number.............. 612
    Variable 1.......... "&0000000000705"
    Variable 2.......... "RSPROCESS"
    Variable 3.......... " "
    Variable 4.......... " "
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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:
"MESSAGE_TYPE_X" " "
"SAPLRSPC_BACKEND" or "LRSPC_BACKENDU05"
"RSPC_PROCESS_FINISH"
    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 701
    Application server... "CMCBIPRD"
    Network address...... "192.168.50.12"
    Operating system..... "Windows NT"
Release.............. "6.1"
    Hardware type........ "16x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "CMCBIPRD"
    Database type..... "MSSQL"
    Database name..... "BIP"
    Database user ID.. "bip"
    Terminal.......... "CMCBIPRD"
  Char.set.... "C"
  SAP kernel....... 701
  created (date)... "Sep 9 2012 23:43:54"
  create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"
  Database version. "SQL_Server_8.00 "
  Patch level. 196
  Patch text.. " "
Database............. "MSSQL 9.00.2047 or higher"
  SAP database version. 701
  Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
   NT 6.0, Windows NT 6.1, Windows NT 6.2"
  Memory consumption
  Roll.... 16192
  EM...... 4189840
  Heap.... 0
  Page.... 16384
  MM Used. 2143680
  MM Free. 2043536
User and Transaction
Client.............. 001
User................ "BWREMOTE"
    Language Key........ "E"
Transaction......... " "
    Transactions ID..... "9C109BE2C9FBF18BBD4BE61F13CE9693"
Program............. "SAPLRSPC_BACKEND"
Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
System.............. "BIP"
    Database Release.... 701
    Kernel Release...... 701
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "asynchron without reply and transactional (emode 0, imode
     0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
Information on where terminated
    Termination occurred in the ABAP program "SAPLRSPC_BACKEND" - in
"RSPC_PROCESS_FINISH".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 75
    of the (Include) program "LRSPC_BACKENDU05".
Source Code Extract
Line  SourceCde
   45         l_t_info        TYPE rs_t_rscedst,
   46         l_s_info        TYPE rscedst,
   47         l_s_mon         TYPE rsmonpc,
   48         l_synchronous   TYPE rs_bool,
   49         l_sync_debug    TYPE rs_bool,
   50         l_eventp        TYPE btcevtparm,
   51         l_eventno       TYPE rspc_eventno,
   52         l_t_recipients  TYPE rsra_t_recipient,
52 l_t_recipients  TYPE rsra_t_recipient,
53         l_s_recipients  TYPE rsra_s_recipient,
54         l_sms           TYPE rs_bool,
55         l_t_text        TYPE rspc_t_text.
56
57   IF i_dump_at_error = rs_c_true.
58 * ==== Dump at error? => Recursive Call catching errors ====
59     CALL FUNCTION 'RSPC_PROCESS_FINISH'
60       EXPORTING
61         i_logid       = i_logid
62         i_chain       = i_chain
63         i_type        = i_type
64         i_variant     = i_variant
65         i_instance    = i_instance
66         i_state       = i_state
67         i_eventno     = i_eventno
68         i_hold        = i_hold
69         i_job_count   = i_job_count
70         i_batchdate   = i_batchdate
71         i_batchtime   = i_batchtime
72       EXCEPTIONS
73         error_message = 1.
74     IF sy-subrc <> 0.
>>> MESSAGE ID sy-msgid TYPE 'X' NUMBER sy-msgno
76               WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
77     ELSE.
78       EXIT.
79     ENDIF.
80   ENDIF.
81 * ==== Cleanup ====
82   COMMIT WORK.
83 * ==== Get Chain ====
84   IF i_chain IS INITIAL.
85     SELECT SINGLE chain_id FROM rspclogchain INTO l_chain
86            WHERE log_id = i_logid.
87   ELSE.
88     l_chain = i_chain.
89   ENDIF.
90 * ==== Lock ====
91 * ---- Lock process ----
92   DO.
93     CALL FUNCTION 'ENQUEUE_ERSPCPROCESS'
94       EXPORTING
If we do this
Use table RSSDLINIT and in OLTPSOURCRE: enter the name of the data  source
And in the logsys enter the name of the source system and delete the entry for that info package. what will happen is process chain will run suceesfully and short dump will not come or what kindly give the detail explanation about this RSSDLINIT.
Regards,
poluru