on 04-17-2008 9:11 AM
Dear Community,
Need some ABAP help.
Know many experts are in our community.
We have added 3 custom fields to the Bid Invitation and Bid header
Coded Badi BBP_CUF_BADI_2 for them to appear in the Search criteria for Find Bid Invitation for both the logins(purchaser and bidder).
The custom fields now appear in the Extended search for both.
These custom fields extract values from custom tables.
But we found that the search criteria seems to be filtering Bid Invitations only in the Process Bid Invitation screen(Find Bid Invitation) of the purchaser login.
Template: bbp_bid_inv/99/saplbbp_bid_inv_1010.html
And NOT filtering Bid Invitations in the Process Bid screen(Find Bid Invitations and Auctions) of the Bidder login.
bbp_quot/99/saplbbp_quot_ui_its_1010.html
The ABAPer has already incuded the custom fields in structures INCL_EEW_PD_HEADER_CSF_BID and INCL_EEW_PD_HEADER_CSF_QUOT,
What is required in addition so that the search criteria will work in the Bidder login as well??
Thanks in Advance,
Dinesh
(Will appreciate with points)
Hi,
To just filter the Bid /Bid invitations for the Bidder login,you can directly implement the BADI "BBP_WF_LIST".
However if the problem lies with the Custom field in the selection screen of the extended search,(i.e. When you enter the value for the custom field in the Extended search help screen,then the corresponding Bid invitations are not seen in the o/p list) then this seems to be a bug.I had seen a thread on similar issue for the BI screen.The workaround for this would be the ITS template mdofiication for filtering the list of BI to be seen.
HTH.
BR,
Disha.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, Disha.
We have alreday activated BBP_WF_LIST
and tried some code in method
BBP_WF_LIST_SOCO
but did not help us.
Can you suggest any specific code to try?
You are right for template modification for values of this custom fields.
If we do that Bidder CAN filter the BI correctly with these values of custom fields.
But customer does not want that way because in future the values would be changing.
and so it would be an additional task to correct templates.
Also they have to redo these changes with every upgrade.
So we are fetching the values from custom tables for these custom fields.
Would like to again draw the attention towards purchaser's search with these custom fields.
Why purchaser can search correctly with these custom fields fetching values from custom tables?
Can we debug or take any hint from there?
Any futher thoughts?
Landscape - SRM 5.0 SP11 CLASSIC
BR
Dinesh
Already raised an OSS for this issue.
Will keep updated about any responce.
SAP created a note for us
1165205
which solved the issue
Thanks for the inputs.
BR
Dinesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.