SDPR Install BCT & Config_AT

8/3/2019 SDPR Install BCT & Config_AT

http://slidepdf.com/reader/full/sdpr-install-bct-configat 1/26

Repor t in g fo r Supp l ie r Del i very Per f o r mance Rat i ng

A D D O N . S R M_

B W

C O N F I G



10.09.2004

Reporting for Supplier Delivery Performance Rating 2

Copyright

© Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose

without the express permission of SAP AG. The information contained herein may bechanged without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400,OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBMCorporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, WorldWide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license fortechnology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products andservices mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All otherproduct and service names mentioned are the trademarks of their respective companies.Data contained in this document serves informational purposes only. National productspecifications may vary.

These materials are subject to change without notice. These materials are provided by SAP

AG and its affiliated companies ("SAP Group") for informational purposes only, withoutrepresentation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products andservices are those that are set forth in the express warranty statements accompanying suchproducts and services, if any. Nothing herein should be construed as constituting anadditional warranty.



10.09.2004


Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of

information at a glance. For more information, see Help on Help → General Information Classes and Information Classes for Business Information Warehouse on the first page of anyversion of SAP Library .

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include fieldnames, screen titles, pushbuttons labels, menu names, menu paths,

and menu options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and tabletitles.

EXAMPLE TEXT Technical names of system objects. These include report names,program names, transaction codes, table names, and key concepts of aprogramming language when they are surrounded by body text, forexample, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and theirpaths, messages, names of variables and parameters, source text, andnames of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace thesewords and characters with appropriate entries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.



10.09.2004


Reporting for Supplier Delivery Performance Rating ................................................................ 5 General Settings .................................................................................................................... 6

Configuration of SAP Business Information Warehouse ................................................... 6 Transferring Global Settings........................................................................................... 6 Defining Reporting Authorizations.................................................................................. 7 Enabling Web Reporting................................................................................................. 7

System Connections .............................................................................................................. 8 Defining Source Systems and Connecting SAP BW to OLTP Systems ............................ 8 Activating DataSources in the OLTP System..................................................................... 9 Activating DataSources in the BW System ........................................................................ 9

Business Customizing.......................................................................................................... 10 Implementation................................................................................................................. 10

Installing BI Content...................................................................................................... 10 Setting Up Supplier Authorizations............................................................................... 12 SDPR Setup ................................................................................................................. 12

Specifying Global Parameters .................................................................................. 13 Specifying Metric Categories .................................................................................... 14 Specifying Metrics..................................................................................................... 14 Specifying Valid Combinations of Metric IDs and Delivery Types............................ 15 Specifying Lookup Table for Score Points................................................................ 15 Specifying Score Calculation Rules.......................................................................... 16 Specifying Weighting Factors for On-Time Delivery ................................................. 16 Specifying Score Reductions for Discrepant Emergency Orders ............................. 17 Specifying Score Reductions for Problem Reports................................................... 17

Administration................................................................................................................... 18 Adjusting Reports ......................................................................................................... 18 Assigning Roles to Users.............................................................................................. 18 Managing User IDs for Suppliers.................................................................................. 19

Runtime Activities............................................................................................................. 21 Replication of Data ....................................................................................................... 21

Loading Master Data................................................................................................. 21 Loading Transaction Data......................................................................................... 22 Updating Supplier Ratings ........................................................................................ 23 Exporting SDPR Data ............................................................................................... 24 Examining Execution Logs........................................................................................ 24



10.09.2004


Reporting for Supplier Delivery PerformanceRating

UseThis business scenario configuration guide applies to the Supplier Delivery Delivery Performance (SDPR) scenario and the corresponding releases of the SAP applicationcomponents involved in this scenario.

Business Scenario and SAP application components

Business Scenario SAP application component withminimum release

Supplier Delivery Performance Rating SAP Business Information Warehouse (SAP BW) 3.5

SAP BI Content 3.5.3 Add-OnSAP Supply Chain Management (SAP SCM) 5

Contents

Supplier Delivery Performance Rating is a decision support application that is used toevaluate suppliers periodically. The SDPR function uses data from delivery processes. Thisdata is transmitted as parts of certain process documents, that is, advanced shipping notices(ASNs), purchase orders, release schedules, and supplier alerts. SDPR evaluates criteria thatare grouped into two categories:

• the accuracy of deliveries

• the accuracy of communication

Score points are calculated for each category, using special measuring methods, calledmetrics. Each metric calculates a score for a certain aspect of supplier performance. Thesum of all score points represents an overall rating for the supplier in a certain time period.

SDPR includes reports for accessing and displaying supplier ratings, aggregated key figuresper period, and detailed information about each process document.

Many aspects of SDPR can be customized to adapt the functional behavior to a givenprocess environment. For example, you can specify which metrics SDPR uses to calculate anoverall rating. Existing metrics can be modified, and new metrics can be introduced.Moreover, calculation rules that state if and how a metric contributes to the rating can bedefined for every single supplier. SDPR is shipped with an initial set of metrics and default

calculation rules, which can be customized during implementation.The business scenario configuration guide contains all steps required to implement thereporting functions for SDPR in SAP Business Information Warehouse . The guide specifiesthe sequence of the configuration activities, and their dependencies.

