JRE performances while executing small components

Hello,
I am developing a very small component that will be executed on a very busy machine.
For this reason I am concerned about the performances while using the JRE to executing it.
The component will also be called multiple times, possibly in parallel.
My question is: how does the JRE works in this case?
Will the JRE loaded on the memory every time the component is executed, or will it be loaded before?
Thank you

The JRE will be loaded for each process that is created.
And the detail you provided doesn't provide enough informaton to indicate whether there is a server application running this or a new process is invoked each time.

Similar Messages

Low qtp performance while executing from eCATT

Hi All,
I have executed Test Package containing eCATT Test Configuration.QTP Scipts are attached in eCATT & eCATT Test Configurations in test package.While executing individual test cases they work fine.But when I executed them in batch(Test Package) the performance was bad.
I got the following error,
'Execution was cancelled in --- from --- runs'.
Also I got some other errors like,
'External test tool 'MERCURY QUICK TEST PROFESSIONAL' is busy and cannot create new test script'.
Can anybody answer what can be the reason.
Thanks,

You can also create a table with the desired records and drop this one.
CREATE TABLE PROFITS_TT2_TEMP AS
SELECT * FROM
(SELECT pt.*, row_number() over (partition by channel_id, cust_id, prod_id order by channel_id) rn
FROM profits_tt2
WHERE rn = 1;

Poor performance while executing

hi,
the java pgm involves display of pictures and movies... but if there are other applications running then it becomes very very slow. WHy is it so? I am using Redhat 9 Linux platform and jdk1.4.5. i have to run the other applciations... y is it that its takin so much time to display each pic. Could there b some memory problem as the pic and movies take a lot of space and the garbage collector doesnt ahve enuf time to recollect the memory?

I would try settings a lower (=higher value) process priority with nice...The nice level influences only the contest for the processor. It won't help with I/O issues.
It would be worth to try to run the other applciation so that it writes into a file instead of to a console and compare the outcome.

Facing a small problem while executing WDA application from portal

Hi Experts,
I developed web dynpro for ABAP application and placed table UI control, which contains 270 records. Executing from SE80, it is working fine and showing clearly all records.
This application integrated in portal, while executing this applicaiton from portal, it is working fine and showing all records.
Here I facing a small problem i.e Pager ( footer area ) of table.
When the table is displayed there are the small box in the below of the table showing ROWS 244 of 270.
244 will be available in a small box. this 244 is not showing clearly, while executing from portal ( last digit 4 displying half part only). but 244 showing clearly while executing from SE80.
Kindly suggest how to resolve this problem.
Thanks & Regards
Sridhar

Hi Gopi Krishna,
Thanks for your time. From SE80, it is working fine and showing clearly row number. There is no property for increase width of small box, which contains current row number).
Facing problem while executing from portal.
Thanks & Regards
Sridhar

Error while executing interface

Hello Friends
The team is trying to integrate 3 sap standard tables into 1 table.
The have a requirement to interface @ 25 sap standard tables.
with 2 tables joining it works fine.
The 2 interfaces run a ABAP program in the form of background job; in the SAP system which integrates these tables.
While executing the program in the SAP system we get the memory dump as mentioned below;
Runtime Errors         TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
Date and Time          24.03.2009 10:27:20
Short text
     No roll storage space of length 1994768 available for internal storage.
What happened?
     Each transaction requires some main memory space to process
     application data. If the operating system cannot provide any more
     space, the transaction is terminated.
What can you do?
     Try to find out (e.g. by targetted data selection) whether the
     transaction will run with less main memory.
     If there is a temporary bottleneck, execute the transaction again.
     If the error persists, ask your system administrator to check the
     following profile parameters:
     o ztta/roll_area            (1.000.000 - 15.000.000)
            Classic roll area per user and internal mode
            usual amount of roll area per user and internal mode
     o ztta/roll_extension       (10.000.000 - 500.000.000)
        Amount of memory per user in extended memory (EM)
o abap/heap_area_total      (100.000.000 - 1.500.000.000)
        Amount of memory (malloc) for all users of an application
        server. If several background processes are running on
        one server, temporary bottlenecks may occur.
        Of course, the amount of memory (in bytes) must also be
        available on the machine (main memory or file system swap).
        Caution:
        The operating system must be set up so that there is also
        enough memory for each process. Usually, the maximum address
        space is too small.
        Ask your hardware manufacturer or your competence center
        about this.
        In this case, consult your hardware vendor
abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
        Restriction of memory allocated to the heap with malloc
        for each dialog process.
Parameters for background processes:
abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
        Restriction of memory allocated to the heap with malloc
        for each background process.
Other memory-relevant parameters are:
em/initial_size_MB:         (35-1200)
        Extended memory area from which all users of an
        application server can satisfy their memory requirement.
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
.    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
Error analysis
    The internal table "\FUNCTION=ZODI_18011_18011\DATA=IT_FINAL[]" could not
     enlarged further.
    Memory location: "Session memory"
    You attempted to extend the data structure for the management of the
    memory blocks for table "\FUNCTION=ZODI_18011_18011\DATA=IT_FINAL[]". Howe
     the 1994768 bytes required for
    this were no longer available in the specified memory area.
    The amount of memory requested is no longer available.
How to correct the error
    Try to decide by analysis whether this request is
    reasonable or whether there is a program error. You should pay
    particular attention to the internal table entries listed below.
    The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 16192
Extended memory (EM)........... 4189840
Assigned memory (HEAP)......... 0
Short area..................... " "
Paging area.................... 0
Maximum address space.......... " "
System details;
ECC 6.0 SP level 13 Oracle data base release 10.2.0.2.0.
64 bit 16 GB RAM
I have checked with the sap notes but not sure enough with what tuning can be done for the same.
Basis memory checks are performed.
Thanks and Regards
Pooja

