Prompt for the CompanyApp

Please create a React-JS application for the CompanyModule. The application  has to offer the following views for the user interface: 
    1. AcquisitionView 
    2. CompanyView 
    3. RegulatoryActionView 
    4. ServiceView 
    5. ServiceRegionView 
    6. SubsidiaryView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 6 views are defined below.

1. The AcquisitionView must contain the following fields: 
    - name: AcquirerCompany   type: Company 
    - name: AnnouncementDate   type: DATE 
    - name: CloseDate   type: DATE 
    - name: DealCurrency   type: STRING 
    - name: DealValue   type: DOUBLE 
    - name: Notes   type: STRING 
    - name: PaymentType   type: STRING 
    - name: TargetCompany   type: Company 
The data source for the [TargetCompany] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
The data source for the [AcquirerCompany] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
An existing Acquisition entity should be loaded from the relative URL: 
    "/CompanyService/acquisition/{id}"   (HTTP-GET) 
If a new Acquisition entity has been created, the new entity should be posted to the relative URL: 
    "/CompanyService/acquisition"   (HTTP-POST) 
If an existing Acquisition entity has been updated, the modified entity should be sent to the relative URL: 
    "/CompanyService/acquisition/{id}"   (HTTP-PUT) 
If an existing Acquisition entity has to be deleted, the following relative URL should be called: 
    "/CompanyService/acquisition/{id}"   (HTTP-DELETE)

2. The CompanyView must contain the following fields: 
    - name: CompanyType   type: STRING 
    - name: Description   type: STRING 
    - name: FormerName   type: STRING 
    - name: FoundedDate   type: DATE 
    - name: HeadquartersAddress   type: STRING 
    - name: Industry   type: STRING 
    - name: Name   type: STRING 
    - name: Website   type: STRING 
An existing Company entity should be loaded from the relative URL: 
    "/CompanyService/company/{id}"   (HTTP-GET) 
If a new Company entity has been created, the new entity should be posted to the relative URL: 
    "/CompanyService/company"   (HTTP-POST) 
If an existing Company entity has been updated, the modified entity should be sent to the relative URL: 
    "/CompanyService/company/{id}"   (HTTP-PUT) 
If an existing Company entity has to be deleted, the following relative URL should be called: 
    "/CompanyService/company/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Acquisition columns: 
    - column: Notes 
    - column: DealValue 
    - column: CloseDate 
    - column: AcquirerCompany 
    - column: DealCurrency 
    - column: AnnouncementDate 
    - column: PaymentType 
    - column: TargetCompany 
The table should have the title "Acquisitions" und the data must be loaded from the server with the following relative URL: 
    "/CompanyService/acquisition/acquirercompany/{id}" 
Add a HTML table to the view with the following Acquisition columns: 
    - column: Notes 
    - column: DealValue 
    - column: CloseDate 
    - column: AcquirerCompany 
    - column: DealCurrency 
    - column: AnnouncementDate 
    - column: PaymentType 
    - column: TargetCompany 
The table should have the title "Acquisitions" und the data must be loaded from the server with the following relative URL: 
    "/CompanyService/acquisition/targetcompany/{id}" 
Add a HTML table to the view with the following FinancialStatement columns: 
    - column: Company 
    - column: TotalEquity 
    - column: NetIncome 
    - column: Employees 
    - column: TotalAssets 
    - column: Revenue 
    - column: FiscalYear 
    - column: OperatingIncome 
The table should have the title "FinancialStatements" und the data must be loaded from the server with the following relative URL: 
    "/PersonService/financialstatement/company/{id}" 
Add a HTML table to the view with the following StockListing columns: 
    - column: Exchange 
    - column: Company 
    - column: ListingDate 
    - column: Ticker 
    - column: Notes 
    - column: DelistingDate 
The table should have the title "StockListings" und the data must be loaded from the server with the following relative URL: 
    "/StockListingService/stocklisting/company/{id}" 
Add a HTML table to the view with the following Service columns: 
    - column: Description 
    - column: Name 
    - column: ServiceType 
    - column: Status 
    - column: LaunchDate 
    - column: Company 
The table should have the title "Services" und the data must be loaded from the server with the following relative URL: 
    "/CompanyService/service/company/{id}" 
Add a HTML table to the view with the following CompanyRole columns: 
    - column: RoleType 
    - column: Title 
    - column: StartDate 
    - column: Company 
    - column: EndDate 
    - column: Person 
The table should have the title "CompanyRoles" und the data must be loaded from the server with the following relative URL: 
    "/PersonService/companyrole/company/{id}" 
Add a HTML table to the view with the following Lawsuit columns: 
    - column: JurisdictionCountry 
    - column: FiledDate 
    - column: Company 
    - column: CaseName 
    - column: ResolvedDate 
    - column: CaseType 
    - column: Description 
    - column: Outcome 
    - column: SettlementCurrency 
    - column: JurisdictionCity 
    - column: SettlementAmount 
The table should have the title "Lawsuits" und the data must be loaded from the server with the following relative URL: 
    "/CityService/lawsuit/company/{id}" 
Add a HTML table to the view with the following Subsidiary columns: 
    - column: Notes 
    - column: ChildCompany 
    - column: ParentCompany 
    - column: StartDate 
    - column: EndDate 
The table should have the title "Subsidiarys" und the data must be loaded from the server with the following relative URL: 
    "/CompanyService/subsidiary/childcompany/{id}" 
Add a HTML table to the view with the following Subsidiary columns: 
    - column: Notes 
    - column: ChildCompany 
    - column: ParentCompany 
    - column: StartDate 
    - column: EndDate 
