Prompt for the BookingApp

Please create a React-JS application for the BookingModule. The application  has to offer the following views for the user interface: 
    1. BookingView 
    2. PaymentView 
    3. PriceCategoryView 
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 BookingView must contain the following fields: 
    - name: BookingDate   type: DATE 
    - name: BookingNumber   type: STRING 
    - name: Currency   type: STRING 
    - name: Customer   type: Customer 
    - name: Status   type: STRING 
    - name: TotalAmount   type: STRING 
The data source for the [Customer] select control should be loaded from the relative URL: 
    "/CustomerService/customer"   (HTTP-GET) 
An existing Booking entity should be loaded from the relative URL: 
    "/BookingService/booking/{id}"   (HTTP-GET) 
If a new Booking entity has been created, the new entity should be posted to the relative URL: 
    "/BookingService/booking"   (HTTP-POST) 
If an existing Booking entity has been updated, the modified entity should be sent to the relative URL: 
    "/BookingService/booking/{id}"   (HTTP-PUT) 
If an existing Booking entity has to be deleted, the following relative URL should be called: 
    "/BookingService/booking/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Payment columns: 
    - column: Currency 
    - column: TransactionReference 
    - column: Booking 
    - column: Amount 
    - column: PaymentStatus 
    - column: CreatedAt 
    - column: PaymentMethod 
The table should have the title "Payments" und the data must be loaded from the server with the following relative URL: 
    "/BookingService/payment/booking/{id}" 
Add a HTML table to the view with the following BookingItem columns: 
    - column: Quantity 
    - column: Booking 
    - column: EventTicketType 
    - column: UnitPrice 
    - column: Event 
    - column: Seat 
    - column: TotalPrice 
The table should have the title "BookingItems" und the data must be loaded from the server with the following relative URL: 
    "/SeatService/bookingitem/booking/{id}"

2. The PaymentView must contain the following fields: 
    - name: Amount   type: STRING 
    - name: Booking   type: Booking 
    - name: CreatedAt   type: DATE 
    - name: Currency   type: STRING 
    - name: PaymentMethod   type: STRING 
    - name: PaymentStatus   type: STRING 
    - name: TransactionReference   type: STRING 
The data source for the [Booking] select control should be loaded from the relative URL: 
    "/BookingService/booking"   (HTTP-GET) 
An existing Payment entity should be loaded from the relative URL: 
    "/BookingService/payment/{id}"   (HTTP-GET) 
If a new Payment entity has been created, the new entity should be posted to the relative URL: 
    "/BookingService/payment"   (HTTP-POST) 
If an existing Payment entity has been updated, the modified entity should be sent to the relative URL: 
    "/BookingService/payment/{id}"   (HTTP-PUT) 
If an existing Payment entity has to be deleted, the following relative URL should be called: 
    "/BookingService/payment/{id}"   (HTTP-DELETE)

3. The PriceCategoryView must contain the following fields: 
    - name: Code   type: STRING 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
An existing PriceCategory entity should be loaded from the relative URL: 
    "/BookingService/pricecategory/{id}"   (HTTP-GET) 
If a new PriceCategory entity has been created, the new entity should be posted to the relative URL: 
    "/BookingService/pricecategory"   (HTTP-POST) 
If an existing PriceCategory entity has been updated, the modified entity should be sent to the relative URL: 
    "/BookingService/pricecategory/{id}"   (HTTP-PUT) 
If an existing PriceCategory entity has to be deleted, the following relative URL should be called: 
    "/BookingService/pricecategory/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following EventTicketType columns: 
    - column: Event 
    - column: BasePrice 
    - column: IsActive 
    - column: SoldQuantity 
    - column: VenueArea 
    - column: TicketType 
    - column: TotalAllocation 
    - column: PriceCategory 
    - column: SeatBlock 
The table should have the title "EventTicketTypes" und the data must be loaded from the server with the following relative URL: 
    "/VenueAreaService/eventtickettype/pricecategory/{id}"