Quantcast
Channel: SCN : All Content - All Communities
Viewing all articles
Browse latest Browse all 3208

Short dump due to update routine

$
0
0

Hello friends,

 

I migtrated the datasource 0BPARTNER_ATTR and also used the proposed transformations whcih have update routine and start routines. When checked , there are no errors.

 

I am getting short dump when I run DTP for 0BPARTNER. It is showing the following error:

 

Please help me for any code changes

 

GETWA_NOT_ASSIGNED 

Error analysis                                                   

    You attempted to access an unassigned field symbol           

    (data segment 32772).                                                                               

This error may occur if                                      

    - You address a typed field symbol before it has been set with

      ASSIGN                                                     

    - You address a field symbol that pointed to the line of an  

      internal table that was deleted                            

    - You address a field symbol that was previously reset using 

      UNASSIGN or that pointed to a local field that no          

      longer exists                                              

    - You address a global function interface, although the      

      respective function module is not active - that is, is     

      not in the list of active calls. The list of active calls  

      can be taken from this short dump.        "         

 

Here is the parts of ABAP code in update routine:

 

// code within  CLASS lcl_transform IMPLEMENTATION.

 

  • Migrated update rule call

  Perform routine_0002

  CHANGING

    RESULT

    l_subrc

    l_abort.

 

// code within CLASS lcl_transform DEFINITION.

 

 

FORM routine_0002

  CHANGING

    RESULT         TYPE tys_TG_1_full-BP_CONS

    RETURNCODE     LIKE sy-subrc

    ABORT          LIKE sy-subrc

  RAISING

    cx_sy_arithmetic_error

    cx_sy_conversion_error.

 

  • init variables

 

  • fill the internal table "MONITOR", to make monitor entries

 

  FIELD-SYMBOLS:

    <fs_key> TYPE char10.

 

  DATA:

    lv_key TYPE char100.

 

  CONCATENATE 'COMM_STRUCTURE-'

              gv_bpartner_fieldnm

              INTO lv_key.

  ASSIGN (lv_key) TO <fs_key>.

 

----- Find entry for partner -


  CLEAR gs_bpartner.

  READ TABLE gt_bpartner

       INTO gs_bpartner

       WITH KEY bpartner = <fs_key>

       BINARY SEARCH.

 

----- No BP_CONS found -


----- (a) because there is no entry in gt_bpartner -


----- (b) because field bp_cons is initial -


  IF gs_bpartner-bp_cons IS INITIAL.

    RESULT = <fs_key>.

  ELSE.

    RESULT = gs_bpartner-bp_cons.

  ENDIF.

 

  • if the returncode is not equal zero, the result will not be updated

  RETURNCODE = 0.

  • if abort is not equal zero, the update process will be canceled

  ABORT = 0.

 

 

ENDFORM.                    "routine_0002

 

 

Thanks,

VNM


Viewing all articles
Browse latest Browse all 3208

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>