FIN Fullmer Anderson New GL Part 2 ASUG Final

Introduction to the
New General Ledger in mySAP ERP: Part Two
Gary Fullmer Kirk Anderson

Solution Management SAP Labs LLC
What Well Cover

New General Ledger (G/L) Introduction Parallel Ledgers Concepts New General Ledger Start Up Considerations Posting Logic New tables Document Splitting Examples Financial Activities Allocations Financial Activities Planning Wrap-up
SAP AG 2005, Slide 2
What Well Cover

New General Ledger Introduction Parallel Ledgers Concepts New General Ledger Start Up Considerations Posting Logic New tables Document Splitting Examples Financial Activities Allocations Financial Activities Planning Wrap-up
The New G/L in mySAP ERP 2004
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?
G/L in ERP 2004 New Customers

In ERP 2004 the current FI functionality remains unchanged after a transition from R/3 to ERP Net new customers can activate the new G/L Customizing using: Financial Accounting (Classic) Financial Accounting Global Settings Activate New General Ledger Accounting (Check Box) Net new customers can also decide to utilize the classic general ledger instead of the new version Both versions of the general ledger will continue to be supported within ERP
New G/L Existing Customers

Existing customers who are upgrading to ERP 2004 will be offered the opportunity to transition to the new G/L in 2005
The migration path is currently under development and testing
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
Comparison of G/L in R/3 Enterprise and mySAP ERP

General Ledger in R/3 Enterprise General Ledger in mySAP ERP
Today: A Scattered World

Classic G/L
Legal requirements
mySAP ERP: A Unified World

G/L supports:
Legal requirements Mgmt. and Segment reporting
CoGS
Ledger
Profit Center Ledger

Management and segment reporting
Extensibility by industries Extensibility by customers Balanced books for any dimension
Special Ledger
Multidimensional, customer-defined
Parallel sets of books Fast close TCO reduction
Industry-specific Ledgers
B/S by grant, fund, title
Intl. accounting standards Compliance and transparency
What We'll Cover ...

Parallelism in the New G/L

Parallel Accounting
Any number of parallel ledgers Same user interface for all ledgers (data entry, functions, reporting) Almost the same functionality for all ledgers Online posting to multiple ledgers Postings per specific ledger Closing activities can be run in parallel ledgers simultaneously Standard reporting for multiple ledgers * Remark: Using parallel accounts is still supported
New G/L Leading Ledger Concepts

Parallel Ledgers There is only one leading ledger in every client In Customizing it is determined which ledger is the leading ledger The leading ledger reflects the accounting principle that is used to generate the consolidated financial statements It is integrated with all subledgers and updated in all company codes (if posting is not ledger-specific)
IAS Ledger
US GAAP Ledger
HGB Ledger
Other Ledger
Leading Ledger Concepts Contd

In G/L one ledger is assigned the role of the leading ledger. Group accounting is usually mapped in this ledger. All company codes are automatically assigned to the leading ledger (cannot be deactivated) Parallel reporting can still be mapped via additional accounts. In this case there is exactly one ledger in the general ledger the leading ledger. For parallel reporting in the new G/L you can also add ledgers to the general ledger (not in an SL, as for R/3 Enterprise) The leading area of asset accounting (area 01) must be posted to the leading ledger Controlling transactions must also be posted to the leading ledger

Data Structures of the New G/L

Additional fields
Document header
BKPF
RLDNR LDGRP
Line items
BSEG
SEGMENT
Documents that are relevant for the leading ledger
BKPF/BSEG remain All documents that are relevant for the leading ledger are written in BKPF/BSEG
Transition Scenario for Reporting

When the new G/L is active, customers requiring a very high level of security can choose to continue updating GLT0 for a transitional period A ledger comparison at totals level is available for comparing GLT0/FAGLFLEXT (RGUCOMP4)
RWIN
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)
Profit Center and Segment

As before, the mapping of internal areas of responsibility can be done by means of profit centers The derivation of profit center and partner profit center is carried out in preceding applications (e.g., MM) or in RWIN or by clearly assigning a CO object to a profit center. This corresponds to the previous R/3 logic. The segment is made available as a new organizational unit to map the legal requirements with regards to segment reporting The segment is derived by clearly assigning a profit center to a segment or via BAdI (ABAP coding or substitution)
Transitional Scenario for Profit Center Accounting