It includes information about the following topics:

• General Settings

• System Connections

• Business Customizing

Target Group

• Technical consultants

• Application consultants



10.09.2004


• Project team members during the implementation of a SAP solution

• SAP customer IT department

The System connections and Data replication sections are aimed at technical consultants inparticular, while the Business customizing section is aimed at application consultants. Theremaining sections are of equal interest to both groups of consultants. The importance of

sections to the other target groups depends on their responsibilities.

General Settings

Configuration of SAP Business InformationWarehouse

PurposeThis section describes the steps that are necessary for preparing SAP Business Information Warehouse (SAP BW) to run SDPR . SAP BW enables you to analyze data from operativeSAP applications as well as from all other business applications and external data sources,such as databases, online services, and the Internet. SAP BW provides flexible reporting andanalysis tools for decision-making support in your enterprise.

Prerequisites

You have installed BI 3.5.3 Content Add-On . For installation information, see the installationand upgrade guides for mySAP Business Intelligence on the SAP Service Marketplace atservice.sap.com\instguides.

Process FlowThe configuration of SAP BW includes the following steps:...

1. Transferring Global Settings

2. Enabling Web Reporting

3. Defining Reporting Authorizations

All of these steps are explained in more detail in the following sections.

Transferring Global Settings

UseGlobal settings include the calendar settings and units of measurement, and can be used inthe reports. If you do not maintain these settings, the reports will still work. However, units ofmeasure and dates may not appear the way you might expect them to.

Procedure

The procedure you follow depends on your specific business process:

• In many cases, BW extracts data from other source systems directly. In such cases,you can transfer the global settings from these systems. In the Administrator

Workbench in the SAP BW system (transaction RSA1), choose Modeling → Source Systems . Select your source system and then choose Transfer Global Settings in thecontext menu.



10.09.2004


• If you use fiscal year variants, you can transfer these from your FI system.Alternatively, you can maintain the fiscal year variant manually in the Implementation

Guide for SAP BW by choosing Business Information Warehouse → General BW

Settings → Maintain fiscal year variant.

Defining Reporting Authorizations

Use

If you want to restrict access to data, you must set up reporting authorizations.

Procedure

The authorizations for reporting are maintained via the authorization functionality in SAP Business Information Warehouse (SAP BW ) (transaction RSSM). You use this to determinewhich data a user can evaluate when he/she navigates within a report.

For more details on the SAP BW authorization concept and on creating reportingauthorizations, see the current BW online documentation on the SAP Help Portal at

help.sap.com and the document on Reporting Authorizations in SAPNet, Quick Link SRM →

SRM in Detail → Components in Detail → Business Information Warehouse → Documentation.

Enabling Web Reporting

Use

You need to maintain the Web Applications Server entry in the SAP BW system.

Prerequisites

You have maintained the SAP BW client.

Procedure

Refer to the guide How to... Customize BW 3.0 after an Upgrade from 2.0B/2.1C . This guide

is available in SAPNet, Quick Link BW → Service&Implementation → How To Guides → Guide 3.0.

The settings required for BW 3.0B or higher Web Applications are available in

the IMG: SAP Reference IMG → BW Customizing Implementation Guide →

Business Information Warehouse → Reporting-Relevant Settings → Web- Based Settings .

Navigation

Menu Path Transaction Code

SAP Reference IMG/BW Customizing Implementation Guide Business Information Warehouse Reporting- Relevant Settings Web-Based Settings

SPRO



10.09.2004


System Connections

PurposeThis section contains information about connecting the SAP Business Information Warehouse (SAP BW ) that runs SDPR with the Online Transaction Processing (OLTP) System thatprovides the documents from the delivery processes.

Moreover, the relevant DataSources for SDPR must be prepared in both the OLTP systemand in SAP BW .

Currently, the Inventory Collaboration Hub (ICH) in mySAP Supply Chain Management (mySAP SCM) is the only type of OLTP system that provides DataSources for SDPR .

Process Flow

Perform the steps in these guidelines in the sequence in which they appear.

Defining Source Systems and Connecting SAP BWto OLTP Systems

Use

Source systems are the systems in which the original data is created. Data is uploaded fromthe source system into SAP BW . The connections to these systems have to be created inSAP BW .

ProcedureCreateabackgrounduser inSAPBW(BWREMOTE, for example) withatleastthisprofile:......

1. In SAP BW , create a background user in SAP BW (for example, BWREMOTE) with atleast the following profile:

- S_BI-WHM_RFC (Business Information Warehouse : RFC users in SAP BW ).

2. In the operational system, create a background user (for example, ALEREMOTE) withat least the following profiles:

- S_BI-WX_RFC (Business Information Warehouse : RFC users in extraction)

For information on creating ALEREMOTE as an interactive user or CommonProgramming Interface – Communication (CPIC) user, see SAP note 161570.For information on BW authorizations for remote users, see SAP note 150315.For information on authorizations for HR data extraction, see SAP note 397208.

3. Define the logical systems that you want to extract data from. For more information, see

