SAP ABAP IMG Activity AFWA (Define Analysis Structure)
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 AFWA Define Analysis Structure  
Transaction Code S_KFM_86000106   (empty) 
Created on 20000714    
Customizing Attributes AFWA   Define Analysis Structure 
Customizing Activity AFWA   Define Analysis Structure 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name _JBAP    

An analysis structure is the technical carrier (data structure) for all characteristics that can be used in Risk Analysis.

The characteristics and their values provide the selection criteria that are used to select transactions for evaluations. You can navigate through the characteristics when you display the results of the evaluations.

The information that defines the data structure applies across all clients. This means that you define the analysis structure once only, and you can then use it in all clients. You then only need to activate it in the individual clients.

Example

Bank XY

    |

    |-------Trader A

    |        |

    |        |------Stocks

    |        |

    |        |------Bonds

    |

    |-------Trader B

            |

            |------Forward transactions

            |

            |------Derivatives

            |

The above example results in the following characteristics and characteristic values:

Characteristics    Characteristic values

Bank:    XY

Trader:    Trader A, trader B

Transaction types:    Stocks, bonds, forward transactions, derivatives

Requirements

Before you begin to customize the analysis structure, you should depict your reporting structures (as shown above) in a portfolio hierarchy.

You also need to have already defined all the analysis characteristics that are relevant to you. When you define the analysis structure, you cannot then go back and create new characteristics. These must exist beforehand.

Activities

  1. Define an analysis structure.

    Enter a 4-character name for a new analysis structure, and confirm your entry with Create.

    The system displays the view Edit data structure.

  2. Define which of the characteristics that you have created are to belong to the analysis structure.

    You can simply transfer the characteristics from the reference catalog (right side of the screen) to the data structure (left side of the screen) using Transfer fields. You can transfer only those characteristics that have the status 'active'.

  3. When you have finished editing the data structures, you need to Save and Activate these. The data structure then receives the technical name I73<Name of the analysis structure>.
  4. Choose Back.

    This takes you back to the screen Maintain Analysis Structure.

  5. In addition to editing the data structure, you have other definition options:
    • Selection screens: Select the characteristics of the analysis structure for which, in risk analysis evaluations, you want to be able to use characteristics values to refine your selection criteria.
    • Entry of characteristics: Here, you can simplify data entry for maintaining characteristic values in the financial object. Using drag & drop, you can sort and hide characteristics by double-clicking. In financial object maintenance, the values of hidden characteristics have to be derived.
  6. Generate the maintenance module for characteristic values.

    Function modules and screens are generated so you can enter the values of the characteristics you have defined yourself. These characteristics have their own value maintenance. If the log shown does not contain any error messages, you can exit the log display, and return to the Maintain Analysis Structure screen.

  7. You do not normally need to generate any other objects manually. However, by choosing Other Objects or Goto -> Generate Environment, you have the option of generating the following objects manually:
    • Maintenance modules for characteristic values (same as point 6)
    • Service programs (use database tables that were generated for the analysis structure; for example, for the external data transfer of financial objects, financial object maintenance, generation of base portfolios, provision of results tables relevant in reporting)
    • Programs for single value analysis (all reports, except drilldown, in which the analysis characteristics are displayed as selection options)
    • Interface programs for drilldown (programs that you can call up in drilldown by using the report-report interface, and which reflect the selection of analysis characteristics)
    • Selection-include for drilldown (required for value-at-risk reports in drilldown reporting)
    • Text read modules (for characteristic values)
    • Characteristic subscreens for maintaining characteristic values (in maintenance of financial objects and in the respective business transactions)
    • BDT carrier screen (screens, which are linked to the screen sequence, are generated for transactions made with the BDT)
    • Transfer programs for the derivation of characteristic (required only if, within characteristic derivation, a reference is made to an operating concern)
    • Number ranges for base portfolio views
  8. Activate the analysis structure.

    When you do this, it becomes the analysis structure valid in this client.

Further notes

Notes about using an analysis structure in multiple clients

As mentioned above, all the objects that are generated when you create an analysis structure are defined across all clients. If you use the analysis structure in multiple clients, then you need to define the data structure once only. You then need only to activate it in the individual clients.

If you have different requirements for your analysis structure in different clients, then you need to create a separate analysis structure for each client, using a suitable naming convention. There are noextra considerations regarding the selection of characteristics, since it is possible to have multiple analysis structures in one system and assign any combinations of characteristics to the analysis structures (also without any overlap).

If, in those clients, there are different requirements for a characteristic, then you create different characteristics, using a suitable naming convention, and choose these for the relevant analysis structure.

Only one analysis structure is ever active for a given client, and only this active structure is used in the application functions. This means that you can use different analysis structures in different clients. The use of characteristics is also client-dependent, as they areassigned to the analysis structure.

For technical information about the objects that are generated when you define the analysis structure in the ABAP Dictionary, see Extras > Status Information -> Tables.

Additional Functions

  • Using old report types

    The Information System in Risk Analysis contains some report types that, although still supported, are no longer recommended for new customers. To keep the number of reports displayed manageable, these report types are not offered for selection. You can, however, still use old report types by choosing Edit -> Report Types.

  • Checking the analysis structure

    Using this function, you can check the consistency of the settings and the condition of the analysis structure. Should any steps be missing, these will be indicated.

    If the check finds errors, no data can be transferred to the analysis structure.

  • Upgrading the system

    After the system has been upgraded to a later release, you need to reactivate the analysis structure. To do this, choose Data Structure -> Change. Messages are displayed about the new structure of the field catalog and the text read modules. Choose Activate without changes to characteristics.

  • Translating the analysis structure

    Using this function, it is possible to translate all language-dependent texts in the analysis structure. Once you have chosen the target language, the system displays the texts in a selection list. You can choose which texts you want to translate (it is not possible to translate back into the source language).

  • Deleting the analysis structure

    The following conditions have to be fulfilled for it to be possible to delete an analysis structure:

    • The analysis structure must be inactive in all clients.
    • All views (in TRM the internal views) for this analysis structure have to have been deleted in other clients. The views in the client in which the analysis structure is deleted, and all connected data, are deleted along with the analysis structure.
    • All financial objects for the analysis structure must be inactive.
  • Transporting the analysis structure

    This function writes the analysis structure and its characteristics to a transport request. You can also opt to transport the characteristic values.

    In the Risk Analysis component, as for other applications, an automatic transport link takes effect for many settings. This does not apply, however, for all settings.

    The following list shows which objects are not automatically transported:

    • Data structure of the analysis structure with characteristics
    • Derivation strategies
    • Characteristic values
    • Char
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 _JBAP 0 I510000051 Risk Analysis 
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
AFWA T - Individual transaction object AFWA  
History
Last changed by/on SAP  20000723 
SAP Release Created in 462_10