Reg:OBJECTS_OBJREF_NOT_ASSIGNED dump

Hi Experts,
I am seeing a lot of OBJECTS_OBJREF_NOT_ASSIGNED dumps in one of our productions servers with the a few of the cancelled background jobs.
We have just upgraded from 4.7 to ECC6
The error text is
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 "GET_SPECIAL_DATA_INTERNAL" "(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: "ME->GO_PARENT_CBASE_PROFILE").
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.
We have tried to find the SAP notes,but could not find the proper ones
Kindly help us fix the dump issue
Rgds-
Venu

Hi Venu,
In your setup of the shared memory area in SHMA, do you have the versioning option unchecked?  If you do that might explain your issue.  If a user tries to access the one instance of the object in the shared memory area while it is currently being refreshed to memory they will get this short dump.  The one way to protect against this error would be to make sure that the user reading from the memory area does a check for success in attach_for_read( ) before going further.  See this example:
  DATA: lv_tries TYPE i,
        lv_subrc TYPE sy-subrc.
  CONSTANTS: lc_max TYPE i VALUE '10000''.
Initialize variables for a max of 10000 tries
  CLEAR lv_tries.
  lv_subrc = 1.
Attach for read from shared memory area
  WHILE lv_tries < lc_max AND lv_subrc <> 0.
    TRY.
      cl_area = zcl_shm_employee_master=>attach_for_read( ).
      lv_subrc = sy-subrc.
      CATCH: cx_shm_inconsistent,
                   cx_shm_no_active_version,
                   cx_shm_read_lock_active,
                   cx_shm_exclusive_lock_active,
                   cx_shm_parameter_error,
                   cx_shm_change_lock_active.
      lv_tries = lv_tries + 1.
    ENDTRY.
  ENDWHILE.
Raise exception if tries reaches count of 10000
  IF lv_tries = lc_max.
    RAISE READ_ERROR.
  ENDIF.
The number 10000 is an arbitrary number chosen for the example but you can get the idea from it.  This will ensure that either a success attach is performed or an exception is thrown.  Of course you could always just call multiple times until you get a successful attach.  I did it this way to avoid a potential infinite loop in the case that it is not able to attach successfully.
Regards,
Ryan Crosby

