Skip to Content
Product Information
Author's profile photo Markus Berg

Output Management in SAP S/4HANA

Many customers and partners seek guidance for output management in SAP S/4HANA. With this blog I would like to provide an overview and hopefully answers to typical questions.

After reading this blog you should be able to take decisions about the right output solution for your business when running on SAP S/4HANA.

For Quick Readers

This article turned out to be very long. When you are just interested in the key messages, here you go:

For SAP S/4HANA 

  • You do not need to change anything.
  • SAP offers a new output solution called SAP S/4HANA output management.
  • This is technically implemented by a reuse service called SAP S/4HANA output control.
  • The scope of SAP S/4HANA output control is different compared to NAST.
  • Using SAP S/4HANA output control for applications previously using NAST currently makes sense only in exceptional cases.

For SAP S/4HANA Cloud

  • SAP S/4HANA output management is the default output solution for the whole product.
  • It’s technically implemented by a reuse service called SAP S/4HANA output control.
  • All business applications with complex output scenarios make use of this reuse service.

For all SAP S/4HANA editions

The following features are not yet supported when using SAP S/4HANA output management:

  • Integration of external output management systems (3rd party OMS)
  • Integration of external content management systems (e.g. OpenText ECM)
  • Support of ArchiveLink or DMS for documents created during output

The following features are supported (excerpt)

  • Flexible output parameter determination based on business rules
  • Emails with multiple recipients (TO, CC, BCC) and email templates for predefining email subject and email body (including variables for dynamic content)
  • Printing attachments and sending attachments via email, including automatic selection and sorting
  • Flexible branding of print forms by separating static layout parts like header, footer, logos from application content

What is Output Management?

When you ask people from different business or technical areas what output management is, you get different answers. You will hear something around PDFs, printing, form templates or email, just to name a few. However, it will always be a description of what output means in their particular area. So, everybody interprets it a little different. Some need just one small feature, others need whatever can be offered (and even more).

This is how I look at it: Output Management in SAP S/4HANA is not a product or a framework. It’s a generic term, grouping various features for the output of documents.

The term also includes already two main aspects:

When describing features like print, form templates or email, you actually describe just the first part: Output (meaning output-related features).

What about the Management ?

Depending on the use case, managing output can also vary a lot. It can describe that the application is orchestrating all different output features on its own. It can mean an application is using a dedicated reuse service for output. It’s even sometimes used when an application just consumes an API to send an email.

What is Output Control?

 

So, it comes down to the question: How many output features are there to be managed?

And secondly: What are the available options to manage my output?

Simple cases like sending an email or creating a PDF file out of a list don’t need sophisticated management.

However, when you need to automatically determine output parameters based on configuration, create documents based on form templates, send them via various output channels and require archiving the created documents, you face very complex tasks.

Therefore, many business applications with such complex output scenarios make use of a reusable output service that includes many basic features for the output of documents and adds specific functionality on top. 

Typical examples of such a service are: SD Output Control (NAST), FI Correspondence, FI-CA Print Workbench, CRM Post-Processing (PPF) or SAP S/4HANA output control.

Output Management and Output Control

As the picture above illustrates, Output Control is always part of Output Management. For many applications they are even synonyms. However, Output Management must not necessarily be done using Output Control.

 

What’s New in SAP S/4HANA?

What I described so far is nothing new and SAP has provided multiple technical solutions for output over the years. So, what actually changes with SAP S/4HANA?

The key message is:

  • There are no mandatory actions for customers regarding output management in on-premise.
  • The entire output management scope of the SAP Business Suite is still available
    in SAP S/4HANA.
  • Currently, there are no plans to deprecate functionality.
  • SAP has introduced a new output management solution which is optional for on-premise.

You as a customer/partner decide whether you want to change something or just continue using your existing output solution!

What’s actually new is the output solution SAP S/4HANA output management.

SAP S/4HANA Output Management

SAP has decided to offer a new output solution with SAP S/4HANA called SAP S/4HANA output management. It contains the reuse service SAP S/4HANA output control that is used for many complex output scenarios.

Please do me a favor and do NOT use the terms “Output Management based on BRFplus” or “BRFplus Output Management”. In fact, forget about BRFplus in this context at all.

Why? BRFplus is an optional part and only used for configuration (similar to the condition technique in NAST), not for processing the output. NAST is also not referred to as the “Condition technique based output management”.

