Monday, April 25, 2016

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

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:

Monitor CPU Consumptionm in one window command :top
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
Monitor Space at OS level in directory /usr/sap/trans with comma:df -h
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
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.

Tuesday, April 19, 2016

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

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

Friday, April 15, 2016

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.