GL Account Write-Up in S/4 HANA

# Why this article?

In 2012, I was on a SAP implementation project for one of the India’s largest cement producer. Its core team members were very smart and passionate about SAP. There was one Finance Core team member who was taking care of GL master including various other part of FICO. This user asked me about GL write-up, which he meant a document explaining the meaning/usage of each field of the GL account. I had prepared it there; the same document I have changed in regard to S/4 HANA changes in GL Account.

# Overview of GL Account in SAP S/4 HANA

G/L account master records is an account’s function. G/L account master records control posting of accounting transactions.

General Ledger Accounts (GL) in SAP are divided into two parts a. Chart of Account Section and b. Company Codes Section. GL is created initially for Chart of Account section and further extension is done to different company codes on need basis.

In S/4 HANA there many changes in GL master compare to ECC environment. Now General Ledger and Cost Element got merged.

# Changes in GL in S/4 HANA

* General Ledger Account and Cost Element got merged
* Secondary Cost Element is also considered as GL
* Secondary cost elements are also created through transaction code FS00
* Transaction code FS00 has been extended and changed to cater the changes all the changes in S/4 HANA in regard to GL
* Transaction code such as KA01, KA02, Ka03, KA06 have been removed. If you try to use them, you will be redirected to FS00.
* SAP tables are still updated as earlier like for GL SKA1 and SKB1 etc. and for cost element CSKA & CSKB etc.
* GL Account Type:

* X – Balance Sheet Account à Balance Sheet Accounts
* N- Non-operating Expenses or Income à Profit & Loss account used only in FI (Without CO).
* P- Primary Costs or Revenue à Profit & Loss account used both in FI & CO
* S- Secondary Costs à Profit & Loss account used for allocations in CO

* Cost Center default account assignment is not available at GL Account level. Default CO objects can be maintained in Transaction code OKB9 which is very stable & old functionality.
* Statistical Cost Element. Balance sheet GLs are also created as statistical cost element with category ‘90’. In S/4 HANA a check box is only appeared if any balance-sheet GLs are related to Material (OBYC-BSX) Account or Assets Account GL (AO90). This field is required for Fund management, internal order, WBS, and Investment order budgeting.
* ‘Manage G/L Account Master Data’ Fiori App is there in S/4 HANA

# Financial Statement Version (FSV) and Reports

* Special attention to be given while creating FSV because in S/4 HANA GL and CE got merged and everything can be seen in finance report including secondary cost element (which is also a GL in S/4 HANA) data. Business never prefer to see cost element and secondary cost element data related to CO allocation, assessment, distribution data which is generally considered to be specific to controlling. Now all these data can be seen in FI reports, Trial Balance & Balance Sheet.
* You need to understand business constraint and needs; and modify the FSV accordingly. You can remove those allocations (CO specific data) from FSVs.
* As mentioned above CO specific data can be seen in FI reports. As per requirement such data can be removed from reporting through report variant.

Note: When it is said that “such data can be removed” that does not mean this data will be deleted from anywhere, it will be stopped from seeing in the particular report.

# General Ledger Account’s Field-Wise Explanation

G/L account master records is account’s function. The G/L account master records control the posting of accounting transactions. Let’s get field wise understanding of GL Accounts in S/4 HANA.

a. Chart of Accounts Section

The Chart of Accounts section contains the data that is valid for all company codes.

Following are the fields in Chart of Account section

Field Name
Field Usage

G/L Account Number
Each account is given an identification number. This numbering could be numeric or alpha numeric. GL account numbering shall be decided very carefully as it is going to be there as long as your SAP system will be there. Generally GL account are kept with numeric numbering in following manner.
Starting with 1 = Liabilities Accounts, Starting with 2 = Assets Accounts, Starting with 3 = Revenue Accounts, starting with 4 = Expense Accounts, Starting with 5 = Any GL which shall be zero at any point of time and which is generally not analysed by business such as Cutover Upload GLs any Zero Balance Clearing Account, Starting with 9 = Secondary Cost Element (GL)

GL Account Type
It identifies if an account is:
X – Balance Sheet Account –> Balance Sheet Accounts
N- Non-operating Expenses or Income   –> Profit & Loss account used only in FI (Without CO).
P- Primary Costs or Revenue –> Profit & Loss account used both in FI & CO
S- Secondary Costs –> Profit & Loss account used for allocations in CO

Account Group
Account group controls which fields are available for use on the GL master creation screen. It also controls number range for GL. Account Groups are generally created based on high level presentation of Financial Statement as per the accounting standard.

Text Fields
In this field you give appropriate name to the GL. Short text (20 Characters) and long text (50 Characters).

