ASUG_0704_(2)

7/23/2019 ASUG_0704_(2)

http://slidepdf.com/reader/full/asug07042 1/60

Kirk Anderson

Solutions Manager mySAP ERP FinancialsSAP Labs LLC

Session: 300

7/23/2019 ASUG_0704_(2)


SAP AG 2004 / General Ledger in mySAP ERP, 27.07.2004, 2

Learning Objectives:

Attendees should gain a deeper understanding of functionalenhancements being delivered with the General Ledger in mySAP.

Attendees will gain a better understanding, in particular from a

technical perspective, of how the General Ledger in mySAP ERPdiffers from their current SAP General Ledger system.

Attendees should obtain a clearer understanding of the current

product status and when it may make sense for them to start lookingat potential implementation.

7/23/2019 ASUG_0704_(2)


Overview

Design of the New General Ledger

Parallel Ledgers (Gary)

Balanced Books by Dimension (Gary)

Profit Centre Accounting and Segment ReportingAllocations and Planning (Gary)

Closing and Reporting

Integration / ALE

Implementation (Gary)

7/23/2019 ASUG_0704_(2)



SAP WebApplication Server

! !

SAP Basis

"#$! %&

"# !

'((#

Application

'((%

SAP R/3Enterprise Core

)*+ ,(%

C o m p o s i t e A p p

l i c a t i o n F r a m e w o r k

--) ./

L i f e C y cl

eM gm t

SAP EnterpriseExtension Set

! !!

-)-)

Multi Channel Access

Portal Collaboration

-)./-) -)-)

Master Data Mgmt

Bus. Intelligence Knowledge Mgmt

-)-)

IntegrationBroker

BusinessProcess Mgmt

J2EE ABAP

DB and OS Abstraction

Self-Service Procurement

"# !

SAP R/3 Enterprise Core

SAP Enterprise Extension Set

Strategic Enterprise Management

Internet Sales

Self Services

… and more

!

SAP ECC Core

SAP ECC Extension Set

Strategic Enterprise Management

Self Services

!

Self-Service Procurement

Internet Sales

! 0((

)*+

C o m p o s i t e A p p

l i c a t i o n F r a m e w o r k

--) ./

L i f e C y cl eM gm t

-)-)

Multi Channel Access

Portal Collaboration

-)./-) -)-)

Master Data Mgmt

Bus. Intelligence Knowledge Mgmt

-)-)

IntegrationBroker

BusinessProcess Mgmt

J2EE ABAP

DB and OS Abstraction

… and more

1 $ 2

New GL is included in the technical component SAP ECC 5.0.

7/23/2019 ASUG_0704_(2)



1 3 $$

General

Ledger

Org Units

Company

Segment

Profit Center

Partner Company

Partner Segment

Partner Profit Center

Account + Subaccts

Account

Transaction Type

Functional Area

Value in TC

Value in LC

Value in GC

Industry Templates

+ Grant

+ Fund

+ Title

+ …

Customer Extension

+ …

+ …

E R P 2

0 0 5

Despite its flexibility, General Ledger is no substitute for SAPProfitability Analysis or SAP Business Information Warehouse.

Reasons: Data volume, performance, functionality.

7/23/2019 ASUG_0704_(2)



Cons.Preparation

EC-PCA

GL inmySAP

ERP

Online Split:

Balanced Book

for any dimension

FI-SL CO-OM

CO-PA

Profit Center

Determination

CoGS Ledger

Currency

TranslationZero balanceDerivation

Accounting Interface

Persistency layer

1 3 $2 !!

Reconc.Ledger

7/23/2019 ASUG_0704_(2)



1 3 42

Unified Financial and Management Accounting One version of the truth – stored in the General Ledger

Support for Multiple Reporting Requirements

Legal, Segment and Management

Full Multi-dimensional analysis

Balanced Books for any Dimension (Real time basis)

