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.
Mail templates bind data sources to recipients — including customer and vendor resolution — so operational reports reach the right inbox without manual export every morning.
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.
Capabilities you use in iDataEngine
- Mail groups and dispatch variants
- Event-triggered mail actions
- Failed mail history and resend
- SMTP corporate configuration
- Long text lists and table templates
- Mail templates: body types and data sources
Recommended workflow
- Run Test (iDataView Test, SQL First Row, API Test Service, or AG scan) before scheduling or publishing.
- Configure source objects, fields, mappings, or rules using session language and customer/system context.
- Open the relevant cockpit (iDataView Explorer, SQL Project, API Service Detail, or AccessGuard).
- Extend the same definition to the next channel (API, SQL, MF, BI) without redesigning from scratch.
Real-world scenario (2022)
Bank statements arrive via SFTP at 03:00; MF picks up, validates, triggers processing, archives to 'processed' — treasury starts work with data, not with file hunts.
Why it matters
Mail and API together cover both human notification and machine integration — one platform, two speeds.
The competitive edge is not more developers; it is removing wait states between idea, data, and delivery.