segunda-feira, 28 de outubro de 2019

Financial Planning Options in S/4HANA

(as of release S/4HANA 1909)
Planning applications have steady evolved at SAP.  In this blog we will explore available planning options with a focus on S/4HANA 1909.
Summary of available SAP planning applications:
Quick Overview:
SAP Cloud Platform (SCP) tools are SAP long term strategic offerings. SAP Analytics Cloud for Planning (SAC), which runs on SCP, is SAP’s recommended strategic planning application for most customers.  For those customers requiring an on-premise planning application, the SAP BPC Optimized for SAP S/4HANA application is the official alternative recommendation.
SAP S/4HANA ERP (Classic ERP Planning Transactions)
The former FI-CO planning t/codes have been removed from the user menu in SAP S/4HANA and the classical planning capabilities have been replaced by modern BPC/SAC functionality and content, there may be situations when it becomes necessary for the classic t/codes to be re-activated. For example, if the customer needs to use a robust planning allocation solution leveraging their actual allocation build, there is no equivalent feature in BPC/SAP.
CO-OM planning, P&L planning, and profit center planning are now covered by SAP BPC for S/4HANA Finance (formerly known as Integrated Business Planning) (SAP Note 2081400).  If you do not want to use SAP BPC for S/4HANA but classic FI-GL and CO-OM planning functions instead, you can continue to use the classic planning transactions. Bear in mind, however, that in this case the planning results are written to totals tables and not the ACDOCP table. Reports designed specifically for use with S/4 HANA Finance do not read these totals tables, so the planned data will only be visible in Report Writer/Painter transactions.
The following key SAP Notes provide details on availability of classic ERP planning and its re-activation:
Key note on using the classic FI-GL and CO-OM planning functions:
2270407 – S4TWL – Profit and Loss Planning, profit center planning, cost center planning, order planning, and project planning
FI-GL Planning – SAP Note 2253067 describes how to reactivate
Profit Center Planning (classic)
SAP Notes 2345118 and 2313341 describe how to reactivate Cost Center Planning by Cost Element, Order Planning by Cost Element , Project Planning by Cost Element , and Project Planning Overall (transaction codes are all no longer in menu but can be reactivated for use in SAP S/4 HANA)
SAP Business Planning and Consolidation for Netweaver
SAP Business Planning and Consolidation for Netweaver (BPC_NW) is a mature, fully-functional planning and consolidation application utilized by thousands of customers. It continues to be supported and maintained so customer’s investments are protected. SAP BPC_NW 10.1 version for Netweaver will receive mainstream maintenance until at least 31-Dec-2024 – please refer to the SAP Product Availability Matrix (PAM) for support dates by specific product version.
SAP BPC_NW continues to be a key part of SAP’s Analytics portfolio, specifically for those customers requiring an on-premise stand-alone (BPC_NW is deployed within a stand-alone SAP Netweaver system) planning application.
SAP Business Planning and Consolidation for Netweaver consist of two model types: Standard and Embedded.  The Standard model was designed for with local ownership and control in mind, while the embedded models were originally evolved from SAP BW Integrated Planning functionality and is a more centralized, IT focused approach. From a technical perspective, Embedded models use a multi-key figure-based data model, while Standard models use an account-based data model. These models can be combined and used in the same license.
Reasons for requiring an on-premise application include:
  • Regulatory requirements
  • Corporate policy or contractual agreements
  • Ability to deliver deeply integrated planning capabilities as an integral component of an on-premise SAP data warehouse
  • Requirements for customization beyond the scope of a public cloud solution