the Implementation Guide (IMG) for SAP Business Information Warehouse → Links to

Other Systems → General Connection Settings → Define Logical System.

4. Define the RFC connections for your logical systems in transaction SM59.

5. Use transaction RSA1. Choose Modeling → Source Systems .

6. In the context menu, choose Create

7. If you select the Automatic creation option, the DataSources will be replicatedautomatically. For troubleshooting information, see SAP note 179602.



10.09.2004


Activating DataSources in the OLTP System

Use

Before you can evaluate documents in SAP BW , you first of all have to extract them from the

OLTP systems. To achieve this, you have to activate the relevant DataSources for SDPR inthe OLTP systems.

Prerequisites

You have permitted repository changes and cross-client customizing in table T000 (cross-client object changes) using transaction SM30.

Procedure......

1. Transfer the application component hierarchy. Use transaction SBIW or alternativelyRSA9.

2. Use transaction SBIW, and choose Business Content DataSources → Transfer

Business Content DataSources . Alternatively, you may also use transaction RSA5. Theprocedure is the same.

3. Transfer the following DataSources assigned to application component

0BW_DATASOURCES → 0SCM → 0SPL → 0SPL_SDPR:

0SPL_DELIVERY_DATA_1 (Deliveries)

0SPL_PO_DATA_1 (Purchase Orders)

0SPL_SCH_DATA_1 (Release Schedules)

0SPL_ALERT_DATA_1 (Alerts)

4. Switch to SAP BW.

5. Open the Administrator Workbench (transaction RSA1).

6. Choose Source Systems in the frame on the left.

7. Right-click the source system and choose Replicate DataSources

8. To install the DataSources and replicate them, you had to permit repository changesand cross-client customizing in table T000 in your transactional system. Now you canwithdraw this permission again in your transactional system using transaction SM30.

Activating DataSources in the BW System

Use

Before the metrics and metric categories defined for SDPR can be activated, this data has tobe extracted from the BW system itself (via the BW myself system connection).

Prerequisites

You have permitted repository changes and cross-client customizing in table T000 (crossclient object changes) using transaction SM30.



10.09.2004


Procedure...

1. Transfer the application component hierarchy. Use transaction SBIW or alternativelyRSA9.

2. Use transaction SBIW, and choose Business Content DataSources → Transfer Business Content DataSources . Alternatively, you may also use transaction RSA5. Theprocedure is the same.

3. Transfer the following DataSources:

BW → SAP_COMP → 0SCM → 0SPL → 0SPL_IO: 0SPL_MTCCAT_TEXT (Texts for Metric Categories)

0SPL_MTCID_ATTR (Attributes for Metric ID’s)

0SPL_MTCID_TEXT (Texts for Metric ID’s)

4. Open the Administrator Workbench (transaction RSA1).

5. Choose Source Systems in the frame on the left.

6. Right-click the source system and choose Replicate DataSources. 7. To install the DataSources and replicate them, you had to permit repository changes

and cross-client customizing in table T000 in your transactional system. Now you canwithdraw this permission again in your transactional system using transaction SM30.

Business Customizing

Purpose

Business customizing enables you to tailor the non company specific functionality that isshipped to the specific requirements of your company.

All configuration activities described in the Business Customizing section are tobe performed in the SAP BW system.

Implementation

Installing BI Content

Use

Before you can use the standard BI Content for SDPR you have to activate it in the SAP BW system.

Procedure

To install BI Content you have to perform the following steps:......



10.09.2004


1. Open the Administrator Workbench (transaction RSA1) and choose Business Content on the left. Alternatively, you can call transaction RSOR directly.

2. Activate the necessary BW objects. Choose the option Grouping → In Data Flow Before and Afterwards to make sure that all necessary objects are collected. Choose

Object Types → Roles and activate the following content roles:

BW Role Description and Remarks

SAP_BW_SPL_SDPR_ADMIN SDPR Admin

• These roles activate most of the necessary BW objects(InfoObjects, InfoObject catalogs, ODS objects, InfoCubes,update rules, InfoSources, transfer rules, queries, workbooks,and Web templates).

• Make sure that your transactional system is selected as the

source system (Shift + F7). This is necessary for activating thetransfer routines.

3. Activate the following ODS object, choosing In Data Flow Before :

BW ODS Description and remarks

0SPL_DS17 Authorization Values for Supplier Users

4. Activate the following InfoSet choosing In Data Flow Before :

BW InfoSet Description and remarks

0SPL_IS1 Authorization Values for Suppliers

5. Activate the end user roles. Choose the option Only Necessary Objects . Choose Object Types → Roles and activate the following content roles:

BW Role Description and remarks

SAP_BW_SPL_SUPPLIER Supplier in SDPR context

SAP_BW_SPL_SDPR_ANALYST_M SDPR Analyst. Activate this role if you planto analyze data on a monthly basis.

SAP_BW_SPL_SDPR_ANALYST_W SDPR Analyst. Activate this role if you planto analyze data on a weekly basis.

6. Furthermore, you have to activate the standard definitions of report/report interfaces,which are provided in BI Content. Choose Object Types, then select objects of typeReport/Report Interface . Choose the Only Necessary Objects option. Set the filter forLong Description, and select objects beginning with 0SPL_

