SDPR Score
Technical name: 0SPL_DS16
Use
This ODS object contains the scores achieved by suppliers.
In SDPR, specific metrics are predefined for each time period, supplier, and ship-to location that is to be rated. Scores are calculated on the basis of these metrics. The metrics that are relevant are specified in Customizing for SDPR. The ODS object “SDPR Score” is updated from the ODS object SDPR Collector. Calculation rules that have been defined for the various metrics are used to transform the data from the key figures. As in the ODS object “Collector,” the two aggregation levels (supplier, and supplier/ship-to location) are stored separately, and each is given a data record type. You can set the time period to months, weeks, or periods, in Customizing for Supply Network Collaboration under Supplier Collaboration ® Functions for Service Parts Planning (SPP) ® Supplier Delivery Performance Rating (SDPR) ® Make Global Settings for SDPR in the Type of Reporting Period field. This ODS object contains a separate fields for each of the reporting periods month and week, but only one of the fields is filled according to the setting made.
The ODS object “SDPR Score” is used to store a so-called elementary score per supplier/period/metric, and per delivery type. This elementary score can then be used to calculated an effective score, which is a combined rating of the elementary scores across all delivery types (distribution center, and third-party processing). These calculations are performed in all queries in SDPR.
Out of 500 ASNs (type: distribution center), 450 were on time. That is 90%, and could result in a score of 20. Out of 50 ASNs (type: third-party processing), only five were on time. That is 10 %, and could result in a score of five. To get the effective score for the timeliness of ASNs, we do not add these two scores together and then divide the total by 2; instead, we weight the scores in accordance with the ratio defined for delivery types Distribution Center and Third-Party Processing. The effective score is then calculated as follows:
20 x 500 / 550 + 5 x 50 / 550 = 18,18 + 0,45 = 18.63
Updating
The following rules are applied when the scores from ODS object “SDPR Collector” are updated:
...
1. A check is run for the various combinations of supplier and ship-to location to see if data exists for a specific time period. If not, a score is not calculated for the relevant metrics (in other words, no entry is made in the ODS object for this supplier and ship-to location). This avoids the situation whereby a supplier could have an “artificial” rating in a period where no delivery activities took place. This kind of rating would have an undesirable effect on the trend analysis.
The data types that are used for this first decision (that is, the decision as to whether a rating should be made) are configured globally:
Document Category |
Relevant for “First” Decision Regarding Whether or Not to Calculate Rating |
ASN |
Yes |
Purchase Order |
No |
Scheduling Agreement Release |
Yes |
Alert to Supplier |
No |
Supplier Confirmation |
No |
If all of the data for a document type is valid for a given period, and this document type is not relevant for the first “decision,” then a score will not be calculated because, on its own, this data is not significant enough for a rating. If, for example, there is only alert data in the period, then a score will not be calculated for the specified metrics.
The following steps only apply if there is relevant data for the period observed.
2. If there is relevant data, then a score is calculated for the supplier and ship-to location in question. To achieve this, the following steps are performed for every metric:
a. The appropriate score calculation rule is determined from the Customizing activity Score Calculation Rule Table.
b. A check is run to see if all of the values required for calculating the metric are available.
If any data is missing, then a check is run on the basis of the Indicator for Applying Default Score If No Valid Data Exists in the score calculation rule to see if a default score should be used.
One reason why data might be missing is that certain activities are not performed within the period in question. In this case, instead of using a zero score or omitting the score from the supplier’s overall rating, it can be appropriate to assign a default score. This means that the metric will be contained in the overall rating, making it easier for you to compare it with the ratings of other suppliers.
The following steps only apply if there is relevant data for the period observed.
c. In the score calculation rule, the Metric Can Be Calculated indicator is checked to determine whether or not it makes sense to calculate a score for the metric. If not, then you should assign a default score.
If you use a default score, then the data that has already been entered for this metric will not be taken into account for the supplier and ship-to location in question. If you do not use a default score, then a score is calculated for the metric on the basis of the data that has been entered.
d. If all of the data required for the calculation is available, then the algorithm specified for the metric will be used to calculate the actual score.
3. When scores (default scores or calculated scores) have been determined, they are written to the Scores ODS object, and the Metric Is Used indicator of the score calculation rule is set for this entry.
If you have used a default score, the weighting factor for the score is also written to the ODS object.
Key Fields
Key Field |
Description |
0APO_SUPPL |
Supplier |
SDPR Record Type |
|
0APO_SHPTO |
Ship-to Location |
Cal. Year / Month |
|
Calendar Year/Week |
|
Delivery Type |
|
Metric |
0CALMONTHNavigational Attributes
Navigation Attribute |
Description |
0SPL_MTCID__0SPL_MTCCAT |
Metric Category |
0APO_SUPPL__0COUNTRY |
Country Key |
0APO_SUPPL__0REGION |
Region (State, County, Province) |
Delta Update
Delta update is possible.