Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 32

SFIN-Training Series

GL Accounting

16th June, 2015


Objectives

• Explain the idea and concept of Universal Journal.

• Outline the purpose and advantages of Appendix Ledger.

• Understand the Merging of GL & Cost element master data.

• Explain the currency configuration.

• How to configure the CO Integration.


Training Scope-Changes in GL Accounting

 Universal Journal
 BSEG Vs ACDOCA
 Non-disruptive Approach
 Ledgers
 GL Master Data
 Currencies
 CO Integration
 New Settings in Simple Finance
 Obsolete Settings in Simple Finance
Universal Journal Entry

• Universal journal entries are written to a new table


ACDOCA.

• One line item table with full details for all


applications. It includes the data of FI-GL, FI-AA,
CO, CO-PA(Account based) & CO-PC-ACT
applications.

• So, the data source is same for all applications,


hence the reconciliation is not required e.g.
Reconciliation between FI, CO and FI, AA.

• Reduction of memory footprint through elimination


of redundancy.

• Account based CO-PA is fully integrated with


journal entry. The system derives the
characteristics for all financial statement items on
the basis of transactions.

• It is possible to enhance the journal entry by


extending the coding block and CO-PA
characteristics.
Copyright © 2015 Accenture All rights reserved. 4
Universal Journal Entry

• Universal journal entry consists of a header(table BKPF) and the


FAGLFLEXA
respective items(table ACDOCA).
BKPF
• There are rare cases, where entries in ACDOCA are written
without a document header e.g. Balance carry forward entries,
corrections in migration. These entries don’t represent standard FAGLFLEXT
business processes. The corresponding line items have artificial
document numbers beginning with letters(E.g. ‘B’- Balance carry
forward entries).
ZZ <CUST> T
• Data previously stored in FAGLFLEXA and FAGLFLEXT is now
stored in the table ACDOCA. ACDOCA
• ZZ <CUST> A
Data of New G/L industry tables for Public sector and Joint
Venture Accounting ( FMGLFLEXA/T, PSGLFLEXA/T and
JVGLFLEXA/T) is now stored in table ACDOCA.

• Compatibility view is provided for table FAGLFLEXA. This Industry T


compatibility view redirects select statements from FAGLFLEXA to
ACDOCA.

Industry A

Copyright © 2015 Accenture All rights reserved. 5


Training Scope-Changes in GL Accounting

 Universal Journal
 BSEG Vs ACDOCA
 Non-disruptive Approach
 Ledgers
 GL Master Data
 Currencies
 CO Integration
 New Settings in Simple Finance
 Obsolete Settings in Simple Finance
BSEG Vs ACDOCA
• BSEG and ACDOCA don’t store completely identical dimensions.

• ACDOCA has fields from CO, CO-PA, ML, AA that are not in BSEG.

• BSEG has dedicated fields for open item management / payment


that are not in ACDOCA.

• Due to 999 line items limitation, BSEG is usually aggregated. This


limitation is not applicable for ACDOCA(DOCLN field length is 6).

• ACDOCA stores all CO internal postings. These are not posted to


BSEG table.

• ACDOCA stores carryforward and correction lines from migration


whereas these are not stored in BSEG.

• ACDOCA stores different GAAPS information, but ledger key


(RLDNR) is missing in BSEG.

Copyright © 2015 Accenture All rights reserved. 7


Training Scope-Changes in GL Accounting

 Universal Journal
 BSEG Vs ACDOCA
 Non-disruptive Approach
 Ledgers
 GL Master Data
 Currencies
 CO Integration
 New Settings in Simple Finance
 Obsolete Settings in Simple Finance
Non-Disruptive Approach – Accounting Interface

• Technically, the Universal Journal


development didn’t affect the external Stable Interfaces FI-AR
interfaces. FI-AP BSEG
CRM
SD Accounting
• External interfaces to FI/CO like BAPI’s MM Interface CO
or direct calls of the Accounting interface FI-AA
have been kept stable. BAPI’s
FI-GL
• Validations/Substitutions work as before.
Internal redirect
• There have been some internal
enhancements to the Accounting
interface which will redirect to new
Accounting interface. New FI-GL
Accounting CO
ACDOCA
Interface FI-AA
ML

Copyright © 2015 Accenture All rights reserved. 9


List of obsolete Accounting tables in sFIN

Index tables removed Aggregate tables removed

Above mentioned tables are replaced by compatibility views