Parallel Accounting (Multiple Ledgers)

Support for Maintaining Multiple Books of Account US GAAP, IAS, Regulatory etc.

Support for Faster Closing

TCO Reduction both during and subsequent to implementationExtensible / Flexible Data Model

Supports Industry Specific and customer defined dimensions.

7/23/2019 ASUG_0704_(2)


Overview

Design of the New General Ledger

Parallel Ledgers

Balanced Books by Dimension

Profit Centre Accounting and Segment Reporting

Allocations and Planning


Integration / ALE

Implementation

7/23/2019 ASUG_0704_(2)



OtherLedgerHGB

LedgerUS GAAPLedger

5

Parallel Ledgers

There is exactly one leading ledger in every client.

In Customizing it is determined, which ledger in a client isassigned the role of leading ledger.

The leading ledger reflects the accounting principle which isused to generate the consolidated financial statement. It is

integrated with all subledgers and updated in all companycodes (if posting is not ledger-specific).

Example:

IASLedger

Leading Ledger =Group Ledger

7/23/2019 ASUG_0704_(2)



5 3 $

The Primary Deprecation Area (01) of Asset Accounting must beposted to the Leading Ledger.

Controlling must also be integrated to the Leading Ledger

The leading ledger inherits precisely these settings of thisposting code in every company code:

Fiscal year variant of the company code

Currency of the company code

Non-leading ledgers must be activated for the respectivecompany code. For every company code, you can havedifferent fiscal year variants and sub-quantities of the secondand third house currency of the leading ledger in the respectivecompany code. The first currency is always maintained in allnon-leading ledgers.

Leading-Ledger

OtherHGBUS

7/23/2019 ASUG_0704_(2)



5 3 -

AAGL

IAS leading

HGB

US-GAAP

CO - IAS

01 IAS

.. US GAAP

.. HGB

…

7/23/2019 ASUG_0704_(2)



5 5 $$ 2 )1

BSEG_ADD

BSEG

BSEG

BKPF BKPF

FAGLFLEXA

(dynamic)

FAGLFLEXT

(dynamic)GLT0

Entry view part of the document

(if the leading ledger is affected)

Ledger and split parts of the document(Much Leaner than data than in BSEG)

Totals table (Split Totals)

Document Header

Entry view part of the document

(if the leading ledger is not affected)

R/3 mySAP ERP

...

...

7/23/2019 ASUG_0704_(2)



5 - 2

A single valuation is maintained in CO.

The reconciliation ledger is omitted for the new GL.

CO can be posted through to the new GL online.

The leading ledger is always supplied with CO data.

You can use Customizing to specify for each company code,which CO postings 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 BADI.

7/23/2019 ASUG_0704_(2)


Overview

Design of the New General LedgerParallel Ledgers





Integration / ALE

Implementation

7/23/2019 ASUG_0704_(2)



3

Ledger not specified at time of document entry: Posting to all defined GL ledgers

Transactions: for example: Ingoing invoice, outgoing invoice, payment

Ledger A(IAS)

(leadingledger)

Ledger C(HGB)

Ledger B(US GAAP)

7/23/2019 ASUG_0704_(2)



3

Ledger specified at time of document entry: Posting to specified ledger only

Transactions: valuation postings, period end postings

Ledger A(IAS)

(leadingledger)

Ledger C(HGB)

Ledger B(US GAAP)

7/23/2019 ASUG_0704_(2)



$ 2

Ledger L1 Ledger L2

Primary Processes

Invoices, Payments, …


Online split, substitution, …

Creation of one documentfor all parallel ledgers

Fiscal year variant and subset

of dimensions may differ perledger.

7/23/2019 ASUG_0704_(2)



$ 2

Ledger L1

Secondary Processes, e.g. IAS

Allocation, Currency Valuation,Carry Forward, …



Creation of parallel documents,separate documents per ledger

Full parallel accounting: differentsettings for valuation, fiscal yearvariant, selected dimensions,

