Functions & Features Universal Journal Entry

Configuration PART 2
SAP Simple Finance 1503
Michael Conrad April 02, 2015

Agenda
Ledger
Currencies
CO Integration

Document Numbers
Recommendations
Obsolete or Replaced Customizing Activities

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 account and also used
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 SAP sFIN OP 1503 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
Obsolete or Replaced Customizing Activities

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
leading ledger. 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
Obsolete or Replaced Customizing Activities

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_CH
K 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
(Splitter relevant characteristics cannot be cleared
currently).
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 or Replaced Customizing Activities

Obsolete / replaced IMG Steps Ledger configuration

SAP ECC6.0

SAP sFIN OP 1503

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
SAP ECC6.0

SAP sFIN OP 1503

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
SAP ECC6.0

SAP sFIN OP 1503

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.

Lesson Summary
You should now be able to
Set up ledger configuration
Define the currency settings for universal
journal entry
Configure CO integration