CLEAN_REQREQ_UP

Hi SRM experts,
Can you please tell me how the shopping cart is getting replicated to backend using CLEAN_REQREQ_UP through RFC call. I want to which BAPI it calls & some other details.
Thanks & Regards,
Ajay

Along the same lines as this question, what is the different doc types seen in the BBP_DOCUMENT_TAB.  We are seeing alot of AV Doc types which is causing or the cause of the Clean_REQREQ_UP job running slower. 
We also see TR and IM.  usually, the IM are what clears when the REQREQ program runs.
Yvette Leaman
Edited by: Yvette Leaman on Dec 29, 2008 8:08 PM

Similar Messages

  • Logical system in CLEAN_REQREQ_UP and BBP_GET_STATUS

    Hi experts,
    Just a very simple question : do you confirm the logical system we have to put in CLEAN_REQREQ_UP and BBP_GET_STATUS variants are that of SRM?
    Thanks in advance.

    Hi,
    CLEAN_REQREQ_UP:
    It checks whether the backend documents (namely-PR/PO/RES) have been created in the backend systems. Deletes obsolete table entries in SRM as well as updates document numbers in the Shopping Cart. You can't process the SC in SRM until this update is complete.
    BBP_GET_STATUS_2:
    It ensures that the information on the back-end documents is up-to-date. Retrieves the updated information from the Back-end systems (for example PO number after it was converted from a PR)
    since both the reports checks and picks up data from backend system, we need to specify RFC for backend systems only.
    -rgds,
    Ravi

  • Job CLEAN_REQREQ_UP and BBP_GET_STATUS_2 does not update SC in SRM With PO

    Hello,
    We are on SRM 5.0 Classic scenario  R3 SAP  ECC 6.0. we recently had a stackupgrade for all our different components.
    Aswe are in a classic scenario we get a prucahse requisition after a shopping cart is approved. The purchaser then creates a purchase order and the program  BBP_GET_STATUS_2 and CLEAN_REQREQ_UP updates the shopping cart  with the PO information.
    For these 2 programmes we have created one Job. The problem  that we now encounter is that the job doesn't update the Shopping cart with the PO information. Only the purchase reuiqisition is visisble. If i go to transaction BBP_PD for that shopping cart i see Item in transfer process marked red. From  BBP_PD I can run BBP_GET_STATUS_2 and CLEAN_REQREQ_UP and the nthe shopping is updated.
    So to summarize: The jobs (BBP_GET_STATUS_2 and CLEAN_REQREQ_UP ) do not update the shopping cart but running BBP_GET_STATUS_2 and CLEAN_REQREQ_UP  manually the Shopping cart is updated.
    The users who running the jobs seem to be ok.
    Any idea ?
    Thanks

    Hi,
    Check this.
    In the backend system, you activate the application SRMNTY in table TBE11 using transaction FIBF so that the purchase order follow-on data is transferred from the SAP backend to the SRM system. In this way, the SRM system is notified when follow-on documents are created in the backend system.
    Check teh variant, Check if the Backend system has been changed, Run BDLS if changed
    regards,
    MRao
    Edited by: Mahesh Rao T.C on Oct 14, 2010 12:31 PM

  • Will BADI BBP_CREATE_REQ_BACK be called by program  CLEAN_REQREQ_UP?

    SRM gurus,
    We are in SRM 4.0 (SRM_SERVER 500).
    I use t code SE38 to run program CLEAN_REQREQ_UP in SRM to convert shopping carts into purchase requisitions in R3 backend. I put our customized codes in BADI BBP_CREATE_REQ_BACK and I thought that this BADI will be called when a shopping carts was converted into a purchase requisition.
    I put a ABAP statement 'break-point.' in the BADI but the program CLEAN_REQREQ_UP did not stop at the BADI BBP_CREATE_REQ_BACK at all.
    Will BADI BBP_CREATE_REQ_BACK be executed when the program  CLEAN_REQREQ_UP runs?
    If the BADI will be called, how can I stop the program when the BADI was executed, so I can debug the codes?
    I did put a hard code statement "break-point." in there but it did not work.
    If the BADI will not be called by the program  CLEAN_REQREQ_UP, when the BADI be called?
    Thanks in advance!
    Fisher Li

    I use t code SE38 to run program CLEAN_REQREQ_UP in SRM to convert shopping carts into purchase requisitions in R3 backend.
    I don't think this report will create PR for your SC.
    Will BADI BBP_CREATE_REQ_BACK be executed when the program CLEAN_REQREQ_UP runs?
    I don't believe so.
    If the BADI will not be called by the program CLEAN_REQREQ_UP, when the BADI be called?
    It's called within a few steps down the stack of FM META_REQUISITION_CREATE.

  • SRM 5.0: CLEAN_REQREQ_UP, BBP_REQEQ_TRANSFER and Webmonitor

    Hi SDN,
    we are on SRM 5.0 SP15. Classic Scenario with MM Backend.
    We have some issues with the webmoitoring. We have the clean job clean_reqreq_up running in 10 minutes intervals. Also we have bbp_get_status_2 every 20 minutes.
    Quite often we have red traffic lights in the webmonitor because users in the backend run transaction MB1A - Material withdrawal (referred to reservations) this leads to SM12 locks. So if now somebody sends a shopping cart from SRM with the same material, we get the backend applic. error: material locked by user xy.
    But even if the users leaves MB1A withdrawal transaction and in SM12 we can see in the backend, that the lock disappears, still the shopping carts keeps hanging in srm. Only via manual action we can transfer the shopping cart posions again. Before the users gets an error during transmission in the status view.
    In SPRO we have set SPOOL_LEAD_INTERVALL and SPOOL_MAX_RETRY. hel.spa.com says we have to delete SPRO entries if we have the clean job running - is that so? look at:
    [http://help.sap.com/saphelp_srm50/helpdata/de/24/64474ecfaf11d2b463006094b92d37/frameset.htm]
    I also noticed, that I can transfer shopping carts manaully vis FM BBP_REQREQ_TRANSFER. When calling afterwards clean_reqreq_up, I get the status view on srm side ok and then I can see there follow on documents. Still the webmonitor does not react and remains red.
    Can somebody spread some light on this?
    kind regards,
    matthias

    Define Objects in Backend System (Purch. Reqs, Reservations,
    You perform this step only if you create your Materials Management documents in a backend system.
    You specify the documents that are to be created in the backend system for a requirement coverage request.
    The following documents can be created:
    Purchase requisition
    Purchase order
    Reservation
    You enter a product category (such as office supplies, or hardware) and/or an organizational unit. The organizational unit contains the purchasing group that is responsible for procuring products in this category.
    You can enter the product category generically, such as Office*.
    Note
    The backend system is determined  using the product category in the requirement coverage request item. The item also contains the organizatinal unit.
    You can use the Business Add-In BBP_TARGET_OBJTYPE if you wish to implement a different logic for creating documents in the backend system.
    Example
    If purchasing group 01 wants to procure materials from the category Raw Materials, a reservation is to be created every time.
    If materials in the category PC are to be procured, a purchase requisition is to be created every time.
    Activities
    1. Enter the organizational unit and/or the category.
    2. Enter a source system.
    3. Choose the procurement type.
    Reservation if stock is available, otherwise external procurement
    The system creates a reservation if the material is subject to inventory management and sufficient stock quantity is available in the warehouse on the requested date.
    Always reservation for materials subject to inventory management
    The system creates a reservation if the material is subject to inventory management, irrespective of whether stock is available.you knew tis ver well.
    mutu

  • Run CLEAN_REQREQ_UP withou logical system

    Dear Experts,
    1) I created some POs from the SOCO.
    2) I deleted the POs and the SC items didn't come back to the SOCO.
    3) I run the CLEAN_REQREQ_UP report with a logical sysem and nothing happened.
    4) I run the CLEAN_REQREQ_UP report without a logical sysem and the SC items came back to the SOCO.
    Do you see some problem to run this report without a logical system?
    We work with SRM 5 and extended classic scenario.
    Best Regards,
    Eyal Weinreb
    HP

    Hi Jay.
    We have the same issue in this moment between our SRM 7.0 EHP 1 y the back-end system SAP ERP ECC 6.0.
    Is the only solution running the report CLEAN_REQREQ_UP without "logical system" ?.
    Regards,
    Martín.

  • CLEAN_REQREQ_UP  SRM5.5 - Question re field entry

    Hi
    Within SRM5.5 for clean_reqreq_up, in the classic scenario,  does the logical system field require an entry ie the backend system or should it be left blank ?
    The reason for the question is that if a held LOCAL PO is deleted,  the end users check status does not show this when the clean program is run with the backend logical system input, but if left blank, the status does show in the check status graphical view.
    We have always run clean program with the backend system in on versions 2.0c, 3.5 and 5.5 and we had no issues, but after a few support packs, this is now a minor problem.
    OSS message was raised, but it seems that we may not now need a logical system in the field.
    Can anyone advise on how the job is recommended to be set for the logical system.
    Thanks

    yes. i schedule this job for every 3 minutes .
    if you have more than one backend system it is definetly required.
    even you can create a variant and mention logical system if you want.
    Muthu

  • CLEAN_REQREQ_UP dumps with "LOG_NOT_FOUND" exception

    Hi all,
    When I run the CLEAN_REQREQ_UP program, I get a dump with exception "LOG_NOT_FOUND" from the function module BBP_PD_LOG_DELETE. I saw a OSS note 1121892 but the symptom says
    "You deleted some Logs with the Transaction SLG2. Afterwards you run the report CLEAN_REQREQ_UP which is ending in dumps with the Function Module BBP_EV_API_EXCEPT_SAVE. The dumps are regarding missing Logs "Exception condition "LOG_NOT_FOUND" raised.    ".
    We didn't touch the SLG2 transaction. But there was a network problem and the application server and database connection was reset. Any idea why this is happening. How to avoid the dump and run the CLEAN_REQREQ_UP program.
    Thanks and Regards,
    Asha

    Hi
    plz refer this note.
    Note 1163947 - Dump LOG_NOT_FOUND in BBP_PROCDOC_SAVE
    regards
    Muthu

  • CLEAN_REQREQ_UP is Dumping

    Hi All
    When I run the CLEAN_REQREQ_UP program, I get a dump with exception "LOG_NOT_FOUND" from the function module BBP_PD_LOG_DELETE. I saw a OSS note 1121892 but the symptom says .
    OSS Note : 1121892 "You deleted some Logs with the Transaction SLG2. Afterwards you run the report CLEAN_REQREQ_UP which is ending in dumps with the Function Module BBP_EV_API_EXCEPT_SAVE. The dumps are regarding missing Logs "Exception condition "LOG_NOT_FOUND" raised. ".
    We didn't touch the SLG2 transaction. But there was a network problem and the application server and database connection was reset. Any idea why this is happening. How to avoid the dump and run the CLEAN_REQREQ_UP program.
    We also check the table BBP_DOCUMENT_TAB, its having so many entries And we checked it RZ20 , Nothing seems to wrong there also .
    Can anybody give me some pointer for the same .

    thank you

  • Scheduling background jobs like clean_reqreq_up, bbp_get_status_2..

    Hi,
    Being am a trainee am little bit confused of scheduling background jobs...
    Among them clean_reqreq_up, bbp_get_status_2 are the two which i didnt understand ...
    Can anyone plz help me in that..
    Thanks
    guna

    Hi Sekhar,
    Check the below links for proper explanation of required terms
    1. CLEAN_REQREQ_UP
    http://help.sap.com/saphelp_srm70/helpdata/EN/4c/ea243f043f48a1a74ec6ae5f59d5af/frameset.htm
    2. bbp_get_status_2
    http://help.sap.com/saphelp_srm70/helpdata/EN/47/83d80296a2500be10000000a421937/frameset.htm
    Regards,
    Jitesh Talreja

  • Diff between programme BBP_GET_STATUS_2  & CLEAN_REQREQ_UP in SRM7.0

    Hi Experts ,
    We have ECC6.04 with SRM 7.0 with Classic Scenarion
    I am confused over exactly what BBP_GET_STATUS_2  do in SRM ?
    I believe CLEAN_REQREQ_UP  update the SC with follow on document i..e Classic PO....
    and BBP_GET_STATUS_2  update the entries in BBP_DOCUMENT_TAB..but not getting exactly what is does..since if we change qty in Classic Po ..it automatically updates automatically  in SC follow on document...if we Craete GR in ECC it updates automatically  in SC follow on document...
    Can anyone please suggest me exactly what BBP_GET_STATUS_2  do in SRM  ( what is exact  diff between both )?
    Thanks
    NAP

    Hello,
    Report : BBP_GET_STATUS_2
    Function : This reports updates the  requirement coverage requests (Shopping carts) to ensure that information on the status of backedn purchase requisitions, purchase orders, and reservations is up-to-date.
    You should schedule this report to run daily in the SRM server system.
    Report : CLEAN_REQREQ_UP
    Function : Interval for update check.
    Updating of documents (purchase requisitions, purchase orders, reservations) is executed asynchronously in the backend system. You can only process the requirement coverage request in the SRM server system further after the update has been carried out. At the interval defined by you in Customizing, the system checks whether the documents have been updated and thus if you can further process the requirement coverage request.You should schedule this report periodically.
    Hope this helps.
    Best Regards,
    Rahul

  • Difference between BBP_GET_STATUS_2 and CLEAN_REQREQ_UP reports

    Could someone explain in simple way what is the difference between BBP_GET_STATUS_2 and CLEAN_REQREQ_UP reports? I have read the differences in standard documentation but it is a little confusing.
    Thanks!
    Regards,
    Madhur

    Hi
    CLEAN_REQREQ_UP (Cleaner Job)
    You can use this function for document types Shopping cart, (Local) Purchase Order, Confirmation, and Invoice to trigger a synchronization with the associated documents in the back-end system. The system checks whether and how the (follow-on) documents were posted in the back end, and updates the object link and references, as well as the document status.
    A job (background processing) is generated for the program CLEAN_REQREQ_UP. When this is run, the system queries a database table containing the transfer information of the documents to the back end. The entries are checked with the data of the respective back-end systems. If the back-end transfer is successful, the respective entries are deleted and the prerequisites for further processing are created.
    BBP_GET_STATUS2 (Status Job)
    The status job was created by SAP to update the EBP system with data such as purchase requisition number, purchase order number, goods received or invoices recorded manually in R/3, etc. The report should not be run on a frequent basis at short intervals unless the order count from EBP to R/3 is not that high. Otherwise, a recommended interval for running the report is approximately every hour. Basically the schedule times depend on your business requirements.
    Until this job runs, the user will not see the number of the backend document created in R/3 for a particular shopping cart in the history tab of the check status transaction.
    Some more information :
    Go to:
    SPRO->IMG->Integration with Other SAP components->Advanced Planning and
    Optimization->basic Settings for the Data Transfer->Change Transfer->
    change Transfer for Transaction Data->Active Online Transfer using BTE
    Here you should maintain the application 'SRMNTY' with active flag.
    Once this customizing is enabled, whenever a follow-on document
    (either confirmation or invoice) for an extended classic PO is created
    in the backend R/3 system, the R/3 system communicates to the SRM system
    by creating an entry in the table BBP_DOCUMENT_TAB for this PO.
    The item level of the SRM PO has fields to store the actual quantity
    and values entered for the corresponding confirmations and invoices.
    After that, run the reports CLEAN_REQREQ_UP and BBP_GET_STATUS_2.
    When the report CLEAN_REQREQ_UP runs this will update the
    PO with statistical information. With the latest information in
    BBP_PDIGP table (statistical information) the query should work fine.
    Summer

  • Difference between BBP_GET_STATUS_2 and CLEAN_REQREQ_UP

    Hi experts,
    Could you point out the difference between BBP_GET_STATUS_2 and CLEAN_REQREQ_UP in SRM? What is its significance both in classic and extended classic scenario?
    Thanks,
    Madhur

    Hi,
    CLEAN_REQREQ_UP:
    It checks whether the backend documents (namely-PR/PO/RES) have been created in the backend systems. Deletes obsolete table entries in SRM as well as updates document numbers in the Shopping Cart. You can't process the SC in SRM until this updae is complete.
    BBP_GET_STATUS_2:
    It ensures that the information on the back end documents is upto date. Retrieves the updated information from the BE systems (for exaple-it retrieves PO number after it was converted from a PR)
    Above reports are mandatory both both Classic and ECS.
    Regards,
    GM

  • BBP_GET_STATUS_2 and CLEAN_REQREQ_UP

    Hi all,
    We need to delete the old insatnces of the jobs which have the reprts BBP_GET_STATUS_2 and CLEAN_REQREQ_UP running  in SM37.
    What is the frequency at which the old isnatnces for these jobs should be deleted so that there are no spool requests which clogged up in the system?
    e.g. all instances of the jobs running which are month old should be deleted?
    Is there any std program which autoamtically deletes OLD SPOOL REQUESTS in the system based on the time interval specified?
    Pls advise.

    Hi,
    We use report RSPO0041 to delete old spool requests. We delete everything older than 10 days.
    Regards,
    Timo

  • CLEAN_REQREQ_UP not updating the status of all confirmations.

    Hello All
    We have scheduled the cleaner report as a job running every 2 minutes.
    This job changes the status of the confirmations from 'Approved' to 'Transmit to backend system'.
    However the job doesn't process a few confirmations randomly.
    In such confirmations, the status remains as ' Approved'.
    There is no issue for replication for such confirmations in the backend.
    This happens on 30 % of all confirmations.
    All these confirmations are coming from an interface and the following sequence occurs
    1) MFG Batch user creates Confirmation in SRM
    2) WF Batch user sets the status as Approved
    3) Job Batch user( CLEAN_REQREQ_UP) updates the status to 'Transmit to Backend system'
    I am trying to find out why the job wont process these confirmations.
    Regards
    Kedar

    HI
    for eg,
    when we do confirmations in SRM
    message type MBGMCR and RFC takes GOODS CONFIRMATION / SERVICES  data to .ECC
    and BBP_GET_STATUS_2 job bring the informations of ECC GR status and update in SRM.
    bbp_docuemnt_tab get entries of srm confirmation data and clears clen req up table (po+confirmation number).
    clean job must clean this PO+confirmation line in the bbp_docuemnt_tab table.
    check your PO number in BBP_DOCUMENT_TAB TABLE.
    i need to check it up.
    br
    muthu

  • Clean_reqreq_up and BBP_get_status_2

    I am bit confused about the use of these two programs Clean_reqreq_up and BBP_get_status_2.
    What I understand from the different forums i read is that clean_reqreq_up creates the PO in the backend (classic scenario) after the shopping cart is approved and BBP_get_status_2 updates the shopping cart with the PO number so that the SC can be processed further( for goods confirmation).
    Am I right gurus? If no , please illustrate with an example as above
    Thanks in advance

    Explanation :
    The CLEAN_REQREQ_UP  and BBP_GET_STATUS2 jobs will be configured to run in each EBP client to synchronize status data between EBP and R/3.
    CLEAN_REQREQ_UP (Cleaner Job)
    You can use this function for document types Shopping cart, (Local) Purchase Order, Confirmation, and Invoice to trigger a synchronization with the associated documents in the back-end system. The system checks whether and how the (follow-on) documents were posted in the back end, and updates the object link and references, as well as the document status.
    A job (background processing) is generated for the program CLEAN_REQREQ_UP. When this is run, the system queries a database table containing the transfer information of the documents to the back end. The entries are checked with the data of the respective back-end systems. If the back-end transfer is successful, the respective entries are deleted and the prerequisites for further processing are created.
    BBP_GET_STATUS2 (Status Job)
    The status job was created by SAP to update the EBP system with data such as purchase requisition number, purchase order number, goods received or invoices recorded manually in R/3, etc. The report should not be run on a frequent basis at short intervals unless the order count from EBP to R/3 is not that high. Otherwise, a recommended interval for running the report is approximately every hour. Basically the schedule times depend on your business requirements.
    Until this job runs, the user will not see the number of the backend document created in R/3 for a particular shopping cart in the history tab of the check status transaction.
    Configuration :
    Go to:
    SPRO->IMG->Integration with Other SAP components->Advanced Planning and
    Optimization->basic Settings for the Data Transfer->Change Transfer->
    change Transfer for Transaction Data->Active Online Transfer using BTE
    Here you should maintain the application 'SRMNTY' with active flag.
    Once this customizing is enabled, whenever a follow-on document
    (either confirmation or invoice) for an extended classic PO is created
    in the backend R/3 system, the R/3 system communicates to the SRM system
    by creating an entry in the table BBP_DOCUMENT_TAB for this PO.
    The item level of the SRM PO has fields to store the actual quantity
    and values entered for the corresponding confirmations and invoices.
    After that, run the reports CLEAN_REQREQ_UP and BBP_GET_STATUS_2.
    When the report CLEAN_REQREQ_UP runs this will update the
    PO with statistical information. With the latest information in
    BBP_PDIGP table (statistical information) the query should work fine.
    Summer

Maybe you are looking for