Kontakt

Ansicht
Dokumentation

RISSR_ANLV2004 - Adjust Master Data in Accordance with Asset Regulation 2004

RISSR_ANLV2004 - Adjust Master Data in Accordance with Asset Regulation 2004

BAL_S_LOG - Application Log: Log header data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This conversion report adapts the assignment of the assets to the asset type in line with the requirements of the German Asset Regulation 2004 so that regulations it contains for regrouping the assets are fulfilled.

Caution
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.

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

Integration

This report uses report RISSR_CHANGE_ANLART in the update run.

In order to generate the necessary ledger postings for the conversion, the report also calls the relevant subsequent posting functions (programs RISSR_NABU and RISSR_NABU_DELETE).

During the update run, the report generates an entry in table TISSR_CHA_MDATA, which records the master data conversions. This entry must exist so that follow-on activities, such as manual postprocessing of the SR additional classifications, conversion of the SV10 identifiers (report RISSR_ISSR_SV10UA_20059), and conversion of the identifiers to R11/2005 (report RISSR_R30_20059) can be carried out.

The assignment between the currently valid asset types and the new asset types is stored in a conversion table. You can check this assignment in the IMG activity Reassign Asset Typesunder Regulatory Reporting Conversions -> Germany -> Conversion to Asset Regulation 2004.

Prerequisites

  • Backup Table for Value and Control Tables
  • The backup table TISSR_AA_BCK for the value and control tables TISSR_ANLART, TISSR_ANLARTT, and TISSR_ANLARTB exists and is active.

  • The data in the backup table fulfills the requirements of the German Asset Regulation 2004.

This table is shipped with the correct data. The table contains all of the data records for the control and value tables that are required for the conversion.
The data records already contain the value ANLV2004 as the indicator for the legal basis. Customer-specific changes are not required and are not supported by the program.
  • The data in the value and control tables used until the conversion is based on the German Asset Regulation 2000 (Circular R30/2002).
  • The backup table ISSR_RPI_MFT_BCK exists, is active, but does not contain any data.
This table is shipped with the correct version (without data).

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.

Features

The report makes the following table changes in the update run:

Changes to the value and control tables

  1. Copy the data records from the control and value tables (Asset Regulation 2002) to the associated backup table.
The backup table then contains both the data for the Asset Regulation 2002 and the data for the the Asset Regulation 2004. The data records are then assigned the relevant indicator for the legal basis of the conversion.
  1. Delete the existing data records (Asset Regulation 2002) from the value and control tables.
  2. Copy the data records from the backup table (Asset Regulation 2004) to the value and control tables.
The value and control tables then contain only data records with the latest version in line with Asset Regulation 2004.

Changes to the master data table ISSR_RPI_MFT

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 values.
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 (a new data record is generated) with the changed field values 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 converted for all relevant data records:

  • Administration Fields

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)

The program also triggers a subsequent posting for all of the assets affected. With large data volumes, this can mean that the program runtime is longer.

Selection

  1. Specify the statutory reporting variant for which the conversion is to be carried out.
  2. Enter a last day of month in the Date of Conversion field.
The specified date is the validity date for the conversion - both for dividing the data records according to changes and transfer postings, and for all subsequent conversion activities (conversion of the indicators according to R11/2005, adjustment of the SR additional classifications). This date is assigned to all new master data records.
Note: This date must be earlier than or equal to the system date because conversions in the future are not possible.
  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






BAL_S_LOG - Application Log: Log header data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 9150 Date: 20240520 Time: 081639     sap01-206 ( 125 ms )