Knowledge quiz

It’s time to put what you’ve learned to the test, get 8 questions right to pass this unit.

What is the difference between comparator components and splitter components?

There are two correct answers.

Splitter components are always the leaves of tree branches while comparator components create branches.

Comparator components create branches while splitters join branches again.

From the outbound branches of a comparator component only one branch is executed. When using a splitter component on the other hand, more than one outbound branch is usually executed.

The icons of splitter components have a different color than the ones of comparator components.

What is the purpose of the charging plan?

Choose the correct answer.

It contains a logic to determine the sign of the charged transaction.

It contains a mandatory logic to select the correct external account to charge the fee against. As the account is not known at the time the logic is created, placeholders are used instead. (correct)

The charging plan is the smallest part of a sellable product, that can be used by SAP Subscription Order Management. It is only visible by SAP Subscription Order Management when the charging plan is released.

The charging plan defines the recurrence pattern of recurring fees. It only needs to be defined when recurring fees need to be triggered by the charge.

Which type of pricing component are the leaves of each price plan?

Choose the correct answer.

Comparator

Operator

Function

Splitter

What is the difference between comparator components and splitter components?

There are two correct answers.

Splitter components are always the leaves of tree branches while comparator components create branches.

Comparator components create branches while splitters join branches again.

From the outbound branches of a comparator component only one branch is executed. When using a splitter component on the other hand, more than one outbound branch is usually executed.

The icons of splitter components have a different color than the ones of comparator components.

What kind of counter is required to share the counter between different provider contracts?

Choose the correct answer.

Permanent counter

Persistent counter

Transient counter

Epic counter

To which date is the last activation set during an activation of a contract?

Choose the correct answer.

The last activation date is set to the requested activation date.

The last activation date is set to the system date and time the activation process was finished in SAP Convergent Charging.

To the date and time the contract was created.

The last activation date is set to the date and time the last one-shot rate or recurring rate was triggered. If no rate is triggered during activation the last activation date remains unchanged.

What is the purpose of parameters?

Choose the correct answer.

Parameters allow to temporarily store values calculated in the price plan. Therefore, they are similar to variables.

Parameters can count things.

Parameters can be used to make calculation logic more flexible as they offer ways to configure the logic when a contract is signed.

Parameters are not tied to data types and are thus more flexible.

How do you create a new chargeable item class when SAP Convergent Charging is integrated with SAP Convergent Invoicing?

Choose the correct answer.

By choosing File → New → Chargeable Item Class.

By choosing File → New → Charged Item Class.

By choosing File → New → Consumption Item Mapping.

By choosing File → New → Billable Item Mapping.

The chargeable item class is not created in SAP Convergent Charging by a user. You need to create a Consumption Item Class first in SAP Convergent Invoicing. Once the class is published there, SAP Convergent Charging will create the corresponding chargeable item class automatically.

Why is it often not a good idea to use the charge effective date as the reference date for a recurring rate?

Choose the correct answer.

Because the charge effective date is never part of a time interval.

Because this way the charge will start its individual recurring period when it is activated as part of a contract. This can lead to contracts with different items having asynchronous recurring periods.

Because the charge effective date can be unset, which leads to a runtime error ("No Access") in certain situations.

Because it is a bad design style.