Oracle Communications Pricing Design Center Release Notes

[1] Oracle® Communications Pricing Design CenterRelease Notes

Release 11.1

E26181-11

March 2018

Oracle Communications Pricing Design Center Release Notes, Release 11.1

E26181-11

Copyright © 2011, 2018, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

iii

Contents

Preface ................................................................................................................................................................ vii

Audience...................................................................................................................................................... viiDownloading Oracle Communications Documentation ..................................................................... viiDocumentation Accessibility .................................................................................................................... viiDocument Revision History ..................................................................................................................... vii

1 New Features

Dynamic Quota Configuration is Now Supported in PDC (Patch Set 12).................................... 1-1Configuring Dynamic Quota Selectors ........................................................................................... 1-5

Support for Configuring Policy Specifications (Patch Set 12) ........................................................ 1-5Configuring Policy Specifications by Using XML Files................................................................ 1-7Configuring Policy Specifications by Using the PDC User Interface ......................................... 1-7

Specifying General Information for a Policy Specification ................................................... 1-7Creating Policy Labels................................................................................................................ 1-8Creating Counter Policies .......................................................................................................... 1-8Adding Counter Ranges ............................................................................................................ 1-8Modifying Policy Specifications ............................................................................................... 1-9Modifying Policy Labels ............................................................................................................ 1-9Modifying Counter Policies....................................................................................................... 1-9Modifying Counter Ranges .................................................................................................... 1-10Deleting Policy Specifications ................................................................................................ 1-10Deleting Counter Policies ....................................................................................................... 1-10Deleting Counter Ranges ........................................................................................................ 1-11

PDC Now Enables you to Export Components Mastered in BRM (Patch Set 12) .................... 1-11Support for NOT Operator in Selectors (Patch Set 12) .................................................................. 1-12Support for Reordering Discount and ChargeShare Rules (Patch Set 12) ................................. 1-13

Reordering Discount Rules............................................................................................................ 1-13Reordering ChargeShare Rules ..................................................................................................... 1-13

Importing PDC Configurations by Ignoring Internal IDs (Patch Set 11) .................................. 1-14Support for Adding Multiple Currencies in the PDC UI (Patch Set 11) .................................... 1-14

Adding Additional Currencies to a Charge ................................................................................ 1-15Removing Currencies from a Charge........................................................................................... 1-15

Support for Aggregation of System-Level ChargeShare Offers (Patch Set 11)......................... 1-16Support for Prorating Charges in Charge Selectors (Patch Set 11) .............................................. 1-16Support for Renaming and Removing Discount Rule Names (Patch Set 11)............................ 1-17

iv

Creating a Discount Rule ............................................................................................................... 1-17Renaming a Discount Rule ............................................................................................................ 1-17Deleting a Discount Rule ............................................................................................................... 1-17

Additional Option for Setting End of Validity for Noncurrency Credit Balance Impacts (Patch Set 10)....................................................................................................................................................... 1-18Additional Options to Configure Discount Filters (Patch Set 10) ............................................... 1-18Dynamic Pricing Can Now Be Configured By Using the PDC UI (Patch Set 10)..................... 1-19PDC Now Enables You to Delete Old Versions of PDC Components (Patch Set 10) ............. 1-20PDC Now Enables you to Export Only Successfully Promoted and Transformed Components (Patch Set 10) .......................................................................................................................................... 1-20Pricing Tiers for Single RUM Graph With Selective RUMs Can Now be Configured by Using the PDC UI (Patch Set 10) .................................................................................................................... 1-21RUMs Can Now Be Configured for Price Overrides in Single RUM graphs (Patch Set 10) .. 1-22Additional Purchase Option for Bundles (Patch Set 9) ................................................................. 1-23Additional Charging Result Attributes Can Be Used for Item Assignment (Patch Set 9)...... 1-24Dynamic Pricing is Now Supported in PDC (Patch Set 9) ............................................................ 1-25Migrate Pricing Data Selectively from BRM to PDC (Patch Set 9).............................................. 1-26PDC Now Enables You to Publish PDC Components to Target Engines (Patch Set 9) .......... 1-28Support to Skip Errors and Continue Pricing Objects Migration (Patch Set 9)........................ 1-29Support for NOT Operator in Discount Filters (Patch Set 9) ....................................................... 1-29Support for Single Currency Graph (Patch Set 9) ........................................................................... 1-31Support for Single RUM Graph (Patch Set 9).................................................................................. 1-33PDC Now Allows You to Create Account-Level Charge Offers, Chargeshare Offers and Discount Offers for ECE (Patch Set 8) ............................................................................................... 1-34Simplified Process to Configure New Services and Events (Patch Set 7) .................................. 1-34Migrating Pricing Data to a BRM System with PDC and ECE (Patch Set 7) ............................. 1-34Truncation and Rounding in Discount Expressions (Patch Set 7)............................................... 1-34Minimum Charges, Price Overrides, Effective Periods, and Relative Date Ranges (Patch Set 7).... 1-34Select Bill Items Based on Business Profiles (Patch Set 7)............................................................ 1-35Charge, Discount, APN, and USC Selectors Supported by ECE (Patch Set 7) .......................... 1-35Changesets for Setup Components (Patch Set 7) ............................................................................ 1-35Effective Periods for Conditional Balance Impacts (Patch Set 7) ................................................ 1-35PDC Now Allows You to Configure Item Type Selectors (Patch Set 6) ..................................... 1-35Special Pricing for Members of Closed user Groups (Patch Set 6) ............................................. 1-35PDC Now Allows You to Configure Conditional Balance Impacts (Patch Set 5)..................... 1-36Balance Elements Can Now Be Created in the PDC UI (Patch Set 5) ......................................... 1-36PDC Now Provides a Migration Utility for Migrating BRM Pricing Data to PDC (Patch Set 4) ..... 1-36Discounts Can Now Be Filtered Based on the Pricing Name (Patch Set 4)................................ 1-36Discounts Can Now Be Filtered Based on the Impact Category in the Charge Selector (Patch Set 4)................................................................................................................................................................ 1-36PDC Now Displays Offers by Service (Patch Set 4) ....................................................................... 1-36PDC Now Allows You to Configure Some of the Selectors Without Specifying a Service or an Event (Patch Set 4) ................................................................................................................................. 1-37PDC Now Provides a Web Service to Create or Update Pricing Components (Patch Set 4) .. 1-37Regular Expressions Can Now Be Used for G/L IDs in Discount Filters (Patch Set 4) ........... 1-37Complex Expressions Are Supported in Discount/Chargeshare Triggers (Patch Set 3) ......... 1-37

v

Multiple Balance Elements and G/L IDs Are Supported in Discount/Chargeshare Filters (Patch Set 3)......................................................................................................................................................... 1-37Multiple RUMs Are Supported in Charge Selectors (Patch Set 3) .............................................. 1-38Customer Segment and Type Can Be Specified in the Package List (Patch Set 3)................... 1-38PDC Now Displays Successfully Submitted Changesets (Patch Set 3)...................................... 1-38

2 Utility Changes

New Utilities ............................................................................................................................................. 2-1Changed Utilities...................................................................................................................................... 2-1

3 Known Problems

Fixed Known Problems ........................................................................................................................... 3-1Known Problems ...................................................................................................................................... 3-1

Migration Fails Even When the Migration Process is Enabled to Skip Errors.......................... 3-2You Are Not Warned to Save Your Changes................................................................................. 3-2

vi

vii

Preface

This guide includes information about Oracle Communications Pricing Design Center (PDC) patch sets. Detailed information on the patch set features for PDC 11.1 Patch Set 3 through PDC 11.1 Patch Set 8 is included in the PDC documentation.

Detailed information on the patch set features for PDC 11.1 Patch Set 9 through PDC 11.1 Patch Set 12 is included in this guide.

AudienceThis document is intended for all PDC users.

Downloading Oracle Communications Documentation Product documentation is located on Oracle Help Center:

http://www.oracle.com/technetwork/index.html

Additional Oracle Communications documentation is available from the Oracle software delivery Web site:

http://edelivery.oracle.com

Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle SupportOracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Document Revision HistoryThe following table lists the revision history for this guide:

Version Date Description

E26181-03 September 2012 Initial release.

Information about Patch Set 2 features, which are identified by "(Patch Set 2)", is added.

E26181-04 May 2014 Information about Patch Set 3 through Patch Set 5 features, which are identified by "(Patch Set 3)", "(Patch Set 4)", and "(Patch Set 5)" is added.

E26181-05 November 2014 Information about Patch Set 6 features, which are identified by "(Patch Set 6)", is added.

E26181-06 June 2015 Information about Patch Set 7 features, which are identified by "(Patch Set 7)", is added.

E26181-07 April 2016 Information about Patch Set 8 features, which are identified by "(Patch Set 8)", is added.

E26181-08 April 2017 Information about Patch Set 9 features, which are identified by "(Patch Set 9)", is added.

E26181-09 August 2017 Information about Patch Set 10 features, which are identified by "(Patch Set 10)", is added.

E26181-10 December 2017 Information about Patch Set 11 features, which are identified by "(Patch Set 11)", is added.

E26181-11 March 2018 Information about Patch Set 12 features, which are identified by "(Patch Set 12)", is added.

viii

1

New Features 1-1

1New Features

This chapter provides an overview of the various feature enhancements introduced in Oracle Communications Pricing Design Center (PDC) 11.1 Patch Set 3 through PDC 11.1 Patch Set 12.

In addition, provides the detailed information on the patch set features for PDC 11.1 Patch Set 9 through PDC 11.1 Patch Set 12.

Dynamic Quota Configuration is Now Supported in PDC (Patch Set 12)

Note: Dynamic Quota Configuration can be used only in Oracle Communications Billing and Revenue Management Elastic Charging Engine (ECE).

Dynamic quota allows you to allocate the available quota dynamically for each parallel session of a subscriber based on the rules you configure. This enables the subscribers to run concurrent online charging sessions effortlessly. This also enables you to optimize the network usage effectively. For more information on dynamic quota, see ECE Release Notes.

You can now define the rules for determining the dynamic quota allocation by configuring dynamic quota selectors in PDC. The rules can reference any of, or a combination of, the event, service, and customer attributes, and profile attribute specifications. You can configure the dynamic quota selector for each service and event combination.

