Typical batch scenario where a scheduled process makes a large bulk extract into a file, and later an update into a target data-base, often at night-time when it has no impact on operational systems.
These interfaces are always scheduled at end of day (EOD), weekly or monthly. The same mechanism can also be used for initial load into new systems, or full refresh of systems that are updated by event-publishing.
There is always an extract of data, the transfer of data to the target system and a load. Extract and/or load can be done by an ETL tool or by the applications themselves.
The transport is usually over native or local FTP or FTPS. It is desired that any such local FTP mechanisms are centralized into S2SMFT
Scheduling is a separate function, and also central, using for example a tool such as Control-M.
Start using Managed File Transfer (S2SMFT) for all transport of files when processing files between applications.
In case of a need to move data within the same server between components of the same application, use a separate scheduling function such as Control-M or Autosys. The local file movements too, can then be monitored and controlled centrally.
Where possible, use an ETL tool for extract and load: (S2SETL). This creates a repeatable and consistent method for moving large sets of data in a controlled manner.