You might also end up connecting with BRFplus experts, but they likely will not be able to answer your output-related questions.

 

Why a New Output Solution?

 

The vision of SAP S/4HANA output management is to

Enable business users to perform all relevant output-related tasks

In order to reach this vision, the existing output solutions like NAST, PPF etc. have been evaluated. However, they are either too generic and/or only available in certain business areas.

Customers have to learn, set up and maintain multiple frameworks in order to perform output. This creates high TCO and very different user experiences across the product.

Therefore, SAP has decided to implement a new output solution that overcomes these challenges.

The SAP S/4HANA output management.

Its main characteristics are:

  • It runs in a cloud or an on-premise environment.
  • It offers a unified solution for all output-related tasks across the product.
  • It supports ready-to-use output scenarios (pre-delivered configuration).
  • It supports standard extensibility for configuration & documents (form & email templates).
  • It provides central monitoring tools for key users.

 

SAP S/4HANA Output Control

SAP S/4HANA output control is a reuse service that provides many basic output features and adds additional functionality on top.

Its main characteristics are:

  • It offers a unified solution for all output-related tasks across the product.
  • It can be natively integrated into SAP Fiori apps (and SAPGUI apps).
  • It provides a new option for form templates (separation of static layout & content).
  • It supports ready-to-use output scenarios (pre-delivered configuration).
  • It supports standard extensibility for configuration & documents (form & email templates).
  • It provides central monitoring tools.
  • It runs in a cloud or an on-premise environment.

As you see, some of the characteristics are identical to the ones of SAP S/4HANA output management. That’s because these goals can only be reached when using a reuse service like SAP S/4HANA output control.

Scope of Output Control

It’s very important to understand what’s in the scope of output control as it might differ from your expectation when comparing it to existing frameworks like NAST. (You find a more detailed comparison with NAST below).

Output control is designed for:

  • Sending outbound messages (e.g. printouts, emails, EDI)
    • From transactional applications
    • To business receivers
  • Documenting the output result

This does not include:

  • System integration scenarios
  • Data replication scenarios

Its design is also document centric. Meaning it’s not a standalone functionality but is always embedded into the processing of business documents, like invoices, purchase orders, dunning letters, etc.

Available Options

So now you know there are multiple output solutions from SAP (including a new one). Which one should I choose? Which one can I use? What about my existing forms?

These kinds of questions can only be answered when we know the specific context.

  1. Which SAP S/4HANA product are we looking at?
  2. Which business application are we looking at?
  3. Which output solution are available for that business application?
  4. Which form technologies are available for that output solution?

As you can see, these points depend on each other, like also the following picture illustrates:

Available options across all SAP S/4HANA editions

 

Depending on where we put our focus, more or less options exist.

Here are some examples:

When we focus on the products SAP S/4HANA and SAP S/4HANA Cloud, private edition it seems you have nearly all the options. However, when you drill down further, not all options might actually be available for each business application.

Available options in SAP S/4HANA and SAP S/4HANA Cloud, private edition

 

For example, when you just focus on the output solution SAP S/4HANA output control within the product SAP S/4HANA, you will not be able to use this output solution in all the business applications. You can still use all existing form technologies though.

Available options in SAP S/4HANA with SAP S4/HANA output control

 

However, when you focus on a non-NAST-based application, like Dunning, you are only able to use  output forms with a gateway interface when using output solution SAP S/4HANA output control.
The reason for this: For previously NAST-based applications the SAP S/4HANA output control has a build-in support for all existing form technologies. All other applications need to explicitly enable the support of these form technologies.

You can decide whether to use SAP Interactive Forms by Adobe or SAP Forms service by Adobe to render your output forms.

Available options in SAP S/4HANA with SAP S4/HANA output control for Dunning

 

When you focus on the NAST output solution you get a similar picture on application level, but you will not be able to use output forms with a gateway interface as NAST is in maintenance mode and not adopted to this new technology.

You can decide whether to use SAP Interactive Forms by Adobe or SAP Forms service by Adobe to render your output forms with DDIC interface.

Available options in SAP S/4HANA with NAST

 

 

In SAP S/4HANA Cloud, all business applications can use only the output solution SAP S/4HANA output control. Also, only output forms with a gateway interface are supported which get rendered by SAP Forms service by Adobe.

Here, the vision of one output solution for the whole product is already realized.

Available options in SAP S/4HANA Cloud

 

Getting Directions

