SAP R3 Reporting Practices
SAP R3 Reporting Practices
SAP R3 Reporting Practices
Looking at R/3 Financials reporting overview Getting the most out of FI/CO Leveraging CO-PA best practices
What Well Cover Looking at R/3 Financials reporting overview Getting the most out of FI/CO Leveraging CO-PA best practices
R/3 Financials Reporting Overview Now more than ever, financial reporting is at the forefront of an organizations reporting needs
Greater visibility to their data (more/better reports) Verification that existing reports are timely and accurate Stock market collapse New legislation Sarbanes-Oxley New board of directors
Building Block
R/3 Financials Reporting Overview (cont.) This places new requirements on financial reporting teams
Must think outside the box Use new and different reporting tools Ensure that documented reporting standards exist and are followed Need additional knowledge on new tools and best practices Increased interaction and pressure from upper management
For a historical perspective on our current and future economic and regulatory environment, read Manias, Panics, and Crashes: A History Of Financial Crisis by Charles P. Kindleberger
2. Not knowing which tool to use for which report 3. Lack of report performance optimization techniques 4. Not making advanced configuration settings, which limits the reporting options GOTCHA! 5. Bad design decisions in the reporting submodules, which negatively impact reporting options
Drill-down
Cash Management
CO-PA
Report request no 1 2 no 3 no
no 4 5
no 6
no 7
no 8
no 9
no 10
no 11
Canned report
Drill-down
Painter/ Writer
Reporting submodules
SAP Query
ABAP
Report request no 1 2 no 3 no
no 4 5
no 6
no 7
no 8
no 9
no 10
no 11
Canned report
Drill-down
Painter/ Writer
Reporting submodules
SAP Query
ABAP
Key reporting tools (and submodules) you should be using How to get the most out of these reporting tools/modules How to alleviate common performance problems Tips for maximizing your reporting options when configuring the reporting submodules Advanced configuration techniques that will enable additional reporting functionality (in Appendix B on the CD)
What Well Cover Looking at R/3 Financials reporting overview Getting the most out of FI/CO Leveraging CO-PA best practices
Explore R/3 drill-down reporting Discover the Special Purpose Ledger Start using R/3 Cash Management! Consider implementing CO-PA
Enables reporting on multiple characteristics at once Users can slice and dice data A single report can fulfill multiple report requests Originally built for CO-PA, but now also usable for other FI/CO areas Foundational technology for BW reporting
See Appendix B for more on how to use this tool for PCA/Costing
Getting the Most from R/3 FI/CO Where can I use it?
General Ledger (G/L) Accounts Payable (A/P) Accounts Receivable (A/R) Profit Center Accounting (EC-PCA) Treasury (TR) Enterprise Controlling Consolidations (EC-CS) Controlling-Profitability Analysis (CO-PA) Project Systems Product Costing Special Purpose Ledger
You must go to the specific application area you want to do drill-down reporting on
See the handout on drill-down reporting for transaction code characteristics and value fields for each area
In 4.6C, there are new output types that you can use
Explore R/3 Drill-Down Reporting Output Types (cont.) New layout options
Graphical output
ALV output
Tip
You can give your users the option of selecting which output type to use when executing the report
Hinders performance A good rule of thumb is to limit characteristics to six or less Line item report for reconciliation Other drill-down reports that have additional characteristics Other SAP report types that are useful for your report See Appendix A for details!
Use frozen data for reports that take a long time to run
Captures only what you want, for the activities you want, in the time frame you want In very general terms, SPL can be thought of as the CO-PA of FI An SPL can update based on any activity You can pick up FI accounts as well as cost elements You can set up a series of ledgers that roll-up into one another for consolidated reporting
R/3 Profit Center Accounting is actually a Special Purpose Ledger!
Report off of a different fiscal year variant Report off of a different organizational structure Report on a different accounting basis (cash basis) Combine data from different parts of the system that arent normally available in a single transaction or reporting tool Consolidate data that falls outside of EC-CS or SEM Consolidations Stage data for export to an external consolidation tool Report off a subset of system activities Handle complex foreign currency reporting issues
It is hard to add them later! At a minimum, include transaction currency and local currency
Make sure you identify all of the activity types that you need to map To capture all of the characteristic data you need You will also have to maintain integrated master data via transaction code GCS1
Your SPL totals table is available as a reporting table in Painter/Writer Use transaction code GCRE1 to activate drill-down reporting for your SPL You will also have to maintain integrated master data via transaction code GCS1
Note
See also: How to Tap into the Power of the Special Purpose Ledger Quentin Hurst
Submodule within Treasury Used to report short-term and medium-term cash position and forecast Electronic bank statement Lockbox processing The Cash Management Position (CMP) report The Liquidity Forecast (LF) report
Well cover the CMP and LF reports since theyre particularly important!
Note
Based on banking transactions entered in R/3 Looks at actual cash transactions only Great tool to help manage float timing differences of when different deposits, outgoing checks, wires, etc., clear the bank
T code FF7A
Forecasts future obligations and receipts Based on business transactions entered in R/3 Includes transactions to convert outgoing/incoming documents to cash Purchase orders, A/P invoices Sales orders, A/R invoices
T code FF7B
You can merge the two reports together to get a consolidated picture of your cash and liquidity positions Provides the optimum view of short-term cash position and forecasted cash position
Use a proper bank account G/L structure Set up the appropriate number of planning groups
What Well Cover Looking at R/3 Financials reporting overview Getting the most out of FI/CO Leveraging CO-PA best practices
R/3 module for tracking and analyzing profitability Helps you understand where your profits come from Captures revenue and cost of goods sold conditions from Sales and Distribution (SD) Can also capture variances and assessments
Materials Manager (MM) variances, Production Planning (PP) variances, CO assessments, and FI journal entry activity
Which are the most profitable customers? What product lines give me maximum contribution margin?
Poor report performance Bad design decisions limits what data you can report on Inconsistent value for the same key figure on different reports Difficult or erroneous reconciliation
GOTCHA!
1. 2. 3. 4.
Choose value fields strategically Ensure consistency with key figure schemes Boost performance with summarization levels Hasten runtimes with report splitting and Report/Report Interface (RRI) 5. Reconciliation tools
In the Appendix on the CD, there are five more CO-PA best practices!
Example: setting up a single field called Net Revenue instead of the components as separate fields Its indivisible once its posted As time goes on, you will be asked to break out Net Revenue to its individual components for analysis
Even if you dont have a current requirement to justify the field, in the future someone will probably ask You can always add value fields together when detail isnt needed
You set them up once and use them across your reports Ensures line items have the same definition across reports Net revenue, total cost of goods sold, etc. When creating your report forms, you have the option of using value fields or key figures
When creating the report form, you will be prompted on whether to use characteristics, value fields with characteristics, or a key figure scheme
You define summary levels (tables) and specify an update frequency R/3 generates, loads, and updates the summary tables When designing reports, you tell R/3 to use the summarized data R/3 fills in any missing data from original table (new with 4.5!)
SL
First
SL
SL
Report
R/3
If no ne fo und
CE3
1. Define summarization levels using transaction code KEDV 2. Then tell R/3 to load the level by executing report RKETRERU Transaction code KEDU 3. Schedule report RKETRERU to periodically run to update your levels Create variant in KEDU, then schedule a batch job to run off of that variant
Tcode KEDV
Choose a frequent update strategy to get the most boost normally a nightly update strategy is used Set up and transport your levels from your Gold/CTS client Include dependent characteristics in summarization levels Dont define too many summarization levels (8-20 suffice) Avoid redundant summarization levels Make sure to periodically delete unused summarization levels Use the delivered summarization level tools
You can also use the summary tables created by summarization levels to hasten custom ABAP reports
Tip
Both improve performance Break one report into multiple reports Useful with large number of characteristics or high data volume Report splitting one report automatically calls the other RRI from the first report list you use, manually navigate to the lower-level report using a menu path
Splitting RRI
Original slow report Faster runtime: 2 smaller reports; one calls the other when needed
Hasten Runtime with Splitting and RRI (cont.) Use transaction code KE3L
Hasten Runtime with Splitting and RRI (cont.) For drill-down reporting, go to the Options tab in either the create or change mode and click on the Report assignment button
Reports that use a lot of characteristics or characteristics that have a lot of values performance becomes an issue Users typically do the same drill-down, e.g., company code, then product line, then customer When you want to link different types of reports, such as ABAP programs to Painter reports or SAP queries to drill-down reports Users dont use a single drill-down approach, so splitting isnt a viable option
When splitting a report, users are limited to specific drill-downs
Name was derived from its transaction code KEAT Tries to reconcile FI, PCA, SD, and CO-PA at an SD condition/account level Provides a quick overview of any discrepancies Offers drill-back functionality for out-of-balance entries
T code KEAT
Not completely reliable, especially in make-to-order environments FI initiated updates arent tracked well or consistently Report output isnt customizable Use as a quick check to identify errors If KEAT shows an error, generally it is an error Doesnt always show all errors Still need a more reliable reconciliation tool for detailed reconciliations
The verdict:
Simply stated, it is the creation of a COS cost element in CO, coupled with the necessary configuration to force a CO-PA segment update during any COS activity The solution provides Dual update into CO-PA delivery and billing A separate value field for each update A low-data alternative to setting up account-based COPA
Benefit from R/3s frozen data feature Boost performance with summarization data Use realignments for mass changes Leverage line item reports Start using characteristic hierarchies
Resources Dig into your system... On CO-PA or financial reporting: help.sap.com The R/3 Reporting Made Easy Guidebook Configuring SAP R/3 FI/CO, by Quentin Hurst and David Nowak Sybex 2000 On your CD
Drill-down reporting handout Appendix A: More CO-PA best practices Appendix B: Using Drill-Down for PCA and Product Costing!
7 Key Points to Take Home Drill-down reporting isnt just for CO-PA anymore Search for the node information system in the IMG
There are report optimization techniques in CO-PA that arent available to other reporting tools There are specific reasons why you would use a Special Purpose Ledger
7 Key Points to Take Home! (cont.) SAP Query has been given a bad wrap give it a try Cash Management Position and Liquidity Forecast are two strategic reporting tools that are often overlooked Dont forget the Appendices
Your Turn!
Questions?