Professional Documents
Culture Documents
1LQ Set-Up EN XX
1LQ Set-Up EN XX
1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.1 Output with Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Printing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Emailing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Merging of Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
6.2 Usage of custom fonts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
The purpose of this document is to provide details on setting up and using output management in SAP S/4HANA
Cloud. It also covers general topics like setting up printers, adapting form templates, and transporting custom
objects from the quality to the productive system. If a section of the document is only relevant for output control,
this is mentioned at the beginning of the section.
Printing in SAP S/4HANA Cloud involves the usage of one or more print queues. For scenarios in which unattended
printing (mass printing) shall be performed automatically by the system, you need the SAP Cloud Print Manager.
The details for the setup are covered in section Setting Up Printers [page 10]. For browser-based printing, no
setup is required.
Sending emails requires defining allowed email domains, as well as sender and recipient email addresses. There’s
also the option to create custom email templates to define a custom email subject and body based on the SAP-
delivered templates.
Form templates in SAP S/4HANA Cloud are using SAP Cloud Platform Forms by Adobe as the standard and only
form technology. All business applications with form processing requirements leverage these forms, and SAP
provides default form templates. A template can be either of type master or content (referring to a master form) or
a standalone (no master is used). A master template defines the generic page layout and includes content such as
headers and footers that have logos and contact information. A content template can be embedded within a
master template and contains unique information such as invoice data. A standalone template has all content in
one form template. Customers can modify predelivered form templates or create their own forms from scratch
using Adobe LiveCycle Designer.
In the end, all custom objects must be transported from the quality to the productive system. This document
provides details on how to enable smooth processing.
● It's mandatory that the Output Management (1LQ) scope item is active.
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options to
check the status:
○ Manage Your Solution:
In the SAP S/4HANA Cloud system, in the SAP Fiori launchpad, open the Manage Your Solution app and go
to View Solution Scope.
○ SAP Central Business Configuration:
In the Explore phase, navigate to the Activities tab. Search for Define Scope and choose Go to App.
If the scope item is not active, please request the activation via BCP – Ticket Component: XX-S4C-OPR-SRV.
● Your key user needs the required authorization in SAP S/4HANA Cloud to enable the related apps in the SAP
Fiori launchpad:
○ Key user: SAP_BCR_CORE_EXT
Note
Alternatively, if the role is not available, make sure that the following business catalog has been
assigned to a role that the user does have: SAP_CORE_BC_EXT.
Note
This role can already include business catalogs that allow you to access certain apps that are used
here, for example: key user catalogs.
Note
Make sure that the Adobe LiveCycle Designer version is 10.4 or higher.
● To follow the examples in this document, your user should also have the following authorizations:
○ Manage Billing Documents app: SAP_BR_BILLING_CLERK
○ Manage Purchase Orders app: SAP_BR_PURCHASER
● For the purpose of verification, use billing documents with the status To Be Posted. Make sure that your system
contains some transactional data.
Output Management is not a standalone functionality but always embedded in a business process or a specific
business application. So when looking at this topic, you should start with the Fit-To-Standard analyses of the
business scenarios of your selected scope.
During these analyses, you identify several requirements for communication with your business partners. Note
them down and structure them as you will need them later for the setup of output management.
The following sections give you some guidance on what you should focus on and which information is necessary to
complete the setup.
The purpose of this task is to define the communication channels with your customers. As a result, you should have
a list of channels with detailed information for each channel. Currently, you can use printing, e-mailing, and
electronic data interchange (EDI) for communicating with your customers.
3.1.1 Print
Printing can be divided into unattended printing (back-end printing) – usually performed via batch jobs – and
attended printing (browser-based printing).
Back-end printing means that you trigger the output to a predefined printer and the system automatically sends it
to this printer without any further user interaction. This method requires more customizing of the system but
allows automated output.
Browser-based printing means that the user selects each document to be printed in the browser and then either
directly prints it from a built-in reader application (for example, PDF reader), or downloads it. In both cases, the
printers connected to the user’s system can be used without any further setup. However, the printing in this
scenario is then not integrated anymore with the system and tracking of the print process is not possible.
Procedure
Define your use cases for unattended and attended printing respectively. Consider your existing printer landscape
and business requirements, such as using printer servers, direct connections, and printing with restricted access.
Emails are sent using the e-mail server provided with your system. The purpose of this task is to define the
technical setup for sending emails. This includes defining the sender domains, sender email addresses, and email
addresses for testing.
Procedure
3.1.3 EDI
There are multiple (application-specific) communication scenarios, which include electronic data interchange
(EDI). These scenarios are described in the scope item of the corresponding business scenario.
Procedure
Once you know which communication channels you are going to use, you need to define how the documents you
send should look like. The term documents here covers form templates and email templates. The latter is of course
only relevant if you use emails. Form templates are used for printing and emailing but cannot be used for electronic
data interchange (EDI).
The purpose of this task is to define the documents for communication including branding. You need to be clear
about how the documents should look like.
Form templates are usually divided into a layout part (which elements are shown, their position, size, etc.) and a
content part (which data is used).
Procedure
Email templates allow you to define the email subject and the email body of your emails. Both can be a combination
of static texts with placeholders (variables). The email body can be set as plain text or as HTML.
When choosing HTML, you can use any external HTML editor to design the email body and copy the HTML source
code into the email template. Hence, HTML expertise is necessary to complete this task.
Note
In the SAP S/4HANA Cloud environment, customer's can print to their local printers by using the print queue
concept. The Maintain Print Queues app creates print queues that are virtual connections between the cloud
system and local printers. Print jobs are initially sent to a print queue. An agent called SAP Cloud Print Manager is
installed on the customer's network. It checks if there are any print jobs in the print queue. If so, the SAP Cloud
Print Manager retrieves these documents and sends them to the locally configured printer. This print queue
concept provides a safe and autonomous way for cloud customers to print to their local printers.
Prerequisites
● You have the necessary authorization to create print queues via the Maintain Print Queues app.
● You have the necessary authorization to maintain rules via the Output Parameter Determination app.
● You have the necessary authorization to install SAP Cloud Print Manager software on your local machine.
● Your user has the necessary (key user) authorizations/roles assigned. This ensures that you can access billing
documents.
The purpose of this task is to define the technical setup for printing business documents unttended (back-end
printing). This involves the following activities:
1. Defining print queues on server side which hold the business documents to be printed,
2. Installing the SAP Cloud Print Manager on each client,
3. Assigning a local printer to a print queue on each client, so documents can be pulled automatically from the
server.
Note
SAP S/4HANA Cloud always includes a print queue with name DEFAULT. It serves mainly as a sample queue which
cannot be used for productive output (as you cannot connect SAP Cloud Print Manager to it). Hence, you need to
create one or more custom print queues in order to connect your physical printers.
Use
You're creating a print queue that's used for the printer channel setting.
Procedure
Field Value
Queue Z_PRINT_EX
Format PDF
Retention 1
Field Value
Name Z_PRINT_USER
Use
In this step, you're installing the SAP Cloud Print Manager software on a server or on your local machine.
Procedure
1. On the SAP Fiori launchpad, choose the app Install Additional Software.
2. Choose SAP Cloud Print Manager and choose Download.
3. Download the latest version of SAP Cloud Print Manager.
Note
To download SAP Cloud Print Manager, you're redirected to the SAP Support Portal. That's why a Support
Portal user is required.
Result
Procedure
Field Value
Name Z_PRINT_EX
User Z_PRINT_USER
Note
The SAP WebService URL typically corresponds to the SAP Fiori launchpad URL.
6. Choose Test Connection and make sure that the connection test is successful.
7. Choose OK.
8. Under Runtime System, select the runtime that you've created.
9. On the Print Queue tab, select the queue.
10. On the menu bar, choose Print Queue Output Options .
11. Make the necessary entries in the Output Options dialog. Choose OK.
Test the selected printer and make sure that the printer is working. The Save to File option allows you to keep a
record of the print content in your file system.
After you've changed the settings, the SAP Cloud Print service restarts automatically.
12. Keep the SAP Cloud Print Manager up and running.
Result
You've successfully modified the SAP Cloud Print Manager settings. The SAP Cloud Print Manager is ready for
printing tasks.
This chapter is only relevant for business applications using SAP S/4HANA output control.
Procedure
1. On the SAP Fiori launchpad, choose the app Output Parameter Determination.
2. On the Output Parameter Determination screen, on the Select Business Rules tab, select an application under
Show Roles for.
3. Under Determination Step, select Printer Settings via the value help icon.
In this example, Billing Document is selected as a business rule. You can select any other option.
4. On the Maintain Business Rules tab, choose Edit.
5. On the Table Contents tab, enter the queue name in the PRINT_QUEUE_NAME field.
Example: Set print queue name as Z_PRINT_EX.
6. Choose the content of the PRINT_QUEUE_NAME field.
7. In the dialog box, select the queue from the options.
8. Choose OK. To save your changes, choose Activate.
9. Make sure that the activation has been successful.
Result
You've successfully modified the print rule. A specific business rule can output to the print queue that you've
assigned.
With the SAP S/4HANA Cloud Output Management framework, you can automatically send configured application
documents in PDF format to business partners via e-mail. SAP provides you with predelivered email templates for
several application objects. You can customize the email templates by cloning the generic ones, and populating the
subject line and body of the email.
During the technical setup procedure, an individual email domain is assigned to each tenant to send emails in the
SAP S/4HANA Cloud environment. The my3XXXXX.mail.s4hana.ondemand.com domain is used in the technical
communication with the cloud email infrastructure. However, in business communication, it's expected that the
readable email header contains addresses from a customer's email domains (for example,
John.Doe@company.com). During tests, it's necessary to control which addresses the test system can send emails
to. This section describes the relevant settings.
● You have the necessary authorization to create email templates via the Maintain Email Templates app.
● You have the necessary authorization to maintain rules via the Output Parameter Determination app.
● You have the necessary authorization to create service tickets.
In business communication, it's expected that the readable email header contains addresses from a customer's
email domain or domains. In this setting, you can define which domain is allowed in the readable email header. You
may also specify a list of domains if multiple domains are allowed.
Examples:
● company.com would allow all email addresses in this domain such as John.Doe@company.com
● *.company.com would allow all email addresses in company.com subdomains such as
John@sales.company.com or Doe@service.company.com
Note
The technical email still contains the technical domain that has been assigned (in the SMTP envelope). This is
required for communication within the SAP S/4HANA Cloud environment. This setting has an impact only on
the readable email header information.
Procedure
1. Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
○ Configure Your Solution:
Log on to the SAP Fiori Launchpad in the SAP S/4HANA Cloud system as a Configuration Expert -
Business Process Configuration (SAP_BR_BPC_EXPERT).
Navigate to Manage Your Solution Configure Your Solution .
On the Configure Your Solution: Realize Phase screen, set the following search filters. Search for the Define
Email Sender Domain configuration item and select the result. Select Configure.
○ SAP Central Business Configuration:
○ Log on to the project experience in SAP Central Business Configuration.
○ In the Realize phase, navigate to the Configurations tab.
○ Set the relevant search filters, to find the Define Email Sender Domain configuration activities.
○ In the Configuration Activities section, select the Define Business System Type configuration activity.
Choose Go to Activity to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori
launchpad as a Configuration Expert - Business Process Configuration SAP_BR_BPC_EXPERT.
2. Choose New Entries and maintain your Sender Domain Name(s).
3. Choose Save and exit.
Generally, the output control functionality determines a sender email address and adds it to the email header.
Within this setting, you may define a default sender address if no sender address has been determined.
Example:
● do.not.reply@company.com
Procedure
1. Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
○ Configure Your Solution:
Log on to the project experience in SAP Central Business Configuration.
Navigate to Manage Your Solution Configure Your Solution .
On the Configure Your Solution: Realize Phase screen, set the following search filters:
Enter Define Default Email Sender Address in the Search Input Text smart field, choose Enter, and
select the result. Select Configure for the configuration step.
○ SAP Central Business Configuration:
○ Log on to the project experience in SAP Central Business Configuration.
○ In the Realize phase, navigate to the Configurations tab.
○ Set the relevant search filters, to find the Define Default Email Sender Address configuration activities.
○ In the Configuration Activities section, select the Define Business System Type configuration activity.
Choose Go to Activity to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori
launchpad as a Configuration Expert - Business Process Configuration.
2. In the Define Default Email Sender Address row, choose Start.
3. Maintain the Default Sender Address field and the Visual Name field.
Example:
Field Value
Within test systems, it's necessary to control which receivers are allowed within email communication. For
example, you don't want dunning runs in the test system to send emails to your real-world business partners. To
avoid this, you must maintain a white list.
Receivers can be explicitly listed with their email addresses, or pattern expressions may be used.
Note
This setting is effective in test systems only. Production systems don't execute this test.
Procedure
1. Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
○ Configure Your Solution:
Log on to the SAP Fiori Launchpad in the SAP S/4HANA Cloud system as a Configuration Expert -
Business Process Configuration (SAP_BR_BPC_EXPERT).
Navigate to Manage your Solution Configure Your Solution
Search for the Define Email Receiver Addresses for Test Systems configuration step and select the result.
Select Configure for the configuration step.
○ SAP Central Business Configuration:
Log on to the project experience in SAP Central Business Configuration.
In the Realize phase, navigate to the Configuration Activities tab and search for the following activity: Define
Email Receiver Addresses for Test Systems.
Choose the line item in the search result to see more details about this configuration activity.
Choose the Go to Activity button to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP
Fiori launchpad as a Configuration Expert - Business Process Configuration (SAP_BR_BPC_EXPERT).
2. To maintain the Receiver Address Pattern, choose New Entries (for example: *@company.com). This table can
have multiple entries.
3. Choose Save and exit.
This chapter is only relevant for business applications using SAP S/4HANA output control.
The default email address of the sender (of the output item) is set by the business application. The business
application decides the source of this email address. For example, it could be read from a master data address or
from a document address.
Output Control offers the Email Settings determination step (within Output Parameter Determination) to
individually configure the sender email address in a more flexible way using business rules. The settings in this
determination step overwrite the default sender email address from the business application.
If no sender email address can be determined from these two sources, it can still be manually added by the user in
the output details screen within the business application. Here, the user can also review the determined sender
email address.
This section is only relevant for business applications using SAP S/4HANA output control.
The default email address of the recipient (receiver of the output item) is set by the business application. The
business application decides the source of this email address. For example, it could be read from a master data
address or from a document address. Output Control uses this email address always as TO address. You can't
define this address as CC or BCC. Currently, only one email address is possible.
Output Control offers the Email Recipient determination step (within Output Parameter Determination) to
individually configure multiple email addresses and their usage (TO, CC, BCC). The settings in this determination
step overwrite the default email address from the business application.
In addition to this default behavior, you can mix both sources. Output Control offers a special constant which can
be used in the Email Recipient determination step to retrieve the default email address of the business application.
It's available for all applications in Output Parameter Determination and allows you to:
● Define the usage of the default email address as TO, CC, or BCC.
● Use the default email address and additional email addresses for one recipient.
Use
In this step, you're defining the usage of the default email address and one additional email address for the output.
Procedure
Note
In this example, Billing Document is selected as application. You can select any other option.
Result
The purpose of this task is to prevent emails sent by your SAP S/4HANA system are classified as spam and do not
reach the recipient(s). The following section shows you how you can create a sender policy framework (SPF) record
for your SAP S/4HANA email sender domain.
SPF is an email validation system designed to prevent email spam by detecting email spoofing, a common
vulnerability, through verifying sender IP addresses.
SPF allows administrators to specify the IP address of the sending email servers that are authorized to send email
with envelope-from addresses in the sender domain. SPF does this by creating a specific SPF record (or TXT
record) in the Domain Name System (DNS).
Email exchangers use the DNS to check that an email from a given domain is being sent by an email server
authorized by that domain's administrator.
Emails sent from servers with unauthorized IP addresses may be considered unsolicited and may be discarded by
the receiver.
Adopting SPF verification on your email servers will ensure that emails are being sent only from authorized email
servers.
Use
SPF record for the business mails are updated on the Technical From/Mail From/Envelop From address, which is
always dsn@myXXXXXX.mail.s4hana.ondemand.com or dsn@myXXXXXX.mail.saps4hanacloud.cn
Example
Procedure
Note
1. Go to https://mxtoolbox.com/SuperTool.aspx
2. Provide the domain as myXXXXXX.mail.s4hana.ondemand.com or myXXXXXX.mail.saps4hanacloud.cn
3. Create a specific SPF record (or TXT record) in the sender Domain Name System (DNS) by specifying IPs from
previous step.
Result
You've successfully created a sender policy framework (SPF) record for your SAP S/4HANA email sender domain
The purpose of this task is to create customer-specific form templates, based on the templates provided by SAP,
using Adobe LiveCycle Designer. Activities include downloading the form template, modifying and testing it locally,
and uploading it back to the system for further testing.
SAP delivers standard form templates for many business applications as well as for different layout definitions.
Master form templates define the page layout (paper size, orientation) and contain placeholders for static data, for
example, a logo, and a footer text. This data is displayed on each form page.
Note
The predelivered templates with the name SOMU_DEMO_FORM_MASTER* contain static content. Don't copy
them. They are only for demonstration purposes. When creating your own master form template, copy one of
the predelivered templates with the name SOMU_FORM_MASTER*. There is a variant for paper size A4 and one
for paper size US letter.
If you want to make minor changes (for example: to change logos, footers, or sender addresses) to your form
template, refer to the following steps.
Procedure
1. Log on to the SAP Fiori launchpad as a key user with the output management role.
2. Choose Manage Logos.
3. Choose Add (the + icon).
4. In the dialog box, choose Add ( the + icon).
5. Select the logo files from your local folder.
6. The next dialog box will show a thumbnail of the selected image. Fill out the necessary fields.
7. Save your changes.
8. The logo that you've created previously should be listed.
Result
Procedure
1. Log on to the SAP Fiori launchpad as a key user with the output management role.
2. Choose Manage Texts.
3. Choose Add (the + icon).
4. In the dialog box, fill out the necessary fields.
Example:
Field Value
Name TEXT_TEST
Language English
Note
You can select the Type (footer or sender address) from the dropdown list.
Result
If you want to make minor changes (for example: customized fields) to your form template, refer to the following
steps.
The Maintain Form Templates SAP Fiori app provides you with a list of predelivered templates. In this section, you're
downloading a standard master form template.
Procedure
1. Log on to the SAP Fiori launchpad as a key user with the output management role.
2. Choose Maintain Form Templates.
3. Switch to the Predelivered Templates tab.
4. Enter Form Master Template in the Description smart field and choose Go.
5. Choose the SOMU_ FORM_MASTER_ A4 line item.
6. To download the English form template, choose Download under English.
7. The browser downloads a WINZIP file with the name entity.zip.
8. Unzip the file to your local folder.
Result
In this section, you're using the Adobe LiveCycle Designer to modify the standard master form.
Note
This is for demonstration purposes only. If you want to use it in a productive system, contact an expert.
Procedure
Result
In the SAP Fiori app Maintain Form Templates, you're uploading the modified template to use it later on.
Procedure
Field Value
Language English
Note
The YY1 prefix in the form template name has been added automatically to indicate that this is a custom
template.
In this step, you're defining rules that determine the master form template in the Manage Your Solution SAP Fiori
app.
Procedure
1. Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
○ Configure Your Solution:
Log on to the SAP Fiori Launchpad in the SAP S/4HANA Cloud system as a Configuration Expert -
Business Process Configuration (SAP_BR_BPC_EXPERT).
Navigate to Manage Your Solution Configure Your Solution .
Search for the Define Rules for Determination of Master Form Template configuration step and select the
result. Select Configure for the configuration step.
○ SAP Central Business Configuration:
○ Log on to the project experience in SAP Central Business Configuration.
○ In the Realize phase, navigate to the Configurations tab.
○ Set the relevant search filters, to find the Define Rules for Determination of Master Form Template
configuration activities.
○ In the Configuration Activities section, select the Define Business System Type configuration activity.
Choose Go to Activity to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori
launchpad as a Configuration Expert - Business Process Configuration.
2. Choose New Entries.
3. On the Define Rules for Determination of Master Form Template panel, enter the following form attributes:
Example:
Field Value
Rule ID RDS_DEMO_RULE_GENERIC
Number 1
Note
In this example, a sequence number of 1 without any other information (for example, channel, form
template, and/or organization units) has been assigned to the RDS_DEMO_RULE_GENERIC rule. This makes
The lower the sequence number, the higher the priority. This implies that lower numbers should be assigned to
more specific rules.
Each rule comprises several parameters. Some of the parameters are optional. If you leave the relevant fields
blank, any value is deemed to satisfy the condition.
4. On the Content for Master Form Template panel, enter the following form attributes:
○ Under Sender Address, enter the sender address that you've created in the Managing Texts [page 22]
section.
○ Under Footer Block, enter the footer that you've created in the Managing Texts [page 22] section.
○ Under Logo, enter the logo that you've created in the Managing Logos [page 21] section.
5. Save your changes.
6. Choose Exit.
Result
You've defined a business rule to determine your custom master form template.
In the following sections, you're downloading the standard form template, modifying it, and adding a new field to it.
Additionally, you're uploading the custom template and assigning it to the output type. Last but not least, you're
creating business rules to define how a custom form is used.
The Maintain Form Templates SAP Fiori app provides you with a series of predelivered templates. In this section,
you're reusing the standard form template and modifying it.
Procedure
Result
In this section, you're using the Adobe LiveCycle Designer to modify the standard form template to include the
custom field that you've created before.
Note
This is for demonstration purposes only. If you want to use it in a productive system, contact an expert.
Procedure
Note
Alternatively, to add a text field (or other field forms), go to Object Library and drag and drop a text field to
the Design View tab.
Result
In the Maintain Form Templates SAP Fiori app, you're uploading the custom template to use it later on.
Procedure
Field Value
Language English
Note
The YY1 prefix in the form template name has been added automatically to indicate that this is a custom
template.
When creating and uploading your custom form template, you can define the language of the form template. This
language is called Original Language. All modifications (layout or content changes) to the form template need to be
done in this language variant.
If you need additional translations of this form template, you can create them with the app Maintain Form
Templates. This app allows you to translate all static texts in the form template. Dynamic texts (added at runtime)
cannot be translated here.
Procedure
This section is only relevant for business applications using SAP S/4HANA output control.
Procedure
1. Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
○ Configure Your Solution:
Log on to the SAP Fiori Launchpad in the SAP S/4HANA Cloud system as a Configuration Expert -
Business Process Configuration (SAP_BR_BPC_EXPERT).
Navigate to Manage your Solution Configure Your Solution
Search for the following configuration activities and create the required settings:
Assign Email Templates.
Under Actions, choose Configure.
○ SAP Central Business Configuration:
Log on to the project experience in SAP Central Business Configuration.
In the Realize phase, navigate to the Configuration Activities tab and search for the following activity: Assign
Email Templates.
Choose the line item in the search result to see more details about this configuration activity.
Choose the Go to Activity button to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP
Fiori launchpad as a Configuration Expert - Business Process Configuration (SAP_BR_BPC_EXPERT).
2. Select New Entries and enter the following information:
Field Value
Note
This is the name of the form you created in the previous
section.
You've assigned the custom form template to the billing document output type. You can now use it for further
customizing of billing documents.
This section is only relevant for business applications using SAP S/4HANA output control.
In the Output Parameter Determination SAP Fiori app, you're creating business rules to define how a custom form
should be used in general.
Note
Procedure
Note
The Decision Table is processed sequentially. This is why the table entry list starts with the most specific
entries, which are followed by more general ones.
○ To add a new entry to the Decision Table, choose (Insert New Row).
9. In the Output Type column, choose (…) for the new entry.
10. Enter BILLING_DOCUMENT in the pane that opens directly under the row (or select it via the value help icon).
11. Choose OK.
12. To find the form template name column, scroll to the right.
13. Choose " ".
Result
You've created a business rule to define when a custom form template should be used.
In this section, we will show you how you can change elements on the master form template depending on
variables from the content form template. In this example, the footer of the purchase order form is changed
depending on the purchasing group.
Prerequisites
● You have the necessary authorization to download the predelivered standard content form template for
purchase order via the Maintain Form Templates app.
● You've installed Adobe LiveCycle Designer locally.
Procedure
if ( this.rawValue == "001" )
then
//Set footer block 1 on first page (always available)
xfa.resolveNode("#pageSet[0].mst1.frmFooter.frmFooterBlock_1.txtLine") =
Form.frmHiddenStaticTexts.lblFooterForPurchaseGroup_001.rawValue
//Set title on subsequent pages (if available)
var pageCount = xfa.layout.pageCount();
if (pageCount > "1")
then
xfa.resolveNode("#pageSet[0].mst2.frmFooter.frmFooterBlock_1.txtLine") =
Form.frmHiddenStaticTexts.lblFooterForPurchaseGroup_001.rawValue
endif
else
//Set footer block 1 on first page (always available)
xfa.resolveNode("#pageSet[0].mst1.frmFooter.frmFooterBlock_1.txtLine") =
Form.frmHiddenStaticTexts.lblFooterForPurchaseGroup_Other.rawValue
//Set title on subsequent pages (if available)
var pageCount = xfa.layout.pageCount();
if (pageCount > "1")
then
xfa.resolveNode("#pageSet[0].mst2.frmFooter.frmFooterBlock_1.txtLine") =
Form.frmHiddenStaticTexts.lblFooterForPurchaseGroup_Other.rawValue
endif
endif
16. Test your form either by following KBA 2825919 to download form data XMLs or by uploading the form to
the system and generating output for different purchase groups.
Result
You've successfully modified the first footer block of the master form template via a script which evaluates an
application specific field (purchasing group).
In this section, you add a custom field to a content form template. In this example, a comment field is created in the
Manage Purchase Contracts app. This field is included in the content form template in Adobe LiveCycle Designer
and printed on the purchase contract.
● You have the necessary authorization to download the predelivered standard content form template for
purchase contracts via the Maintain Form Templates app.
● You've installed Adobe LiveCycle Designer locally.
● The necessary (key user and purchaser) authorizations and roles have been assigned to your user. This
ensures that you can access the Manage Purchase Contracts app and the Custom Fields and Logic app.
Use
In this section, you display the custom field on a PDF file using the example of the Manage Purchase Contracts app.
Prerequisites
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options to
check the status:
You might have to create another purchase contract and maintain a text for the new custom field (enter a quick
note) to make sure that the new form template is assigned to your business rules.
Procedure
Result
You've successfully extended a standard form template and added a custom field which is output in a PDF.
In this section, you create a custom text field that is added to an SAP Fiori app. In this example, we use the
Purchasing Document as business context.
Note
Procedure
Field Value
Identifier YY1_QuickNote_PDH
Type Text
Length 20
Before you continue, make sure that the custom field has the status Published.
In this step, you add the custom text field to an SAP Fiori app. In this example, you use the Manage Purchase
Contracts app. First of all, you create a new purchase contract. Afterwards, you add the field to the maintenance
view.
Procedure
Field Value
Valid To Date
Field Value
Material TG10
7. Choose Add.
8. Save your changes.
Note
An alternative way to create a custom field is to choose Create Custom Field. This button redirects you to
the Custom Field and Logic app. The advantage is that by using the app itself, the business context is
automatically selected.
Prerequisites
● You've downloaded the predelivered standard content form template for purchase contracts
(MM_PUR_PURCHASE_CONTRACT; English language) via the Maintain Form Templates app.
● You've extracted the downloaded entity.zip file locally.
Procedure
Note
Alternatively, to add a text field (or other field forms), go to the Object Library on the right side of the
screen. Drag and drop a text field to the Design View. To make sure that the relevant content is displayed,
modify the attributes on the Object tab. Refer to the example below.
7. Make sure that you maintain the attributes for the custom field appropriately to display data. Refer to the
following example for attributes that are maintained on the Object tab:
○ On the Field tab, you can adapt the caption of the field or modify the appearance. Enter, for example,
Quick Note, and maintain None for Appearance.
○ On the Value tab, you can provide the respective type, for example, User Entered – Optional.
○ On the Binding tab, you can provide the name of the data binding for the field, for example,
YY1_QuickNote_PDH.
1. Choose the Data Binding icon.
2. Go to Use "Data Connection" ContractHeaderNode .
3. Select the desired data binding (in this case YY1_QuickNote_PDH).
4. In the Binding Properties dialog window, do not choose Update all related properties.
5. Choose OK.
6. The data binding shows now as $.YY1_QuickNote_PDH.
8. Save your changes.
The purpose of this task is to create customer-specific email templates based on the templates provided by SAP.
Activities include copying an SAP email template, modifying its content, and defining business rules for its usage.
SAP delivers standard email templates for many business applications.
You can create a new email template and adapt it using the Maintain Email Templates app. In the next step, you
assign this email template to a business rule.
Procedure
Result
This section is only relevant for business applications using SAP S/4HANA output control.
1. Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
○ Configure Your Solution:
Log on to the SAP Fiori Launchpad in the SAP S/4HANA Cloud system as a Configuration Expert -
Business Process Configuration (SAP_BR_BPC_EXPERT).
Navigate to Manage your Solution Configure Your Solution
Search for the following configuration activities and create the required settings:
Assign Email Templates.
Under Actions, choose Configure.
○ SAP Central Business Configuration:
Log on to the project experience in SAP Central Business Configuration.
In the Realize phase, navigate to the Configuration Activities tab and search for the following activity: Assign
Email Templates.
Choose the line item in the search result to see more details about this configuration activity.
Choose the Go to Activity button to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP
Fiori launchpad as a Configuration Expert - Business Process Configuration (SAP_BR_BPC_EXPERT).
2. Choose Add in the upper right corner.
3. In the Assign Form Templates window, enter the following information:
Field Value
Note
This is the name of the email template you've created in
the previous section.
Result
You've assigned the custom email template to the billing document output type. With this, the email template can
now be used for of billing documents.
This chapter is only relevant for business applications using SAP S/4HANA output control.
In this step, you're assigning an email template to a business rule. This allows you to send application documents
automatically to business partners using the assigned email template.
Procedure
Result
This section is only relevant for business applications using SAP S/4HANA output control.
This section provides you with more details on how to define rules for the determination of content forms.
You can define default output settings for specific business objects, for example, for billing documents or purchase
orders. Technically, you're creating and maintaining business rules in BRFplus decision tables. These rules are used
to determine the output parameters of specific business objects. An output parameter is, for example, an output
channel, a recipient, or a form template.
Example
The example is based on a purchase order (PO) context. The output is created in the Manage Purchase Orders SAP
Fiori app.
● the company-wide content form template for purchase orders (default layout). Alternatively, you can use the
predelivered standard output form template.
● custom content form templates with specific layouts/content for purchase orders.
For example, if output for purchase orders is created, you want to use custom templates that are used when
the following rules are applied:
○ POs with certain sender country
○ POs with certain supplier
○ POs without any specific criteria
Procedure
Note
○ Each rule consists of several determination steps that are connected to specific parameters. If you
leave a column in the decision table blank, any value is deemed to satisfy the condition.
Note
11. Once you've successfully created the rules, leave the Edit mode.
12. To check object consistency and to activate the object for productive use, choose Activate.
13. In the Confirm Activation window, choose YES to activate it.
A success message is displayed.
Result
For testing purposes, you can now select a purchase order whose attributes match a certain rule within the Manage
Purchase Order SAP Fiori app. Go to the Output section and choose the icon in the Display column.
A PDF document is displayed in a new window. It contains your corresponding custom content form.
Note
The determination of rules is only processed once while the document is being created. If you change the rule,
existing documents aren’t affected by it. The changes apply only to new documents.
Each determination step within the output parameter determination is technically represented by a decision table.
This table consists of a table definition and the content (the business rules). This section gives you an overview of
possible changes of the table definition.
You reach the table definition from within the dialog where you maintain the business rules for a determination
step. Select Table Settings to show the current settings. When you are in edit mode, you can also change the
settings.
By default, you can only adjust the condition columns. All other settings are predefined by SAP and must not be
changed. The system runs a consistency check when activating the decision table and inconsistent settings
prevent activation.
Section Result Data Object: The only relevant setting here is Return all matches found. This indicates whether the
table returns a single match (when unchecked) or all matches (when checked) when processing the business rules.
All other settings can be ignored.
Section Condition Columns: Each condition column represents a single parameter of your business rules. SAP
predelivers a set of columns. You can change this default by adding or deleting columns.
This section provides you with more details on how to add a column to the decision table used for the
determination of the output channel. The shown principle applies to all decision tables. Adding a column to existing
rules is safe, as the default value for the new column is always Any Value (empty). Only if you mark the new column
as mandatory, you need to adjust the existing rules.
Applications provide a set of default attributes from which new columns can be selected. It’s also possible to
extend this list with custom fields, if the business application enabled standard extensibility for the underlying CDS
view. If in doubt, please check the application-specific documentation.
Example
Procedure
Note
The option From Expression is technically not supported. Do not use it.
9. A popup appears, listing all available data objects for this decision table.
You can decide to move it to another position or to mark it as mandatory. In this example, we leave it at the end
as an optional parameter.
12. Choose OK to apply the changes and to get back to the decision table.
Result
You've successfully enhanced the business rules for output determination with a new parameter.
For testing purposes, you can now select a purchase order whose attributes match a certain rule within the Manage
Purchase Order SAP Fiori app. Go to the Output section and check the output channel.
This section provides you with more details on how to remove a column from a decision table used for the
determination of the output channel. However, the shown principle applies to all decision tables. Removing a
Example
Procedure
Result
You've successfully removed a parameter from existing business rules for output determination.
For testing purposes, you can now select a purchase order with attributes that match a certain rule within the
Manage Purchase Order app. Go to the Output section and check the output settings.
The change should not lead to a different result, as there is only one output type for purchase order. With this
change, we simplified the existing rules but did not change the business logic behind it.
This section provides you with more details on how to extend the structure Condition Parameters of Application
with additional fields.
The structure Condition Parameters of Application in output parameter determination, is technically bound to a
CDS view. This section shows you how to identify the name of the underlying CDS view and check whether it's
extensible.
Example
Procedure
Note
When a context menu isn't shown with a right-click, check the Optimized for Touch Input settings on your
SAP Fiori launchpad and disabled it. You can change the settings via Settings Apperarance Display
Settings .
5. Select Get technical details for Condition Parameters of Application from the context menu.
6. The system shows you that the CDS view can be extended.
7. Note down the name of the CDS view (C_BILLINGDOCUMENTOMPARAMDET).
Result
You've identified the underlying name of the CDS view for Condition Parameters of Application and know that the
CDS view can be extensible.
When the CDS view is extensible, you can use the standard extensibility features (app Custom Fields & Logic) to
enhance it.
When the underlying CDS view Condition Parameters of Application are extensible, you can add additional fields.
Afterwards, you need to refresh the structure Condition Parameters of Application in Output Parameter
Example
Procedure
Note
When a context menu isn't shown with a right-click, check the Optimized for Touch Input settings on your
SAP Fiori launchpad and disabled it. You can change the settings via Settings Apperarance Display
Settings .
5. Select the Refresh Condition Parameters of Application option from the context menu.
6. Confirm the dialog box.
7. The system notifies you about the success of the update.
8. Select Output Type from the Determination Step dropdown list.
9. Switch to edit mode by choosing Edit.
10. Choose Table Settings to open the table settings dialog.
11. Under Condition Columns, choose Insert Column.
12. From the dropdown, choose From Context Data Objects.
13. A dialog box appears, listing all available data objects for this decision table.
14. Under Condition Parameters of Application, your newly added fields are displayed.
Result
You've successfully updated the Condition Parameters of Application structure, and you verified that the newly
added fields are available for usage.
Note
You currently have to perform the updates of the structure in each system separately. There's no transport
from quality system to productive system.
This chapter is only relevant for business applications using SAP S/4HANA output control.
This is a general description of the process you use to define rules that determine the master form template. Each
time a document (using a form template of the Content type) is output by the end user in an application, these
rules identify the master form template that is to be used.
This section provides you with more details on how the logical framework is used to resolve to a master form
template when, for example, a purchase order has certain business attributes that match one of the rules.
Example
The example is based on a purchase order (PO) context. The output is created in the Manage Purchase Orders app.
Procedure
1. Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
Configure Your Solution:
Log on to the SAP Fiori Launchpad in the SAP S/4HANA Cloud system as a Configuration Expert - Business
Process Configuration (SAP_BR_BPC_EXPERT).
Navigate to Manage Your Solution Configure Your Solution . On the Configure Your Solution: Realize Phase
screen, search for Define Rules for Determination of Master Form Template and select the result. Select
Configure for the configuration step.
SAP Central Business Configuration:
○ Log on to the project experience in SAP Central Business Configuration.
○ In the Realize phase, navigate to the Configurations tab.
○ Set the relevant search filters, to find the Master Form Template Determination configuration activities.
○ In the Configuration Activities section, select the Define Business System Type configuration activity.
Choose Go to Activity to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori
launchpad as a Configuration Expert - Business Process Configuration SAP_BR_BPC_EXPERT.
2. Enter Master in the Search Input Text smart field and choose Enter.
3. Choose Start in the Master Form Template Determination row.
Note
○ To ensure that the correct master form templates are used, create one rule for each use case and one
company-wide rule.
○ Since the company-wide rule should be generic, most of the parameters are left blank.
○ Assign an ordinal number to each rule according to the priority (the lower the number, the higher the
priority). Whenever an output process is triggered, the master form template is determined by
comparing the defined rules in their numerical order with the data provided by the application. As a
consequence, lower numbers should be assigned to more specific rules. If you want to have rules that
have the same priority, assign the same numbers to them. However, you must enter at least one
different parameter, for example, the organization unit ID. Otherwise, you would be creating identical
rules.
○ The comparison process starts with the rule with the lowest number, that means with the most specific
rule. If not all parameter conditions are met, the comparison process moves on to the rule with the next
lowest number. The comparison process continues until a rule is found with all parameters matching
the data. The determination process is complete and the master form template specified in this rule is
used for output.
○ Each rule consists of several parameters. Some of the parameters are optional. If you leave the relevant
fields blank, any value is deemed as satisfying the condition.
○ POs with certain Org. Unit type + Org. unit ID (Rules ZRULE_ORG_1010 and ZRULE_ORG_3010)
In the example above, you're specifying that the master form template is used for Org. Unit Type : EKORG
and Org. Unit ID: 1010.
You can also create another document with the same ordinal number (for example, with Org. Unit Type :
EKORG and Org. Unit ID: 3010).
○ POs with certain Org. Unit Type(Org ID is, for example, 1710) (Rule ZRULE_ORGID_1710)
○ POs with certain Country, for example Australia (AU).(Rule ZRULE_COUNTRY_AU)
Result
For testing purposes, you can now select a purchase order whose attributes match a certain rule within the Manage
Purchase Order SAP Fiori app. Go to the Output section and choose the icon in the Display column.
A PDF document is displayed in a new window. It contains your corresponding custom master form.
The following steps describe how you can transport your custom form templates, e-mail templates, texts, and
logos from your quality system to your productive system. To achieve this, these custom extension items need to
be added to a software collection in the quality system so that they can be exported to the productive system.
It’s very important that you transport the custom objects before you transport the customizing that
references to these objects.
For example: First, transport the custom form template to the productive system. Second, transport the settings of
the Assigning Form Templates and Output Parameter Determination activities.
Procedure
1. Log on to your SAP Fiori launchpad of your SAP S/4HANA Cloud quality system.
2. Open the Export Software Collection app.
3. Choose + (Create Software Collection) on the lower left part of the screen to create a software collection. You
can also add items to the default collection.
4. Enter a name, for example, Extension Collection.
5. Select Extension Collection on the left side of the screen and choose Add Items to add the necessary extension
items.
6. In the Add Items dialog box, select the checkboxes for the following items and choose OK to add them to the
software collection:
○ Email Template
○ Form Template
○ Form Template Logo
○ Form Template Text
Note
From the list of items included in the software collection, select Check to check for any existing
inconsistencies and dependencies.
7. Choose Export to export the software collection and transport the extension items you added to the software
collection.
Procedure
1. Log on to your SAP Fiori launchpad of your SAP S/4HANA Cloud productive system.
2. Open the Import Software Collection app. A number should be displayed on the app tile denoting the software
collections ready to be imported.
3. Go to ExtensionCollection in the Version section. Make sure that the status is Ready for Import.
4. Select the collection and choose Import.
5. Confirm the Import Version dialog box. Choose Import.
6. Once the import has finished, you see a green success message and the Import Software Collection
DetailsStatus: Imported screen.
7. Choose OK.
Currently, there's no automation for transferring changes to decision tables and business rules from quality system
to production system.
You've to manually redo all changes to decision tables in the productive system.
For example, if you added or removed columns, you need to perform the same steps in the productive system.
This must be the first step you perform, before you start transferring the business rules.
Business rules can be transferred using the features Export to Excel and Import from Excel. With these features, you
can download all business rules of a decision table in the quality system to an excel file. Then, you can upload the
rules from this excel to the production system. Currently, you need to perform the steps per decision table.
This section provides you with more details on how to export the defined rules for a determination step. Perform
these steps in the quality system.
Example
Procedure
Result
You've successfully exported the business rules of the selected determination step to an excel file.
This section provides you with details on how to import the defined rules for a determination step. Perform these
steps in the productive system.
Make sure you performed all changes, if any, to the table columns first, before you start this step. If table columns
aren't exactly the same, the import fails.
Example
Result
You've successfully imported the business rules of the selected determination step from an excel file.
This section provides you with more information on business rules for master form templates, the output
parameter determination, and output with attachments.
This chapter is only relevant for business applications using SAP S/4HANA output control.
Some business applications, like billing documents, allow you to select attachments for output along with the main
document (rendered form).
Depending on your use cases and the selected output channel, the file types of the attachments are important.
6.1.1 Printing
If you want to send the main document and attachments to a printer using the Cloud Print Manager, you should
select only file types which can be natively understood by a printer (like TXT or PDF). The system would then add
the selected files to the print queue item, which you can view as well in the Maintain Print Queues app.
In the Cloud Print Manager, you need to enable attachments when mapping the print queue to the printer. This can
be done by selecting option Print PDF Attachments in the Output Options of the Cloud Print Manager.
If you do not actually want to print the documents but store them in a file directory, there is no restriction to the file
types. In this case, enable the option Save Attachments in the Cloud Print Manager. This can be done by selecting
option Save PDF Attachments in the Output Options of the Cloud Print Manager.
6.1.2 Emailing
For the channel EMAIL, there is no restriction on the file type. All selected files are added to the generated email
along with the main document.
There can be, however, restrictions on the receiving side about the accepted file types and file sizes.
When selecting an attachment for the output, you can also decide whether the selected documents can be merged
with the main document.
Moving an attachment from the section Available Attachments to the section Merge with Form Template, results in
merging the chosen attachment along with the main output document. The attachments selected for merge aren't
attached separately to the output.
Note
The merging of documents occurs during rendering, so a preview shows the newly merged document as well.
Merging is done in the order of the selected attachments in the list.
After the output, the merged document is treated as the final main output document (auditable document).
Therefore, while issuing an output for a duplicate item, the merge option isn't available as this could create a
document that differs from the original document. It also means that you aren't able to unmerge the document
once the final document is saved.
When you have the requirement to use a custom font in your rendered form outputs, you can use the Adobe
Document Services Configuration app to maintain configuration artifacts for your Adobe Document Services
service.
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you
agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.