ECE evaluates the rules defined in the dynamic quota selector at run time to derive the quota to be allocated for a session and the quota attributes, such as quota holding time (QHT), volume quota threshold (VQT), and quota validity time (VT). Dynamic quotas change in real time based on the dynamic quota selector rules as ECE grants and redistributes the quotas.

You configure dynamic quota selectors by importing the rules in XML files by using the ImportExportPricing utility. You can use the SampleDynamicQuotaSelector.xml file in the PDC_home/apps/Samples/Examples directory (where PDC_home is the directory in which the PDC software is installed) to create the XML files for configuring dynamic quota selectors. See "Configuring Dynamic Quota Selectors" for more information.

Table 1–1 lists the elements that are supported in the dynamic quota selector XML file, the usage of each element, and a description of how to specify each element in the XML file.


1-2 PDC Release Notes

Table 1–1 Elements Supported in the Dynamic Quota Selector XML File

Element Syntax Description

dynamicQuotaSelectors <dynamicQuotaSelectors>DynamicQuotaSelector</dynamicQuotaSelectors>

DynamicQuotaSelector specifies the root element of the DynamicQuotaSelector.xml file.

name <name>DynamicQuotaConfiguration</name> DynamicQuotaConfiguration specifies the dynamic quota selector name. For example, Generic Selector ABC.

description <description>DynamicQuotaSelectorDescription</description>

DynamicQuotaSelectorDescription specifies the description of the dynamic quota selector.

priceListName <priceListName>PriceListName </priceListName>

PriceListName specifies the price list name. The valid value is Default.

applicableToName <applicableToName>ApplicableToName</applicableToName>

ApplicableToName specifies the service name. The attributes of this service are used in the rules.

eventSpecName <eventSpecName>EventName</eventSpecName> EventName specifies the name of an event. The attributes of this event are used in the rules.

validityPeriod <validFrom>Validfromdate</validFrom> Validfromdate specifies the date from which the rule is valid. The valid format is YYYYMMDD.

Note: It is mandatory to mention the date from when the rule is valid. If no date is specified, the rule is valid from immediate effect.

applicableToAllChildEvent

<applicableToAllChildEvent>ChildEventsOption</applicableToAllChildEvent>

Specifies whether the dynamic quota selector is applicable to the child events, where ChildEventsOption is:

■ True if the dynamic quota selector applies to all the child events.

■ False if the dynamic quota selector applies to only the specific event type.

rule <rule> <ruleName>RuleName</ruleName> <ruleOrder>RuleOrder</ruleOrder> <configuration>DyamicQuotaConfiguration</configuration> <requestedUnits>RequestedUnitsForAllocation</requestedUnits> <dynamicQuotaFieldToValueExpression>FieldToValueExpression</dynamicQuotaFieldToValueExpression> <dynamicQuotaComplexExpression>ComplexExpression</dynamicQuotaComplexExpression></rule>

Specifies the rules for allocating dynamic quotas, where:

■ RuleName specifies the rule name.

■ RuleOrder specifies the order in which the rules must be applied.

■ DyamicQuotaConfiguration contains the configurations for dynamic quotas.

■ RequestedUnitsForAllocation contains the requested units for allocating dynamic quotas.

■ FieldToValueExpression contains the attributes used for deriving the quota.

■ ComplexExpression contains the complex conditions for deriving the quota.

Note: You can add multiple rules in the dynamic quota selector.

Each rule in the dynamic quota selector can refer to a different attribute. For example, Rule 1 can use an event attribute, Rule 2 can use a balance expression, and Rule 3 can use a service attribute.


New Features 1-3

DyamicQuotaConfiguration

<configuration> <key>key</key> <value>value</value> <unit>unit</unit></configuration>

Specifies the quota attribute configurations, where:

■ key specifies the quota attribute. The valid values are:

VOLUME_QUOTA_THRESHOLD. Specifies how long a granted quota can be idle before the reservation is released.

QUOTA_HOLDING_TIME. Specifies how much of the granted quota must be consumed before a subscriber can request additional quota. This attribute is configured per service, event, and number of granted units.

VALIDITY_TIME. Specifies whether validity time can be set to a fixed value per service-event combination at runtime. This attribute is independent of the number of units in the granted quota.

■ value specifies the quota attribute value.

■ unit specifies the unit for measurement. The valid values are:

Seconds

Minutes

Hours

Days

Bytes

Kbytes

Mbytes

Gbytes

None

Note: You must add the DyamicQuotaConfiguration element for each valid quota attribute.

RequestedUnitsForAllocation

<requestedUnits> <fieldName>fieldname</fieldname> <unit>unit</unit> <dynamicQuotaBinaryExpression>dynamicQuotaBinaryExpression</dynamicQuotaBinaryExpression></requestedUnits>

<requestedUnits> <fieldName>fieldname</fieldname> <unit>unit</unit> <numberExpression>numberExpression</numberExpression></requestedUnits>

Specifies the details about the requested units, where:

■ fieldName specifies the fully qualified requested attribute field name. This is specified in the event specification. For example, EventDelayedSessionTelcoGsm.REQUESTED_UNITS.INPUT_VOLUME.

■ unit specifies the unit for measurement. The valid values are:

Seconds

Minutes

Hours

Days

Bytes

Kbytes

Mbytes

Gbytes

None

■ dynamicQuotaBinaryExpression specifies the condition for deriving the quota.

■ numberExpression specifies a valid number; for example, 10.0.

Table 1–1 (Cont.) Elements Supported in the Dynamic Quota Selector XML File




dynamicQuotaBinaryExpression

<dynamicQuotaBinaryExpression> <leftOperand> <numberExpression>numberExpression</numberExpression> <balanceExpression>balanceExpression</balanceExpression> </leftOperand>

<rightOperand> <balanceExpression>balanceExpression</balanceExpression> <numberExpression>numberExpression</numberExpression> </rightOperand> <dynamicQuotaBinaryOperator>Operator</dynamicQuotaBinaryOperator></dynamicQuotaBinaryExpression>

Specifies the condition for deriving the quota, where:

■ numberExpression specifies a valid number; for example, 10.0.

■ balanceExpression specifies the currency or noncurrency balance element defined in PDC.

■ Operator specifies the arithmetic operators. The valid values are:

Add

Subtract

Multiply

Divide

FieldToValueExpression <dynamicQuotaFieldToValueExpression> <separator>Delimiter</separator> <operation>Operator</operation> <fieldName>FieldName</fieldName> <fieldKind>FieldKind</fieldKind> <fieldValue>FieldValue</fieldValue></dynamicQuotaFieldToValueExpression>

Specifies the attributes used for deriving the quota, where:

■ Delimiter specifies the character that is used to separate the field values.

Note: This is applicable only when the operator is IN_LIST.

■ Operator specifies the operator to be used in the expression. The valid values are:

EQUAL_TO

NOT_EQUAL_TO

GREATER_THAN

GREATER_THAN_EQUAL

LESS_THAN

LESS_THAN_EQUAL

IN_LIST

CONTAINS

■ FieldName specifies the fully qualified field name. For example, EventSessionTelcoGsm.REQUESTED_UNITS.NUMBER_OF_UNITS.

■ FieldKind specifies the type of attributes. The valid values are:

PRODUCT_SPEC_FIELD

EVENT_SPEC_FIELD

CUSTOMER_SPEC_FIELD

PROFILE_SPEC_FIELD

■ FieldValue specifies the field value that is used to track the balance impacts.

Note: You can add multiple FieldToValueExpression elements in a rule to derive the quota based on a combination of attributes.



Support for Configuring Policy Specifications (Patch Set 12)

New Features 1-5

Configuring Dynamic Quota SelectorsTo configure a dynamic quota selector:

1. Make a copy of the PDC_home/apps/Samples/Examples/Sample_DynamicQuotaSelector.xml file to customize.

2. Open the file in a text editor or XML editor.

3. Add or modify the elements as required. See Table 1–1, " Elements Supported in the Dynamic Quota Selector XML File" for the usage and description of each element.

4. Save and close the file.

Note: You can save the file with a different name.

5. Go to the directory where you have saved the file.

6. Import the dynamic quota selector from the customized XML file into the PDC database by running the following command:

ImportExportPricing -import -config filename

where filename is the name of the customized XML file. For example, the Dynamic_QuotaSelector.xml file.

The dynamic quota selector is imported into the PDC database and published to ECE.

Support for Configuring Policy Specifications (Patch Set 12)ECE supports policy-driven charging. For ECE to support policy-driven charging, you need to configure offer profiles with policies to define the ranges in the quality of service (QoS) for the services you offer.

In the previous releases, to configure offer profiles for ECE, you had to create the offer profiles in BRM by using the XML interface, create provisioning tags in BRM with the same name as offer profiles, and then associate the offer profiles with charge offers and

ComplexExpression <dynamicQuotaComplexExpression> <operator>Operator</operator> <value>Value</value> <dynamicQuotaBinaryExpression>dynamicQuotaBinaryExpression</dynamicQuotaBinaryExpression></dynamicQuotaComplexExpression>

Specifies complex conditions for deriving the quota, where:

■ Operator specifies the operator to be used in the expression. The valid values are:

EQUAL_TO

NOT_EQUAL_TO

GREATER_THAN

GREATER_THAN_EQUAL

LESS_THAN

LESS_THAN_EQUAL

■ Value is a numeric value. For example, 0.004.

■ dynamicQuotaBinaryExpression specifies the condition for deriving the quota.





discount offers in PDC by using the provisioning tags. And, load the offer profiles from BRM into ECE to extract the policy information for charging.

With this enhancement, the process for configuring offer profiles has been simplified. You can now configure policy specifications (offer profiles) directly in the PDC user interface or by importing the specifications into PDC by using XML files and then publish them to ECE for policy-driven charging. The PDC term for offer profile is policy specification.

A policy specification is made up of one or more counter policies each of which defines a gradation in the QoS based on the subscriber's service usage. For example, you can have a policy specification called Platinum for a data service and a balance element for it as Megabytes Used. You can define a counter policy labeled Fair Usage, which has three levels, Low QoS, Medium QoS, and High QoS, with each level containing a usage range valid for that quality of service, such as 100-150, 150-200, and 200-No Maximum megabytes.

