Short dump - CX_SY_OPEN_SQL_DB during MODIFY statement

In production system, sometimes it dumps with this error:
Runtime Errors         DBIF_RSQL_INVALID_RSQL
Exception              CX_SY_OPEN_SQL_DB
And here is the code cause this problems:
CALL FUNCTION 'ENQUEUE_E_TABLE'
EXPORTING
mode_rstable = 'E'
tabname     = 'ZVKN_TRPHIST'.
MODIFY zvkn_trsphist FROM TABLE lt_trsphist. <<<<<< Error
CALL FUNCTION 'DEQUEUE_E_TABLE'
EXPORTING
mode_rstable = 'E'
tabname = 'ZVKN_TRPHIST'.
IF sy-subrc EQ 0.
return-type = 'S'.
ELSE.
ROLLBACK WORK.
return-type = 'E'.
ENDIF.
I have tried to use ENQUEUE statement with WAIT but no succeed. How to manage with no dump?

Hi, thanks for your reply.
Did you mean that adding COMMIT WORK AND WAIT when ENQUEUE is success and before modify statement?
I not get it clearly. I use the code below. Is this ok to transport to Production?
CALL FUNCTION 'ENQUEUE_E_TABLE'
    EXPORTING
      MODE_RSTABLE         = 'E'
      TABNAME              = 'ZVKN_TRPHIST'
*   VARKEY               =
*   X_TABNAME            = ' '
*   X_VARKEY             = ' '
*   _SCOPE               = '2'
      _WAIT                = 'X'
*   _COLLECT             = ' '
    EXCEPTIONS
      FOREIGN_LOCK         = 1
      SYSTEM_FAILURE       = 2
      OTHERS               = 3
   IF SY-SUBRC <> 0.
     return-type = 'E'.
     return-number = sy-msgno.
     return-id = sy-msgid.
     CALL FUNCTION 'MESSAGE_TEXT_BUILD'
       EXPORTING
         msgid               = sy-msgid
         msgnr               = sy-msgno
         msgv1               = sy-msgv1
         msgv2               = sy-msgv2
         msgv3               = sy-msgv3
         msgv4               = sy-msgv4
       IMPORTING
         message_text_output = return-message.
     ROLLBACK work.
     RETURN.
   ELSE.
     COMMIT WORK AND WAIT.
     MODIFY zvkn_trsphist FROM TABLE lt_trsphist.
     CALL FUNCTION 'DEQUEUE_E_TABLE'
       EXPORTING
         mode_rstable = 'E'
         tabname      = 'ZVKN_TRPHIST'.
     RETURN-type = 'S'.
   ENDIF.

Similar Messages

Short dump with a select statement

I have the following select statement (I have also inluded my data statement(s)) and I get a short dump. The error is as follows:
<b>What happened?
    Error in ABAP application program.
The current ABAP program "ZPARTNER" had to be terminated because one of the
    statements could not be executed.
This is probably due to an error in the ABAP program.
Following a SELECT statement, the data read could not be placed in AN
    the output area.
    A conversion may have been intended that is not supported by the
    system, or the output area may be too small.
Error analysis
    An exception occurred. This exception will be dealt with in more detail
    below. The exception, assigned to the class 'CX_SY_OPEN_SQL_DB', was not
     caught, which
     led to a runtime error. The reason for this exception is:
    The data read during a SELECT access could not be inserted into the
    target field.
    Either conversion is not supported for the target field's type or the
    target field is too short to accept the value or the data are not in a
    form that the target field can accept          </b>
it_adrc TYPE TABLE OF adrc,
      wa_adrc LIKE LINE OF it_adrc,
SELECT addrnumber name1 street city1 region post_code1 tel_number
FROM adrc INTO TABLE it_adrc
FOR ALL ENTRIES IN it_detail
WHERE addrnumber = it_detail-adrnr.
Regards,
Davis

If you only need the fields mentioned in the select query, then follow this:
TYPES: BEGIN OF ADRC_TYPE,
     ADDRNUMBER LIKE ADRC-ADDRNUMBER,
     NAME1        LIKE ADRC-NAME1,
     STREET        LIKE ADRC-STREET,
     CITY        LIKE ADRC-CITY,
     REGION        LIKE ADRC-REGION,
     POST_CODE1 LIKE ADRC-POST_CODE1,
     TEL_NUMBER LIKE ADRC-TEL_NUMBER,
       END OF ADRC_TYPE,
       ADRC_T_TYPE TYPE TABLE OF ADRC_TYPE.
DATA: IT_ADRC TYPE ADRC_T_TYPE WITH HEADER LINE.
IF NOT IT_DETAIL[] IS INITIAL.
SELECT addrnumber name1 street city1 region post_code1 tel_number
FROM adrc INTO TABLE it_adrc
FOR ALL ENTRIES IN it_detail
WHERE addrnumber = it_detail-adrnr.
ENDIF.
Thanks,
SKJ

Short dump (DBIF_RSQL_INVALID_RSQL) during activating ODS

Hello Experts,
I found short dump during activating ODS.
The error message in short dump:
Runtime Error: DBIF_RSQL_INVALID_RSQL
Except.: CX_SY_OPEN_SQL_DB
The termination occurred in the ABAP program "GP7WIVS2MDWGSTMN3ICFDKNAH65" in "ACTIVATE_SIDS".
The main program was "RSODSACT1 ".
I add one InfoObject in the ODS. After activating related objects, I loaded data into the data target.
Data seemed to be loaded correctly, but couldn't be activated.
Any suggestion on this?
-WJ-

Hi,
Please chekc the following SAP Notes you will find solution
Note 908599 - Runtime error SAPSQL_INVALID_FIELDNAME during activation
Note 612995 - P13:ODS:Data activation in bckgrnd always ends 'successfully
Note 1175860 - P19: DSO: SDL: Automatic update after activation
Note 1113603 - P17:DSO:Postprocessing ODS - activating and updating
Note 378447 - Correction: hierarchies do not become green
Note 1272738 - P21:DSO: Activation and automatic updating
Note 794584 - P26:Timestamp field empty in RS2NDPROCPROT after ODSACTIVATE
Note 800086 - P26: ODS activation: Status field in table RS2NDPROCPROT
Note 856292 - P28: Automatic functions: No lock obtained for ERSICENQ
Thanks
Reddy

