RFQ Msg Status is "Not Processed"

HI
If the message was processed successfully, the status is set to '1' and if an error occurs, the status is set to '2'. Status '0' usually means that the processing program has not yet been started (if the message is to be processed manually, for example).
In my RFQ the processing status is "0" means " Not Processed"
In the msg status a "traingle button" is thr instead of the "Green Button"
How to make this processsed...
Vijay

Hello,
Print the RFQ in ME9A transaction.
Regards,
Shailesh

Similar Messages

  • Idoc in 53 status but not processed completely. Missing authorisation error

    Hi ,
    Some of the ORDER Idocs are in 53 status, but the orders are not processed successfully and no PO created for these Idocs.
    They got below warning message when I checked in WPER transaction code.
    " Missing authorization: Purchase Order Create Purchasing Grou 110 " - "Workitems (tasks) were created for this IDoc"
    This is happening once in a while for some of the idocs. Remaining all idocs are posting successfully.
    These IDOCu2019s are processed via user background. Not sure why we have authorisation issues as this user has SAPALL. Any ideas?
    Thanks
    Deepthi.

    done.

  • Idocs neding in 64 status and not processed further

    Hi
    We have inbound idocs of FIDCC2 message type, which are set to be triggered immediately. However we have noticed that sometimes (not always) these idocs are in 64 status and are not processed further. We have to manually reprocess them.
    What could be the problem? Where should we start investigating?
    Any help would be appreciated.
    Thanks
    Mick

    I think the comment by Gautham Vangaveti  is probably correct.
    We hit the same issue occassionally.  We have IDOCS as trigger immediately, but at the time they try to process, there are no available work processes which can handle the IDOC and they sit at status 64.
    There is an oss note 1333417 which describes the situation
    https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1333417
    And unhelpfully suggests changing over to processing by batch job, which is not always appropriate.
    It may be worth enlisting help from you Basis team to try and indentify if those going to status 64 are occuring at the same time each day, and maybe looking to see what other processes are running at that time.  If the load on the system can be managed then the problem may go away, it did for us.
    Otherwise, Basis may be able to increase the number of work process which may also resolve the issue.

  • Idoc in 53 status but not processed completely.

    Hi ,
    Some of the ORDER Idocs are in 53 status, but the orders are not processed successfully and no PO created for these Idocs.
    They got below warning message when I checked in WPER transaction code.
    " Missing authorization: Purchase Order Create Purchasing Grou 110 " - "Workitems (tasks) were created for this IDoc"
    This is happening once in a while for some of the idocs. Remaining all idocs are posting successfully.
    Any idea what might be the reason? 
    Thanks
    Deepthi.

    Hello,
    This seems to be an Authorisation issue, Kindly check for Purchasing Group 110, who are all assigned Buyers...
    Then for those Buyers.. you can check what authorization is missing from Su53..
    Compare with those who has authorisation to create PO Vs who does not have ..
    you will have to provide the same authorisation to those users
    Thanks and regards
    PJ

  • Status clsd not unique (Selection via input help (F4) only) -COOIS

    Hi all,
    We doing upgradation 4.7E to Ecc 6.O
    In coois , When we enter system status as 'clsd' , system showing error msg
    Status clsd not unique (Selection via input help (F4) only)
    Message no. COIS054
    Why this error occurs.. how to solve this???
    looking for answers..
    Thanks in advance..

    Please read OSS note 1377678.

  • Email/print in status "Not processed" when RFQ is published

    Hello,
    We are running SRM 5.0.
    We have set up the event schema for BUS2200 (RFQ) to react on events: PUBLISHED, PUBLISHED_AGAIN etc. And assigned the event schema to RFQ's transaction types, eg BID.
    However, when an RFQ is published, the email is not sent to vendor (whose default medium is MAI) or printed on vendor's default printer (if the medium is set to PRN). The output log under bidder/bids tab shows something like :
    Status: Not processed       
    Medium: Print      
    When I clicked on the action button "Output pushbutton", the status would be changed to "Successful" and the email would be sent or the print job would be printed then.
    I have checked the PPTTRIGG table and all the entries in there are of DISPATCH = 1 or 4. Not 3, which seems to indicate an "immediate processing".
    My question is how I would configure the system so that the email/print when the RFQ is published could be processed immediately.
    Thanks.

    Hello Masa,
    I realized it as well. I was then a little puzzled why SRM didn't allow "immediate processing" for the "processing time" parameter in the action definition. Do you know if there is a particular reason for that?
    Thanks,

  • RFQ Message Error " Not Processed"

    HI
    If the message was processed successfully, the status is set to '1' and if an error occurs, the status is set to '2'. Status '0' usually means that the processing program has not yet been started (if the message is to be processed manually, for example).
    In my RFQ the processing status is "0" means " Not Processed"
    In the msg status a "traingle button" is thr instead of the "Green Button"
    So that we can not able take print out in ME9A also not able see print preview thro ME9A
    How to make this processsed...
    Vijay

    check if the RFQ contain release strategy and alrady released for output.
    you can check the print preivew in ME4N.

  • IDOC is not processing in R/3 with status 64(Urgent)--Production issue.

    Dear Folks,
    Here we are implementing MIRROR sytem for data extraction in to BIW.
    I had gone through the steps in PDF file(How to minimize down thime for Delta Initialization) which has given by SAP.
    These are following steps I had performed in BW production
    1. Using RSADMIN transcation- Assigned one user as a Debugging user.
    2. With the Debugging user Created one infopackage on Purhcasing ITM datasource--
        In data selection tab, I given date as from 2002 to 2003
        In Update tab, I selected update mode as Initialize Delta process-               without data transfer and Uncheck Update Data in master   system immediately
       In schedule tab I selected option Start Data load immediately then Start extraction.
    3.Data was requested and It was intialized properly with green status 1 from 1 Records.
    4. In details tab Request, Extraction, transfer(IDOC and TRFC), Processing everything in Green color.
    5.As per document I have checked in R/3 for IDOC with status 64 using transaction BD87/WE05
    Problem is that IDOC is not processing in R/3 system. for that IDOC I have checked in BW montior screen using the option <b>IDOC list in Source sytem</b>, here also it is not showing any IDOCs.
    Please let me know why BW sytem is not sending any IDOCs to source sytem.Is there any settings I could have miss in BW aswell as in R/3 system.
    Note: In BW production I successfully loaded master data from R/3. aswell as I triggered infopackage-Initialization with data transfer, it is showing IDOC number properly in R/3 system.
    Points is Assured for all replies.

    Hi,
    - check you RFC destination (normal test + authorization test)
    - Check you partner profiles in WE20 and its ports WE21
    - from the source system tree (RSA13) right click your source system and perform a check
    - the best is to restore your source R/3 source system from BW (right click on it ans select RESTORE); you'll need to be able to log in the source system as an admin as well as opening the source system for customizing in SCC4 so that BW can recreate the correct partner parameters automatically; the best is to do that with your basis group.
    hope this helps,
    Olivier.

  • XML failure with ASN no Process DELIVERY_INFO_GR for ASN in status is not allowed

    Hi All,
    In production , we are having many XML failures while sending inbound delivery to SNC from ECC.
    In SXMB_Moni,  ASN XXXX: Process DELIVERY_INFO_GR for ASN in status is not allowed. Becasue ASN is not exist in SNC but in ECC GR status is complete.
    Please help to resolve the same.
    Regards,
    Sheetal

    Hi,
    Please go the tcode CO02 and click on functions and select the restrict processingand click on unlock
    the reason may be tht some might have locked the produvtion order ,
    hopw it wud have answered ur question.
    rewards if it is useful
    Shawn

  • SQL Developer, Deploy Cloud Cart Status is at Approved for a long time and not moving forward i.e. not processing.

    SQL Developer, Deploy Cloud Cart Status is at Approved for a long time and not moving forward i.e. not processing.
    Please help.
    Thanks
    Srinivas

    Hi Gustavo,
    It appears your Service SFTP user was not created correctly. Please contact support and mention the fact that your Service SFTP user appears on Security/Users tab and not on Security/SFTP Users tab.
    Vlad

  • WIP status (RESA) not updated for process order with co-product

    Hi,
    We are facing the scenario below, please confirm whether item 2 behaviour is standard SAP.
    1. Process order with settlement rule MAT - after WIP calculated, status RESA is updated & FI document it posted.
    2. Process order with settlement rule OIT (co-product) - after WIP calculated, status RESA not updated & FI document posted.
    Thank you.

    Self found answer

  • IDOC status 64 not getting processed.

    Hi Gurus,
          I have a problem where IDOC's with status 64 are not getting processed via background job. the IDOCs weere getting processed with the background job till today evening, but suddenly no changes were made and the processing of IDOC's with status 64 has stopped and they keep filling up, when i checked the log of the Background job it says finished, and the log has the following information,
    17.09.2009 19:05:23 Job started                                                                   00           516          S
    17.09.2009 19:05:23 Step 001 started (program RBDAPP01, variant POS_IDOCS, user ID SAPAUDIT)      00           550          S
    17.09.2009 19:05:25 No data could be selected.                                                    B1           083          I
    17.09.2009 19:05:25 Job finished                                                                  00           517          S
    Kindly advise on this.
    Regards,
    Riaz.

    When i process the IDOC's using BD87, they gets processed wiwth out aany issues no dump is displayed, idoc gets a status 53 after processing via BD87.
    There is another problem how ever there are other jobs scheduled to run in the background other than this background job which are getting cancelled and have two different error logs for different jobs they are as follows.
    1) 18.09.2009 02:00:06 Job started                                             00           516          S
    18.09.2009 02:00:06 Logon not possible (error in license check)             00           179          E
    18.09.2009 02:00:06 Job cancelled after system exception ERROR_MESSAGE      00           564          A
    2) 18.09.2009 00:55:27 Job started                                                          00           516          S
    18.09.2009 00:55:27 Step 001 started (program RSCOLL00, variant , user ID JGERARDO)      00           550          S
    18.09.2009 00:55:29 Clean_Plan:Gestartet von RSDBPREV                                   DB6PM         000          S
    18.09.2009 00:55:29 Clean_Plan:beendet                                                  DB6PM         000          S
    18.09.2009 01:00:52 ABAP/4 processor: DBIF_RSQL_SQL_ERROR                                00           671          A
    18.09.2009 01:00:52 Job cancelled                                                        00           518          A
    This is a production server and the Licence is valid till 31.12.9999, and has no issues with the license.

  • PO output status not processed

    Hi,
    I am trying to print PO using output type NEU and ZNEU (copy of the NEU) with medium 1-print, communication method filled with required information and also further data with 4-print immediately.
    After saving it, the status of the PO in PO output showing yellow-not processed and also it is not seen in ME9F transaction without process/ with process.
    Can any one help me understanding why it is happening. or any customization is required to avoid this situation.
    Thanks in advance!
    Karun

    Hi Revi,
    Thanks for the reply but what is the link of release strategy with PO output processing.
    Best regards,
    Karun

  • Report RBDAPP01 not processing IDocs in status 51

    Hello guys,
    I have a problem with the execution of some Inbound Idocs using program RBDAPP01.
    Now the Idoc is executed in background with a job. Sometimes we have some locks because we receive idocs going to the same order, and then remain in status 51.
    In the variant of the job we filled to execute Idocs with status 64 and 51, but the idocs that remain in status 51 are not processed, at the end we have to do it manually.
    There is no parallel processo to avoid the locks.
    Do you know how we can solve it?
    Many thans in advance.
    Regards,
    Xavi.

    i do have the same problem. is there an solution to this?

  • Update Tasks remain in status = init / started forever. Doest not process

    Hello Everyone,
    We have the FM ME_DB_UPDATE_INFORECORDS called in update task from one of our program
       CALL FUNCTION 'ME_DB_UPDATE_INFORECORDS' IN UPDATE TASK
          EXPORTING
            i_changedocument = c_upd
          TABLES
            db_eina_u        = li_eina
            db_eine_u        = li_eine.
        COMMIT WORK.
    But all these calls does not process. it queues up in SM13 and uses up all update WP and affects the whole system.
    The update records in SM 13 stays with status init or started with the enqueue locks. This results in unresolved table locks on the EINA table.
    The concerned program generates multiple of these update requests with results in piling up of unprocessed such update requests.

    Hello,
    I only suggested SM12 because you said "I feel there is an enqueue problem".
    I would just look for any locks, if you can reproduce the problem. It depends on the ones your method uses.
    Can you tell if the method has been run successfully for those In Process steps? If so, you could try a Complete Manually.
    regards
    Rick Bakker
    hanabi technology

Maybe you are looking for

  • 'access denied' when opening from Office

    Hello, I've experienced this 'access denied' message too. Now I realized that when opening AdobeReader manually all works fine. But when Reader is closed and is opened by Office after saving as PDF file - it still shows this error message. There's no

  • 1sip cost cener report update

    Hello In FI we change numbers of all vendors accounts, to correspond to concern accounts. But funny thing is, in standard report for cost centers (1sip),  old vendor accounts are showing up (offsetting account ) that were booked before the change. Is

  • How i reduced by 10 times the size of imovie Thumbnails

    hi, as you may know imovie produces huge movie thumbnails file that appears to be encoded in this format: Apple Photo - JPEG, 160 x 90, Millions 16-bit Integer (Big Endian), Stereo, 48.000 kHz it's there just to allow the timeframe to be animated whi

  • I'ma newer

    when i connect as hr/hr@orcl an error msg appear saying "TNS:listener does not currently know of service requested in connect descriptor" what i can do

  • How do I update LoginModule's shared state (wildcards)?

    In the API definition for interface javax.security.auth.spi.LoginModule, the prototype for initialize is as follows: public void initialize(Subject subject, CallbackHandler ch, Map<String, ?> sharedState, Map<String,?> options);I can believe that 'op