Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
FIN-FSCM-TRM-CR (Application Component) Credit Risk Analyzer⤷
CFM_ACUST (Package) Analyzer Customizing
IMG Activity
| ID | AFWS | Edit Segment-Level Characteristics |
| Transaction Code | S_KFM_86000107 | (empty) |
| Created on | 20000714 | |
| Customizing Attributes | AFWS | Edit Segment-Level Characteristics |
| Customizing Activity | AFWS | Edit Segment-Level Characteristics |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | AFWS |
In this IMG activity you specify which characteristics are used to form segments. You make the specification for an analysis structure and a certain client.
Segments are internal keys that describe combinations of characteristic values. In many functions they are used instead of the original characteristic values. Key figures in the results database are stored by segment, for example.
For performance reasons, it is necessary to differentiate between characteristics that are relevant for segments and characteristics that are not relevant for segments. If a characteristic such as "Transaction number" were used for segment formation, there would be just as many segments as transactions (if not more). Data storage would inflate enormously and performance would worsen.
When you select characteristics for segment formation, you should make absolutely sure that no more than 10000 different combinations of segment-relevant characteristics are possible (what counts are the combinations that actually come to pass, not those that are theoretically possible). Since this is hard to estimate, a rule of thumb is to avoid using those characteristics - like the transaction number - that have a different value for virtually every transaction.
Only the characteristics used for segment formation can be included in portfolio hierarchies.
Otherwise however, reporting across all characteristics is possible, including those that are not selected here.
In Release CFM 1.0 there are still a few restrictions (for example, reporting from the results database is only possible with segment characteristics).
The characteristic Company code is always used for segment formation, which is why you cannot remove the corresponding indicator.
In change mode you can make a proposal for the selection of characteristics. Afterwards a message appears (message AFWCH_DB 019). The criteria for the proposal are explained in the message's long text.
You can display information on the characteristic, such as the data element or the check table, with a double-click on the appropriate line or by choosing "Details for characteristic".
When you change the segment-level characteristics retrospectively, you need to bear in mind the following:
- You have to update the finance object - segment allocations. You can either do this using FO mass processing or view reconstruction (also see the information in the dialog box that is displayed).
- The values in the results database are only stored in accordance with the new segment-level characteristics in the case of future evaluations. Evaluation results that have already been generated remain unchanged. This may affect the extent to which results can be compared.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| 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 | AFWS | 0 | HLA0100041 O | |
| SIMG | AFWS | 1 | KFM0000014 O KFM0000015 |
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 |
| AFWS | T - Individual transaction object | AFWS |
History
| Last changed by/on | SAP | 20000911 |
| SAP Release Created in | 462_10 |
