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,

Similar Messages

Short Dump in SAP BW Sys while extracting data from R/3

HI All,
I am getting short dump problem in sap bw while extracting the data from r/3 to bw info cube.
the error message is like this,
Runtime Error          DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          11.05.2011 09:36:51
ShrtText
An SQL error occurred when accessing a table.
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
How to correct the error
Database error text........: "ORA-14400: inserted partition key does not map to
any partition"
Internal call code.........: "[RSQL/INSR//BIC/B0000115000 ]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"GPCX2UNC5JG556R7DPSFJUGJS1Z" or "GPCX2UNC5JG556R7DPSFJUGJS1Z"
|    "INSERT_ODS"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"INSERT_ODS"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "bwdev"
Network address.......... "10.10.100.36"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "8x AMD64 Level"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "BWDEV"
Database type............ "ORACLE"
Database name............ "BWD"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Aug 17 2008 20:56:58"
Created in............... "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version......... "OCI_10201_SHARE "
Patch level.............. "247"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
Memory usage.............
Roll..................... 16128
EM....................... 6265200
Heap..................... 0
Page..................... 0
MM Used.................. 5972296
MM Free.................. 289384
SAP Release.............. "640"
User and Transaction
Information on where terminated
The termination occurred in the ABAP program "GPCX2UNC5JG556R7DPSFJUGJS1Z" in
"INSERT_ODS".
The main program was "SAPMSSY1 ".
The termination occurred in line 41 of the source code of the (Include)
program "GPCX2UNC5JG556R7DPSFJUGJS1Z"
of the source code of program "GPCX2UNC5JG556R7DPSFJUGJS1Z" (when calling the
editor 410).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "INSERT_ODS" "(FORM)" but was not handled locally, not declared in
the
RAISING clause of the procedure.
The procedure is in the program "GPCX2UNC5JG556R7DPSFJUGJS1Z ". Its source code
starts in line 21
|    of the (Include) program "GPCX2UNC5JG556R7DPSFJUGJS1Z ".

Hi,
This error occurs if you want to insert an entry in the table that does not match the value range of any partition. In such a case, you must compare the value of the entry with the definitions of the partitions to determine the cause of the error.
please run the following test/repair in transaction RSRV ,
RSRV -> All Elementary Test -> PSA Tables -> Consistency Between PSA Partitions and SAP Administration Information
-> include the PSA table
    /BIC/B0000115000
Check OSS note 339896 which explains the repair procedure.
Regards,
Lokesh

Short dump in RSA3 --Z Data Source

Hi,
I created a Z data source based on view and i appended extract structure to insert ZZ fields.
When i execute the data source it is showing me short dump how shall i proceed
I checked the view conditions and it is extracting data and showing now error and i checked the enhancements i have written in CMOD and checked the program it is displaying No syntax errors
Please advise me on how to correct the errors....
If need further info of short dump please ask
Runtime Error          DBIF_RSQL_INVALID_RSQL
Exception              CX_SY_OPEN_SQL_DB
What happened?
Error in ABAP application program.
The current ABAP program "SAPLRSA3" had to be terminated because one of the
Statements could not be executed.
Error analysis
An exception occurred. This exception is dealt with in more detail belo.The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', waS neither                                                           caught nor passed along using a RAISING clause, in the procedure "RSA3_GEN_GET_DATA" "(FUNCTION)"
Since the caller of the procedure could not have expected this exceptio to occur, the running program was terminated.
The reason for the 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.
Information on where terminated
The termination occurred in the ABAP program "SAPLRSA3" in "RSA3_GEN_GET_DATA".
The main program was "RSFHGEN2 ".
The termination occurred in line 226 of the source code of the (Include)
program "LRSA3U03"
of the source code of program "LRSA3U03" (when calling the editor 2260).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "RSA3_GEN_GET_DATA" "(FUNCTION)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLRSA3 ". Its source code starts in line 5
of the (Include) program "LRSA3$03 ".
Program
002150
002160       CASE G_S_INTERFACE-UPDMODE.
002170         WHEN 'F' OR 'C' OR 'I'.
002180   * First data package -> OPEN CURSOR
002190           IF G_COUNTER_DATAPAKID = 0.
002200   * Open Cursor for dynamical SELECT
002210             OPEN CURSOR WITH HOLD G_CURSOR FOR
002220             SELECT * FROM (G_S_OLTPSOURCE-EXTRACTOR)
002230                    WHERE (L_T_DYNAMIC_SELECT).
002240           ENDIF.
002250   * Fetch first data package
>           FETCH NEXT CURSOR G_CURSOR
002270                        APPENDING CORRESPONDING FIELDS OF TABLE E_T_DATA
002280                        PACKAGE SIZE G_S_INTERFACE-MAXSIZE.
002290           IF SY-SUBRC <> 0.
002300             RAISE NO_MORE_DATA.
002310           ENDIF.
002320           G_COUNTER_DATAPAKID = G_COUNTER_DATAPAKID + 1.
002330         WHEN 'D'.
002340           PERFORM FETCH_GEN_DELTA IN PROGRAM (L_GEN_PROGID)
002350                           TABLES E_T_DATA
002360                                  L_T_DYNAMIC_SELECT
002370                                  G_T_FIELDS
002380                           USING G_S_INTERFACE-MAXSIZE
002390                           CHANGING L_FLG_NO_MORE_DATA.
002400           IF L_FLG_NO_MORE_DATA = 'X'.
002410             IF NOT L_T_BDCPS[] IS INITIAL.
002420               L_T_BDCPS-PROCESS = SBIWA_C_FLAG_ON.
002430               MODIFY L_T_BDCPS
002440                    TRANSPORTING PROCESS WHERE PROCESS = SBIWA_C_FLAG_OFF.

