TSO150 Sourcing CLM Configuration

SAP Sourcing / Contract Lifecycle Mgmt Overview June 2011

Material # TSO15095P

SAP Class Week of March 19, 2012

2011 SAP AG. All rights reserved. 2

Disclaimer

The information in this document is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. This presentation is not subject to your license agreement or any other service or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation and SAP's strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information on this document is not a commitment, promise or legal obligation to deliver any material, code or functionality. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This document is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.

All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.



Ineffective Strategic Sourcing Processes Results in the Lack of Sustainable Savings

Lack of Process Management Limited ability to conduct simple and or complex sourcing activities Lack of a standard sourcing process across spend categories

Limited Supplier Qualification Difficulty in identifying, evaluating and, qualifying suppliers Lack of on boarding and engagement process

Ineffective Sourcing Event Management No automated RFI, RFQ, and or RFP sourcing capabilities Inability to effectively manage auctions and supplier engagement

Poor Negotiation and Award Process Ineffective ability to collaborate with suppliers efficiently Limited tools to examine, score and award proposals

Slow Time to Value

Adoption to new tools can be slow Lack of deployment flexibility Limited process and data integration to ERP

Poor strategic sourcing process results in long cycle times, lost savings opportunities, and slow time to value



Effective Strategic Sourcing Process Delivers Sustainable Savings

Streamline complex sourcing processes and automate tasks Pre-configured processes, templates enabling standardization and reduced cycle times

Efficiently identify, evaluate and qualify new suppliers Enables straightforward onboarding process inclusive of specific attributes e.g. sustainability criteria

Automated RFI, RFQ, and or RFP sourcing capabilities Effectively manage, track auctions and supplier engagement

Effective ability to collaborate with suppliers efficiently Extensive tools for bid optimization, scoring, and award selection

Enables fast adoption Delivers rapid on demand deployment Provides process and data integration to ERP

Effective strategic sourcing process reduced cycle times, increased savings opportunities and rapid time to value

Enable Effective Process Management Deliver Supplier Qualification

Manage Sourcing Events

Comprehensive Negotiation and Award Process

Rapid Time to Value



SAP Sourcing Delivers the Strategic Sourcing Process

Enables the strategic sourcing process across all categories of spend

Delivers sourcing strategy and project management capabilities

Manages supplier identification, qualification and on boarding

Provides extensive RFI, RFQ, RFP and Auction tools and templates

Enables effective bid negotiation, evaluation and awards

Drives rapid time to value via On Demand Deployment and ERP integration

Effectively Managing Todays Important Procurement Needs with Rapid Time to Value

On Demand

Enaprospe

Delma

Maqua

Proand

Enaeva



Ineffective Contract Lifecycle Management Results in Increased Compliance Risks

Poor Contract Lifecycle Management Results in Significant Legal Risk,

Financial Impact, and Slow Time to Value

Sales Legal Le

Poor contract compliance (PO, invoice, SLAs) Belated renewals management Lack of performance information hinders re-sourcing or resale efforts

Weak Contract Management

Lack of tight controls (e.g., for non-standard contracts / language) Legal risk

Ineffective Contract Creation

Financial Inconsistent and email-intensive processes Risk of not including correct stakeholders Long negotiation and approval cycle times

Disconnected Negotiation Processes

Organizationally dispersed contracts Redundant contracts No visibility into commitments (financial, legal) Inability to track regulatory compliance or understand contract history

Poor Contract Visibility

Operational Contracts

eLLLLLLLLLLLLLProcurement

Slow Time to Value Adoption to new tools can be slow Lack of deployment flexibility Limited process and data integration to ERP



Effective Contract Lifecycle Management Delivers Optimized Contract Value

Operational Contracts

i

Improved contract compliance (PO, invoice, SLAs) Timely renewals management Visibility to performance information enables proactive relationship management

Improved Contract Management

Financial Legal Leg

Effective Contract Creation Tighter controls (e.g., for non-standard contracts / language) Minimized legal risk

Streamlined and controlled processes Inclusion of the right stakeholders Abbreviated negotiation and approval cycles

Streamlined Negotiation Processes

Single repository for contracts Elimination of redundant contracts Visibility into commitments (financial, legal) Ability to track regulatory compliance and understand contract history

Full Contract Visibility

Sales SProcurement

Improved Contract Lifecycle Management Reduces Legal and Financial Risk, and Delivers Rapid Time to Value

Enables fast adoption Delivers rapid on demand deployment Provides process and data integration to ERP

Rapid Time to Value



SAP Contract Lifecycle Management Supports the Entire Contract Lifecycle

Automates the contract creation

cycle from draft to reviews and approvals

Includes contract authoring with clause and template libraries

Creates a contract repository with access-controlled search and reporting

Includes standard integration with SAP ERP-MM for procurement contract compliance

Deep bi-directional integration within the source to contract process

Drives rapid time to value via On-Demand Deployment and integration into ERP

Effectively Managing Todays Important Procurement Needs with Rapid Time to Value



SAP CLM application footprint

SAP Sourcing

Project & Process Management

Contract Management & Compliance

Standardize sourcing process: steps, tasks, owners, due dates, etc.

User dashboards Centralize all sourcing

project management

Centralize contracts Contract authoring Standard templates and

clause library Collaboration and

approval workflows

Supply Mgmt. Sourcing / Negotiation

Supplier self-registration and self-maintenance

Single entry point for all bid and contract activities

Management of prospective supplier database

Simple to complex RFx events

Business scenario award optimization

Reverse and forward auctions

Project & Process Management

Supplier Qualification & Performance

Sourcing & Evaluation

Contracts Repository & Negotiation (CLM)



SAP Contract Lifecycle Management OnDemand - OnDemand Services

Standard Services Customer success manager Onboarding and enablement Hosting Training On-going support 2 new innovation waves per year Additional Services Event day support Supplier support Contracting support Legacy contract migration Supplier management risk profiling Consulting services



OP Hosted

Partner-based SaaS (multi-tenant

hosted) OnDemand

Strategic Differentiation Own-practice is better

Common practice is better

Economics of Buy CAPEX OPEX

Speed of implementation Not critical Critical

Security concerns Critical Not critical

Landscape complexity High Low

Fast access to innovation Not critical Critical

Contract Lifecycle Management OnDemand OnDemand vs. OnPremise | What to Choose?



SRM Portfolio Enables the Complete Source to Pay Process

Strategic:

SPM &

E-Sourcing

Operational:

ERP & SRM

Sour

ce to

Pay

Contract

Analyze/ Strategize

Source Qualify

Negotiate

Award

Requisition or Spot Source

Approve

Assign Order

Receive

Invoice

Strategic Procurement Enables the complete source to contract process and the consistent improvement in purchasing activities

Operational Procurement Enables complete procure to pay process from the daily requisition, including spot sourcing, to the order and pay process for all goods and services



Legend

User action System activity

SAP Sourcing to ERP Summarized Integration

SAP Sourcing Business Suite 7

Contracts Requisition Order Invoice Strategic Sourcing

Contract Lifecycle

Mgmt

Supplier Mgmt



SAP Procurement Solutions Deliver Choices for Deployment

On-demand:

SAP

