Process Chain fails - ABAP dump

Question

Hi Everyone,
Some of the process chains in our system keep failing at random intervals and end with an ABAP dump (MESSAGE_TYPE_X). The short text error message in the log says: 'The current application triggered a termination with a short dump'.
Long Text:
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).
Code Extract:
  14   select single * from rsmdatastate  bypassing buffer
  15                   into l_s_datastate
  16                   where infocube = i_infocube.
  17   if sy-subrc ne 0.
  18     message x051(rsar) with 'infocube_not_found' i_infoc
  19     raise infocube_not_found.
  20   endif.
  21
  22 * nur weitere Tests, falls Request kleiner als qualok
  23   if i_rnsid <= l_s_datastate-qualok.
>>>>     message x051(rsar) with 'sid_too_low' i_rnsid
  25                             l_s_datastate-qualok.
  26   else.
  27
  28     if   i_rnsid <= l_s_datastate-compr
  29       or i_rnsid <= l_s_datastate-rollup_rsvd_dual
  30       or i_rnsid <= l_s_datastate-dmall.
  31
  32       message x051(rsar) with i_rnsid
  33                               l_s_datastate-compr
  34                               l_s_datastate-rollup_rsvd_
  35                               l_s_datastate-dmall.
  36       raise write_not_allowed.
  37
  38     elseif l_s_datastate-rollup_rsvd_dual = 0.
  39 *   es sind noch keine Aggregate vorhanden
  40 *   check, ob ein Aggregat gefüllt wird
We have been getting this error in different PCs with no specific pattern. When I re-generate the program and repeat the process chain, it executes successfully.
What could be the cause of this repeated failure?
Thanks,
Ram

Answer 1

To recognize this error early on, the attached corrections check whether the references are correct. If they are not, the following termination occurs:
"System error in program SAPLRRSI and form INITIALIZE-1- (see long text)".
The content version of the characteristic 0REQUEST is usually correct. You can see this in transaction RSD5 (dropdown content). If this is the case, you can transfer the InfoObject from the content again:
Transaction RSOR -> BI Content -> Object Types -> under InfoObjects select 0REQUEST and transfer it to the right (note the following settings: "Only Necessary Objects"; collection mode: "Collect Automatically").