Professional Documents
Culture Documents
Training: April 2011
Training: April 2011
April 2011
TRAINING
FIN201 – Fundamentals Finance part 2,
Booklet
Version 6.2
TRAINING FIN201 – Fundamentals Finance part 2, Booklet – 2/15
COURSE CONTENTS
COURSE CONTENTS................................................................................................. 2
2. ANALYTICAL FUNCTIONALITY....................................................................3
2.1. Analytical Accounting.....................................................................................3
2.2. Analytical Ledgers.......................................................................................... 3
2.3. Analytical Accounting.....................................................................................4
2.4. Analytical Accounting.....................................................................................4
2.5. Dimension Types...........................................................................................5
2.6. Dimension Values.......................................................................................... 6
2.7. Dimension Types – Default Dimensions........................................................7
2.8. Dimension Types – Control & Restrictions.....................................................7
2.9. Dimension & Account Restrictions.................................................................8
2.10. Dimension Pyramids/Groups..........................................................................9
2.11. Analytic Allocations......................................................................................10
2.12. Budgets........................................................................................................ 11
2.13. Commitments and Pre-Commitments..........................................................14
2.14. Inquiries....................................................................................................... 14
2.15. Reports........................................................................................................ 15
2. ANALYTICAL FUNCTIONALITY
Only ONE ledger within an accounting core model should be authorized as « Operating
budgets ».
Dimensions can easily be added to an analytical ledger but not removed. ANA folder option controls the
number of types that are allowed for any single line (Maximum 20).
Invoice
Product Sales
Number Account Account
Type Region
701000 5000 Cars UK
1
701000 Trucks UK
2 702000 Cars USA
6
The user has a choice of which ledgers, if any, are to use Analytical functions.
A ledger may only be Analytical.
The User has a choice of which ledgers, if any, are to use Analytical functions.
A ledger may be combined with another Ledger. Here the same ledger is both general & analytical
Auto Carry
Size
Create Forward
Adjustment
Entity Envelope
Allowed
For direct journal entry, a new initialization of the dimensions exists. This new
initialization is made with respect to the previous line. The rule applied consists in:
Step 1- Taking into account of the default dimension code by means of the default value DEFVAL
defined in the document entry transaction (tab Dimensions)
Otherwise (not found), Step 2
Step 2 - Taking into account of the CDE default dimension code in "hard code" in the setting of the
document entry transaction (tab Dimensions)
Carry Forward stops the resetting to zero of the collected values during the financial year.
The No Financial Units can be used for budget comparison and the use of latest distribution.
Dimension Restrictions allow the user to limit values e.g. Finance department with a Product Category.
Exercise 1
The types you see, and post to, can be controlled at:
Company level: here you can make dimensions mandatory on all postings (useful for countries where
segmented accounts are normal, such as USA)
Ledger level: here you can limit types available for a given ledger and determine how many types will
be used
Account level: here you must add all the dimension types that you wish to post to, otherwise you
cannot enter values.
Common data > G/L Accounting Tables > Analytical > Prohibition codes
In order to ensure the consistency of the analytical postings, it is possible to prohibit the entry of
associations between accounts, between dimensions or between dimensions and accounts.
The principle is to define the “restriction codes” combinations that are incompatible upon posting. When
two accounts, two dimensions or an account/dimension pair have unauthorized codes, they cannot be
used together to post the same entry line.
For instance: account/dimension restriction
Over a dimension view X designed to analyse expenses relating to corporate vehicles, it will be possible
to prohibit the posting of accounts other than those likely to record vehicle expenses (maintenance,
petrol, taxes, etc.). For instance, on entry, the user will not be able to allocate an account of “turnover”
type to a dimension of the dimension view X.
The restriction function makes it possible to define the restriction codes that it will not be possible to
associate upon journal entry.
Exercise 2
2.10. Dimension
Dimension Pyramids/Groups
Pyramids/Groups
Common data > G/L Accounting Tables > Analytical > Dimensions Pyramids
Allows user to create a hierarchy of dimensions for reporting purposes
15
For example the Total value will show a single value at the highest level and will generate more totals as
you ask for greater level detail (20,30 etc.).
The migration of data has been improved: instead of carrying out on a last homogeneous
level: the migration takes the lower levels into account.
Exercise 3
Analytical Allocations
Common data > G/L Accounting Tables > Analytical > Analytic allocations
Enable immediate distribution of analytical values against a single
Enable immediate distribution of analytical values against a single account
account
Allows
Allows a single
a single journal
journal lineline rather
rather thanthan multiple
multiple lines
lines
It often happens that several analytic allocations correspond to one18 accounting allocation. In that case,
the “distribution” enables an amount entered to the general ledger to be distributed onto several analytical
dimensions.
The allocation can be limited to a single company, site or a group.
Exercise 4
2.12. Budgets
Parameters used within a budget
Budget
Company or Site Cannot be both
Code Mandatory
Weighting Optional
Chart of Accounts Determines dimensions available
Up to 3 Dimension Types Pyramids optional
Currency Mandatory
Quantity Optional
Controls None, Annual, Period or Sliding [Multi Annual]
No, Manual [Allows MO and Budget Entry], Complete
Misc. Ops. Allowed
[same as manual but generates trace in Misc Ops]
Controls:
Currency (field CUR)
It indicates the currency in which the budget must be built. By default, this field is initialized with the local
currency of the company concerned by the budget.
Company A to Company B
Site A to Site B
Year 1 to Year 2
Ledger1 to Ledger2
Increase or Decrease Amounts
Formulae can be used to generate lines within a budget from either previous budgets or actual values
Budget Copy
Destination Budget (field BUDDES)
If the destination budget exists, it must have the same characteristics as the original budget:
it must bear the same dimension view code,
or it must be associated with a reverse dimension view code.
If analytical pyramids are defined on the original budget, the same analytical pyramids must be
associated with the destination budget.
If the destination budget does not exist, its creation is submitted. This new budget is by default strictly
identical to the original budget.
The destination budget can show an amount (or a quantity) that is similar to the original budget but it
can also show an increase or a decrease with respect to the original budget, via the coef field.
For instance:
Entered coefficient =0.95, which means a 5% decrease.
Entered coefficient =1.20, which means a 20% increase.
Formula Codes
This function is used to automatically calculate the elements constituting a budget code by means of
formulas indicating the elements to be calculated and from where to start the calculation.
It is with this single function that the parameterization of all the calculation elements is carried out.
For instance: The budget for company AAA is calculated each year on a global envelope basis
($100,000). For each dimension, the proportion (%) of the actual N-1 with respect to the N-1 budget,
determines the new percentage for the budget obtained for the year N. In this way, the budget N for
“Department 1” is equal to the total amount for the Budget N* (Actual for “Department 1” / Total
amount for N-1 budget). This case can be defined simply in the following way:
Exercise 5
The use of commitments and pre-commitments is detailed during the Finance Advanced Course in the
topic called “Budget control”.
Purchase Request creates a Pre-Commitment
Purchase Order creates a Commitment
These values are stored and viewed in a unique Commitments function GESCMM
Amendments to a PO will cause reversal of the original line and creation of a new line
This functionality may be automatic or set to manual operation whereby the user creates commitments as
required and possibly only for limited purchases.
User-defined order
User-defined number of rows.
Exercise 6
2.15. Reports