Errors in ABAP queries

Hi Experts,
Iam working in upgradation project( from 3.1i to ECC 6.0) there are some ABAP queries which are moved from 3.1i to ECC 6.0 the infoset contains the errors so iam unable to move it to quality server because of erros i have tried with ADJUST option but the result is same please any body suggest me how to tranport to quality it's very urgent.
Thank you

Hi,
check wheather u have make Unicode Active in all Generated Programs.
Regards,
Balakumar.G
Reward Points if helpful.

Similar Messages

How to check syntax errors in ABAP Queries

HI Guys,
How to check syntax errors in ABAP queries, Can please provide the T-Codes.
Advande thanks to everybody.
Thanks,
Gourisankar

Hi
with these you can check syntax errors and performance points
Hi
these all are doing t he same thing that is checking the program for better performance
Tools for Performance Analysis
Run time analysis transaction SE30
SQL Trace transaction ST05
Extended Program Check (SLIN)
Code Inspector ( SCI)
Run time analysis transaction SE30 :This transaction gives all the analysis of an ABAP program with respect to the database and the non-database processing.
SQL Trace transaction ST05: The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.
The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on a particular database table of the ABAP program would be mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.
The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.
To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.
Extended Program Check
This can be called in through transaction SE38 or through transaction SLIN. This indicates possible problems that may cause performance problems.
Code Inspector (SCI)
You can call the Code Inspector from the ABAP Editor (SE38), the Function Builder (SE37), the Class Builder (SE24), or as a separate transaction (SCI).
The Code Inspector indicates possible problems. However, note that, especially with performance issues: There is no rule without exception. If a program passes an inspection, it does not necessarily mean that this program will have no performance problems.
reward if usefull

ABAP Queries not available after upgarde from 4.6C to ECC 6.0

Hi All,
We have upgraded from 4.6C to ECC 6.0 version. There is some problem with the ABAP queries. The ABAP queries created in 4.6C were assigned to a Ztcode and now after the upgrade when we execute the Ztcode we are getting the error
that the program does not exist.
I tried to regenerate the code ( a new program name is generated) but there are differences in the selection screen (like the output format etc) between the two versions.
I looked into the relevant SAP notes also but could not find any solution.
Could any of you suggest any ideas to generate abap queries after upgrade?

hi,
Re: SAP version differences 4.5b, 4.6c and ECC6.0
http://help.sap.com/saphelp_47x200/helpdata/en/fc/e3003deddfae4de10000000a114084/frameset.htm
http://help.sap.com/saphelp_scm50/helpdata/en/28/b34c40cc538437e10000000a155106/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
Hope this helps.
venkat.

How to put Mandatory option for selection screen fields in ABAP Queries

Hi Experts
Can anyone tell me how to put mandatory option for the selection screen fields in ABAP Queries.
Manually I had written code in the At Selection Screen option in infoset to display error message if that field is blank.
But I need to display the selection fields with the tick mark (obligatory mark).
How to do this?
Appropriate answers will be awarded

Hi
For parameter option
parameters : p_kunnr type kna1-kunnr obligatory.
For select option
select-options: s_date for vbak-erdat obligatory.
Plz rewards points ,
Regards ,
Ganesh.

Re: join cluster table into transperant table in ABAP Queries

Hi gurus
How to join cluster tables into transperant tables in ABAP Queries,
I want to join KNA1, KNB2, BSEG(cluster table)
pls explain me
amk

Hi
You can use join for KNA1 and KNB1 which will much faster
then use for all entries of this itab to get the BSEG to improve the performance
here you need to do some trial and error method by joining removing the tables and also for all entries
regards
Shiva

Error while transporting Queries

Hi,
I am getting this error while transporting queries!!
Object '!ZTIC_UKA' (ELEM) of type 'Query' is not available in version 'A'
Message no. RSO252
Diagnosis
You wanted to generate an object with the name '!ZTIC_UKA' (in transport request ELEM) of type 'Query' (TLOGO). This is, however, not available in the BW Repository database. It does not exist in the requested version A. If the version is 'D' then it is possible that an error arose during the delivery or installation. If the version is 'A' then the Object was either not created or not activated.
System Response
The object was not taken into account in the next stage of processing
Thanks

Hi Murali,
YOu are trying to transport the element ZTIC_UKA' of the query,may be an variable which is not colelcted in the request.
Try to transport the query through RSA1> Transport connection->Query-->give you query name -->Drag and Drop to Right hand side and Click on collect all dependent objects and check whetehr they have collected in the same request.Make sure ur variables are collected.
Tranport it now and Check.
Rgds
SVU123
Edited by: svu123 on Mar 4, 2010 7:41 AM

Runtime error in abap report

error analysis as in ST22 TRANSACTION:
AN EXCEPTION OCCURED THE EXCEPTION ASSIGNED TO CLASS CX_SY_CONVERSION_NO_NUMBER WAS NOT CAUGHT WHICH LED TO AN ERROR. THE REASON FOR THIS EXCEPTION IS :
THE PROGRAM TRIED TO INTERPRET VALUE ':4' AS NUMBER SINCE THE VALUE CONTRAVENES THE CORRECT NUMBER FORMAT THIS WAS NOT POSSIBLE.
ATTACHED IS MY PROGRAM
REPORT ZVXR0303
      LINE-COUNT 60(3)
      LINE-SIZE 132
       MESSAGE-ID VN.
Tables: VBEP, VBAP, NAST.
DATA: BEGIN OF HEADER,
      ORDER(15) VALUE 'ORDER',
       LINE(5) VALUE 'LINE',
MATERIAL(14) VALUE 'MATERIAL',
       DUE(15) VALUE 'DUE (MAD)',
   CREATED(10) VALUE 'CREATED',
       QTY(10) VALUE 'QUANTITY',
        KEY(5) VALUE 'KEY',
       TYPE(5) VALUE 'TYPE',
       END OF HEADER.
DATA: Begin of IDAT OCCURS 0,
VBELN         LIKE VBAP-VBELN,
POSNR         LIKE VBAP-POSNR,
werks         LIKE VBAP-WERKS,
cuobj         LIKE vbap-CUOBJ,
MBDAT         LIKE vbep-mbdat,
ERDAT         LIKE VBAP-ERDAT,
MATNR         LIKE VBAP-MATNR,
KWMENG        LIKE VBAP-KWMENG,
QTY           TYPE I,
END of IDAT.
class cl_abap_char_utilities definition load.
constants: tab type c value cl_abap_char_utilities=>HORIZONTAL_TAB.
DATA: t_record(1000) TYPE C.
DATA: C_KWMENG(20)   TYPE C.
data: OUTFILE(50) value '/usr/users/ftpsapfi/locks_540318'.
DATA: BEGIN OF TKOMCON OCCURS 50.
        INCLUDE STRUCTURE CONF_OUT.