Hi Pooja
your problem is memory consumption problem,
if you want overcume these problem you need to tuning paramateors.
in SAP we have 3 types of memory areas are available
1. Primary memory that is called roll_area
2. Extended memory
3. Heap Memory
above each memory areas has reserved some amount of space
if not enoghf Primary memory for perticular transaction, then it will use extended memory then again not enoghf extended memory then it will go to heap memory, then that time transaction is terminated.
so you need to increase below prametor value in RZ10
ztta/roll_extension
next you need to restart sap other wise it wont effect which your changes values.
regards
Bandla

Dump error while executing this unicode program.....

Hi,
     I got a program for 'Production Order Quantity Change Daily Checklist' ,but while executing i got the dump error from the following program stating tat,
The current statement is only defined for character-type data objects.
Error in the ABAP Application Program
The current ABAP program "ZPROD" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
For the statement
   "READ DATASET ... INTO f"
only character-type data objects are supported at the argument position
"f".
In this case. the operand "f" has the non-character-type "u". The
current program is a Unicode program. In the Unicode context, the type
'X' or structures containing not only character-type components are
regarded as non-character-type.
Program:
REPORT ZPPORDER LINE-SIZE 180 NO STANDARD PAGE HEADING
                LINE-COUNT 058(001).
TABLES: AUFK, "Order master data
        AFKO, "Order header data PP orders
        RESB, "Reservation/dependent requirements
        MAST, "Material to BOM Link
        STKO, "BOM Header
        STPO. "BOM item
DATA: BEGIN OF WA,
         AUART      TYPE AUFK-AUART,
         AUFNR      TYPE AUFK-AUFNR,
         AEDAT      TYPE AUFK-AEDAT,
         AENAM      TYPE AUFK-AENAM,
         WERKS      TYPE AUFK-WERKS,
         PLNBEZ     TYPE AFKO-PLNBEZ,
         GAMNG      TYPE AFKO-GAMNG,
         GASMG      TYPE AFKO-GASMG,
         MATNR      TYPE RESB-MATNR,
         POSNR      TYPE RESB-POSNR,
         BDMNG      TYPE RESB-BDMNG,
         BMENG      TYPE STKO-BMENG,
         MENGE      TYPE STPO-MENGE,
      END OF WA,
      ITAB LIKE SORTED   TABLE OF WA WITH NON-UNIQUE KEY AUFNR POSNR.
DATA: BEGIN OF ITAB2 OCCURS 0.
      INCLUDE STRUCTURE WA.
DATA: END OF ITAB2.
DATA: BEGIN OF ITAB_AUFK OCCURS 0,
      AUART LIKE AUFK-AUART,
      AUFNR LIKE AUFK-AUFNR,
      POSNR LIKE RESB-POSNR,
      AEDAT LIKE AUFK-AEDAT,
      AENAM LIKE AUFK-AENAM,
      WERKS LIKE AUFK-WERKS,
      PLNBEZ LIKE AFKO-PLNBEZ,
      GAMNG(7) TYPE P DECIMALS 0,
      GASMG(7) TYPE P DECIMALS 0,
      MATNR LIKE RESB-MATNR,
      BDMNG(7) TYPE P DECIMALS 0,
      BMENG(7) TYPE P DECIMALS 0,
      MENGE(7) TYPE P DECIMALS 3.
DATA: END OF ITAB_AUFK.
DATA: FDATE LIKE SY-DATUM,
      LDATE LIKE SY-DATUM.
DATA: X_AUFNR LIKE AFKO-AUFNR,
      X_MENGE(7) TYPE P DECIMALS 0,
      X_ERR(3).
DATA: W_DATASET1(500) VALUE '/usr/sap/trans/data/'.
SELECT-OPTIONS T_WERKS FOR AUFK-WERKS OBLIGATORY.
SELECT-OPTIONS T_AUFNR FOR AUFK-AUFNR.
SELECT-OPTIONS T_AEDAT FOR AUFK-AEDAT.
PARAMETERS     PDATA    LIKE W_DATASET1.
CONCATENATE W_DATASET1 PDATA INTO W_DATASET1.
PERFORM F_COLLECT_DATA.
FORM F_COLLECT_DATA.
OPEN DATASET W_DATASET1 FOR INPUT IN TEXT MODE encoding default.
DO.
     IF sy-subrc <> 0.
        EXIT.
     ENDIF.
     READ DATASET W_DATASET1 INTO WA.
     APPEND WA TO ITAB2.
