Ansicht
Dokumentation

ISSR_MAIN - Ledger Position Generation for SAP Insurance Statutory Reporting

CPI1466 during Backup   General Data in Customer Master  
This documentation is copyright by SAP AG.

After you have made the necessary Customizing settings for the migration and migrated positions and flows to the SR feeder database (see Notes on Migrating Positions/Flows), you need to create ledger positions and SR flows to be able to create the relevant statutory lists.

Statutory reporting flows contain all of the data that statutory reporting uses as a basis for generating lists (together with the master data read for creating these lists and other feeder system information).

Statutory Reporting Ledger

The system manages the ledger flows and positions in the FISL ledger tables of table group ISSRFLDE. Table ISSRFLDDEA contains the line items and table ISSTRFLDET is the totals table. With the table group, SAP AG delivers standard ledgers specific to statutory reporting with names that lie outside the customer namespace: Ledger 3I = position ledger, 3J = revenue ledger , 3F = receivable ledger

Necessary Customizing Settings

Before you can create SR ledger positions and transfer flows, you must have carried out the following activities:

Activate Statutory Reporting

Using transaction ISSR_MAIN22 (Regulatory Reporting Settings for the Insurance Supervisory Authority → Activate Statutory Reporting), you activate statutory reporting for all company codes.

The three activities listed there must be carried out (their status must be green). In this process, FISL is regenerated. For this reason, take into account the warning message in the transaction.

General Settings

Under Variant-Dependent Settings → General Settings, you will find the relevant activities for generating ledger positions and ledger flows.

You should check or carry out the following activities: (Observe the notes in the corresponding IMG documentation.)

• Create Fiscal Year Variant

The system automatically creates a fiscal year variant with 366 days under the name SR; you can name the FY variant freely.

• Define Number Range Object DOCNR

Create a number range interval (for example, 01 with numbers 1 to 9999999999). The number taken here is used by the system for the document number ( DOCNR field) in the FISL line item table ISSRFLDEA. For subsequent postings that contain errors or have been deleted, you can reset the number assignment manually.

• Field Control Settings for Statutory Reporting Variant

Using transaction ISSR_MAIN_03C (Define Statutory Reporting Variant), you specify which fields the system transfers from tables ISSRPREFLOW (feeder database) and ISSR_RPI_MFT (SR master data such as stock, line of business, PRF, and statement identifiers) to which fields of the ledger tables ISSRFLDEA and ISSRFLDET.

SAP AG delivers the variant DE-V in sample Customizing settings. Under Define Line Item Table (Receiver Table), you also need to assign the number range interval you defined. Also check whether the predefined settings are complete (see Customizing documentation).

• Define SR Flow Types

The settings in this Customizing activity are included in the sample Customizing settings. You only need to make changes or amendments if you have changed the definition of SR FTPs and their assignment to the feeder system flow types (Customizing activity Define and Assign Flows) – for example, you have defined your own flow types. In this case, you also need to change the assignment between the SR flow types and the flow type part.

FTPs not assigned are not transferred to the SR ledger.

• Activate Statutory Reporting for Company Code

In this Customizing activity, you assign the statutory reporting variant (DE-V for Germany) to the company code and activate statutory reporting at company code level using the Activate Statutory Reporting indicator. You then assign the defined SR valuation area (OP) to the company code. The system transfers only assigned valuation areas to the SR ledger.

• Assign Ledger to Company Code

Here you assign ledgers 3I and 3J only (3K is not relevant), together with the fiscal year variant you defined, to the company code. The remaining settings are for your information only. The CrryFrwdYear field is set automatically by the balance carryforward report. Manual changes are required in exceptional cases only (for example, after the entire ledger position has been deleted).

Note: You require the Customizing activities in the Periodic Tasks area not to generate/subsequently post the ledger flows but to make the default settings for the balance carryforward report and to start this report.

Generate and Edit SR Ledger Flows

To generate ledger flows, the system summarizes the data from the feeder database (table ISSRPREFLOW), enriches the data records with the relevant statutory reporting master data (table ISSR_RPI_MFT), and fills the relevant ledger tables.

You can generate ledger flows in the following ways:

• Using the online posting, you copy the flow records automatically from the feeder system (or the accounting interface) to the statutory reporting ledger. For this purpose, the system generates the corresponding statutory reporting ledger flow for every relevant posting in the feeder system.

If you have activated statutory reporting for all systems, online postings are activated (activity Activate Statutory Reporting (Cross-System), transaction ISSR_MAIN22). The system saves the flows from the accounting interface initially to the SR feeder database and links them to an SR master data record (if one exists). You can deactivate online posting again in this activity.

• With the subsequent posting, you generate statutory reporting ledger flows if you have already imported the feeder system flows to the feeder database using the import reports (see Notes on Migrating Positions/Flows).

You start the subsequent posting using transaction ISSR_NB1 ( Generate Flows). To optimize the amount of data and thus optimize performance, limit the selection by specifying at least a company code, ledger type (B), and capital investment type. For more information, see the documentation for report RISSR_NABU.

• With other functions for identifier changes (asset category transfer posting) and after a business partner change.

Tools - Other Functions in Menu

1. Deleting Ledger Flows

In the event of Customizing errors, transfer errors, or other errors, you can delete the ledger flows from the ledger table using the Delete Flows application (transaction ISSR_NB2). Note that although the deletion log displays only records of the totals table ISSRFLDET, the system also deletes records from the line item table.

1. Position Display/Check

You can display and check transferred flows and positions using transactions GD23 (FI-SL: Local Actual Document Display), ISSR_GD20 (Select FI-SL Line Items), and ISSR_GD13 (Totals Record Display).

3. Data Organization in the Statutory Reporting Ledger

To organize data, you can currently use the two Customizing tools for balance carryforward and currency translation, which are known functions in FISL. You can find these functions under the Customizing node General Settings → Periodic Tasks.

The currency translation is only relevant when a local currency changeover is to be carried out at company code level. Since this is required only in rare cases, we refer you to the FISL documentation for currency translation.

In contrast, the balance carryforward is much more important. To be able to create the balance carryforward (see Create Balance Carryforward for Ledger, transaction ISSR_MAIN_GVTR), you first need to make the field assignments (transaction ISSR_MAIN_GVTR_FUDEF). The transaction automatically creates an ISSR field assignment in the FISL Customizing tables and assigns it to the corresponding ledgers (3I and 3J). You can control this using transaction ISSR_MAIN_GVTR_FU (Customizing activity Assign Field Movement for Balance Carryforward).

rdisp/max_wprun_time - Maximum work process run time   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 11803 Date: 20240523 Time: 183045     sap01-206 ( 175 ms )