For more information, see the SAP BW documentation in the SAP Help Portal at

http://help.sap.com → Data Warehousing → Data Warehouse Management → Business

Content (Versions) → Installing Business Content .

Note that a large number of BI Content objects are collected. For more information, see SAPnote 528435 – (Content transfer contains unexpected objects).



10.09.2004


Setting Up Supplier Authorizations

Use

SDPR provides reports that allow external suppliers to view their own SDPR ratings at all

levels of detail. To guarantee that supplier users have access only to their own ratings andunderlying process data, the corresponding authorization values have to be maintained foreach SAP BW user.

Prerequisites

You have activated BI Content for SDPR as described above.

Procedure......

1. Specify that InfoObject 0SPL_SUPPL is authorization-relevant.

Use transaction RSD1, and open the Characteristic InfoObject 0SPL_SUPPL inmaintenance mode. Choose the Business Explorer tab page, and select the

Authorization relevant checkbox.

2. Create an authorization object in transaction RSSM and assign it to InfoObject0SPL_SUPPL.

Use transaction RSSM. In the Authorization Object box, select the Object radio buttonand create a new authorization object named ZSDPR.

From the list of authorization-relevant objects, select InfoObject 0SPL_SUPPL, andassign it to the authorization object.

3. Assign InfoSet 0SPL_IS1 to this Authorization object.

Use transaction RSSM. In the Authorization Object box, select the Check for InfoCubes radiobutton, and edit authorization object ZSDPR. Select the Switched On checkbox for

InfoSet 0SPL_IS1.4. Create an administrative user and assign the authorization profile S_BW_RFC to this

user.

This user will be used for maintaining the SAP users for external suppliers.

To generate the authorization profile, the admin user has to be assigned to theauthorization profile S_BW_RFC.

Use transaction SU01. On the Profiles tab page, assign the value S_BW_RFC. Savethe user.

SDPR Setup

Purpose

Before you can use SDPR , you have to adapt it to your environment. SDPR providesparameters to control many aspects of ratings.

Starting with the information extracted from the delivery process, you can specify how certaindocuments are handled. For example, you can specify if manually created ASN’s are to berated in the supplier rating. These settings are stored as global parameters.

From the user’s viewpoint, a rating comprises a set of metrics. SDPR provides a flexiblemechanism for defining metrics, their properties, and calculation rules. Calculation rules

define how supplier data (aggregated over a certain time period) is transformed into score



10.09.2004


points. These settings are stored as metric groups, metrics, valid combinations ofmetrics and delivery types, and score lookup tables.

SDPR ships with a set of predefined metrics for two rating categories: supplier communicationand delivery. These predefined metrids do not require modifications and can be used rightaway. Of course, you are free to define new or modified metrics for supplier ratings.

Some of the predefined metrics refer to specific parameters that control how the metrics’scores are calculated. These settings include score reductions for discrepant emergencyorders and score reductions for problem reports.

While it is likely that the activities mentioned so far are performed as part of the an initialsetup, you can just as easily adjust the rating for individual suppliers at runtime (see theoptional steps for initial setup in the “Process Flow” section). For this purpose, SDPR providescalculation rules that give you a large degree of control over the metric scores that arecalculated for individual suppliers. These settings are stored as score calculation rules.

Prerequisites

You have configured the SAP BW system and prepared it for SDPR as explained in theprevious chapters.

Process Flow

The configuration steps for SDPR outlined above can be divided into three basic categories:

• Initial Setup – Mandatory Steps

Specify global parameters

• Initial Setup – Optional Steps

a. Specify metric categories

b. Specify metrics

c. Specify valid combinations of metrics and delivery types

d. Specify score lookup tables

e. Specify score reductions for discrepant emergency orders

f. Specify score reductions for problem reports

• Continuous Adjustment of Rating Rules

Specify score calculation rules

All these steps are explained in more detail in the following sections.

Specifying Global Parameters

Use

Global parameters define central configuration settings in SDPR .

Procedure

To maintain global parameters, proceed as follows:......

1. In the Implementation Guide (IMG), choose SAP NetWeaver → SAP Business

Information Warehouse →

Settings for Business Content →

Supply Chain Management → Service Part Logistics → Supplier Delivery Performance Rating → Global Parameters.



10.09.2004


2. Enter values for the following parameters:

PERIOD_OF_INVEST This parameter specifies the time periodused as a basis for calculating supplierratings

CONSIDER_MAN_ASN Indicator to specify whether manually

created ASN/deliveries should be included inthe rating

EOR_MAX_SCORE_REDUCT This is a global setting for the predefinedmetric with ID ‘EO_RESP’

For more information about the parameters, their use and possible values, see the IMGdocumentation.

Specifying Metric CategoriesUse

Metric categories enable you to group together multiple metrics. They can be used to set upSDPR reports where the supplier ratings are aggregated and grouped on the basis of thedefined categories.

Procedure

To maintain metric categories, proceed as follows:......

1. In the Implementation Guide (IMG) choose SAP NetWeaver → SAP Business

Information Warehouse → Settings for Business Content → Supply Chain

