Prompt for the TarifApp

Please create a React-JS application for the TarifModule. The application  has to offer the following views for the user interface: 
    1. CallcenterView 
    2. TarifView 
    3. TarifkomponenteView 
    4. ZugangsmittelView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below.

1. The CallcenterView must contain the following fields: 
    - name: CarsharingOrganisation   type: CarsharingOrganisation 
    - name: Name   type: STRING 
    - name: Telefonnummer   type: STRING 
    - name: Zeitzone   type: STRING 
The data source for the [CarsharingOrganisation] select control should be loaded from the relative URL: 
    "/CarsharingOrganisationService/carsharingorganisation"   (HTTP-GET) 
An existing Callcenter entity should be loaded from the relative URL: 
    "/TarifService/callcenter/{id}"   (HTTP-GET) 
If a new Callcenter entity has been created, the new entity should be posted to the relative URL: 
    "/TarifService/callcenter"   (HTTP-POST) 
If an existing Callcenter entity has been updated, the modified entity should be sent to the relative URL: 
    "/TarifService/callcenter/{id}"   (HTTP-PUT) 
If an existing Callcenter entity has to be deleted, the following relative URL should be called: 
    "/TarifService/callcenter/{id}"   (HTTP-DELETE)

2. The TarifView must contain the following fields: 
    - name: Anmeldegebuehr   type: STRING 
    - name: Beschreibung   type: STRING 
    - name: CarsharingOrganisation   type: CarsharingOrganisation 
    - name: FreeFloatingTarif   type: BOOL 
    - name: Kaution   type: STRING 
    - name: KilometerAbrechnung   type: BOOL 
    - name: Monatspauschale   type: STRING 
    - name: Name   type: STRING 
The data source for the [CarsharingOrganisation] select control should be loaded from the relative URL: 
    "/CarsharingOrganisationService/carsharingorganisation"   (HTTP-GET) 
An existing Tarif entity should be loaded from the relative URL: 
    "/TarifService/tarif/{id}"   (HTTP-GET) 
If a new Tarif entity has been created, the new entity should be posted to the relative URL: 
    "/TarifService/tarif"   (HTTP-POST) 
If an existing Tarif entity has been updated, the modified entity should be sent to the relative URL: 
    "/TarifService/tarif/{id}"   (HTTP-PUT) 
If an existing Tarif entity has to be deleted, the following relative URL should be called: 
    "/TarifService/tarif/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Tarifkomponente columns: 
    - column: Tarif 
    - column: Komponententyp 
    - column: PreisProEinheit 
    - column: NurNebenzeit 
    - column: Einheit 
    - column: NurHauptzeit 
The table should have the title "Tarifkomponentes" und the data must be loaded from the server with the following relative URL: 
    "/TarifService/tarifkomponente/tarif/{id}" 
Add a HTML table to the view with the following Reservierung columns: 
    - column: StartGeplant 
    - column: StationRueckgabe 
    - column: StationAbholung 
    - column: StorniertAm 
    - column: Status 
    - column: Mitgliedschaft 
    - column: Tarif 
    - column: EndeGeplant 
    - column: Fahrzeug 
    - column: ErstelltAm 
The table should have the title "Reservierungs" und the data must be loaded from the server with the following relative URL: 
    "/StationService/reservierung/tarif/{id}"

3. The TarifkomponenteView must contain the following fields: 
    - name: Einheit   type: STRING 
    - name: Komponententyp   type: STRING 
    - name: NurHauptzeit   type: BOOL 
    - name: NurNebenzeit   type: BOOL 
    - name: PreisProEinheit   type: STRING 
    - name: Tarif   type: Tarif 
The data source for the [Tarif] select control should be loaded from the relative URL: 
    "/TarifService/tarif"   (HTTP-GET) 
An existing Tarifkomponente entity should be loaded from the relative URL: 
    "/TarifService/tarifkomponente/{id}"   (HTTP-GET) 
If a new Tarifkomponente entity has been created, the new entity should be posted to the relative URL: 
    "/TarifService/tarifkomponente"   (HTTP-POST) 
If an existing Tarifkomponente entity has been updated, the modified entity should be sent to the relative URL: 
    "/TarifService/tarifkomponente/{id}"   (HTTP-PUT) 
If an existing Tarifkomponente entity has to be deleted, the following relative URL should be called: 
    "/TarifService/tarifkomponente/{id}"   (HTTP-DELETE)

4. The ZugangsmittelView must contain the following fields: 
    - name: AusgestelltAm   type: DATE 
    - name: EntzogenAm   type: DATE 
    - name: Kennung   type: STRING 
    - name: Mitgliedschaft   type: Mitgliedschaft 
    - name: Typ   type: STRING 
The data source for the [Mitgliedschaft] select control should be loaded from the relative URL: 
    "/StationService/mitgliedschaft"   (HTTP-GET) 
An existing Zugangsmittel entity should be loaded from the relative URL: 
    "/TarifService/zugangsmittel/{id}"   (HTTP-GET) 
If a new Zugangsmittel entity has been created, the new entity should be posted to the relative URL: 
    "/TarifService/zugangsmittel"   (HTTP-POST) 
If an existing Zugangsmittel entity has been updated, the modified entity should be sent to the relative URL: 
    "/TarifService/zugangsmittel/{id}"   (HTTP-PUT) 
If an existing Zugangsmittel entity has to be deleted, the following relative URL should be called: 
    "/TarifService/zugangsmittel/{id}"   (HTTP-DELETE)