What does a charged item class define?

Question

Options

• AThe validity period of a charge
• BThe output format for the downstream system
• CThe frequency with which items are transferred downstream
• DThe scope of a charge

• A
  3% (1)
• B
  92% (36)
• D
  5% (2)

Explanation

Option B is correct because a charged item class defines how charge data is structured and formatted when passed to a downstream system - it acts as a template controlling what fields are included and how they appear in the output. This is distinct from when charges are valid, how often they're sent, or what they apply to.

Why the distractors are wrong:

• A (validity period) - validity periods are controlled by date ranges or pricing conditions, not the item class itself.
• C (transfer frequency) - transfer frequency is a scheduling/batch configuration concern, not something defined by the item class.
• D (scope of a charge) - scope (what a charge applies to) is determined by charge assignment rules or pricing structures, not the item class.

Memory tip: Think of "class" like a CSS class - it controls presentation/format, not timing or scope. If you see "item class," think "output template."

No community discussion yet for this question.