ST22 SCREEN

Hi,
When i login into production System i am getting the screen of ST22 screen. Please, let me know what is the reason.
Regards,
Deve

Don´t know what you mean.
ST22 is a transaction to display all the runtime errors that occured. What you maybe mean is that you actually have an error after logging on.
If that is the case, be more specific.
Markus

Similar Messages

  • BWLoadissue

    Hi forums,
                 Daily we are running 40 jobs in BW system.But half of the data loads are keeping on processing for a long time and some loads are failed.No short dumps occur in ST22 screen(BW and Source system).
                It is throwing errors like error7when sending Idoc,communicationerror (RFC error), Data not arrived into PSA properly etc.. which we found while viewing the monitor screen(Staus and Details tab).
       We are facing first time this kind of issue.Can any one help me  why it is happening.
    Regards,
    Charan.

    Hi,
    It may be resource issue at tht time...for the time being run the loads in differetnt timings and test it....
    And also chk the idocs in SM58 whther they r moving freely from R/3 to BW/BI system....
    rgds,

  • WHILE DELETING A SALE ORDER GETTING A RUNTIME ERROR " Screen: Illegal message"

    Hi Experts,
    While deleting a sales order giving run time error.  PFB runtime error details.
    If you know any OSS message, please let m know. I tried, but there is no luck.
    Short text
        Screen: Illegal message
    What happened?
        The current screen processing action was terminated since a situation
        occurred where the application could not continue.
        This is probably due to an error in the ABAP program or in the current
        screen.
    What can you do?
        Note which actions and input led to the error.
        For further help in handling the problem, contact your SAP administrator.
        You can use the ABAP dump analysis transaction ST22 to view and manage
        termination messages, in particular for long term reference.
    Error analysis
        The program attempted to issue a " " message during "Exit Command" processing.
        This is an illegal operation.
        The program was terminated.
        Screen name.............. "SAPMV45A"
        Screen number............ 4001
    How to correct the error
        The program must be modified to correct the error.
        The modification must be made in "Exit Command" processing.
        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)".
    Source Code Extract
    Line  SourceCde
        1 *---------------------------------------------------------------------*
        2 *       FORM YVBEP_LESEN                                              *
        3 *---------------------------------------------------------------------*
        4 *       Lesen der Tabelle YVBEP (nicht sortiert)                      *
        5 *---------------------------------------------------------------------*
        6 FORM YVBEP_LESEN USING US_POSNR
        7                        US_ETENR
        8               CHANGING CH_TABIX.
        9
       10   YVBEP = SPACE.
       11   YVBEP-MANDT = VBAK-MANDT.
       12   YVBEP-VBELN = VBAK-VBELN.
       13   YVBEP-POSNR = US_POSNR.
       14   YVBEP-ETENR = US_ETENR.
       15   READ TABLE YVBEP.
       16   IF SY-SUBRC > 0.
       17     MESSAGE E506 WITH US_POSNR US_ETENR.
       18   ENDIF.
    >>>>>   CH_TABIX = SY-TABIX.
       20
       21 ENDFORM.
    Could you please help on this issue.
    Thanks
    Srinu

    Hi Srinu,
    it looks like you got the error message Schedule line &1 &2 is missing in table YVBEP while deleting the sales order.
    It seems, that there are no SAP notes regarding this issue. Do you have this issue with all orders or with a single order?
    If only a single order causes this issue, maybe something was wrong during an update.
    If you get this error for many orders, then custom code (modification, enhancement, user exit in MV45AFZZ, ...) may be the reason for it.
    If you have no custom code in module pool SAPMV45A, then contact SAP for this issue.
    Regards,
    Klaus

  • Screen output without connection to user and other portal trouble

    I created filter. Saved it. If I tried edit it - it was allow. But after some time and after I used it in a query I trying edit the filter and can't do it! My rsplan portal page write to me:
    Screen output without connection to user., error key: RFC_ERROR_SYSTEM_FAILURE.
    ST22:
    Dynamic error:   DYNPRO_SEND_IN_BACKGROUND
    Short text:
         Screen output without connection to user.
    What happend?
         Error in the ABAP Application Program
         The current ABAP program "SAPLSTRD" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    user, transaction...
        Client.............. 100
        User................ "PI_JCO_RFC"
        Language Key........ "E"
        Transaction......... " "
        Program............. "SAPLSTRD"
        Screen.............. "SAPLSTRD 0302"
        Screen Line......... 0
        Information on caller of Remote Function Call (RFC):
        System.............. "########"
        Database Release.... 645
        Kernel Release...... 645
        Connection Type..... "E" (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
        Call Type........... "synchron and non-transactional (emode 0, imode 0)"
        Inbound TID.........." "
        Inbound Queue Name..." "
        Outbound TID........." "
        Outbound Queue Name.." "
    What happend? What I need to do? I try delete filter from query but it isn't make it editable.
    Another bug: I can delete this filter and can copy them into new filter. But when I delete it and try copy another filter to deleted technical name then system said that "element with same name already exist". How to delete the filter correctly?
    One more bug:
    I work with russian language. And on personalisation page of portal options I selected "Russian (Russia)" (There are variant simply "Russian" in list of langs but I tried it too with the same result) BUT I have only interface with russian lang and TEXTS of objects got for eng lang anymore (and in damp we can see that lang key = "E"). Where it must be corrected?
    And for last in this message: I can create an object or edit it but can see that object was last edited by PI_JCO_RFC. Is it right? So, how I will can see who change the object at last time?
    Help me please!

    >
    Deepti Maru wrote:
    > What object text you are talking about for which language is english but you want russian?
    I try describe it again.
    If I logon via SAPlogon with russian language in RSA1 I can see descriptions of objects for russian lang (and new objects which I will create will be with russian description if I enter it). In portal (rsplan) in personality I set russian language ang get the russian interface BUT it get descriptions for ENG and in this way I can't see any descriptions - only technical name because all objects was created with russian lang. So, what I need to do for get russian descriptions of objects in portal?
    And another trouble - when I create object (for example - aggregation level) in portal then I can't see descriptions of it in RSA1.
    And from this I have another question too. How I can (if it possible) use english interface and russian descriptions of objects in both portal and SAPLogon?

  • Error when calling a popup window in the initial screen of an application

    Hi,
        I am calling a popup window in the Initial screen to select the variant list.
    I am getting an error reference to Null Object reference.
    Here is the Error.
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED_NO
    Exception              CX_SY_REF_IS_INITIAL
    Date and Time          15.06.2007 10:00:16
    Short text
    Access via 'NULL' object reference not possible.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_WDR_MESSAGE_AREA===========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 "SUPPLY_VIEW_DATA" "(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.
    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
    Probably the only way to eliminate the error is to correct the program.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "OBJECTS_OBJREF_NOT_ASSIGNED_NO" "CX_SY_REF_IS_INITIAL"
    "CL_WDR_MESSAGE_AREA===========CP" or "CL_WDR_MESSAGE_AREA===========CM00Q"
    "SUPPLY_VIEW_DATA"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "SUPPLY_VIEW_DATA" "(METHOD)", or its possible occurrence must be declared in
    the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
    Looking for Ur valuable suggestions.
    Cheers,
    Sam

    Hi Sam,
    The correct code for creating a popup window will be:
      data lo_window_manager type ref to if_wd_window_manager.
      data lo_api_component  type ref to if_wd_component.
      data lo_window         type ref to if_wd_window.
      lo_api_component  = wd_comp_controller->wd_get_api( ).
      lo_window_manager = lo_api_component->get_window_manager( ).
      lo_window         = lo_window_manager->create_window(
                         window_name            = 'WINDOW_NAME'
    *                    title                  =
    *                    close_in_any_case      = abap_true
                         message_display_mode   = if_wd_window=>co_msg_display_mode_selected
    *                    close_button           = abap_true
                         button_kind            = if_wd_window=>co_buttons_okcancel
                         message_type           = if_wd_window=>co_msg_type_none
                         default_button         = if_wd_window=>co_button_ok
      lo_window->open( ).
    Hope this helps.
    Regards,
    Ram

  • SAPSQL_ARRAY_INSERT_DUPREC error in ST22

    Dear all,
    We have CI and 2 Dialog instanence in Prod Environment . 
    Oracle 10g , AIX and Ecc6.0 .
    past 2 days i am getting the below error on Application 1 error .
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Exception              CX_SY_OPEN_SQL_DB
    Date and Time          05.05.2010 00:30:57
    Short text
         The ABAP/4 Open SQL array insert results in duplicate database records.
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "SAPLSLIM_CNT" 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.
    Kindly suggest me
    Regards

    Hi,
    The dump doesn`t point to any job and the client where it's generated is 000:
    User and Transaction
        Client.............. 000
        User................ "SAPSYS"
        Language key........ "S"
        Transaction......... " "
        Transactions ID..... "4BF64BEB79450E9BE1000000C0A84866"
        Program............. "SAPLSLIM_CNT"
        Screen.............. "SAPMSSY0 1000"
        Screen line......... 6
    Information on where terminated
        Termination occurred in the ABAP program "SAPLSLIM_CNT" - in
         "SLIM_CNT_CONSOLIDATE_COUNTERS".
        The main program was "RSUVM018 ".
        In the source code you have the termination point in line 106
        of the (Include) program "LSLIM_CNTU02".
        The program "SAPLSLIM_CNT" was started as a background job.
        Job Name....... " "
        Job Initiator.. " "
        Job Number..... " "
        The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
        procedure "SLIM_CNT_CONSOLIDATE_COUNTERS" "(FUNCTION)", but it was neither
         handled locally nor declared
        in the RAISING clause of its signature.
        The procedure is in program "SAPLSLIM_CNT "; its source code begins in line
        1 of the (Include program "LSLIM_CNTU02 ".
    I've observed the dump in alternate days, not all days and without any periodicity.
    I've been looking for SAP notes in sapnet and in forums, but I didn't find anything similar.
    Thank you very much!!!
    BR,
    Martina

  • INDEX 0 SIZE 0 error mssage while opening the screen

    Hi Friends,
    I have error message for E-Seperation after approval from L1 and L2 managers, screen is displaying below error message. We have customized that application in EHP 4 EP 7.0, here is the reference screen attached. I tested in ST22 there is no Dumps are available. Please do the needful on priority.

    Hi Friends,
    I have error message for E-Seperation after approval from L1 and L2 managers, screen is displaying below error message. We have customized that application in EHP 4 EP 7.0, here is the reference screen attached. I tested in ST22 there is no Dumps are available. Please do the needful on priority.

  • Runtime Error in CA01 - Syntx error or generation error in a screen 1200.

    Hi,
    I am unable to identify the exact reson for this runtime error, please guid what i need to do to overcome this error.
    Transaction CA01.
    I am getting below Syntax Error in Screen 1200 of Prog SAPLCPDA
    Element CHANGE_RULE touches or overlaps other element
    Message no. 37315
    Please find below Error Log.
    Short text
        Syntx error or generation error in a screen.
    What happened?
        At the screen generation it was detected that a screen to be generated
        has a syntax error or could not be generated due to another error.
    What can you do?
        Note which actions and input led to the error.
        For further help in handling the problem, contact your SAP administrator
        You can use the ABAP dump analysis transaction ST22 to view and manage
        termination messages, in particular for long term reference.
    Error analysis
        Screen "SAPLCPDA" 1200 could not be generated.
    How to correct the error
        Rerport the error to SAP if it is a SAP screen.

    Hi,
    What are the possible reasons for getting this error.
    Runtime Error in CA01 - Syntx error or generation error in a screen 1200.
    Thanks in advance

  • ESS Persoanl Data Error(Screen output without connection to user)

    Hi All,
            When i am trying to Save my data in my ESS----->Personal Info -
    >Personal Data, i am getting below error, any body know how to resolve this issue, please let me know.
    Screen output without connection to user., error key: RFC_ERROR_SYSTEM_FAILURE:
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Screen output without connection to user., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
         at com.sap.xss.per.fc.persinfo.FcPersInfo.save(FcPersInfo.java:440)
         at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfo.save(InternalFcPersInfo.java:770)
         at com.sap.xss.per.fc.persinfo.FcPersInfoInterface.save(FcPersInfoInterface.java:186)
         at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfoInterface.save(InternalFcPersInfoInterface.java:275)
         at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfoInterface$External.save(InternalFcPersInfoInterface.java:435)
         at com.sap.xss.per.vc.reviewnavi.VcPersInfoReviewNavi.onEvent(VcPersInfoReviewNavi.java:213)
         at com.sap.xss.per.vc.reviewnavi.wdp.InternalVcPersInfoReviewNavi.onEvent(InternalVcPersInfoReviewNavi.java:171)
         at com.sap.xss.per.vc.reviewnavi.VcPersInfoReviewNaviInterface.onEvent(VcPersInfoReviewNaviInterface.java:115)
         at com.sap.xss.per.vc.reviewnavi.wdp.InternalVcPersInfoReviewNaviInterface.onEvent(InternalVcPersInfoReviewNaviInterface.java:124)
         at com.sap.xss.per.vc.reviewnavi.wdp.InternalVcPersInfoReviewNaviInterface$External.onEvent(InternalVcPersInfoReviewNaviInterface.java:200)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:533)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$600(FPMComponent.java:78)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseSaveEvent(FPMComponent.java:951)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.raiseSaveEvent(FPMComponent.java:1114)
         at com.sap.xss.per.vc.reviewnavi.VcPersInfoReviewNavi.next(VcPersInfoReviewNavi.java:227)
         at com.sap.xss.per.vc.reviewnavi.wdp.InternalVcPersInfoReviewNavi.next(InternalVcPersInfoReviewNavi.java:175)
         at com.sap.xss.per.vc.reviewnavi.ReviewNaviView.onActionNext(ReviewNaviView.java:153)
         at com.sap.xss.per.vc.reviewnavi.wdp.InternalReviewNaviView.wdInvokeEventHandler(InternalReviewNaviView.java:173)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
         at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1299)
         at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:326)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:868)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Screen output without connection to user., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
         at com.sap.xss.per.model.mac.HRXSS_PER_MAC.hrxss_Per_Save(HRXSS_PER_MAC.java:478)
         at com.sap.xss.per.model.mac.Hrxss_Per_Save_Input.doExecute(Hrxss_Per_Save_Input.java:137)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
         ... 64 more
    and after that i went to ST22 Transaction Code in my ECC System i found two types of DUMP errors,
    the below are those details.
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED_NO
    Exception              CX_SY_REF_IS_INITIAL
    Date and Time          09/09/2008 08:19:16
    Short text
    Access via 'NULL' object reference not possible.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLHRXSS_PER_MAC" 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 "HRXSS_PER_CLEANUP" "(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.
    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
    Probably the only way to eliminate the error is to correct the program.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "OBJECTS_OBJREF_NOT_ASSIGNED_NO" "CX_SY_REF_IS_INITIAL"
    "SAPLHRXSS_PER_MAC" or "LHRXSS_PER_MACU04"
    "HRXSS_PER_CLEANUP"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "HRXSS_PER_CLEANUP" "(FUNCTION)", or its possible occurrence must be declared
    in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
    System environment
    SAP-Release 700
    Application server... "ERPDEV01"
    Network address...... "10.88.1.6"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "ERPDEV01"
    Database type..... "MSSQL"
    Database name..... "DE1"
    Database user ID.. "de1"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Oct 23 2007 00:33:51"
    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version. "SQL_Server_8.00 "
    Patch level. 133
    Patch text.. " "
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
    NT 6.0"
    Memory consumption
    Roll.... 16192
    EM...... 4189840
    Heap.... 0
    Page.... 0
    MM Used. 1229856
    MM Free. 2957360
    User and Transaction
    Client.............. 210
    User................ 937048
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "68211f907e6911ddbfef005056833439"
    Program............. "SAPLHRXSS_PER_MAC"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
    System.............. "########"
    Database Release.... 645
    Kernel Release...... 645
    Connection Type..... "E" (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchron and non-transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
    Client.............. "###"
    User................ "############"
    Transaction......... " "
    Call Program........." "
    Function Module..... "HRXSS_PER_CLEANUP"
    Call Destination.... "<unknown>"
    Source Server....... "ERPDEV04"
    Source IP Address... "10.88.1.9"
    Additional information on RFC logon:
    Trusted Relationship " "
    Logon Return Code... 0
    Trusted Return Code. 0
    Note: For releases < 4.0, information on the RFC caller are often
    only partially available.
    Information on where terminated
    Termination occurred in the ABAP program "SAPLHRXSS_PER_MAC" - in
    "HRXSS_PER_CLEANUP".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 13
    of the (Include) program "LHRXSS_PER_MACU04".
    The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
    procedure "HRXSS_PER_CLEANUP" "(FUNCTION)", but it was neither handled locally
    nor declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLHRXSS_PER_MAC "; its source code begins in
    line
    1 of the (Include program "LHRXSS_PER_MACU04 ".
    Source Code Extract
    Line
    SourceCde
    1
    FUNCTION hrxss_per_cleanup.
    2
    3
    ""Local interface:
    4
    *"  EXPORTING
    5
    *"     VALUE(MESSAGES) TYPE  BAPIRETTAB
    6
    7
    8
    CALL METHOD mac_adapter->cleanup
    9
       IMPORTING
    10
         messages = messages.
    11
    12
    TRY.
    >>>>>
    CALL METHOD xss_adapter->cleanup
    14
    15
    CATCH CX_HRPA_VIOLATED_ASSERTION .
    16
    ENDTRY.
    17
    18
    ENDFUNCTION.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    2
    SY-TABIX
    0
    SY-DBCNT
    0
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    CPIC and RFC Control
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20080909
    SY-UZEIT
    081916
    SY-XPROG
    SAPLHRXSS_PER_MAC
    SY-XFORM
    HRXSS_PER_CLEANUP
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    4 FUNCTION     SAPLHRXSS_PER_MAC                   LHRXSS_PER_MACU04                      13
    HRXSS_PER_CLEANUP
    3 FORM         SAPLHRXSS_PER_MAC                   LHRXSS_PER_MACU04                       1
    HRXSS_PER_CLEANUP
    2 FORM         SAPMSSY1                            SAPMSSY1                               85
    REMOTE_FUNCTION_CALL
    1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
    %_RFC_START
    Chosen variables
    Name
    Val.
    No.       4 Ty.          FUNCTION
    Name  HRXSS_PER_CLEANUP
    MESSAGES
    Table[initial]
    %_DUMMY$$
    2222
    0000
    0000
    0000
    No.       3 Ty.          FORM
    Name  HRXSS_PER_CLEANUP
    SYST-REPID
    SAPLHRXSS_PER_MAC
    5454455555545544422222222222222222222222
    310C82833F052FD1300000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    %_%_MESSAGES
    Table[initial]
    No.       2 Ty.          FORM
    Name  REMOTE_FUNCTION_CALL
    %_DUMMY$$
    2222
    0000
    0000
    0000
    SY-REPID
    SAPMSSY1
    5454555322222222222222222222222222222222
    310D339100000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    SYST-REPID
    SAPMSSY1
    5454555322222222222222222222222222222222
    310D339100000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    HEADER
    000000000000
    000000000000
    TYPE
    3
    0000
    3000
    SY-XPROG
    SAPLHRXSS_PER_MAC
    5454455555545544422222222222222222222222
    310C82833F052FD1300000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    RC
    0
    0000
    0000
    SY-XFORM
    HRXSS_PER_CLEANUP
    455555545544444552222222222222
    82833F052F3C51E500000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    %_SPACE
    2
    0
    0
    0
    No.       1 Ty.          MODULE (PBO)
    Name  %_RFC_START
    %_PRINT
    000                                                                                0###
    2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    RFCTYPE_INTERNAL
    3
    0000
    3000
    Internal notes
    The termination was triggered in function "method_call_iref"
    of the SAP kernel, in line 2207 of the module
    "//bas/700_REL/src/krn/runt/abmethod.c#8".
    The internal operation just processed is "METH".
    Internal mode was started at 20080909081916.
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    SAP (R) - R/3(TM) Callstack, Version 1.0
    Copyright (C) SAP AG. All rights reserved.
    Callstack without Exception:
    App       : disp+work.EXE (pid=3864)
    When      : 9/9/2008 8:19:16.162
    Threads   : 2
    Computer Name       : ERPDEV01
    User Name           : SAPServiceDE1
    Number of Processors: 4
    Processor Type: AMD64 Family 15 Model 65 Stepping 2
    Windows Version     : 5.2 Current Build: 3790
    State Dump for Thread Id d90
    FramePtr         ReturnAd         Param#1          Function Name
    0000000007d1bb20 0000000077d704bf 000000003879a800 ntdll!ZwWaitForSingleObject
    0000000007d1bbc0 0000000001722981 0000000000000180 kernel32!WaitForSingleObjectEx
    0000000007d1be10 00000000006110c5 0000000000000001 disp+work!NTDebugProcess [ntstcdbg.c (501)]
    0000000007d1be40 0000000000af8e9c 0000000000000001 disp+work!CTrcStack [dptstack.c (182)]
    0000000007d1be90 0000000000afe0c0 0000000000000001 disp+work!rabax_CStackSave [abrabax.c (7091)]
    0000000007d1c870 000000000081768a 0000000001adae28 disp+work!ab_rabax [abrabax.c (1231)]
    0000000007d1c8d0 0000000000830b12 0000000000000000 disp+work!method_call_iref [abmethod.c (2215)]
    0000000007d1ca50 0000000000a0bac7 0000000000000008 disp+work!ab_extri [abextri.c (554)]
    0000000007d1caa0 0000000000ac830c 0000000000000008 disp+work!ab_xevent [abrunt1.c (281)]
    0000000007d1cb30 000000000066f348 0000000000000008 disp+work!ab_dstep [abdynpro.c (492)]
    0000000007d1ccb0 0000000000672f1d 000007fe571fc890 disp+work!dynpmcal [dymainstp.c (2403)]
    0000000007d1cd40 000000000067291a 000007fe571414a0 disp+work!dynppbo0 [dymainstp.c (543)]
    0000000007d1cdf0 00000000006320d5 0000000000000000 disp+work!dynprctl [dymainstp.c (360)]
    0000000007d1fc30 00000000004d7393 0000000000000003 disp+work!dynpen00 [dymain.c (1629)]
    0000000007d1feb0 000000000042d5a6 000000000a595080 disp+work!TskhLoop [thxxhead.c (4470)]
    0000000007d1fee0 000000000040108d ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1121)]
    0000000007d1ff10 00000000019c7dd1 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)]
    0000000007d1ff70 0000000077d5964c 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]
    0000000007d1ffa0 0000000000000000 00000000019c7c60 kernel32!BaseProcessStart
    State Dump for Thread Id 1e0c
    FramePtr         ReturnAd         Param#1          Function Name
    000000000edffe40 0000000077d5f691 0000000007d86460 ntdll!NtFsControlFile
    000000000edffeb0 00000000018ae00f 0000000000000000 kernel32!ConnectNamedPipe
    000000000edfff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)]
    000000000edfff70 0000000077d6b6da 0000000077d6b6a0 msvcrt!endthreadex
    000000000edfffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart
    List of ABAP programs affected
    Index
    Typ
    Program
    Group
    Date
    Time
    Size
    Lang.
    0
    Prg
    SAPMSSY1
    0
    04/11/2005
    09:27:15
    22528
    E
    1
    Prg
    SAPLSYST
    1
    02/13/2005
    17:31:56
    35840
    E
    2
    Prg
    SAPLHRXSS_PER_MAC
    2
    07/03/2008
    12:14:05
    58368
    E
    3
    Prg
    CX_SY_REF_IS_INITIAL==========CP
    3
    07/05/2005
    13:10:16
    10240
    E
    4
    Typ
    SCX_SRCPOS
    0
    05/18/2004
    14:07:11
    2048
    5
    Prg
    CX_DYNAMIC_CHECK==============CP
    5
    07/05/2005
    13:10:16
    10240
    E
    6
    Prg
    CX_ROOT=======================CP
    6
    02/06/2008
    15:43:48
    11264
    E
    7
    Prg
    CX_NO_CHECK===================CP
    7
    07/05/2005
    13:10:16
    10240
    E
    8
    Prg
    CX_SY_NO_HANDLER==============CP
    8
    07/05/2005
    13:10:16
    10240
    E
    9
    Typ
    SYST
    0
    09/09/2004
    14:18:12
    31744
    Directory of Application Tables
    Name                                     Date       Time       Lngth
    Val.
    Program  SAPMSSY1
    SYST                                       /  /       :  :     00004612
    \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0\0
    ABAP Control Blocks (CONT)
    Index
    Name
    Fl
    PAR0
    PAR1
    PAR2
    PAR3
    PAR4
    PAR5
    PAR6
    Source Code
    Line
    243
    FUNC
    03
    001F
    LHRXSS_PER_MACU03
    1
    244
    PAR2
    02
    0000
    001F
    C000
    LHRXSS_PER_MACU03
    1
    246
    FUNC
    13
    0003
    LHRXSS_PER_MACU03
    1
    247
    PAR2
    01
    0000
    0014
    C001
    LHRXSS_PER_MACU03
    1
    249
    FUNC
    FF
    0000
    LHRXSS_PER_MACU03
    1
    250
    ENDF
    00
    0000
    LHRXSS_PER_MACU03
    1
    251
    00
    0000
    LHRXSS_PER_MACU03
    1
    252
    STCK
    02
    C001
    LHRXSS_PER_MACU03
    1
    253
    CPOP
    00
    0000
    LHRXSS_PER_MACU03
    1
    254
    00
    0000
    LHRXSS_PER_MACU03
    1
    255
    FUNP
    3E
    0000
    0014
    8000
    0000
    8000
    0000
    0000
    LHRXSS_PER_MACU04
    1
    259
    FUNP
    80
    0000
    0000
    0000
    0000
    0000
    0000
    0000
    LHRXSS_PER_MACU04
    1
    >>>>>
    METH
    03
    0000
    0000
    8006
    0000
    0000
    0000
    0000
    LHRXSS_PER_MACU04
    13
    267
    PAR2
    00
    0000
    0001
    0000
    LHRXSS_PER_MACU04
    13
    269
    FUNE
    00
    0000
    LHRXSS_PER_MACU04
    18
    270
    00
    0000
    LHRXSS_PER_MACU04
    18
    271
    PERP
    00
    0000
    LHRXSS_PER_MACU04
    1
    272
    FUNC
    03
    E844
    LHRXSS_PER_MACU04
    1
    273
    FUNC
    03
    0020
    LHRXSS_PER_MACU04
    1
    274
    FUNC
    13
    0003
    LHRXSS_PER_MACU04
    1
    Second Dump
    Runtime Errors         DYNPRO_SEND_IN_BACKGROUND
    Date and Time          09/09/2008 08:19:15
    Short text
    Screen output without connection to user.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSTRD" 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
    During background processing, the system attempted to send a
    screen to a user.
    Current screen: "SAPLSTRD " 0351.
    How to correct the error
    If the error occurred in your own ABAP program or in an SAP
    program you modified, try to remove 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:
    "DYNPRO_SEND_IN_BACKGROUND" " "
    "SAPLSTRD" or " "
    "SYSTEM-EXIT"
    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... "ERPDEV01"
    Network address...... "10.88.1.6"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "ERPDEV01"
    Database type..... "MSSQL"
    Database name..... "DE1"
    Database user ID.. "de1"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Oct 23 2007 00:33:51"
    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version. "SQL_Server_8.00 "
    Patch level. 133
    Patch text.. " "
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
    NT 6.0"
    Memory consumption
    Roll.... 16192
    EM...... 12569520
    Heap.... 0
    Page.... 131072
    MM Used. 8307376
    MM Free. 4259072
    User and Transaction
    Client.............. 210
    User................ 937048
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "68211f907e6911ddbfef005056833439"
    Program............. "SAPLSTRD"
    Screen.............. "SAPLSTRD 0351"
    Screen Line......... 0
    Information on caller of Remote Function Call (RFC):
    System.............. "########"
    Database Release.... 645
    Kernel Release...... 700
    Connection Type..... "E" (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchron and non-transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Nam

    Hello Abhiram,
    Please i request weather you have assign 0105 - Communication infotype to ESSuser and
    check the following JCos has been configured.
    SAP_R3_Financials
    SAP_R3_Financials_Metadata
    SAP_R3_HumanResources
    SAP_R3_HumanResources_MetaData
    SAP_R3_SelfServiceGenerics
    SAP_R3_SelfServiceGenerics_MetaData
    SAP_R3_Travel
    SAP_R3_Travel_MetaData
    SAP_R3_SelfServiceGenerics_MetaDataFIN
    SAP_R3_SelfServiceGenericsFIN
    let me know this
    points if problem solved
    please close thread if problem solved
    thanksyou,
    regards
    Vijai

  • Screen output without connection to user - Work flow

    Hi,
    i  have created a workflow, it has a task which refers to a method which call a BDC in N mode, but workitem is not generating, in event trace showing RFC status 'Screen output without connection to user'.
    Same time i observed in ST22 for any dumps, as it is giving this error 'DYNPRO_SEND_IN_BACKGROUND'.
    Please suggest how to solve. Thanks in advance.
    BR,
    Rajani

    Hi  Vijay shah /Rick Bakker ,
    As i am on leave from last 2 days, sorry for delay in response.
    As the work flow tasks and what ever the methods i developed are working as per requried.
    But  after each step by step analysis i founn every usefull information regarding the background type activity options.
    Solution :
    In background type activity step, in details tab  we have option of ->Advance With Immediate Dialog flag is set to X, due to this system checking for user interaction.
    Because of this its creating problem.  After unmarking the falg i am able to execute the task in background successfully
    with out any problem.
    Once again sorry for delay in reponse 
    BR,
    Rajani

  • LSO PORTAL - SCREEN OUTPUT WITHOUT CONNECTION TO USER

    Hi All,
    When I try to book a participant for a course in Learning Solutions Portal, my event/business object gets triggered and i get a SWEL entry, but the RFC status in SWEL gives error saying Screen output without connection to user because of which my workflow attached to the business object is not getting triggered.
    Any input as how to solve this error or anything related will be of great help and highly appreciated.
    Thanks in Advance,
    Vaishnavi Varadarajan

    This is probably because the system is trying to output something to screen. This is for an RFC (user) just not possible. When you do this, also have a look at ST22 (short dump). If my assumption is true, then you will also have a dump stating something like: DYNPRO_SEND_IN_BACKGROUND.
    So check what the 'coding' is trying to do, and then avoid doing this. Possibly there is a call screen or a pop-up coming along which just can't be processed in background / by RFC.

  • Screen output without connection to user error in Form 16 ESS

    Hi ,
    We are implementing Form 16 in benefits and pay section of ESS and getting error ' screen output without conection to user '.
    We are using ESS 1.41 BP and EP 7.0 EHP 4 version  , standard ESS / MSS.
    Can you please help me fix this issue .  Is this because of some setting in EP or something missing in backend .
    The tcode st22 in backend also giving similar error ' dynpro _send ...etc etc error '.
    I did go through some forums asking to implement SAP Note for this and i have asked my basis team to look into that.
    Need your help in understanding the issue , why this error  and fix for this problem ..
    Thanks and regards,
    Sai

    Hi Bala
    I am very thankful to your quick reply.
    i have  already checked the dump in st22 , From the dump i understand that while executing the
    function module it is refering some NULL value. I have asked my abap to look in to this.
    Bala is there any other setting we have to do , other than tracing the function module.
    Currently EA-HR patch level is 28.
    Regards
    Surya

  • Screen become blank during the Manual Target Group creation

    Hi SAP,
    In the Marketing Segmentation, there is an option to allow the manual Target Group creation. I have a list of 5000 BP and I upload it via "Import Business Partner". It is just 5krecords and the screen goes blank. We have tried several times and encountering the same thing which there is no enhancement applied. Any idea if there is limit on BP to be uploaded?

    Hi Subhashish,
    High Volume Segmentation is recommended for segmentation activities for more than 500.000 BPs. In  your case Classic Segmentation fits perfectly.
    Please read the SAP documentation for more information:
    Segmentation - SAP Library
    Furthermore since the Import Business Partner functionality is not Java based this cannot be a Java problem.
    Do you receive a dump in transaction "st22" after trying the import?
    Regards,
    Markus

  • Statement "CALL SCREEN" is not allowed in this form.

    Hi,
    Could anyone identify the short dump.
    Statement "CALL SCREEN" is not allowed in this form.
    There is probably an error in the program
    "SAPLKKBL".
    This program is triggered in the update task. There, the
    following ABAP/4 statements are not allowed:
    -  CALL SCREEN
    -  CALL DIALOG
    -  CALL TRANSACTION
    -  SUBMIT
    Error in
    "POSTING_ILLEGAL_STATEMENT" " "
    "SAPLKKBL" or "LKKBLU01"
    "K_KKB_LIST_DISPLAY"
    Regards
    Manohar S

    Short text
    Statement "CALL SCREEN" is not allowed in this form.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLKKBL" 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
    There is probably an error in the program
    "SAPLKKBL".
    This program is triggered in the update task. There, the
    following ABAP/4 statements are not allowed:
    -  CALL SCREEN
    -  CALL DIALOG
    -  CALL TRANSACTION
    |    -  SUBMIT       
    Information on where terminated
    Termination occurred in the ABAP program "SAPLKKBL" - in "K_KKB_LIST_DISPLAY".
    The main program was "RSM13000 ".
    In the source code you have the termination point in line 441
    of the (Include) program "LKKBLU01".
    |    The program "SAPLKKBL" was started in the update system.    
    This is the dump

  • SCreen Painter working not correctly.

    Hi,
    In se53 when we go to screen painter it's not coming properly..
    some line is coming.
    and we got EU_SCRP_WN32 : timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'  error message.
    we have sap gui 710 with patch level 7.
    the dumpfile also generated.
    Runtime Errors         STORAGE_PARAMETERS_WRONG_SET
    Date and Time          22.07.2008 12:44:27
    Short text
    The system is configured incorrectly.
    What happened?
    The current program had to be terminated because of an
    error when installing the R/3 System.
    The program had already requested 453411792 bytes from the operating
    system with 'malloc' when the operating system reported after a
    further memory request that there was no more memory space
    available.
    What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
    In the system profile, set the parameters
    -abap/heap_area_dia and
    -abap/heap_area_nondia
    to a maximum of 453411792. To be on the safe side, reduce the value by 10,000,
    000.
    Then restart the SAP system.
    Error analysis
    When the program was running, it was established that more
    memory was needed than the operating system is able safely
    to provide. To avoid a system crash, you must prevent this
    situation from occurring.
    Last error logged in SAP kernel
    Component............ "EM"
    Place................ "SAP-Server mtw02sdec01_DE7_00 on host mtw02sdec01 (wp
    1)"
    Version.............. 37
    Error code........... 7
    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
    Description.......... " "
    System call.......... " "
    Module............... "emxx.c"
    Line................. 1881
    The error reported by the operating system is:
    Error number..... " "
    Error text....... " "
    How to correct the error
    Report the error to the group responsible for installing your
    R/3 System.
    Please help.
    regards
    deepak

    Dump is telling you what to do...
    Review abap/heap_area_dia and abap/heap_area_nondia
    I presume you try that before posting right?...
    Whats the issue then?
    Regards
    Juan

Maybe you are looking for