Data Mart Manager
The Data Mart Manager (OLAPDBM) file stores information about each data mart that has been defined by IA10.1 (Data Mart Manager) program.
REFERENCED BY
ACDL.1 | AMDL.1 | CBOP.1 | HC10.1 | HCDL.1 | HCHP.1 |
IA05.1 | IA05.3 | IA10.1 | IA10.2 | IA11.2 | IA120 |
IA15.1 | IA15.4 | IA150 | IA20.1 | IAAP.1 | IANM.1 |
IASV.1 | IASV.2 | GLOP.1 | POA3.1 | WADL.1 | WAOP.1 |
FIELD NAME | DESCRIPTION/VALID VALUES | UPDATED BY | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ODB-DATA-MART-NAME Element: Data Mart Name | Alpha 20 (Lower Case) This field contains the name of the data mart. |
|
||||||||||||
ODB-DESCRIPTION Element: Description | Alpha 30 (Lower Case) The Description field contains a description of the data mart. |
|
||||||||||||
ODB-APPLIC-TYPE Data Mart Type | Alpha 3 The Application Type file stores the names of the Lawson applications that can be requested to supply information to the OLAP database. The Lawson applications that are currently OLAP-ready are: FIN = Financial Analyzer FND = Daily Financial Analyzer SA = Sales Analyzer CX = Case Cart Analyzer PO = Purchasing Analyzer WO = Work Order Analyzer |
|
||||||||||||
ODB-SERVER-NAME Element: Server Name | Alpha 40 (Lower Case) The Server Name field contains the IP address of the server to which you are connecting. You can also specify a name that has been associated with the server (DNS name). |
|
||||||||||||
ODB-DIM-BUILD-DTE Element: Dimension Build Date | Numeric 8 (yyyymmdd) The Dimension Build Date field contains the most recent date that this dimension was updated in the outline. The date format used is YYYYMMDD. |
|
||||||||||||
ODB-DIM-BUILD-TME Element: Dimension Build Time | Numeric 6 (hhmmss) The Dimension Build Time field contains the most recent time that this dimension was updated in the outline. The time format used is HHMMSS. |
|
||||||||||||
ODB-DATA-BUILD-DTE Element: Data Load Date | Numeric 8 (yyyymmdd) The Data Load Date field contains the most recent date that the OLAP data mart was populated with data values. The date format used is YYYYMMDD. |
|
||||||||||||
ODB-DATA-BUILD-TME Element: Data Load Time | Numeric 6 (hhmmss) The Data Load Time field contains the most recent time that the OLAP data mart was populated with data values. The time format used is HHMMSS. |
|
||||||||||||
ODB-REQ-DIM-REBLD Required Dimension Rebuild | Alpha 1 The value in the Required Dimension Rebuild field is set by the system. The value is based on whether changes that require the dimensions to be rebuilt have been made to the data mart. Valid values are: Y = Yes N = No; Default value. |
|
||||||||||||
ODB-REQ-DATA-REBLD Element: Required Data Reload | Alpha 1 The Required Data Reload field is set by the system. The setting is based on whether changes that require the data values to be reloaded have been made to the data mart. Valid values are: Y = Yes N = No; Default value. |
|
||||||||||||
ODB-LOCK-OPTION Element: Lock Option | Alpha 1 The Lock Option field provides additional security by preventing changes to the data mart definition, even if the user tries to initiate an outline build or a data load. The operation of this field depends on the user's security privileges. Value values are: Y = Yes N = No; Default value. |
|
||||||||||||
ODB-PROCESSING Element: Processing | Alpha 1 The Processing field shows the current status of the data mart. It provides a locking mechanism to prevent updates when data is being loaded to the data mart. Value values are: ~ = No data is being processed M = Outline build in process D = Data load in process C = Data mart calculation in process " " = Not Processing L = Process Lawson Data A = Process MSOLAP F = FTP Data |
|
||||||||||||
ODB-AUTO-REBUILD Element: Auto Rebuild | Alpha 1 The Auto Rebuild field determines whether the data mart should be rebuilt if dimensions or data values have changed. If an incremental data load is requested, this field uses the values in the Required Dimension Rebuild and Required Data Reload fields to determine if the data mart should be reloaded. Set this field to Y if all data for a complete load is still available. Valid values are: Y = Yes N = N; Default value. |
|
||||||||||||
ODB-ERROR-LOG-NBR Element: Error Log Number | Numeric 3 The Error Log Number field displays the error message number found during the outline build or data mart load. |
|
||||||||||||
ODB-LAST-DIM-SEQ Last Dimension Sequence Number | Numeric 4 The Last Dimension Sequence Number field contains the sequence number of the last dimension in the outline. The number in this field determines the number of the next dimension that is added to the outline. |
|
||||||||||||
ODB-STAGE-APP-NAME Staging Application Name | Alpha 8 (Lower Case) The Stage Application Name field contains the name of the application that is temporarily created when the data mart staging option is set. Staging a data mart lets users work with the data mart while data is being loaded. This name can contain up to 8 characters of any kind. |
|
||||||||||||
ODB-ADDT-SOURCES External Data Sources Exist | Alpha 1 The External Data Sources Exists field determines whether external data sources are used to update the data mart. A value of Y (Yes) in this field indicates that external data sources exist, thereby preventing the administrator from clearing the data mart prior to updating it. Valid values are: Y = Yes. External data sources exist. N = No; Default value. |
|
||||||||||||
ODB-DATA-TARGET Element: Data Target | Alpha 1 1 = Hyperion Essbase Server 2 = Star Schema Format |
|
||||||||||||
ODB-ARBOR-PATH Element: Arbor Path | Alpha 100 (Lower Case) The Arbor Path field contains the name of the directory where all CSV output files are stored. |
|
||||||||||||
ODB-DTA-DRILL-PATH Element: Dta Drill Path | Alpha 100 (Lower Case) |
|
||||||||||||
ODB-APPLIC-NAME Element: Applic Name | Alpha 8 (Lower Case) The Application Name is the name of the application that describes the database names it contains. This user-defined name can contain up to eight characters. The first letter of the name must be capitalized. |
|
||||||||||||
ODB-DATABASE-NAME Element: Database Name | Alpha 8 (Lower Case) The Database Name is the name of the database that is stored within the OLAP application. Each application may contain more than one database. This user-defined name can contain up to eight characters. The first letter of the name must be capitalized. |
|
||||||||||||
ODB-ACTIVE-STATUS Element: Active Status | Alpha 1 The status of the account. If Inactive, no posting can be done to the account. A = Active I = Inactive |
|
||||||||||||
ODB-SECURITY-ON Element: Security On | Alpha 1 This field indicates whether the budget is securing individuals from access. Y = Yes N = No |
|
||||||||||||
ODB-MART-CREATOR Element: Mart Creator | Alpha 20 (Lower Case) |
|
||||||||||||
ODB-DATABASE-SPACE Element: Database Space | Alpha 25 (Lower Case) |
|
||||||||||||
ODB-CREATED-GEN Element: Created Gen | Alpha 1 Y = Yes N = No " " = No |
|
||||||||||||
ODB-TABLE-CHANGE Element: Table Change | Alpha 1 |
|
||||||||||||
ODB-FACT-TBL-NAME Element: Fact Tbl Name | Alpha 50 (Lower Case) |
|
||||||||||||
ODB-NBR-COLUMNS Element: Nbr Columns | Numeric 3 |
|
||||||||||||
ODB-OLAP-TYPE Element: Olap Type | Alpha 1 X = XML OUTPUT C = CSV OUTPUT |
|
||||||||||||
ODB-DRILL-ENABLED Element: Drill Enabled | Alpha 1 This field indicates whether drill around functionality should be enabled for this data mart. Y = Yes N = No |
|
||||||||||||
ODB-SERVICE-OPTION Element: Service Option | Alpha 1 This flag determines whether the data mart will be built by an internal server or a service provider. Y = Yes N = No |
|
||||||||||||
ODB-CONVERTED Element: Converted | Alpha 1 " " = Requires Conversion N = Does Not Require Conversion |
|
||||||||||||
ODB-OLAP-STORAGE Element: Olap Storage | Alpha 1 This determines the data storage that will be utilized for the data mart cube. The options are Molap (multidimensional), Rolap (relational), or Holap (hybrid of relational and multidimensional). M = Molap R = Rolap H = Holap |
|
||||||||||||
ODB-OLAP-AGGR-OPT Element: Olap Aggr Opt | Alpha 1 Olap aggregation option: perform aggregations until the OLAP-AGG-LIMIT is hit. S = Storage P = Performance |
|
||||||||||||
ODB-OLAP-AGGR-LIMT Element: Olap Aggr Limt | Alpha 10 Olap aggregation limit: max storage size or performance percentage in which to perform aggregations. This field and the OLAP-AGGR-OPT are concatenated together to describe how aggregation should function. |
|
||||||||||||
ODB-OBJ-ID-PREFIX Element: Obj Id Prefix | Numeric 3 |
|
||||||||||||
ODB-OBJ-ID-SUFFIX Element: Obj Id Suffix | Numeric 9 |
|
||||||||||||
ODB-ENABLE-XML Element: Enable Xml | Alpha 1 " " = Destination Default A = XML Output Active X = XML Output Only |
|
||||||||||||
ODB-NUMERIC-ID Element: Numeric Id | Numeric 3 |
|
NAME | KEY FIELDS | DESCRIPTION / SUBSET CONDITION | USED IN | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ODBSET1 |
DATA-MART-NAME |
|
|||||||||||
ODBSET2 |
APPLIC-TYPE DATA-MART-NAME |
|
| ||||||||||
ODBSET3 |
APPLIC-NAME DATABASE-NAME DATA-MART-NAME |
|
| ||||||||||
ODBSET4 |
DATABASE-SPACE DATA-MART-NAME |
|
| ||||||||||
ODBSET5 |
DATABASE-SPACE FACT-TBL-NAME DATA-MART-NAME |
|
RELATION NAME |
RELATED FILE | INTEGRITY RULES / FIELD MATCH | |||
---|---|---|---|---|---|
Applictype | APPLICTYPE |
Required
| |||
Rolapdbs | ROLAPDBS |
Not Required
|
RELATION NAME |
RELATED FILE | INTEGRITY RULES / FIELD MATCH | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Aliastable | ALIASTABLE |
| |||||||||
Datasource | DATASOURCE |
| |||||||||
Dimdatarel | DIMDATAREL |
| |||||||||
Member | MEMBER |
| |||||||||
Olapdim | OLAPDIM |
| |||||||||
Olapdim 3 | OLAPDIM |
| |||||||||
Olapprof | OLAPPROF |
| |||||||||
Olapuda | OLAPUDA |
| |||||||||
Profdatrel | PROFDATREL |
|
All trademarks and registered trademarks are the property of their
respective owners.