Important: If you are using ECE for usage charging, ensure that you migrate the existing offer profile data from BRM into PDC and use only PDC for configuring policy specifications. After you migrate the offer profile data into PDC, do not create any offer profiles in BRM.

For more information on migrating the offer profile data, see PDC Installation and System Administration Guide.

Policy specification is one of the setup components that you configure before creating any product offering in PDC. You can associate the policy specification with the product offering by selecting the policy specification when specifying the charge or discount offer settings. For more information, see the discussions about creating a charge offer and creating a discount offer in the PDC Help.

When you configure policy specifications, ensure the following:

■ The policy label and counter range label (policy sublabel) names specified in the policy specification matches the policy label and sublabel names (respectively) specified in the policy label.

■ The balance element referenced in the policy specification is a noncurrency balance element.

■ Only one counter policy is added per balance element in the policy specification and the balance element is used in the corresponding charge offer or discount offer.

■ The counter ranges in the policy specification are in sequence.

To configure policy specifications by using the PDC user interface, see "Configuring Policy Specifications by Using the PDC User Interface". You can also configure policy specifications by using the following sample files in the PDC_home/apps/Samples/Examples directory:

■ SamplePolicyLabel.xml. Contains policy labels referenced in the policy specifications.

■ SamplePolicySpecification.xml. Contains policy specifications referenced in the charge offers and discounts offers used for policy-driven charging.

You can load the customized XML files into PDC by using the ImportExportPricing utility. See "Configuring Policy Specifications by Using XML Files" for more information.


New Features 1-7

Configuring Policy Specifications by Using XML FilesTo configure policy specifications by using XML files:

1. Make a copy of the PDC_home/apps/Samples/Examples/SamplePolicyLabel.xml file to customize.


3. Add or modify the elements as required.


5. Make a copy of the PDC_home/apps/Samples/Examples/SamplePolicySpecification.xml file to customize.


7. Add or modify the elements as required.


9. Go to the directory where you have saved the files.

10. Import the policy specifications and policy labels from the customized XML files into the PDC database by running the following command:

ImportExportPricing -import -config filename

where filename is the name of the customized XML file.

The policy specifications and policy labels are imported into the PDC database and transformed to ECE.

After you configure policy specifications, you can export the policy specifications and policy labels in PDC to XML files by running the following command:

ImportExportPricing -export -config POLICY_SPECIFICATIONImportExportPricing -export -config POLICY_LABEL

For more information, see the discussion about the ImportExportPricing utility in PDC User's Guide.

Configuring Policy Specifications by Using the PDC User InterfaceTo configure policy specifications by using the PDC user interface:

1. In the Setup section of the navigation pane, under Pricing Elements, click Policy Specifications.

The Policy Specifications page appears.

2. Specifying general information for a policy specification. See "Specifying General Information for a Policy Specification" for more information.

3. Create policy labels. See "Creating Policy Labels" for more information.

4. Create counter policies. See "Creating Counter Policies" for more information.

Specifying General Information for a Policy SpecificationTo specify general information for a policy specification:

1. In the Policy Specifications section, click the Add icon in the table toolbar.

A new row is added.

2. In the Name column, enter a unique name for the policy specification.



3. In the Description column, enter a description for the policy specification.

Creating Policy LabelsTo create a policy label:

1. In the Counter Policies section, click the Add icon in the table toolbar.

The Create Counter Policy dialog box appears.

2. From the Policy Label list, select Create….

The Create Policy Label dialog box appears.

3. In the Name field, enter a unique name for the policy label.

4. In the Sub-Labels section, click the Add icon in the table toolbar.

A new row is added.

5. In the Label column, enter a unique name for the sublabel.

You can add additional sublabels by repeating step 4 and 5.

6. Click OK.

Creating Counter PoliciesTo create a counter policy:

1. In the Counter Policies section, click the Add icon in the table toolbar.

The Create Counter Policy dialog box appears.

2. From the Policy Label list, select a policy label or create a new policy label. See "Creating Policy Labels" for more information.

3. From the Unit list, select the unit to be used for measurement.

4. From the Balance Element list, select a balance element to which the counter policy must be applied.

Note: The Balance Element list displays only the noncurrency balance elements. You can add only one counter policy for a balance element in a policy specification.

5. Add counter ranges. See "Adding Counter Ranges" for more information.

6. From the Label list, select the corresponding label for each counter range.

Tip: You can select the same label for multiple counter ranges as appropriate.

7. Click OK.

8. Click Save.

Adding Counter RangesTo vary QoS based on the level of usage, add counter ranges to a counter policy and use different policy labels for each range.

To add a counter range to a counter policy:

1. In the Counting Ranges section, click the Add icon in the table toolbar.


New Features 1-9

The Add Counter Range dialog box appears.

2. In the Starting At field, enter the starting value for the range, or select No Minimum.

PDC automatically generates an end value for the range based on the existing counter ranges.

For example, if you specify 5, PDC creates the following range:

■ 5 – No maximum

If you then create another quantity range with a start value of 2.5, PDC creates the following ranges:

■ 2.5 – 5

■ 5 – No maximum

3. Click OK.

A table for the counter range is added.

Modifying Policy SpecificationsTo modify a policy specification:

1. In the Policy Specifications section, click the policy specification that you want to modify.

2. Edit the name and description as required.

3. Modify the counter policies as required. See "Modifying Counter Policies" for more information.

4. Click Save.

Modifying Policy LabelsTo modify a policy label:

1. In the Counter Policies section, click the counter policy that you want to modify.

The Edit Counter Policy dialog box appears.

2. From the Policy Label list, select the policy label that you want to modify and click Edit....

The Edit Policy Label dialog box appears.

3. Modify the policy label and sublabels as required.

To edit a sublabel, click a label in the Sub-labels section.

To delete a sublabel, select a label in the Sub-labels section and then click the Delete icon in the table toolbar.

4. Click OK.

Modifying Counter PoliciesTo modify a counter policy:

1. In the Counter Policies section, click the counter policy that you want to modify.

The Edit Counter Policy dialog box appears.

2. Modify the policy label, counter ranges, and the range labels as required.



For modifying policy labels, see "Modifying Policy Labels".

For modifying counter ranges, see "Modifying Counter Ranges".

3. Click OK.

Modifying Counter RangesTo modify the counter range in a counter policy:

1. Go to the Counter Ranges section.

2. In the Counter Ranges table, click the link in the Counter Ranges column for which you want to change the range.

The Edit Counter Range dialog box appears.

3. Modify the Start value.

You can specify a minimum start value or select No Minimum.

You cannot enter a value that includes the entire following counter range. Instead, to extend a range beyond the following range, first delete the following range. See "Deleting Counter Ranges" for more information.

PDC adjusts the start and end values of the preceding and following counter ranges accordingly.

4. Click OK.

Deleting Policy SpecificationsTo delete a policy specification:

Note: You cannot delete a policy specification that is referenced by other components. The In Use icon indicates that the policy specification is referenced by other components and that it cannot be deleted.

1. In the Policy Specifications section, click the policy specification that you want to delete.

2. Click the Delete icon in the table toolbar.

A confirmation message appears.

3. Click OK.

The policy specification and the associated counter policies are removed.

4. Click Save.

Deleting Counter PoliciesTo delete a counter policy:

1. In the Counter Policies section, select the counter policy that you want to delete.



3. Click OK.

The counter policy is removed from the table.

PDC Now Enables you to Export Components Mastered in BRM (Patch Set 12)

New Features 1-11

4. Click Save.

Deleting Counter RangesTo delete a counter range:

1. Go to the Counter Ranges section.

2. In the Counter Ranges table, select the range in the Counter Ranges column.



4. Click OK.

The counter range and the corresponding policy label are removed from the table.

If you deleted a middle range, PDC automatically adjusts the end value of the previous counter range.

PDC Now Enables you to Export Components Mastered in BRM (Patch Set 12)

You run the ImportExportPricing utility to export components mastered in PDC into XML files. With this enhancement, you can run the ImportExportPricing utility with -brmobject parameter to export the components mastered in BRM from PDC into XML files.

Note: You cannot use the -brmobject parameter to import components into PDC.

The syntax for exporting the components mastered in BRM into an XML file is as follows:

ImportExportPricing -export -brmobject [BRMObjectType1,BRMObjectType2,…] [FileNamePrefix]

where:

■ BRMObjectType is the following:

– GLID

– TAX_CODE

– TAX_SUPPLIER

– PROVISIONING_TAG

You can also view the supported object types by running the following command:

ImportExportPricing -type -brmobject

If you do not specify BRMObjectType, the utility exports all the components mastered in BRM into the XML file.

■ FileNamePrefix is the prefix to append to the beginning of the generated XML file name.

For example, you can export the G/L IDs from the PDC database into an XML file by running the following command:

Support for NOT Operator in Selectors (Patch Set 12)


ImportExportPricing -export -brmobject GLID GLID

All G/L IDs are exported to the GLID_brm_object.xml file.

For more information on using the ImportExportPricing utility to import or export components from PDC, see the discussion about ImportExportPricing utility in PDC User's Guide.

Support for NOT Operator in Selectors (Patch Set 12)In previous releases, the NOT operator for the selectors was not supported in the PDC user interface.

With this enhancement, you can set the NOT operator for all the selectors, such as the APN Selector, Charge Selector, Discount Selector, Generic Selector, Price Selector, and USC Selector, in the PDC user interface.

You can set the NOT operator while creating a rule for the selector. You can select the NOT operator from the operator list and specify a value in the Rules section.

Note: The NOT operator can be set for a selector only if you are using ECE for usage charging.

Depending on the selector for which the rule is being added, the PDC user interface displays one of the following set of values in the operator list:

■ Equals or Not Equals

■ In or Not In

■ Matches or Not Matches

For more information on configuring rules for the selectors in the PDC user interface, see the PDC Help.

You can also set the NOT operator for the selectors by defining the operator in the XML files and then import that into the PDC database by using the ImportExportPricing utility. For more information, see the discussion about importing and exporting pricing and setup components in PDC User’s Guide.

In the XML file, for a selector for which the rule is being added, you can set the NOT operator as shown in the following example:

<! -- Example for NOT Operator for a complex FieldToValue expression. -->

<complexAAExpression> <rightOperand> <fieldToValueExpression> <operation>EQUAL_TO</operation> <seperator>;</seperator> <fieldName>EventActivityTelco.BATCH_ID</fieldName> <fieldValue>*</fieldValue> <fieldKind>EVENT_SPEC_FIELD</fieldKind> </fieldToValueExpression> </rightOperand> <operator>NOT</operator></complexAAExpression>

Support for Reordering Discount and ChargeShare Rules (Patch Set 12)

New Features 1-13

Support for Reordering Discount and ChargeShare Rules (Patch Set 12)By default, discount and ChargeShare rules are added in the order that they are created. This order determines the priority of the rules.

In previous releases, to reorder these rules, you either had to create duplicate rules, change the order, and then delete the duplicate rules or export the rules to an XML file, reorder the rules, and import the rules back.

With this enhancement, you can change the order of the discount and ChargeShare rules in the PDC User Interface. You can move the rules to the desired location either by dragging and dropping them or by using the Actions option. For more information, see:

■ Reordering Discount Rules

■ Reordering ChargeShare Rules

For more information on discount or ChargeShare rules, see the discussion about configuring discount or ChargeShare rule in the PDC Help.

Reordering Discount RulesTo reorder a discount rule:

1. In the Pricing section of the navigation pane, click Search Pricing.

2. Click Advanced.

The Search page appears.

3. Select Discount Offer from the Pricing Component list and click Search.

4. Select the required discount offer.

The Discount Offer page appears.

All available rules for the selected discount are displayed in the Rules tab as subtabs.

5. Click Edit to modify or reorder the rules.

6. In the Rule Details section, select a rule.

7. Drag and drop it to the desired location in the Rules tab or do the following:

a. Click Discount Actions.

b. Click Rule Actions.

c. Click Move Rule.

The Move the Rule dialog box appears.

d. From the Move the rule before list, select the desired location.

e. Click OK.

The rule is moved to the new location.

8. Click Save.

9. Click Save and Done.

Reordering ChargeShare RulesTo reorder a ChargeShare rule:

Importing PDC Configurations by Ignoring Internal IDs (Patch Set 11)


1. In the Pricing section of the navigation pane, click Search Pricing.

2. Click Advanced.

The Search page appears.

3. Select ChargeShare from the Pricing Component list and click Search.

4. Select the required ChargeShare offer.

The ChargeShare Offer page appears.

All available rules for the selected ChargeShare are displayed in the Rules tab as subtabs.

5. Click Edit to modify or reorder the rules.

6. In the Rule Details section, select a rule.

7. Drag and drop it to the desired location in the Rules tab or do the following:

a. Click ChargeShare Actions.

b. Click Rule Actions.

c. Click Move Rule.

The Move the Rule dialog box appears.

d. From the Move the rule before list, select the desired location.

e. Click OK.

The rule is moved to the new location.

8. Click Save.

9. Click Save and Done.

Importing PDC Configurations by Ignoring Internal IDs (Patch Set 11)In previous releases, before running the ImportExportPricing utility to import pricing components into PDC, all the internal IDs for the objects with the same name had to be removed from the input XML file due to validation errors.

With this enhancement, you can run the ImportExportPricing utility with the -ignoreID parameter to ignore the internal IDs and import the pricing components by the input file name.

For example, running the following command ignores the internal IDs in the pdc_config.xml file and imports the setup components into PDC:

ImportExportPricing -import –config pdc_config.xml -ignoreID -ow

For more information on using the ImportExportPricing utility to import or export pricing components, see the discussion about importing and exporting pricing and setup components in PDC User’s Guide.

Support for Adding Multiple Currencies in the PDC UI (Patch Set 11)In previous releases, you could add charges with multiple currencies only by importing them into PDC.

Support for Adding Multiple Currencies in the PDC UI (Patch Set 11)

New Features 1-15

With this enhancement, you can add charges with multiple currencies for charge offers, charge selectors, and price selectors by using the PDC user interface or by importing them into PDC.

To add charges with multiple currencies, select the currencies from the Currency list when adding a new charge. You can also select the Using same pricing rule for all selected currencies option for using the same pricing rule for all the currencies in the single currency graph. This option is not applicable for the currencies in the multi currency graph.

For more information on adding charges, see the discussion about adding charges to a charge offer in the PDC Online Help.

In addition, you can add additional currencies to a charge and remove currencies from a charge in the PDC user interface. For more information, see the following:

■ Adding Additional Currencies to a Charge

■ Removing Currencies from a Charge

Adding Additional Currencies to a ChargeTo add additional currencies to a charge:

1. In the Charges section of the Create Charge Offer page, do one of the following:

■ If you are adding the currency to a multi currency graph, click the Charge Currency list.

■ If you are adding the currency to a single currency graph, click the Tier Currency list.

2. Select Add.

The Manage Currencies dialog box appears listing all the currencies that are available for the charge.

3. Select the required currencies.

4. Click OK.

The selected currencies are added to the charge.

Removing Currencies from a ChargeTo remove currencies from a charge:

1. In the Charges section of the Create Charge Offer page, do one of the following:

■ If you are removing the currency from a multi currency graph, click the Charge Currency list.

■ If you are removing the currency from a single currency graph, click the Tier Currency list.

2. Select Delete.

The Manage Currencies dialog box appears listing all the currencies that are configured for the charge.

3. Select the currencies to be removed.

4. Click OK.

The selected currencies are removed from the charge.

Support for Aggregation of System-Level ChargeShare Offers (Patch Set 11)


Support for Aggregation of System-Level ChargeShare Offers (Patch Set 11)

In previous releases, you could not use the ChargeShare offers configured at the system level in ECE.

With this enhancement, you can configure system-level ChargeShare offers in PDC and use them in ECE for aggregation.

To create system-level ChargeShare offer with aggregation enabled:

1. In the Pricing section of the navigation pane, under Offers, click Create ChargeShare Offer.

The Create ChargeShare Offer page appears.

2. Enter a unique name and a description for the ChargeShare offer.

3. From the Applicable To list, select the service for which you want to create the ChargeShare offer.

4. Select Use for Aggregation.

The ChargeShare offer is set for aggregation.

5. Expand the Offer Settings section.

6. In the Available group, specify the period when the ChargeShare offer is valid.

7. Add ChargeShares. For instructions, see the PDC Online Help.

8. Configure pricing for the ChargeShares. For instructions, see the PDC Online Help.

Note: After you create the ChargeShare offer, you must restart the ECE server to publish it to ECE. See the discussion about starting and stopping ECE in ECE System Administrator's Guide for more information.

Support for Prorating Charges in Charge Selectors (Patch Set 11)In previous releases, you could not prorate charges in charge selectors.

With this enhancement, you can configure proration for charges in charge selectors by using the PDC user interface or by importing the configuration into PDC.

When adding a charge selector, to configure proration for charges:

1. In the Charges section of the Create Charge Selector page, click Charge Selector Configuration.

2. Select Proration Settings from the list.

The Proration Settings dialog box appears.

3. Specify how the charge should be handled if the charge selector is purchased or canceled in the middle of the billing cycle by selecting one of the following options:

■ Prorate: Calculate the charge based on the amount used.

■ Full Charge: Charge for the entire cycle.

■ No Charge: Do not charge for the cycle.

Support for Renaming and Removing Discount Rule Names (Patch Set 11)

New Features 1-17

4. click OK.

Note: The proration settings is applicable to all the charges in the charge selector.

For more information on charge selectors, see the discussion about charge selectors in the PDC Online Help.

Support for Renaming and Removing Discount Rule Names (Patch Set 11)In previous releases, discount rule names were added by default and you could not change the default rule names or remove the discount rules.

With this enhancement, you can change the default discount rule name and also remove the discount rule. You can now add, rename, or delete discount rules using the new Rules Actions list for Discount Actions. For more information, see the following:

■ Creating a Discount Rule

■ Renaming a Discount Rule

■ Deleting a Discount Rule

Creating a Discount RuleTo create a new discount rule:

1. From the Discounts Actions list, select Rule Actions.

2. Select Add Rule.

The rule is added as a subtab of the discount tab with default filter and trigger.

Renaming a Discount RuleTo rename a discount rule:


2. Select Rename Rule.

The Change Rule Name dialog box appears.

3. Enter the new name.

4. Click OK.

Deleting a Discount RuleTo delete a discount rule:


2. Select Remove Rule.

The selected rule name is deleted

For more information, see the discussion about discount rules in PDC User’s Guide.

Additional Option for Setting End of Validity for Noncurrency Credit Balance Impacts (Patch Set 10)


Additional Option for Setting End of Validity for Noncurrency Credit Balance Impacts (Patch Set 10)

In previous releases, when you set the validity period for a noncurrency credit balance impact (for example, free minutes) to one day, the validity ended only after 24 hours.

With this enhancement, when you add a charge or discount, you can select the Calendar Day option to set the validity of a noncurrency credit balance impact to end by midnight (which is 12:00 AM) of a specific day. For example, to allocate free minutes to a customer for a special day, you can set the balance impact validity to start from a specific date and end by midnight of the same day.

When you add a charge or discount, to set the validity of a noncurrency credit balance impact to end by midnight of a specific day:

1. In the Pricing Details section, click the Add Balance Impact icon in the pricing table tool bar.

2. Edit the values for the balance impact. See the discussion about the pricing table in the PDC Online Help for details on the balance impact values.

3. In the Amount is Valid dialog box, do the following:

a. To select the validity start time, select any option from the list on the left.

b. To select the validity end time, select End Relative to Validity Start from the list on the right.

The lists to select number of days and the validity end option are displayed.

c. Select the number of days.

d. Select Calendar Day.

For example, if you select 2 in the number of days list and then select Calendar Day, the balance impact will not be valid after midnight of the second day from the validity start time.

Note: You can use the Calendar Day option only for charges or discounts with the Convergent Usage pricing profile.

See the PDC Online Help for more information on adding balance impacts for charges or discounts.

Additional Options to Configure Discount Filters (Patch Set 10)In previous releases, for Convergent Usage pricing profiles, you could not use the following fields in discount filters:

■ Usage Class