It is possible to continue the previous PCA in parallel with the new G/L for a transitional period:
GLPCT (old) does not access split documents SAPF180 may still be used temporarily to transfer receivables and payables SAPF181 can no longer be used. A valuation with updates in the original document is also no longer supported. Exchange rate differences and discounts thus cannot be transferred to GLPCT. GLPCT will not be developed further SAP does not recommend permanent parallel operation!
Motivation of Segment Reporting

Segment reporting aims:
To give detailed insight into different business activities of a diversified company To offer information about the general environment In order to: Better understand the economic performance Better forecast the potential of revenue and financial backup Better anticipate risks and opportunities And more... of the company
Legal Definition of Segments Example

IAS distinguishes between business and geographic segments A business segment represents a selected part or segment of the company that delivers a product or a service with risks and revenues that differ from those of other business segments A geographic segment informs about risks and revenues that differ from other geographic segments in terms of economic, political, etc., reasons
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.....
New G/L: Derivation of Segment from Profit Centers
Mat.- Management and Production: Controlling object or material master
Sales: Customer order position
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...
Functionality for the Segment

User interface: journal entry (derivation, manual entry, BAdI) Standard reporting:
Balance and P&L-sheet Display balances
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
Planning on segment ALE:

Segment information in FI documents is transferred
What Well Cover

Posting Tables New G/L

R/3 mySAP ERP New G/L
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
(if the leading ledger is not affected)
FAGLFLEXA (dynamic)
Ledger and split parts of the document
...
GLT0
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
Example 1: Posting to All Ledgers

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 ______ LDGRP ______ BSTAT ______
BSEG_ADD BUKRS BELNR GJAHR BUZEI
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
Example 2: Posting to Leading Ledger LL

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
FI Entry View
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
Details General Ledger View

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

Document Splitting: Invoice Posting

General Ledger View (Flexibility)
Vendor Invoice Prctr CostCtr Amount PK 40 40 31 Expense PC01 CC01 Expense PC02 CC02 Vendor 400.00 600.00 1000.00Account Prctr Expense Expense Payable Payable PC01 PC02 PC01 PC02 CostCtr CC01 CC02 Amount 400.00 600.00 400.00600.0040 40 31 31
Entry View
Vendor Invoice PK Account
Enhancement
Document number 4711
Totals table
Balances
Actual line items
Posting
Split info table
Posting Payable Step

Clearing: Enhancing the follow-up costs (before RWIN) Entry View 4712 Entry View Enhanced Document Vendor payment PK 25 50 50 50 Acc. Prctr CoCtr Payable Bank Disc. PC01 CC01 Disc. PC02 CC02 Amount 1,000.00 970.00 12.00 18.00 -
Vendor payment for 4711 PK 25 50 50 Acc. Prctr CoCtr Amount Payable 1,000.00 Bank 970.00 Discount 30.00 -
Projection
Split Info 4711 001

< Reference to invoice
Document Split: Payment Step

Enhancement of the document (in RWIN) Enhanced Document
Vendor payment PK 25 50 50 50 Account Prctr Payable Bank Discount PC01 Discount PC02 CoCtr Amount 1000.00 970.00 CC01 12.00 CC02 18.00 -
General Ledger View

Vendor payment PK 25 25 50 50 50 50 Account Payable Payable Bank Bank Discount Discount Prctr PC01 PC02 PC01 PC02 PC01 PC02 CoCtr Amount 400.00 600.00 388.00 582.00 12.00 18.00 -
CC01 CC02
Cleared document 4711
Enhancement
4711 Totals table GLFLEXT Split info table Update
Balances
Split Logic Diagram

Classification as a business transaction for document splitting Document type
CI (customer invoice)
Splitting method
Business transaction
0000000012 0200 (customer invoice) RULE
Business transaction variant
0001 (standard)
What is the target 02000 customer Item type to of the split line item be processed information? According to the basic item
30000 revenue SAP AG Slide 33 2005,
Basic item type
What is the source of the split information?

New General Ledger Introduction New General Ledger Concepts New General Ledger Start Up Considerations Posting Logic New tables Document Splitting Examples Financial Activities Allocations Financial Activities Planning Wrap-up
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
Function Module FAGL_ALLOCATION_POST
G/L Plan allocation
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 the Basic Settings

