Does SAP Simple Finance 2.0 change the Ledger concept in SAP?
Does SAP Simple Finance 2.0 change the Ledger concept in SAP?
SAP introduced New GL renamed later to SAP GL with Leading Ledgers and Non Leading Ledgers almost 10 years ago This was meant to replace good old solutions like parallel accounts, dummy LEs, special purpose ledgers that SAP customers have been using for a long time to report financials under multiple accounting standards. There are still quite a few customers who are on latest versions of SAP but still use parallel accounts approach. I asked a few why and did not get a good answer and I surmised that their finance users got used to the Parallel accounts approach and did not want to enhance the functionality. Wherever I designed SAP GL post 2005, I recommended 2 ledgers minimum and 3 ledgers in few cases : Leading Ledger 0L for US GAAP, One Non leading ledger for local GAAP and another Non leading ledger for IFRS if there is as dual reporting requirement in local countries during transition period
In early 2015 SAP released SFIN 2.0 and introduced Appendix Ledger (AL) concept. I was in a S4/HANA workshop recently with finance stakeholders who are considering implementing S4/HANA and they had several questions on what this new AL ledger is and also how the Leading and Non leading ledgers get impacted with SFIN 2.0. I thought of sharing key changes to the ledger design with SFIN 2.0. I had to get a bit technical on this topic and apologies for that.
Leading Ledger 0L
Leading ledger 0L still stays in SFIN 2.0 and US Customers should use this primarily for US GAAP reporting. However the two underlying physical tables in which all the transactions are stored, FAGLFLEXA (line item table) and FAGLFLEXT (totals table) are no longer there and are replaced by a new table ACDOCA which is the detailed line item table. This table has 360 + fields and provides the basis for majority of reporting in SAP both statutory and managerial going forward. BSEG table will still be there though I have a feeling that this is probably temporary and over a period of time ACDOCA will be the solitary table that stores all Financial/Managerial data. In a perfect world why we should have more than two tables in ERP systems for financials - one for master data and one for transactions. With SFIN 2.0 almost every total table in SAP will go away because totals can be done on fly as the application logic runs on HANA database which is fantastically fast. 0L Leading Ledger by default gets assigned to all legal entities (Co Codes in SAP) and no change to that in SFIN 2.0. SAP document number that gets generated when you post financials postings is now unique regardless of which ledger you post which is different to multiple document numbers in previous versions.
Non Leading ledgers
Non leading ledgers still stay and can be used for select legal entities that need to report in different accounting standards. Normally when you post an Accounting document, you do not post to a ledger but to a ledger group. Ledger group is where you group the Leading ledger and associated Non leading ledgers so that you enter Journal entries only once and all the ledgers within that ledger group get updated with values. If you have to make adjustment postings for different accounting standards you do that only in specific Non leading ledgers. Similar to Leading Ledgers, Non Leading Ledger financial postings that were previously stored in FAGLFLEXT and FAGLFLEXA in ECC 6 will be replaced with new table ACDOCA in SFIN 2.0. You can have a different fiscal calendar for the same Legal entity – one for leading ledger and one for non- leading ledger and there is no change to that. You can continue to close periods in Non leading ledger though they are open in Leading ledger and vice versa. So basically the functionality for Leading and Non leading ledgers did not change though the underlying tables changed.
Appendix ledgers
This is a new concept that was introduced in SFIN 2.0. These are new ledgers that sit on top of the Leading ledger. When you create an Appendix ledger in SAP, you flag it as “Appendix Ledger” and link that to a base leading ledger. Unlike Non leading ledger, Appendix Ledger cannot have a separate fiscal year different to Leading ledger but at the same time, you can open and close fiscal periods separately from Leading ledger. All the financials postings that happen in Leading ledger 0L are available for reporting purpose in Appendix Ledger though they are not physically updated. In addition to that, you can manually post management reporting adjustments directly in Appendix Ledger. Please note that in case of Non Leading Ledgers, you can post manual postings and system generated postings like foreign currency valuations etc but it is not the case with Appendix ledger
Now what is the Use case for Appendix ledger? From what I heard from SAP Architects and my read of partner documentation, the main use case is to give business a “Management” Ledger without impacting your Financial/Statutory reporting ledgers like Leading and Non leading ledgers. You do not get AP/AR details in AL and the only way you update Appendix ledgers is through manual postings with limited SAP transactions. I am yet to hear from any ramp up Customers on how they used AL and their experiences. SAP documentation, release notes etc are also still light on this concept. In my view, the Use cases for Appendix ledger are still be established with real business benefits and so as of now I am reserving my recommendation on using AL for new implementations till there is better clarity on this functionality from SAP and we hear some success stories.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/29829936/viewspace-2123609/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- How does SAP freelancer find a project that is not tough?Project
- SAP Retail Listing – How does it work (中英文對照版)AI
- SAP UI5 Form 和 Simple Form 的設計規範UIORM
- SAP Fiori SSL 和 SAML 2.0 配置文件
- SAP ME12 修改PIR,系統提示:Condition type P000 does not allow supplementary
- SAP CRM Advanced search和Simple search裡Max hit表現行為的差異
- SAP SD Reference Guide: SAP NotesGUIIDE
- 關於 SAP ABAP SYSTEM_SHM_OPEN_CHANGE_LOCK 執行時錯誤的問題
- SAP MM 公司間退貨STO的交貨單PGI報錯 -Purchase order 4500000773 does not -
- SAP UI5 Simple Form 控制元件的使用方法介紹試讀版UIORM控制元件
- SAP Emarsys 和 SAP Spartacus 的整合
- SAP 如何啟用SAP IS-RETAIL?AI
- 從SAP Leonardo到SAP Data IntelligenceIntel
- Generate Distribution Model from SAP ERP to SAP EWM in SAP S/4Hana
- SAP UI5 Simple Form 屬性 columnsL,columnsM,columnsXL 的屬性深入剖析試讀版UIORM
- SAP HANA 2.0 SP07版本新功能特性彙總
- SAP整合技術(十三)SAP Cloud IntegrationCloud
- 「SAP技術」SAP不夠嚴謹?
- SAP UI5 sap.ui.Device.media.RANGESETS.SAP_STANDARD_EXTENDED 介紹UIdev
- SAP PI
- SAP整合
- SAP Fiori 2.0中文版系列視訊教程(中文首發)
- Fabric 1.0原始碼分析(26)Orderer #ledger(Orderer Ledger)原始碼
- SAP對工單做101收貨,報錯- Check table TFBEFU_CR entry 10 does not exist–對策
- SAP R/3,SAP ECC 和 SAP S/4HANA 的聯絡和區別
- SAP ECC,SAP HANA和SAP S/4HANA之間有什麼區別?
- 「翻譯」SAP製造整合和智慧(SAP MII)
- SAP freelancer接SAP專案的幾種方法
- SAP Business Application Studio和SAP雲平臺DestinationAPP
- SAP Commerce(SAP Hybris)學習資料彙總
- sap.ui.require in SAP UI5 and require in nodejsUINodeJS
- 基於SAML2.0的SAP雲產品Identity Authentication過程介紹IDE
- NEW CONCEPT ENGLISH 51 - 60
- sap strans 表格
- SAP-Dialog
- SAP Stock Inconsistency
- SAP Fiori + Vue = ?Vue
- SAP MM 對採購訂單執行收貨,報錯 - Table T169P entry ZNMI does not exist -
- SAP HANA,S/4HANA 和 SAP BTP 的辨析