Getting short dump "TSV_TNEW_PAGE_ALLOC_FAILED" during the load

Hi Experts,
I am getting short dump "TSV_TNEW_PAGE_ALLOC_FAILED" when loading data one ODS to Two cubes in 3.1 system . we have only 12000 records to load. this load is delta update. daily we loaded 14000 record from this load but today we are getting short dump.
Short Dump : TSV_TNEW_PAGE_ALLOC_FAILED
Description : No storage space available for extending the internal table.we attempted to extend an internal table, but the required space wasnot available.
Thanks

This is a memory issue whereby an internal table requires more memory than what is currently available. If you're executing this during processing of other ETL, then your memory is being consumed by all of the processes and you would need to change your schedule as to balance the load better.
Another possibility is that you have an extremely inefficient SQL statement in a routine that is causing the memory to be overly consumed. Even though the output may be less than average, there is a possiblity that it's reading more data in a SELECT statement and therefore requires more memory than normal.
Finally, have you Basis team look at this issue to determine if there's anything that they can do to resolve it.

Short Dump created while modifying a process chain

Hi guys ,
Iam getting a short dump while trying to modify a process chain and it is taking me too short dump where the message is PROCESS HAS NO PREDECESSOR but even when Iam trying to DETAILED VIEW it is taking me too short dump
Can anyone help me out of this issue

Hi ,
I have removed the existing start process and I have checked but there is no Use the same short dump is created again
Please suggest me some usefull solution .

Short dump Error during VM container communication between ABAP and JAVA.

Hello All,
Can anybody please help with resolving the following issue:
Short dump is displayed, when I try to insert CRM product (type: material) in the document (opportunity). This CRM product was created in CRM directly.
When I try to insert ECC migrated material, everything works fine.
Here is the details of dump:
Short text
    Error during VM container communication between ABAP and JAVA
Information on where terminated
    Termination occurred in the ABAP program "SAPLPRC_INT" - in "GET_PRICING_PROCEDURE_INFO".
    The main program was "SAPMHTTP ". In the source code you have the termination point in line 100 of the (Include) program "LPRC_INTF35".
Thank you!

hi Willie,
     this is the dump, and i have used the t-code sm52 . the VMC is not active.
|Short Text                                                                                        |
|    Error during VM Container communication between ABAP and JAVA.                                |
|What happened?                                                                                    |
|    The current program had to be terminated because of an                                        |
|    error when installing the R/3 System.                                                         |
|    Error in the RFC layer.                                                                       |
|What can you do?                                                                                  |
|    Note which actions and entries caused the error to occur.                                     |
|                                                                                                  |
|    Consult your SAP administrator.                                                               |
|                                                                                                  |
|    Using transaction ST22 for ABAP dump analysis, you can view, manage,                          |
|    and retain termination messages for longer periods.                                           |
|Error analysis                                                                                    |
|    An error has occurred in the RFC layer during communication between                           |
|    JAVA and the ABAP stack. This prevents data from being passed correctly                       |
|    between the two stacks.                                                                       |
|                                                                                                  |
|    Message    = TH_VMC_SERV_NOT_ACTIVE                                                           |
|    Return code = -1007                                                                           |
|    Pointer    = "000007DD348F6138"                                                               |
|How to correct the error                                                                          |
|    Check whether the VMC is active on your application server. To do this,                       |
|    run transaction SM52. If the VMC is not active, contact your SAP                              |
|    administrator.                                                                                |
Regards
Charles

Short Dump 'ASSERTION_FAILED' during updating partner Functions

Hi All,
I am updating the Partner Functions for the Customers using FM 'SD_CUSTOMER_MAINTAIN_ALL' and passing the partner functions and numbers to the XKNVP structure.
while running the program in am getting the short dump as ASSERTION_FAILED.
Detailed Description:
In the running application program, the ASSERT statement recognized a situation that should not have occurred.
The runtime error was triggered for one of these reasons:
- For the checkpoint group specified with the ASSERT statement, the activation mode is set to "abort".
- Via a system variant, the activation mode is globally set to "abort" for checkpoint groups in this system.
- The activation mode is set to "abort" on program level.
- The ASSERT statement is not assigned to any checkpoint group.
The Dump is occuring in the method 'get_cvic_cust_to_bp1_line'.
We have searched for a relevant SAP note but could not find any.
can any one please help to solve this issue?
Helpful answer will surely be rewarded.
Thanks in Advance,
Asif Ali Khan

When you are (absolutely) sure you are using this function module in the correct way, only then opening a message for SAP is liable. However, most of the times this happens because not all (or all) parameters are not provided for the FM to work properly, or what ever reason that may be.
It might be helpful to determine the checkpoint group and have a look at the log in transaction SAAB. This might give you a clue as to where the problems lies.

Short dump in quality

Dear All,
Hope all are doing fine ..Am struck with some issue.
Am getting short dump in Quality system because of excess time limit in the following select statement.
data: l_size type i value 1000.
SELECT vbeln
         posnr
         matnr
         werks
         ps_psp_pnr
         APPENDING TABLE it_vbap
         FROM vbap
         PACKAGE SIZE L_SIZE
         FOR ALL ENTRIES IN it_vbak
         WHERE vbeln EQ it_vbak-vbeln
         AND lsmeng EQ space
         AND matnr IN r_matnr
         AND werks IN r_werks.
   ENDSELECT.
Pls. suggest me alternatives to get out of this short dump in the select statement....
Thanks & Regards
Jack

Dear RichHeilman,
Thanks alot for your great response..
am pasting the code which will be more easier for you to rectify my dump.
In Quality it_vbak has 80,000 records ,, the moment it reaches to it_vbap it goes to dump for having excess time limit.
SELECT vbeln
         vkorg
         vtweg
         spart
         kunnr
         INTO TABLE it_vbak
         FROM vbak
         WHERE vkorg IN so_vkorg
         AND vtweg IN r_vtweg
         AND spart IN r_spart
         AND kunnr IN r_kunnr
         AND bukrs_vf EQ p_bukrs.
