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

Similar Messages

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

SRM program running too long BBP_GET_STATUS_2 and is locking carts

Program BBP_GET_STATUS_2 appears to be running for more than 7-8 minutes at a time, and apparently is locking carts (especially those that buyers are in the process of approving)/
The variant we are using is wide open (i.e. there are not selections) what can we do to ensure that it is not looking at every single cart item and only addressing those that are open?
please advise, we are using SRM Server 50 EBP 40, on SAP 47,
Thank you.
Bill

Hi William,
BBP_GET_STATUS_2 should not be executed with default parameters, otherwise for each run you will scan all the SC !!!
To only address those that are open, use the flag "Delivery completed ind.".
I have a customer creating 50 000 SC per months.
So I used a variant with:
- SC of last 30 days (because for this customer, the order cycle should be closed in 30 days)
- Deletion indicator = '' (we don't care about deleted SC)
- Deletion indicator in BE = '' (idem)
- Delivery completed ind = '' (once the SC is received, it is closed in SRM, and does not appear in default "Check status", neither in PO to be received
Another variant scan all the SC from last 365 days, but runs only once a week.
In this case, we don't care about updating SC with invoiced quantity, so once the SC is received, we don't look at it anymore.
Rgds
Christophe
PS: please reward points for helpfull answers

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

Shopping cart not returning to SoCo even after PO and confirmation deleted

Shopping cart not returning to SoCo even after PO and confirmation are deleted.
Steps followed:
Created shopping cart
SC approved
Assigned vendor in sourcing and created PO(PO created successfully created in ECC)
Confirmation created
Deleted the conformation
Deleted the PO
When PO is deleted SC should return to Sourcing Cockpit, but it is not returning.
Checked the table BBP_PDIGP, source_del_ind is space.
Ran BBP_GET_STATUS_2 and CLEAN_REQREQ_UP both the programs manually but in vein.

Hi,
Can you try by just deleting the PO? Dont delete the confirmation.
I think once you have done the confirmation, the SC will not come back to SOCO. (Logically if you see, confirming means you have already received goods, so after receiving goods, I dont think SC will be visible again in SOCO)
Nikhil

Error while reading the PO in the Backend system. Inform system admin

Hi All,
We are having a peculiar issue of 'Error while reading the PO in the Backend system. Inform system admin'.
The P.O is in ordered status in SRM but the same is not getting transferred to backend ECC system.
No error messages or logs in RZ20, SLG1 any where.
All programmes like BBP_GET_STATUS_2 and CLEAN_REQREQ_UP are running fine.
Tried pushing the P.Os manually using function module (BBP_PD_PO_TRANSFER_EXEC_V2) to backend ECC.
It was working fine till a week ago and suddenly this problem is coming.
We had implemented few OSS notes suggested by SAP for the issue of 'shopping carts appearing in sourcing cockpit even after P.O creation' in both development and test system.
Now this issue is coming up in test system where as development system is working fine.
Please let us know where to look and how to resolve this issue.
A quick response would be highly appreciated.
Regards,
Teja

I am facing the same issue with one PO in the Production system.
SRM 5.0 , R/3 4.6C Extended classic scenario.
I checked the status of other PO's created today. I see them in R/3. There is one PO which was created a week back which shows up as "ordered" in SRM but the PO is missing in R/3. When clicked on the details on the web, system throws the error
Error while reading the PO in the Backend system. Inform system admin.
Message no. BBP_CF010
I checked RZ20, SLG1 no errors were found. I checked RFC connection, it was working fine too.
I tried pushing the PO using the FM BBP_PD_PO_TRANSFER_EXEC, it did not solve the problem.
In SRM WEBGUI Process PO - Item data -->follow on documents --> PO status is shown as Archived.
Any inputs would be greatly appreciated. Please throw some light on this issue.
Krishna

Limit order items to be sent back to sourcing on deletion

Hi all,
We are on SRM 7.1 Extended classic.
Can anyone confirm if the limitatin on the LIMIT orders not being sent back to SOURCING even after the PO items are deleted is stilll valid in SRM 7.1.???
Also we want to use LIMIT orders instead of service orders in SRM 7 as there are seevral issues when users try creating carts with the SERVICE HIERARCHY.To avoid the manual errors,we would like to use limit orders in SRM and then if required when the PO items are deletd in SRM the items should be sent back to sourcing.
If the limitation for the LIMIT orders items still hold true for SRM 7,then is there a way or enhancement to enable the sending of limit orders back to sourcing once the items are deleted in the PO in SRM?
I know the report responsible for snding items back to sourcing is BBP_GET_STATUS_2 and CLEAN_REQREQ_UP but is there a way we can handle the sendng of the PO items back to sourcing base don some custom logic for limit orders or for that matter any type of PO created in SRM?
Pls advise.

The note 1247922 is for EXTERNAL requirements/Purchase requsitions in ECC backend system and is not what I'm looking for.
Neverthless,I will create an OSS message with SAP and check if tehre is any enhancmenet available for sending limit items back to sourcing on PO deletion.Will update the thread accordingly
Thanks for the help.

Back Ground Jobs in SRM

Dear SRMer's,
System Info SRM 5.0
I have scheduled BBP_GET_STATUS_2 and CLEAN_REQREQ_UP to run every 1 minute.Both jobs are in released status
Now I have a requirement to change to frequency to every 5 minutes as I am getting Internal spool errors. When I select the job to change the frequency, I get the message: 'Job not modifiable' in the status bar.
Please let me know the procedure for modifying a released job.
Thanks in advance.
Points will be rewarded.
Best regards,
Bob.

HI BOB
Can you cancell both the Jobs when they are in Release status
And then Reschudle new jobs with a new frequency....
Schedue BBP_GET_STATUS_2 first and subsequently Schedue CLEAN_REQREQ_UP .
regards,
Nimish Sheth

Invoice status in SRM -- Error in process

Hi,
I am on SRM6.0 (Extended Classic Scenario) with backend ECC6.0. I have a invoice posted in SRM and went into error while transferring to backend. We reviewed the reason of backend error (it was because of MM period close) and reprocess the IDOC in backend after allowing posting in previous period. IDOC got processed and we can see the backend document link in SRM Invoice now but the status of the invoice is still "Error in process".
I checked program "BBP_GET_STATUS_2" and "CLEAN_REQREQ_UP" is setup correctly and running sucessful in SRM. Appreciate any help to resolve this issue.
Thanks,
Sachin

Hi All,
Any updates. Today I have another invoice where the IDOC got posted in backend sucesfully but system still shows invoice status as "Approved" whereas it should be "posted in backend".
Thanks, Sachin

Non-catalog shopping cart - manual po not showing up when extracting

I see the purchase requisition in table BBP_PDBEI. However, I do not see the associating manual created PO within this table. The manual PO has been created within ECC 6.0 and
shows up when running BBP_PD. Therefore, I know its recognizing the link the between the purchase requisition and po within SRM. In addition, I have run the programs BBP_GET_STATUS_2 and CLEAN_REQREQ_UP with
no luck.
Why is the manual po not showing up in table BBP_PDEBEI? Why is the function BBP_SC_BW_GET_TD not getting the manual created PO? Suggestions?
Thanks
Chris Hitzke

The BW team is using function BBP_SC_BW_GET_TD to retrieve purchase requisition and purchase order changes from SRM. In a non-catalog scenario, BW system is getting the purchase requisition from SRM but not the manual created purchase order (references purchase requisition).
I see the purchase requisition and purchase in the function BBP_PD (SRM), which retrieves its information from tables srrelroles and bbp_pdbinrel. However, I do not see the manual created purchase order in table bbp_pdbei, which function BBP_SC_BW_GET_TD uses to retrieve the purchase order. Any ideas??? Should bw be using a different function for getting the po for a non-catalog scenario? I see no oss notes on this issue. In addition, I have run the program BBP_GET_STATUS_2 and clean program over and over. I have heard of consultants creating a trigger.
Thanks
Chris Hitzke

Status I1113 missing in SC in Extended classic scenario using TA BBP_POC

Hi all,
I am using SRM in extended classic scenario (ECS) (SRM Server 5.5) SP09.
1. Scenario (without any problems)
Shopping carts have been succesfully replicated from R/3 with standard report
BBP_EXTREQ_TRANSFER.
transfered to Sourcing Cockpit.
No problems at all using standard Sourcing Cockpit -> POs are replicated to R/3, status correctly transfered into Shopping Carts (Status I1113 after creating a PO out of SC).
2. Scenario (problems concerning Status I1113 in SC)
Shopping carts have been succesfully replicated from R/3 with standard report
BBP_EXTREQ_TRANSFER.
transfered to Sourcing Cockpit.
Shopping carts are manually transfered into a local PO by using standard transaction BBP_POC (create PO) -> function "Add shopping cart item" within item data
Local PO is created without any problem, sucessfully replicated to R/3 and if I start the Monitor for shopping carts I get all the detailed information (follow on documents) -> PO number etc.
Problem: If I use TA BBP_POC and add these shopping carts to PO positions, the status I1113 is not written to SC after executing BBP_GET_STATUS_2 and CLEAN_REQREQ_UP .
The SC remains in Status I1106 (Shopping Cart ordered) / I1129 (approved)
I cant find any entries in table BBP_DOCUMENT_TAB and the shopping carts have been removed from SoCo after creating a PO out of it...
Does anybody uses Transaction BBP_POC in ECS and adds Shopping Carts to POs?
Any Idea why the status for these SCs is just I1106 "Shopping Cart ordered" but status I1113 "Follow-on Document Created" is missing/not updated?
Best regards,
Andreas

Hi
Please go through the SAP OSS Notes below ->
Note 1053433 Extended classic: Incorrect status shown in check status
Note 730239 Check status: Missing Backend reference
Note 819094 shopping cart monitor:Update status after resubmit shop.cart
Note 825761 Report program for shopp. cart status update after resubmit
Note 768164 Multiple SCs via SoCo are processed incorrectly
Note 729967 Shoppng cart:Status I1111,no follow-on docs->analysis report
Note 728536 Shopping cart: Follow-on docs => analysis-/correction report
Note 704941 EBP 3.0: Status error in SC extractor
Note 486246 Incorrect shopping carts offered for confirmation
Do let me know.
Regards
- Atul

About the Classic scenario,ERP PO number didn't return go Shopping card

About the Classic scenario,We create a shopping card,And approved,the follow document purchaser order create the ERP system,But the Purchaser order number didn't return to the shopping card follow document tab page.How can help me?

Dear Masa ,
Yeah,we schedule program BBP_GET_STATUS_2 and CLEAN_REQREQ_UP,Then have this issue,We didn't know why.

SC Item in Transfer process active - follow on document status not updated

Hi Gurus,
    Follow on document is not updated in SRM after PO creation. Ours is classic scenario (SRM 5.5, ECC6.0) and passed thru the following steps - SC (FFT) created, document approved, sent to SoCo, purchaser assigned vendor and created PO, PO created in ECC.
In SRM SoCo screen displays message 'PO created 45xxxxxxxxxx' successfully. Checked the BE PO 45xxxxxxx that was created successfully.
Ran BBP_GET_STATUS_2 and CLEAN_REQREQ_UP jobs. jobs finished successfully. But status is not updated in SRM. RZ20/SLG1 does not have any errors.
BBP_PD shows following statuses:
     I105   Awaiting Approval         X
     I1021 Created
     I1038 Complete
     I1106 SC ordered
     I1129 Approved
     I1111 Item in Transfer process
                    The last status I1111 is still active.
Any advise are welcome. Not sure if I am missing any OSS Notes.
Regards
Viktor Paul

Hi,
1. Check in table BBP_DOCUMENT_TAB if the entry exists use CLEAN_REQREQ_UP program.
2. If entry in the table not exists then check in transaction BBP_PD if the follow on document ( PO ) Number reserved for
the SC .. then use FM BBP_PD_SC_RESUBMIT.
3. none of these use normal process execute BBP_REQREQ_TRANSFER And then use CLEAN_REQREQ_UP
Thanks,
prasad.s

BLAREL IDOC is failing to post in SRM

Folks,
We are trying to update the Release Orders from backend PO into the SRM GOA.
From the sourcing in SRM we create a GOA and distribute the GOA to backend system.
After distribution a contract is created in the backend system. In the backend from contract we create a purchase order. When this happens the IDOC BLAREL is triggered from R/3 to SRM . From the R/3 end there is no error, however in the SRM end the IDOC goes into error with the message "Object Linkage for Global Outline Agreement does not exist".
After some analysis we found that
1.The table SRRELROLES does not contain an entry with the correct OBJTYPE. Its checking for object type BUS2014 but in the table there is an entry for BUS2000113.
2.The status of the contract is u201CIn Distributionu201D, even after Backend contract is created successfully in the R/3 system
3.We have manually executed the BBP_GET_STATUS_2 and CLEAN_REQREQ_UP but they were of no help either.
4.IDOC configurations seem to be correct because not all the BLAREL Idocs are failing.
5.We have also found that in few Idocs Plant in the contract is different from the plant in the PO created in R/3
Now we are not sure whether the problem is because of point 2 or point 5.
Please let me know if anyone has experienced similar problems and resolved them.
Thanks, Amith

Hi Amit your analysis pefectly correct.
Your first point is very valid point.
in the goa , you might have deleted any one of the item
so you have two entries in bbp_pd one is new another one is deleted.
and when PO created and release orders trying to update wrong.
sap has to offer a notes.
Muthu

BBP_GET_STATUS_2 and CLEAN_REQREQ_UP

Similar Messages

Maybe you are looking for