Hello,
This thread is answered. Was it the table space or something else?
We may have a similar issue as recently posted in thread:
"Short dump in SAP R/3: SQL statement buffer overflow?"
Best regards
Thomas

Short Dump:DBIF_RSQL_SQL_ERROR; Exception :CX_SY_OPEN_SQL_DB

Hi All,
I am getting the below short when i try to load the data into BI system. when I start the Info Package, it is immediately going to this short dump.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          15.12.2011 02:43:18
Short text
SQL error in the database when accessing a table.
Please find the short dump details below.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          15.12.2011 02:43:18
Short text
     SQL error in the database when accessing a table.
Missing RAISING Clause in Interface
     Program                                 SAPLBTCH
     Include                                 LBTCHFXX
     Row                                     1.525
     Module type                             (FORM)
     Module Name                             STORE_NEW_STEPLIST_IN_DB
Trigger Location of Exception
     Program                                 SAPLBTCH
     Include                                 LBTCHFXX
     Row                                     1.652
     Module type                             (FORM)
     Module Name                             STORE_NEW_STEPLIST_IN_DB
Source Code Extract
Line SourceCde
1622              ID 'DATA' FIELD jobinfo_egj.
1623
1624           rc = 1.
    EXIT.
ELSE.
    db_steplist-priparkey = tmp_key.
ENDIF.
ENDIF.
SEIF new_steplist-typ = btc_xcmd." Step executes external command
db_steplist-extcmd = new_steplist-program.
db_steplist-xpgparams = new_steplist-parameter.
db_steplist-xpgflag = 'X'.
SE. " Step führt ein externes Programm aus
db_steplist-xpgprog   = new_steplist-program.
db_steplist-xpgparams = new_steplist-parameter.
db_steplist-xpgflag   = 'X'.
DIF.
steplist-sdldate = newjob_head-sdldate.
steplist-sdltime = newjob_head-sdltime.
steplist-sdluname = newjob_head-sdluname.
PEND db_steplist.
ep_count = step_count + 1.
OOP.
liste in DB speichern
RT tbtcp FROM TABLE db_steplist ACCEPTING DUPLICATE KEYS."n952782
y-subrc NE 0.
dialog EQ btc_yes.
MESSAGE s120 WITH new_job_head-jobname.
ENDIF.
CONCATENATE new_job_head-jobname new_job_head-jobcount INTO
jobinfo_egj SEPARATED BY '/'.
CALL 'C_WRITE_SYSLOG_ENTRY' ID 'TYP' FIELD ' '
        ID 'KEY' FIELD tbtcp_insert_db_error
        ID 'DATA' FIELD jobinfo_egj.