Business process outsourcing (BPO): Enabled through partners

On-premise:

SAP

SAP Delivers on-premise,

hosted, and on-demand deployment options

Enables a common experience across all procurement solutions

Supports additional choice of deployment while extending existing investments

Partners Deliver BPO offerings and

other flexible deployment options


SAP Sourcing / Contract Lifecycle Mgmt Setup page Aug 2011



Setup functionality

Setup is the area of the application where most application configuration and setup is done

The setup area consists of four major sections System Setup Master Data Document Setup System Administration

Access to the various areas of setup is controlled through the security profiles and access rights of a particular usertypically end users, for example, wont have access to much (or anything) within setup.

Access is also impacted by deployment mode (e.g., Public OnDemand users do not have access to all functionalities)

There are many possible users of the setup components, however: Key user Business analyst Technical configuration user System administrator



Setup area

System Setup Master Data Document Setup

System Administration

Typical User(s) Technical Configuration User, Key User

Key User, Business Analyst

Key User, Business Analyst

System Admin, Technical, Key User

Description Various technical configurations such as: reporting, custom fields, user interface, scripting, and workflow

Master and configuration data to support the business documents

Document configuration data to support the process and functional use of the business documents

User and security management, import and export tools, and various system monitoring functions

Key Objects Query Definitions Extension Definition Localized Resources Page Customizations Script Definition WYSIWYG

Product Category Material Purchasing Organizations Purchasing Groups Company Codes

Document Report Configuration Document Types Configurable Phase Definitions Contract Document Libraries

Internal User Accounts Security Profiles Import Data



Demo

Demo Setup page

Highlight extension definition and localized resources on System Setup tab

Highlight organizational setup data on Master Data tab

Highlight Projects area on Document Setup tab

Highlight Internal User Accounts and Security Profiles on System Administration tab


SAP Sourcing / Contract Lifecycle Mgmt Localized Resources Aug 2011



Agenda

Localized Resources General Extensions

Definition Attributes Collections

Difference in attribute / collection storage Browsing Extension tables Some DOs and DONTs



Setup functionality

Used throughout the user interface to support multiple languages

Each user interface label is a localized resource A localized resource is uniquely identified by: A bundle A resource id

A localized resource has a Default Value Override Value Values per each installed language pack

The application comes delivered with 1000s of localized resources

New localized resources are created in an implementation as needed

Localized resources are maintained in: Setup > System Setup > User Interface > Localized Resources



Example Localized Resource

Bundle = cterms Resource ID: cterm.value Default Value: Value (what is shown if locale-specific

entry is not provided) Locale-Specific Entries: translations for each language

Tip: English is not a language packit is the default



Where are localized resources used? (1/2)

User interface labels Field labels Tabs Buttons Column Headers

Error message text



Where are localized resources used? (2/2)

Value List Values Names of certain objects e.g. queries reports

Extension attribute names



Localized Resources Best Practices

Re-use SAP provided localized resources when possible Search by bundle (cterms) or value

Create new localized resources when the value doesnt exist Always use a consistent bundle name for easy searching and

migration (recommendation: custom) The resource id can be used to help name the usage of the

localized resource (for example, the module area, extension area, etc.)

Translations are your responsibility

When modifying a localized resource value, you should plan to modify each of the translations as well



Extensions General

Extensions are custom fields / collections

that can be added to any business document or master data object (including User Defined)

This is accomplished by creating an

extension definition for the class to be extended and then adding the attributes (fields) to that definition.

The fields / collections are stored in

dynamically created tables.



Extensions Extension Definition

In Setup System Setup Configuration Extension Definition

Using the Extended Class Name dropdown, select The Class (object) to be extended



Extensions Extension Attributes

Adding an attribute:

Internal Name Database Column Attribute Display name Field name in the UI

(localized resource) Data Type data type since this equates to column

qty and type it is not changeable once saved

NOTE: Display After, Required and Read Only are better supported as page customizations



Extension Attributes

String: Character string up to 256 characters can be sized as needed (256 by default)

Integer: Basic whole number ( 1 356 etc ) Decimal: Floating point value. Precision can be

specified Boolean: True / False equates to a check box in the UI Date Time: Includes both date and time information Date: Includes only date URL: A link to either local files or to other internet

accessible content Object Reference: Reference to another business

document or master data object Value List: Drop down lists either standard or custom Attachment: File attachment (stored as a BLOB) Amount: Decimal value followed by a unit of measure Price: Decimal value followed by a currency Text: A rich text field (AKA big text) allows formatting

and larger capacity up to 4K characters



Extensions - Attributes

The attribute display name will be the field text in the UI

NOTE: the Database Table name is shown as well



Extensions - Attributes

By default extensions are positioned at the end of the header page fields



Exercise 1

Objective Familiarize yourself with the process of creating extensions

Exercise Based on your group and object assignments, Create Date/Time extension(s) that will

capture a validity range.



Extensions Extension Collections

What are Collections? Collections are tables of rows and columns

The extension includes the definition of the columns of the table

The user adds rows to the table (collection)




Extension collections are groups of attributes that allow for multiple occurrences o The fields (a table of values) initially the collection name and internal name must be

specified




Subsequent additions to the collection are achieved by selecting use existing collection and picking the proper collection




Notice the separation in the single attributes and the collection. Also notice the extra attributes. By default these are hidden but can be exposed by.




Selecting the attribute, and changing the visibility from none to Internal Only, External Only or Internal and External



Resulting Extension Collection

The results of the field and collection created



Extensions - Storage Differences / Attributes / Collections

Attributes There is 1 table for all single attributes of an extension

definition . Each object instance has a row in the table that contains a reference to the parent Relationship 1-1

Collections Each collection has its own dynamic table since there

N entries for a collection per document. Relationship 1- N



Extensions Browsing the extension tables



Extensions Browsing the extension tables Attribute View



Extensions Browsing the extension tables- Collection view

Note 7-9 reference to parent object

11-13 The object ref to user attribute

22 The string attribute (defaulted)



Extensions Dos and Donts

Do consider and plan carefully. Even though you can make mistakes go away by making the extension inactive the data and infrastructure remain in the DB

Do define the value list type before adding the extension using the value list type

Dont make a single extension field Required or Read Only in the attribute definition. Do that with a page customization instead. NOTE: collection fields cannot be affected by page customizations should making them Required or Read Only in the extension definition is necessary

Dont rely on the display after to position multiple extensions on a page. Again use page customizations. Do use the display after to place the extension on the correct tab.



Exercise 2

Objective Familiarize yourself with the process of creating extension collections.

Exercise Based on your group and object assignments, create an extension Collection to capture

Savings Entries. This should include: A savings amount entry Who entered the entry A display of when it was entered A field to entry comments


SAP Sourcing / Contract Lifecycle Mgmt Page CustomizationsAug 2011


Page Customizations



Configurations Page Customization Any of the Standard fields / extensions in any object in SAP Sourcing can be customized Hide Change Field Label Hide Field Label Make editable/read-only Change Field position Make required Add Pre and Post Text Add Description (mouse over tool tip) Change Checkbox Label Hide Checkbox Label Make Price Currency read-only Object Picker (Query Group) Add to Quick Create

Dividers between fields can also be customized



