SAP Fiori

Journal Entry Fiori Upload

The purpose of JE posting is to take a batch, validate it for consistency, and create FI documents and post those entries in various line item accounts needed for subsequent business processing.

JE Posting is a process that with a few exceptions runs "behind the scenes" (without user dialog) and is the heart of Journal Entry. It receives journal entry data (representing financial transactions) from the PRA modules (Valuation, Revenue Distribution, etc.), and summarizes them in batches and posts them to the PRA JE line item tables and to SAP FI. JE Posting is the link between the journal entries coming from PRA applications and the FI documents and JE line item table items that are created.

The JE Posting Module is automatically called by the various PRA application areas. For example, whenever you create a Valuation, Revenue Distribution, Checkwrite, Check Input, Tax and Royalty, Owner Suspense, or Accounts Receivable document, the JE Posting Process is automatically triggered, but the standard postings limited in such a way that it can’t handle mass upload of the JE records for various business needs like periodically post entire leasing documents and costs associated to it into SAP FI . Also, the standard SAP JE backend upload program provides the ability to rejected / errored out entries corrected online and it is a manual and tedious effort. This can be simplified by using this JE Fiori upload application by mass upload of the rejected records by downloading, correcting and uploading again

The need is to have an JE Fiori upload application so that the end users can validate, park / post the various financial records into SAP FI with ease , simplified and with great user experience.

First Steps in SAP Fiori

Excerpt from    First Steps in SAP®    Fiori    by: Anurag Barua

Excerpt from First Steps in SAP® Fiori

by: Anurag Barua


Chapter 4 SAP Fiori: An Overview

A question that many of my customers ask is, “What is SAP Fiori all about?” It’s a question that has a significantly long answer because SAP Fiori is not just one thing but rather a convergence of many things. Quite simply, it is SAP’s truly new user experience, or for those of you with a technical mindset, it is SAP’s new user interface. SAP Fiori marks the end of the era of the traditional gray screens of the flagship SAP GUI, which has existed for over two decades. SAP GUI has been a constant scourge for SAP users worldwide because of the over-abundance of fields and tabs that users have to either enter data in or click through and because of its distinct lack of visual appeal. For those of you interested in statistics, there are over 300,000 individual SAP screens that form the conduit for transactional processing. This is not a trivial number and what bewilders SAP users even today, is that a lot of these screens contain fields that are rarely used and every basic transaction has multiple screens that a user may have to scroll through.

SAP Fiori provides users with a standardized (tile-based) look and feel that is intuitive, visual, and offers fields that are displayed based on the user’s roles and authorizations.

At the heart of SAP Fiori is the increasing number of out-of- the-box apps (applications) that SAP provides which correspond to the whole gamut of standard business processes such as order entry (purchase or sales), leave request approval, etc. Currently, there are almost 500 apps available free of charge and if the investment into SAP Fiori is any indication, this number will continue to increase. If the SAP infrastructure prerequisites are met (I will discuss these later), you should be able to be up and running with any such app in a matter of a few hours. When I started my own SAP Fiori odyssey a couple of years ago, it took me approximately six hours to get a standard cost center app up and running. Disclaimer: All configuration on the infrastructure side had already been performed by the Basis/NetWeaver administrator and I was able to draw heavily on my years of SAP experience.

SAP Fiori represents a shift from transaction code-based interaction to interaction that is driven by business processes and the users’ roles and responsibilities in an organization and as maintained in the SAP security framework. The interaction is heavily influenced by the seismic shift that has taken place in the consumer marketplace, where business is increasingly transacted on mobile devices via simple apps. SAP Fiori leverages this concept to provide the same end user experience that eschews exposing the complexity of the solution and provides users with an engaging experience. It is based on the theory of “build once, run everywhere”. Therefore, with SAP Fiori, your app will run on your desktop as well as your mobile device and will look and feel exactly the same on both: you do not have to create a separate desktop version of your app and a separate one for your mobile device.

As the years have gone by, SAP’s advertising campaigns bear testimony to how the focus has shifted from highlighting its all-encompassing and integrated nature to a simplified, user-driven software suite. The journey from The Best Run Businesses Run SAP to Run Simple has seen SAP go through many ups and downs and

detours, has seen SAP go through many ups and downs and detours, including multiple acquisitions and strategy changes, as it has evolved from an introverted German software maker to a global innovation factory that provides speedy solutions with a high business ROI. And one of the primary lessons that SAP has learned well is that no matter how wonderfully efficient the software engineering is, it is ultimately the user experience that counts.

SAP Fiori apps have been designed using certain platform-agnostic design tools such as HTML5, JavaScript, and CSS. This combination of tools has been wrapped into something called SAP UI5 but I will come back to this a little later. As a result, SAP Fiori apps can be rendered on all kinds of mobile devices without the need for any software magic such as creating wrappers to ensure compatibility. Furthermore, this framework also provides users with a convenient means to enhance existing apps and incorporate users’ business needs.

SAP Fiori and NetWeaver security: A question that is often asked is whether SAP Fiori leverages the SAP NetWeaver security framework or whether you have to design security separately for SAP Fiori. The good news is that SAP Fiori allows you to leverage your existing NetWeaver security model. In fact, when you configure any app, the visibility and access are determined by the roles and authorizations that particular user is assigned to.

Keep reading in First Steps in SAP Fiori by Anurag Barua [].

Are you wondering what SAP Fiori is all about? Dive into SAP’s new user interface and gain an understanding of core SAP Fiori concepts and get quickly up to speed SAP Fiori functionality, architecture, prerequisites, and technical components. Walk through key configuration and get examples of what has gone well (and not so well) on real SAP Fiori implementation projects. Take a technical deep dive into the types of Fiori apps including transactional apps, analytics apps, and fact sheets and walk through custom development and enhancements. By using practical examples, tips, and screenshots, the author brings technical and non-technical readers alike up to speed on SAP Fiori.

  • SAP Fiori fundamentals and core components

  • Instructions on how to create and enhance an SAP Fiori app

  • Installation and configuration best practices

  • Similarities and differences between SAP Fiori and Screen Personas