Short dump in bapi

hi gurus,
       i have a z-bapi (Z_BAPI_SB_SALESORDER_CREATE), where i added some import parameters(z-fields),
i need to populate these fields on the sales order screen 'additional data B'.. In the structure bape_vbak which in turn has a append structure zabap_vbak i added the z-fields..
now in the source code of Z_BAPI_SB_SALESORDER_CREATE  added the following code
Data :
  customdatavbak  LIKE bape_vbak,
  w_bape_vbakx TYPE bape_vbakx.
wvbak_bape_vbakx type bape_vbakx
if i_usertype <> 'NBSS'.
        MOVE I_BILLING_TYPE_OTHER to customdatavbak-ZZOBILLTYP.
       MOVE I_TYPE_SALES_ORDER_OTHER to customdatavbak-ZZOSOTYPE.
MOVE I_BILLING_COMPANY to customdatavbak-ZZBILCO.
MOVE I_BILLING_CONTACT_COMPANY to customdatavbak-ZZBILCNM.
MOVE I_BUSINESS_CONTACT_NAME to customdatavbak-ZZBUSCNM.
MOVE I_PROJECT_NAME to customdatavbak-ZZPRJNM.
MOVE I_BELL_REFERENCE_NO to customdatavbak-ZZBELLREF.
MOVE I_PS_CONTRACT_MGMT_PRIME to customdatavbak-ZZPSCMPRM.
MOVE 'BAPE_VBAK'         TO IT_EXTENSIONIN-structure.
        MOVE customdatavbak      TO IT_EXTENSIONIN-valuepart1.
        MOVE customdatavbak+240  TO IT_EXTENSIONIN-valuepart2.
        MOVE customdatavbak+480  TO IT_EXTENSIONIN-valuepart3.
        APPEND IT_EXTENSIONIN.
add check box info for: Billing Type, Other Billing Type,
             Type of Sales Order, Other Type of Salers Order.
             to VBAK.
      w_bape_vbakx-ZZBILLTYPE = 'X'.
      w_bape_vbakx-ZZOBILLTYP = 'X'.
      w_bape_vbakx-ZZSOTYPE = 'X'.
      w_bape_vbakx-ZZOSOTYPE = 'X'.
      wvbak_bape_vbakx-ZZBILCNM = 'X'.
      wvbak_bape_vbakx-ZZBUSCNM = 'X'.
      wvbak_bape_vbakx-ZZPRJNM = 'X'.
      wvbak_bape_vbakx-ZZBELLREF = 'X'.
      wvbak_bape_vbakx-ZZPSCMPRM = 'X'.
      wvbak_bape_vbakx-ZZBILCO = 'X'.
      MOVE : 'BAPE_VBAKX'  TO IT_EXTENSIONIN-structure,
              w_bape_vbakx TO IT_EXTENSIONIN-valuepart1.
      MOVE: wvbak_bape_vbakx TO IT_EXTENSIONIN-valuepart2.
      APPEND IT_EXTENSIONIN.
      clear IT_EXTENSIONIN.
After this i am calling the FMCALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
           EXPORTING
                order_header_in     = IT_ORDER_HEADER
           IMPORTING
                salesdocument       = E_SALESDOCUMENT
           TABLES
                return              = T_RETURNTBL
                order_items_in      = IT_ORDER_ITEMS_IN
                order_partners      = IT_ORDER_PARTNERS
                order_schedules_in  = IT_ORDER_SCHED_IN
                order_conditions_in = IT_ORDER_COND_IN
                order_text          = IT_ORDER_TEXT
                extensionin         = IT_EXTENSIONIN.
but in the include LVBAK001 i am getting short dump  SAYING "Invalid subfield access: Offset and length too large"
THIS IS THE PLACE I AM GETTING DUMP
Daten übertragen * CHECKMAN / UNICODE
              call method cl_abap_container_utilities=>fill_container_c
                   exporting
                      im_value     = da_bape_vbak
                   importing
                      ex_container = ch_parex+lenstruc(da_length_bape_vbak)
                   exceptions
                      illegal_parameter_type = 1
                      others                 = 2.
PLEASE HELP ME...

issue solved

