Prompt for the OrtApp

Please create a React-JS application for the OrtModule. The application  has to offer the following views for the user interface: 
    1. BrueckeFunktionskategorieView 
    2. DecksystemView 
    3. FunktionskategorieView 
    4. OrtView 
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 BrueckeFunktionskategorieView must contain the following fields: 
    - name: Bruecke   type: Bruecke 
    - name: Funktionskategorie   type: Funktionskategorie 
The data source for the [Funktionskategorie] select control should be loaded from the relative URL: 
    "/OrtService/funktionskategorie"   (HTTP-GET) 
The data source for the [Bruecke] select control should be loaded from the relative URL: 
    "/BrueckeService/bruecke"   (HTTP-GET) 
An existing BrueckeFunktionskategorie entity should be loaded from the relative URL: 
    "/OrtService/brueckefunktionskategorie/{id}"   (HTTP-GET) 
If a new BrueckeFunktionskategorie entity has been created, the new entity should be posted to the relative URL: 
    "/OrtService/brueckefunktionskategorie"   (HTTP-POST) 
If an existing BrueckeFunktionskategorie entity has been updated, the modified entity should be sent to the relative URL: 
    "/OrtService/brueckefunktionskategorie/{id}"   (HTTP-PUT) 
If an existing BrueckeFunktionskategorie entity has to be deleted, the following relative URL should be called: 
    "/OrtService/brueckefunktionskategorie/{id}"   (HTTP-DELETE)

2. The DecksystemView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Name   type: STRING 
An existing Decksystem entity should be loaded from the relative URL: 
    "/OrtService/decksystem/{id}"   (HTTP-GET) 
If a new Decksystem entity has been created, the new entity should be posted to the relative URL: 
    "/OrtService/decksystem"   (HTTP-POST) 
If an existing Decksystem entity has been updated, the modified entity should be sent to the relative URL: 
    "/OrtService/decksystem/{id}"   (HTTP-PUT) 
If an existing Decksystem entity has to be deleted, the following relative URL should be called: 
    "/OrtService/decksystem/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following BrueckenBauteil columns: 
    - column: Gruendungstyp 
    - column: Lagertyp 
    - column: Fahrbahnuebergangstyp 
    - column: Schutzsystem 
    - column: Bauteiltyp 
    - column: Beschreibung 
    - column: Gelaendersystem 
    - column: Bruecke 
    - column: Material 
    - column: Decksystem 
The table should have the title "BrueckenBauteils" und the data must be loaded from the server with the following relative URL: 
    "/MaterialService/brueckenbauteil/decksystem/{id}"

3. The FunktionskategorieView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Name   type: STRING 
An existing Funktionskategorie entity should be loaded from the relative URL: 
    "/OrtService/funktionskategorie/{id}"   (HTTP-GET) 
If a new Funktionskategorie entity has been created, the new entity should be posted to the relative URL: 
    "/OrtService/funktionskategorie"   (HTTP-POST) 
If an existing Funktionskategorie entity has been updated, the modified entity should be sent to the relative URL: 
    "/OrtService/funktionskategorie/{id}"   (HTTP-PUT) 
If an existing Funktionskategorie entity has to be deleted, the following relative URL should be called: 
    "/OrtService/funktionskategorie/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following BrueckeFunktionskategorie columns: 
    - column: Bruecke 
    - column: Funktionskategorie 
The table should have the title "BrueckeFunktionskategories" und the data must be loaded from the server with the following relative URL: 
    "/OrtService/brueckefunktionskategorie/funktionskategorie/{id}"

4. The OrtView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Breitengrad   type: STRING 
    - name: Laengengrad   type: STRING 
    - name: Land   type: STRING 
    - name: Name   type: STRING 
    - name: Region   type: STRING 
    - name: Stadt   type: STRING 
An existing Ort entity should be loaded from the relative URL: 
    "/OrtService/ort/{id}"   (HTTP-GET) 
If a new Ort entity has been created, the new entity should be posted to the relative URL: 
    "/OrtService/ort"   (HTTP-POST) 
If an existing Ort entity has been updated, the modified entity should be sent to the relative URL: 
    "/OrtService/ort/{id}"   (HTTP-PUT) 
If an existing Ort entity has to be deleted, the following relative URL should be called: 
    "/OrtService/ort/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Bruecke columns: 
    - column: BreiteMeter 
    - column: Name 
    - column: Eroeffnung 
    - column: Beschreibung 
    - column: LaengeMeter 
    - column: Baujahr 
    - column: Tragwerkssystem 
    - column: Wasserlauf 
    - column: BeweglichesBrueckensystem 
    - column: Material 
    - column: HauptspannweiteMeter 
    - column: IstBeweglich 
    - column: AnzahlFelder 
    - column: LichtraumhoeheMeter 
    - column: Ort 
The table should have the title "Brueckes" und the data must be loaded from the server with the following relative URL: 
    "/BrueckeService/bruecke/ort/{id}"