In a company XYZ, the HR User wants to store the Long Service Bonus amount based on the number of years of service. For 0 to 5 years of service, the value is 40,000 USD; for 6 to 7 years, the value…

Question

Options

• ACreate a User Defined Table with the Match Type set as Match and Key Unit of Measure as
• BCreate a User Defined Table with the Match Type set as Match and Key Unit of Measure as Text.
• CCreate a User Defined Table with the Match Type set as Range and Key Unit of Measure as
• DCreate a User Defined Table with the Match Type set as Range and Key Unit of Measure as Text.
• ECreate a User Defined Table with the Match Type set as Range and Key Unit of Measure as

• A
  3% (1)
• B
  3% (1)
• C
  6% (2)
• D
  75% (24)
• E
  13% (4)

Explanation

Option D is correct because the bonus amounts are tied to ranges of years (e.g., 0–5, 6–7), not exact values, so the Match Type must be Range - this allows the system to look up a value when the input falls anywhere within a defined interval rather than matching a single specific number. The Key Unit of Measure is set to Text because, in this type of UDT (common in SAP SuccessFactors), range boundaries are stored and interpreted as text entries even when they represent numeric spans.

Options A, B (Match type) are wrong because "Match" requires an exact key match - a specific year like "7" - and cannot handle open-ended ranges like "6 to 7 years"; it would miss any year not explicitly listed. Options C and E are wrong because, while they correctly use Range, they pair it with a non-Text Key Unit of Measure (likely Number), which is not the correct configuration for range-based lookups in this system - Text is required for the range key field to function properly.

Memory tip: Think "R-T" - Ranges need Text. Whenever bonus tiers span a band of values (not a single point), reach for Range + Text. If you're matching one exact value (like a specific job code), that's when Match applies.

No community discussion yet for this question.