I guess there are still many question marks. So, let me try to break it further down.

The first thing to remember is: There are no mandatory actions necessary for on-premise. The existing output solutions still exist, and you can continue to use them. They are even the default in SAP S/4HANA.

When you want to explore output with SAP S/4HANA output management, you need to know whether there is an option to enable this output solution.

Basically, two cases need to be considered:

  1. The business application existed before SAP S/4HANA (and therefore has an existing output solution from the past).
  2. The business application is (newly) implemented with SAP S/4HANA (and has no existing output solution).

The following tables illustrate the available options for both cases:

Output solutions for existing business applications

 

Output solution for new business applications

 

So, you see, it’s up to the individual business application whether you can choose between different output solutions and whether you can use SAP S/4HANA output control or not.

However, you will still be in touch with output control when your scope includes new business applications that only offer SAP S/4HANA output control.

Of course, this also means that at least in on-premise it will add another output solution to maintain as long as not all applications are harmonized to offer one solution.

 

Should I Switch from Existing Output Solution to SAP S/4HANA Output Control?

 

After you know you can switch to SAP S/4HANA output control, should you do that?

My view:

  • It is not mandatory for customers to switch to SAP S/4HANA output control.
  • Default is still the existing output solution.
  • The scope of SAP S/4HANA output control includes output-only functionality.
  • Switching business applications from specialized or generic frameworks to SAP S/4HANA output control might lead to loss of functionality.
  • Customers can test out SAP S/4HANA output control for existing applications.
  • Productive usage shall only be considered if scope and functionality of SAP S/4HANA output control fits to the customer requirements.

Output only? Loss of functionality? What does this mean? 

Let me explain by comparing the NAST with SAP S/4HANA output control.

NAST vs. SAP S/4HANA Output Control

 

When we look at NAST, we find a generic framework that can be used for output but also for: Integration, Workflow and (due to the medium Special Function) for literally anything that can be implemented.

This flexibility comes with the price of very high complexity. It’s a tool from technical experts for technical experts. Nearly no customer can perform the setup of NAST without consultants. I even know customers who are afraid to touch their NAST setup once it’s running. They rather don’t add new features than risking breaking their system. If you ask me, our customers deserve better!

On the other hand, the SAP S/4HANA output control provides output functionality. Not more, not less. It’s not a generic framework like NAST and isn’t designed to be. It follows a new architecture paradigm including the separation of concerns. This pictures shows it best:

Scope%20of%20NAST%20and%20SAP%20S/4HANA%20output%20control

Scope of NAST and SAP S/4HANA output control

 

Output Channels

Even if comparing the output channels, there are some differences.

Output%20channels%20of%20NAST%20and%20SAP%20S/4HANA%20output%20control

Output channels of NAST and SAP S/4HANA output control

 

Some channels like Telex or SAP Office are obsolete, others, like External Send are not yet covered. But even the same channels as Print or Email deviate in detail. Email functionality in NAST is very limited and printing includes archiving as well. SAP S/4HANA output control offers rich email functionality but handles archiving separately.

Some Words about IDoc & EDI

I want to especially focus on IDoc & EDI here, as this is a very complex topic with many misunderstandings.

Some basics:

  • IDoc is a technical message format, not a communication channel/medium.
  • Application Link Enabling (ALE) is a technology to create and run distributed applications.
  • Electronic Document Interchange (EDI) is a technology to exchange business documents between systems.

Both, ALE and EDI, can send messages in the IDoc format, but can (in principle) use any other format as well.

Now these things need to be put into context of the corresponding frameworks.

NAST has a medium (channel) called EDI, which is limited to IDoc message format. Via medium EDI, NAST supports IDoc to business partners and IDocs for system integration (named ALE).

SAP S/4HANA output control supports IDoc to business receivers only! System integration (via ALE, EDI or whatever technology) is not part of this framework and will not be. In many cases, this doesn’t even make sense, as there receiver determination isn’t needed. The receiving end point for system integration is typically known and static. Hence, it’s actually a drawback of NAST that customers are forced to set up many things that are not needed.

Replacing the NAST Framework

 

Of course, no functionality that is covered by NAST should be lost when switching to a different output solution. However, right now no application fully covers the same functionality from NAST when the output part is switched to SAP S/4HANA output control. In most cases, the non-output-related functionality is not available in this case.

 