Version
As in CO, new G/L planning requires planning versions You can use any number of independent versions for planning From a technical perspective, the actual data in G/L is still maintained in version 001 A number of basic settings for planning are specified for each version (plan integration, line items, lock)
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.
Manual Planning Keys

In the new G/L, manual planning data is entered via the planning processor Planning layout
Defines which content appears in the header, in the lines, and in columns of the planning screen A number of standard layouts are available
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
Planning layouts and/or planner profiles can be customer-defined
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
Copyright 2005 SAP AG. 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 AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix and Informix Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE is a registered trademark of ORACLE Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves information purposes only. National product specifications may vary.
Slide Appendix ...

New G/L Data Structure Addl Info New G/L Integration other Applications Ledger Groups Concepts Additional Posting Examples Multi-Ledgers
Data Structures of the New G/L (cont.)
BKPF
BSEG
BSEG_ADD
Fields like BSEG
Documents that are not relevant for the leading ledger
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
Data Structures of the New G/L (cont.)
BKPF
Document header
BSEG
Un-split line item
BSEG_ADD
Un-split line item (only for additional ledger)
FAGLFLEXA
Split line item
Split totals
FAGLFLEXT
Replaces GLT0
Parallel Reporting via Additional Ledgers Integration: G/L AA

01 IAS 30 US GAAP G/L 60 30 - 01 IAS leading US GAAP AA
Depreciation Area 01 30 60 30 - 01
Ledger Group A B B
Ledger
IAS US GAAP US GAAP
Slide Appendix ...

G/L Asset Accounting (AA) Integration

As before, the depreciation areas of AA can be directed to different accounts in G/L If a parallel valuation in G/L is depicted by means of additional ledgers in the general ledger, this means for AA:
A ledger group is assigned to a depreciation area The leading ledger must be assigned to area 01 The beginning and end of the fiscal year in asset accounting must be identical to the ledger in general ledger accounting because the depreciation values in the G/L accounts would otherwise be mapped incorrectly An additional ledger is supplied via a derived area. This ledger does not keep any data in the data basis but calculates it at the time of the APC postings.
Integrating G/L with CFM and Consolidation

Corporate Finance Management (CFM)
As in R/3, the valuation areas of CFM are assigned to an accounting principle The accounting principle is assigned to a ledger group. Here, one has to consider that the accounting principle that is assigned to the operational valuation area 001 points to a ledger group that contains the leading ledger. In CFM a separate document is created for all postings per valuation area. This document is then transferred to RWIN. In doing so, an open item is created only for operational area 001. The postings in the parallel areas may contain only the corresponding reconciliation account. If charges for securities purchases are treated differently for two accounting principles, then the position and cost lines must have identical additional account assignments as the splitter would otherwise create incorrect values for one of the views
Strategic Enterprise Management Business Consolidation (SEM-BCS) (SAP BW-based)

The SEM-BCS is supplied by the SAP Business Information Warehouse (SAP BW) extractors of the new G/L
Integrating G/L with EC-CS and SEM-BCS

Enterprise Controlling Consolidation (EC-CS) and SEM-BCS (R/3based)
Documents that affect the leading ledger can be transferred to Consolidation online
User-defined fields can also be transferred (maintenance of the field transfer 0C03) Profit center and partner profit center can be transferred with the user-defined fields of EC-CS. When this is done, only a drill down by profit centers is possible, but no complete EC-CS consolidation is possible. Reason: Elimination logic exists only for consolidation unit/partner consolidation unit fields, but not for user-defined fields.
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
Integrating G/L with Logistics and HCM

Logistics
In the same way as in R/3, Materials Management (MM) and Sales and Distribution (SD) generate documents and then call RWIN The derivation of the organizational units (such as profit center) is done as in Logistics in R/3 The exceptions are the segment and partner segment they are derived in RWIN from the profit center or by substitution
Human Capital Management (HCM) and Travel Management (TM)

As in R/3, HCM and TM generate documents and then call RWIN The derivation of the organizational units (such as profit center) is done as in HCM and TM in R/3 The transfer of detailed account assignment information such as profit center or segment is not realized for all types of line items (eg., payables to employees)
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
Slide Appendix ...

