Kontakt

Ansicht
Dokumentation

RISSR_DV10UA_2005 - Adjust Master Data to Changes in R31/2002 - Change Subsect. of PRFL10

RISSR_DV10UA_2005 - Adjust Master Data to Changes in R31/2002 - Change Subsect. of PRFL10

CPI1466 during Backup   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This conversion report adapts the assignment of subsection numbers 1 to 4 of premium reserve fund list 10 (VV10) and subsections 6 to 8 of premium reserve fund list 3 (VV3) in line with the requirements set out in Circular R12/2005 (Aufstellung und Führung des Vermögensverzeichnisses sowie Vorlage des Ausdrucks gem. § 66 Abs. 6 VAG (Establishment and Maintenance of the Premium Reserve Fund List and Presentation of the Printout Pursuant to Article 66 Para. 6 of the Law on Insurance Supervision (VAG)); Aufbewahrung des Sicherungsvermögens gem. § 66 Abs. 5 VAG (Retention of the Premium Reserve Fund Pursuant to Article 66 Para. 5 of the Law on Insurance Supervision (VAG))). In addition, the texts in the value table for the subsections are adapted in line with the new requirements.

This conversion is required due to the restructuring of the subsections for VV10 und VV3, which came into force on January 1, 2006. For more information, refer to the notes on the conversion date in the Selection section.

Important
Do not run this report until you have the created and submitted the position lists for 2005 (key date December 31, 2005). According BaFin, the legal changes to the subsections of the premium reserve fund lists will apply only to statutory reporting for 2006 (key date January 1, 2006). In other words, the reassignment must apply after this date only. For more information, refer to the notes on the conversion date in the Selection section.

Note the requirements for calling the report (see Prerequisites).

Perform a test run first and check that the data has been converted correctly in the ALV results display.

Integration

  • The report must not be run during ongoing business operations since data consistency cannot be ensured in the event of parallel activities.
  • You can run the report in dialog mode only. Background processing is not supported.
    As a result, a longer online runtime is required for dialog mode. For this reason, you should change the relevant system parameters if necessary.
  • This report uses report RISSR_CHANGE_SV10UA in the update run.
  • In order to generate the necessary ledger postings for the conversion, the report also calls the relevant subsequent posting functions (reports RISSR_NABU and RISSR_NABU_DELETE).

Prerequisites

Necessary Conversion and Assignment Activities

You have successfully carried out all of the activities required for conversion to Circular R11/2005 (see Conversion Guidelines):

  • You have changed the asset types in line with the German Asset Regulation 2004 (you have successfully executed report RISSR_ANLV2004 in an update run).
  • You have entered the statutory reporting additional classifications for the affected assets (transaction ISSR_SPEC_ASSET and ISSR_SPEC_ASSETB).
  • You have successfully executed the conversion of the indicators/changes to the value tables for the statements 670/ 671 and mix asset (report RISSR_R30_2005 in an update run).

Backup Table for Value and Control Tables

  • The backup table TISSR_DVUA_BCK for the value and control tables TISSR_DVUA and TISSR_DVUAT exists and is active.
  • The data in the backup table fulfills the requirements of the Circular R12/2005. The table contains all of the data records for the control and value tables that are required for the conversion.
This table is shipped with the latest data. If necessary, check that the data is correct using SAP Note 910410 (Solution section, point 1).
The data records already contain the value R11_2005 as the indicator for the legal basis. Customer-specific changes are not required for this purpose and are not supported by the program.

Additional Prerequisites

  • The data in the value and control tables used until the conversion is based on the requirements of the Circular R31/2002, which was applicable up to then.
  • The backup table ISSR_RPI_MFT_BCK for the master data table exists, is active, and does not yet contain any data records with the value SV10 in the SAVE_COMPONENT field.
If you have carried out the conversion correctly, this table will contain the correct version (see Necessary Conversion and Assignment Activities).

Recommendations for Displaying the Log

This report changes the contents of the master data table ISSR_RPI_MFT. This table is extremely large. For this reason, we recommend that you optimize the change log displayed for these tables. To do so, check the Customizing settings in the IMG activity Configure ALV Display and, if necessary, adjust the log layout in the ALV output directly.

Features

Changes to the Value and Control Tables (Update Run Only)

