Hierarchy
BI_CONT (Software Component) Business Intelligence Content⤷
BW-BCT-SPL-SDR (Application Component) Supplier Delivery Performance Rating⤷
RS_BCT_SPL_SDPR (Package) BW: Content Logistics - Supplier Delivery Performance Rating
IMG Activity
| ID | RSBCTSDPR_MTCDTY | Valid Combinations of Metrics and Delivery Types |
| Transaction Code | S_B52_73000017 | (empty) |
| Created on | 20040116 | |
| Customizing Attributes | RSBCTSDPR_MTCDTY | Valid Combinations of Metrics and Delivery Types |
| Customizing Activity | RSBCTSDPR_MTCDTY | Valid Combinations of Metrics and Delivery Types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | RSBCTSDPR_MTCDTY |
Use
In this activity, you define for which delivery type a metric is valid.
In general, all metrics are based on the measured data extracted from operational business processes concerning supplier deliveries. These processes can be distinguished with regard to their delivery type:
- TPOP - goods are directly shipped to a customer (Third Party Order Processing)
- PDC - goods are shipped to a Distribution Center
Dependent on the delivery type, not all metrics make sense for both types. For example, some metrics might rely on measured data that is only relevant in case of TPOP. Hence, they should not be calculated for data coming from processes with delivery type PDC.
The system checks the settings in this IMG activity to determine the valid combinations of metrics and delivery type that is provided in reporting.
Requirements
You can only maintain the valid combinations for metrics that have been entered in IMG activity Definition of Metric ID's.
Standard settings
The standard setup includes a list of valid combinations of metrics and delivery types for those metrics that are also included in the standard setup.
Activities
Enter the valid combinations in the table: For each combination, create an entry as follows:
- Specify the name of the metric.
- Specify one of the delivery types for which this metric is applicable.
If you create, change, or delete entries in this table, all these changes will affect metric calculations that are performed after the changes have been saved, but not those ratings that have already been calculated.
Example
The metric Accuracy (ASN) with name ASN_ACCUR is applicable for both delivery types, since the accuracy is comparably important in all delivery processes.
The metric Shipped Quantity Discrepency (SHIP_DISCR) is applicable only for PDC, since it can be measured only for processes with this delivery type.
Business Attributes
| ASAP Roadmap ID | 207 | Establish Reporting |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | RSBCTSDPR_MTCDTY | 0 | ARS0000023 | Business Content and Extractors |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| RSBCTSDPR_MTCDTY | S - Table (with text table) | SM30 |
History
| Last changed by/on | SAP | 20040318 |
| SAP Release Created in | 352 |