Ledger L2

Secondary Processes, Local GAAP



Allocation, Currency Valuation,

Carry Forward, …

7/23/2019 ASUG_0704_(2)


Overview






Integration / ALE

Implementation

7/23/2019 ASUG_0704_(2)



4 4 5 61

Data entry: Expenses for two profit centers

7/23/2019 ASUG_0704_(2)



4 4 5 61

Payables and taxes are split online, respectively.

7/23/2019 ASUG_0704_(2)



4 4 5 ! 3 -

Totals

Enrichment

Entry View GL View

Posting

Single

Items

Doc 4711

SplitInfo

Table

Vendor Invoice

PK Account PrCtr CCtr Amount

40 Expense PC01 KS01 400,0040 Expense PC02 KS02 600,0031 Payables 1000,00-

Vendor Invoice

PK Account PrCtr CCtr Amount

40 Expense PC01 KS01 400,0040 Expense PC02 KS02 600,0031 Payables PC01 400,00-31 Payables PC02 600,00-

Document 4711

Posting

7/23/2019 ASUG_0704_(2)



4 4 5 2 " $

Payment

PK Account PrCtr CCtr Amount25 Payables 100050 Bank 970-50 Discount 30-

Payment

PK Account PrCtr CCtr Amount25 Payables 100050 Bank 970-50 Discount PC01 KS01 12-50 Discount PC02 KS02 18-

Enrichment of additional costs occurs in the sending application (here: payment).

Projection

Entry View Enriched Document

Split

Info

Table

Split of the Discount

7/23/2019 ASUG_0704_(2)



4 4 5 ! 3

Enrichment

Posting

Cleared Document

Enriched Document

Payment

PK Account PrCtr CCtr Amount25 Payables 1000

50 Bank 970-50 Discount PC01 KS01 12-50 Discount PC02 KS02 18-

GL View

PK Account PrCtr CCtr Amount25 Payables PC01 40025 Payables PC02 600

50 Bank PC01 388-50 Bank PC02 582-50 Discount PC01 KS01 12-50 Discount PC02 KS02 18-

Totals SplitInfo

Table

SingleItems

Doc 4712

Posting

7/23/2019 ASUG_0704_(2)



0200 (customer 0001 (standard)invoice)

Splitting method

0000000012

Business

transaction

Businesstransaction

variant

Document type CI (customer

invoice)

Item type tobe processed

02000 customerline item

…

Basis item type

RULE

30000 revenue

…

According to the basic item

Classification as a business transactionfor document splitting

What is the source of

the split information?

What is the target

of the splitinformation?

4 4 5 !

7/23/2019 ASUG_0704_(2)



4 4 5 2 !

Business transaction: For example, customer invoice, payment,account statement or un-specified posting.

Business transaction variant: The maximum (default) number of itemtypes (see below) assigned to the business transaction can be

restricted (customer specific). Item type: Classification of lines for document splitting, such as item

type “customer line item” (only relevant for the part of documentsplitting that is rule based - see below). The split is not rule based incase of clearing and if a zero balance is generated. The split is always

performed for these processes.

Splitting method: Recognizes the business transaction variants.The splitting methods combined with the BT variants produce a rule.The procedure 0000000012 is the standard (recommended tocustomers).

Rule: Includes from where the split information is to be taken(basic item type = line type, such as revenue) and the target of the split(item type to be processed, such as customer line item).

7/23/2019 ASUG_0704_(2)


Overview






Integration / ALE

Implementation

7/23/2019 ASUG_0704_(2)



2

As before, the mapping of internal areas of responsibility can bedone by means of profit centers.

The derivation of profit center and partner profit center is carriedout in preceding applications (e.g. MM) or in RWIN or by clearly

assigning a CO object to a profit center. This corresponds to theprevious R/3 logic.

The segment is made available as a new organizational unit tomap the legal requirements with regards to segment reporting.