Management → Service Part Logistics → Supplier Delivery Performance Rating → Metric Categories.

2. SAP ships some standard metric categories. You can modify these metric categories,which are displayed in the table, according to your individual requirements. You canalso delete them, and create new categories.

Note that you have to load these master data into the BW system before thechanges to metric categories will take effect in SDPR ratings. The detailedprocedure is explained in the section Loading Master Data [Page 21].

For more information about categories, their use and possible values, see the table field

documentation and IMG documentation.

Specifying Metrics

Use

You specify the metrics that will contribute to the supplier ratings. A metric has an identifier, adescription, a relation to a category, and a rule to specify how it is calculated.

Procedure

To define metrics, proceed as follows:GototheIMG(transactionSPRO)ChooseSAPNetWeaver SAPBusinessInformationWarehouse Settingsfor theBusinessContent Supply ChainManagement ServicePartLogistics Supplier Delivery PerformanceRating MetricsMaintainthemetric categoriesdisplayedinthetable.......



10.09.2004


1. In the Implementation Guide (IMG) choose SAP NetWeaver → SAP Business


Management → Service Part Logistics → Supplier Delivery Performance Rating → Metrics

2. SAP ships some standard metrics. You can modify these metrics, which are displayed

in the table, according to your individual requirements. You can also delete them, andcreate new metrics.

Note that you have to load these master data into the BW system before thechanges to metric categories will take effect in SDPR ratings. The detailedprocedure is explained in the section Loading Master Data [Page 21].

For more information about categories, their use and possible values, see the fielddocumentation and IMG documentation.

Specifying Valid Combinations of Metric IDs andDelivery Types

Use

All metrics are based on the measured data extracted from delivery processes. Theseprocesses are of different delivery types. Not all metrics make sense for all delivery types.

Procedure

To maintain the combinations, proceed as follows:......



Management → Service Part Logistics → Supplier Delivery Performance Rating → Valid Combinations of Metric IDs and Delivery Types

2. SAP ships some standard combinations. You can modify these combinations, whichare displayed in the table, according to your individual requirements. You can alsodelete them, and create new combinations.

For more information about valid combinations, their use and possible values, see the fielddocumentation and IMG documentation.

Specifying Lookup Table for Score Points

Use

Some metrics make use of a lookup table to convert a percentage - calculated from businessprocess data - into a score value. You must specify the mappings from percentages to scorevalues for metrics that make use of the lookup table.

Procedure

To maintain the mappings, proceed as follows:GototheIMG(transactionSPRO)ChooseSAPNetWeaver SAPBusinessInformationWarehouse Settingsfor theBusinessContent Supply ChainManagement ServicePartLogistics Supplier Delivery PerformanceRating ScoreLookupTableMaintainthemappingsdisplayedinthetable.......



10.09.2004




Management → Service Part Logistics → Supplier Delivery Performance Rating → Score Lookup Table

2. SAP ships some standard mappings. You can modify these mappings, which are

displayed in the table, according to your individual requirements. You can also deletethem, and create new mappings.

For more information about valid mappings to score points, their use and possible values, seethe field documentation and IMG documentation.

Specifying Score Calculation Rules

Use

Metrics can contribute toward the overall rating of suppliers to varying extents. You can

control this behavior by a set of calculation rules. You may specify default rules that apply toall suppliers, and special rules for a specific supplier to express rule exceptions and ruleextensions.

Procedure...

To maintain calculation rules, proceed as follows:...


Information Warehouse → Settings for Business Content → Supply Chain Management → Service Part Logistics → Supplier Delivery Performance Rating → Score Calculation Rule Table

2. SAP ships some standard calculation rules. You can modify these calculation rules,which are displayed in the table, according to your individual requirements. You canalso delete them, and create new rules.

For more information about the calculation rules, their use and possible values, see the fielddocumentation and IMG documentation.

Specifying Weighting Factors for On-Time Delivery

Use

These settings are for metrics related to on-time delivery. The calculation of score values forthese metrics is defined by a general mathematical formula. This formula computes aweighted average of the quantities of different on-time categories. You can maintain theweighting factors used in the formula.

Procedure

To maintain weighting factors, proceed as follows:......



Management → Service Part Logistics → Supplier Delivery Performance Rating → Weighting Factors for On-Time Delivery in Quantity Algorithm



10.09.2004


2. SAP ships some standard weighting factors. You can modify these factors, which aredisplayed in the table, according to your individual requirements. You can also deletethem, and create new factors.

For more information about these weighting factors, their use and possible values, see thefield documentation and the IMG documentation.

Specifying Score Reductions for DiscrepantEmergency Orders

Use

These settings are for the metric with the ID EO_RESP , which denotes Response to Emergency Orders . This metric rates the number of discrepant items in emergency orders.You have to maintain the mapping from item counts to score reductions.

ProcedureTo maintain the mapping, proceed as follows:GototheIMG(transactionSPRO)ChooseSAPNetWeaver SAPBusinessInformationWarehouse Settingsfor theBusinessContent Supply ChainManagement ServicePartLogistics Supplier Delivery PerformanceRating ScoreReductionfor DiscrepantEmergency OrdersMaintainthemappingsdisplayedinthetable.......