■ Usage Type

■ Service Class

■ Service Code

You could use them only in discount selectors. With this enhancement, the above fields are enabled by default in discount filters for Convergent Usage pricing profiles. You can use them as criteria to filter discounts for usage charging.

Dynamic Pricing Can Now Be Configured By Using the PDC UI (Patch Set 10)

New Features 1-19

For more information on adding discount filters, see the discussion about adding a new filter in the PDC Online Help.

Dynamic Pricing Can Now Be Configured By Using the PDC UI (Patch Set 10)

In previous releases, you could configure dynamic pricing to override the price specified in the product offerings only by importing pricing XML files into PDC.

With this enhancement, you can configure dynamic pricing by using the PDC user interface or by importing pricing XML files into PDC. You can perform this by adding price tags to balance impacts or quantity ranges in the charges. You can later edit or delete these tags when required.

Note: You can add price tags only for charges with the Convergent Usage pricing profile.

To configure dynamic pricing:

1. Create a charge offer. See the discussion about creating a charge offer in the PDC Online Help.

2. Add a new charge to the charge offer. See the discussion about adding a new charge in the PDC Online Help.

3. Add balance impacts to the charge. See the discussion about adding balance impacts to a charge in the PDC Online help.

4. Add a price tag by doing the following:

a. In the Pricing Details section of the charge tab, select a balance impact.

b. Click the Price Tag icon in the pricing table tool bar.

The Price Tag dialog box appears.

c. From the Attribute list, select the attribute name.

If you selected Amount or Increment, proceed to step g.

To configure price tags for quantity range, go to price tags under quantity range option and modify them.

d. Modify the values in the Start and End fields.

The Start field is available only for the first quantity range in the pricing. To modify the start value of subsequent ranges, change the end value of the range that precedes them.

By default, the first quantity range has no minimum start value. To specify a minimum start value, first deselect No Minimum.

You cannot enter a value that includes the entire following quantity range. Instead, to extend a range beyond the following range, first delete the following range.

By default, the last quantity range has no maximum end value. To specify a maximum end value, first deselect No Maximum.

e. Expand Price Tag.

f. From the Attribute list, select End.

PDC Now Enables You to Delete Old Versions of PDC Components (Patch Set 10)


g. Enter or select a name for the price tag.

h. (Optional) Enter the description for the price tag.

i. Click OK.

To delete price tags, in the Price Tag dialog box, select Not Set from the Name list and click OK.

For more information on dynamic pricing, see "Dynamic Pricing is Now Supported in PDC (Patch Set 9)".

PDC Now Enables You to Delete Old Versions of PDC Components (Patch Set 10)

PDC now enables you to delete old versions of PDC components that are no longer used by PDC or the associated target engines (for example, Oracle Communications Billing and Revenue Management (BRM) Elastic Charging Engine (ECE)) and keeps only the latest versions of successfully promoted PDC components.

You can perform this by running the -keep parameter with the ImportExportPricing utility:

./ImportExportPricing -keep [metadata | config | pricing | all] -numVersion N

where N is a positive integer that specifies the number of latest successful versions to be kept in the PDC database.

Note: PDC keeps N+1 versions of the successfully promoted components if they are available in the PDC database. For example, if you want to keep the latest two versions of successfully promoted components and there is only one version available in the PDC database, PDC keeps only that one version of successfully promoted components.

For example:

./ImportExportPricing -keep all -numVersion 2

keeps only the latest three versions (2+1) of all the successfully promoted objects in the PDC database and deletes the remaining versions.

For more information on the ImportExportPricing utility, see the discussion about importing and exporting pricing and setup components in PDC User's Guide.

PDC Now Enables you to Export Only Successfully Promoted and Transformed Components (Patch Set 10)

In previous releases, when running the ImportExportPricing utility to export pricing components from PDC, the utility exported the latest promoted versions of all components, including the components that failed during the transformation. Consequently, the failed components could not be published to the target engines.

With this enhancement, you can now export only the successfully promoted and transformed versions of the components by running the ImportExportPricing utility without the inclFailedObjs parameter. By default, the ImportExportPricing tool exports only successfully promoted and transformed objects. Running the

Pricing Tiers for Single RUM Graph With Selective RUMs Can Now be Configured by Using the PDC UI (Patch Set 10)

New Features 1-21

ImportExportPricing utility with the inclFailedObjs parameter exports the most current promoted components in addition to the failed components.

To export only successfully promoted and transformed pricing components, run the following command:

ImportExportPricing -export –pricing -name -expRefs

For example, the following command exports the latest version of only the successfully promoted and transformed pricing components in ChargeOffer COTest along with the reference components:

ImportExportPricing –export –pricing CHARGE_OFFERING -name "COTest" -expRefs

After exporting the promoted and transformed versions of the pricing components, you can publish the components to the target engines.

For more information on using the ImportExportPricing utility to import or export pricing components, see the discussion about importing and exporting pricing and setup components in PDC User’s Guide.

Additionally, when publishing components in a change set to multiple target engines in different jobs, if any job fails, PDC now marks the failed job and the other jobs created for the change set as FAILED and displays the appropriate reason code. This lets you fix the failed job and transform all the components in the change set successfully.

Pricing Tiers for Single RUM Graph With Selective RUMs Can Now be Configured by Using the PDC UI (Patch Set 10)

In previous releases, when configuring a single RUM graph with multiple ratable usage metrics (RUMs), you could configure a subset of the applicable RUMs for each price tier only by using the ImportExportPricing utility.

With this enhancement, you can configure a subset of the applicable RUMs for each price tier by using the PDC user interface as well. After creating a single RUM graph, you can add or remove pricing tiers for any applicable RUMs. In the PDC user interface, the Pricing Details section of the charge that you configured now shows a tab with the RUM name even if only one pricing tier is configured for the RUM. If multiple pricing tiers and RUMs are configured, you can add or remove price tiers for the applicable RUMs that are configured in the charge by using the new Pricing Actions list. You can also rename a pricing tier by using the Rename Pricing option in the Pricing Actions list.

You can add or remove pricing tiers only for single RUM graphs with multiple RUMs. For more information on creating a single RUM graph, see "Support for Single RUM Graph (Patch Set 9)".

To add, remove, or rename pricing tiers for selective RUMs:

1. In the Pricing Details section of the charge tab, click the Pricing Actions list.

The Pricing Actions list displays the following options:

■ Add Price Tier

■ Remove Price Tier

■ Rename Pricing

2. Do one of the following:

RUMs Can Now Be Configured for Price Overrides in Single RUM graphs (Patch Set 10)


To add a pricing tier:

a. Select Add Price Tier.

b. Select any RUM from the list of available RUMs.

c. Click OK.

To remove a pricing tier:

a. Select Remove Price Tier.

b. Select the RUM you want to remove.

c. Click OK.

To rename a pricing tier:

a. Select Rename Pricing.

The Rename Pricing dialog box appears.

b. In the Pricing Name field, enter a unique name for the pricing tier.

c. Click OK.

The new name of the pricing tier appears in the Charges tree and in the heading of the Pricing Details section.

Note: If you do not add a pricing tier for any of the applicable RUMs in the charge, when you validate the charge, PDC displays an error message with a list of missing and required pricing configurations.

RUMs Can Now Be Configured for Price Overrides in Single RUM graphs (Patch Set 10)

In previous releases, it was not possible to select RUMs for price overrides. As a result, when a single RUM graph was configured with multiple RUMs, price overrides were applied to all the RUMs in the single RUM graph.

With this enhancement, when you add a price override to a charge, you can select the RUMs to which the price override applies. You can select the RUMs from the new Measured By list in the Price Override section.

To add a price override to a charge and configure RUMs for the price override:

1. In the Charges tree, select the parent node for the price override.

2. From the Add list, select Price Override.

A Price Override child node is added to the selected parent node, and a corresponding table is displayed in the charge.

3. In the Impact to Original Price column, select the type of override.

4. In the Amount column, enter the amount of the override.

5. In the Balance Element column, select the balance element affected by the override.

6. In the Measured By column, select the RUMs to which the price override applies.

Note: You can select RUMs for price overrides only when you create charge offers with single RUM graphs.

Additional Purchase Option for Bundles (Patch Set 9)

New Features 1-23

7. In the GLID column, enter the general ledger (G/L) ID for the event associated with the charge.

For more information on adding a price override, see the discussion about adding price overrides to a charge in the PDC Online Help.

Additional Purchase Option for Bundles (Patch Set 9)In previous releases, when adding services and bundles, you had only two purchase options. You could specify if a bundle is required or optional.

With this enhancement, you have an additional purchase option. You can now add services and bundles by doing the following:

1. In the Manage Package Content section, click Add Service in the table.

The Add Service dialog box appears.

2. Select the service that you want to associate the bundles with in the package and click OK.

The table is updated with the new service.

3. (Optional) Create a service group.

4. Select a service, service group, or Account, then click Add Bundle.

Note: You cannot add more than one bundle to Account.

The Search for Bundles dialog box appears.

5. Search for the bundles to add to the package.

6. In the Results table, select the bundles that you want to add to the package and click OK. Hold down the CTRL key to select more than one bundle.

The bundles appear under the service in the table.

7. Select one of the following:

a. Optional. Select this if the bundle can be optionally purchased with the service.

b. Required—can be canceled on its own. Select this if the bundle is required but can be canceled without canceling the associated service.

c. Required—must cancel service with bundle. Select this if the bundle is required but can be canceled only after canceling the associated service.

8. Add more services and bundles as needed.

For a description of the fields, see Table 1–2, " Manage Package Content section".

Table 1–2 Manage Package Content section

Column Description

Add Service Click to add services.

Add Bundle Click to add bundles for a service.

Add Member Service Click to add member services to a service group.

Additional Charging Result Attributes Can Be Used for Item Assignment (Patch Set 9)


For more information, see the discussion about Adding Services and Bundles in the PDC Online Help.

Additional Charging Result Attributes Can Be Used for Item Assignment (Patch Set 9)

You can now use the following additional charging result (CHARGING_RESULT_SPEC) attributes in item type selectors for item assignment:

■ ORIG_ZONE_RESULT

■ PRICING_NAME

■ TIME_MODEL_NAME