The segment is derived by clearly assigning a profit center to asegment or via BadI (Abap- Coding or substitution).

The profit center and/or segment as well as the corresponding

partner information are managed as characteristics in the new GL.The following are optional for the profit center and/or segment: Document splitting and Zero balance

7/23/2019 ASUG_0704_(2)



)1 5 2 2 2

Totals per: Ledger CCode Segment etc...

Profit Center

Derivation of segment

Sales:Customer order position

Mat.- Management and Production:

Controlling object ormaterial master

GL- Postings without PC-info:a) Manual entry of segment orb) BADI (Coding or Substitution) orc) Default Segment

Controlling:CO-objects

7/23/2019 ASUG_0704_(2)



.$ 2 . 78

UI: Journal entry (derivation, manual entry, BADI) Standard Reporting:

Balance and P&L-sheet

Display balances

Document Split :

Projection and / or inheritance

Balance zero for each document

Periodic activities:

Revaluation, regrouping and balance carry forward keep the segment

Allocation per segment Planning on segment

ALE:

Segment information in FI- documents are transferred

The field “business area” will be still available for customersupgrading from R/3 and is to be considered as any other accountassignment field.New customers should use the segment field.

7/23/2019 ASUG_0704_(2)


Overview






Integration / ALE

Implementation

7/23/2019 ASUG_0704_(2)



Allocations are used to allocate values and quantities from one or moresenders to one or more receivers (i.e. Between Profit Centres /Segments)

Allocations can be made for actual 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)

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 tobe used for allocation

Allocation of quantities

Allocation in transaction currency

Iterative or non-iterative cycles

Cumulated processing

7/23/2019 ASUG_0704_(2)



/$

In the new GL manual planning data is entered via the planningprocessor

Planning layout

defines, which contents appears in the header, in the lines and incolumns 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 -specifically defined

Multiple Versions of Plan data can be maintained.

7/23/2019 ASUG_0704_(2)



- 2

CO-OM The CO-OM plan data can be transferred to the GL online

Prerequisites:

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.

7/23/2019 ASUG_0704_(2)


Overview






Integration / ALE

Implementation

)

7/23/2019 ASUG_0704_(2)



)1

The closing operations in FI affect The foreign currency valuation of open items and monthly

balances (SAPF100> FAGL_FC_VALUATION ),

Translation (FAGL_FC_TRANSLATION)

Grouping (SAPF101 > FAGL_CL_REGROUP ), Other valuations (old: SAPF107V, SAPF103 and SAPF104 )

WE/RE accounts clearing (old: RFWERE00 ).

Balance carry-over (old: SAPFVGTR)

Balance sheet and P&L adjustment (SAPF180 and SAPF181) areremoved.

7/23/2019 ASUG_0704_(2)



Example: LC1 = EUR LC2 = USD

Posting to be evaluated:

Amount TC Amount LC1 Amount LC2

100 CAD 160 EUR 120 USD (Posting exchange rate: 1 EUR = 0.75 USD)

Valuation for the exchange rate 1 CAD -> 1.50 EUR TYPE M1 EUR -> 1.20 USD TYPE B

ERD amount TC ERD amount LC1 ERD amount LC2

0 -10 -12

Comment:The calculation (TYPE B) of the valuation amount LC2 (-12) is not carried out fromthe conversion of the posting amount LC1 (160 EUR),

That would be:160 x 1.20 = 192

192 – 120 = + 72 (calculated exchange rate difference)

but from the direct conversion of the valuation amount LC1 (-10 x 1.20) to thevaluation amount LC2 (-12). Also TYPE B.

$

D i r e c t

c o n v

e r s i o n

( r e m e a s

u r e m e

n t )

9.40'"-':;

7/23/2019 ASUG_0704_(2)



FAGL_FC_TRANSLATION

Evaluation of balance sheet/P&L areas (example: reporting currency TC2 USD)