ENDDO.
CLOSE DATASET W_DATASET1.
SELECT AAUFNR AAUART AAEDAT AAENAM A~WERKS
        BPLNBEZ BGAMNG B~GASMG
        CMATNR CBDMNG C~POSNR
     INTO CORRESPONDING FIELDS OF TABLE ITAB
     FROM          ( AUFK AS A
          INNER JOIN AFKO AS B ON BAUFNR = AAUFNR
          INNER JOIN RESB AS C ON CAUFNR = AAUFNR )
     WHERE A~AEDAT IN T_AEDAT
       AND A~WERKS IN T_WERKS.
     LOOP AT ITAB INTO WA.
        CLEAR MAST.
        SELECT SINGLE * FROM MAST WHERE MATNR = WA-PLNBEZ
                                    AND WERKS = WA-WERKS.
        CLEAR STKO.
        SELECT SINGLE * FROM STKO WHERE STLNR = MAST-STLNR
                                    AND STLAL = MAST-STLAL.
        CLEAR STPO.
        SELECT SINGLE * FROM STPO WHERE STLNR = MAST-STLNR
                                    AND POSNR = WA-POSNR.
        WA-BMENG = STKO-BMENG.
        WA-MENGE = STPO-MENGE.
        MODIFY ITAB FROM WA.
        AT NEW AUFNR.
           SKIP.
        ENDAT.
        LOOP AT ITAB2 WHERE AUFNR = WA-AUFNR
                        AND POSNR = WA-POSNR.
            IF ITAB2-GAMNG <> WA-GAMNG OR
               ITAB2-GASMG <> WA-GASMG OR
               ITAB2-BDMNG <> WA-BDMNG.
               CLEAR X_MENGE.
               IF ITAB2-BMENG <> 0.
                  X_MENGE = ITAB2-GAMNG / ITAB2-BMENG * ITAB2-MENGE.
               ENDIF.
               CLEAR X_ERR.
               IF ITAB2-BDMNG <> X_MENGE.
                  X_ERR = 'Err'.
               ENDIF.
               FORMAT COLOR COL_TOTAL.
               WRITE: / ITAB2-AUART UNDER 'Type',
                        ITAB2-AUFNR UNDER 'Prod Order',
                        ITAB2-AEDAT UNDER 'Last Chg Dt',
                        ITAB2-AENAM UNDER 'Last Chg by',
                        ITAB2-WERKS UNDER 'Plant',
                        ITAB2-PLNBEZ UNDER 'Material',
                   (10) ITAB2-GAMNG UNDER 'Order Qty' DECIMALS 0,
                   (10) ITAB2-GASMG UNDER 'Scrap Qty' DECIMALS 0,
                        ITAB2-POSNR UNDER 'Item',
                        ITAB2-MATNR UNDER 'Component Req',
                   (10) ITAB2-BDMNG UNDER 'Req Qty' DECIMALS 0,
                        X_MENGE      UNDER 'BOM Qty' COLOR COL_TOTAL,
                        ITAB2-BMENG UNDER 'BOM Base',
                        ITAB2-MENGE UNDER 'BOM Comp',
                        X_ERR        UNDER 'Rmks' COLOR COL_TOTAL.
               CLEAR X_MENGE.
               IF WA-BMENG <> 0.
                  X_MENGE = WA-GAMNG / WA-BMENG * WA-MENGE.
               ENDIF.
               CLEAR X_ERR.
               IF WA-BDMNG <> X_MENGE.
                  X_ERR = 'Err'.
               ENDIF.
               FORMAT COLOR OFF.
               WRITE: / WA-AUART UNDER 'Type',
                        WA-AUFNR UNDER 'Prod Order',
                        WA-AEDAT UNDER 'Last Chg Dt',
                        WA-AENAM UNDER 'Last Chg by',
                        WA-WERKS UNDER 'Plant',
                        WA-PLNBEZ UNDER 'Material',
                   (10) WA-GAMNG UNDER 'Order Qty' DECIMALS 0,
                   (10) WA-GASMG UNDER 'Scrap Qty' DECIMALS 0,
                        WA-POSNR UNDER 'Item',
                        WA-MATNR UNDER 'Component Req',
                   (10) WA-BDMNG UNDER 'Req Qty' DECIMALS 0,
                        X_MENGE   UNDER 'BOM Qty' COLOR COL_TOTAL,
                        WA-BMENG UNDER 'BOM Base',
                        WA-MENGE UNDER 'BOM Comp',
                        X_ERR     UNDER 'Rmks' COLOR COL_TOTAL.
             ENDIF.
        ENDLOOP.
     ENDLOOP.
   LOOP AT ITAB2.
        LOOP AT ITAB INTO WA WHERE AUFNR = ITAB2-AUFNR
                               AND POSNR = ITAB2-POSNR.
             DELETE ITAB2.
        ENDLOOP.
        SELECT SINGLE * FROM AUFK WHERE AUFNR = ITAB2-AUFNR.
        IF SY-SUBRC <> 0.
             DELETE ITAB2.
        ENDIF.
   ENDLOOP.
   OPEN DATASET W_DATASET1 FOR OUTPUT IN TEXT MODE encoding default.
        LOOP AT ITAB INTO WA.
           TRANSFER WA TO W_DATASET1.
        ENDLOOP.
        LOOP AT ITAB2 INTO WA.
           TRANSFER WA TO W_DATASET1.
        ENDLOOP.
   CLOSE DATASET W_DATASET1.
ENDFORM.
TOP-OF-PAGE.
    FORMAT COLOR COL_TOTAL.
    WRITE: / SY-DATUM, SY-UZEIT, SY-REPID, SY-UNAME,
         50 'Daily Qty Changed Checklist for Production Order',
        120 SY-PAGNO.
    SKIP.
    WRITE: / 'Plant ', T_WERKS-LOW.
    WRITE:   ' Last Change Date ', T_AEDAT-LOW, ' to ', T_AEDAT-HIGH.
    SKIP.
    WRITE: /1 'Type',
            6 'Prod Order',
            17 'Last Chg Dt',
            29 'Last Chg by',
            42 'Plant',
            49 'Material',
            69 'Order Qty',
            83 'Scrap Qty',
            99 'Item',
           105 'Component Req',
           121 'Req Qty',
           135 'BOM Qty',
           149 'BOM Base',
           163 'BOM Comp',
           178 'Rmks'.
     ULINE.
     WRITE: / 'Previous data :- '.
     FORMAT COLOR OFF.
     WRITE: / 'Current data :- '.
INITIALIZATION.
   LDATE = SY-DATUM.
   LDATE = LDATE - 1.
   FDATE = LDATE.
   MOVE:   FDATE         TO T_AEDAT-LOW.
   APPEND T_AEDAT.
   PDATA = 'AE001'.
So,give me any suggestions where to customize r do rectify the error.This will be useful for me.
Advance Thnx..

*REPORT ZPROD.
REPORT ZPPORDER LINE-SIZE 180 NO STANDARD PAGE HEADING
                LINE-COUNT 058(001).
TABLES: AUFK, "Order master data
        AFKO, "Order header data PP orders
        RESB, "Reservation/dependent requirements
        MAST, "Material to BOM Link
        STKO, "BOM Header
        STPO. "BOM item
