SAP® Documentation

Single view

/PM0/AB_TEST_ACCOUNTING - Obsolete: Display Journal and Settlement Information for Contract

Vendor Master (General Section)   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

The report is to provide an overview of the contract history and the associated transactions and accounts. It is only to be used for test purposes and does form part of the scope of delivery for FS-PM.

Master data is not displayed in the report. It is also possible to use the new functionality 'Scrolling in the Journal'. If necessary, you can enhance the report with further transactions and accounts.

If you notice any errors, or have any suggestions for improvements to the display, contact michael.spiess@sap.com.

Integration

The report is only to be used for in-force business management.

Prerequisites

The policy exists in the system and has been released

Features

1. Aggregation using the Accounting From Date for a transaction

All cashflow, non-cashflow and account balances aggregated using the Accounting From Date are listed here. The display of transactions and account balances is dependent on the selected product (see below).

Double clicking on an entry displays all transactions for the selected Accounting From Date. Double clicking on an entry now displays all transactions for an Accounting From Date, which are also selected for the chose journal number.

2. Aggregation using Journal Number

All cashflow, non-cashflow and account balances aggregated using the journal number are listed here. The display of transactions and account balances is dependent on the selected product (see below).

Reversed processing steps are displayed on an aggregated basis and offset against the processing to be reactivated. This allows you to check correct reversal. Double-clicking on a reversed entry allows you to find information about all reversed entries that have been reversed with the same reversal transaction.

Double-clicking on a reversed or non-reversed entry takes you to a list that displays all cashflow and non-cashflow transactions for a journal number. Account balances are not displayed.

The report has product-dependent subviews when displaying the aggregated values:

General View for All Products When Displaying Aggregated Values

  1. Effective date for journal entry (valid_from_dt) for aggregation using journal number, or 'Accounting Date From' for aggregation using effective date
  2. Journal number
  3. Processing text for journal number
  4. Business process
  5. Cashflow amount
  6. Insurable object no.
  7. Name of insurable object

Special View for Capital and Annuity Products

  1. Savings premium from 'Premium Splitting' transaction
  2. Risk premium from 'Premium Splitting' transaction
  3. Costs and interest from the 'Premium Splitting' transaction
  4. All dividends from the 'Dividend Allocation', 'Dividend Clearing' 'Final Dividend' and 'Accumulated Interest' transactions.
  5. Net reserve from the 'Balance Sheet Values' account
  6. Coverage reserve from the 'Balance Sheet Values' account
  7. Activated entitlements for the financial accounting date, from the 'Balance Sheet Values' account
  8. Risked capital from the 'Balance Sheet Values' account
  9. Statistical premium from the 'Balance Sheet Values' account
  10. Statistical sum insured from the 'Balance Sheet Values' account
  11. Premium carryforward from the 'Balance Sheet Values' account

Special View for Fund Products

  1. Investment amount from the 'Premium Splitting' transaction (posting code N010 and N073)
  2. Various costs from the 'Premium Splitting' transaction (all posting codes except N010 and N073)
  3. Investment amounts from the 'Fund Shares' transaction (all posting codes)
  4. Fund assets from the 'Balance Sheet Account' account
  5. Statistical premium from the 'Balance Sheet Account' account
  6. Statistical sum insured from the 'Balance Sheet Account' account
  7. Risked capital 1 from the 'Balance Sheet Account' account
  8. Premium carryforward from the 'Balance Sheet Account' account

Special View for Non-Life Products

  1. Sum insured from 'Object Liability Total' transaction
  2. Net premium without installment surcharge from 'Object Liability Total' transaction
  3. Net premium from the 'Premium Splitting' transaction (posting code N216)
  4. Insurance tax from the 'Premium Splitting' transaction (posting code N217)
  5. Risk surcharges and other splitting values from the 'Premium Splitting' transaction (all except posting code N216 and N217)
  6. Values from 'Premium Carryforward' transaction

Technical Documentation:

The report first selects all cashflow and non-cashflow transactions, journal data and other relevant data for the selected contract from the data and transfers it to internal global tables (gt_cf, gt_abdjpol, gt_noncf, and so on). The global tables for transactions contain the 'flattened' structure, meaning the document header with items.

The next step creates the tables gt_eff, gt_ino and gt_ino_cancelled, which contain the data aggregated according to effective date, journal number or reversal journal number. It is not possible to use a collective table, as the effective date for the transactions (Accountingfrom_dt) can differ from the effective date for the corresponding journal entry (valid_from_dt). Aggregation takes place in the gt_eff table according to the Accounting From Date for the transactions, and in the gt_ino table according to the journal number.

Table gt_eff (key is the effective date):

Each transaction from the global internal table is added to the table gt_eff with the COLLECT command, with the key Effective Date = Accounting From Date for the transaction.

Table gt_ino (key is the journal number)

Each transaction that has a journal number is added to the table gt_ino with the COLLECT command, with the key Journal Number = Journal Number for transaction. Cashflow documents that do not have a journal number are aggregated with journal number 99999.

Table gt_ino_cancelled (key is the reversal journal number)

Each transaction that has a journal number, and for which the journal number in the contract journal refers to a reversal journal number and for which the transaction is not an inverse transaction (reversaldoc_id = 0) is added to the gt_ino_cancelled table with the COLLECT command. This differentiation is necessary, as inverse transactions are not regenerated when reversing processing that reversed processing (reactivation) and generated inverse transactions. There is therefore no inverse transaction for the inverse transaction.

Steps for Adding More Fields in the Aggregated View

  1. Enhance the category x_output if account data is displayed, or enhance the category amount_fields if new transactions are to be displayed and aggregated.
  2. Enhance the method map_non_cf_to_aggregate for non-cashflow transactions or map_acc_to_output for accounts.
  3. Enhance the method write_output
  4. Set the list title and transfer to the method write_output_top-of-page with copy & paste
  5. Enhance documentation






BAL_S_LOG - Application Log: Log header data   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 8116 Date: 20191019 Time: 090237     sap01-206 ( 61 ms )

Our Service

Looking for Support? Questions?

The

Consolut

Callback-Service

Leave us your contact details and we will call you back. Panels marked with * are mandatory.