Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
FIN-FSCM-TRM-AN (Application Component) Analyzer⤷
CFM_AFWBM (Package) CFM Analyzer: Benchmark Management
Basic Data
| Data Element | AFWBM_KEYFIGURE |
| Short Description | Benchmark Key Figure |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AFWKF_DEFINITION | |
| Data Type | CHAR | Character String |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 8 | |
| Value Table | AFWKF_DEFIN |
Further Characteristics
| Search Help: Name | S_HLP_BM_KEYFIGURE | |
| Search Help: Parameters | KEYFIGURE | |
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Key Figure |
| Medium | 15 | BM Key Figure |
| Long | 20 | Benchmark Key Figure |
| Heading | 20 | Benchmark Key Figure |
Documentation
Definition
In a benchmark run, you can calculate basic key figures and return-on-investment key figures separately, or together. When the system calculates return-on-investment key figures, it checks whether all the key figure values that it needs actually exist. It does not matter whether these were calculated in a different benchmark run, or in this benchmark run. If it cannot calculate the value of a key figure for a key date because data is missing, the system records in the log for which key date the basic key figure values do not exist.
The key figure values for a benchmark and a key figure are stored in the results database only if the system was able to calculate a key figure value for each key date within the analysis period. If it could not calculate a key figure value, it records an error message in the log. If you chose the option Save as Worklist, the relevant selection criteria are included in the worklist.
Before the system saves the key figure values, it checks whether the database already contains values from a different benchmark run. If the values from an existing benchmark run are different from the new values, the new values are written to the database, and an information message is recorded in the log.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20050705 |
| SAP Release Created in | 600 |
