DTP Short dump issue

Question

Hi Expert,
I face a DTP shortdump issue on loading data from PSA to DSO
The DSO is write optimize.
DTP is using symantic loading and support 3 processor, pack size is default
Situation is as below:
1. This issue occurs every two days. In some situation, it will occur everday
2. The DTP will face short dump. Then when we rerun the DTP, everything goes will
3. Not all the system face this issue (for example, we have dev/qas/prd, this issue cannot be reproduced in qas)
Below is the shortdump point in ST22
   when '3'.
      select single * from rsmonicdp into l_s_monicdp where
             rnr   = l_rnr and
             icube = p_ods and
             dp_nr = i_datapakid.
      if sy-subrc <> 0.
        data: l_s_iccont type rsiccont.
        data: l_s_reqdone    type rsreqdone.
        select single * from rsreqdone into l_s_reqdone where
               rnr = l_rnr.
        if sy-subrc <> 0.
          message x000.
        endif.
        l_s_reqdone-datum = l_s_reqdone-datum + 3.
        if l_s_reqdone-datum < sy-datum.
          select single * from rsiccont into l_s_iccont where
                 rnr   = l_rnr and
                 icube = p_ods.
          if sy-subrc <> 0.
            exit.
          else.
            message x000.
          endif.
        else.
           message x000. (Shortdump here)
        endif.
      endif.
      l_s_monicdp-status     = icon_red_light.
Could you kindly let me know you face simulation issue before and possible solution?
Thanks and best regards
Alex yang

Answer 1

Hi KP,
Thanks for your information.
Please check below information in ST22 side
Error analysis
    Short text of error message:
Status Manager *****
    Long text of error message:
    Technical information about the message:
    Message class....... "RSSTATMAN"
    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" " "
    "CL_RSSM_STATMAN_TARGET_ODSO===CP" or "CL_RSSM_STATMAN_TARGET_ODSO===CM007"
    "IF_RSBK_DATAPACKAGE_OBSERVER~UPDATE_STATUS_TABLES"
BTW, do you think this issue will be related to larger data volum in DSO side?
Thanks and best regards
Alex yang