BBP_GET_STATUS_2

Hi,
We are on SRM 5.0 and configuring the extended classic scenario.
Local PO is created sucessfully and when it is trying to replicate the PO to abckend PO, it says that "Error in Process".
I have scheduled the job BBP_GET_STATUS_2 and it is working fine.
I am trying to execute this report again with the Shopping cart number, it says Error E031, Shopping carts item excluded (due to ext. PO status). please let me know how to solve this.
Regards,
Chary

Hi Chary,
Check if the number range defination is correct. Internal number range of SRM PO should fall in the external number range defined for R/3 PO.
Also check if the material master and material group in the PO exists in R/3.
Regards,
Prashant
Do reward points for helpful answers

Similar Messages

BBP_GET_STATUS_2 Message E 031

Hy Experts!,
In my requirement, i´m looking the planned JOBS with the BBP_GET_STATUS_2 program in SRM 4.00. A lot of these Jobs are returned with message E 031 in SPOOL, with empty description, because there is not a Symbol Text 031 in BBP_GET_STATUS_2 Text Elements.
I was searching OSS Notes, and forums threats posted with BBP_GET_STATUS_2 messages, but i can´t found a solution.
Did you know an OSS Note that may resolve it?
The code in program is:
DESCRIBE TABLE gt_sc_refdata LINES lines_refdata.
IF lines_refdata < 1.
    IF lt_guid_ignore[] IS INITIAL.
      PERFORM error_and_leave.
    ELSE.
      DESCRIBE TABLE lt_guid_ignore LINES lines_refdata.
      NEW-PAGE NO-HEADING.
      FORMAT COLOR 6.
WRITE: /, text-200, / 'E 031' , /10 lines_refdata ,
text-031, text-200.
      WRITE: /.
      WRITE: /.
      EXIT.
    ENDIF.
ENDIF.
Regards.

Hi,
Check for notes related to E 031 and locks, there was a note, 1420833, released to combat too much locking in SM12 from the BBP_GET_STATUS_2 report which was dealt with by this note, it is a side effect of note 1342152
Regards,
jason

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

BBP_Get_Status_2 Variant values

Dear SRMers,
System Info SRM 4.0
We have a variant for BBP_GET_STATUS_2 called GetStatus.
This variant has the following values set a.) no Shopping cart time frame set
b.) the SC..... in last days is 0.
Does this mean it will pick up the shopping carts created today or does it process all shopping carts in the system
Points will be rewarded.
Thanks in advance,
Regards,
Bob

Hi Bob,
Normally it is advised to create variant with 5 days runs for every 15 min, and 30 days for every 3 hours and 365 days for every weekend.
if you leave days 0, it will pick all the shopping carts.
Let me know if you need any further info on this.
Thank you
Sreedhar Vetcha

BBP_GET_STATUS_2 - issue

Hi Guy's , We are currently on SRM7 and recently have noticed that when the BBP_GET_STATUS_2 job is run it is applying a lock in table USR02 in ECC which causes the ECC system to stale. I have checked the SM37 Log and there i could see the following
message "These requirements were blocked during update by other users" with the list of SC object Id.
I have gone through some notes and seems like we can improve the performance by applying 1590401. However could not see any information on why it is locking table usr02 in ECC. has anyone faced this similiar problem.
Please advise and shre your experience on how it was fixed.
Thanks
Saj

Hello Saj,
could you please check SRM How-To below:
[BBP_GET_STATUS_2 causes the error u201CLock Table Overflowu201D|http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=235674617]
Maybe it could be relevant for you.
Regards.
Laurent.

BBP_GET_STATUS_2 only works when entering SC number

Hi all.
SRM 4.0.
I am seeing some strange behaviours in my system these days. The job BBP_GET_STATUS_2 is set up in batch to run every 5 minutes, but now I am seeing issues where the documents are not properly updated in SRM.
The case is that in the user's Goods Receipt screen they have the list of purchase orders that are relevant for GR - once the GR has been posted, the PO will disappear from the screen. However, nowadays many POs do not automatically remove themselves from the users' GR screens. When I run the job BBP_GET_STATUS_2 manually and entering the SC number(s) everything works. So it seems the job is not working very well if no SC numbers are maintained in it.
Has anyone else seen this type of strange behaviour? It seems strange to me that this should not be working in batch runs where it would make no sense to type in the SC numbers.
DM