Management → Service Part Logistics → Supplier Delivery Performance Rating → Score Reduction for Discrepant Emergency Orders

2. SAP ships some standard mappings. You can modify these mappings, which aredisplayed in the table, according to your individual requirements. You can also deletethem, and create new mappings.

For more information about the mappings, their use and possible values see the field

documentation and the IMG documentation.

Specifying Score Reductions for Problem Reports

Use

These settings are for the metrics with the IDs PR_COM and PR_DLV , which denote Problem Report (Communication) and Problem Report (Delivery), respectively. These metrics collectscore point reductions due to problem reports. Each report is assigned to one of the metricgroups (“communication” or “delivery”). You can specify the maximum number of points that

contribute to a score reduction due to problem reports for a given metric group in a period ofinvestigation.

Procedure

To maintain score reductions, proceed as follows:......



Management → Service Part Logistics → Supplier Delivery Performance Rating → Problem Report Score Reductions.

2. SAP ships some standard score reduction rules. You can modify these scorereductions rules, which are displayed in the table, according to your individual

requirements. You can also delete them, and create new rules.



10.09.2004


For more information about score reduction rules, their use and possible values, see the tablefield documentation and IMG documentation.

Administration

Adjusting Reports

Use

SDPR provides a set of reports, that is, SAP BW Web templates and queries, for displayingSDPR information at all levels of detail. These reports are shipped to the users along with acomprehensive set of standard functions to filter certain values, or to include more informationin the report.

Besides these standard reports, SDPR also includes sample reports demonstrating howSDPR ratings for suppliers can be grouped on the basis of specific supplier attributes. TheWeb templates SDPR Score Overview per Region (Month) (0TPL_SPL_DS16_Q010) andSDPR Score Overview per Region (Week) (0TPL_SPL_DS16_Q025) group suppliers by theirregion.

Prerequisites

• You have configured the SAP BW system and prepared it for SDPR as explained in theprevious sections.

• You have loaded appropriate master data for the suppliers and chosen groupingattributes.

Procedure

Make your own copies of these sample reports, and modify them to create a grouping. Beaware that it will mislead users if score points are shown at grouping level, because thesevalues would be the sum of score points of the grouped suppliers. Actually, sums make nosense at this level, since they depend solely on the number of suppliers in the differentgroupings. The same issue arises if you try to create a nested grouping (for example bycountry, and then by region).

Assigning Roles to UsersUse

To enable the SDPR analysts to call up the reports, you have to assign them to one of thefollowing roles:

• SAP_BW_SPL_SDPR_ANALYST_M (monthly)

• SAP_BW_SPL_SDPR_ANALYST_W (weekly)

The role you use depends on the period of investigation you chose for reporting, see sectionSpecifying Global Parameters [Page 13].



10.09.2004


Prerequisites

You have configured the SAP BW system and prepared it for SDPR as explained in theprevious sections.

Procedure

Normally, you assign the SDPR role in a composite role that represents a typical workingprofile in your organization. Alternatively, you can assign the role to users directly:......

1. Use transaction PFCG and select the appropriate role.

2. On the User tab page, add the users to he list.

Managing User IDs for Suppliers

Use

Every external supplier who is to be given access to his/her SDPR ratings requires acorresponding SAP user in the SAP BW system. This user has to be assigned to the supplier.

The following figure illustrates the way authorization data is maintained and applied atruntime:

AuthorizationODS

0SPL_DS17

BW-User

Authorization

Profile

Authorization

Profile

Generation of AuthorizationProfile using scheduledtransaction RSSM

BW Web Report

Authorization ObjectAuthorization Object

Queries on ODSwith InfoObject0APO_SUPPL and

replacement pathvariable (pre-query)

Query Definition WithReplacement Path Variable

Query Definition WithReplacement Path Variable

InfoObject 0SPL_SUPPLInfoObject 0SPL_SUPPL

Log on

1

B

EBPODSseEBP

ODSse

2

4

Pre-Query withAuthorization Variable

Pre-Query withAuthorization Variable

3

5 Query result:Value(s) for0APO_SUPPL

Pre-Query onInfoSet 0SPL_IS1

with authorization-relevant InfoObject0SPL_SUPPL

AWith assignment: BW User 0SPL_SUPPL

This section describes an elementary method for maintaining users with flat files.



10.09.2004


Prerequisites

• You have fulfilled the prerequisites for supplier authorizations as described in sectionSetting Up Supplier Authorizations [Page 12].

• The administrative user has the necessary authorizations for creating new SAP userswith their profiles. Moreover, s/he needs to have the profile S_USER_ALL to generateuser authorizations with transaction RSSM.

Procedure

The following steps are to be performed by one or more administrative userswith the required authorizations.

...

...

1. Create a new SAP user with transaction SU01. The new user is assigned to the roleSAP_BWC_SPL_SUPPLIER.

2. Create a CSV file with the relevant data for all current users. It must contain thefollowing fields in the order shown:

Field Comment

User SAP User Name

BW System 3-digit system name of SAP BW

Update Mode Leave it empty