IF NOT it_vbak[] IS INITIAL.
    SELECT vbeln
           posnr
           matnr
           werks
           ps_psp_pnr
           APPENDING TABLE it_vbap
           FROM vbap
           PACKAGE SIZE L_SIZE
           FOR ALL ENTRIES IN it_vbak
           WHERE vbeln EQ it_vbak-vbeln
           AND lsmeng EQ space
           AND matnr IN r_matnr
           AND werks IN r_werks.
     ENDSELECT.
ENDIF.
Thanks in advance
Jack

Short dump in BP after upgrade to ECC 6.0

Hi,
We have upgraded system to ECC 6.0 from ECC 5.0
After upgrade system is giving short dump in transaction BP, event tried to navigate on BP screen.
Short dump description:
A RAISE statement in the program "CL_OS_TRANSACTION=============CP" raised the exception condition "OS_COMMIT_TOP_FAILED".
Since the exception was not intercepted by a superior program, processing was terminated.
Please advise to resolve this issue.
Regards,
Dipak

When exactly does this error appear? On save? clicking on a specific entry?
I suggest opening an OSS call for this problem, this doesn't seem to known (at least I didn't find any notes)
Markus

OBJECT_ID_NOT_FOUND short dump (BBP_CENTRALPERSON_GET with WF-BATCH?)

Hi there,
We are currently doing an upgrade from SRM 3.0 to SRM 5.0. We initially had one backend system configured and PO's are happily replicated across to it.
We have now added a SECOND backend and now we have the following strange error scenario:
The SC is created (with a user linked to the 2nd backend) but when trying to determine the BE Purchasing Org (function BBP_PDH_PO_DET_BE_PUR_ORGS) for the PO replication etc it gets a short dump saying:
A RAISE statement in the program "SAPLBBP_ATTR_PDORG" raised the exception
condition "OBJECT_ID_NOT_FOUND".
The actual error occurs in program SAPLBBP_ATTR_PDORG and form MAP_OBJECT
So the error is occuring because it tries to run function module BBP_CENTRALPERSON_GET with user the background user WF-BATCH (for some reason).
NOTE: I have examined the short dump and it is definetly occuring AFTER mapping the SC to the PO (MAP_SHOPPING_BASKET_PO
in program SAPLBBP_PD_SC)
Why on earth would the WF-BATCH user be used at this point? We have compared the backend systems in config and cannot see anything wrong from our understanding.
So this is the call that is causing the error:
CALL FUNCTION 'BBP_CENTRALPERSON_GET'
EXPORTING
    iv_username        = iv_user
IMPORTING
    ev_bu_partner_guid = lv_person_guid
EXCEPTIONS
    OTHERS             = 1.
And the value of variable "iv_user" at this point is "WF-BATCH".
Does anyone have any idea why this could be happening with the second R/3 backend?
Any help in this regard would be great appreciated.
Thanks
Lynton

Well I managed to get the problem to go away but de-activating the BBP_PGRP_FIND badi implementation.
And after further tests all seems to be fine anyway.
Lynton

Short dump during select statement

hi,
i have to display 1 alv list output using REUSE_ALV_HIERSEQ_LIST_DISPLAY function module...so i have populated the data using select statement
select EXIDV
    brgew meabm
           vegr1 erlkz vhilm erdat aenam
           ernam from vekp
                into corresponding fields of table gt_master
                up to gs_test-select_amount rows.
so the data is also getting populated to gt_master table before the function module...but after executing the function module..it is giving short dump...due to some standard program....any idea

hi,
my coding is
Report       : ZBCALV                                                 *
Author       :                                                       *
SAP-User     :                                                       *
Requester    :                                                       *
Date         :                                                       *
Specification:                                                       *
Description :                                                       *
Changes      :                                                       *
Change No    :                                                       *
Author       :                                                       *
SAP-User     :                                                       *
Date         :                                                       *
Reason / Desc:                                                       *
REPORT   ZBCALV.
**& Report BCALV_TEST_HIERSEQ_LIST_EVENTS                              *
*report bcalv_test_hierseq_list_events.
types: g_ty_t_exidv type standard table of vekp,
       g_ty_t_brgew type standard table of vekp,
       g_ty_t_vegr1 type standard table of vekp,
       g_ty_t_vekp    type standard table of vekp,
       g_ty_t_curr    type standard table of alv_cur,
      g_ty_s_vekp type alv_t_t2,
       g_ty_s_exidv type alv_tab,
       g_ty_s_brgew   type alv_tab,
       g_ty_s_vegr1 type alv_chck,
       g_ty_s_vekp    type vekp,
       g_ty_s_curr    type alv_cur.
constants:
*con_vekp type lvc_fname value 'ALV_T_T2',
           con_scarr   type lvc_fname value 'ALV_TAB',      "#EC *
           con_spfli   type lvc_fname value 'ALV_CHCK',     "#EC *
           con_vekp    type lvc_fname value 'VEKP',
           con_scurx   type lvc_fname value 'ALV_CUR'.      "#EC *
DATA                                                                 *
tables: sscrfields.   " for processing the FCODEs in Selektion screens
type-pools: slis, kkblo.
class lcl_events_d1001 definition deferred.
types: begin of g_ty_s_test,
         select_amount      type i,
         selected_recs_m    type i,
         selected_recs_s    type i,
         no_info_popup      type char1,
         info_popup_once    type char1,
         events             type lvc_fname occurs 0,
         events_exit        type slis_t_event_exit,
         events_info_popup type lvc_fname occurs 0,
         list_append        type char1,
         list_amount        type i,
         list_append_status type i,
         layo_expand_field type char1,
         layo_expand_all    type char1,
         vari_default       type char1,
         vari_save          type char1,
         bypassing_buffer   type char1,
         buffer_active      type char1,
       end   of g_ty_s_test,
       begin of g_ty_s_evt_exit.
include type slis_event_exit.
types:   text    type string,
       end   of g_ty_s_evt_exit,
       g_ty_t_evt_exit type standard table of g_ty_s_evt_exit.