Conclusion

  • SAP S/4HANA output control is not designed to completely replace NAST.
  • It will only cover the output part of NAST (print, email, partly EDI).
  • The rest – like system integration, workflow, or special function – is not (and will not be) in the scope of SAP S/4HANA output control.
  • Hence, business applications need to cover these parts differently, but nearly none of them is completely achieving this at the moment.
  • Therefore, customers will lose all these features from NAST when switching on SAP S/4HANA output control.
  • This means using SAP S/4HANA output control for applications previously using NAST only makes sense in exceptional cases.
  • Only when you have verified that the current functionality of SAP S/4HANA output control matches your requirements, you should enabled it productively.

 

Additional Resources

If you’ve read the whole blog until here, you are really brave and very much interested in output management. Thank you!

Here are some more resources for you to continue reading.

SAP note 3097507 – Output Management in SAP S/4HANA

SAP Roadmap Viewer

SAP Best Practices Explorer – Output Management (‏1LQ‏)

Output Management Setup Guide cloud / on premise

SAP Help Portal – Output Control on premise / cloud

Guided Answer for Output Management in SAP S/4HANA Cloud

SAP Learning Hub – Meet-The-Expert Sessions (on premise)

Reminder:  To access the SAP Learning Hub, edition for SAP Enterprise Support, a one-time registration is required. A detailed step-by-step guidance can be found here.

 

