SMQ1 - Outbound Ques in Status " READY"

Dear Experts
We have 30,000 + queues in R/3 system which need to be transferred to APO system.
Almost all queus are in status " READY"
if we manually activating - it gets cleared
But it is impossible to activate manually 30,000+ Queus.
How can i automatically activate all these queues.
Thanks in advance
Please Help
Rgds
PR

Hi ,
Check in SMQS if there are entries with "U" as unregistered. All the entries should be "R" type.
otherwise , they will only if manual intervention is present.
Award points if helpful.
Thanks,
Tanuj

Similar Messages

  • Queues getting piled up in Outbound que SMQ1

    Queues getting piled up in the outbound que and wait time now is 10 to 15 minutes before getting refreshed which was more then 45 minutes earlier,
    FYI there are 5 application instances in the prod system and this ques getting piled up after hitting application 3 & 4 only otherwise geting cleared during load balance process
    Please suggest

    Hi i would like to inform you that the isue has been resolved  as there was error at OS level might have been due to firmware upgrade patches

  • Error 'sysfail' in outbound que of SRM :Initial download - DNL_CUST_BASIS3

    Dear Consultants,
                                   We are trying to replicate the product categories and material master from ECC system to SRM system for the first time.
    Performed all the middleware settings as per note 720819. When running the initial load - DNL_CUST_BASIS3 the prog keeps on running. We are getting a entry in SRM outbound que - Sysfail - trigerred a dump in the source system. When we get into ST22 in ECC system we see there is a dump. While analysing the dump in st22 we get that table CRMATAB is empty, the same issue we get when we debug the que in outbound que in SRM.
    We are planning to apply note 1501685 to address the issue. But there are some entries which are there in Inbound que of SRM system. All have the status of sysfail. Some refer to analyse the error in SMW01 and some say refer note 490748. In the Note 490748 all entries are maintained . Other entries says the category for material group xxx does not exist - import the Customizing object DNL_CUST_PROD1.
    I am a bit confused now, will the application of the Note will solve the issue or is there something else that may need to be done.
    Any specific inputs will be valuable for me.
    regards
    Arindam.

    Hello All,
                                I am getting the following error in SMW01a re as follows
    Category for material type MAT_KMAT does not exist
    Category for material group CM14 does not exist
    Please note I am running the following initial load in sequence
    DNL_CUST_BASIS3
    DNL_CUST_PROD1
    DNL_CUST_PROD0
    We are also getting a dump in SRM system -
    ST22 -
    Runtime Errors         CALL_FUNCTION_PARM_MISSING
    ABAP Program           SAPLSMOUTIL
    any specific inputs will be welcome
    regards
    Arindam

  • Mail stuck in wf_notification_out with status = ready

    Hi All,
    Please help on workflow mailer .
    EBS R12 12.1.3 DB:11GR2 OS: OUL5X64
    when sending a test mail and verify with this script below , i could see the message was in wf_notification_out table with status READY
    BUT IT JUST SAT THERE AND NEVER GOES ANYWHERE.
    SELECT n.begin_date,
    n.status,
    n.mail_status,
    n.recipient_role,
    de.def_enq_time,
    de.def_deq_time,
    de.def_state,
    ou.out_enq_time,
    ou.out_deq_time,
    ou.out_state
    FROM applsys.wf_notifications n,
    (SELECT d.enq_time def_enq_time,
    d.deq_time def_deq_time,
    TO_NUMBER((SELECT VALUE
    FROM TABLE(d.user_data.parameter_list)
    WHERE NAME = 'NOTIFICATION_ID')) d_notification_id,
    msg_state def_state
    FROM applsys.aq$wf_deferred d
    WHERE d.corr_id = 'APPS:oracle.apps.wf.notification.send') de,
    (SELECT o.deq_time out_deq_time,
    o.enq_time out_enq_time,
    TO_NUMBER((SELECT str_value
    FROM TABLE(o.user_data.header.properties)
    WHERE NAME = 'NOTIFICATION_ID')) o_notification_id,
    msg_state out_state
    FROM applsys.aq$wf_notification_out o) ou
    WHERE n.notification_id = &NOTIFICATION_ID
    AND n.notification_id = de.d_notification_id(+)
    AND n.notification_id = ou.o_notification_id(+);
    Here was the result.
    BEGIN_DATE STATUS MAIL_STATUS RECIPIENT_ROLE DEF_ENQ_T DEF_DEQ_T DEF_STATE OUT_END_TIME OUT_DEQ_TIME OUT_STATE
    11-JUN-12     OPEN      MAIL     TEST.USER      11-JUN-12     11-JUN-12     PROCESSED     11-JUN-12          READY
    Please advise it i miss anything. This was working before.
    Thanks in advance.

    Please advise it i miss anything. This was working before.Can you find any errors in the Database and Workflow log files?
    Troubleshooting Workflow Java Notification Mailer - Technical Reference [ID 1191125.1]
    A Guide For Troubleshooting Workflow Notification Emails - Inbound and Outbound [ID 831982.1]
    How To Troubleshoot Java-based Workflow Notification Mailer [ID 242941.1]
    Troubleshooting Inbound & Outbound Email Notifications [ID 1184846.1]
    OWF H Diagnostics, Solutions and Information [ID 332152.1]
    Oracle Workflow Release 12 Diagnostics [ID 469822.1]
    Thanks,
    Hussein

  • Struck up with R3AD_* Queues in SMQ1(Outbound Queue in ECC Side)

    Hi ,
    I am using CRM Middleware for replicating business partner(BP) from CRM to ECC
    and material from ECC to CRM.
    BP and Materials are replicating well.
    My Issue is,
    while checking queues in SMQ1 (Outbound Queue in ECC Side), i am getting many queues are pending also
    status as "SYSFAIL".
    QUEUE Names are R3AD_000000123,R3AD_000000139,R3AD_000000141... R3AD_*,etc..
    I tried to unlock the queues and activated, afterthat also queue status is "SYSFAIL". Then i checked in CRM side
    Transaction Code SMW01,
    BDOC Details:
    BDOC State Description: Information no processing.
    BDOC Type :BUS_TRANS_MSG.
    ERROR Message:
       a.Processing of document with GUID 4E57E4A5108162A7E10000000A0BE02A is canceled.
      b.Business transaction type ZEQQ does not exist.
      c.Validation error occurred: Module CRM_DOWNLOAD_BTMBDOC_VAL, BDoc type BUS_TRANS_MSG.
    Thanks and Regards,
    Ravi A

    Maintain a filter in ECC go to Tcode SM30 , then go to table/view and enter CRMRFCPAR click maintain and enter
    User CRM
    Object Name SALESDOCUMENT
    Destination xxxxxxxxxxxx
    Load Type delta download
    Queue Name
    Queue Name
    BAPINAME
    INFO
    InQueue Flag X
    Send XML
    CRM Release 700
    Logical system xxxxxxxxxxx
    this will stop the flow of ecc sales documents to crm
    this will also stop Bdcos in SMW01
    Please let me know if this helped

  • CIF Ques Stuck in READY State on R3 Inbound for no Reason

    Hi,
    Question pertains to CIF Processing and Ques waiting in READY State from R3 to SCM-APO for no Apparent Reason.
    Our Orders (PRs, STOs) generated via APO are being sent to R3 correctly, getting generated in R/3 but not coming back with the PR/STO Number back to APO.  Stuck in R3 inbound.
    I've read a couple of articles on SDN on this.
    Apart from the Standard CIF Configuration, and Settings in SMQR and SMQS (Qin & Qout Scheduler) for retrying Stuck Ques to be processed, is there anything else that can be looked at ?  Any Consulting Notes on this Topic ?
    SCM-APO version 4.0 on latest Support Pack.
    R3 4.6c and Plugin compatible. Not on most latest SP.
    Thanks,
    Ambrish Mathur

    Hai,
    Yes our Problem is resolved now.  The Solution was Technical in Nature and not functional  (as you can logically expect).
    Assuming your Basis Team has properly setup the QIN and QOUT Scheduler on BOTH sides (APO and R3) ...
    Also in QIN and QOUT the Time to RETRY a Que is set to something low as every 5 minutes and retry 10 times. 
    (However this was not the main issue for us).
    We found in our Case since the R3's Support Pack and Plug-In were not upgraded due to many depandancies to other Projects ... we found that the QRFC Versions on the R3 side were a few sub versions behind the APO QRFC Version since APO was on Latest Support Pack on SCM 4.
    The BASIS Group downloaded and Installed the Latest QRFC version and the Problem was subsequently resolved. 
    QRFC Version can be found in Transaction SMQ1 / SMQ2 -> Menu Path Information -> Version.
    We are now at QRFC ver. 6.30.060, Supplement # 11.
    Hope you find this usefull and it resolves your issue.  Do revert back if it does.
    Regards,
    Ambrish Mathur

  • SMWMQUEUES -  what does status "ready" mean

    SMWMQUEUES lists all outbound queues by name in CRM. All my queues are in status NOSEND . They currently can not conntrans so I am wondering if this is some indication that their site is not correctly identified. Does anyone know why all the othere queues are in status NOSEND and this one is READY ?
    Many thanks MM

    Please have a look  at the note below and <b>reward points if it helps</b>
    Basically, if the initial load is not successful, you should analyze queues and restart them if required. It makes sense to restart the initial load of an individual object if the analysis did not result in problems. Always log on to the CRM/EBP server in English to see the error texts. For notes on the delta data supply from the R/3 Backend system into the CRM server and the other way round, see the attached notes.
    Error Detection - Tool Monitoring in the Middleware Menu:
    a) Transaction R3AM1: Initial load monitor: After a successful initial load, all traffic lights should be "green".
    b) Transaction SMWP: 'Middleware Portal':Under 'Runtime Information' -> 'Adapter Status Information' -> 'Initial Load Status', you can investigate the inbound and outbound queues and branch to the qRFC transactions from there. Below, the error analyses with access via the CRM Middleware Portal are described.
    c) Transaction SMW01: Analysis of errors in the BDoc flow, in particular CRM/EBP application Customizing errors during the initial load into the CRM Server.
    d) Transaction SMWT: Middleware trace with trace environment 'I':Display of additional information for each data block transferred.
    Analysis
    1. Ensure that the highest available plug-in (PI) Support Package plus Core Support Package is installed in the R/3 back-end system. The same applies to the CRM/EBP Server.
    2. Transaction SM30:In the R/3 Back-end System, the correct RFC destination must be entered in table CRMRFCPAR for CONSUMER CRM. For this, see the documentation on the CRM Adapter Framework.
    3. Transaction SM59:Test RFC connection - 'Remote login' from CRM/EBP to R/3 Back end and vice versa.
    4. Transaction SMOEAC (Administration Console): Check the sites for R/3 systems. Have the RFC destinations been entered correctly and do the additional attributes exist? For this, see the documentation on the CRM Adapter Framework.
    5. Transaction SMWP:Menu item 'Runtime information' -> 'Adapter Status Information' -> 'Initial Load Status':The subitems for the monitoring of the different inbound and outbound queues must each be evaluated in a similar way:
                  Double-click a queue entry to display the status of a queue (for example, READY, RUNNING, SYSFAIL). If you double-click again, you can see the cause of the error from the status text in the case of an error (SYSFAIL). Note: In case of temporary errors, it often helps to restart the queue (F6).
                  In general, a short dump occurs for status SYSFAIL. For the outbound queues, this short dump exists in the target system and not in the system in which the queue is. For inbound queues, the short dump exists in the same system as the inbound queue. For the initial data transfer between CRM and CDB or CRM and XML/ALE sites, the source and the target system are the same.
    a) Menu option 'Load from OLTP systems:Start outbound queues in the CRM server':Status SYSFAIL in these outbound queues displays that a program termination occurred during the selection or the sending of data from an R/3 source system.If the program termination occurs in programs SAPLCRM0, SAPLCXML, SAPLCXMP, SAPLCTRK, SAPLCRMD, SAPLCGEN, SAPLCGNR, SAPLCFIL, SAPLCRMR, SAPLCRMS, SAPLCRMC and if you cannot solve the problem with the help of this note, send a customer message to component CRM-MW-ADP.In all other cases, choose the corresponding application component.
    b) Menu item 'Load from CRM: Start outbound queues in the CRM server': Status SYSFAIL displays that a program termination occurred during the selection of data from the CRM for the CDB or a different site (for example, XML). Apart from that, the same applies as under the previous point.
    c) Menu item 'Outbound queues in OLTP-R/3 System(s)':In general, these queues are only temporary because they are converted into inbound queues on the CRM Server. Consequently, they only exist if network errors, incorrect RFC connection parameters or database problems occur on the CRM server. If a restart of the queue is not successful, a short dump has occurred on the receiving side, the cause of which you must first correct. If the status of the queue is 'NOSENDS', the sending of data was blocked by mistake. This should never be set during live operation. To solve the problem, ensure that the HOLD_DATA field is initial in the CRMRFCPAR table. You can use Transaction SM30 to check or change this. In this transaction, it is the entry for the 'Save data' text. You must trigger existing queues with the status 'NOSENDS' manually. Afterwards, the processing of the outbound queue will occur automatically again.
    d) Menu item 'Inbound queues on CRM server': In these queues, you find the data from the initial data transfer from an R/3 System. A SYSFAIL is by far the most frequent item in these queues. The reasons for this can be manifold. Program terminations in the CRM application due to missing or incorrect Customizing are the most frequent reason. To see detailed information on the errors which occurred, call Transaction SMW01 for the corresponding BDoc type. This is also required if there is no queue with errors that you can use to determine and analyze errors in any type of data transport. Short dumps may also occur due to real program errors. In this case, there is a corresponding short dump on the same system. If the error occurs in the SAPLSMOUTIL, SAPLSMO0 or SAPLSMOXML programs and if you cannot correct the error yourself, create a message for component CRM-MW-ADP. In all other cases, create a message for the corresponding component.
    A possible error text in the inbound queue is "Error in Mapping (Details: Transaction SMW01)" (SMOF078). To correct this error, proceed as follows: Analyze and correct the error which is displayed in Transaction SMW01 at the error segments. You can find the correct BDoc message with the aid of the date and the time of the entry in the queue as well as with the BDoc status which is 'F05'. After you have corrected this problem, restart the inbound queue in order to process the entry. You can request help for correcting the error displayed in Transaction SMW01 in the corresponding application component.
    e) Menu item 'Inbound queue on CRM server from CRM': These queues contain the data from the initial data transfer from the CRM Server to the CDB or other linked sites (for example, XML). For the error analysis, the same applies as for the previous menu item.
    6. Logical system maintained in the CRM/EBP Server and in the R/3 Back end?
    7. Transaction SMW01: Incorrect settings in the CRM/EBP application.In the selection screen, restrict the relevant period and, if required, the BDoc type.In the result of the selection, select the incorrect message and choose 'Display errors/error segments'.Here, you find notes on CRM/EBP application Customizing problems.
    8. Transaction ST22: Short dumps on OLTP CRM/EBP Server
    9. Transaction SE80:Syntax check for generated functions in development class $SAP_MSAGEN, for example function group /1CRMG0/PRDCT_OBJECT for product master. If a function group has syntax errors, it is often useful to regenerate it by using Transaction SMOGGEN.
    Typical error messages and their solution:
    Error 1654, for example for table space PSAPBTABI: Solution: add SAPDBA to the table space.
    Timeout in R/3 back-end system during the initial download: Solution:See Note 162956
    General performance problems during the initial download:See Note 350176
    Inbound queue (SMQ2) on the CRM/EBP Server has status 'READY', but it is not processed. Solution:Restart the queue and check the registration of R3A, CRI in Transaction SMQR
    The outbound queue in the R/3 Back-end System has status 'SYSFAIL', the detailed message is: Solution:shut down the CRM/EBP Server and restart it.If other SYSFAIL messages occur, restart the queue and analyze the short dumps.
    RSQL error 13 when accessing table SMOTCURR:you should convert the data exchange between the R/3 Back end and the CRM Server to the XML format (see Note 333008).Then delete the inbound queue (in SMQ2, for example, R3AI_DNL_CUST_CURREN) and restart the object.
    The number of data records between an R/3 Back-end table or a CRM table and the corresponding CRM CDB table do not match. Solution:Check the following:
    Was the initial load completed successfully?
    Are filters set for the object?
    Note:Filters that are defined in the CRM Server must be defined in the form in which the data is stored in the source system in the database. For example, the filter for date 20010215 corresponds to a filter for February 15, 2001 (format YYYYMMDD).Make sure that the filter criteria are entered with leading digits, for example 10-digit customer numbers, 18-digit material numbers with leading zeros.
    Are there error messages in Transaction SMW01 indicating rejections by the CRM server application?
    Is the table a child table and are the excessive records orphaned child records that are not selected as well?
    Should this delta data only be in the Customizing tables after the compare?
    After you start the initial load using Transaction R3AS, the started object remains in status WAIT in Transaction R3AM1, and the initial download is not started. This is not an error.
    The following causes are possible:
    Too many objects already have status RUNNING or too many requests have been started or too many DIMa instances have been started and not completed. The number of running initial loads plus the number of running requests is the total number of all running initial-like processes. Therefore, this object must wait for the initial load or request of a different object to be completed. After an object is completed, a different object in status 'WAIT' is started automatically. If the initial load/request of the other objects is not completed, you can use this note to analyze why these are not completed and trigger their processing. You can change the maximum number of parallel initial loads using the MAX_PARALLEL_PROCESSES parameter in the SMOFPARSFA table. The standard value in the 'Param. Value' field is 5.
    The object has a parent object whose initial load was not completed successfully. You can see from flag 'P' in Transaction R3AM1 whether an object has a parent object. You can see from table SMOFOBJPAR which objects these are.
    No entry exists in one of the queues, but the status in R3AM1 remains 'Running':
    This is probably because after the data selection in the source system, no reply was sent to the CRM system. If this is the case for one adapter object but not for others, contact the respective application component, which can analyze why the source system does not send a reply and correct the problem.
    If this system response occurs for all adapter objects, create a message for component CRM-MW-ADP.
    During the start of the initial load, the system displays the message "No initial load if COMPARE is active" or "No Initial Load if data distribution is active. Use Synchron. Load" (SMOF162):
    In this case, start a synchronization load for the respective Adapter Object.

  • Queues, not processed automatically they are status Ready

    Hi Experts ,
    Queues in outbound(smq2), not processed automatically they are status Ready from long time, RFC is working fine
    i tried to process maually one by one ,but they are many.
    how can i execute this , need your inputs.
    thanks in advance
    vamsi

    Check that the scheduler is running in SMQR
    Read,
    http://help.sap.com/saphelp_nw04s/Helpdata/EN/e4/df5f3c8dde1c67e10000000a114084/content.htm
    Regards
    Juan

  • Logical drive 1 status = Ready for recovery ml350 g5

    Hi,
    I have a problem with a HP Proliant ML350 G5, 2 weeks ago the server did shutdown unexpectedly i looked in the ACU and saw that the controller had a battery problem. I replaced the battery but the server keeps once or twice a day shutting down. I made a report from the ACU but i don't know what this all means.
    Here is a part of the report, i hope someone can lead me to the right solution,
    Thanks in advance.
    Array Diagnostic Utility Version 7.85.16.0
    Array Diagnostic Utility Inspection Report Version 7.85.16.0
    Date/Time:          Friday, June 27, 2014 3:43:11PM
    Computer Model:     HP Server
    SLOT SUMMARY:
       Slot Num  Slot Type  Array Controllers and Host Adapters Detected
       SLOT 0    PCI        Smart Array E200i Controller
    SLOT 0 Smart Array E200i Controller ERROR REPORT:
       Logical drive 1 status = Ready for recovery
    SUBSYSTEM INFORMATION:
       Chassis Serial Num:              GB87494LT1
       This Controller
          Array Serial Number:          QT79MU6382    
          Cache Serial Number:          P9A3A0B9SV00ST
       Other Controller
          Array Serial Number:          Not Available
          Cache Serial Number:          Not Available
    CONTROLLER IDENTIFICATION:
       Configured Logical Drives: 1
       Configuration Signature:   0xa00004c9
       Controller Firmware Rev:   1.66
       Controller ROM Revision:   1.66
       Controller Hardware Rev:   0x00
       Boot Block Version:        1.66
       Board ID:                  0x3211103c
       Cable or Config Error:     0x00 (No)
       Invalid Host RAM Address:  No
       CPU Revision:              0x00
       CPU to PCI ASIC Rev:       0x00
       Cache Controller ASIC Rev: 0x00
       PCI to Host ASIC Rev:      0x00
       Marketing Revision:        0x41 (Rev A)
       Expand Disable Code:       0x01
       Protocol Chip Count:       1
       Enclosure Count:           3
       Max SCSI IDs per Bus:      0
       Big Drive Map:             0x000c 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
       Big Ext Drive Map:         0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
       Big Non-Disk Drive Map:    0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
       Fibre Chip Count:          0
       Recovery ROM Inactive     
       Image Revision:               
       Recovery ROM Active Image 
       Flags Status:              0x10
       Battery PIC Rev:           0x20
       NCQ:                       Not Supported
    LOGICAL DRIVE IDENTIFICATION:
       Logical Drive 1:
          Sector Size:              512
          Sectors Available:        143305920
          Fault Tolerance Mode:     Mirroring
          Logical Param Table:      cyl=17562 heads=255 sec/track=32 xlate sig=0x0
          BIOS Disabled:            No
          Logical Drive Ident:      0x       0
          Logical Drive Label:      A00004C9QT79MU6382     678E
    LOGICAL DRIVE CONFIGURATION:
       Logical Drive 1:
          Configuration Signature:  0xa00004c9
          Mapping Scheme:           Multiple Block
          Physical Drives:          2 (number not valid after drive movement)
             This Logical Drive:    2 (excluding spare drives)
          Fault Tolerance Mode:     Mirroring
          Logical Param Table:      cyl=17562 heads=255 sec/track=32 xlate sig=0x0
          Distribution Factor:      256
          Operating System:         64768
          Controller Order:         0
          Additional Information:   0
          Offset to Data&colon;           0
          Int 13h Support Enabled:  Yes
          Sectors on Volume:        143305920
          Sectors per Drive:        143305920
          Big Drive Assignment Map: 0x000c 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
          Big Spare Assignment Map: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
          Array Accelerator is enabled for this logical drive.
    LOGICAL DRIVE STATUS:
       Logical Drive 1:
          Drive Status:           Ready for recovery
          Blocks to Rebuild:      0
          Blocks Re-mapped:      
          Spare Status Flags:     0x00
          Spare to Replaced Map:  See Big Spare to Replace Map:
          Media Was Exchanged:    No
          Cache Failure:          No
          Expand Failure:         0x00
          Unit Flags:             0x00
          Big Remap Count:        All Counts Zero
          Big Drive Failure Map:     0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
          Big Replacement Drive Map: 0x0004 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
          Big Active Spare Map:      0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
          Big Spare to Replace Map:  No spares have replaced any drives
          Big Spare Marked OK Map:   0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
    MONITOR AND PERFORMANCE DATA&colon;
       Port 1I, Box 1, Bay 2
          Factory:     Serial #, Firmware Rev, and Mfg/Model #:
             33 4e 50 32 34 36 59 30 30 30 30 30 39 38 31 36      3NP246Y000009816
             51 35 58 4e 48 50 44 37 00 00 00 00 48 50 20 20      Q5XNHPD7....HP 
             20 20 20 20 44 47 30 37 32 41 42 41 42 33 20 20          DG072ABAB3 
             20 20 20 20 00 00 00 00 00 00 00 00 00 00 00 00          ............
             00 00 00 00                                          ....
          Since Power: Serial #, Firmware Rev, and Mfg/Model #:
             33 4e 50 32 34 36 59 30 30 30 30 30 39 38 31 36      3NP246Y000009816
             51 35 58 4e 48 50 44 37 00 00 00 00 48 50 20 20      Q5XNHPD7....HP 
             20 20 20 20 44 47 30 37 32 41 42 41 42 33 20 20          DG072ABAB3 
             20 20 20 20 00 00 00 00 00 00 00 00 00 00 00 00          ............
             00 00 00 00                                          ....
          Serial Number Control:     0x0054
          Firmware Revision Control: 0x0248
          Mfg/Model Number Control:  0x0268
                     Factory          Since Power      Threshold        Control
          Serv. Time 00341415         000001d4         00000000         2104
          Read Blks  0000001788c34d46 00000000000002b1                  0108
          Hrd Read   00000485         00000000         00000000         2104
          Rtry Read  00000000         00000000         00000000         2104
          ECC Read   000000000000000d 0000000000000000 0000000000000000 2108
          Write Blks 00000006c04e371c 0000000000ffcf08                  0108
          Hrd Write  00000000         00000000         00000000         2104
          Rtry Write 00000006         00000000         00000000         2104
          Seeks      0000000000000000 0000000000000000                  0808
          Seek Errs  0000000000000000 0000000000000000 0000000000000000 0808
          Spin Cyls  00000000         00000000         00000000         2104
          Spin Time  0000             0000             0000             2202
          Test 1     0000             0000             0000             0802
          Test 2     0000             0000             0000             0802
          Test 3     0000             0000             0000             0802
          Test 4     0000             0000             0000             0802
          Spare Blks ffffffff         ffffffff                          0a04
          Re-mapped  0000009b         00000000         00000000         2504
          DRQ Tmots  0000             0000             0000             0802
          Timeouts   0000             0000             0000             2102
          Rebuilds   0002             0000             0000             2102
          Spn Retrs  ffff             ffff             0000             2902
          Fl Rd Recv 0000             0000             0000             2102
          Fl Wt Recv 0000             0000             0000             2102
          Format Err 0000             0000             0000             2102
          POST Err   0000             0000             0000             0802
          Drv Nt Ry  00000000         00000000         00000000         2104
          Reallc Abt 00000000         00000000         00000000         0804
          IRQ Gltchs 00000000         00000000         00000000         0804
          Bus Flts   00000054         00000001         00000000         2104
          Hot Plgs   00000000         00000000         00000000         2104
          Tk Rwt Err ffff             ffff             0000             2902
          Rmp Wt Err 0000             0000             0000             2102
          Bg Fw Rev  0000000000000000 0000000000000000                  0848
          Med Flrs   0000             0000             0000             2102
          Hrdw Errs  0007             0000             0000             2102
          Abt Cmd Fl 0000             0000             0000             2102
          Spn Up Fl  0000             0000             0000             2102
          Bd Tgt Cnt 0000             0000             0000             2102
          Pred Fails 00000000         00000000         00000000         2104
          DRIVE ERROR LOG:
             Error Log Header:
                Parameter Length    = 0x14
                Entry Size          = 0x0040
                Current Entry       = 0x1c
                Total Errors Logged = 0x0000021c
             Error Log Data&colon;
    SCSI  CAM   Sense  Sense
    Stat  Stat  Key    Code    Qual   Block(Vl)       Time       Op   Info
    02    04    06     29      02     00000000(0)     002f200b   00   0000
    02    04    06     29      02     00000000(0)     002f477e   00   0000
    02    04    06     29      02     00000000(0)     0030a78b   00   0000
    02    04    06     29      02     00000000(0)     00311fd3   00   0000
    02    04    06     29      02     00000000(0)     00316ebf   00   0000
    00    0a    00     00      00     00000000(0)     00317117   00   0000
    02    04    06     29      02     00000000(0)     0032043a   00   0000
    02    04    06     29      02     00000000(0)     00329e1f   00   0000
    02    04    06     29      02     00000000(0)     0032c9aa   00   0000
    02    04    06     29      02     00000000(0)     0033b5c4   00   0000
    00    0a    00     00      00     00000000(0)     0033e304   00   0000
    00    0a    00     00      00     00000000(0)     0033e430   00   0000
    00    22    00     00      00     3f000000(0)     0033e509   5a   0000
    00    0a    00     00      00     00000000(0)     0033eec2   00   0000
    00    0a    00     00      00     00000000(0)     0033f285   00   0000
    00    0a    00     00      00     00000000(0)     0033f4f2   00   0000
    00    0a    00     00      00     00000000(0)     0033f6d2   00   0000
    00    0a    00     00      00     00000000(0)     0033fe90   00   0000
    00    0a    00     00      00     00000000(0)     0034003c   00   0000
    00    0a    00     00      00     00000000(0)     003402d0   00   0000
       Port 1I, Box 1, Bay 1
          Factory:     Serial #, Firmware Rev, and Mfg/Model #:
             33 4e 50 32 46 41 57 38 30 30 30 30 39 38 33 30      3NP2FAW800009830
             32 39 41 52 00 00 00 00 00 00 00 00 48 50 20 20      29AR........HP 
             20 20 20 20 44 47 30 37 32 41 42 41 42 33 20 20          DG072ABAB3 
             20 20 20 20 00 00 00 00 00 00 00 00 00 00 00 00          ............
             00 00 00 00                                          ....
          Since Power: Serial #, Firmware Rev, and Mfg/Model #:
             33 4e 50 32 46 41 57 38 30 30 30 30 39 38 33 30      3NP2FAW800009830
             32 39 41 52 48 50 44 43 00 00 00 00 48 50 20 20      29ARHPDC....HP 
             20 20 20 20 44 47 30 37 32 41 42 41 42 33 20 20          DG072ABAB3 
             20 20 20 20 00 00 00 00 00 00 00 00 00 00 00 00          ............
             00 00 00 00                                          ....
          Serial Number Control:     0x0054
          Firmware Revision Control: 0x0248
          Mfg/Model Number Control:  0x0268
                     Factory          Since Power      Threshold        Control
          Serv. Time 00055b43         000001d4         00000000         2104
          Read Blks  000000029c28733f 0000000001e70b56                  0108
          Hrd Read   00000000         00000000         00000000         2104
          Rtry Read  00000000         00000000         00000000         2104
          ECC Read   0000000000000000 0000000000000000 0000000000000000 2108
          Write Blks 00000000c7b62ee8 0000000000ffcf36                  0108
          Hrd Write  00000000         00000000         00000000         2104
          Rtry Write 00000000         00000000         00000000         2104
          Seeks      0000000000000000 0000000000000000                  0808
          Seek Errs  0000000000000000 0000000000000000 0000000000000000 0808
          Spin Cyls  00000000         00000000         00000000         2104
          Spin Time  0000             0000             0000             2202
          Test 1     0000             0000             0000             0802
          Test 2     0000             0000             0000             0802
          Test 3     0000             0000             0000             0802
          Test 4     0000             0000             0000             0802
          Spare Blks ffffffff         ffffffff                          0a04
          Re-mapped  00000000         00000000         00000000         2504
          DRQ Tmots  0000             0000             0000             0802
          Timeouts   0000             0000             0000             2102
          Rebuilds   0001             0000             0000             2102
          Spn Retrs  ffff             ffff             0000             2902
          Fl Rd Recv 0000             0000             0000             2102
          Fl Wt Recv 0000             0000             0000             2102
          Format Err 0000             0000             0000             2102
          POST Err   0000             0000             0000             0802
          Drv Nt Ry  00000000         00000000         00000000         2104
          Reallc Abt 00000000         00000000         00000000         0804
          IRQ Gltchs 00000000         00000000         00000000         0804
          Bus Flts   00000004         00000001         00000000         2104
          Hot Plgs   00000000         00000000         00000000         2104
          Tk Rwt Err ffff             ffff             0000             2902
          Rmp Wt Err 0000             0000             0000             2102
          Bg Fw Rev  0000000000000000 0000000000000000                  0848
          Med Flrs   0000             0000             0000             2102
          Hrdw Errs  0000             0000             0000             2102
          Abt Cmd Fl 0000             0000             0000             2102
          Spn Up Fl  0000             0000             0000             2102
          Bd Tgt Cnt 0000             0000             0000             2102
          Pred Fails 00000000         00000000         00000000         2104
          DRIVE ERROR LOG:
             Error Log Header:
                Parameter Length    = 0x14
                Entry Size          = 0x0040
                Current Entry       = 0x1f
                Total Errors Logged = 0x0000001f
             Error Log Data&colon;
    SCSI  CAM   Sense  Sense
    Stat  Stat  Key    Code    Qual   Block(Vl)       Time       Op   Info
    02    04    06     29      02     00000000(0)     00000000   00   0000
    02    04    06     29      02     00000000(0)     00000001   00   0000
    02    04    06     29      02     00000000(0)     00006731   00   0000
    02    04    06     29      02     00000000(0)     00008ea4   00   0000
    02    04    06     29      02     00000000(0)     0001eeb1   00   0000
    02    04    06     29      02     00000000(0)     000266f9   00   0000
    02    04    06     29      02     00000000(0)     0002b5e5   00   0000
    02    04    06     29      02     00000000(0)     0002b83d   00   0000
    02    04    06     29      02     00000000(0)     00034b60   00   0000
    02    04    06     29      02     00000000(0)     0003e545   00   0000
    02    04    06     29      02     00000000(0)     000410d0   00   0000
    02    04    06     29      02     00000000(0)     0004fcea   00   0000
    02    04    06     29      02     00000000(0)     00052a2a   00   0000
    02    04    06     29      02     00000000(0)     00052b56   00   0000
    00    22    00     00      00     3f000000(0)     00052c2f   5a   0000
    02    04    06     29      02     00000000(0)     000535e8   00   0000
    02    04    06     29      02     00000000(0)     000539ab   00   0000
    02    04    06     29      02     00000000(0)     00053c18   00   0000
    02    04    06     29      02     00000000(0)     00053df8   00   0000
    02    04    06     29      02     00000000(0)     000545b6   00   0000

    Hi QUANT,
    Your Proliant server is a commercial product and to get your issue more exposure I would suggest posting in the commercial forums. Here is a link to the Commercial Notebook forum.
    Thank you,
    Please click “Accept as Solution ” if you feel my post solved your issue.
    Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
    Thank you,
    BHK6
    I work on behalf of HP

  • Exit CL_HRASR00_POBJ_WF_EXIT triggered exeception for event STATE_CHG and (target) status READY- ERROR EVENT_RAISED - Error updating the process object

    Hi All
    I have set up a simple custom HCM process and Form regarding Infotype TO CREATE AND CHANGE POSITION. I have checked the process and form consistency and it seems fine. Now when I run the process from HRASR_DT it generates a process number but it also gives an error workflow could not start.I get following error (SWIA log - Step history)
    Executing flow work item - Transaction brackets of the workflow has been damaged
    Exception occurred - Error when starting work item 000000007031
    PROCESS_NODE - Error when processing node '0000000014' (ParForEach index 000000)
    CREATE - Error when creating a component of type 'Step'
    CREATE_WIM_HANDLE - Error when creating a work item
    CREATE_VIA_WFM - Exit CL_HRASR00_POBJ_WF_EXIT triggered exeception for event CREATED and (target) status
    EVENT_RAISED - Error updating the process object
    Executing flow work item - Exit CL_HRASR00_POBJ_WF_EXIT triggered exeception for event STATE_CHG and (target) status READY->ERROR
    EVENT_RAISED - Error updating the process object
    Executing flow work item - Transaction brackets of the workflow has been damaged
    Executing flow work item - Work item 000000007031: Object FLOWITEM method EXECUTE cannot be executed
    Executing flow work item - Error when processing node '0000000014' (ParForEach index 000000)
    Points to be noted:
    1) I have searched few SAP notes such as 1384961(Notes for 6.0.4) but our system is in higher level patch 6.0.5
    2) WF-BATCH have SAP_NEW and SAP_ALL authorization.
    Appreciate your valuable suggestions.
    Thanks
    Ragav

    Hi Ragav
    did you try to debug this? maybe something is missing in config of P&F?
    Since you are on 605, the following note would be there in your system....use it to debug:
    1422496 - Debugging background workflow tasks in HCM P&F
    This will help you find the root cause.
    regards,
    modak

  • Status Ready in BPM

    Hello All,
                    I have created a control step to trigger alert for success condition in BPM after send step.
    When i executed the BPM status ready is showing for the control step in workflow logs.
    Will it get executed? Otherwise is there anything else to be added for this to get executed.
    Thanks in Advance
    Rajesh

    Hi Rajesh,
    That means it is still waiting for condition to be met. Try checking the technical details of the same. you can use Goto->technical details and check where it is waiting.
    Else you can add a switch step in BPM and put the control step in one branch and cancel  in the other . So, in that case atleast one of them will execute and you will come to know what the error is?
    Regards,
    Sachin

  • Workitem in status ready

    Dear Experts,
    I have a workitem (activity step) in status ready. I have bind a webdynpro java application for this in SWFVISU tcode. So once user clicks workitem from portal dynpro java application will open. But workitem in R/3 remains in status ready even after user clicks submit from the java application. So on action submit I need to complete that workitem. Is there any FM to complete a workitem which is in status ready. This workitem is from a task of activity step. This is just a dummy workitem that is I have given a BO method inside it that does not have any code. I use this to start the dynpro java appln alone.
    First i will be using sap_Wapi_write_container FM. Then I will complete the workitem. Then using sap_wapi_read_container I will read the written values. If i use sap_wapi_workitem_complete FM then the written values change back to old values again.
    KR,
    Bharath
    Edited by: bharath padmanabhan on Dec 29, 2009 10:06 AM
    Edited by: bharath padmanabhan on Dec 29, 2009 10:28 AM

    Dear All,
    Thanks a lot for your replies. I have solved the problem. First I set the status of workitem to started and then completed it. Please find the code below.
    CALL FUNCTION 'SAP_WAPI_SET_WORKITEM_STATUS'
    EXPORTING
    workitem_id = lv_wi_id     " workitem id
    status = 'STARTED'
    USER = SY-UNAME
    LANGUAGE = SY-LANGU
    DO_COMMIT = 'X'.
    CALL FUNCTION 'SAP_WAPI_DECISION_COMPLETE'
    EXPORTING  
    workitem_id = lv_wi_id     " workitem id
    LANGUAGE = SY-LANGU
    USER = SY-UNAME
    decision_key = '0001'
    DO_COMMIT = 'X'.
    KR,
    Bharath

  • How to Reprocess Outbound Idocs in Status 02 (Errors)

    Hi,
        I have an urgent problem. How do I re-process an Outbound IDoc in Status '02' (Error Passing Data to Port)
        I have tried reprocessing this IDoc through BD87 using both the options Edit>Process and Edit>Restrict and Process, but it doesn't work
         Please help as we are migrating cutover data from SAP to another system
    Regards,
    Aditya

    Worth to have a look at this thread
    Error handling problem with outbound idoc status 02 and  XML HTTP Port
    Regards
    Vivek
    Reward points for all the useful answers

  • SYSFAIL Error in SMQ1 (Outbound)

    Hi Experts,
    We came across the dumped queues in SMQ1 (Outbound) with SYSFAIL error which were specifically described as: Die laufende Anwendung hat bewußt einen Abbruch mit Kurzdump ausgelöst which means, The current application has deliberately triggered a termination with short dump.
    One example is: CRM_BT_LRP4910739398ZDE1.
    We tried RSQOWKEX to restart the queues but the attempt was unsuccessful.
    Thanks for your help.

    Hi Vinay/Denis,
    Thanks for your inputs.
    We already tried to look for these queues in SMW01 but all of those queues are not found in middleware.
    Is there any other way on how we can proceed?
    Thanks for your prompt response.

  • Backgroud task of a workflow set to status "ready"

    Hi all, We have a worflow working since some years ago and now suddenly one problem has started to ocurr...
    sometimes, one of the backgroud steps of this workflow is not processed in backgroud by WF-BATCH as expected but it remain in status "READY"....this is not intended and what we are expecting is that this task is processed in background without any user input inmediately after the previous task....
    Until today, this task has worked without problems but now we got this task not processed but waiting in status "ready"...this only occurs sometimes, not with all instances of this workflow but only sometimes in a random way....
    I can´t see anything wrong in the template...only thing I see is that this background task is executed right after a "dialog task" where user need to aprove or reject the document in workflow. this "dialog step" use the standard task "TS00008267" (generic decission task) as base and this standard task has "latest end" setted (I don´t know if this can be the problem or always has been in this way with this "latest end" active...)
    any tips???? someone with same problems????
    Thanks in advance....

    hi Rob, first at all, thanks for your fast reply, much appreciated mate....
    surfing this forum I just found this post () , I think, is same problem, related to RSWERRE program jobs....
    I´ve seen that all of those background workitems in status "ready" that we expected to be processed automatically are from same day, and in that day we suffered a problem related to jobs system so I think that is the key of my problem....no wrong workitems in status "ready" others days than that one when we suffered that problem with jobs systems so pretty sure this is my case...
    anyway, thanks a lot for your tips...if I found that my problem continues I will be sure of check what you are pointing me...
    Thanks.
    Miguel.

Maybe you are looking for

  • HT1414 How do I find out a forgotten passcode?

    I have followed the directions about using I-Tunes and everything appeared to be working until I got the message that nothing would happen until I put the Passcode in. 

  • Keeping e-mail alarms in the bg?

    Not sure if this is an iCal question, a Mail question, or a Leopard question -- all I know is it stumped the Genius at my local Apple Store, so I'll try here first: Is there a way to have iCal-trigged alarm e-mails to be sent in the background, inste

  • Formatting the date in an output file

    Greetings Abapers I am writing a program which outputs a file in csv format. Currently the date is shown in the file as 20080609000000 but i would like it to be shown as 09.06.2008. Help anyone?

  • How to sync iPhone music from 2nd Mac? (don't read this if you own 1 Mac)

    If you don't own two Macs, please don't try answering this post with guesses. I need to find someone with real world experience to solve this problem: My contacts and Calendar are on my laptop. My music and videos are on a Mac Pro. I have disabled au

  • Educator's discount - Can I receive even though I'm in South Korea?

    Hello!  I'm a university professor in Seoul, South Korea and would like to get the English version of Captivate using the educator's discount.  This educator's version is offered on the U.S. site.  I don't know if they offer a similar discount for Ko