1. Translation happens at totals level (possible for all types of G/L accounts)

2. Account determination happens via valuation area and financial statement version

Example:TC1 EUR TC2 USD

Orig. document 160 120

Remeasurement -10 -12 ________ ________

Account balances 150 108

Translation: What is the value of LC1 (EUR) in reporting currency (USD) per key date?(LC1 evaluated with key data exchange rate 1 EUR = 1.20 USD)

(150 X 1.20 = 180) value to be achieved

Required adjustment posting + 72 to get key date value

Asset accounts are evaluated with the historical exchange rate, P&L accounts areevaluated with the weighted exchange rate (corresponding exchange rate type intable TCURR must be maintained).

9.40'"-':;

! !

7/23/2019 ASUG_0704_(2)



! !

Switch “New General Ledger” = set

Reports read the new totals table FAGLFLEXT

Switch “Read GLT0” is set > reports read GLT0

User-specific parameters:“Read GLT0, even though “Read GLT0” is not set”> Reports read GLT0

(for occasional reading of GLT0 and synchronization withFAGLFLEXT in separate valuations)

! !

7/23/2019 ASUG_0704_(2)



! !

Classical ABAP/4 reports (log. databases SDF, BRF)

Additional selection field “Ledger” (US GAAP, IAS, local GAAP)

Dynamic selections: Additional and user-defined fields e.g. RFBILA10 can create a balance sheet for profit center

Balance Display:

Selection according to new dimensions (if contained in the ledger)

Display: A maximum of 5 dimensions can be defined in Customizing;these dimensions can be used to restrict the display.

Drilldown according to the respective characteristic withaccumulated period values

Drilldown-Reports can navigate via new characteristics

! 4* ! 2

7/23/2019 ASUG_0704_(2)



EC-CS

FI

CO

. . .

Periodic Extractor

Remote Extractor

SAP BWGeneral

Ledger

mySAP ERP is based on SAP NetWeaver which includes BW reporting.

Therefore, there is only 1 system required.

! 4* ! 2

Company, Segment, Profit Center, …Functional Area, Transaction Type, …

Company, Segment, PC, …

7/23/2019 ASUG_0704_(2)


Overview






Integration / ALE

Implementation

- 1 $

7/23/2019 ASUG_0704_(2)



- 1 $

If parallel valuation in GL is to be supported via additional ledgersthis means for Asset Accounting:

The applicable ledger group must be assigned to the applicabledepreciation area.

The leading ledger must be assigned to area 01.

The beginning and end of the fiscal year in asset accountingmust be identical to the ledger in general ledger accounting

because the depreciation values in the G/L accounts wouldotherwise be mapped incorrectly.

- 1 $

7/23/2019 ASUG_0704_(2)



!

AAGL

IAS leading

US GAAP

01 IAS

30 US GAAP

60 30 - 01

…

Depreciation Ledger LedgerArea Group

01 A IAS30 B US GAAP6030 - 01 B US GAAP

- 1 $

7/23/2019 ASUG_0704_(2)



AA

IAS leading

1000 USD

US GAAP

1000 USD (1)200 USD (3)

01 IAS 1000 USD (1)

30 US GAAP 1000 USD (1)

60 30 - 01

Example: Integrated asset acquisition 1000 USDplus 200 USD shipment costs

(1) Asset acquisition(2) Manuel capitalization of additional costs in area 30(3) APC posting

200 USD (2)

(1)

(1)

(3)

- 1 $ 5!

7/23/2019 ASUG_0704_(2)



!

If parallel ledgers are to be mapped in GL, then the depreciation isposted to the ledger assigned to the depreciation area:

The depreciation run posts the depreciation for area 01 to the IASledger and the depreciation for area 30 to the US GAAP ledger.

Depreciation Ledger LedgerArea Group

01 A IAS30 B US GAAP6030 - 01 B US GAAP

Example