DATA: END   OF TKOMCON.
DATA: iKEY         TYPE I,
      offset       TYPE I,
      KeyTypeLOC   TYPE I,
      KeyNumberLOC TYPE I,
      type(15)     TYPE C.
    select-options: sVBELN FOR VBEP-VBELN obligatory,
                    sMAD FOR VBEP-MBDAT obligatory,
                    sERDAT FOR VBAP-ERDAT,
                    sMATNR FOR VBAP-MATNR,
                    sWERKS FOR VBAP-WERKS,
                    sKWMENG FOR VBAP-KWMENG.
SELECT
vbap~vbeln
vbap~POSNR
vbap~werks
vbap~cuobj
VBEP~MBDAT
VBAP~ERDAT
VBAP~MATNR
VBAP~KWMENG
INTO CORRESPONDING FIELDS of IDAT
FROM ( VBEP INNER JOIN VBAP ON vbepvbeln = vbapvbeln
AND vbepposnr = vbapposnr )
WHERE BMENG > 0
AND vbep~MBDAT IN sMAD
AND VBEP~VBELN in sVBELN
AND VBAP~werks IN sWERKS
AND VBAP~ERDAT IN sERDAT
AND VBAP~MATNR IN sMATNR
AND VBAP~KWMENG IN sKWMENG
AND VBAP~ABGRU = SPACE.
APPEND IDAT.
ENDSELECT.
PERFORM TOP-OF-PAGE.
if sy-batch = 'x'.
OPEN DATASET OUTFILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
TRANSFER t_record TO OUTFILE.
endif.
IF SY-SUBRC = 0.
LOOP at IDAT.
   write IDAT-KWMENG DECIMALS 0 TO C_KWMENG.
    REFRESH TKOMCON.
    CALL FUNCTION 'VC_I_GET_CONFIGURATION'
         EXPORTING
              INSTANCE      = idat-cuobj
              LANGUAGE      = NAST-SPRAS
         TABLES
              CONFIGURATION = TKOMCON
         EXCEPTIONS
              OTHERS        = 4.
    LOOP AT TKOMCON
      WHERE ATNAM = 'S_SK_SPEC_KEY' OR ATNAM = 'S_MK_SPEC_KEY'
      OR ATNAM = 'S_SK_CONSC_KEY' OR ATNAM = 'S_MK_CONSC_KEY'.
      IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
      OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
        KeyTYPELOC = 0.
        keynumberloc = 2.
        TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
        IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
          iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
          IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
          OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
            PERFORM OUT-OF-RANGE-FOUND.
          ENDIF.
        ENDIF.
      Else.
        Offset = 0.
        DO.
          IF offset <= 9.
            offset = offset + 1.
            If TKOMCON-ATWRT+Offset(1) = ':'.
              KeyTypeLOC = Offset + 1.
              KeyNumberLOC = Offset + 3.
              EXIT.
            ENDIF.
          ELSE.
            EXIT.
          ENDIF.
        ENDDO.
        TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
        IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
          iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
          IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
          OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
            IDAT-KWMENG = TKOMCON-ATWRT(3).
            PERFORM OUT-OF-RANGE-FOUND.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDLOOP.
ENDLOOP.
ENDIF.
CLOSE DATASET OUTFILE.
      FORM OUT-OF-RANGE-FOUND                                       *
FORM OUT-OF-RANGE-FOUND.
WRITE: / IDAT-VBELN.
WRITE: 10 IDAT-POSNR.
WRITE: 20 IDAT-MATNR.
WRITE: 35 IDAT-MBDAT.
WRITE: 50 IDAT-ERDAT.
WRITE: 65(3) IDAT-KWMENG DECIMALS 0.
WRITE: 75 TKOMCON-ATWRT+KeyTypeLOC(6).
IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
     OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
    WRITE: 85 'Consecutive'.
ELSE.
    WRITE: 85 'Specific'.
ENDIF.
IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
     OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
    TYPE = 'Consecutive'.
ELSE.
    TYPE = 'Specific'.
ENDIF.
* PREPARING A RECORD TO BE SENT TO FILE
CONCATENATE
IDAT-VBELN
IDAT-POSNR
IDAT-MATNR
IDAT-MBDAT
IDAT-ERDAT
C_KWMENG
TKOMCON-ATWRT+KeyTypeLOC(6)
TYPE
INTO t_record SEPARATED BY tab.
if sy-batch = 'x'.
TRANSFER t_record TO OUTFILE.
endif.
ENDFORM.
      FORM TOP-OF-PAGE                                              *
FORM TOP-OF-PAGE.
WRITE: / 'ORDER'.
WRITE: 10 'LINE'.
WRITE: 20 'MATERIAL'.
WRITE: 35 'DUE (MAD)'.
WRITE: 50 'CREATED'.
WRITE: 65 'QTY'.
WRITE: 75 'KEY'.
WRITE: 85 'TYPE'.
PREPARING A RECORD TO BE SENT TO FILE
CONCATENATE
header-ORDER
header-LINE
header-MATERIAL
header-DUE
header-CREATED
header-QTY
header-KEY
header-TYPE
INTO t_record SEPARATED BY tab.
ENDFORM.
THIS IS WORKING FINE WITH DIFFERENT RANGES BUT WHEN I USE RANGE
Sales Order 1250000 TO 2250000
MAD 01/18/2005 TO 03/02/2005
Material LOCK9250FR TO LOCK9250XF
PLANT 4500
IT GIVES THE RUNTIME ERROR I MENTIONED ABOVE
ANY HELP WOULD BE GREATLY APPRECIATED
THANKS.

HI ROB YOUR REPLY LOOKS TO BE VERY CLOSE OTHER GUYS SAID IT MIGHT BE PROBLEM WITH VARIABLE C_KWMENG BUT I REMOVED THAT PIECE OF CODE WITH C_KWMENG BUT STILL I WAS GETTING THE ERROR ATTACHED IS THE COMPLETE ERROR DETAILS FROM ST22
Runtime Errors         CONVT_NO_NUMBER
Exception              CX_SY_CONVERSION_NO_NUMBER
       Occurred on     09/29/2005 at 14:33:21
Unable to interpret "04:" as a number.
What happened?
Error in ABAP application program.
The current ABAP program "ZVXR0303" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception will be dealt with in more detail
below. The exception, assigned to the class 'CX_SY_CONVERSION_NO_NUMBER', was
not caught, which
led to a runtime error. The reason for this exception is:
The program attempted to interpret the value "04:" as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
How to correct the error
Integers are represented in ABAP using a sequence of digits and, in some
cases, a preceding sign.
The system offers the following options for displaying floating point
numbers:
[mantissa]E[sign][exponent]
[whole number part].[fractional part]
e.g. -12E+34, +12E-34, 12E34, 12.34
If the error occurred in one of your own programs or in an SAP program
that you modified, try to correct it yourself.
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:
"CONVT_NO_NUMBER" CX_SY_CONVERSION_NO_NUMBERC
"ZVXR0303" or "ZVXR0303"
"START-OF-SELECTION"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
                                                                                2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "grrsap54"
