"Assertion failed" error in Transfer rule routine

Question

Hello Experts,
I am new to BW. I am writing small abap routine in Transformation.
  IMPORTING
    request     type rsrequest
    datapackid  type rsdatapid
    SOURCE_FIELDS-DIVISION TYPE /BI0/OIDIVISION
    SOURCE_FIELDS-/BIC/ZDIVNAME TYPE /BIC/OIZDIVNAME
   EXPORTING
     RESULT type tys_TG_1-/BIC/ZDIVNAME
     Data: wa_Division type /BI0/TDIVISION.
     select single * fROm /BI0/TDIVISION into wa_division where DIVISION
     = SOURCE_FIELDS-DIVISION.
     IF SY-SUBRC = 0.
     RESULT = WA_DIVISION-TXTSH.
     ENDIF.
My aim here is that I have a Division Infoobject and I want to get its text(name) from text table /BI0/TDIVISION but this code doesnot work.
Any suggestions!!
Regards,
DNP

Answer 1

Hi Jerry,
Please find below the details of dump. Thankyou very much for your help.
Short text
    The ASSERT condition was violated.
What happened?
    In the running application program, the ASSERT statement recognized a
    situation that should not have occurred.
    The runtime error was triggered for one of these reasons:
    - For the checkpoint group specified with the ASSERT statement, the
      activation mode is set to "abort".
    - Via a system variant, the activation mode is globally set to "abort"
      for checkpoint groups in this system.
    - The activation mode is set to "abort" on program level.
    - The ASSERT statement is not assigned to any checkpoint group.
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
    The following checkpoint group was used: "No checkpoint group specified"
    If in the ASSERT statement the addition FIELDS was used, you can find
    the content of the first 8 specified fields in the following overview:
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
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:
    "ASSERTION_FAILED" " "
    "CL_RSTRAN_GEN=================CP" or "CL_RSTRAN_GEN=================CM00H"
    "GET_SOURCE_PARAMETER"
    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.
User and Transaction
    Client.............. 001
    User................ "USNDIPA"
    Language key........ "E"
    Transaction......... "RSA1 "
    Transactions ID..... "498AF810CE1C0214E10080000AF00ED9"
    Program............. "CL_RSTRAN_GEN=================CP"
    Screen.............. "SAPLSPO4 0300"
    Screen line......... 19
Information on where terminated
    Termination occurred in the ABAP program "CL_RSTRAN_GEN=================CP" -
     in "GET_SOURCE_PARAMETER".
    The main program was "RSAWBN_START ".
    In the source code you have the termination point in line 39
    of the (Include) program "CL_RSTRAN_GEN=================CM00H".
Source Code Extract
Line  SourceCde
    9     lr_rule           TYPE REF TO cl_rstran_trfn_rule,
   10     l_posit_source_ex TYPE rsposit,
   11     l_seg_source      TYPE rstran_segid.
   12
   13
   14   lr_rule = i_r_rule->get_model_rule( ).
   15 *-- GET POSIT pointer to segment field of source.
   16   CALL METHOD lr_rule->get_posit_ext
   17     EXPORTING
   18       i_paramtype = cl_rstran_stat=>paramtype_importing
   19       i_ruleposit = i_posit
   20       i_rulesegid = i_segid
   21     IMPORTING
   22       e_segid     = l_seg_source
   23       e_posit     = l_posit_source_ex.
   24
   25   ASSERT l_seg_source = i_segid.
   26
   27 *-- Get component name from seg
   28   READ TABLE i_t_segment_m ASSIGNING <ls_s_seg>
   29     WITH KEY segid = i_segid.
   30   ASSERT sy-subrc = 0.
   31
   32 *-- Get field name from source field with extern posit.
   33   READ TABLE i_t_seg_source ASSIGNING <ls_s_seg_source>
   34     WITH KEY segid = i_segid.
   35   ASSERT sy-subrc = 0.
   36   IF sy-subrc = 0.
   37     READ TABLE <ls_s_seg_source>-t_field ASSIGNING <ls_s_field>
   38       WITH KEY position = l_posit_source_ex.
>>>>>     ASSERT sy-subrc = 0.
   40   ENDIF.
   41
   42 *--  r_s_parameter-param_id has to be set out side due to type inheritance of RuleStepMappin
   43
   44   CONCATENATE '<' <ls_s_seg>-y__nm '>' INTO
   45   c_s_connector-s__nm.
   46   c_s_connector-f__nm = <ls_s_field>-fieldname.
   47
   48 ENDMETHOD.
Regards,
DNP