This blog talks about some SRM Tcodes for managing POWL changes. Below is the summarized list of the T-codes which can be used when making changes in standard POWL. Some of them are commonly used but there are some reports and POWL advanced Tcodes which are not used so frequently the blog lists all such Tcodes and reports for managing POWLs
Check the Tcodes for POWL setttings
- POWL_QUERY: To check Type ID, Layout settings
- POWL_QUERYR: To find the Query ID, Tab sequence number etc.
- POWL_TYPER: Find the POWL TYPE ID
- POWL_TYPE: To find the feeder class based on POWL Type ID
- /SAPSRM/POWL_CUST: To make changes in Field catalog, Trex, DB criteria or buttons
- POWL_CAT: To define categories for POWL
Some of the important SRM reports are as below which you can run via SE38 transaction.
- POWL_D01: Delete reports if any changes in POWL
- POWL_D02: Shows the Active POWL queries in the system.
- POWL_D03: Check consistency of POWL table entries by running this report if you feel something is not working fine in Portal as shown in Figure 152
The above reports should be sufficient enough to perform a fix for any issues found in POWL. However, if the issues persist you may choose the below reports as well however this should be used under expert guidance as these reports delete all queries from the system
Check some more POWL specific reports are mentioned below:
- POWL_D04: Delete criteria from Admin queries and result are immediately stored in a transport
- POWL_D05: Deletes the result if any left from the last run of POWL_D03 report.
- POWL_D06: Activate derived queries when you created some queries and link of POWL_QUERY to POWL_QUERYR is missing and needs to be activated for derived queries.
- POWL_D07: Same as POWL_D01 Shadowing entries to be deleted in case of multiple users.
- POWL_D08: When any layout changes occur in Development the report requires execution and result are stored in a workbench transport.
- POWL_D09: Default mapping of default layouts in queries or make any changes to the system.
|Adding new fields to the Business documents||Control via config to add new field|
|Make changes in field layouts||· Control via config to make fields editable/read only/ Enabled|
|Make changes to add default values to the field||· Use Web Dynpro or code changes in BBP_DOC_CHANGE Badi|
|Make changes in POWL search help to add new search fields or add as a result column||· Check the POWL and make necessary changes to add / remove field|
This is the blog I refer to for reading about how to add custom search fields in the POWL search criteria and result section
Also, check the note which talks about adding fields to partner extension
Note: 1386310 – Creating SRM business partner field extensions
Thanks for reading the blog. This blog is taken from a book I had written on SRM consulting sometime back!
I would like to mention a few lines about the book so that it reaches the right audience who are interested to learn more about SRM.
This book comprises of 115 top consulting scenarios which you should know when you start to work in any procurement module but specifically in SRM Module in SAP. I have added these easy to understand format. Keep as a side note and should be a guide for you to help you in handling most of the scenarios in SRM
As per what happens in any consulting environment the issues you actually get from your client may not be included in here but after you have read through this guide, it would give you a very good base in the terms of helping you to experiment and try things out in the system directly to come closer to a resolution. This book is prepared based on my notes from hundreds of meetings, being part of multiple projects, brainstorming with my colleagues and lastly to be able to provide ongoing support to my clients to manage their procurement landscape. Please note that this book focuses on building basic concepts for both Technical as well as functional people, so I recommended you go through all the pages to have a good understanding of the SRM system. If you have basic ABAP knowledge, it would be easier if not, it can be a good learning which can also be applied to other SAP modules.
Although this book is geared more towards SRM as a product but having worked in other modules as well, it includes some general SAP concepts which help you to apply the same knowledge in multiple other modules like MM, PM, HR, and other areas. SRM has a tight integration with all the above modules, and hence it is important to have a good understanding so you can work effectively in a collaborative environment with other team members by knowing how the other module work rather than just passing the buck.
Link to buy the book as below
Thanks a lot for supporting 🙂