rc = 1.
EXIT.
ENDIF.
rc = 0.
DFORM.                               " STORE_NEW_STEPLIST_IN_DB
I would like to know where exactly it is getting error. Please help me on this.
Regards,
Venkat.

Hi,
Check following
See the OSS Notes:
Note 1379839 - RuntimeError DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB
Note 917927 - Status of transactional requests
Note 863054 - Correction: Missing packages not in the tree
And also check the following things.
1.Connections from BW to ECC and ECC to BW in SM59
2.Check Port,Partner Profiles,and Message Types in WE20 in ECC & BW.
3.Check Dumps in ST22, and SM21.
4.If Idocs are stuck i.e see the OLTP Idoc numbers in RSMO Screen in (BW) detials tab see in bottom, you can see OLTP Idoc number and take the Idoc numbers and then goto to ECC see the status in WE05 or WE02, if error then check the log else goto to BD87 in ECC and give the Idoc numbers and execute manually and see in RSMO and refresh.
5.Check the LUWs struck in SM58,User Name = * (star) and run it and see Strucked LUWs and select our LUW and execute manually and see in RSMO in BW.
There are many threads also on this.
Go through them
Runtime Errors DBIF_RSQL_SQL_ERROR & Exception: CX_SY_OPEN_SQL_DB
Short Dump in SAP BW Sys while extracting data from R/3
Thanks and regards

Short dump in debug mode

Hi All,
We have recently upgraded our server from SAP R/3 4.6b to ECC 5.0. Whenever we are debugging any program(Both standard and Z-programs) getting short dump
in the select and endselect statements. This is happening only when we are going on DEBUG MODE only Appreciate any lights on this issue.(All programs are Unicode enabled).
Regards,
Ameer.

hi
your problem will solve if you put the break point after <b>ENDSELECT</b> statement. let the cursor not go inside the select-endselect statement. it causes short-dump.
thx
murthy

Short dump while inserting into PA0008

Hi Gurus,
I am trying to use a transfer tool to import employee details from one system to another.
All infotypes are being imported properly but the table PA0008 is not getting imported and
it gives short dump when the program reaches the statement :
"INSERT (AKT-TABLE) FROM W_PREL."
The dump is shown as "DBIF_RSQL_INVALID_REQUEST".The reason are not clear.
Any hints please ?
Waiting for responses,
Sandip.

Hi
How you are inserting data into PA0008?
You can use HR_INFOTYPE_CREATION fun module to insert data .
See the dump completely in ST22 tcode and analyse it
always better to use MODIFY statement instead of INSERT statement to insert the data into tables/infotypes.
do like that, and check the Dump.
Regards
Anji

I get short dump, please help~

Hi!
I get the short dump , for the code below.
Since I have exported to memory, why i get this short dump when i try to list it from the memory?
SUBMIT (prog) with SELECTION-TABLE (seltab)
                      EXPORTING LIST TO MEMORY
                      AND RETURN.
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
listobject = abaplist.
and the short dump is as follows
A RAISE statement in the program "SAPLSLST" raised the exception
condition "NOT_FOUND".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
No list found in memory
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.

Hi,
I have given a saple code for SUBMIT
SUBMIT RMCB0300 WITH SL_WERKS-LOW EQ SO_WERKS-LOW
                  WITH SL_MATNR      IN SO_MATNR
                  WITH VA            EQ 'X'
                  WITH SL_SPMON-LOW EQ W_BUDAT1
                  WITH SL_SPMON-HIGH EQ W_BUDAT1
                  WITH SL_MTART-LOW EQ 'ROH'
                  WITH SLV_NO        EQ 'STOCK'
                  EXPORTING LIST TO MEMORY AND RETURN.
CALL FUNCTION 'LIST_FROM_MEMORY'
    TABLES
      LISTOBJECT = LISTTAB
    EXCEPTIONS
      NOT_FOUND = 1
      OTHERS     = 2.
CALL FUNCTION 'LIST_TO_ASCI'
    TABLES
      LISTASCI           = I_LISTASCI
      LISTOBJECT         = LISTTAB
    EXCEPTIONS
      EMPTY_LIST         = 1
      LIST_INDEX_INVALID = 2
      OTHERS             = 3.
IF SY-SUBRC <> 0.
ENDIF.
Which im using currently .PLease reward points if solved
Thanks
Shankar S

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

