Q: 12
What must be done to ensure that you can use a custom generic (MDF) object for Employee Self-
Service? Note: There are 2 correct answers to this question.
Options
Discussion
C/D? Had something like this in a mock, C and D both matched ESS config steps.
D , C and D are needed for ESS objects specifically. Pretty sure that's what SAP expects here.
C/D? Official SAP guide and practice tests say config UI plus externalCode as User is the combo for ESS.
A and C for me. I always thought config UI is required for ESS so users see the object, and setting externalName to User feels like it points the record to an employee for self-service. Not totally sure if it's really supposed to be externalCode instead though. Anyone else pick A?
C vs D. Some say A looks right since externalName seems user-related, but it's actually the externalCode that needs Data Type = User to link ESS records to the employee. Config UI (C) is definitely required so users can interact with the object. Pretty sure A is a common distractor here. If anyone's implemented this differently, let me know.
Maybe A and C. I remember externalName with Data Type User being required, not sure if D is a trap.
C and D imo. For Employee Self-Service, you need to link the object directly to the user so externalCode as User (D) is a must. The Config UI (C) gives users an interface to manage the object. A trips people up because externalName isn't used for this linkage in ESS cases. Correct me if I've missed something.
I don’t think it’s A. C and D.
Saw a very similar question in recent exam reports, it's C and D.
C/D? I get why people pick A, but for Employee Self-Service the system needs to know which record belongs to each employee, so externalCode as User (D) is essential. Configuration UI (C) is what lets employees access and edit those records. Pretty sure B is a distractor-Valid When association isn't mandatory for ESS here. Anyone disagree?
Be respectful. No spam.