Error while opening infopackage

Question

Hi,
I get a short dump when i open infopackage for 2LIS_02_SCLdelta/
MESSAGE_TYPE_X.
Information on where terminated
    Termination occurred in the ABAP program "SAPLRSS1" - in
     "RSM1_CHECK_FOR_DELTAUPD".
    The main program was "RSAWBN_START ".
    In the source code you have the termination point in line 1530
    of the (Include) program "LRSS1F11".
I am not understanding this dumo and that to i am not starting the load but just opening infopackage and getting this dump. Pl help me in resolving this.
Thanks & Regards,
Vijaya

Answer 1

Hi,
We need to make some changes in delta settings.
See this SAP Note providing exact solution. Need to delete some table entries in PRD and BW DEV BOX.
Refer Note # 852443.
Summary
Symptom
If a MESSAGE_TYPE_X runtime error occurs in the LRSSMU36 include program in the SAPLRSSM ABAP program of the RSSM_OLTPSOURCE_SELECTIONS function module, proceed as described in the solution below.
This dump occurs if you try to open an InfoPackage for a DataSource/source system combination for which an initialization terminated incorrectly and a new INIT with overlapping selections was executed without the delta-administration being cleaned up.
The dump can also occur if you import a system copy/backup into only one of the two BW/OLTP systems without first deleting all delta queues for this BW/OLTP combination because the delta administration is always inconsistent. In such cases, contact the SAP consulting department.
A similar dump occurs in
perform "RSM1_CHECK_FOR_DELTAUPD in the LRSS1F11 include if the source system does not recognize any more inits (the roosprmsc and roosprmsf tables are empty) but if there are still entries in the RSSDLINIT/RSSDLINITSEL tables in the BW system.
This is the same as the problem described in Notes 424848 and 591382.
Other terms
Dump, include LRSSMU36, RSSM_OLTPSOURCE_SELECTIONS, MESSAGE_TYPE_X,
Init, delta queue, system copy, backup, initialization, InfoPackage,
RSM1_CHECK_FOR_DELTAUPD, LRSSMU36, LRSS1F11,
RSSDLINIT, RSSDLINITSEL, RSSM_OLTP_INIT_DELTA_UPDATE.
Reason and Prerequisites This problem is caused by a program error.
Solution
You can implement this correction only for load times from an OLTP system because transaction RSA7 is used for the delta administration/deletion.
For a DataMart, you may have to delete using transaction SE16 or a native SQL.
1. The entries for the initialization in the BW system are contained in the RSSDLINIT table for the DataSource/source system combination. Compare these with the entries in the ROOSPRMSC table in the OLTP system.
2. If there are NO entries in the RSSDLINIT table in BW, use transaction RSA7 to delete the delta queue for this DataSource/BW application combination in the source system (OLTP). For a DataMart source system, manually delete the entries in the ROOSPRMSC and ROOSPRMSF tables for your DataSource using transaction SE16 or a native SQL on the database. A DataMart can be identified by the DataSource that starts with '8', and by the fact that you CANNOT find it in RSA7 of the source system.
3. If the RSSDLINIT table in the BW system already contains entries, check the requests listed there in the RNR column in the monitor (transaction RSRQ). Compare these entries with the entries in the ROOSPRMSF and ROOSPRMSC tables with the INITRNR field. If, in the ROOSPRMSF and ROOSPRMSC tables for your DataSource source system combination, there are more entries with different INITRNR numbers, use transaction RSA7 in an OLTP source system to delete all entries and then use the RSSM_OLTP_INIT_DELTA_UPDATE report mentioned in the next section. For a DataMart source system, delete the entries that you cannot find in the RSSDLINIT table using the procedure described above.
4. Read also Notes 591382 and 424848. The errors described there also occur if you delete entries using transaction RSA7 in the source system but there is no RFC connection to the BW system. In the source system, there are no more entries in the ROOSPRMSC and ROOSPRMSF tables, but in the BW system, there are still entries in the RSSDLINIT and RSSDLINITSEL tables. Execute the RSSM_OLTP_INIT_DELTA_UPDATE report and then delete all init selections in the 'Scheduler/Init selections in the source system' menu in the InfoPackage.
5. When you have completed this procedure, you should be able to create a new InfoPackage or open an InfoPackage.
You can then open the InfoPackage again.
Check that there are no more entries in the
'Scheduler'/'Initialization options for source system' menu
If you do find some entries, delete them.
You can then start a new initialization.
If, despite the first incorrect init, you want to be able to create a second init with overlapping selections, which means that this dump will then occur, enter a detailed description of your procedure in a customer message and send it to Development. SAP has never been able to reproduce this behavior, therefore, a great deal of testing and the option to debug in your system would be required.
OR
Note 405943 - Calling an InfoPackage in BW causes short dump
Symptom
Calling an InfoPackage in BW causes a short dump (MESSAGE_TYPE_X).
Other terms
OLTP, DataSource, extractor, data extraction, delta, MESSAGE_TYPE_X
Reason and Prerequisites
The following conditions must be met:
1. The DataSource that is extracted using this InfoPackage must be a delta-capable transaction data DataSource or a master data or text DataSource if there is flexible updating of InfoObjects in BW. Additional prerequisites are listed below (there are several cases in which the dump may occur):
2
Case 1
3. There are several initialization selections for this DataSource.
4. A subset of the initialization selections was deleted before the dump.(Scheduler -> Menu scheduler -> Initialization selections source system)
5. The RSSDLINIT table in BW and the ROOSPRMSC table in the source system display different entries concerning the DataSource in question. More precisely: The RSSDLINIT table contains entries for the DataSource that have no corresponding entry in the ROOSPRSMC.
Case 2.
Alternatively, the problem may occur after a BW 12B upgrade.
Case 3.
Alternatively, the problem may occur if you have copied your OLTP system.
Case 4.
Alternatively, the problem may occur if you have installed a back-up in the OLTP system but not in BW.
Case 5.
Alternatively, the problem may occur if you load master data with flexible updating as a delta requests (0MATERIAL_ATTR, 0VENDOR_ATTR, 0CUSTOMER_ATTR and others).
Solution
You can apply note 0424848 if you are sure that this behavior only occurred because an upgrade was carried out 1.2B to 2.0B or 2.1C (Case 2) and, therefore, the roosprmsc and roosprmsf tables do not contain any entries for their Datasource/source system combination.This will copy the entries from BW into the source system and fill the roosprmsc and roosprmsf tables.
You can also use this solution for case 5 (as a workaround; the final solution is currently in progress).
IMPORTANT: You must only use this program in case 2 or case 5. We recommend that you do not use it in any other case as it may lead to data inconsistencies in BW.
If the problem is caused by individually deleted Delta Inits (Case 1), then implement the following steps according to your source system release:
1. As of 4.0B
Currently the only solution is reinitializing the delta update.To eliminate all inconsistencies, call the transaction RSA7 in your source system and delete the corresponding DataSource's delta queue for the relevant BW system.After that you must request the data again in the DeltaInit mode from BW.
If you no longer have any entries in the delta queue (RSA7) in OLTP, the inconsistencies must be eliminated by SAP BW support service.
The next PI patch contains a correction that no longer deletes all initialization selections in the source system when the deletion of a subset is called in the scheduler.
Alternatively you can import the correction instructions provided in this note into the OLTP.
2. 3.1H and 3.1I
The only way of eliminating the inconsistency is to reinitialize the delta update.In the scheduler menu, delete all the remaining initialization selections and reload data in 'Initialization of delta process' mode with or without the 'Simulation of delta initialization' flag.
If you can no longer access the scheduler because of a dump displaying this problem, ask your system consultant to implement note 419923.
If the problem is caused by a system copy (Case 3):
Ask your system consultant or SAP Support service to clean up the BW delta tables (the consultant can find the names of the tables in Note 419923 mentioned above) because you will have to reinitialize the delta again in all cases.
OR
Execute the FM "RSS1_QUEUE_DELETED_IN_OLTP", by giving OLTP source & logical system.
In RSSDLINIT table in BI entry for this datasourceROOSPRMSC table in OLTP.
Error - RSM1_CHECK_FOR_DELTAUPD
Short Dump when opening Info Package
Delete Initialization request
Hope this helps.
Thanks,
JituK