Which data objects are distributed to CC along with the SOM product during design time?

Question

Options

• ACharge plan
• BParameter
• CProduct name
• DMapping table

• A
  10% (5)
• B
  8% (4)
• C
  4% (2)
• D
  78% (39)

Explanation

Mapping tables are distributed to CC (Converged Charging/Charging Center) alongside the SOM product during design time because they define how the SOM product's attributes and parameters correspond to charging configurations - without this translation layer, CC cannot properly interpret or apply the product's logic.

• Charge plan (A) is incorrect because charge plans are managed and maintained within the charging system itself, not pushed out from SOM during design-time distribution.
• Parameter (B) is incorrect because parameters belong to the product's runtime or instance-level configuration, not a design-time distribution artifact.
• Product name (C) is incorrect because the product name is simply a descriptive label and does not constitute a functional data object required by CC to process charging.

Memory tip: Think of the mapping table as the "translator" - SOM speaks in product terms, CC speaks in charging terms, and the mapping table is the dictionary sent at design time so they can communicate. If no translator is distributed, CC has no way to understand the product.

No community discussion yet for this question.