In Offer Design, create a charge offer and use a recurring charge. For example, to create a monthly fee that's charged in advance, use Monthly Cycle Forward.
In Offer Design, create a recurring charge with a balance impact that credits the amount of an allowance and a balance impact that debits the charge amount. To enable the subscriber to use the minutes, create a usage charge and an allowance discount that credits the usage charge when there's an available allowance.
Yes. In Offer Design, you can create package lists to organize packages according to a type of customer or type of package; for example:
Customers in a particular location, such as Canada
Packages that include promotional discounts offered for a limited time
Yes. When you create a bundle or a package in Offer Design, enable Bill on Purchase. When a customer purchases the bundle, a bill is generated immediately for the purchase fees associated with the bundle.
Note:Only purchase fees are billed on purchase, not usage fees or recurring charges.
In offers, bundles, and packages, use validity period dates and purchase dates. See Configuring validity periods.
No. You can include one of each type of recurring fee in a charge offer; for example, one monthly fee, one annual fee, and so on.
Similarly, you can include only one purchase fee and one cancellation fee.
To include multiple fees of the same type, create multiple charge offers and include them in the same bundle.
In Business Configuration, check whether your changeset has been submitted successfully. Any pricing and financial components that you worked on won't be visible to other applications until the changeset has been submitted successfully.
If there are problems with your components, Business Configuration displays error messages when you validate or submit your changeset. A changeset might fail for a variety of reasons, such as:
You don't have the appropriate permissions to submit changesets. You must have both the DesignCenterAdapterGroup and JDGroup functional roles.
Your components are valid, but an associated subcomponent isn't valid.