POWL Query changed automatically in SRM when adding new field in POWL search

[Former Member]

Hello Experts,

As per my requirement, I have added a new field in SRM POWL search criteria and results. I have added the field to all relevant feeder types. Everything is working as expected.

But when I moved the changes to quality and production, the POWL_QUERy got changed and some default values got populated to certain fields and some fields became Read Only. I am sure, i have not done any POWL_QUERY changes.

Can anyone explain this behaviour.

Thank you.

Saran

[daniel_marlen]

Hello Saran,

The default values and disabled fields are coming from POWL_QUERY customizing. Please check, if you can find the default values and Read Only settings in the Query parameters.

• If yes, please correct it in dev system or if it is correct in dev, make a small change and transport it into quality.
• If no, please run report POWL_D01 for the relevant APPLID and User to delete the user-specific POWL personalization.

Let me know the outcome.

Best regards,

Daniel Marlen

[Former Member]

Hello Daniel,

Thank you for you response.

I am able to fix this by making changes in POWL_QUERY transaction.

But I wanted to understand, how these values got defaulted without making the changes in the POWL_QUERY in the firstplace. Also, no default value was given in the SPRO configuration as well.

Regard,

Saran

[daniel_marlen]

Hello Saran,

If no error occurs in the system, default values can come from three sources:

• customizing (POWL_QUERY),
• BAdI (BD_POWL_CHNG_SELCRIT),
• User personalization.

If none of these sources is relevant in your case and the default values are only appearing after transport request, there can be an error during transport, which causing this. Can you reproduce this error every time?

Best regards,

Daniel