Prompt for the VenueAreaApp

Please create a React-JS application for the VenueAreaModule. The application  has to offer the following views for the user interface: 
    1. AccessPointView 
    2. SeatView 
    3. SeatBlockView 
    4. VenueAreaView 
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 AccessPointView must contain the following fields: 
    - name: AccessCode   type: STRING 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
    - name: VenueArea   type: VenueArea 
The data source for the [VenueArea] select control should be loaded from the relative URL: 
    "/VenueAreaService/venuearea"   (HTTP-GET) 
An existing AccessPoint entity should be loaded from the relative URL: 
    "/VenueAreaService/accesspoint/{id}"   (HTTP-GET) 
If a new AccessPoint entity has been created, the new entity should be posted to the relative URL: 
    "/VenueAreaService/accesspoint"   (HTTP-POST) 
If an existing AccessPoint entity has been updated, the modified entity should be sent to the relative URL: 
    "/VenueAreaService/accesspoint/{id}"   (HTTP-PUT) 
If an existing AccessPoint entity has to be deleted, the following relative URL should be called: 
    "/VenueAreaService/accesspoint/{id}"   (HTTP-DELETE)

2. The SeatView must contain the following fields: 
    - name: IsStanding   type: BOOL 
    - name: RowLabel   type: STRING 
    - name: SeatBlock   type: SeatBlock 
    - name: SeatNumber   type: STRING 
The data source for the [SeatBlock] select control should be loaded from the relative URL: 
    "/VenueAreaService/seatblock"   (HTTP-GET) 
An existing Seat entity should be loaded from the relative URL: 
    "/VenueAreaService/seat/{id}"   (HTTP-GET) 
If a new Seat entity has been created, the new entity should be posted to the relative URL: 
    "/VenueAreaService/seat"   (HTTP-POST) 
If an existing Seat entity has been updated, the modified entity should be sent to the relative URL: 
    "/VenueAreaService/seat/{id}"   (HTTP-PUT) 
If an existing Seat entity has to be deleted, the following relative URL should be called: 
    "/VenueAreaService/seat/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following BookingItem columns: 
    - column: Quantity 
    - column: Event 
    - column: Seat 
    - column: UnitPrice 
    - column: EventTicketType 
    - column: Booking 
    - column: TotalPrice 
The table should have the title "BookingItems" und the data must be loaded from the server with the following relative URL: 
    "/EventService/bookingitem/seat/{id}"

3. The SeatBlockView must contain the following fields: 
    - name: Capacity   type: LONG 
    - name: Code   type: STRING 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
    - name: VenueArea   type: VenueArea 
The data source for the [VenueArea] select control should be loaded from the relative URL: 
    "/VenueAreaService/venuearea"   (HTTP-GET) 
An existing SeatBlock entity should be loaded from the relative URL: 
    "/VenueAreaService/seatblock/{id}"   (HTTP-GET) 
If a new SeatBlock entity has been created, the new entity should be posted to the relative URL: 
    "/VenueAreaService/seatblock"   (HTTP-POST) 
If an existing SeatBlock entity has been updated, the modified entity should be sent to the relative URL: 
    "/VenueAreaService/seatblock/{id}"   (HTTP-PUT) 
If an existing SeatBlock entity has to be deleted, the following relative URL should be called: 
    "/VenueAreaService/seatblock/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Seat columns: 
    - column: IsStanding 
    - column: SeatBlock 
    - column: RowLabel 
    - column: SeatNumber 
The table should have the title "Seats" und the data must be loaded from the server with the following relative URL: 
    "/VenueAreaService/seat/seatblock/{id}" 
Add a HTML table to the view with the following EventTicketType columns: 
    - column: VenueArea 
    - column: SoldQuantity 
    - column: TicketType 
    - column: SeatBlock 
    - column: IsActive 
    - column: TotalAllocation 
    - column: Event 
    - column: PriceCategory 
    - column: BasePrice 
The table should have the title "EventTicketTypes" und the data must be loaded from the server with the following relative URL: 
    "/PriceCategoryService/eventtickettype/seatblock/{id}"

4. The VenueAreaView must contain the following fields: 
    - name: Arena   type: Arena 
    - name: Capacity   type: LONG 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
    - name: Type   type: STRING 
The data source for the [Arena] select control should be loaded from the relative URL: 
    "/ArenaService/arena"   (HTTP-GET) 
An existing VenueArea entity should be loaded from the relative URL: 
    "/VenueAreaService/venuearea/{id}"   (HTTP-GET) 
If a new VenueArea entity has been created, the new entity should be posted to the relative URL: 
    "/VenueAreaService/venuearea"   (HTTP-POST) 
If an existing VenueArea entity has been updated, the modified entity should be sent to the relative URL: 
    "/VenueAreaService/venuearea/{id}"   (HTTP-PUT) 
If an existing VenueArea entity has to be deleted, the following relative URL should be called: 
    "/VenueAreaService/venuearea/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Event columns: 
    - column: ExternalReference 
    - column: TicketUrl 
    - column: DoorOpenTime 
    - column: StartDateTime 
    - column: Organizer 
    - column: EndDateTime 
    - column: Subtitle 
    - column: VenueArea 
    - column: Language 
    - column: Arena 
    - column: Name 
    - column: Description 
    - column: IsCanceled 
    - column: EventSeries 
    - column: IsPostponed 
    - column: EventCategory 
    - column: MinimumAge 
The table should have the title "Events" und the data must be loaded from the server with the following relative URL: 
    "/EventService/event/venuearea/{id}" 
Add a HTML table to the view with the following SeatBlock columns: 
    - column: Name 
    - column: Code 
    - column: Capacity 
    - column: Description 
    - column: VenueArea 
The table should have the title "SeatBlocks" und the data must be loaded from the server with the following relative URL: 
    "/VenueAreaService/seatblock/venuearea/{id}" 
Add a HTML table to the view with the following GastronomyUnit columns: 
    - column: OpeningHours 
    - column: Description 
    - column: VenueArea 
    - column: Name 
    - column: Type 
The table should have the title "GastronomyUnits" und the data must be loaded from the server with the following relative URL: 
    "/GastronomyUnitService/gastronomyunit/venuearea/{id}" 
Add a HTML table to the view with the following AccessPoint columns: 
    - column: VenueArea 
    - column: AccessCode 
    - column: Name 
    - column: Description 
The table should have the title "AccessPoints" und the data must be loaded from the server with the following relative URL: 
    "/VenueAreaService/accesspoint/venuearea/{id}" 
Add a HTML table to the view with the following EventTicketType columns: 
    - column: VenueArea 
    - column: SoldQuantity 
    - column: TicketType 
    - column: SeatBlock 
    - column: IsActive 
    - column: TotalAllocation 
    - column: Event 
    - column: PriceCategory 
    - column: BasePrice 
The table should have the title "EventTicketTypes" und the data must be loaded from the server with the following relative URL: 
    "/PriceCategoryService/eventtickettype/venuearea/{id}" 
Add a HTML table to the view with the following ConferenceRoom columns: 
    - column: VenueArea 
    - column: Name 
    - column: Description 
    - column: Floor 
    - column: RoomNumber 
    - column: Capacity 
The table should have the title "ConferenceRooms" und the data must be loaded from the server with the following relative URL: 
    "/ConferenceRoomService/conferenceroom/venuearea/{id}"