Prompt for the FitnessStudioApp

Please create a React-JS application for the FitnessStudioModule. The application  has to offer the following views for the user interface: 
    1. FitnessStudioView 
    2. KursView 
    3. KursEinheitView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 3 views are defined below.

1. The FitnessStudioView must contain the following fields: 
    - name: FitnessKette   type: FitnessKette 
    - name: FranchiseSystem   type: FranchiseSystem 
    - name: GroesseQuadratmeter   type: INT 
    - name: Ist24StundenGeoeffnet   type: BOOL 
    - name: IstMikrostudio   type: BOOL 
    - name: Land   type: STRING 
    - name: Name   type: STRING 
    - name: Oeffnungszeiten   type: STRING 
    - name: Postleitzahl   type: STRING 
    - name: SportVerein   type: SportVerein 
    - name: Stadt   type: STRING 
    - name: Strasse   type: STRING 
    - name: StudioTyp   type: STRING 
The data source for the [FitnessKette] select control should be loaded from the relative URL: 
    "/MitgliedschaftsVertragService/fitnesskette"   (HTTP-GET) 
The data source for the [SportVerein] select control should be loaded from the relative URL: 
    "/GeraeteTypService/sportverein"   (HTTP-GET) 
The data source for the [FranchiseSystem] select control should be loaded from the relative URL: 
    "/TrainerService/franchisesystem"   (HTTP-GET) 
An existing FitnessStudio entity should be loaded from the relative URL: 
    "/FitnessStudioService/fitnessstudio/{id}"   (HTTP-GET) 
If a new FitnessStudio entity has been created, the new entity should be posted to the relative URL: 
    "/FitnessStudioService/fitnessstudio"   (HTTP-POST) 
If an existing FitnessStudio entity has been updated, the modified entity should be sent to the relative URL: 
    "/FitnessStudioService/fitnessstudio/{id}"   (HTTP-PUT) 
If an existing FitnessStudio entity has to be deleted, the following relative URL should be called: 
    "/FitnessStudioService/fitnessstudio/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following MitgliedschaftsVertrag columns: 
    - column: Mitglied 
    - column: VertragsStatus 
    - column: StartDatum 
    - column: FitnessStudio 
    - column: ZahlungsMethode 
    - column: UnterzeichnetAm 
    - column: MitgliedschaftsTyp 
    - column: KuendigungsDatum 
    - column: EndDatum 
The table should have the title "MitgliedschaftsVertrags" und the data must be loaded from the server with the following relative URL: 
    "/MitgliedschaftsVertragService/mitgliedschaftsvertrag/fitnessstudio/{id}" 
Add a HTML table to the view with the following Mitarbeiter columns: 
    - column: Email 
    - column: Telefon 
    - column: FitnessStudio 
    - column: IstExtern 
    - column: Nachname 
    - column: Vorname 
    - column: Rolle 
The table should have the title "Mitarbeiters" und the data must be loaded from the server with the following relative URL: 
    "/MitarbeiterService/mitarbeiter/fitnessstudio/{id}" 
Add a HTML table to the view with the following Zahlung columns: 
    - column: ZeitraumStart 
    - column: IstErfolgreich 
    - column: ZahlungsDatum 
    - column: MitgliedschaftsVertrag 
    - column: Mitglied 
    - column: Betrag 
    - column: ZeitraumEnde 
    - column: ExterneReferenz 
    - column: Waehrung 
    - column: ZahlungsTyp 
    - column: FitnessStudio 
The table should have the title "Zahlungs" und the data must be loaded from the server with the following relative URL: 
    "/MitgliedService/zahlung/fitnessstudio/{id}" 
Add a HTML table to the view with the following ServiceTermin columns: 
    - column: Mitarbeiter 
    - column: Notizen 
    - column: StartZeit 
    - column: Status 
    - column: FitnessStudio 
    - column: ServiceTyp 
    - column: Mitglied 
    - column: EndZeit 
The table should have the title "ServiceTermins" und the data must be loaded from the server with the following relative URL: 
    "/MitarbeiterService/servicetermin/fitnessstudio/{id}" 
Add a HTML table to the view with the following Trainer columns: 
    - column: Email 
    - column: FitnessStudio 
    - column: Telefon 
    - column: Vorname 
    - column: BeschaeftigungsArt 
    - column: EinstellungsDatum 
    - column: Nachname 
    - column: IstFreiberufler 
The table should have the title "Trainers" und the data must be loaded from the server with the following relative URL: 
    "/TrainerService/trainer/fitnessstudio/{id}" 
