Lesson 3 of 5
Channels and forms
9 min
Once SAP knows what to send and to whom, it has to produce the document and get it there. That is the job of channels and forms. Both differ between editions and between projects, so treat this lesson as the map and confirm the detail with your output consultant.
Channels
| Channel | What happens | What to check | Contoso use |
|---|---|---|---|
| A print job is sent to a print queue, which sends it to a physical printer | Right printer, copies, paper tray; job actually printed | Delivery notes at shipping points 1710 and 1720 | |
| A PDF is attached to an email built from an email template and sent via the mail server | Sender, recipients, subject and body, attachment, size | Invoices and order confirmations to fleet customers | |
| XML | Structured data is sent electronically, typically to a network or e-invoicing service | Format, mandatory fields, acknowledgments | Possible future e-invoicing |
| IDoc (on-premise and private cloud) | An IDoc is created for EDI partners | Partner profile, message type, status of the IDoc | Invoices to a large fleet customer's EDI system |
EDI-type channels do not use form templates; they send data, not a layout. That changes what you test: field mapping and acknowledgment instead of how the page looks.
Form templates
For print and email, the document layout comes from a form template. In SAP S/4HANA output management the default form technology is Adobe-based forms (XFA), rendered by Adobe Document Services; SAP also offers the SAP Forms Service by Adobe on SAP BTP as a hosted option. Form templates are commonly split into a master form (logo, header, footer, company address, shared across documents) and a content form (the document-specific content, such as invoice items).
Key users manage templates in the Maintain Form Templates app: they can see SAP's delivered templates, download one, adapt it in Adobe LiveCycle Designer, and upload it as a custom template, which output parameter determination can then select. Email bodies and subjects come from email templates, maintained in their own app in many releases. In Public Edition, this is the main way to change forms; Private Edition and on-premise customers can also develop forms in the classic way. Legacy forms built with SAPscript or Smart Forms can still be used in some scenarios, which matters for ECC conversions.
Email specifics
Email output depends on more than SAP. The mail server configuration, sender domain settings and the receiving company's spam filters all decide whether an invoice arrives. Email templates define the subject and body, often with placeholders such as the invoice number, so test that the placeholders are filled. Size limits apply to attachments; in Public Edition SAP documents a limit of 25 MB per email including attachments, and on-premise limits depend on your mail setup.
Languages and versions
Forms are language-dependent. If Contoso ships to a Canadian customer that wants French documents, the form template step must find a French version. Test each language in scope with real characters (accents, special symbols), and check that long product descriptions and addresses do not overflow the layout.
What would you do?
Contoso wants its new logo on all customer documents. The output consultant proposes updating the master form template only. Priya asks how much testing is needed. What do you recommend?
- Channels: print (print queue), email (template + PDF), XML and IDoc for electronic exchange.
- EDI-type channels send data, not forms; test mapping and acknowledgments.
- Forms: Adobe-based by default; master form for shared elements, content form per document.
- Maintain Form Templates manages custom templates; confirm edition-specific options with an SME.
Check your understanding · not graded
Lesson check
1. Which channel does NOT use a form template?
2. What does a master form template typically contain?
3. Which app is used to upload a custom form template?
4. What is the default form technology in SAP S/4HANA output management?