DATA: BEGIN OF WA,
         AUART      TYPE AUFK-AUART,
         AUFNR      TYPE AUFK-AUFNR,
         AEDAT      TYPE AUFK-AEDAT,
         AENAM      TYPE AUFK-AENAM,
         WERKS      TYPE AUFK-WERKS,
         PLNBEZ     TYPE AFKO-PLNBEZ,
         GAMNG      TYPE AFKO-GAMNG,
         GASMG      TYPE AFKO-GASMG,
         MATNR      TYPE RESB-MATNR,
         POSNR      TYPE RESB-POSNR,
         BDMNG      TYPE RESB-BDMNG,
         BMENG      TYPE STKO-BMENG,
         MENGE      TYPE STPO-MENGE,
      END OF WA,
      ITAB LIKE SORTED   TABLE OF WA WITH NON-UNIQUE KEY AUFNR POSNR.
DATA: BEGIN OF ITAB2 OCCURS 0.
      INCLUDE STRUCTURE WA.
DATA: END OF ITAB2.
DATA: BEGIN OF ITAB_AUFK OCCURS 0,
      AUART LIKE AUFK-AUART,
      AUFNR LIKE AUFK-AUFNR,
      POSNR LIKE RESB-POSNR,
      AEDAT LIKE AUFK-AEDAT,
      AENAM LIKE AUFK-AENAM,
      WERKS LIKE AUFK-WERKS,
      PLNBEZ LIKE AFKO-PLNBEZ,
      GAMNG(7) TYPE P DECIMALS 0,
      GASMG(7) TYPE P DECIMALS 0,
      MATNR LIKE RESB-MATNR,
      BDMNG(7) TYPE P DECIMALS 0,
      BMENG(7) TYPE P DECIMALS 0,
      MENGE(7) TYPE P DECIMALS 3.
DATA: END OF ITAB_AUFK.
DATA: FDATE LIKE SY-DATUM,
      LDATE LIKE SY-DATUM.
DATA: X_AUFNR LIKE AFKO-AUFNR,
      X_MENGE(7) TYPE P DECIMALS 0,
      X_ERR(3).
DATA: W_DATASET1(500) VALUE '/usr/sap/trans/data/'.
SELECT-OPTIONS T_WERKS FOR AUFK-WERKS OBLIGATORY.
SELECT-OPTIONS T_AUFNR FOR AUFK-AUFNR.
SELECT-OPTIONS T_AEDAT FOR AUFK-AEDAT.
PARAMETERS     PDATA    LIKE W_DATASET1.
CONCATENATE W_DATASET1 PDATA INTO W_DATASET1.
PERFORM F_COLLECT_DATA.
FORM F_COLLECT_DATA.
OPEN DATASET W_DATASET1 FOR INPUT IN TEXT MODE encoding default.
DO.
     IF sy-subrc <> 0.
        EXIT.
     ENDIF.
     READ DATASET W_DATASET1 INTO WA.
     APPEND WA TO ITAB2.
ENDDO.
CLOSE DATASET W_DATASET1.
SELECT AAUFNR AAUART AAEDAT AAENAM A~WERKS
        BPLNBEZ BGAMNG B~GASMG
        CMATNR CBDMNG C~POSNR
     INTO CORRESPONDING FIELDS OF TABLE ITAB
     FROM          ( AUFK AS A
          INNER JOIN AFKO AS B ON BAUFNR = AAUFNR
          INNER JOIN RESB AS C ON CAUFNR = AAUFNR )
     WHERE A~AEDAT IN T_AEDAT
       AND A~WERKS IN T_WERKS.
     LOOP AT ITAB INTO WA.
        CLEAR MAST.
        SELECT SINGLE * FROM MAST WHERE MATNR = WA-PLNBEZ
                                    AND WERKS = WA-WERKS.
        CLEAR STKO.
        SELECT SINGLE * FROM STKO WHERE STLNR = MAST-STLNR
                                    AND STLAL = MAST-STLAL.
        CLEAR STPO.
        SELECT SINGLE * FROM STPO WHERE STLNR = MAST-STLNR
                                    AND POSNR = WA-POSNR.
        WA-BMENG = STKO-BMENG.
        WA-MENGE = STPO-MENGE.
        MODIFY ITAB FROM WA.
        AT NEW AUFNR.
           SKIP.
        ENDAT.
        LOOP AT ITAB2 WHERE AUFNR = WA-AUFNR
                        AND POSNR = WA-POSNR.
            IF ITAB2-GAMNG <> WA-GAMNG OR
               ITAB2-GASMG <> WA-GASMG OR
               ITAB2-BDMNG <> WA-BDMNG.
               CLEAR X_MENGE.
               IF ITAB2-BMENG <> 0.
                  X_MENGE = ITAB2-GAMNG / ITAB2-BMENG * ITAB2-MENGE.
               ENDIF.
               CLEAR X_ERR.
               IF ITAB2-BDMNG <> X_MENGE.
                  X_ERR = 'Err'.
               ENDIF.
               FORMAT COLOR COL_TOTAL.
               WRITE: / ITAB2-AUART UNDER 'Type',
                        ITAB2-AUFNR UNDER 'Prod Order',
                        ITAB2-AEDAT UNDER 'Last Chg Dt',
                        ITAB2-AENAM UNDER 'Last Chg by',
                        ITAB2-WERKS UNDER 'Plant',
                        ITAB2-PLNBEZ UNDER 'Material',
                   (10) ITAB2-GAMNG UNDER 'Order Qty' DECIMALS 0,
                   (10) ITAB2-GASMG UNDER 'Scrap Qty' DECIMALS 0,
                        ITAB2-POSNR UNDER 'Item',
                        ITAB2-MATNR UNDER 'Component Req',
                   (10) ITAB2-BDMNG UNDER 'Req Qty' DECIMALS 0,
                        X_MENGE      UNDER 'BOM Qty' COLOR COL_TOTAL,
                        ITAB2-BMENG UNDER 'BOM Base',
                        ITAB2-MENGE UNDER 'BOM Comp',
                        X_ERR        UNDER 'Rmks' COLOR COL_TOTAL.
               CLEAR X_MENGE.
               IF WA-BMENG <> 0.
                  X_MENGE = WA-GAMNG / WA-BMENG * WA-MENGE.
               ENDIF.
               CLEAR X_ERR.
               IF WA-BDMNG <> X_MENGE.
                  X_ERR = 'Err'.
               ENDIF.
               FORMAT COLOR OFF.
               WRITE: / WA-AUART UNDER 'Type',
                        WA-AUFNR UNDER 'Prod Order',
                        WA-AEDAT UNDER 'Last Chg Dt',
                        WA-AENAM UNDER 'Last Chg by',
                        WA-WERKS UNDER 'Plant',
                        WA-PLNBEZ UNDER 'Material',
                   (10) WA-GAMNG UNDER 'Order Qty' DECIMALS 0,
                   (10) WA-GASMG UNDER 'Scrap Qty' DECIMALS 0,
                        WA-POSNR UNDER 'Item',
                        WA-MATNR UNDER 'Component Req',
                   (10) WA-BDMNG UNDER 'Req Qty' DECIMALS 0,
                        X_MENGE   UNDER 'BOM Qty' COLOR COL_TOTAL,
                        WA-BMENG UNDER 'BOM Base',
                        WA-MENGE UNDER 'BOM Comp',
                        X_ERR     UNDER 'Rmks' COLOR COL_TOTAL.
             ENDIF.
        ENDLOOP.
     ENDLOOP.
   LOOP AT ITAB2.
        LOOP AT ITAB INTO WA WHERE AUFNR = ITAB2-AUFNR
                               AND POSNR = ITAB2-POSNR.
             DELETE ITAB2.
        ENDLOOP.
        SELECT SINGLE * FROM AUFK WHERE AUFNR = ITAB2-AUFNR.
        IF SY-SUBRC <> 0.
             DELETE ITAB2.
        ENDIF.
   ENDLOOP.
   OPEN DATASET W_DATASET1 FOR OUTPUT IN TEXT MODE encoding default.
        LOOP AT ITAB INTO WA.
           TRANSFER WA TO W_DATASET1.
        ENDLOOP.
        LOOP AT ITAB2 INTO WA.
           TRANSFER WA TO W_DATASET1.
        ENDLOOP.
   CLOSE DATASET W_DATASET1.
