Skip to Content
Personal Insights

SAP S/4HANA Output Management (1LQ): single-tenant and multi-tenant

Thanks for stopping by!

I wanted to write a quick blog that covers a few topics that fall under the 1LQ – Output Management scope item for SAP S/4HANA single-tenant and multi-tenant. My goals are to keep this blog high level while offering valuable insight that could support any SAP user during his/her journey. As always, I will attach links to more detailed information covering each of the below topics. Enjoy!

 

Output Control

Single-Tenant

  • Output Configuration in single-tenant can be managed in a few different ways. While these ways may vary for each application object, the concept is the same. Single-tenant allows users to configure output management via NAST or utilize BRF+ technology via API/FIORI app Output Parameter Determination.
  • NAST and Output Parameter Determination (BRF+) are not 1:1. OPD does not replace NAST and is not comparable in scope.
  • You do not have to use the Output Parameter Determination for output configuration.
  • Not all application objects are available in Output Parameter Determination and therefore will need to be configured separately via the appropriate application object’s output control.
  • All existing output management solutions for SD Output Control, FI Correspondence, and FI-CA Print Workbench are still supported.

Multi-Tenant

  • Output Configuration in multi-tenant can be configured only using the Fiori application Output Parameter Determination.
  • There is no NAST in multi-tenant.

 

For more information on this topic, check out the below blogs.

BRF+ Output Managementhttps://blogs.sap.com/2019/12/18/brf-output-management/

 

Forms

Single-Tenant

  • Applications in single-tenant use SAP Cloud Platform Forms by Adobe as the standard form technology.
  • Still offer existing form templates from Business Suite which are implemented via SAPScript, SmartForms or SAP Interactive Forms By Adobe (SIFbA).
  • Output Parameter Determination (BRF+) can only use Adobe Forms (other forms will need to be converted if utilizing BRF+).
  • Customers can modify pre-delivered forms templates or create their own forms from scratch using Adobe LiveCycle Designer

Multi-Tenant

  • Applications in mult-tenant use SAP Cloud Platform Forms by Adobe as the standard form technology.
  • Developers must use SAP pre-delivered adobe form templates.
  • Unable to build custom forms from ground up (must use a pre-delivered template).
  • Users can customize the Master and Content form templates.
  • Output control for forms is maintained via Fiori application Output Parameter Determination.
  • Field extensibility and custom logic are available for most business contexts.

For more information on this topic, check out the below blogs.

SAP S/4 Hana Cloud: Testing Form Developments in Adobe Livecycle Designer – https://blogs.sap.com/2019/07/24/sap-s4-hana-cloud-testing-form-developments-in-adobe-livecycle-designer/

Output Management – Customize Content Form for Outgoing Check – https://blogs.sap.com/2017/11/24/output-management-customize-content-form-for-outgoing-check/

 

 

Email

Single-Tenant

  • SMTP is configured and managed by the customer.
  • Sending emails requires defining allowed email domains and sender and recipient email addresses.
  • You can create custom email templates with a custom email body and subject line.
  • Custom email templates are based on SAP-delivered templates.

Multi-Tenant

  • SMTP is managed by SAP.
  • You can create custom email templates with a custom email body and subject line.
  • Custom email templates are based on SAP-delivered templates.
  • Sending emails requires defining allowed email domains, sender and recipient email addresses

For more information on this topic, check out the below blogs.

Output Management – Customize Email Form for Payment Advice – https://blogs.sap.com/2018/02/03/output-management-customize-email-form-for-payment-advice/

Printing

Single-Tenant

  • Single-tenant uses Spool Administration as known from the business suite.
  • Front-end printing is not supported.
  • Unattended/attended printing available.

Multi-Tenant

  • Multi-tenant uses SAP Cloud Print Manager for printing.
  • Unattended/attended printing available
  • LOCL is not available.

For more information on this topic, check out the below blogs.

SAP S/4 Hana Cloud Print Capabilities: Your guide to printing in the cloud – https://blogs.sap.com/2019/08/14/sap-s4-hana-cloud-print-capabilities-your-guide-to-printing-in-the-cloud/

Cloud Print Manager – Installation and Configuration – https://blogs.sap.com/2017/08/07/cloud-print-manager-installation-and-configuration/

 

1LQ Output Management Documentation – Setting up Output Management

Single-tenant https://support.sap.com/content/dam/SAAP/Sol_Pack/Library/Setup/1LQ_S4HANA1909_Set-Up_EN_XX.pdf

Multi-tenant – https://support.sap.com/content/dam/SAAP/Sol_Pack/Library/Setup/1LQ_Set-Up_EN_XX.pdf

 

Thanks for reading and please be sure to like, share and comment.

Until next time..

 

 

4 Comments
You must be Logged on to comment or reply to a post.
  • This is Good

    Single-Tenant

    • Applications in single-tenant use SAP Cloud Platform Forms by Adobe as the standard form technology.
    • Still offer existing form templates from Business Suite which are implemented via SAPScript, SmartForms or SAP Interactive Forms By Adobe (SIFbA).
    • Output Parameter Determination (BRF+) can only use Adobe Forms (other forms will need to be converted if utilizing BRF+). mp3 ytb
    • Customers can modify pre-delivered forms templates or create their own forms from scratch using Adobe LiveCycle Designer
  • Single-Tenant

    • SMTP is configured and managed by the customer.
    • Sending emails requires defining allowed email domains and sender and recipient email addresses.Medium
    • You can create custom email templates with a custom email body and subject line.
    • Custom email templates are based on SAP-delivered templates.
  • Single-Tenant

    • Output Configuration in single-tenant can be managed in a few different ways. While these ways may vary for each application object, the concept is the same. Single-tenant allows users to configure output management via NAST or utilize BRF+ technology via API/FIORI app Output Parameter Determination.
    • NAST and Output Parameter Determination (BRF+) are not 1:1. OPD does not replace NAST and is not comparable in scope.
    • You do not have to use the Output Parameter Determination for output configuration.
    • Not all application objects are available in Output Parameter Determination and therefore will need to be configured separately via the appropriate application object’s output control.
    • All existing output management solutions for SD Output Control, FI Correspondence, and FI-CA Print Workbench are still supported.

    http://tiendabeyond.com

    https://www.wired.com/2000/10/p2p-pages

    http://axe6.tripod.com

    http://m.nettime.org/Lists-Archives/rohrpost-0010/msg00002.html

    https://support.google.com/youtube/answer/6083754?hl=en

    https://www.youtube.com/user/jpelirrojo

    https://mp3ytb-76.webself.net/