BOBJ report failed in SAP 6.0.   "/CRYSTAL/OSQL_EXECUTE".*. short dump in S

We have a set of crystal reports that run correctly in SAP4.6C. During the upgarde, we are unable to run any report against the new sap 6.0 but the same report run correctly against SAP4.6C. Whenever we run the bobj report, a short dump is created in SAP ECC6.0 as follow:
Information on where terminated
    Termination occurred in the ABAP program "/CRYSTAL/OSQL_EXECUTE" - in
     "START-OF-SELECTION".
    The main program was "/CRYSTAL/OSQL_EXECUTE ".
    In the source code you have the termination point in line 48
    of the (Include) program "/CRYSTAL/OSQL_EXECUTE".
We are using BOBJ XI SP2. SAPGUI 6.2. SAP ECC6.0 SERVER. The following sets of transports from BOBJ integration kit SP4 have been imported into SAP.
Open SQL Connectivity transport
Row-level security definition transprot
cluster definition transport
Infoset Connectivity transport
Authenticaton helpers tranport
BOBJ support has been unable to help so far..

Roland, we tried using the IP address to connect and create report and the same short-dump still occurs. We also applied BOBJ SP4 and it still didn't help. Please let us know if you have other thoughts. Thank you.
Here is a snapshot of the sap short-dump.
Error analysis                                                                                |
Short text of error message:
Syntax error in code: Error line #: 1 Message: REPORT/PROGRAM statement
missing, or program type
Long text of error message:
Technical information about the message:
Message class....... "AD"
Number.............. 010
Variable 1.......... "Syntax error in code: Error line #:"
Variable 2.......... 1
Variable 3.......... "Message:"
Variable 4.......... "REPORT/PROGRAM statement missing, or program type"
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"/CRYSTAL/OSQL_EXECUTE" or "/CRYSTAL/OSQL_EXECUTE"
"START-OF-SELECTION"
|----
System environment
SAP-Release 700
Application server... "ldcnadtc301"
Network address...... "20.22.185.84"
Operating system..... "SunOS"
Release.............. "5.10"
Hardware type........ "sun4u"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "ldc-nadtc301-db.ldco"
Database type..... "ORACLE"
Database name..... "DEV"
Database user ID.. "SAPR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Feb 3 2008 21:08:24"
create on........ "SunOS 5.9 Generic_117171-13 sun4u"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "SunOS 5.9, SunOS 5.10"
User and Transaction
Client.............. 200
User................ "CRYSTAL"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "48BE892424F37464E10000001416B954"
Program............. "/CRYSTAL/OSQL_EXECUTE"
Screen.............. "SAPMSSY0 1000"
Screen Line......... 6
Information on caller of Remote Function Call (RFC):
System.............. "DEV"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and non-transactional (emode 0, imode 1)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Name.." "
Client.............. 200
User................ "CRYSTAL"
Transaction......... " "
Call Program........."/CRYSTAL/SAPLOPENSQL"
Function Module..... "/CRYSTAL/OSQL_EXECUTE_INTERNAL"
Call Destination.... "NONE"
Source Server....... "ldcnadtc301_DEV_00"
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Information on where terminated
Termination occurred in the ABAP program "/CRYSTAL/OSQL_EXECUTE" - in
"START-OF-SELECTION".
The main program was "/CRYSTAL/OSQL_EXECUTE ".
In the source code you have the termination point in line 48
of the (Include) program "/CRYSTAL/OSQL_EXECUTE".
Source Code Extract
Line
SourceCde
18
EXPORTING
19
PROGID                            = P_PROGID
20
GWHOST                            = P_GWHOST
21
GWSERV                            = P_GWSERV
22
IMPORTING
23
DESTINATION                       = DESTINATION
24
EXCEPTIONS
25
INVALID_PROGRAM_ID                = 1
26
CONNECT_TO_GATEWAY_FAILED         = 2
27
SERVER_NOT_REGISTERED             = 3
28
CONNECT_TO_REG_SERVER_FAILED      = 4
29
EXCLUSIV_NOT_SUPPORTED            = 5
30
OTHERS                            = 6
31
32
IF SY-SUBRC <> 0.
33
write   / 'Did not Connect to reg server'.
34
write : / 'SY-SUBRC', SY-SUBRC.
35
EXIT.
36
ENDIF.
37
38
IMPORT IMG_GETDATA_SOURCE[] FROM DATABASE INDX(ZA) ID P_JNAME.
39
DELETE FROM DATABASE INDX(ZA) ID P_JNAME.
40
41
GENERATE SUBROUTINE POOL IMG_GETDATA_SOURCE
42
NAME PROGNAME
43
MESSAGE SYNTAX_CHECK_MESSAGE
44
LINE ERROR_LINE_NO.
45
IF SY-SUBRC <> 0.
46
WRITE: / 'Syntax error, message', SYNTAX_CHECK_MESSAGE.
47
WRITE: / 'in line', ERROR_LINE_NO.
>>>>>
MESSAGE ID 'AD' TYPE 'X' NUMBER 010 WITH
49
'Syntax error in code: Error line #:'
50
ERROR_LINE_NO
51
'Message: '
52
SYNTAX_CHECK_MESSAGE.
53
ENDIF.
54
55
PERFORM GETDATA IN PROGRAM (PROGNAME)
56
using p_fname p_pksize p_progid p_gwhost p_gwserv destination.

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

