Direct Input for Collective Subrogation/Recovery

In direct input you can import virtually all collective subrogation/recovery data (including the posting to the Collections & Disbursements system) without the need for dialog. Only the texts for the claim bundle cannot be imported via direct input.

Collective Subrogation/Recovery Objects in the Database

The following individual data objects are stored in the database for collective subrogation/recovery:

Data object	Database table	Direct input strukture
Claim Bundle (meaning collective subrogation/recovery here)	ICLCCEVENT	ICLCCEVENT_DI (plus header data)
Region	ICLCCEVENTR	ICLCCEVENTR_DI
Participants	ICLCCEVENTB	ICLCCEVENTB_DI
Description	<R/3 Function>	This is not implemented in the claim bundle at present.
Subclaim assignment	ICLCLAIMA	ICLE_SUBCLASSIGN_DI_S This structure is contained in generic structure ICL_GEN_DI .
Settlement	ICLEBULKSBR	ICLEBULKSBR_DI_S This structure is contained in generic structure ICL_GEN_DI .
Receivables header	ICLPAY	ICLE_BSR_REQUEST_DI_S This structure is contained in generic structure ICL_GEN_DI .
Receivables item	ICLPAYI	ICLE_BSR_REQUESTITEM_DI_S This structure is contained in generic structure ICL_GEN_DI .

Processing Modes

The following processing modes are available for processing collective subrogation/recovery data via direct input:

Create/Insert

This processing mode is available in all data objects.
Change

This processing mode is only available in the following data objects:
- Claim bundle (collective subrogation/recovery)
- Participants
- Settlement
Delete

This processing mode is only available in the following data objects:
- Region
- Participants

Procedure

To create data objects for collective subrogation/recovery, you must perform at least two direct input runs:

First direct input run

In the first direct input run you can only create the following objects:
- Claim bundle (collective subrogation/recovery)
- Region
- Participants
- Subclaim assignments
- Settlements
Second direct input run

In the second direct input run you can create receivables and park them or post them. The prerequisite is that you have created the following objects in the first direct input run:
- Claim bundle (collective subrogation/recovery)
- Subclaim assignment, provided you want to create receivable items from payment items
  
  You cannot create the participants required for the receivable (payers) and settlements until the second direct input run.

Notes on Execution of Direct Input

Test: Function module ICLE_CCEVENT_DI
Data transfer:

Use transaction KCLJ (external data transfer)

In contrast to the claim, there are no transfer programs or transactions yet for the claim bundle. This means that you have to develop your own transfer procedure. In this transfer procedure you must use the main components that are called by the above function module.

Program Logic and Checks

When data is imported via direct input, the system behaves in the same way as in dialog mode, with regards to the validity checks and automatic corrections.

When data is being imported, the system continues processing if it detects an error. This ensures that the system is able to check the remaining data and that the final log contains all error messages. If errors exist, you can correct the data in question and you only have to repeat the direct input once.