Copyright © 2015 Accenture All rights reserved. 10


Training Scope-Changes in GL Accounting

 Universal Journal
 BSEG Vs ACDOCA
 Non-disruptive Approach
 Ledgers
 GL Master Data
 Currencies
 CO Integration
 New Settings in Simple Finance
 Obsolete Settings in Simple Finance
Ledgers

Two types of Ledgers


Standard Ledgers
• Leading Ledger
• Non-leading Ledger

Appendix Ledger

• Is defined on top of a Base Ledger & Base ledger should


be a standard ledger.

• Inherits Currency settings and fiscal year variant of base ledger.

• Only ledger specific manual postings are allowed.

• Can’t be part of standard ledger group.

• Separate posting period variant can be maintained..

• Appendix ledger can be used to create


management view on top of a legal ledger.
Also helpful for reporting purpose.
Ledgers – Appendix Ledger

• Regular transaction data is stored in the standard ledger, only adjustments


are stored in Appendix ledger. One Appendix ledger for one purpose.

• Except creating of ledger master data, Appendix ledger doesn’t require any
additional configuration. Universal Journal
• Benefit of reduced data foot print.

• Benefit of reduced reconciliation as only(manual) delta postings are Appendix Ledger A Appendix Ledger B
maintained in the appendix ledger “Post into closed periods “Distribute revenues differently on
for restatement purposes” org units than in legal view”

• ACDOCA stores the data for all appendix ledgers.


Appendix Ledger C
• BSEG doesn’t store the appendix ledger data. “Adjustments for consolidation
purposes”

• Authorization on appendix ledger level is easily provided.

Base Ledger US-GAAP


Purpose: Financial Statement for US-GAAP

Copyright © 2015 Accenture All rights reserved. 13


Training Scope-Changes in GL Accounting

 Universal Journal
 BSEG Vs ACDOCA
 Non-disruptive Approach
 Ledgers
 GL Master Data
 Currencies
 CO Integration
 New Settings in Simple Finance
 Obsolete Settings in Simple Finance
Master Data- Merging of GL Account & Cost element
• Cost elements are merged with GL account masters.
GL Account
• No longer creation of cost elements in controlling. Based on the GL
account type, we can create primary and secondary cost elements in
GL master. Balance Sheet Accounts
• Cost element creation transactions KA01 & KA06 will redirect you to
FS00 transaction.

• Default account assignments which are maintained at cost element


level will be moved to OKB9.
Non Operating
• Secondary cost elements are part of GL reporting. Expenses/Revenues

Primary Cost Elements

r e
fo
be Secondary Cost Elements

Copyright © 2015 Accenture All rights reserved. 15


Master Data- Merging of GL Account & Cost element

• Statistical cost element (category 90 for assets) can be


maintained in FS00.

• Though cost elements are merged with GL master in the


frontend transactions, master data tables of cost
elements i.e. CSKA and CSKB are continue to store the
cost element master data.

• Even though cost element settings are available under


control data tab, these settings are applicable at chart of
account level and not company code level.

• Time dependency for cost elements is not relevant


anymore. We can’t delete cost elements since they are
merged with GL accounts.

Copyright © 2015 Accenture All rights reserved. 16


Training Scope-Changes in GL Accounting

 Universal Journal
 BSEG Vs ACDOCA
 Non-disruptive Approach
 Ledgers
 GL Master Data
 Currencies
 CO Integration
 New Settings in Simple Finance
 Obsolete Settings in Simple Finance
Currencies

As earlier FI still supports max. 3 currencies


and CO still supports max. 2 currencies

SAP Recommended Currency Settings


 Local Currency
– Inherited from Company code settings.
– Can‘t be modified as earlier.
 Global Currency for GL & CO
– Inherited from controlling area definition settings.
– Currency type 30 is preferred currency type always.
 1st additional Currency
– Inherited from Country settings if required.
– E.g.Hard Currency, Index-Based Currency
 2nd additional Currency
– This is avilable only when your Controlling area currency
type
Is other than 30.

Copyright © 2015 Accenture All rights reserved. 18


Currencies

• All currency fields are available in ACDOCA


table.

• SAP is suggesting to maintain currency type 30


to controlling area for all new installations. So
that controlling area currency and FI group
currency is unique. No need to maintain group
currency separately in FI as before.

• If controlling area currency type is other than


30, then this currency type will be applicable to
controlling area only. Need to maintain group
currency as 2nd or 3rd local currency as per the
requirement in FI.

