Q: 13
You want to create a query that includes information about an employee's current job, as well as
information such as name and date of birth. How do you do this? Note: There are 2 correct answers
to this question.
Options
Discussion
I think A and B, seen similar in practice questions. Check the official SAP guide and hands-on labs to confirm.
Its A and B, since User/Employee tables in C and D are more for ID objects, not ideal for pulling current job data cleanly. Tricky if you missed how the schemas relate.
D imo. C is tempting but User/Employee Info doesn't give you both personal and job fields cleanly like A and B.
A and B tbh, that's what actually works for current job info in Story reports.
Pretty sure C should count since Employee Information table also gives personal details after expanding from Employment. Isn't the trap here just mixing up historic vs current job records?
B . Starting from Employment and then going into Person seems logical since you want both job and personal details. I always use the Employee Information table for this type of thing, so C makes sense to me too. Not 100% sure what would break with that method unless there's a limitation on joins. Open to corrections though.
I saw this style on a practice test, picked C. The Employee Information table can pull personal fields after starting from Employment. Might be missing something subtle about the schema joins but I thought it worked.
How do you guys distinguish between starting from Person vs Employment category in these queries? I always mix up which path is cleaner for personal vs job info. Does it matter for current vs historical jobs or just a best practice thing?
A/B. Had something like this in a mock, Person and Employment categories both get you the current job plus personal info.
I don't think C or D fit since User/Employee info doesn't link back to current job fields cleanly. A and B.
Be respectful. No spam.