Network address.......... "10.80.96.102"
Operating system......... "HP-UX"
Release.................. "B.11.11"
Hardware type............ "9000/800"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 3
Short dump setting....... "full"
Database server.......... "grrsap54"
Database type............ "ORACLE"
Database name............ "D01"
Database owner........... "SAPR3"
Character set............ "en_US.iso88591"
SAP kernel............... "640"
Created on............... "Aug 28 2005 20:25:49"
Created in............... "HP-UX B.11.00 A 9000/800"
Database version......... "OCI_920 "
Patch level.............. "88"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
10.1.0.."
SAP database version..... "640"
Operating system......... "HP-UX B.11"
User, transaction...
Client.............. 050
User................ "NSHAKER"
Language key........ "E"
Transaction......... "SE38 "
Program............. "ZVXR0303"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "ZVXR0303" in
"START-OF-SELECTION".
The main program was "ZVXR0303 ".
The termination occurred in line 156 of the source code of the (Include)
program "ZVXR0303"
of the source code of program "ZVXR0303" (when calling the editor 1560).
Source code extract
Caution: Program has changed
Caution: At time of termination, Active source code no longer available
001260 ?         TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
001270 ?         IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
001280 ?           iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
001290 ?
001300 ?           IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
001310 ?           OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
001320 ?             PERFORM OUT-OF-RANGE-FOUND.
001330 ?           ENDIF.
001340 ?         ENDIF.
001350 ?       Else.
001360 ?         Offset = 0.
001370 ?         DO.
001380 ?           IF offset <= 9.
001390 ?             offset = offset + 1.
001400 ?             If TKOMCON-ATWRT+Offset(1) = ':'.
001410 ?               KeyTypeLOC = Offset + 1.
001420 ?               KeyNumberLOC = Offset + 3.
001430 ?               EXIT.
001440 ?             ENDIF.
001450 ?           ELSE.
001460 ?             EXIT.
001470 ?           ENDIF.
001480 ?         ENDDO.
001490 ?
001500 ?         TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
001510 ?
001520 ?         IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
001530 ?           iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
001540 ?           IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
001550 ?           OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
?             IDAT-KWMENG = TKOMCON-ATWRT(3).
001570 ?             PERFORM OUT-OF-RANGE-FOUND.
001580 ?           ENDIF.
001590 ?         ENDIF.
001600 ?       ENDIF.
001610 ?     ENDLOOP.
001620 ?   ENDLOOP.
001630 ? ENDIF.
001640 ? CLOSE DATASET OUTFILE.
001650 ?
001660 ? *----
001670 ? *       FORM OUT-OF-RANGE-FOUND                                       *
001680 ? *----
001690 ? *       ........                                                      *
001700 ? *----
001710 ? FORM OUT-OF-RANGE-FOUND.
001720 ?
001730 ?   WRITE: / IDAT-VBELN.
001740 ?   WRITE: 10 IDAT-POSNR.
001750 ?   WRITE: 20 IDAT-MATNR.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0                             SY-INDEX 44
SY-TABIX 7                             SY-DBCNT 1
SY-FDPOS 4                             SY-LSIND 0
SY-PAGNO 2                             SY-LINNO 18
SY-COLNO 94                            SY-PFKEY
SY-UCOMM                               SY-TITLE Out of Range Keys
SY-MSGTY I                             SY-MSGID SF
SY-MSGNO 616                           SY-MSGV1
SY-MSGV2                               SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
       Program
       Include                                  Line
       Class
     1 EVENT        START-OF-SELECTION
       ZVXR0303
       ZVXR0303                                   156
Chosen variables
     1 EVENT        START-OF-SELECTION
       ZVXR0303
       ZVXR0303                                   156
%_SPACE
2
                               0
SY-REPID                       ZVXR0303
                               5555333322222222222222222222222222222222
                               A682030300000000000000000000000000000000
TKOMCON-ATWRT                  04:XF1260
                               333543333222222222222222222222
                               04A861260000000000000000000000
KEYNUMBERLOC                   5
                               0000
                               0005
SYST-REPID                     ZVXR0303
                               5555333322222222222222222222222222222222
                               A682030300000000000000000000000000000000
SY-LDBPG                       SAPDB__S
                               5454455522222222222222222222222222222222
                               31042FF300000000000000000000000000000000
IKEY                           1260
                               000E
                               004C
KEYTYPELOC                     3
                               0000
                               0003
SY                             ###,####################################
                               0002000000000001000000000000000000000000
                               000C00020007000E00000001000A000000000000
... + 40                      ###########^###<########################
                               0000000000050003000100080000000000000009
                               00010004000E000C000200040000000000000000
... + 80                      ########################################
                               0000000000000000000000000000000000000000
                               0000000000000000000A00000000000000000000
... + 120                      #######################################_
                               0000000000000000000000000000000000010005
                               00000000000000000000000000000000000A000F
... + 160                      ############ÿÿ¹°XC#############   E2 X1
                               000000000000FFBB540000000000000222432253
                               0000000A0000FF90830040000C0000C000520081
... + 200                      000         ####__S                 050
                               3332222222220000555222222222222222223332
                               0000000000000000FF3000000000000000000500
... + 240                           00
                               222223322222222
                               000000000000000
SVBELN                         IBT00012500000002250000
                               44533333333333333333333
                               92400012500000002250000
IDAT-KWMENG                    ########
                               00000000
                               0000000C
TKOMCON-ATWRT+0(3)             04:
                               333
                               04A
SYST                           ###,####################################
                               0002000000000001000000000000000000000000
                               000C00020007000E00000001000A000000000000
... + 40                      ###########^###<########################
                               0000000000050003000100080000000000000009
                               00010004000E000C000200040000000000000000
... + 80                      ########################################
                               0000000000000000000000000000000000000000
                               0000000000000000000A00000000000000000000
... + 120                      #######################################_
                               0000000000000000000000000000000000010005
                               00000000000000000000000000000000000A000F
... + 160                      ############ÿÿ¹°XC#############   E2 X1
                               000000000000FFBB540000000000000222432253
                               0000000A0000FF90830040000C0000C000520081
... + 200                      000         ####__S                 050
                               3332222222220000555222222222222222223332
                               0000000000000000FF3000000000000000000500
... + 240                           00
                               222223322222222
                               000000000000000
OUTFILE                        /usr/users/ftpsapfi/locks_540318
                               2777277677267776766266667533333322222222
                               F532F53523F64031069FCF3B3F54031800000000
... + 40
2222222222
                               0000000000
