cancel
Showing results for 
Search instead for 
Did you mean: 

Internal session terminated with a runtime error

Former Member
0 Kudos

Hello Experts,

I am getting some errors while extracting data from R3T to BIT system.

the basis team refresh the R3 system, after that when i execute the process chain it says that "No transfer structure is available for info source in Source System". After refreshing the R3 system again, i have replicate the data source in BIQ system & try to execute the Info package manually but it throws a short dump saying "The current application triggered a termination with a short dump." MESSAGE_TYPE_X

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:
    *** Data request to the OLTP ***

    Long text of error message:

    Technical information about the message:
    Message class....... "RSM"
    Number.............. 000
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "

Also before refreshing the system again, the info package was executable.

kindly advice for the same as soon as possible.

Thanks

Neha

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Issue resolved by executing the program RSSM_OLTP_INIT_DELTA_UPDATE which sync the table in target system.

thanks all for your inputs

Former Member
0 Kudos

hi experts,

After executing these program RSSM_OLTP_INIT_DELTA_UPDATE it show

LOGSYS---------

DATASOUR------

I don't know witch data to pass ..

Regards

rajasekhar

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

For the error you are facing in BW side try the follwing steps

1)replicate the data source

2)goto SE38 and use the program RSDS_TRANSTRU_ACTIVATE_ALL

then again try to repeat the failed process chain

hope this helps

regards

Vilas Kamath

former_member182343
Active Contributor
0 Kudos

HI,

Analise Shot dump using - ST22.

Check for any table space issue or resource problem.

- rvc

Former Member
0 Kudos

Hello,

there is no such kind of issue..i have analyse the dump but not getting anything relevant in the dump

former_member186082
Active Contributor
0 Kudos

Hi Neha,

I guess under "How to correct the error" section in the dump, you will find these messages

   "MESSAGE_TYPE_X" " "

   "SAPLRSSM" bzw. "LRSSMU36"

   "RSSM_OLTPSOURCE_SELECTIONS"

Applying note 852443 will resolve your issue


Regards

Chandu

Former Member
0 Kudos

hi Chandu,

i getting the following message

"MESSAGE_TYPE_X" " "

"SAPLRSS1" or "LRSS1F11"

"RSM1_CHECK_FOR_DELTAUPD"

former_member186082
Active Contributor
0 Kudos

Neha,

Have you tried these steps?

In BW System:

Delete records from tables RSSDLINIT and RSSDLINITSEL for that datasource.

 

In R/3 side

Delete records in tables ROOSPRMSF and ROOSPRMSC for that datasource.

These tables will store the init conditions. If there are any mismatches between these, this issue arises. After deleting these entries, initialization has to be done.

Regards

Chandu

Former Member
0 Kudos

hi Chandu

thanks for the suggestion.

i will try this & let u know in either case.

thanks

neha

Former Member
0 Kudos

Hi ,

Please go through Link .

http://www.ittestpapers.com/blogs/runtime-error-message_type_x-when-opening-an-infopackage-in-sap-bw...

Hope it will help you.

Regards,

Anand Mehrotra.



Former Member
0 Kudos

Hello Neha ,

The dump with error "Mesage_Type_X"  occurs when the system is not able to find a particular value which is required at the  time of processing of a query written in code.

Please go to SE91 trransaction and enter RSM  in message class and 000 as message number .then the message will come.

find the whereused list of the message and see what condition is getting failed.

Also you can directly go through ST22 .see  the dump analysis and  clcik on ABAP Editor.

there you can get so much ingo which caused the dump .

i hope i  might able to help you and you will get benefited by my help.

Vijay Agarwal .

Former Member
0 Kudos

hi Vijay,

Thanks for the prompt response, but this issue is coming while clicking on any of the info package. I also checked with an ABAPer but they also dont get the reason for the failure.

is there anything else that can help

former_member186082
Active Contributor
0 Kudos

Hi Neha,

I guess under "How to correct the error" section in the dump, you will find these messages

   "MESSAGE_TYPE_X" " "

   "SAPLRSSM" bzw. "LRSSMU36"

   "RSSM_OLTPSOURCE_SELECTIONS"

Applying note 852443 will resolve your issue


Regards

Chandu