Professional Documents
Culture Documents
When will the new G/L be available? Is it still possible to use the old classic G/L? Can we use both? Does everything look different in the new G/L? How can we migrate from the old to the new G/L?
If the customer decides to use the new G/L, then he/she can activate it at a client level Once new G/L has been activated, the new Implementation Guide (IMG) and the new transactions are added to the application menus
CoGS
Ledger
Special Ledger
Multidimensional, customer-defined
Industry-specific Ledgers
B/S by grant, fund, title
SAP AG 2005, Slide 7
IAS Ledger
SAP AG 2005, Slide 10
US GAAP Ledger
HGB Ledger
Other Ledger
Document header
BKPF
RLDNR LDGRP
Line items
BSEG
SEGMENT
BKPF/BSEG remain All documents that are relevant for the leading ledger are written in BKPF/BSEG
GLT0
FAGLFLEXA
Write GLT0
FAGLFLEXT
Integration G/L CO
One valuation is maintained in CO The reconciliation ledger is omitted for the new G/L CO can be posted through to the new G/L online The leading ledger is always supplied with data You can use Customizing to specify for each company code which CO postings will post to which ledgers:
Postings in which the company code, profit center, business area, functional area, or segment changes Postings determined by a boolean rule Postings specified by means of a Business Add-In (BAdI)
According to US GAAP, a segment is a part of the company that leads to expenses and revenues and that underlies to its own profitability and allocation of resources.
IAS and US-GAAP: A segment must be reported if external revenues constitute 10% (or more) of the total revenues And more.....
G/L- Postings without PC-info: a) Manual entry of segment or b) BAdI (Coding or Substitution) or c) Default Segment
Controlling: CO-objects
Profit Center
Derivation of segment
Totals per:
Ledger CCode
Segment, etc...
Document split :
Projection and/or inheritance Zero balance each document
Periodic activities:
Revaluation, regrouping, and balance carry forward all keep the segment Allocation per segment
BKPF
BKPF
Document Header
BSEG
Entry view part of the document (if the leading ledger is affected) Entry view part of the document
BSEG_ADD BSEG
FAGLFLEXA (dynamic)
...
GLT0
SAP AG 2005, Slide 23
FAGLFLEXT (dynamic)
Totals table
...
Key to the Following Posting Examples Ledger LL L2 L3 Leading ledger Ledger with different fiscal year Ledger with same fiscal year variant as LL
Ledger Groups LLL2 L3L2 Contains LL and L2; LL represents the group Contains L2 and L3; L3 represents the group
FAGLFLEXA (or per ledger to related table) RBUKRS DOCNR 0001 00017 0001 00017 0001 00017 0001 00017 0001 0001 0001 0001 0001 00038 00038 00038 00038 00017 RYEAR 2003 2003 2003 2003 2004 2004 2004 2004 2003 DOCLN 0001 0002 0003 0004 0001 0002 0003 0004 0001 RLDNR LL LL LL LL L2 L2 L2 L2 L3 ... BELNR 00017 00017 00017 00017 00017 00017 00017 00017 00017 GJAHR 2003 2003 2003 2003 2003 2003 2003 2003 2003 BUZEI 001 001 002 003 001 001 002 003 001
FAGLFLEXA (or related table) RBUKRS DOCNR 0001 00017 0001 00017 0001 00017 0001 00017 RYEAR 2003 2003 2003 2003 DOCLN 0001 0002 0003 0004 RLDNR LL LL LL LL BELNR 00017 00017 00017 00017 GJAHR 2003 2003 2003 2003 BUZEI 001 001 002 003
FI Entry View
BKPF BUKRS BELNR 0001 0017 BSEG BUKRS 0001 0001 0001 BELNR 0017 0017 0017 GJAHR 2003 2003 2003 BUZEI 001 002 003 GJAHR 2003 RLDNR LL LDGRP ______ BSTAT ______
FAGLFLEXA (or related table !) RBUKRS DOCNR 0001 00017 0001 00017 0001 00017 0001 00017 RYEAR 2003 2003 2003 2003 DOCLN 0001 0002 0003 0004 RLDNR LL LL LL LL BELNR 00017 00017 00017 00017 GJAHR 2003 2003 2003 2003 BUZEI 001 001 002 003
FAGLFLEXA (or related table) RBUKRS DOCNR 0001 00017 0001 00017 0001 00017 0001 00017 RYEAR 2003 2003 2003 2003 DOCLN 0001 0002 0003 0004 RLDNR LL LL LL LL BELNR 00017 00017 00017 00017 GJAHR 2003 2003 2003 2003 BUZEI 001 001 002 003
Entry View
Vendor Invoice PK Account
Enhancement
Totals table
Balances
Posting
Vendor payment for 4711 PK 25 50 50 Acc. Prctr CoCtr Amount Payable 1,000.00 Bank 970.00 Discount 30.00 -
Projection
CC01 CC02
Enhancement
Balances
CI (customer invoice)
Splitting method
Business transaction
0001 (standard)
What is the target 02000 customer Item type to of the split line item be processed information? According to the basic item
Allocations in G/L
Allocations are used to allocate values and quantities from one or more senders to one or more receivers Allocations can be made in the actual and/or plan Actual/plan distribution
The distribution is posted under the original account, no aggregation is made
Actual/plan assessment
The posted values are aggregated via an assessment account and allocated to the receivers (the assessment account is a primary account)
Posting Allocations
RWIN
Actual allocation
Actual allocations are posted via RWIN Plan allocations are posted directly via update functions
Functionality
Allocations are provided with the same options as in CO or FI-SL:
Different rules for what is to be allocated and which reference values are to be used for allocation Allocation of quantities Allocation in transaction currency Iterative or non-iterative cycles Cumulated processing
Planning periods
Periods must be stored for planning (usually the same as the actual)
Document categories
Separate document categories must be defined for planning. SAP recommends defining separate document types for allocations and manual planning.
Planner profile
In the planner profile you define which layouts are available You can preset parameters for the planning layouts in the profile The SAPFAGL profile is shipped in the standard
Integration of CO Planning
CO-OM
The CO-OM plan data is transferred online Prerequisites:
Plan version integrated into CO planning Plan version integrated into CO planning (indicator for general version maintenance) Integration activated
CO-PA The CO-PA plan data can be transferred per report Technically, this uses the FI-SL through-posting For the transfer, you can use the record type to select by plan data In doing so, existing plan data is overwritten. This means the transfer should usually happen exactly once.
Key Points
The new G/L is an available option with SAPs ERP04 product release Main advantages of the New General Ledger: Speed up Month End Closing Simplify entire technical landscape Lower Total Cost of Ownership The Classic General Ledger is still available within ERP04 The Classic General Ledger will continue to be supported by SAP The conversion/migration path is under development at present SAP is looking for Pilot customers who wish to migrate to the New General Ledger The New General Ledger contains enhanced report techniques, but does not replace CO-PA or SAP BW For a limited time it is possible to run both systems in parallel mySAP ERP04 completed ramp-up February 05
Additional Resources
www.help.sap.com
ERP04 Help documents ERP04 Release notes ERP04 Solution maps
www.sap.com
Information on: Industries Solutions Services
Your Turn!
Questions?
How to Contact Us:
Gary Fullmer/Kirk Anderson
Solution Managers - mySAP ERP Financials SAP Labs, LLC
gary.fullmer@sap.com kirk.anderson@sap.com
BKPF
BSEG
BSEG_ADD
BSEG_ADD is only filled if additional ledgers are used for parallel reporting! Documents without valuation differences are posted to all ledgers. They are also relevant for the leading ledger and are written to BSEG. Documents that are only posted in one or more additional ledgers are only written to BSEG_ADD
SAP AG 2005, Slide 48
BKPF
Document header
BSEG
BSEG_ADD
FAGLFLEXA
Split totals
FAGLFLEXT
Replaces GLT0
Depreciation Area 01 30 60 30 - 01
Ledger Group A B B
Ledger
The data transfer by means of periodic extracts from R/3 and R/3 Enterprise was based on GLT3 and no longer makes sense in the new G/L. Reason: The new G/L aims to do without tables such as GLT3. In the following cases the data has to be transferred to Consolidation via a roll-up:
Transfer of profit center and partner profit center for complete profit center consolidation (company/profit center is reassigned to consolidation unit and partner company/partner profit center to partner consolidation unit ) OR Transfer of documents that do not affect the leading ledger
Remark: You can also use the roll-up as an alternative to online postings
Interfaces
The existing BAPIS have been enhanced with the new fields and continue to be available If postings are to be made via a BAPI with an accounting principle, then the accounting principle must be assigned to a ledger group in Customizing
Representative Ledgers Every ledger is automatically created as a ledger group with the same name There is exactly one representative ledger in each ledger group Significance of the representative ledger: derivation of the period determination for the entry view (Updates in the respective ledgers, however, happen according to the fiscal year variants per ledger) Note! If the posting periods of the representative ledger are open, then postings are made in all other ledgers, even if their periods are closed
BSEG_ADD BUKRS 0001 0001 0001 BELNR 0099 0099 0099 GJAHR 2004 2004 2004 BUZEI 001 002 003
FAGLFLEXA (or related table) RBUKRS DOCNR 0001 00038 0001 00038 0001 00038 0001 00038 RYEAR 2004 2004 2004 2004 DOCLN 0001 0002 0003 0004 RLDNR L2 L2 L2 L2 BELNR 00099 00099 00099 00099 GJAHR 2003 2003 2003 2003 BUZEI 001 001 002 003
L2 has a different fiscal year than LL: DOCNR has its own allocation of document numbers
SAP AG 2005, Slide 61
BSEG_ADD BUKRS 0001 0001 0001 BELNR 0200 0200 0200 GJAHR 2004 2004 2004 BUZEI 001 002 003
FAGLFLEXA (or related table) RBUKRS DOCNR 0001 00200 0001 00200 0001 00200 0001 00200 RYEAR 2004 2004 2004 2004 DOCLN 0001 0002 0003 0004 RLDNR L3 L3 L3 L3 BELNR 00200 00200 00200 00200 GJAHR 2003 2003 2003 2003 BUZEI 001 001 002 003
FAGLFLEXA (or per ledger to related table) RBUKRS DOCNR 0001 00017 0001 00017 0001 00017 0001 00017 0001 0001 0001 0001 00038 00038 00038 00038 RYEAR 2003 2003 2003 2003 2004 2004 2004 2004 DOCLN 0001 0002 0003 0004 0001 0002 0003 0004 RLDNR LL LL LL LL L2 L2 L2 L2 BELNR 00017 00017 00017 00017 00017 00017 00017 00017 GJAHR 2003 2003 2003 2003 2003 2003 2003 2003 BUZEI 001 001 002 003 001 001 002 003
BSEG_ADD BUKRS 0001 0001 0001 BELNR 0017 0017 0017 GJAHR 2003 2003 2003 BUZEI 001 002 003
FAGLFLEXA (or per ledger to related table) RBUKRS DOCNR 0001 00017 0001 00017 0001 00017 0001 00017 0001 0001 0001 0001 00038 00038 00038 00038 RYEAR 2003 2003 2003 2003 2004 2004 2004 2004 DOCLN 0001 0002 0003 0004 0001 0002 0003 0004 RLDNR L3 L3 L3 L3 L2 L2 L2 L2 BELNR 00017 00017 00017 00017 00017 00017 00017 00017 GJAHR 2003 2003 2003 2003 2003 2003 2003 2003 BUZEI 001 001 002 003 001 001 002 003