S/4HANA

Fiori Advancements in Financial Closing Cockpit in S/4HANA 

Period end closing is always a critical and high visibility item in any ERP. The timely and effective monitoring and control of period end closing is top most need for the finance department. For this purpose, you must process a sequence of interdependent steps diligently in a specific and well-defined order. Entities use various tools for this, ranging from excel to more sophisticated tools like SAP Financial Closing Cockpit, Blackline’s Runbook etc.

BPC Standard to BPS Optimized for S/4 HANA

Design Summary and Guiding Principles

Overall Objectives

  • Develop a solution to improve the budgeting and consolidation business processes of the Company.

  • Integrate data in a centrally accessible repository storing one version of the truth.

  • Make the monthly reporting preparation more transparent and efficient by aligning process owners. Enhance collaboration between contributors.

  • Improve business information, enable business visibility and analysis of the cost base and standardize the management reporting outputs.

Securing SAP Fiori

SAP Fiori Help
 

This article is an excerpt from Securing SAP S/4HANA, courtesy of Espresso Tutorials.

Securing Fiori

SAP Fiori is a new user experience (UX) for SAP software and applications. It provides a set of applications that are used in regular business functions such as work approvals, financial apps, calculation apps, and various self-service apps. The SAP user interface, or SAP GUI as we know it today, was first introduced in 1992 together with the official release of SAP R/3. SAP R/3, the client server edition, was the successor to the SAP R/2 release, the mainframe edition. Although SAP has made several attempts to modernize SAP GUI, an end user from the time it was introduced would still find their way around today. Many transactions and screens have remained the same or changed very little. Since the initial release of SAP GUI, SAP has released several alternative user interfaces such as the SAP Workplace (which was part of the mySAP.com offering), the SAP Enterprise Portal, and the NetWeaver Business Client or NWBC. None were as successful as SAP GUI except, perhaps, for the NetWeaver Business Client. The NetWeaver Business Client is, however, an extension to the SAP GUI. The conclusion of all this is that although many people complained about the old-fashioned look of SAP GUI, they kept using it and will probably continue to do so in the future. But there is no denying the fact that the user community is changing fast. The SAP users of tomorrow are the youngsters of today, who are used to accessing data from their mobile devices. To them, SAP GUI is a relic from the dark ages. This shift is not limited to youngsters—many end users want data access from any device, from any place, at any time. SAP released SAP Fiori to respond to this demand. SAP Fiori is built using modern design principles you might expect from applications designed for smartphones and tablets. There are already more than 500 role-based Fiori applications such as for HR, Finance, and Business Intelligence. An SAP Fiori application is always limited to a specific task or activity. The design is responsive and deployable on multiple platforms. There are three types of SAP Fiori applications: transactional apps, fact sheets, and analytical apps. SECURING FIORI 46

Transactional or task-based applications

The transactional SAP Fiori applications are limited to specific tasks such as entering a holiday request or expense note. They give end users fast access to data and represent a simplified view of an existing business process or workflow.

Fact sheets

Fact sheets have far more capabilities than transactional applications. From a fact sheet, you can drill down into the details. You can even navigate from one fact sheet to another or jump to the related transactional applications. For fact sheets, the underlying database must be SAP HANA. An example of a fact sheet is an application that shows the overview and details of a piece of equipment and its maintenance schedule.

Analytical applications

Analytical applications build on business intelligence using the capabilities of SAP HANA. They allow you to monitor key performance indicators (KPIs) of your business operations and to react immediately as changes occur. An example is the sales orders application, which immediately shows your sales representative the sales history from his customer, allowing him to take discount decisions immediately.

Deployment options

SAP Fiori apps consist of front-end components, which provide the user interface and the connection to the back end, and back-end components, which provide the data. The front-end components and the back-end components are delivered in separate products and must be installed in a system landscape that is enabled for SAP Fiori. There are multiple deployment options for the SAP Fiori components, each with their respective advantages and disadvantages. SAP Fiori applications are accessed through the SAP NetWeaver Gateway. The gateway consists of two components: SAP Gateway Foundation (SAP_GWFND) and User Interface Technology (SAP_UI). Both components are add-ons, which from NetWeaver version 7.4, are part of the SAP NetWeaver ABAP Stack. With NetWeaver 7.31, the components had to be deployed separately. This means that any system built on SAP NetWeaver, such as SAP ERP or SAP CRM, can be used to deploy SAP Fiori applications. SECURING FIORI 47 The following deployment options exist: central hub deployment, the embedded scenario and the cloud edition (see Figure 2.1). Figure 2.1: SAP Fiori deployment options

Figure 2.1: SAP Fiori deployment options

Figure 2.1: SAP Fiori deployment options