Application Calls
No dump information available
Application Information
No dump information available
Internal notes
The termination occurred in the function "ab_Move" of the SAP
Basis System, specifically in line 529 of the module
"//bas/640_REL/src/krn/runt/abmove1.c#6".
The internal operation just processed is "MOVE".
The internal session was started at 20050929142552.
Active calls in SAP kernel
( 0) 0x4000000001751924   CTrcStack2 + 0x2bc dw.sapD01_DVEBMGS00
( 1) 0x4000000001751658   CTrcStack + 0x18 dw.sapD01_DVEBMGS00
( 2) 0x4000000001db7478   rabax_CStackSave__Fv + 0x100 dw.sapD01_DVEBMGS00
( 3) 0x4000000001dc3abc   ab_rabax + 0x1e1c dw.sapD01_DVEBMGS00
( 4) 0x4000000001b44cb4   ab_cnverr__FiPcPCvN21T2 + 0x18c dw.sapD01_DVEBMGS00
( 5) 0x40000000016c96f8   ab_Move + 0x1910 dw.sapD01_DVEBMGS00
( 6) 0x40000000016d4434   ab_jmove__Fv + 0x384 dw.sapD01_DVEBMGS00
( 7) 0x4000000001022348   ab_extri__Fv + 0x17a0 dw.sapD01_DVEBMGS00
( 8) 0x4000000001726dc8   ab_xevent__FPCc + 0x38 dw.sapD01_DVEBMGS00
( 9) 0x40000000019f7efc   ab_trigg__Fv + 0x94 dw.sapD01_DVEBMGS00
(10) 0x40000000019dc9ec   ab_run + 0xc4 dw.sapD01_DVEBMGS00
(11) 0x4000000000f65e0c   N_ab_run + 0x14 dw.sapD01_DVEBMGS00
(12) 0x4000000000f5fa88   dynpmcal + 0x198 dw.sapD01_DVEBMGS00
(13) 0x4000000000f5d500   dynppai0 + 0x830 dw.sapD01_DVEBMGS00
(14) 0x4000000000f5b8b4   dynprctl + 0x43c dw.sapD01_DVEBMGS00
(15) 0x4000000000f56728   dynpen00 + 0x2118 dw.sapD01_DVEBMGS00
(16) 0x400000000102f1b4   Thdynpen00 + 0x69c dw.sapD01_DVEBMGS00
(17) 0x400000000102e1e4   TskhLoop + 0x523c dw.sapD01_DVEBMGS00
(18) 0x4000000001022f50   tskhstart + 0x1e0 dw.sapD01_DVEBMGS00
(19) 0x4000000000dce3c4   DpMain + 0x484 dw.sapD01_DVEBMGS00
(20) 0x40000000022784cc   nlsui_main + 0x14 dw.sapD01_DVEBMGS00
(21) 0x4000000000a39534   main + 0x14 dw.sapD01_DVEBMGS00
(22) 0xc00000000000a588   $START$ + 0xa0 /usr/lib/pa20_64/dld.sl
List of ABAP programs affected
Type Program                            Gen. Date Time       Load Size
Prg   ZVXR0303                           09/29/2005 14:25:42       39936
Prg   SAPMSSY0                           05/01/2005 00:21:19       66560
Prg   SAPMSSYD                           06/05/2002 17:09:33       16384
Prg   SAPFSYSCALLS                       02/14/2002 14:22:47        6144
Prg   RSDBRUNT                           06/13/2004 00:43:20      226304
Typ   RSSCR                                / /       : m:15        5120
Prg   RSDBSPBL                           01/07/2003 18:47:02       59392
Prg   SAPDB__S                           02/14/2002 14:22:47       15360
Typ   VARID                              05/12/1997 16:51:30        4096
Prg   %_CSYDB0                           02/14/2002 14:22:46       28672
Prg   RSDBSPVA                           09/06/2005 22:54:22      112640
Prg   SAPLSVAR                           09/06/2005 22:57:28      625664
Typ   VARIS                              05/12/1997 15:27:21        2048
Typ   RSVAMEMKEY                         05/07/1997 13:07:49        2048
Prg   RSDBSPMC                           06/05/2002 17:09:26       66560
Typ   DDSHDESCR                          09/03/1997 03:05:16        3072
Typ   SPPARAMS                           05/07/1997 13:10:38        2048
Typ   SPPARAMS                           05/07/1997 13:10:38        2048
Typ   RSSELINT                           04/04/1995 16:12:37        2048
Prg   SAPLICON                           03/12/2004 06:57:52       23552
Prg   %_CICON                            02/14/2002 14:22:46       65536
Prg   SAPLSABE                           02/14/2002 14:22:47       11264
Prg   SAPLSECU                           05/23/2005 14:04:05       64512
Typ   RSSUBINFO                          10/14/1999 22:01:03        3072
Prg   %_CRSDS                            02/14/2002 14:22:46        8192
Typ   RSDSEXPR                           08/20/1998 10:57:18        2048
Prg   SAPLDSYA                           02/14/2002 14:22:47       39936
Prg   SAPFSDS1                           01/07/2003 18:32:17       47104
Typ   TDCLD                              11/02/1998 09:51:35        5120
Prg   SAPLSDOD                           04/30/2005 22:53:50       39936
Typ   DOKIL                              05/12/1997 16:46:17        3072
Prg   SAPCNVE                            02/14/2002 14:22:47        6144
Prg   SAPLLANG                           02/14/2002 14:22:47        8192
Typ   T002                               02/14/1998 10:24:58        2048
Typ   RSEXFCODE                          08/13/1997 12:52:57        1024
Prg   SAPFSPOR                           03/13/2004 19:20:44       12288
Prg   SAPLOMCV                           05/01/2005 00:14:10       16384
Prg   CL_EXITHANDLER================CP   06/13/2004 00:40:58       26624
Prg   SAPLSEXV                           09/06/2005 22:55:26      107520
Prg   CL_BADI_FLT_DATA_TRANS_AND_DB=CP   05/01/2005 00:21:35       33792
Typ   SXS_ATTR                           08/20/2001 12:23:27        4096
Typ   V_EXT_ACT                          11/09/2000 14:27:05        2048
Typ   SXC_EXIT                           11/09/2000 14:23:43        2048
Prg   CL_EX_BADI_MATN1==============CP   05/01/2005 00:14:04       22528
Prg   IF_EX_BADI_MATN1==============IP   06/13/2004 00:48:55        4096
Typ   TMCNV                              02/24/1999 03:33:25        3072
Prg   SAPLSCNT                           02/14/2002 14:22:47       24576
Typ   DYCBOX                             08/20/1998 11:16:53        2048
Prg   SAPLSVSM                           01/07/2003 18:35:45       22528
Prg   SAPLSGUI                           01/09/2003 17:15:12       31744
Prg   SAPLSTTM                           05/01/2005 00:24:04       75776
Prg   SAPLSBDC                           05/23/2005 14:05:19       38912
Prg   CL_DATAPROVIDER===============CP   02/14/2002 14:22:46       40960
Prg   %_CCNTL                            02/14/2002 14:22:46       13312
Typ   OBJ_RECORD                         02/14/1998 08:30:43        2048
Prg   SAPLSTUP                           05/23/2005 14:03:46       65536
Prg   SAPLCNDP                           05/23/2005 14:05:47      167936
Prg   SAPFGUICNTL                        01/09/2003 17:18:52       20480
Prg   SAPLOLEA                           05/23/2005 14:03:56       79872
Prg   SAPLSFES                           09/06/2005 22:53:55      191488
Prg   SAPLSPLUGIN                        02/14/2002 14:22:48        6144
Typ   ARFCRDATA                          11/09/2000 14:04:16        6144
Prg   SAPLGRFC                           02/14/2002 14:22:47       13312
Typ   SWCBCONT                           11/15/2000 17:55:11        3072
Typ   OLE_VERBS                          04/04/1995 16:02:20        2048
Typ   OLE_PA                             04/04/1995 16:02:19        2048
Prg   SAPSHDTV                           03/12/2004 06:40:27       28672
Typ   SSCRTEXTS                          09/03/1997 03:12:33        3072
Typ   SSCRFIELDS                         05/13/1997 12:54:26        4096
Prg   CL_GUI_PROPS_CONSUMER=========CP   01/07/2003 18:26:56       26624
Prg   SAPLTHFB                           09/06/2005 22:52:48      306176
Prg   CL_DYNAMIC_GUI_EXTENSIONS=====CP   02/14/2002 14:22:46       33792
Prg   CL_GUI_DATAMANAGER============CP   05/01/2005 00:20:36       70656
Prg   CL_ABAP_CHAR_UTILITIES========CP   05/01/2005 00:14:49       11264
Prg   RSDBSPVD                           05/01/2005 00:15:44       73728
Typ   RVARI                              03/30/1998 09:40:50        4096
Typ   RSVARIVDAT                         04/04/1995 16:12:54        2048
Typ   VBEP                               01/27/2003 16:50:17       10240
Typ   VBAP                               09/15/2005 11:15:36       44032
Prg   SAPLCEI0                           09/22/2005 14:34:40      936960
Typ   API_VALUE                          02/20/1998 08:46:47        2048
Prg   SAPLCUEV                           06/07/2001 18:26:56       10240
Prg   SAPLSUNI                           06/13/2004 00:42:30      131072
Typ   TFDIR                              07/29/1998 19:49:08        3072
Prg   %_CIBCO2                           03/13/2004 14:32:13       12288
Typ   IBINCOM                            06/01/1999 11:56:27        3072
Typ   IBINCONF                           06/01/1999 11:56:27        2048
Typ   IBSTCONF                           06/01/1999 11:56:28        1024
Prg   SAPLCUCB                           05/23/2005 15:20:17      192512
Typ   TCUIBSPECIAL                       06/07/2001 17:50:37        1024
Prg   %_CIBXX                            03/13/2004 14:38:45       49152
Typ   BAL_S_MSG                          12/04/2000 13:04:01        6144
Prg   CX_CBASE_ERROR================CP   01/27/2003 16:58:10       10240
Typ   SCX_SRCPOS                         11/09/2000 14:12:15        2048
Typ   BAL_S_CONT                         11/02/1998 09:43:07        2048
Typ   BAL_S_PARM                         12/04/2000 12:45:14        3072
Typ   BAL_S_CLBK                         11/02/1998 09:43:07        2048
Prg   CX_STATIC_CHECK===============CP   02/14/2002 14:22:47        8192
Prg   CX_ROOT=======================CP   02/14/2002 14:22:47        9216
Prg   CL_CBASE======================CP   05/23/2005 15:19:44       87040
Typ   T371G                              04/29/1998 10:42:48        2048
Prg   SAPLIBCO                           03/13/2004 15:32:40      269312
Prg   %_CIBCO                            03/13/2004 14:38:45       11264
Prg   SAPLIBXX                           03/13/2004 14:38:46       11264
Prg   SAPLIBIBF                          03/13/2004 14:38:46      179200
Prg   %_CIBIB                            03/13/2004 14:38:45       18432
Prg   SAPLIBINF                          06/12/2004 22:20:22      415744
Prg   %_CIBIN                            03/13/2004 15:32:40       48128
Prg   CL_IBASE_STRUC================CP   06/07/2001 19:59:10      106496
Prg   %_CIBST                            03/13/2004 14:38:45       37888
Prg   CL_IBASE_STRUC_BUF============CP   06/07/2001 19:59:10       89088
Prg   CL_IBASE_STRUC_STAT===========CP   06/07/2001 19:59:10        8192
Prg   CL_IBASE_STRUC_BUF_IBSTREF====CP   06/07/2001 19:59:10       35840
Prg   %_CIBCO1                           03/13/2004 14:38:45       14336
Typ   IBINVAL                            09/18/2001 10:02:52        2048
Prg   SAPLIBCU                           03/13/2004 14:38:46       12288
Prg   SAPLIBCUT                          06/07/2001 18:27:19       12288
Typ   T371B                              05/14/1998 22:58:43        2048
Typ   V_IBINR                            03/13/2004 15:32:40        5120
Typ   V_IBINR_CM                         03/13/2004 15:32:40        5120
Prg   CL_IBASE_SERVICE==============CP   06/07/2001 19:59:10       13312
Prg   CL_IBASE_T371D_BUF============CP   06/07/2001 19:59:10       12288
Typ   T371D                              08/27/1999 18:19:44        2048
Prg   CL_IBASE_R3_MATERIAL==========CP   05/23/2005 15:08:24       59392
Typ   MARA                               05/23/2005 15:08:18       22528
Typ   MAKT                               08/28/1997 08:52:19        2048
Typ   ICON                               01/03/1996 15:34:02        3072
Prg   CL_ABAP_TYPEDESCR=============CP   05/01/2005 00:20:10       21504
Prg   CL_ABAP_ELEMDESCR=============CP   05/01/2005 00:20:33       20480
Prg   CL_ABAP_DATADESCR=============CP   03/12/2004 07:16:33       14336
Prg   CL_ABAP_REFDESCR==============CP   03/12/2004 07:17:23       16384
Prg   CL_ABAP_STRUCTDESCR===========CP   05/01/2005 00:20:33       20480
Prg   CL_ABAP_COMPLEXDESCR==========CP   03/12/2004 07:16:33       13312
Prg   CL_ABAP_TABLEDESCR============CP   03/12/2004 07:17:23       17408
Prg   CL_ABAP_CLASSDESCR============CP   03/12/2004 07:17:23       23552
Prg   CL_ABAP_OBJECTDESCR===========CP   03/12/2004 07:17:23       25600
Prg   CL_ABAP_INTFDESCR=============CP   03/12/2004 07:16:33       19456
Prg   CL_ABAP_SOFT_REFERENCE========CP   03/29/2001 16:42:12        7168
Prg   CL_ABAP_REFERENCE=============CP   02/14/2002 14:22:46        6144
Prg   IF_EX_CM_BADI_VERSION=========IP   01/07/2002 16:09:04        3072
Prg   %_CABAP                            01/07/2003 18:31:23       23552
Typ   SXS_INTER                          11/30/1998 15:55:16        2048
Prg   CL_EX_CM_BADI_VERSION=========CP   05/01/2005 00:14:04       13312
Prg   %_CSXRT                            06/13/2004 00:40:55       11264
Prg   CL_EXIT_MASTER================CP   06/13/2004 00:40:58       13312
Typ   V_EXT_IMP                          11/09/2000 14:27:05        2048
Typ   V_EXT_IMP                          11/09/2000 14:27:05        2048
Typ   SXC_IMPSWH                         11/09/2000 14:23:44        2048
Prg   CL_IM_CM_BADI_VERSION_DEF=====CP   04/17/2002 11:01:00        6144
Prg   SAPLASTAT_TRIG                     02/14/2002 14:22:47       11264
Typ   ASTAT_TYP2                         11/10/1998 05:35:18        2048
Prg   IF_CM_BASELINE================IP   05/23/2005 15:08:24        9216
Prg   IF_IBASE_IBOF_TREE_OBJECT=====IP   05/23/2005 15:08:24        5120
Prg   IF_IBASE_INSTALL==============IP   06/07/2001 20:08:54        4096
Prg   IF_IBASE_MATERIAL=============IP   06/07/2001 20:08:54        3072
Prg   IF_IBASE_OBJECT===============IP   06/07/2001 20:08:54        4096
Prg   SAPLBOMA                           02/14/2002 14:15:40       10240
Typ   IONRA                              03/12/2004 02:09:40       23552
Typ   IBIBCOM                            08/30/2001 17:56:57        4096
Typ   IBIB                               03/13/2004 14:32:13        5120
Prg   CL_IBASE_STRUC_SERVICE========CP   06/07/2001 19:59:10       17408
Prg   CL_CU_CBASE_ENQUEUE_CORE======CP   06/07/2001 19:58:59       11264
Prg   CL_CU_CBASE_ENQUEUE===========CP   06/07/2001 19:58:59       16384
Typ   T371F                              06/01/1999 12:00:49        2048
Typ   V_IBIN_SYVAL                       03/13/2004 15:32:41        4096
Typ   IBIN                               09/18/2001 10:02:52        6144
Typ   IBINOWN                            02/01/2000 14:56:07        2048
Prg   CL_IBASE_T371F_BUF============CP   06/07/2001 19:59:11        8192
Prg   CL_IBASE_STRUC_FILT_02========CP   06/07/2001 19:59:10       11264
Prg   CL_IBASE_STRUC_FILT===========CP   06/07/2001 19:59:10       10240
Typ   IBST                               09/18/2001 10:02:52        4096
Typ   IBST                               09/18/2001 10:02:52        4096
Typ   IBSTREF                            04/15/1998 00:20:43        2048
Typ   IBSTREF                            04/15/1998 00:20:43        2048
Prg   IF_CBASE_E====================IP   06/07/2001 20:08:25        3072
Prg   %_CCXTAB                           02/14/2002 14:22:46        6144
Prg   SAPLCUCQ                           09/15/2005 11:15:38       79872
Typ   CUCO                               09/18/2001 10:02:34       18432
Typ   CUCO_OBJ                           09/18/2001 10:02:34       18432
Prg   SAPLCLCA                           09/06/2005 23:33:29       68608
Typ   TCLA                               03/13/2004 14:10:20        5120
Typ   TCLAO                              08/13/1997 13:57:22        4096
Prg   SAPLCUOB                           05/23/2005 14:31:35       31744
Typ   INOB                               09/03/1997 03:20:02        4096
Prg   SAPLCLSE                           05/23/2005 14:32:26      167936
Prg   %_CCC01                            05/01/2005 00:34:57       53248
Typ   TABLEKEY                           07/06/1998 21:01:06        2048
Typ   KSSK                               09/18/2001 10:02:58        3072
Prg   SAPLCLEF

