FC – How To Guide
Flow behavior
BFC – HTG : FLOW BEHAVIOR(V1.0)
TABLE OF CONTENT
PURPOSE ......................................................................................................................................................... 3
OPENING AND CARRY-OVER FLOWS .......................................................................................................... 4
PACKAGE DATA .............................................................................................................................................. 7
CONSOLIDATION ........................................................................................................................................... 10
USING OPENING BALANCES ....................................................................................................................... 11
2
BFC – HTG : FLOW BEHAVIOR (V1.0)
PURPOSE
This document describes some of the flow behavior in Financial Consolidation.
3
BFC – HTG : FLOW BEHAVIOR (V1.0)
OPENING AND CARRY-OVER FLOWS
In the Category Builder, we use the following account setup.
Note: this is the account structure –but we really are interested only in ACCOUNT2
We define a single account family
4
BFC – HTG : FLOW BEHAVIOR (V1.0)
This is the Flow behavior for F00 and F20
For both these flows, F99 is the carry-over flow
For F99, this is the setup
5
BFC – HTG : FLOW BEHAVIOR (V1.0)
It has not carry-over but F00 is the opening flow.
There are no formulas – all is based only on flow behavior
6
BFC – HTG : FLOW BEHAVIOR (V1.0)
PACKAGE DATA
We have a Reporting Unit Organizer setup, with no opening balance
Opening the package, we see this:
7
BFC – HTG : FLOW BEHAVIOR (V1.0)
-
No data (of course, as this is a newly generate package)
-
F35 cannot be entered. This is because F35 is an undefined flow for this account family. I have
shown this for illustrative purposes. This flow plays no further role
-
-
F00 and F20 can be entered
F99 cannot be entered. This is because F99 of the carry-over flow
If we enter some data (on F00 and F20), the F99 flow is calculated
This is the simple principle of carry-over flows
8
BFC – HTG : FLOW BEHAVIOR (V1.0)
9
BFC – HTG : FLOW BEHAVIOR (V1.0)
CONSOLIDATION
We now consolidate (in EUR, our package was in GBP)
The F99 flow (for ACCOUNT2) is included in the consolidated data
Note: the exchange rate will calculate the “convamount” and “consamount” (250 * exchange rate)
10
BFC – HTG : FLOW BEHAVIOR (V1.0)
USING OPENING BALANCES
We now look at opening flows. First for the package
We create a new package (in 1900.02) with the previous period as its opening
When opening the package, we see the following:
11
BFC – HTG : FLOW BEHAVIOR (V1.0)
-
There is data (caused by the opening)
-
F20 can be entered
-
-
F00 has the value of 250. This came from the F99 of the previous period. This is the mechanism of
opening balance flow
F35 – as before, not relevant
F99 is 250 (this comes from the carry-over from F00, not directly from F99 from previous period)
F00 cannot be entered, see below
The RU Organizer controls the reason you cannot enter on F00. We have indicated that F00 is read-only if
there is an opening balance.
This is not by default like this, and the Category Scenario (or Flow behavior) does not control this.
12
BFC – HTG : FLOW BEHAVIOR (V1.0)
We enter some data (77, so we track it easily in the tables)
13
BFC – HTG : FLOW BEHAVIOR (V1.0)
We now run two consolidations
The first has no opening balance
The opening (of 250) on F00 is present, so is the F99.
All these values come simply from the package (via pre-consolidated)
The second consolidation, uses an opening balance
14
BFC – HTG : FLOW BEHAVIOR (V1.0)
F99 amount is there (as expected)
The main difference is that F00 will have a technical origin of -524287 (Consolidated op. bal.) as they now
come from the previous consolidation and not the package level
15
www.sap.com
© 2016 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
BusinessObjects Explorer, StreamWork, SAP HANA, 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 other countries.
Business Objects and the Business Objects logo, BusinessObjects,
Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP
company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL
Anywhere, and other Sybase products and services mentioned herein
as well as their respective logos are trademarks or registered
trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are
registered trademarks of Crossgate AG in Germany and other
countries. Crossgate is an SAP company.
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.
These materials are subject to change without notice. These materials
are provided by SAP AG and its affiliated companies ("SAP Group")
for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP Group
products and services 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.