SAP GUI for HTML - Short dump for Office intehration

Hi Experts.
I am using portal to view the transaction and it needs to open a document, while opening a document through it getting an error. when using
SAPGUI for HTML.
But it is working fine for GUI for Windows. ( selected this option in iView). It also works fine when use the transaction SAP itself.
Getting an below error from portal.
A RAISE statement in program "C_OI_CONTAINER_CONTROL_CREATORCP" has rais
exception condition "JAVABEANNOTSUPPORTED".
Since the exception was not caught by a program higher up in the call
hierarchy, processing was terminated.
Thanks
Rag

Anurag,
I have gone through notes.
I am using 7.2 version and access transaction through portal. while opening MS-office document, it is giving an error like JAVABEANNOTSUPPORT. and OFFICEINTREGRATION issue.
While opening it in SAP its working fine as well as using GUY for Windows also good.
But giving a short dump while accessing through portal with GUI for HTML option.
Any idea or work around for the same.
Thanks
Rag

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

SAP CRM middleware problem (sysfail ) The current application has triggered a termination with short dump

i'm having a proplem during starting initial load although i'm using the best practice documents C71 and B09 and all the configration was done by them .... could any one help ??

this is the first dump error for my RFCUSER on the ECC server
Category               ABAP Programming Error
Runtime Errors         MESSAGE_TYPE_X
ABAP Program           SAPLCRMC
Application Component CA
Date and Time          05.03.2014 17:50:47
Short Text
     The current application has triggered a termination with a short dump.
What happened?
     The current application program has detected a situation that should
     not occur. A termination with short dump has therefore been triggered
     by the key word MESSAGE (type X).
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
Error analysis
    Short text of the error message:
    See SAP Note 1498111
    Long text of the error message:
     Diagnosis
     System Response
     Procedure
         Refer to the SAP Note that was mentioned.
     Procedure for System Administration
    Technical information about the message:
    Message class....... C_
    Number.............. 330
    Variable 1.......... 1498111
    Variable 2..........
    Variable 3..........
    Variable 4.......... " "
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If the error occurs in a non-modfied SAP program, you might be able to
    find a solution in the SAP Notes system. If you have access to the SAP
    Notes system, check there first using the following keywords:
    "MESSAGE_TYPE_X"
    "SAPLCRMC" bzw. LCRMCF0C
    "CHECK_CRMATAB"
    If you cannot solve the problem yourself, please send the following
    information to SAP:
    1. This description of the problem (short dump)
    To do this, choose System -> List -> Save -> Local File (unconverted)
    on the screen you are in now.
    2. A suitable system log
    To do this, call the system log in transaction SM21. Restrict the time
    interval to ten minutes before the short dump and five minutes after
    it. In the display, choose System -> List -> Save -> Local File
    (unconverted).
3. If these are programs of your own, or modified SAP programs: Source
code of these programs
To do this, choose More Utilities -> Upload/Download -> Download in
the Editor.
4. Details regarding the conditions under which the error occurred or
which actions and input caused the error.
thanks

SQL Statement Dump