Central hub deployment

The central hub deployment is the preferred option. Here, SAP NetWeaver Gateway is installed as a separate system. The Fiori applications are deployed here and access the data on the back-end business systems, such as SAP ERP or SAP CRM. Although this option implies an extra system, thus a higher total cost of ownership (TCO), it enables a multi-back-end system scenario while ensuring a consistent look and feel for the different applications. The central hub can be considered a single point of access for all mobile applications. In addition, installing SAP NetWeaver Gateway on a separate system allows you to move the system behind or in front of the firewall depending on your current network topology and security requirements. SECURING FIORI 48

Embedded scenario

SAP NetWeaver is the basis of all ABAP-based SAP applications, regardless of whether you are talking about SAP ERP, SAP BW, or any of the others. As the gateway is an add-on for SAP NetWeaver, it is available on every ABAP-based business application. This means that it can be activated and that Fiori applications can be deployed on any system. This makes an extra system unnecessary. However, we do not recommend the embedded scenario as, in contrast to the central hub deployment, it results in Fiori applications being installed all over the place— negating the advantage of the single point of access for all mobile applications. The embedded scenario should only be considered during a proof of concept or when the deployment of mobile applications is going to be limited to a single SAP application such as SAP ERP. 2.1.3

Cloud edition

The SAP Fiori cloud edition is a ready-to-use infrastructure which can serve as a front end while leaving the back-end systems on premise. The connection to the SAP Fiori Cloud is realized via SAP Cloud Connector, which must be installed on premise. The back-end components still have to be installed on the back-end systems.

Comparison of the deployment options

Table 2.1 compares the different deployment options. Every deployment option has its respective advantages and disadvantages. The importance of the pros and cons differ in every customer situation. We strongly recommend the central hub deployment option as it enables a single point of access to your mobile applications for SAP ERP, SAP BW, and many others, while at the same time ensuring the same look and feel. Due to its limitations and dependencies, the embedded scenario should only be considered in a proof-of-concept scenario.

Table 2.1: Comparison of the deployment options

Table 2.1: Comparison of the deployment options

Q&A: FIN REVENUE RECOGNITION - With the Deadline Looming, Are You Ready?

SAP Help

Get answers to the following questions in this co-hosted ASUG webcast:

  • This presentation focused on the use of RAR. But that has only been generally available since Mar, 2015. How many customers are actually using RAR? What about the rest (assumed to be the majority) who are using "old" functionality like basic SD Rev rec?

 

  • In your opinion, how long should the project be for a fortune 500 company to implement RAR, the right way?

 

  • What is software requirement to have implemented RAR in SAP ECC6 EHP6?

 

  • Do companies seem to be also changing all of their internal and management reporting and metrics or do most companies appear to only be changing their external SEC reporting to align with the new standard?

 

  • How does/can RAR handle revenue recognition based on estimates, when customer actuals are submitted a quarter later?

 

  • For a mining company with sales restricted to few customers, do you think RAR is a scope?

 

  • RAR requires a separate license, correct?

 

  • What all criteria need to be met for the company to be required for this reporting?

 

Watch the prerecorded webcast by pressing play:


Is your Contract Roll-Forward external disclosure report ready?

Poll stats from webcast attendees

When is your ASC606 US Adoption Rate?

Poll stats from webcast attendees

Q&A: What you should know about New Asset Accounting with S/4 HANA

August Post.png

Q: If you do not currently use the Fixed Assets module in SAP, and you are planning on moving to S/4 HANA, is it better to implement Fixed Assets before you move to S/4 or after?

A: Assuming that you are on SAP, it depends whether you have the new GL or not (as New GL is a pre-requisite for New Asset Accounting), whether you plan to have additional accounting principles, and whether you are converting to S/4 HANA on-premise or doing a Greenfield implementation, which version you are planning to move to and when. Uploading an excel file with batch processing via the LSMW is not available at the moment on-premise, but you can use a BAPI.  An asset upload is usually easier at a year end. If you are already on NewGL and planning to convert to S/4HANA at a year end, it may be easier to get the asset upload out of the way before the S/4 HANA migration.  In all cases I would get expert advice to examine all the facts before making a decision.

A: The fiscal year end of asset accounting must agree with the fiscal year end of Finance, (even if the periods differ) but how can you map a depreciation area with one fiscal year end if you have a different fiscal year end for the parallel ledger in finance?

Q: Lets say you have 0L with March year end and 2L with Dec year end. Create a new ledger e.g. NL with March year end and add to a new ledger group so the new ledger group has both 2L and NL in it and mark  NL as the representative ledger and map the depreciation area for the Dec year end to the new ledger group. This should allow you to post from asset accounting to a different year end in finance.

