Error: Migration V20222601101059__fsm_vehicle_capacity_data_fix.sql failed

[nsrivastava2]

WARNING: Unable to resolve location filesystem:/flyway/seed
WARNING: Unable to resolve location filesystem:/flyway/seed
Successfully validated 23 migrations (execution time 00:00.067s)
Current version of schema "public": 20222502155636
WARNING: outOfOrder mode is active. Migration of schema "public" may not be reproducible.
Migrating schema "public" to version 20222601101059 - fsm vehicle capacity data fix
ERROR: Migration of schema "public" to version 20222601101059 - fsm vehicle capacity data fix failed! Changes successfully rolled back.
ERROR: 
Migration V20222601101059__fsm_vehicle_capacity_data_fix.sql failed

-------------------------------------------------------------------
SQL State  : 42P01
Error Code : 0
Message    : ERROR: relation "eg_vehicle" does not exist
  Where: PL/pgSQL function inline_code_block line 5 at FOR over SELECT rows
Location   : /flyway/sql/V20222601101059_fsm_vehicle_capacity_data_fix.sql (/flyway/sql/V20222601101059_fsm_vehicle_capacity_data_fix.sql)
Line       : 1
Statement  : do
$$
declare
    f record;
begin
    for f in  
                select fsm_app.applicationno,fsm_app.vehicletype,
                vehicle.type, vehicle.tankcapicity
                from eg_fsm_application fsm_app, eg_vehicle vehicle 
                where fsm_app.vehicle_id=vehicle.id  
    loop 
                UPDATE eg_fsm_application 
                set vehiclecapacity=f.tankcapicity,lastmodifiedby='SAN-798',lastmodifiedtime=extract(epoch from current_timestamp )*1000
                where applicationno=f.applicationno;
    end loop;
end;
$$

[nsrivastava2]

The issue happens when deploying the UPYOG FSM module on Standalone server (it happens on AWS deployment as well). Solution is to create the table schema manually. Attached is the schema file.
Create-pg_vehicle.txt