Post on 18-Apr-2015
Live Expert Session
Murali Chandrasekaran – CSA EPM
July 20th 2011
© 2011 SAP AG. All rights reserved. 2
Agenda
Introduction
Creating the Model
Consolidation features
Consolidation Monitor
Controls
Ownership Manager
Journals
Business Rules
Incremental / Full Consolidation
IFRS Starter Kit
Questions
Introduction
© 2011 SAP AG. All rights reserved. 4
Terminology between BPC 7.5 and BPC 10
BPC 7.5 BPC 10.0 NetWeaver
Appset Environment InfoArea
Application Model InfoCube
Dimension Dimension InfoObjects
Property Attribute Attribute
Apshell EnvironmentShell
© 2011 SAP AG. All rights reserved. 5
Terminology between BPC 7.5 and BPC 10
BPC 7.5 BPC 10.0
Input Schedules Input Form
Reports Reports
Dynamic Hierarchy Editor Ownership Manager
Current View Context
DataSource AuditID
Appset Busines Rules Global Definitions
Application Business Rules Model Business Rules
Automatic Adjustments Elimination and Adjustments
Validations Controls
Account Transformations Account-based calculations
© 2011 SAP AG. All rights reserved. 6
Consolidation Features in 10.0
Functionality Comment
Consolidation Monitor New feature
Controls New feature (replace validations
but more powerfull)
Journals Enhanced functionality and is
now web-based
Ownership Manager Similar functionality than DHE
and is now web-based
Business Rules Similar functionality than in 7.5,
but the uses the web based client
Creating the model
© 2011 SAP AG. All rights reserved. 8
Administration Console
All the administration tasks are now available through
the Web client.
A Navigation Panel enables to access all the
administration views that are grouped by consistent
domains.
© 2011 SAP AG. All rights reserved. 9
Required Dimension properties for Consolidation
When creating dimension the system will provide options to create all
dimension properties required for Consolidation and Ownership (available
option depends on dimension type)
© 2011 SAP AG. All rights reserved. 10
Web Admin parameters
Web Administration parameters (appset and application parameters) are now
maintained in the NetWeaver back-end with the transaction SPRO
Consolidation Features
© 2011 SAP AG. All rights reserved. 12
Consolidation Central
The Consolidation Central now groups all the all the main tasks linked to
consolidation
The node contains 4 modules (only 2 on the MS platform) being
Consolidation Monitor (NW only)
Controls (NW only)
Journals
Ownership Manager
Consolidation Monitor
© 2011 SAP AG. All rights reserved. 14
Consolidation Monitor
Introduction
This feature provides an overview of the whole consolidation process in one single
screen. The monitor tracks the following items:
Status of the controls
Work Status
Execution status for currency conversion
Execution status for consolidation
This feature will be very useful for all the users that need to monitor the progress of the
consolidation process (at a group or at a local level), as they have all the information they
need on one single screen.
The currency conversion and consolidation processes can also be started from this screen
© 2011 SAP AG. All rights reserved. 15
Consolidation Monitor
Starting Page
The starting page can be divided into 3 sections
– Context: Selection of Model, Category, Entity and Consolidation Group
– Actions List of possible actions
– Status: Details of the status for the selected context
Context
Actions
Status
© 2011 SAP AG. All rights reserved. 16
Consolidation Monitor
Actions
The following Actions are available (some actions may be grayed out if no entity or a node
level is selected)
– Work Status: Open the screen to update work status for the selection
– Translate: Runs currency conversion
– Consolidate: Runs consolidation
– Display Running Processes: Opens a window that shows which processes are currently running
– Reset: Resets execution status for Currency Translation and Consolidation
– Refresh: Refreshes the current screen
– Show Description: Shows description instead of ID
– View Select between a hierarchical and flat view
© 2011 SAP AG. All rights reserved. 17
Consolidation Monitor
Running Processes
The following steps need to be performed in order to execute Currency Conversion
1. In Consolidation Central Consolidation Monitor, in the scope context area, select the Category, Time
and Group dimension members for which you want to run the currency translation.
2. Select the row for the Group or Entity you require and click Translate.
3. In the next dialog box, verify the selected dimension members and choose whether to run a full or
incremental process.
4. Click OK.
© 2011 SAP AG. All rights reserved. 18
Consolidation Monitor
Currency Conversion and Consolidation
Please note the following points:
– Member in the Entity type dimension of the Rate application needs to be called GLOBAL (in upper
case) for the conversion to group currencies to work properly
– The respective programs for currency conversion and consolidation are called directly. No logic script
is called, therefore no custom calculations can be executed.
© 2011 SAP AG. All rights reserved. 19
Consolidation Monitor
Display Running Processes
This screen displays the currently running processes and shows the progress of each
process (you can select whether you want to see all processes or only your own ones)
If a process has failed, opening this screen will allow this process to be reset (after a
certain period), so that it can be executed again.
© 2011 SAP AG. All rights reserved. 20
Consolidation Monitor
Reset
Highlight a group or entity and click the Reset button, this will display a screen with the
current selection
The Currency Conversion and Consolidation status are then set back to “To be executed”
© 2011 SAP AG. All rights reserved. 21
Consolidation Monitor
Status Roll-up
The status on the parent level (for controls, work status, currency translation and
consolidation) is based on the lowest status of the children. There is no status that is stored
on the node levels, they are computed when the monitor is displayed.
In the example below, one entity has the status set to To Be Executed and the parent
Corporate shows that same status, as it is the lowest status of all it’s children.
ControlsControls
© 2011 SAP AG. All rights reserved. 23
Controls
Introduction
New “Controls” feature replaces the former “Validation” business rule; they have a
new dedicated interface for maintenance within the web administration console.
Controls are organized in control sets, which are activated using assignments per
Category and Period.
The new controls home page displays the number of controls per model, as well as
well as the number of control sets and assignments
Controls are associated to a Control Level property : this new property is also
mandatory on the entity dimension of the selected model in order to launch only the
relevant controls for each entity
© 2011 SAP AG. All rights reserved. 24
Controls
Administration - Overview
The Main Controls Main Page shows the different objects that have been defined
When a specific component is open, there is always a link on the top right of the screen for
the next step
– In Controls
– In Control Sets
– In Assignments
© 2011 SAP AG. All rights reserved. 25
Controls
Administration
The Main screen for controls can be used to add New controls, Edit or Delete existing
controls
The drop-down box allows to display all controls or to filter them by a Set of controls
© 2011 SAP AG. All rights reserved. 26
Controls
Editing controls
The control definition screen can be split in 2 main sections:
– The top of the screen contains the buttons to Save, Close and Validate the control
– The header section : specifies the type of control, the threshold and the break-down dimensions
– The detail section : specifies which members are compared (account,flow, interco and auditid)
Top
Header
Detail
© 2011 SAP AG. All rights reserved. 27
Controls
Editing Controls (2)
The header section
– Type : Blocking / Warning. All blocking controls must pass before the work status can be changed
– Tolerance Threshold (in value or percentage)
– Control Level : control only executed for entities with specific control levels
– Breakdown Dimension(s)
o Up to 2 dimensions can be specified as break-down dimensions
o The control will be executed separately for each member of the break-down dimension. In the
example of a break-down by Audit on the member ALL_INPUT, the control will be executed for each
member below ALL_INPUT (INPUT and INPUT11) in this example
o For a breakdown, the same member must be specified in the top and in the bottom part
– Compare different periods and/or category in controls (compare to last year for example)
© 2011 SAP AG. All rights reserved. 28
Controls
Controls Monitor
Controls Monitor indicates for each entity :
– Control Set : Control set that has been assigned for this category and period
– Status : displays status of current control
– Level : level of control applicable for that entity (linked to the CONTROL_LEVEL property)
– Number of Blocking : How many blocking controls have failed
– Number of Warnings : How many warning controls have failed
© 2011 SAP AG. All rights reserved. 29
Controls
Controls Monitor
Depending on the type of application, the entities are organized according to :
– the setup in the Ownership Manager for Consolidation applications
– The hierarchy of the Entity dimension for Planning applications
The View drop down box on the top right corner allows to select between a hierarchy and a
flat view
© 2011 SAP AG. All rights reserved. 30
Controls
Execute Controls
To execute controls, highlight the entity or node and click the button Run Controls button
Check the settings for the dimensions, they should be correct as they are taken over from
the context
© 2011 SAP AG. All rights reserved. 31
Controls
Review Controls (1)
After the execution, the status and the number of blockings and warnings are updated
Status for node levels are calculated on the fly, the node level will always show the lowest
status of all its children
Highlighting an entity in the top part of the screen display a list of the failed controls in the
bottom part of the screen (details for S000 in this example)
© 2011 SAP AG. All rights reserved. 32
Controls
Review Controls (2)
To get a detailed view of all controls, select the Entity and click the Open Control Results
button
This opens a new tab that contains the details (with filtering by status possibilties)
Ownership Manager
© 2011 SAP AG. All rights reserved. 34
Ownership Manager
Overview
The formerly called dynamic hierarchy editor was rewritten, moved to the web
client, and renamed Ownership Manager.
The features are essentially the same than in the DHE
A read-only landing page was added in order to enable access to this feature
to a broader user-base with viewing needs only.
An editable page can be used to manually update ownership data or run the
Ownership Calculation routine.
In the editor, columns to be displayed can be selected.
Note: On the NW platform, the Ownership Calculation can be called from
within the Ownership Manager Editor. The use of a specific Data Manager
package is no longer needed.
© 2011 SAP AG. All rights reserved. 35
Ownership Manager
Display structure
The Ownership Manager displays the ownership structure for the selected Context
© 2011 SAP AG. All rights reserved. 36
Ownership Manager
Editor
The Edition view can be used to add new entities, remove entities and specify the
consolidation method and the rates
© 2011 SAP AG. All rights reserved. 37
Ownership Manager
Calculations
The Ownership Manager can also be used to launch the calculations of the
Ownerships based on the direct ownerships that were entered in a schedule
Journals
© 2011 SAP AG. All rights reserved. 39
Journals
Overview
The journals have been moved to the web-interface. The basic functionality is
very similar and the following features have been added (or enhanced)
New search functionality
Journal groups
Advanced balancing
Multi-header and multi-value journals (new for NW, was already existing in MS)
Badi on journals (NW only)
Additional Properties
Lock/unlocking of journals
© 2011 SAP AG. All rights reserved. 40
Journals
Managing the journal template
Highlighting the journal template activates/deactivates available actions that can be
taken.
The following journal parameters can be defined
© 2011 SAP AG. All rights reserved. 41
Journals
Journal Template Features
The journal template can define how the journal entries will be displayed. By
checking the Balance by Entity option, the journal entries will be subtotaled and
checked for balances across each Entity (the Balance by Currency works in a
similar fashion).
© 2011 SAP AG. All rights reserved. 42
Journals
Journal Entries
Journal statuses can be viewed on the journal landing page, as well as date of
posting, who posted the document, and modified date/time.
Individual Journals can be opened in separate tabs for easy viewing.
© 2011 SAP AG. All rights reserved. 43
Journals
Journal Landing Page
Journal entries can be entered via the web interface or via the EPM 10 add-in for
Excel. When entering a journal via the web interface, navigate to Consolidation
Central >Journals > New.
© 2011 SAP AG. All rights reserved. 44
Advanced Query for Journal Entries
Advanced query: files can be +/- from the query definition, values can be
included/excluded, and journal properties can be access via the advanced query tool.
Advanced Query allows end-users to define criteria making it faster and easier to display
specific journals
All dimensions and journal options can be used as filters
Filter on text fields “Beginning with…”, “Containing…”, “In List” as well as on Dates:
“From… To…”
Journals
© 2011 SAP AG. All rights reserved. 45
Journals
Journal Group Management
Journals created via multiple headers are automatically grouped together under a
common Group ID.
Grouped journals can be ungrouped and separated into independent journals.
Actions taken (such as Posting) on one group member will be taken on all group
members.
© 2011 SAP AG. All rights reserved. 46
Journals
Advanced Journal Balancing
Journal entries are checked dynamically, if an out of balance condition occurs the
system will color code the problem area in red highlights.
© 2011 SAP AG. All rights reserved. 47
Journals
Multiples headers / values
The following options are available:
Multiple Headers : same journal details will be posted to different members (for example
same values can be posted to different periods)
Multiple Values : user can specify different debit/credit values for each member (for
example different members per period)
Here is an example of a multiple values journal template entries with 3 time periods
© 2011 SAP AG. All rights reserved. 48
Journals
Journal BAdIs (Business Add Ins)
When journal entries are being Saved or Posted, an ABAP based BAdI can be
triggered to create additional calculated records.
This journal specific BAdI allows can perform calculations on the journal entries and
can create new records which will be stored and displayed within the journal itself.
The BAdI is delivered empty but can be customized by clients.
A typical BAdI implementation will be able to leverage fields that the journal.lgf
logic does not access (additional items, date fields, and so on)
© 2011 SAP AG. All rights reserved. 49
Journals
Additional Properties
The Additional Properties sub-tab allows the user to enter and additional property
fields defined in the template. See the entry for “Ldate” in the example below.
Consolidation FeaturesBusiness Rules
© 2011 SAP AG. All rights reserved. 51
Business Rules
New User Interface
Business rules interface was rewritten to be part of the new web
administration console.
Business Rules are no longer activated when a model is created or modified.
This can be done directly from the Rules view in the Administration Console
Consolidation FeaturesIncremental / Full Consolidation
© 2011 SAP AG. All rights reserved. 53
Consolidation Monitor
Incremental vs. Full
The Currency Conversion and Consolidation programs can be executed in incremental or
full mode. The incremental mode will only execute the program for those entities that were
changed since the last execution of the program (this is of course much faster than
executing the program for all entities)
The process works the following way:
– Every time data is written-back to the system, a timestamp is written to a separate table to keep track
of when the data of an entity has last been updated
– When a program runs in incremental mode, it will check which entity have been modified since it’s last
execution and only perform the calculation for those entities, which significantly speeds up the
process.
© 2011 SAP AG. All rights reserved. 54
Consolidation Monitor
Incremental vs. Full (cont’d)
The incremental mode only works when data have been updated, it does not work in the
following cases:
Rates were changed
Ownership information was changed
Business Rules were changed
The program needs to be run in full mode if one of the cases mentioned above has
occurred
IFRS Starter-Kit
© 2011 SAP AG. All rights reserved. 56
Starter KitsFaster legal compliance – reduce implementation
Fast implementation
● Pre-packaged content reduces implementation
times
● Dynamic configuration enables easy
customization to specific requirements
● Complete, generic reference implementation
Rapid and trusted legal compliance
● Embedded expertise in meeting financial
regulations including best practice in financial
consolidations and internal controls
● Detailed process guidance for business users
Comprehensive scope
● Full support for GAAP to IFRS transition
● Pre-configured IFRS/GAAP consolidation rules,
controls, and calculations
● Publishable financial statements
© 2011 SAP AG. All rights reserved. 57
For more information
See sap.com for:● Solution in detail
www.sap.com/epm
See help.sap.com for:● Starter Kit Description
● Help and documentation
● Release Notes
● IFRS Analysis Notes
http://help.sap.com
See sap.ifrs.community.com for:● Starter kit for IFRS Blogs
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/17896
You can also follow us on:
www.twitter.com/SAP_IFRS_XBRL
www.facebook.com/sapifrs
www.linkedin.com/
Specific starter kit content examples
SAP BusinessObjects Planning and Consolidation, starter kit for IFRS on SAP NetWeaver
© 2011 SAP AG. All rights reserved. 59
SAP BusinessObjects Planning and Consolidation
Starter kit for IFRS on SAP NetWeaverData collection, control and data processing
Business Process Flows
● Data collection
● Preparing and running the consolidation
● Reports and analysis
IFRS Data Input & Control
● CoA based on final IFRS Taxonomy 2010
● Input schedules for data entry or data import
● Control reports for validation of collected
data
Consolidation Processing
● Full, proportionate and equity method
● Extensive set of automatic business rules
● Scope changes and rate variations
© 2011 SAP AG. All rights reserved. 60
SAP BusinessObjects Planning and Consolidation
Starter kit for IFRS on the SAP NetWeaverAnalysis, audit trail and publishing of financial statements
Analysis & Audit Trail
● Dynamically formatted accounting and
analysis reports leverage native drill down
● Audit IDs for tracking data origin
Publishable Financial Statements
following the requirements of IAS 1
● Balance Sheet (current/non-current format)
● Income Statement (by function)
● Statement of Comprehensive Income
● Statement of Cash Flows
● Statement of Changes in Equity
XBRL Templates
● Excel templates pre-mapped with IFRS
taxonomy
Questions
Thank You!
Contact information:
Murali Chandrasekaran
CSA - EPM
Murali.Chandrasekaran@sap.com