SAP ABAP IMG Activity SIMG_CMS_BASEL_DEXPR (Maintain Settings for Data Extraction Process)
Hierarchy
☛ EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   ⤷ FS-CMS-IS (Application Component) Information System
     ⤷ CMS_BASEL (Package) Basel II
IMG Activity
ID SIMG_CMS_BASEL_DEXPR Maintain Settings for Data Extraction Process  
Transaction Code S_ALN_01001891   (empty) 
Created on 20030312    
Customizing Attributes SIMG_CMS_BASEL_DEXPR   Maintain Settings for Data Extraction Process 
Customizing Activity SIMG_CMS_BASEL_DEXPR   Maintain Settings for Data Extraction Process 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CMS_BASEL_DEXPR    

In this IMG activity, you must maintain the configuration details that are required for the data extraction process from Collateral Management (CM).

Note: As part of the data extraction process from Collateral Management to the Financial Database (FDB), you must maintain the required Customizing settings in CM. Additionally, in the FDB, you must define the mapping structure required to map the collateral agreement and asset details to the appropriate objects.

In this IMG activity, you must specify the following:

Data extraction process type: This configuration type includes the data extraction structure, the destination of the data and other settings for the IDocs required for the interrface to the FDB. You can define any number of required data extraction process types.

Data extraction object category: Determines if the extraction process is being executed for collateral agreements or assets.

Message type of the IDoc : Determines the data structure of the object (asset or collateral agreement) to be extracted.

Receiver port

Partner type of receiver

Partner number of recipient

    Note: The details of the file port as the receiver determines the destination of the IDocs. In the case of Bank Analyzer, you can use a file as the receiver of data.

Application log (object name) : Name of the application log where all the messages reported during the extraction process of assets and collateral agreements, are collected.

Application log (sub object) : Name of sub-object (assets or collateral agreements) for which the application log is maintained.

Collateral value type: You can specify the value type of the asset or collateral agreement that must be considered when transferring the relevant data to the financial database. You can choose from two values, namely the Nominal value and the Market value for assets and the assessment value for collateral agreements.

Requirements

Standard settings

The following settings are recommended for the current release of Collateral Management and Bank Analyzer 2.1 Interface:

The standard process extraction types:

  • DE 000 : Standard process type
  • DE 001 : Process type specific for Bank Analyzer

The standard ALE message types of IDOCs are:

CMS_BII_CAGMT_AST_RBL : CMS-Basel II: Coll.Agmt ,Ast & Rbl Links (Rel 2.1 Bank Analyzer)

CMS_BII_STD_AST : CMS-Basel II: Asset Details Standard

CMS_BII_STD_CAGMT_AST_RBL : CMS-Basel II: Collateral Agreements Standard

Note: The message type CMS_BII_CAGMT_AST_RBL has been used in the standard release of Bank Analyzer 2.1

Activities

Determine the IDoc settings for various combinations of data extraction process type, object category and the collateral value type.

Example

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional 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 SIMG_CMS_BASEL_DEXPR 0 ALN0000072 Master Data 
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
V_TCMS_BII_DEXPR V - View SM30  
History
Last changed by/on SAP  20030312 
SAP Release Created in 200