ekt general ledger

7/24/2019 EKT General Ledger

http://slidepdf.com/reader/full/ekt-general-ledger 1/38

Universal Journal Entry - Configuration

SAP Simple Finance Add-On 2.0 for SAP Business Suite powered by SAP HANA

March, 2015



© 2015 SAP SE or an SAP affiliate company. All rights reserved. 2CustomerEarly Knowledge Transfer

At the end of this lesson, you will be able to:

• Understand consequences of the FI CO Merge for the configuration

• Maintain new ledger master data

• Explain the currency configuration• Configure the CO integration

Objectives Slide




Agenda

Ledger

Currencies

CO Integration

Document NumbersRecommendations

Obsolete or Replaced Customizing Activities




Agenda

Ledger

Currencies

CO Integration






Ledger

Business Data of Universal Journal Entry is organized in Ledgers

A ledger / company code represents an accounting principle (except parallel account

solution)

New configuration table for ledgers of universal journal entry

NewGL ledgers are migrated to the new universal journal entry ledgers

Universal journal entry ledgers are no longer assigned to total / line item tables, as line itemsare always persistent in table ACDOCA.

Types of Ledgers

Standard

• Leading Ledger

• Non-leading Ledger

Appendix Ledger




Standard Ledger

Leading Ledger

There must be exactly one leading ledger.

It is assigned to all company codes.

Defines document number (BELNR) for all ledgers.

Ledger 0L is delivered with as leading ledger (default setting).

It is in sync with FIN OP processes (AR/AP open item management,…)

Basis for actual CO data (assigned to actual VERSN 0).

Contains full set of line items in ACDOCA.

Additional Non-leading Standard Ledgers

Can be assigned to selected company codes.

Contains full set of line items in ACDOCA.

Inherits currency configuration of leading ledger (in SFIN 2.0 SP0).

Deviating fiscal year variant / open period variant possible.


http://slidepdf.com/reader/full/ekt-general-ledger 7/38© 2015 SAP SE or an SAP affiliate company. All rights reserved. 7CustomerEarly Knowledge Transfer

Appendix and Base Ledger

Use Case: Create management view on top of a legal ledger

Appendix ledger contains only adjustment postings. In reporting appendix

ledger inherits postings of base ledger.

Posting Valid for

Appendix only

Posting Valid for

both Base and Appendix



Appendix Ledger

Is defined on top of a base ledger, which is a standard ledger.

Inherits in reporting all transaction data of underlying base ledger.

Contains physically only line items posted to appendix ledger only.

Inherits currency settings and fiscal year variant of base ledger.

Separate company code assignment (subset of base ledger)

Separate Open Period Variant

Can be used e.g. to create management views without influencing the data in the base

ledger.

Cannot be part of ledger groups, except generated group containing the ledger itself.

Only manual postings are allowed to the appendix ledger (FB01L, FBB1, KB11, KB41)

You can define several appendix ledgers onto the same base ledgers, but not on top of anappendix ledger (no stacking).



View Maintenance for Ledger I

First Level: Master Data of Ledger

Define leading Ledger

Make the Ledger a Standard or Appendix Ledger

Set a Standard Ledger as Base Ledger for Appendix Ledgers

Viewcluster: FINSVC_LEDGER

Transaction: FINSC_LEDGER



View Maintenance for Ledger II

Second Level

Company Code Assignment to Ledger

For Leading Ledger holds:

• All Company Codes are assigned

• Company Code Assignments for Leading Ledgers are defaulted in the view maintenance. Do not forget

to save the defaulted entries!



View Maintenance for Ledger III

Second Level – Detail Screen – Currency Settings

Local Currency

• ACDOCA-Field HSL

• All settings are fix

Global Currency for GL & CO• ACDOCA Field KSL

• Curr. type of controlling area

• Special case: only rel. In CO

Curr. type not used in FI

1st additional Currency

• ACDOCA Field OSL• Leading Ledger defines settings

• Non-Leading Ledgers inherit settings

2nd additional Currency

• ACDOCA Field VSL

• Only available in the special case, „KSL is only rel. in CO“



View Maintenance for Ledger IV

Second Level – Detail Screen – Other Company Code Settings

Fiscal Year Variant

• In leading ledger inherited

from controlling area setting

• Non leading ledger may have