New G/L -- Ledger Groups

The ledger group contains the leading ledger. The leading ledger is also the representative ledger. If the group does not contain the leading ledger, then the following apply: If a group contains precisely one ledger, then the abovementioned condition applies, which states that this ledger is also the representative ledger The assignment of the company code is relevant for the following two conditions. The final correctness check is carried out only at runtime:
If all ledgers of a group have a different fiscal year variant from the company code to which they are assigned, then any ledger can be flagged as the representative ledger If some of the ledgers have the same fiscal year variant as the leading ledger of the company code and other ledgers have fiscal year variants that differ from that of the company code, then one of the ledgers with the identical fiscal year variant has to be flagged as the representative ledger
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
Slide Appendix ...

Example 3: Posting to Non-Leading Ledger L2

BKPF BUKRS BELNR 0001 0099 BSEG BUKRS BELNR GJAHR BUZEI GJAHR 2004 RLDNR L2 LDGRP ______ BSTAT L
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
Example 4: Posting to Non-Leading Ledger L3

BKPF BUKRS BELNR 0001 0200 BSEG BUKRS BELNR GJAHR BUZEI GJAHR 2004 RLDNR L3 LDGRP ______ BSTAT L
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
L3 has the same fiscal year as LL DOCNR. It inherits BELNR

Example 5: Posting to Ledger Group LL,L2

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 ______ LDGRP LLL2 BSTAT ______
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
Example 6: Posting to Ledger Group L2,L3

BKPF BUKRS BELNR 0001 0017 BSEG BUKRS BELNR GJAHR BUZEI GJAHR 2003 RLDNR ______ LDGRP L3L2 BSTAT L
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

FIN Fullmer Anderson New GL Part 2 ASUG Final

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FIN Fullmer Anderson New GL Part 2 ASUG Final

Uploaded by

Copyright:

Available Formats

Introduction to the

New General Ledger in mySAP ERP: Part Two

Gary Fullmer Kirk Anderson

What Well Cover

What Well Cover

SAP AG 2005, Slide 3

The New G/L in mySAP ERP 2004

SAP AG 2005, Slide 4

G/L in ERP 2004 New Customers

SAP AG 2005, Slide 5

New G/L Existing Customers

SAP AG 2005, Slide 6

Comparison of G/L in R/3 Enterprise and mySAP ERP

Today: A Scattered World

mySAP ERP: A Unified World

Profit Center Ledger

Extensibility by industries Extensibility by customers Balanced books for any dimension

Parallel sets of books Fast close TCO reduction

Intl. accounting standards Compliance and transparency

What We'll Cover ...

SAP AG 2005, Slide 8

Parallelism in the New G/L

SAP AG 2005, Slide 9

New G/L Leading Ledger Concepts

Leading Ledger Concepts Contd

SAP AG 2005, Slide 11

What We'll Cover ...

SAP AG 2005, Slide 12

Data Structures of the New G/L

Documents that are relevant for the leading ledger

SAP AG 2005, Slide 13

Transition Scenario for Reporting

SAP AG 2005, Slide 14

SAP AG 2005, Slide 15

Profit Center and Segment

SAP AG 2005, Slide 16

Transitional Scenario for Profit Center Accounting

SAP AG 2005, Slide 17

Motivation of Segment Reporting

SAP AG 2005, Slide 18

Legal Definition of Segments Example

SAP AG 2005, Slide 19

New G/L: Derivation of Segment from Profit Centers

Mat.- Management and Production: Controlling object or material master

Sales: Customer order position

SAP AG 2005, Slide 20

Functionality for the Segment

Planning on segment ALE:

SAP AG 2005, Slide 21

What Well Cover

SAP AG 2005, Slide 22

Posting Tables New G/L

(if the leading ledger is not affected)

Ledger and split parts of the document

SAP AG 2005, Slide 24

Example 1: Posting to All Ledgers

BSEG_ADD BUKRS BELNR GJAHR BUZEI

SAP AG 2005, Slide 25

Example 2: Posting to Leading Ledger LL

BSEG_ADD BUKRS BELNR GJAHR BUZEI

SAP AG 2005, Slide 26

BSEG_ADD BUKRS BELNR GJAHR BUZEI

SAP AG 2005, Slide 27