5$ . $ <

7/23/2019 ASUG_0704_(2)



Local purchasing,Local purchasing,

invoice verificationinvoice verification

InventoryInventory

managementmanagement Sales & distributionSales & distribution

function (internal)function (internal)

AccountingAccounting

PRODUCTIONPRODUCTION

HEAD OFFICEHEAD OFFICE

SALES &SALES &

DISTRIBUTIONDISTRIBUTION SalesSales

ShippingShipping

InvoicingInvoicing Purchase ofPurchase of

trading goodstrading goods

Accounts payable accounting Accounts receivable accounting

FI Document

(IDoc)

FI Document

(IDoc)

! 2 "# ! )1

7/23/2019 ASUG_0704_(2)



1. IDoc type FIDCMT01 - Distributed general ledger (No longersupported in New General Ledger).

Message types:

FIDCMT Document lines (real time)

FIROLL Account balances (periodically)

2. IDoc type FIDCCP01/02 - Sends complete FI documents(Supported in New General Ledger)

- Entries in BKPF and BSEG/BSEG_ADD are required in the targetsystem

- with IDoc type FIDCCP01/02. Corresponds to the documentstructure, additional fields were included (e.g. ledger group)

- Updates the new GL in the receiver system when posting the IDoc

according to the central settings (split)

2 )1 "

7/23/2019 ASUG_0704_(2)



Remember:When New GL is active (sending or target system) then the message

type is checked in the IDoc inbox/outbox: No processing ofFIDCMT/FIROLL! (Error status in the target system)

In general, complete FI documents can always be sent: Scenario 1:

New G/L is active in the non-central system, but not in the central system:The central system does not recognize the ledger/group.>>>>The incoming document is posted as a normal document.Note: Ledger-specific documents become generally valid!

Scenario 2:New G/L is active in the central system, but not in the non-central system:

>>>>The documents are posted with the ledger group “Space”. This meansthey are updated in the leading ledger and in all ledgers activated in thecompany codes!

No system adjustments required.

7/23/2019 ASUG_0704_(2)


Overview




Allocations and PlanningClosing and Reporting

Integration / ALE

Implementation

-! )1 $

7/23/2019 ASUG_0704_(2)



The New General Ledger of mySAP ERP provides all benefits listedbefore to the new customers.

The New General Ledger is ready to use and strongly recommendedfor customer projects.

It is based on proven functionality and technology of the classic GL inR/3 which is currently used at more than 10.000 customers.

During ramp up of mySAP ERP 2004, SAP focuses on small and mid-sizeinstallations for the new General Ledger.

With unrestricted shipment of mySAP ERP 2004, the New General Ledgerwill be the default recommendation also for larger installations.

There are a few, small gaps in the New GL compared to the classic GL.These functions will be provided with mySAP ERP 2005, and importantfunctions will also be downgraded to mySAP ERP 2004 in year 2005.

The classic GL remains available in mySAP ERP

for upgrade customers

for new customers with specific industry requirements (see below)

-! 2 )1 !

7/23/2019 ASUG_0704_(2)



!

Some functionality from classic GL and profit center accounting is notyet available for the New GL.

Topic Planned for

Archiving of Totals and Documents ERP 2005 *

EURO Conversion ERP 2005 *

Audit Information System ERP 2005 *

Reconciliation report for totals and documents ERP 2005 *

Enhanced standard reporting for segment and profit center ERP 2005

Statistical Key Figures ERP 2005

Transfer Prices open

* Functionality will be downgraded to mySAP ERP 2004.

-! =! $

7/23/2019 ASUG_0704_(2)



The classic GL from SAP R/3 is still included in mySAP ERP.

Upgrade installations will continue to use their current applications perdefault. Customers who are satisfied with their current installation will

not be required to change anything and will not be affected at all.

There is a central flag in customizing to switch from the classic GL to theNew GL at a later point of time. This flag is available on client level.