ENDFORM.
TOP-OF-PAGE.
    FORMAT COLOR COL_TOTAL.
    WRITE: / SY-DATUM, SY-UZEIT, SY-REPID, SY-UNAME,
         50 'Daily Qty Changed Checklist for Production Order',
        120 SY-PAGNO.
    SKIP.
    WRITE: / 'Plant ', T_WERKS-LOW.
    WRITE:   ' Last Change Date ', T_AEDAT-LOW, ' to ', T_AEDAT-HIGH.
    SKIP.
    WRITE: /1 'Type',
            6 'Prod Order',
            17 'Last Chg Dt',
            29 'Last Chg by',
            42 'Plant',
            49 'Material',
            69 'Order Qty',
            83 'Scrap Qty',
            99 'Item',
           105 'Component Req',
           121 'Req Qty',
           135 'BOM Qty',
           149 'BOM Base',
           163 'BOM Comp',
           178 'Rmks'.
     ULINE.
     WRITE: / 'Previous data :- '.
     FORMAT COLOR OFF.
     WRITE: / 'Current data :- '.
INITIALIZATION.
   LDATE = SY-DATUM.
   LDATE = LDATE - 1.
   FDATE = LDATE.
   MOVE:   FDATE         TO T_AEDAT-LOW.
   APPEND T_AEDAT.
   PDATA = 'AE001'.

CASE not found while executing CASE statement on Submit Form

Hi to all APEX users and developers.
I have several APEX applications and they are all working well, but recently I got one strange exception when I try to submit page:
Session: Fetch session header information
...metadata, fetch page info
...Validate item page affinity.
...Validate hidden_protected items.
Add error onto error stack
...Error data:
......message: Error processing request.
......additional_info: ORA-06592: CASE not found while executing CASE statement
......display_location: ON_ERROR_PAGE
......is_internal_error: true
......apex_error_code: APEX.UNHANDLED_ERROR
......ora_sqlcode: -6592
......ora_sqlerrm: ORA-06592: CASE not found while executing CASE statement
.....error_backtrace: ORA-06512: at "APEX_040100.WWV_FLOW", line 9273
......component.type: APEX_APPLICATION_AUTH
......component.id: 41350431648668800
......component.name: MNRFR
...Show Error on Error Page
......Performing rollback
Processes - point: AFTER_ERROR_HEADER
Processes - point: BEFORE_ERROR_FOOTER
End Page Processinga
Page has more than 120 items (most of them are hidden), so my first thought is that page has problem with posting so many items, but APEX error message doesn't hel me at all. Any help would be very appreciated :)
Almir

