Statistical Key Figures

in mySAP ERP 2005

SAP AG

20.07.2005

©SAP AG 2005
 Statistical Key Figures

New Features for Statistical Key Figures

„ From mySAP ERP2005, statistical key figures can now be stored in
New General Ledger Accounting as well
„ Entry in CO as ACTUALS (KB31N) and PLAN (KP46)
(online update and complete transfer using report)
„ Entry in FI
(new transactions FAGLSKF / FAGLSKF1)
„ Possible to use report to perform one complete transfer from Profit
Center Accounting (no online transfer)
„ Own tables: FAGLSKF , FAGLSKF_PN

© SAP AG 2005
 Data Storage

Data Storage
„ On the database, independently of the ledger
„ Fiscal year, period, and fiscal year variant not stored
„ No period block (as in CO, PCA, and SL tables)
„ For each statistical key figure, company code, and account assignment
(cost center, profit center, segment, and so on), the quantitiy is stored
with a date field
„ Sorting into periods only when the data is read:

a. Ledger + company code Î fiscal year variant

b. Fiscal year variant + year, period Î date known

© SAP AG 2005
 When Are Statistical Key Figures Required?

ƒ FI allocation (from ERP2004):

For example Î Distribution of amounts from PC1 to PC2 and
PC3 on the basis of the number of employees:

PC Acct Stat.KF Amount Qty Unit

PC1 400000 1.000 EUR
PC2 9100 60 Employees
PC3 9100 40 Employees

ƒ Reporting: FAGLSKF3 : simple ALV list

ƒ Reporting: in BW
(DataSource, extractor exists, no InfoObjects, InfoSource, InfoCube )
ƒ Reporting: Drilldown – Example report 0SAPSTKYF-01 (must be
copied and adjusted by customer)

© SAP AG 2005
 Update of Characteristics

Update of Characteristics

Since the data is stored independently of the ledger, the scenarios

for all ledgers in General Ledger Accounting are considered. If a
scenario is used in at least one ledger, the fields of this scenario
are also updated.

(For example, if three ledgers are used and then a fourth ledger is
later implemented, and no new scenarios are used in the fourth
ledger, the data automatically becomes available for the fourth
ledger.)

© SAP AG 2005
 Enhancement of Transactions
CO KB31N CO- Stat. key figures ACT Online into FI
IST
KP46 CO- Stat. key figures PLAN Online into FI
PLAN
FAGLSKF6 Rebuild of stat. key figures in FI from the data
posted in CO
FI FAGLSKF FI-IST Statistical key figures New entry transaction
(ACT) for Gen. Ledger

FAGLSKF1 FI- Statistical key figures New entry transaction

PLAN (PLAN) for Gen. Ledger
New transaction
Old transaction
FAGLSKF7 FI-IST Rebuild of statistical key figures in FI from FI data
FI-
PLAN
PCA 9KE5 PCA- Balances: Stat. key No transfer to FI
IST figures

7KE5 PCA- Planning: Stat. Key No transfer to FI

PLAN figures

FAGLSKF8 FI-IST Rebuild of statistical key figures in FI from data

FI- posted in PCA
PLAN

© SAP AG 2005
 Authorization Object F_FAGL_SKF

Authorization Object F_FAGL_SKF

ƒ Business activity GLSK , RKS , PRC2 ,GLPK , RKP4 , PCAK

ƒ Authorization activity 02 , 03
ACTUAL PLAN
ƒ Company code
ƒ No special objects such as profit centers or individual stat. key figures
ƒ The (plan) version and the record type (actual data or plan data) can still be
checked additionally in a BAdI

© SAP AG 2005
 Statistical Key Figures (ACTUAL) for
New General Ledger Accounting (FAGLSKF)

Item data entry using ALV Edit

© SAP AG 2005
 Posting Logic in FI

Posting Logic in FI (in connection with CO)

Example:
• Two cost centers (1,2) are assigned to a profit center (A)
• Key figures of type 1 (fixed values such as employee) need to be posted
• Posting in CO: Ctr 1 / Qty 100 im FI:
Ctr 2 / Qty 200 KST PC Menge Aktivität
PC A = 300
If the entry Profit Center A => 800 (target value) 1 A 100 RKS
is now made in FI,
the database then has three records in FI 2 A 200 RKS

A 500 GLSK
Subsequent postings in CO only affect RKS !

Î If possible:
First close CO entries (for example, entries for cost centers and and orders) and then
adjust values in FI (for example, entries for profit centers and segments).

© SAP AG 2005
 Statistical Key Figures (PLAN) for
New General Ledger Accounting (FAGLSKF1)

In contrast to the entry for ACTUAL, the plan version is quoted here

© SAP AG 2005
 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, 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 or registered 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 registered trademarks 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 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 informational purposes only. National product specifications
may vary.

„ The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose
without the express prior written permission of SAP AG.
„ This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
„ SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited
to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
„ SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use
of these materials. This limitation shall not apply in cases of intent or gross negligence.
„ The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use
of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party
Web pages.

© SAP AG 2005