...
To load ad-hoc source data the following steps should be followed:
Create an ad-hoc data source definitionentry.
Define the ad-hoc data source. There are three ad-hoc data source types; csv source file, SQL query, either uploaded to the staging cube from Excel, or copy-and-pasted directly into the staging cube.
Map the data source to the target cube.
Restrict the source data.
Load the data to the target cube.
...
Pick the target cube from the drop-down list. The ad-hoc data is needs to be aligned with the target cube using fixed dimensional references and or the columns from the ad-hoc data source. Fixed dimensional references is a single leaf element in the dimension that is a member of the target cube. The ad-hoc source data will include dimensional references and values that need to load into the target cube. One or more columns can include data that needs to be mapped to the target cube.
...
In the following walk through we are going to map a csv file to be loaded to the FIN General Ledger TB cube to load the statistical data for 2022. The columns of the sample ad-hoc source data are as follows:
Column | Sample Data |
|---|---|
Period | 20212022-M01 |
Company | 1000 |
BSEG1 (Cost Center) | NA FIN BSEG 1 |
BSEG2 (Customer) | 110001 |
BSEG3 (Product) | 400103 |
BSEG4 (Channel) | 111 |
Account | Quantity Consolidated |
Value | -1000.00 |
...
Based on the mapping provided the data will be loaded to the target cube. The ad-hoc data can be restricted to load to nominated elements listed as the valid elements for the dimension. Each element is separated by the Element Separator set in the settings. If the restricting element is a consolidated element, then the leaf elements under the restricting consolidated element are the restricted elements. Data cannot be loaded to consolidated elements. If there are no restrictions for the dimension, then all elements can be loaded from the ad-hoc data source. See Adding elements from the ad-hoc data source.
...
When loading the ad-hoc data any records that are not valid are listed as a Rejected RecordRecords. The Rejected Records should be reviewed, and the valid records adjusted as required.
...
Before the data is loaded the data in the cube is cleared. The portion of the cube that is cleared is based on the fixed dimensional references and the restricted elements. If there are no restricting elements than , then the data against all elements in the dimension will be cleared with respect to the restriction of the other dimension. If the restricted element is at a consolidated element, then the data against the leaf elements under the consolidated element in the dimension will be cleared with respected the restrictions in the other dimensions.
...
Elements will automatically be added if the dimension is the Operational CoA (FIN OCoA) or a Business Segment dimension (FIN BSEG 1, FIN BSEG 2, FIN BSEG 3, FIN BSEG 4) that is mapped to the ad-hoc data source and has no restrictions. If For the dimension is the Operational CoA (FIN OCoA) , new the list of valid elements must be Total GL Accounts. New elements are first added to the Total GL Accounts. For the Business Segments there must be no restrictions. New elements are first added to the Total FIN BSEG x consolidation.
After the ad-hoc data has been load the new accounts must be mapped to the Management Trial Balance, see Chart of Accounts Management. If the dimension is a Business Segment, new elements are first added to the Total FIN BSEG x consolidation. After the ad-hoc data has been loaded the new New business segments must be mapped to the business segment reporting structures, see Setup and Maintenance of the Business Segments.
...