Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
Wagnerfr
Active Participant

With the TOP Simplification List Items approach we want to start a S/4HANA SCN Blog series to provide more information about dedicated simplification items. Simplification items where we assume that any customer project has to deal with. The following S/4HANA SCN Blog is collecting these TOP Simplification Items with the links to the dedicated S/4HANA blogs.

The TOP Simplification List Items

Within this blog we want to provide additional information regarding the Simplification Item: Output Management

Simplification List Item Description

The new output management is going to be the successor of all legacy frameworks (SD Output Control, FI Correspondence, FI-CA Print Workbench, CRM Post-Processing). However, all legacy frameworks are still available and can be used. It is not mandatory to use the new output management.

Business applications already adopted to the new output management use it by default. Anyhow customers can always revert back to the corresponding legacy framework. How this reversion can be achieved depends on the business application (e.g. via SAP Note or implementation of an enhancement point). Also enabling the new output management again at a later point in time is possible.

Business Impact

Business applications like Billing and Purchasing already use the new output management by default and require a setup of the new output management in order to be able to output business documents. However these applications also allow to enable the legacy output framework (NAST) again.

Required and Recommended Action(s)

Follow the technical setup and customizing activities for the new output management.

Refer to SAP Notes 2292571 and 2292539.

For more details see the PDF attached to the following SAP Note:

http://service.sap.com/sap/support/notes/2228611

4 Comments