Assigned tags

      41 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Joachim Rees
      Joachim Rees

      A very nice overview, thanks!

      Author's profile photo Imran Khan
      Imran Khan

      Thanks for this comprehensive overview. really useful.

      Regards, Imran

      Author's profile photo Jigang Zhang 张吉刚
      Jigang Zhang 张吉刚

      Thanks for sharing. So much information!

      When close to master one tool there'll be new. enjoy learning 😀

      Btw, so how do answer the questions related to NAST/BRF+ at the certification exam? haha

      Author's profile photo Joost Klijbroek
      Joost Klijbroek

      Hi Markus,

      thank you for the information on SAP OutputManagement with HANA. But I still do have some questions.

      Actually I am an SAP forms developer on ISU. We use the PrintWorkBench - usually with SAPscript/RDI -> external OMS. This is what the Utilities clients still are requesting. Sometimes they use StreamServe, sometimes DOK1 or they used to use DETEC LaserSoft as  OMS.

      Now my question: how does the forms development change in SAP S/4 HANA and/or the HANA cloud?

      Will there be the complete collection of forms development tools? Even SAPscript-scripting? What about the transactions - are they going to move to fiory(?), Eclipse or anywhere? Or will it still be in the GUI?

      What will change for PWB-forms developers?

      Thanks in advance.

      Cheers and tschüss,

      Joost

      Author's profile photo Markus Berg
      Markus Berg
      Blog Post Author

      Hello Joost,

      The Print Workbench is one existing output solution, so all things I described above apply here as well.

      • First of all, there is no change in on-premise when you continue to use PWB (this includes the form development)
      • Even when SAP S/4HANA output control would be used (when available) for applications, previously using PWB in on-premise, the form development part does not change. Simply because SAPscript Smart Forms and IFbA are in maintenance mode and will not be adapted in any way.
      • Even for the output forms with gateway interface, only the data interface changes to a gateway model. The form layout is still using the Adobe LiveCycle Designer.
      • For SAP S/4HANA Cloud, the applications already did or will do the adaption of SAP S/4HANA output control and with that only the output forms with gateway-interface exist.

      Connecting external OMS will also be possible as before in on-premise. For SAP S/4HANA output control and option will be added as well.

      Regards,

      Markus

      Author's profile photo Prabhjot Bhatia
      Prabhjot Bhatia

      Awesome blog post with compete information

      One question: on-premise version doesn't support all the applications e.g. we can't use dunning or FI correspondence to be used by S/4 HANA output.

      Is there any plans to add some new applications for on-premise system?

      Author's profile photo Markus Berg
      Markus Berg
      Blog Post Author

      Hello Prabhjot,

      From OM framework side I cannot comment on if or when which application will move to SAP S/4HANA output control in on-premise. Here you need to check with the corresponding application owners. You can be certain however that every application moving to SAP S/4HANA Cloud will need to adopt. 

      Regards,

      Markus

      Author's profile photo Joost Klijbroek
      Joost Klijbroek

      Thanks for your quick reply!

      Author's profile photo Michael Keller
      Michael Keller

      Many thanks! Great news.

      Author's profile photo Priya Shekhar
      Priya Shekhar

      Great Blog.

      Is the Delivery option supported for S/4 HANA 2020 On prem currently?

      Author's profile photo Markus Berg
      Markus Berg
      Blog Post Author

      Hello Priya,

       

      Which delivery option do you mean? SAP S/4HANA output management is available since SAP S/4HANA 1511.

       

      Regards,

      Markus

      Author's profile photo Priya Shekhar
      Priya Shekhar

      Hi Markus,

      I apologize for not being clear. We have SAP S/4 HANA 2020 on premise but the Application Object Type "OUTBOUND_DELIVERY"  is set as "Never Active" in APOC_I_OBJ_TYPEV.

      And Outbound Delivery is not available in the OPD transaction for configuration of output management.

      What we would like to achieve is to send PDF output to multiple email recipients. While this is possible via "BILLING_DOCUMENT" Application Object Type but I do not seem to find the same for Outbound Delivery document.

      Thanks,

      Priya

      Author's profile photo Markus Berg
      Markus Berg
      Blog Post Author

      No problem. Please refer to SAP note 2590037 for Outbound Delivery. As far as I know there is no change although the validity of the note might need to be extended to reflect it.

      Author's profile photo Priya Shekhar
      Priya Shekhar

      Thanks. I read this note earlier but since the last update date was way in the past, it confused me.

      Author's profile photo Markus Berg
      Markus Berg
      Blog Post Author

      I agree. Let me try to get it updated accordingly.

      Author's profile photo Priya Shekhar
      Priya Shekhar

      Hi Markus,

      Is the new output management available for Shipment Outputs in S4 HANA 2020?

      Thanks,

      Priya S Shekhar

      Author's profile photo Markus Berg
      Markus Berg
      Blog Post Author

      Hello Priya,

      SAP has just released note 3097507 which contains information about applications offering S/4HANA Output Management. Applications not listed here at all do not support it.

      Regards,

      Markus

      Author's profile photo Priya Shekhar
      Priya Shekhar

      Hi Markus,

      Thanks for the information.

      Regards,

      Priya

      Author's profile photo Peter Landwehr
      Peter Landwehr

      Hi Markus,

      thanks for this detailed overview! Still one point I am struggling with is your statement that ArchiveLink is not supported (yet). SAP help on the other hand states that "You can select the storage type ... HTTP content server" which in my mind fits ArchiveLink. We run a S/4 2020 system on premise and ArchiveLink is mandatory for us. Could you please clarify?

      Regards,

      Peter

      Author's profile photo Markus Berg
      Markus Berg
      Blog Post Author

      Hello Peter,

      The configuration you are referring to belongs to KPRO (Knowledge Provider). This is the low level component on top of GOS, DMS and ArchiveLink. All of these document services in the end use KPRO to store documents into the defined repository, but they all bring individual features on top.

      S/4HANA Output Management currently uses the low level KPRO APIs to store the documents. Hence all additional features from GOS, DMS or ArchiveLink are not available. Therefore there is no out-of-the-box support for these frameworks.

      Best regards,

      Markus

      Author's profile photo Peter Landwehr
      Peter Landwehr

      Hi Markus,

      so S/4 OM uses KPRO low level component i.e. KPRO-CMS. We did do the customizing that KPRO points to our external content server. And in fact e.g. channel email the email as well as the print pdf are saved to the content server and not on the HANA db which is good. I checked this in table SOOD. But how can the user access these documents?

      Regards,

      Peter

      Author's profile photo Markus Berg
      Markus Berg
      Blog Post Author

      Hello Peter,

      The SAP S/4HANA output control offers reusable screens for SAPGUI/WEBGUI and Fiori. Many applications, like SD Billing, make use of these screens.

      There you find a table of all outputs with the corresponding status. The action "Display Document" gives the user access to either the stored document (when the output item status is "Completed") or provides a preview when the output has not been performed.

      Regards,

      Markus

      Author's profile photo Peter Landwehr
      Peter Landwehr

      Hallo Markus,

      thanks for your answer. Based on what you said we will use S/4 OM in our on prem system. I did read in a former blog yours that only printer with device type pdf1 or pdfuc are possible. Is this still case?

      Regards,

      Peter

       

      Author's profile photo Markus Berg
      Markus Berg
      Blog Post Author

      Hello Peter,

      With release SAP S/4HANA 2021 we have some enhanced spool support.

      Supported device types

      You can choose any device type which maps to one of the following page description languages:

      • PostScript
      • PCL
      • ZPL (for Zebra label printers)
      • IPL (Intermec Printer Language)
      • TPCL (Toshiba)
      • DPL (Datamax)
      • PDF
      • CAB (for CAB label printer)

      Note:

      These are exactly the file types Adobe Document Services support as rendering formats. Hence the support is just guaranteed when using gateway-based Adobe Forms. 

      Supported access methods

      Output Control only supports access methods which represent printing as well as access method "E" for external output management systems.

      • C: Direct operating system call

      • E: External output management system

        Access Method E

        • This is not a raw data interface solution. No additional files such as XFD (XML data) or CFG (meta information) files are available.

        • Only the rendered document (this means one file of type PDF, PS, PCL, ZPL etc.) is put to the spool request. Its file format is controlled by the device type of the used spool device.

      • L: Print locally using LP/LPR

      • S: Print using SAP protocol

      • U: Print using Berkeley protocol

      Not supported features

      Note that further spool features like

      • “Output attributes” (e.g. Cover page),
      • “Tray Info”,
      • “Print Options” and
      • “Print Tickets”
      • “Printer Parameter” (e.g. Duplex)
        are not available
        .

      Best regards,

      Markus

      Author's profile photo Bernd Steinhauer
      Bernd Steinhauer

      Hello Markus,

      is it possible to define customer-specific application-object-types, in order to use the S/4HANA Outputmanagement in custom development scenarios?

      Best  Regards

      Bernd

      Author's profile photo Markus Berg
      Markus Berg
      Blog Post Author

      Hello Bernd,

      This is currently not possible. We think about offering this in the future. Then likely based on the ABAP RESTful Application Programming Model.

      Regards,

      Markus

      Author's profile photo Bernd Steinhauer
      Bernd Steinhauer

      Thank you, Markus!

      Author's profile photo Xavier PETIT
      Xavier PETIT

      Hello Markus

      Thanks so much for this complete overview on SAP Output Management in S/4 HANA. It is very helpful

      However i have also a tricky question that is coming from my partner viseo who is implementing customer project in France (Somfy)

      indeed they are currently facing a technical problem with the mail output as they wanted to create  output email for multiple recipients and in standard the system handles only one unique mail address at the partner  master data

      so in order to solve this problem they decided to use the table BRF+ dedicated in email receiver and they entered in it all the address mail of the customers (getting rid of the address mail at partner master data  !!!)

      Unfortunately it happens that this table is not able to handle for performance issue more than 10 000 entries (see oss note 2585774 - Maximum number of rows in a BRF+ Decision Table  )  and in live production this table stopped to use properly generating so many inconsistencies

      what would be your insight about his problem, is this table really shaped for email address or only for exception rules ?

      thanks

       

       

      Author's profile photo Markus Berg
      Markus Berg
      Blog Post Author

      Hello Xavier,

      Yes, the decision table is designed to be used for multiple email addresses. However, as you rightly state there is a technical limit to it.

      It would need to be evaluated how the SAP standard could better support such a use case.

      Short-term maybe only a custom solution might help in such a case.

      Regards,

      Markus

      Author's profile photo Xavier PETIT
      Xavier PETIT

      Yes indeed Markus
      May be we should use this decision table only for additional mail address (and not for all the customers)  and use as well the email address located at the partner master data
      Am i right ?

      thanks

       

      Author's profile photo Markus Berg
      Markus Berg
      Blog Post Author

      Hello Xavier,

      Since release 1709 there is definitely no need to have the default email address here. If you want to use the default email address together with others, you can just add a placeholder for it in the rules. This also allows you to use the default email address as CC and BCC instead of TO.

      So only additional email addresses need to be defined in this table. And only for customers which are relevant for the corresponding business application, not all customers.

      You find more information in the document Setting Up Output Management (1LQ)

      Chapter: Determining Email Recipients

      Regards,

      Markus

      Author's profile photo Thomas Woelfel
      Thomas Woelfel

      Thank you for the great breakdown of this functionality, very helpful!

      Author's profile photo Andreas Binder
      Andreas Binder

      Hello Markus,

      thanks for this great overview!

      I have one question, that i either didn't get to 100% or it was not described clearly... 🙂

      We are running an erp system with lots of customer adobe interactive forms with ddic interfaces, and we're actually in pre-studies on the way to S/4 HANA. So my question is, if it is basically from technical side possible, to migrate these forms easily from erp to S/4 HANA, or are there any restrictions or difficulties?  Thanks in advance!

      Best regards Andreas

      Author's profile photo Markus Berg
      Markus Berg
      Blog Post Author

      Hello Andreas,

      As stated above, for existing applications there is no change necessary. You can continue using the existing output solution including your existing forms in S/4HANA.

       

      Even when working with new applications using SAP S/4HANA output control or when you decide to switch an existing application to use SAP S/4HANA output control, there is likely no need to migrate, as SAP S/4HANA output control supports also the existing form technologies.

       

      Independent from this: Automatic migration of Adobe forms (IFbA) to the gateway-based Adobe forms is not available. The layout can basically be kept, but the data binding would need to be changed to the new form form data provider (gateway model). Also all extensions which you used  (including any logic in the print program) need to be manually moved to the form data provider (using standard extensibility features).

       

      Regards,

      Markus

      Author's profile photo Peter Gerhard
      Peter Gerhard

      Dear Markus,

       

      you wrote "SAP S/4HANA output control offers rich email functionality but handles archiving separately.". Could you please explain the archiving a little bit more in detail?

      With NAST, a document which is archived, was attached to the corresponding business object, so that you could access the document within the archive even when the output request was deleted.

      With the new output management the document is stored within the repositoy but only linked to the output request but not to the business object itself. Is there any way to link the output request within the repository to the related business object?

      Best regards

      Peter

      Author's profile photo Markus Berg
      Markus Berg
      Blog Post Author

      Hello Peter,

      ".. but handles archiving separately" means there is no Print & Archive feature like in NAST. Archiving needs to be started separately for the business objects which support it (include the archiving class from SAP S/4HANA Output Control)

      As you rightly point out, the access to the archived document is also different compared to NAST.

      In general all the document related features including archiving is very limited right now. This is what we want to change in the future by having a better integration with the SAP Document Management. With this we hope to overcome a lot of the current limitations.

      Best regards,

      Markus

      Author's profile photo Project Dept owner Project Dept
      Project Dept owner Project Dept

      Hello Markus,

      Thanks for detailed information.

      In our existing S/4 hana system, we are using NAST output to send XML file out to 3rd party system.  Just want to confirm with you, the sending of XML file is not supprted so far with above new Output Management in S/4hana, right?

      Looking forward to your confirmation.

      Thank you and best regards,

       

      Author's profile photo Markus Berg
      Markus Berg
      Blog Post Author

      Hello,

      Sending XMLs would be a use case for the channel EDI which is offered by SAP S/4HANA output control. However, whether the corresponding business application offers XML as technical message format when using channel EDI, would need to be checked with the business application.

      You should then also explore whether the XML needs to be send via SAP S/4HANA output control or whether there is another way. As explained above the scope from SAP S/4HANA output control is different to NAST, especially in regard to EDI.

      Regards,

      Markus

       

      Author's profile photo Project Dept owner Project Dept
      Project Dept owner Project Dept

      Hi Markus,

      Thanks a lot for your reply.

      You mean if a business application supports channel EDI, then it is possible to use channel EDI to send out XML, right? Is there any guide/documentation/blog/note for issuing XML with EDI? I was not able to find any.   Besides, the XML can only be sent to a partner function but not a logical system since S/4 HANA Output Management is business partner - based, am I right?

      To be specific, the business application I am referring is SD(sales and distribution), and note 2330928 mentions that "Output for sales documents is only issued by Output Management for the output medium types PRINT and EMAIL. The output medium types XML and IDOC are not currently supported".  So, If I have understood this correctly, with standard system, it is not possible to send out XML in SD area now since EDI is not supported in SD. Am I right, do you have any comment or info for this?

       

      Thank you and best regards,

       

      Author's profile photo Markus Berg
      Markus Berg
      Blog Post Author

      Hello,

      I can only describe here what the SAP S/4HANA output control offers as a framework. Which features are available in each consuming business application I cannot tell. This should be documented by the business application (like in the example from SD).

      Regards,

      Markus

      Author's profile photo Project Dept owner Project Dept
      Project Dept owner Project Dept

      Hi Markus,

       

      Thanks a lot for the information.

      I will check further from business application point of view.

       

      Thank you and best regards,