Using Pricing Macros and Understanding the Replication of Prices/

1.

Which data types must be used for the parameters when using price tables for automatic condition replication from SAP Subscription Order Management?

There are two correct answers.

String

Number

Date

Price Key

Multivalued String

Multivalued Number

Boolean

Mapping Table ID

Price Table ID

CHAR

VARCHAR

2.

What options are there to call a macro from a price plan?

There are two correct answers.

Call the macro as a function. This makes calling the macro the last component of the tree branch.

Call the macro as a comparator component. This will branch the tree into 2 till n outbound branches.

Call the macro as a splitter component. This makes the tree logic branch into several outbound branches depending on the type of comparator chosen. It is possible that more than one outbound branch is executed in this case!

Call the macro as an operator component.

Macros are not called with components at all. They are implicitly and automatically executed by SAP Convergent Charging each time the activation scheduler runs. When an external scheduler is used, a set of parameters passed in the activation API call can be used to control which macros are executed.

3.

What are the purposes of pricing macros?

There are two correct answers.

They increase rating speed.

They help to reduce redundancies in price plans.

They allow you to execute the custom code provided as Java libraries (.jar files).

They allow a charge to access price plan logics of other charges.

They allow merging the control flow of a price plan that has branched several times back into one execution path / branch.

4.

What do you have to do to add an additional rating context property (also called input property) to a macro that was already saved to the database?

Choose the correct answer.

Open the macro and add the new rating context property.

It is not possible. The best you can do is to open the macro as a copy, provide a unique name to the new macro and add the additional rating context property. After saving the new macro, all references to the old macro must be updated to reference the new one instead.

The core tool of SAP Convergent Charging doesn’t allow this. Ask for access to the SAP Convergent Charging and make the necessary modifications there.

Knowledge quiz

Which data types must be used for the parameters when using price tables for automatic condition replication from SAP Subscription Order Management?

What options are there to call a macro from a price plan?

What are the purposes of pricing macros?

What do you have to do to add an additional rating context property (also called input property) to a macro that was already saved to the database?