Prompt for the CurrencyApp

Please create a React-JS application for the CurrencyModule. The application  has to offer the following views for the user interface: 
    1. CurrencyView 
    2. FlightBookingView 
    3. PaymentView 
    4. RoomRatePlanPriceView 
    5. StayBookingPriceBreakdownView 
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 CurrencyView must contain the following fields: 
    - name: Code   type: STRING 
    - name: IsActive   type: BOOL 
    - name: Name   type: STRING 
    - name: Symbol   type: STRING 
An existing Currency entity should be loaded from the relative URL: 
    "/CurrencyService/currency/{id}"   (HTTP-GET) 
If a new Currency entity has been created, the new entity should be posted to the relative URL: 
    "/CurrencyService/currency"   (HTTP-POST) 
If an existing Currency entity has been updated, the modified entity should be sent to the relative URL: 
    "/CurrencyService/currency/{id}"   (HTTP-PUT) 
If an existing Currency entity has to be deleted, the following relative URL should be called: 
    "/CurrencyService/currency/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following StayBookingPriceBreakdown columns: 
    - column: StayBooking 
    - column: Amount 
    - column: Description 
    - column: Currency 
    - column: Date 
    - column: LineType 
The table should have the title "StayBookingPriceBreakdowns" und the data must be loaded from the server with the following relative URL: 
    "/CurrencyService/staybookingpricebreakdown/currency/{id}" 
Add a HTML table to the view with the following StayBooking columns: 
    - column: Booking 
    - column: CheckOutDate 
    - column: RoomType 
    - column: Adults 
    - column: Children 
    - column: SpecialRequests 
    - column: NumberOfRooms 
    - column: RoomRatePlan 
    - column: CheckInDate 
    - column: BaseAmount 
    - column: Currency 
    - column: CancellationPolicySnapshot 
    - column: TaxesAmount 
    - column: Property 
    - column: FeesAmount 
The table should have the title "StayBookings" und the data must be loaded from the server with the following relative URL: 
    "/StayBookingService/staybooking/currency/{id}" 
Add a HTML table to the view with the following RoomRatePlanPrice columns: 
    - column: DateFrom 
    - column: Currency 
    - column: TaxesIncluded 
    - column: FeesIncluded 
    - column: PricePerNight 
    - column: RoomRatePlan 
    - column: DateTo 
The table should have the title "RoomRatePlanPrices" und the data must be loaded from the server with the following relative URL: 
    "/CurrencyService/roomrateplanprice/currency/{id}" 
Add a HTML table to the view with the following CarRentalBooking columns: 
    - column: TotalAmount 
    - column: CarRentalProduct 
    - column: DropoffLocation 
    - column: DropoffDateTime 
    - column: Booking 
    - column: PickupLocation 
    - column: Currency 
    - column: PickupDateTime 
The table should have the title "CarRentalBookings" und the data must be loaded from the server with the following relative URL: 
    "/CarRentalLocationService/carrentalbooking/currency/{id}" 
Add a HTML table to the view with the following FlightBooking columns: 
    - column: Booking 
    - column: Currency 
    - column: TotalAmount 
    - column: CabinClass 
    - column: PnrCode 
The table should have the title "FlightBookings" und the data must be loaded from the server with the following relative URL: 
    "/CurrencyService/flightbooking/currency/{id}" 
Add a HTML table to the view with the following Payment columns: 
    - column: Currency 
    - column: Booking 
    - column: Status 
    - column: ProviderReference 
    - column: Amount 
    - column: ProcessedAt 
    - 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: 
    "/CurrencyService/payment/currency/{id}" 
Add a HTML table to the view with the following AirportTransferBooking columns: 
    - column: PickupAddress 
    - column: Booking 
    - column: PickupDateTime 
    - column: Passengers 
    - column: DropoffAddress 
    - column: AirportTransferProduct 
    - column: TotalAmount 
    - column: Currency 
The table should have the title "AirportTransferBookings" und the data must be loaded from the server with the following relative URL: 
    "/BookingService/airporttransferbooking/currency/{id}" 
Add a HTML table to the view with the following AttractionBooking columns: 
    - column: TotalAmount 
    - column: Children 
    - column: Currency 
    - column: AttractionSchedule 
    - column: Booking 
    - column: Adults 
The table should have the title "AttractionBookings" und the data must be loaded from the server with the following relative URL: 
    "/AttractionBookingService/attractionbooking/currency/{id}" 
Add a HTML table to the view with the following TravelCreditTransaction columns: 
    - column: UserAccount 
    - column: Amount 
    - column: CreatedAt 
    - column: Booking 
    - column: Description 
    - column: Currency 
    - column: Type 
The table should have the title "TravelCreditTransactions" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/travelcredittransaction/currency/{id}" 
Add a HTML table to the view with the following Booking columns: 
    - column: Channel 
    - column: UserAccount 
    - column: Currency 
    - column: UpdatedAt 
    - column: Status 
    - column: TotalAmount 
    - column: DisplayAmount 
    - column: CreatedAt 
The table should have the title "Bookings" und the data must be loaded from the server with the following relative URL: 
    "/BookingService/booking/currency/{id}" 
Add a HTML table to the view with the following UserAccount columns: 
    - column: DefaultCurrency 
    - column: Email 
    - column: CreatedAt 
    - column: PhoneNumber 
    - column: DefaultLanguage 
    - column: PasswordHash 
    - column: IsActive 
    - column: FullName 
The table should have the title "UserAccounts" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/useraccount/defaultcurrency/{id}"