Trading Partner
The trading partner is auto flowed during postings if it is maintained in GL accounts.

Group account
Group accounts (account from Group Chart of Account) is used to roll up transactional data of Accounts of multiple operational chart of account to a common account Balance sheet Consolidation

b. Company Code Section

The Company Code section contains the data that is valid for a specific company code. Company code section is extended to company code on need basis.

Control Data Tab has following are the fields in Company Code Section

Field Name
Field Usage

Account Currency
Account Currency. If the currency is the same as the company code’s local currency, then any document currency can be used when posting to the account. If not, then document currency must match that of the GL account currency. Different GL currency from company code currency is used where you want keep certain GLs like Bank accounts or investment GLs in specific currency and further you want all the posting to such GLs in only one currency only.

Only balances in local currency

If this field is flagged, any document currency can be used with this account.

Set the indicator in cash discount clearing accounts and GR/IR clearing accounts. It cannot be set in reconciliation accounts for customers or vendors. Setting it in all other instances is optional.

Exchange Rate Difference Key
This key specifies where exchange rate variances will be posted to.

Tax category

The tax category will allow the entry of a tax code during postings to account. Following Tax categories are available:

– Only input tax allowed

+ Only output tax allowed

* All tax types allowed

Output Tax Account

Posting w/o tax
This setting will enable postings to the GL without a tax code even if the tax category is set in previous step.

Recon account type
Reconciliation accounts are used in sub ledgers such as Assets, AR, AP. Direct posting to these GLs are not possible. Transactions to these GLs comes from sub ledgers.

Alternative  Account Number
The alternate account number is a free field and can be used as per business need. Generally it is used to map with legacy account numbers.

Tolerance Group for GL Accounts
Tolerance groups fields checks maximum percentage or absolute amount that can be written off during open item clearing.

Open Item Managed
If an account is tracked for its following process than Open Item Managed is ticked i.e. Tax Payable GL keeps accumulating postings from sales transactions and at the end of the period cumulated tax is paid to the tax authorities and posting is made in the same GL. Ultimately Tax Payable Account becomes Zero. Similarly GR/IR Clearing Account, Bank Incoming/Outgoing Accounts etc.
Note: All Reconciliation accounts do show open items in the reports (FBL3H/FBL3N/FAGLL03) but we still don’t need to select this flag for reconciliation account. It is inherited that if account is created with reconciliation account type line items would be tracked through open item management.

Line Item Display
If you want to see line items in SAP reports for an accounts in transaction code FBL3H/FBL3N/FAGLL03. You have to select this tick.
This tick is not selected in case where huge postings take place and are not actually posted for any business process or action. One example of this would “ZERO BALANCING ACCOUNT” which is required for document splitting.

Sort key
Many sort key fields are available in standard SAP and it can be further customised. It controls what value will be filled automatically during postings in ‘Assignment Field’.
For example: Sort Key 10 and 14 (Purchase Order & Item) is used for GR/IR Clearing account so that auto clearing (F.13) is enabled.

Authorization Group
Accounts can be controlled for who can make posting to an account with authorization group. It is a free field and you can put any value and the same value need to be put in the SAP user ID who is authorised to make posting to this account.
Authorization group is used for sensitive GLs.

Accounting Clerk
It helps identifying the responsible person for the account.

Cost Element Category
Cost Element Category is selected for profit & loss accounts. This is new field in S/4 HANA.
Available categories are e.g. 41-Over Head Rates, 42-Assessment, 43-Internal Activity Allocation, 21-Internal Settlement.
Note: Balance sheet GLs are also created as statistical cost element with 90 category. In S/4 HANA a check box is appeared if any balance sheet GLs are related to Material (OBYC-BSX) Account or Assets Account GL (AO90). This field is required for Fund management, internal order, WBS, and Investment order budgeting.

Record Quantity
This tick is selected to track quantity in accounts

‘Create/bank/interest’ tab has following are the fields in Company Code Section

Field Name
Field Usage

Field Status Group

The field status group controls what fields are kept as required, optional, display, and hidden during postings for an account. User happiness comes with minimum visible fields during postings.

It shall be analysed carefully what fields should be available for postings.

Post Automatically Only
If this field is ticked, the account cannot be posted manually.

Supplement Auto Postings
If this field is set, a ‘post automatically only’ account can have additional characteristics such as profit center or cost center and these fields can be filled or updated manually during posting.

Recn. Acct. Ready for Input
It determines that the reconciliation account is ready for input when posting a document.

Planning level
This field is used to classify the account’s activity in cash management

Relevant to cash flow
This field must be set to accounts which impact your cash flow. It enables cash management reporting for cash flow

