Use of PDF Fragments in Outputs – Part 1

Introduction

With S/4 HANA platform SAP has provided new Output Management Architecture built on BRF+ with Fragmented Adobe Forms. This blog will focus more on how to use the Fragments effectively. Also how the SAP configuration can be used without change in SAP Output Forms (Fragment-based PDFs).

Purpose

New Form Technology does not have print programs like traditional forms but uses OData services to populate the information on the PDF Forms. Information on the end-to-end configuration is divided into multiple parts. Part 1 will cover the PDF-based forms with Fragment form technology (The Architecture).

What are Fragments?

Considering the reusability of templates, Adobe has developed Fragment-based PDF templates. These templates are divided into two parts, Master Form Template and Content Form Template.

Master Form Template

A master form template is a separate form template (XDP file). It includes different layout definitions (fragments) for one or more master pages. The application form can reference only one at a time. These templates contain the placeholders for static texts, logos, and addresses Standard Templates in S/4 HANA: SAP provided two Master Templates based on the paper size · SOMU_FORM_MASTER_A4 – master form template for paper size A4 · SOMU_FORM_MASTER_LETTER – master form template for paper size Letter Each Master Template contains different Fragment designed for Page Layouts (landscape or portrait) and  Layout Variant (fact sheet, item list or outbound letter). Fragments: ·         Landscape_Factsheet ·         Landscape_ItemList ·         Portrait_Factsheet ·         Portrait_ItemList ·         Portrait_OutboundLetter Each Fragment Layout contains placeholders for below items in Master Page (mst1) and Subsequent Page (mst2). ·   Header Information §  Document Title (E.g. Purchase Order) §  Logo §  Page Number ·   Sender Address ·   Recipient Address ·   Footer Information

These placeholders are configurable and the users can dynamically populate the required values based on the organization structure.

Configuration: Transaction Code SPRO

Cross-Application Components -> Output Control -> Define Rule for Determination of Master Form Template

Currently, SAP supports Org Structure like Company as the top level and Purchase Org, Plant or Sales Org as next level. Against each of the entry, users can be maintained the Sender Address or Footer information (SO10 Text) and Logo on the printout.

Content Form Template

This is PDF form which is used to show the data like header information, item information, Terms, and Conditions etc. In each content form, there is a place where Master temple is inserted. So in runtime master form template prints on the content form.

Conclusion

To summarize, with new output management is easy to deploy the change in standard forms. In next part, we will discuss more on how to modify the Master and Content Form templates.