Add a HTML table to the view with the following Kurs columns: 
    - column: Raum 
    - column: KursTyp 
    - column: Trainer 
    - column: IstAktiv 
    - column: IstNurFrauen 
    - column: FitnessStudio 
    - column: MaxTeilnehmer 
The table should have the title "Kurss" und the data must be loaded from the server with the following relative URL: 
    "/FitnessStudioService/kurs/fitnessstudio/{id}" 
Add a HTML table to the view with the following Mitglied columns: 
    - column: Email 
    - column: Geschlecht 
    - column: HeimStudio 
    - column: Registrierungsdatum 
    - column: Stadt 
    - column: Nachname 
    - column: Vorname 
    - column: Status 
    - column: Geburtsdatum 
    - column: Postleitzahl 
    - column: Strasse 
    - column: Telefon 
    - column: Land 
The table should have the title "Mitglieds" und the data must be loaded from the server with the following relative URL: 
    "/MitgliedService/mitglied/heimstudio/{id}" 
Add a HTML table to the view with the following Geraet columns: 
    - column: StandortBeschreibung 
    - column: SerienNummer 
    - column: KaufDatum 
    - column: FitnessStudio 
    - column: GeraeteTyp 
    - column: IstAktiv 
The table should have the title "Geraets" und the data must be loaded from the server with the following relative URL: 
    "/GeraeteTypService/geraet/fitnessstudio/{id}" 
Add a HTML table to the view with the following Bereich columns: 
    - column: FitnessStudio 
    - column: BereichsTyp 
    - column: Name 
The table should have the title "Bereichs" und the data must be loaded from the server with the following relative URL: 
    "/MitgliedService/bereich/fitnessstudio/{id}"

2. The KursView must contain the following fields: 
    - name: FitnessStudio   type: FitnessStudio 
    - name: IstAktiv   type: BOOL 
    - name: IstNurFrauen   type: BOOL 
    - name: KursTyp   type: KursTyp 
    - name: MaxTeilnehmer   type: INT 
    - name: Raum   type: STRING 
    - name: Trainer   type: Trainer 
The data source for the [FitnessStudio] select control should be loaded from the relative URL: 
    "/FitnessStudioService/fitnessstudio"   (HTTP-GET) 
The data source for the [KursTyp] select control should be loaded from the relative URL: 
    "/MitgliedschaftsVertragService/kurstyp"   (HTTP-GET) 
The data source for the [Trainer] select control should be loaded from the relative URL: 
    "/TrainerService/trainer"   (HTTP-GET) 
An existing Kurs entity should be loaded from the relative URL: 
    "/FitnessStudioService/kurs/{id}"   (HTTP-GET) 
If a new Kurs entity has been created, the new entity should be posted to the relative URL: 
    "/FitnessStudioService/kurs"   (HTTP-POST) 
If an existing Kurs entity has been updated, the modified entity should be sent to the relative URL: 
    "/FitnessStudioService/kurs/{id}"   (HTTP-PUT) 
If an existing Kurs entity has to be deleted, the following relative URL should be called: 
    "/FitnessStudioService/kurs/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following KursEinheit columns: 
    - column: Status 
    - column: Kurs 
    - column: StartZeit 
    - column: EndZeit 
    - column: StornoGrund 
The table should have the title "KursEinheits" und the data must be loaded from the server with the following relative URL: 
    "/FitnessStudioService/kurseinheit/kurs/{id}"

3. The KursEinheitView must contain the following fields: 
    - name: EndZeit   type: DATE 
    - name: Kurs   type: Kurs 
    - name: StartZeit   type: DATE 
    - name: Status   type: STRING 
    - name: StornoGrund   type: STRING 
The data source for the [Kurs] select control should be loaded from the relative URL: 
    "/FitnessStudioService/kurs"   (HTTP-GET) 
An existing KursEinheit entity should be loaded from the relative URL: 
    "/FitnessStudioService/kurseinheit/{id}"   (HTTP-GET) 
If a new KursEinheit entity has been created, the new entity should be posted to the relative URL: 
    "/FitnessStudioService/kurseinheit"   (HTTP-POST) 
If an existing KursEinheit entity has been updated, the modified entity should be sent to the relative URL: 
    "/FitnessStudioService/kurseinheit/{id}"   (HTTP-PUT) 
If an existing KursEinheit entity has to be deleted, the following relative URL should be called: 
    "/FitnessStudioService/kurseinheit/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following KursBuchung columns: 
    - column: KursEinheit 
    - column: Mitglied 
    - column: Status 
    - column: CheckInZeit 
    - column: BuchungsZeit 
The table should have the title "KursBuchungs" und the data must be loaded from the server with the following relative URL: 
    "/MitgliedService/kursbuchung/kurseinheit/{id}"