If the data source loads without error, but the data in the database is wrong, check whether the following conditions exist:
You loaded the correct data source.
If so, check the data source again to make sure that it contains the correct values.
There are blank fields in the data source.
You must insert #MI or #MISSING into a data field that has no value. Otherwise, the data source may not load correctly. To replace a blank field with #MI or #MISSING using a rules file, see Placing Text in Empty Fields.
The data source is formatted correctly.
The data is clean. For example, as it processes the data source, Essbase recognizes member names and knows the dimensions they belong to. If a data source record inadvertently includes a member from a dimension for which there is a member named in the header record, the new member name replaces the header record member for that dimension. In the following example data source, Essbase recognizes Florida as a member of the Market dimension. The values in the last four records are interpreted as Florida values instead of Texas values.
Jan Actual Texas Sales "100-10" 51.7 "100-20" 102.5 "100-20" 335.0 Florida 96.7 "200-20" 276.0 "200-20" 113.1 "200-10" 167.0
There are any implicitly shared members (when a parent and child share the same data value) of which you were unaware.
This situation occurs if a parent has only one child or only one child rolls up into the parent.
You added incoming data to existing data instead of replacing incoming data with existing data.
You selected or rejected any records that you did not intend to select or reject.
See Selecting Records and Rejecting Records.
The sign is reversed (for example, a minus sign instead of a plus sign) and whether you performed sign flips on any UDAs.
See Flipping Field Signs.
You cleared data combinations that you did not intend to clear.
You scaled the incoming values incorrectly.
See Scaling Data Values.
All member and alias names are fewer than 79 characters long.
You can check data by exporting it, by running a report on it, or by using a spreadsheet. If exporting or running reports, see Developing Report Scripts and Using ESSCMD. If using a spreadsheet, see Oracle Essbase Spreadsheet Add-in User's Guide. |