Skip to Content

What are Advanced List Page queries in Sourcing 7.0 and how to take advantage of it?

July 7, 2011 | 156 Views |
 sap clmsap sourcingsap srmsourcing
Follow

Introduction

In SAP Sourcing, one of the challenges customers face in the query area is, in order to make an enhancement to a custom query a report developer with SQL experience would have to get involved as it requires updating SQL in most cases. Well, if you are one of those customers, there is good news. SAP has introduced a rich set of reporting enhancements in Sourcing 7.0 and the one I will cover in this blog is –Advanced List Page queries. Advanced List Page queries offer end-users the ability to add new columns to the list page query as well as define new filters, all without having to write any SQL. 

For convenience, I will refer to Advanced List Page queries as ALP in the rest of the blog. In this blog I will explain how ALP queries work and show how to convert a custom list page query to a new ALP query.

What is a ALP query?

ALP queries allows end-user to customize a list page by providing:

1)     Ability to add new columns to the query and delete existing columns

2)     Ability to reorder columns through simple drag and drop

3)     Ability to add new search parameters to query

4)     Ability to save and manage Custom Search

If you are a customer upgrading to Sourcing 7.0 the standard SAP provided list page queries will be converted to ALP queries automatically as part of the upgrade; however custom queries need to be converted manually.

Adding new columns

To add a new column to the list page query, click on the Personalize icon on the query toolbar as shown in the query below.

image

On the personalization screen select the columns to be added to the query. In the screenshot below, the Document Type column is selected to be added as a new column. Any extension field that belongs to the Default Extension Group will also be listed on the personalization screen. To delete a column, simply uncheck the checkbox next to the column name.

image

By default, the new columns are added at the end. Column order can be easily changed by simply dragging the column header and dropping it where desired. In the screenshot below, the Document Type column was added by default at the end of the query and I dragged and dropped it next to the Name column.

image

Adding new search parameters

In ALP queries search parameters are not displayed on the UI by default. To add search parameter, click on Modify Search button and click on Add button as shown below. This action adds a new search parameter. The parameter you want to filter can be changed by simply selecting the filter from the dropdown which contains a predefined list of fields. The list of fields in the dropdown cannot be modified. This list includes Extension fields. The end user can add additional search parameters as desired by clicking on the Add button.

image

Save Search

The customized query can be saved by entering a name for the saved search in the Save Search As field and saving it. The saved search will appear on the list page dropdown as shown below

image

A saved search is specific to a user. It is not possible to share a saved search with another user.

Deleting Saved Search

To delete a Saved Search, a special Workbench channel called Saved Search would have to be added to user’s workbench. This workbench channel will display all the saved searches for that user. Saved Search can be deleted by simple clicking on the trash icon next to the Saved Search name as shown in the screenshot below. Note, this workbench channel also shows the list of page personalizations the user has created in the system.

image

So far we have seen the functional aspects and usage of ALP queries. In part 2 of this series, I will get into the technical details. Stay tuned…

To report this post you need to login first.

8 Comments

You must be Logged on to comment or reply to a post.

  3. Former Member

    Hi Vikram,

    When a query is built to return multiple objects (say master agreements and agreements), can it still be converted to an ALP? In other words, would the filters be able to list fields from both the objects? Or can we make one filter list master agreement fields and the other list agreement fields?

    Regards,

    Subhasini

    (0) 
  4. Former Member

    Hi Vikram,

    I’m pretty new in SAP Sourcing (I’m working in SAP Souring 9.0) and I’ve got a problem. I have created new Query (by editing default Query “All Projects” and editing it) and added new Result Fields to it (values with two places displayed after comma). Those new fields I’ve added refer to existing Extension Definition (I’ve got three types of Projects and one of them is using this Extension Definitions). When I am trying to Personalize Project List of this Query i can add two fields with the same name: one results from fields I’ve added to my Query and the other one refers to Existing Definition. Do you know whether it is any way to delete these second ones from Personalize Project List but not from Existing Definition? I added link to a screen with an example.

    http://postimg.org/image/c3nnpiowl/

    Regards

    Paweł Skawiński

    (0) 
    1. Vikram Shanmugasundaram
      Post author

      Hi Pawel,

      I’m not sure if I fully understand the question.

      You may want to play around with the Sensitive flag on the extension definition. By making a field sensitive, I believe it will not be available as an option to select on the advanced list page query.

      Hope this helps.

      Regards,

      Vikram

      (0) 

Leave a Reply