Professional Documents
Culture Documents
1. Will have the instruction for multiple choice questions? Like – choose correct two answers?YES
2. Can we skip the questions in the middle to come back and answer at the end for skipped
questions? YES, You’ll have FLAG option to skip & come back
3. How does the answer process? Save and submit or submit only/ can we change / correct the
answer when we do the revision at the end? Save(Click NEXT) & Submit for each
block & then finally at the end of 80 questions, SUBMIT YOUR SCORE.
4. Hope we do not have negative mark? but all multiple answer has not been selected will be
considered as negative? Please confirm? NO NEGATIVE MARKINGS. IF OUT OF 3
CORRECT OPTIONS, YOU SELECTED ONLY 2, IT’LL BE CONSIDERED
INCORRECT.
5. Business Content topics? Is it scenario based? YES
6. Will it be possible to have a question from’ Direct extraction’ DXC? YES
7. Will it be possible to have question from BW direct connection with HANA – BW 7.3? Is it from
SP04? YES & ITS FROM SP03 ONWARDS.
8. What kind of questions may expect from optimization topics? Will it be referring what type of
optimization? Modeling or reporting optimization? OPTIMIZATION FROM
REPLICATION, DATA MODELLING & REPORTING.
Technical Question:
Param.th.2009@gmail.com
this connection? DB CONNECTION IS THE SQL DBC & WE DO THE SETTINGS
INSIDE LTR OF SLT.
1) I created an analytic view. I have added some columns, calculated and restricted columns to my
output. Then I went back to my "Logical Join" and clicked on "Auto match" function to determine which is
an attribute and measure. How does the system know which one is an attribute and which one is a
measure? Does it have any relation to the DD02L and DD02T tables?
Logical join- Auto match function will ONLY take the datatypes of the selected
fields & match it as Attribute & Measure.
(CHAR/VARCHAR/NCHAR/NVARCHAR)->Attribute
(DECIMAL/INTEGER/SMALLINT etc) ->Measure
On the other hand, the DD02L & DD02T are the Trigger tables for SLT.
2) During data replication (either SLT or BODS), how does the system know which table should be a row
store or a column store? Is there any specific criteria that is checked before the meta data of the tables is
loaded from the source system?
By default, during dataload, all the application tables via replicators will be
auto-converted to Column based tables in HANA.
Only the system settings tables will be row-based tables.
3) I was looking at joining some tables using the various Cardinality options available. What exactly does
1:1, 1:n, n:1 or n:n mean in analytic view? I kind of have an idea but it will be clear if there is an example.
I know it is difficult to type but if you can send me the link where I can find the info, that will be great.
Different cardinalities exist in HANA namely 1:1, 1:n, n:1, n:n
Examples:
1:1 used during text-joins
1:n used if 1 masterdata value from LEFT TABLE/VIEW need to look up to
multiple values in RIGHT TABLE/VIEW
n:1 used in reverse of the above
n:n NOT RECOMMENDED due to high level of sub-joins.
4) During the creation of calculation view, "Schema for Conversion" is restricted to certain schemas. Is it
determined by security authorization or some configuration setting?
Schema for Conversion will POINT to the schema which has the conversion
factor table eg. (Foreign Exchange factor for Currency conversion). Hence, if we
use currency conversion in that Calc_view, it'll internal refer that schema for
conversion purposes.
Param.th.2009@gmail.com