Mail Groups and Dispatch Variants addresses a problem most SAP landscapes know too well: Manual exports and forgotten file drops do not scale with transaction volume.

The MF module automates report delivery by e-mail (HTML, Excel, PDF) and file transfer (FTP/SFTP, CSV, JSON) with templates, mail groups, dispatch variants, and failed-item history.

File jobs watch directories, rename after pickup, and alert on failure — the silent automation layer next to real-time APIs.

Capabilities you use in iDataEngine

  • CSV/JSON export jobs
  • SMTP corporate configuration
  • Long text lists and table templates
  • FTP/SFTP with key auth
  • Directory watch and scheduled pickup
  • Mail groups and dispatch variants

Recommended workflow

  1. Open the relevant cockpit (iDataView Explorer, SQL Project, API Service Detail, or AccessGuard).
  2. Extend the same definition to the next channel (API, SQL, MF, BI) without redesigning from scratch.
  3. Run Test (iDataView Test, SQL First Row, API Test Service, or AG scan) before scheduling or publishing.
  4. Configure source objects, fields, mappings, or rules using session language and customer/system context.

Real-world scenario (2021)

Sales managers receive personalized HTML dashboards at 06:00 with Excel attachments — recipient lists resolved from SAP hierarchy, not a static distribution list.

Why it matters

File automation catches bank and supplier drops that humans forget on Friday nights — errors become alerts, not discovered Monday crises.

The competitive edge is not more developers; it is removing wait states between idea, data, and delivery.