Customization Descriptions

Hide - Remove the field from the UI (Dont try this on required fields) Change Field Label - Change the text of a field (Localized Resource) Hide Field Label - Leave the field and just hide the label Make editable/read-only Make a field read-only Change Field position Move the filed in a relative position in the UI Make required Force the field to be set. (becomes part of validation) Add Pre and Post Text Allows for clear instruction on field content Add Description (mouse over tool tip) same as above but temporary Change Checkbox Label Specialized version for checkboxes Hide Checkbox Label Specialized version for checkboxes Make Price Currency read-only Price editable Currency fixed Object Picker UI specific changes to pickers ( ! auto complete ) Add to Quick Create Add this field to the Quick Create UI



Configurations Page Customization

Step 1: Locate the Page's UI Metadata Go to the object you want to

change Click on the Reference Guide

Link In the Class Reference page

that comes up, toggle to UI View

Locate the page where you want to make the change



Configurations Page Customization Step 2: Create a Page Customization Use the UI ID field obtained from the Reference Guide. Or by using the dropdowns in the

Page Customization UI if this is the first time this page is being modified. An example might be projects.projects.ui.buyside.default



Configurations Page Customization

Step 3: Add Element Customization Find Field ID of field to be

changed Add many different fields or

one field many times If text is used, you will create

a localized resource



Before After

Configurations Page Customization Step 4: Test Your Changes



Live Demo

Requirement: Change the Description Field in all Projects to: Have a field label of Project Scope Make it required Add a tool tip that describes what the description field should

include



Configurations Conditional Page Customizations

Page Customizations can be conditional using dimension capabilities

If Dimension Field (which is of type Dimension Field Type) has the value Dimension Value, then apply the page customization override

Example: If DOC_TYPE (which is of type Project Type) has the value Category Project, then apply the page customization override

Dimension Field: The field ID on which the conditional logic is based

Dimension Field Type: The data type (class) of the Dimension Field

Dimension Value: The value which will make the condition true and apply the page customization override

NOTE: Page customizations are applied when you enter the business document only; they are not applied on page refresh, save, etc. So, the dimension field should be a value that is set before entering the business document.

Ntv



Another Example of Conditional Page Customizations

Example Requirement: Hide the extension field Financial Impact (FIN_IMPACT) for all users except members of the Financial Audit Team Solution: Create 2 page customization overrides in the

page customization:

Field: FIN_IMPACT, Hidden property: No, Dimension Field: , Dimension Field Value: Financial Audit Team group The above makes the field visible for the specified group

Field: FIN_IMPACT, Hidden property: Yes The above makes the field invisible for all other conditions



UI Configurations Page Customization Exercises

Exercise 1 Create a page customization override on

the project object that makes the description field a required value.

Exercise 2 Create a series of page customizations to

change the order of the first 3 fields.

Objective: Become familiar with general and dimensioned page customizations


WYSWIG Customization



WYSIWYG Capabilities

Easy user friendly way to create page customizations. Drag and drop for positioning, Click on field to see / set options

Supports: (Standard and Extension Fields) Positioning of fields Hiding fields Making fields required Making fields read only Overriding field labels* Adding tool tips* Adding Pre Post Text*

Provides access to Value lists in that UI, and a link to add extensions NOTE: Only users with create access to localized resources



Access to WYSIWYG customizations

Access to these customizations is dependent on the current users access to the master data object or Business document.



WYSIWYG UI



WYSIWYG actions

Field positioning select (CLICK and HOLD) the field and a movement indicator will appear. Drag the field to the desired location release the mouse. Save changes

Note: For objects that support Document Types select the

Document Type to apply the changes to.

Field label and other modifications. Click on the field label. A small window with the available options appears. Complete the needed modifications. Save changes

Each save creates or modifies an actual page customization. In cases where objects have internal and external visibility we automatically generate the buyside and sellside customizations.

N

D



Limitations

By default customizations are dimensioned by type. If the user didnt want this behavior or dimension by another means, this requires direct modification of Page Customization

If internal and external visibility needs to be different on a document that supports both these differences need to be maintained manually

No access to newer more advanced customizations Object picker Modifying content of collection displays

No access to UDOs

No ability to perform tab label changes or tab description changes



UI Configurations WYSIWYG Exercises

Objective Become familiar with general and dimensioned page customizations

Exercise 1 Create a WYSIWYG override on your assigned project type that makes the description field

a required value and changes the description label to Project type description

Exercise 2 Create a series of WYSIWYG actions to change the order of the first 3 fields back to where

they were originally.


SAP Sourcing / Contract Lifecycle Mgmt Reports and Queries November 2011



Course Assumptions & Objectives

Assumptions Proficient and comfortable with SQL Basic understanding of SAP Sourcing and its use

Objectives Gain a deeper understanding of query development in

SAP Sourcing Learn about specific objects and how to query them Learn tips and tricks that will assist with advanced

query development Workshop where you can develop your own queries

with the guidance of SAP professionals



Agenda

1. Introduction to Queries

2. SAP Sourcing Query Infrastructure

3. Reference Materials

4. Developing Queries

5. Additional Reporting Capabilities

6. Group Workshop

7. Schema Review

8. Advanced Reporting Concepts

9. Appendix

10.Common Errors

11.Customer Support Expectations


Introduction to Queries



Introduction to Queries Overview

Queries are a major part of SAP Sourcing as they provide customizable access to data. SAP Sourcing Query Infrastructure

A typical query is a single SQL SELECT statement. SAP Sourcing adds powerful functionality that enhances the query development and results presentation, and provides the integration of the SQL statement with the application.

Key query capabilities are as follows: Formatting (Formatting of each results column, incl. Links, Pictures, etc.) Filtering (One or more user supplied parameters with wild card support) Paging, Sorting and Searching (Support for sorting and searching within the returned result set) Totaling (Ability to generate column totals while still returning detailed results) Attribute/Token Substitution (Substitution significantly simplifies the development and enhances the

usability of common query features) Charting (Automatic generation of various chart types from the query results)

The following slides show examples for the use of Queries in SAP Sourcing.



Introduction to Queries List Pages

List Pages Queries are used to generate List Pages Example: All Projects Query in the example below Project Management > Projects > All Projects



Introduction to Queries - Object Pickers

Object Pickers Queries are used for Object Pickers Example: Search Organizational Units by

Name Query in the Organizational Unit picker shown below



Introduction to Queries Workbench Channels

Workbench Channels Queries are used as content of Workbench Channels Example: My Projects Query in the example below (Projects List Channel)



Introduction to Queries Query Groups

Query Groups (used for menus, lists, pickers and other selection areas) Queries are part of Query Groups Example: All Projects Query in the FCI-ProjectBuyList Group or the Query Search

Organizational Units by Name in the FCI-BusinessUnitBuyPicker Group

Query Group used on a menu Query Group used on a list Query Group used on a picker



Introduction to Queries - Reports

Reports (used on reports tab, document reports, desktop channels) Queries are providing the data for tables and charts in Reports Example: Historical Usage Query in the example below (Historic Usage Report)



Introduction to Queries Document Reports

Document Reports (Run from Reports menu on a specific document) Queries are providing the data for tables and charts in Document Reports Example: Project Schedule Summary and Project Schedule Extract Queries in the