Lower Value ID of Supplier

3. Delete the contents of the ODS object 0SPL_DS17 (Authorization Values for Supplier Users ).

4. When performing this procedure for the first time, create an InfoPackage. (Once youhave created it, you can reuse it).

To load the data relevant for authorizations into the Authorization ODS object, create anew InfoPackage for InfoSource 0SPL_SUPPLAUTH_DATA_1.

Use transaction RSA1, then choose Modeling → InfoSources . Select the InfoSource0SPL_SUPPLAUTH_DATA_1. Create a new InfoPackage for this InfoSource andspecify a local file on your computer as the source system. Choose Full Upload for theInfoPackage. Save the InfoPackage.

5. Select the CSV file you want to load, and then schedule the InfoPackage.

6. Use transaction RSSM and select the Generating Authorizations options in the

Authorizations group box. Choose Change . The next screen shows a matrix ofInfoProviders and authorization objects.

7. Select the cell where the row of InfoProvider 0SPL_DS17 and the column ofauthorization object ZSDPR intersect. Choose Generate Authorizations .



10.09.2004


Runtime Activities

Replication of Data

Loading Master Data

Use

The master data contains the texts, attributes and hierarchies of characteristics. You candisplay this master data in the queries. You can apply standard procedures to load masterdata into the SAP BW system on which you run SDPR . You do not have to load the masterdata before transactional data is loaded or before SDPR ratings are calculated. Nevertheless,it might be beneficial to load master data in a first step, because this will help to loadtransactional data faster.

Prerequisites

• You have installed BI Content for SDPR.

• You have connected the source system to the SAP BW system on which you runSDPR.

• The source system provides the required master data.

Procedure

We recommend that you load master data at least for the InfoObjects listed inthe table below.

To load the data, create an appropriate InfoPackage for the source system of the InfoSource.Schedule the InfoPackage.

Application Component InfoObject Comment

0APO_LOCNO Load attributes and texts fromOLTP source system. TheInfoObject is referenced by

0APO_SUPPL.

0APO-IO

0APO_PROD

0SPL_MTCCAT Load texts from BW Myself via DataSource0SPL_MTCCAT_TEXT.

0SPL-IO

0SPL_MTCID Load attributes from BW Myself via DataSource0SPL_MTCID_ATTR.

Load texts from BW Myself via DataSource0SPL_MTCID_TEXT.



10.09.2004


Loading Transaction Data

Use

Transaction data comprises four document types from the delivery processes in the OLTP

system (source system) required to calculate the SDPR ratings:

• Advanced shipping notifications

• Purchase orders

• Scheduling Agreement Releases

• Alerts

The following figure illustrates the data flow from the source system through various ODSobjects into the SAP BW system on which you run SDPR .

OLTP System

ASN PORel.

Sched.Alerts

Aggregated Data

Score Data

Collector

Score

Detailed Business Documents

Queries

Scores/ Period

AggregatedData / Period

DetailedDocuments

Web Templates

0SPL_DS010SPL_DS010SPL_DS030SPL_DS12

0SPL_DS030SPL_DS12

0SPL_DS020SPL_DS11

0SPL_DS020SPL_DS11

0SPL_DS040SPL_DS04

0SPL_DS140SPL_DS14

0SPL_DS160SPL_DS16

Individual documents are stored at the lowest level. A separate ODS object exists for eachdocument type. Update rules connect these ODS objects with corresponding InfoSources,which in turn are connected to the corresponding DataSources in the source system.

The Collector ODS object aggregates information from the documents. This is the data basis

for calculating SDPR metrics. Update rules propagate the data from all the ODS objects withdocument-level information to this ODS object.

The Score ODS object stores the score points calculated for the suppliers and metrics inSDPR . The update rule from the Collector ODS to this Score ODS controls and performs thiscalculation.

Prerequisites


• You have set up SDPR as explained in section SDPR Setup [Page 12].



10.09.2004


Procedure......

1. Perform a delta initialization for your transaction data from the OLTP systems into theODS objects that store the process documents.

To do so, create an appropriate InfoPackage for the source system of the InfoSource.

The settings of all these ODS objects specify that all their data targets, namely theCollector ODS object, are updated automatically. This means that the documents areautomatically aggregated into the Collector ODS object.

Application Component InfoSource Comments

0SPL_DELIVERY_DATA_1 Updates delivery documentsfrom the source system

0SPL_PO_DATA_1 Updates purchase ordersfrom the source system

0SPL_SCH_DATA_1 Updates documents aboutrelease schedules from thesource system

0SPL

0SPL_ALERT_DATA_1 Updates documents aboutalerts from the sourcesystem

2. Use the delta method for loading transaction data after a successful delta initialization.You can reuse the InfoPackage you created in step 1.

Updating Supplier Ratings

UseAs illustrated in the section Loading Transaction Data [Page 22], the Collector ODS objectaggregates information from the documents and is the data basis for calculating SDPR metrics. Update rules propagate the data from all the ODS objects with document-levelinformation to this Collector ODS object. The system is set up to perform this updateautomatically for every change at document level.

