Prompt for the SubscriptionPlanApp

Please create a React-JS application for the SubscriptionPlanModule. The application  has to offer the following views for the user interface: 
    1. PortCallView 
    2. RouteWaypointView 
    3. SubscriptionPlanView 
    4. UserSubscriptionView 
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 PortCallView must contain the following fields: 
    - name: ArrivalActualUtc   type: DATE 
    - name: ArrivalEstimatedUtc   type: DATE 
    - name: BerthName   type: STRING 
    - name: DepartureActualUtc   type: DATE 
    - name: DepartureEstimatedUtc   type: DATE 
    - name: DraftArrival   type: STRING 
    - name: DraftDeparture   type: STRING 
    - name: Port   type: Port 
    - name: Reason   type: STRING 
    - name: Route   type: Route 
    - name: Vessel   type: Vessel 
The data source for the [Vessel] select control should be loaded from the relative URL: 
    "/VesselService/vessel"   (HTTP-GET) 
The data source for the [Port] select control should be loaded from the relative URL: 
    "/PortService/port"   (HTTP-GET) 
The data source for the [Route] select control should be loaded from the relative URL: 
    "/PortService/route"   (HTTP-GET) 
An existing PortCall entity should be loaded from the relative URL: 
    "/SubscriptionPlanService/portcall/{id}"   (HTTP-GET) 
If a new PortCall entity has been created, the new entity should be posted to the relative URL: 
    "/SubscriptionPlanService/portcall"   (HTTP-POST) 
If an existing PortCall entity has been updated, the modified entity should be sent to the relative URL: 
    "/SubscriptionPlanService/portcall/{id}"   (HTTP-PUT) 
If an existing PortCall entity has to be deleted, the following relative URL should be called: 
    "/SubscriptionPlanService/portcall/{id}"   (HTTP-DELETE)

2. The RouteWaypointView must contain the following fields: 
    - name: EstimatedTimeUtc   type: DATE 
    - name: Latitude   type: STRING 
    - name: Longitude   type: STRING 
    - name: Route   type: Route 
    - name: SequenceNumber   type: LONG 
The data source for the [Route] select control should be loaded from the relative URL: 
    "/PortService/route"   (HTTP-GET) 
An existing RouteWaypoint entity should be loaded from the relative URL: 
    "/SubscriptionPlanService/routewaypoint/{id}"   (HTTP-GET) 
If a new RouteWaypoint entity has been created, the new entity should be posted to the relative URL: 
    "/SubscriptionPlanService/routewaypoint"   (HTTP-POST) 
If an existing RouteWaypoint entity has been updated, the modified entity should be sent to the relative URL: 
    "/SubscriptionPlanService/routewaypoint/{id}"   (HTTP-PUT) 
If an existing RouteWaypoint entity has to be deleted, the following relative URL should be called: 
    "/SubscriptionPlanService/routewaypoint/{id}"   (HTTP-DELETE)

3. The SubscriptionPlanView must contain the following fields: 
    - name: BillingPeriod   type: STRING 
    - name: Currency   type: STRING 
    - name: Description   type: STRING 
    - name: HistoricalDataDays   type: LONG 
    - name: HistoricalDataYears   type: LONG 
    - name: IsActive   type: BOOL 
    - name: IsEnterprise   type: BOOL 
    - name: MaxApiCallsPerMonth   type: LONG 
    - name: MaxCustomAreas   type: LONG 
    - name: MaxNotificationsPerMonth   type: LONG 
    - name: MaxTrackedVessels   type: LONG 
    - name: Name   type: STRING 
    - name: PriceAmount   type: STRING 
An existing SubscriptionPlan entity should be loaded from the relative URL: 
    "/SubscriptionPlanService/subscriptionplan/{id}"   (HTTP-GET) 
If a new SubscriptionPlan entity has been created, the new entity should be posted to the relative URL: 
    "/SubscriptionPlanService/subscriptionplan"   (HTTP-POST) 
If an existing SubscriptionPlan entity has been updated, the modified entity should be sent to the relative URL: 
    "/SubscriptionPlanService/subscriptionplan/{id}"   (HTTP-PUT) 
If an existing SubscriptionPlan entity has to be deleted, the following relative URL should be called: 
    "/SubscriptionPlanService/subscriptionplan/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following UserSubscription columns: 
    - column: StartUtc 
    - column: SubscriptionPlan 
    - column: UserAccount 
    - column: IsTrial 
    - column: AutoRenew 
    - column: EndUtc 
The table should have the title "UserSubscriptions" und the data must be loaded from the server with the following relative URL: 
    "/SubscriptionPlanService/usersubscription/subscriptionplan/{id}"

4. The UserSubscriptionView must contain the following fields: 
    - name: AutoRenew   type: BOOL 
    - name: EndUtc   type: DATE 
    - name: IsTrial   type: BOOL 
    - name: StartUtc   type: DATE 
    - name: SubscriptionPlan   type: SubscriptionPlan 
    - name: UserAccount   type: UserAccount 
The data source for the [SubscriptionPlan] select control should be loaded from the relative URL: 
    "/SubscriptionPlanService/subscriptionplan"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing UserSubscription entity should be loaded from the relative URL: 
    "/SubscriptionPlanService/usersubscription/{id}"   (HTTP-GET) 
If a new UserSubscription entity has been created, the new entity should be posted to the relative URL: 
    "/SubscriptionPlanService/usersubscription"   (HTTP-POST) 
If an existing UserSubscription entity has been updated, the modified entity should be sent to the relative URL: 
    "/SubscriptionPlanService/usersubscription/{id}"   (HTTP-PUT) 
If an existing UserSubscription entity has to be deleted, the following relative URL should be called: 
    "/SubscriptionPlanService/usersubscription/{id}"   (HTTP-DELETE)