■ ZONE_MODEL_NAME

■ EVALUATED_ZONE_MODEL_NAME

■ EVALUATED_ZONE

■ CHARGE_RATE_PLAN_NAME

ECE uses these attributes to derive bill items for assigning balance impacts.

With this enhancement, in the expression section of the item type selector XML file, you can provide the following values for FieldName if the FieldKind is CHARGING_RESULT_SPEC:

■ TAX_CODE

■ GLID

■ RUM

■ BALANCE_ELEMENT

■ ZONE_RESULT

■ TIMEMODEL_TAG_NAME

■ GENERIC_SELECTOR_RESULT

■ ORIG_ZONE_RESULT

■ PRICING_NAME

■ TIME_MODEL_NAME

Services in Package Lists the services and associated bundles in the package. Included services can be either standalone services or service groups.

Purchase options The following options are supported:

■ Optional. Select this if the bundle is not required to be purchased with the package. Optional bundles can be purchased at a later time.

■ Required—can be canceled on its own. Select this if the bundle is required but can be canceled later. You can cancel this bundle without canceling the associated service.

■ Required—must cancel service with bundle. Select this if the bundle can be canceled only when canceling the service.

Table 1–2 (Cont.) Manage Package Content section

Column Description

Dynamic Pricing is Now Supported in PDC (Patch Set 9)

New Features 1-25

■ ZONE_MODEL_NAME

■ EVALUATED_ZONE_MODEL_NAME

■ EVALUATED_ZONE

■ CHARGE_RATE_PLAN_NAME

For more information, see the discussion about the elements supported in the item type selector XML file in PDC User's Guide.

Dynamic Pricing is Now Supported in PDC (Patch Set 9)With this enhancement, you can now override the price specified in the product offerings at run time. To override the price, you create a pricing XML file with dynamic tags and import the file into the PDC database by using the ImportExportPricing utility.

Dynamic tags are the XML elements that are used for overriding the value of the pricing attributes. ECE uses these attributes to determine the price when processing a usage request.

Important: Ensure that you create a unique dynamic tag across multiple charge offers since the tags are not scoped to charge offers at run time.

Dynamic tags are used for different pricing within a rate plan. PDC provides a sample XML file for dynamic tags in the PDC_home/apps/Samples/Examples directory, where PDC_home is the directory in which you installed PDC. The dynamic tag (priceTag) consists of the following fields:

■ attributeName. The name of the attribute. The value of the attribute is dynamically determined during rating.

■ tagName. The unique identifier of the dynamic tag.

■ tagScope. The scope of the dynamic tag. Following are the available tag scopes:

– EVENT_PROFILE

– PRODUCT_PROFILE

– CUSTOMER_PROFILE

Note: Only the EVENT_PROFILE tag scope is supported for charges with the Convergent Usage pricing profile.

■ Description. (Optional) The description of the dynamic tag.

For example:

<fixedCharge> <price>20.0</price> <unitOfMeasure>NONE</unitOfMeasure> <balanceElementNumCode>840</balanceElementNumCode> <discountable>true</discountable> <priceType>CONSUMPTION</priceType> <priceTag> <attributeName>price</attributeName> <tagName>PRICE_TAG_FIXED_PRICE</tagName>

Migrate Pricing Data Selectively from BRM to PDC (Patch Set 9)


<tagScope>EVENT_PROFILE</tagScope> </priceTag> </fixedCharge>

In this example, the default price is 20.0. This is used by default if an overriding price is not specified.

For information on importing the pricing XML file into the PDC database, see the discussion about importing and exporting pricing and setup components in PDC User’s Guide.

For information on enabling ECE to override the default value of the pricing attributes at run time, see the discussion about configuring ECE to override a product price in BRM Elastic Charging Engine Implementation Guide.

Migrate Pricing Data Selectively from BRM to PDC (Patch Set 9)The existing migration process migrates all the data from BRM to PDC.

With this enhancement, you can migrate pricing objects selectively to PDC. You can migrate the following pricing objects: products, discounts, and sponsorships.

Note: You cannot migrate subscriptions (bundles or packages) selectively.

You cannot migrate data incrementally. After migrating a set of pricing objects, restart the migration process with new set of pricing objects.

To migrate the required pricing objects, selectively:

1. Ensure that the metadata and setup data migration are completed.

For instructions on migrating configuration objects, see the discussion about migrating BRM configuration objects in PDC Pricing Migration Guide.

2. In the PDC application, ensure that the configuration objects are available.

3. Ensure that the BRM and PDC databases are running.

4. In the BRM_Integration_Pack_Home/apps/migration directory (where BRM_Integration_Pack_Home is the directory in which you installed BRM Integration Pack), create an XML file with the required pricing objects to be migrated; for example, pricingbatch.xml.

This XML file can include either the services for which the pricing objects have to be migrated (for example, /service/telco/gsm/gprs) or the categories of pricing objects (for example, product) that need to be migrated. Multiple pricing objects can be separated by a comma.

Pricing objects for both the specific service and the specific category cannot be migrated together. You can migrate pricing objects either by services associated with these objects or by the category of pricing objects, selectively, at a time. If both service types and offering codes are specified in the same XML file, offering codes takes precedence.

The following example shows the sample XML file created for migrating pricing objects by services:



Migrate Pricing Data Selectively from BRM to PDC (Patch Set 9)

New Features 1-27

<filterBy><service><name>/service/telco/gsm/roaming</name><name>/service/telco/gsm/gprs</name><name>/service/subscription</name></service></filterBy>

The following example shows the sample XML file created for migrating pricing objects by category:

<filterBy><product>Product1,Product2</product>

<discount>Discount1,Discount2</discount>

<sponsorship>Sponsorship1,Sponsorship2</sponsorship>

</filterBy>

5. Open the BRM_Integration_Pack_Home/apps/migration/MigrationConfiguration.xml file and search for the following element:

<useBatch>false</useBatch>

6. Set the value to true for enabling the migration selectively:

<useBatch>true</useBatch>

7. Search for the following element:

<batchName>batchfilename</batchname>

where batchfilename is the name of the XML file that is used for migrating selective data.

8. Specify the name of the XML file that you created in step 4.

For example:

<batchName>pricingbatch.xml</batchname>


10. Continue the pricing objects migration process.

For instructions, see the discussion about migrating BRM pricing objects by category in PDC Pricing Migration Guide.

PDC Now Enables You to Publish PDC Components to Target Engines (Patch Set 9)


PDC Now Enables You to Publish PDC Components to Target Engines (Patch Set 9)

You can now run the ImportExportPricing utility with -publish and -target parameters to publish the components from PDC to the specified target engines, such as batch rating engine, real-time rating engine, and ECE.

The syntax for publishing the components from PDC to the target engines is as follows:

ImportExportPricing -publish [Component] [ObjectType1,ObjectType2,…] -target Target_Engine

where:

■ [Component] is the following:

– metadata

– config

– pricing

– all

■ [ObjectType] is the component type; for example, BALANCE_ELEMENT. You can specify [Component] or [ObjectType] for publishing the components. For the list of component types, see the discussion about the ImportExportPricing utility in PDC User’s Guide.

■ Target_Engine is the following:

– rre

– bre

– ece

– all

For example:

■ You can publish all the setup components in PDC to ECE by running the following command:

ImportExportPricing -publish config -target ece

All the setup components in PDC are published to ECE.

■ You can publish only the balance elements in PDC to ECE by running the following command:

ImportExportPricing -publish BALANCE_ELEMENT -target ece

All the balance elements in PDC are published to ECE.

For more information on using the ImportExportPricing utility to import or export components from PDC, see the discussion about the ImportExportPricing utility in PDC User's Guide.

Support for NOT Operator in Discount Filters (Patch Set 9)

New Features 1-29

Support to Skip Errors and Continue Pricing Objects Migration (Patch Set 9)

In previous releases, when a critical error was encountered while migrating pricing objects from BRM to PDC, the migration process failed with errors.

With this enhancement, you can run the MigrateBRMPricing utility with -skip parameter to skip critical errors encountered during pricing objects migration and continue the migration process.

Important: You can use the -skip parameter only if you are migrating BRM pricing objects to PDC with ECE.

Critical errors encountered due to configuration objects cannot be skipped by using the -skip parameter. You need to manually fix the errors and then restart the migration process.

Typically, the migration process stops if critical errors are encountered. For pricing objects, you can run the MigrateBRMPricing utility with the -skip parameter to skip the critical errors encountered and continue the migration process. You can use the -skip parameter with -pricing, -product, -discount, and -sponsorship parameters. For example:

MigrateBRMPricing -product -skip

When you run the MigrateBRMPricing utility with -skip parameter, you are warned to ensure that you would want to skip objects and continue migration with errors. If you enter Y (yes), you are prompted to enter the encrypted password for the migration cross-reference database and the migration process is started after you provide the password. If you enter N (no), the migration process stops.

Running the MigrateBRMPricing utility with the -skip parameter:

1. Skips the following objects if there are critical errors encountered for these objects during the migration analysis phase: price selectors, Access Point Name (APN) selectors, price models, time models, usage scenario (USC) selectors, discount selectors, discount filters, and discount triggers.

2. Creates dummy objects for the following pricing objects while migrating the data: charges, discounts, discount selectors, charge selectors, and chargeshares.

You can find the dummy objects in the XML files in the BRM_Integration_Pack_Home/apps/migration/xml/pdc directory. After you complete the migration, you can search for the dummy objects in the PDC UI and fix the values.

Note: Dummy objects for charges and discounts are created with the pricing as 0 (zero) and the description as MIGRATION_DUMMY_OBJ.

For more information on the MigrateBRMPricing utility, see the discussion about MigrateBRMPricing in PDC Pricing Migration Guide.

Support for NOT Operator in Discount Filters (Patch Set 9)In previous releases, the NOT (!) operator was not supported in the discount filter fields in PDC.

Support for NOT Operator in Discount Filters (Patch Set 9)


With this enhancement, the NOT operator is supported for all discount filter fields in PDC. The NOT operator specifies the values in the discount filter fields that have to be excluded.

You can set the NOT operator for all discount filters in XML files and then import the XML files into the PDC database by using the ImportExportPricing utility. For more information, see the discussion about importing and exporting pricing and setup components in PDC User’s Guide.

