Which object is created during design time after you create a billable item mapping in SAP Convergent Charging?

Question

Options

• ACharged item
• BBillable item
• CCharged Item class
• DChargeable item class

• A
  5% (1)
• C
  91% (20)
• D
  5% (1)

Explanation

When you create a billable item mapping in SAP Convergent Charging at design time, the system automatically generates a Charged Item Class - a design-time template object that defines the structure for how billable items will be converted into charged items during the billing process. Option A (Charged item) is wrong because charged items are runtime objects - actual instances produced during processing, not design-time constructs. Option B (Billable item) is wrong because billable items are inputs to the charging process (usage events or consumables), not outputs of a mapping creation. Option D (Chargeable item class) is a plausible distractor but is not the object generated by a billable item mapping - it conflates the input concept ("chargeable") with the correct output concept ("charged").

Memory tip: In SAP CC, design-time objects end in "Class" (they're templates), and the mapping goes from billable → charged - so what gets created is a Charged Item Class, not a chargeable one.

No community discussion yet for this question.