Technical Aspect
Note:
- In the table below, if the Date tracked column
is marked as Yes, assume the Primary key to be Composite. The given
Primary will bind with the two date tracked columns to make the Composite
Primary keys
- Some of the
values in the column Table could be a view / synonym.
Table
Name
|
Date
Tracked?
|
Primary
Key
|
Description
|
FF_FORMULAS_F
|
Yes
|
FORMULA_ID
|
Stores the details of the Formulae,
along with the Business group, formula type, and the text. |
FF_FUNCTIONS
|
No
|
FUNCTION_ID
|
Stores the details of the Formula
Functions. |
FF_DATABASE_ITEMS |
No
|
USER_NAME
|
Stores the details of
the DBIs along with the Definition Text and user Entity. |
FF_USER_ENTITIES |
No
|
USER_ENTITY_ID
|
Stores the Entity Related
Information with ROUTE_ID |
FF_ROUTES |
No
|
ROUTE_ID
|
This one stores the actual query of
the DBI along with other details. |
FF_CONTEXTS |
No
|
CONTEXT_ID
|
Stores the different contexts used
in the DBI |
FF_ROUTE_CONTEXT_USAGES |
No
|
Composite
Primary Key
|
This links the FF_ROUTES and the
FF_CONTEXTS tables. |
Summary
In this chapter we
discussed about the need and usage of fats formulas. We started with the
basics, like variables, data types and expressions. Then we moved on to the
database items and global variables. We discussed about the flow of a formula,
the conditions, comments, Input Values and the different keywords. Then we
discussed about the user functions, their definition and how they are helpful
in adopting PLSQL programming into formulae. We discussed the compilations,
tips on the efficiency of the formula, the underlying table structures and
finally we saw two different examples of fast formulas.
No comments :
Post a Comment