SAP Ecc6.0 Installation error during ABAP Import Phase 20 of 24

While I am installing SAP ECC 6.0 with Original DVD. I am getting some Issues.
I had finished upto 4 stpes . and after that IMPORT ABAP, showing error in " Log files are written to C: Program files:sapinst......"
Please Retry , View Log & Stop.
I am clicking Retry again it will be come same issue. Please Let me know.
Log Files Name - "ABAP Processors of Instances SID\DVEMGS00"

Still I am getting same problem in mine SAP ECC6.0 Installation.
In Abap Instance Phase 20 of 24. Error in ABAP Instance. I check the mmc.
Disp+work is in Gray Color. Remainiing Server Green Color. After Few minutes it will stopped in Work Process.
Still Going Installation for same Process.
Let me know.

How to find out which abap queries were executed by a user

Dear SAP Gurus,
Is there a way to find out which abap queries were executed by an end user in the recent past??
1.I tried using the t-code "stat" BUT:
dont seem to be getting any results even though I put the start time almost 2 months back.
2.Also when using STAT, I give the report name of the query in the program field but it seems to truncate it.
Any ideas how can I find out which abap queries were executed by the end user.
thanks a lot, I'll make sure to award points for your help.

STAT will give you the information for a limited period of time and is limited to the server which you are logged onto yourself. Beyond 24 hours it is of even less use even if you change the selection screen values.
If you want it for a period way back into the past, then you need to use ST03N.
There are at least 2 dependencies and 1 confusion:
1 dependency) The length of period is determined by the size (length) of the file. You can change this in ST03N (default 50MB) via the menu settings.
2 dependency) The stat collector jobs need to be scheduled to write the information to ST03N (once per hour is a legal requirement in some non-banana republic countries).
1 confusion) There is an obscure function which converts a report submit to a transaction name (there is not much difference anyway) and an even more obsure one which filters what ST03N will record and therefore whether you can read it. You can (un)filter these things away if you search the SAP Marketplace for the term "MONI".
What is of particular value from this control is that you can even detect a submission of an abap which only existed temporarily.
Also note that having this information is potentially very powerfull with respect to the users (some of them are human too), so you should expose and use it responsibly.
You should also ensure that only responsible users / auditors have access to S_TOOLS_EX.