deviating fiscal year variants

Posting Period Variant

• Defines open periods

• Check for leading ledger /

representative ledger in

ledger group

Parallel Accounting usingG/L Accounts

• Flag switches off the check,

that Ledger / Company is

assigned to max. one

Accounting Principle



View Maintenance for Ledger V

Third Level

Assignment of Accounting Principle to Ledger / Company Code

Assign one Accounting Principle per Ledger / Company, unless you use Parallel Accounting

with GL Account Approach.

The customizing migration cannot derive this assignment and all Accounting Principles

relevant for the ledger will be shown -> this needs to be adapted manually, after themigration



Agenda

Ledger

Currencies

CO Integration





Currencies

Basic Principles

Currency Setting for Universal Journal Entry needs to be compatible with CO and FI

currency settings.

FI still supports max. 3 local currencies.

CO still supports max. 2 currencies .

Currency settings for leading ledger define also settings for non-leading ledgers.• Exception: In NewGl it used to be possible to deselect a currency of the leading ledger; this is still

supported for migrated NewGL Ledger configurations.

Transferprices are not yet supported (SFIN2.0 SP0).



Amount fields of Universal Journal Entry

These are the most important amount field of database table ACDOCA:

WSL Original Transaction Currency (Document Currency)

TSL Line Item Currency (Transaction Currency of Balances)

HSL Local currency

KSL Global Currency for FI and CO (special case: Currency in Controlling)

OSL 1st additional currency in FI

VSL 2nd additional currency in FI (only in the aforementioned special case!)

CO_OSL Object currency of CO



Examples for Currency configuration I

Recommended configuration for new installations

Currency Types used for Universal Journal Entry

Local Currency 10Global CO/FI Currency 30

1st Additional Currency _ / 40 / 50 / 60

2nd Additional Currency n.a.

Currency types used in FI

1st local currency 10

2nd local currency 30

3rd local currency _ / 40 / 50 / 60

Currency types used in CO

CT Controlling Area 30

CT Company Code 10




Examples for Currency configuration II

Alternative Configurations (Migration only)


Local Currency 10Global CO/FI Currency 20 only rel. in CO

1st Additional Currency _ / 30 / 40 / 50 / 60

2nd Additional Currency _ / 30 / 40 / 50 / 60



2nd local currency _ / 30 / 40 / 50 / 60

3rd local currency _ / 30 / 40 / 50 / 60


CT Controlling Area 20

CT Company Code 10




Examples for Currency configuration III

Alternative Configurations (Migration only)



2nd local currency _ / 30 / 40 / 50 / 60

3rd local currency _ / 30 / 40 / 50 / 60


CT Controlling Area =

CT Company code

10

Object Currency 70


Local Currency 10Global CO/FI Currency 10 only rel. in CO

1st Additional Currency _ / 30 / 40 / 50 / 60

2nd Additional Currency _ / 30 / 40 / 50 / 60




Agenda

Ledger

Currencies

CO Integration






Integration of Controlling with Financial Accounting I

New settings for CO integration

Configuration for document type

Ledger Assignment

Intercompany Clearing Accounts

GL Account Mapping of CO-Realtime Integration with New GL is obsolete

Secondary cost elements are no longer mapped to GL Accounts

Secondary cost elements are part of chart of accounts and are also used in General Ledger




Integration of Controlling II

Mapping Variant for CO Transaction to Document Types

Groups the assignments

Separate assignment for cross

company code transactions possible

Mapping variant …0001 is shipped

Migration creates mapping variant…0100.

Note: Assign document type to a free range of the number range object RF_BELEG.




Integration of Controlling III

Default Values for Posting in Controlling

Default ledger group is used, if no ledger group is entered in CO transactions (KB11, KB41)

If no default ledger group is configured, then all ledgers are updated

Document Type Mapping Variant is used to derive document type from CO transaction (see

previous slide)

Setting may be changed at any time and then will be used to future postings.




Integration of Controlling IV

This view defines, which ledger contains actual data for CO (Version 0).

In SFIN2.0 SP0 Version 0 must be assigned to the leading ledger in all company codes,

which are assigned to a controlling area.

Parallel actual versions are currently not supported

Note: CO transactions can write to several ledgers, but read data from one ledger




Agenda

Ledger

Currencies