SAP will deliver major new planning enhancements based upon SAP Analytics Cloud, but BPC_NW customers can leverage these enhancements as well via “hybrid” integration with Analytics Cloud ensuring an alternative path of continuous innovation.
BPC Optimized for S/4HANA
Designed to function from within a S/4HANA installation, Integrated Business Planning for Finance (IBPf) was the first dedicated S/4HANA financial planning application. IBPf was re-branded in S/4HANA release 1610 to BPC Optimized for S/4HANA.  A limited embedded BW is provisioned within S/4HANA and provides the support to host the BPC Optimized application.  Caution:  The S/4HANA embedded BW is not intended to be used as an Enterprise Data Warehouse (SAP’s recommendation for EDW scenarios is to use a dedicated BW/4HANA solution instead).
BPC Optimized for S/4HANA provides only the embedded modeling option.  “Actuals” are sourced from ACDOCA and plan data is stored in the ACDOCP table (additional data modeling variations can provide some data model flexibility on where plan data is ultimately stored).
BPC Optimized for S/4HANA (or IBPf) is not the same as IBP (Integrated Business Planning). SAP Integrated Business Planning focuses on supply chain monitoring, sales and operations planning, demand management, inventory planning, and supply planning.
The decision to use SAP BPC Optimized for S/4HANA should also consider the anticipated volume of data. The rule of thumb is to use SAP BPC Optimized for S/4HANA when approximately 80% (note that this percentage is only a guide and not a hard limit and may vary due to factors such as anticipated OLAP reporting requirements) of the data is already existing within S/4HANA. The following SAP compilation note provides additional details: 2081400 – SAP BPC Optimized for S/4HANA Finance.
SAP Business Planning and Consolidation for BW/4HANA
SAP Business Planning and Consolidation 11.x, version for SAP BW/4HANA is a new product based on SAP BW/4HANA. This product supports the HANA database and uses SAPUI5 user interface technology. The SAP UI5 user interface is based on standard HTML5, which provides all the benefits of HTML5 and supports languages such as Hebrew and Arabic that are written and read from right to left. BW/4HANA is a new, next-generation data warehouse product that is optimized for the SAP HANA platform, delivering real-time, enterprise-wide analytics that minimizes the movement of data and connecting all the data in an organization into a single logical view.
SAP Business Planning and Consolidation 11 can be deployed in two configurations:
  1. In an embedded configuration, Business Planning and Consolidation is integrated with SAP HANA-optimized processing, through which you can perform SAP HANA-optimized planning.
  2. In a standard configuration, you can use all the functionality that is available in the standard configuration of SAP Business Planning and Consolidation, version for SAP Netweaver.
SAP Analytics Cloud
SAP Analytics Cloud (SAC) is SAP’s strategic next-generation software-as-a-service (SaaS) solution built from the ground up that allows business users to plan, discover, predict, and collaborate all in one place.  SAC enjoys the benefits of a modern user interface that allows usage across all mobile devices.
SAC planning has deep integration with S/4HANA and the ability to deploy delivered connectors that allow the free movement of data between S/4HANA and SAC.
Data can be accessed by SAC using a “live” connection, providing run-time access to S/4HANA data and KPIs:
https://help.sap.com/viewer/00f68c2e08b941f081002fd3691d86a7/release/en-US/d2a1edf7cda74315a2c5052de8a3a4eb.html ]
SAC enjoys significant predefined content that makes productive integration with S/4HANA easy and efficient.  For more details on SAC : S/4HANA available content:  https://www.sapanalytics.cloud/learning/business-content/ and  https://rapid.sap.com/bp/#/BP_OP_ENTPR .
New planning content for SAC: S/4HANA 1909:
Revenue Planning with SAP Analytics Cloud is new content for SAC: S/4HANA 1909 financial planning (see description for scope item 1YB below):
Listing of all new S/4HANA 1909 relevant SAC content:
To stay up to date on the latest new SAC-S/4HANA 1909 content, follow this link:
https://help.sap.com/doc/474a13c5e9964c849c3a14d6c04339b5/100/en-US/8880de6dbfb94ea3b0de1f26b40816dc.html?version=1909
and search for “Analytics Cloud”.
Summary of the Financial Planning Options in S/4HANA:
Summary
The right planning solution is both a technical and functional decision. It depends on where the source data is coming from, which features the customer needs and how much data is required to be consumed. The timing of the implementation should also be considered. SAP strategic development is focusing on the SCP tools, but while initially some features may have been more robust in the mature BPC products, SAC has been quickly maturing into a full function planning application.