example below (Project Schedule Extract Report)



Introduction to Queries - Dashboards

Dashboards Queries are used to provide the data for Dashboards Example: Contract Dashboard - Search Master Agreements and Agreements Query in the

example below (Contract Performance Dashboard)


Query infrastructure



SAP Sourcing Query Infrastructure Availability per Deployment Mode and Licensing

Capability Licensed OnPremise

Licensed Hosted

Private OnDemand (Premium)

Public OnDemand (Premium)

Public OnDemand (Standard)

Creation of Custom Queries Yes Yes Yes Yes* No

Creation of Custom Reports Yes Yes Yes Yes* No

Creation of Custom Dashboards Yes** Yes** Yes** Yes* No

Customization of Query Groups Yes Yes Yes Yes* No

Customization of Reports Page Yes Yes Yes Yes Yes

Customization of Document Report Toolbar

Yes Yes Yes Yes Yes

Creation of Report Channels Yes Yes Yes Yes Yes

* Requires additional service from SAP Service Delivery since the Key User is not authorized to perform these tasks themselves in the Public Edition.

** SAP Business Objects Dashboard Design tool is required to adjust Dashboards



SAP Sourcing Query Infrastructure Setup (1/2)

Most of the elements of the SAP Sourcing Query Infrastructure can be configured in the Setup > System Setup > Queries and Reports

The availability of some of the links (e.g. Query Definitions, Query Groups, etc.) is depending on (tenant) security settings.



SAP Sourcing Query Infrastructure Setup (2/2)

Document Reports are configured in the Setup > Document Setup > General > Document Report Configurations.

Desktop Channels are configured in the Setup > System Setup > Workbench > Desktop Channels



SAP Sourcing Query Infrastructure Query Definition

Query Definition Includes annotated SQL (or calls stored procedures), results, filters, chart details Allows you to Preview (NOTE: Charts not shown in preview)



SAP Sourcing Query Infrastructure - Report

Report Collection of report elements, which can be queries or dashboards Used on reports tab, document reports, or desktop channels Can be emailed to users



SAP Sourcing Query Infrastructure Report (Setup)

Setup > System Setup > Queries and Reports > Reports Report Elements Tab Used to add query definitions and Xcelcius definitions to a

report and to reorder the display of the report results.

Reports Page Layout Tab Definition of the default layout of a report page when it is

viewed as a PDF. This is not applicable to an Xcelsius definition.

Changing the page layout will override both the hard-coded defaults and the report pages' system properties for this report.

Reports Access List Tab List of users, groups and companies who are authorized to

edit and/or execute the report



SAP Sourcing Query Infrastructure Query Group

Query Group Collection of Query Definitions Used for Menus, List Pages, Pickers and other selection areas



SAP Sourcing Query Infrastructure Query Group (1/3)

Setup > System Setup > Queries and Reports > Query Group Standard Query Groups are available for all business objects. Leaving no need to create custom query groups Custom Queries can be to added to a standard Query Group and optionally replace standard queries Query Groups are used for different purposes depending on the value of the their Query Use field (see next slide for more details) In general, the internal names of the query groups follow a pattern: *buypick* - Buyside pickers *buylist* - Buyside lists *sellpick* - Sellside pickers *selllist* - Sellside lists



SAP Sourcing Query Infrastructure Query Group Setup (2/3)

Query Use: List Every business object has one query group of

type List which is used to bundle queries which are used to display the business object on list pages with varying result fields and filter parameters.

Query Use: Picker Every business object has one query group of

type Picker which is used to bundle queries which are used to display the business object on Object Pickers

Query Use: Selection Every business object can have multiple query

groups of type Selection. Those query groups are used for special purposes like object migration and export or as menu entries and should generally not be customized.



SAP Sourcing Query Infrastructure Query Group Setup (3/3)

Adding Custom Queries to Standard Query Groups Default Query Query which will be executed on lists or pickers by default Use for auto complete Query which will be used for auto completion in pickers (user types

in the picker field, rather than opening up the picker window) Remove Query From Selection List Queries can not be selected by the end user. Often

used to replace standard queries with custom queries by removing the standard query Include in SRM Navigation Queries are listed in the navigation menu



SAP Sourcing Query Infrastructure Reports Page

Reports Page (Analysis Reports Setup) Setup your own sections Attach reports



SAP Sourcing Query Infrastructure Reports Page Setup (1/2)

Setup > System Setup > Queries and Reports > Analysis Reports Setup

The content of the reports page is implemented as a hierarchy with sections and groupings (categories, subcategories)

Main Category

Sub Category 1



SAP Sourcing Query Infrastructure Reports Page Setup (2/2)

Sub Category 2

The actual reports are items of sub category 2

Categories of all levels are only appearing in the UI if they are containing reports which are not hidden and can be accessed by the current user



SAP Sourcing Query Infrastructure Document Report

Executed from the Reports toolbar within a business object Add new reports to the toolbar Remove or hide existing reports



SAP Sourcing Query Infrastructure Document Report Setup (1/2)

Setup > Document Setup > General > Document Report Configuration The Document Report Configuration is used to manage the list of reports that appears in

