Dump while Select files - Confirm Target step in MOPZ

Question

Hi All,
I'm getting dump while trying to confirm files in mopz. This is in the step confirm target.
Please see this link, issue exactly what we have but the notes cannot be implemented which is in this link Maintenance Optimizer: "Value loss during allocation"
Kindly have a look on below dump
Category               ABAP Programming Error
Runtime Errors         CONVT_DATA_LOSS
Except.                CX_SY_CONVERSION_DATA_LOSS
ABAP Program           CL_MO_SMP_ADAPTER=============CP
Application Component  SV-SMG-MAI
Date and Time          16.12.2011 00:32:20
     Short text
          Value loss during allocation.
     What happened?
          Error in the ABAP Application Program
          The current ABAP program "CL_MO_SMP_ADAPTER=============CP" had to be
           terminated because it has
          come across a statement that unfortunately cannot be executed.
     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
          An exception occurred that is explained in detail below.
          The exception, which is assigned to class 'CX_SY_CONVERSION_DATA_LOSS', was not
           caught in
          procedure "GET_2ND_CHECK_RESULT" "(METHOD)", nor was it propagated by a RAISING
           clause.
          Since the caller of the procedure could not have anticipated that the
          exception would occur, the current program is terminated.
          The reason for the exception is:
          Value "01200314695000002461|01200314694900013074:01200314694900009502|" was
           allocated in a field which is not long enough.
          Therefore the target field could not store all information of
           "01200314695000002461     01200314694900013074:01200314694900009502     ".
     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:
          "CONVT_DATA_LOSS" "CX_SY_CONVERSION_DATA_LOSS"
          "CL_MO_SMP_ADAPTER=============CP" or "CL_MO_SMP_ADAPTER=============CM00A"
          "GET_2ND_CHECK_RESULT"
          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.
          The exception must either be prevented, caught within proedure
          "GET_2ND_CHECK_RESULT" "(METHOD)", or its possible occurrence must be declared
           in the
          RAISING clause of the procedure.
          To prevent the exception, note the following:
     System environment
          SAP Release..... 702
          SAP Basis Level. 0004
          Application server... "OMEGASOL"
          Network address...... "172.16.1.13"
          Operating system..... "Windows NT"
          Release.............. "6.0"
          Hardware type........ "4x AMD64 Level"
          Character length.... 16 Bits
          Pointer length....... 64 Bits
          Work process number.. 5
          Shortdump setting.... "full"
          Database server... "OMEGASOL"
          Database type..... "DB6"
          Database name..... "OS1"
          Database user ID.. "SAPOS1"
          Terminal.......... "124.123.157.231"
          Char.set.... "C"
          SAP kernel....... 720
          created (date)... "Aug 5 2010 02:21:12"
          create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"
          Database version. "DB6_81 "
          Patch level. 59
          Patch text.. " "
          Database............. "DB6 08.02., DB6 09."
          SAP database version. 720
          Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
           NT 6.0, Windows NT 6.1"
          Memory consumption
          Roll.... 0
          EM...... 33518336
          Heap.... 0
          Page.... 81920
          MM Used. 32855760
          MM Free. 658336
     User and Transaction
          Client.............. 100
          User................ "OS1_USER"
          Language key........ "E"
          Transaction......... " "
          Transaction ID...... "344F27E12581F11B97DA920465FA5E5A"
          EPP Whole Context ID.... "920465FA5E5A1ED189E9DA9C282A77DA"
          EPP Connection ID....... "920465FA5E5A1ED189E9DAF1CA0A37DA"
          EPP Caller Counter...... 1
          Program............. "CL_MO_SMP_ADAPTER=============CP"
          Screen.............. "SAPMHTTP 0010"
          Screen Line......... 2
          Debugger Active..... "none"
     Server-Side Connection Information
          Information on Caller of "HTTP" Connection:
          Plug-in Type.......... "HTTP"
          Caller IP............. "124.123.157.231"
          Caller Port........... 8000
          Universal Resource ID. "/sap/bc/webdynpro/sap/wda_mopz_plan"
          Program............. "CL_MO_SMP_ADAPTER=============CP"
          Screen.............. "SAPMHTTP 0010"
          Screen Line......... 2
          Information on Caller ofr "HTTP" Connection:
          Plug-in Type.......... "HTTP"
          Caller IP............. "124.123.157.231"
          Caller Port........... 8000
          Universal Resource Id. "/sap/bc/webdynpro/sap/wda_mopz_plan"
     Information on where terminated
          Termination occurred in the ABAP program "CL_MO_SMP_ADAPTER=============CP" -
           in "GET_2ND_CHECK_RESULT".
          The main program was "SAPMHTTP ".
          In the source code you have the termination point in line 19
          of the (Include) program "CL_MO_SMP_ADAPTER=============CM00A".
          The termination is caused because exception "CX_SY_CONVERSION_DATA_LOSS"
           occurred in
          procedure "GET_2ND_CHECK_RESULT" "(METHOD)", but it was neither handled locally
           nor declared
          in the RAISING clause of its signature.
          The procedure is in program "CL_MO_SMP_ADAPTER=============CP "; its source
           code begins in line
          1 of the (Include program "CL_MO_SMP_ADAPTER=============CM00A ".
     Source Code Extract
     Line     SourceCde
         1     method GET_2ND_CHECK_RESULT.
         2       DATA ls_buffer TYPE smp_buffer.
         3       CLEAR ev_status.
         4       DATA lv_crm_id TYPE crmt_object_guid.
         5     mo_controller->crm_adapter->get_crm_id(
         6     IMPORTING ev_crm_id = lv_crm_id
         7     ).
         8       SELECT * FROM smp_buffer INTO ls_buffer WHERE crm_id EQ lv_crm_id AND action EQ mopzp_c_ac
         9         ev_status = ls_buffer-action_lock.
        10       ENDSELECT.
        11     
        12       IF ev_status EQ 2.
        13         DATA lt_errors TYPE mopzp_t_errors.
        14     
        15     
        16         IF ls_buffer-data IS NOT INITIAL.
        17           DATA lt_start TYPE mopzp_tt_system_constellation.
        18           DATA lt_target TYPE mopzp_tt_system_constellation.
     >>>>>           call TRANSFORMATION id SOURCE XML ls_buffer-data RESULT system_base = lt_start
        20           system_goal = lt_target
        21           stacklist = et_targets
        22           errors = lt_errors.
        23           et_target_constellation = lt_target.
        24           et_start_constellation = lt_start.
        25           on_errors( lt_errors ).
        26         ENDIF.
        27     
        28         IF ls_buffer-error IS NOT INITIAL.
        29           CLEAR lt_errors.
        30           CALL TRANSFORMATION id SOURCE XML ls_buffer-error
        31           RESULT errors = lt_errors.
        32           on_errors( lt_errors ).
        33         ENDIF.
        34       ELSEIF ev_status EQ 0.
        35         check_target_constellation_asc( ).
        36       ENDIF.
        37     endmethod.
Thanks in advance
Uday

Answer 1

Hi,
yes, upgrade to latest level is a good move to eliminate all possible bugs. Also, you can read my blog on assigning to correct product system in solman 7.1
#sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification  work in SOLMAN7.1
hope it helps,
Cheers,
Nicholas Chang