CO Integration

Document Numbers

Recommendations





Document Number for Universal Journal Entries

Document Number

Transactions posted into multiple ledgers create universal journal entries with the same

document number in all ledgers.

The document number depends on company code and fiscal year of the leading ledger

(or of the representative ledger of the ledger group).

There is a separate document type assignment for postings made without the leadingledger. This ensures no gaps in document number of leading ledger.

Migration and balance carry forward generate document numbers with a letter as prefix

Fieldname BELNR, number range object RF_BELEG

New General Ledger document number (fieldname DOCNR, number range object

FAGL_DOCNR) is not used any longer.

Note:

Also non-leading ledger with a shifted fiscal year variant inherit the document number of the

leading ledger. There might be duplicate document numbers within one (shifted) fiscal year

(RYEAR) .

But: BELNR / RBUKRS / GJAHR is unique for all ledgers.




Document Numbers in CO

Transactions entered in CO still draw a CO document number

E.g. Repostings (KB11, KB41)

Original document (Prima Nota) for the universal journal entry

Existing customizing for CO document number is still valid for this case.

Fieldname in universal journal entry: CO_BELNR

Journal entries triggered from other applications (FI, logistics, …)

System generates a cryptic document number into field CO_BELNR

It is needed for CO compatibility views

The generated CO document number groups universal journal entries from CO perspective

(e.g. cross company postings)

Migrated CO Documents

The migration tool writes CO document number in field CO_BELNR for migrated journal

entries.




Agenda

Ledger

Currencies

CO Integration

Document Numbers

Recommendations





Recommendations – Sequence , Co Area Assignment

Recommended sequence for configuration

Company Codes

Create Company Codes

maintain global data

Controlling Area

Create and configure controlling area

Assign Company Codes

Ledger

Assign Company Codes

Configure Currencies / Accounting Principle

CO Integration

Configure CO Integration (assign Version to Ledger/Company)

Recommendation:

Assign a controlling area from beginning for new company codes.




Recommmendation - Copy Company Codes with Co Area

assigment

TX EC01 Copy Company Codes

New: You now can copy company codes with controlling area assignment

If you copy company code with controlling area assignment, then the currency

settings are consistent.

Otherwise: Adjust/Check currency setting after assignment to a controlling area




Recommendations - Consistency Check

Call tx FINS_CUST_CONS_CHK to

check customizing consistency.

Clean up all inconsistencies.

Check is performed online during posting

for involved company codes




Recommmendations - Document Summarization

Recommendation

Configure maximal document summarization for BSEG.

ACDOCA still contains the full detail.

For compatibility reasons document item number of BSEG (BUZEI) is still limited to 999.

Document item number in ACDOCA (DOCLN) has 6 digits.

-> you can mitigate BUZEI limitation with high BSEG document summarization.




Agenda

Ledger

Currencies

CO Integration

Document Numbers

Recommendations





Obsolete / replaced IMG Steps - Ledger configuration

SAP ECC6.0 SAP SFIN2.0

Ledger configuration

Define Ledgers for … V_FAGL_T881 is replaced by Define Settings for Journal… FINSVC_LEDGER

Define Curr. of Lead… V_T001A (tx OB22) is replaced by Define Settings for Journal… FINSVC_LEDGER Define and Activate ….V_FAGL_T882G is replaced by Define Settings for Journal… FINSVC_LEDGER

New GL Scenarios

New GL Scenarios are obsolete

In the universal journal entry all details are persisted




Obsolete IMG Activities - Document Type & Numbers


Common Document Number

Document type / number in General Ledger View (FAGL_DOCNR) per ledger is obsolete.

Document type and number of entry view (RF_BELEG) is used for all ledgers.




Obsolete IMG Activities - CO Integration


CO Realtime Integration into New GL is obsolete

No longer mapping of secondary cost elements to GL Accounts

Only account determination for intercompany clearing accounts remains.




You should now be able to

Set up ledger configuration

Define the currency settings for universal journal entry

Configure CO integration

Lesson Summary



© 2015 SAP SE or an SAP affiliate company.

All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an

SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE

(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional

trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or

SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and

services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related

presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliatedcompanies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be

changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,

promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertaintiesthat could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking

statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://global12.sap.com/corporate-en/legal/copyright/index.epx