The table should have the title "Subsidiarys" und the data must be loaded from the server with the following relative URL: 
    "/CompanyService/subsidiary/parentcompany/{id}" 
Add a HTML table to the view with the following RegulatoryAction columns: 
    - column: City 
    - column: Country 
    - column: StartDate 
    - column: AuthorityName 
    - column: SourceReference 
    - column: Company 
    - column: ActionType 
    - column: Description 
    - column: EndDate 
The table should have the title "RegulatoryActions" und the data must be loaded from the server with the following relative URL: 
    "/CompanyService/regulatoryaction/company/{id}"

3. The RegulatoryActionView must contain the following fields: 
    - name: ActionType   type: STRING 
    - name: AuthorityName   type: STRING 
    - name: City   type: City 
    - name: Company   type: Company 
    - name: Country   type: Country 
    - name: Description   type: STRING 
    - name: EndDate   type: DATE 
    - name: SourceReference   type: STRING 
    - name: StartDate   type: DATE 
The data source for the [Company] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/CityService/country"   (HTTP-GET) 
The data source for the [City] select control should be loaded from the relative URL: 
    "/CityService/city"   (HTTP-GET) 
An existing RegulatoryAction entity should be loaded from the relative URL: 
    "/CompanyService/regulatoryaction/{id}"   (HTTP-GET) 
If a new RegulatoryAction entity has been created, the new entity should be posted to the relative URL: 
    "/CompanyService/regulatoryaction"   (HTTP-POST) 
If an existing RegulatoryAction entity has been updated, the modified entity should be sent to the relative URL: 
    "/CompanyService/regulatoryaction/{id}"   (HTTP-PUT) 
If an existing RegulatoryAction entity has to be deleted, the following relative URL should be called: 
    "/CompanyService/regulatoryaction/{id}"   (HTTP-DELETE)

4. The ServiceView must contain the following fields: 
    - name: Company   type: Company 
    - name: Description   type: STRING 
    - name: LaunchDate   type: DATE 
    - name: Name   type: STRING 
    - name: ServiceType   type: STRING 
    - name: Status   type: STRING 
The data source for the [Company] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
An existing Service entity should be loaded from the relative URL: 
    "/CompanyService/service/{id}"   (HTTP-GET) 
If a new Service entity has been created, the new entity should be posted to the relative URL: 
    "/CompanyService/service"   (HTTP-POST) 
If an existing Service entity has been updated, the modified entity should be sent to the relative URL: 
    "/CompanyService/service/{id}"   (HTTP-PUT) 
If an existing Service entity has to be deleted, the following relative URL should be called: 
    "/CompanyService/service/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following ServiceRegion columns: 
    - column: StartDate 
    - column: Service 
    - column: City 
    - column: Notes 
    - column: EndDate 
    - column: Country 
The table should have the title "ServiceRegions" und the data must be loaded from the server with the following relative URL: 
    "/CompanyService/serviceregion/service/{id}" 
Add a HTML table to the view with the following Trip columns: 
    - column: CompletedAt 
    - column: RequestedAt 
    - column: PriceCurrency 
    - column: Service 
    - column: StartedAt 
    - column: AcceptedAt 
    - column: DurationMinutes 
    - column: DriverAccount 
    - column: Status 
    - column: DistanceKm 
    - column: PriceAmount 
    - column: RiderAccount 
    - column: OriginCity 
    - column: Vehicle 
    - column: CanceledAt 
    - column: DestinationCity 
The table should have the title "Trips" und the data must be loaded from the server with the following relative URL: 
    "/VehicleService/trip/service/{id}"

5. The ServiceRegionView must contain the following fields: 
    - name: City   type: City 
    - name: Country   type: Country 
    - name: EndDate   type: DATE 
    - name: Notes   type: STRING 
    - name: Service   type: Service 
    - name: StartDate   type: DATE 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/CityService/country"   (HTTP-GET) 
The data source for the [Service] select control should be loaded from the relative URL: 
    "/CompanyService/service"   (HTTP-GET) 
The data source for the [City] select control should be loaded from the relative URL: 
    "/CityService/city"   (HTTP-GET) 
An existing ServiceRegion entity should be loaded from the relative URL: 
    "/CompanyService/serviceregion/{id}"   (HTTP-GET) 
If a new ServiceRegion entity has been created, the new entity should be posted to the relative URL: 
    "/CompanyService/serviceregion"   (HTTP-POST) 
If an existing ServiceRegion entity has been updated, the modified entity should be sent to the relative URL: 
    "/CompanyService/serviceregion/{id}"   (HTTP-PUT) 
If an existing ServiceRegion entity has to be deleted, the following relative URL should be called: 
    "/CompanyService/serviceregion/{id}"   (HTTP-DELETE)

6. The SubsidiaryView must contain the following fields: 
    - name: ChildCompany   type: Company 
    - name: EndDate   type: DATE 
    - name: Notes   type: STRING 
    - name: ParentCompany   type: Company 
    - name: StartDate   type: DATE 
The data source for the [ParentCompany] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
The data source for the [ChildCompany] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
An existing Subsidiary entity should be loaded from the relative URL: 
    "/CompanyService/subsidiary/{id}"   (HTTP-GET) 
If a new Subsidiary entity has been created, the new entity should be posted to the relative URL: 
    "/CompanyService/subsidiary"   (HTTP-POST) 
If an existing Subsidiary entity has been updated, the modified entity should be sent to the relative URL: 
    "/CompanyService/subsidiary/{id}"   (HTTP-PUT) 
If an existing Subsidiary entity has to be deleted, the following relative URL should be called: 
    "/CompanyService/subsidiary/{id}"   (HTTP-DELETE)