BADI BBP_WF_LIST implementation

Question

Hello,
I would like to implement a the BBP_WF_LIST BADI for confirmation (BUS2203).
Can someone explain me all the step I have to do. I never did this before and I don't know the step to do.
thanks

Answer 1

Hi
Implement the BADI - BBP_WF_LIST using SE18 Transaction for the filter type - BUS2203 for doing this job.
Here is the documetation of this BADI
<b>BBP_WF_LIST BADI</b>
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.
Change Output List Purchasing Documents
Functionality
With method BBP_WF_LIST in SAP Enterprise Buyer, you can adapt the display list of the worklist for purchasing documents and search results lists according to your own criteria.
Parameters
Importing
FLT_VAL
Filter value
I_PDLIST_NEW
Entry list of worklist or the search results list and additional information
Changing
E_PDLIST
Output list of worklist or the search results list (contains only GUIDs)
<b>And Here is the sample Code for the BADI Implementation...</b>
METHOD if_ex_bbp_wf_list~bbp_wf_list.
  DATA: t_header_guids     TYPE TABLE OF bbp_guid_tab,
        t_pdlist           TYPE TABLE OF bbp_pds_pdlist,
        t_messages         TYPE TABLE OF bbp_pds_messages,
        t_sc_guids         TYPE TABLE OF bbp_guid_tab,
        t_ref_doc          TYPE TABLE OF bbps_sc_refdata,
        t_itemlist         TYPE TABLE OF bbp_pds_sc_itemlist,
        t_conf_pdlist      TYPE TABLE OF bbp_pds_pdlist.
  DATA: wa_sc_guids        TYPE bbp_guid_tab,
        wa_pdlist          TYPE bbp_pds_pdlist,
        wa_ref_doc         TYPE bbps_sc_refdata,
        wa_itemlist        TYPE bbp_pds_sc_itemlist,
        wa_conf_pdlist     TYPE bbp_pds_pdlist.
    IF sy-tcode EQ   'BBPCF02'.   
*--- First Get all the Reference documents
*--- Get all the Shopping Carts
      CALL FUNCTION 'BBP_PD_SC_GETLIST'
        TABLES
          i_header_guids = t_header_guids
          e_pdlist       = t_pdlist
          e_messages     = t_messages.
*--- Sort the SC based on SC number
      SORT t_pdlist BY object_id.
*--- Get all the Header Guids
      LOOP AT t_pdlist INTO wa_pdlist.
        wa_sc_guids-guid = wa_pdlist-guid.
        APPEND wa_sc_guids TO t_sc_guids.
      ENDLOOP.
*--- Get all the Reference Document for the Header Guids
      CALL FUNCTION 'BBP_PD_SC_REF_GETLIST'
        EXPORTING
          i_item_not_deleted = 'X'
        TABLES
          it_header_guids    = t_sc_guids
          et_refdata         = t_ref_doc
          it_logical_systems = 'R3BACKENDSYSTEM' -> Give he R/3 backend system RFC Destination name here
        EXCEPTIONS
          nothing_found      = 1
          OTHERS             = 2.
*--- Retain only the PO (Business Object 2012)
        DELETE t_ref_doc WHERE ( be_object_type NE 'BUS2012' AND
                                 be_object_type NE 'BUS2012001' ).
*--- Sort all reference documents based on be_object_id - Purchase Order numbers.
      SORT t_ref_doc BY be_object_id.
*--- Loop on all remaianing POs
*---  Use SC Guid (Header)
      LOOP AT t_ref_doc INTO wa_ref_doc.
          DELETE e_pdlist WHERE object_id = wa_ref_doc-be_object_id.
      ENDLOOP.
*--- Here make a call to the R/3 system by using your RFC Function module
*---- and update e_pdlist [] table which finally will contain all the
*--- detialed confirmations starting with Document type - "EB"
*---- based on the document type "ECDP" and "ECPO" - Add one more document type "EB" ..
*---- so when ever BBPCF02 is called in ITS it should disply the POs
*--- which are based on document types as "ECDP" "ECPO" and "EB".
    ELSEIF sy-tcode EQ 'BBPCF03'. " Display All PO/Confirmations
*--- Similar code as above
    ENDIF. "if sy-tcode eq 'BBPCF02'.
ENDMETHOD.
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul