SAP HANA FAQ...

1.What is SAP HANA?
SAP HANA is an in-memory computing engine (IMCE) used for real-time processing of huge volumes of data and building and deploying real-world applications. Adopting the row-based and column-based DB technology, SAP HANA is an advanced relational DB product serviced by SAP SE. With this high-performance analytic (HANA) system, the big data exists on the main memory and not on the hard disk. It replaces the onus of data maintenance separately on the legacy system and simplifies the tasks of administrators in this digital world.

2.What is the development language used by SAP HANA?
C++

3.Name the operating system SAP HANA supports.
More than 70% of customers run their SAP workloads on Linux with the use of SUSE Linux Enterprise Server, which is the best OS choice for SAP HANA.

4.Explain Parallel Processing in SAP HANA?
Using the columnar data storage approach, the workload in SAP HANA is divided vertically. The columnar approach allows linear searching and aggregation of data rather than two-dimensional data structure. If more than one column is to be processed, each task is assigned to diverse processor. Operations on one column are then collimated by column divisions processed by different processors.

5.List advantages of using SAP HANA database.
• With the HANA technology, you can create gen-next applications giving effective and efficient results in the digital economy.
• By using singe data-in memory, SAP HANA supports smooth transaction process and fault-tolerant analytics
• Easy and simple operations using an open-source, unified platform in the cloud
• High-level Data Integration to access massive amounts of data
• Advanced tools for in-depth analysis of present, past and the future.
6.List the merits and demerits of using row-based tables.
Merits:
• No data approach can be faster than row-based if you want to analyze, process and retrieve one record at one time.
• Row-based tables are useful when there is specific demand of accessing complete record.
• It is preferred when the table consists of less number of rows.
• This data storage and processing approach is easier and effective without any aggregations and fast searching.
Demerits:
• The data retrieval and processing operations involve the complete row, even though all the information is not useful.

7.List advantages of column-based tables.
• Allows smoother parallel processing of data as the data in columns is stored vertically. Thus, to access data from multiple columns, every operation can be allocated to a separate processor core.
• Only specific columns need to be approached for Select query and any column can be used for indexing.
• Efficient operations since most columns hold unique values and thus, high compression rate.
8. What table type is preferred in SAP HANA Administration: column-based or row-based?
Since analytic applications require massive aggregations and agile data processing, column-based tables are preferred in SAP HANA as the data in column is stored consequently, one after the other enabling faster and easier readability and retrieval. Thus, columnar storage is preferred on most OLAP (SQL) queries. On the contrary, row-based tables force users to read and access all the information in a row, even though you require data from few and/or specific columns.
9.What is the main SAP HANA database component?
Index Server consists of actual data engines for data processing including input SQL and MDX statements and performs authentic transactions.
10.Explain the concept of Persistence Layer.
The persistence layer in SAP HANA handles all logging operations and transactions for secured backup and data restoring. This layer manages data stored in both rows and columns and provides steady savepoints. Built on the concept of persistence layer of SAP’s relational database, it ensures successful data restores.
 Besides managing log data on the disk, HANA’s persistence layer allows read and write data operations via all storage interfaces.
11.Define Modeling Studio in SAP Hana Administration.
Modeling Studio is an operational tool in SAP HANA based on Eclipse development and administration, which includes live project creation.
• The SAP HANA Studio further builds development objects and deploys them, to access and modify data models like HTML and JavaScript files.
• It also handles various data services to perform data input from SAP warehouse and other related databases.
• Responsible for scheduling data replication tasks.
12.List the different compression techniques in HANA?
• Run-length encoding
• Cluster encoding
• Dictionary encoding
13.Explain SLT
SLT expands to SAP Landscape Transformation referring to trigger –based replication. SLT replication permits data transfer from source to target, where the source can be SAP or non-SAP while the target system has to be SAP HANA with HANA database. Users can accomplish data replication from multiple sources. The three replication techniques supported by HANA are:
• SLT
• SAP Business Objects Data Services (BODS)
• SAP HANA Direct Extractor Connection (DXC)
14. Name the replication jobs in SAP HANA.
• Master Job (IUUC_MONITOR_)
• Data Load Job (DTL_MT_DATA_LOAD__<2digits>)
• Master Controlling Job (IUCC_REPLIC_CNTR_)
• Migration Object Definition Job (IUCC_DEF_MIG_OBJ_<2digits>)
• Access Plan Calculation Job (ACC_PLAN_CALC__<2digits>)
15. What is Latency?
The time duration to perform data replication starting from the source to the target system is known as latency.
16.What are the various components of SAP HANA Administration?
• SAP HANA Studio
• SAP HANA Application Cloud
• SAP HANA Cloud
• Sap HANA DB
17.How to perform backup and recovery operations?
During a regular operation, data is by default stored to the disk at savepoints in SAPHANA. As soon a there is any update and transaction, logs become active and get saved from the disk memory. In case of power failure, the database restarts like any other DB returning to the last savepoint log state. SAP HANA requires backup to protect against disk failure and reset DB to the previous state. The backups simultaneously as the users keep performing their tasks.
18.Define SLT Configuration
Configuration is the meaningful information to establish a connection between source, SLT system and SAP HANA architecture as stated in the SLT system. Programmers are allowed to illustrate a new Configuration in Configuration and Monitoring Dashboard.
19.What is Stall?
The waiting process for data to load from the main memory to the CPU cache is called Stall.
20.Define different types of information views.
There are primarily three types of information views in SAP HANA, which are all non-materialized.
• Attribute view
• Analytic view
• Calculation View
21.What are Configuration and Monitoring dashboard?
They are SLT Replication Application Servers to provide configuration information for data replication. This replication status can also be monitored.
22.What is logging table?
Logging table records all replicated changes in the table, which can be further replicated to the target system.
23.How to define Transformation rules in HANA?
Using advanced replication settings, transformation rules are specified to transfer data from source tables during replication process. For instance, setting rules to covert fields, fill vacant fields and skip records. These rules are structured using advanced replication settings (transaction IUUC_REPL_CONT)
24.Explain the role of transaction manager and session?
SAP HANA transaction manager synchronizes database transactions keeping the record of closed and open transactions. When a transaction is committed or rolled back, the manager informs all the active stores and engines about the action so that they can perform required actions in time.
25.How is SQL statement processed in SAP HANA?
Each SQL statement in SAP HANA is carried out in the form of a transaction. Every time, a new session is allocated to a new transaction.
26. Define Master-Controller job.
A Master-controller job is responsible to build database logging table in the source system. It further creates synonyms and new entries in SLT server admin when the table loads / replicates.
27.How users can avoid un-necessary storage of logging information?
Pause the replication process and terminate the schema-related jobs.
28.Is the table size in source system and Sap HANA system same?
No
29.When to change the number of Data Transfer Jobs?
The number of data transfer jobs change when the initial loading speed or latency replication time is not up to the mark. At the end of the initial load, the number of initial load jobs may be reduced.
30.What is the default IMCE Studio perspective?
Administrator Console

Data Load from S/4HANA into BW via SDA... !!!

Being a SAP Consultant, I am a especially interested in everything which has to do with embedded analytics in S/4, but also in the integration with existing platforms like Business Objects and last, but not least, Business Warehouse.

 

When discussing SAP Activate and Best practices, it was brought to my attention that there are a lot of best practices how to integrate S/4 with Business Objects and BW. You can find the best practices at the following location:

 

SAP Best Practices for analytics with SAP S/4HANA

 

One of the interesting integration scenario’s one might come across with is the ability to take a HANA view (or CDS view) and persist that in BW. Think about scenario’s where you might like to take the accounts payables or receivables of a certain moment and build that up from a historical perspective. As normal real time analytics would show you the open items at a certain key date, it will make sense to calculate snapshots per month to show open items in a trend.

 

In this blog post, I would like to show you how easy it is to go from a real time view of your data into a persistent way of looking at the data.