constants: con_true     type char1 value 'X',
           con_ok   type sy-ucomm value 'OK',
           con_exit type sy-ucomm value 'EXIT',
           con_canc type sy-ucomm value 'CANC',
           con_back type sy-ucomm value 'BACK',
           con_event_01 type lvc_fname value 'PF_STATUS_SET',
           con_event_02 type lvc_fname value 'USER_COMMAND',
           con_event_03 type lvc_fname value 'CALLER_EXIT',
           con_event_04 type lvc_fname value 'LIST_MODIFY',
           con_event_05 type lvc_fname value 'BEFORE_LINE_OUTPUT',
           con_event_06 type lvc_fname value 'AFTER_LINE_OUTPUT',
           con_event_07 type lvc_fname value 'SUBTOTAL_TEXT',
           con_event_08 type lvc_fname value 'REPREP_MODIFY',
           con_event_09 type lvc_fname value 'TOP_OF_PAGE',
           con_event_10 type lvc_fname value 'END_OF_PAGE',
           con_event_11 type lvc_fname value 'TOP_OF_LIST',
           con_event_12 type lvc_fname value 'END_OF_LIST',
           con_event_13 type lvc_fname value 'TOP_OF_COVERPAGE',
           con_event_14 type lvc_fname value 'END_OF_COVERPAGE',
           con_event_15 type lvc_fname value 'TOP_OF_FOREIGN_PAGE',
           con_event_16 type lvc_fname value 'END_OF_FOREIGN_PAGE',
           con_event_17 type lvc_fname value 'GROUPLEVEL_CHANGE',
           con_event_18 type lvc_fname value 'ITEM_DATA_EXPAND'.
data: gs_test type g_ty_s_test.
data: g_okcode type sy-ucomm.
data: g_repid type sy-repid.
data: gt_evt_exit type g_ty_t_evt_exit.
data: gr_container_d1001   type ref to cl_gui_custom_container,
      gr_grid_d1001        type ref to cl_gui_alv_grid,
      gr_events_d1001      type ref to lcl_events_d1001.
data: g_start_listinfo type slis_lineinfo.
*addition for extra
DATA: fieldcatalog TYPE slis_t_fieldcat_alv with header line.
types : BEGIN OF gt_output ,
       EXIDV TYPE VEKP-EXIDV,
      VGBEL TYPE LIPS-VGBEL,
       BRGEW TYPE VEKP-BRGEW,
       VEGR1 TYPE VEKP-VEGR1,
       MEABM TYPE VEKP-MEABM,
       ERLKZ TYPE VEKP-ERLKZ,
      VSTAT TYPE NAST-VSTAT,
       VHILM TYPE VEKP-VHILM,
       ERDAT TYPE VEKP-ERDAT,
       AENAM TYPE VEKP-AENAM,
       VBELN TYPE VBELN_GEN,
       ERNAM TYPE VEKP-ERNAM,
        END OF gt_output.
data: ls_output type gt_output,
      lt_output type gt_output occurs 0 WITH HEADER LINE .
types : BEGIN OF gt_item_output ,
       EXIDV TYPE VEKP-EXIDV,
       BRGEW TYPE VEKP-BRGEW,
        vEGR1 TYPE VEKP-VEGR1,
       TARAG TYPE VEKP-TARAG,
       NTGEW TYPE VEKP-NTGEW,
       MEABM TYPE VEKP-MEABM,
       BREIT TYPE VEKP-BREIT,
       HOEHE TYPE VEKP-HOEHE,
      ANW_STATUS TYPE VEKP-ANW_STATUS,
       MATNR TYPE VEPO-MATNR,
       VEGR2 TYPE VEKP-VEGR2,
       VSTEL TYPE VEKP-VSTEL,
       WERKS TYPE VEKP-WERKS,
       END OF gt_item_output.
data: ls_ITEM_output type gt_ITEM_output,
       lt_ITEM_output type gt_ITEM_output occurs 0 with header line.
types:       begin of g_ty_s_master.
include type gt_output.
types:   box                  type char1,
        lights               type char1,
         checkbox             type char1,
         expand               type char1,
         help                 type i,
         end   of g_ty_s_master,
       g_ty_t_master type standard table of g_ty_s_master,
       begin of g_ty_s_slave.
include type gt_item_output.
types:   box                  type char1,
        lights               type char1,
         checkbox             type char1,
         expand               type char1,
         help                 type i,
         end   of g_ty_s_slave,
       g_ty_t_slave type standard table of g_ty_s_slave.
data: gt_master type g_ty_t_master with header line,
      gt_slave type g_ty_t_slave with header line,
      gs_master type g_ty_s_master.
      CLASS lcl_events_d1001 DEFINITION
class lcl_events_d1001 definition.
public section.
    methods:
    data_changed         for event data_changed
                         of cl_gui_alv_grid
                         importing er_data_changed
                                   e_onf4
                                   e_onf4_before
                                   e_onf4_after,
    data_changed_finished
                         for event data_changed_finished
                         of cl_gui_alv_grid.
endclass.                    "lcl_events_d1001 DEFINITION
      CLASS lcl_events_d1001 IMPLEMENTATION
class lcl_events_d1001 implementation.
method data_changed.
endmethod.                    "data_changed
method data_changed_finished.
endmethod.                    "data_changed_finished
endclass.                    "lcl_events_d1001 IMPLEMENTATION
SELECTION-SCREEN                                                     *
selection-screen begin of block gen with frame.
parameters:
p_amount type i default 30.
selection-screen end of block gen.
at selection-screen.
AT SELECTION-SCREEN                                                  *
case sscrfields-ucomm.
    when 'PB01'.
      call screen 1001 starting at 1 1 ending at 80 20.
endcase.
START-OF-SELECTION                                                   *
start-of-selection.
g_repid = sy-repid.
gs_test-select_amount = p_amount.
END-OF-SELECTION                                                     *
end-of-selection.
perform f01_call_list.
*&      Form f01_call_list
      text
