POWL BADIs

[Former Member]

Hi All,

SRM Version 7 . scenario : Classic

The requirement goes like:

We have to add another custom field in search criteria as a User ID. user should be able to select SC status as 'Awaiting approval' and enter user ID. all SCs awaiting for this user's approval should appear as POWL result.

I have added the fields in standard result / search structure and field is appearing as column. Now to fill this field with data and put my filter criteria in the code I am trying to check these BADIs , but not getting called.

Please let me know the actual usage of these BADIs if anybody used it so far.

/SAPSRM/BD_POWL_CHNG_SEL_RSLT

/SAPSRM/BD_POWL_CHNG_SELCRIT

/SAPSRM/BD_POWL_CHNG_CUF_SRCH

/SAPSRM/BD_POWL_CHNG_FIELDCAT

Is this possible through BADIs Or an implicit enhancement would be required? OR do we need to create Custom feeder class?

Thanks

Vipin

[Former Member]

Hi Vipin,

Any succes in implementing the BADI's?

I am currently trying to enhance a POWL with a few extra search criteria. The POWL i am trying to enhance is implemented in the feeder class /SAPSRM/CL_CLL_PWL_A_CTR. Here only the BADI's have effect.

/SAPSRM/BD_POWL_CHNG_SEL_RSLT

/SAPSRM/BD_POWL_CHNG_SELCRIT

/SAPSRM/BD_POWL_CHNG_FIELDCAT

Implementations of the BADI's:

/SAPSRM/BD_POWL_CHNG_CUF_SRCH

are not executesd. It simply is not "connected" yet

So did get this to work?

Best regards,

Martin

[Former Member]

Hey Martin

I kept one of the Badis in an infinite loop & executed query

From portal and it was stopping as expected...

Give a try ...

-vipin

[jason_boggans]

Hi Vipin,

A similar issue was responded to by our POWL development as follows:

the documentation is a little bit missleading because

the described steps are just valid for the specific BOs

Shopping Cart, Purchase Order, Confirmation and Central Contracts.

For all other BOs you can't extend the list of POWL search criteria via

DB view /SAPSRM/V_SRC_CR.

Instead you must implement the BAdIs of Enhancement Spot

/SAPSRM/BD_CLL_POWL_FEEDER.

There are four enhancement spot definitions:

1) /SAPSRM/BD_POWL_CHNG_CUF_SRCH is for changing the user input and also

for filling it to the correct parts of the search structure (e.g.

customer header and customer items table)

2) /SAPSRM/BD_POWL_CHNG_FIELDCAT is for changing the result table

structure

3) /SAPSRM/BD_POWL_CHNG_SELCRIT is for changing the list of offered

selection criteria in the POWL

4) /SAPSRM/BD_POWL_CHNG_SEL_RSLT is for changing the result data

In your case the numbers 1) and especially 3) are important.

Please implement the BAdIs to fullfill your requirements. Extend

the selection fields with BAdI spot definition 3 .

Use BAdI definition 1) for filling the input to the search processing

fields. Instead of using the structure you are naming above you have to

use the two parameters of BAdI spot definintion 1), cs_search_cuf_h and

cs_search_cuf_i.

Furhtermore you need to implement the note 1402576 so that these

customer field values are processed correctly in the search framework.

PLease note this is simply a word for word extract obviously not for your problem but hopefully it may steer you in the direction you need to resolve your problem.

Regards,

Jason

[Former Member]

Hi Jeson,

Many thanks for this information I will try as per your suggestion.

~Thanks

Vipin