2. The FlightBookingView must contain the following fields: 
    - name: Booking   type: Booking 
    - name: CabinClass   type: STRING 
    - name: Currency   type: Currency 
    - name: PnrCode   type: STRING 
    - name: TotalAmount   type: STRING 
The data source for the [Currency] select control should be loaded from the relative URL: 
    "/CurrencyService/currency"   (HTTP-GET) 
The data source for the [Booking] select control should be loaded from the relative URL: 
    "/BookingService/booking"   (HTTP-GET) 
An existing FlightBooking entity should be loaded from the relative URL: 
    "/CurrencyService/flightbooking/{id}"   (HTTP-GET) 
If a new FlightBooking entity has been created, the new entity should be posted to the relative URL: 
    "/CurrencyService/flightbooking"   (HTTP-POST) 
If an existing FlightBooking entity has been updated, the modified entity should be sent to the relative URL: 
    "/CurrencyService/flightbooking/{id}"   (HTTP-PUT) 
If an existing FlightBooking entity has to be deleted, the following relative URL should be called: 
    "/CurrencyService/flightbooking/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following FlightPassenger columns: 
    - column: NationalityCountry 
    - column: PassengerType 
    - column: DocumentNumber 
    - column: FullName 
    - column: FlightBooking 
    - column: DateOfBirth 
The table should have the title "FlightPassengers" und the data must be loaded from the server with the following relative URL: 
    "/LocationCityService/flightpassenger/flightbooking/{id}" 
Add a HTML table to the view with the following FlightBookingSegment columns: 
    - column: Status 
    - column: Flight 
    - column: FlightBooking 
    - column: Seat 
    - column: SegmentNumber 
The table should have the title "FlightBookingSegments" und the data must be loaded from the server with the following relative URL: 
    "/AirportService/flightbookingsegment/flightbooking/{id}"

3. The PaymentView must contain the following fields: 
    - name: Amount   type: STRING 
    - name: Booking   type: Booking 
    - name: CreatedAt   type: DATE 
    - name: Currency   type: Currency 
    - name: PaymentMethod   type: PaymentMethod 
    - name: ProcessedAt   type: DATE 
    - name: ProviderReference   type: STRING 
    - name: Status   type: STRING 
The data source for the [Currency] select control should be loaded from the relative URL: 
    "/CurrencyService/currency"   (HTTP-GET) 
The data source for the [PaymentMethod] select control should be loaded from the relative URL: 
    "/UserAccountService/paymentmethod"   (HTTP-GET) 
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: 
    "/CurrencyService/payment/{id}"   (HTTP-GET) 
If a new Payment entity has been created, the new entity should be posted to the relative URL: 
    "/CurrencyService/payment"   (HTTP-POST) 
If an existing Payment entity has been updated, the modified entity should be sent to the relative URL: 
    "/CurrencyService/payment/{id}"   (HTTP-PUT) 
If an existing Payment entity has to be deleted, the following relative URL should be called: 
    "/CurrencyService/payment/{id}"   (HTTP-DELETE)

4. The RoomRatePlanPriceView must contain the following fields: 
    - name: Currency   type: Currency 
    - name: DateFrom   type: DATE 
    - name: DateTo   type: DATE 
    - name: FeesIncluded   type: BOOL 
    - name: PricePerNight   type: STRING 
    - name: RoomRatePlan   type: RoomRatePlan 
    - name: TaxesIncluded   type: BOOL 
The data source for the [RoomRatePlan] select control should be loaded from the relative URL: 
    "/StayBookingService/roomrateplan"   (HTTP-GET) 
The data source for the [Currency] select control should be loaded from the relative URL: 
    "/CurrencyService/currency"   (HTTP-GET) 
An existing RoomRatePlanPrice entity should be loaded from the relative URL: 
    "/CurrencyService/roomrateplanprice/{id}"   (HTTP-GET) 
If a new RoomRatePlanPrice entity has been created, the new entity should be posted to the relative URL: 
    "/CurrencyService/roomrateplanprice"   (HTTP-POST) 
If an existing RoomRatePlanPrice entity has been updated, the modified entity should be sent to the relative URL: 
    "/CurrencyService/roomrateplanprice/{id}"   (HTTP-PUT) 
If an existing RoomRatePlanPrice entity has to be deleted, the following relative URL should be called: 
    "/CurrencyService/roomrateplanprice/{id}"   (HTTP-DELETE)

5. The StayBookingPriceBreakdownView must contain the following fields: 
    - name: Amount   type: STRING 
    - name: Currency   type: Currency 
    - name: Date   type: DATE 
    - name: Description   type: STRING 
    - name: LineType   type: STRING 
    - name: StayBooking   type: StayBooking 
The data source for the [Currency] select control should be loaded from the relative URL: 
    "/CurrencyService/currency"   (HTTP-GET) 
The data source for the [StayBooking] select control should be loaded from the relative URL: 
    "/StayBookingService/staybooking"   (HTTP-GET) 
An existing StayBookingPriceBreakdown entity should be loaded from the relative URL: 
    "/CurrencyService/staybookingpricebreakdown/{id}"   (HTTP-GET) 
If a new StayBookingPriceBreakdown entity has been created, the new entity should be posted to the relative URL: 
    "/CurrencyService/staybookingpricebreakdown"   (HTTP-POST) 
If an existing StayBookingPriceBreakdown entity has been updated, the modified entity should be sent to the relative URL: 
    "/CurrencyService/staybookingpricebreakdown/{id}"   (HTTP-PUT) 
If an existing StayBookingPriceBreakdown entity has to be deleted, the following relative URL should be called: 
    "/CurrencyService/staybookingpricebreakdown/{id}"   (HTTP-DELETE)