In close cooperation with some ramp up customers, SAP will developsupport programs for different scenarios of switching from classic to

new GL. There will be a separate ramp up for these support programs.

Even with the availability of these support programs, there is no push-

button solution. Customers are strongly advised to setup a separateproject for changing from the classic GL to the New GL.

Benefits mentioned before fully apply to upgrade customers. However,the benefits have to be compared against the overall project effort of

changing to the new GL.

-! / 3 $ 2 (

7/23/2019 ASUG_0704_(2)



The required Customizing and the activation of the new GL istransported to the live system.

A transfer report (RGURECGLFLEX) generates the new data. Thismeans:

The open items are unchanged (BSIK..). The documents are unchanged (BKPF/BSEG).

The documents are used to generate FAGLFLEXA and FAGLFLEXT.

For the opening balance sheet, the initial positions are transferred

to FAGLFLEXT via a roll-up from GLT0.

The totals records of earlier previous years can also betransferred to FAGLFLEXT for reporting by using a roll-up fromGLT0.

The EC-PCA ledger and FI-SL ledgers will be evaluated as otherstarting points for the migration of totals.

-! / 3 5$ !

7/23/2019 ASUG_0704_(2)



During the data transfer, documents are automatically splitaccording to the Customizing settings.

The selection time frame for the data transfer must be selected insuch a way that it includes all open items.

If required, the document chains are analyzed for documentsplitting.

Old documents cannot be subsequently split according to new

account assignment (not included in BSEG).

Complete balance sheets according to new characteristics arethus only available after a transitional time period or requireadditional manual work.

-! !

7/23/2019 ASUG_0704_(2)



For a single client, the switch ‘read GLT0’ is used to control from

where the data is to be read (in a function module that is called whenthe logical database is read)

This setting can be overwritten by means of a user parameter(FAGL_READ_GLT0_USER)

You can thus create parallel reports for comparative purposes

FAGLFLEXT

GLT0Existingreports

ReadGLT0?

RFBILA, balance sheet, drilldown reporting.

Newreports

Balance sheet, drilldown reporting

$ ! 2

7/23/2019 ASUG_0704_(2)



Preparation

Identification of first

wave of ramp-up

customers

Q1 / 2004 –Q2 / 2004 mySAP ERP2004

General Functionality

Unified General Ledger

for Financial and

Management Accounting Extensibility / Flexibility

Balanced books by any

dimension

Parallel Accounting

Switch from “Classic GL”

will be developed together

with ramp-up customers

unrestricted shipment will

be reached earliest at the

end of the general ramp-up

General Functionality

EURO conversion

Archiving

Reconciliation Tools

Improved Online Split

…

Industry Requirements

Improvements for

Public Sector

Industry Templates

mySAP ERP2005

RTCJul 2004

$ 42 2

7/23/2019 ASUG_0704_(2)



1. The General Ledger supports a Unified Financial and ManagementAccounting.

2. It provides Extensibility and Flexibility to add industry or customer

specific dimensions to standard accounting.

3. There is powerful functionality for Balanced Books by Any Dimensionwhich is important for segment and management reporting, and inmany industries.

4. The General Ledger supports Parallel Accounting by Using Parallel

Ledgers or Parallel Accounts.

5. There is a strong support of Fast Close since many period-end

activities are no longer required.

6. The General Ledger provides perfect transparency and reduces therisk of non-compliance – thus supporting Corporate Governance.

7. Low TCO for implementing and running the General Ledger.

7/23/2019 ASUG_0704_(2)



#((

Session Code:

! '((%

7/23/2019 ASUG_0704_(2)



No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission 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 othersoftware vendors.

Microsoft, Windows, Outlook, and PowerPoint 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, and Informix are trademarks orregistered trademarks of IBM Corporation in the United States 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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C 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.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned hereinas well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several othercountries all over the world. All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Groupshall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products andservices 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.