the dropdown list for the Reports toolbar. Locate and click the link for the business object whose reports should be customized (e.g.

Project Document Report Configuration to customize the report toolbar for Projects.



SAP Sourcing Query Infrastructure Document Report Setup (2/2)

Use Add [Internal/External] Report to add (custom) reports to the report menu which will be available for internal (buy-side) or external (sell-side) users.

Check Open New Window to open a report in a new (popup) Window This option should not be used when the report has links to further reports or documents. Links

typically require breadcrumbs, but breadcrumbs are not supported in a popup window. Use Hidden to hide (standard) reports



SAP Sourcing Query Infrastructure - Workbench Channels

Queries and Reports are mainly used in two type of channels Report Channel (left side of screen) List Page Channel (right side of screen)



SAP Sourcing Query Infrastructure Workbench Channels Report Channel The reports which is shown in channel is often a summary, just a chart or contains data

which is optimized for the width of a channel. In addition it may limit the number of visible rows to fit all data in the channel without scrolling.

More Details is linking to a second report which will be opened using the entire screen size. Most often containing the same data but with more details (columns) and/or more rows.

4 Customizable Report Channels are delivered by default (Report 1 to Report 4). Additional ones can be created using Setup > Desktop Channel



SAP Sourcing Query Infrastructure Workbench Channels List Page Channel

Using queries out of the List query group of business objects Provides Saved Search capability Filter Parameter customization Actions like New Search within the result set Sorting Column personalization



SAP Sourcing Query Infrastructure Relationship between infrastructure key elements

Query Definition

Report

Query Group

List Page

Picker

Analysis Page

Document Report

Has 1 or more Is of type

L

Has 1 or more Refers to 1 or more

Refers to 1 or more

Desktop Channel

Refers to 1

WorkbenchPage

Refers to 1 or more



Exercise Note

The following 3 exercises require that users edit the same object (e.g., analysis reports setup). As a result, it is recommend that some students begin with exercise 1, some with exercise 2, and some with exercise 3. this will limit the delays while students wait for other students to complete their changes.



Exercise 1

Objective Familiarize yourself with the Query Definition, Report,

and Analysis objects Exercise Find the Query Definition named: FCI-ProjectSummary Duplicate the Query Definition You will need to enter

the Internal Name Add the Query Definition to a new Report Add the Report to the Reports Page



Exercise 2

Objective Familiarize yourself with the Query

Definition and Query Group Exercise Find the Query Definition named: FCI-

DocProject Duplicate the Query Definition, giving it a

new display name (new localized resource)

Add the Query Definition to the FCI-ProjectBuyList Query Group

Hide the SAP Sourcing standard FCI-DocProject (only 1 student will be able to do this

View the Projects list to see the new query used



Exercise 3

Objective Familiarize yourself with the Query Definition, Reports,

and Document Report Configuration Exercise Find the Query Definition named: FCI-

ProjectScheduleExtract Duplicate the Query Definition Add the Query Definition to a new Report Find the Project Document Report Configuration Add the new Report to the Project Document Report

Configuration View the report in a Project (NOTE: The project must

have a schedule for the report to be useful)



Exercise Review

Query Definition

Query Groups

Reports

Document Report Configuration


Reference Material Queries



Reference Materials

Reference Guide Access via Reference Guide Link Class Reference Lists ALL classes Enables navigation from class to class Shows database schema and column types Includes class id (number) and logical name (string) that are used in classes

Database ERD

Demonstrate reference guide and information available in it



Reference Materials

On-Line Help Access via Help Link or via SAP Help Portal

http://help.sap.com/content/documentation/sbs/docu_sbs_esourcing.htm Guide

Browse Full Schema Setup > System Setup > Queries and Reports > Browse Full Schema

Browse Extension Schema Setup > System Setup > Queries and Reports > Browse Extension Schema



Exercise 4

Objective Familiarize yourself with the RG

Exercise Find the table name for Projects Identify the table name to which the

Internal Category data member refers Find the class logical name for RFxs Find the class id for Vendors



Exercise 4 - Solution

Objective Familiarize yourself with the RG

Exercise Find the table name for Projects: FCI_PRO_PROJECTS

Identify the table name to which the Internal Category data member refers FCI_MAS_INTERNAL_CAT

Find the class logical name for RFxs rfx.RFXDoc

Find the class id for Vendors 607


Developing Queries



Developing Queries - Query Definition key Components

Query SQL statement to be executed. Includes query attributes for advanced capabilities

Result Fields Definition of result fields and their visibility and sort order

Filter Prompts Definition of filter prompts

Chart Definition Definition of chart(s)

Access List List of users, groups and companies who are authorized to edit and/or execute the query



Developing Queries Query Definition (Query Tab)

Inactive Indicates whether query is active or not Display Name The name that will be displayed in the user interface when the query is

executed Internal Name Unique identifier for the query. Typically a word with no spaces and

starting with CUSTOM- (e.g., CUSTOM-ProjectsByOwner) Description A description of the query Query String The annotated SQL for the query Stored Procedure Indicates whether the query string is using a stored procedure Execution Type Always choose SQL. It means that the specified SQL statement defined

in the Query String will be executed Max Rows Returned The maximum number of rows returned by the query assists with

performance if the query potentially will return a lot of rows Rows Per Page The number of result rows that will be displayed per page Category A categorization of the query (no logic dependent on this) Workbook Template An Excel spreadsheet template used for Export Excel capability Java Hooks Only show for Java queries. For SAP use only.

2011 SS1 SAP AG

Open query with name FCI-ProjectActivityByPhaseChart and show query tab



Developing Queries Query Definition Result fields (Column Type independent)

Database Column Name The SQL for the column (can be a simple column name, a complex sub-select, or anything in between) Column ID Unique identifier of a column The Column ID is the same as the Database Column Name field when the database

column name is a simple column name Use a unique string for all other column definitions (e.g. SQL functions, static values, etc.)

Examples:

Database Column Name Column ID Usage

T1.DISPLAY_NAME T1.DISPLAY_NAME Simple column name

607 AS CLASSID ClassId Static value for all rows

UPPER(T1.DISPLAY_NAME) UpperDisplayName Column name with formatting

T1.LAST_NAME COALESCE(T1.FIRST_NAME,'') FullName

Concatenated values, with the FIRST_NAME column value not required

COALESCE(T1.TOTAL_EXPECTED_PRICE, 0) TotalExpectedPrice Define a value to use for null data

SUM(COALESCE(T1.TOTAL_EXPECTED_PRICE, 0)) SumTotalExpectedPrice SQL sum function



Developing Queries - Query Definition Result Fields (Column Type independent)

Display indicator Allows fields to be hidden (useful when wanting to setup special columns for sort order)

Column Header Resource The string displayed for the column in the result set Hide column header Allows column headers to be hidden (recommended for columns

that contain some action icons, like Delete or Edit) Column Type The type of data being returned (also specialized column types for drill

downs, hyperlinks, etc.) Repeating Column Columns with this indicator in a pivot query will be expanded to

multiple columns Default Display Indicates whether this column will be displayed to the end user by

default Sort Order Indicates the number within the sort for this column only applies when the

token is part of the Query String. Ascending Indicator Indicates whether the sorting direction should be ascending or

descending



Developing Queries - Query Definition Result Fields (Column Type dependent)

Display Widths Width of the table column in either characters or pixels Applies to all but Quantity Unit Object ID, Class ID, Object ID, Monetary Currency

Show Image Display of an image together or instead of the value being returned Applies to String, String Resource, Enumeration, URL

Resolve Token(s) in Value Indicates that the value of the string field in the query results might contain one or more tokens that must be resolved. Applies to String, String Resource, URL

Total Indicator Used for numeric columns allows for totals on the page Applies to Number, Monetary Amount, Quantity Amount

Show Seconds Include seconds along with hours and minutes in the formatted time value Applies to DateTime, Time

Convert Scale To Allows reduction of decimal places Applies to Number

Link Image Source A way to have an image displayed in the results (e.g., red, yellow, green indicator) Applies to URL



Developing Queries Query Definition Result Fields (Column Type dependent)

Enum Type Name Applies to Enumeration

Currency Conversion Source Applies to Monetary Currency

Conversion Unit Applies to Quantity Unit Display Name

Dimension ID Used in Spend Reports not covered today Applies to String, Date

Open query with name FCI-ProjectActivityByPhaseChart and show results tab



Developing Queries Query Definition The SQL Query Strings will commonly be structured like:

SELECT FROM .TABLE1 T1, .TABLE2 T2 WHERE T2.PARENT_OBJECT_ID = T1.OBJECTID AND UPPER(T1.DISPLAY_NAME) LIKE AND T1.INACTIVE = 0 AND T1.IS_TEMPLATE = 0 AND T1.CONTEXTID =

token will be replaced by SQL generated based on the defined result

fields token ensures that the proper database schema is used token refers to the filter prompt with the defined parameter name

(value of the Column ID field) token enforces desired ordering as defined on the Result Fields tab Ensure that each table is joined to avoid Cartesian joins Filter out Cancelled and Closed documents with INACTIVE = 0 Filter out document templates with IS_TEMPLATE = 0 Ensure documents from the correct context are included with token Use UPPER to allow filtering to be case-insensitive. Also make sure to check Convert to

Upper Case for the Query Parameter.



Exercise 5

Objective Create a basic query

Exercise Create and preview a query

definition for Projects that retrieves the project name



Exercise 5 - Solution Query Header



Exercise 5 - Solution

Query Result Fields and Details



Developing Queries Query Definition Include Extensions

The query string must include the extension table T3

OR T4

The extension table must be joined T3.PARENT_OBJECT_ID = T1.OBJECTID (no outer join required)

OR T4 RIGHT OUTER JOIN

.FCI_PRO_PROJECTS T1 ON (T4.PARENT_OBJECT_ID = T1.OBJECTID)

Column names can be found in Browse Extension Schema (they dont always match the extension attribute internal name)



Exercise 6

Objective Create a query using an extension table

Exercise Modify the query created in Exercise 5

adding in a string extension field (PROContractor) to the result set



Exercise 6 Solution

Query



Exercise 6 Solution

Result Fields and Details



Developing Queries Query Definition SQL Common Patterns

Basic join concepts and keys Schema is generated automatically using advanced development tools Most tables have common columns due to the object oriented nature of the application

Key columns OBJECTID Numeric identifier for this object

CONTEXTID SAP Sourcing has the concept of multiple enterprises being able to reside in the same Oracle

database Used in where clause with token

UNIQUE_DOC_NAME Unique key for the object In many cases this is automatically generated by a numbering table or some other mechanism

DISPLAY_NAME Human readable name for object



Developing Queries Query Definition SQL Common Patterns (continued)

Key columns (cont.) IS_TEMPLATE For those objects that are template based indicates that the object is a template when set to 1.

Normally your queries will have a selection criteria with this set to 0 (no templates)INACTIVE Other than legal documents SAP objects are not deleted from the system. They can be hidden by

marking them as inactive. When this column is set to 1 it means the object is in an inactive state. Normally queries will have a selection criteria with this set to 0 (only active objects)

PARENT_OBJECT_ID If the object is a subordinate, RFx Vendors as an example, this column contains the parents objectid.

XXXX_OBJECT_ID If the object has a reference to another object these columns will contain that objects objectid. XXXXX

will give you a hint as to what other object it is referring. LOCATION_OBJECT_ID as an example refers to a location object



Developing Queries Query Definition Filter Prompts

Parameter Name A string with no spaces. If the same name is used multiple times, the parameter will only be displayed

once Prompt Message Resource The string the user will see next to the prompt in the user interface

Default Value The default value for the prompt (has specialized value when doing Object Reference prompts)

Get Token Use data from the current or parent business object as default value

Data Type The type of prompt field

Value List Type For value list prompts, indicates which value list to use

Default Operator Default operator used for this parameter



Developing Queries - Query Definition Filter Prompts (Checkbox Options)

Convert to Upper Case Used for case insensitive comparison Prefill value from Cache Always check Optional Typically used with token Hidden The prompt is hidden from the user (typically used on drilldown reports or hard-

coded prompts) Locked The prompt cannot be changed by the user (typically used on drill down reports) Show By Default Indicates that this filter parameter should be included in a search in the

Advanced List page by default Fixed Operator The operator can not be changed by the end user (applies to list page

queries only)

Open query with name FCI-ProjectActivityByPhaseChart and show filters tab



Developing Queries Query Definition Filter Prompts

Filter prompts allow the results of the query to be limited

Filter prompts are typically going to be used by a user, but can be hard-coded

Basic filter prompt data types: String, Integer, Big Decimal, Date, Date Time, and Boolean

Advanced filter prompt data types: Value List: Must choose the list to use Enumeration: Must choose the enumeration type Object Reference: The Default Value must be of the form: NULL::NULL For example, to have a Vendor object reference filter, the default value would be: NULL:607:NULL



Exercise 7

Objective Add an object reference filter to a query

Exercise Modify the query created in Exercise 5/6,

adding in a Filter Prompt of type Object Reference to filter for projects by the owner (a user)



Exercise 7 Solution

Query



Exercise 7 Solution

Filter Prompt and Details



Developing Queries - Query Definition Optional Filter Prompts (AND Token)

Execution:

SQL: Filter Prompt:

Check Convert to Upper Case to enable case insensitive comparison Check Optional Check Fixed Operator, it is mandatory for this token



Developing Queries - Query Definition Optional Filter Prompts (AND_OP Token) Execution:

SQL: Filter Prompt:

Check Convert to Upper Case to enable case insensitive comparison Check Optional Uncheck Fixed Operator to let the end user choose the operator



Developing Queries - Query Definition Token Review

Online Help SAP Sourcing > Setup > System Setup > Queries and Reports > Query Definition: Attribute

Substitution

Show the online help and tokens



Developing Queries - Review

What is a Class Id? Class Name? Where are these used? What are extensions? What token is used to access an extension table? How many extension tables will an object (e.g., projects) have? Name a place where the end-user will access a report? What are the key objects used to configure reports? Name a place where the query developer will go to get assistance on the database

schema? What naming conventions are used? How does this help? What is a localized resource? How is it used?


Additional Reporting Capabilities



Additional Reporting Capabilities Query Definition Linking to an Object

Three columns must be created in the results fields of the query Object ID T1.OBJECTID Class ID 1100 (1100 = Project) Display Name T1.DISPLAY_NAME

Alternative: the LOAD_PAGE token can be utilized, but is not commonly used

Show the FCI-AllProjects query for an example



Additional Reporting Capabilities Query Definition Using Aggregate functions

Group By can be used in a query along with aggregate functions: MIN MAX COUNT SUM

Example: SELECT T1.DISPLAY_NAME, COUNT(T2.OBJECTID) FROM FCI_RFX_DOC T1, FCI_RFX_VENDOR T2 WHERE T2.PARENT_OBJECT_ID = T1.OBJECTID GROUP BY T1.DISPLAY_NAME



Exercise 8

Objective Create a query using an aggregate function Use the string concatenation token

Exercise Create a project query that has two columns: Project Status, including the total number of projects in that status Value: the sum of all projects in the status

The results will look like:



Exercise 8 Solution

Query



Exercise 8 Solution

Result Fields



Additional Reporting Capabilities Report Drill Downs

Report drill downs are very useful for allowing navigation to increasing levels of detail For example, a summary report may show the total number of projects by category.

Clicking on the number of projects (a drill down) could show a listing of the individual projects

Report drill downs are formed using two query columns URL: This will be the string displayed to the user which will be hyperlinked. Internal Page: This will be a string result that forms the actual URL. For a drill down report, it will look

like: /analysis/report?queryGroupName=&=&&link_crumb=true For example:

/analysis/report?queryGroupName=CUSTOM-DrillDown&Category= || T1.INTERNAL_CAT_OBJECT_ID || :603: || T1.INTERNAL_CAT_OBJECT_NAME || &&link_crumb=true

Show the RFx Summary Report by Workflow Phase report (Enterprise Sourcing WB)



Additional Reporting Capabilities Charting-Overview

SAP Sourcing supports various chart types (Variations of Bars, lines, Pies, Radars)

Charts are possible through a Chart Definition

Show the RFx Summary Report by Workflow Phase report (Enterprise Sourcing WB)



Charts Charts Chart

Definitions Definitions

Chart Definitions

Query Definitions Definitions

Query Definitions

Additional Reporting Capabilities Charting - Overview

Chart Definitions can be added to the Query Definition which provides for a user selectable drop down

Query Definitions can be associated with a Report Reports can be shown in various UI elements such as Desktop Channels or Report pages

Charts

Definitions

Query Definitions

Definitions

Chart Definitions

Desktop Channel Report



Additional Reporting Capabilities Charting - Features

2 different formats of charts: Flash and Jpeg image Runtime selection of charts and chart definition on a

Report User Personalization of charts Drill down on charts Export to PDF Linear and Logarithmic scaling mode Support of 2 dimension charts SAP Standard and SAP Business Objects Flash based

color palettes 12 different types of charts



Additional Reporting Capabilities Charting

Charts do not show during query definition preview Charts are developed over a single numeric value Data must be a numeric column Data Labels and Series must be Strings Series provide additional dimensions Developer must sort and group the results of the query

for the chart Developer must specify the max number of data points Data over this max this can be bucketed into an

Other category



Additional Reporting Capabilities Charting Chart Definition

Chart Type Chart types in this drop down are dynamically shown

based on the selection of two combinations: 1 dimension, 1 measure 2 dimensions, 1 measure

Chart selected here would be treated as default chart. Multiple chart types would be shown at run time and end users can change from the default chart to the chart of there choice.

Disable Multiple Chart Selection Users can not change the chart type

Column Containing Label for Data The non numeric result fields defined in the query. This is

default dimension. Column Containing Data The column which provides the numeric data for the chart

elements. This is a measure. Each row in the result set that does not have a value for the

data column will not be represented in the chart. If none of the rows has a value for the data column, the chart is suppressed.



Additional Reporting Capabilities Charting Chart Definition

Maximum Number of Data Points Maximum number of data points to be used in the chart

Use Other Category and Sort Data This field is used if the number of rows returned exceeds the value in

the Maximum Number of Data Points field. Check to aggregate the additional rows into a single Other category in the chart.

Column Containing Label for Series The Result Field column used to label the series elements. This is

another dimension value.

Maximum Number of Series Maximum number of series to be used in the chart.

Use Other Series and Sort Data Same as above for Maximum Number of Series

Legend None: Suppresses the legend. East: Displays the legend at the right edge of the chart.

Scaling Mode Linear: Useful when the data covers a small range of values for e.g. 1

to 50 in the division of 1, 2, 3, 4, etc. Logarithmic: Helpful when the data covers a large range of values



Additional Reporting Capabilities Charting - Example

Developer must organize the result to fit the chart If I want Projects budgeted value

by Status I will SUM the value and GROUP BY status. (example)

If I want Projects budgeted value, by Status and Priority I would include the priority in the GROUP BY condition. (example)


Schema review



Schema Review Vendor

Key tables FCI_MAS_VENDOR FCI_MAS_CONTACT

Interesting columns EXTERNAL_ID is the primary key and also refers to the SAP number

Joins FCI_MAS_CONTACT.PARENT_OBJECT_ID FCI_MAS_VENDOR.OBJECTID



Schema Review RFX

Key tables FCI_RFX_DOC FCI_RFX_VENDOR FCI_RFX_RESPONSE FCI_ONT_LINE_ITEM

Interesting columns FCI_RFX_DOC.CURRENT_PHASE is an enum FCI_RFX_DOC. DUE_DATE_DATETIME

Joins FCI_RFX_VENDOR.PARENT_OBJECT_ID FCI_RFX_DOC.OBJECTID FCI_RFX_RESPONSE.PARENT_OBJECT_ID FCI_RFX_DOC.OBJECTID FCI_ONT_LINE_ITEM.PARENT_OBJECT_ID FCI_RFX_DOC.OBJECTID



Schema Review Contract

Key tables FCI_CONTRACT Master Agreement FCI_AGREEMENT Sub Agreement FCI_CONTRACT_LINEITEM Line items (for both objects)

Interesting columns VENDOR_OBJECT_NAME Vendor EFFECTIVE_DATE_DATE EXPIRATION_DATE_DATE

Joins FCI_AGREEMENT.PARENT_OBJECT_ID --> FCI_CONTRACT.OBJECTID FCI_CONTRACT_LINEITEM.PARENT_CLASS_ID = xxx AND

FCI_CONTRACT_LINEITEM.PARENT_OBJECT_ID = yyy.OBJECTID



Schema Review Auction

Key tables FCI_AUCT_AUCTION_EVENT FCI_AUCT_BIDDERS FCI_AUCT_LINE_ITEMS

Joins FCI_AUCT_BIDDERS.PARENT_OBJECT_ID ->

FCI_AUCT_AUCTION_EVENT.OBJECTID FCI_AUCT_LINE_ITEMS.PARENT_OBJECT_ID ->

FCI_AUCT_AUCTION_EVENT.OBJECTID



Schema Review Project

Key tables FCI_PRO_PROJECTS FCI_PRO_SCHEDITEMS FCI_PRO_VENDOR

Interesting columns FCI_PRO_PROJECTS.PLANNED_xxx_DATE FCI_PRO_PROJECTS.ACTUAL_xxx_DATE FCI_PRO_VENDOR.VENDOR_OBJECT_NAME FCI_PRO_SCHEDITEMS.DISPLAY_NAME

Joins FCI_PRO_SCHEDITEMS.PARENT_OBJECT_ID FCI_PRO_PROJECTS.OBJECTID FCI_PRO_VENDOR.PARENT_OBJECT_ID FCI_PRO_PROJECTS.OBJECTID



Schema Review Common Tables

Key tables FCI_DOC_LINK FCI_DOC_COLLABORATOR

Interesting columns PARENT_CLASS_ID: Identifies class that a record is used with

Joins FCI_DOC_LINK.PARENT_CLASS_ID = xxx AND FCI_DOC_LINK.PARENT_OBJECT_ID =

yyy.OBJECTID FCI_DOC_COLLABORATOR.PARENT_CLASS_ID = xxx AND

FCI_DOC_COLLABORATOR.PARENT_OBJECT_ID = yyy.OBJECTID



Review

What is a Class Id? Class Name? Where are these used? What are extensions? What token is used to access an extension table? How many extension tables will an object (e.g., projects) have? Name a place where the end-user will access a report? What are the key objects used to configure reports? Name a place where the query developer will go to get assistance on the database

schema? What naming conventions are used? How does this help? What is a localized resource? How is it used? What capability is used to add parameters to reports? How are parameters added to reports? Where should you go to add a chart to a report? What technique is used to enable a hyperlink to an SAP Sourcing document (e.g., Project,

RFx, Contract) from within a query? What technique is used to enable a hyperlink to a drill-down report?


Advanced Reporting Concepts



Advanced Reporting Concepts Database Functions

There are four types or groups of database functions recommended for use: SAP Sourcing User Defined functions which provide a common interface to commonly

available database functionality for which a common interface is not available. Example datetime functions

SAP Sourcing defined replaceable tokens which provide a common interface to common database functionality where only the name varies among database platforms.

SAP Sourcing defined user defined functions which provide application specific functionality.

A small set of database built-in functions which are believed to be syntactically and semantically equivalent across the range of supported Database Management System (DBMS)

A list of supported functions and token can be found in the embedded Excel Worksheet.

Although it is possible to use DBMS provided functions it is recommended to refrain from using functions whose syntax and semantics may vary from DBMS to DBMS or which are not universally supported such as OLAP functions; ROWNUM and RANK being prime examples.



Advanced Reporting Concepts Currency Conversions

The query definition provides a couple different ways to perform currency conversions Approach 1: Monetary Currency columns can be converted to the User Currency, Organization

Currency, or a specified Currency Approach 2: The SAP Sourcing FCI_DOC_CUR_CONVERT function can be used



Advanced Reporting Concepts Showing a Comma Separated List of Values

In certain cases, it is convenient to show a comma separated list of values in a single cell in a result set

For example, show all of the collaborators (comma separated) on a document when querying over a list of documents

SAP Sourcing includes or Oracle function to do this: FCI_GET_COMMA_LIST

This function can cause performance issues with a query it should be used judiciously

There is an Oracle function, WM_CONCAT, that also can be used



Advanced Reporting Concepts Access Lists

Access Lists allow security to be setup for reports

Very similar to document collaborators

Example: Report should only be available to System Administrators -> Add the System Administrators User Group to the Access List of the Report

An empty Access List means the report is available to all users

A populated Access List means the report is restricted to the listed users



Advanced Reporting Concepts Scheduled Tasks

Scheduled Tasks can be used to email reports on a scheduled basis Report Execution Task Configure Schedule Choose Report Choose Action: Alert (populates workbench page alerts channel) PDF (emailed) Excel (emailed) CSV (emailed) Integration Export (put on server usually requires additional configuration with SAP)

Choose Recipients Populate Filter Parameters



Advanced Reporting Concepts Defaulting a Value List Value in Filter Parameters

Some requirements necessitate that a specific value list value be the default value in a report

For example, suppose a report could be run for a year, where the filter prompt was a year value list. It likely would be desirable for the value list to default to the current year.

Unfortunately, there is no way to have it auto populate the year based on the date.

But, the year can be defaulted by using the default value on the filter prompt

The value for the default value MUST BE THE DISPLAY NAME ID from the value list value (not the display name resource)

To default the VLV filter to none, use the following construct in the default value: :616:NULL (e.g., for MA Status: 10:616:NULL)



Advanced Reporting Concepts Default Date Parameters

Date filters can sometimes be improved with default values

To have the date filter default to the current day, use the token for the default value

To have the date filter default to a specific date, the default date value MUST BE FORMATTED AS: YYYY/MM/DD

This can be useful or YTD filtering

NOTE: The construct - x could also be used in the WHERE clause of the SQL to subtract days from today



Advanced Reporting Concepts Portable SQL

As of SAP Sourcing 7.0 the following Database Management Systems (DBMS) are supported: IBM DB2 9.7 Oracle 10.2 (SP 04) and 11.x

SQL Constructs There are differences in the SQL constructs among DMBS vendors . The Word document

provides guidelines for writing SQL which is portable across the set of Database Management Systems (DBMs) supported by the SAP Sourcing product .These guidelines are not exhaustive.

Database Stored Procedures There is no universally adopted stored procedure language among DBMS vendors. The use of stored procedures in the standard product is a significant impediment to adding

support for additional DBMS to the SAP Sourcing product. The only exception is in cases where a database stored procedure is used to implement

one of the standard supported database functions when necessary to accommodate differences in SQL supported by a particular DBMS vendors functions.



Advanced Reporting Concepts Filtering using a specific Value List Value

In many cases, the query requirements necessitate that a query explicitly filter data by a specific value list value

For example, a query that retrieves only projects that are Pending

Two ways to do this: Use a filter prompt that is locked/hidden and

has the value list value as the default Hard code the filtering into the query

SAP recommends the first approach as it

is easier to maintain



Advanced Reporting Concepts Queries used in Menus

(Custom) Queries can be added to Menus by adding them to the Query Groups which are used in the Menu.

The corresponding query groups need to be located by inspecting the SRM Navigation Group inside the System Navigation Tabset (Buyside) System Toolbar.



Advanced Reporting Concepts URL Parameters & Report Format Directives

URL Parameters are used for drill down reports to pass parameter values

URL Parameters also can be used to configure report layout

&reportFormatDirectives= suppressTableGrid suppressTableColumnHeaders suppressTableToolbar

Search online help for: URL Parameters



Advanced Reporting Concepts Report Format Configuration

Allows for some advanced configuration of results Vertical display Side by Side

Example: Master Agreement Cover Page

Configured via an XML file that is uploaded to the File Attachment Container

Search online help for: query results layout



Advanced Reporting Concepts Workbook Templates

Workbook Templates: Excel workbook templates can be setup for a report Export to Excel option

The option exists on both the Query Definition and the Report (most likely the one to use) via the Workbook Template field

The Workbook Template is a reference to a File Attachment Container (Setup > User Interface > File Attachment Containers), which contains the Excel workbook: create the File Attachment Container first, the reference it on the Report

The Excel workbook can contain additional sheets, formulas, and VBA

Example for Project Summary Extract Report attached



Advanced Reporting Concepts Images Images can be displayed in the result set

Technique 1: The results contain a value list value and it is desirable to show an image for that value. Each value in the value list value should have a corresponding localized resource with a

.image suffix The value of the localized resource for the .image should be something like

/customimages/xxx.jpg Each image should be uploaded as a file attachment container with the path name like

/customimages/xxx.jpg The query should select the DISPLAY_NAME_ID of the value list value using column type

String Resource Attached XLS creates a VLV and Project extension

Load these as file attachment containers



Advanced Reporting Concepts Images Image Query

QUERY STRING: SELECT FROM .FCI_PRO_PROJECTS T1 JOIN

T2 ON T2.PARENT_OBJECT_ID = T1.OBJECTID LEFT OUTER JOIN .FCI_MAS_VALUE_LIST_VALUE T3 ON T2.STAR_RATING_OBJECT_ID = T3.OBJECTID WHERE T1.INACTIVE = 0 AND T1.IS_TEMPLATE = 0 AND T1.CONTEXTID = AND T1.DOC_OWNER_USER_OBJECT_ID =

QUERY COLUMNS: T1.OBJECTID 1100 T1.UNIQUE_DOC_NAME T3.DISPLAY_NAME_ID



Advanced Reporting Concepts Images (continued)

Technique 2: The results contain a string which resolves to a image path.

Each image should be uploaded as a file attachment container with the path name like /customimages/xxx.jpg

The query should have a column which resolves to the image path



Developing Queries Query Definition Optional Filter Prompts (DYN_* Tokens)

Execution:

SQL: SELECT FROM .FCI_PRO_PROJECTS T1 WHERE T1.IS_TEMPLATE=0 AND T1.CONTEXTID= These tokens are used to enable the Advanced List Page (adding/removing columns/filters) Both tokens have to be in the SQL. At least one manually entered condition should be placed before the

TSO150 Sourcing CLM Configuration

Documents

Transcript of TSO150 Sourcing CLM Configuration