Connecting S/4 to BW

 

In short we want to take an existing HANA model (one of the 3000+ views) and use that as a datasource in BW.

 

 

We will be using a combination of SDA (smart data access), an open ODS view and an Advanced DSO to go from a virtual scenario into a persistent scenario
.
The open ODS view architecture:

 

 

The generation of an open ODS into an ADSO is something I’ll show you in the next paragraphs.


Creating the SDA connection

 

Creating a remote connection to your S/4 system is a piece of cake. Go into the HANA studio of the receiving BW system, go to provisioning and create a new connection

 

 

Be sure to select the correct driver, the IP address of the source system and log on with your system user.

 

If all is ok, you will get the following screen

 

 

Now the fun starts. Select your view. I suggest you look at this blog post to get an idea on how to select the view you’re looking for

 

SAP S/4HANA Embedded Analytics – A detailed Walkthrough (Part 1)

 

For my example I will be taking the S4_HANA_SDA_sap.erp.sfin.fi.ar/FAR_CUSTOMER_LINE_ITEMS source and add that as a virtual (remote table) by right clicking on the view.





After adding the virtual table you can do a quick SQL content query to the results from my source table

 

 

Connecting the view to BW

 

Moving along to my BW system to connect the remote table to an Open ODS view.

 

Go to your info area of choice, right mouse click and create open ODS view

 

 

As I want to keep my ADSO fairly aggregated, I only select a number of fields

 

 

We now have a virtual connection via BW to S/4!

 

From Open ODS to Advanced DSO


Persisting it only takes two more steps:

 

Press generate dataflow to create the data source

 

 

Press a second time to get your flow generated

 

 

And ready we are with our ADSO and data flow!

 

 

I am just going to make one small modification in the ADSO and transformation by adding today's date as part of my key so that I truly have a snapshot per day

 

 

Load and activate the ADSO

 

 

We have data!

 

 

Let’s do a quick test in Analysis for Office

 

 

All done, we have snapshot AR data from S/4 per day!

How to save time to import many Language Packs for ERP/S4HANA Installation !!!

When you install languages using Software Provisioning Manager (sapinst) - Each language is installed sequentially and it takes a very long time. Just the install of French language takes 3 hrs 15 min. considering average of 2.5 hrs if you were to install 36 additional languages, it should take 90 hrs which is approx. 4 days. You can use the procedure below to save time when installing many languages required to be installed.

 

1. PREPARATION:

Provide sufficient additional space (36 languages need 100GB) in /usr/sap/trans. There should be sufficient background jobs. Also, take a backup at this point.

The media directory structure is as shown below after extracting the zip files:

vhcals4hci:/media/51050422_LNG1/DATA_UNITS # ls

AR BG  CA  CS DA  DE  EL EN  ES  ET  FI

vhcals4hci:/media/51050422_LNG2/DATA_UNITS # ls

FR HE  HI  HR  HU IT  JA  KK KO  LT  LV NL  NO  PL PT  RO

vhcals4hci:/media/51050422_LNG3/DATA_UNITS # ls

RU SH  SK  SL SV  TH  TR UK  VI  ZF  ZH

Copy the *.PAT files into /usr/sap/trans/EPS/in with this single command

