EAM 10.1 Change in runtime error on FF Logon

Hi,
We have configured Decentralized Firefighter in AC 10.1 and connected the plug in system.  We have confirmed that FF is working but there are intermittent access issues with FF Logon.
When a user executes /n/grcpi/gria_eam they get the FF Login and once they click on the Login button, they get the following error:
The other interesting fact is that two users with the exact same access have issues on different FF id's that are assigned.
We have been looking at the user groups assigned to both the end user and the FF ids and there is some validity in that being part of the issue.  When we change user group assignments we do get some differences in which FF ids work for users and which ones don't but this is inconsistent.
We are on ECC6 with the latest Plug-ins and GRC 10.1 at the highest SP level.
If anyone can offer any advice on where to look or what to try it would be greatly appreciated.

Hi Alessandro,
There are no logs in ST22 or SLG1 for this error in either the GRC client or the Plug in.  I have a developer trying to debug for me as well as we speak and there appears to be an issue in the temporary table.  I will keep you updated on what we find.
At this stage, I am checking the setup with the document Anji sent a link to as well.
Regards,
Sonia

Similar Messages

  • Java iview Runtime error in Portal Logon

    hi
    I login portal with
    http://<ipaddress>:50000/irj/portal
    Java iView Runtime
    An exception occured while processing your request.
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
    If this situation persists, please contact your system administrator.
    Can any one help me,,,how to sort this error.
    Regards
    sushma

    Hi Sushma,
    It seems that there are problems with permissions in Security Zones.
    Check this links below to know more:
    http://help.sap.com/saphelp_nw04/helpdata/en/25/85de55a94c4b5fa7a2d74e8ed201b0/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/ee/acd8403e37762ae10000000a155106/content.htm
    Thanks
    Mihir

  • While trying to change a BOM with transaction CS02, a runtime error appears

    While trying to change a BOM with transaction CS02, a runtime error appears.
    In intial screen he entered material ,plant BOM usage and date valid from  after executed then id displayed item list in that he wantu2019s delete one item, he has been deleted selected item after that when he was saving he is getting runtime error
    Developer trace
    ABAP Program SAPLKED1_WRITE_CE4_BPS1                 .
    Source LKED1_WRITE_CE4_BPS1U01                  Line 30.
    Error Code SAPSQL_ARRAY_INSERT_DUPREC.
    Module  $Id: //bas/640_REL/src/krn/runt/absapsql.c#17 $ SAP.
    Function HandleRsqlErrors Line 775.
    RABAX: level LEV_RX_STDERR completed.
    RABAX: level LEV_RX_RFC_ERROR entered.
    RABAX: level LEV_RX_RFC_ERROR completed.
    RABAX: level LEV_RX_RFC_CLOSE entered.
    RABAX: level LEV_RX_RFC_CLOSE completed.
    RABAX: level LEV_RX_IMC_ERROR entered.
    RABAX: level LEV_RX_IMC_ERROR completed.
    RABAX: level LEV_RX_DATASET_CLOSE entered.
    RABAX: level LEV_RX_DATASET_CLOSE completed.
    RABAX: level LEV_RX_RESET_SHMLOCKS entered.
    RABAX: level LEV_RX_RESET_SHMLOCKS completed.
    RABAX: level LEV_RX_ERROR_SAVE entered.
    RABAX: level LEV_RX_ERROR_SAVE completed.
    RABAX: level LEV_RX_ERROR_TPDA entered.
    RABAX: level LEV_RX_ERROR_TPDA completed.
    RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
    RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
    RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
    RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
    RABAX: level LEV_RX_END entered.
    RABAX: level LEV_RX_END completed.
    RABAX: end RX_RFC
    In sm21
    Perform rollback
    Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred
         Short dump "090618 110101 donalda 11557 " generated
    Runtime Error          SAPSQL_ARRAY_INSERT_DUPREC
    Exception              CX_SY_OPEN_SQL_DB
           Occurred on     18.06.2009 at   11:01:01
    The ABAP/4 Open SQL array insert results in duplicate database records.
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLKED1_WRITE_CE4_BPS1" had to be terminated because
    one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that 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
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "RKE_WRITE_CE4__BPS1" "(FUNCTION)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
    situation, processing does not terminate, but SY-SUBRC is set to 4.)
    How to correct the error
    The exception must either be prevented, caught within the procedure
    "RKE_WRITE_CE4__BPS1"
    "(FUNCTION)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    Use an ABAP/4 Open SQL array insert only if you are sure that none of
    the records passed already exists in the database.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC
    "SAPLKED1_WRITE_CE4_BPS1" or "LKED1_WRITE_CE4_BPS1U01"
    "RKE_WRITE_CE4__BPS1"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
       To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
       To obtain this, call the system log with Transaction SM21
       and select the "Print" function to print out the relevant
       part.
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, you can either use the "PRINT" command in the editor or
       print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.

    Hi ,
    you are getting beacuse u are trying to do mass update to database.
    Please check that below note are applicable to your system.
    Note 453313 - DBIF_RSQL_ERROR_INTERNAL for mass insert
    Note 869534 - AFS MRP doesn't work properly with all BOM item categories
    Thanks Rishi Abrol

  • Crystal Report runtime error while changing Data Source Location

    Dear All
    We are using "Crystal reports for SAP Business one".The Crystal reports version is 12.1.
    We built a report in another database with another server.
    As we are importing the report in another database of another server,
    I am not able to change the Data Source location.
    When I am trying to change it,it gives Runtime error and closed automatically.
    How can i resolve and change the data source location?

    hi kambadasan,
    is your CR version the same from which you design the report and to the another server? also did you import your report directly to SBO without changing the data source first? in the case you should update first your Data Source in Crystal Report IDE before importing it to SBO.
    regards,
    Fidel

  • Runtime error when updating service item with BAPI PO CHANGE

    Hi,
    I get rutime error TABLE_INVALID_INDEX after calls:
    BAPI_PO_CHANGE-> PROCESS_NON_INTEGRATED_COMP-> CHANGE_PO_SRV_ITEM -> MS_CHANGE_SERVICE_PACKAGE_PO -> ROW_IN_PO -> CHECK_ACC_PO -> MS_CHANGE_ACCASS_PO -> ESKL_UPDATE.
    the reason is, that ESKL internal table is empty, so the function retrieves last entry index, there is no entry , so  sy-tabix = 0 , and function updates with index 0, which causes the runtime error. I dont know why it is empty, maybe I should copy this table gt_srvaccess from BAPI_PO_GETDETAIL  to BAPI_PO_CHANGE.
    This error appears only in mode KNTIMOD=2 (Multikontierung), not in KNTIMOD=1(Einfachkontierung), so just when ESKL contains more lines for one PACKAGE_NUMBER.
    I am just updating the value ordered to be equal value delivered to close the PO, or delete the item in case ordered >0 and deliveded = 0.
    Here is my part of code:
    *close existing PO's by changing the value ordered to the value receipted
                move 'X' to w_change_flag.
                w_hdrx-po_number = 'X'.
                if w_total-val_gr_for is not initial.
                  w_itemx-delete_ind = 'X'.
                  append w_itemx to gt_itemx.
                  clear: w_itemx.
                  read table gt_services into w_service2 with key pckg_no = w_item-pckg_no.
                  if sy-subrc eq 0.                                                                               
    read table gt_services into w_service with key pckg_no = w_service2-subpckg_no.
                    if sy-subrc eq 0.                                                                               
    move: w_total-val_gr_for to w_service-quantity,
                            '1'                to w_service-gr_price.
                      modify gt_services index sy-tabix from w_service transporting quantity gr_price.
                    endif.
                  endif.
                else. "nothing delivered yet, set deletion flag
                  w_itemx-po_item = w_item-po_item.
                  w_itemx-delete_ind = 'X'.
                  append w_itemx to gt_itemx.
                  clear: w_itemx.
                  w_item-delete_ind = 'L'.
                  modify gt_item index w_count from w_item transporting delete_ind.
                endif.
        call function 'BAPI_PO_CHANGE'
          exporting
            purchaseorder = w_ekko-ebeln
            poheader      = w_header
            poheaderx     = w_hdrx
            testrun       = w_testrun_flag
            no_messaging  = 'X'
          importing
            expheader     = w_exphdr
          tables
            return        = gt_return1
            poitem        = gt_item
            poitemx       = gt_itemx
            poservices    = gt_services.
    Thanks, please help.
    regards Rob
    Edited by: xsmid4 on Nov 2, 2011 11:49 AM
    Edited by: xsmid4 on Nov 2, 2011 12:08 PM

    Hi,
    Take a look at OSS Note 827731. It might be helpful to you.
    [ Link for Note 827731|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=827731]
    Regards,
    koolspy.

  • ABAP runtime error in FBV2 Change parked document using workflow

    Hi,
    When selecting screen template variant in tcode FBV2 change parked document, I get abap runtime error DYNPRO_NOT_FOUND
    Tcode- FBV2
    Program- SAPLF040
    Screen- SAPLF040  0310
    Main Program - SAPMF05V
    Information on were terminated.
    Program SAPLF040 - in " %_CTL_END "
    In the source code you have the termination point in line 50 of the (Include) program " <SYSINI> "
    How can we solve this error. We are on ECC6 with release 600.
    Thanks,
    Mark

    Hi Mark,
    We have this same issue in transaction F-65
    I believe that when a new screen template is configured, a new screen is generated within function group F040. A later action (applying a hotpack??) has removed this screen, but the config (in table T021D) still points the processing to the screen even though it has been removed.
    Did you find a solution? We want to get the screen back as it is still valid to use this screen template in the business
    Thanks
    Ben

  • Portal Runtime Error when changinG Welcome Message

    Hi Experts,
    Here is the what I did :
    Downloaded com.sap.portal.navigation.afp.masthead WAR file.
    Imported to NWDS with a name com.sap.portal.navigation.afp.masthead.cust
    In the AFPMasthead_nls_en.properties and AFPMasthead_nls prefixed the Welcome Messgae text(WELCOME_MESSAGE with a text 'Sandbox'
    Changed the application name in Portalapp.xml from com.sap.portal.navigation.afp.masthead to com.sap.portal.navigation.afp.masthead.cust.
    Build and Deployed the WAR.
    In portal created new Iview with com.sap.portal.navigation.afp.masthead.cust WAR for Masthead and made standard invisible in AFP.
    It gives below runtime error:
    Exception ID:10:51_04/04/14_0006_4730550
    [EXCEPTION]
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Application name : com.sap.portal.navigation.afp.masthead.cust
    Please see the attached file for details of exception.
    Urgent help is needed, points awarded to useful answers.
    Regards,
    Sumit Oberoi

    HI Saar,
    I have checked this document but not clear about step 3. Where to get the Masthead.java, MastHeadBean.java, Utils.java files from.
    Also my project does not have mastHeadBin.java . I have also checked this in the unzipped WAR.
    Please suggest.
    Regards,
    Sumit Oberoi

  • Runtime Error Using BAPI SALESORDER CHANGE

    Hi,
    I was trying to use the BAPI_SALESORDER_CHANGE to change 'Material Group 1' field. When executing the program, it kept on failing with this runtime error 'CALL_FUNCTION_CONFLICT_LENG'. Below is my codes and also the error analysis found in ST22.
    Kindly please let me know my program errors.
    Thanks much.
    CODES :-
    DATA: l_vbeln TYPE bapivbeln-vbeln,
    l_hx LIKE bapisdhead1x,
    l_r TYPE STANDARD TABLE OF bapiret2 WITH HEADER LINE,
    l_i TYPE STANDARD TABLE OF bapisditem WITH HEADER LINE,
    l_ix TYPE STANDARD TABLE OF bapisditemx WITH HEADER LINE,
    l_success(1) TYPE c VALUE 'Y'.
    l_vbeln = '0000707671'.
    l_hx-updateflag = 'U'.
    l_i-itm_number = '000010'.
    l_i-prc_group1 = 'Y'.
    APPEND l_i.
    l_ix-itm_number = '000010'.
    l_ix-updateflag = 'U'.
    l_ix-prc_group1 = 'X'.
    APPEND l_ix.
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
    EXPORTING
    salesdocument = l_vbeln
    ORDER_HEADER_IN =
    order_header_inx = l_hx
    SIMULATION =
    BEHAVE_WHEN_ERROR = ' '
    INT_NUMBER_ASSIGNMENT = ' '
    LOGIC_SWITCH =
    NO_STATUS_BUF_INIT = ' '
    TABLES
    return = l_r
    order_item_in = l_i
    order_item_inx = l_ix
    PARTNERS =
    PARTNERCHANGES =
    PARTNERADDRESSES =
    ORDER_CFGS_REF =
    ORDER_CFGS_INST =
    ORDER_CFGS_PART_OF =
    ORDER_CFGS_VALUE =
    ORDER_CFGS_BLOB =
    ORDER_CFGS_VK =
    ORDER_CFGS_REFINST =
    SCHEDULE_LINES =
    SCHEDULE_LINESX =
    ORDER_TEXT =
    ORDER_KEYS =
    CONDITIONS_IN =
    CONDITIONS_INX =
    EXTENSIONIN =
    NFMETALLITMS =
    LOOP AT l_r.
    IF l_r-type <> 'S'.
    l_success = 'N'.
    EXIT.
    ENDIF.
    CLEAR l_r.
    ENDLOOP.
    IF l_success = 'Y'.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
    WAIT =
    IMPORTING
    RETURN =
    WRITE: / 'Update successful'.
    ELSE.
    WRITE: / 'Update fail'.
    ENDIF.
    Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was
    not caught and
    therefore caused a runtime error.
    The reason for the exception is:
    The call to the function module "BAPI_SALESORDER_CHANGE" is incorrect:
    In the function module interface, you can specify only
    fields of a specific type and length under "ORDER_HEADER_INX".
    Although the currently specified field
    "L_HX" is the correct type, its length is incorrect.

    Thanks ALL. Here is the amended program that works fine :-
    DATA: l_vbeln TYPE bapivbeln-vbeln,
          l_hx TYPE bapisdh1x,
          l_r TYPE STANDARD TABLE OF bapiret2 WITH HEADER LINE,
          l_i TYPE STANDARD TABLE OF bapisditm WITH HEADER LINE,
          l_ix TYPE STANDARD TABLE OF bapisditmx WITH HEADER LINE,
          l_success(1) TYPE c VALUE 'Y'.
    l_vbeln = '0000707671'.
    l_hx-updateflag = 'U'.
    l_i-itm_number = '000010'.
    l_i-prc_group1 = 'Y'.
    APPEND l_i.
    l_ix-itm_number = '000010'.
    l_ix-updateflag = 'U'.
    l_ix-prc_group1 = 'X'.
    APPEND l_ix.
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
      EXPORTING
        salesdocument               = l_vbeln
      ORDER_HEADER_IN             =
        order_header_inx            = l_hx
      SIMULATION                  =
      BEHAVE_WHEN_ERROR           = ' '
      INT_NUMBER_ASSIGNMENT       = ' '
      LOGIC_SWITCH                =
      NO_STATUS_BUF_INIT          = ' '
      TABLES
        return                      = l_r
        order_item_in               = l_i
        order_item_inx              = l_ix
      PARTNERS                    =
      PARTNERCHANGES              =
      PARTNERADDRESSES            =
      ORDER_CFGS_REF              =
      ORDER_CFGS_INST             =
      ORDER_CFGS_PART_OF          =
      ORDER_CFGS_VALUE            =
      ORDER_CFGS_BLOB             =
      ORDER_CFGS_VK               =
      ORDER_CFGS_REFINST          =
      SCHEDULE_LINES              =
      SCHEDULE_LINESX             =
      ORDER_TEXT                  =
      ORDER_KEYS                  =
      CONDITIONS_IN               =
      CONDITIONS_INX              =
      EXTENSIONIN                 =
      NFMETALLITMS                =
    LOOP AT l_r.
      IF l_r-type <> 'S'.
        l_success = 'N'.
        EXIT.
      ENDIF.
      CLEAR l_r.
    ENDLOOP.
    IF l_success = 'Y'.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        WAIT          =
      IMPORTING
        RETURN        =
      WRITE: / 'Update successful'.
    ELSE.
      WRITE: / 'Update fail'.
    ENDIF.

  • UNCAUGHT_EXCEPTION runtime errors when changing the PO

    Hi everyone,
    We are facing the problem which is when changing the PO short dump UNCAUGHT_EXCEPTION is occurred then it will display "The page cannot be displayed"
    I don't know what is the exactly that cause of this problem
    Anyone who facing the same problem before, pls help on this. Hope anyone can help us on this.
    Thanks,
    quare

    Hi Disha,
    I found that only this PO cannot be change. Others are ok. There is an error in ST22 which is as below:
    Runtime Errors         UNCAUGHT_EXCEPTION
    Except.                CX_BBP_PD_ABORT
    Error analysis
        An exception occurred. This exception is dealt with in more detail below
        . The exception, which is assinged to the class 'CX_BBP_PD_ABORT', was not
         caught,
        which led to a runtime error.
        The reason for this exception is:
        Übernehmen
    After further search of error there is also message that relates to this error:
    Buffer table not up to date
    Message no. BBP_PD001
    Diagnosis
    In FORM CHANGE_VERSION_MAP_ORG (function group SAPLBBP_PDCV) an inconsistent status was discovered.
    Procedure
    Start the transaction again. If the error occurs again, create an OSS message.
    To analyze the error, you can set a breakpoint in the function module 'BBP_PD_ABORT' and look at the call-up hierarchy in debugging mode.
    I wondering what is the problem. Since it occurs not for all PO but certain PO only.
    Please help.
    Thanks,
    quare

  • Java iView Runtime error occurs whilw changing Theme Editor

    Hi,
    i have to face the following error while changing Theme.
    <b>Java iView Runtime
    Version : 6.4.200512140312
    + Copyright 2002 SAP AG. All rights reserved.
    An exception occured while processing your request.
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:304)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:284)
         ... 20 more
    Caused by: java.lang.OutOfMemoryError
    If this situation persists, please contact your system administrator.</b>
    Please give me right solution.
    Thanks & Regards,
    Nisarg Patel

    Hi,
         Try out the answers given in the following threads:
    Theme Editor : Runtime error
    Problem with Theme Editor
    Regards,
    Pooja.

  • ClockIn/ClockOut Error: Class interface was changed at runtime

    Hi,
    We are testing clock in / clock out corrections and the following error is arising when we call the functionality by this link:
    http://server:port/sap/bc/webdynpro/sap/hress_a_corrections?sap-wd-configid=HRESS_AC_CORRECTIONS&sap-client=400&sap-language=PT
    Error:
    Class interface was changed at runtime
    The strange is that before it was working fine and now we are getting this dump.
    Any Idea?
    Thanks
    Bruno

    I have found the error. Someone in the project run some process and input  wrong data in infotype 2006.
    I cleaned it and it worked!
    Thank Siddharth.
    Regards,
    Bruno

  • Change vendor detail got fiz runtime error

    Hi.
    when i ru transaction xk03 and try to change vender Email then it is giving fix ' DYNP_TOO_MANY_RADIOBUTTONS_ON'
    runtime error.u know module pool for this transaction is too big.i am beginer in abap so how can remove these error.
    I know thare may be multiple or no checkbox is selected but where???Please check

    Hi,
    The issue will be due to several radiobuttons but not grouped together.
    Have you added any custom screen in XK03 transaction.
    Check in the same.
    Incase not then search for some notes in service.sap.com.
    Regards,
    Ankur Parab

  • 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

  • Portal runtime error while selecting page layout in WPC editor

    Hello,
    in web page composer, editing page, when i click on "select page layout" I have a portal runtime error popup.
    The logfile shows the following :
    #1.5 #005056834112005E0000000C00000FA800048E28A94966CC#1282205196819#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#1016#149##n/a##7ff9c93eab6811dfa9c70000003307de#SAPEngine_Application_Thread[impl:3]_15##0#0#Error##Java###10:06_19/08/10_0010_3344350
    [EXCEPTION]
    #1#com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error in java compiling
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: E:
    usr
    sap
    EPD
    JC00
    j2ee
    cluster
    server0
    apps
    sap.com
    irj
    servlet_jsp
    irj
    root
    WEB-INF
    portal
    portalapps
    com.sap.netweaver.bc.util
    lib
    bc.util.public_api.jar(com/sapportals/wcm/WcmException.java):24: class WcmException is public, should be declared in a file named WcmException.java
    (source unavailable)
    1 error
    I have the same by clicking on "check assignments"
    Any help ?
    Thanks

    Hello Jego.
    We faced the same issue after upgrade to EHP1 SP07 last week and managed to solve it by modification of layout.jsp and com.sap.nw.wpc.layoutmanager.LayoutBean within com.sap.nw.wpc.designtime.par. SAP's code requires an additional catch handler, so it is better to rise an OSS message.
    As a workaround you may change a default layout for wpc main page (good for new pages) or manually edit output.xml for existing pages.
    Best regards,
    Aliaksandr Zhukau

  • Runtime Error in ALV Tree Output

    Dear All, I am trying to create a ALV Tree using Class cl_gui_alv_tree. The Report Shows the Output with the first Node but when i try to expand it is dumping with a runtime error GETWA_NOT_ASSIGNED in class CL_ALV_TREE_BASE and method SET_ITEMS_FOR_COLUMN. The Reason being the data which was copied in the initial node display to mt_outtab is getting refreshed.
    Can any one of you help me the reason for the table getting refreshed. Do i need to pass any data.
    I am doing the following steps.
    1. Create Container,
    2. Create Tree Class object
    3. Generate the Field Catalog.
    4. Set table for first display  " With empty internal table
    5. Generate the Hierarchy
    6. Call the Method Frontend Update.
    Let me know if i had missed any steps in the process.
    Thank you,
    Regards,
    Swaroop Patri

    One reason for getting this error is using local defined tables for it_outtab parameter in the below code:
    To get rid of the dump, define two distinct output tables globally: one is an empty table which you will pass to the below method, other one is your real output table whose size increases dependently.
      CALL METHOD go_tree->set_table_for_first_display
          EXPORTING
            is_hierarchy_header = ls_hier_header
          CHANGING
            it_outtab           = gt_data_e "Empty table
            it_fieldcatalog     = gt_fcat_tree.

Maybe you are looking for