In the PDC UI, you can set the NOT operator only for the following discount filter fields:

■ GLID

■ Time Period

■ Impact Category

■ Generic Selector

For information on configuring discount filters in the PDC UI, see the PDC Online Help.

The discount filter field names are named differently in the XML file and the PDC UI. Only some of the discount filter fields appear in the PDC UI. Table 1–3 displays the supported discount filter field names in the XML file and the corresponding UI field names. In the table, NA specifies that the field does not appear in the PDC UI.

Table 1–3 Discount Filter Field Names—XML Field Names vs UI Field Names

XML Field Name UI Field Name

balanceElementNumCode Balance Element

chargeRatePlanName NA

genericSelectorResult Generic Selector

glid GLID

priceModelName NA

pricingName Pricing Name

rumName Measured By

timeModelName Time Period

timeModelTagName NA

zoneModelName NA

zoneResult Impact Category

In the XML file, select the NOT operator and then specify the values that need to be excluded as shown in the following examples:

<balanceElementNumCode> !BE840</balanceElementNumCode>

where !BE840 is the name of the balance element number code that needs to be excluded.

<pricemodel>

Support for Single Currency Graph (Patch Set 9)

New Features 1-31

!(PrMo125|PrMo135|PrMo450)</pricemodel>

where !PrMo125, PrMO135, and PrMo450 are the names of the price models that need to be excluded.

<chargeRatePlanname> !rate_plan1</chargeRatePlanname>

where !rate_plan1 is the name of the rate plan that needs to be excluded.

<rumName> !Duration10</rumName>

where !Duration10 is the name of the RUM that needs to be excluded.

<timeModelName> !TimeModel_Test</timeModelName>

where !TimeModel_Test is the name of the time model that needs to be excluded.

 <zoneResult> !CUZ</zoneResult>

where !CUZ is the zone that needs to be excluded.

For more information, see the discussion about discount rules in PDC User’s Guide.

Support for Single Currency Graph (Patch Set 9)In previous releases, only one type of currency balance element could be added for a pricing tier.

With this enhancement, you can add multiple currency balance elements for subscriber currencies under a single pricing tier by using the ImportExportPricing utility.

To enable a single currency graph:

1. Go to the PDC_Home/apps/bin directory.

2. Export the pricing data by running the ImportExportPricing utility.

For example, to export the data to a file named chargeoffer_pricing.xml, run the following command:

./ImportExportPricing -export chargeoffer -pricing

3. In the chargeoffer_pricing.xml file, search for the balanceElementNumCode attribute. By default, only one currency code is available. You can add more currency codes.

For example:

-<subscriberCurrency> <currencyCode>USD</currencyCode> <currencyCode>EUR</currencyCode>

Support for Single Currency Graph (Patch Set 9)


-<applicableRum> <applicableRumName>Duration</applicableRumName> <minQuantity>1.0</minQuantity> <minQuantityUnit>NONE</minQuantityUnit> <incrementQuantity>1.0</incrementQuantity> <incrementQuantityUnit>NONE</incrementQuantityUnit> <roundingMode>NEAREST</roundingMode> -<crpRelDateRange> -<absoluteDateRange> <startDate>0</startDate> <endDate>inf</endDate> </absoluteDateRange> -<crpCompositePopModel> <name>Pricing</name> -<usageChargePopModel> -<priceTier> <distributionMethod>FROM_BAL_IMPACT</distributionMethod> -<tierBasis> <rumTierExpression/> </tierBasis> <enforceCreditLimit>false</enforceCreditLimit> <rumName>Duration</rumName> <currencyCode>USD</currencyCode> -<priceTierValidityPeriod> <lowerBound>0</lowerBound> <validFrom>0</validFrom> -<priceTierRange> <upperBound>NO_MAX</upperBound> -<scaledCharge> <price>0.0</price> <unitOfMeasure>NONE</unitOfMeasure> <balanceElementNumCode>840</balanceElementNumCode> <discountable>true</discountable> <priceType>CONSUMPTION</priceType> <incrementStep>1.0</incrementStep> <incrementRounding>NONE</incrementRounding> </scaledCharge> </priceTierRange> </priceTierValidityPeriod><applicableQuantity>ORIGINAL</applicableQuantity></priceTier></usageChargePopModel></crpCompositePopModel></crpRelDateRange></applicableRum></subscriberCurrency>

4. Save the XML file as import_pricing.xml file.

5. Import the import_pricing.xml file by using the ImportExportPricing utility.

For example:

./ImportExportPricing -import -pricing import_pricing.xml -ow

6. In the PDC UI, add, edit, or remove balance impacts for all the supported subscriber currencies.

For more information, see the discussion about importing and exporting pricing and setup components in PDC User’s Guide.

Support for Single RUM Graph (Patch Set 9)

New Features 1-33

Support for Single RUM Graph (Patch Set 9)In previous releases, PDC supported only the multi-RUMs graph for migration.

The multi-RUMs graph includes all the RUMs for a charge offer. When a large number of RUMs are configured for a charge offer, migrating the multi-RUMs graph from BRM into PDC consumes a lot of time. This impacts the migration process.

To optimize the migration process, you can now create a single-RUM graph with multiple RUMs in PDC.

To enable a single-RUM graph:

1. In the Offers section, select Create Charge Offer.

The Create Charge Offer page appears.

2. In the General Information section, provide a Name and Description for the charge offer.

3. Select the Type of the charge offer.

4. Select the Applicable To service.

5. In the Charges section, click the Add Charge list and select Add New Charge.

The Create Charge dialog box appears.

6. From the Charge Category list, select the Usage event category to which the charge applies.

7. From the Charge Type list, select the type of event to which the charge applies.

8. From the Pricing Profile list, select a pricing profile for the charge.

9. From the Measured By list, select the RUMs to use in the charge.

10. Select the Using same pricing rule for all RUMs check box to create a single- RUM graph for all RUMs.

11. From the Currency list, select the charge currency.

This step does not apply to rollover charges.

12. (Optional) Enter a name for the charge.

If you leave this field blank, PDC generates a name.

13. From the Stop Charging list, select when to stop applying the charge to an account.

14. (Optional) In the Taxation section, specify when to apply taxes and enter a tax code.

This step does not apply to rollover charges.

15. (Usage charges only) In the Advanced section, specify settings for processing events.

16. Click OK.

You can now configure pricing for the charge.

When you create a charge offer with a single RUM graph, the PDC UI shows a complete RUM graph of the single charge offer with multiple RUMs. Each RUM appears in its own tab and represents a price tier.

For more instructions, see the discussion about charge offers and adding charges to a charge offer in the PDC Online Help.

PDC Now Allows You to Create Account-Level Charge Offers, Chargeshare Offers and Discount Offers for ECE (Patch Set 8)


PDC Now Allows You to Create Account-Level Charge Offers, Chargeshare Offers and Discount Offers for ECE (Patch Set 8)

With this enhancement, you can now create account-level charge offers, chargeshare offers, and discount offers when you are using ECE for usage rating.

For more information about creating account-level charge offers or discount offers, see PDC User's Guide.

Simplified Process to Configure New Services and Events (Patch Set 7)With this enhancement, creating new services and events when using ECE for usage rating contains fewer steps.

In PDC, you can now enrich the events that are created in Developer Center and publish them to ECE for processing usage requests. You need not manually create and reformat request specification files in ECE.

For more information, see the discussion about enriching event definitions in PDC User’s Guide.

Migrating Pricing Data to a BRM System with PDC and ECE (Patch Set 7)If you use BRM with real-time and batch rating engines with either PDC or Pricing Center, you can now use the migration utility to migrate the pricing data to a BRM system that uses PDC and ECE.

For information about the migration process and the migration utility, see PDC Pricing Migration Guide.

Truncation and Rounding in Discount Expressions (Patch Set 7)PDC now supports truncation and rounding of elements in discount expressions. You can use the Round, Round Up, Round Down, or Round Bankers element to specify the precision for rounding or truncating a discount expression.

For more information, see the discussion about discount expressions in PDC User’s Guide.

Minimum Charges, Price Overrides, Effective Periods, and Relative Date Ranges (Patch Set 7)

You can now do the following in PDC even when you are using ECE for usage rating:

■ Specify minimum charges

■ Override balance impacts for a prerated event by adjusting or replacing the amount charged

■ Use effective periods for pricing

■ Use relative date ranges in a charge

For more information, see PDC User’s Guide. For instructions on how to specify or use these, see the PDC Help.

Special Pricing for Members of Closed user Groups (Patch Set 6)

New Features 1-35

Select Bill Items Based on Business Profiles (Patch Set 7)You can now associate bill item types to business profiles in the item type selector. This enables you to aggregate balance impacts based on the subscriber's business profile.

For information about item type selectors, see the discussion about configuring item type selectors in PDC User’s Guide.

Charge, Discount, APN, and USC Selectors Supported by ECE (Patch Set 7)

You can now use the following specialized selectors even when you are using ECE for usage rating: charge selectors, discount selectors, usage scenario (USC) selectors, and access point name (APN) selectors.

For instructions on how to create charge selectors, discount selectors, USC selectors, and APN selectors, see the PDC Help.

Changesets for Setup Components (Patch Set 7)You can now create, modify, and submit setup components in a changeset. This enables you to save new and modified setup components as drafts until they are ready to be submitted.

For more information, see the discussion about changesets in PDC User’s Guide.

Effective Periods for Conditional Balance Impacts (Patch Set 7)You can now align the start time of a conditional balance impact period with the start time of the associated charge offer, the start of a calendar day, or the event occurrence.

For conditional balance impacts that credit noncurrency balance elements, you can specify whether the balance is available from the start time of the conditional balance impact period or from the time the event occurs.

For more information, see the discussion about conditional balance impacts in PDC User’s Guide.

PDC Now Allows You to Configure Item Type Selectors (Patch Set 6)If you are using ECE for usage rating, you can now assign different bill items for balance impacts within the same event by configuring item type selectors. For example, you can define separate bill items for international and national calls and apply a different tax to each bill item at billing time.

For information about configuring item type selectors, see the discussion about configuring item type selectors in PDC User’s Guide.