This is an official SAP RIG (Regional Implementation Group) blog.

Source: https://blogs.sap.com/2019/10/25/financial-planning-options-in-s4hana/

SAP Fiori Theme Customization

Introduction

SAP Fiori  is  a good design system. It can bring us unified user experience. It contains 5 themes, SAP Belize, SAP High Contrast Black, SAP High Contrast White, SAP Blue Crystal, SAP Quartz Light by default. In many cases, these theme’s color or font size cannot meet the needs of customer. So you can customize the theme base on one of the base theme. If you want to build your own theme, just follow me.

Process framework overview

Prerequisites

1. You need to have an adequate understanding of sapui5 framework
2.  You should have a hana cloud platform like
        https://account.cn1.hana.ondemand.com/cockpit/ 
3. You have the SAP GUI system and can login a system.
4. You have basic understanding of t-code in SAP GUI.

Detail Steps

  1. Create a new SAP UI5 Application with SAP Web IDE Full-Stack.
  2. Open the project and and open the file neo-app.json
  3. Append the json content into the routes property
     {
        "path": "/themedesigner",
        "target": {
           "type": "application",
           "name": "themedesigner"
         },
        "description": "Route for theme designer"
     },
    {
       "path": "/theme1",
        "target": {
            "type": "application",
             "name": "theme1"
         },
         "description": "Route for theme"
    }
   4. Run the ui5 application and modify the url like this
        https://....hana.ondemand.com/themedesigner/index.html 
      (The ellipsis parts depends on your subaccount name)
   5. Create a new theme as follows,

  
  After that, you can create a new theme base on the 5 kinds
  base theme.

   6. Design the theme with the designer tools

    There are 4 kinds of design tools.
    <1> Quick  The easiest way to design the theme for a beginner.
        You can modify the parameter according to the panel. 
    <2> Expert If you have mastered the sapui5 css rule, 
        this is suitable for you. Here is a small example.

 
 After you change the tile title text color, the preview page will 
 take effect at once.
    <3>Palette  If the colors are come from the ux designers, 
       you can define some colors here. And use the color in above picture.
       Here is a small demo
        3.1 Firstly, define some colors in the palette 
        

        3.2  Use the predefined color

        
    <4>CSS You can define some css from technical code. And then you can apply
       them in the page.

7. Save and publish --> export-->generate and download a new zip file

   You need select the second option in the picture as follows. Or else, 
   the theme zip file maybe too large to import into the new system.
    

8. Import the zip file into a new system.

   8.1  login the SAP GUI system and run t-code /n/ui5/theme_tool. You can see 
        the available themes in the system. And don't modify these themes.  If you 
        cannot open the theme tool, please run the t-code /nsu53 to view the 
        permission information.
   8.2  click the upload and import the zip file that be exported before
      

 
   8.3 login in the new system and the new imported theme will be available.
   

 
    8.4 Select the new theme, and it will be take effect in the home page.
    
 9. Transport the theme to QA or PROD system

    9.1 Create the Transport button, it will tell you to input a request no. 

    
   9.2 Create a Custom Request in the GUI, a new request No. will be generated.
       (You cannot create a Workbench Request here.)
    
   9.3 Execute transfer.

10. The new theme will be available in the new system.

Now you can apply the new theme in new system.

  Congratulations, you have finished the all steps for a new fiori theme.

Conclusion:

Finally we achieve our goal to build a custom theme and apply to the aim system.
This is a whole process to build a basic custom fiori theme and transfer it to product system.
Hope you can do some deep discussion with me.

Related Resources

SAP Fiori ByDesign

SAP Fiori UI Theme Designer

SAP Fiori

Integrated Analytics: SAP Analytics Cloud now embedded in SAP S/4HANA Cloud

Word’s out! Jürgen Müller, SAP’s Chief Technology Officer and Executive Board member, has announced the general availability of embedded SAP Analytics Cloud for SAP S/4HANA Cloud customers at TechEd (see Details here).
This blog provides additional insights, trying to help answer the questions that this announcement may have triggered for you:

Q: What exactly is SAP Analytics Cloud?
A: SAP Analytics Cloud is a SaaS solution for analytics, planning and smart prediction. Please refer https://www.sapanalytics.cloud/ for details.
Q: Why does SAP S/4HANA Cloud embed SAP Analytics Cloud?
A: Next to integrated operational processes, it takes first-class analytics to make an enterprise intelligent: Business users expect pre-defined reporting, seamlessly embedded into their daily work. They expect personalized access to data and ad-hoc analytical capabilities to get as much value out of their enterprise data as possible. And with the deep integration of SAP Analytics Cloud into the solution, this is exactly what SAP S/4HANA Cloud customers get with the 1911 release.
Q: How does the embedding work?
A: For each SAP S/4HANA Cloud tenant, a new SAP Analytics Cloud tenant is provided. The SAP Analytics Cloud accesses the ABAP CDS views live, using the transient analytical queries generated automatically for the CDS views. Please look at the Architecture diagram in Figure 1: High Level Architecture. SAP Analytics Cloud UIs will be embedded in iFrames and published on the Fiori Launchpad.
All relevant SAP Analytics Cloud features – from tenant provisioning and connectivity to content management and lifecycle – have been published as APIs, so the embedded SAP Analytics Cloud can be “remote controlled” by the embedding applications. These APIs are available to other applications and even Partners.
This means, that the embedded SAP Analytics Cloud is completely managed by SAP S/4HANA Cloud. Customers do not need to log on to the embedded SAP Analytics Cloud specifically, nor can they.
Figure 1: High Level Architecture
Q: Does “embedded SAP Analytics Cloud” go beyond a simply iFrame integration?
A: Yes! SAP Analytics Cloud is deeply embedded into the Fiori UX paradigms: Launched for the Fiori launchpad and based on live data connections and thus up-to-date information, SAP Analytics Cloud stories are integrated by means of a “wrapper application”: This software takes care of offering screen-variant saving and personalization features as well as intend-based navigation between analytical and operational applications. Role-based assignment of the SAP Analytics Cloud Stories is also available, and the content lifecycle is also fully handled by SAP S/4HANA Cloud.
(A lab preview showing screen variants and Intend-based navigation can be found in Figure 2. Of course, users will not be able to simultaneously trigger both option. These options have been overlaid in one screen for simplicity.)
Figure 2: Lab Preview — Screen Variants and Intend-based Navigation
Q: What scenarios are supported? In which way are embedded and enterprise tenants different?
A: The embedded SAP Analytics Cloud uses the live data connection to the embedding S/4HANA Cloud data exclusively. Thus, up-to-date dashboards and ad-hoc data analyzer scenarios as well as the consumption of analytical applications are supported.
If you are interested in scenarios that require data acquisition, e.g. planning or prediction, or a cross application scenario, you need to license an enterprise SAP Analytics Cloud tenant in addition.
See Figure 3: Embedded and Enterprise scenarios for details.
The embedded tenant does not interfere with the enterprise tenant, so you can continue to connect from the enterprise tenant as if the embedded did not exist. To save potential double efforts, means to move content from the embedded to the enterprise tenant are being looked at.
Figure 3: Embedded and Enterprise scenarios
Q: Do all SAP S/4HANA Cloud customers receive the embedded SAP Analytics Cloud or do I need to apply for it specifically?
A: No need to apply: During the course of Q4/2019, all SAP S/4HANA Cloud customers receive the embedded SAP Analytics Cloud in a phased approach. Details will be communicated, e.g. in this Roll-Out event. Customers do not need to trigger this.
Q:  How do SAP S/4HANA Cloud customers receive the embedded SAC? Does an additional scope item need to be implemented? How much effort does that create?
A: After the upgrade, dedicated scripts spin off a new SAP Analytics Cloud tenant for each S/4HANA Cloud tenant (so, one for your Q and one for your P system). These scripts also set up the live data connection between SAP Analytics Cloud and S/4HANA Cloud and finally hook SAP Analytics Cloud into to common user management. Thus, the entire system landscape enhancement is fully automated. No additional scope item needs to be implemented.
Q: What can customers expect in terms of predefined dashboards?
A: The last step of the landscape provisioning is the automatic installation of so-call business content. SAP Analytics Cloud models and stories are installed in your tenants and they are ready to run.
The first delivery focusses on Finance, so expect the following dashboards and data analyzer reports:
  • Group Financial Statements
  • Aging Report for Accounts Payable
  • Treasury Executive Dashboard
  • Disputes
  • Group Data Analysis
  • Group Data Analysis With Reporting Rules