Hi there.
I have a batch running every 5 minutes with the steps
CLEAN_REQREQ_UP
BBP_GET_STATUS_2
and the spool list tells me:
Update Successful
... 6.466 Data Records Updated (SC Rows)
and 0 Data Records Created (References)
So this should be fine, right? But it is still not removing the purchase orders from the GR screen after this. What could be causing this?

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

Requirements reappear in Sourcing Cockpit after running BBP_GET_STATUS_2

I have set up plan-driven procurement in the extended classic scenario in SRM 5.0 with an ECC 5.0 back-end. When I assign a vendor to a shopping cart in the sourcing cockpit for an external requirement, it disappears from the worklist. As soon as I have run program BBP_GET_STATUS_2 and I run transaction BBPSOCO01 again, the SC will appear in the worklist again although a PO has been created in both SRM as in the Back-end system. The status of the SC is ordered, the Purchase Requisition is not send again to SRM and I have implemented all relevant notes for program BBP_GET_STATUS_2. How can I prevent that shopping carts are being ordered multiple times? The problem is similar to the problem from KA posted on 9 July 2007, only this is not yet solved.

Hi Nishant,
Thanks for your answer. The problem I have that I have already applied note 1050349. Besides note 1050349 I have also implemented the following notes:
0000691569 Error messages in BBP_GET_STATUS_2
0000989891 BBP_GET_STATUS_2: Incorr quantity determination in back end
0001001882 BID: Requirement reappears in sourcing cockpit
0001012124 SHP not reappear in SOCO after backend PO delete
0001027598 BBP_GET_STATUS_2: Error message E 011 in back end
0001032713 BBP_GET_STATUS_2: incorrect sourcing indicator
0001033208 Complete sourcing indicator is getting lost
0001040847 Requirement is removed from sourcing after BBP_GET_STATUS_2
0001041334 BBP_GET_STATUS_2 cannot handle more than one PO
0001044351 BBP_GET_STATUS_2: Error message with reservation
0001049989 External requirements: Object id not found error in XI
0001050349 Sourced Shopping cart reappears in Sourcing cockpit.
0001055375 BBP_GET_STATUS_2: Error message during conversion
0001056941 Shp. cart sent back to SOCO in case of P. Req. or Reservatio
0001062223 BBP_GET_STATUS_2: Performance and runtime error
0001062565 No reference of backend Object ID is updated in Shop. cart
0001066128 Shp cart item is not updated from the related PO
0001084144 BBP_GET_STATUS_2 sourcing relevant indicator
0001088315 External Requirement: Sourcing ind. flag is wrongly set
0001106550 SOCO: completed requirement is sent back to SOCO
Do you have other recommendations?
Regards,
Jos van den Berg

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 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

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 <b>30</b> 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

Impact of non running BBP_GET_STATUS_2.

Good morning,
I'd like to have an answer to the following question please : "what is the real impact when the job BBP_GET_STATUS_2 do not run in an SRM production system ; or only rarely ?".
Many thanks for your contribution.
Best regards,
Stéphan

Hi ,
   Lets take an example of confirmation creation.
    I have created GR confirmation from SRM .GR document will post to back end and after creating material document in back end system will notify to SRM to update SRM PO the final indicators basing on BBP_DOCUMENT_TAB table and which will be taken care by Clean_req job.
After clean_req job the   BBP_GET_STATUS2 (scheduled ) Job will update the GR final indicators at SC level by checking the backend PO details whether the GR is fully completed then it will update the final indicators in SC..
If you wont update these final indicators at SC then after GR is full confirmed then also SRM will allow to create GR again.Actually this is wrong.
this is one example where the impact of get_status job and it is required..
Regards
Devi

BBP_GET_STATUS_2

Similar Messages

Maybe you are looking for