Q: Can you map depreciation areas to appendix or extension ledgers in finance?

A: No this cannot be done at the moment. The extension ledger posts only delta postings in finance.

Q: If you have an asset with different useful lives for example for local GAAP and IFRS, so that the total depreciation calculated to date is different, and you make a sale to a customer, how does the system post the different values to different ledgers, but the same amount to the customer?

A: The system will automatically use the technical clearing account in a similar way to an acquisition to post the different values in different ledgers.

Q: Can you set up asset accounting with Central Finance on S/4HANA?

A: FI documents from Asset Accounting that are sent to Central Finance are only replicated as FI documents and not currently as fixed assets, and some of the fixed asset information may be removed. Therefore, although in the source system, the APC and accumulated depreciation accounts are set up as reconciliation accounts, in the SAP S/4HANA Finance system, they are not and accept only finance postings.

Q: Is it beneficial to implement new asset accounting prior to upgrading to S/4 Hana?

A: Assuming that you are on SAP, it depends whether you have the new GL or not (as New GL is a pre-requisite for New Asset Accounting), whether you plan to have additional accounting principles, and whether you are converting to S/4 HANA on-premise or doing a Greenfield implementation, which version you are planning to move to and when. Uploading an excel file with batch processing via the LSMW is not available at the moment on-premise, but you can use a BAPI.  An asset upload is usually easier at a year end. If you are already on NewGL and planning to convert to S/4HANA at a year end, it may be easier to get the asset upload out of the way before the S/4 HANA migration.  In all cases I would get expert advice to examine all the facts before making a decision.

Q: For parallel ledgers with differing fiscal year variants, is the migration scenario mandatory for new primary ledger with same fiscal year variant as leading ledger?  Or, can new primary ledger be treated as a "technical ledger" only?

A: I think you can use the representative ledger box to get round this. Lets say you have 0L with March year end and 2L with Dec year end. Create a new ledger e.g. NL with March year end and add to a new ledger group so the new ledger group has both 2L and NL in it and mark  NL as the representative ledger and map the depreciation area for the Dec year end to the new ledger group. This should allow you to post from asset accounting to a different year end in finance.

Q: Each currency needs separate Dep. Area.  Can you please elaborate this from with current ECC EHP6 scenario?

A: It is the same principle as in ECC6, if you have two currencies in finance for a ledger you will need two depreciation areas, one for each currency, for that accounting principle. The main difference is that you no longer need any delta depreciation areas.

Q: How is archiving of FI_DOCUMNT impacted?

A: Not sure if this is a question about new asset accounting or asking if an S/4HANA migration affects already archived documents, or how documents are archived on S/4HANA.

Q: Where do you configure technical clearing account? In AO90 - Asset account determination, or somewhere else? Can you please specify.

A: You cannot configure the technical clearing account in AO90. It has its own section in the New Asset Accounting section under Integration with General Ledger Accounting in the IMG.

Q: I heard a new year could not be opened independently in both Finance and Asset Accounting and is done in a single t-code which is balance carry forward. The carry forward transaction to open the new year can’t be processed if the previous year hasn’t been closed. Does this mean that AJAB closing asset has to be performed before we open a new fiscal year?

A: It is correct that transaction FAGLGVTR, which is the general ledger carry forward is now used for asset accounting as well. However it only opens the new year and you can continue to post to the old year. You should not need to close the old year with AJAB before opening the new year. (In ECC6 i have seen the old year closed 10months later in one company).

Q: If LSMW doesn't work, will tools like WinShuttle or SHDB work?

A: It depends on the version of S/4HANA - I believe the Cloud version has its own tools. For on-premise you can use a BAPI, or transaction AS100 if you don't have too many items, or can split the upload into 2 or 3 uploads.I have not used either Winshuttle nor SHDB  to upload to S/4HANA, the Winshuttle website mentions Certified S/4HANA integration including the 1610 version, but I don't know about SHDB.

Q: For Depreciation areas that do not post to FI where is the data kept and what does it look like what tables do reports run against? Is it held in ADOCA and marked as statistical in some way?

A: ACDOCA contains actual data by ledger and therefore if a depreciation area is not mapped to a ledger it can't record data from it. FAAT_DOC_IT will contain statistical data.  Most of the asset reports can be run by depreciation area so you can see data in the asset module for all the depreciation areas in the same way.

Q: Can we change accounting principle on a depreciation area after the initial migration?

A: During the migration you may need to do some changes to the configuration, but if you want to point one depreciation area at a completely different ledger, It would be best to check with SAP as I am not sure of the consequences.

Q: Can we still use calculated depreciation areas in S4 still posting to ledge?

