Prompt for the BuchungApp

Please create a React-JS application for the BuchungModule. The application  has to offer the following views for the user interface: 
    1. BuchungView 
    2. GastView 
    3. PreisView 
    4. TrendView 
    5. ZahlungView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 5 views are defined below.

1. The BuchungView must contain the following fields: 
    - name: BeginnDatum   type: DATE 
    - name: BuchungsDatum   type: DATE 
    - name: EndeDatum   type: DATE 
    - name: Gast   type: Gast 
    - name: Gesamtpreis   type: STRING 
    - name: Status   type: STRING 
    - name: Unterkunft   type: Unterkunft 
    - name: Vermittler   type: Vermittler 
The data source for the [Unterkunft] select control should be loaded from the relative URL: 
    "/UnterkunftService/unterkunft"   (HTTP-GET) 
The data source for the [Vermittler] select control should be loaded from the relative URL: 
    "/VermittlerService/vermittler"   (HTTP-GET) 
The data source for the [Gast] select control should be loaded from the relative URL: 
    "/BuchungService/gast"   (HTTP-GET) 
An existing Buchung entity should be loaded from the relative URL: 
    "/BuchungService/buchung/{id}"   (HTTP-GET) 
If a new Buchung entity has been created, the new entity should be posted to the relative URL: 
    "/BuchungService/buchung"   (HTTP-POST) 
If an existing Buchung entity has been updated, the modified entity should be sent to the relative URL: 
    "/BuchungService/buchung/{id}"   (HTTP-PUT) 
If an existing Buchung entity has to be deleted, the following relative URL should be called: 
    "/BuchungService/buchung/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Zahlung columns: 
    - column: Status 
    - column: Methode 
    - column: ZahlungsDatum 
    - column: Buchung 
    - column: Betrag 
The table should have the title "Zahlungs" und the data must be loaded from the server with the following relative URL: 
    "/BuchungService/zahlung/buchung/{id}"

2. The GastView must contain the following fields: 
    - name: Adresse   type: STRING 
    - name: Email   type: STRING 
    - name: Nachname   type: STRING 
    - name: Telefon   type: STRING 
    - name: Vorname   type: STRING 
An existing Gast entity should be loaded from the relative URL: 
    "/BuchungService/gast/{id}"   (HTTP-GET) 
If a new Gast entity has been created, the new entity should be posted to the relative URL: 
    "/BuchungService/gast"   (HTTP-POST) 
If an existing Gast entity has been updated, the modified entity should be sent to the relative URL: 
    "/BuchungService/gast/{id}"   (HTTP-PUT) 
If an existing Gast entity has to be deleted, the following relative URL should be called: 
    "/BuchungService/gast/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Buchung columns: 
    - column: BuchungsDatum 
    - column: Status 
    - column: Unterkunft 
    - column: Vermittler 
    - column: Gesamtpreis 
    - column: EndeDatum 
    - column: BeginnDatum 
    - column: Gast 
The table should have the title "Buchungs" und the data must be loaded from the server with the following relative URL: 
    "/BuchungService/buchung/gast/{id}"

3. The PreisView must contain the following fields: 
    - name: GueltigAb   type: DATE 
    - name: GueltigBis   type: DATE 
    - name: InklusiveEndreinigung   type: BOOL 
    - name: InklusiveStrom   type: BOOL 
    - name: PreisProNacht   type: STRING 
    - name: PreisProPerson   type: STRING 
    - name: PreisProWoche   type: STRING 
    - name: Unterkunft   type: Unterkunft 
The data source for the [Unterkunft] select control should be loaded from the relative URL: 
    "/UnterkunftService/unterkunft"   (HTTP-GET) 
An existing Preis entity should be loaded from the relative URL: 
    "/BuchungService/preis/{id}"   (HTTP-GET) 
If a new Preis entity has been created, the new entity should be posted to the relative URL: 
    "/BuchungService/preis"   (HTTP-POST) 
If an existing Preis entity has been updated, the modified entity should be sent to the relative URL: 
    "/BuchungService/preis/{id}"   (HTTP-PUT) 
If an existing Preis entity has to be deleted, the following relative URL should be called: 
    "/BuchungService/preis/{id}"   (HTTP-DELETE)

4. The TrendView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Jahr   type: LONG 
    - name: Quelle   type: STRING 
    - name: Thema   type: STRING 
An existing Trend entity should be loaded from the relative URL: 
    "/BuchungService/trend/{id}"   (HTTP-GET) 
If a new Trend entity has been created, the new entity should be posted to the relative URL: 
    "/BuchungService/trend"   (HTTP-POST) 
If an existing Trend entity has been updated, the modified entity should be sent to the relative URL: 
    "/BuchungService/trend/{id}"   (HTTP-PUT) 
If an existing Trend entity has to be deleted, the following relative URL should be called: 
    "/BuchungService/trend/{id}"   (HTTP-DELETE)

5. The ZahlungView must contain the following fields: 
    - name: Betrag   type: STRING 
    - name: Buchung   type: Buchung 
    - name: Methode   type: STRING 
    - name: Status   type: STRING 
    - name: ZahlungsDatum   type: DATE 
The data source for the [Buchung] select control should be loaded from the relative URL: 
    "/BuchungService/buchung"   (HTTP-GET) 
An existing Zahlung entity should be loaded from the relative URL: 
    "/BuchungService/zahlung/{id}"   (HTTP-GET) 
If a new Zahlung entity has been created, the new entity should be posted to the relative URL: 
    "/BuchungService/zahlung"   (HTTP-POST) 
If an existing Zahlung entity has been updated, the modified entity should be sent to the relative URL: 
    "/BuchungService/zahlung/{id}"   (HTTP-PUT) 
If an existing Zahlung entity has to be deleted, the following relative URL should be called: 
    "/BuchungService/zahlung/{id}"   (HTTP-DELETE)