• SAP is suggesting that try to maintain


currencies which are unique for both FI &CO
areas.
Training Scope-Changes in GL Accounting

 Universal Journal
 BSEG Vs ACDOCA
 Non-disruptive Approach
 Ledgers
 GL Master Data
 Currencies
 CO Integration
 New Settings in Simple Finance
 Obsolete Settings in Simple Finance
CO Integration
• Integration of Controlling with
Financial Accounting node has
been introduced in Simple finance.

• Since secondary cost elements


are part of chart of accounts now,
we don’t need to map secondary
cost elements to GL accounts for
CO allocations.

• We have to define document types


for CO postings and have to
assign it to Mapping variant,
further under mapping variant we
can define required CO business
transactions. You can define
different document types for
different business transactions.

• Finally, the completed variant is


assigned to company code.

Copyright © 2015 Accenture All rights reserved. 21


CO Integration

• Define ledger for CO version.

• Now we can define which ledger will carry the


data to controlling for CO versions.

• Version 0 must be assigned to leading ledger.

• Please note that fiscal year variants must be


identical in FI and CO including special
periods.

• Parallel actual versions are currently not


supported.

Copyright © 2015 Accenture All rights reserved. 22


Training Scope-Changes in GL Accounting

 Universal Journal
 BSEG Vs ACDOCA
 Non-disruptive Approach
 Ledgers
 GL Master Data
 Currencies
 CO Integration
 New Settings in Simple Finance
 Obsolete Settings in Simple Finance
New settings with sFIN - Define Settings for Journal Entry Ledger
This single step inbuilt with multiple transactions
• We can create Ledgers(Standard / Appendix).
• Ledgers can be assigned to company codes.
• Currency settings are maintained.
• Fiscal Year Variant & Posting Period Variant can be assigned to company
codes.
• Accounting Principles are assigned to the combination of Ledger &
Company code.

Copyright © 2015 Accenture All rights reserved. 24


New settings with sFIN - Define Settings for Journal Entry Ledger

• In this view we will maintain currency


settings.

• Also we will maintain Fiscal year


variant and Posting Period Variant
settings for the combination of
company code and ledger.

• Accounting Principle can be


maintained in this view for the
combination of company code and
ledger.

Copyright © 2015 Accenture All rights reserved. 25


New settings with sFIN - Deactivate a Ledger for a Company Code

• In this activity, we can deactivate a ledger for future fiscal years on a


company code basis.

• We can’t deactivate the leading ledger.

• Documents which are falling posting date , before or during the fiscal year
specified in To Fiscal year field are still posted to the ledger.

• Existing data in the ledger is retained and can continue to use it in


analyses. But, this data is incomplete and not suitable for reporting
purpose.

• Please note that it is not possible to activate again a deactivated ledger.

Copyright © 2015 Accenture All rights reserved. 26


New settings with sFIN - Posting period variant

• Now we can maintain periods at posting period variant


level.

• we can choose the option whether maintaining periods


at posting period variant level or maintaining periods
for all posting period variants simultaneously.

• If we choose maintenance at posting period variant


level, then another user can maintain periods for a
different posting period variant at the same time.

• With this change, authorization at posting


period variant level is possible.

Copyright © 2015 Accenture All rights reserved. 27


Training Scope-Changes in GL Accounting

 Universal Journal
 BSEG Vs ACDOCA
 Non-disruptive Approach
 Ledgers
 GL Master Data
 Currencies
 CO Integration
 New Settings in Simple Finance
 Obsolete Settings in Simple Finance
Obsolete settings in sFIN
New GL scenarios are obsolete, because all details are available in universal journal
entry.

Define currencies of Leading ledger is replaced by define settings to journal entry ledger.

Define and Activate Non-Leading Ledgers is replaced by define settings to journal entry
ledger.

Copyright © 2015 Accenture All rights reserved. 29


Obsolete settings in sFIN

CO Real-time integration into New GL is obsolete. Because secondary cost


elements are moved to Chart of Accounts in sFIN, so mapping of secondary cost
elements to GL accounts is no longer. Hence, definition of Real-time integration
variant and assigning it to company code are obsolete.

Document type and document number in General Ledger View per ledger is
obsolete. Document type and number of entry view is used for all ledgers.

Copyright © 2015 Accenture All rights reserved. 30


GL Accounting

Q&A
GL Accounting

Thank you

You might also like