form f01_call_list.
data: l_callback_program type sy-cprog,                   "#EC NEEDED
        ls_layo            type slis_layout_alv,
        lt_fcat            type slis_t_fieldcat_alv,
        ls_keyinfo         type slis_keyinfo_alv.
data: ls_master type g_ty_s_master,
        ls_slave type g_ty_s_slave.
l_callback_program = sy-repid.
perform f01_alv_get_outtab.
perform f01_alv_set_layout changing ls_layo.
perform f01_alv_set_fcat   changing lt_fcat.
perform f01_alv_set_keyinfo changing ls_keyinfo.
if gs_test-list_append_status ne 0.
    ls_layo-list_append = gs_test-list_append.
endif.
call function 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'
    exporting
      i_callback_program             = g_repid
      is_layout                      = ls_layo
      it_fieldcat                    = lt_fcat
      i_tabname_header               = 'GT_MASTER'
      i_tabname_item                 = 'GT_SLAVE'
      is_keyinfo                     = ls_keyinfo
    tables
      t_outtab_header                = gt_master
      t_outtab_item                  = gt_slave
    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.                    " f01_call_list
FORM f01_alv_set_fcat
form f01_alv_set_fcat changing ct_fcat type slis_t_fieldcat_alv.
data: lt_fcat_master type slis_t_fieldcat_alv,
        lt_fcat_slave type slis_t_fieldcat_alv.
clear ct_fcat[].
perform f01_alv_set_fcat_master changing lt_fcat_master.
perform f01_alv_set_fcat_slave changing lt_fcat_slave.
append lines of lt_fcat_master to ct_fcat.
append lines of lt_fcat_slave to ct_fcat.
endform.                               " F01_ALV_SET_FCAT
*&      Form f01_alv_set_fcat_master
      text
form f01_alv_set_fcat_master changing ct_fcat type slis_t_fieldcat_alv.
data: ls_fcat type slis_fieldcat_alv,
        l_char(3) type c.
get fieldcatalog
fieldcatalog-fieldname   = 'EXIDV'.           "Field name in itab
fieldcatalog-seltext_l = 'HU-NR'. "Column text
FIELDCATALOG-KEY         = 'X'.
FIELDCATALOG-TECH        = 'X'.
fieldcatalog-col_pos     = 1. "Column position
   fieldcatalog-ref_tabname     = 'VEKP'.
fieldcatalog-outputlen   = 05.                "Column width
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'VGBEL'.
fieldcatalog-seltext_L   = 'SALES ORDER'.
fieldcatalog-outputlen   = 15.
   fieldcatalog-ref_tabname     = 'LIPS'.
fieldcatalog-col_pos     = 2.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'BRGEW'.
fieldcatalog-seltext_l   = 'WEIGHT'.
FIELDCATALOG-KEY         = 'X'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 3.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'MEABM'.
fieldcatalog-seltext_l   = 'DIMENSION'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 4.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'VEGR1'.
fieldcatalog-seltext_l   = 'IPPC NR'.
fieldcatalog-outputlen   = 15.
FIELDCATALOG-KEY         = 'X'.
fieldcatalog-col_pos     = 5.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'ERLKZ'.
fieldcatalog-seltext_l   = 'STATUS'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 6.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'VSTAT'.
fieldcatalog-seltext_l   = 'PRINT STATUS'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 7.
   fieldcatalog-ref_tabname     = 'VSTAT'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'VHILM'.
fieldcatalog-seltext_l   = 'PACKING MATERIAL'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 8.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'ERDAT'.
fieldcatalog-seltext_l   = 'CREATED FROM'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 9.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'AENAM'.
fieldcatalog-seltext_l   = 'LAST CHANGE'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 10.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'VBELN'.
fieldcatalog-seltext_l   = 'DELIVERY'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 11.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'ERNAM'.
fieldcatalog-seltext_l   = 'CREATED BY'.
fieldcatalog-outputlen   = 12.
fieldcatalog-col_pos     = 8.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
ls_fcat-tabname = 'GT_MASTER'.
modify ct_fcat from ls_fcat transporting tabname
                 where tabname ne ls_fcat-tabname.
loop at ct_fcat into ls_fcat.
    if    ls_fcat-fieldname eq 'BRGEW'.
      or ls_fcat-fieldname eq ''.
*§1.Set status of columns PLANETYPE and SEATSOCC to editable.
      ls_fcat-edit = 'X'.
      modify ct_fcat from ls_fcat.
    endif.
endloop.
endform.                    " f01_alv_set_fcat_master
*&      Form f01_alv_set_fcat_slave
      text
form f01_alv_set_fcat_slave changing ct_fcat type slis_t_fieldcat_alv.
data: ls_fcat   type slis_fieldcat_alv,
        l_char(3) type c.
fieldcatalog-fieldname   = 'EXIDV'.           "Field name in itab
fieldcatalog-seltext_l = 'HU-NR'. "Column text
FIELDCATALOG-KEY         = 'X'.
   FIELDCATALOG-TECH        = 'X'.
fieldcatalog-col_pos     = 1. "Column position
   fieldcatalog-ref_tabname     = 'VEKP'.
fieldcatalog-outputlen   = 05.                "Column width
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'TARAG'.           "Field name in itab
fieldcatalog-seltext_l = 'HU-NR'. "Column text
fieldcatalog-col_pos     = 1. "Column position
   fieldcatalog-ref_tabname     = 'VEKP'.
fieldcatalog-outputlen   = 05.                "Column width
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'NTGEW'.
fieldcatalog-seltext_L   = 'WEIGHT HU'.
fieldcatalog-outputlen   = 15.
   fieldcatalog-ref_tabname     = 'VEKP'.
fieldcatalog-col_pos     = 2.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'BRGEW'.
fieldcatalog-seltext_l   = 'WEIGHT'.
FIELDCATALOG-KEY         = 'X'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 3.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'LAENG'.
fieldcatalog-seltext_l   = 'LENGTH'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 4.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'BREIT'.
fieldcatalog-seltext_l   = 'WIDTH'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 5.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'HOEHE'.
fieldcatalog-seltext_l   = 'HEIGHT'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 6.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'VEGR1'.
fieldcatalog-seltext_l   = 'HU GR1'.
FIELDCATALOG-KEY         = 'X'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 7.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'VEGR2'.
fieldcatalog-seltext_l   = 'HU GR2'.
FIELDCATALOG-KEY         = 'X'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 8.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'MATNR'.
fieldcatalog-seltext_l   = 'MAT NO'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 9.
   fieldcatalog-ref_tabname     = 'VEPO'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'VSTEL'.
