C_InsurClm1stNotifTP
Schadenmeldung
C_InsurClm1stNotifTP is a Consumption CDS View that provides data about "Schadenmeldung" in SAP S/4HANA. It reads from 1 data source (I_InsurClm1stNotifTP) and exposes 48 fields with key field InsuranceClaim. It has 13 associations to related views. It is used in 1 Fiori application: First Notice of Loss.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| I_InsurClm1stNotifTP | I_InsurClm1stNotifTP | from |
Associations (13)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [1..1] | I_InsurClmIncdntType | _IncidentType | _IncidentType.InsurClmPolicyProduct = $projection.InsurClmPolicyProduct and _IncidentType.InsurClmPolicyProdGeneration = $projection.InsurClmPolicyProdGeneration and _IncidentType.InsurClmPolicyProductVersion = $projection.InsurClmPolicyProductVersion and _IncidentType.InsurClmIncdntType = $projection.InsurClmIncdntType |
| [0..*] | I_InsurClmIncdntTypeText | _IncidentTypeText | $projection.InsurClmIncdntType = _IncidentTypeText.InsurClmIncdntType |
| [0..1] | I_Country | _Country | _Country.Country = $projection.InsurClmLossLocCountry |
| [0..1] | I_Region | _Region | _Region.Region = $projection.InsurClmLossLocRegion and _Region.Country = $projection.InsurClmLossLocCountry |
| [0..*] | C_InsurClm1stNotifNoteTP | _Note | $projection.InsuranceClaim = _Note.InsuranceClaim |
| [0..*] | C_InsurClm1stNotifDmgdVehTP | _DamagedVehicle | $projection.InsuranceClaim = _DamagedVehicle.InsuranceClaim |
| [0..*] | C_InsurClm1stNotifWtnssTP | _Witness | I_InsurClm1stNotifTP.InsuranceClaim = _Witness.InsuranceClaim |
| [0..1] | I_InsurClmHandler | _ClaimHandler | $projection.InsuranceClaim = _ClaimHandler.InsuranceClaim |
| [1..1] | I_InsurClm1stNotifIncdntTypeVH | _InciVH | $projection.InsurClmIncdntType = _InciVH.InsurClmIncdntType |
| [0..1] | I_InsurClm1stNotifCauseVH | _CauseVH | $projection.InsurClmCauseOfLoss = _CauseVH.InsurClmCauseOfLoss |
| [1..1] | I_InsurClm1stNotifBP | _PolicyHolder | _PolicyHolder.BusinessPartner = $projection.InsurancePolicyholder |
| [1..1] | I_InsurClm1stNotifContrValHelp | _ContractVH | _ContractVH.InsuranceContract = $projection.InsuranceContract |
| [0..*] | C_InsurClm1stNotifFactTP | _Facts | $projection.InsuranceClaim = _Facts.InsuranceClaim |
Annotations (18)
| Name | Value | Level | Field |
|---|---|---|---|
| EndUserText.label | Schadenmeldung | view | |
| AbapCatalog.sqlViewName | CICL1STNFTP | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| VDM.viewType | #CONSUMPTION | view | |
| ObjectModel.compositionRoot | true | view | |
| ObjectModel.transactionalProcessingDelegated | true | view | |
| ObjectModel.createEnabled | true | view | |
| ObjectModel.updateEnabled | EXTERNAL_CALCULATION | view | |
| ObjectModel.deleteEnabled | EXTERNAL_CALCULATION | view | |
| ObjectModel.draftEnabled | true | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view | |
| ObjectModel.usageType.sizeCategory | #XL | view | |
| ObjectModel.usageType.serviceQuality | #X | view | |
| OData.publish | true | view | |
| Metadata.allowExtensions | true | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| AccessControl.personalData.blocking | #REQUIRED | view |
Fiori Apps (1)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F2846 | First Notice of Loss | Transactional | Desktop/Mobile App to create a claim by recording the first notification of loss information including loss location, description of loss/accident, involved participants, injuries and property damages. |
First Notice of Loss
Business Role: Customer Service Representative - Insurance
With this app, you can - in the role of a service center employee - create an auto claim with the basic claim data.Note This SAP Fiori app with the SAP Fiori ID F2846 is deprecated with SAP S/4HANA 2021 (no longer recommended). The app is still available but will be deleted in the next release. Instead, use the new SAP Fiori app First Notice of Loss (FNOL) with the SAP Fiori ID F5750 (see First Notice of Loss (FNOL)).
Key Features: Capture of the data for a new auto claimTo do this, in the top right of the start page click the plus sign with the tooltip Create Claim.You can enter the following claim data:General loss information (all three input fields are required entry fields)ContractYou can use the input help to search for a contract.Then choose “Enter”. Otherwise, the system cannot provide any values for the input help for the Incident Type field. Incident typeUse the input help to select an incident type and then choose “Enter”. Otherwise, the system cannot provide any values for other fields, such as the cause of loss. Date of loss Origin of lossCause of loss Loss descriptionNote After you have created a claim, the following applies: The system displays the loss description in the app only if the long texts are replicated (see App Configuration: Notice of Loss, "Replication of Long Texts"). If the long texts are not replicated, the loss description is displayed only in the backend system in expert mode. Loss location Damaged vehicleThe system gets the input data about the vehicle and driver from the contract.Note If you enter a text to describe the damage, note the following: The system displays this text only if you have activated the replication of long texts (see App Configuration: Notice of Loss, "Replication of Long Texts"). You can order a towing service when you enter data about the damaged vehicle.The system locates the possible towing services based on the loss location entered and displays these towing services on a map.You order a towing service as follows:Select a towing service (either using the symbols on the map or in the Business Partner field under Towing Service). Choose Copy. For more information about the prerequisites, see App Configuration: Notice of Loss, "Ordering a Towing Service and Displaying a Map". WitnessYou can enter an existing business partner as a witness or create a new business partner.Note You can enter the first or last name of the witness directly in the Participant BP No. field as a search term.If you enter an existing business partner and choose “Enter”, the system fills the business partner fields with the data from the backend system. It is then no longer possible to edit the business partner fields. You can edit the fields again if you then remove the business partner number and choose “Enter”. Details on origin of lossYou can enter detailed information about the claim based on preconfigured questions and answers for structured facts capture.For more information, see Structured Facts Capture. NotesYou can enter a note title and note text. Display of header data for the notice of lossAs soon as you enter the contract and incident type and choose “Enter”, the system displays the policyholder and their date of birth in the header data for the notice of loss. From here, you can contact the policyholder directly by mail or telephone (provided the corresponding contact data is entered in the user master data).After you have created a claim, the system also displays the claim handler in the header data. For more information about the prerequisites, see App Configuration: Notice of Loss. Creation of a claimYou can use the data captured in the notice of loss to create a claim in the backend system. You can then no longer edit the data in the app. It is only possible to edit the claim further in the backend system in expert mode. Automatic creation of a draftAs soon as you enter data in the app (without explicitly creating a claim), the app automatically saves this data in draft form. This ensures that data is not lost if you are interrupted during data capture and have not created a claim. Display of existing drafts or claimsYou can display existing drafts or claims on the start page of the app. Drafts are marked accordingly.The following filter or search criteria is available:Filter by editing statusYou can filter by the following editing statuses: All and Own Draft. Then choose Start.Note All editing statuses other than All and Own Draft are not relevant for the Notice of Loss app. Search for specific data using direct inputYou can search for the following data in the first input field by entering the data directly and then choosing “Enter”:First/last name of policyholder Contract number Claim number Claim handler who created the draft Claim handler who last changed the draft The system then displays the drafts and claims that contain the specified search term. Navigation to a draft or notice of loss for which a claim has already been createdTo navigate to a draft or notice of loss for an existing claim, click the corresponding row. In a draft, you can enter additional data or change the existing data but in the notice of loss you can only display the data for an existing claim. Deletion of a draftSelect the radio button in the row and choose Delete.
Fields (48)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | InsuranceClaim | InsuranceClaim | Claim Number | |
| InsuranceContract | InsuranceContract | Contract | ||
| ChangedOnDateTime | ChangedOnDateTime | Last Changed At | ||
| LastChangedByUser | LastChangedByUser | User Name | ||
| CreationDateTime | CreationDateTime | Timestamp | ||
| CreatedByUser | CreatedByUser | User Name | ||
| IsReviewed | ||||
| InsurClmPolicyProduct | InsurClmPolicyProduct | Policy Product | ||
| InsurClmPolicyProdGeneration | InsurClmPolicyProdGeneration | Generation | ||
| InsurClmPolicyProductVersion | InsurClmPolicyProductVersion | Version | ||
| AuthorizationGroup | _Contract | AuthorizationGroup | AuthorizGroup | |
| FirstName | _Contract | FirstName | First Name | |
| LastName | _Contract | LastName | Last Name | |
| InsurancePolicyholderName | ||||
| InsurClmIncdntType | InsurClmIncdntType | Incident Type | ||
| InsurClmIncdntTypeName | ||||
| InsurClmType | InsurClmType | Claim Type | ||
| InsurClmTypeGeneration | InsurClmTypeGeneration | Generation | ||
| InsurClmTypeVers | InsurClmTypeVers | Clm Type Versn | ||
| InsurClmAuthznGrp | InsurClmAuthznGrp | AuthGroup (VIP) | ||
| InsurancePolicyholder | InsurancePolicyholder | BusPartner | ||
| InsurClmDateOfLoss | InsurClmDateOfLoss | Date of Loss | ||
| InsurClmCauseOfLoss | InsurClmCauseOfLoss | Cause | ||
| InsurClmLossLocAddressID | InsurClmLossLocAddressID | Loss Location | ||
| InsurClmLossLocStreet | InsurClmLossLocStreet | Text | ||
| InsurClmLossLocHouseNumber | InsurClmLossLocHouseNumber | House Number | ||
| InsurClmLossLocCity | InsurClmLossLocCity | Name | ||
| InsurClmLossLocRegion | InsurClmLossLocRegion | Venue Region | ||
| InsurClmLossLocPostalCode | InsurClmLossLocPostalCode | Postal Code | ||
| InsurClmLossLocCountry | InsurClmLossLocCountry | Venue: Ctry/Reg | ||
| InsurClmLossLocLongitude | InsurClmLossLocLongitude | |||
| InsurClmLossLocLatitude | InsurClmLossLocLatitude | |||
| InsurClmDescriptionOfLoss | InsurClmDescriptionOfLoss | |||
| _Contract | _Contract | |||
| _ClaimHandler | _ClaimHandler | |||
| _Country | _Country | |||
| _Region | _Region | |||
| _IncidentType | _IncidentType | |||
| _IncidentTypeText | _IncidentTypeText | |||
| _LossCause | _LossCause | |||
| _PolicyHolder | _PolicyHolder | |||
| _DamagedVehicle | _DamagedVehicle | |||
| _Witness | _Witness | |||
| _Note | _Note | |||
| _Facts | _Facts | |||
| _InciVH | _InciVH | |||
| _CauseVH | _CauseVH | |||
| _ContractVH | _ContractVH |
Derived SQL interpretation, reconstructed from the parsed view metadata (data sources, associations, and field mappings). SAP annotations are omitted and the structure is reformulated as SQL — this is a functional approximation, not the verbatim SAP source.
-- Derived SQL interpretation of CDS view C_InsurClm1stNotifTP.
-- Reconstructed from parsed metadata (data sources, associations, fields).
-- SAP annotations are omitted and the structure is reformulated as SQL;
-- this is a functional approximation, not the verbatim SAP source. Some join
-- conditions may be unavailable and a few CDS constructs are kept as-is.
-- SQL view name: CICL1STNFTP
CREATE VIEW C_InsurClm1stNotifTP AS
SELECT
InsuranceClaim,
InsuranceContract,
ChangedOnDateTime,
LastChangedByUser,
CreationDateTime,
CreatedByUser,
cast( ' ' as icl_active preserving type ) AS IsReviewed,
InsurClmPolicyProduct,
InsurClmPolicyProdGeneration,
InsurClmPolicyProductVersion,
_Contract.AuthorizationGroup AS AuthorizationGroup,
_Contract.FirstName AS FirstName,
_Contract.LastName AS LastName,
cast ( _PolicyHolder.BusinessPartnerName as icl_policyholder_name preserving type ) AS InsurancePolicyholderName,
InsurClmIncdntType,
_IncidentTypeText[ Language = $session.system_language ].InsurClmIncdntTypeName AS InsurClmIncdntTypeName,
InsurClmType,
InsurClmTypeGeneration,
InsurClmTypeVers,
InsurClmAuthznGrp,
InsurancePolicyholder,
InsurClmDateOfLoss,
InsurClmCauseOfLoss,
InsurClmLossLocAddressID,
InsurClmLossLocStreet,
InsurClmLossLocHouseNumber,
InsurClmLossLocCity,
InsurClmLossLocRegion,
InsurClmLossLocPostalCode,
InsurClmLossLocCountry,
InsurClmLossLocLongitude,
InsurClmLossLocLatitude,
InsurClmDescriptionOfLoss
FROM I_InsurClm1stNotifTP
LEFT OUTER JOIN I_InsurClmIncdntType AS _IncidentType ON _IncidentType.InsurClmPolicyProduct = InsurClmPolicyProduct AND _IncidentType.InsurClmPolicyProdGeneration = InsurClmPolicyProdGeneration AND _IncidentType.InsurClmPolicyProductVersion = InsurClmPolicyProductVersion AND _IncidentType.InsurClmIncdntType = InsurClmIncdntType -- association [1..1]
LEFT OUTER JOIN I_InsurClmIncdntTypeText AS _IncidentTypeText ON InsurClmIncdntType = _IncidentTypeText.InsurClmIncdntType -- association [0..*]
LEFT OUTER JOIN I_Country AS _Country ON _Country.Country = InsurClmLossLocCountry -- association [0..1]
LEFT OUTER JOIN I_Region AS _Region ON _Region.Region = InsurClmLossLocRegion AND _Region.Country = InsurClmLossLocCountry -- association [0..1]
LEFT OUTER JOIN C_InsurClm1stNotifNoteTP AS _Note ON InsuranceClaim = _Note.InsuranceClaim -- association [0..*]
LEFT OUTER JOIN C_InsurClm1stNotifDmgdVehTP AS _DamagedVehicle ON InsuranceClaim = _DamagedVehicle.InsuranceClaim -- association [0..*]
LEFT OUTER JOIN C_InsurClm1stNotifWtnssTP AS _Witness ON I_InsurClm1stNotifTP.InsuranceClaim = _Witness.InsuranceClaim -- association [0..*]
LEFT OUTER JOIN I_InsurClmHandler AS _ClaimHandler ON InsuranceClaim = _ClaimHandler.InsuranceClaim -- association [0..1]
LEFT OUTER JOIN I_InsurClm1stNotifIncdntTypeVH AS _InciVH ON InsurClmIncdntType = _InciVH.InsurClmIncdntType -- association [1..1]
LEFT OUTER JOIN I_InsurClm1stNotifCauseVH AS _CauseVH ON InsurClmCauseOfLoss = _CauseVH.InsurClmCauseOfLoss -- association [0..1]
LEFT OUTER JOIN I_InsurClm1stNotifBP AS _PolicyHolder ON _PolicyHolder.BusinessPartner = InsurancePolicyholder -- association [1..1]
LEFT OUTER JOIN I_InsurClm1stNotifContrValHelp AS _ContractVH ON _ContractVH.InsuranceContract = InsuranceContract -- association [1..1]
LEFT OUTER JOIN C_InsurClm1stNotifFactTP AS _Facts ON InsuranceClaim = _Facts.InsuranceClaim -- association [0..*]
;
Learn More
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- SAP Fiori Apps Architecture — How Fiori Apps Connect to Data
- CDS View Annotations — A Complete Guide
- What Is a CDS View in SAP S/4HANA?
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- CDS View Field Mapping and Associations
- Understanding the SAP S/4HANA Data Model
- CDS View Extensions and Custom Fields in SAP S/4HANA
- Released APIs and Stability Contracts in SAP S/4HANA
- BSEG to ACDOCA: The Universal Journal Migration
- Business Partner Migration: KNA1/LFA1 to BUT000
- Material Document Migration: MSEG/MKPF to MATDOC
- How to Find the Right CDS View for an SAP Table
- BW Extractor to CDS View Migration Guide
- S/4HANA CDS View Deprecation: What You Need to Know
- ABAP CDS View Tutorial — From Basics to Real-World Examples
- RAP and CDS Views — Building Transactional Apps in SAP S/4HANA
- Sales Document Status Migration: VBUP/VBUK Removal in S/4HANA
- CO Tables in S/4HANA: COEP, COBK, COSS, COSP to ACDOCA