Transport Release runtime error in BPC Netweaver 10.1

Hi,
We are getting the following error while releasing the transport in SAP BPC NW 10.1 Development system
Category               ABAP Programming Error
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_RSBPCR_INTERNAL_EXCEPTION
ABAP Program           CL_RSBPCR_RES_MANAGER=========CP
Application Component  BW-PLA-BPC-INF-WP
Short Text
    An exception has occurred that was not caught.
What happened?
    Exception 'CX_RSBPCR_INTERNAL_EXCEPTION' was raised, but it was not caught
     anywhere along the
    call hierarchy.
    Since exceptions represent error situations, and this error was not
    adequately responded to, ABAP program 'CL_RSBPCR_RES_MANAGER=========CP' had
     to be terminated.
We are on SAP BW 7.40 patch level 5. Could you please advice the reason for this?

Hello,
so after implementing note 2050531 you should add the following entry in table UJPS_RESOURCE (caution I misspelled it earlier, it is not ups_resource).
You can do this through transaction SE16 -> enter UJPS_RESOURCE and hit Create Entries.
Fields MANDT and APPSET_ID should be filled with your BW System Client ID (i.e. 100) and your BPC Environment ID (i.e. ENVIRONMENTSHELL). The entries that appear to be empty should be left empty.
MANDT
APPSET_ID
RESOURCE_ID
TSTPNM
TIMESTMP
OBJSTAT
CONTREL
CONTTIMESTMP
OWNER
BWAPPL
ACTIVFL
PARENT_RES_ID
UPDATE_COUNTER
RESOURCE_TYPE
CREATE_USER
CREATE_TIME
ORIG_LANGU
OWNER_ID
OWNER_TYPE
Client ID
Your Environment ID
005056B236881ED38AE1D894578A8F97
0
ACT
0
3
0
FOLDER
0
E
005056B236881ED38AE1D894578A8F97
TEAM
After this you should be able to release your request.
Hope this is helpful.