fieldcatalog-seltext_l   = 'SHIPPING'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 10.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'WERKS'.
fieldcatalog-seltext_l   = 'PLANT'.
fieldcatalog-outputlen   = 15.
fieldcatalog-col_pos     = 11.
   fieldcatalog-ref_tabname     = 'VEKP'.
APPEND fieldcatalog TO ct_fcat.
CLEAR fieldcatalog.
ls_fcat-tabname = 'GT_SLAVE'.
modify ct_fcat from ls_fcat transporting tabname
                 where tabname ne ls_fcat-tabname.
endform.                    " f01_alv_set_fcat_slave
FORM f01_alv_set_layout
form f01_alv_set_layout changing cs_layout type slis_layout_alv.
*... Display options
cs_layout-colwidth_optimize      = con_true.
cs_layout-no_colhead             = space.
cs_layout-no_hotspot             = space.
cs_layout-zebra                  = space.
cs_layout-no_vline               = space.
cs_layout-cell_merge             = space.
cs_layout-no_min_linesize        = space.
cs_layout-min_linesize           = space.
cs_layout-max_linesize           = space.
cs_layout-window_titlebar        = space.
cs_layout-no_uline_hs            = space.
cs_layout-no_sumchoice           = space.
cs_layout-no_totalline           = space.
cs_layout-totals_before_items    = space.
cs_layout-totals_only            = space.
cs_layout-totals_text            = space.
cs_layout-no_subchoice           = space.
cs_layout-no_subtotals           = space.
cs_layout-subtotals_text         = space.
cs_layout-numc_sum               = space.
cs_layout-no_unit_splitting      = space.
*... Interaction
cs_layout-box_fieldname          = 'BOX'.
cs_layout-box_tabname            = space.
cs_layout-box_rollname           = space.
if gs_test-layo_expand_field eq con_true.
    cs_layout-expand_fieldname       = 'EXPAND'.
endif.
cs_layout-hotspot_fieldname      = space.
cs_layout-f2code                 = space.
cs_layout-key_hotspot            = space.
cs_layout-flexible_key           = space.
cs_layout-reprep                 = space.
cs_layout-group_buttons          = space.
cs_layout-no_keyfix              = space.
cs_layout-get_selinfos           = con_true.
cs_layout-group_change_edit      = con_true.
cs_layout-no_scrolling           = space.
cs_layout-expand_all             = gs_test-layo_expand_all.
*... Detailed screen
cs_layout-detail_popup           = space.
cs_layout-detail_initial_lines   = space.
cs_layout-detail_titlebar        = space.
*... PF-status
cs_layout-def_status             = space.
*... Display variants
cs_layout-header_text            = space.
cs_layout-item_text              = space.
cs_layout-default_item           = space.
*... colour
cs_layout-info_fieldname         = space.
cs_layout-coltab_fieldname       = space.
*... others
cs_layout-list_append            = space.
endform.                               " F01_ALV_SET_LAYOUT
*&      Form f01_alv_set_keyinfo
      text
form f01_alv_set_keyinfo changing cs_keyinfo type slis_keyinfo_alv.
cs_keyinfo-header01 = 'EXIDV'.
cs_keyinfo-item01   = 'EXIDV'.
cs_keyinfo-header02 = 'BRGEW'."'CARRID'.
cs_keyinfo-item02   = 'BRGEW'."."'CARRID'.
cs_keyinfo-header03 = 'VEGR1'."'CONNID'.
cs_keyinfo-item03   = 'VEGR1'."'CONNID'.
cs_keyinfo-header04 = space.
cs_keyinfo-item04   = 'VEGR2'."'FLDATE'.
cs_keyinfo-header05 = space.
cs_keyinfo-item05   = space.
endform.                    " f01_alv_set_keyinfo
FORM f01_alv_event_pf_status_set
form f01_alv_event_pf_status_set using rt_extab type slis_t_extab.
                                                            "#EC *
data: l_event type lvc_fname.                             "#EC NEEDED
if gs_test-info_popup_once eq con_true.
    read table gs_test-events_info_popup into l_event
               with key table_line = 'PF_STATUS_SET'.
    if sy-subrc ne 0.
      insert 'PF_STATUS_SET' into gs_test-events_info_popup index 1.
      message i000(0k) with text-t01.
    endif.
elseif gs_test-no_info_popup eq space.
    message i000(0k) with text-t01.
endif.
set pf-status 'STANDARD' excluding rt_extab.
set titlebar 'STANDARD'.
endform.                               " F01_ALV_EVENT_PF_STATUS_SET
*&      Form F01_ALV_EVENT_BEFORE_LINE_OUTP
      text
form f01_alv_event_before_line_outp
                      using rs_lineinfo type slis_lineinfo. "#EC *
data: l_event type lvc_fname.                             "#EC NEEDED
if gs_test-info_popup_once eq con_true.
    read table gs_test-events_info_popup into l_event
               with key table_line = 'BEFORE_LINE_OUTPUT'.
    if sy-subrc ne 0.
      insert 'BEFORE_LINE_OUTPUT' into gs_test-events_info_popup
                                  index 1.
      message i000(0k) with text-t05.
    endif.
elseif gs_test-no_info_popup eq space.
    message i000(0k) with text-t05.
endif.
format color off
         intensified off
         inverse off
         hotspot off
         input off.
if rs_lineinfo-tabname eq 'GT_MASTER'.
    if
   gs_master-exidv ne gt_master-exidv or
       gs_master-brgew ne gt_master-brgew.
      write: / text-t05.
      write: /
     gt_master-exidv,
               gt_master-brgew.
      gs_master = gt_master.
    endif.
    if gs_test-selected_recs_m eq rs_lineinfo-tabindex.
      clear gs_master.
    endif.
