This is one of the examples of the file transfer between internal systems with numbered steps

Process Steps:

1. A job is schedule to run every x minutes
2. The job calls an ABAP program, and the execution parameter is the flow name in Active Transfer
3. The ABAP program calls a new function module created for MFT project
4. Function module calls Active Transfer via RFC, passing the flow name
5. Active Transfer gets the flow definition (only if it is a flow-based transfer) and starts the processing
6. Files previously created in the file system are read by Active Transfer
7. Files are stored temporarily in Active Transfer storage
8. Files are transferred to Unix file system based on flow definition; a name convention must be defined
9. Active performs a RFC call to the destination SAP system through function module FM RSSM_EVENT_RAISE, passing the flow process as event ID, and the file name as a parameter
10. SAP Event Management triggers all jobs related to the event ID
11. The job calls an ABAP program, and the file system source and archive folders are defined in the selection screen as a variant
12. The ABAP program calls function module GET_JOB_RUNTIME_INFO, which reads the event parameter to define the file to be processed
13. Process and archive

Active Transport performs post-processing events, such as deleting, renaming, archiving the files