Similar Messages

  • OBJECTS_OBJREF_NOT_ASSIGNED Dump while Installing Process Chain

    Hi Gurus,
                 I got OBJECTS_OBJREF_NOT_ASSIGNED dump while installing Business Content process chian "0TCT_C2_INIT_P01".
    Also 6 info packages were not delivered in business content for the above chian.
    Any Help.
    Regards,
    Anil

    Check if this note helps..though it is for infoobjects
    <a href="https://websmp202.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1019055&_NLANG=E">Note 1019055 - Runtimer errors when activating InfoObjects</a>
    Message was edited by:
            Manga Paidikondala

  • OBJECTS_OBJREF_NOT_ASSIGNED dump

    Hi,
    I am facing the ABPAP dump " OBJECTS_OBJREF_NOT_ASSIGNED"
    Can anyone pls suggest me.
    I am facing this  when running the tcode HRFORMS in a method "READ_DB".
    Information on where terminated
        Termination occurred in the ABAP program "CL_INFOSTAR_HRF02=============CP" -
         in "READ_DB".
        The main program was "H99HRF03 ".
        In the source code you have the termination point in line 32
        of the (Include) program "CL_INFOSTAR_HRF02=============CM003".
        The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
        procedure "READ_DB" "(METHOD)", but it was neither handled locally nor declared
        in the RAISING clause of its signature.
        The procedure is in program "CL_INFOSTAR_HRF02=============CP "; its source
         code begins in line
        1 of the (Include program "CL_INFOSTAR_HRF02=============CM003 ".
    Thank u

    Hello,
    is there any solution for this problem? I have the same problem.
    Bye.
    Markus

  • Reg:ABAP dump:TYPELOAD_NEW_VERSION

    Hi All,
    We are getting the dumps(150),TYPELOAD_NEW_VERSION with only one particular user in one of our production servers,there are a few background jobs scheduled with the same user and all the jobs have got finished successfully.
    below pasted is the detailed dump message
    Data type "MC11VA0ITM" was found in a newer version than required.
    What happened?
    Runtime error
    The current ABAP program, "SAPLMCEX", had to be terminated because one of the
    statements could not be executed at runtime.
    What can you do?
    Try restarting the program.
    If the error occurrs several times, consult your SAP administrator.
    Choose "Print" to obtain a hard copy of the termination message.
    You can use Transaction ST22 to display and manage short dump messages.
    It also allows you to retain them beyond their normal deletion date.
    Error analysis
    The data type "MC11VA0ITM" was reloaded from the database while the program
    was running.
    However, the system found a version of the type that was newer than
    the one required.
    How to correct the error
    Try to restart the program.
    System environment
    SAP Release.............. "620"
    Application server....... "provpr08"
    Network address.......... "10.130.33.98"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00C6C8D04C00"
    Character length......... 16 Bits
    Pointer length........... 64 Bits
    Work process number...... 0
    Short dump setting....... "full"
    Database server.......... "provpr01"
    Database type............ "ORACLE"
    Database name............ "VPR"
    Database owner........... "SAPERP"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "Aug 17 2008 21:27:08"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
    Patch level.............. "247"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
    10.2.0.."
    SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
    User, transaction...
    Client.............. 810
    User................ "ADMINJOBS"
    Language key........ "E"
    Transaction......... " "
    Program............. "SAPLMCEX"
    Screen.............. "SAPMSSY0 1000"
    Row of screen....... 6
    Information about program making the Remote Function Call (RFC):
    System.............. "VPR"
    Database Release.... 620
    Kernel Release...... 640
    Connection type: 3 (2 = R/2, 3 = R/3, E = External, R = Reg.external)
    Call type: "synchron (imode 1)" (S = Synchronous, a/A = Asynchronous, T =
    Transaction)
    Client.............. 810
    User................ "ADMINJOBS"
    Transaction......... " (Program: SAPLV50R_VIEW)"
    Function module..... "SHP_VL10_DELIVERY_CREATE_PARA"
    Call destination.... "provpr08_VPR_01"
    Source server....... "provpr05_VPR_01"
    Source IP address... "10.130.33.108"
    Additional RFC logon information:
    Trusted Relation....." "
    Logon return code....0
    Trusted return code..0
    Note: Prior to Release 4.0, there was less information available on RFC
    calling programs.
    Information on where terminated
    The termination occurred in the ABAP program "SAPLMCEX" in "MCEX_11_QRFC".
    The main program was "SAPMSSY4 ".
    The termination occurred in line 0 of the source code of the (Include)
    program " "
    of the source code of program " " (when calling the editor 00).
    We are on 640 Kernel-AIX ,level-247
    I have no clue on how to go about,
    can some one pls.look into it nad do the needful.
    Thanks in advance
    Rgds
    Venu

    Hi Rohit,
    Thanks once again
    I believe that my question has been answered appropriately,I appriciate the your help and support.
    I take the liberty to put across one more ABAP dump(80 dumps by a single user),"RABAX_CALLING_RABAX:"
    The error text is as below
    Runtime Error          RABAX_CALLING_RABAX
           Occurred on     03/24/2009 at   07:25:29
    Error "14 431" in error handling.
    What happened?
    A further error occurred when displaying an error message.
    What can you do?
    You can display the error message using Transaction ST22. If
    no further error is logged there, try to find an appropriate
    entry in the SAP system log.
    Make a note of the actions and input which caused the error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    Error analysis
    The T100 error code is "14 431".
    The error text reads
    Invalid output to terminal from background processing
    with this key.
               Last error logged in SAP kernel
    Component............ "Taskhandler"
    Place................ "SAP-Server provpr03_VPR_01 on host provpr03 (wp 0)"
    Version.............. 1
    Error code........... 5
    Error text........... "ThAMInsert: no active mode"
    Description.......... " "
    System call.......... " "
    Module............... "thxxhead.c"
    Line................. 9893
    How to correct the error
    In general, it is sufficient to determine the original cause of the
    error and to eliminate it. Since the display of the runtime error
    has failed, you can only analyze the error by looking at the
    system log or the short dump display.
    System environment
    SAP Release.............. "620"
    Application server....... "provpr03"
    Network address.......... "10.130.33.106"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00C6C9904C00"
    Character length......... 16 Bits
    Pointer length........... 64 Bits
    Work process number...... 2
    Short dump setting....... "full"
    Database server.......... "provpr01"
    Database type............ "ORACLE"
    Database name............ "VPR"
    Database owner........... "SAPERP"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "Aug 17 2008 21:27:08"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
    Patch level.............. "247"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
    10.2.0.."
    SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
    Client.............. 810
    User................ "HJAFFER"
    Language key........ "E"
    Transaction......... " "
    Program............. "SAPLSGUI"
    Screen.............. "SAPMS380 0100"
    Row of screen....... 3
    Information about program making the Remote Function Call (RFC):
    System.............. "VPR"
    Database Release.... 620
    Kernel Release...... 640
    Connection type: 3 (2 = R/2, 3 = R/3, E = External, R = Reg.external)
    Call type: "synchron (imode 1)" (S = Synchronous, a/A = Asynchronous, T =
    Transaction)
    Client.............. 810
    User................ "HJAFFER"
    Transaction......... "ZSA5E (Program: ZVRV_OPEN_ORDERS_ALV)"
    Function module..... "ZVRV_OPEN_ORDERS_ALV_PRL"
    Call destination.... "provpr03_VPR_00"
    Source server....... "provpr03_VPR_01"
    Source IP address... "10.130.33.106"
    Additional RFC logon information:
    Trusted Relation....." "
    Logon return code....0
    Trusted return code..0
    Note: Prior to Release 4.0, there was less information available on RFC
    calling programs.
    Information on where terminated
    The termination occurred in the ABAP program "SAPLSGUI" in
    "SAPGUI_PROGRESS_INDICATOR".
    The main program was "SAPMS380 ".
    The termination occurred in line 33 of the source code of the (Include)
    program "LSGUIU01"
    of the source code of program "LSGUIU01" (when calling the editor 330).
    There are so many logs written in SM21 by the same user as mentioned below
    HJAFFER           AB0 Run-time error "CALL_FUNCTION_SEND_ERROR" occurred
    HJAFFER           AB1 > Short dump "090324 072401 provpr03 HJAFFER " generated
    HJAFFER           D01 Transaction Canceled 14 431 ( )
    HJAFFER           AB0 Run-time error "RABAX_CALLING_RABAX" occurred
    detailed Log...
    Details Page 1 Line 17    System Log: Central Analysis                        1
    Time     Instance             Ty. Nr Cl. User         Tcod MNo Text                                               Date : 24.03.09
    07:24:01 provpr03_VPR_00      DIA 01 810 HJAFFER           D01 Transaction Canceled 14 431 ( )
    Details
    Recording at local and central time........................ 03/24/2009 07:24:01
    Entry in collective system log at local time............... 03/24/2009 07:25:25
    Task................ 55318 . 01 D1 Dialog work process No. 01
    User................ HJAFFER
    Client.............. 810
    Terminal............ TXFRIALP
    Session............. 1
    Transaction code....
    Program name........ SAPMS380
    Problem class....... K    SAP Web AS Problem
    Development class... SDYN
    Module name.........
    Location............
    T100................ 14                  431
    Parameters..........
    Documentation for system log message D0 1 :
    The transaction has been terminated.  This may be caused by a
    termination message from the application (MESSAGE Axxx) or by an
    error detected by the SAP System due to which it makes no sense to
    proceed with the transaction.  The actual reason for the termination
    is indicated by the T100 message and the parameters.
    Additional documentation for message 14                  431
    Invalid output to terminal from background processing
    No documentation exists for message 14431
    Pls.look into it and guide me thru as you did in the earlier case
    Rgds
    Venu

  • Reg Core Dump

    We are getting bad address core dump while using Coherence lib .
    Please find the dbx stack trace below in .
    @null (l@9) terminated by signal SEGV (no mapping at the fault address)
    0xffffffffffffffff: <bad address 0xffffffffffffffff>
    (dbx) where
    [1] 0xfa666f08(0xf71f8940, 0x28ec9c8, 0xf71f8930, 0x18, 0x8, 0xf71f8880), at 0xfa666f08
    [2] 0xfa662da8(0xf71f8ab0, 0x28ec9c8, 0xf71f89b0, 0xf71f8940, 0x154396e8, 0xfdf88a80), at 0xfa662da8
    [3] 0xfa414a6c(0xf71f8ab0, 0x28ec9d0, 0xf71f8aa0, 0xf71f91e0, 0x0, 0xf71f89b0), at 0xfa414a6c
    [4] 0xfaba8c78(0x28ec9c8, 0xf71f8c20, 0x0, 0xf71f8b80, 0xf71f8ab0, 0x1), at 0xfaba8c78
    [5] 0xfb1f6b8c(0xf71f9190, 0xf71f91e0, 0xf71f8c20, 0xf71f91a0, 0xf71f8c30, 0x28af100), at 0xfb1f6b8c
    [6] 0xfb1f2af0(0x28aaeb0, 0xf71f91a0, 0x0, 0x1, 0xf71f9190, 0xfb1df870), at 0xfb1f2af0
    [7] 0xfb1f5c48(0x28aaeb0, 0x569fb10, 0xf71f9270, 0xf71f9280, 0xf71f9280, 0xf71f9360), at 0xfb1f5c48
    [8] 0xfad25bd0(0x289f3b8, 0xf71f9360, 0xf71f9360, 0xf71f92f0, 0x1, 0xf71f9360), at 0xfad25bd0
    [9] 0xfabf44c0(0x569fb10, 0xfb1fefd4, 0xfeb88ae0, 0xf71f9360, 0xfabf309c, 0xfeaae700), at 0xfabf44c0
    [10] 0xfa8a3d70(0x289f228, 0xf71f9460, 0xf71f9420, 0xf71f9430, 0xfdf88a80, 0xf71f9460), at 0xfa8a3d70
    [11] 0xfa8a338c(0x289f228, 0xf71f9540, 0xf71f9540, 0xf71f94d0, 0x1, 0xf71f95c0), at 0xfa8a338c
    [12] 0xfa7c1dd8(0x25b6ef8, 0x7f13700, 0xf71f9540, 0xf71f95c0, 0xf71f9550, 0x289f2a0), at 0xfa7c1dd8
    [13] 0xfabf44c0(0x7f13700, 0xfa7c3a60, 0xfe37b854, 0xf71f95c0, 0xfabf309c, 0xfe37ac90), at 0xfabf44c0
    [14] 0xfb2c9184(0xf71f9be0, 0xfdd965d4, 0x0, 0xffffffff, 0x1, 0x0), at 0xfb2c9184
    [15] 0xfa8866b4(0x28df150, 0xf71f9d14, 0xf71fa390, 0xfdf88a80, 0x0, 0xf71fa134), at 0xfa8866b4
    [16] 0xfa90c320(0x41f30d0, 0xfe476544, 0x28aae50, 0xf71fa380, 0x3, 0xf71fa458), at 0xfa90c320
    [17] 0xfad8f044(0x867800, 0x41f3198, 0xf71fb500, 0xf71fa670, 0xf71fb500, 0xf71fa5b0), at 0xfad8f044
    [18] 0xfad838dc(0x28aad08, 0xf71fb234, 0xfe7f165c, 0xfdf88a80, 0xf71fad6c, 0xf71fae44), at 0xfad838dc
    [19] 0xfb293ed0(0x28dba98, 0x28aad08, 0xc54400, 0xf71fb500, 0xf71fb4d0, 0xfdf88a80), at 0xfb293ed0
    [20] 0xfa758038(0x28dbab0, 0xfe6ea03c, 0xfe6ea03c, 0xf71fb5a0, 0x1, 0xf71fb5c0), at 0xfa758038
    [21] 0xfa9d9918(0xf71fbed0, 0x28dbdc0, 0xfdf88a80, 0x28e05b8, 0xf71fbf28, 0xfe4eab9c), at 0xfa9d9918
    [22] 0xfa614f74(0x17be110, 0xf71fc000, 0x0, 0x0, 0xfa629ee8, 0xfe275df0), at 0xfa614f74
    Without Coherence lib we don't see these kind of bad address core dumps

    Some time we do see below stack trace caused by coherence ,
    Current function is coherence::native::NativeAtomic64::peek
    79 return m_lAtomic;
    (dbx) where
    =>[1] coherence::native::NativeAtomic64::peek(this = 0x3844119f), line 79 in "NativeAtomic64.hpp"
    [2] coherence::lang::Object::_detach(this = 0x38441197, fEscaped = false), line 761 in "Object.hpp"
    [3] 0xfa2a7fc0(0x3192d5b0, 0x0, 0xc0000000, 0xfdf88a80, 0x0, 0x4f5ca40), at 0xfa2a7fc0
    [4] 0xfa7c5570(0x3192d528, 0x1, 0x1000, 0x3f1728, 0x3f1400, 0xfdf88a80), at 0xfa7c5570
    [5] 0xfab9537c(0x3192d5c8, 0x1ffffe0, 0xfdf88a80, 0x80000000, 0xc0, 0x80), at 0xfab9537c
    [6] coherence::lang::Object::_detach(this = 0x3192d5c8, fEscaped = false), line 774 in "Object.hpp"
    [7] 0xfa7ccd34(0xf71fa288, 0x2, 0x18, 0xfdf88a80, 0x1, 0x1), at 0xfa7ccd34
    [8] 0xfa886744(0x2c0d4e0, 0xf71f9d14, 0xf71f9d14, 0xfdf88a80, 0x0, 0xf71fa134), at 0xfa886744
    [9] 0xfa90c320(0x655adb0, 0xfe476544, 0x2bc2a40, 0xf71fa380, 0x2, 0xf71fa458), at 0xfa90c320
    [10] 0xfad8f044(0x867800, 0x655ae78, 0xf71fb500, 0xf71fa670, 0xf71fb500, 0xf71fa5b0), at 0xfad8f044
    [11] 0xfad838dc(0x2bc28f8, 0xf71fb234, 0xfe7f165c, 0xfdf88a80, 0xf71fad6c, 0xf71fae44), at 0xfad838dc
    [12] 0xfb293ed0(0x2c09620, 0x2bc28f8, 0xc54400, 0xf71fb500, 0xf71fb4d0, 0xfdf88a80), at 0xfb293ed0
    [13] 0xfa758038(0x2c09638, 0xfe6ea03c, 0xfe6ea03c, 0xf71fb5a0, 0x1, 0xf71fb5c0), at 0xfa758038
    [14] 0xfa9d9918(0xf71fbed0, 0x2c09948, 0xfdf88a80, 0x2c0e9c8, 0xf71fbf28, 0xfe4eab9c), at 0xfa9d9918
    [15] 0xfa614f74(0x256e910, 0xf71fc000, 0x0, 0x0, 0xfa629ee8, 0xfe275df0), at 0xfa614f74
    (dbx)
    Please advice.

  • Reg: SXMB_MONI Dump

    Hi All,
    I am getting the below error. In SXMB_MONI first it is failed automatically it Processed successfully. In Development same scenario is working fine.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
    <SAP:Category>XIProtocol</SAP:Category>
    <SAP:Code area="PARSER">ITEM_MISSING</SAP:Code>
    <SAP:P1>Envelope</SAP:P1>
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText />
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack>XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    In SXMb_MONI if i click on Inbound Message or Technical routing, it's getting shot dump.
    Short dump Message is : A raise statement in the program SAPLOLEA raised an expection condition "SYSTEM_FAILURE"
    Plese help me...
    Regards,
    Chandra.

    Hi Chandra,
    Are you using SOAP adapter ?
    If yes, check if you have selected the check button "Do not use SOAP Envelop" then Uncheck it.
    (if you are using this setting then you have to send nosoap in your URL else it will through short dump)
    Thanks,
    Sunil Singh

  • Reg : Short Dump While Activating Workflow

    Hi All,
    This morning I added a condition step in my workflow and created two custom methods in the corresponding BO and used them in the task. Initially when i made the changes in the workflow and tested it, it was working fine. But after sometime, when I did the necessary binding and tried to activate the workflow, the workflow started resulting in short dump.
    Below is the dump analysis.
    SAPSQL_ARRAY_INSERT_DUPREC
    The ABAP/4 Open SQL array insert results in duplicate database records.
    000310        L_OTYPE EQ ORG_OBJTYPE_WORKFLOW.
    000320       LOOP AT ACT_LINES.
    000330         MOVE-CORRESPONDING ACT_WFDKEY TO ACT_LINES.
    000340         MOVE ACT_CLIENT TO ACT_LINES-CLIENT.
    000350         MODIFY ACT_LINES.
    000360       ENDLOOP.
    000370     ELSE.
    000380       MESSAGE E280 WITH L_OTYPE RAISING INVALID_OBJECT_TYPE.
    000390     ENDIF.
    000400
    000410   *- insert lines table
    ------>     INSERT SWD_LINES CLIENT SPECIFIED FROM TABLE ACT_LINES.
    000430     IF SY-SUBRC NE 0.
    000440       MESSAGE E281 WITH SY-SUBRC 'SWD_LINES'
    000450                    RAISING INTERNAL_DATABASE_ERROR.
    000460     ENDIF.
    000470
    000480   *- commit
    000490     IF DO_COMMIT NE ' '.
    000500       COMMIT WORK.
    000510     ENDIF.
    000520
    000530   ENDFUNCTION.
    I tried searching sdn. But all other posts were related to passing entries from internal table to DB. Also I'm not even sure if i can raise a OSS, because a few minutes back the system was working fine and all of sudden this started happening.
    So can you please guide me what I am missing and how can i fix this?
    Thanks & Regards,
    Raj

    Hi Rick,
    When I get acitvate the workflow, the workflow template is gettign active & saved and after that the system results into short dump. And also when i try creating a PR and test this workflow, in SWEL, i can see the below message in RFC status field.
    The ABAP/4 Open SQL array insert results in duplicate database records..
    I haven't done any duplicate binding. Also I checked what you suggested. Didn't work. Also checked my newly added code. But I'm not accessing database directly anywhere. All is done via SAP standard function module.
    Even if i try to display this workflow in PFTC, the system is resulting in the same short dump.
    What could be the reason?
    Regards,
    Raj
    Edited by: Raj  Karunanidhi on Feb 23, 2010 5:30 AM

  • Reg 10g dumps

    hai all can any one help me with oracle 10g dumps my email id is
    [email protected]

    no, noone is going to give you a cheatsheet to cram for the exam.
    Such practices reduce the value of the cert to the point of worthlessness, degrading the effort people put in who do seriously study for it.

  • ABAP DUMP IN SRM4.0

    Hi,
    In SRM 4.0 i am getting the below dumps every day.Can you suggest me reg.this dump how to approach.
    OBJECTS_OBJREF_NOT_ASSIGNED_NO
    ShrtText                                                
        Access with 'ZERO' object reference not possible.   
    What happened?                                                                      
        Error in ABAP application program.                                                                               
    The current ABAP program "SAPLSWRR" had to be terminated because one of the     
        statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                           
    Information on where terminated                                                      
        The termination occurred in the ABAP program "SAPLSWRR" in                       
         "SAP_WAPI_READ_CONTAINER".                                                      
        The main program was "SAPMSSY1 ".                                                                               
    The termination occurred in line 126 of the source code of the (Include)         
         program "LSWRRU03"                                                              
        of the source code of program "LSWRRU03" (when calling the editor 1260).         
    Regards,
    Deve

    Hi,
    Check following Notes might helps you.
    Note 1004384 - Note 905894; 925151 - Correction
    Note 925151 -     Dump or simple pricing after Note 905894
    regards,
    kaushal

  • 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.

  • Dump with error OBJECTS_OBJREF_NOT_ASSIGNED

    Hi,
    When I execute infospoke it is ending in Dump with the
    runtime error OBJECTS_OBJREF_NOT_ASSIGNED
    and exception  CX_SY_REF_IS_INITIAL..
    Please advice.
    Thanks,
    Vrrp

    Hi VRRP,
    check u'r sys version & sp level.......
                Import Support Package 15 for SAP NetWeaver 7.0 BI (BI Patch 14 or SAPKW70015) into your BI system. The Support Package is available once Note 991094"

  • BAPI_SAG_CHANGE: dump OBJECTS_OBJREF_NOT_ASSIGNED

    Hello,
    I have just written a custom report that calls BAPI_SAG_CHANGE.
    It works fine if run in foreground, but if run in background, with the same data, I get a dump:
    Runtime error
    OBJECTS_OBJREF_NOT_ASSIGNED
    Exception    
    CX_SY_REF_IS_INITIAL
    Some more infos:
    I'm working on a system with following software component:
              SAP_APPL    600    0021    SAPKH60021
    I have just applied two more SAP Notes, 1719540 and 1730058 (released with SAPKH60022) but error happen as well
    Here following I copy source code of my own form. Of course <fs_alv> is assigned and all fields are filled with their own value and just before this piece of code I have just done a CLEAR and a FREE of all tables/structures used by the BAPI
    wa_header-number  = <fs_alv>-ebeln.
    wa_headerx-number = <fs_alv>-ebeln.
    wa_schedule-item_no = <fs_alv>-ebelp.
    wa_schedule-sched_line = <fs_alv>-etenr.
    wa_schedule-quantity   = <fs_alv>-wemng.
    APPEND wa_schedule TO tb_schedule.
    wa_schedulex-item_no = <fs_alv>-ebelp.
    wa_schedulex-sched_line = <fs_alv>-etenr.
    wa_schedulex-quantity   = 'X'.
    APPEND wa_schedulex TO tb_schedulex.
    CALL FUNCTION 'BAPI_SAG_CHANGE'
    EXPORTING
    purchasingdocument
    = <fs_alv>-ebeln
    header         
    = wa_header
    headerx        
    = wa_headerx
    TABLES
    return         
    = tb_bapiret2
    schedule
    = tb_schedule
    schedulex      
    = tb_schedulex.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
    wait = 'X'.
    Here following I post the first page of the dump, copied from ST22:
    Short Text    Access via 'NULL' object reference not possible.   What happened?    Error in the ABAP Application Program     The current ABAP program "CL_MASTER_CONDITIONS_MM=======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_REF_IS_INITIAL', was not     caught in    procedure "IF_MASTER_CONDITIONS_MM~GET_PERSISTENT_DATA" "(METHOD)", nor was it     propagated by a RAISING clause.    Short Text    Access via 'NULL' object reference not possible.   What happened?    Error in the ABAP Application Program     The current ABAP program "CL_MASTER_CONDITIONS_MM=======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_REF_IS_INITIAL', was not caught in    procedure "IF_MASTER_CONDITIONS_MM~GET_PERSISTENT_DATA" "(METHOD)", nor was it     propagated by a RAISING clause.
    Do anybody have experience about this problem?
    Thank you!
    Guido

    Solved.
    I have just applied Sap Note 1694513 in order to solve the dump.
    Ciao,
    Guido

  • 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.

  • Dump while testing Idoc from WE19-OBJECTS_OBJREF_NOT_ASSIGNED

    Hi Experts,
    I am trying to Post inbound PO idoc from we19 tcode.
    MessageType:PORDCR1
    Idoctype:PORDCR102
    FM:BAPI_IDOC_INPUT1
    while testing this Idoc it is going dump.
    Runtime Errors     :    OBJECTS_OBJREF_NOT_ASSIGNED
    Short text            :    Access via 'NULL' object reference not possible.
    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 "PROCESS_COMPONENTS" "(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:
        You attempted to use a 'NULL' object reference (points to 'nothing')
        access a component (variable: "L_ITEM").
        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.
    Could you plz suggest how to resolve this issue.
    regards,
    Bhuvan.

    Hi,
    Please implement the OSS Note 1409498 (Relavent to your problem).
    I am sure it will resolve your issue.
    If not solving your than You can serch for relavent SAP note on SAP serivce market place.
    Regards,
    Lokesh.
    Edited by: Lokesh Tarey on Apr 15, 2010 2:31 PM
    Edited by: Lokesh Tarey on Apr 15, 2010 2:33 PM

  • Dump OBJECTS_OBJREF_NOT_ASSIGNED on service contract creation

    Hi All,
    I am working on crm upgrade from 7.0 to ehp3.
    After upgrade, I am facing the dump when creating the new service contract from New-->By selecting the Transaction type.
    Please find the below dump description.
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
    ABAP Program           CL_BT112H_S_ITEMLIST_CN01=====CP
    Application Component  CRM-BTX-CTR-SCO
    Short Text
         Access using a 'ZERO' object reference is not possible.
    Error analysis
        You are trying to access a component with a 'ZERO' object reference
        (points to 'nothing'). Variable: " ".
        An object reference must point to an object (an instance of a class)
        before it can be used to access a component. The reference has either
        never been set, or it was set to 'ZERO' with a CLEAR statement.
    Information on where terminated
        The termination occurred in ABAP program "CL_BT112H_S_ITEMLIST_CN01=====CP"
         in "ON_NEW_FOCUS".
        1 METHOD on_new_focus.
        2
        3   DATA lv_collection TYPE REF TO if_bol_bo_col.
        4   DATA lr_entity     TYPE REF TO cl_crm_bol_entity.
        5 ************************************************************
        6
    >>>>>   IF gr_tvc->gv_fast_mode_enabled EQ abap_true.
        8     trigger_coll_determ( focus_bo ).
        9   ELSE.
       10     lr_entity ?= focus_bo.
       11     TRY.
       12         lv_collection = lr_entity->get_related_entities( iv_
       13       CATCH cx_crm_genil_model_error cx_sy_ref_is_initial.
       14         RETURN.
       15     ENDTRY.
    Can anyone please help me in resolving the issue.
    Thanks & Regards,
    Chiru

    I'm afraid not, I'm still in ehp2, I just pointed to the note to ensure you started from there, I don't know if Nicolas Busson or Christian Drumm can help you from here keep us updated!

Maybe you are looking for