Q: Can the pre-delivered dashboards be modified?
A: Yes, by making a copy of the pre-delivered dashboard and modifying the copy. Actually, this functionality will be made available in the release 2002 according to current plans. Until then, business users may use the screen variant saving to personalize the stories for their needs.
Q: Can I build my own content?
A: Yes. SAP S/4HANA Cloud extensibility concepts also apply to content: Key users can use the already existing Fiori application “Manage KPIs and Report” to build their own stories with the intuitive what-you-see-is-what-you-get WYSIWYG SAP Analytics Cloud designer. You may even create your custom ABAP CDS view and build your own content on top of this.
Q: How does the lifecycle of custom content work?
A: SAP Analytics Cloud artefacts will be moved to receiving tenants using the standard SAP S/4HANA Cloud mechanisms. SAP ensures, that content and other configurations or enhancements (like your custom CDS view) are consistently treated automatically.
Technically, the Analytics Content Network (ACN), an integral component of SAP Analytics Cloud, takes care of moving content between tenants. This technical process has once more been included into the Fiori tool set and thus customers do not need to trigger any additional processes to move content.
Q: Does the “embedded scenario” require additional licenses?
A: No, the embedded SAP Analytics Cloud features are covered by the existing SAP S/4HANA Cloud license.
Q: Does the embedded SAP Analytics Cloud replace any other technology or product?
A: No, it does not. It is an additional offer to support dashboard and data analysis. If at a later state technology or products will be substituted by SAC, this will be announced 2 releases in advance as always.
Q: Is the embedded scenario restricted to SAP S/4HANA Cloud?
A: Yes, for the time being. The complete embedded experience is not available yet for SAP S/4HANA on premise. While the URLS to SAP Analytics Cloud stories may even today be added to Fiori tiles, the result cannot be called truly embedded, not least because a new window will be opened. The above-mentioned wrapper application ensures the tight integration between Fiori UX and SAP Analytics Cloud. Similar coding will eventually be made available for SAP S/4HANA on premise, according to current plans with the next major release in Q3/2020.
The end-to-end tenant provisioning will most probably not be included, so customers of SAP S/4HANA on premise will have to pay for a license and the system landscape management will be a one-time manual effort.

Part#1. SAP CDS views Demystification

With this blog post series, I am trying to put together CDS views concepts and technology in detail with screenshots so that you can better understand even though you do not have access to S4HANA system.  I will break this knowledge into multiple blog posts with this first blog post as an introduction and index to all others.  So let’s get started.
Introduction:
CDS stands for Core Data Services.  This is the new programming paradigm within new SAP environment specifically S4HANA systems.  CDS views can be created without HANA DB as well but I will focus on an S4 system with a HANA DB as that is the future road map of SAP .
If you are not new to SAP, by now you might have already explored what HANA brings on the table.  In a nutshell, HANA is an in-memory database which enables high speed data processing.  With this awesome feature, SAP has tried to put all the logic calculations back into the database instead of the application server as it was done prior to HANA.  So CDS views are the new programming design concepts which can achieve Code-to-Data paradigm which actually means Code push down into the database for processing.  CDS is an enhancement to standard SQL technology which runs within ABAP layer which means that the design time objects are created in the ABAP layer and can be transported by regular Transport mechanism with a TR number assigned to each object.  The Design Time object is created in database i.e. the HANA DB which enables Code-to-Data shift.
As I mentioned, CDS is an enhancement to standard SQL language, it has all SQL features as below;
  1. DDL – Data Definition Language.  Used to CREATE Table, MODIFY Table etc.
  2. DQL – Data Query Language.  Used to READ data.
  3. DCL – Data Control Language.  Used to configure ‘SECURITY’
  4. Expression Language – Mathematical calculations, conditions Case..Endcase etc.

