Automate SAP Report Delivery by Mail addresses a problem most SAP landscapes know too well: Manual exports and forgotten file drops do not scale with transaction volume.
File jobs watch directories, rename after pickup, and alert on failure — the silent automation layer next to real-time APIs.
Mail templates bind data sources to recipients — including customer and vendor resolution — so operational reports reach the right inbox without manual export every morning.
Capabilities you use in iDataEngine
- Directory watch and scheduled pickup
- FTP/SFTP with key auth
- Failed mail history and resend
- SMTP corporate configuration
- CSV/JSON export jobs
- Mail groups and dispatch variants
Recommended workflow
- Open the relevant cockpit (iDataView Explorer, SQL Project, API Service Detail, or AccessGuard).
- Save and capture the generated URL, job ID, or snapshot reference in your change record.
- Extend the same definition to the next channel (API, SQL, MF, BI) without redesigning from scratch.
- Configure source objects, fields, mappings, or rules using session language and customer/system context.
Real-world scenario (2023)
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
Mail and API together cover both human notification and machine integration — one platform, two speeds.
Measured on lead time, defect rate, and audit readiness, the platform pays back in the first production quarter.