Short dump OBJECTS_OBJREF_NOT_ASSIGNED

Hi All,
I have a BSP application where the Application class has several attributes TYPE REF TO other classes.   In production we are getting hundreds of OBJECTS_OBJREF_NOT_ASSIGNED short dumps a day.  The references to these TYPE REF TO attributes on the application class are being lost.  
Initially we were not able to reproduce the problem in development, however I have found that if you stay on a page for 10-15 minutes then navigate to another page the references are lost and the short dump occurs.  I can see in the short dump that the reference to the Application object still exists but not to the TYPE REF TO attributes which are now all ???.  If you navigate without waiting everything is fine.
I thought it might be the garbage collector cleaning them up, however at the time the page is displayed all the references are valid.  Why do they disappear?  Is there a time-out parameter somewhere?
Thanks in advance.
Sandra Lawrence

Thanks for all your replies.  I realise now that I am getting a session time-out.  As I still had some data remaining I originally didn't think this was my problem.
I am now in the process of implementing Thomas Jung's timeout solution from his blog BSP Developer's Journal: Part XV - Stateful BSP and Timeouts.
Thanks again for pointing me in the right direction.

Similar Messages

  • Short dump OBJECTS_OBJREF_NOT_ASSIGNED when activating infoobjects

    Hi Experts,
    We are  getting a short dump when activating bussiness content infoobject which contain attributes, for e.g. 0COSTCENTER.
    We are not getting the same dump when activating infoobjects whith out attributes.
    We found a note 1019055 that recomends install sp13 or install six or seven notes for an emergency issue.
    The problem is that if we install sp13 we will get out of stack.
    What is your recomendation in this case? we are afraid that the problems will continue until we don't implement the sp13.
    Thanks!

    use t-code SNOTE to implement the OSS note you mentioned ,if it doesnt work you can always revert back to old status by doing Reset.
    Hope it Helps
    Chetan
    @CP..

  • Short Dump in RDDEXECL with OBJECTS_OBJREF_NOT_ASSIGNED on import

    Hello,
    I am currently having problems importing a transport to our production environment as I get the above error on import. It successfully imported to the text environment though, both systems are BI 7 SP14.
    The error analysis in the short dump is as follows:-
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
    caught in
    procedure "CHECK_ME" "(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:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: "L_R_RULE").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
    The transport contains Transformations and DTP's which I think may be the cause of the problem, but since I have a large number of transports ready to import after this one, it is difficult to go back and retry the transport without certain objects.
    I can find nothing relating to this on SAP notes.
    Any advice would be much appreciated...
    Regards,
    Mark.

    Hi Mark,
    you should implement the note 1094978.
    This note is a collection note with notes which correct most errors concerning Transformation.
    This should solve the issue.
    Regards,
    Srikanth

  • BCS Release Request Short dump

    Hello,
    I'm trying to release my costumizing request, that contains the SEM-BCS configuration, although i'm getting a short-dump.
    The description is as follows:
    Short text
        Access via 'NULL' object reference not possible.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "CL_UG_MD_TR_METHOD_EXPORT=====CP" had to be
         terminated because it has
        come across a statement that unfortunately cannot be executed.
    Error analysis
        You attempted to use a 'NULL' object reference (points to 'nothing')
        access a component (variable: " ").
        An object reference must point to an object (an instance of a class)
        before it can be used to access components.
        Either the reference was never set or it was set to 'NULL' using the
        CLEAR statement.
    How to correct the error
        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:
        "OBJECTS_OBJREF_NOT_ASSIGNED" " "
        "CL_UG_MD_TR_METHOD_EXPORT=====CP" or "CL_UG_MD_TR_METHOD_EXPORT=====CM003"
        "UGMD_EXTRACT_SID_2"
    Information on where terminated
        Termination occurred in the ABAP program "CL_UG_MD_TR_METHOD_EXPORT=====CP" -
         in "UGMD_EXTRACT_SID_2".
        The main program was "RDDM0001 ".
        In the source code you have the termination point in line 62
        of the (Include) program "CL_UG_MD_TR_METHOD_EXPORT=====CM003".
    Source Code Extract
    Line  SourceCde
       32   FIELD-SYMBOLS <lt_table> TYPE INDEX TABLE.
       33   FIELD-SYMBOLS <ld_fsid> TYPE ug_sid.
       34   FIELD-SYMBOLS <ld_vsid> TYPE ug_sid.
       35 *  FIELD-SYMBOLS <lt_target> TYPE ANY TABLE.
       36
       37   ASSIGN io_itab->rd_wa->* TO <ls_wa>.
       38   IF i_value_sid IS NOT INITIAL.
       39     ASSIGN COMPONENT i_value_sid
       40            OF STRUCTURE <ls_wa>
       41            TO <ld_vsid>.
       42     CHECK sy-subrc = 0.
       43   ELSE.
       44     CREATE DATA lr_sid.
       45     ASSIGN lr_sid->* TO <ld_vsid>.
       46     CLEAR <ld_vsid>.
       47   ENDIF.
       48
       49   IF NOT i_fieldname_sid IS INITIAL.                  "Start hah160603.1
       50     ASSIGN COMPONENT i_fieldname_sid
       51            OF STRUCTURE <ls_wa>
       52            TO <ld_fsid>.
       53     CHECK sy-subrc = 0.
       54   ELSE.
       55     CALL METHOD ugmd_get_fieldname_to_table
       56       EXPORTING
       57         i_tabname = i_datainfo-tabname
       58       IMPORTING
       59         e_fieldname = ld_fieldname.
       60     lo_fieldname = cl_ug_md_fieldname=>if_ug_md_fieldname~get_instance(
       61       ld_fieldname ).
       62  >>>>>     ld_fieldname_sid_fix = lo_fieldname->ds_data-sid.
       63     ASSIGN ld_fieldname_sid_fix TO <ld_fsid>.
       64   ENDIF.                                                "End hah160603.1
       65
    Contents of system fields
    Name     Val.
    SY-SUBRC 0
    SY-INDEX 1
    SY-TABIX 0
    SY-DBCNT 0
    SY-FDPOS 0
    SY-LSIND 1
    SY-PAGNO 0
    SY-LINNO 1
    SY-COLNO 1
    SY-PFKEY TDR_FULL
    SY-UCOMM REFR
    SY-TITLE Transport organizer: ordens
    SY-MSGTY I
    SY-MSGID FINB_TR
    SY-MSGNO 009
    SY-MSGV1 &
    SY-MSGV2 &
    SY-MSGV3
    SY-MSGV4
    SY-MODNO 0
    SY-DATUM 20080904
    SY-UZEIT 200112
    SY-XPROG SAPLSYST
    SY-XFORM SYSTEM_HOOK_OPEN_DATASET
    If someone have gone trough a similar experience, or have any tip of how to solve this issue, i'd apreciate a comment.
    Will award points for valuable help.
    Thank you

    Hi Ricardo,
    You tried to transport the BCS' configuration, right?
    If in the request was the full set of settings from the start of the project, the it will definitely fail.
    There are some restrictions in BCS transport. See, for example the OSS Note #627924 - 'Restrictions with transport in BW-based SEM-BCS'. It particularly says:
    "For the initial system setup, and after substantial changes in the data model, you should transport the Customizing by means of manually created transport requests. We advise you not to use the automatic recording of all Customizing settings during the first implementation phase in the development system and not to use this request for the structure of the test and productive systems.
    During the transport of a new consolidation area, the following settings should be transported in the following sequence:
    1. Data basis
    2. Consolidation area
    3. Special versions
    After the import of the data basis and the consolidation area, these settings should be checked in the target system. In particular, the RFC destination, the InfoCubes and ODS objects, as well as the InfoObjects. Note that RFC destinations, InfoCubes, ODS objects, virtual cubes and InfoObjects cannot be transported from the consolidation workbench with the transport functions. For instance, you have to transport and activate the InfoCubes and InfoObjects using the BW."
    I usually transport the BCS setting in a little transport requests in this order:
    - all BW objects and settings
    - data basis (with source DB)
    - cons area
    - special versions
    - versions
    - master data
    ...etc.
    Hope this helps.

  • Short dump while creating a new status report in webdynpro cprojects

    Short dump details are
    Runtime Errors       OBJECTS_OBJREF_NOT_ASSIGNED
    Exception              CX_SY_REF_IS_INITIAL
    Access via 'NULL' object reference not possible.     
    GET_AVAIL_CALID" "(METHOD)",  of the class CL_DPR_BUPA_DISTRIBUTION failed to capture the Business partner details.
    The dump analysis shows
    You attempted to use a 'NULL' object reference (points to 'nothing') access a component  variable: "LR_BUPA_LINK").                                                       
        An object reference must point to an object (an instance of a class)     before it can be used to access components.                      
        Either the reference was never set or it was set to 'NULL' using the                         
        CLEAR statement.       
    Can anyone throw some light on this?

    Hello Srikanth,
    I have no issues in trying to help someone as polite as you! It is very nice to have questions answered in an intelligible manner - not unfortunately always the case.
    Without being able to debug on your system it is quite difficult to say what might be causing this error - especially as you say this was working in a different system.
    I'm sure you've already tried eliminating differences in your authorisations between the two systems? Are you registered as a developer in the new system?
    Sorry I'm now just guessing as I've not come across the error myself - hopefully now that we have clearly documented the issue, someone else might be able to shed some light on what might cause it!
    Chris

  • Short Dump Error While Data load

    Hi Experts,
    Data load to an ODS in production server has been failed because of Short dump error. The error message shows " OBJECTS_OBJREF_NOT_ASSIGNED ".
    Request you to please help me out with a solution ..
    Regards,
    Vijay

    Hi Vijay,
    follow the steps below (May Help you)
    Goto Monitor screen>Status Tab> using the wizard or the menu path >Environment -> Short dump> In the warehouse
    Select the Error and double click
    Analyse the error from the message.
    1.-->Go to Monitor
    -->Transactional RFC
    -->In the Warehouse
    -->Execute
    -->EDIT
    -->Execute LUW
    Refresh the Transactional RFC screen and go to the Data Target(s) which have failed and see the status of the Request-->Now it should be green.
    2.In some cases the above process will not work (where the Bad requests still exists after the above procedure).
    In that case we need to go to the Data Targets and need to delete the bad requests and do the update again
    Regards,
    BH

  • Short dumps in Web Dynpro

    Hi Experts,
    Problem is:
    We created an interactive form with web dynpro abap for one of our client and integrated it into portal sytem. We tested in our development system and it was working fine.
    After go live we started getting following short dumps in the production system which we never got in our development system.
    For some of the users it is working fine. Where as for some users following short dumps are coming. Is it some thing to do with adobe version the user has or any basis settings? Please suggest me.
    Some users getting this error:
    u201C$$$/com/adobe/document/xmlform/msg.XFA=Invalid version: The current version of the XFA template model exceeds the capability of Acrobat / Adobe Reader 7.0.5.u201D
    1. ASSERTION_FAILED exception in method IF_WDR_UPDATE_SERVER_PEER_DATA~CLOSE_WINDOW of class CL_WDR_CLIENT_APPLICATION.
    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) "
    2. CX_WDR_RT_EXCEPTION exception in method ADD_VIEW_CONTROLLER of class CL_WDR_COMPONENT.
    Error Analaysis:
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_WDR_RT_EXCEPTION', was not caught
    and
    therefore caused a runtime error.
    The reason for the exception is:
    Instance of the view WND_EXTENDED_OPTIONS already exists in component
    3. OBJECTS_OBJREF_NOT_ASSIGNED exception in method IF_WDR_ADAPTER_EVENT_HANDLER~HANDLE_EVENT of CL_WDR_CONTEXT_MENU_HANDLER class
    Error Analysis:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: " ").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
    Error in the ABAP Application Program
    The current ABAP program "CL_WDR_CONTEXT_MENU_HANDLER===CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    Please let me know what can be the issue and how to fix this at the earliest.
    Thanks a lot in advance,
    Regards,
    Phani.

    Hi Shankar,
    The NULL object ref error occurs when you try to use an object reference that has not been created.
    For example : if you want to bind data to a node and write code some like this
    lo_nd_table->bind_table( lt_table ).
    if there is no instance of lo_nd_table availabe at this time the program will dump. to avoid this you can code some like this
    if not lo_nd_table is initial.
      lo_nd_table->bind_table( lt_table ).
    endif.
    just check ue code to see if any access is made to an obj ref which is not yet created. put a break point in ur code and debug to see where exactly it fails.
    Thanks,
    Abhishek

  • ABAP DUMP - OBJECTS_OBJREF_NOT_ASSIGNED

    Hi Experts
    We are facing the dump  OBJECTS_OBJREF_NOT_ASSIGNED very regularly in ST22.
    Error Details
    Short text
         Access via 'NULL' object reference not possible.
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "CL_CRM_BSP_FRAME_SRES=========CP" had to be
          terminated because it has
         come across a statement that unfortunately cannot be executed.
    please letme Know why this dump is comming reguraly and what action to be taken to aviod such dumps
    Thanks
    kumar

    Hi,
    What does this applicaiton do? Is it anywhere linked to Transactions in CRM.
    We faced similar Dump in CRM SAPGUI. and that was when we entered the Tcode: CRMD_ORDER.
    Just try the same with another User ID. If the dump doesnot occur then follow the procedure below:
    Tcode: SU01
    Open the User for which teh dump is coming.
    Goto Parameters tab
    Enter follwoing:
    Parameter ID: CRM_PROCESS_TYPE
    Parameter Value: TA
    SAVE.
    This should resolve,
    Kindly reward with points in case helpful
    Sharif.

  • Short Dump Applicant Infotype

    Dear All,
    we have to create a client infotype for an applicant implementation.
    We create succesfully the infotype in transaction PM01.
    The problem is that when we want to test the new infotype in PB30, the system show us a short dump:
    The current ABAP program "SAPFP50P" had to be terminated because it has....
    OBJECTS_OBJREF_NOT_ASSIGNED
    CX_SY_REF_IS_INITIAL
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL'
    (variable: "INFOTYPE_CHECK").
    Can you please tell me which is the solution? We are not sure if we need any adittional add-on in the system to customize RC module.
    Many thanks in advance,
    Laura

    Hello Laura
    Check the following steps correctly to create a HR Infotype:
    1) Go to Transaction PM01.
    2) Enter the custom Infotype number which you want to create (Should be a 4 digit number, start with 9).
    3) Select the 'Employee Infotype' radio button.
    4) Select the 'PS Structure Infotype'.
    5) Click on Create... A separate table maintenance window appears...
    6) Create a PS structure with all the fields you want on the Infotype
    7) Save and Activate the PS structure
    8) Go back to the initial screen of PM01.
    9) Click on 'All' push button. It takes a few moments.
    10) Click on 'Technical Characteristics'. Infotype list screen appears
    11) Click on 'Change'(pencil) button
    12) Select your Infotype and click on 'Detail' (magnifying glass) button
    13) Give 'T591A' as subtype table
    14) Give 'T591S' as subtype txt tab
    15) Give your subtype field as subtype field
    16) Save and come back to PM01 initial screen
    17) Click on 'Infotype Characteristics' ... Infotype list screen appears
    18) Click on 'Change' (pencil) button
    19) Click on 'New Entries'
    20) Enter your Infotype number and short text
    21) Here we have to set different Infotype Characteristics as per the requirement. (Better open another session with some standard Infotype's infotype characteristics screen and use as the reference to fill yours)
    22) Save your entries.
    23) Now the Infotype is created and ready to use.
    24) If you want to change the layout of the Infotype as per your requirement...
    25) In the PM01 initial screen...Select 'Screen' radio button and give 2000 as the screen name, then click on edit.
    26) In the next screen.. Select 'Layout Editor' and click 'Change'.
    27) Screen default layout appears...here you can design/modify the screen..change the attributes of the fields..etc.
    28) Save and activate. (Don't forget to 'Activate at every level)
    Subtype Creation :
    Transaction PM01 Goto Subtype Characteristics. Click on Append and then subtype. Enter the name and description of subtype on screen.
    Then goto technical Characteristics and maintain the details of subtype there. I.e name of subtype i.e. component name defined in PSnnnn. Subtype table is T591A.
    Subty.text tab is T591S and time const tab is T591A.
    See:
    http://help.sap.com/saphelp_46c/helpdata/en/4f/d5268a575e11d189270000e8322f96/content.htm
    HR related site:
    http://www.sapdevelopment.co.uk/hr/hrhome.htm
    Enhancement of Infotype
    Check the following
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAXX/PYINT_INFOTYP.pdf
    Infotype Enhancement overview screen
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60a7586d-edd9-2910-68a8-8204303835a1

  • When I run the BAPI "BAPI_PBSRVAPS_GETDETAIL" .It gives me a short dump.

    When I run the BAPI "BAPI_PBSRVAPS_GETDETAIL" .It gives me a short dump.
    Can anybody help me with this?

    This is the content of the dump.
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
    Except.                CX_SY_REF_IS_INITIAL
    Date and Time          05/17/2007 11:21:29
    Short text
         Access via 'NULL' object reference not possible.
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "/SAPAPO/SAPLADVF" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
          caught in
         procedure "/SAPAPO/ADVF_CELL_INPUT" "(FUNCTION)", 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:
         You attempted to use a 'NULL' object reference (points to 'nothing')
         access a component (variable: "C_S_ACTVIEW-AGC_CHILD1-APOGRID").
         An object reference must point to an object (an instance of a class)
         before it can be used to access components.
         Either the reference was never set or it was set to 'NULL' using the
         CLEAR statement.
    Missing RAISING Clause in Interface
        Program                                 /SAPAPO/SAPLADVF
        Include                                 /SAPAPO/LADVFU06
        Row                                     1
        Module type                             (FUNCTION)
        Module Name                             /SAPAPO/ADVF_CELL_INPUT
    Trigger Location of Exception
        Program                                 /SAPAPO/SAPLADVF
        Include                                 /SAPAPO/LADVFU06
        Row                                     81
        Module type                             (FUNCTION)
        Module Name                             /SAPAPO/ADVF_CELL_INPUT
    Source Code Extract
    Line  SourceCde
       51 *#TR# (1) Check arguments: Read only mode must be 0, 1 or 2 and row and column must be provi
       52   if f_argument2 is initial or f_argument3 is initial.
       53     break-point id /SAPAPO/ADV__EXECUTION. clear f_argument. f_calc_error = true. exit.
       54   endif.
       55
       56
       57 *#TR# (1a) Calculate line number of the cell (line + line offset)
       58   l_line = f_argument2 + i_line_offset.
       59
      60 *#TR# (1b) Set L_CELL_READONLY depending on the read only mode F_ARGUMENT
      61   case f_argument.
      62     when 0. l_cell_readonly = /sapapo/cl_agc_base=>gs_c_agc_readonly_values-read_only.
      63     when 1. l_cell_readonly = /sapapo/cl_agc_base=>gs_c_agc_readonly_values-read_write.
      64     when 2. l_cell_readonly = /sapapo/cl_agc_base=>gs_c_agc_readonly_values-stateless.
      65     when others.
      66       break-point id /SAPAPO/ADV__EXECUTION. clear f_argument. f_calc_error = true. return.
      67   endcase.
      68
      69 *#TR# (1c) The input status of cells set to read only by the data view definition (history)
      70   if f_argument3 < g_s_cols_properties-first_input_column.
      71     return.
      72   endif.
      73
      74 *#TR# (1d) Note 1005813: The old APOGRID does not support the read only mode
      75 *#TR# /SAPAPO/CL_AGC_BASE=>GS_C_AGC_READONLY_VALUES-READ_WRITE. For compatibility reasons, w
      76 *#TR# read only mode /SAPAPO/CL_AGC_BASE=>GS_C_AGC_READONLY_VALUES-STATELESS
      77
      78 *#TR# Determine version of APOGRID to check, if new or old APOGRID is used. The version is b
      79 *#TR# reasons
      80   if g_agc_grid_version is initial.
    >>>>     c_s_actview-agc_child1-apogrid->get_control_version(
      82       IMPORTING
      83         apogrid           = l_apogrid
      84       EXCEPTIONS
      85         cntl_system_error = 1
      86         cntl_error        = 2
      87         others            = 3
      88           ).
      89     if sy-subrc <> 0.
      90       break-point id /sapapo/adv__execution. clear f_argument. f_calc_error = true. exit.
    91     endif.
    92
    93     g_agc_grid_version = l_apogrid.
    94   endif.
    95
    96 *#TR# If the old grid is used change read only mode if necessary
    97   if g_agc_grid_version < 200
    98     and l_cell_readonly = /sapapo/cl_agc_base=>gs_c_agc_readonly_values-read_write.
    99
    100     l_cell_readonly = /sapapo/cl_agc_base=>gs_c_agc_readonly_values-stateless.

  • Short dump 'Table does not exist in database'

    Hello All,
    When a report is executing it is going to short dump by saying 'Table does not exist in database'. As per the short dump analysis this issue is happening because of the following   Native SQL statement statement :
    Program :  %_T050N0 (This is a dynamic  program generating by SAP )
    Form Name :  DYN_LIC_SEL_TOT
    exec sql performing LOOP_MOVE_WRITE_ISAP.
    select single_plate, itm_num, ctry_code, model_lot,
    lic_hold_flg, qty into :dcat-lplate, :dcat-matnr,
    :dcat-werks, :dcat-charg, :dcat-holdflag,
    :dcat-qty from ZLICENSE_R2 where itm_num   = :p_matnr and
                    model_lot = :p_charg
    endexec.
    As per the customer this issue occurring since they migrated the SAP  back-end data base from Oralce to DB6. Here I felt that ZLICENSE_R2 is not migrated from the  Oracle to DB6. But as per the BASIS Team, even this table was not maintained in Oracle also. If the table was not maintained in the Oracle, this issue should have been there even before migration also.
    Following is the short dump details:
    Short text
        Table does not exist in database.
    What happened?
        The table or view name used does not
        exist in the database.
        The error occurred in the current database connection "DEFAULT".
    What can you do?
        Check the spelling of the table names in your report.
        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_NATIVE_SQL_ERROR', was not
         caught in
       procedure "DYN_LIC_SEL_TOT" "(FORM)", 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:
    Triggering SQL statement: "select single_plate, itm_num, ctry_code, model_lot,
    lic_hold_flg, qty from ZLICENSE_R2 where itm_num = ? and model_lot = ? "
    Database error code: "-204"
    Could you please  let me know what might be the reason for this issue.
    Many Thanks in Advance.

    Transaction SE11, input ZLICENSE_R2 for table name, and display the table. Did the table display? If not, that is the main problem.
    If the table displays, go to menu item Utilities -> Database Object -> Database Utility
    In the resulting screen, under the "Status" fields, you should see text "Exists in the database." If you don't, then the table exists in the dictionary, but doesn't exist in the database system. Click the "Create database table" button and then you should be able to run the program.
    You may need basis team's help to carryout some of these actions.

  • Short Dump while scrolling in a maintenance view

    A maintenance view has one field, defined as "Radiobutton".
    1) Select the radiobutton for one entry.
    2) Scroll down so that in the new page (i.e. the entries displayed in the new page) the entry selected in the first step is not visible.
    3) Select any radiobutton again corresponding to any of the entries displayed in the new page.
    4) On scrolling up again the short dump occurs.
    The short dump text says "More than one radio button is active".
    Any inputs in this regards are appreciated.
    Thanks.
    Gajendra.

    Hi,
    that means you are trying to make two radio buttons active.
    parameters: ra radiobutton group g1 default = 'X',
                rb radiobutton group g1.
    ra = 'X'.
    and rb = 'X'.
    in your case so obviously it will dump.
    check your coding..
    and show your code...
    Regards
    vijay

  • SHORT DUMP WHILE EXECUTING DTP.

    Hi Gurus,
    I have got a short dump while executing DTP the Error is as Follows.
    Runtime Error: MESSAGE_TYPE_X.
    Reasons for Error: 1.The installation of the SAP GUI on the present server is faulty or obselete
    2.There is a error in the application program
    And i have sent the sreen shot of the Short Dump to BASIS TEAM and they have replied me that they have to install some patches and it will take some time.
    But i have no much time and i have to someway or the other execute the DTP and load the data.
    Is there any shortcuts for this i mean to say without the involvement of Basis team that i can do in th BI System
    Regards
    Amar.

    Hi Amar,
    If the problem is with with System itself, how can we all have a short cut in that case. You may give it another trial, but you have to wait for the patches to be applied. Ask your basis team to get it done ASAP.
    Thanks..
    Shambhu

  • Custom error message in user exit is giving Short dump

    Hi All,
    We have a scenario where in if any user try to create/Change/Delete particular types of contract in SAP system we have to issue error message
    saying ZIN/ZIR contract creation/Change/Deletion is blocked in SAP. This has to be done from the web application. So we are putting below code
    in user exit MV45AFZZ in the form USEREXIT_SAVE_DOCUMENT_PREPARE.
    CONSTANTS: lc_vbcpic01 TYPE sy-uname VALUE u2018VBCPIC01u2019, u201CWeb application user ID
             lc_zin           TYPE vbak-auart VALUE u2018ZINu2019,
                         lc_zir            TYPE vbak-auart VALUE u2018ZIRu2019,
                         lc_text(32)    TYPE c VALUE u2018Check long text for more detailsu2019.
    DATA: l_uname TYPE sy-uname.
    CLEAR: l_uname.
    MOVE sy-uname TO l_uname.
    *If user ID is not the Web application ID then block the creation/Change/Deletion
    IF   l_uname NE lc_vbcpic01
    AND ( vbak-auart EQ lc_zin
    OR    vbak-auart EQ lc_zir ).
    MESSAGE e830(zv) WITH lc_text.
    ENDIF.
    This code is working fine while creating/Changing the contract i.e. Giving us error message so that user wonu2019t be able to create/change the contract.
    But when we delete the contract from VA42, Control is coming to this message statement and is giving Short dump. Below is the error analysis of the dump.
    Error Analysis:
    During "Exit Command" processing, the program tried to send a " " message.
    This is not allowed at this point in processing.
    The program had to be terminated.
    Screen name.............. "SAPMV45A"
    Screen number............ 4001
    If any one has come across such scenario/any work around for this problem please let me know your inputs. Your inputs are highly appreciated.
    I am working on 4.6C version of SAP.
    Note: When i issue information/Warning message contract is getting deleted after displaying the message.
    Thanks,
    Vinod.

    I exactly replicated the same in DELETE_DOCUMENT also
    I am getting the Dump. I tried with exit also , but it continued and deleted. To avoid deletion we have to use Leave program or LEAVE TO CURRENT TRANSACTION.
    Delete Function is Defined as EXIT command. so it is not possible to give error message. To convice you i just copied demo program and raised the error message.
    it is also giving the dump.
    copy the demo program DEMO_DYNPRO_AT_EXIT_COMMAND and make this change , information to error .
    MODULE cancel INPUT.
      MESSAGE e888(sabapdocu) WITH text-001 ok_code input1 input2.
      IF ok_code = 'CANCEL'.
        CLEAR ok_code.
        LEAVE PROGRAM.
      ENDIF.
    ENDMODULE.
    and see...

  • Short dump while creating a plant.

    Dear experts,
    Iam getting a short dump whenever I try to create a plant and save it. Iam posting the contents of the dump ... Iam using Ecc 6.0 with Oracle as database. Kindly help me to resolve this ...
    Runtime Errors         RAISE_EXCEPTION
    Date and Time          27.10.2007 17:10:59
    Short text
    Exception condition "DATA_INCONS_IN_EXIT_MANAGEM" raised.
    What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
    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
    A RAISE statement in the program "CL_EXITHANDLER================CP" raised the
    exception
    condition "DATA_INCONS_IN_EXIT_MANAGEM".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
    How to correct the error
    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:
    "RAISE_EXCEPTION" " "
    "CL_EXITHANDLER================CP" or "CL_EXITHANDLER================CM001"
    "GET_INSTANCE"
    or
    "CL_EXITHANDLER================CP" "DATA_INCONS_IN_EXIT_MANAGEM"
    or
    "SAPLS_IMG_TOOL_5 " "DATA_INCONS_IN_EXIT_MANAGEM"
    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.
    System environment
    SAP-Release 700
    Application server... "BSLERP"
    Network address...... "10.60.0.30"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x Intel 801586"
    Character length.... 16 Bits
    Pointer length....... 32 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "BSLERP"
    Database type..... "ORACLE"
    Database name..... "BTS"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Apr 2 2006 23:08:16"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "OCI_10103_SHARE "
    Patch level. 52
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    Memory consumption
    Roll.... 8176
    EM...... 17768808
    Heap.... 0
    Page.... 65536
    MM Used. 12293456
    MM Free. 1291704
    User and Transaction
    Client.............. 800
    User................ "MURTHYTSN"
    Language key........ "E"
    Transaction......... "SPRO "
    Program............. "CL_EXITHANDLER================CP"
    Screen.............. "SAPLSZA1 0201"
    Screen line......... 70
    Information on where terminated
    Termination occurred in the ABAP program "CL_EXITHANDLER================CP" -
    in "GET_INSTANCE".
    The main program was "SAPLS_IMG_TOOL_5 ".
    In the source code you have the termination point in line 36
    of the (Include) program "CL_EXITHANDLER================CM001".
    Source Code Extract
    Line
    SourceCde
    6
    type_ref TYPE REF TO cl_abap_typedescr,
    7
    class_name TYPE seoclsname,
    8
    abs_type_classname TYPE string,
    9
    def_impl TYPE seex_boolean VALUE seex_false,
    10
    mig_enhspotname TYPE enhspotname,
    11
    is_impl TYPE enhboolean,
    12
    mig_badi_name TYPE enhbadiid.
    13
    14
    CALL METHOD cl_exithandler=>get_class_name_by_interface
    15
    EXPORTING
    16
    instance                      = instance
    17
    IMPORTING
    18
    class_name                    = class_name
    19
    CHANGING
    20
    exit_name                     = exit_name
    21
    EXCEPTIONS
    22
    no_reference                  = 1
    23
    no_interface_reference        = 2
    24
    no_exit_interface             = 3
    25
    data_incons_in_exit_managem   = 4
    26
    class_not_implement_interface = 5
    27
    OTHERS                        = 6.
    28
    CASE sy-subrc.
    29
    WHEN 1.
    30
    RAISE no_reference.
    31
    WHEN 2.
    32
    RAISE no_interface_reference.
    33
    WHEN 3.
    34
    RAISE no_exit_interface.
    35
    WHEN 4.
    >>>>>
    RAISE data_incons_in_exit_managem.
    37
    WHEN 5.
    38
    RAISE class_not_implement_interface.
    39
    ENDCASE.
    40
    41
    CONCATENATE '\CLASS=' class_name INTO abs_type_classname.
    42
    43
    Is the given instance initial?
    44
    IF NOT instance IS INITIAL.
    45
    CALL METHOD cl_abap_typedescr=>describe_by_object_ref
    46
    EXPORTING
    47
    p_object_ref = instance
    48
    RECEIVING
    49
    p_descr_ref  = type_ref.
    50
    CHECK type_ref->absolute_name NE abs_type_classname.
    51
    ENDIF.
    52
    53
    SELECT SINGLE mig_enhspotname mig_badi_name FROM sxs_attr INTO (mig_enhspotname,mig_badi_n
    54
    WHERE exit_name = exit_name.
    55
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    4
    SY-INDEX
    1
    SY-TABIX
    0
    SY-DBCNT
    0
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    ADDR0200
    SY-UCOMM
    CHCK
    SY-TITLE
    Edit address:  5002
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20071024
    SY-UZEIT
    171059
    SY-XPROG
    SAPCNVE
    SY-XFORM
    CONVERSION_EXIT
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    43 METHOD       CL_EXITHANDLER================CP    CL_EXITHANDLER================CM001    36
    CL_EXITHANDLER=>GET_INSTANCE
    42 FUNCTION     SAPLXSZAR                           ZXSZARU01                              25
    EXIT_SAPLSZAR_001
    41 FUNCTION     SAPLSZAR                            LSZARU01                              108
    ADDR_REGIONAL_DATA_CHECK
    40 FORM         SAPLSZA2                            LSZA2F20                              382
    CHECK_ADDR1_DATA
    39 FUNCTION     SAPLSZA2                            LSZA2U02                               42
    ADDR_CHECK
    38 FUNCTION     SAPLSZA0                            LSZA0U01                               79
    ADDR_INSERT
    37 FORM         SAPLSZA1                            LSZA1F22                             1886
    INSERT_ADDRESS_INTO_MEMORY
    36 FORM         SAPLSZA1                            LSZA1F22                             2234
    PUT_ADDRESS_TO_MEMORY
    35 FORM         SAPLSZA1                            LSZA1I02                              409
    D0100_OK_CODE
    34 FORM         SAPLSZA1                            LSZA1F03                               17
    D0100_OK_CODE_WRAPPER
    33 MODULE (PAI) SAPLSZA1                            LSZA1I02                               13
    D0100_OK_CODE
    32 FUNCTION     SAPLSZA1                            LSZA1U01                              200
    ADDR_DIALOG_INTERN
    31 FUNCTION     SAPLSZA1                            LSZA1U05                              177
    ADDR_DIALOG
    30 FORM         SAPL0ORG                            LSVIMF24                              292
    ADDRESS_MAINTAIN
    29 FORM         SAPL0ORG                            LSVIMFX2                              577
    DETAIL_PAI
    28 MODULE (PAI) SAPL0ORG                            LSVIMIXX                              354
    DETAIL_PAI
    27 FORM         SAPL0ORG                            LSVIMF2L                              337
    CALL_DYNPRO
    26 FUNCTION     SAPL0ORG                            L0ORGU34                               35
    VIEWPROC_V_T001W
    25 FUNCTION     SAPL0ORG                            L0ORGU33                               49
    VIEWFRAME_V_T001W
    24 FUNCTION     SAPLSVIM                            LSVIMU01                              138
    VIEW_MAINTENANCE
    23 FUNCTION     SAPLSVIM                            LSVIMU03                              427
    VIEW_MAINTENANCE_CALL
    22 FORM         SAPLS_CUS_ACTIVITY                  LS_CUS_ACTIVITYF01                    358
    START_SELECTED_TRANSACTION
    21 MODULE (PAI) SAPLDSYH                            LDSYHI12                               56
    D1200_PAI_MODULE
    20 FUNCTION     SAPLDSYH                            LDSYHU11                               70
    OUTLINE_LIST_TCODES
    19 FUNCTION     SAPLS_CUS_ACTIVITY                  LS_CUS_ACTIVITYU07                    103
    S_CUS_ACTIVITY_EXECUTE
    18 FUNCTION     SAPLS_CUS_IMG_ACTIVITY              LS_CUS_IMG_ACTIVITYU04                 35
    S_CUS_IMG_ACTIVITY_EXECUTE
    17 FUNCTION     SAPLS_IMG_TOOL_1                    LS_IMG_TOOL_1U02                       63
    STREE_EXIT_TO_OBJECT_COBJ
    16 FUNCTION     SAPLSHI1                            LSHI1U16                              120
    STREE_EXIT_TO_OBJECT
    15 FORM         SAPLSHI01                           LSHI01F0Y                             185
    EXIT_TO_OBJECT_HC
    14 FORM         SAPLSHI01                           LSHI01F05                              70
    HANDLE_LINK_CLICK
    13 METHOD       SAPLSHI01                           LSHI01CI1                              25
    LCL_APPLICATION=>HANDLE_LINK_CLICK
    12 METHOD       CL_ITEM_TREE_CONTROL==========CP    CL_ITEM_TREE_CONTROL==========CM013    53
    CL_ITEM_TREE_CONTROL=>HANDLE_NODE_KEY_ITEM_NAME_EVT
    11 METHOD       CL_ITEM_TREE_CONTROL==========CP    CL_ITEM_TREE_CONTROL==========CM00S    60
    CL_ITEM_TREE_CONTROL=>HANDLE_EVENT
    10 METHOD       CL_GUI_COLUMN_TREE============CP    CL_GUI_COLUMN_TREE============CM01O    15
    CL_GUI_COLUMN_TREE=>HANDLE_EVENT
    9 METHOD       CL_TREE_CONTROL_BASE==========CP    CL_TREE_CONTROL_BASE==========CM017    32
    CL_TREE_CONTROL_BASE=>DISPATCH
    8 METHOD       CL_GUI_CFW====================CP    CL_GUI_CFW====================CM001   138
    CL_GUI_CFW=>DISPATCH
    7 FORM         SAPLSHI01                           LSHI01F1M                              17
    EXECUTE_USER_COMMAND_W_EXITS
    6 FUNCTION     SAPLSHI01                           LSHI01U12                              30
    STREE_BROWSER_PAI
    5 MODULE (PAI) SAPLSHI01                           LSHI01I01                              55
    PAI_200
    4 FUNCTION     SAPLSHI01                           LSHI01U07                             165
    STREE_BROWSER_DYNP_HC
    3 FUNCTION     SAPLSHI21                           LSHI21U03                             144
    STREE_EXTERNAL_DISPLAY
    2 FORM         SAPLS_IMG_TOOL_5                    LS_IMG_TOOL_5F01                       20
    DISPLAY_REFERENCE_IMG
    1 MODULE (PAI) SAPLS_IMG_TOOL_5                    LS_IMG_TOOL_5I01                       39
    USER_COMMAND_0100
    Chosen variables
    Name
    Val.
    No.      43 Ty.          METHOD
    Name  CL_EXITHANDLER=>GET_INSTANCE
    EXIT_NAME
    22222222222222222222
    00000000000000000000
    00000000000000000000
    00000000000000000000
    NULL_INSTANCE_ACCEPTED
    2
    0
    0
    0
    ACT_IMP_EXISTING
    2
    0
    0
    0
    INSTANCE
    F0000000
    F0000000
    SY-REPID
    CL_EXITHANDLER================CP
    4454545444444533333333333333334522222222
    3CF589481E4C52DDDDDDDDDDDDDDDD3000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    %_SPACE
    2
    0
    0
    0
    CL_DRAGDROP=>COPY
    1
    0000
    1000
    CL_WB_REQUEST=>TO_IMMEDIATE_START
    SY-SUBRC
    4
    0000
    4000
    CL_DRAGDROP=>USEDEFAULTEFFECT
    4
    0000
    4000
    SYST-REPID
    CL_EXITHANDLER================CP
    4454545444444533333333333333334522222222
    3CF589481E4C52DDDDDDDDDDDDDDDD3000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    CL_GUI_CONTROL=>LIFETIME_DEFAULT
    0
    0000
    0000
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    ABS_TYPE_CLASSNAME
    No.      42 Ty.          FUNCTION
    Name  EXIT_SAPLSZAR_001
    IV_NATION
    2
    0
    0
    0
    X_ACCEPT_ERROR
    2
    0
    0
    0
    X_ADRC_STRUC
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    X_DIALOG_ALLOWED
    X
    5
    8
    0
    0
    Y_ADRC_STRUC
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    Y_RETCODE
    2
    0
    0
    0
    ERROR_TABLE[]
    Table IT_2299[0x572]
    \FUNCTION-POOL=SZA1\FORM=INSERT_ADDRESS_INTO_MEMORY\DATA=ERROR_TABLE[]
    Table reference: 208
    TABH+  0(20) = 00000000F8EB2E3D00000000D0000000FB080000
    TABH+ 20(20) = 000000003C020000FFFFFFFF04A90100303E0000
    TABH+ 40( 8) = 10000000C1248001
    store        = 0x00000000
    ext1         = 0xF8EB2E3D
    shmId        = 0     (0x00000000)
    id           = 208   (0xD0000000)
    label        = 2299  (0xFB080000)
    fill         = 0     (0x00000000)
    leng         = 572   (0x3C020000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000317
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    collHook     = 0x00000000
    ext2         = 0xD09AD03C
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x30F18E3D
    delta_head   = 000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    SY-XPROG
    SAPCNVE
    5454454222222222222222222222222222222222
    3103E65000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    SY-XFORM
    CONVERSION_EXIT
    444545544454545222222222222222
    3FE65239FEF5894000000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    %_VIASELSCR
    0
    4
    %_SPACE
    2
    0
    0
    0
    SY-REPID
    SAPLXSZAR
    5454555452222222222222222222222222222222
    310C83A120000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    LR_EXIT
    F0000000
    F0000000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    Y_ERROR_TABLE
    Table[initial]
    No.      41 Ty.          FUNCTION
    Name  ADDR_REGIONAL_DATA_CHECK
    IV_NATION
    2
    0
    0
    0
    X_ACCEPT_ERROR
    2
    0
    0
    0
    X_ADRC_STRUC
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    X_DIALOG_ALLOWED
    X
    5
    8
    0
    0
    X_T005
    800IN IND064            ININD000   00 15500  4111  0000 00 436      664000INDIEN 000 1
    3334424443332222222222224444433322233233333223333223333233233322222233333344444423332322222222
    8009E09E40640000000000009E9E40000000001550000411100000000004360000006640009E495E00000100000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    Y_ADRC_REGIO
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    Y_ADRC_STRUC
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    Y_RETCODE
    2
    0
    0
    0
    ERROR_TABLE[]
    Table IT_2299[0x572]
    SY-XPROG
    SAPCNVE
    5454454222222222222222222222222222222222
    3103E65000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    LV_MAND
    C
    422
    300
    000
    000
    SY-REPID
    SAPLSZAR
    5454554522222222222222222222222222222222
    310C3A1200000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    %_SPACE
    2
    0
    0
    0
    %_CX_GRID_ID
    1
    0000
    1000
    SYST-REPID
    SAPLSZAR
    5454554522222222222222222222222222222222
    310C3A1200000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    SV_THERE_IS_CUST_EXIT
    X
    5
    8
    0
    0
    T005S
    22222222222222
    00000000000000
    00000000000000
    00000000000000
    T005
    00                  000   00 00 00   00   0000 00             000       000
    2222222223322222222222222222233322233233233222332223333233222222222222233322222223332222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    CO_ERROR
    E
    4
    5
    0
    0
    No.      40 Ty.          FORM
    Name  CHECK_ADDR1_DATA
    SY-MSGV3
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    FIELDNAME
    222222222222222222222222222222
    000000000000000000000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    C_NULL
    0
    0000
    0000
    RETURNCODE_ERRORS
    2
    0
    0
    0
    C_ERROR_OCCURRED
    E
    4
    5
    0
    0
    H_ADRC_STRUC+0(1800)
    2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    ADDR1_DATA+460(1800)
    2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    H_ADRC_STRUC
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    C_COMM_TTX
    TTX
    555
    448
    000
    000
    NATION
    2
    0
    0
    0
    G_ACCEPT_ERROR
    2
    0
    0
    0
    G_DIALOG_ALLOWED
    X
    5
    8
    0
    0
    T005
    800IN IND064            ININD000   00 15500  4111  0000 00 436      664000INDIEN 000 1
    3334424443332222222222224444433322233233333223333223333233233322222233333344444423332322222222
    8009E09E40640000000000009E9E40000000001550000411100000000004360000006640009E495E00000100000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    TSAD6T
    222222222222222222222222222222222222222222222222
    000000000000000000000000000000000000000000000000
    000000000000000000000000000000000000000000000000
    000000000000000000000000000000000000000000000000
    ERROR_TABLE[]
    Table IT_2299[0x572]
    %_SPACE
    2
    0
    0
    0
    No.      39 Ty.          FUNCTION
    Name  ADDR_CHECK
    ADDRESS_HANDLE
    8005002
    3333333222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    8005002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    ADDRESS_NUMBER
    2222222222
    0000000000
    0000000000
    0000000000
    ADDRESS_OBJECT_TYPE
    1
    3
    1
    0
    0
    NATION
    2
    0
    0
    0
    RETURNCODE
    2
    0
    0
    0
    ERROR_TABLE[]
    Table IT_2299[0x572]
    ADDRESS_DATA_1
    00000000000000000003XYZ SOLUTIONS LIMITED
    3333333333333333333355525445544452444454422222222222222222222222222222222222222222222222222222
    0000000000000000000389A03FC549FE30C9D945400000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    ADDRESS_DATA_2
    0000000000000000
    3333333333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    ADDRESS_DATA_3
    0000000000000000
    3333333333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    LV_ADRC_STRUC+0(1800)
    2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    ADDRESS_DATA_1+460(1800)
    2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    C_DEFAULT_HANDLE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SYST-REPID
    SAPLSZA2
    5454554322222222222222222222222222222222
    310C3A1200000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    ERROR_TABLE
    000
    2222222222222222222223332222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    LV_ADRC_STRUC
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    C_DEFAULT_NATION
    2
    0
    0
    0
    C_SHOW_ALL
    2
    0
    0
    0
    C_PERSONAL_ADDRESS
    2
    3
    2
    0
    0
    SY-REPID
    SAPLSZA2
    5454554322222222222222222222222222222222
    310C3A1200000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    ADDRESS_DATA_2+32(1800)
    2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.      38 Ty.          FUNCTION
    Name  ADDR_INSERT

    Dear Sunil,
    Thanks a lot for your reply. I did search in service market place for notes regarding this problem. However, i could not find possible solutions to resolve this. I will once again search the notes in case if i have missed something. in case, if you come across any solutions to resolve this problem, Kindly post that here and that would be a great help for me.
    Regards,
    Chaitanya

Maybe you are looking for