Error "Error in ABAP statement when processing an internal table. table."

Hello,
I am facing the error when tried for GR from SRM portal for my shopping cart and for others created shopping cart. The error is
"Error in ABAP statement when processing an internal table. table."
I have the central receipient role. Couold any body assist me?
Thanks,
Pijush

Hi Harish,
Execute the query in RSRT and check whether you have any short dump is in ST22. This would give a clear idea at what might have gone wrong.
Another thing is to check whether the code for the variable is fine in the user exit.
Hope this helps.
Bye
Dinesh

Executing Abap Queries in Abap Code and processing the result

Hi,
I want to execute ABAP Queries (designed by sq01) in an abap report and processing the result in an internal table.
How could it be work?
Thanks a lot for your responses,
with kind Regards
Reinhold Strobl

Hello,
GO to SQ01 and select your query. Go to Menu QUERY-->More Functions->Display Report Name.
You can then take that report name and go to SE38. Copy the code before END-OF_SELECTION and then modify as per your own requirements.
Regrads
Saket Sharma

Deployment error - Errors in named queries in weblogic 10

Hi, All.
I got the error message when I tried to deploy my webapp to weblogic 10 & 10.1(10M1).
Stacktrace:
<May 19, 2008 11:51:14 AM EDT> <Error> <Console> <BEA-240003> <Console encounter
ed the following error weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:314)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedM
oduleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.ja
va:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.j
ava:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(Deployme
ntStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(App
ContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.cr
eateAndPrepareContainer(ActivateOperation.java:189)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do
Prepare(ActivateOperation.java:87)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.pr
epare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym
entPrepare(DeploymentManager.java:719)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploy
mentList(DeploymentManager.java:1186)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare
(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.pre
pare(DeploymentServiceDispatcher.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Caused by: java.lang.Throwable: Substituted for missing class org.hibernate.Hibe
rnateException - Errors in named queries: SpotType.findById, Spot.findByTopic, T
argetAudience.findById, SpotOrder.findById, SpotAuditDetails.findById, ProjectOf
ficer.findById, SpotOrderAvailable.findById, ProjectOfficer.findByStatus, SpotOr
derTopic.findById, Topic.findById, findAllSpots, SpotOrderDetails.findById, find
AllCategory, SME.findById, SpotAudit.findById, ContactInfo.findById, SpotCategor
y.findById, SpotOrderTopicSpot.findById, ProjectTopic.findById, NetworkType.find
ById, Source.findById, NetworkType.findByStatus, RecordStatus.findById, SpotType
.findByStatus, findAllClient, Spot.findByTitle, findAllRecordStatus, SMETopicCom
ments.findById, ContractInfo.findById, Channel.findById, Client.findById, findAl
lSource, SMETopic.findById, Project.findById, SpotComments.findById, SpotOrderCo
mments.findById, ContactInfoComments.findById, Spot.findById
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:
365)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.jav
a:1300)
at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(Annotat
ionConfiguration.java:859)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Con
figuration.java:669)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFa
ctory(HibernatePersistence.java:132)
at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactor
y(PersistenceUnitInfoImpl.java:264)
at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInf
oImpl.java:110)
at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(
AbstractPersistenceUnitRegistry.java:316)
at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDe
scriptors(AbstractPersistenceUnitRegistry.java:96)
at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersis
tenceUnitRegistry.java:53)
at weblogic.servlet.internal.WebAppModule.initPURegistry(WebAppModule.ja
va:1151)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:304)
>
I included named queries on orm.xml file and also in each entities using annotations like following.
orm.xml>
<?xml version="1.0" encoding="UTF-8"?>
<entity-mappings xmlns="http://java.sun.com/xml/ns/persistence/orm" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/persistence/orm http://java.sun.com/xml/ns/persistence/orm_1_0.xsd"
     version="1.0">
     
     <named-query name="findAllClient">