endif.
endform.                               " F01_ALV_EVENT_BEFORE_LINE_OUTP
*&      Form f01_alv_get_outtab
      text
form f01_alv_get_outtab .
field-symbols: .
   select
   exidv BRGEW VEGR1
    TARAG NTgew meabm BREIT HOEHE VEGR2 VSTEL weRKS
                       from
                      (con_vekp) into corresponding fields of table
                       lt_slave up to gs_test-select_amount rows
                       where
                      exidv eq <ls_master>-exidv and
                       brgew eq -vegr1.
append lines of lt_slave to gt_slave.
endloop.
sort gt_slave by exidv brgew vegr1.
endif.
describe table gt_master lines gs_test-selected_recs_m.
describe table gt_slave lines gs_test-selected_recs_s.
clear gt_master.
clear gt_slave.
endform.                    " f01_alv_get_outtab
*&      Module d1001_pbo OUTPUT
      text
module d1001_pbo output.
perform d1001_pbo.
endmodule.                 " d1001_pbo OUTPUT
*&      Module d1001_pai INPUT
      text
module d1001_pai input.
perform d1001_pai.
endmodule.                 " d1001_pai INPUT

Short dump in SAP R/3: SQL statement buffer overflow?

Hello,
I hope someone can help us with the following problem:
A short dump in SAP R/3 (DBIF_RSQL_INVALID_RSQL, CX_SY_OPEN_SQL_DB)
occurred during a delta load, which worked fine for several month.
The custom code crashes at a FETCH NEXT CURSOR statement.
I assume, it might be a SQL statement buffer overflow in SAP R/3?
The problem can be reproduced by RSA3, and is therefore not time-dependent.
The problem did not occur before or on the quality assurance system.
Cursor code:
      Read all entries since last transfer (delta mechanism)
        OPEN CURSOR WITH HOLD s_cursor FOR
          SELECT * FROM ekko
            WHERE ebeln IN t_selopt_ekko.
t_selopt_ekko has up to 60.000 data sets, which worked fine in the past.
It is very likely that the amount of data during the first crash did not exceed this.
SQL-Trace of RSA3 call:
It seems that 25150 data set can be processed via fetch before the short dump occurs
After that object SNAP is written:
"...DBIF_RSQL_INVALID_RSQL...dynpen00 + 0xab0 at dymain.c:1645 dw.sapP82_D82
Thdyn...Report für den Extraktoraufruf...I_T_FIELDS...Table IT_43[16x60]TH058FUNCTION=
RSA3_GET_DATA_SIMPLEDATA=S_S_IF_SIMPLE-T_FIELDSTH100...shmRefCount = 1...
...> 1st level extension part <...isUsed       = 1...isCtfyAble   = 1...> Shareable Table Header Data
<...tabi         = Not allo......S_CURSORL...SAPLRSA3...LRSA3U06...SAPLRSA3...
During dump creation the following occurs:
"...SAPLSPIAGENTCW...CX_DYNAMIC_CHECK=...CRSFH...BALMSGHNDL...
DBIF_RSQL_INVALID_RSQL...DBIF_RSQL_INVALID_RSQL...DB_ERR_RSQL_00013...
INCL_ABAP_ERROR...DBIF_INCL_INTERNAL_ERROR...INCL_INTERNAL_ERROR...
GENERAL_EXC_WITHOUT_RAISING...INCL_SEND_TO_ABAP...INCL_SEARCH_HINTS...
INCL_SEND_TO_SAP...GENERAL_EXC_WITHOUT_RAISING...GENERAL_ENVIRONMENT...
GENERAL_TRANSACTION...GENERAL_INFO...GENERAL_INFO_INTERNAL...
DBIF_INCL_INTERNAL_CALL_CODE..."
Basis says, that the Oracle data base works fine. The problem seems to be a SAP R/3 buffer.
Does anyone had a similar problem or knows where such a buffer might be or how it can be enlarged?
Best regards
Thomas
P.S.
Found a thread that contains part of the dump message "dynpen00 + 0xab0 at dymain.c:1645":
Thread: dump giving by std prg contains -> seems not to be helpful
Found a similar thread:
Thread: Short dump in RSA3 --Z Data Source -> table space or somting else?
Edited by: Thomas Köpp on Apr 1, 2009 11:39 AM

Hi Thomas,
      Its due to different field length.
Just check it out in code after FETCH NEXT CURSOR what internal table you have mention.
that internal table shoul deffined by taking refrence of ekko, because your code is
OPEN CURSOR WITH HOLD s_cursor FOR
SELECT * FROM ekko
WHERE ebeln IN t_selopt_ekko.
hope you got solution.
Regards,

Short dump in ECC 6.0 during delta load

Hi,
We are currently working in BI upgrade project
from BW 2.1c to BI 7.0
At the same time R/3 is being upgraded from 4.0B to ECC 6.0
During delta load we are getting short dump in R/3 system.
Below is the short dump detalis
The current ABAP prgm "SAPMSSY1" had to be terminated because it has come across a statement that unfortunately cannot be executed.
The following syntax error occured in program "/BI0/SAPLQI2LIS_11_VAITM" in include "/BI0/SAPLQI2LIS_11_VAITM" is not Unicode-compatible, according to its attributes.
If any help can be provided on this issue it would be great.
Regards,
Nikhil
Edited by: Nikhil Sakhardanday on Sep 11, 2008 1:58 PM

Hi,
did you made UCCHECK ?
/manfred

Short Dump during Business Content Installation

Hi Gurus,
       I'm working on SAP BI 7.0. I'm getting a Short Dump Error stating " Program error: ASSIGN with length 0 in program "SAPLSNR3". " while I'm try to install the Business Content.
      I'm getting this error when I'm trying to install Business Content with Grouping Option " Data flow Before ", but I didn't face any problem when I started off with the Grouping Option " Only Necessary Objects ".
     I tried analysing this problem by going to ST22 transaction & during my analysis I found that in the said program " SAPLSNR3 ", there's LSNR3F01 include in which line number 178 is having a ASSIGN statement, where its trying to assign a computed value to some data variable. Now i understand that there's some problem with the value getting computed in the ASSIGN statement.
     I also tried finding some SAP Notes for the same problem, but to my misery I couldn't find anything appropriate. Could anyone of you who had faced similar problem help me out.
     For further assistance in making your replies much easier here in I'm adding the information about BI 7.0 system components.
           SAP ABAP:               Level 12
           SAP BASIS:               Level 12
           SAP BW:                   Level 14
           Business Content:       Level 5