Hi Almir,
actually it is the 100 page item limit. See (http://download.oracle.com/docs/cd/E17556_01/doc/user.40/e15517/limits.htm)
I also had a look into the source code and the code at the position where the error gets raised only supports 100 page items.
Can you have a look into the generated HTML code and look if you have a page items which is mapped to p_t101 or a higher number ?
I will file a bug to show a better error message.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Short dump while executing job SM:EXEC SERVICES for EWA alert generation

Hello All,
I'm getting short dump error while executing job SM:EXEC SERVICES for EWA alert generation.I'm using EHP1@SP22 of Sol Man.
Please find the logs
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RDSVASCABAP_TRANS__________073
" in include "RDSVASIABAP_TRANS__________073 " in
line 1782:
"Field "STATEMENT_SUMMARY001019" is unknown. It is neither in one of th"
"e specified tables nor defined by a "DATA" statement. "DATA" statement"
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
If anyone came across such kind of dump, please reply asap, due to this, i could not generate EWA report for R/3 system 6.04.
Thanks,
Anand.

>
Anand Tigadikar wrote:
> Thx Paul, but i already did checked this note and its not solving my issue
Dear Anand,
Did you perform a complete service definition replacement for SDCC/SDCCN as described in the note?
These are manual steps you need to perform on the system and are not code corrections.
I would suggest you perform it, if you have not, and check the SDCCN logs to review the process ran cleanly.
Note: Please make sure SDCC_OSS is functioning and a connection to SAP can be made before
deleting the service definitions.
If you have already replaced the service defintions on the Solution Manager system, then no point doing it again. However checking a note and applying it are not the same thing. So I am uncertain if you replaced the service definitions or not. The dump you are getting in SM:EXEC SERVICES suggests its due to a problem with the service definitons. The recommendation is to replace them according to the process described in SAP Note 727998. If you have not done so please do so.
If you have successfully replaced the service definitions are you still getting the same dump, or has it possibly changed?
Regards,
Paul

Short Dump while executing New Hire (action type) in PA40

Hi All,
i am getting short dump while executing PA40 for new hire action type can anyone look into this and guide as i am new to HCM.
Category               ABAP Programming Error
Runtime Errors         SYNTAX_ERROR
ABAP Program           /1PAPAXX/HDR_21000A
Application Component Not Assigned
Date and Time          21.08.2014 14:07:03
Short text
    Syntax error in program "/1PAPAXX/HDR_21000A ".
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPFP50M" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in
    include "/1PAPAXX/HDR_21000AO01 " in
    line 52:
    ""LV_LENGTH" has already been declared"
    The include has been created and last changed by:
    Created by: "HCM04 "
    Last changed by: "HCM03 "
    Error in the ABAP Application Program
    The current ABAP program "SAPFP50M" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "/1PAPAXX/HDR_21000A ".
    You can also perform the syntax check from the ABAP Editor.
    If the problem persists, proceed as follows:
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    The following syntax error was found in the program /1PAPAXX/HDR_21000A :
    ""LV_LENGTH" has already been declared"
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
System environment
    SAP Release..... 731
    SAP Basis Level. 0007
    Application server... "dc-ds-erp"
    Network address...... "172.16.23.111"
    Operating system..... "Linux"
    Release.............. "3.0.13-0.27-default"
    Hardware type........ "x86_64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "dc-ds-erp"
    Database type..... "ORACLE"
    Database name..... "ECD"
    Database user ID.. "SAPSR3"
    Terminal.......... "NLC-HP"
    Char.set.... "C"
    SAP kernel....... 720
    created (date)... "Sep 14 2013 06:16:24"
    create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"
    Database version. "OCI_112, 11.2.0.3.0, V1, default"
    Patch level. 500
    Patch text.. " "
    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
    SAP database version. 720
    Operating system..... "Linux 2.6, Linux 3"
    Memory consumption
    Roll.... 0
    EM...... 37708200
    Heap.... 0
    Page.... 106496
    MM Used. 4666776
    MM Free. 3709976
User and Transaction
    Client.............. 210
    User................ "HCM03"
    Language key........ "E"
    Transaction......... "PA40 "
    Transaction ID...... "53EF470299AB5D67E1000000AC10176F"
    EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"
    EPP Connection ID....... 00000000000000000000000000000000
    EPP Caller Counter...... 0
    Program............. "SAPFP50M"
    Screen.............. "MP000000 1000"
    Screen Line......... 3
    Debugger Active..... "none"
Information on where terminated
    Termination occurred in the ABAP program "SAPFP50M" - in
    "GET_HEADER_WITH_TCLAS".
    The main program was "MP000000 ".
    In the source code you have the termination point in line 146
    of the (Include) program "FP50MDHD".
Source Code Extract
Line
SourceCde
116
CALL FUNCTION 'HR_HEADER_GET'
117
      EXPORTING
118
           DHDID                    = FHD_HID
119
           BEGDA                    = BEGDA
120
           TCLAS                    = TCLAS
121
* Es wird nur einer der folgenden 3 Parameter benutzt.
122
* Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.
123
* Der erste der nicht initial ist wird ausgewertet.
124
*           MOLGA                   =
125
           P0001                    = P0001
126
           PERNR                    = PSPAR-PERNR
127
      IMPORTING
128
           PROG                     = HEADER_PROG
129
           DNUM                     = HEADER_DYNNR
130
       EXCEPTIONS
131
            HEADER_DEACTIVATED          = 1
132
            HEADER_UNKNOWN              = 2
133
            HEADER_GENERATE_DEACTIVATED = 3
134
            HEADER_GENERATE_FAILED      = 4
135
            INTERNAL_ERROR              = 5
136
            OTHERS                      = 6.
137
138
IF NOT SY-SUBRC IS INITIAL.
139
* Bei Problemen gibt's eben ein leeres Dynpro.
140
    HEADER_PROG = 'SAPMP50A'.
141
    HEADER_DYNNR = '0090'.
142
ELSE. " NOT sy-subrc IS INITIAL.                                   "
143
* Dann setzen wir jetzt auch noch das Datum fest.
144
    PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.
145
* Und schalten auf Uebergabe der PERNR mit globalen Variablen.
>>>>>
    PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).
147
ENDIF. " (ELSE) NOT sy-subrc IS INITIAL.                           "
148
* Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.

Hi,
Error Log: Syntax error
""LV_LENGTH" has already been declared"
please check LV_LENGTH variable declaration.
It may be declared more once!

Runtime error while executing New Hire action in PA40

