Ansicht
Dokumentation

RICL_REPLICATE_NOTES_FOR_FIORI - Replicate Notes from SAPoffice to Table SGBT_NTE_CONT

CPI1466 during Backup BAL Application Log Documentation
This documentation is copyright by SAP AG.

Purpose

You can use this report to replicate notes.

Background

Claim notes are saved in the following database tables:

In SAP Claims Management: ICLNOTE

In SAP Business Workplace:

Header data of the note (including note title): SOOD

Long texts of the notes: cluster table SOC3

This is sufficient for the processing of notes during claims processing. If you want to display notes in applications other than the back-end application (such as in SAP Fiori applications), however, this is not directly possible. The reason for this is that the notes in table SOC3 have a file format that cannot be read by the CDS views. It is also not possible to perform a simple search in the note texts from the ABAP programs because the cluster data has to be decrypted first.

Framework for Replication of Notes

A basic framework is available in the on-premise edition of SAP S/4HANA in which you can save notes in table SGBT_NTE_CONT in a plain text format. This means that these notes can also be read by CDS views. The framework does not replace the existing note functions in SAP Claims Management but simply enhances these functions.

You replicate notes in table SGBT_NTE_CONT as follows:

To replicate notes from existing claims, run this report (RICL_REPLICATE_NOTES_FOR_FIORI).
To replicate notes that are created or changed in the future, activate the enhancement implementation ICL_CLAIM_UPDATE_NOTES in Business Add-In (BAdI) BADI_ICL_CLAIM_UPDATE (Customizing activity BAdI: New and Changed Data When Saving a Claim).

As soon as the system saves the claim, it automatically replicates the notes in table SGBT_NTE_CONT.

Integration

Replicated notes are an integral part of the SAP Fiori app Notice of Loss and can be evaluated using the CDS view I_InsurClmNoteExtn.

Prerequisites

Table ICLNOTE contains notes.

Features

Selection

Since the productive system usually contains a large number of notes, we recommend you proceed as follows:

Perform a test run first using one or only a few claim numbers.
Once the test run has completed without errors, perform an update run. To do this, split the claims whose notes you want to replicate into sensible intervals, such as claim numbers 1-10,000, 10,001-20,000, 20,001-30,000, and so on.

Do not use only one run that processes all notes in sequence.

Start the update run for the first interval.
Start the update run for the second interval, and so on.

Notes for the fields:

If you set the Include Replicated checkbox, the system replicates notes that have already been replicated again. Note: If a note has already been replicated, the NOTEID field is filled in table ICLNOTE.

The Commit After x Notes field specifies the number of replicated notes after which the system executes a database commit.

If you set the Display Note Texts checkbox, the system displays the key, title, and long text for each note.

This checkbox is relevant for development and test systems only. This checkbox is ignored by the productive system since it is only important in this system whether a note has been replicated without errors (see also "Output").

Standard Variants

Output

The system displays the number of replicated notes. If an error occurs during the replication of a note, the system displays the note key and a generic error message.

Errors should occur only if incorrect Customizing settings have been made for the notes. If an error occurs, check the following Customizing activities:

Table SGBT_NTE_TYPE (maintenance view VSGBT_NTE_TYPE)

The following entry must exist in this maintenance view:

NAME = ICL_NOTE

Table SGBT_NTE_TYASSGN (maintenance view VSGBT_NTE_TYASGN)