vhcals4hci: cp /media/51050422_LNG?/DATA_UNITS/??/*.PAT /usr/sap/trans/EPS/in/.

 

2. ADD LANGUAGES IN RSCPINST:

Execute tCode SE38, program RSCPINST

Click on Add Language

RtClick First Column and select Set Filter from Popup

Click on Multiple Selection

Select items from below for cut & paste

AR

BG

CA

CS

DA

DE

EL

EN

ES

ET

FI

FR

HE

HI

HR

HU

IT

JA

KK

KO

LT

LV

NL

NO

PL

PT

RO

RU

SH

SK

SL

SV

TH

TR

UK

VI

ZF

ZH

 

Click on icon below to paste all 38 language codes

Click on Execute and Ok

Click on Select All

You will get screen like this. Languages already installed will be shown

Click on Check and then Activate. You will get message below

 

3. SETUP MONITORING AT OS LEVEL:

While the languages are being imported in the next step you will see no job running in SAP.

 

But R3trans processes will be running. The following scripts will help to check progress:

1. Monitor CPU Consumptionm in one window command :top
2. Count number of R3trans processes at OS level and they reduce in umber as the language import is completed.command :ps -ef | grep R3trans | wc -l
3. Monitor Space at OS level in directory /usr/sap/trans with comma:df -h
4. Count the number of files in /usr/sap/trans/tmp. The number of languages remaining to be imported are approx half the number of files here.ls –l /usr/sap/trans/tmp | wc -l
5. Tail ALOG file in /usr/sap/trans/log. Find out the last ALOG file like ALOG1601 and tail the file to check current date to substitute MM, DD and execute  command: grep "S4H.ALL R 0004 2016MMDD" ALOG1601.S4H

 

4. ADD LANGUAGES TO SMLT:

enter tCode SMLT click on create icon. Assuming the box is not used for any other work, as you add each language watch the CPU utilisation and after you reach about 70%, wait for 5 minutes before adding next language.

 

In the above screen, “supplementation” language is a secondary language used to supplement a language that is not completely translated. English & German are only 2 languages which are completely translated. Missing texts in other languages can cause process to crash and language supplementation function helps to replace that missing text with supplementation language text. When you choose English here for Arabic language, whichever text is not translated for Arabic will appear in English.

SWPM (sapinst) procedure by default does not add any supplementation language and can be added manually later on.

5. REPEAT ABOVE STEPS FOR ALL LANGUAGES:

Add one by one language from below list shown here for Cut and Paste. Please pick the correct ones from the popup list one by one.

AR          Arabic

BG          Bulgarian

CA          Catalan

CS          Czech

DA          Danish

DE          German  - Already installed

EL           Greek

EN          English--- - Already installed

ES           Spanish

ET           Estonian

FI            Finnish

FR           French

HE          Hebrew

HI           Hindi

HR          Croatian

HU          Hungarian

IT            Italian

JA           Japanese

KK          Kazakh

KO          Korean

LT           Lithuanian

LV           Latvian

NL          Dutch

NO         Norwegian

PL           Polish

PT           Portuguese

RO          Romanian

RU          Russian

SH          Serbian(Latin)

SK          Slovak

SL           Slovenian

SV          Swedish

TH          Thai

TR          Turkish

UK          Ukrainian

VI            Vietnamese

ZF           Chinesetrad.

ZH          Chinese

The screen should look like this. If you are installing 36 additional languages, please ensure the number of languages is 38.

6. IMPORT PACKAGES:

Against each language click on Import Package icon

Find Packages, Select and Execute

7. MONITOR THE JOB:

A job will be launched in SM37

8. REPEAT ABOVE STEP FOR ALL LANGUAGES:

Check the jobs scheduled

The process of adding and running all above can be completed in 30 mins

 

9. MONITOR PROCESSES AT OS LEVEL AND IMPORT STATUS IN SMLT:

After above jobs are completed, you will need to monitor R3trans processes as below. The number of R3trans processes reduces as language import is completed.

All above should be completed in 7 Hrs

Following is the typical order of import if you have added all languages in SMLT one after other in listed sequence, The first language to finish was CA – Catalonia and after that in 4 minutes language ET finishes and so on. Arabic Language finishes last.

CA          4hrs8min

ET          4hrs12min

LV           4hrs33min

NO          4hrs36min

FI            4hrs40min

SH          4hrs42min

SL           4hrs47min

HE          4hrs49min

UK          4hrs49min

KO          4hrs49min

HI           4hrs49min

HR          4hrs49min

SV          5hrs

VI            5hrs1min

PL           5hrs5min

RO          5hrs7min

KK          5hrs8min

EL           5hrs10min

NL          5hrs11min

HU          5hrs13min

DA          5hrs14min

LT           5hrs16min

ZF           5hrs17min

SK          5hrs18min

TH          5hrs20min

TR          5hrs22min

RU          5hrs26min

IT            5hrs28min

CS          5hrs35min

PT           5hrs36min

JA           5hrs38min

ZH          5hrs39min

ES           5hrs41min

BG          6hrs

AR          6hrs 10min

 

For S/4HANA 1511 FPS1 if you are installing Best Practices content, please use Note 2292425 - Removal Language-dependent SAP Best Practice content  to install only the needed languages.

Technical procedure and semantic adaption tasks - The System Conversion to SAP S/4HANA, on-premise edition 1511...

Release of SAP S/4HANA, on-premise edition 1511

In November 2015 (1511) updates have been released for both, SAP S/4HANA, on-premise and cloud edition. In November 2015, SAP delivered a massive wave of simplification and innovation in the core of SAP S/4HANA. With this delivery, enterprises can drive unprecedented business value with innovative use-cases - in core financial and operational areas such as in logistics – taking full advantage of a simplified data model and a responsive user experience.

Key simplifications and innovations include:

• Optimized working capital with new accounts payables and receivables cockpits
• Decreased stock buffers with simplified data model in inventory management for real-time, high-volume processing
• Increased visibility with real-time stock and material flow insight
• Reduced manufacturing cycle time with streamlined material flow for internal requirements (MRP)
• Augmented reactivity with real-time monitoring of production orders regarding flow and critical issues
• Improved operational decisions with easy simulation of supply alternatives
• Lower procurement costs with standard integration to the Ariba Business Network
• Better customer service with new sales order fulfillment cockpit for instantly identifying bottlenecks and issues

 

For more information see as well the SCN blog from Sven Denecken: Link

 

 

The System Conversion to SAP S/4HANA, on-premise edition 1511

Different transition paths are supported with SAP S/4HANA, on-premise edition 1511:

 

 

 

• New Implementation
  New installation of SAP S/4HANA e.g. for customers migrating a legacy system.
• System Conversion
  Customers who want to change their current system into a SAP S/4HANA system.
• Landscape Transformation
  Customers who want to consolidate their landscape or to selectively transform data into a SAP S/4HANA system.

 

The SAP S/4HANA, on-premise edition 1511 system conversion supports one-step procedure (Database, SAP NetWeaver and application transition in one step) for SAP ERP 6.0 EHP x…7 systems. System Conversion requires a Unicode (UC) source system. Non-Unicode source systems will require a two-step approach (first move to Unicode then to SAP S/4HANA, on-premise edition 1511).

 

 

 

Basically it can be distinguished between technical and semantic tasks during the system conversion. The technical installation procedure is based on established lifecycle management tools (Maintenance Planner, Software Update Manager [SUM] and Database Migration Option [DMO]). Due to the fact that SAP S/4HANA is a new product line (and not the successor of SAP Business Suite) things are done differently in SAP S/4HANA.

• Many of the changes are technical in nature and have no or only limited impact on peoples work and thus do not trigger business change management. Such changes will be mandatory when converting a system to SAP S/4HANA.
• Other decisions are more of a strategic nature determining which version of functional support will evolve into the digital era and provide the capabilities demanded from the unstoppable business process innovation. Where those strategic directions demand change management through adoption, SAP at large keeps the traditional capabilities available as compatibility scope enabling a rather technical migration of these processes and leaving the time of change management at customer decision that may well happen when initially converting or at a later point in time.

 

To allow our customers a better planning and estimation of their way to SAP S/4HANA, we have created the “Simplification List for SAP S/4HANA, on-premise edition 1511”. In this list we are describing in detail on a functional level what happens in S/4HANA to individual transactions and solution capabilities. In some cases, we have merged certain functionality with other elements or reflected it within a new solution / architecture compared to the SAP Business Suite products.

 

The technical procedure – well established tooling

Maintenance Planner

The Maintenance Planner checks the system with regards to business functions, industry solutions, and add-ons. If there is no valid path for the conversion (for example, the add-on is not released yet), the Maintenance Planner prevents the conversion.
The Maintenance Planner is a pre-requisite for the system conversion to SAP S/4HANA, on-premise edition 1511. The Maintenance Optimizer (MOPZ) is not used
For more information regarding Maintenance Planner see SAP Help: http://help.sap.com/maintenanceplanner

 

Software Update Manager (SUM)

Software Update Manager (SUM) is the technical tool for system conversion to SAP S/4HANA, on-premise edition 1511.
Note:

• You must run the Maintenance Planner before the SUM.
• Ensure that the latest version of the Software Update Manager is used:

For all information about using the SUM, please see the document Conversion of SAP Systems to SAP S/4HANA, on-premise edition Using Software Update Manager available at:

• service.sap.com/sltoolset (LINK)
  • Software Logistics Toolset 1.0
  • Section "Documentation"
  • System Maintenance

 

Database Migration Option (DMO)

DMO - the one-step-migration to SAP HANA database for SAP systems. It is called "database migration option (DMO) of Software Update Manager (SUM)". For SAP S/4HANA it combines the installation of the SAP S/4HANA, on-premise software and database migration to SAP HANA in one tool

 

 

See the following SCN Blog with helpful information regarding DMO - SCN LINK

 

 

Adoption Tasks – how SAP support the customer

Simplification List for SAP S/4HANA, on-premise edition 1511

To allow our customers a better planning and estimation of their way to SAP S/4HANA, we have created the “Simplification List for SAP S/4HANA, on-premise edition 1511”. In this list we are describing in detail on a functional level what happens in S/4HANA to individual transactions and solution capabilities. In some cases, we have merged certain functionality with other elements or reflected it within a new solution / architecture compared to the SAP Business Suite products.

For more information see Simplification List for SAP S/4HANA, on-premise edition 1511 (FPS1): PDF

 

Conversion Pre-Checks

Pre-checks are shipped as SAP Notes to customers that want to convert to SAP S/4HANA. Customers can use these pre-checks to find out what mandatory steps they have to carry out before converting to S/4HANA. The results list the instances that need addressing before attempting the conversion process. The checks are run twice again during the conversion process: both times in the Software Update Manager (SUM). The conversion is stopped if errors persist.

 

Implement SAP Note 2182725, and all the related notes attached to it. Make sure to use latest version of this note and regularly check for updates of all attached notes. Implement and run these reports on every system (Sandbox, DEV, QA, PROD) you want to convert to SAP S/4HANA, on-premise edition 1511. Report R_S4_PRE_TRANSITION_CHECKS.

 

Custom Code Checks

These checks are based on the Simplification list concept. Before converting to SAP S/4HANA, on-premise edition 1511 you need to check your custom code against the SAP S/4HANA simplifications. These simplifications are loaded into the Custom Code Check Tool. After you run the tool, you obtain a list of instances where your custom code does not comply with the scope and data structure of SAP S/4HANA 1511, on-premise edition

For more information about the Custom Code Check tool, see SAP Help Portal: Link and the following SCN blog: SAP S/4HANA Custom Code Migration Worklist.

 

 

 

 

Related information – at a glance

 

SAP S/4HANA, on-premise edition – General Information
SAP Help
SAP S/4HANA, on-premise edition 1511 documentation	Link
Getting Started With SAP S/4HANA, on-premise edition 1511	Link
Conversion Guide for SAP S/4HANA, on-premise edition 1511 FPS1	PDF
Simplification List for SAP S/4HANA, on-premise edition 1511 FPS1	PDF
Maintenance Planner – SCN Blog	Link Link
Software Update Manager (SUM) for SAP S/4HANA, on-premise edition 1511Software Logistics Toolset 1.0 --> Section "Documentation" --> System Maintenance	Link
Custom Code Check tool (SAP Help)	Link
SAP S/4HANA Feature Scope Description	Link
SAP SCN
SAP S/4HANA Cookbook	Link
Simplification List for SAP S/4HANA, on-premise edition 1511 FPS1 – XLS Version	Link
Software Update Manager (SUM)  - SCN Blog with more information	Link
DMO Database Migration Option – SCN Blog with more information	Link
SAP SCN - SAP S/4HANA Custom Code Migration Worklist	Link
Custom Code within SAP S/4HANA On-Premise	Link
SAP S/4HANA, on-premise edition:  Additional remarks regarding Business Functions (FPS1)	Link
Miscellaneous
SAP S/4HANA @SAP Learning Hub	Link
S/4HANA Trial	Link
SAP Best Practices for SAP S/4HANA, on-premise edition	Link
SAP Activate	Link
FIORI App Library	Link

 

SAP S/4HANA, on-premise edition – Important SAP Notes
General Information
SAP S/4HANA, on-premise edition 1511: Release Information Note	SAP Note 2189824
SAP S/4HANA, on-premise edition 1511: Restriction Note	SAP Note 2214213
SAP S/4HANA, on-premise edition 1511: Download Request	SAP Note 2244225
SAP S/4HANA, on-premise edition 1511: supported industry solutions	SAP Note 2214213
SAP S/4HANA, on-premise edition 1511, Country Versions: Release Information & Restriction Note	SAP Note  2228890
Blacklist Monitor in SAP S/4HANA on premise	SAP Note 2249880
SAP Fiori for S/4HANA	SAP Note 2214245
Process integration with other SAP on-premise systems	SAP Note 2241931
Custom Code related information
Delivery of the S/4H System Conversion Checks	SAP Note 2182725
Custom code check content for SAP S/4HANA on-premise edition 1511	SAP Note 2241080
Running Custom Code Analyzer and Downloading ZIP File(s)	SAP Note 2185390
Business Function related information
SAP S/4HANA, on-premise edition 1511: Always-Off Business Functions	SAP Note 2240359
SAP S/4HANA, on-premise edition 1511: Always-On Business Functions	SAP Note 2240360
Add-On related information
SAP S/4HANA, on-premise edition 1511: Compatible Add-ons	SAP Note 2214409
SAP S/4HANA, on-premise edition 1511: Compatible partner products	SAP Note  2244450
Add-on Product Versions released on SAP NETWEAVER 7.5	SAP Note 2156130
Uninstalling ABAP add-ons	SAP Note 2011192
SAP NetWeaver 7.5
Additional Information about the update/upgrade to SAP NetWeaver 7.5	SAP Note 2197259
Minimal DB system platform requirements for SAP NetWeaver 7.5	SAP Note  2158828

Output Management via BRF+ (Business Rule Framework Plus)... on S4/HANA.

With SAP S/4 HANA a new Output Management approach is in place. The complete configuration differs from the configuration that is used when output management is based on NAST (condition technique). The configuration is based on BRF+. In SAP S/4 HANA, the target architecture is based on Adobe Document Server and Adobe Forms only. For the form determination rules (along with other output parameters) BRF+ functionality is used.

 

Output management based on NAST is not available for new documents in SD Billing from 1511 and is extended to sales order management from 1602. Similarly, output  management using BRF+ is mandatory for Purchase order from 1511.

Prerequisites –

Uploading XML for importing output determination application in BRF+ (Ref note 2248229).

• BRF+ is active and usable
• Background RFC configuration has been set up
• Adobe Document Server is available – ADS needs to be implemented to allow SAP to fetch PDF properties for rendering output form
• KPRO has been maintained – KPRO allows to store PDF attachments on physical location.

 

Steps for uploading XML –

Note 2248229, provides decision tables for new output management. We need to download XML files to local drive and import them using below steps.

Transaction code

BRF+ or BRFPLUS

BRF+ workbench will be displayed. For importing output application, we need to change layout to “Expert” mode. Follow below steps –


 


a) Select user mode as “Expert”.
b) Save this settings.


Steps to import –    


a) Download zip files from SAP note 2248229 and save them on your local machine   
b) Next, we need to select Import XML under the Tools menu.  
         
c) Select relevant file in below screen.        
          
d) Specify Customizing request.    
e) Click on “Upload XML File” button.    
f) Uploaded application will now be available under Repository tab. 

          
Configuration –

Below configuration steps are relevant for all application areas (Sales Order, Purchase Order, Billing Documents and Outbound Delivery)

  SPRO Node for output configuration (IMG Path --> Cross Application Components)      


1) Define Output types –   


     Output Control -> Define Output Types    
     

2) Assign Output Channels -

     Output Control -> Assign Output channels      In this activity assign output channels to output type. 
     


3) Define Determination of Form Master Templates –    


Output Control -> Define Determination of Form Master Templates     


The master form template contains static data (such as a logo and footer) that is applied to each form page and is determined based on configuration setting maintained.      
    
Activities 
a) Enter a rule ID, preferably an ID that indicates the logic of the rule.     
b) Enter an ordinal number to specify the position of the rule in the determination sequence.     
c) Following parameters are optional –

• Organization Type
• Organizational unit

• Channel
• Sender country
• Form Template

 

During document output, the master form template is determined by comparing each defined rule with the current data provided by the application. If a parameter is not defined (no value entered), this parameter is considered as a match, and else, system determines the rule where all parameters match. Master form template is used corresponding to this rule.

Business Rules for Output Determination –

 

Below configuration steps are relevant for all application areas (Sales Order, Purchase Order, Billing Documents and Outbound Delivery)

SPRO - > Cross-Application Components -> Output Control -> Define Business Rules for Output Determination (Transaction: OPD)


In this Customizing activity, you can define how the system determines output parameters during document processing. You can define business rules for the determination of output parameters, such as output types, recipients, and form templates. 


Following determinations are available -

Determination	Number of Matches	Result	Example
Output Type	Multiple	Output Type to be used	Output BILLING_DOCUMENT can be determined on the basis of billing document type (F2).
Receiver	Multiple	List of Receiver Roles	Receiver roles (SP, SH, RE, RG) are determined for the determined output type (BILLING_DOCUMENT).
Channel	Multiple	List of Output Channels	Channels (EMAIL, PRINT and IDOC) are determined.
Printer Settings	Single	Output devices and number of copies	Output device (LOCL) for channel PRINT
Email Settings	Single	Sender Email address and Email Template	Sender email address & Email template (SD_CI_DEFAULT_EMAIL_TEMPLATE)  is determined for output type.
Email Receiver	Multiple	List of Email roles(To, Cc, Bcc) and email addresses	Email addresses for roles (To, Cc, Bcc) are determined for output type. This step is optional and system uses receiver email address in case step is not maintained.
Form Template	Single	Form Template name and language	Form template (SD_CI_STANDARD_DE) is determined with following options:  Output type, Receiver, Channel, Recipient language, Sender Country, Recipient Country and document category.
Output Relevance	Single	Can the document be output based on the defined condition (Yes/No)?	Output to be issued only when billing document is successfully passed to accounting.

Example of maintenance of Channel determination -

• Select Rules for relevant document, example BILLING_DOCUMENT.
• Select determination, example Channel to be used for triggering output type.
• Input parameters could be changed by adding input columns to determination table. Each determination table consists of input columns (condition columns) and result columns. You can add new input columns via the table settings.
• Maintain relevant input combination to determine the channel needed. Multiple channel can be selected for the same combination.

 
 
After changes, click on Save and Activate.

Output processing –

• Output determination is performed in document based on determination rules defined for Output type, receiver role, channel, form template, receiver email address and email template with the status as 'In Preparation'. Default data can be changed in the document.

                  Overview Screen:                     
                    
             Detail Screen: 
            

• Processing of output –

           Only two dispatch times are available in new output management system.

• Immediately (1)

                    Output is processed as soon as document is saved. If no errors, output type status changes to “Successful”. In case of errors, output will be in “Error” status. Errors can be viewed by clicking log button.

• Scheduled (2)

                    Output is processed using new transaction introduced VF31F for billing document.               
            

• Email output in SOST –

          Invoice copy is sent as PDF attachment.