Hi All,i am getting short dump while executing PA40 for new hire action typecan anyone look into this and guide as i am new to HCMNote: getting dump only for one user id for rest all other user id i am not getting dump.
Category               ABAP Programming Error
Runtime Errors         SYNTAX_ERROR
ABAP Program           /1PAPAXX/HDR_21000A
Application Component Not Assigned
Date and Time          21.08.2014 14:07:03
Short text
    Syntax error in program "/1PAPAXX/HDR_21000A ".
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPFP50M" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in
    include "/1PAPAXX/HDR_21000AO01 " in
    line 52:
    ""LV_LENGTH" has already been declared"
    The include has been created and last changed by:
    Created by: "HCM04 "
    Last changed by: "HCM03 "
    Error in the ABAP Application Program
    The current ABAP program "SAPFP50M" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "/1PAPAXX/HDR_21000A ".
    You can also perform the syntax check from the ABAP Editor.
    If the problem persists, proceed as follows:
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    The following syntax error was found in the program /1PAPAXX/HDR_21000A :
    ""LV_LENGTH" has already been declared"
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
System environment
    SAP Release..... 731
    SAP Basis Level. 0007
    Application server... "dc-ds-erp"
    Network address...... "172.16.23.111"
    Operating system..... "Linux"
    Release.............. "3.0.13-0.27-default"
    Hardware type........ "x86_64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "dc-ds-erp"
    Database type..... "ORACLE"
    Database name..... "ECD"
    Database user ID.. "SAPSR3"
    Terminal.......... "NLC-HP"
    Char.set.... "C"
    SAP kernel....... 720
    created (date)... "Sep 14 2013 06:16:24"
    create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"
    Database version. "OCI_112, 11.2.0.3.0, V1, default"
    Patch level. 500
    Patch text.. " "
    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
    SAP database version. 720
    Operating system..... "Linux 2.6, Linux 3"
    Memory consumption
    Roll.... 0
    EM...... 37708200
    Heap.... 0
    Page.... 106496
    MM Used. 4666776
    MM Free. 3709976
User and Transaction
    Client.............. 210
    User................ "HCM03"
    Language key........ "E"
    Transaction......... "PA40 "
    Transaction ID...... "53EF470299AB5D67E1000000AC10176F"
    EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"
    EPP Connection ID....... 00000000000000000000000000000000
    EPP Caller Counter...... 0
    Program............. "SAPFP50M"
    Screen.............. "MP000000 1000"
    Screen Line......... 3
    Debugger Active..... "none"
Information on where terminated
    Termination occurred in the ABAP program "SAPFP50M" - in
    "GET_HEADER_WITH_TCLAS".
    The main program was "MP000000 ".
    In the source code you have the termination point in line 146
    of the (Include) program "FP50MDHD".
Source Code Extract
Line
SourceCde
116
CALL FUNCTION 'HR_HEADER_GET'
117
      EXPORTING
118
           DHDID                    = FHD_HID
119
           BEGDA                    = BEGDA
120
           TCLAS                    = TCLAS
121
* Es wird nur einer der folgenden 3 Parameter benutzt.
122
* Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.
123
* Der erste der nicht initial ist wird ausgewertet.
124
*           MOLGA                   =
125
           P0001                    = P0001
126
           PERNR                    = PSPAR-PERNR
127
      IMPORTING
128
           PROG                     = HEADER_PROG
129
           DNUM                     = HEADER_DYNNR
130
       EXCEPTIONS
131
            HEADER_DEACTIVATED          = 1
132
            HEADER_UNKNOWN              = 2
133
            HEADER_GENERATE_DEACTIVATED = 3
134
            HEADER_GENERATE_FAILED      = 4
135
            INTERNAL_ERROR              = 5
136
            OTHERS                      = 6.
137
138
IF NOT SY-SUBRC IS INITIAL.
139
* Bei Problemen gibt's eben ein leeres Dynpro.
140
    HEADER_PROG = 'SAPMP50A'.
141
    HEADER_DYNNR = '0090'.
142
ELSE. " NOT sy-subrc IS INITIAL.                                   "
143
* Dann setzen wir jetzt auch noch das Datum fest.
144
    PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.
145
* Und schalten auf Uebergabe der PERNR mit globalen Variablen.
>>>>>
    PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).
147
ENDIF. " (ELSE) NOT sy-subrc IS INITIAL.                           "
148
* Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.
149
* Wird mit Einfuehrung des Headerobjekts obsolet.
150
PERFORM REMEMBER_HEADER "                             "XYVPH4K015649
151
    USING HEADER_PROG HEADER_DYNNR 'S'. "               "XYVPH4K015649
152
ENDFORM.
153
154
*       FORM RE588I                                                   *
155
156
157
158
* --> T588I_DHDID                                                   *
159
* --> T588I_MOLGA                                                   *
160
* --> T588I_TCLAS

Implement SAP Note 1004280.. your issue if fixed
If your issue is resolved request you to close the thread or else free feel to touch base
BR
Anil

Error while executing the compilation process

Hi,
ISA Framework: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: javac: invalid flag: "/usr/sap/CJP/J06/j2ee/cluster/server2/apps/sap.com/crm~isauseradm/servlet_jsp/isauseradm/work/jsp_login XXXXXXXXXXX.java" Usage: javac <options> <source files> where possible options include: -g Generate all debugging info -g:none Generate no debugging info -g:{lines,vars,source} Generate only some debugging info -nowarn Generate no warnings -verbose Output messages about what the compiler is doing -deprecation Output source locations where deprecated APIs are used -classpath <path> Specify where to find user class files -sourcepath <path> Specify where to find input source files -bootclasspath <path> Override location of bootstrap class files -extdirs <dirs> Override location of installed extensions -d <directory> Specify where to place generated class files -encoding <encoding> Specify character encoding used by source files -source <release> Provide source compatibility with specified release -target <release> Generate class files for specific VM version -help Print a synopsis of standard options ].
We get this message periodically then we login to isauseradm-application or shopadmin-application.
How we can solve this issue? Why it's appears in system?
/nwa shows this error:
Process after commit failed - may be hanging internal locks mut be removed manually.
Where I can see hanging internal locks ?
Denis

to add some information,
in runtime workbench, component monitoring, performance monitoring and all other thing except message monitoring is OK.

2499 error while executing a Oracle PL/SQL query