A: Yes, although as with most of my answers, you should carry out extensive testing to make sure that the results are as you expect.

Q: FYI: LSMW is still officially supported for RE and FI-AA legacy conversion. It just requires that you use the BAPI_FIXEDASSET_OVRTAKE_CREATE rather than a screen recording.  Note 2208321 has more information.

A: In the Simplification List issued for the S/4HANA 1610 release, it states: ""The LSMW (Legacy System Migration Workbench) function is still available within SAP S/4HANA, (onpremise edition) but not considered as the migration tool. LSMW might propose incorrect migration interfaces that cannot be used in SAP S/4HANA anymore. The Legacy System Migration Workbench (LSMW) is an SAP NetWeaver tool for data migration that was first introduced with R/2 to R/3 migrations. It uses standard interfaces like BAPIs, IDocs, Direct Input and Batch Input programs and recordings. Due to this nature, the use of LSMW is restricted for migrations to SAP S/4HANA. The Legacy System Migration Workbench (LSMW) can only be considered as a migration tool for SAP S/4HANA using workarounds and careful testing for each and every object. The use of LSMW for data load to SAP S/4HANA is not recommended and at the customer's own risk. However it then goes on to quote the OSS note 2208321 for one of the workarounds - hence the confusion.

Q: Will you still have the tax deprn available for reporting?

A: If I understand the question,  if you have a tax depreciation area set up and you keep that tax depreciation you should be able to continue to report on it after a migration.

Q: Pease could you confirm. I believe you said migration had to occur at fiscal year end and that you could not reopen the prior year once the migration was over. Our tax only books are often re-opened for the prior year.

A: I believe a New GL migration has to occur at a fiscal year end, but an S/4HANA migration,  can occur at any period end. If I mentioned a closed fiscal year could not be re-opened after migration I was referring specifically to a closed fixed asset year end at the time of migration.

Q: Does HANA still support multiple Chart of Accounts? Or are these now unified into a single CoA?

A: If you mean for example an operating chart or accounts, local chart of accounts or group chart of accounts, then they behave the same in S/4HANA. You still have the option to add a local chart of accounts to the company code in global parameters and enter the alternative account number in the GL account master data.

Q: We have to report by tax jurisdiction and have the tax jurisdiction on the asset will that still be there?

A: The tax jurisdiction field is still available in the asset master data.

Q: Is it possible to add parallel ledgers at the same time as S/4HANA migration?

A: You cannot add parallel ledgers during the migration.  I understand that adding parallel ledgers once on S/4HANA is now available since version 1610 on-premise.

Q: Could the AP invoice in the example have been posted w/ different amounts by ledger?

A: The initial AP invoice would have the same amount for each ledger, so for example the whole amount in one ledger could be capitalized and the whole amount in the other ledger could be expensed, but if you wanted to transfer part of the amount to say shipping costs you would need a subsequent journal using FB01L or AB01L posting to just the one ledger.

Q: It seems in 1605 you must add then parallel ledger in separate year.  can you do it in the same year as migration then with 1610?

A: I think it would be safer to check with SAP as I am not 100% sure of when the parallel ledgers can be added.

Q: We calculate tax depreciation each month and report it at the end of the year the the taxing authority we have a special tax depreciation area.

A: I see no reason that this would not work on S/4HANA although would need more detail to be sure what the exact question is.

Q: Can you open the new year with a pending new project adding a parallel ledger?

A: I think it would be safer to check with SAP as I am not 100% sure of when the parallel ledgers can be added.

Q: Heard that carry forward is only needed one time and will update automatically after performed if posting is made to prior year in the ledger. is this correct?

A: This is the carry forward transaction FAGLGVTR - this is how it worked in ECC6 and as far as I am aware should work the same in S/4HANA.

 

Watch the prerecorded webcast by pressing play:

Q&A: Demystifying the GR/IR Process

The Goods Receipt / Invoice Receipt (GR/IR) account is normally the most challenging account to manage. This is partly because of the number of transactions that are posted to it, and also because of numerous factors that could lead to its discrepancy.

Review the Q&A by Oona Flanagan, FICO Consultant and author of the SAP Press E-Bite “Invoice Verification with SAP: Payment Blocks in GR/IR Accounts”, where you can ask your most pressing questions such as:

- In transaction MIRO (post invoice) should I use a credit memo or a subsequent credit to post a credit note from the vendor?
- What is “Goods Receipt Based Invoice Verification” and when should I use it?
- What is the best way to post a “receipt” for a service?
- Why does my GR/IR account have a balance on it for a particular purchase order when the amount of the related invoices seems to be correct?
- When should I use Transactions MRBR to release an invoice and MR11 to write off a balance?