The report changes the long texts for subsections 01 to 04 of VV10 in the value and control tables.

  • Copy the data records from the control and value tables (version R31/2002) to the associated backup table.
The backup table then contains both the data for version R31/2002 and the data for the new requirements (R12/2005).
The data records are then assigned the relevant indicator for the legal basis of the conversion (DVUA_ALT or R11_2005).
  • Delete the existing data records (version R31/2002) from the value and control tables.
  • Copy the data records with the identifier R11_2005 from the backup table to the associated value and control tables.
The value and control tables then contain only data records with the latest version in line with the Circular R12/2005.

Changes to the master data table ISSR_RPI_MFT

The report changes only those data records that are assigned to subsections 1 to 4 (not 5) of premium reserve fund list 10 and subsections 6 to 8 of premium reserve fund list 3.

General Information

To perform the conversion, the data records to be processed are first copied. The system then either makes changes to these copies or generates new data records by means of a transfer posting.
The validity date determines how the data records are processed:

  • Validity date after the entered conversion date - only the copy of the existing data record is changed to the new subsection.
Note: All of the data records affected by the conversion are processed, irrespective of how many data records exist for the capital investment. The validity date is unchanged.
  • Validity date before or equal to the entered conversion date or blank (no date specified) - transfer posting (an new data record is generated) with a changed subsection and validity date = conversion date.
Note: If several data records with a validity date like this exist, the most recent data record (compared to the date of the conversion) is used. If several data records exist for this date, the highest counter in the NUMB_PER_ASSET applies.

The following fields are also changed as a result of the transfer posting:

  • NUMB_TP_DAY
  • NUMB_PER_ASSET
  • BUDAT(filled with conversion date)
  • MASTER_REC_KEY (filled with the value D so that inflow and outflow records for the asset category transfer posting are written)

Caution: The program also triggers the subsequent posting (ISSR_NB2) for all of the assets affected over the entire term of the investments. With large data volumes, this can mean that the program runtime is longer.

Conversion for Premium Reserve Fund List 10

To carry out the conversion, the program uses the information about the type of hedge fund in the statutory reporting additional classifications (field HF_TYPE) as well as the assigned asset type (after conversion to Asset Regulation 2004) as a the conversion criterion. For asset types II and III (opening clause and special approval), the registered office of the issuer (address data stored for the class) is also taken into account:

Field HF_TYPE Asset Type New Subsection
Blank (no entry) 15 01
Blank (no entry) 16 02
Blank (no entry) 17 03
Not blank (contains a value) All 04
Blank (no entry) II 01 if issuer's registered office is in Germany, 03 if issuer's registered office is in rest of EEA
Blank (no entry) III 01 if issuer's registered office is in Germany, 03 if issuer's registered office is in rest of EEA

Conversion for Premium Reserve Fund List 3

The report carries out the following defined conversions for the subsections for premium reserve fund list 3:

Previous Subsection New Subsection
06 05
07 06
08 07

Note: Subsection 08 of premium reserve fund list 3, therefore, no longer exists after the conversion.

Selection

  1. Specify the statutory reporting variant for which the conversion is to be carried out.
  2. Enter the required conversion date in the Date of Conversion field.
Important Information Regarding the Conversion Date
The specified date is the validity date for dividing the data records according to changes and transfer postings. This date is assigned to all new master data records.
The date must be earlier than or equal to the system date AND later than or equal to the conversion date for the conversion to R30/2005. Based on the BaFin requirements, we recommend that you carry out the conversion on January 1, 2006 because the lists pursuant to the requirements of R12/2005 are not submitted until after this date and the lists that were applicable previously must still be reproducible.
If you choose a conversion date before January 1, 2006, old lists cannot be output correctly.
  1. Choose whether the report is to be executed as a test or update run.
  2. If you choose update run, confirm that all of the prerequisites have been fulfilled in the Prerequisites for Update Run section.

Note

You do not need to make any entires under Backup Identifier.

Standard Variants

Output

If you execute the report in a test run, you can check the results in an ALV display. The results of update runs are not displayed. The systems converts the data in the database directly and triggers the automatic subsequent posting.

Caution:
You should also execute an update run if the log display is empty (no data relevant for the conversion exists). This is required for the change log.

Activities

Example






Fill RESBD Structure from EBP Component Structure   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 14256 Date: 20240520 Time: 044156     sap01-206 ( 188 ms )