Your customer wants you to restrict the values of Receivables Transaction Type for their three business units. You created three reference data sets for each business unit. However, the user is…

Question

Options

• AThe user is seeing the values defined in the common set. The values should be removed from the
• BReceivables Transaction Types are common across business units.
• CReference Data Sets cannot be used uniquely across business units. They can only be used at the
• DThe user has multiple Business Unit Roles and, therefore, is able to see additional values.

• A
  93% (39)
• B
  2% (1)
• D
  5% (2)

Explanation

Option A is correct because Oracle's reference data architecture includes a special "Common Set" that is automatically visible to all business units, regardless of which custom reference data set is assigned to them. When transaction types exist in the Common Set, they will appear in every business unit's list of values - meaning creating three BU-specific sets doesn't hide the Common Set values; those must be explicitly removed from the Common Set to achieve the desired restriction.

Why the distractors are wrong:

• B is false - Receivables Transaction Types can be restricted by business unit using reference data sets; they are not inherently global.
• C is false - Reference Data Sets are specifically designed to be used uniquely across business units; that is their core purpose.
• D is a distraction - a user's Business Unit Roles control which BUs they can transact in, not which reference data values appear within a given LOV.

Memory tip: Think of the Common Set as a "baseline pool" that every business unit automatically inherits. Creating a custom set adds a layer; it doesn't replace the Common Set. Whenever a restriction isn't working after setting up BU-specific sets, always ask: "Did anyone clean up the Common Set?"

No community discussion yet for this question.