Similar Messages

  • Error In BPC Netweaver Export Package-version 7.5

    Hi Bpc Experts, We upgraded DEV BPC Version 7 to 7.5 netweaver version. We are facing an issue when exporting data from BPC to BI application server.Please find the error message as below
    Task name CONVERT:
    No 1 Round:
    0GL_ACCOUNT is not a valid command or column 0GL_ACCOUNT does not exist in source
    Application: CONSOLIDATION Package status: ERROR
    I request you to give a suggestion to fix the above issue
    Thanks
    Mahesh

    Can you try the below mapping:
    0GLACCOUNT=C_ACCT
    I have my transformation file maintained in such a way that my BPC dimensions are maintained to the right of '=' sign.
    Maintain your mapping like that and validate the tansformation file with the data in the BPC cube.
    Thanks

  • Runtime Error in B2B application logon!

    Hi,
    I am working on a custom SAP B2B application.  The B2B version is 7.0 SP19. 
    We have done a SAP upgrade to ECC6 in the backend ABAP system.  After the SAP upgrade in dev and quality portals, the development portal is working fine.  But, in the quality portal, the customer number was not getting passed to the backend ABAP system.  So, we did a portal transport for the SHRWEB-B2B component and its associated CUSTCRM component from Dev to Q.  After this transport, we did a comparison for the deployed versions in dev and Q.  Both are found to be exactly the same.
    But after the transport, I am getting 'Runtime Error - Contact your system administrator' error while logging into the Quality portal.  The same application works fine in the development portal.  When we reverted the transport, the runtime error is not seen but the customer number is not getting passed to the ABAP system.
    I checked the XCM configuration.  Both the dev and Q have similar settings in XCM configuration.
    Please help!
    Thanks,
    Yuvaraj

    Yuvaraj,
    What does the default trace log file say for the Runtime error? At what point does it fail?
    Pradeep

  • BPC for NW Client SP08 Problem - Runtime Error

    Hello,
    I'm having issues after the installation process. When I try to execute the Client, the software is throwing me the following error:
    "Runtime Error - It is not possible to open the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\OUTLOOKSOFT\50\CLIENT\SUPPORTLANGUAGE""
    The user has full administration rights, Office 2007, windows 7 and we are in SAP BPC for SAP Netweaver SP08.
    Any ideas?
    Thanks & Regards
    SU

    Hi SU,
    I am assuming you are on BPC 7.5.
    This issue has been identified on BPC 7.5 SP07 and SP08.
    You may refer to KBA 1596543 for further info.
    Here is how to correct this issue in BPC 7.5 NW SP8:
    1 - Create this folder structure:
    "C:\Documents and Settings\All Users\Start Menu\Programs\SAP BusinessObjects\Planning and Consolidation"
    2 - Run the installation
    Please let us know if this helped!
    Regards,
    Marcelo

  • Netweaver 7.0 EHP 1 upgrade on AIX platform runtime error

    Dear all,
    I am currently running on Netweaver 7.0 on IBM AIX / Oracle 10.2 platform.
    I am trying to upgrade Kernel from 700 to 701 release patch level 39.
    Unfortunately after extracting few of the exe files Example disp+work are
    giving error as
    could not load disp+work progarm
    rtld : 0712-001 Symbol XTCgetprefixForURI was referenced
    from module disp+work(), but a runtime definition of the symbol was not found
    rtld : 0712-002 fatal error : exiting
    I have faced this error in Windows platform where we need to run some microsoft DLL
    as per SAP Note 684106 which clears these fatal runtime errors,
    but this note applies to only windows platform .
    Is there any note specific to AIX platform.
    Please let me know ASAP.
    Best Regards,
    RR
    Edited by: BASISRR on Sep 23, 2009 10:32 PM

    Hello!
    We get this problem on an HP-UX server as well....
    After replacing the SAP Kernel (from NW700) to NW701 patch level 69,
    during a EHP1 upgrade of this system, the dispatcher and dw-processes is not starting (using startsap/stopsap-scripts)!
    In the dev_ms we get following error message:
    "/usr/lib/hpux64/dld.so: Unsatisfied code symbol 'XTCGetPrefixForURI' inload module 'dw.sapSID_DVEBMGS20'."
    We started the processes manuellay instaed, using "dw.sapSID_DVEBMGS20
    pf=/sapmnt/SID/profile/SID_DVEBMGS20_sapsid", and succesfully upgraded
    the ABAP-part to EHP1.
    Do we have to patch HP-UX?
    server:sidadm 32> uname -a
    HP-UX server B.11.31 U ia64 3960812771 unlimited-user license
    server:sidadm 33>

  • Runtime Error in Test Client after Transport

    Hello SDNers,
    I did enhancements to standard SAP component ICCMP_BP_SEARCH in developement system in client XXX of system SSS.
    I wanted to test the functionality in client YYY so used SCC1 transaction to transport from client XXX to client YYY.
    But when i tried to test the application, it resulted in runtime error.
    I had kinda identified the problem while debugging, in the class CL_CHTMLB_CONFIG_UTILITY method CREATE_UI_ELEMENT, it is not taking my Z class references rather it still referring to starndard classes.
    My Z classes are created for IMPL  class, CTXT class and CN00 class.
    If any one has suggestions your help would be appreciated
    Thanks in advance.
    Best Regards,
    Srikanth

    Srikanth,
    Is the definition of the enhancement set defined properly for your test client.  This table does not transport and you have to maintain it manually in each client.  The view is BSPWDV_EHSET_ASG for SM30.  Client is not the first field in the table, so you have to edit this view in each client.
    Take care,
    Stephen

  • RUNTIME Error - User Status for Order release

    HI Friends,
    Pls go thru the run-time error description,which i'm getting on Order release.Pls reply,.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          31.03.2008 13:16:08
    Short text
    The current application triggered a termination with a short dump.
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    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
    Short text of error message:
    Unable to read RFC destination WORKFLOW_LOCAL_250
    Long text of error message:
    Technical information about the message:
    Message class....... "SWF_RUN"
    Number.............. 617
    Variable 1.......... "WORKFLOW_LOCAL_250"
    Variable 2.......... "RFC_READ_DESTINATION_TYPE"
    Variable 3.......... "DESTINATION_NOT_EXIST"
    Variable 4.......... " "
    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:
    "MESSAGE_TYPE_X" " "
    "CL_SWF_RUN_WIM_LOCAL==========CP" or "CL_SWF_RUN_WIM_LOCAL==========CM088"
    "IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER"
    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... "SILDEV"
    Network address...... "192.168.255.70"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x IA64 Level 3"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 2
    Shortdump setting.... "full"
    Database server... "SILDEV"
    Database type..... "MSSQL"
    Database name..... "DEV"
    Database user ID.. "dev"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Mar 3 2008 03:55:37"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "SQL_Server_8.00 "
    Patch level. 150
    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...... 8379680
    Heap.... 0
    Page.... 16384
    MM Used. 4889280
    MM Free. 3487552
    User and Transaction
    Client.............. 250
    User................ "PM5CHARL"
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "49F6FEDCA000F177897B0017A4ABF059"
    Program............. "CL_SWF_RUN_WIM_LOCAL==========CP"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
    System.............. "DEV"
    Database Release.... 700
    Kernel Release...... 700
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchron and transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........."C0A8FF46013847F096C00004"
    Outbound Queue Name.." "
    Client.............. 250
    User................ "PM5CHARL"
    Transaction......... " "
    Call Program........."SAPLERFC"
    Function Module..... "ARFC_DEST_SHIP"
    Call Destination.... "NONE"
    Source Server....... "SILDEV_DEV_00"
    Source IP Address... "192.168.255.70"
    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 "CL_SWF_RUN_WIM_LOCAL==========CP" -
    in "IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 10
    of the (Include) program "CL_SWF_RUN_WIM_LOCAL==========CM088".
    Source Code Extract
    Line
    SourceCde
    1
    METHOD if_swf_run_wim_utl_internal~get_system_user .
    2
    DATA: l_excp TYPE REF TO cx_swf_run_wim.
    3
    4
    TRY.
    5
    IF me->m_int_state-system_user IS INITIAL.
    6
    me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
    7
    ENDIF.
    8
    re_user = me->m_int_state-system_user.
    9
    CATCH cx_swf_run_wim INTO l_excp.
    >>>>>
    MESSAGE ID     l_excp->t100_msg-msgid
    11
    TYPE   'X'
    12
    NUMBER l_excp->t100_msg-msgno
    13
    WITH   l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2
    14
    l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4.
    15
    ENDTRY.
    16
    17
    ENDMETHOD.                    "
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    2
    SY-TABIX
    1
    SY-DBCNT
    0
    SY-FDPOS
    1
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    CPIC and RFC Control
    SY-MSGTY
    X
    SY-MSGID
    SWF_RUN
    SY-MSGNO
    617
    SY-MSGV1
    WORKFLOW_LOCAL_250
    SY-MSGV2
    RFC_READ_DESTINATION_TYPE
    SY-MSGV3
    DESTINATION_NOT_EXIST
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20080331
    SY-UZEIT
    131608
    SY-XPROG
    SAPMSSY1
    SY-XFORM
    XAB_READ
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    26 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM088    10
    CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
    25 METHOD       CL_SWF_UTL_MAIL===============CP    CL_SWF_UTL_MAIL===============CM00J     5
    CL_SWF_UTL_MAIL=>GET_OWNER
    24 METHOD       CL_SWF_UTL_MAIL===============CP    CL_SWF_UTL_MAIL===============CM002    37
    CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND
    23 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM0IE    38
    CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL
    22 METHOD       CL_SWF_RUN_WIM_STATE==========CP    CL_SWF_RUN_WIM_STATE==========CM021     7
    CL_SWF_RUN_WIM_STATE=>DYN_SEND_ERROR_REPAIR_MAIL
    21 METHOD       CL_SWF_RUN_WIM_STATE==========CP    CL_SWF_RUN_WIM_STATE==========CM01V    12
    CL_SWF_RUN_WIM_STATE=>EXECUTE_STATE_TRANSITION
    20 METHOD       CL_SWF_RUN_WIM_STATE_FLOW=====CP    CL_SWF_RUN_WIM_STATE_FLOW=====CM004     2
    CL_SWF_RUN_WIM_STATE_FLOW=>IF_SWF_RUN_WIM_STATE~EXECUTE_STATE_TRANSITION
    19 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM09A    72
    CL_SWF_RUN_WIM_LOCAL=>SET_STATUS_INTERNAL
    18 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM0H3    16
    CL_SWF_RUN_WIM_LOCAL=>_SET_STATUS
    17 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM04P     7
    CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SET_STATUS
    16 METHOD       CL_SWF_RUN_WIM_EXECUTION_MGR==CP    CL_SWF_RUN_WIM_EXECUTION_MGR==CM011    12
    CL_SWF_RUN_WIM_EXECUTION_MGR=>SET_WORKITEM_STATUS_ERROR
    15 METHOD       CL_SWF_RUN_WIM_EXECUTION_MGR==CP    CL_SWF_RUN_WIM_EXECUTION_MGR==CM01A    81
    CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXCEPTION_RESULT
    14 METHOD       CL_SWF_RUN_WIM_EXECUTION_MGR==CP    CL_SWF_RUN_WIM_EXECUTION_MGR==CM00R    93
    CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXECUTION_RESULT
    13 METHOD       CL_SWF_RUN_WIM_EXECUTION_MGR==CP    CL_SWF_RUN_WIM_EXECUTION_MGR==CM008   144
    CL_SWF_RUN_WIM_EXECUTION_MGR=>START_EXECUTION
    12 METHOD       CL_SWF_RUN_WORKFLOW_START=====CP    CL_SWF_RUN_WORKFLOW_START=====CM016    42
    CL_SWF_RUN_WORKFLOW_START=>START_WORKITEM
    11 METHOD       CL_SWF_RUN_WORKFLOW_START=====CP    CL_SWF_RUN_WORKFLOW_START=====CM002    33
    CL_SWF_RUN_WORKFLOW_START=>EXECUTE
    10 FUNCTION     SAPLSWW_SRV                         LSWW_SRVU13                           135
    SWW_WI_CREATE_VIA_EVENT_INTERN
    9 FUNCTION     SAPLSWW_SRV                         LSWW_SRVU11                            64
    SWW_WI_CREATE_VIA_EVENT
    8 FORM         SAPLSWW_SRV                         LSWW_SRVU11                             1
    SWW_WI_CREATE_VIA_EVENT
    7 FORM         SAPMSSY1                            SAPMSSY1                              271
    XAB_RUN_DRIVER
    6 FUNCTION     SAPLSXAB                            LSXABU01                                9
    RFC_RUN_XAB_DRIVER
    5 FUNCTION     SAPLERFC                            LERFCU01                              115
    ARFC_EXECUTE
    4 FUNCTION     SAPLERFC                            LERFCU02                              386
    ARFC_DEST_SHIP
    3 FORM         SAPLERFC                            LERFCU02                                1
    ARFC_DEST_SHIP
    2 FORM         SAPMSSY1                            SAPMSSY1                               85
    REMOTE_FUNCTION_CALL
    1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
    %_RFC_START
    Chosen variables
    Name
    Val.
    No.      26 Ty.          METHOD
    Name  CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
    RE_USER
    222222222222
    000000000000
    000000000000
    000000000000
    L_EXCP
    B0004000
    90006000
    SY-MSGID
    SWF_RUN
    55455542222222222222
    376F25E0000000000000
    00000000000000000000
    00000000000000000000
    L_EXCP->T100_MSG-MSGID
    SWF_RUN
    55455542222222222222
    376F25E0000000000000
    00000000000000000000
    00000000000000000000
    SWFCO_WIM_WI_FORWARD
    SWW_WI_FORWARD
    555554544554542222222222222222
    377F79F6F271240000000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    SY-MSGNO
    617
    333
    617
    000
    000
    L_EXCP->T100_MSG+40(6)
    617
    333
    617
    000
    000
    SY-MSGV1
    WORKFLOW_LOCAL_250
    54544445544444533322222222222222222222222222222222
    7F2B6CF7FCF31CF25000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    L_EXCP->T100_MSG+48(100)
    WORKFLOW_LOCAL_250
    54544445544444533322222222222222222222222222222222
    7F2B6CF7FCF31CF25000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV2
    RFC_READ_DESTINATION_TYPE
    54455444544554445444555542222222222222222222222222
    263F2514F45349E149FEF49050000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    L_EXCP->T100_MSG+148(100)
    RFC_READ_DESTINATION_TYPE
    54455444544554445444555542222222222222222222222222
    263F2514F45349E149FEF49050000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV3
    DESTINATION_NOT_EXIST
    44554445444544554545522222222222222222222222222222
    45349E149FEFEF4F5893400000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    L_EXCP->T100_MSG+248(100)
    DESTINATION_NOT_EXIST
    44554445444544554545522222222222222222222222222222
    45349E149FEFEF4F5893400000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    L_EXCP->T100_MSG+348(100)
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    No.      25 Ty.          METHOD
    Name  CL_SWF_UTL_MAIL=>GET_OWNER
    RE_OWNER
    %_DUMMY$$
    2222
    0000
    0000
    0000
    ME->M_OWNER
    %_VIASELSCR
    0
    4
    ME
    A0005000
    E0001000
    L_WORKITEM
    60009000
    3000C000
    SY-REPID
    CL_SWF_UTL_MAIL===============CP
    4455545554544443333333333333334522222222
    3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    No.      24 Ty.          METHOD
    Name  CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND
    EX_SENT_TO_ALL
    2
    0
    0
    0
    EX_MAIL_OBJECT
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SYST-REPID
    CL_SWF_UTL_MAIL===============CP
    4455545554544443333333333333334522222222
    3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    ME
    A0005000
    E0001000
    OBJECT_HD_CHANGE-ACNAM
    SWW_WI_DISPLAY_FOR_MAIL
    555554544554455445544442222222222222222222222222222222
    377F79F4930C19F6F2FD19C0000000000000000000000000000000
    000000000000000000000000000000000000000000000000000000
    000000000000000000000000000000000000000000000000000000
    OBJPARB
    Table IT_758[1x570]
    \CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJPARB
    Table reference: 224
    TABH+  0(20) = E06D6DEFF9060000000000000000000000000000
    TABH+ 20(20) = E0000000F6020000010000003A020000FFFFFFFF
    TABH+ 40(16) = 042A0200600B000010000000C1248401
    store        = 0xE06D6DEFF9060000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 224   (0xE0000000)
    label        = 758   (0xF6020000)
    fill         = 1     (0x01000000)
    leng         = 570   (0x3A020000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000046
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x80095FEFF9060000
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 540   (0x1C020000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x10000000)
    lineAlloc    = 16    (0x10000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    OBJECT_HD_CHANGE-OBJDES
    Workflow 405090 set to status ERROR
    56766667233333327672762776777245545222222222222222
    7F2B6CF70405090035404F03414530522F2000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    %_FSREG_001
    OBJCONT
    Table IT_760[9x510]
    \CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJCONT
    Table reference: 225
    TABH+  0(20) = 106F6DEFF9060000000000000000000000000000
    TABH+ 20(20) = E1000000F802000009000000FE010000FFFFFFFF
    TABH+ 40(16) = 042A0200300B000010000000C1248401
    store        = 0x106F6DEFF9060000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 225   (0xE1000000)
    label        = 760   (0xF8020000)
    fill         = 9     (0x09000000)
    leng         = 510   (0xFE010000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000045
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x402D5FEFF9060000
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 541   (0x1D020000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x10000000)
    lineAlloc    = 16    (0x10000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    OWNER
    222222222222
    000000000000
    000000000000
    000000000000
    SENDER
    222222222222
    000000000000
    000000000000
    000000000000
    SY-SUBRC
    0
    0000
    0000
    SWFCO_MAIL_ERROR_NOTIFY
    0002
    3333
    0002
    0000
    0000
    OBJECT_HD_CHANGE
    E          ERRORMESSAGEWorkflow 405090 set to status ERROR                00000000000000 F F S
    4222222222245545445544456766667233333327672762776777245545222222222222222233333333333333242425
    50000000000522F2D5331757F2B6CF70405090035404F03414530522F2000000000000000000000000000000060603
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    OBJECT_TYPE
    RAW
    545
    217
    000
    000
    SWFCO_OBJTYPE_BOR
    BO
    44
    2F
    00
    00
    No.      23 Ty.          METHOD
    Name  CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL
    LT_AGENTS
    Table IT_752[1x28]
    \CLASS=CL_SWF_RUN_WIM_LOCAL\METHOD=IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL\DATA=LT_AGEN
    Table reference: 207
    TABH+  0(20) = 806B6DEFF9060000000000000000000000000000
    TABH+ 20(20) = CF000000F0020000010000001C000000FFFFFFFF
    TABH+ 40(16) = 04180100E006000010000000C1248401
    store        = 0x806B6DEFF9060000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 207   (0xCF000000)
    label        = 752   (0xF0020000)
    fill         = 1     (0x01000000)
    leng         = 28    (0x1C000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000022
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xA0696DEFF9060000
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 537   (0x19020000)
    refCount     = 1     (0x01000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x10000000)
    lineAlloc    = 16    (0x10000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 2     (0x02000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    SYST-REPID
    CL_SWF_RUN_WIM_LOCAL==========CP
    4455545554554454444433333333334522222222
    3CF376F25EF79DFCF31CDDDDDDDDDD3000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD+840(28)
    WS20000014
    55333333332222
    73200000140000
    00000000000000
    00000000000000
    SY-REPID
    CL_SWF_RUN_WIM_LOCAL==========CP
    4455545554554454444433333333334522222222
    3CF376F25EF79DFCF31CDDDDDDDDDD3000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    FUNCNAME
    SWW_WI_DISPLAY_FOR_MAIL
    555554544554455445544442222222
    377F79F4930C19F6F2FD19C0000000
    000000000000000000000000000000
    000000000000000000000000000000
    SWFCO_WI_REMOTE
    R
    5
    2
    0
    0
    PARAMETER-NAME
    WI_ID
    54544
    79F94
    00000
    00000
    SWFCO_CALLBACK_AGENTS
    CALLBACKAGENTS
    54444444454444552222222222222222
    F31CC213BF175E430000000000000000
    00000000000000000000000000000000
    00000000000000000000000000000000
    PARAMETER-VALUE
    000000405090
    333333333333
    000000405090
    000000000000
    000000000000
    ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD-WI_ID
    000000405090
    333333333333
    000000405090
    000000000000
    000000000000
    PARAMETER
    807020C0
    7080A050
    00000000
    00100010
    LS_MAILOBJ
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    ME
    60009000
    3000C000
    SWFCO_WORKITEM_OBJECT
    _WORKITEM
    55454454422222222222222222222222
    F7F2B945D00000000000000000000000
    00000000000000000000000000000000
    00000000000000000000000000000000
    No.      22 Ty.          METHOD
    Name  CL_SWF_RUN_WIM_STATE=>DYN_SEND_ERROR_REPAIR_MAIL
    SWFCO_WORKITEM_OBJECT
    _WORKITEM
    55454454422222222222222222222222
    F7F2B945D00000000000000000000000
    00000000000000000000000000000000
    00000000000000000000000000000000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    No.      21 Ty.          METHOD
    Name  CL_SWF_RUN_WIM_STATE=>EXECUTE_STATE_TRANSITION
    IM_STATE_ACTIONS
    Table IT_279[30x152]
    \CLASS=CL_SWF_RUN_WIM_STATE_FLOW\DATA=M_STATE_ACTIONS
    Table reference: 112
    TABH+  0(20) = 90CE53EFF9060000B04D6BEFF906000000000000
    TABH+ 20(20) = 70000000170100001E0000009800000090010000
    TABH+ 40(16) = 049A01007004000010000000C9248001
    store        = 0x90CE53EFF9060000
    ext1         = 0xB04D6BEFF9060000
    shmId        = 0     (0x00000000)
    id           = 112   (0x70000000)
    label        = 279   (0x17010000)
    fill         = 30    (0x1E000000)
    leng         = 152   (0x98000000)
    loop         = 400   (0x90010000)
    xtyp         = TYPE#000009
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 1     (ItIndexLinear)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xF0C453EFF9060000
    pgHook       = 0xF0CE53EFF9060000
    idxPtr       = 0x50E253EFF9060000
    shmTabhSet   = 0x0000000000000000
    id           = 207   (0xCF000000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 48    (0x30000000)
    lineAlloc    = 48    (0x30000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x204C6BEFF9060000
    collHook     = 0x0000000000000000
    ext2         = 0x0000000000000000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    SWFCO_WI_NO_DEADLINE
    0000
    3333
    0000
    0000
    0000
    L_OBJ
    A0005000
    D0002000
    ME
    A0005000
    D0002000
    ME->IF_SWF_RUN_WIM_STATE~NEW_STATUS
    ERROR
    455452222222
    522F20000000
    000000000000
    000000000000
    <%_L003>
    ERROR
    455452222222
    522F20000000
    000000000000
    000000000000
    SY-REPID
    CL_SWF_RUN_WIM_STATE==========CP
    4455545554554455545433333333334522222222
    3CF376F25EF79DF34145DDDDDDDDDD3000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    <%_L004>
    F
    4
    6
    0
    0
    <STATE_ACTION>
    FERROR       01DYN_SEND_ERROR_REPAIR_MAIL
    4455452222222334545544454554555454455444422222222222222222222222222222222222
    6522F200000000149EF35E4F522F2F250192FD19C00000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000
    <%_L002>
    <%_L002>-WI_STAT
    SYST-REPID
    CL_SWF_RUN_WIM_STATE==========CP
    4455545554554455545433333333334522222222
    3CF376F25EF79DF34145DDDDDDDDDD3000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    SWFCO_WI_STATUS_WILD_CARD
    222222222222
    A00000000000
    000000000000
    000000000000
    <%_L002>-WI_TYPE
    <STATE_ACTION>-METHOD
    DYN_SEND_ERROR_REPAIR_MAIL
    4545544454554555454455444422222222222222222222222222222222222
    49EF35E4F522F2F250192FD19C00000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000
    %_SPACE
    2
    0
    0
    0
    LV_EXCP
    F0000000
    F0000000
    No.      20 Ty.          METHOD
    Name  CL_SWF_RUN_WIM_STATE_FLOW=>

    Hello,
    Get help from your abaper on this.
    Vinay

  • Runtime error on Project/WBS element release

    Hi All,
    I am trying to release a WBS element, however the system hangs and eventually causes a runtime error. How do I rectify this?
    Thanks in advance.
    Regards,
    PS_PS01

    Hi,
    I have done that already. This problem is 4 days old. Everyday I log off, then log in.
    The error meassage reads: "time limit exceeded. The program "SAPLCJDW" has exceeded the maximum permitted runtime without interruption and has therefore been terminated."
    Is there perhaps a note I can apply to correct this?

  • Can't release transport time out error

    Hi,
    I can't release the transport and giving time out error,increased the rdisp/max_wprun_time to 5000 seconds even though it is failing.Its is accessing TLOCKPC table and this contain 5 lack entries I created T02 index for this table.
    Please help to fix this issue.
    Thanks
    jalandhar

    Hi,
    Yes,we have latest tp version and /usr/sap/trans is have free space.
    We are facing issue with only one transport remaining all transports releasing properly.

  • Clock-in/out runtime error in Netweaver UI5 portal

    Dear Experts
    Following error is runtime error for the service clock-in/out in the portal
    when i click on the service,i m getting the runtime error(in ST22)
    Category                        ABAP Programming Error
    Runtime Errors              MESSAGE_TYPE_X
    ABAP Program             SAPLPT_COR_REQUEST_UIA
    Application Component  PT-RC-TE
    Date and Time              12.09.2014 16:45:43
    Error analysis
        Short text of the error message:
        No Customizing E
        Long text of the error message:
        Technical information about the message:
        Message class....... 53
        Number.............. 999
        Variable 1.......... No Customizing
        Variable 2.......... E
        Variable 3..........
        Variable 4.......... " "
    please help.
    what should i do, to fix this error

    thank you
    this issue is solved!

  • ABAP runtime error while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N

    Dear All Expert,
    I am facing problem while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N,
    Please find the below ABAP Runtime Error.
    Runtime Errors         LOAD_TYPE_VERSION_MISMATCH
    Date and Time          10.02.2011 11:13:07
    Short text
         Change of a Dictionary structure at runtime of a program.
    What happened?
         Runtime error
         The current ABAP program "CL_IM_WRF_MM_PROC_PO==========CP" had to be
          terminated because one
         of the statements could not be executed at runtime.
    What can you do?
         Restart the program.
         If the error persists, 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 ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY"
          changed
         during the flow of the transaction.
         As the type was already used in the old version
         and in the new type should be used in the same transaction in the new
          version, the transaction had to be cancelled to avoid inconsistencies.
    How to correct the error
        Try to restart the program.
    System environment
        SAP-Release 700
        Application server... "iqe"
        Network address...... "172.25.0.85"
        Operating system..... "Linux"
        Release.............. "2.6.9-55.ELsmp"
        Hardware type........ "x86_64"
        Character length.... 16 Bits
        Pointer length....... 64 Bits
        Work process number.. 0
        Shortdump setting.... "full"
        Database server... "iqe"
        Database type..... "ORACLE"
        Database name..... "IQE"
        Database user ID.. "SAPSR3"
        Terminal................. "MUMJML5727"
        Char.set.... "C"
        SAP kernel....... 700
        created (date)... "Dec 26 2010 20:17:07"
        create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"
        Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 285
    Patch text.. " "
    Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
    SAP database version. 700
    Operating system..... "Linux 2.6"
    Memory consumption
    Roll.... 16192
    EM...... 25139088
    Heap.... 0
    Page.... 40960
    MM Used. 8038136
    MM Free. 4528408
    User and Transaction
    Client.............. 600
    User................ "JKMM"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "4D524AD1FD7A42F9E1000000AC190055"
    Program............. "CL_IM_WRF_MM_PROC_PO==========CP"
    Screen.............. " "
    Screen line......... " "
    Information on where terminated
        The termination occurred during generation of the ABAP/4 program
         "CL_IM_WRF_MM_PROC_PO==========CP".
        The termination occurred in line 213
        of the source code of program "CL_IM_WRF_MM_PROC_PO==========CM007" (when
         calling the editor 2130).
    Source Code Extract
    Line  SourceCde
      183   DATA: l_flag TYPE wrf_pbas_boolean.
      184
      185   CALL FUNCTION 'WRF_POHF_MSG_READ_PREVIEW_FLAG'
      186     IMPORTING
      187       e_preview_flag = l_flag.
      188
      189   IF NOT l_flag IS INITIAL.
      190
      191     DATA: l_header TYPE REF TO cl_po_header_handle_mm.
      192
      193     MOVE im_header ?TO l_header.
      194
      195     CALL METHOD l_header->if_output_mm~preview( ).
      196
      197     CALL FUNCTION 'WRF_POHF_MSG_RESET_PREV_FLAG'.
      198
      199 ***$ Widening Cast for printing information.
      200 **    CALL FUNCTION 'WRF_POHF_STORE_PRINT_INFO_SET'
      201 **      EXPORTING
      202 **        im_header = l_header.
      203
      204 * Printing Preview
      205 * IF NOT gv_preview IS INITIAL.
      206 *    CALL METHOD l_header->if_output_mm~overview( ).
      207 *    CALL METHOD l_header->if_output_mm~preview( ).
      208 * clear gv_preview.
      209   ENDIF.
      210
      211 *  ENDIF.
      212
    >>>>> ENDMETHOD.
    Internal notes
        The termination was triggered in function "ab_RxDdicStruShareFailed"
        of the SAP kernel, in line 2539 of the module
         "//bas/700_REL/src/krn/runt/abtypload.c#11".
        The internal operation just processed is " ".
        Internal mode was started at 20110210111306.
        Name of the changed type......: "WRF_POHF_KOMP_STY"
        New version of the type.......: 20070508193207
        Old version of the type.......: 20070508193207
        New user......................: "Type" "WRF_POHF_KOMP_STY"
        Version of the new user.......: 20070508193207
        Old user......................: "???" "???"
        Version of the old user.......: "???"
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    (CTrcStack2+0x78)[0x6cbb78]
    (CTrcStack+0xb)[0x6cc17b]
    (ab_rabax+0x3be5)[0xb8d985]
    (_Z24ab_RxDdicStruShareFailedPKtm4RUDIS0_S1_S0_+0x163)[0xb16823]
    (_Z19ab_GetDdicTypeIndexPKtm4RUDI+0x1f6)[0xb0dbb6]
    (_Z11ab_LoadViewPtjPKtPK11PROGRAMHEADPj+0x27e)[0xb16ede]
    (_Z18ab_GetDdicTypeLoad4RUDI+0x6e)[0xb1705e]
    (ab_GetView+0xc1d)[0xb0ee1d]
    (_Z20CompressInitRcByDatajPK6CG_DIRjjS1_jj4RUDIPKhj+0x60d)[0xe32b2d]
    (_Z21cg_CompressStackFrameP4TRIGjj+0x169)[0xe33399]
    (_Z8cg_blkleP3ENV+0x75f)[0xe4779f]
    (_Z9sc_cblklePKt8ENV_KINDP7SC_INFO+0x394)[0xe90024]
    (sc_blkle+0xdd)[0xec6e4d]
    (rs_oper_abap1729+0x37)[0x10eb237]
    (rs_expan_abap+0xa1996)[0xfd7a2a]
    (_Z8sc_expanj+0x76d)[0xe1d55d]
    (_Z5parsejPi+0x258)[0xe19998]
    (sc_check+0xb9c)[0xe1857c]
    (sc_inclu+0x5fa)[0xe0d50a]
    (rs_oper_abap2160+0x3a)[0x1115d6a]
    (rs_expan_abap+0xcd41d)[0x10034b1]
    (_Z8sc_expanj+0x76d)[0xe1d55d]
    (_Z5parsejPi+0x258)[0xe19998]
    (sc_check+0xb9c)[0xe1857c]
    (sc_checkStart+0x41)[0xe1ac51]
    (cg_generate+0xb65)[0xe57755]
    (ab_gabap+0x14a)[0xb01a5a]
    (dy_gen_abap+0x63c)[0x74428c]
    (ab_genprog+0x13d3)[0xb03d13]
    (_Z17ab_LoadProgOrTrfoPKtjPj+0xb56)[0x8f9ab6]
    (_Z11ab_LoadProgPKtj+0x11)[0x8f9ca1]
    (_Z15LoadGlobalClassPKtjjj9ClasState+0x24c)[0x958c2c]
    (_Z11FillCfixIntPK4CREFP4CFIXjj9ClasState+0x214)[0x957404]
    (_Z11ab_FillCfixtj+0x65)[0x957ae5]
    (_Z26ab_CrefToCladId_ActivateOKtPh+0x7d)[0x957b6d]
    (_Z8ab_jaboov+0x623)[0x959793]
    (_Z8ab_extriv+0x607)[0x8ba9c7]
    (_Z9ab_xeventPKt+0x1c1)[0xa1c021]
    (_Z8ab_triggv+0x9c)[0xa1c77c]
    (ab_run+0x97)[0xbde5c7]
    (N_ab_run+0x9)[0x736359]
    (dynpmcal+0x669)[0x7333b9]
    (dynppai0+0x8eb)[0x734d9b]
    (dynprctl+0x3e9)[0x733db9]
    (dynpen00+0x4a5)[0x726eb5]
    (Thdynpen00+0x359)[0x541bd9]
    (TskhLoop+0xc49)[0x54d999]
    (ThStart+0x20f)[0x55b29f]
    (DpMain+0x2da)[0x4bd49a]
    (nlsui_main+0x9)[0x4910c9]
    (main+0x33)[0x491103]
    /lib64/tls/libc.so.6(__libc_start_main+0xdb)[0x3cde51c3fb]
    Please help me to resolve the issue.
    Thanks & Regards
    SKK

    read this part again:  The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY" changed during the flow of the transaction. As the type was already used in the old version and in the new type should be used in the same transaction in the new version, the transaction had to be cancelled to avoid inconsistencies. How to correct the error Try to restart the program
    how often had you restarted ME21N before you posted this message?
    In best case this message appears only once, because the program / or dictionary was changed while you executed ME21N
    If many times, then contact your ABAPer, because then he probably did not transport all objects that were changed, or the objects have to be regenerated in your system.

  • Runtime error in excise tax

    hi
    i am getting runtime error while doing googs receipt with tax code(without tax not getting error).please see this error.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          27.08.2008 20:32:45
    Short dump has not been completely stored (too big)
    Short text
    The current application triggered a termination with a short dump.
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    Error analysis
    Short text of error message:
    Balance in transaction currency
    Long text of error message:
    Diagnosis
    A balance has occurred in transaction currency 'INR' with the
    following details:
    Exchange rate '00', amount '             8.00-' and currency key
    'INR'.
    The data in the transaction currency were transferred from the
    calling application.
    System Response
    Your data cannot be processed in FI.
    Procedure
    The error is probably in the calling application.
    Technical information about the message:
    Message class....... "F5"
    Number.............. 702
    Variable 1.......... 00
    Variable 2.......... " 8.00-"
    Variable 3.......... "INR"
    Variable 4.......... " "
    Trigger Location of Runtime Error
    Program                                 SAPLMBWL
    Include                                 LMBWLU21
    Row                                     59
    Module type                             (FUNCTION)
    Module Name                             MB_POST_GOODS_MOVEMENT
    Source Code Extract
    Line
    SourceCde
    29
       when a goods movement for an inbound or outbound delivery is posted
    30
       directly from VL31N/ VL01N, XBLNR is not yet known when we call
    31
       CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
    32
       BKPF as well. There is no other way to forward XBLNR to FI as not
    33
       every document is posted by MB_CREATE -> a new function module in
    34
       MBWL for transferring the information, called by FI, meant to load
    35
       the complete function group for all MBxx postings when this isn't
    36
       required (Performance). Would be the better way to transport the
    37
       information after switching off MBxx in later release.
    38
       corresponding IMPORT ... FROM MEMORY ... can be found in
    39
       AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
    40
    l_mem_id = 'MKPF-XBLNR'.                                   " 641365
    41
    EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id.             " 641365
    42
    ENDIF.
    43
    IF xmkpf-xabln IS INITIAL.                               "note 434093
    44
    CALL FUNCTION 'MB_XAB_NUMBER_GET'.                   "note 434093
    45
    ENDIF.                                                   "note 434093
    46
    47
    ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
    48
    49
    ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
    50
    CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
    51
    EXCEPTIONS
    52
    error_message = 4.
    53
    As soon as we have started to put things into UPDATE TASK, we must
    54
    ensure that errors definitely terminate the transaction.
    55
    MESSAGE A is not sufficient because it can be catched from
    56
    external callers which COMMIT WORK afterwards, resulting in
    57
    incomplete updates. Read note 385830 for the full story.
    58
    IF NOT sy-subrc IS INITIAL.
    >>>>>
    MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
    60
    sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    61
        MESSAGE A263.
    62
    ENDIF.
    63
    Optische Archivierung
    64
    Spaete Erfassung mit Barcode
    65
    Redesign of barcode handling -> note 780365
    66
    PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
    67
    xmkpf-mjahr
    68
    barcode.
    69
    70
    MOVE-CORRESPONDING xmkpf TO emkpf.
    71
    CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
    72
    EXCEPTIONS
    73
    error_message = 4.
    74
    MOVE-CORRESPONDING xmkpf TO emkpf.
    75
    CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
    76
    EXCEPTIONS
    77
    error_message = 4.
    78
    IF NOT sy-subrc IS INITIAL.

    Hi,
    Please check the following notes
    Note 1242773 - Getting short dump when doing GR for combined requisitions
    Note 1047059 - Run time error in migo/Goods receipt
    Regards,
    Jigar

  • Runtime error when executing F4 help on 0FISPER or 0FISCYEAR

    Hi experts,
    I got a problem on F4 help.
    When executing F4 help on 0FISPER or 0FISCYEAR using tcode LISTCUBE,
    abap dump occurs. The problem also exists when run query in BEx analyzer.
    My BW version is NW2004s. And SAPKW70012 has been implemented.
    Thanks very much for any advices.
    <b>The error message when run in BEx analyzer:</b>
    System error in program SAPLRRS2 and form EXTRA_FIELDS_SET-01- (see long
    text)
        Message no. BRAIN299
    Diagnosis
        This internal error is an intended termination resulting from a program
        state that is not permitted.
    Procedure
        Analyze the situation and inform SAP.
        If the termination occurred when you executed a query or Web template,
        or during interaction in the planning modeler, and if you can reproduce
        this termination, record a trace (transaction RSTT).
        For more information about recording a trace, see the documentation for
        the trace tool environment as well as SAP Note 899572.
    <b>And the ABAP dump log:</b>
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_RSR_PROPAGATE_X
    Date and Time          2007.04.28 15:08:47
    Short text
    An exception occurred that was not caught.
    What happened?
    The exception 'CX_RSR_PROPAGATE_X' was raised, but it was not caught anywhere
    along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
    'CL_RS_BASE====================CP' has to be
    terminated.
    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 which is explained in detail below.
    The exception, which is assigned to class 'CX_RSR_PROPAGATE_X', was not caught
    and
    therefore caused a runtime error.
    The reason for the exception is:
    No text available for this exception
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_SY_NO_HANDLER", which was raised in the program
    "CL_RSMD_RS_BUILD_QUERY========CP",
    specifically in line 1 of the (include) program
    "CL_RSMD_RS_BUILD_QUERY========CM00Y".
    The cause of the exception was:
    An exception with the type CX_RS_SQL_ERROR_SILENT occurred, but was neither
    handled locally, nor declared in a RAISING clause
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_RS_SQL_ERROR_SILENT", which was raised in the program
    "CL_RSDRS_SQL_QUERY============CP",
    specifically in line 288 of the (include) program
    "CL_RSDRS_SQL_QUERY============CM00J".
    The cause of the exception was:
    No text available for this exception
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_SQL_EXCEPTION", which was raised in the program
    "CL_SQL_STATEMENT==============CP",
    specifically in line 32 of the (include) program
    "CL_SQL_STATEMENT==============CM004".
    The cause of the exception was:
    Invalid object name 'T009C'.
    How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "UNCAUGHT_EXCEPTION" "CX_RSR_PROPAGATE_X"
    "CL_RS_BASE====================CP" or "CL_RS_BASE====================CM005"
    "X_PROPAGATE"
    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... "sapdev2"
    Network address...... "192.168.1.74"
    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... "SAPDEV2"
    Database type..... "MSSQL"
    Database name..... "BW1"
    Database user ID.. "bw1"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Sep 1 2006 00:19:17"
    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version. "SQL_Server_8.00 "
    Patch level. 75
    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"
    Memory consumption
    Roll.... 16192
    EM...... 14617568
    Heap.... 0
    Page.... 163840
    MM Used. 4553264
    MM Free. 663776
    User and Transaction
    Client.............. 100
    User................ "HANDLCR"
    Language key........ 1
    Transaction......... "LISTCUBE "
    Program............. "CL_RS_BASE====================CP"
    Screen.............. "SAPMSHLP 0600"
    Screen line......... 7
    Information on where terminated
    Termination occurred in the ABAP program "CL_RS_BASE====================CP" -
    in "X_PROPAGATE".
    The main program was "GP9QWV49ZUMYUSW6JLZIZ85P81N ".
    In the source code you have the termination point in line 12
    of the (Include) program "CL_RS_BASE====================CM005".
    Source Code Extract
    Line
    SourceCde
    1
    METHOD X_PROPAGATE .
    2
    3
    DATA: l_r_x TYPE REF TO cx_rs_no_check.
    4
    5
    TRY.
    6
    l_r_x ?= i_r_root.
    7
    CATCH cx_root.
    8
    CLEAR l_r_x.
    9
    ENDTRY.
    10
    11
    IF l_r_x IS INITIAL.
    >>>>>
    RAISE EXCEPTION TYPE cx_rsr_propagate_x
    13
    EXPORTING
    14
    previous = i_r_root.
    15
    ELSE.
    16
    RAISE EXCEPTION l_r_x.
    17
    ENDIF.
    18
    19
    ENDMETHOD.

    I got reply from SAP. The problem can be solved by running program RSDG_XPRA_IOBJ_TO_NW05. Note 939484 describes this.
    Note 939484 - Input help for tech characteristic and time characteristics
    Summary
    Symptom
    You upgraded to SAP NetWeaver 2004s. An open SQL error occurs when you execute input help for a technical characteristic, a time characteristic or a unit.
    The 'SAPSQL_INVALID_FIELDNAME' short dump in the 'CL_RSDM_READ_MASTER_DATA' class indicates that these characteristics have not been maintained. This error may also occur when you activate InfoProviders, for example.
    The error MAY occur for the following InfoObjects:
    0CALMONTH
    0CALMONTH2
    0CALQUART1
    0CALQUARTER
    0CALWEEK
    0CALYEAR
    0CURRENCY
    0FISCPER
    0FISCPER3
    0FISCVARNT
    0FISCYEAR
    0LOGSYS
    0SOURSYSTEM
    0UNIT
    0WEEKDAY1
    0RATE_TYPE
    0DATE
    0LANGU
    Other terms
    Input help, F4, 0CALMONTH, 0CALMONTH2, 0CALQUART1, 0CALQUARTER, 0CALWEEK, 0CALYEAR, 0CURRENCY, 0FISCPER, 0FISCPER3, 0FISCVARNT, 0FISCYEAR, 0LOGSYS, 0SOURSYSTEM, 0UNIT, 0WEEKDAY1, 0RATE_TYPE, 0DATE, 0LANGU, RSDG_XPRA_IOBJ_TO_NW05
    Reason and Prerequisites
    The problem can have the following causes:
    The characteristic does not have any master data, although you did define a master data read class.
    There is no generated master data table for the characteristic (for example, 0CURRENCY) and you have not defined a corresponding master data read class in the meta data.
    Solution
    Technical characteristics and time characteristics were delivered again for SAP NetWeaver 2004s with new properties. The first time you call the data warehousing workbench, the system activates the technical content. If the (time) characteristic already exists in the active version, the system does not copy it from the technical content again.  For SAP NetWeaver 2004s, however, the following conditions must be fulfilled:
    The characteristic has the property "With master data", which ensures that the master data read class functions correctly.
    If the active version of the characteristic does not have any master data, copy the characteristic from the content again. Make any necessary adjustments. Ensure that the "With master data" property is set.
    The characteristic does not have a generated table, rather it has its own table, delivered by SAP (for example, unit 0CURRENCY -> table TCURC). The definition of the characteristic must include a relevant master data read class (for example, unit 0CURRENCY -> class CL_RSMD_RS_0CURRENCY).
    The RSDG_XPRA_IOBJ_TO_NW05 XPRA defines a master data read class automatically. This XPRA is executed when you upgrade. It may, however, occur, that the XPRA is not executed successfully. If this happens, you can execute the XPRA again manually.
    Start Transaction SE38.
    Enter the name RSDG_XPRA_IOBJ_TO_NW05 in the 'Program' field.
    Choose 'Execute' to execute the program.

  • Runtime error alv list report out put

    Runtime Errors         GETWA_NOT_ASSIGNED
    Date and Time          03.03.2014 13:11:56
    Short text
         Field symbol has not yet been assigned.
    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
         You attempted to access an unassigned field symbol
    (data segment 93).
    This error may occur if
    - You address a typed field symbol before it has been set with
      ASSIGN
    - You address a field symbol that pointed to the line of an
      internal table that was deleted
    - You address a field symbol that was previously reset using
      UNASSIGN or that pointed to a local field that no
      longer exists
    - You address a global function interface, although the
      respective function module is not active - that is, is
      not in the list of active calls. The list of active calls
      can be taken from this short dump.
    to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "GETWA_NOT_ASSIGNED" " "
    "SAPLKKBL" or "LKKBLF99"
    "GEN_FIELD_OUT2"
    If you cannot solve the problem yourself and want to send an error
    (data segment 93).
    This error may occur if
    - You address a typed field symbol before it has been set with
      ASSIGN
    - You address a field symbol that pointed to the line of an
      internal table that was deleted
    - You address a field symbol that was previously reset using
      UNASSIGN or that pointed to a local field that no
      longer exists
    - You address a global function interface, although the
      respective function module is not active - that is, is
      not in the list of active calls. The list of active calls
      can be taken from this short dump.
    to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "GETWA_NOT_ASSIGNED" " "
    "SAPLKKBL" or "LKKBLF99"
    "GEN_FIELD_OUT2"
    If you cannot solve the problem yourself and want to send an error
    Operating system..... "HP-UX"
    Release.............. "B.11.23"
    Hardware type........ "ia64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "CFLDEV01"
    Database type..... "ORACLE"
    Database name..... "CD1"
    Database user ID.. "SAPSR3"
    Terminal.......... "CFINWL0115"
    Char.set.... "C"
    SAP kernel....... 701
    created (date)... "Apr 2 2011 01:40:22"
    create on........ "HP-UX B.11.23 U ia64"
    Database version. "OCI_102 (10.2.0.4.0) "
    Patch level. 137
    Patch text.. " "
    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
    SAP database version. 701
    Operating system..... "HP-UX B.11"
    Memory consumption
        Roll.... 16192
        EM...... 20949200
        Heap.... 0
        Page.... 122880
        MM Used. 3677872
        MM Free. 509344
    User and Transaction
        Client.............. 200
        User................ "GUEST"
        Language key........ "E"
        Transaction......... "SE38 "
        Transactions ID..... "5311AF68E99111BDE1000000C009C834"
        Program............. "SAPLKKBL"
        Screen.............. "SAPLKKBL 0500"
        Screen line......... 3
    Information on where terminated
        Termination occurred in the ABAP program "SAPLKKBL" - in "GEN_FIELD_OUT2".
        The main program was "ZTEST_11 ".
        In the source code you have the termination point in line 2844
        of the (Include) program "LKKBLF99".
    Source Code Extract
    Line  SourceCde
    2814       gs_sfc97 = gs_out_fieldcat.
    2815     when 98.
    2816       assign component gs_out_fieldcat-fieldname
    2817              of structure t_outtab_slave to <fs98>.
    2818       gs_sfc98 = gs_out_fieldcat.
    2819     when 99.
    2820       assign component gs_out_fieldcat-fieldname
    2821              of structure t_outtab_slave to <fs99>.
    2822       gs_sfc99 = gs_out_fieldcat.
    2823   endcase.
    2824 endform.                    "field_assign_hier_slave
    2825 *---------------------------------------------------------------------*
    2826 *       FORM GEN_FIELD_OUT2                                           *
    2827 *---------------------------------------------------------------------*
    2828 *       ........                                                      *
    2829 *---------------------------------------------------------------------*
    2830 form gen_field_out2.
    2831   field-symbols <l_initial>.
    2832
    2833   case gs_out-field_colcount.
    2834     when 001.
    2835       if gs_out_flags-slave ne 'X'.
    2836         assign <fm01> to <field>.
    2837         gs_fc = gs_mfc01.
    2838       else.
    2839         assign <fs01> to <field>.
    2840         gs_fc = gs_sfc01.
    2841       endif.
    2842     when 002.
    2843       if gs_out_flags-slave ne 'X'.
    >>>>>         assign <fm02> to <field>.
    2845         gs_fc = gs_mfc02.
    2846       else.
    2847         assign <fs02> to <field>.
    2848         gs_fc = gs_sfc02.
    2849       endif.
    2850     when 003.
    2851       if gs_out_flags-slave ne 'X'.
    2852         assign <fm03> to <field>.
    2853         gs_fc = gs_mfc03.
    2854       else.
    2855         assign <fs03> to <field>.
    2856         gs_fc = gs_sfc03.
    2857       endif.
    2858     when 004.
    2859       if gs_out_flags-slave ne 'X'.
    2860         assign <fm04> to <field>.
    2861         gs_fc = gs_mfc04.
    2862       else.
    2863         assign <fs04> to <field>.
    Contents of system fields
    Name     Val.
    Name     Val.
    SY-SUBRC 4
    SY-INDEX 2
    SY-TABIX 0
    SY-DBCNT 1
    SY-FDPOS 80
    SY-LSIND 0
    SY-PAGNO 1
    SY-LINNO 4
    SY-COLNO 13
    SY-PFKEY STANDARD
    SY-UCOMM
    SY-TITLE Sales nformation
    SY-MSGTY I
    SY-MSGID SF
    SY-MSGNO 616
    SY-MSGV1 ZTEST_11
    SY-MSGV2 RE
    SY-MSGV3 EN
    SY-MSGV4
    SY-MODNO 0
    SY-DATUM 20140303
    SY-UZEIT 131156
    SY-XPROG SAPCNVE
    SY-XFORM CONVERSION_EXIT
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
          Name
       10 FORM         SAPLKKBL                            LKKBLF99                             2844
          GEN_FIELD_OUT2
        9 FORM         SAPLKKBL                            LKKBLF99                              797
          GEN_LINE_OUT
        8 FORM         SAPLKKBL                            LKKBLF98                             1359
          DATA_OUT_SIMPLE
        7 FORM         SAPLKKBL                            LKKBLF01                              457
          LIST_OUTPUT_NEW
        6 FORM         SAPLKKBL                            LKKBLF01                             6205
          FIRST_LIST_DISPLAY
        5 MODULE (PBO) SAPLKKBL                            LKKBLO01                               11
          LIST_DISPLAY
        4 FUNCTION     SAPLKKBL                            LKKBLU01                              441
          K_KKB_LIST_DISPLAY
        3 FUNCTION     SAPLSALV                            LSALVU07                              504
          REUSE_ALV_LIST_DISPLAY
        2 FORM         ZTEST_11                            ZTEST_11                              181
          DISPLAY
        1 EVENT        ZTEST_11                            ZTEST_11                              103
          START-OF-SELECTION
    Chosen variables
    Name
    Val.
          10 Ty.          FORM
    e  GEN_FIELD_OUT2
    SFC22
    0000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000
    0000222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000
    OUT-FIELD_COLCOUNT
    2
    0000
    0002
    UMMY$$
    0000
    0000
    2222
    0000
    REPID
    SAPLKKBL
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5454444422222222222222222222222222222222
    310CBB2C00000000000000000000000000000000
    OUT_FLAGS-SLAVE
    0
       0
       2
       0
    PACE
       0
       0
       2
       0
    FM01>
       0000
       0000
       2222
       0000
    FIELD>
       0000
       0000
       2222
       0000
    S_FC
       ####BSARK                         1
       0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
       0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
       0000454542222222222222222222222222322222222222222222222222222222222222222222222222222222222222
       01012312B0000000000000000000000000100000000000000000000000000000000000000000000000000000000000
    S_MFC01
       ####BSARK                         1
       0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

    this is a report n im getiing runtime error Runtime Errors         GETWA_NOT_ASSIGNED   give the solution
    TABLES : VBAK , VBAP , KNA1.
    TYPE-POOLS : SLIS.
    TYPES : BEGIN OF TY_VBAP,
             matnr   type    matnr,
             vbeln   type    vbeln,      " order no
             ARKTX   type    ARKTX,      "item name
             KWMENG  type    KWMENG,     " order qua.
             audat   type    audat,      " SD document item date (incoming or outgoing date)
             posnr   type    posnr,
             END OF TY_VBAP.
    TYPES : BEGIN OF TY_KNA1,
             NAME1 TYPE NAME1,
    *        KUNNR TYPE KUNNR,
             END OF TY_KNA1.
    TYPES : BEGIN OF TY_VBAK,
             VTWEG   type   VTWEG,   " Distribution Channel
             BSARK   type   BSARK,   "Customer purchase order type
             END OF TY_VBAK.
    TYPES : BEGIN OF TY_FINAL,
             matnr   type    VBAP-matnr,
             vbeln   type    VBAP-vbeln,      " order no
             ARKTX   type    VBAP-ARKTX,      "item name
             KWMENG  type    VBAP-KWMENG,     " order qua.
             audat   type    VBAP-audat,      " SD document item date (incoming or outgoing date)
             posnr   type    VBAP-posnr,
             VTWEG   type    VBAK-VTWEG,   " Distribution Channel
             BSARK   type    VBAK-BSARK,   "Customer purchase order type
             NAME1   TYPE    KNA1-NAME1,
    *        KUNNR   TYPE    KNA1-KUNNR,
             END OF TY_FINAL.
    DATA : IT_VBAP TYPE TABLE OF TY_VBAP,
            IT_VBAK TYPE TABLE OF TY_VBAK,
            IT_KNA1 TYPE TABLE OF TY_KNA1,
            IT_FINAL1 TYPE TABLE OF TY_FINAL,
            IT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV.
    DATA : WA_VBAP LIKE LINE OF IT_VBAP,
            WA_VBAK LIKE LINE OF IT_VBAK,
            WA_KNA1 LIKE LINE OF IT_KNA1,
            WA_FINAL LIKE LINE OF IT_FINAL1,
            WA_FIELDCAT TYPE          SLIS_FIELDCAT_ALV.
    INITIALIZATION.
    SELECTION-SCREEN BEGIN OF BLOCK BL WITH FRAME TITLE TEXT-001.
         SELECT-OPTIONS :
                         SO_NO     FOR VBAP-VBELN,
                         M_NO      FOR VBAP-MATNR,
                         SO_DATE   FOR VBAP-AUDAT OBLIGATORY.
    SELECTION-SCREEN END OF BLOCK BL.
         START-OF-SELECTION.
         SELECT VBELN MATNR AUDAT ARKTX KWMENG POSNR
            FROM VBAP INTO CORRESPONDING FIELDS OF TABLE IT_FINAL1 WHERE VBELN IN SO_NO
                                                                     AND MATNR IN M_NO
                                                                     AND AUDAT IN SO_DATE.
           SELECT NAME1  FROM KNA1 INTO CORRESPONDING FIELDS OF TABLE IT_FINAL1 .
           LOOP AT IT_FINAL1 INTO WA_FINAL.
             SELECT SINGLE name1 FROM kna1 INTO WA_FINAL-name1 WHERE KUNNR = WA_FINAL-name1.
               MODIFY IT_FINAL1 FROM WA_FINAL TRANSPORTING NAME1.
           ENDLOOP.
    SELECT VTWEG BSARK FROM VBAK INTO CORRESPONDING FIELDS OF TABLE IT_FINAL1.
    *      SELECT VTWEG BSARK FROM VBAK INTO CORRESPONDING FIELDS OF TABLE IT_VBAK
    *                         FOR ALL ENTRIES IN IT_FINAL1
    *                         WHERE VTWEG = IT_FINAL1-VTWEG
    *                         AND   BSARK = IT_FINAL1-BSARK.
           LOOP AT IT_FINAL1 INTO WA_FINAL.
             READ TABLE IT_VBAK INTO WA_VBAK WITH KEY VTWEG = WA_FINAL-VTWEG.
             READ TABLE IT_VBAK INTO WA_VBAK WITH KEY BSARK = WA_FINAL-BSARK.
             IF SY-SUBRC EQ 0.
               WA_FINAL-VTWEG = WA_VBAK-VTWEG.
               WA_FINAL-BSARK = WA_VBAK-BSARK.
             ENDIF.
                   MODIFY IT_FINAL1 FROM WA_FINAL TRANSPORTING VTWEG BSARK.
             ENDLOOP.
             PERFORM BUILD.
             PERFORM DISPLAY.
    *&      Form  BUILD
    *       text
    *  -->  p1        text
    *  <--  p2        text
    form BUILD .
    *CLEAR WA_FIELDCAT.
    WA_FIELDCAT-COL_POS = '1'.
    WA_FIELDCAT-FIELDNAME = 'BSARK'.
    WA_FIELDCAT-SELTEXT_L = 'Order type'.
    APPEND WA_FIELDCAT TO IT_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-COL_POS = '2'.
    WA_FIELDCAT-FIELDNAME = 'AUFNR'.
    WA_FIELDCAT-SELTEXT_L = 'Order number'.
    APPEND WA_FIELDCAT TO IT_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-COL_POS = '3'.
    WA_FIELDCAT-FIELDNAME = 'POSNR'.
    WA_FIELDCAT-SELTEXT_L = 'Line No.'.
    APPEND WA_FIELDCAT TO IT_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-COL_POS = '4'.
    WA_FIELDCAT-FIELDNAME = 'VTWEG'.
    WA_FIELDCAT-SELTEXT_L = 'Dis Channel'.
    APPEND WA_FIELDCAT TO IT_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-COL_POS = '5'.
    WA_FIELDCAT-FIELDNAME = 'audat'.
    WA_FIELDCAT-SELTEXT_L = 'Order Date'.
    APPEND WA_FIELDCAT TO IT_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-COL_POS = '6'.
    WA_FIELDCAT-FIELDNAME = 'audat'.
    WA_FIELDCAT-SELTEXT_L = 'delivey date'.
    APPEND WA_FIELDCAT TO IT_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-COL_POS = '7'.
    WA_FIELDCAT-FIELDNAME = 'name1'.
    WA_FIELDCAT-SELTEXT_L = 'Name'.
    APPEND WA_FIELDCAT TO IT_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-COL_POS = '8'.
    WA_FIELDCAT-FIELDNAME = 'ARKTX'.
    WA_FIELDCAT-SELTEXT_L = 'Iem Name'.
    APPEND WA_FIELDCAT TO IT_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-COL_POS = '9'.
    WA_FIELDCAT-FIELDNAME = 'KWMENG'.
    WA_FIELDCAT-SELTEXT_L = 'Order quantitye'.
    APPEND WA_FIELDCAT TO IT_FIELDCAT.
    endform.                    " BUILD
    *&      Form  DISPLAY
    *       text
    *  -->  p1        text
    *  <--  p2        text
    form DISPLAY .
       CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
        EXPORTING
    *     I_INTERFACE_CHECK              = ' '
    *     I_BYPASSING_BUFFER             =
    *     I_BUFFER_ACTIVE                = ' '
          I_CALLBACK_PROGRAM             = sy-repid
    *     I_CALLBACK_PF_STATUS_SET       = ' '
    *     I_CALLBACK_USER_COMMAND        = ' '
    *     I_STRUCTURE_NAME               =
    *     IS_LAYOUT                      =
          IT_FIELDCAT                    = IT_FIELDCAT[]
    *     IT_EXCLUDING                   =
    *     IT_SPECIAL_GROUPS              =
    *     IT_SORT                        =
    *     IT_FILTER                      =
    *     IS_SEL_HIDE                    =
    *     I_DEFAULT                      = 'X'
    *     I_SAVE                         = ' '
    *     IS_VARIANT                     =
    *     IT_EVENTS                      =
    *     IT_EVENT_EXIT                  =
    *     IS_PRINT                       =
    *     IS_REPREP_ID                   =
    *     I_SCREEN_START_COLUMN          = 0
    *     I_SCREEN_START_LINE            = 0
    *     I_SCREEN_END_COLUMN            = 0
    *     I_SCREEN_END_LINE              = 0
    *     IR_SALV_LIST_ADAPTER           =
    *     IT_EXCEPT_QINFO                =
    *     I_SUPPRESS_EMPTY_DATA          = ABAP_FALSE
    *   IMPORTING
    *     E_EXIT_CAUSED_BY_CALLER        =
    *     ES_EXIT_CAUSED_BY_USER         =
         TABLES
           t_outtab                       = IT_FINAL1.
    *   EXCEPTIONS
    *     PROGRAM_ERROR                  = 1
    *     OTHERS                         = 2
       IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
       ENDIF.
    endform.                    " DISPLAY

  • Everest Shared Module Runtime Error "9"

    Hi
    I really need help on this one. We have installed BPC 7.0 for NW SP07 and release 7.00.7 for the Excel client . In BPC Client for Excel, whenever I select a dimension for selection, and then click on 'Table' I get the following error:
    Everest Shared Module
    Run Time Error "9"
    Subscript Out of Range.
    This error only appears on certain pc's, but not on others. Could anyone help me by indicating what we should update/patch etc.
    Thanks
    L.

    I have the same problem.
    In the "Everest Shared Module" popup sometimes there is Runtime Error "13" instead of Runtime Error "9".
    In every client with this problem: repaire the installation doesn't solve it. The problem persists. The only way I found is to reinstall the whole pc including Windows when the error occours. But this isn't a solution and it costs a lot of time.
    Any way to fix the "Everest Shared Module" popup problem without reinstalling the whole pc?

Maybe you are looking for

  • Sending 2 Different Data

    hi i wanted to send a string text (id) and a image byte from my phone to the servlet how can i do so? using doPost?

  • WS_FILENAME_GET is obsolete function module in ECC 6.0

    Hi Guys, The function module "WS_FILENAME_GET" was obsolete in ECC 6.0, could you please suggest me which is relevant function module in ECC 6.0. Thanks, Gourisankar.

  • Returning parts to Apple question

    I called apple out of warrenty and paid $80 for a new power brick for my display. Was getting curious what went wrong with my original brick and new 100% it was the brick that was bad so I hacked open the brick and saw the grounding point was loose.

  • New 80gb iPod works, but not shown as a disk drive... help!

    Hi, My brand new iPod is not show as a disk drive, even though it shows on iTunes, and has been updated, synchronized. Even after enabling disk use, it still isn't there. It is on the device manager, and it says that the device is working ok. I have

  • Need to share pptp vpn on OS 10.6 (NOT SERVER) to other devices on LAN?

    Hi there. I created a PPTP dail-in on a Billion router. I have a user from the UK connecting to it. It connects fine. I have another device that needs to use this tunnel to communicate with something on the other end of the tunnel - thus the Mac will