Product Information
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
SAP S/4HANA output management itself is part of the SAP S/4HANA standard. So there are no additional costs to use it. When using additional services on BTP (for example SAP Forms service by Adobe) this might be different, depending on your SAP S/4HANA edition.
The following features are not yet supported when using SAP S/4HANA output management:
- Support of ArchiveLink or DMS for documents created during output
Check out SAP blog – Storing Output Documents in SAP S/4HANA for more details.
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. It is integrated in the SAP S/4HANA standard and does not require any additional purchase or license.
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.
Features of Output Control
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.
- Which SAP S/4HANA product are we looking at?
- Which business application are we looking at?
- Which output solution are available for that business application?
- 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:
- The business application existed before SAP S/4HANA (and therefore has an existing output solution from the past).
- 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 of NAST and SAP S/4HANA output control
Output Channels
Even if comparing the output channels, there are some differences.
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 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)
- Output Management in SAP S/4HANA – Part 1 – from Apr 17th 2019 – blog
- Hands-on on SAP S/4HANA Output Management- Part 2 from May 8, 2019 – blog
- Tutorials: Hands-on SAP S/4HANA Output Management
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.
A very nice overview, thanks!
Thanks for this comprehensive overview. really useful.
Regards, Imran
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
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
Hello Joost,
The Print Workbench is one existing output solution, so all things I described above apply here as well.
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
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?
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
Thanks for your quick reply!
Many thanks! Great news.
Great Blog.
Is the Delivery option supported for S/4 HANA 2020 On prem currently?
Hello Priya,
Which delivery option do you mean? SAP S/4HANA output management is available since SAP S/4HANA 1511.
Regards,
Markus
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
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.
Thanks. I read this note earlier but since the last update date was way in the past, it confused me.
I agree. Let me try to get it updated accordingly.
Hi Markus,
Is the new output management available for Shipment Outputs in S4 HANA 2020?
Thanks,
Priya S Shekhar
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
Hi Markus,
Thanks for the information.
Regards,
Priya
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
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
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
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
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
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:
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
are not available.
Best regards,
Markus
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
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
Thank you, Markus!
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
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
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
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
Thank you for the great breakdown of this functionality, very helpful!
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
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
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
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
Hi,
is there any detailed information on this part "Archiving needs to be started separately for the business objects which support it"
Thanks in advance
Uli
Hello Uli,
With that I mean the standard ILM archiving. SAP S/4HANA output control offers an archiving class which need to be included in the ILM archiving object of the consuming SAP business application.
Then the standard ILM process can be followed. More details could be documented by the individual business application.
Regards,
Markus
Hi,
the original post was related to "...means there is no Print & Archive feature like in NAST" -> Document Archving/Stirage.
For my understanding the ILM was for Data Archiving, not Document related. Which Optios do I have to archive/store documents in a external (CMIS) archive?
Thanks
Uli
Hello Uli,
Document storage is documented in the SAP help portal: "Setting up Storage System and Storage Category"
https://help.sap.com/viewer/8308e6d301d54584a33cd04a9861bc52/2020.002/en-US/01e115a5788d40a0a5d9318db7798aa0.html
Every document which gets created based on a form-template, is automatically saved in the defined repository.
As mentioned above in the blog, due to the usage of low-level KPRO APIs there is no support of ArchiveLink or DMS for those documents though.
Regards,
Markus
Hi,
thanks for your answer - just to be sure, this "for example, an SAP system database or an HTTP content server" will also work in a public cloud environment?
Where Do I set up the HTTP Content Server in a public cloud environment?
> is no support of ArchiveLink or DMS for those documents though
Does this not say the opposite - no DMS usage is possible for the documents?
Thanks
Uli
Hello Uli,
I am no expert with this kind of setup. Sorry.
DMS (and ArchiveLink) put additional features on top of the pure document storage. For example, they provide document types or Document Info Records. These kind of things are not available for the documents stored by SAP S/4HANA output control. It's just a low-level storage of the documents.
Regards,
Markus
Hi,
Thanks - who may be able to answer these questions - to ask as basic as I understand the SAP Cloud framework 🙂
Is it possible to store outbound documents from output control in a CMIS Repo - if yes, how could I do the setup?
Thanks
Uli
Hi Markus,
you mentioned in your blog...
The following features are not yet supported when using SAP S/4HANA output management:
=> This implies they will be made available for S/4HANA output management at some point in time. Where can we see these timelines. ( i tried roadmap viewer, but was not successful).
Regards,
ASingh
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,
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
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,
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
Hi Markus,
Thanks a lot for the information.
I will check further from business application point of view.
Thank you and best regards,
Hello Markus,
Thanks for the detailed explanation about New Output Management. Well I would like to know how to manage a requirement where if you want to trigger output on certain condition only when documents gets change. i.e. with Purchase order with NAST based output - using requirement routine we can easily set sy-subrc as 0 or 4 based on the condition to trigger the output or not to trigger the output. If the same thing would want to achieve using New Output management, how this can be done.
Thanks in Advance..!!! Sameer
Hello Sameer,
The code-snippets from NAST have been transferred to a customizing activity (step "Output Relevance" in Output Parameter Determination). There you can define business rules based on pre-defined attributes or custom fields to determine the output relevance. This means, your business users can now freely define the conditions. No need for a developer here anymore.
Example: Output Relevance for Billing Documents
Regards,
Markus
Thanks Markus for your quick reply.
Well need your input that what could be the missing parameter that I could not see the Output Relevance Determination step for Purchase Order. The same is available for Sales Document, Payment Advice and other rules.
Hello Sameer,
In the end it's up to the business application whether it offers the step "Output Relevance" or not. Purchase Contract does not offer it, meaning everything is relevant for output all the time.
Same was true for Purchase Order in older releases, but it's offered in the latest versions. For new applications this step is now mandatory, but older ones are not automatically changed.
So it would be a new requirement for Purchase Contract to offer this step.
Regards,
Markus
Thanks Markus,
Well we are into S/4 HANA 2020 and hope you are talking the latest S/4 HANA version only. And in 2020 we don't see the Output Relevance step in Determination for Purchase Order. Are you saying that this will be available in 2021.
Hello Sameer,
Yes, in release 2021 this step is available for Purchase Order.
Output Relevance - Purchase Order - Release 2021
Regards,
Markus
Hi Markus, Good day,
For archiving, earlier Output type(NACE) settings, where all entries are stored in TOA* tables, where ILM Retention rules(AL_DOCUMENTS (attachments))can be applied for the attachments by conversion report (ARLNK_SET_PROXYS_ALDOCUMENTS (for attachments)) and then can be destruction as separate ILM_DESTRUCTION, if retention period has reached.
https://help.sap.com/doc/saphelp_crm700_ehp01/7.0.1.15/en-US/ee/b91dcd1aa444a98ffbba662ecddb9c/frameset.htm.
but for BRF+, Output management has generate and config(2279725, 2292571) made to store in SAP Table(with storage category mapping to repository), and Now again made a setup to move from table stored attachments to archive server. Now as per above sap help url, ILM Retention can be applied to TOA* tables only. can you please guide, how to apply the ILM retention for the attachments which are moved to archive server for BRF+ output management
(** Also we are not going with purchase data archiving , where APOC_OR class involves. here NO data archiving at this stage, only attachment(document archiving)(routing from KPRO table to 3rd party ARCHIVE SERVER), where ILM rule cant applied), Not sure in recent release after 2020, can be achieved or not))
BRF+ -> Output determination(OPD) -> table SFORM_A_STORAGE -> Repository SOMU_DB -> SOMU Category -> class -> Archive server repo -> attachment move to 3rd party server ------> where how ILM RETENTION rule can apply on the archived attachments. ?
whats ILM object and conversion report for this BRF+ or any other solution for the BRF+ output attachments can move to archive server and APPLY ILM RETNETION on the archived attachments ? any guidance pls
Thanks & regards,
Mohan.
Hello Mohan,
Archiving in general
As mentioned above in the blog, due to the usage of low-level KPRO APIs there is no support of ArchiveLink or DMS for documents created during output.
Regarding ILM
For ILM archiving the output history (including content from storage SOMU_DB) will be handled by the ILM archiving object of the corresponding business application.
SAP S/4HANA output control offers an archiving class which takes care of the output control data and related data like KPRO. This class is used in the ILM archiving object of the application.
So from my point of view no direct actions are necessary on the SOMU_DB level. But I have to admit that I am not an ILM expert.
Regards,
Markus
Hi Markus,
very good explanation.
Currently I'm configuring the output management using SAPScript forms. Unfortunately cannot find any guidance for this.
I'm wondering if you can give me some hints to perform this.
Thanks and regards
Klaus
Hello Klaus,
As described in the section "Available Options", such questions depend on the overall context.
Can you please let me know your context. So which SAP S/4HANA edition, which application, which output solution you want to use the SAPscript forms in?
Regards,
Markus
Hi Markus,
thanks for this fast reply.
S/4HANA edition is 2020 SP02, want to use the existing SAPscript forms for PO print out.
Regards,
Klaus
Hi Markus,
thanks for this fast reply.
S/4HANA edition is 2020 SP02, want to use the existing SAPscript forms for PO print out.
Regards,
Klaus
Hello Klaus,
And output solution is SAP S/4HANA output control?
If yes, I recommend the SAP help portal - "Using Customized Application Forms"
https://help.sap.com/viewer/8308e6d301d54584a33cd04a9861bc52/2020.002/en-US/641f5b7a52af402fbbf2d0fded507f41.html
Regards,
Markus
Hi Markus,
thanks for your support. It's working now.
Regards,
Klaus
Dear Markus,
thank you for the comprehensive overview. I have a specific question regarding form size limitations with ADS when using S/4HANA Cloud.
We have currently an issue (on the productive system!) with generating PDF forms for very large salesorders, containing several hundred line items.
The PDF is not generated, some ADS error message is returned.
SAP support has analyzed the issue and told us there is a limit for the number of pages. Our invoice will have around 230 pages. And even larger ones may be generated by the customer.
While searching for solutions I found this link: https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/en-US/1f/d9bc3854564800be3a220912428288/frameset.htm
It says, there is a method called "stitching bundled forms" to overcome the page number limitation. However, I do not think we can implement this in S/4HANA Cloud as we have no access to the ABAP stack or ADS configuration.
My questions are:
Thank you,
Johannes
Hello Johannes,
Yes, there are technical limitations of the ADS in SAP S/4HANA Cloud.
Maybe also the rendering takes too long and runs into a time-out.
Without further details it's hard to give any advise. I am also not an expert with ADS specifics. So likely it's better to continue the discussion with SAP support.
The documentation which you found does not apply here, as this is for the Java-based ADS which is not available for SAP S/4HANA Cloud. Therefore a feature like stitching is not available.
Best regards,
Markus
Hi,
Before asking my question, I must confess I didn't read the blog, I just discovered the new output management system in a training, sorry for my laziness if my question is answered above.
If I'm not mistaken, defining business rules for the output determination is what the business did in the past in VV... records of the 'NAST' solution, but this is now in the IMG.
If the business used only one output device for everything, but want now to use different print queues by distribution channel for example, this will mean defining a new rule in the IMG, what business people usually don't have access to, or is there anything I missed?
BR
Yan
Hello Yan,
You are lucky, this part is not described above 😉
The business rules can be maintained via app "Output Parameter Determination", technically based on an BRFplus application of type "Customizing". Hence it is linked in IMG.
In SAP S/4HANA on-premise the maintained rules can be transported via a customizing request. However, the business rules are a mix of customizing and other data. It's also possible for customers to allow business users to maintain the rules in the productive system, to add some master data.
In SAP S/4HANA Cloud there is no transport and the rules can be maintained in all systems by default.
Regards,
Markus
Thanks Markus :).
If I may ask, is there a direct Fiori app or tcode in the UI where business users can maintain the rules/add some more MD in the productive system, if this is allowed by the customer?
Regards
Yan
Hello Yan,
There is a Web Dynpro application which can be started via transaction OPD in on-premise and via a corresponding Fiori tile in cloud. There's also a specific user role which can be assigned to the business user for the access to this app.
Regards,
Markus
Thanks again, I indeed saw ODP (accessible via BR+ in the UI if I'm not mistaken), but I didn't realize that it could also be use to 'refine' the BRF+ decision tables, I thought it was just used as a a kind of analyze tool to simulate and tests the output config.
Thanks thanks.
Regards
Yan
Hello Markus
Can we use in on prem 1809 version, customer correspondence generation using OPD? We can see xml formats and other objects like FFO_CORR_CUSST provided for customer correspondence for 1809 but cannot see in activation for application objects. Can you please share your thoughts?
Regards
Debasmita
Hello Debasmita,
It's an application specific decision whether and when output control gets enabled.
Please check SAP note 3097507 – Output Management in SAP S/4HANA for an overview. This note also describes how to check directly for supported applications in the system yourself.
When your application is not listed or does not allow enabling SAP S/4HANA output control, then you would need to reach out to the application owners for their plans in future releases.
Regards,
Markus
Thanks for quick reply. I will check with Product owners.
Hi Markus,
Can we use this Output Control for BRIM2021 documents like Master Agreement, Solution quotations & contracts. We have PPF framework already .
Hello Indraneel,
It's an application specific decision whether and when output control gets enabled.
Please check SAP note 3097507 – Output Management in SAP S/4HANA for an overview. This note also describes how to check directly for supported applications in the system yourself.
When your application is not listed or does not allow enabling SAP S/4HANA output control, then you would need to reach out to the application owners for their plans in future releases.
Regards,
Markus
This became impossible to follow even for experienced Solution Archietects.
It would be helpful if you could be more specific where you struggle. Then we can better check how we can help.
Wonderful Blog Makus
I have one question within a specific application for exampleV1 sales, depending on direction inbound or outbound , do we have option to use NACE for Inbound and S/4 HANA new output for outbound?
This would need to checked with a product expert for sales. I assume it it not possible.
Is it true that New S/4 HANA Output Management does not support LS as partner ? What are the approaches thought through to ensure any logical system communication can be addressed with New S/4 HANA output Management? For Example currently we are using logical systems for IDOCs, how it will work in S/4 Hana output management
Yes, that's true. Please check the chapter "Some Words about IDoc & EDI" as well as the scope definition of SAP S/4HANA Output Control.
The SAP business application(s) would need to provide an alternative way for system integration when SAP S/4HANA Output Control is switched on.
Hi Markus
Thanks for your knowledge.
By this sentence,
I require to attached Purchse order form and send via Email. Could you please kindly guide me step to do, or any Note to execute.
Best Regards,
Kittipong
The rendered document (here Purchase Order) is always attached by default to an email send by SAP S/4HANA Output Control. No additional steps necessary.
Regards,
Markus
Hi Markus
Thank you for quick reply. I will try.
Best Regards,
Kittipong
Hi Markus,
Thanks for this blog! Are you able to say which BP master data field exactly is used to determine the Receiver e-mail address in which Business Application?
Reason I'm asking is that I have set up ORDER_CONFIRMATION output to be sent to multiple partner functions. In the order itself I see that for some of these partner functions (AP, VE, ZM) the receiver is found with corresponding email address. But for other partner functions (ES) it is not (no Receiver ID and no TO: mail address). For all of these partner functions there is a BP linked in the Partner tab of the order. All of the partners also have an email address maintained in the BP master data.
Thanks in advance
Wouter
Hello Wouter,
Unfortunately I cannot answer this from framework perspective because this information is retrieved via an application callback. The Output Control is agnostic here and just works with the provided values.
So it's best to check with the corresponding application experts on which receiver roles are supported and which data sources are used.
Regards,
Markus
Thanks for your reply Markus. I will check further with the application experts.
Kr,
Wouter
Hello Wouter
Would you please confirm that you can Email Order_Confimation to the contact Person (AP) ?
Thanks
Philippe
Hi Philippe, yes I confirm. Contact Person BP must have customer role and email address assigned for it to work though.
Kr,
Wouter
Thanks a lot
in fact, in our case, we want to send the purchase order to the contact person (AP) by email. Do you have any recommendations? Looks like it's not possible with OPD.
Regards
I have not tried this for the PO but I would think that as long as you have defined AP as a role in 'Receiver' step in OPD and also have the supplier role assigned to the BP you are using as contact person that it should work.
Kr, Wouter
Hi Markus Berg
Would you confirm that is possible (or not possible yet in SAP HANA on Prem.) to email Purchase Order to the Contact Person (AP ) using OPD ?
Actually, we can send Purchase to LF (vendor) or RS (invoicing Party) but not the AP (contact Person).
Thanks
Philippe
hi Philippe
sorry, we dont have support for sending output to receiver role "contact person". Would you raise a CIP or WCR request to the product management and mention the business need?
thanks
Rajesh
Hi Philippe,
Please find the blog for raising CIP request
https://blogs.sap.com/2019/08/10/submitting-new-feature-requests-sap-customer-influence/
Regards,
Rahul
Hi Markus
We are running a Greenfield implementation on S/4 HANA 2021 FPS02. We have chosen to use the old NAST output solution.
We are wondering how to migrate the output conditions from our old ECC system into S/4. As far as we can see there are no migration objects for this type of data. Any advice from your side how to migrate output conditions from ECC to S/4?
Best Regards
Gitte Greibe
Hello Gitte,
I am not aware of any specifics for migrating the data from NAST.
I assume it should be possible to migrate it as other data. So maybe the general SAP note "2973957 - SAP S/4HANA Migration Cockpit" can help you here.
Regards,
Markus
Thanks for your reply, Markus.
Unfortunately, there are no migration objects in the Migration Cockpit for these kinds of data.
BR Gitte.
HI Markus,
Question, here it has been configured to send Purchase Order Form via PRINT, and now I am changing it to send it via E-MAIL, I made an OPD change, but it is showing the error "The sender's email address cannot be initial." . Do you know this error? Another point, can I put the Email Subject or Email Template ID field in the OPD with the fixed value?
Thanks.
Dear Roberto,
Please check the output management setup guide attached to scope item 1LQ. There's a section for the sender email address. You will find that there is always an application specific default (which usually reads from master data of the entry which is behind the selected receiver role). In addition you can define a sender email address in OPD which would overrule this default. Even a mix is possible.
You should definitely set the email template ID in OPD as well, otherwise no email output is possible. The email template allows you to set the subject and body of the email (including placeholders)-
Regards,
Markus
Hello Markus,
Thanks for the detailed explanation about New Output Management. This is a fantastic blog for starters into output determination for S/4 HANA .
I am currently engaged in a S/4HANA 2021 Greenfield Implementation project and in the explore phase of the same . We are currently using a S/4 HANA 2021 On Pemise edition.
Please can you help me understand the following points :
eg: a) BILLING DOCUMENT - using BRF+
b) Remittance Advice - using NACE
c) Purchase Document - Using BRF+ and so on .
2. It was also mentioned in a note that there is a limitation of using BRF plus with IDOC's as the new way of doing the same is through API , if we have to fall back to IDOC's to support the AS-IS scenarios we must use NACE with certain SAP Note implementations for adjustment .
Can you please help me understand this point ? and if we need any further adjustments to the landscape will there be any impact to the Output Determination usage for the same or other processes ? any link to the related notes will also be helpful .
Thank and regards,
Sankha
Hi Markus,
Thank you for this very comprehensive overview.
For an application, what would it mean to support the output management? Currently we are using ppf actions. Are there any guidelines how to enable an application for output management?
We are also thinking about the use case, taking the result from a situation which we have in place to additionally inform the external affected business person (aka customer) about the result (such as an expiring contract). Would there be a way to do a handshake between the situations management and the output management, maybe via BRF+?
Any advice and proposals are appreciated very much.
Best Regards
Helene
Hello Helene,
Currently only SAP business applications can adopt the S/4HANA Output Control following the internal development guidelines.
We plan to enable this for custom applications in the future, but I cannot give any timeline right now.
Regards,
Markus
Hi, Markus,
Is it possible to expose s4hana embeded adobe service as an API ? As you know, BTP Form Service by Adobe is not available in China .
Best regards!
Jacky Liu
Hello Jacky,
This would not help you, as the Adobe Document Services (ADS) do not run in ABAP. They either run on the application server in a Java stack (SAP S/4HANA on-premise only) or on BTP.
So if you are running on-premise, you could install the on-premise ADS in the Java stack. For other editions, please get in touch with SAP S/4HANA solution management to discuss the options.
Best regards,
Markus
Hi Markus,
First of all Thank you for such an highly informative Blog.
I have a question here
Since we have two types of Output determination 1. NAST condition technique and 2. S/4 Hana Output management,
Which type should we go with when dealing S/4 HANA Central Procurement scenario with ERP connected systems.
For example considering central requisitioning scenario. Central purchase requisitions created in the S/4 Hana CP system are replicated to backened ERP connected systems. And respective POs are created in Connected ERP systems which are agained imported back to S/4 System for approval.
Now where does the output management works and how are they configured ?
Can we use any of those 2 output determination methods or only S/4 Hana output determination?
Thankyou in advance
Pavan
Hello Pavan,
Basically, that decision is fully up to the customer, where likes to configure his output in case of a Central Procurement setup. He can keep his existing NAST-based output in his connected ERP backends, if he likes to. In this case he does not really need to change anything in his today's setup in the connected system. Or he could choose to use the central output from his Central Procurement hub system, if he wants to have a central place alone, where all his output configurations could be configured (form, print relevant changes, etc.). And that output control in Central Procurement is then based on the new S/4 output management alone. As we do not actively stop any output in the connected systems, just because the central output is used, the customer himself needs to make sure in his configuration, that only a single output is triggered for a given purchase order.
Kind regards,
Peter.
Hi Markus,
In the S/4 HANA Output Management, Do we have any Events which can be raised when an output is generated? or Do we have any extensibility option to implement a custom logic post generation of an output item?
Our scenario is to send an Event to BTP Event Mesh indicating output is generated for Purchase Order or Scheduling agreement.
System Version : OP 2021
Thanks,
Rishab
Hello Rishab
The are currently no events available from Output Control. You may check whether the corresponding business applications in your scenario offer something.
Regards,
Markus
Hello Markus,
Thanks a lot for the detailed explanation about New Output Management. We are running on premise version 1709 and OPD is activated. I would like to know if some changes have been done since you wrote your explanation on the possibility to use content server with S4 Hana and OPD?
I would like to archive invoices and others document, but I don't find any solution to link customizing OAC* with OPD. Or do you have any idea to do it?
Thanks in advance for your help
Regards,
Laurent
Hello Laurent,
SAP S/4HANA Output Control automatically stores the rendered document (NAST option: Print & Archive) in the defined content repository. The storage location can be freely defined by the you using the KPRO configuration (e.g. SAP DB or HTTP content server). Main difference to frameworks like NAST is that there is only one storage category (meaning all documents end up in one folder) and the document data/object relations are handled within output control and not via Archive Link.
Hence you will not find any entries in the TOA* tables. This is also only required, when you need additional information regarding the object relation and/or data from the leading business application. Otherwise you can archive the files directly from the content repository.
Regards,
Markus
Hello Markus,
Thanks a lot for your time and answer, I will have a look in KPRO. Ok to store all documents in the same storage location. Is it possible to get the link to display these documents without duplicate in other application. It was possible with archive link function module to get this link, possible in this case?
Regards,
Laurent
Hello Laurent,
I am not really able to answer this as I do not know the previous feature. When it is archive link specific, then likely it is not available in the same way.
Regards,
Markus
Thanks a lot for your answer Markus
Firstly thank you for erudite summary on the new output management solution on S/4HANA on prem/private/public context. I read through your entire blog including all the comments! Why I stumbled upon your blog is to look for an explanation on Form Type- DDIC vs Gateway ,As I Used DDIC earlier-I also got to know many valuable points from those comments-thank you for the same. E.g.- 'PrintWorkBench' which I was not aware of since I did not work on Utility sector.
However, I would like to notify that I do not agree completely with the section - "Some Words about IDoc & EDI"
As I could recall in 2018, we were implementing S/4 on prem to US client and then we had many integration touchpoints where the consuming applications were accustomed to accept XML message format. I tried to generate out of box EDI channel XML, Integration platform was SAP PO, however it did not workout as per requirement even after multiple technical expert's effort from SAP side as well.
Eventually, it turned out from SAP product support in Germany, that with ARIBA Network we could generate XML successfully- so essentially which you vaguely meant by business network term is SAP's push towards ARIBA- Obviously we were little surprised, as most of the customers wouldn't like to move entirely inside SAP ecosystem, neither we wanted to setup 3rd party as ARIBA agent.
Finally we implemented 'Outside the box'-alternate solution for IDOC with small customizing and minor enhancement. Since then S/4HANA 1709 and upward versions in multiple clients we had implemented that approach for similar requirements.
KR
Avik
Dear Markus,
thank you for your interesting text. I have got one simple question, though: We have numerous forms in SAP script and Smart Forms (e.g. MM, SD, LE, dunning, …) and are considering converting those to Adobe Forms. We do NOT need advanced features like interactive forms, electronic signature etc. provided by Adobe Forms technology. We just would like to print forms on premise as we did for more than 20 years.
Knowing that ADS will be discontinued, is there or will there be any other way to print “plain” Adobe Forms in S/4 on premise without using a cloud solution?
Thank you
Jens
Hello Jens,
According to my knowledge, SAP has a clear maintenance strategy for the java-based ADS until 2030. SAP also evaluates options for beyond this point to keep up to the promise that SAP S/4HANA will be maintained until 2040 including all released capabilities (e.g. forms).
In addition, SAP offers the ADS as a cloud-service (SAP Forms service by Adobe) which has no dedicated end of maintenance.
Regards,
Markus
I have used BRF+ to configure PO Output to trigger on a Schedule (previously, Immediate). I now want to schedule a job to run every n minutes. Can anyone direct me to the Fiori app to do this (or the ABAP program is this is still the method).
Running S/4HANA 2020 FPS02.
Hello Gerald,
There is no Fiori app available for this. You may use transaction ME9FF.
Regards,
Markus
Thank you Markus, appreciate you getting back to me. As it happened, I eventually found the transaction and for anyone else looking who wants to run it as a batch job, the ABAP report is
PURCHASE_ORDER_OUTPUT_RUN
Hello Gerald,
In general, there is framework called Application Jobs. Using this framework, you can expose Abap Reports to be usable via Fiori (framework allows schedulling options - like run every week etc.).
If you have Abap report, which triggers Output Requests, then you can expose such report via Application Jobs.
https://help.sap.com/docs/SAP_NETWEAVER_750/b4367b1cec3243c4989f0ff3d727c4ab/37e7a011a524405882af49cce79f0fb4.html
Best Regards,
Jiri
Thanks Jiri, I'm always on the look out for good Fiori apps to replace GUI transactions. However, as is often the case with SAP, there are pros and cons with each approach. I like the app because it's a one-stop-shop function: find your template, schedule the job, done. A couple of drawbacks: you cannot make use of variants and only the user who created the job can see the logs "You are not authorized to display spool requests other than your own". More often than not you want to schedule a background job under a specific User ID; we've not found a way to do this other than reverting to the SM36 approach.
I will look at the option to Define Job Catalog entries, that could be handy.