Waiting for a early solution from U guyz.........
Regards,
Syed Shujaath Ali.

Hi,
Apply SAP BW: Level 19 or 20
Business Content: 10
patches .

Native sql DBCO, CONNECT statement short dump

Hi ALL ,
I am facing the problem here. please help me out in this.
i am trying to connce to the external database MSS, i made all the entries in the DBCO t-code and writing the follwoing native sql statement.
EXEC SQL.
CONNECT TO 'AAJ' AS 'V'
ENDEXEC.
EXEC SQL.
SET CONNECTION 'V'
ENDEXEC.
The above statement is not giving any error when i activate it but when i execute it is giving me shortdump error .
I already maintan   entries in DBCON table or DBCO t-code
And also tel me once it is connect how can i access the data from MSS (Microsoft sql server)i mean what kind of statement.
helpfull answer will be rewarded.
Anees
9886358645
Message was edited by:
        anees jawad

Native SQL
Open SQL allows you to access database tables declared in the ABAP Dictionary regardless of the database platform that you R/3 System is using. Native SQL allows you to use database-specific SQL statements in an ABAP program. This means that you can use database tables that are not administered by the ABAP Dictionary, and therefore integrate data that is not part of the R/3 System.
As a rule, an ABAP program containing database-specific SQL statements will not run under different database systems. If your program will be used on more than one database platform, only use Open SQL statements.
Native SQL Statements in ABAP Programs
To use a Native SQL statement, you must precede it with the EXEC SQL statement, and follow it with the ENDEXEC statement as follows:
EXEC SQL [PERFORMING )
The parameters are separated by commas. You must also specify whether the parameter is for input (IN), output (OUT) or input and output (INOUT). For further information, refer to SAP Note 44977.
EXEC SQL
   EXECUTE PROCEDURE proc1 ( IN , OUT :y )
ENDEXEC.
Cursor Processing
Cursor processing in Native SQL is similar to that in Open SQL:
OPEN
ENDIF.
ENDDO.
EXEC SQL.
CLOSE c1
ENDEXEC.
This example opens a cursor, reads data line by line, and closes the cursor again. As in Open SQL, SY-SUBRC indicates whether a line could be read.
Data Types and Conversions
Using Native SQL, you can
Transfer values from ABAP fields to the database
Read data from the database and process it in ABAP programs.
Native SQL works without the administrative data about database tables stored in the ABAP Dictionary. Consequently, it cannot perform all of the consistency checks used in Open SQL. This places a larger degree of responsibility on application developers to work with ABAP fields of the correct type. You should always ensure that the ABAP data type and the type of the database column are identical.
If the database table is not defined in the ABAP Dictionary, you cannot refer directly to its data type. In this case, you should create a uniform type description in the ABAP Dictionary, which can then be used by all application programs.
If the table is defined in the ABAP Dictionary, you should remember that the sequence of fields in the ABAP Dictionary definition may not be the same as the actual sequence of fields in the database. Using the asterisk (*) in the SELECT clause to read all columns into a corresponding work area would lead to meaningless results. In the worst case, it would cause an error.
The Native SQL module of the database interface passes a description of the type, size, and memory location of the ABAP fields used to the database system. The relevant database system operations are usually used to access and convert the data. You can find details of these operations in the manuals for the programming interface of the relevant database system. In some cases, Native SQL also performs other compatibility checks.
The documentation from the various database manufacturers provides detailed lists of combinations of ABAP data types and database column types, both for storing ABAP field values in database tables (INSERT, UPDATE) and for reading database contents into ABAP fields (SELECT). You can also apply these descriptions for the input and output parameters of database procedures. Any combinations not listed there are undefined, and should not be used.
The following sections provide details of the data types and conversions for individual databases. Although they are database-specific, there are also some common features.
Recommended type combinations are underlined. Only for these combinations is behavior guaranteed from release to release. For any other combinations, you should assume that the description only applies to the specified release.
The results of conversions are listed in a results column:
"OK": The conversion can be performed without loss of data.
Operations that fail are indicated by their SQL error code. Errors of this kind always lead to program termination and an ABAP short dump.
In some cases, data is transferred without an SQL error occurring. However, the data is truncated, rounded, or otherwise unusable:
Right truncation.
"Left" or "right" applies to the normal way of writing a value. So, for example, if a number is truncated, its decimal places are affected.
: Left truncation
: Number is rounded up or down during conversion
: A number that was "too small" is rounded to 0 (underflow)
: The conversion result is undefined.
There are several possible results. The concrete result is either not known at all, or can only be described using a set of rules that is too complicated for practical use.
: The conversion returns the SQL value NULL.
: The conversion is performed without fields and unchecked.
The original data is converted, but without its format being checked. The result may therefore be a value invalid for the result type, which cannot be processed further. An example of this is a date field containing the value "99999999" or "abcdefgh" after conversion.
Combinations of ABAP data type and database column type can be divided into finer subcategories. Here, for example, using the transfer direction ABAP ® database (INSERT, UPDATE):
If the width of the ABAP field is greater than that of the database column, the ABAP field may contain values for which there is not enough space in the database column. This can produce other cases: The concrete data value in ABAP finds space in the database column, or not.
If the ABAP field is at most as long as the database column, there is always space for the ABAP value in the database column.
Some types, such as numeric columns, expect values in a particular format. This is particularly important in connection with character types, for example, when you want to write an ABAP character field (type C) into an integer column.
Native SQL for Oracle
Native SQL for Informix
Native SQL for DB2 Common Server
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3b8b358411d1829f0000e829fbfe/content.htm

Short dump - CX_SY_OPEN_SQL_DB during MODIFY statement

Similar Messages

Maybe you are looking for