Similar Messages

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

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

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

  • Short Dump on BAPI_TRANSACTION_COMMIT with destination NONE

    Hi All
    I am using SAP-PM with Compatible Unit(CU) functionality in ECC6 environment.
    After we release the CU design to Generate order we get SHORT DUMP.
    Any help will be of great help.
    I am pasting the details from the dump file here.
    Please let me know.
    Appretaite your help.
    Thanks
    Meghana
    Runtime Errors         CALL_FUNCTION_REMOTE_ERROR
    Date and Time          27.08.2007 18:01:10
    Short text
    "The current application triggered a termination with a short dump."
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "/***/SAPLCUORDER_N" had to be terminated because it
    has
    come across a statement that unfortunately cannot be executed.
    The error occurred during an RFC call to another system.
    In the target system, a short dump has been written as well.
    More detailed information on the error cause can be found there.
    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 error occurred when executing a REMOTE FUNCTION CALL.
    It was logged under the name "MESSAGE_TYPE_X"
    on the called page.
    How to correct the error
    Please refer to the notes described in the
    short dump.
    System environment
    SAP-Release 700
    Application server... "MB1ES1005"
    Network address...... "10.191.97.206"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "2x Intel 801586"
    Character length.... 16 Bits
    Pointer length....... 32 Bits
    Work process number.. 3
    Shortdump setting.... "full"
    Database server... "MB1ES1005"
    Database type..... "ORACLE"
    Database name..... "EC6"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Jul 25 2007 00:57:05"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "OCI_10201_SHARE (10.2.0.1.0) "
    Patch level. 121
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
    NT 6.0"
    Memory consumption
    Roll.... 8176
    EM...... 14633136
    Heap.... 0
    Page.... 131072
    MM Used. 5005432
    MM Free. 1263944
    User and Transaction
    Client.............. 200
    User................ 10086330
    Language key........ "E"
    Transaction......... "/***/DESIGN "
    Transactions ID..... "409954DC5D77F1C58E2D0013725D3B3B"
    Program............. "/***/SAPLCUORDER_N"
    Screen.............. "/***/SAPLCUORDER_N 2000"
    Screen line......... 34
    Information on where terminated
    Termination occurred in the ABAP program "/***/SAPLCUORDER_N" - in
    "SAVE_DESIGN".
    The main program was "/***/SAPLCUORDER_N ".
    In the source code you have the termination point in line 594
    of the (Include) program "/***/LCUORDER_NF07".
    Source Code Extract
    Line
    SourceCde
    564
    ENDIF .
    565
    ENDLOOP .
    566
    IF l_ret-type = 'E' OR
    567
    l_ret-type = 'A' .
    568
    CLEAR: save_okcode .
    569
    570
    Show Messages
    571
    CALL FUNCTION '/***/N_LOG_ADD_MSG'
    572
    EXPORTING
    573
    i_log_type = 'G'
    574
    TABLES
    575
    t_ret      = t_ret.
    576
    PERFORM log_order_create_show  .
    577
    Show first Message
    578
         MESSAGE ID l_ret-id TYPE l_ret-type NUMBER l_ret-number
    579
         WITH
    580
           l_ret-message_v1 l_ret-message_v2
    581
           l_ret-message_v3 l_ret-message_v4.
    582
    CALL FUNCTION '/***/N_DESIGN_INIT' .
    583
    ELSE .
    584
    IF g_design_mode = con_mode_crea.
    585
    Need to update DMS documents with real design number
    586
    PERFORM document_prepare_002 USING con_desnum_tmp_1
    587
    lv_desnum.
    588
    ENDIF.
    589
    Commit design BAPI's
    590
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' .
    591
    592
    IF save_okcode = con_order.
    593
    Commit order BAPI's
    >>>>>
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    595
    DESTINATION 'NONE'.
    596
    597
    call of fct. RFC_CONNECTION_CLOSE is important to get a new
    598
    initial roll area with initial internal tables next time
    599
    CALL FUNCTION 'RFC_CONNECTION_CLOSE'
    600
    EXPORTING
    601
    destination          = 'NONE'
    602
    EXCEPTIONS
    603
    destination_not_open = 1
    604
    OTHERS               = 2.
    605
    ENDIF.
    606
    607
    IF lv_desnum IS INITIAL .
    608
    lv_desnum = /***/cudesign-desnum .
    609
    ENDIF .
    610
    SET PARAMETER ID '/***/DESNUM' FIELD lv_desnum .
    611
        Changes saved
    612
    MESSAGE ID '/***/MSG' TYPE 'S' NUMBER '529' WITH lv_desnum .
    613
    ENDIF .
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    2000
    SY-UCOMM
    CU01
    SY-TITLE
    Change Design: 50000109
    SY-MSGTY
    X
    SY-MSGID
    00
    SY-MSGNO
    341
    SY-MSGV1
    MESSAGE_TYPE_X
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20070827
    SY-UZEIT
    180110
    SY-XPROG
    SAPMSSY1
    SY-XFORM
    XAB_READ
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    4 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF07                    594
    SAVE_DESIGN
    3 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF07                   2616
    CHECK_AND_SAVE_F07
    2 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF04                    311
    USER_COMMAND_D2000
    1 MODULE (PAI) /***/SAPLCUORDER_N                  /***/LCUORDER_NI05                     28
    USER_COMMAND_2000
    Chosen variables
    Name
    Val.
    No.       4 Ty.          FORM
    Name  SAVE_DESIGN
    %_DUMMY$$
    2222
    0000
    0000
    0000
    CL_GUI_RESOURCES=>COL_TEXTAREA
    31
    1000
    F000
    G_DESIGN_MODE
    R
    5
    2
    0
    0
    CON_MODE_CREA
    I
    4
    9
    0
    0
    GT_NODE_CUI
    Table[initial]
    SY-REPID
    /***/SAPLCUORDER_N
    2454254544545445542222222222222222222222
    F35DF310C35F2452FE0000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    CON_DESNUM_TMP_1
    TM00000001CY
    543333333345
    4D0000000139
    000000000000
    000000000000
    LV_DESNUM
    222222222222
    000000000000
    000000000000
    000000000000
    SAVE_OKCODE
    CU01
    4533222222222222222222222222222222222222222222222222222222222222222222
    3501000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    CON_ORDER
    CU01
    4533222222222222222222222222222222222222222222222222222222222222222222
    3501000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    SY-XPROG
    SAPMSSY1
    5454555322222222222222222222222222222222
    310D339100000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    CON_DELETE
    LVMS
    4545222222222222222222222222222222222222222222222222222222222222222222
    C6D3000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    No.       3 Ty.          FORM
    Name  CHECK_AND_SAVE_F07
    CL_GUI_ALV_GRID=>MC_MB_VIEW
    &MB_VIEW
    2445544522222222222222222222222222222222222222222222222222222222222222
    6D2F695700000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    GT_OP
    Table IT_303[2x1320]
    PROGRAM=/***/SAPLCUORDER_NDATA=GT_OP
    Table reference: 118
    TABH+  0(20) = 7039FC3C5824DB3C00000000760000002F010000
    TABH+ 20(20) = 0200000028050000FFFFFFFF0400000030140000
    TABH+ 40( 8) = 08000000C1308001
    store        = 0x7039FC3C
    ext1         = 0x5824DB3C
    shmId        = 0     (0x00000000)
    id           = 118   (0x76000000)
    label        = 303   (0x2F010000)
    fill         = 2     (0x02000000)
    leng         = 1320  (0x28050000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000093
    occu         = 8     (0x08000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    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         = 0x2010FC3C
    pgHook       = 0x00000000
    idxPtr       = 0x00000000
    shmTabhSet   = 0x00000000
    id           = 234   (0xEA000000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 8     (0x08000000)
    lineAlloc    = 8     (0x08000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x60B7153D
    collHook     = 0x00000000
    ext2         = 0x1024DB3C
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xE00FFC3C
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    G_BADI_PROGRAM
    2222222222222222222222222222222222222222
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    LOG_ERROR
    2
    0
    0
    0
    CON_BUTT_DELETED
    @11QDelete@
    43355466676422222222222222222222222222222222
    011C145C545000000000000000000000000000000000
    00000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000
    G_CU_EXIT_CU_EXPLODE
    F0000000
    F0000000
    /***/CUDESIGN-OBJNR
    CY00000000000000008835
    4533333333333333333333
    3900000000000000008835
    0000000000000000000000
    0000000000000000000000
    CL_GUI_RESOURCES=>COL_TEXTAREA
    31
    1000
    F000
    G_SEC_COUNT
    0
    0000
    0000
    LV_UPD
    X
    5
    8
    0
    0
    %_SPACE
    2
    0
    0
    0
    GS_ROW_NO
    0.0.0.1.
    0000
    1000
    0000
    0000
    SCREEN
    /***/CUDESIGN-GLTRP
    2454245445444244555222222222222222222222222222222222222222222222222222222222222222222222222222
    F35DF3545397ED7C420000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SY-MSGID
    00
    33222222222222222222
    00000000000000000000
    00000000000000000000
    00000000000000000000
    SWO_%CONTAINER
    000000000
    2222222222222222222222222222222233333333322222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SPACE
    2
    0
    0
    0
    SY-MSGNO
    341
    333
    341
    000
    000
    /***/CVCUI-CUTYP
    2
    0
    0
    0
    SY-MSGV1
    MESSAGE_TYPE_X
    44554445555455222222222222222222222222222222222222
    D533175F4905F8000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV2
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV3
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    No.       2 Ty.          FORM
    Name  USER_COMMAND_D2000
    /***/CVCUI
    0.0.0.0.0.0.0.1.                                                                         000000
    2220000000022222222222222222222222222222222222222222222222222222222222222222222222223333332222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SYST-REPID
    /***/SAPLCUORDER_N
    2454254544545445542222222222222222222222
    F35DF310C35F2452FE0000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    CON_MODE_COPY
    C
    4
    3
    0
    0
    LT_BAPI_RETURN
    Table IT_1778[2x1088]
    PROGRAM=/***/SAPLCUORDER_NFORM=USER_COMMAND_D2000DATA=LT_BAPI_RETURN
    Table reference: 310
    TABH+  0(20) = 8837083D407E1C3D0000000036010000F2060000
    TABH+ 20(20) = 0200000040040000FFFFFFFF04000000F0170000
    TABH+ 40( 8) = 08000000C1308101
    store        = 0x8837083D
    ext1         = 0x407E1C3D
    shmId        = 0     (0x00000000)
    id           = 310   (0x36010000)
    label        = 1778  (0xF2060000)
    fill         = 2     (0x02000000)
    leng         = 1088  (0x40040000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000113
    occu         = 8     (0x08000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 1
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x50C6073D
    pgHook       = 0x00000000
    idxPtr       = 0x00000000
    shmTabhSet   = 0x00000000
    id           = 1534  (0xFE050000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 8     (0x08000000)
    lineAlloc    = 8     (0x08000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    collHook     = 0x00000000
    ext2         = 0x6067033D
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xE82F063D
    delta_head   = 0000000000000000CF000000000000000400000020180000000000004D00430055004F000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    CON_MODE_ORDE
    O
    4
    F
    0
    0
    TGSBT
    22222222222222222222222222222222222222
    00000000000000000000000000000000000000
    00000000000000000000000000000000000000
    00000000000000000000000000000000000000
    CL_GUI_RESOURCES=>COL_TEXTAREA
    31
    1000
    F000
    LS_NUMBERS-AUFNR_NEW
    000001000677
    333333333333
    000001000677
    000000000000
    000000000000
    T024I
    200UT10100PG for Term & Comp
    33355333335426672567622246672222222222222222
    20054101000706F20452D0603FD00000000000000000
    00000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000
    LS_T399X
    200UT10UM01                  X    INST  30UT01UT01
    3335533543322222222222222222252222445522335533553322222222222222222222222222222222222222222222
    20054105D01000000000000000000800009E3400305401540100000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    CON_VBKZ_U
    U
    5
    5
    0
    0
    /***/CU_ORDER_IO-DISP_FACTOR
    2097152
    0
    0
    LS_DESIGN
    200########000050000109DDCY00000000000000008835PROFILE1  0001UT10UM0100220100MWH001
    333D5FC807333333333333344453333333333333333333355444443223333553354333333333345433322222222222
    200CDB1E02B00005000010944390000000000000000883502F69C5100000154105D0100220100D7800100000000000
    000599F215300000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0004C91D3DB00000000000000000000000000000000000000000000000000000000000000000000000000000000000
    /***/CUDESIGN
    200########000050000109DDCY00000000000000008835PROFILE1  0001UT10UM0100220100MWH001
    333D5FC807333333333333344453333333333333333333355444443223333553354333333333345433322222222222
    200CDB1E02B00005000010944390000000000000000883502F69C5100000154105D0100220100D7800100000000000
    000599F215300000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0004C91D3DB00000000000000000000000000000000000000000000000000000000000000000000000000000000000
    G_DROP_COUNT
    0
    0000
    0000
    LS_DESIGN-DESNUM
    000050000109
    333333333333
    000050000109
    000000000000
    000000000000
    No.       1 Ty.          MODULE (PAI)
    Name  USER_COMMAND_2000
    GT_SELTAB_INIT
    Table[initial]
    Internal notes
    The termination was triggered in function "RfcExtendedReceive"
    of the SAP kernel, in line 422 of the module
    "//bas/700_REL/src/krn/rfc/abrfcrcv.c#4".
    The internal operation just processed is "FUNC".
    Internal mode was started at 20070827180011.
    Status of connection:
    RFC state: " "
    RFC error text: "RFC_ERROR_SYSTEM_FAILURE"
    CPI-C error text: "The current application triggered a termination with a short
    dump."
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    SAP (R) - R/3(TM) Callstack, Version 1.0
    Copyright (C) SAP AG. All rights reserved.
    Callstack without Exception:
    App       : disp+work.EXE (pid=26488)
    When      : 8/27/2007 18:1:10.942
    Threads   : 2
    Computer Name       : MB1ES1005
    User Name           : ec6adm
    Number of Processors: 2
    Processor Type: x86 Family 15 Model 4 Stepping 10
    Windows Version     : 5.2 Current Build: 3790
    State Dump for Thread Id 5e10
    eax=000f93c0 ebx=0000042c ecx=00003118 edx=00000000 esi=0000042c edi=00000000
    eip=7c82ed54 esp=056d71f0 ebp=056d7260 iopl=0         nv up ei ng nz ac po cy
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00200297
    function : KiFastSystemCallRet
    7c82ed54 c3               ret
    7c82ed55 8da42400000000   lea     esp,[esp]              ss:056d71f0=7c822124
    7c82ed5c 8d642400         lea     esp,[esp]              ss:62bd5803=00000000
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    056d7260 77e6ba42 0000042c 0001d4c0 00000000 056d7298 ntdll!KiFastSystemCallRet
    056d7274 0109504d 0000042c 0001d4c0 00000001 7c38b5c8 kernel32!WaitForSingleObject
    056d7298 00582118 00582151 7c38b5c8 7c38b5c8 7c38b5c8 disp+work!NTDebugProcess  (ntstcdbg.c (501))
    056d729c 00582151 7c38b5c8 7c38b5c8 7c38b5c8 01e9b1b8 disp+work!NTStack  (dptstack.c (1367))
    056d72b8 00582185 7c38b5c8 00000000 008b7ec8 7c38b5c8 disp+work!CTrcStack2  (dptstack.c (352))
    056d72c4 008b7ec8 7c38b5c8 00000000 005f0059 00330030 disp+work!CTrcStack  (dptstack.c (182))
    056d72e8 008bb39f 00711076 056d8018 056d7be8 00200020 disp+work!rabax_CStackSave [abrabax.c (7063)
    056d7b90 009eca8b 020b9e4c 020b9e14 000001a6 5d88acf0 disp+work!ab_rabax  (abrabax.c (1243))
    056d7bcc 009ed19e 00000003 00711076 00000020 00000000 disp+work!rcv_message  (abrfcrcv.c (422))
    056d8068 009ed29d 00000003 00000000 00710c47 056d80c0 disp+work!RfcExtendedReceive [abrfcrcv.c (14
    056d808c 00714873 00000003 00710c47 056d80c0 00711076 disp+work!ab_rfcreceive  (abrfcrcv.c (59))
    056d80e4 0071886b 2694a7c8 2694a7cc 2694a7cc 2694a7cc disp+work!jfunc_get  (abfunc.c (5103))
    056d89f4 007191d0 00000003 000000b4 00000000 05e8b7c0 disp+work!jfunc_nonstandard [abfunc.c (1655)
    056dcfb0 006e3e2d 00000003 3ced8f90 00000000 056dd018 disp+work!ab_jfunc  (abfunc.c (554))
    056dd018 0081cb5e 00000000 3ced8f90 056dd164 3cedb514 disp+work!ab_extri  (abextri.c (552))
    056dd02c 00897dbd 00000000 3cedae46 005bf4cd 3ceda13c disp+work!ab_xevent  (abrunt1.c (281))
    056dd038 005bf4cd 3ceda13c 000000ea 3cedae46 00000000 disp+work!ab_dstep  (abdynpro.c (492))
    056dd164 005c25be 3ced8f90 3ced8f90 056dfc78 00000000 disp+work!dynpmcal  (dymainstp.c (2398))
    056dd178 005c1def 00000001 3ced8f90 00000003 056dfc78 disp+work!dynppai0  (dymainstp.c (1004))
    056dd194 00595e69 3ced8f90 00000001 00000001 00000001 disp+work!dynprctl  (dymainstp.c (360))
    056dfcec 00490e06 00000004 0049d15f 00000004 01dadd00 disp+work!dynpen00  (dymain.c (1628))
    056dfcf4 0049d15f 00000004 01dadd00 00000003 00000002 disp+work!Thdynpen00  (thxxhead.c (4773))
    056dfee0 0049d6d6 00000001 00000000 00000000 00430000 disp+work!TskhLoop  (thxxhead.c (4455))
    056dff00 00421c36 00000000 00000000 7ffde000 056dff60 disp+work!ThStart  (thxxhead.c (1173))
    056dff14 00401080 00000003 05876980 00000001 00000000 disp+work!DpMain  (dpxxdisp.c (1121))
    056dff60 01242970 00000003 05876980 05877a10 01cce000 disp+work!nlsui_main  (thxxanf.c (82))
    056dffc0 77e523e5 00000000 00000000 7ffde000 8967f020 disp+work!wmainCRTStartup  (crtexe.c (395))
    056dfff0 00000000 0124282d 00000000 00905a4d 00000003 kernel32!IsProcessorFeaturePresent
    State Dump for Thread Id 61fc
    eax=00000000 ebx=00000103 ecx=0587a700 edx=02714360 esi=00000000 edi=00000000
    eip=7c82ed54 esp=0799fec0 ebp=0799ff04 iopl=0         nv up ei pl zr na po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    function : KiFastSystemCallRet
    7c82ed54 c3               ret
    7c82ed55 8da42400000000   lea     esp,[esp]              ss:0799fec0=7c821514
    7c82ed5c 8d642400         lea     esp,[esp]              ss:64e9e4d3=00000000
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    0799ff04 0119030a 000006e0 00000000 00000000 0587a798 ntdll!KiFastSystemCallRet
    0799ff84 7c349565 00000000 00000000 00000000 0587a700 disp+work!SigIMsgFunc  (signt.c (610))
    0799ffb8 77e6608b 0587a700 00000000 00000000 0587a700 MSVCR71!endthreadex
    0799ffec 00000000 7c3494f6 0587a700 00000000 00000000 kernel32!GetModuleFileNameA
    List of ABAP programs affected
    Index
    Typ
    Program
    Group
    Date
    Time
    Size
    Lang.
    0
    Prg
    /***/SAPLCUORDER_N
    0
    10.08.2007
    10:12:44
    541696
    E
    1
    Typ
    /***/CUDESIGN
    0
    10.08.2007
    10:05:19
    7168
    2
    Typ
    /***/CU_ORDER_IO
    0
    10.08.2007
    09:53:38
    4096
    3
    Typ
    /***/DESTYPE
    0
    10.08.2007
    10:05:21
    2048
    4
    Typ
    /***/PRF_ORD
    0
    10.08.2007
    10:05:21
    4096
    5
    Prg
    SAPMSSYD
    0
    04.04.2007
    10:28:36
    21504
    E
    6
    Prg
    SAPFSYSCALLS
    0
    09.09.2004
    14:18:32
    8192
    E
    7
    Typ
    /***/G_CUST
    0
    10.08.2007
    09:53:39
    3072
    8
    Prg
    /***/SAPLTABLES
    8
    10.08.2007
    10:13:00
    19456
    E
    9
    Typ
    /***/G_CHAR
    0
    10.08.2007
    10:05:21
    3072
    10
    Prg
    SAPLCTCE
    10
    09.09.2004
    14:18:34
    9216
    E
    11
    Typ
    CABN
    0
    18.09.2001
    10:02:26
    12288
    12
    Prg
    SAPLICON
    12
    04.04.2007
    10:10:28
    27648
    E
    13
    Prg
    %_CICON
    12
    07.02.2006
    10:40:00
    104448
    E
    14
    Typ
    ICONT
    0
    04.04.2007
    10:10:08
    2048
    15
    Typ
    NRIV
    0
    02.04.1998
    08:14:54
    3072
    16
    Prg
    SAPLBSVA
    16
    04.04.2007
    14:47:00
    296960
    E
    17
    Typ
    /***/CU_ORDER_S_OP_N
    0
    10.08.2007
    09:53:39
    14336
    18
    Prg
    CL_GUI_CONTROL================CP
    18
    28.02.2005
    21:03:09
    112640
    E
    19
    Prg
    %_CCNTL
    18
    18.02.2005
    14:15:08
    15360
    E
    20
    Typ
    OBJ_RECORD
    0
    14.02.1998
    08:30:43
    2048
    21
    Prg
    CL_GUI_OBJECT=================CP
    21
    05.07.2005
    13:10:15
    375808
    E
    22
    Prg
    CL_GUI_CFW====================CP
    22
    28.02.2005
    21:03:09
    172032
    E
    23
    Prg
    CL_GUI_PROPS_CONSUMER=========CP
    23
    18.02.2005
    14:15:08
    30720
    E
    24
    Prg
    SAPLTHFB
    24
    04.04.2007
    13:24:38
    390144
    E
    25
    Typ
    EUDB
    0
    06.11.2003
    20:28:08
    8192
    26
    Prg
    SAPLSFES
    26
    08.08.2007
    16:46:17
    259072
    E
    27
    Prg
    SAPLSPLUGIN
    27
    09.09.2004
    14:18:36
    8192
    E
    28
    Prg
    SAPLSTTM

    Yes even i find it strange. But there is no syntax error and the fact is that it was working 2 days back.  Suddenly it has started giving us this dump.
    The code is as follows.
    Commit design BAPI's
          CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' .
          IF save_okcode = con_order.
    Commit order BAPI's
            CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
              DESTINATION 'NONE'.
    Here con_order is CU01.
    Please let me know if anybody has faced this problem earlier.
    Thanks in Advance
    Meghana

  • Dump in BAPI while fetching data

    Hi all,
    I m getting a short dump (: ' No more storage space available for extending an internal table.') in my vendor trial balance report  . The place of short dump is the BAPI which im using to fetch opening balance i.e BAPI_AP_ACC_GETKEYDATEBALANCE.
    Please find below the screen shot of the dump.
    Kindl suggest the possible solutions.
    Short text
        No more storage space available for extending an internal table.
    What happened?
        You attempted to extend an internal table, but the required space was
        not available.
    Error analysis
        The internal table "\FUNCTION-POOL=3008\DATA=XLINEITEMS[]" could not be further
         extended. To enable
        error handling, the table had to be delete before this log was written.
        As a result, the table is displayed further down or, if you branch to
        the ABAP Debugger, with 0 rows.
        At the time of the termination, the following data was determined for
        the relevant internal table:
        Memory location: "Session memory"
        Row width: 2122
        Number of rows: 2757476
        Allocated rows: 2757476
        Newly requested rows: 4 (in 1 blocks)
    How to correct the error
        The amount of storage space (in bytes) filled at termination time was:
        Roll area...................... 6216720
        Extended memory (EM)........... 4005681840
        Assigned memory (HEAP)......... 1998959040
        Short area..................... " "
        Paging area.................... 24576
        Maximum address space.......... 18446743890435787967
        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:
        "TSV_TNEW_PAGE_ALLOC_FAILED" " "
        "SAPL3008" or "L3008U05"
        "BAPI_AP_ACC_GETKEYDATEBALANCE"
    Information on where terminated
        Termination occurred in the ABAP program "SAPL3008" - in
         "BAPI_AP_ACC_GETKEYDATEBALANCE".
        The main program was "ZIBFI_VEND_TB_H1 ".
        In the source code you have the termination point in line 48
        of the (Include) program "L3008U05".
        The program "SAPL3008" was started as a background job.
        Job Name....... "ZIBFI_VEND_TB_H1"
        Job Initiator.. 108735
        Job Number..... 11490500
    Line number:
       44   PERFORM READ_KONTO USING  VENDOR
       45                             COMPANYCODE RETURN.
       46   CHECK RETURN IS INITIAL.
       47
    >>>>>   SELECT * FROM BSIK APPENDING CORRESPONDING FIELDS OF TABLE XLINEITEMS
       49     WHERE BUDAT <= KEYDATE
       50     AND   BUKRS EQ COMPANYCODE
       51     AND   LIFNR EQ VENDOR
       52     AND   BSTAT IN BSTAT.

    Only 2 ways for this:
    a) reduce the no of records
    b) ask your basis team to increase the session memory
    Regards,
    Nikhil

  • Short Dump LIST_TOPOFPAGE_OVERFLOW ???

    I am getting short dump in a custom z program with Runtime Errors LIST_TOPOFPAGE_OVERFLOW. All program does is calling a BAPI to update sales orders. I did make sure that line-count and line-size are not specified under REPORT. Tried everything I can. Does anyone have any idea on how to deal with it?
    Thanks,
    Alex

    Rob,
    The strange part that the short dump happens in standard program include LKKBLF00, main program SAPLKKBL. Here is the syntax of where it happens:
    perform top_of_page using  gt_stackit_fieldcat           
                            gt_stackt_columns             
                            gt_stackis_layout             
                            gt_stack-s_lprint              
                            gt_stack2-s_header             
                            gt_stack-listtype              
                          gt_stack-i_tabname             
                          gt_stack-i_tabname_slave       
                            gt_stack-i_callback_program    
                            gt_stack-i_callback_top_of_page.
    My program does not have top-of-page event, and all it does is populate few strctures and call BAPI_CUSTOMERCONTRACT_CHANGE. It used to work in 4.7, we recently upgraded to ECC 5.0 2004.
    Thanks,
    Alex

  • Short Dump while using BAPI_PS_PRECOMMIT to set Project Definition Status

    Hi All,
    I am getting a short dump while using BAPI_PS_PRECOMMIT for setting the Project Definition status..
    The requirement is to create a Project Definition and then set its status to REL from CRTD. For this purpose i am using the BAPI's in the following sequence :
    1. BAPI_PS_INITIALIZATION
    2. BAPI_PROJECT_MAINTAIN
    3. BAPI_BUS2001_SET_STATUS
    4. BAPI_PS_PRECOMMIT
    5. BAPI_TRANSACTION_COMMIT
    The Proj Def creation is happening successfully in step2. Interestingly, when I debug the program and stop at PRECOMMIT BAPI the program does not give a dump. I have also tried to give COMMIT WORK / WAIT FOR n SECONDS after BAPI_BUS2001_SET_STATUS, to give BAPI sometime for DB update but nothing seems to be a permanent solution.
    Please give your views on a solution for this problem..
    Thanks & Regards,
    Somil

    Can you please check how to post code in SDN ...
    I cannot read your code properly

  • BAPI_GOODSMVT_CREATE short dump while posting a GR for inbound delivery

    Dear Experts,
    I am using BAPI_GOODSMVT_CREATE to post a goods receipt for a PO using Inbound Delivery
    here is how I am populating bapi input parameters:
      lw_goodsmvt_code-gm_code = '01'.
      lw_goodsmvt_item-deliv_numb =  lw_inb_delivery_items-delivery.
      lw_goodsmvt_item-quantity = lw_inb_delivery_items-deliv_qty.
      lw_goodsmvt_item-entry_qnt = lw_goodsmvt_item-quantity
      lw_goodsmvt_item-no_more_gr = ''.
      lw_goodsmvt_item-move_type = '101'.
      lw_goodsmvt_item-mvt_ind = 'B'.
      lw_goodsmvt_item-STGE_LOC = '0001'.
        lw_goodsmvt_item-po_number and   lw_goodsmvt_item-po_item are populated as well.
    When I execute the BAPI I get the short dump
    Message Class: 'VL'
    Number = 143
    in the module MB_POST_GOODS_MVT and a reference to 385830 note.
    Would you please help me how to solve this problem?

    from the dump the error orrcurs here:
    CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
            EXCEPTIONS
              error_message = 4.
    As soon as we have started to put things into UPDATE TASK, we must
    ensure that errors definitely terminate the transaction.
    MESSAGE A is not sufficient because it can be catched from
    external callers which COMMIT WORK afterwards, resulting in
    incomplete updates. Read note 385830 for the full story.
       IF NOT sy-subrc IS INITIAL.
    >      MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
                     sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        MESSAGE A263.
       ENDIF.
    The short text of the error is: Cannot be processed with this transaction.
    Can you tell me if my BAPI Call is correct to post GR in Inbound Delivery?

  • BAPI_GOODSMVT_CREATE is directing to short dump.

    Hi,
    When i am running a BAPI(BAPI_GOODSMVT_CREATE) it is throwing an error.
    error:The FM MB_CREATE_GOODS_MOVEMENT is called up for second time.After it was called up for the first time Commit work was not done.
    But i called BAPI_Transaction commit after BAPI_GOODSMVT_CREATE but even then it was directing to short dump.
    when i am execting this FM in se38 there it is not directing to short dump but when i am using it in BADI then it is dumping.
    Helpful answer will be rewarded.

    Hey,
    Can u please explain how to handle this situation,because if i dont use commit the also it is giving the error and if i use commit then also it is giving error.
    Thanks for Replay.

  • Initial customizing loads (DNL_*) causing short dumps in R/3

    Hi,
    I'm trying to run the initail loads for the DNL_* customizing objects.  When I start a load in R3AS and check the status in R3AM1, it shows "Running".  In the CRM oubound queue (SMQ1), there is an entry for the load with status SYSFAIL.  The detailed status message is "The current application triggered a termination with a short dump". 
    The short dump in R/3 shows an error "No external system (such as CRM) connected" which occurs in function module CRM_FIRST_CALL_OPERATIONS.  Looking at the code, there seems to be a problem with the CRMRFCPAR table.  I had only one record in this table for object CUSTOMER_MAIN, so I tried adding a record with Object Name "*" and Load Type "I", but this had no effect. 
    What is the proper configuration of table CRMRFCPAR for customizing loads?  Is it possible that this error is related to some other config or a problem with the RFC connection?  These loads work fine in our quality system which is configured the same as production (as far as I can tell).
    Thanks.
    Martin

    hi,
    Maintaining Table CRMRFCPAR (SAP R/3)
    The parameters in this table indicate the RFC destinations which receive data. The required parameters include, for example: consumer, client, object name, and download type.
    You can send data to a certain consumer only in an initial download and not in a delta download by making the appropriate specifications for the data exchange.
    User- That uses the OLTP plug-in functions as data receivers
    Object name -Object name
    Destination -Specifies the destination of the CRM server
    Load Type -Restricts CRMRFCPAR entries to the initial (I) or delta (D) download.
    Out Queue - Name RFC outbound queue
    In Queue -Name RFC inbound queue
    BAPI name
    INFO -Information/Comments
    InQueue flag- Controls whether qRFC inbound queues are used on the CRM server
    Send XML -XML supports (Should data be sent in XML format?)
    Stop data -Causes the OLTP System to place data into the outbound queue.
    Regards
    sri

  • Short dump with BAPI_ACC_DOCUMENT_POST

    Dear All,
    When I try to use BAPI "BAPI_ACC_DOCUMENT_POST" for F-02 posting, I get the following short dump:
    "Syntax error in program SAPLACC9".
    "The data object GS_ACCIT does not have a component called BAPI_PARA"
    Please suggest me how can this error be removed.
    Regards,
    Kanupriya

    Hi Suneel,
    Please look at the code below:
    LOOP AT it_upload_rec.
        header-bus_act = 'RFBU'.
        header-doc_date = it_upload_rec-bldat.
        header-pstng_date = it_upload_rec-budat.               header-header_txt = 'F-02 Posting'.
        header-comp_code = 'PL10'.
        header-doc_type = 'SA'.
        header-username = sy-uname.
        APPEND header.
        CLEAR header.
        account_gl-itemno_acc = '1'.
        account_gl-gl_account = it_upload_rec-account1.
        APPEND account_gl.
        CLEAR account_gl.
        account_payable-itemno_acc = '2'.
        account_payable-vendor_no = it_upload_rec-account2.
        APPEND account_payable.
        CLEAR account_payable.
        currency_amount-itemno_acc = '1'.
        currency_amount-currency = 'INR'.
        currency_amount-amt_doccur = it_upload_rec-amount.
        APPEND currency_amount.
        CLEAR currency_amount.
      ENDLOOP.
      CALL FUNCTION 'BAPI_ACC_DOCUMENT_POST'
        EXPORTING
          documentheader          = header
    *   CUSTOMERCPD             =
    *   CONTRACTHEADER          =
       IMPORTING
      obj_type = gv_obj_type
      obj_key = gv_obj_key
      obj_sys = gv_obj_sys
        TABLES
         accountgl               = account_gl
       ACCOUNTRECEIVABLE       =
         accountpayable          = account_payable
    *   ACCOUNTTAX              =
          currencyamount          = currency_amount
    *   CRITERIA                =
    *   VALUEFIELD              =
    *   EXTENSION1              =
        return                  = it_return
    *   PAYMENTCARD             =
    *   CONTRACTITEM            =
    *   EXTENSION2              =
    *   REALESTATE              =
    Regards,
    Kanupriya

  • Purchase order print preview - Short Dump - in ME23N

    Dear Experts,
                         I am doing PO layout in PDF format . When i see print preview in me23n transaction its displaying as PDF format.
    when i close the output selection popup screen its giving short dump, saying that ' A RAISE statement in the
    program "CL_HANDLE_MANAGER_MM==========CP" raised the  exception condition "FAILURE". Pls let me know if
    anybody come across this issue.
    Thanks & Regards
    Ramesh Manoharan.

    Hi,
    Dump is a result of common work area 'cleanup' procedure inside BAPI_PO_GETDETAIL1 (module cleans memory area which transaction ME2xN expects to be filled).
    Luckily you are able to turn off this code section by adding some MM tool method call just before calling FM BAPI...
    you need only one code line - worked perfectly in my case:
    cl_mmpur_bapi_po=>put_repid( im_repid = sy-repid ).
    CALL FUNCTION 'BAPI_PO_GETDETAIL1'
         EXPORTING..............
    Regards,
    Rafał Szczerba

  • Short Dump While Changing reservation line using BAPI_ALM_ORDER_MAINTAIN

    Hello!
    I have a problem changing the reservation line using BAPI_ALM_ORDER_MAINTAIN. I am very sure that I am passing all correct parameters in BAPI. It gives short dump with type  MESSAGE_TYPE_X and main program "SAPLCOBC" or "LCOBCU02" and "READ_RESB_IND". at line
    Satz gefunden?
      IF sy-subrc <> 0.
        MESSAGE x901.                                               "n779835
      ENDIF.
    This dump comes only when I run my Transfers workbench for the first time, when I run it for the second time, it executes correctly and reservation line gets changed successfully.
    Does anyone have face such problem or have any ideas about how this can be solved??
    Please let me know if you need more information......

    Hi Km,
    Here is your answer:
    SAP Note 1269069 - BAPI_ALM_ORDER_MAINTAIN: Runtime error MESSAGE_TYPE_X
    https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1269069
    Also henceforth Pls try to navigate through service market place if you find Issues with Standard SAP Program as somebody else might have faced the same and there must be solution readily available.
    Let me know if it helps.
    Regards
    Shital
    Edited by: shital phadake on Mar 23, 2009 6:59 PM

  • WBS Conversion FM using RFC Causing Short Dumps

    Hello,
    I have been trying to validate WBS element entries by using an RFC call to a FM on the back-end.  However, I keep getting short dumps on the back-end system with 'Statement "MESSAGE E" is not allowed in this form.' message.  The custom back-end FM calls one of the CPJN FMs like CONVERSION_EXIT* that deal with WBS elements.
    So, I tried changing the custom FM to use the data element that does a the conversion instead of the FM. Now, I get a short dumps on the front-end with CALL_FUNCTION_REMOTE_ERROR with 'Key does not correspond to mask: B/0000-XXXXXXX.0.0.0' message.
    Has anyone been successful without duplicating the CONVERSION_EXIT* FMs in order to validate a WBS element entry remotely?
    Thank you in advance for any assistance.
    Regards, Dean.

    Hello Dean
    On ERP 6.0 (IDES) there is the RFC-enabled fm /SPE/WBS_ELEM_CONV_INT_EXT available.
    If you feed the fm with an external ID it tries to convert it into the corresponding internal ID and vice versa. Perhaps this fm might be useful for you.
    Probably the BAPI BAPI_PROJECT_EXISTENCECHECK is more useful (can be feed either with internal or external ID).
    Regards
      Uwe

  • Short dump in BAPI_PO_CHANGE

    HI all,
       I am using BAPI_PO_CHANGE to change the Quantity and Item text of PO items .
    The following is the function call :
    Loop at loop at z_i_item assigning <z_f_item>.
    call function 'BAPI_PO_CHANGE'
          exporting
            purchaseorder                = <z_f_item>-ebeln
         tables
           return                        = z_i_return
           poitem                        = z_i_poitem
           poitemx                       = z_i_poitemx
          poschedule                     = z_i_posch
          poschedulex                    = z_i_poschx
           potextitem                =  z_i_itemtxt .
    Endloop.
    Am filling all the internal tables in the " tables parameter " for every loop of z_i_item.
    But it throws a short dump as soon as the BAPI is executed .
    "   The current ABAP "SAPLMEPO" program had to be terminated because the
         ABAP processor detected an internal system error.
         When exporting the structure description, the structure
         components overlapped. The error occured in the
          description of the object "XEKPO".     "

    Hi
    You can change the approach to get the better pefromance.
    try as below:
    Loop at item table.
    Move all the related items of PO into another ITAB.
    Use AT END of  EBELN and call the BAPI pass EBELN and ITAB and use commit.
    The above will have better performance.
    if you wish continue the current appraoch then,
    Put some wait after iteration and also use comit based on the return of SY-SUBRC.
    Use WAIT UPTO 2 SECONDS. (please check correct stmt)
    Regards
    Shiva

  • Neep Urgent Help!!! About "SAPSQL_ARRAY_INSERT_DUPREC" short dump

    Hi All,
       I had modified program to create Potential Sale (ZT03) and Opportunity (ZOPS) by using BAPI_ACTIVITYCRM_CREATEMULTI and BAPI_OPPORTUNITY_CREATEMULTI respectively. During run time, I already created potential sale no. properly but when I had created opportunity by refer to potential sale, I got this SAPSQL_ARRAY_INSERT_DUPREC short dump and Can't create opportunity.
        Once that I had seperate creating potential and opportunity, It works well. But need to Log-off and Log-in again to create opportunity if short dump is occured.
       Can anyone help me to solve this issue? Thank you very much.
    Short dump error is show below
    000170   ***   records to insert
    000180     IF NOT it_records_to_insert IS INITIAL.
    >       INSERT crmd_orderadm_h FROM TABLE it_records_to_insert.
    000200       IF sy-subrc NE 0.
    000210         MESSAGE a002(crm_order_misc) WITH gc_object_name-orderadm_h.
    000220       ENDIF.
    000230       PERFORM trigger_events ON COMMIT.
    000240     ENDIF.
    000250

    GUI ID of opportunity is created by this BAPI function. I think it because of this BAPI function try to insert this GUI ID twist into Database (SAP NOTE NO. 620953). According to this SAP note, I already following those solution but still short dump occured.
      By the way, Thank for you help. Very appreciate.

Maybe you are looking for