Ansicht
Dokumentation

Incoming Documents in the Claims Management System (New) ( RELNFSCM_471_ARCHIVELINK )

Incoming Documents in the Claims Management System (New) ( RELNFSCM_471_ARCHIVELINK )

PERFORM Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Incoming Documents in the Claims Management System (New)

Use

From Release 4.71, you can use the Archive Link to store incoming documents in an archive, and then assign them to a claim or a subobject (claim, subclaim, damaged object, and so on).

You can store and assign documents in one of the following ways:

  • You can use the navigation tree to store assign documents, for the Claim and Subclaim subobject categories only:
In the context menu for the subobject, select the Store document entry.
In the subsequent Store document dialog box, you can store documents for the following objects:
  • For the current subobject

  • For all subordinate subobjects in the hierarchy

  • For cross-subclaim subobject categories (such as participants)

If you click on the Store document icon on the Archived documents screen, this takes you back to the Store document screen.
  • Documents button
The Documents button is available in the details for the claim item, appraisal order and for invoice processing. This allows you to call up a window for document storage. You can only store documents for the current subobject here.
  • Direct Input
You can use the Direct Input interface to assign incoming documents to a claim or subobject. You can find more information in the release note for Direct Input.

You have to specify the folder and the name for the document to be stored on the local hard disk in the respective windows.

In the Direct Input interface, you can either specify an access path for the document, or an existing archive ID.

Irrespective of the processing type, the system also requires information about the business type of the document (such as invoice, appraisal, accident sketch). You can also specify a short text, to enable more accurate identification of the stored document.

You are able to get an overview of already assigned documents as follows:

  • On claim header level, the Documents tab page provides a list of documents that were assigned directly to the claim, or to an associated subobject.
  • On subclaim level, the Archived Documents tab page provides a list of documents that were assigned to the relevant subclaim, or to a subobject within this subclaim. Assignments to cross-subclaim subobjects (such as participants) are also displayed.
  • You can use the Documents button to get an overview of documents for the current subobject. The color of the button denotes whether documents have already been assigned to the subobject. If documents have already been assigned to the subobject, the button is green.
In display mode, the button is only displayed if documents have already been assigned.

In all variants, a double click allows you to display documents, create more assignments and delete existing assignments.

If you store or assign incoming documents, the BRF event AL001 is triggered. If this event is triggered, the system logs the document assignment as standard in the activities log.

If an error occurs during archiving or document assignment, the BRF event ALUNDO is triggered. This can have an effect on previously executed actions.

If you delete a document assignment, the BRF event ALDEL is triggered. You can define actions that are to be executed.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information






ROGBILLS - Synchronize billing plans   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 4733 Date: 20240520 Time: 235117     sap01-206 ( 63 ms )