Let’s dive deep into CORE DATA SERVICES..
      Part# 2. Create a Basic CDS View: Learn about the default annotations while creating a basic CDS view.
    Part# 3. CDS view with Expressions and Session Variable: Find how to configure mathematical expressions and session variables to fetch system parameters.
    Part# 4. Consume CDS View in an ABAP Program: Check the new ABAP syntax to consume CDS view.
    Part# 5. CDS View Extension: Learn the concept of re-usability within CDS views.
    Part# 6. Parameters in a CDS view : Learn how to filter data in a CDS view
    Part# 7. How to search for SAP standard CDS Views : Find ways to search for SAP delivered CDS content.
    Part# 8. CDS Views – Joins and Associations : Learn to combine data with multiple tables or CDS views.
    Part# 9. CDS View – OData Service : Publishing to the outer world : Learn how to create an OData service.
    Part# 10. CDS Views – @VDM Annotation: Check the SAP Best Practices for CDS view development
    Part# 11. End to End Data Modeling and Reporting with CDS views: Hands on with a complete business scenario for a simple analytical requirement.

To summarize, with above blog posts you are able to understand the CDS views way better than just high level information scattered around all over internet.  Its mandatory to learn CDS views to work on S4HANA systems as a technical expert.  Hope you have enjoyed it.
Stay tuned for more on CDS security and other topics.

Keep learning..
SK.

S/4 HANA: Between Migration and New Implementation

Based on SAP announcement to prolong mainstream maintenance until the end of 2025 for SAP Business Suite 7 core application releases including SAP ERP 6.0, SAP Customer.
“https://news.sap.com/2014/10/sap-committed-innovation-choice-sap-business-suite/”
This make moving to SAP S/4 HANA is only a matter of time.

SAP provides three options to have S/4 HANA system:
1- Conversion / Migration
2- New Implementation / Greenfield
3- Central finance implementation

This blog post helps to getting better decision for moving to S/4 HANA using one of first two options.

In order to provide appropriate recommendation for which method to use, we need to:

  • First : Discuss , Explain and Get answers for predefined questions:


Here are Questions in more details:

  1. Do you want to keep your solution enhancements (ABAP Code for Non-standard solutions / Functions)?
  2. Do you want to keep your transaction data history (Not only open items or balances but full SAP ECC historical data)?
  3. Do you need a phased business roll out (Ex. Introduce some firori apps as starting phase, not all S/4 HANA capabilities at once)?
  4. Does your system fulfill all conversion prerequisites? (Like Update to latest version of ECC6 Enhancement package .There are several tools that can be used to check the prerequisites for moving to Suite on HANA or S/4HANA from ECC 6 Any DB)
  5. Do You Perceive your current system as Key Asset (Percentage of Current system satisfaction is important key here)?

  • Second : Answers analysis

If Answers for all previous questions or majority are YES, we recommend Migration option as it going provide following benefits:
▪ Faster move to SAP S/4HANA: Conversion mainly takes much less time than new implementation as SAP ECC system is up and running with all functions , Integrations and authorization
▪ Preserve historic data: All Historical data will be migrated and still reachable on current system (Note: Un-needed Historical data recommended to be archived to reduce migrated documents size)
▪ Investment protection: S/4 HANA migration will contribute to client new investment, will not start from beginning to start a new implementation
▪ Limit change management: Change management for migration and tracking delta are less than new implementation
▪ Prepare for business innovations: Massive innovation capabilities for S/4 HANA with new industry specific business processes and integration to the Cloud, SaaS applications, IoT and beyond.
▪ No initial load of data: All ECC system data will be migrated that’s why no more data upload needed either master data nor beginning balances

However, if the answers or Majority of them are NO, We need to ask following direct question:

  1. Do you need a renewal of your complete ERP solution? If answer is YES

Hence, Going with Fresh S/4 HANA new implementation Option is recommended, with all new implementations considerations.