
With this method of uploading data, the files are placed in a folder on a file server. The folder scanner repeatedly scans the folder and triggers the upload process.
The files are placed in the file system by file transfer protocol, for example.
The load manager reads the active data delivery agreements to determine which folders in the file system to scan.
It determines this based on the definition of the logical file path you made in the transaction Logical File Path Definition (FILE).
The folder scanner scans the inbound folder.
In the standard system each data delivery is placed in a folder that is reserved for one specific data delivery agreement.
File names can contain a pattern, such as a date or an ID, by which files from the same delivery can be recognized and placed in the correct folder. This can be set up in Customizing for Cross-Application Components under
As soon as the load manager detects that all the mandatory files in a data delivery agreement are in the inbound folder, it creates runtime instances of the following:
Steps
Processes
Data sets
After creating the instance data, the load manager does the following:
Associates the process ID with the files and the data sets
Tries to set the status of all the process steps to Ready
The statuses of the steps are propagated to all the instances.
The files that have the status Ready are moved to the file processing folder.
If any of these conditions are not met, the data delivery stays in status New.
Steps 1-4 are repeated continuously.
The process scheduler scans the steps instance table to determine what is ready for execution.
The process scheduler updates the status of the step.
The process scheduler executes a step.
The step triggers a process chain.
The process chain reads instance tables for information that is needed for processing.
The process chain finishes executing the step and updates its status.
When all the steps are executed and the data delivery is complete, the files are moved to the archive folder.