SAP Note Number 2228611 - Kodyaz

1 SAP Note Number 2228611 Number2228611 Version0024 Processor-Processing StatusnewImpl. StateCannot be implementedLanguageEShort TextOutput Management in SAP S/4 HANAC omponent-Long TextSymptomSAP S/4 HANA introduces a new style of output management (OM). This SAP Note provides you with an overview of this TermsOutput management, Output controlReason and PrerequisitesThe new output management is going to be the successor of all other output management frameworks (SD Output Control, FI Correspondence, FI-CA Print Workbench, CRM Post-Processing). However, all other frameworks are still available and can be used. It is not mandatory to use the new output applications that have already adopted the new output management use it by default.

2 Nonetheless, customers can always revert back to the other supported framework. How this reversion is realized depends on the business application (for example via SAP Note or by implementation of an enhancement point). It is also possible to re-enable the new output management again at a later point in , the new output management for SAP S/4 HANA coexists with other frameworks. Customers can decide on business application level which framework supports their output scenarios more details on output management usage in a specific business application please check the simplification item of that business 1 of output management for SAP S/4 HANA comprises all functionalities and processes that are related to the output of documents.

3 This includes the integration of output management functions into the business applications, the reuse component output control, as well as the SAP NetWeaver technologies and the technical control is the central element of output management. It serves as an interface between business applications and SAP NetWeaver that although output control is by definition one of several parts of output management, the term output management is often used to describe the functionality of output you use applications that have adopted the new output control, please consider the following aspects and consult the following SAP notes : Technical setup - SAP Note 2292571 Configuration - SAP Note 2292539 New form templates used by output control.

4 Form templates with fragments - SAP Note 2292646 Master form templates - SAP Note 2292681 Customized forms - SAP Note 2294198 Customized master forms - SAP Note 2367080 Conversion (see below)Features and functionsThe following table provides an overview of existing features and functions of the new output control:Supported channels Printer Using the spool Email Allows flexible configuration of sender and recipient(s) as well as use of email templates XML integration with the Ariba Network IDoc (limited support only; for more information, see below)Supported UI technologies Fiori SAP GUI and SAP GUI for HTMLS upported form technologies PDF-based print forms with fragments (default) PDF-based print forms Smart Forms SAPscriptMaster form templatesA master form template defines a universally valid layout and features reuseable parts of a form, such Page 2 of header, footer, or logo (only available for PDF-based print forms with fragments).

5 This allows you to maintain general content and application-specific content separately. If you make changes in the general content (master form), the application forms will be updated of master form templatesMaster form templates can be determined based on preconfigured parameters, such as company, sender country, or channel. This makes it easy to define separate logos or footer texts per parameter determination via BRFplusAll output parameters can be automatically determined via a configuration activity based on BRFplus. The benefits are: You can send multiple messages to multiple recipients using multiple channels at the same time.

6 You can configure anything without the need for ABAP exits. You can base each determination step on application-specific fields that can be extended. You can use predelivered content/determination rules to simply run output control out of the box. Extensibility via CDS is timeImmediately or scheduled via batch job (application-specific)Application logThe system creates one application log per output request instance. In addition, you can filter messages by output request item. You can display the log in the business application or via transaction SLG1 once an output item has been frameworks/services BOPF BRFplus KPro Gateway Services Fiori Web Dynpro SAP GUIPage 3 of , IDocs are not fully supported by the new output management.

7 Their use is restriced to business applications that previously used NAST. Furthermore, the following limitations apply: Only output types which can be mapped 1:1 to the NAST-KSCHL can use IDoc. Only business partner-based communication is supported, but no communication to logical systems (no ALE support). Manually created output items cannot be used for IDoc, as the partner role cannot be set for such check your business requirements agains these limitations. Refer to the simplification item list of the business applications to check which business scenarios support the use of In the ECC Business Suite, different output frameworks are used in different applications (SD Output Control, FI Correspondence, FI-CA Print Workbench, CRM Post-Processing Framework).

8 Considering the conversion of an existing system to SAP S/4 HANA, it becomes evident that there cannot be one generic approach to cover the conversion of all other OM further into the most prominent existing OM framework SD Output control (NAST), it becomes clear that: 100% feature parity is not a given (and, most likely, is not wanted). Migration of data cannot be performed because even the NAST is highly , the recommendation is not to carry out a conversion, but to establish a coexistence of old and new output means: For existing customers who are using the old output management: Data from the old OM is kept. Customizing for the old OM is kept.

9 Customers need to customize the new OM. Documents that were processed in the old OM will still be processed using the old OM. New documents will only use the new OM (if the corresponding application has already adopted this framework). For new customers Customers need to customize the new OM. All documents will be using the new OM (if the corresponding application has already adopted this framework).Page 4 of Releases 100 101 Links to Support PackagesSoftware ComponentReleasePackage NamePage 5 of