The Score ODS object stores the score points calculated for the suppliers and metrics inSDPR . The update rule from the Collector ODS object to this Score ODS object controls andperforms this calculation.

Prerequisites


• You have set up SDPR as explained in section SDPR Setup [Page 12].

• You have loaded transaction data as explained in section Loading Transaction Data[Page 22].

Procedure......

1. Perform a delta initialization for the update from the Collector ODS object to the Score ODS object. This enables initial score points to be calculated for the existing suppliers.

Note that in contrast to the update of the Collector ODS object, this will nothappen automatically.



10.09.2004


2. Use the delta method to update the Score ODS object on the basis of the data in theCollector ODS object. You may want to update the scores less frequently, because notevery single change in the Collector ODS object really needs to be reflected by anupdate of the Score ODS object. In fact, a single change of some aggregated keyfigure often does not have any impact on a score point. Rather, it is the sum of multiplechanges that results in a different score.

Exporting SDPR Data

Use

SDPR provides a function for exporting all data. Using this function, you can write customprocedures, for example to save the data locally, or to transfer it to another system for furtherprocessing.

The export function is implemented as an RFC in the function module EXPORT_DATA infunction group RSBCTSDPR_EXPORT. For a detailed description of its usage, refer to thedocumentation of the function module. To access the documentation, use transaction SE37,enter EXPORT_DATA , and choose Function Module Documentation .

Prerequisites

• You have loaded transaction data as explained in section Loading Transaction Data[Page 22].

• If you want to export supplier ratings, you must have updated them as described insection Updating Supplier Ratings [Page 23].

Procedure

•

Write a procedure that invokes the RFC, either remotely or via a local report.• Pass the required arguments and retrieve the results.

Examining Execution Logs

Use

As part of the standard functionality of SAP BW , you can examine the success or failure ofany job that loaded data. There are two error categories:......

• Technical errors reported by the SAP BW system. Possible causes include networktransport errors, problems related to data storage, and data format errors.

• Logical errors reported by SDPR update routines. These errors provide you with abusiness-oriented view of what went wrong and why. They signal data inconsistenciesin the process documents, invalid settings in SDPR customizing, and score calculationerrors.

Prerequisites

• You have scheduled some jobs to load data for SDPR.

Procedure

To determine the status of a particular job that loads some data, proceed as follows:...

1. Use transaction RSA1.



10.09.2004


2. Choose Modeling → InfoSources , and select the InfoSource for the data load.

You have to perform an additional step if you want to check the data upload betweentwo ODS objects, for example between the Collector ODS object (0SPL_DS14) and theScore ODS object (0SPL_DS16). To do so, proceed as follows:

a. Choose Settings → Display generated Objects . A dialog box appears.

b. Choose Show generated ODS objects .Now, you will be able to find the generated InfoSource for 0SPL_DS14 bysearching for an InfoSource with the name prefix “80SPL”.

3. Open the InfoPackage that scheduled the job to load the data.

4. Choose Monitor . On the next screen, you get an overview of recent jobs for theInfoPackage. You can check the status of each job and perform detailed error analysis.

Logical errors are reported to the application log. This logging facility provides you with acomplete view of all errors that have occurred in a certain time period. Entries in the log areassigned to one of the following log objects of SDPR :

Log Object Description

SPL_SDPR SDPR Log (Misc.)

SPL_SDPR_ALR2COLL SDPR Log (Update from Alert ODS toCollector ODS)

SPL_SDPR_ASN2COLL SDPR Log (Update from ASN ODS toCollector ODS)

SPL_SDPR_COLL2SCORE SDPR Log (Update from Collector ODS toScore ODS)

SPL_SDPR_IS2DET SDPR Log (Update from Source System toDetails ODS)

SPL_SDPR_PO2COLL SDPR Log (Update from PO ODS toCollector ODS)

SPL_SDPR_POLINE2COLL SDPR Log (Update from PO (L.Alg.) ODS toCollector ODS

SPL_SDPR_SCH2COLL SDPR Log (Update from Rel.Sch. ODS toCollector ODS)

SPL_SDPR_SCHLINE2COL SDPR Log (Update from Rel.Sch. (L.Alg.) ODS to Collector ODS)

Moreover, SDPR defines a specific external ID for the application log which acts as agrouping for all these log objects. It helps you to select all entries of all log objects defined forSDPR . Its name is SPL_SDPR.

To search the application log for SDPR entries, proceed as follows:...

1. Use transaction SLG1.

2. Either enter a specific log object or the external ID of SDPR, and specify an appropriatetime range.

3. Perform the search.

4. In the next screen, the matching log entries are displayed in a list. Each log entryrepresents a collection of messages created by an individual job. The colored icon onthe left indicates highest error severity assigned to some messages in the collection.



10.09.2004

A red square indicates that an error in SDPR has occurred. Errors have certainimplications, for example, data could not be loaded into SDPR , or datainconsistencies were detected.

A yellow triangle indicates a warning. Warnings have implications, for examplesupplier scores could not be calculated.

Log entries and the associated messages remain in the application log until you clean it up.To clean up the application log, use transaction SLG2, enter a log object or the external ID ofSDPR , specify which entries to delete, and then perform the deletion.