<query><![CDATA[SELECT e FROM Client e ORDER BY e.clientName]]></query>
</named-query>
<named-query name="findAllSource">
<query><![CDATA[SELECT e FROM Source e ORDER BY e.sourceDesc]]></query>
</named-query>
<named-query name="findAllCategory">
<query><![CDATA[SELECT e FROM SpotCategory e ORDER BY e.spotCategoryDesc]]></query>
</named-query>
<named-query name="findAllRecordStatus">
<query><![CDATA[SELECT e FROM RecordStatus e ORDER BY e.id]]></query>
</named-query>
<named-query name="findAllSpots">
<query><![CDATA[SELECT e FROM Spot e ORDER BY e.id]]></query>
</named-query>
</entity-mappings>
entity example:
@Entity
@Table(name = "SPOTTYPE")
@NamedQueries( { @NamedQuery(name = "SpotType.findById", query = "SELECT e FROM SpotType e WHERE e.id = :id"),
     @NamedQuery(name = "SpotType.findByStatus", query = "SELECT e FROM SpotType e WHERE e.recordStatus.id = :status") })
public class SpotType implements Serializable {
private static final long serialVersionUID = 1L;
@Id
@GeneratedValue(generator = "spotTypeSeq")
@SequenceGenerator(name = "spotTypeSeq", sequenceName = "SEQ_SPOTTYPE", allocationSize = 1)
@Column(name = "SPOTTYPEID", nullable = false, length = 2)
private Long id;
@Column(name = "SPOTTYPESHRTNM", nullable = false, length = 2)
private String spotTypeShortName;
@Column(name = "SPOTTYPELONGNM", nullable = false, length = 35)
everything works until I clicked the activate the change button. I tried to override libs by putting libs I'm using in my domain, still I have the same error message.
Libs that I have:
Name 5 Size Type Date Modified
antlr-2.7.6.jar 434 KB ALZip jar File 2/13/2008 5:28 PM
asm.jar 26 KB ALZip jar File 2/13/2008 5:28 PM
asm-attrs.jar 17 KB ALZip jar File 3/17/2005 4:05 PM
cglib-2.1.3.jar 276 KB ALZip jar File 2/13/2008 5:28 PM
commons-beanutils-1.7.0.jar 185 KB ALZip jar File 12/15/2007 7:12 PM
commons-codec-1.3.jar 46 KB ALZip jar File 12/15/2007 7:12 PM
commons-collections-3.1.jar 547 KB ALZip jar File 4/24/2008 10:28 AM
commons-digester-1.8.jar 141 KB ALZip jar File 12/15/2007 7:13 PM
commons-discovery-0.4.jar 75 KB ALZip jar File 12/15/2007 9:08 PM
commons-el-1.0.jar 110 KB ALZip jar File 5/15/2008 1:11 PM
commons-logging-1.0.4.jar 38 KB ALZip jar File 7/4/2004 4:49 AM
dom4j-1.6.1.jar 307 KB ALZip jar File 2/13/2008 5:28 PM
ehcache-1.2.jar 116 KB ALZip jar File 2/13/2008 5:28 PM
ejb3-persistence.jar 52 KB ALZip jar File 3/14/2008 4:45 PM
hibernate3.jar 2,222 KB ALZip jar File 2/6/2008 9:31 PM
hibernate-annotations.jar 274 KB ALZip jar File 3/14/2008 4:44 PM
hibernate-commons-annotatio... 65 KB ALZip jar File 3/14/2008 4:45 PM
hibernate-entitymanager.jar 116 KB ALZip jar File 3/14/2008 8:07 PM
jaas.jar 102 KB ALZip jar File 6/3/2004 11:31 AM
javassist.jar 449 KB ALZip jar File 2/13/2008 5:28 PM
jaxen-1.1-beta-7.jar 222 KB ALZip jar File 8/16/2005 2:04 PM
jboss-archive-browsing.jar 13 KB ALZip jar File 2/13/2008 5:28 PM
jhighlight-1.0.jar 92 KB ALZip jar File 12/20/2007 4:51 PM
jsf-facelets.jar 294 KB ALZip jar File 9/27/2007 12:20 PM
jstl-1.2.jar 405 KB ALZip jar File 5/15/2008 1:12 PM
jta.jar 9 KB ALZip jar File 6/3/2004 11:31 AM
junit-4.4.jar 158 KB ALZip jar File 5/15/2008 1:12 PM
log4j-1.2.11.jar 343 KB ALZip jar File 8/13/2005 3:28 PM
myfaces-api-1.2.2.jar 319 KB ALZip jar File 1/22/2008 3:40 PM
myfaces-impl-1.2.2.jar 739 KB ALZip jar File 1/22/2008 3:40 PM
nekohtml-0.9.5.jar 104 KB ALZip jar File 12/20/2007 4:42 PM
ojdbc14.jar 1,322 KB ALZip jar File 2/13/2008 5:30 PM
readme.txt 1 KB Text Document 5/15/2008 3:58 PM
richfaces-api-3.2.0.GA.jar 150 KB ALZip jar File 3/31/2008 4:23 PM
richfaces-impl-3.2.0.GA.jar 1,372 KB ALZip jar File 3/31/2008 4:23 PM
richfaces-ui-3.2.0.GA.jar 2,215 KB ALZip jar File 3/31/2008 4:50 PM
spring.jar 2,604 KB ALZip jar File 5/15/2008 1:12 PM
xerces-2.6.2.jar 988 KB ALZip jar File 12/19/2004 6:14 PM
xml-apis.jar 121 KB ALZip jar File 6/3/2004 11:31 AM
This can be deployed to tomcat 6 without any problems.
Thank you in advance for reading and your help.
Edited by gzson at 05/19/2008 9:07 AM

Follow the below link:
http://www.hibernate.org/250.html#A25

How to avoid time out error in abap program

How to avoid time out error in abap program
based on performance wise i want please help

Timeout occurs when a statement exceeds its time limit.To avoid this we need to tune the statements.
I can give give you few tips for tune a select stament.
1.The order of the feilds in the select statement should be same as the order of fields in the database table.
2.It is always advisible to use the key fields when you are using the where clause.
3. Sort the internal table while using the for all entreis statements.
4.Use index in where clause if necessary.
5.When you have a read statement user binary search but before this a sort statement should be there.
6. Check your program with the Tcode ST05 and check which statement takes much time based on that tune that.

ABAP Queries

We have just upgraded from 4.6 to 6.0. I have noticed lot of differences in the code behind the ABAP queries that is generated once the queries are created. In some instances they are form bunch of include programs like the ones below but in some other queries its the regular code of a query program like it used to be in 4.6 . I also noticed that the extra coding I did in the END_OF_SELECTION event of the Infoset is not getting picked when I execute the query. Have any of you encountered these things?
*report AQICZSD_CORP====Z_DIR_SALE_NEW.*
*include /1BCDWB/IQ000000000725DAT.*
*data %dtab type standard table of /1BCDWB/IQ000000000725 with header line.*
*data %subrc type sy-subrc.*
*include /1BCDWB/IQ000000000725SSCR.*
*include /1BCDWB/IQ000000000725SSCRAT.*
*start-of-selection.*
*if %runmode-extr_on <> space.*
    *call function '/1BCDWB/IQ000000000725EXTR'*
         *tables     %selopt = %seloptions*
                    *%dtab   = %dtab*
         *changing   %rtmode = %runmode*
         *exceptions no_data = 1*
                    *others = 2.*
    *%subrc = sy-subrc.*
    *call function 'RSAQRT_CHECK_EXTR'*
         *exporting extr_subrc = %subrc*
         *tables    dtab   = %dtab*
         *changing rtmode = %runmode.*
*endif.*
*end-of-selection.*
*if %runmode-show_on <> space.*
    *call function '/1BCDWB/IQ000000000725SHOW'*
         *tables   %dtab   = %dtab*
         *changing %rtmode = %runmode.*
*endif.*
   special code for old API and BW extractor calls**
*form %set_data changing p_lines type i.*
*import ldata to %dtab from memory id 'AQLISTDATA'.*
*describe table %dtab lines p_lines.*
*free memory id 'AQLISTDATA'.*
*endform.*
*form %get_data tables p_dtab structure %dtab*
               *using p_first type i*
                      *p_last type i.*
*append lines of %dtab from p_first to p_last to p_dtab.*
*endform.*
*form %get_ref_to_table using p_lid   type aql_lid*
                             *p_ref   type ref to data*
                             *p_subrc type i.*
*if p_lid = %iqid-lid.*
    *create data p_ref like %dtab[].*
    *p_subrc = 0.*
*else.*
    *p_subrc = 4.*
*endif.*
*endform.*

Hi Jak,
I guess all ur questions are answered except 2.
Ans2. Well a correction is a change done to a original SAP object, while a repair is done to a duplicate SAP objects. (I hope its not vice vers, I am bit confused wid that : ) )
Lets take an example. All the object on a customer system are duplicate object since they are all copy of Original SAP object. So if u make a modification to an existing SAP object at a customer system it comes under the category of Repair i.e all customer modifications of SAP standard objects are repairs.
While if SAP makes changes to its original object it comes under Corrections. i.e all support packages / Notes comes wid correction requests.
Now what if a customer has its own object changed .. .then it wil come under the cateogry of correction and not repair.
Now the trick is which system Dev , Test , Prod ...
well ofcourse Development .. since your test and production system contains a copy of the objects in Development system. : )
hope this help .... but please verify the answer I may not be 100 percent correct.
regards,
Sumeet Mishra

Creating ABAP queries with t-code SQ01 in SRM

Hi.
What tables are available for me to use ABAP queries with t-code in SRM as we currently use this for MM.
Please can someone tell me if a list of usefull tables for Carts, Approvals, PO are available in SRM as I cannot find these in SE11. We have no BW and need ABAP query for fullfilings any business requirements.
Thankyou.
Vijay.

Please search the documents in transaction BBP_PD. When you click the details it will give you the table details as well.
Additionally check this thread for details
good source for tables and reports
Regards
Kathirvel

Errors in ABAP queries

Similar Messages

Maybe you are looking for