Architectural Principles Economics and Financial
PPDM does not, at this time, provide an economic model to handle AFE’s and other financial information other than at a high level. Feedback from the membership indicates that most members have financial systems in place, and merely wish to obtain summary information or pointers into the financial databases.
Contents |
Guidelines
1. Currency values should be stored in a single unit of measure for a column in a table to prevent scalability problems from developing. In addition, as many currency-based questions are likely to combine data from more than one column, it is desirable to encourage all values in a table or even in a subject area (CONTRACTS) to utilize the same stored currency type .
- Use the currency domain (NUMBER 12,2).
2. The column CURRENCY_OUOM should accompany each currency. In many cases, one set of these is sufficient for a row in a table, even if there is more than one currency value stored.
- Indicates the units of currency as originally received by the payee.
3. The column CURRENCY CONVERSION should accompany each currency field. In many cases, one set of these is sufficient for a row in a table, even if there is more than one currency value stored. Use the following column information:
- Use the currency conversion domain (NUMBER 10,5)
- CURRENCY CONVERSION RATE: the rate applied to convert the currency to its original monetary UOM from the stored UOM. This value is valid for this row in this table only. When this value is multiplied by the STORED currency value, the original value of the transaction in the original currency is obtained.
Modeling Financial Information
1. At this time, PPDM does not attempt to fully model financial or accounting information. Intent of modeling should be to capture summary information and a connection to an accounting system only.
2. AFE or cost center numbers may be captured in the data model:
- using the FINANCE module. Relationships to FINANCE are captured in the table FIN COMPONENT.
- as a column in the host table, if it is known that only one number is necessary (this is rarely the case, however)
Go to
- Architectural Principles NULL Data
- Architectural Principles Dates
- Architectural Principles Versioning
- Architectural Principles Vertical Tables
- Architectural Principles Sequence Control
- Architectural Principles Economics and Financial
- Architectural Principles Column Precision
- Architectural Principles Column Field Type
- Architectural Principles Standardized Columns
- Architectural Principles SQL View Definitions
- Architectural Principles Other SQL Definitions