Special Pricing for Members of Closed user Groups (Patch Set 6)PDC now allows you to configure special pricing for events between members of a closed user group. For example, you can configure a closed user group for applying special rates on calls between members of that group.

For information about setting up closed user groups, see the discussion about configuring closed user groups in PDC User’s Guide.

PDC Now Allows You to Configure Conditional Balance Impacts (Patch Set 5)


PDC Now Allows You to Configure Conditional Balance Impacts (Patch Set 5)

You can now configure a conditional balance impact to credit or debit a customer’s balance when the customer uses a charge offer for the first time within a specified number of days. The days can be either calendar days or days from the event time.

For example, you can configure conditional balance impacts, instead of using recurring events, to grant daily included minutes to a customer.

Conditional balance impacts are applicable only for charges with the Convergent Usage pricing profile.

For more information, see the discussion about conditional balance impacts in PDC User’s Guide.

Balance Elements Can Now Be Created in the PDC UI (Patch Set 5)You can now create, modify, or delete balance elements in the PDC UI.

For more information, see the discussion about creating balance elements in the PDC Help.

PDC Now Provides a Migration Utility for Migrating BRM Pricing Data to PDC (Patch Set 4)

PDC now supports the migration of existing BRM pricing data to the PDC database. The new migration utility, MigrateBRMPricing, migrates the configuration and pricing objects from the BRM database to the PDC database.

For information about the migration process and the migration utility, see PDC Pricing Migration Guide.

Discounts Can Now Be Filtered Based on the Pricing Name (Patch Set 4)You can now filter discounts based on the Pricing Name value in the Pricing Details section of the Charge tab.

For more information, see the discussion about creating a discount filter in the PDC Help.

Discounts Can Now Be Filtered Based on the Impact Category in the Charge Selector (Patch Set 4)

You can now filter discounts based on the impact category specified in the charge selector rules.

For more information, see the discussion about creating charge selector rules and creating a discount filter in the PDC Help.

PDC Now Displays Offers by Service (Patch Set 4)You can now view the number of offers, sorted by service, in your product catalog by clicking Offers by Service in the Analytics section of the navigation pane.

For more information, see the discussion about viewing a chart of offers by service in the PDC Help.

Multiple Balance Elements and G/L IDs Are Supported in Discount/Chargeshare Filters (Patch Set 3)

New Features 1-37

PDC Now Allows You to Configure Some of the Selectors Without Specifying a Service or an Event (Patch Set 4)

When creating a discount selector or a price selector, if you want to use only customer attributes in the selector rules, you no longer need to specify a service or an event. In this case, the selector can be used in a charge with any service or event. If you want to use service or event attributes in the selector rules, you need to specify the service or event.

When creating a USC selector or an APN selector, you no longer need to specify a service or an event. The event attributes in the selector are validated against the event attributes of the charge when the selector is included in a charge.

For more information, see the discussion about creating a price selector, a discount selector, a USC selector, or an APN selector in the PDC Help.

PDC Now Provides a Web Service to Create or Update Pricing Components (Patch Set 4)

You can now create or update pricing components by using the PDC Web service.

For more information, see the discussion about creating pricing components by using the PDC Web service in PDC User’s Guide.

Regular Expressions Can Now Be Used for G/L IDs in Discount Filters (Patch Set 4)

When configuring general ledger (G/L) IDs in the discount filter, in addition to selecting multiple values from the list, you can now enter a specific value or use a regular expression to match a pattern.

For more information, see the discussion about creating a discount filter in the PDC Help.

Complex Expressions Are Supported in Discount/Chargeshare Triggers (Patch Set 3)

In previous releases, you could add only one element to an expression for a discount or chargeshare trigger.

You can now add multiple elements to an expression using the new Expression field in the Expression Builder dialog box. In this field, you can enter elements, standard arithmetic operators, and decimal constants.

For more information, see the discussions about creating a discount trigger and creating a chargeshare trigger in the PDC Help.

Multiple Balance Elements and G/L IDs Are Supported in Discount/Chargeshare Filters (Patch Set 3)

In previous releases, to add multiple balance elements and G/L IDs as criteria for applying a discount or chargeshare, you had to configure multiple discount or chargeshare filters.

You can now add multiple balance elements and G/L IDs to a single discount or chargeshare filter.

Multiple RUMs Are Supported in Charge Selectors (Patch Set 3)


For more information, see the discussions about creating a discount filter and adding a new chargeshare filter in the PDC Help.

Multiple RUMs Are Supported in Charge Selectors (Patch Set 3)In previous releases, you could select only one ratable usage metric (RUM) in the Measured by field in the Create Charge Selector page.

You can now select multiple RUMs in the Measured by field in the Create Charge Selector page.

For more information, see the discussions about creating a charge selector in the PDC Help and about measuring events in PDC User’s Guide.

Customer Segment and Type Can Be Specified in the Package List (Patch Set 3)

When creating a package list, you can now specify segment and type, which together determine the package list name when the package list is used in Customer Center.

For more information, see the discussion about specifying the package list segment and type in PDC User’s Guide.

PDC Now Displays Successfully Submitted Changesets (Patch Set 3)PDC now displays successfully submitted changesets. You can view the list of the successfully submitted changesets by moving the mouse over the Successfully Submitted link in the Workspace task pane.

For more information, see the discussion about submitting a changeset in the PDC Help.

2

Utility Changes 2-1

2Utility Changes

This chapter provides an overview of the utility changes introduced in Oracle Communications Pricing Design Center (PDC) 11.1 Patch Set 3 through PDC 11.1 Patch Set 12.

New UtilitiesTable 2–1 lists the utilities introduced in PDC 11.1 Patch Set 3 through PDC 11.1 Patch Set 12.

Table 2–1 New Utilities

New Utility Description

MigrateBRMPricing (Patch Set 4) Migrates the configuration and pricing objects from the BRM database to the PDC database.

See the discussion about MigrateBRMPricing in PDC Pricing Migration Guide for more information.

Changed UtilitiesTable 2–2 lists the utilities that were changed in PDC 11.1 Patch Set 3 through PDC 11.1 Patch Set 12.

Table 2–2 Changed Utilities

New Utility Description

ImportExportPricing (Patch Set 12) Modified by including the following parameter:

■ -brmobject. Exports the components mastered in BRM from PDC into XML files.

Note: You cannot use the -brmobject parameter to import components into PDC.


ImportExportPricing (Patch Set 11) Modified by including the following parameter:

■ -ignoreID. Ignores the internal IDs in the input XML file and imports the pricing components by the input file name.


ImportExportPricing (Patch Set 10) Modified by including the following parameters:

■ -keep. Keeps only the latest versions of successfully promoted PDC components and deletes old versions of PDC components that are no longer used by PDC or the associated target engines (for example, ECE).

■ -inclFailedObjs. Exports the most current promoted components and the failed components as well. To export only the successfully promoted and transformed versions of the components, run the ImportExportPricing utility without the inclFailedObjs parameter.


ImportExportPricing (Patch Set 9) Modified by including the following parameters:

■ -publish Component. Publishes the Component in PDC to the target engines specified, where Component is the following: metadata, config, pricing, or all. You can use this parameter to publish metadata, setup components, and pricing components in PDC.

■ -target Target_Engine. Specifies the Target_Engine to which the components have to be published from PDC, where Target_Engine is the following: rre, bre, ece, or all. You can use this parameter to publish the PDC components to the batch rating engine, real-time rating engine, and Oracle Communications Billing and Revenue Management Elastic Charging Engine (ECE).


MigrateBRMPricing (Patch Set 7) Modified to migrate the configuration and pricing objects from the BRM database to the PDC database or from the PDC database to another PDC database.

See the discussion about MigrateBRMPricing in PDC Pricing Migration Guide for more information.

Changed Utilities


3

Known Problems 3-1

3Known Problems

This chapter provides an overview of the known problems in Oracle Communications Pricing Design Center (PDC) 11.1 Patch Set 2 through PDC 11.1 Patch Set 12.

Fixed Known ProblemsTable 3–1 lists the known problems in previous patch sets that are now fixed.

Table 3–1 Known Problems Fixed

SR Number Bug Number Resolution

Not Applicable 25918824 (Patch Set 11) During installation, the PDC Installer now updates the target engine details in the BRM_Integration_Pack_Home/apps/migration/MigrationConfiguration.xml file.

Not Applicable 18484749 (Patch Set 6) When you create a saved search, the search criteria is now saved and the saved search appears in the Saved Searches list in the Search Pricing section.

Note: PDC 11.1 Patch Set 5 did not support saved searches. Therefore, if you had installed PDC 11.1 Patch Set 5, the saved searches created in the earlier patch sets do not appear in the Saved Searches list.

Not Applicable 17635144 (Patch Set 5) You can now install PDC in silent mode and then run the ImportExportPricing utility without any errors.

Not Applicable 17632760 (Patch Set 5) You can now install PDC on Oracle Database 12c.

Not Applicable 17795799 (Patch Set 5) You can now create a bundle and package with the same name in different changesets.

Not Applicable 13494536 (Patch Set 3) Using the Created User field in Advanced Search now displays correct results.

Not Applicable 14581997 (Patch Set 3) You can now map the alias event and the PDC event to the same service.

Not Applicable 14588924 (Patch Set 3) In the Map RUMs dialog box, clicking the disabled Edit icon now does not display the RUM Expression Builder dialog box.

Known ProblemsThis section describes known problems and workarounds for PDC 11.1 Patch Set 12.

Known Problems


Migration Fails Even When the Migration Process is Enabled to Skip ErrorsSR Number: Not applicable

Bug Number: 25943341, 25634869

During migration, when a critical error is encountered while migrating a discount filter or a discount trigger, migration fails with errors even when the migration process is enabled to skip errors and continue migration.

To work around this problem, manually fix the errors encountered during migration and restart the migration process.

You Are Not Warned to Save Your ChangesSR Number: Not applicable

Bug Number: 12717423, 12883782

After modifying a setup or pricing component, you are not warned that you have unsaved changes when you do the following:

■ Close the tab

■ Log out of PDC

If you perform any of the above actions before saving your changes, the changes are lost.

To work around this problem, save your changes before closing a tab or logging out of PDC.

Documents

Oracle Communications Pricing Design Center Release Notes