Skip to content

Configure E-mail

This use case describes how to configure distribution via the EMAIL channel: PLOSSYS Distribution Engine creates an e-mail with the form and the original files of a SAP structure as attachment, optionally merged into one PDF or ZIP file. The e-mail can be re-archived into the attachment list of the SAP structure.

Prerequisites

Activate the E-mail Channel

To activate the E-mail channel, execute the following steps in SAP:

  1. Start transaction /n/seal/img.

  2. Navigate to SEAL BC Sets → BC Sets PLOSSYS Distribution Engine (BC Set /SEAL/DDD_DST_DEV, registers the EMAIL output device together with FILEOUT and WEBPORTAL in one shared BC Set).

  3. Check the delivered defaults and activate the BC Set for the desired SAP order type, for example PUR.

  4. Also activate /SEAL/DDD_DST_EMAIL for the same order type. It presets the menu function, user exits, and the mandatory MAILRECEIVER/MAILSENDER/MAILSUBJECT settings.

Hint - related BC Set

/SEAL/DDD_DST_EMAIL_DAT presets DIST_CONFIG and QUEUE to EMAIL for order type PUR.

Configure the Distribution Engine Server

Execute the following steps on the Distribution Engine server:

  1. Open the <DIST_CONFIG>.ini file selected by the DIST_CONFIG parameter:

    • Windows: D:\SEAL\customer\server\dpf\conf\dpf4distribute\email.ini (default installation drive)
    • Linux: /opt/seal/server/dpf/conf/dpf4distribute/email.ini

    Hint - only the file name is configurable

    The directory is fixed. Only the file name changes, following the DIST_CONFIG value passed from SAP. Confirmed against a May 2026 test server configuration, which uses this per-channel file selection.

  2. Add the channel activation entry:

    DistChannel_1 = dpf4distribute.DistributeMail

  3. Set the mail server connection parameters, for example:

    JavaMailWorker_MailAuthType     = ""
JavaMailWorker_MailPassword     = ""
JavaMailWorker_MailSendPort     = 25
JavaMailWorker_MailSendProtocol = SMTP
JavaMailWorker_MailSendHost     = <smtp-relay-host>

Caution - DistChannel_1 is required

Without a DistChannel_n entry pointing to dpf4distribute.DistributeMail, no mail is sent even if the SAP-side BC Set is fully activated. This is the step that actually connects the EMAIL channel to the mail-sending workflow on the Distribution Engine server.

Remove Parameters Not Needed for E-mail

If unrelated parameters are not removed, they can cause error messages for the EMAIL channel. Remove them in SAP:

  1. Navigate to Grundeinstellungen → Parameter-Konfiguration → Parameter festlegen (Detail) (table /seal/out_cr010).

  2. Delete the row for your order type (for example PUR) with parameter ID MAILFILENAME.

Enable Re-archiving (Optional)

By default, the BC Set delivers re-archiving via SAP ArchiveLink (SEAL ArchiveLink File Loader), document type Bestellung, MIME type PDF. Execute the following steps in SAP:

  1. In addition to the E-mail BC Set, activate under DDD BC Sets - SAP Upload:

    • BC Set aktivieren - SAP Upload

      BC Sets: /SEAL/DDD_UPL_DAT, /SEAL/DDD_UPL_PAR

      Confirmed presets for order type PUR: DPFL_VARIANT, SAPAL_ARCHIVEID, SAPAL_DESCRIPTION, SAPAL_DOCCLASS

    • Either BC Set aktivieren - SEAL Generic Object Loader (/seal/lad_go) or BC Set aktivieren - SEAL ArchiveLink Loader (/seal/lad_al), depending on the upload variant used.

      Hint - source

      Both BC Set IDs confirmed in the Document Distribution Director System Description, version 1.5.0 (2025-04-17).

  2. If you use the SAP ArchiveLink File Loader as upload variant, set the following parameters:

    • SAPAL_ARCHIVEID: mandatory, ArchiveLink archive to store the document in, no default — must be set to a customer-specific archive, for example Z7.
    • SAPAL_DESCRIPTION: optional, free-text description shown in ArchiveLink, default provided by the BC Set.
    • SAPAL_DOCCLASS: optional, ArchiveLink document class, default Bestellung (BC Set default), for example MEOORDER.
    • SAPAL_DOCTYPE: optional, ArchiveLink document type/MIME type, default Portable Document Format (BC Set default), for example PDF.

Activate re-archiving with the following steps on the Distribution Engine server:

  1. Copy the configuration file:

    • Source: applications/server/dpf/conf/dpf4distribute/email.ini
    • Target: customer/server/dpf/conf/dpf4distribute/email.ini

  2. Open the copied file and set:

    WantArchiveMail = Y

  3. Run dpfupdate.

Hint - alternative upload variant

Instead of the SAP ArchiveLink File Loader, you can use the SEAL Generic Object Loader (DPFL_VARIANT = SAPGO) or disable the upload entirely (DPFL_VARIANT empty). Refer to SAP Archiving for the corresponding parameters.

Advanced Configuration

Settings in SAP

  • DIST_TYPE: attachment type of a document, ZIP, MERGE, NATIVE, or PDF. Set it on order level as the default. Override it on document or file level. Default: MERGE on order level, NATIVE for the form, object type /seal/0300.
  • PLS_MAIL_ZIP: packs all attachments of the e-mail into one ZIP file, if set to Y. Default: N.
  • PLS_MAIL_ZIPFILENAME: file name of the ZIP file. Default: attachmentsZip.zip.
  • MAIL_RECEIVER_CC and MAIL_RECEIVER_BCC: CC and BCC receivers, set on order level. Also requires the keys JavaMailWorker_MessageCcAddrList and JavaMailWorker_MessageBccAddrList on the Distribution Engine server.
  • SAP_UPLOAD_FORMAT = EML: re-archives the e-mail instead of the PDF. Requires the SEAL Generic Object Loader instead of the SAP ArchiveLink File Loader. Also requires an ArchiveLink document type such as ZEML with MIME type message/rfc822.
  • E-mail text: standard text in transaction SO10. Assign a custom standard text to the order type via Textvorlagen und Rückmeldungseinstellungen. Default: /seal/out_ml_mm_raw.
  • PDF/A check profile: check profile for the re-archived PDF, for example PDFA2B.

Settings on the Distribution Engine Server

  • JavaMailWorker_MessageAttachments_MaxSize: maximum size of the attachments of one e-mail, as an integer in MB without unit. 1 MB counts as 1,000,000 bytes. Larger attachments are distributed across several e-mails. With PLS_MAIL_ZIP = Y, they are distributed across several ZIP files. Set it in dpf4distribute.customer.ini. Default: 20.
  • JavaMailWorker_MessageCcAddrList: CC receivers of the e-mail, set in dpf4distribute.ini. Default: %PLS_RECEIVER_CC%.
  • JavaMailWorker_MessageBccAddrList: BCC receivers of the e-mail, set in dpf4distribute.ini. Default: %PLS_RECEIVER_BCC%.

Validate

  1. In SAP, trigger a message for a purchase order (transaction me22n).

  2. In SAP, check that the DDD output order was created, and that the Ausgabeparameter and SAP Upload tabs match your configuration.

  3. On the Distribution Engine server, check that the output order was processed in the DPF Tracker.

  4. Check that the e-mail was sent with the expected attachments.

  5. If re-archiving is enabled, check in SAP that the object was re-archived into the attachment list of the purchase order.

Back to top