T510 entry not present on particular date

Hi all,
I have created paysacle type , pay Scale Are , Pay Scale Group and it level and has assigned it in PA30 for infotype 0008 along with the country grouping .
But i am getting an error saying ' No table Entry inTable T510 for the Key county grouping Pay Scale Type PayScale Area Pay Scale Grouping and Level on particular date.
When i looked at T510 entry , I can see those Records .
Can you please suggest what i am missing here .
Thanks in Advance,
Regards,
Ry

Hi,
Maintain the T510 table with wage type and along with amounts.
Like
Grouping PS group level wage type    start    end       amount      cur
3                 TOP     1       1011                               10,000         inr
In this way maintain the grouping and values. after matain the IT0008. If it is coming same error directly maintain the amounts for that each wage types. That's good.
Good luck
Devi

Similar Messages

  • SAP workload monitor is not showing for particular date in Total Option

    Hi,
    In t. code ST03N (Work Load Monitor) data is not showing in option total for particular date but it is showing in all the instances.
    Please support
    Regards
    Ganesh Tiwari

    Hi Mamtha
    Does the same navigation work directly in the backedn? In RSRT?
    Pls try that, will halp narrow down your problem. WHether it is a data issue, whetehr it is a BW issue or whether it is a display issue.
    Regards
    Rajesh

  • Reboot and select proper Boot Device on Satellite C55-B5200, odd not present

    I have a new laptop barley used. I bought this back in August then bam in January it started giving me this error message "Reboot and select proper Boot Device".
    I'd like to get this fixed so I can start using it again. I tried pressing f2 on restart and when it powers up it says
    CPU/SSD: HGST HTS545050A7E380
    ODD: NOT PRESENT
    SYSTEM DATE: 1/16/2015
    on Satellite C55-B5200, odd not present
    Is there something specific I should do to get this running again?

     it started giving me this error message "Reboot and select proper Boot Device".
    It is not finding or communicating with the hard drive to boot, most of the time it is a bad hard drive or bios is not set correctly for the operating system.
    f2 to enter the bios then f9 to set bios to the defaults, then f10 to save - then try to start.
    What you are saying the bios reads is wierd?
    CPU/SSD: HGST HTS545050A7E380 -- that is the hard drive: HGST Travelstar Z5K500 HTS545050A7E380 (0J11285) 500GB 5400 RPM 8MB Cache SATA 3.0Gb/s 2.5" Internal Notebook Hard Drive.
    ODD: NOT PRESENT - ?
    SYSTEM DATE: 1/16/2015
    on Satellite C55-B5200, odd not present - ?
    Your support page is here - http://support.toshiba.com/support/modelHome?freeText=1200008272
    S70-ABT2N22 Windows 7 Pro & 8.1Pro, C55-A5180 Windows 8.1****Click on White “Kudos” STAR to say thanks!****

  • Master data not present in the reporting cube

    Dear Experts,
    There is a scenario in report design for me.
    I have already created the Bex report and all the fields as mentioned are in the  sales report.
    Client now wants to include two more fields in the report.
    One is the keyfig  " Net value" which is present in the sales cube  and i have already included in the report
    and another field which is master data  0profit_center  is not present in the cube.
    Any ideas how can i include this  0profit center  data  so that i can display in the report?
    As far as i understand, I need to include this master data in the sales  Infocube which is being used for reporting.
    But i am pondering  upon the impact on the system because of this.
    Now i have checked the BI system and the ECC table. In VBRP table of ECC,  the profit center is present.
    But when i see in BI the profit center is not being loaded  from ECC but from flat file source system.
    So i am confused how to go forward.
    Can anyone suggest me  what should be my approach?
    Best Regards!!

    You didn't understand what we suggested.
    Rather than checking 0profit_ctr master data, you need to find the info objects(which are part of your cube) which have master data. in those 0profit_ctr can be a attribute. if yes then navigation settings will work.
    if not then you can add 0profit_ctr to info cube and user master data look up thru routine or option read from master data(bw 7.3).
    Other wise, directly add 0profit_ctr to your flat file data source(and cube) and maintain data thru flat file.
    To look up your cube and 0pfirt_ctr need to have relations with another info objects other wise not possible.

  • Adding new attribute to Master data - Not present in ECC

    Hi,
    We want to add a new field in the master data object 0plant. the new field is not present in the R/3 side. So we are planning to maintain it manually.
    Is it feasible? Can someone explain how to approach the situation?
    Since it is not going to come in Process chain or any of the mappings below InfoObject will the process chains work properly?
    Regards

    Hi
    if you cant impliment any logic you cam maintani it mannually.
    First add attribute to master data object and activate.
    Do master data load if required.
    Then right click on materdata addtribute and manage -> content tab -> Content
    display complete data and you can maintain attribute values individually for all ercords one by one (will be pain even for 100 records).
    another alternative is of doing file upload for this attribute.
    Regards
    Sudeep

  • Alert data is not present in SCOM 2012 Data Warehouse database since two weeks

    Alert data is not present in SCOM 2012 Data Warehouse database since a week though I could see Performance data for the latest dates. Old Alert data is present but I think the latest Alert data is not being inserted to Data warehouse. No activity was done
    on the day from where we are missing data.
    I could see 31554 events on all my Management servers and this proves that Data Insertion is happening. I am not sure why only Alert data is missing (or not getting inserted) in DW database. I am trying to use SQL queries to fetch the data as I dont have reporting
    currently. The same query is working for other dates, so there is no issue with this query.
    I have noticed that I could see the Alert Data present in SCOM OperationsmNager Db but NOT present in OperationsManagerDW database.
    In SCOM 2007, data will be inserted in both Ops DB and DW simultaneously. I believe the same methodology in 2012 too.
    Please help me to fetch Alert data from DW. Any suggestion pls?
    Regards, Suresh

    Hi,
    Generally, data warehouse store a long-term data, and by default, it would keep 400 days data, I suggest check your configuration:
    How to Configure Grooming Settings for the Reporting Data Warehouse Database
    http://technet.microsoft.com/en-us/library/hh212806.aspx
    Alex Zhao
    TechNet Community Support

  • ODS not picking one particular master data record

    Hi All,
    Problem is when we run a query on ODS,it is not displaying the one particular data records.Then we check the ods that particular record values are not available,but it is in master data tables.
    My question is what will be the reason for this.we are using Generic extraction.
    thanks

    Hi,
    Check for primary keys of master data tables and key fields of ODS . I think there should be mismatch which is why some records are getting overwritten.
    Also in the ods request check number of records transfered and number of records added.
    ODS key fields should be exactly same as Primary key of master data table otherwise there are chances of loosing data.
    Hope that helps.
    Regards
    Mr Kapadia
    Assigning points is the way to say thanks in SDN.

  • Entries in T510 are not getting defaulted in IT0008

    Hi Experts,
    Entries maintined in T510  are not getting defaulted in IT0008.
    According to the wagetype model  (LGMST - Feature ) the wage types are defaulting accurately  but the amount is coming blank.
    Please advice.
    Regards,
    IFF

    V_T511 - Wage Type Characteristics maintian the indirect valuation model. Select the module variant as per ur req.
    V_T539A - Default Wage Types for Basic Pay
    LGMST - Feature
    V_T539J - Base Wage Type Valuation
    V_T7INA1 - Pay scale grouping for allowances
    V_T7INA3 - Associating pay parameters to pay scale grouping
    V_T7INB1 - Basic Wages
    V_T7INA5 - Wage type model for pay scale grouping for allowances
    V_T7INA9 - Reimbursement allowances perks - eligibility and calculation

  • Pegging areas are not creating eventhough entries are present.

    While running the program /SAPAPO/SAPRRP_NETCH in the background, we are getting "0 pegging areas were generated".
    But when we check in the same variant we could see many entries.
    This is affecting our system so much.
    Urgent help is appreciated.

    Dear krish,
    recently our customer came across similar issue.
    It has happened if for that product-location combination already entry present in the /SAPAPO/PEGKEY table, then it is not possible to generate the pegging area.
    Could you please confirm once, if the entry already present in the //PEGKEY table.
    BR,
    Thushitha.

  • Restore from time machine does not list all my backups.  I know they exist but there dates are not present on the restore list.  Any help appreciated.

    Restore from time machine does not list all my backups.  I know they exist but their dates are not present on the restore list.  Any help appreciated.  If I must use one of these older dates to restore, how do I then get the more current data off time machine?

    Ok, so am i correct in saying that the steps to fix are as follows.
    That's one option, but not what I meant by restoring in the time-travel view. The latter is what you get when you enter Time Machine.
    is the fresh install not going to be able to "see" the time machine backups that I have at the moment.
    It should, but sometimes people report that it fails. I'm not sure why that happens.

  • Functional Specification For Opening And closing stock On Particular Date

    Dear Gurus,
    I am creating report for opening and closing stock on particular date in which batch and storage location should also be included. I want to know the tables and fields for the same.I have searched the forum and got report on month basis but I want this report on posting day basis.kindly suggest tables and fields. Thanks in Advance

    Dear sir,
    There are many other colums that client wants to add which are not present in MB5B transaction.columns which client wants to add are as follows...
    Material Number                                                   
    Material Description                                       
    Material Type                                                                        
    Material Group                                                                     
    External material Group                                                            
    Movement Type     
    Plant     
    Storage Location     
    Customer Number     
    Customer Name     
    Vendor Number     
    Vendor Name     
    Posting Date     Receipt Doc. Number
    Issue Doc. Number     
    Reference Issue Document Number     
    Opening Stock Quanity     
    Material Receipt Quantity     
    Material Issue Quantity     
    Material Closing Stock Quantity      
    Value Of Closing Stock
    And for this I want  tables and logic for the same. kindly provide the solution for the same.

  • Closing stock of a particular date

    how to get plant wise material closing stock on any particular date. say previous months end date. I am calculating that from MSEG table with the help of MSEGINSMK and MSEGSHKZG field. (with date filtaration by joining MBLNR of MKPF table) But stock is showing different with the closing stock showing in MB5B report for that date. I don't know which BWART of MSEG table to be excluded. My email id is [email protected]

    Hi,
    This is a stock aging report, you can use this for reference.
    Logic: Based on current stock and value from MBEW table. The latest receipt dates were taken till the qty tallies off.Rejections and reversals are considered.
    The movement types considered are ('101','102','105','106','122','123','131','132','301','302','309','310','501','502','531','532','561','562','701','702').
    *& Report  ZMM03_TRY                                                 *
    REPORT  ZMM03 LINE-SIZE 226
                   LINE-COUNT 35(2)
                    NO STANDARD PAGE HEADING..
    TABLES : S032,  "Current Stock And Grouping Terms
             MBEW,  "Material Valuation
             T023T, "Material Group Desc.
             MAKT,  "Material Description
             EKPO.  "Purchasing Document Item.
    DATA : BEGIN OF T_HEADER OCCURS 0,
           MTART LIKE MARA-MTART,
           MATNR LIKE MBEW-MATNR,
           BWKEY LIKE MBEW-BWKEY,
           MATKL LIKE MARA-MATKL,
           MAKTX LIKE MAKT-MAKTX,
           MEINS LIKE MARA-MEINS,
           LBKUM LIKE MBEW-LBKUM,
           SALK3 LIKE MBEW-SALK3,
           VERPR LIKE MBEW-VERPR,
           CLSTK LIKE MBEW-LBKUM,
           CLVAL LIKE CKMLCR-SALK3,
           UNIT LIKE CKMLCR-PVPRS,
           END OF T_HEADER.
    DATA : BEGIN OF T_MSEG OCCURS 0,
           MATNR LIKE MSEG-MATNR,
           WERKS LIKE MSEG-WERKS,
           BUDAT LIKE MKPF-BUDAT,
           MBLNR LIKE MKPF-MBLNR,
           MJAHR LIKE MKPF-MJAHR,
           ZEILE LIKE MSEG-ZEILE,
           LFBNR LIKE MSEG-LFBNR,
           LFBJA LIKE MSEG-LFBJA,
           LFPOS LIKE MSEG-LFPOS,
           BWART LIKE MSEG-BWART,
           MENGE LIKE MSEG-MENGE,
           EBELN LIKE MSEG-EBELN,
           EBELP LIKE MSEG-EBELP,
           XAUTO LIKE MSEG-XAUTO,
           UMMAT LIKE MSEG-UMMAT,
           UMWRK LIKE MSEG-UMWRK,
           MARK(1),
           END OF T_MSEG.
    TYPE-POOLS : SLIS.
    DATA : L_STOCK TYPE MSEG-MENGE.
    DATA : WA_MSEG LIKE T_MSEG.
    DATA : WA_MSEG1 LIKE T_MSEG.
    DATA : T_ITEMS LIKE T_MSEG OCCURS 0 WITH HEADER LINE.
    DATA : T_CUR_STOCK LIKE T_MSEG OCCURS 0 WITH HEADER LINE.
    DATA : L_LBKUM TYPE MBEW-LBKUM.
    DATA : BEGIN OF T_OUTPUT OCCURS 0,
             WERKS LIKE MSEG-WERKS,
             MATNR LIKE MSEG-MATNR,
             BUDAT LIKE MKPF-BUDAT,
             MENGE LIKE MSEG-MENGE,
             PDAYS TYPE I,
             PVAL  TYPE MSEG-MENGE,
             MAKTX LIKE MAKT-MAKTX,
             CQTY  LIKE MSEG-MENGE,
             CPRC  LIKE MBEW-SALK3,
           END OF T_OUTPUT.
    DATA: GRID_TAB TYPE SLIS_T_FIELDCAT_ALV  WITH HEADER LINE.
    DATA : T_SORT TYPE SLIS_T_SORTINFO_ALV,
           WA_SORT TYPE SLIS_SORTINFO_ALV.
    *AT SELECTION-SCREEN.
    SELECTION-SCREEN BEGIN OF BLOCK 1 WITH FRAME TITLE TEXT-014.
    SELECTION-SCREEN SKIP 1.
    PARAMETERS : P_DATE LIKE S032-LETZTABG OBLIGATORY DEFAULT SY-DATUM.
    SELECTION-SCREEN SKIP 1.
    SELECTION-SCREEN END OF BLOCK 1.
    SELECTION-SCREEN BEGIN OF BLOCK 2 WITH FRAME TITLE TEXT-015.
    PARAMETERS     : P_WERKS    TYPE S032-WERKS OBLIGATORY.
    SELECT-OPTIONS : S_LGORT    FOR S032-LGORT,
                     S_MATNR    FOR S032-MATNR.
    SELECTION-SCREEN END OF BLOCK 2.
    SELECTION-SCREEN BEGIN OF BLOCK 3 WITH FRAME TITLE TEXT-016.
    SELECT-OPTIONS : S_MTART    FOR S032-MTART,
                     S_MATKL    FOR S032-MATKL.
    SELECTION-SCREEN END OF BLOCK 3.
    IF  P_DATE IS INITIAL AND
        P_WERKS IS INITIAL AND
        S_LGORT IS INITIAL AND
        S_MATNR IS INITIAL AND
        S_MTART IS INITIAL AND
        S_MATKL  IS INITIAL.
      MESSAGE I398(00) WITH 'Enter Selection Critirea'(019).
      SY-SUBRC = '1'.
    ELSE.
      SELECT AMATNR ABWKEY BMATKL BMTART CMAKTX BMEINS A~LBKUM
             A~SALK3
           INTO CORRESPONDING FIELDS OF TABLE T_HEADER
           FROM MBEW AS A INNER JOIN MARA AS B ON AMATNR = BMATNR
                          INNER JOIN MAKT AS C ON AMATNR = CMATNR
                                            WHERE A~MATNR IN S_MATNR
                                              AND A~BWKEY EQ P_WERKS
                                              AND MATKL IN S_MATKL
                                              AND MTART IN S_MTART
                                              AND BWTAR EQ ' '
                                              AND C~SPRAS = SY-LANGU.
      IF SY-SUBRC EQ 0.
        SELECT ABUDAT AMBLNR AMJAHR BZEILE BMATNR BWERKS B~BWART
               BMENGE BLFBNR BLFBJA BLFPOS BEBELN BEBELP B~XAUTO
               BUMMAT BUMWRK
            INTO CORRESPONDING FIELDS OF TABLE T_MSEG
            FROM MKPF AS A INNER JOIN MSEG AS B ON AMBLNR = BMBLNR
                                               AND AMJAHR = BMJAHR
             FOR ALL ENTRIES IN T_HEADER
                                             WHERE A~BUDAT <= P_DATE
                                               AND B~MATNR = T_HEADER-MATNR
                                               AND B~WERKS = T_HEADER-BWKEY
                                               AND B~BWART IN ('101',
                                                               '102',
                                                               '105',
                                                               '106',
                                                               '122',
                                                               '123',
                                                               '301',
                                                               '302',
                                                               '701',
                                                               '702',
                                                               '131',
                                                               '132',
                                                               '309',
                                                               '310',
                                                               '501',
                                                               '502',
                                                               '531',
                                                               '532',
                                                               '561',
                                                               '562').
        PERFORM GET_DEAD_STOCK.
        PERFORM DISPLAY_OUTPUT.
      ELSE.
        MESSAGE S398(00) WITH 'No Data found for'(013)
        'Given Selection Critirea'(017).
        LEAVE LIST-PROCESSING.
      ENDIF.
    ENDIF.
    *&      Form  get_dead_stock
          text
    FORM GET_DEAD_STOCK .
      LOOP AT T_HEADER.
        SORT T_MSEG BY MATNR WERKS BUDAT DESCENDING MBLNR DESCENDING.
        LOOP AT T_MSEG WHERE MATNR = T_HEADER-MATNR
                         AND WERKS = T_HEADER-BWKEY
                         AND ( BWART = '101' OR
                               BWART = '105' OR
                               BWART = '501' OR
                               BWART = '531' OR
                               BWART = '561' OR
                               BWART = '701' OR
                               BWART = '309' OR
                               BWART = '301' OR
                               BWART = '131' ).
          IF T_MSEG-BWART = 101.
            READ TABLE T_MSEG WITH KEY LFBNR = T_MSEG-MBLNR
                                       LFBJA = T_MSEG-MJAHR
                                       LFPOS = T_MSEG-ZEILE
                                       BWART = 102.
            IF SY-SUBRC = 0.
              T_MSEG-MARK = 'X'.
              MODIFY T_MSEG.
              CONTINUE.
            ENDIF.
            READ TABLE T_MSEG INTO WA_MSEG WITH KEY LFBNR = T_MSEG-MBLNR
                                       LFBJA = T_MSEG-MJAHR
                                       LFPOS = T_MSEG-ZEILE
                                       BWART = 122.
            IF SY-SUBRC = 0.
              READ TABLE T_MSEG INTO WA_MSEG1 WITH KEY LFBNR = WA_MSEG-MBLNR
                                         LFBJA = WA_MSEG-MJAHR
                                         LFPOS = WA_MSEG-ZEILE
                                         BWART = 123.
              IF SY-SUBRC EQ 0.
                WA_MSEG-MARK = 'X'.
                MODIFY T_MSEG FROM WA_MSEG.
                CONTINUE.
              ELSE.
                IF T_MSEG-MENGE EQ WA_MSEG-MENGE.
                  T_MSEG-MARK = 'X'.
                  MODIFY T_MSEG.
                  CONTINUE.
                ELSE.
                  T_MSEG-MENGE = T_MSEG-MENGE - WA_MSEG-MENGE.
                  MODIFY T_MSEG.
                ENDIF.
              ENDIF.
            ENDIF.
          ELSEIF T_MSEG-BWART = 105.
            READ TABLE T_MSEG INTO WA_MSEG WITH KEY LFBNR = T_MSEG-MBLNR
                                       LFBJA = T_MSEG-MJAHR
                                       LFPOS = T_MSEG-ZEILE
                                       BWART = 106.
            IF SY-SUBRC = 0.
              T_MSEG-MARK = 'X'.
              MODIFY T_MSEG.
              CONTINUE.
            ENDIF.
          ELSEIF T_MSEG-BWART = 131.
            READ TABLE T_MSEG INTO WA_MSEG WITH KEY LFBNR = T_MSEG-MBLNR
                                       LFBJA = T_MSEG-MJAHR
                                       LFPOS = T_MSEG-ZEILE
                                       BWART = 132.
            IF SY-SUBRC = 0.
              T_MSEG-MARK = 'X'.
              MODIFY T_MSEG.
              CONTINUE.
            ENDIF.
          ELSEIF T_MSEG-BWART = 501.
            READ TABLE T_MSEG WITH KEY LFBNR = T_MSEG-MBLNR
                                       LFBJA = T_MSEG-MJAHR
                                       LFPOS = T_MSEG-ZEILE
                                       BWART = 502.
            IF SY-SUBRC = 0.
              T_MSEG-MARK = 'X'.
              MODIFY T_MSEG.
              CONTINUE.
            ENDIF.
          ELSEIF T_MSEG-BWART = 301.
            READ TABLE T_MSEG WITH KEY LFBNR = T_MSEG-MBLNR
                                       LFBJA = T_MSEG-MJAHR
                                       LFPOS = T_MSEG-ZEILE
                                       BWART = 302.
            IF SY-SUBRC = 0.
              T_MSEG-MARK = 'X'.
              MODIFY T_MSEG.
              CONTINUE.
            ENDIF.
          ELSEIF T_MSEG-BWART = 531.
            READ TABLE T_MSEG WITH KEY LFBNR = T_MSEG-MBLNR
                                       LFBJA = T_MSEG-MJAHR
                                       LFPOS = T_MSEG-ZEILE
                                       BWART = 532.
            IF SY-SUBRC = 0.
              T_MSEG-MARK = 'X'.
              MODIFY T_MSEG.
              CONTINUE.
            ENDIF.
          ELSEIF T_MSEG-BWART = 561.
            READ TABLE T_MSEG WITH KEY LFBNR = T_MSEG-MBLNR
                                       LFBJA = T_MSEG-MJAHR
                                       LFPOS = T_MSEG-ZEILE
                                       BWART = 562.
            IF SY-SUBRC = 0.
              T_MSEG-MARK = 'X'.
              MODIFY T_MSEG.
              CONTINUE.
            ENDIF.
          ELSEIF T_MSEG-BWART = 701.
            READ TABLE T_MSEG WITH KEY LFBNR = T_MSEG-MBLNR
                                       LFBJA = T_MSEG-MJAHR
                                       LFPOS = T_MSEG-ZEILE
                                       BWART = 702.
            IF SY-SUBRC = 0.
              T_MSEG-MARK = 'X'.
              MODIFY T_MSEG.
              CONTINUE.
            ENDIF.
          ELSEIF T_MSEG-BWART = 309.
            READ TABLE T_MSEG WITH KEY LFBNR = T_MSEG-MBLNR
                                       LFBJA = T_MSEG-MJAHR
                                       LFPOS = T_MSEG-ZEILE
                                       BWART = 310.
            IF SY-SUBRC = 0.
              T_MSEG-MARK = 'X'.
              MODIFY T_MSEG.
              CONTINUE.
            ELSEIF T_MSEG-XAUTO = ' '.
              T_MSEG-MARK = 'X'.
              MODIFY T_MSEG.
              CONTINUE.
            ELSEIF T_MSEG-MATNR EQ T_MSEG-UMMAT.
              T_MSEG-MARK = 'X'.
              MODIFY T_MSEG.
              CONTINUE.
            ENDIF.
          ENDIF.
          SELECT SINGLE EBELN INTO EKPO-EBELN FROM EKPO
                             WHERE EBELN = T_MSEG-EBELN
                               AND EBELP = T_MSEG-EBELP
                               AND KNTTP = 'K'.
          IF SY-SUBRC = 0.
            T_MSEG-MARK = 'X'.
            MODIFY T_MSEG.
            CONTINUE.
          ENDIF.
         TMENGE = TMENGE - t_mseg-MENGE.
        ENDLOOP.
      ENDLOOP.
      DELETE T_MSEG WHERE MARK = 'X'.
      DELETE T_MSEG WHERE ( BWART = '102' OR
                            BWART = '106' OR
                            BWART = '502' OR
                            BWART = '532' OR
                            BWART = '562' OR
                            BWART = '702' OR
                            BWART = '310' OR
                            BWART = '302' OR
                            BWART = '123' OR
                            BWART = '122' OR
                            BWART = '132' ).
      SORT T_HEADER BY MATNR BWKEY.
      DELETE ADJACENT DUPLICATES FROM T_HEADER COMPARING MATNR BWKEY.
      T_CUR_STOCK[] = T_MSEG[].
      SORT T_CUR_STOCK BY MATNR WERKS.
      LOOP AT T_CUR_STOCK.
        WA_MSEG = T_CUR_STOCK.
        AT END OF WERKS.
        ENDAT.
      ENDLOOP.
      LOOP AT T_HEADER.
        CLEAR L_LBKUM.
        L_LBKUM = T_HEADER-LBKUM.
        REFRESH T_ITEMS.
        CLEAR T_ITEMS.
        LOOP AT T_MSEG WHERE MATNR EQ T_HEADER-MATNR
                         AND WERKS EQ T_HEADER-BWKEY.
          T_ITEMS = T_MSEG.
          APPEND T_ITEMS.
          CLEAR T_ITEMS.
        ENDLOOP.
        SORT T_ITEMS BY BUDAT DESCENDING
                        MBLNR DESCENDING.
        CLEAR L_LBKUM.
        LOOP AT T_ITEMS.
          L_LBKUM = T_ITEMS-MENGE - T_HEADER-LBKUM.
          IF L_LBKUM GE 0.
            T_OUTPUT-MATNR = T_HEADER-MATNR.
            T_OUTPUT-WERKS = T_HEADER-BWKEY.
            T_OUTPUT-BUDAT = T_ITEMS-BUDAT.
            T_OUTPUT-MENGE = T_HEADER-LBKUM.
            APPEND T_OUTPUT.
            CLEAR T_OUTPUT.
            EXIT.
          ELSE.
            T_HEADER-LBKUM = T_HEADER-LBKUM - T_ITEMS-MENGE.
            T_OUTPUT-MATNR = T_HEADER-MATNR.
            T_OUTPUT-WERKS = T_HEADER-BWKEY.
            T_OUTPUT-BUDAT = T_ITEMS-BUDAT.
            T_OUTPUT-MENGE = T_ITEMS-MENGE.
            APPEND T_OUTPUT.
            CLEAR T_OUTPUT.
            CONTINUE.
          ENDIF.
        ENDLOOP.
      ENDLOOP.
    ENDFORM.                    " get_dead_stock
    *&      Form  DISPLAY_OUTPUT
          text
    FORM DISPLAY_OUTPUT .
      DATA: L_DAYS TYPE I.
      DATA : WA_OUTPUT LIKE T_OUTPUT.
      DATA : T_FINAL LIKE T_OUTPUT OCCURS 0 WITH HEADER LINE.
      DATA : WA_FINAL LIKE T_OUTPUT.
      DATA : L_CQTY TYPE MSEG-MENGE,
             L_CPRC TYPE MBEW-SALK3.
      DATA : L_TITLE TYPE LVC_TITLE.
      DATA : L_NAME1 TYPE T001W-NAME1.
    *C-- Not to output when the quantity is zero.
      DELETE T_OUTPUT WHERE MENGE EQ 0.
      SORT T_OUTPUT BY WERKS MATNR BUDAT.
      LOOP AT T_OUTPUT.
        T_FINAL = T_OUTPUT.
        AT NEW MATNR.
          CLEAR T_HEADER.
          READ TABLE T_HEADER WITH KEY MATNR = T_OUTPUT-MATNR
                                       BWKEY = T_OUTPUT-WERKS.
        ENDAT.
        T_FINAL-MAKTX = T_HEADER-MAKTX.
        IF T_HEADER-LBKUM GT 0.
          T_FINAL-PVAL = ( T_OUTPUT-MENGE * T_HEADER-SALK3 / T_HEADER-LBKUM ).
        ELSE.
          CLEAR T_FINAL-PVAL.
        ENDIF.
        L_CQTY = L_CQTY + T_OUTPUT-MENGE.
        IF T_HEADER-LBKUM GT 0.
          L_CPRC = L_CPRC + ( T_OUTPUT-MENGE * T_HEADER-SALK3 / T_HEADER-LBKUM ).
        ENDIF.
        CALL FUNCTION 'HR_SGPBS_YRS_MTHS_DAYS'
          EXPORTING
            BEG_DA        = T_OUTPUT-BUDAT
            END_DA        = P_DATE
          IMPORTING
            NO_CAL_DAY    = L_DAYS
          EXCEPTIONS
            DATEINT_ERROR = 1
            OTHERS        = 2.
        IF SY-SUBRC <> 0.
          WRITE : 70 'Error While Calculating days'(018) .
        ELSE.
          T_FINAL-PDAYS = L_DAYS.
        ENDIF.
        T_FINAL-CQTY = L_CQTY.
        T_FINAL-CPRC = L_CPRC.
        APPEND T_FINAL.
        AT END OF MATNR.
          CLEAR : L_CPRC, L_CQTY.
        ENDAT.
      ENDLOOP.
      PERFORM BUILD_FIELD_CATALOG.
      WA_SORT-FIELDNAME = 'MATNR'.
      WA_SORT-SPOS = '1'.
      APPEND WA_SORT TO T_SORT.
      SELECT SINGLE NAME1 FROM T001W INTO L_NAME1
      WHERE WERKS = P_WERKS.
      CONCATENATE 'Plant: ' P_WERKS ',' L_NAME1 INTO L_TITLE.
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
          I_CALLBACK_PROGRAM = SY-CPROG
          I_GRID_TITLE       = L_TITLE
          IT_FIELDCAT        = GRID_TAB[]
          IT_SORT            = T_SORT
          I_SAVE             = 'A'
        TABLES
          T_OUTTAB           = T_FINAL[].
    SORT T_FINAL BY WERKS MATNR BUDAT.
    LOOP AT T_FINAL.
       WRITE : /10 T_FINAL-MATNR.
       WRITE : 30 T_FINAL-WERKS.
       WRITE : 40 T_FINAL-BUDAT.
       WRITE : 50 T_FINAL-MENGE.
    **C-- FM to find the number of days between
    **C-- todays date and the posting date
       CALL FUNCTION 'HR_SGPBS_YRS_MTHS_DAYS'
         EXPORTING
           BEG_DA        = T_FINAL-BUDAT
           END_DA        = P_DATE
         IMPORTING
           NO_CAL_DAY    = L_DAYS
         EXCEPTIONS
           DATEINT_ERROR = 1
           OTHERS        = 2.
       IF SY-SUBRC <> 0.
         WRITE : 70 'Error While Calculating days'(018) .
       ELSE.
         WRITE : 70 L_DAYS.
       ENDIF.
       AT END OF MATNR.
         ULINE.
         READ TABLE T_HEADER WITH KEY MATNR = T_FINAL-MATNR
                                      BWKEY = T_FINAL-WERKS.
         IF SY-SUBRC EQ 0.
           WRITE : /1 'Total Valuated Stock', T_HEADER-LBKUM.
           WRITE : /1 'Value of total valuated Stock', T_HEADER-SALK3.
           ULINE.
         ENDIF.
       ENDAT.
    ENDLOOP.
    ENDFORM.                    " DISPLAY_OUTPUT
    *&      Form  BUILD_FIELD_CATALOG
          text
    -->  p1        text
    <--  p2        text
    FORM BUILD_FIELD_CATALOG .
      DATA : CNT1 TYPE I.
      CNT1 = CNT1 + 1.
      GRID_TAB-COL_POS = CNT1.
      GRID_TAB-SELTEXT_L = 'Material'.
      GRID_TAB-FIELDNAME = 'MATNR'.
      GRID_TAB-KEY = 'X'.
      GRID_TAB-NO_ZERO = 'X'.
      GRID_TAB-TABNAME = 'T_FINAL'.
      APPEND GRID_TAB.
      CLEAR GRID_TAB.
      CNT1 = CNT1 + 1.
      GRID_TAB-COL_POS = CNT1.
      GRID_TAB-SELTEXT_L = 'Material Description'.
      GRID_TAB-FIELDNAME = 'MAKTX'.
      GRID_TAB-OUTPUTLEN = '30'.
    GRID_TAB-KEY = 'X'.
    GRID_TAB-NO_ZERO = 'X'.
      GRID_TAB-TABNAME = 'T_FINAL'.
      APPEND GRID_TAB.
      CLEAR GRID_TAB.
      CNT1 = CNT1 + 1.
      GRID_TAB-COL_POS = CNT1.
      GRID_TAB-SELTEXT_L = 'Date of Reciept'.
      GRID_TAB-FIELDNAME = 'BUDAT'.
    GRID_TAB-KEY = 'X'.
    GRID_TAB-NO_ZERO = 'X'.
      GRID_TAB-TABNAME = 'T_FINAL'.
      APPEND GRID_TAB.
      CLEAR GRID_TAB.
      CNT1 = CNT1 + 1.
      GRID_TAB-COL_POS = CNT1.
      GRID_TAB-SELTEXT_L = 'Quantity'.
      GRID_TAB-FIELDNAME = 'MENGE'.
    GRID_TAB-KEY = 'X'.
    GRID_TAB-NO_ZERO = 'X'.
      GRID_TAB-TABNAME = 'T_FINAL'.
      APPEND GRID_TAB.
      CLEAR GRID_TAB.
      CNT1 = CNT1 + 1.
      GRID_TAB-COL_POS = CNT1.
      GRID_TAB-SELTEXT_L = 'Pending Days'.
      GRID_TAB-FIELDNAME = 'PDAYS'.
    GRID_TAB-KEY = 'X'.
    GRID_TAB-NO_ZERO = 'X'.
      GRID_TAB-TABNAME = 'T_FINAL'.
      APPEND GRID_TAB.
      CLEAR GRID_TAB.
      CNT1 = CNT1 + 1.
      GRID_TAB-COL_POS = CNT1.
      GRID_TAB-SELTEXT_L = 'Value'.
      GRID_TAB-FIELDNAME = 'PVAL'.
    GRID_TAB-KEY = 'X'.
    GRID_TAB-NO_ZERO = 'X'.
      GRID_TAB-TABNAME = 'T_FINAL'.
      APPEND GRID_TAB.
      CLEAR GRID_TAB.
      CNT1 = CNT1 + 1.
      GRID_TAB-COL_POS = CNT1.
      GRID_TAB-SELTEXT_L = 'Cumulative Quantity'.
      GRID_TAB-FIELDNAME = 'CQTY'.
    GRID_TAB-KEY = 'X'.
    GRID_TAB-NO_ZERO = 'X'.
      GRID_TAB-TABNAME = 'T_FINAL'.
      APPEND GRID_TAB.
      CLEAR GRID_TAB.
      CNT1 = CNT1 + 1.
      GRID_TAB-COL_POS = CNT1.
      GRID_TAB-SELTEXT_L = 'Value of Cumulative Quantity'.
      GRID_TAB-OUTPUTLEN = '30'.
      GRID_TAB-FIELDNAME = 'CPRC'.
    GRID_TAB-KEY = 'X'.
    GRID_TAB-NO_ZERO = 'X'.
      GRID_TAB-TABNAME = 'T_FINAL'.
      APPEND GRID_TAB.
    ENDFORM.                    " BUILD_FIELD_CATALOG

  • Stock on particular date (performance issue)

    Hi Folks,
    I m calculating stock at all vendor on a particular date.
    But it takes very long and time_out occurs.
    I m calculating opening closing provided return and rejection based on movement types.
    The report hangs up at following particular Join.
    SELECT MKPFBUDAT MSEGBWART MSEGMATNR MSEGLIFNR SUM( MSEG~MENGE )
                  AS MENGE
                      INTO CORRESPONDING FIELDS OF TABLE IT_OPEN
                      FROM
                         MKPF INNER JOIN MSEG ON
                               MKPFMBLNR = MSEGMBLNR AND
                               MKPFMJAHR = MSEGMJAHR
                       WHERE MKPF~MJAHR = D_YEAR AND
                             MKPF~BUDAT GE D_DATE AND
                             MKPF~BUDAT LT S_BUDAT-LOW AND
                    MSEG~BWART IN ('541','542','543','544','551','702') AND
                             MSEG~XAUTO NE 'X' AND
                             MSEG~MATNR IN S_MATNR AND
                             MSEG~WERKS IN P_WERKS AND
                             MSEG~LIFNR IN P_LIFNR
                  GROUP BY LIFNR MATNR BUDAT BWART.
    Is there any way to increase performance by breaking this inner join into select statements or anyhow.
    Regards
    Sachin

    HI,
    On seeing your code, it seems like,
    SELECT MKPFBUDAT MSEGBWART MSEGMATNR MSEGLIFNR SUM( MSEG~MENGE )
    AS MENGE
    INTO CORRESPONDING FIELDS OF TABLE IT_OPEN
    FROM
    MKPF INNER JOIN MSEG ON
    MKPFMBLNR = MSEGMBLNR AND
    MKPFMJAHR = MSEGMJAHR
    WHERE MKPF~MJAHR = D_YEAR AND
    MKPF~BUDAT GE D_DATE AND
    MKPF~BUDAT LT S_BUDAT-LOW AND
    MSEG~BWART IN ('541','542','543','544','551','702') AND
    MSEG~XAUTO NE 'X' AND
    MSEG~MATNR IN S_MATNR AND
    <b>MSEG~WERKS EQ P_WERKS</b> AND
    <b>MSEG~LIFNR EQ P_LIFNR</b>
    GROUP BY LIFNR MATNR BUDAT BWART.
    Please see the code marked with bold as parameter passing in the select statement must be EQ and not IN.
    Secondly, remove the aggregate function SUM from the select. First select all the records into an internal table and either use control break statements or Collect to sum up the entries.
    Next, while selecting from the database use INTO TABLE IT_OPEN rather than into corresponding fields of table.
    Also remove the movement types from the select and restrict it inside the Loop and Endloop.
    Lakshminarayanan
    Please mark all helpful answers for points

  • Reporting (Project Publish) job is failing with 'The given key was not present in the dictionary'

    I am using Project Server 2010 with SQL Server 2008 R2.
    I have a PWA Instance which was running fine. I have a big number of projects and I do not keep site for all the projects as we do not need project site in our business.
    Everything was running fine but during last few days, some of the jobs like Reporting (Project Publish) and Reporting (Project Delete) job is failing with the same error details for all the projects. I am not able to trace where the data is wrong/corrupt
    and how to resolve it.
    The error detail and ULS Log is given below anod I would appreciate if someone can guide me where the problem is and suggest me any solution.
    QUEUE ERROR DETAIL:
    General Reporting message processor failed:
     ReportingProjectChangeMessageFailed (24006) - The given key was not present in the dictionary.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='4f36afe0-43dc-4143-befc-0452da416e69' QueueMessageBody='Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
    PublishType='ProjectPublish'' Error='The given key was not present in the dictionary.'.
     ReportingProjectChangeMessageFailed (24006) - The given key was not present in the dictionary.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='071aeb7b-540e-45fa-b40b-a94a5d2e8e04' QueueMessageBody='Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
    PublishType='ProjectPublish'' Error='The given key was not present in the dictionary.'.
     ReportingProjectChangeMessageFailed (24006) - The given key was not present in the dictionary.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='55445e77-51e3-40d8-a62f-e6db0b897444' QueueMessageBody='Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
    PublishType='ProjectPublish'' Error='The given key was not present in the dictionary.'.
     ReportingProjectChangeMessageFailed (24006) - The given key was not present in the dictionary.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='3ab5a1ba-0915-45bb-a078-4b4b7c38af51' QueueMessageBody='Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
    PublishType='ProjectPublish'' Error='The given key was not present in the dictionary.'.
     ReportingProjectChangeMessageFailed (24006) - The given key was not present in the dictionary.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='b27acd8f-6cde-47d4-bd53-5930e84dc940' QueueMessageBody='Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
    PublishType='ProjectPublish'' Error='The given key was not present in the dictionary.'.
     ReportingProjectChangeMessageFailed (24006) - The given key was not present in the dictionary.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='b7250544-2a11-4887-8dcd-378b34b33ae1' QueueMessageBody='Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
    PublishType='ProjectPublish'' Error='The given key was not present in the dictionary.'.
     Queue:
     GeneralQueueJobFailed (26000) - ReportingProjectPublish.ReportProjectPublishMessageEx. Details: id='26000' name='GeneralQueueJobFailed' uid='0706d212-f737-43ea-b694-c420488d57bb' JobUID='ca238fcf-d91b-46d6-a9c2-15f2cc35230d' ComputerName='WebSrv1' GroupType='ReportingProjectPublish'
    MessageType='ReportProjectPublishMessageEx' MessageId='1' Stage=''. For more details, check the ULS logs on machine WebSrv1 for entries with JobUID ca238fcf-d91b-46d6-a9c2-15f2cc35230d.
    ULS LOG:
    Timestamp               Process                                
     TID    Area                           Category                     
     EventID Level      Message  Correlation
    01/19/2015 19:05:07.44 Microsoft.Office.Project.Server (0x1D30) 0x23FC SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=117.485513497555 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:07.66 Microsoft.Office.Project.Server (0x1D30) 0x2C94 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=192.534598230475 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:08.16 Microsoft.Office.Project.Server (0x1D30) 0x1CFC SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=448.362263674397 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:08.36 Microsoft.Office.Project.Server (0x1D30) 0x17E0 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=162.22152253546 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:09.00 Microsoft.Office.Project.Server (0x1D30) 0x0898 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=557.699412860413 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:09.36 Microsoft.Office.Project.Server (0x1D30) 0x1F20 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=253.695754010613 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:09.67 Microsoft.Office.Project.Server (0x1D30) 0x0D68 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=239.76302803952 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:10.64 Microsoft.Office.Project.Server (0x1D30) 0x3324 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=973.469925841736 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:11.92 Microsoft.Office.Project.Server (0x1D30) 0x2DB8 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=1275.5063556303 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:12.96 Microsoft.Office.Project.Server (0x1D30) 0x0A1C SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=1041.55499409959 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:13.15 Microsoft.Office.Project.Server (0x1D30) 0x0518 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=133.891034879385 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:13.35 Microsoft.Office.Project.Server (0x1D30) 0x14EC SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=207.250205426327 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:14.69 Microsoft.Office.Project.Server (0x1D30) 0x10B4 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_PUBLISH_PROJECT). Execution Time=267.137845971639 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:14.93 Microsoft.Office.Project.Server (0x1D30) 0x14E0 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_PUBLISH_PROJECT). Execution Time=209.552772167485 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:16.10 Microsoft.Office.Project.Server (0x1D30) 0x2AB4 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureNoResultWithOutputParameters -- MSP_SRA_ValidateServerLevelSRA).
    Execution Time=717.808222684698 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:16.67 Microsoft.Office.Project.Server (0x1D30) 0x2AB4 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (FillTypedDataSet -- MSP_SRA_GetData). Execution Time=307.24482978413 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:17.58 Microsoft.Office.Project.Server (0x1D30) 0x2AB4 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureNoResultWithOutputParameters -- MSP_SRA_ValidateServerLevelSRA).
    Execution Time=123.306566048297 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:19.12 Microsoft.Office.Project.Server (0x1D30) 0x25F4 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureNoResult -- MSP_WEB_SP_QRY_CreateSavedTasksForProject). Execution
    Time=111.699445284922 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:19.61 Microsoft.Office.Project.Server (0x1D30) 0x2AC8 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureNoResult -- MSP_WEB_SP_QRY_Statusing_BuildTaskHierarchy). Execution
    Time=449.279962592357 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:19.79 Microsoft.Office.Project.Server (0x1D30) 0x26D0 Project Server Server-side Project Operations 8tci Monitorableser1 PWA:http://epm.company.com/PWA, ServiceApp:SharedServices1_PsiServiceApplication, User:Domain1\User1,
    PSI: [QUEUE] System.IO.FileNotFoundException: The site
    http://epm.company.com/sites/Workspaces2/PROJECT_1 could not be found in the Web application SPWebApplication Name=SharePoint - 80.     at Microsoft.SharePoint.SPSite..ctor(SPFarm farm, Uri requestUri, Boolean contextSite, SPUserToken
    userToken)     at Microsoft.SharePoint.SPSite..ctor(String requestUrl)     at Microsoft.Office.Project.Server.BusinessLayer.Project.OpenProjectWeb(Guid projectUid)     at Microsoft.Office.Project.Server.BusinessLayer.Project.SetPwsProperties(Guid
    projectUid)     at Microsoft.Office.Project.Server.BusinessLayer.Queue.ProcessPublishMessage.ProcessMiscellaneousPublishMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext) ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:19.79 Microsoft.Office.Project.Server (0x1D30) 0x26D0 Project Server Server-side Project Operations 8tcj Monitorable PWA:http://epm.company.com/PWA, ServiceApp:SharedServices1_PsiServiceApplication, User:Domain1\User1,
    PSI: [QUEUE] MiscellaneousPublishMessage failed on project b95c52ba-bc00-4301-aab5-890d0b057c29 ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:27.42 Microsoft.Office.Project.Server (0x1D30) 0x3088 Project Server Reporting atwj Monitorable Error is: ReportingProjectChangeMessageFailed. Details: Attributes:  Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
    PublishType='ProjectPublish'  The given key was not present in the dictionary.  . Standard Information: PSI Entry Point:   Project User: Domain1\User1  Correlation Id: ae078058-f794-47ca-b1ad-0834f7a07f4d  PWA Site URL:
    http://epm.company.com/PWA  SSP Name: SharedServices1_PsiServiceApplication  PSError: ReportingProjectChangeMessageFailed (24006) ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:27.42 Microsoft.Office.Project.Server (0x1D30) 0x3088 Project Server Reporting atwr High PWA:http://epm.company.com/PWA, ServiceApp:SharedServices1_PsiServiceApplication, User:Domain1\User1, PSI: [RDS] ULS
    Event: ReportingProjectChangeMessageFailed was associated with exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.     at System.ThrowHelper.ThrowKeyNotFoundException()    
    at System.Collections.Generic.Dictionary`2.get_Item(TKey key)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.InitializeSprocParameterTypeData(Dictionary`2& routineParameterInfos)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal..ctor(DAL
    dal, DataStoreEnum store)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.get_Reporting()     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.GetRefreshOperationStatus(MessageAreaType
    messageArea)     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.CheckIfAllowedToProceed(ReportingBaseMessage msg, MessageContext msgContext, Group messageGroup, JobTicket jobTicket)    
    at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.ProjectPublishMessageProcessor.HandleMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext) ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:28.47 Microsoft.Office.Project.Server (0x1D30) 0x31F8 Project Server Reporting atwj Monitorable Error is: ReportingProjectChangeMessageFailed. Details: Attributes:  Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
    PublishType='ProjectPublish'  The given key was not present in the dictionary.  . Standard Information: PSI Entry Point:   Project User: Domain1\User1  Correlation Id: ae078058-f794-47ca-b1ad-0834f7a07f4d  PWA Site URL:
    http://epm.company.com/PWA  SSP Name: SharedServices1_PsiServiceApplication  PSError: ReportingProjectChangeMessageFailed (24006) ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:28.47 Microsoft.Office.Project.Server (0x1D30) 0x31F8 Project Server Reporting atwr High PWA:http://epm.company.com/PWA, ServiceApp:SharedServices1_PsiServiceApplication, User:Domain1\User1, PSI: [RDS] ULS
    Event: ReportingProjectChangeMessageFailed was associated with exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.     at System.ThrowHelper.ThrowKeyNotFoundException()    
    at System.Collections.Generic.Dictionary`2.get_Item(TKey key)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.InitializeSprocParameterTypeData(Dictionary`2& routineParameterInfos)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal..ctor(DAL
    dal, DataStoreEnum store)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.get_Reporting()     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.GetRefreshOperationStatus(MessageAreaType
    messageArea)     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.CheckIfAllowedToProceed(ReportingBaseMessage msg, MessageContext msgContext, Group messageGroup, JobTicket jobTicket)    
    at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.ProjectPublishMessageProcessor.HandleMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext) ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:29.51 Microsoft.Office.Project.Server (0x1D30) 0x2B00 Project Server Reporting atwj Monitorable Error is: ReportingProjectChangeMessageFailed. Details: Attributes:  Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
    PublishType='ProjectPublish'  The given key was not present in the dictionary.  . Standard Information: PSI Entry Point:   Project User: Domain1\User1  Correlation Id: ae078058-f794-47ca-b1ad-0834f7a07f4d  PWA Site URL:
    http://epm.company.com/PWA  SSP Name: SharedServices1_PsiServiceApplication  PSError: ReportingProjectChangeMessageFailed (24006) ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:29.51 Microsoft.Office.Project.Server (0x1D30) 0x2B00 Project Server Reporting atwr High PWA:http://epm.company.com/PWA, ServiceApp:SharedServices1_PsiServiceApplication, User:Domain1\User1, PSI: [RDS] ULS
    Event: ReportingProjectChangeMessageFailed was associated with exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.     at System.ThrowHelper.ThrowKeyNotFoundException()    
    at System.Collections.Generic.Dictionary`2.get_Item(TKey key)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.InitializeSprocParameterTypeData(Dictionary`2& routineParameterInfos)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal..ctor(DAL
    dal, DataStoreEnum store)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.get_Reporting()     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.GetRefreshOperationStatus(MessageAreaType
    messageArea)     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.CheckIfAllowedToProceed(ReportingBaseMessage msg, MessageContext msgContext, Group messageGroup, JobTicket jobTicket)    
    at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.ProjectPublishMessageProcessor.HandleMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext) ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:30.56 Microsoft.Office.Project.Server (0x1D30) 0x1D20 Project Server Reporting atwj Monitorable Error is: ReportingProjectChangeMessageFailed. Details: Attributes:  Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
    PublishType='ProjectPublish'  The given key was not present in the dictionary.  . Standard Information: PSI Entry Point:   Project User: Domain1\User1  Correlation Id: ae078058-f794-47ca-b1ad-0834f7a07f4d  PWA Site URL:
    http://epm.company.com/PWA  SSP Name: SharedServices1_PsiServiceApplication  PSError: ReportingProjectChangeMessageFailed (24006) ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:30.56 Microsoft.Office.Project.Server (0x1D30) 0x1D20 Project Server Reporting atwr High PWA:http://epm.company.com/PWA, ServiceApp:SharedServices1_PsiServiceApplication, User:Domain1\User1, PSI: [RDS] ULS
    Event: ReportingProjectChangeMessageFailed was associated with exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.     at System.ThrowHelper.ThrowKeyNotFoundException()    
    at System.Collections.Generic.Dictionary`2.get_Item(TKey key)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.InitializeSprocParameterTypeData(Dictionary`2& routineParameterInfos)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal..ctor(DAL
    dal, DataStoreEnum store)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.get_Reporting()     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.GetRefreshOperationStatus(MessageAreaType
    messageArea)     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.CheckIfAllowedToProceed(ReportingBaseMessage msg, MessageContext msgContext, Group messageGroup, JobTicket jobTicket)    
    at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.ProjectPublishMessageProcessor.HandleMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext) ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:31.60 Microsoft.Office.Project.Server (0x1D30) 0x2170 Project Server Reporting atwj Monitorable Error is: ReportingProjectChangeMessageFailed. Details: Attributes:  Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
    PublishType='ProjectPublish'  The given key was not present in the dictionary.  . Standard Information: PSI Entry Point:   Project User: Domain1\User1  Correlation Id: ae078058-f794-47ca-b1ad-0834f7a07f4d  PWA Site URL:
    http://epm.company.com/PWA  SSP Name: SharedServices1_PsiServiceApplication  PSError: ReportingProjectChangeMessageFailed (24006) ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:31.60 Microsoft.Office.Project.Server (0x1D30) 0x2170 Project Server Reporting atwr High PWA:http://epm.company.com/PWA, ServiceApp:SharedServices1_PsiServiceApplication, User:Domain1\User1, PSI: [RDS] ULS
    Event: ReportingProjectChangeMessageFailed was associated with exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.     at System.ThrowHelper.ThrowKeyNotFoundException()    
    at System.Collections.Generic.Dictionary`2.get_Item(TKey key)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.InitializeSprocParameterTypeData(Dictionary`2& routineParameterInfos)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal..ctor(DAL
    dal, DataStoreEnum store)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.get_Reporting()     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.GetRefreshOperationStatus(MessageAreaType
    messageArea)     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.CheckIfAllowedToProceed(ReportingBaseMessage msg, MessageContext msgContext, Group messageGroup, JobTicket jobTicket)    
    at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.ProjectPublishMessageProcessor.HandleMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext) ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:32.66 Microsoft.Office.Project.Server (0x1D30) 0x24DC Project Server Reporting atwj Critical Standard Information:PSI Entry Point:   Project User: Domain1\User1  Correlation Id: ae078058-f794-47ca-b1ad-0834f7a07f4d 
    PWA Site URL: http://epm.company.com/PWA  SSP Name: SharedServices1_PsiServiceApplication  PSError: ReportingProjectChangeMessageFailed (24006) RDS: The request to synchronize change(s) to project Project
    UID='b95c52ba-bc00-4301-aab5-890d0b057c29'. PublishType='ProjectPublish' failed.  Message: 'ReportingProjectChangeMessageFailed'. Message Body: The given key was not present in the dictionary. Error:(null) ae078058-f794-47ca-b1ad-0834f7a07f4d
    01/19/2015 19:05:32.66 Microsoft.Office.Project.Server (0x1D30) 0x24DC Project Server Reporting atwr High PWA:http://epm.company.com/PWA, ServiceApp:SharedServices1_PsiServiceApplication, User:Domain1\User1, PSI: [RDS] ULS
    Event: ReportingProjectChangeMessageFailed was associated with exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.     at System.ThrowHelper.ThrowKeyNotFoundException()    
    at System.Collections.Generic.Dictionary`2.get_Item(TKey key)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.InitializeSprocParameterTypeData(Dictionary`2& routineParameterInfos)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal..ctor(DAL
    dal, DataStoreEnum store)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.get_Reporting()     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.GetRefreshOperationStatus(MessageAreaType
    messageArea)     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.CheckIfAllowedToProceed(ReportingBaseMessage msg, MessageContext msgContext, Group messageGroup, JobTicket jobTicket)    
    at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.ProjectPublishMessageProcessor.HandleMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext) ae078058-f794-47ca-b1ad-0834f7a07f4d

    Without seeing the history, one possibility might be some corruption in the reporting database. Assuming that you are following best practices for SQL DB management, and this is not a DB neglect problem, then I would try to force a refresh to see if that
    helps. You can do this by executing a custom field backup and then restore. Note: Do not do this during production hours. Let us know if that provides any therapy.
    Gary Chefetz, MCITP, MCP, MVP msProjectExperts
    Project and Project ServerFAQs
    Project Server Help BLOG

  • How to see data for particular date from a alert log file

    Hi Experts,
    I would like to know how can i see data for a particular date from alert_db.log in unix environment. I'm suing 0racle 9i in unix
    Right now i'm using tail -500 alert_db.log>alert.txt then view the whole thing. But is there any easier way to see for a partiicular date or time
    Thanks
    Shaan

    Hi Jaffar,
    Here i have to pass exactly date and time, is there any way to see records for let say Nov 23 2007. because when i used this
    tail -500 alert_sid.log | grep " Nov 23 2007" > alert_date.txt
    It's not working. Here is the sample log file
    Mon Nov 26 21:42:43 2007
    Thread 1 advanced to log sequence 138
    Current log# 3 seq# 138 mem# 0: /oracle/NEWDB/oradata/NEWDB/redo3.log
    Mon Nov 26 21:42:43 2007
    ARCH: Evaluating archive log 1 thread 1 sequence 137
    Mon Nov 26 21:42:43 2007
    ARC1: Evaluating archive log 1 thread 1 sequence 137
    ARC1: Unable to archive log 1 thread 1 sequence 137
    Log actively being archived by another process
    Mon Nov 26 21:42:43 2007
    ARCH: Beginning to archive log 1 thread 1 sequence 137
    Creating archive destination LOG_ARCHIVE_DEST_1: '/oracle/NEWDB/admin/arch/1_137
    .dbf'
    ARCH: Completed archiving log 1 thread 1 sequence 137
    Mon Nov 26 21:42:44 2007
    Thread 1 advanced to log sequence 139
    Current log# 2 seq# 139 mem# 0: /oracle/NEWDB/oradata/NEWDB/redo2.log
    Mon Nov 26 21:42:44 2007
    ARC0: Evaluating archive log 3 thread 1 sequence 138
    ARC0: Beginning to archive log 3 thread 1 sequence 138
    Creating archive destination LOG_ARCHIVE_DEST_1: '/oracle/NEWDB/admin/arch/1_138
    .dbf'
    Mon Nov 26 21:42:44 2007
    ARCH: Evaluating archive log 3 thread 1 sequence 138
    ARCH: Unable to archive log 3 thread 1 sequence 138
    Log actively being archived by another process
    Mon Nov 26 21:42:45 2007
    ARC0: Completed archiving log 3 thread 1 sequence 138
    Mon Nov 26 21:45:12 2007
    Starting control autobackup
    Mon Nov 26 21:45:56 2007
    Control autobackup written to SBT_TAPE device
    comment 'API Version 2.0,MMS Version 5.0.0.0',
    media 'WP0033'
    handle 'c-2861328927-20071126-01'
    Clearing standby activation ID 2873610446 (0xab47d0ce)
    The primary database controlfile was created using the
    'MAXLOGFILES 5' clause.
    The resulting standby controlfile will not have enough
    available logfile entries to support an adequate number
    of standby redo logfiles. Consider re-creating the
    primary controlfile using 'MAXLOGFILES 8' (or larger).
    Use the following SQL commands on the standby database to create
    standby redo logfiles that match the primary database:
    ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 10485760;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 10485760;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 10485760;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 10485760;
    Tue Nov 27 21:23:50 2007
    Starting control autobackup
    Tue Nov 27 21:30:49 2007
    Control autobackup written to SBT_TAPE device
    comment 'API Version 2.0,MMS Version 5.0.0.0',
    media 'WP0280'
    handle 'c-2861328927-20071127-00'
    Tue Nov 27 21:30:57 2007
    ARC1: Evaluating archive log 2 thread 1 sequence 139
    ARC1: Beginning to archive log 2 thread 1 sequence 139
    Creating archive destination LOG_ARCHIVE_DEST_1: '/oracle/NEWDB/admin/arch/1_139
    .dbf'
    Tue Nov 27 21:30:57 2007
    Thread 1 advanced to log sequence 140
    Current log# 1 seq# 140 mem# 0: /oracle/NEWDB/oradata/NEWDB/redo1.log
    Tue Nov 27 21:30:57 2007
    ARCH: Evaluating archive log 2 thread 1 sequence 139
    ARCH: Unable to archive log 2 thread 1 sequence 139
    Log actively being archived by another process
    Tue Nov 27 21:30:58 2007
    ARC1: Completed archiving log 2 thread 1 sequence 139
    Tue Nov 27 21:30:58 2007
    Thread 1 advanced to log sequence 141
    Current log# 3 seq# 141 mem# 0: /oracle/NEWDB/oradata/NEWDB/redo3.log
    Tue Nov 27 21:30:58 2007
    ARCH: Evaluating archive log 1 thread 1 sequence 140
    ARCH: Beginning to archive log 1 thread 1 sequence 140
    Creating archive destination LOG_ARCHIVE_DEST_1: '/oracle/NEWDB/admin/arch/1_140
    .dbf'
    Tue Nov 27 21:30:58 2007
    ARC1: Evaluating archive log 1 thread 1 sequence 140
    ARC1: Unable to archive log 1 thread 1 sequence 140
    Log actively being archived by another process
    Tue Nov 27 21:30:58 2007
    ARCH: Completed archiving log 1 thread 1 sequence 140
    Tue Nov 27 21:33:16 2007
    Starting control autobackup
    Tue Nov 27 21:34:29 2007
    Control autobackup written to SBT_TAPE device
    comment 'API Version 2.0,MMS Version 5.0.0.0',
    media 'WP0205'
    handle 'c-2861328927-20071127-01'
    Clearing standby activation ID 2873610446 (0xab47d0ce)
    The primary database controlfile was created using the
    'MAXLOGFILES 5' clause.
    The resulting standby controlfile will not have enough
    available logfile entries to support an adequate number
    of standby redo logfiles. Consider re-creating the
    primary controlfile using 'MAXLOGFILES 8' (or larger).
    Use the following SQL commands on the standby database to create
    standby redo logfiles that match the primary database:
    ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 10485760;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 10485760;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 10485760;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 10485760;
    Wed Nov 28 21:43:31 2007
    Starting control autobackup
    Wed Nov 28 21:43:59 2007
    Control autobackup written to SBT_TAPE device
    comment 'API Version 2.0,MMS Version 5.0.0.0',
    media 'WP0202'
    handle 'c-2861328927-20071128-00'
    Wed Nov 28 21:44:08 2007
    Thread 1 advanced to log sequence 142
    Current log# 2 seq# 142 mem# 0: /oracle/NEWDB/oradata/NEWDB/redo2.log
    Wed Nov 28 21:44:08 2007
    ARCH: Evaluating archive log 3 thread 1 sequence 141
    ARCH: Beginning to archive log 3 thread 1 sequence 141
    Wed Nov 28 21:44:08 2007
    ARC1: Evaluating archive log 3 thread 1 sequence 141
    ARC1: Unable to archive log 3 thread 1 sequence 141
    Log actively being archived by another process
    Wed Nov 28 21:44:08 2007
    Creating archive destination LOG_ARCHIVE_DEST_1: '/oracle/NEWDB/admin/arch/1_141
    .dbf'
    Wed Nov 28 21:44:08 2007
    ARC0: Evaluating archive log 3 thread 1 sequence 141
    ARC0: Unable to archive log 3 thread 1 sequence 141
    Log actively being archived by another process
    Wed Nov 28 21:44:08 2007
    ARCH: Completed archiving log 3 thread 1 sequence 141
    Wed Nov 28 21:44:09 2007
    Thread 1 advanced to log sequence 143
    Current log# 1 seq# 143 mem# 0: /oracle/NEWDB/oradata/NEWDB/redo1.log
    Wed Nov 28 21:44:09 2007
    ARCH: Evaluating archive log 2 thread 1 sequence 142
    ARCH: Beginning to archive log 2 thread 1 sequence 142
    Creating archive destination LOG_ARCHIVE_DEST_1: '/oracle/NEWDB/admin/arch/1_142
    .dbf'
    Wed Nov 28 21:44:09 2007
    ARC0: Evaluating archive log 2 thread 1 sequence 142
    ARC0: Unable to archive log 2 thread 1 sequence 142
    Log actively being archived by another process
    Wed Nov 28 21:44:09 2007
    ARCH: Completed archiving log 2 thread 1 sequence 142
    Wed Nov 28 21:44:36 2007
    Starting control autobackup
    Wed Nov 28 21:45:00 2007
    Control autobackup written to SBT_TAPE device
    comment 'API Version 2.0,MMS Version 5.0.0.0',
    media 'WP0202'
    handle 'c-2861328927-20071128-01'
    Clearing standby activation ID 2873610446 (0xab47d0ce)
    The primary database controlfile was created using the
    'MAXLOGFILES 5' clause.
    The resulting standby controlfile will not have enough
    available logfile entries to support an adequate number
    of standby redo logfiles. Consider re-creating the
    primary controlfile using 'MAXLOGFILES 8' (or larger).
    Use the following SQL commands on the standby database to create
    standby redo logfiles that match the primary database:
    ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 10485760;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 10485760;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 10485760;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 10485760;
    Thu Nov 29 21:36:44 2007
    Starting control autobackup
    Thu Nov 29 21:42:53 2007
    Control autobackup written to SBT_TAPE device
    comment 'API Version 2.0,MMS Version 5.0.0.0',
    media 'WP0206'
    handle 'c-2861328927-20071129-00'
    Thu Nov 29 21:43:01 2007
    Thread 1 advanced to log sequence 144
    Current log# 3 seq# 144 mem# 0: /oracle/NEWDB/oradata/NEWDB/redo3.log
    Thu Nov 29 21:43:01 2007
    ARCH: Evaluating archive log 1 thread 1 sequence 143
    ARCH: Beginning to archive log 1 thread 1 sequence 143
    Creating archive destination LOG_ARCHIVE_DEST_1: '/oracle/NEWDB/admin/arch/1_143
    .dbf'
    Thu Nov 29 21:43:01 2007
    ARC1: Evaluating archive log 1 thread 1 sequence 143
    ARC1: Unable to archive log 1 thread 1 sequence 143
    Log actively being archived by another process
    Thu Nov 29 21:43:02 2007
    ARCH: Completed archiving log 1 thread 1 sequence 143
    Thu Nov 29 21:43:03 2007
    Thread 1 advanced to log sequence 145
    Current log# 2 seq# 145 mem# 0: /oracle/NEWDB/oradata/NEWDB/redo2.log
    Thu Nov 29 21:43:03 2007
    ARCH: Evaluating archive log 3 thread 1 sequence 144
    ARCH: Beginning to archive log 3 thread 1 sequence 144
    Creating archive destination LOG_ARCHIVE_DEST_1: '/oracle/NEWDB/admin/arch/1_144
    .dbf'
    Thu Nov 29 21:43:03 2007
    ARC0: Evaluating archive log 3 thread 1 sequence 144
    ARC0: Unable to archive log 3 thread 1 sequence 144
    Log actively being archived by another process
    Thu Nov 29 21:43:03 2007
    ARCH: Completed archiving log 3 thread 1 sequence 144
    Thu Nov 29 21:49:00 2007
    Starting control autobackup
    Thu Nov 29 21:50:14 2007
    Control autobackup written to SBT_TAPE device
    comment 'API Version 2.0,MMS Version 5.0.0.0',
    media 'WP0280'
    handle 'c-2861328927-20071129-01'
    Thanks
    Shaan

Maybe you are looking for