Hierarchy

⤷

⤷

IMG Activity
ID | SIMG_ICL_DUPL_CHECK | BAdI: Find Possible Duplicates During Claim Creation |
Transaction Code | S_KK4_08000465 | IMG Activity: |
Created on | 20011203 | |
Customizing Attributes | _ICL_DUPLICATE_CHECK | Find Possible Claim Duplicates During Creation Process |
Customizing Activity | SIMG_ICL_DUPL_CHECK | Find Possible Claim Duplicates During Creation Process |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | _ICL_DUPLICATE_CHECK |
Use
The system uses this Business Add-In (BAdI) to perform a check for duplicate creation of a claim.
When you create a claim, the system performs a check for duplicates at the following different events:
- Check for duplicates after initial screen
When you are on the Create Claim: Claim Processing screen and select @2K@ with the quick info text Enter or @0Y@ with the quick info text Create, the system performs a check for duplicates. Very little data on the claim is available at this point in time, meaning that the only search criteria that can be used for this check are:
- Date of claim/loss
- Contract
- Policyholder
- Incident type
- Check for duplicates when claim is saved
When you save the claim (BDT event DCHCK), it can be assumed that more data is available, allowing a more exact search.
Requirements
You have set the Check for Duplicate flag in IMG activity Configure Internal Claim Types (at claim header level in the detail view of the version of the internal claim type).
Standard settings
Check for duplicates after initial screen
An active standard implementation and a corresponding layout of the hit list are available for the search after the initial screen. The system displays the claims that are within a certain period of time around the claim date that you entered on the initial screen. You specify this period in IMG activity Configure Internal Claim Types (in the Days Deviation field at claim header level in the detail view of the version of the internal claim type).
Check for duplicates when the claim is saved
There is no implementation for a search as the claim is being saved.
The BAdI is not filter-dependent nor can it be used multiple times.
Activities
After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:
- In the dialog box, enter a name for the implementation of the Add-In and choose Create.
The system displays the initial screen for creating Business Add-In implementations. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.
andendmethod.
statements. - Save and activate your code. Navigate back to the Change Implementation screen.
Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step: - Choose Activate.
When the application program is executed, the code you created is run through.
The system provides the interface of the BAdI with data on the claim, existing subclaims, and participant occurrence. Within the BAdI you can use corresponding function modules to call further data from the current memory of the claim. The return value is a table with claim data on possible duplicates which is displayed to the claim handler. The claim handler can then decide whether he/she wants to continue saving the claim or to cancel.
See also:
Methods:
- Execute Search for Duplicates (Initial Screen)
- Execute Search for Duplicates (Event DCHCK)
- Prepare Hit List
Interface:
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | _ICL_DUPLICATE_CHECK | 0 | ITB0000001 | Claims Management |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20031128 |
SAP Release Created in | 464 |