Filter Back-end PO's for transaction BBPCF02

Question

Hello,
We have SRM 4.00.
We have gave to some users the transaction BBPCF02. The problem is that all the PO's that exist in our backend system are appearing. We whant to restrict by document type. Is this possible?
Thansk in adavance.
Catarina Campos

Answer 1

Hi,
You can filter the list of confirmations to be shown by implementing the  logic in BADI "BBP_WF_LIST".
Here is the documetation of the BADI -
BBP_WF_LIST
Short Text
Display Worklists and Search Results Lists
With the Business Add-In BBP_WF_LIST , you can tailor the
display of worklists and search results lists for purchase order documents (and Sourcing applications) in SRM Server according to your own criteria.
Standard settings
The following methods are available:
BBP_WF_LIST for purchasing documents
BBP_WF_LIST_SOCO for the Sourcing application
In the standard version, the following differences exist between the display of worklists and search results lists:
Normal employees see only their own requirements and documents
The purchaser's worklist in Sourcing and in the application for processing purchase orders is dependent on assignment to an organizational unit.
The goods recipient and invoicing party can find all purchase orders, confirmations, and invoices.
As standard, the system sorts the purchasing documents in ascending order by the last date of processing.
To distinguish between the worklists and search results lists of the SRM Server applications, the BAdI is implemented dependent on the following filters:
BUS2201
Filter value for the worklist in purchase order processing in SAP Enterprise Buyer
BUS2203
Filter value for the worklist in confirmation processing in SAP Enterprise Buyer
BUS2205
Filter value for the search results list in invoice processing in SAP Enterprise Buyer
BUS2121
Filter value for the worklist in shopping cart status check in SAP Enterprise Buyer
BUS2200
Filter value for the search results list in bid invitation processing in SAP Bidding Engine
BUS2202
Filter value for the search results list in bid processing in SAP Bidding Engine
BUS2000113
Filter value for the search results list in contract processing in SAP Enterprise Buyer
Activities
Implement and activate the BAdI if you wish to adapt worklists and search results lists.
Note that the filter value Object type (field OBJECT_TYPE) determines for which application the BAdI implementation is active.
Example
Using the BadI BBP_WF_LIST you can sort the worklist by document number, for example, or remove documents belonging to a particular user from the worklist.
The implementation of the BadI using Business object type BUS2205 allows you to change the list of invoices and the purchase orders associated with these invoices independently of one another. For example, you could sort the purchase orders by purchase order number and the invoices by the name of the user who created them.
You can exclude bid invitations from a certain product category, for example, from the purchaser's search results list in SAP Bidding Engine.
You can exclude contracts from a certain purchasing organization or purchasing group, for example, from the purchaser's search results list in SAP Enterprise Buyer.
Further notes
If the BadI is used for confirmations and purchase orders, it always accesses the list of the actual document and its purchase orders.
The purchaser's worklist contains only requirements that, according to Customizing, are to be processed in the Sourcing application. See the IMG activity Define Sourcing for Product Categories.
Sample BADI code in foll threads ->
Filtering content in the SRM confirmation worklist
Re: Using BADi's BBP_PGRP_FIND  and BBP_WF_LIST  for Sourcing
Re: Resctriction while displaying work items in sourcing cockpit..
Re: Purchaser worklist
BR,
Disha.
Do reward  points  for   useful  answers.