Hi,
Im a newbie, using Oracle 10g enterprise edition, netbeans 6.5. Im unable to execute a SELECT query which contains multiple JOINS & UNIONS(lengthening upto 3800 chars) through code hence It flashes SP2-0027: Input is too long (> 2499 characters) - line ignored.
Earlier i had same problem while executing the query on the web interfaced query browser(isqlplus), sqlplus prompt.
Later on i found a Solution for such queries which are lengthening more than 2499 chars is either to break the query into multiple lines by pressing enter manually or to use M$ Word application (paste the query in a file and save it as a plain text filetype with insert line breaks option checked).
But what about the coding part now?
Please guide me through this.
Regards,
Peter

On sqlplus Oracle can't process lines over 2500 (cero is included on the counting) that's the reason why the error is displayed. To sort out this problem divide your query string into parts smaller than 2500 (2000 is recomended) and just add the next line between them:
CHR(10) || CHR(13)
Since this is gonna be read by the Oracle's engine and embedded into your query line, it will understand that every pair of CHR(10) || CHR(13) is a carriage return command and will drain the buffer processing every line with not errors.
Hope this helps
Edited by: MiloHega on Jan 27, 2009 1:00 PM

Receiving SQL Error: INTERNAL_ERROR while executing the query

Dear All,
I am receiving the below error while executing a query.
SQL Error: INTERNAL_ERROR
Diagnosis
The database system registered an SQL error. As available, the error number and a description are included in the short text. Possible causes for SQL errors include:
Overflow of database objects such as buffers, temporary tablespaces, rollback segments or data containers/tablespaces.
->These problems can generally be eliminated by system administrators.
Missing generated database objects such as tables or views based on inconsistent or inactive InfoCubes or InfoObjects. Examples of this include the view of the fact table for an InfoCube or the attribute SID table (X/Y table) of a characteristic.
-> These problems can generally be eliminated by a BW administrator.
SQL requests with incorrect content.
-> Problems of this type are generally programming errors.
System Response
Procedure
Contact your system administrator.
Procedure for System Administration
If there is no error description, look for one in the reference from the database producer.
Decide on the correct category for the SQL error and check if it can be eliminated. Generally the error can also be found in the syslog (transaction sm21). From there, transactions sm51 and sm50, the developer's trace log of the work process can be determined and the erroneous statement can be viewed in the log. This procedure is described in SAP Note 568768.
Notification Number DBMAN 257
I verified the table spaces and also done RSRV Repair of InfoObjects and InfoCubes and didnt find any error. But I am receiving this error for one particular month and remaining months are executing fine. Any ideas why i am receiving this error.
Regards
Ravi Y

OSS Note 1305568:
Symptom
A data mart query that
you want to execute within a data transfer process (DTP), for example, terminates with the
SQL error -1013 "Too many order columns".
The following is displayed in the monitor log of the data transfer process:
Error while extracting from source xxxxxx (type InfoProvider)
Message number RSBK 242
Exception CX_SQL_EXCEPTION occurred (program:
CL_SQL_STATEMENT==============CP, include:
CL_SQL_STATEMENT==============CM004, line: 32).
Message number RS_EXCEPTION 000
SQL error: POS(3306) Too many order columns
Message number DBMAN 257
Error reading the data of InfoProvider xxxxxx
Message number DBMAN 305
You have already implemented Note 1065380.
Other terms
CX_SQL_EXCEPTION, message number, RS_EXCEPTION 000, DBMAN 257, RSBK 242,
RS_EXCEPTION 000
Reason and Prerequisites
The MaxDB internal limit of 4016 bytes or 128 fields for GROUP BY columns was exceeded.
Solution
When you implement these corrections, no aggregation is performed for the data (GROUP BY) if the limits of the MaxDB database have been exceeded.
The limit values for the aggregation bahavior can also be manually reduced if there are problems with the default values.
Two RSADMIN parameters are provided for this.
MAXDB_MAX_GROUP_BY_FLDS is the maximum number of GROUP BY fields. The default value is 128.
MAXDB_MAX_GROUP_BY_LEN is the maximum total length of the GROUP BY fields. The default value is 4000.
SAP NetWeaver BI 7.00
Import Support Package 21 for SAP NetWeaver BI 7. 00 (SAPKW70021) into your BI system. The Support Package is available when Note 1270629"SAPBINews NW 7.00 BI Support Package 21", which describes this Support Package in more detail, is released for customers.

Error while executing the query

Hi all,
I am facing two errors while executing my query namely
1)The validity interval has initial value as lower limit.
2)Diagnosis
Query uses non-cumulative key figures. It requires calculation for non-cumulative values for more than 2000 periods in time. The most common reason for this is that the non-cumulative InfoCube has a very large validity interval and the query has no time restrictions. With exception aggregation AVERAGE (AV1 or AV2) in particular, this lack of time restriction would result in considerable memory and performance problems.
System Response
Query cannot be executed in this way.
Please suggest a possible reason for these errors.
Thanks and Regards.
Mudit Khanna

Hi,
See
Refer Notes 496638,571364
210432
528202
1318741
208546
and also see simila thread
Problem getting data from BF cube in report (Non cummulative keyfigures)
Thanks
Reddy

Error while executing the payroll through transaction code PC00_M40_CALC

Dear Sir/ Madam,
While executing the payroll through the transaction code PC00_M40_CALC , i am getting the error as mentioned below :
"Division by zero not performed "
Calculation rule X0133****5 RTE = ISDIVP DIVID ARR ZERO=A ADD
I am not able to resolve this error. So request to guide me on this.
Thanks & regards,
vijaya.s.c.
Moderator message: wrong forum, please have a look in the (I guess) ERP HCM forums.
Edited by: Thomas Zloch on Jan 24, 2012

Hi,
Maintain have you changed any x013 rule?
If not, just maintain attendance/time events then process the payroll.

JRE performances while executing small components

Similar Messages

Maybe you are looking for