hi
We are getting the following sql statement dump, and i am not able to understand what should be done here, would anyone please advise
Registered qb: SEL$1 0xc4c8a150 (PARSER)
QUERY BLOCK SIGNATURE
signature (): qb_name=SEL$1 nbfros=1 flg=0
fro(0): flg=4 objn=272221 hint_alias="BSAD"@"SEL$1"
SPM: statement not found in SMB
SPM: statement not a candidate for auto-capture
Automatic degree of parallelism (ADOP)
Automatic degree of parallelism is disabled: Parameter.
PM: Considering predicate move-around in query block SEL$1 (#0)
Predicate Move-Around (PM)
PM: PM bypassed: disabled due to star transformation.
OPTIMIZER INFORMATION
----- Current SQL Statement for this session (sql_id=82mdu08rbcnyy) -----
EXPLAIN PLAN SET STATEMENT_ID='SAP_STMT' FOR /*+ 142235 */ SELECT "MANDT" , "BUKRS" , "KUNNR" , "UMSKS" , "UMSKZ" , "AUGDT" , "AUGBL" , "ZUONR"
, "GJAHR" , "BELNR" , "BUZEI" , "BUDAT" , "BLDAT" , "CPUDT" , "WAERS" , "XBLNR" , "BLART" , "MONAT" , "BSCHL" , "ZUMSK" , "SHKZG" , "GSBER" ,
"MWSKZ" , "DMBTR" , "WRBTR" , "MWSTS" , "WMWST" , "BDIFF" , "BDIF2" , "SGTXT" , "PROJN" , "AUFNR" , "ANLN1" , "ANLN2" , "SAKNR" , "HKONT" , "FK
ONT" , "FILKD" , "ZFBDT" , "ZTERM" , "ZBD1T" , "ZBD2T" , "ZBD3T" , "ZBD1P" , "ZBD2P" , "SKFBT" , "SKNTO" , "WSKTO" , "ZLSCH" , "ZLSPR" , "ZBFIX
" , "HBKID" , "BVTYP" , "REBZG" , "REBZJ" , "REBZZ" , "SAMNR" , "ANFBN" , "ANFBJ" , "ANFBU" , "ANFAE" , "MANSP" , "MSCHL" , "MADAT" , "MANST" ,
"MABER" , "XNETB" , "XANET" , "XCPDD" , "XINVE" , "XZAHL" , "MWSK1" , "DMBT1" , "WRBT1" , "MWSK2" , "DMBT2" , "WRBT2" , "MWSK3" , "DMBT3" , "W
RBT3" , "BSTAT" , "VBUND" , "VBELN" , "REBZT" , "INFAE" , "STCEG" , "EGBLD" , "EGLLD" , "RSTGR" , "XNOZA" , "VERTT" , "VERTN" , "VBEWA" , "WVER
W" , "PROJK" , "FIPOS" , "NPLNR" , "AUFPL" , "APLZL" , "XEGDR" , "DMBE2" , "DMBE3" , "DMB21" , "DMB22" , "DMB23" , "DMB31" , "DMB32" , "DMB33"
, "BDIF3" , "XRAGL" , "UZAWE" , "XSTOV" , "MWST2" , "MWST3" , "SKNT2" , "SKNT3" , "XREF1" , "XREF2" , "XARCH" , "PSWSL" , "PSWBT" , "LZBKZ" , "
LANDL" , "IMKEY" , "VBEL2" , "VPOS2" , "POSN2" , "ETEN2" , "FISTL" , "GEBER" , "DABRZ" , "XNEGP" , "KOSTL" , "RFZEI" , "KKBER" , "EMPFB" , "PRC
TR" , "XREF3" , "QSSKZ" , "ZINKZ" , "DTWS1" , "DTWS2" , "DTWS3" , "DTWS4" , "XPYPR" , "KIDNO" , "ABSBT" , "CCBTC" , "PYCUR" , "PYAMT" , "BUPLA"
, "SECCO" , "CESSION_KZ" , "PPDIFF" , "PPDIF2" , "PPDIF3" , "KBLNR" , "KBLPOS" , "GRANT_NBR" , "GMVKZ" , "SRTYPE" , "LOTKZ" , "FKBER" , "INTRE
NO" , "PPRCT" , "BUZID" , "AUGGJ" , "HKTID" , "BUDGET_PD" , "KONTT" , "KONTL" , "UEBGDAT" , "VNAME" , "EGRUP" , "BTYPE" , "PROPMANO" , "YYSTORE
" , "YYDELGRP" , "YYBOLNR" FROM "BSAD" WHERE "MANDT" = :A0 AND "KUNNR" IN ( :A1 , :A2 , :A3 , :A4 , :A5 ) AND "BUKRS" = :A6 AND "AUGDT" = :A7
user_id=27 user_name=SAPSR3 module=RSXPLORA action=7093
sql_id=82mdu08rbcnyy plan_hash_value=1162638466 problem_type=3
----- Current SQL Statement for this session (sql_id=82mdu08rbcnyy) -----
EXPLAIN PLAN SET STATEMENT_ID='SAP_STMT' FOR /*+ 142235 */ SELECT "MANDT" , "BUKRS" , "KUNNR" , "UMSKS" , "UMSKZ" , "AUGDT" , "AUGBL" , "ZUONR"
, "GJAHR" , "BELNR" , "BUZEI" , "BUDAT" , "BLDAT" , "CPUDT" , "WAERS" , "XBLNR" , "BLART" , "MONAT" , "BSCHL" , "ZUMSK" , "SHKZG" , "GSBER" ,
"MWSKZ" , "DMBTR" , "WRBTR" , "MWSTS" , "WMWST" , "BDIFF" , "BDIF2" , "SGTXT" , "PROJN" , "AUFNR" , "ANLN1" , "ANLN2" , "SAKNR" , "HKONT" , "FK
ONT" , "FILKD" , "ZFBDT" , "ZTERM" , "ZBD1T" , "ZBD2T" , "ZBD3T" , "ZBD1P" , "ZBD2P" , "SKFBT" , "SKNTO" , "WSKTO" , "ZLSCH" , "ZLSPR" , "ZBFIX
" , "HBKID" , "BVTYP" , "REBZG" , "REBZJ" , "REBZZ" , "SAMNR" , "ANFBN" , "ANFBJ" , "ANFBU" , "ANFAE" , "MANSP" , "MSCHL" , "MADAT" , "MANST" ,
"MABER" , "XNETB" , "XANET" , "XCPDD" , "XINVE" , "XZAHL" , "MWSK1" , "DMBT1" , "WRBT1" , "MWSK2" , "DMBT2" , "WRBT2" , "MWSK3" , "DMBT3" , "W
RBT3" , "BSTAT" , "VBUND" , "VBELN" , "REBZT" , "INFAE" , "STCEG" , "EGBLD" , "EGLLD" , "RSTGR" , "XNOZA" , "VERTT" , "VERTN" , "VBEWA" , "WVER
W" , "PROJK" , "FIPOS" , "NPLNR" , "AUFPL" , "APLZL" , "XEGDR" , "DMBE2" , "DMBE3" , "DMB21" , "DMB22" , "DMB23" , "DMB31" , "DMB32" , "DMB33"
, "BDIF3" , "XRAGL" , "UZAWE" , "XSTOV" , "MWST2" , "MWST3" , "SKNT2" , "SKNT3" , "XREF1" , "XREF2" , "XARCH" , "PSWSL" , "PSWBT" , "LZBKZ" , "
LANDL" , "IMKEY" , "VBEL2" , "VPOS2" , "POSN2" , "ETEN2" , "FISTL" , "GEBER" , "DABRZ" , "XNEGP" , "KOSTL" , "RFZEI" , "KKBER" , "EMPFB" , "PRC
TR" , "XREF3" , "QSSKZ" , "ZINKZ" , "DTWS1" , "DTWS2" , "DTWS3" , "DTWS4" , "XPYPR" , "KIDNO" , "ABSBT" , "CCBTC" , "PYCUR" , "PYAMT" , "BUPLA"
, "SECCO" , "CESSION_KZ" , "PPDIFF" , "PPDIF2" , "PPDIF3" , "KBLNR" , "KBLPOS" , "GRANT_NBR" , "GMVKZ" , "SRTYPE" , "LOTKZ" , "FKBER" , "INTRE
NO" , "PPRCT" , "BUZID" , "AUGGJ" , "HKTID" , "BUDGET_PD" , "KONTT" , "KONTL" , "UEBGDAT" , "VNAME" , "EGRUP" , "BTYPE" , "PROPMANO" , "YYSTORE
" , "YYDELGRP" , "YYBOLNR" FROM "BSAD" WHERE "MANDT" = :A0 AND "KUNNR" IN ( :A1 , :A2 , :A3 , :A4 , :A5 ) AND "BUKRS" = :A6 AND "AUGDT" = :A7
sql_text_length=2001
----- Explain Plan Dump -----
----- Plan Table -----
============
Plan Table
============
| Id | Operation | Name | Rows | Bytes | Cost | Time |
| 0 | SELECT STATEMENT | | | | 2 | |
| 1 | INLIST ITERATOR | | | | | |
| 2 | TABLE ACCESS BY INDEX ROWID | BSAD | 1 | 601 | 2 | 00:00:01 |
| 3 | INDEX RANGE SCAN | BSAD~1 | 1 | | 1 | 00:00:01 |
Predicate Information:
3 - access("MANDT"=:A0 AND (("KUNNR"=:A1 OR "KUNNR"=:A2 OR "KUNNR"=:A3 OR "KUNNR"=:A4 OR "KUNNR"=:A5)) AND "BUKRS"=:A6 AND "AUGDT"=:A7)
Content of other_xml column
===========================
db_version : 11.2.0.1
parse_schema : SAPSR3
plan_hash : 1162638466
plan_hash_2 : 3684135643
Outline Data:
/*+
BEGIN_OUTLINE_DATA
IGNORE_OPTIM_EMBEDDED_HINTS
OPTIMIZER_FEATURES_ENABLE('11.2.0.1')
DB_VERSION('11.2.0.1')
OPT_PARAM('query_rewrite_enabled' 'false')
OPT_PARAM('_optim_peek_user_binds' 'false')
OPT_PARAM('_optimizer_extended_cursor_sharing_rel' 'none')
OPT_PARAM('_optimizer_adaptive_cursor_sharing' 'false')
OPT_PARAM('_optimizer_use_feedback' 'false')
OPT_PARAM('star_transformation_enabled' 'true')
OPT_PARAM('optimizer_index_cost_adj' 20)
OPT_PARAM('_fix_control' '4728348:0 5483301:0 5705630:1 6626018:1 6440977:1 6972291:1 6399597:1 6430500:1 5099019:1 9196440:1 9495669:1 8
937971:1')
ALL_ROWS
OUTLINE_LEAF(@"SEL$1")
INDEX_RS_ASC(@"SEL$1" "BSAD"@"SEL$1" ("BSAD"."MANDT" "BSAD"."KUNNR" "BSAD"."BUKRS" "BSAD"."AUGDT" "BSAD"."AUGBL" "BSAD"."GJAHR" "BSAD"."B
ELNR" "BSAD"."BUZEI" "BSAD"."BUDAT"))
END_OUTLINE_DATA
Query Block Registry:
SEL$1 0xc4c8a150 (PARSER) [FINAL]
call(in-use=194136, alloc=229336), compile(in-use=233336, alloc=338904), execution(in-use=540368, alloc=544176)
End of Optimizer State Dump
Dumping Hints
=============
====================== END SQL Statement Dump ======================
thx
Jonu Joy

would anyone please advise It looks OK to me.

SAP BW 3.5 "Error in SQL Statement: DBIF_RSQL_INVALID_RSQL" in Infospoke

Hi ,
I am working on SAP BW 3.5.
while downloading the records through infospoke and giving them to the Application server side, I am getting an error "Error in SQL Statement: DBIF_RSQL_INVALID_RSQL".
Daily the Infospoke runs on delta mode. But for downloading of few records i have deactivated the delta and changed it in to Full mode. After downloading the data I again Activated the delta.but while Executing on Background mode I am getting an error mentioned above.
can anyone please suggest a solution for resolving this error?
Thanks in advance.
Santosh.

Hi:
Did you do some recent change in the objects?. I face sometimes this error and it is due to misalignment among the objects in a data flow (cubes, DSOs, transformations, DTPs, etc.).
What you can do is activate everything again.
Best regards.

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

Similar Messages

Maybe you are looking for