Commitment Item
This field is used to classify the account’s activity in cash management

House Bank
Related house bank is updated here. It is updated in bank accounts only.

House Bank Account
Related house bank account is updated here. It is updated in bank accounts only.

Interest Indicator
If interest Indicator is given to an account; such accounts are considered for automatic interest calculation.

Interest Calculation Frequency
This indicator determines at which interval interest should be calculated and posted.

Note: Since the same GL is used by multiple company codes which might be situated in different countries which may have different language; to tackle such scenarios you can maintain different description in different language under tab ‘Key Word/Translation’.

# Manage G/L Account Master Data Fiori App Screen Overview:

________________________________________________________________________________

Many more such article on S/4 HANA topic to come. Stay Connected.

Learn, Share, Grow, & Succeed! http://bit.ly/2nuWjUI #SAP #SAPCloud #AI

Leading S/4HANA UX – How to extend a SAP Fiori app in SAP S/4HANA

As part of the S/4HANA Regional Implementation Group I’m privileged to work with and advise many of our SAP S/4HANA customers regarding making the most of the SAP S/4HANA User Experience.  One of the questions we are asked over and over and over again, is how to extend standard SAP Fiori apps to add a few extra fields, set up defaults, or hide a couple of unwanted fields, or just to reorganize the screen a little.  A lot depends on how the app was written. So now we have created a SAP Guided Answer to lead you through the extension process.

On a typical SAP S/4HANA project, you will usually identify some gaps or custom business needs for the user experience.  That’s just a normal part of adapting your S/4HANA solution to your business.

At this design stage you will usually already have your SAP S/4HANA Fiori Launchpad, your Fiori apps, and your other classic apps working. However for many customers, partners, and consultants, the Fiori world – and especially the Fiori for S/4HANA world – is not as well known as earlier solutions such as SAPGUI or Web Dynpro ABAP.

So your question is HOW do I extend the Fiori apps?

You can now use a SAP Guided Answer – How to extend a SAP Fiori app for SAP S/4HANA to lead you through this process.

Just read the introduction and scroll down to choose which type of SAP Fiori app you need to extend.

Why you want to use a SAP Guided Answer

Ok well the first thing that will help you understand what’s possible when extending Fiori apps is that while the apps are all written using SAPUI5 ( SAP Development Toolkit for HTML5 ) different apps can be based on different UI technology frameworks. These frameworks are essentially composed of different smart templates & features that provide implicit extension options and flexibility services that you can use to adapt your Fiori app.

While implicit extension options usually require developer tools and skills, Flexibility Services include features that can be used by authorized key users (such as power users, business process experts, and functional consultants on your project) and developers alike.  Typically these Flexibility Services are executed directly in the Fiori interface, e.g. using options in the Me Area or using specific Fiori apps such as KPI Workspace (for adjusting Smart Business KPI thresholds, targets, timelines, currency) or Custom Fields and Logic (for adding fields and business logic to business context scenarios that impact the behaviour of multiple related apps).

And of course the Fiori app could also be a freestyle app (i.e. written without a smart template) with explicit extension options. And of course some freestyle apps also have Flexibility Services built-in.

So being able to identify what UI Technology framework has been used, what extension options it provides and how to approach extending that type of app means you can approach extending a Fiori app with confidence.

Knowing what’s available for a specific Fiori app also helps you estimate effort – as flexibility services and implicit extension options are typically quicker to implement than explicit options.

What will you find in this Guided Answer 

For each type of Fiori app that can be extended you will find:

* How to identify what extension options your selected Fiori app provides
* What types of skills and tooling you will need to extend the app
* A typical process flow for approaching the extension

The process flow is particularly helpful for the many Fiori apps which provide multiple extension options, as it tells you in what sequence you should apply extensions.

You will also find a special section just for Fiori app My Inbox – just because it’s time and again the most popular app with SAP S/4HANA customers and it has some extra configuration capabilities you can use for extensions.

What else can you do 

You can also give us feedback on the Guided Answer. If there’s anything that’s not clear, or where you would like to see more information, or if there’s any other topics you would like created as a Guided Answer, or you just want to give us some encouragement, please add that in the feedback or in the blog comments here.

Becoming a SAP Fiori for SAP S/4HANA guru

You’ll find much more on our SAP Fiori for SAP S/4HANA wiki

You might also be interested in these Guided Answers:

* Finding the Best Available App for your Use Case
* Solving the infamous “could not open” app error

And you will find more Guided Answers in the Guided Answers Viewer.

Brought to you by the S/4HANA RIG http://bit.ly/2nsZbl6 #SAP #SAPCloud #AI