Oracle Revenue Management and Billing Versin 2.3.0.1.0 E55302-01 August, 2014
Oracle Revenue Management and Billing Versin 2.3.0.1.0 E55302-01 Cpyright Ntice Cpyright 2014, Oracle and/r its affiliates. All rights reserved. Trademark Ntice Oracle and Java are registered trademarks f Oracle Crpratin and/r its affiliates. Other names may be trademarks f their respective wners. Intel and Intel Xen are trademarks r registered trademarks f Intel Crpratin. All SPARC trademarks are used under license and are trademarks r registered trademarks f SPARC Internatinal, Inc. AMD, Optern, the AMD lg, and the AMD Optern lg are trademarks r registered trademarks f Advanced Micr Devices. UNIX is a registered trademark f The Open Grup. License Restrictins Warranty/Cnsequential Damages Disclaimer This sftware and related dcumentatin are prvided under a license agreement cntaining restrictins n use and disclsure, and are prtected by intellectual prperty laws. Except as expressly permitted in yur license agreement r allwed by law, yu may nt use, cpy, reprduce, translate, bradcast, mdify, license, transmit, distribute, exhibit, perfrm, publish, r display any part, in any frm, r by any means. Reverse engineering, disassembly, r de-cmpilatin f this sftware, unless required by law fr interperability, is prhibited. Warranty Disclaimer The infrmatin cntained herein is subject t change withut ntice and is nt warranted t be errrfree. If yu find any errrs, please reprt them t us in writing. Restricted Rights Ntice If this sftware r related dcumentatin is delivered t the U.S. Gvernment r anyne licensing it n behalf f the U.S. Gvernment, the fllwing ntice is applicable: U.S. GOVERNMENT RIGHTS Oracle prgrams, including any perating system, integrated sftware, any prgrams installed n the hardware and/r dcumentatin delivered t U.S. Gvernment end users are cmmercial cmputer sftware pursuant t the applicable Federal Acquisitin Regulatin and agency-specific supplemental regulatins. As such, use, duplicatin, disclsure, mdificatin, and adaptatin f the prgrams, including any perating system, integrated sftware, any prgrams installed n the hardware and/r dcumentatin shall be subject t license terms and restrictins applicable t the prgrams. N ther rights are granted t the U.S. Gvernment. Hazardus Applicatins Ntice This sftware is develped fr general use in a variety f infrmatin management applicatins. It is nt develped r intended fr use in any inherently dangerus applicatins, including applicatins that may ii Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
create a risk f persnal injury. If yu use this sftware in dangerus applicatins, then yu shall be respnsible t take all apprpriate fail-safe, backup, redundancy, and ther measures t ensure the safe use f this sftware. Oracle Crpratin and its affiliates disclaim any liability fr any damages caused by use f this sftware in dangerus applicatins. Third Party Cntent, Prducts, and Services Disclaimer This sftware and dcumentatin may prvide access t r infrmatin n cntent, prducts, and services frm third parties. Oracle Crpratin and its affiliates are nt respnsible fr and expressly disclaim all warranties f any kind with respect t third party cntent, prducts, and services. Oracle Crpratin and its affiliates will nt be respnsible fr any lss, csts, r damages incurred due t yur access t r use f third party cntent, prducts, r services. Cpyright 2014, Oracle and/r its affiliates. All rights reserved. iii
Abut this Dcument This dcument describes the enhancements made in this release. It indicates the changes made t the existing screens in Oracle Revenue Management and Billing. It als highlights the bug fixes and knwn issues in this release. This dcument des nt describe the functinality f Oracle Revenue Management and Billing r technical knw-hw n hw t install r upgrade Oracle Revenue Management and Billing. Fr mre detailed infrmatin, yu can refer t the fllwing dcuments: Dcument Oracle Revenue Management and Billing Banking User Guide Oracle Revenue Management and Billing Insurance User Guide Oracle Revenue Management and Billing Installatin Guide Oracle Revenue Management and Billing Quick Installatin Guide Oracle Revenue Management and Billing Database Administratr's Guide ORMB-Dcumaker Integratin Guide fr Banking ORMB-Dcumaker Integratin Guide fr Insurance ORMB - Transactin Feed Management - Batch Executin Guide Lists and describes varius banking features in Oracle Revenue Management and Billing. It als describes all screens related t these features and explains hw t perfrm varius tasks in the applicatin. Lists and describes varius insurance features in Oracle Revenue Management and Billing. It als describes all screens related t these features and explains hw t perfrm varius tasks in the applicatin. Lists the pre-requisites, supprted platfrms, and hardware and sftware requirements fr installing the Oracle Revenue Management and Billing applicatin. It als explains hw t install the Oracle Revenue Management and Billing applicatin. Prvides high-level infrmatin n hw t install the Oracle Revenue Management and Billing applicatin. Prvides detailed infrmatin n hw t install the database fr the Oracle Revenue Management and Billing applicatin. Prvides detailed infrmatin n hw t integrate Oracle Dcumaker with Oracle Revenue Management and Billing s that yu can use Oracle Dcumaker fr the Banking mdule. Prvides detailed infrmatin n hw t integrate Oracle Dcumaker with Oracle Revenue Management and Billing s that yu can use Oracle Dcumaker fr the Insurance mdule. Describes the sequence in which the batches must be executed while perfrming varius tasks in the Transactin Feed Management mdule. iv Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
Dcument ORMB Billing - Batch Executin Guide Oracle Revenue Management and Billing Server Administratin Guide Oracle Revenue Management and Billing Batch Server Administratin Guide Oracle Revenue Management and Billing Security Guide Oracle Revenue Management and Billing Upgrade Guide Oracle Revenue Management and Billing Upgrade Path Guide Oracle Revenue Management and Billing Self Service Guide Oracle Revenue Management and Billing Self Service Installatin and Cnfiguratin Guide Oracle Revenue Management and Billing Reprts Installatin Guide Describes the batches that yu can use fr generating bills in Oracle Revenue Management and Billing. Describes the Oracle Revenue Management and Billing architecture. It als explains hw t cnfigure, deply, and mnitr web and business applicatin servers. Prvides detailed infrmatin n hw t cnfigure and wrk with the batch cmpnent in Oracle Revenue Management and Billing. Describes hw t cnfigure security fr the Oracle Revenue Management and Billing applicatin using the default security features. Explains hw t upgrade the Oracle Revenue Management and Billing framewrk, applicatin, and its database. Explains the path and pre-requisites fr upgrading Oracle Revenue Management and Billing frm ne versin t anther. Explains the sample pages available in the Self Service applicatin and hw t custmize these pages as per the custmer s requirements. Explains hw t install and cnfigure the Self Service applicatin. Explains hw t install reprts in Oracle BI Publisher and ORMB. It als explains hw t create new reprts frm scratch r using the sample reprt as a starting pint. Cpyright 2014, Oracle and/r its affiliates. All rights reserved. v
Cntents Prerequisites...1 New Features...2 Enhancements...3 Transactin Feed Management... 3 Billing... 7 Pricing Management... 9 Payments... 10 On Demand Billing... 10 Pay Plan... 12 User Interface (UI) Level Changes... 13 Supprted Platfrms... 16 Technical Recmmendatins... 17 Framewrk Upgrade... 18 Supprted Upgrades... 19 Discntinued Features... 20 Prduct Dcumentatin... 21 Media Pack Dwnlad... 22 Bug Fixes... 23 Knwn s... 28 Banking... 28 Insurance... 40 Dcumentatin... 42 Technical Supprt... 45 vi Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
Prerequisites If a custmer is already using the Transactin Feed Management feature and wants t upgrade t Oracle Revenue Management and Billing Versin 2.3.0.1.0, then the custmer needs t ensure the fllwing (befre upgrading): All bills generated in the system are in the Cmplete status. In ther wrds, there shuld nt be any bills in the Pending status. If there are any bills in the Pending status r if any billable charge (generated thrugh TFM) is nt yet billed, disaggregatin and cancellatin f transactins which are upladed using 2.3.0.0.0 will nt happen successfully. Transactins which are upladed using 2.3.0.0.0 must nt be in the Initial Prduct Determined (INPD) status. They can be in the Upladed (UPLD), Invalid (INVL), Errr (EROR), Cmpleted (COMP), r Cancelled (CNCL) status. Equal t (=) r tilde (~) symbl is nt used in any existing prduct parameter cde r value. Otherwise, errneus results might ccur. Cpyright 2014, Oracle and/r its affiliates. All rights reserved. 1
New Features N new features are intrduced in this release. 2 Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
Enhancements This sectin lists the enhancements made t the fllwing features: Transactin Feed Management Billing Pricing Management Payments On Demand Billing Pay Plan Transactin Feed Management The fllwing changes are made t the transactin feed management prcess: Earlier, the system allwed multiple accunts t bear the charges fr a transactin prvided these accunts belng t the divisin t which the transactin belngs. But, nw, these accunts can belng t different divisins (and need nt belng t the divisin t which the transactin belngs). Earlier, in the CSV file, if a transactin r any ther user defined currency was ther than the divisin s base currency, the system did the currency cnversin if the apprpriate exchange rate was available in the system. Nw, in the CSV file, if a transactin r any ther user defined currency is ther than the pricing currency, the system will d the currency cnversin if the apprpriate exchange rate is available in the system. The status f the transactin will nt be changed t Errr (EROR) if the base currency is nt defined fr the divisin (t which the transactin belngs). The disaggregatin prcess is redesigned t wrk when the charges fr a transactin are brne by multiple accunts. Nw, t disaggregate transactins f an accunt, yu need t execute the fllwing batches in the specified rder: Disaggregatin Request Creatin (C1-DISTG) Identify Affected Transactins (C1-IAENT) Prcess Nn Aggregated Transactins (C1-PDTXN) Clean Up (C1-TXNCU) Update Disaggregatin Request Status (C1-DARSU) The Disaggregatin Request Creatin (C1-DISTG) batch is ptinal. Yu can directly execute the Identify Affected Transactins (C1-IAENT) batch if the disaggregatin requests are available in the CI_TXN_DISAGG_REQ table. Cpyright 2014, Oracle and/r its affiliates. All rights reserved. 3
Earlier, yu were able t create a disaggregatin request fr an accunt r a custmer nly thrugh the Disaggregatin Request Creatin (C1-DISTG) batch. Nw, yu can als create a disaggregatin request fr an accunt r a custmer manually thrugh a user interface. A new screen named Disaggregatin Request is intrduced in the Transactin Feed Management main menu. The Disaggregatin (C1-TXNDA) batch is n lnger available fr disaggregating transactins f an accunt. Yu can nw define the Prcessing Date fr Transactin Feed Management characteristic fr each divisin. This characteristic is used while executing the fllwing TFM batches: Transactin Validatin and Initial Prduct Determinatin (C1-TXNIP) If the Prcessing Date fr Transactin Feed Management characteristic type f the divisin (t which the transactin belngs) is set t BATCH_DT, the system executes the rules which are effective n the batch business date. Hwever, if the Prcessing Date fr Transactin Feed Management characteristic type f the divisin (t which the transactin belngs) is set t TXN_DT, the system executes the rules which are effective n the transactin date. Prduct Pricing Verificatin (C1-TXNVP) - If the Prcessing Date fr Transactin Feed Management characteristic type f the divisin (t which the accunt belngs) is set t BATCH_DT, the system searches fr the pricing which is effective n the batch business date. Hwever, if the Prcessing Date fr Transactin Feed Management characteristic type f the divisin (t which the accunt belngs) is set t TXN_DT, the system searches fr the pricing which is effective n the transactin date. Service Quantity Calculatin (C1-TXNSQ) and Clean Up (C1-TXNCU) - If the Prcessing Date fr Transactin Feed Management characteristic type f the divisin (t which the accunt belngs) is set t BATCH_DT, the system uses the exchange rate which is effective n the batch business date. Hwever, if the Prcessing Date fr Transactin Feed Management characteristic type f the divisin (t which the accunt belngs) is set t TXN_DT, the system uses the exchange rate which is effective n the transactin date. A sft parameter named Pricing Level is remved frm the Prduct Pricing Verificatin (C1- TXNVP) batch. This sft parameter was earlier added t imprve batch perfrmance. As the Prduct Pricing Verificatin (C1-TXNVP) batch is tuned t prvide better perfrmance in this release, the Pricing Level parameter is n lnger required. Yu can nw use the Clean Up (C1-TXNCU) batch t: Delete and update billable charges fr transactins which are in the Errr (EROR) status Delete and update billable charges while disaggregating transactins Delete and update billable charges while cancelling a transactin feed 4 Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
Earlier, the Rule Validatin algrithm was used t check whether the values specified against the utput parameters exist in the system. Nw, it als checks whether the same prduct parameter (fr example, PCD1_1_1_VAL) is nt used multiple times fr a divisin, accunt, and prduct cmbinatin. Earlier, the Parameter Grup Creatin was a distinct sub-prcess in TFM. Nw, it is a part f the Transactin Validatin and Initial Prduct Determinatin sub-prcess. Once the transactin validatin, and initial prduct and parameters mapping is cmplete, the prduct parameters t which the transactin is mapped are gruped. A set f prduct parameters are gruped nly when the multi parameter based pricing feature is enabled. The Parameter Grup Creatin (C1- PRMGC) batch is n lnger supprted frm this release nwards. A sft parameter named Disaggregate Transactins Frm Date is added in the fllwing batches: Identify Affected Transactins (C1-IAENT) Prcess Nn Aggregated Transactins (C1-PDTXN) Clean Up (C1-TXNCU) Update Disaggregatin Request Status (C1-DARSU) The fllwing tw sft parameters are added in the Rllback (C1-TXNRB) batch: Rllback Frm Date Rllback T Date The transactin aggregatin prcess is redesigned t enfrce the rder in which the batches must be executed. Nw, The system allws yu t execute each batch cnsecutively. Yu can execute the Transactin Validatin and Initial Prduct Determinatin batch cnsecutively with the same divisin and same parameters, r with the different divisin and different parameters. But, yu cannt execute the Transactin Validatin and Initial Prduct Determinatin (C1-TXNIP) batch cnsecutively with the same divisin and different parameters. Fr example, nce yu execute this batch with divisin as D1 and transactin surce as S1, yu cannt execute this batch again with divisin as D1 and transactin surce as S2. Once the Prduct Pricing Verificatin (C1-TXNVP) batch is executed, yu cannt execute the Transactin Validatin and Initial Prduct Determinatin (C1-TXNIP) batch again with the same divisin and same parameters unless and until the transactin aggregatin cycle is cmplete. During the transactin aggregatin prcess, yu must specify the same divisin and same parameters acrss each batch. Otherwise, errneus results might ccur. If yu have already executed the Transactin Validatin and Initial Prduct Determinatin (C1-TXNIP) batch withut any divisin, then yu cannt execute this Cpyright 2014, Oracle and/r its affiliates. All rights reserved. 5
batch nce again with a divisin unless and until the transactin aggregatin cycle is cmplete. The fllwing tw tables are partitined based n the CURR_SYS_PRCS_DT primary key: CI_TXN_DETAIL CI_TXN_DTL_PRITM Therefre, nw, when yu execute the Transactin Validatin and Initial Prduct Determinatin (C1-TXNIP) batch n different dates, a partitin is created fr each date n the table. Fr example, when yu execute the Transactin Validatin and Initial Prduct Determinatin (C1-TXNIP) batch n 1 st Aug, 2 nd Aug, and 3 rd Aug, three partitins are created n the table ne fr the respective date. But, when yu execute the Transactin Validatin and Initial Prduct Determinatin (C1-TXNIP) batch multiple times (with same and different divisin and/r parameters) n the same date, the prcessed data will be n the same partitin. All ther aggregatin batches (such as, C1-TXNVP, C1-TXNEX, C1-TXNSQ, C1-TXNCM, and C1- TXNCU) will refer t ne r mre table partitins and prcess the data accrdingly. If yu are executing all batches n 1 st Aug, each batch will refer t the 1 st Aug partitin n the table. But, if yu are executing the Transactin Validatin and Initial Prduct Determinatin (C1-TXNIP) batch n 1 st Aug, 2 nd Aug, and 3 rd Aug and the Prduct Pricing Verificatin (C1-TXNVP) batch n 3 rd Aug, then the C1-TXNVP batch will prcess the data available n three partitins - 1 st Aug, 2 nd Aug, and 3 rd Aug. This means that each batch will refer t a range f partitins whse data is nt yet prcessed. Nw, the system allws yu t cache the prduct pricing infrmatin which can then be used by the Prduct Pricing Verificatin (C1-TXNVP) batch. This helps t imprve the batch perfrmance. If yu set the Materialized View Used ptin type f the C1_FM feature cnfiguratin t true, the system will cache the prduct pricing infrmatin in the fllwing tables: CI_PRC_AGRD CI_PRC_PL CI_PRC_INH_PL But, if yu set the Materialized View Used ptin type f the C1_FM feature cnfiguratin t false, the system will nt cache the prduct pricing infrmatin. If there are any pricing changes, we have t update this cache befre executing the Prduct Pricing Verificatin (C1-TXNVP) batch. A batch named Refresh Pricing (C1-TXNRP) is intrduced which will help t update the prduct pricing infrmatin in the cache. Ideally, yu must execute this batch after yu execute the Flush All Caches (F1-FLUSH) batch during the transactin aggregatin prcess. 6 Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
Billing The fllwing changes are made t the billing feature: If a billable charge is generated autmatically thrugh the transactin feed management r n demand billing prcess, yu cannt edit the details f the billable charge. Yu can nly cancel the billable charge, if required. The Bill Cycle (BILL-CYC-CD) parameter is added in the Billing (BILLING) batch. It is used when yu want t generate bills fr accunts having a particular bill cycle. In the BILLING batch, multi-threading is based n Accunt ID and chunks fr multi-threading are created based n numerical distributin f Accunt ID. This chunking lgic might nt be efficient while handling vluminus data. T handle high vlume with better perfrmance, yu must generate bills using the fllwing three batches (in the specified rder): 1. Pending Bill Generatin (C1-PNDBL) This batch is used t generate pending bills fr accunts that meet the criteria. 2. Bill Segment Generatin (C1-BLGEN) This batch is used t generate the bill segments. 3. Bill Cmpletin (C1-BLPPR) This batch is used t generate pst prcessing bill segments during the bill cmpletin prcess and change the status f the bill t Cmplete. These three are multi-threaded batches. They are primarily designed and develped fr the Banking and Payments industries. Fr mre infrmatin abut these batches, refer t the ORMB Billing - Batch Executin Guide. Initially, yu were nt able t cntrl the rder in which bill segments were generated during the billing prcess. Nw, using the Bill Segment Generatin (C1-BLGEN) batch, yu can generate bill segments in a particular rder f imprtance. This batch allws yu t specify the billing prcessing sequence f the cntract s cntract type whse bill segments yu want t generate. Yu can delete a bill cycle nly if it is nt assciated t any divisin. There is a change in the lgic fr calculating the pst prcessing bill segment start and end dates. Nw, the system finds the bill segment whse start date is earlier than all ther bill segments start date in the bill and then cnsiders this date as the pst prcessing bill segment start date. Similarly, the system finds the bill segment whse end date is later than all ther bill segments end date in the bill and then cnsiders this date as the pst prcessing bill segment end date. Initially, yu were able t generate a bill using the billable charges whse start date is earlier than r equal t the cut-ff date. Nw, yu can generate a bill using the billable charges whse start r end date is earlier than r equal t the cut-ff date. If yu want t cnsider the billable charges whse start date is earlier than r equal t the cut-ff date, yu must set the Billable Charges Date ptin type f the C1_FINTRANOP feature cnfiguratin t S. And, if yu want t cnsider the billable charges whse end date is earlier than r equal t the cut-ff date, yu Cpyright 2014, Oracle and/r its affiliates. All rights reserved. 7
must set the Billable Charges Date ptin type f the C1_FINTRANOP feature cnfiguratin t E. A new ptin type named Bill Segment Regeneratin n Freeze is added and the Billing Pst Prcessing Optin type is remved frm the C1_FINTRANOP feature cnfiguratin. If yu want t regenerate the bill segments befre freezing them, yu must set the Bill Segment Regeneratin n Freeze ptin type f the C1_FINTRANOP feature cnfiguratin t Y. Hwever, if yu d nt want t regenerate the bill segments befre freezing them, yu must leave the Bill Segment Regeneratin n Freeze ptin type blank. The Prcess Only Frzen FTs (FROZEN-FT-SW) parameter is added in the Assign GL Accunt t Financial Transactin (GLASSIGN) batch. It is used t indicate whether yu want t assign GL accunt nly t frzen financial transactins. If yu set the value f this parameter t Y, GL accunt is assigned nly t frzen financial transactins. Hwever, if yu want t assign GL accunt t bth frzen and freezable financial transactins, yu must leave this field blank. In the GLASSIGN batch, multi-threading is based n FT_ID and chunks fr multi-threading are created based n numerical distributin f FT_ID. This chunking lgic might nt be efficient while handling vluminus data. T handle high vlume with better perfrmance, yu must assign GL accunt t financial transactins using the fllwing tw batches (in the specified rder): 1. Insert Recrds in CI_FTTEMP (GLASSGN1) This batch is used t search and add the frzen and/r freezable financial transactins (FTs) (where the GL accunt is nt yet assigned) in the CI_FTTEMP table. The data in this table is used fr creating chunks fr multi-threading. Yu can specify the fllwing parameters while executing this batch: Parameter Name Mandatry (Yes r N) Thread Cunt N Used t specify the number f threads yu want t spawn in parallel. Override Maximum Number f Errrs Prcess Only Frzen FTs N N Used t verride the maximum number f errrs after which the batch must be terminated. Used t indicate whether yu want t assign GL accunt nly t frzen financial transactins. If yu set the value f this parameter t Y, GL accunt is assigned nly t frzen financial transactins. Hwever, if yu want t assign GL accunt t bth frzen and freezable financial transactins, yu must leave this field blank. 2. Assign GL Accunt t Financial Transactin (GLASSGN2) This batch is used t assign GL accunt t frzen and/r freezable financial transactins which are stred in the CI_FTTEMP table. This is a multi-threaded batch where financial transactins are equally distributed in each chunk (wrk unit). If the GL accunt is nt successfully assigned any financial transactin, an errr is lgged and T D is created fr the crrespnding 8 Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
Parameter Name financial transactin. Yu can specify the fllwing parameters while executing this batch: Mandatry (Yes r N) Thread Cunt N Used t specify the number f threads yu want t spawn in parallel. Override Maximum Number f Errrs Prcess Only Frzen FTs N N Used t verride the maximum number f errrs after which the batch must be terminated. Used t indicate whether yu want t assign GL accunt nly t frzen financial transactins. If yu set the value f this parameter t Y, GL accunt is assigned nly t frzen financial transactins. Hwever, if yu want t assign GL accunt t bth frzen and freezable financial transactins, yu must leave this field blank. Nte: Yu must specify same parameters in the GLASSGN1 and GLASSGN2 batches. Otherwise, errneus results will be generated. The system enables yu t create a FT in divisin s base currency if the accunt s invice currency is different frm the divisin s base currency. Accrdingly, an entry is lgged in the CI_FT_GL_EXT table. Earlier, t enable this functinality, yu had t attach an algrithm f the C1-SATPBLPPS algrithm type n the Bill Pst-Prcessing system event f the cntract type fr which yu want t create FT in divisin s base currency (FT GL Extensin). Nw, t enable this functinality, yu will have t attach an algrithm f the C1-SATPBLPPS algrithm type n the FT Freeze system event f the custmer class. The system will then create FT in divisin s base currency (FT GL Extensin) fr all custmers wh belng t the respective custmer class. A new screen named Billed Revenue is added in the Financial Query menu. It allws yu t view the ttal adjustment and bill segment amunt which is billed r cancelled in a particular duratin. In ther wrds, yu can view infrmatin abut different types f financial transactins which are frzen in a particular duratin. The data is gruped based n the currency and distributin cde. Yu can view the details f all adjustments r nly thse adjustments which are fetched n the bill. Pricing Management The fllwing changes are made t the pricing management feature: Earlier, the system did nt allw yu t add same set f prducts using the same relatinship type while defining tw r mre bundles r prduct t prduct relatinships. Nw, yu can add same set f prducts using the same relatinship type while defining tw r mre prduct t prduct relatinships. Fr example, yu can add P1 and P2 using the same relatinship type, such as Service, Service Grup, r Prduct while defining prduct relatinship fr PN1 and PN2. Cpyright 2014, Oracle and/r its affiliates. All rights reserved. 9
But, yu cannt add P1 and P2 using the same relatinship type, such as Bundle, Numeratr r Denminatr while defining regular bundles named BUN1 and BUN2. Payments The fllwing changes are made t the payments feature: Yu can nw edit the characteristics f a payment even when it is in the Frzen r Cancelled status. On Demand Billing The fllwing changes are made t the n demand billing feature: The fllwing prcesses are redesigned t supprt a usage data file with large number f recrds: Uplading a Usage Data File Earlier, a usage data file was upladed and validated nly in the nline mde. But, nw, if the usage data file size exceeds the value derived by multiplying average recrd size and transactin limit, the usage data file is upladed and validated thrugh a batch prcess. A batch jb is created using the Uplad and Validate Usage Data File (C1-ODFU) batch. Revalidating a Usage Data File Earlier, a usage data file was revalidated nly in the nline mde. But, nw, if the usage data file size exceeds the value derived by multiplying average recrd size and transactin limit, the usage data file is revalidated thrugh a batch prcess. A batch jb is created using the Uplad and Validate Usage Data File (C1-ODFU) batch. Submitting the Valid Recrds On clicking the Submit buttn, the system creates a billable charge fr each valid recrd either in the nline mde r thrugh a batch prcess. If the ttal number f valid recrds in a usage data file exceeds the transactin limit, a billable charge fr each valid recrd is created thrugh a batch prcess. A batch jb is created using the Billable Charge Creatin (C1-ODBCH) batch. Apprving the Valid Recrds - On clicking the Apprve buttn, the system creates a billable charge fr each apprved recrd in the nline mde. Whereas, n clicking the Apprve All buttn, the system creates a billable charge fr each apprved recrd either in the nline mde r thrugh a backgrund prcess. If the ttal number f recrds that yu want t apprve exceeds the transactin limit, a billable charge fr each apprved recrd is created thrugh a batch prcess. A batch jb is created using the Billable Charge Creatin (C1-ODBCH) batch. Nte: Yu can change the transactin limit, whenever required, using the On Demand Billing (C1 ODBFC) feature cnfiguratin. 10 Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
The fllwing new prcesses are designed t enhance the user experience: Generating Adhc Bills Earlier, the adhc bills were generated n submitting and apprving the valid recrds when the bill after date was equal t r earlier than the current date. Nw, the Generate Bill buttn is available crrespnding t each usage data file in the On Demand Billing screen. On clicking the Generate Bill buttn, yu can generate adhc bills fr a usage data file when the bill after date is equal t r earlier than the current date. If the ttal number f billable charges created fr a usage data file exceeds the nline bill creatin limit, adhc bills are generated fr the usage data file thrugh a backgrund prcess. A batch jb is created using the Adhc Billing (C1-FABL) batch. Freezing and Cmpleting Adhc Bills Oracle Revenue Management and Billing prvides yu with the ability t freeze and cmplete adhc bills generated fr a usage data file frm the On Demand Billing screen. Yu can freeze and cmplete either all r selected adhc bills, whenever required. Hwever, yu cannt freeze and cmplete nrmal r regular bills frm the On Demand Billing screen. The system freezes and cmpletes ne r mre selected adhc bills in the nline mde. But, if yu want t freeze and cmplete all adhc bills f a usage data file, a batch jb is created using the Freeze and Cmplete Adhc Bills (C1-FCADH) batch. The fllwing new batches are created t supprt a usage data file with large number f recrds: Uplad and Validate Usage Data File (C1-ODFU) Billable Charge Creatin (C1-ODBCH) Freeze and Cmplete Adhc Bills (C1-FCADH) The fllwing new ptin types are added in the On Demand Billing (C1-ODBFC) feature cnfiguratin: Average Recrd Size Validatin Chunk Size Staging XML Size Billable Charge Chunk Size Online Bill Creatin Limit The Recrds Per Page ptin type is remved frm the On Demand Billing (C1-ODBFC) feature cnfiguratin. Nw, by default, the number f recrds that appear in the Usage Data and View Bill Data screens depends n the minimum value defined in the PAGE_NUMBER lkup field. Fr example, if the PAGE_NUMBER lkup field has fur values 10, 20, 30, and 40, then the number f recrds displayed in each page, by default, wuld be 10. Cpyright 2014, Oracle and/r its affiliates. All rights reserved. 11
On successful cmpletin f the fllwing batches, a T D entry is created using the respective T D type. This T D indicates whether the batch was successfully executed r nt. Batch T D Type C1-ODFU Uplad and Validate Usage Data File C1-ODFU C1-ODBCH Billable Charge Creatin C1-ODBCH C1-FABL Adhc Billing C1-FABL C1-FCADH Freeze and Cmplete Adhc Bills C1-FCADH Earlier, yu were nly able t reject ne r mre valid recrds and nt all valid recrds (which were pending fr apprval) in a usage data file. Nw, the Reject All buttn is added in the Usage Data screen which allws yu t reject all valid recrds (which are pending fr apprval) in a usage data file. Pay Plan The fllwing changes are made t the pay plan feature: Yu can nw change the maturity date alng with the installment amunt in the invice schedule. Hwever, yu can change the maturity date and amunt nly when the plicy installment is nt yet inviced r cancelled. 12 Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
User Interface (UI) Level Changes The fllwing table lists changes made t the existing screens in Oracle Revenue Management and Billing: Screen Feed Management Dashbard Payment Accunt Financial Histry Accunt Bill/Payment Histry Bill Segment Payment Histry - Search Prtal Changes The fllwing changes are made t this screen: The Bill ID clumn is remved frm the Transactin Level Infrmatin zne. The fllwing changes are made t this screen: The Bill ID clumn is added and the Lcatin clumn is remved frm the Manual Distributin tab. The fllwing changes are made t this screen: The Bill/Payment/Adjustment ID clumn is added in this screen. The fllwing changes are made t this screen: The Bill/Payment ID clumn is added in this screen. The fllwing changes are made t this screen: The Billable Charge ID field is added in the Calc Lines tab. There is a G T buttn crrespnding t this field which helps in navigating t the Billable Charge screen. The fllwing changes are made t this screen: The Payment Histry - Search Prtal screen is renamed t Payment Histry. The Payment Histry - Search Prtal zne is renamed t Search Payments. The Pricing Currency clumn in the search results is renamed t Payment Currency. Cpyright 2014, Oracle and/r its affiliates. All rights reserved. 13
Billable Charge Screen Pricing (Accunt), Pricing (Custmer) Rule Check On Demand Billing View Bill Data Usage Data (while viewing all, prcessed, billed, unbilled and cancelled recrds) Plicy Changes The fllwing changes are made t this screen: The Currency Cde field in the Main tab is renamed t Currency. The Variatin Parameter field in the SQ Details and Pricing Infrmatin tabs is renamed t Variance Parameter. The Price Item Parm Cde field in the Pricing Infrmatin tab is renamed t Prduct Parameter. The Price Item Parm Value field in the Pricing Infrmatin tab is renamed t Prduct Parameter Value. The fllwing changes are made t these screens: Nw, the Rate clumn in the Effective Price Assignment zne als indicates whether the price is a Flat, Threshld, r Step price. The fllwing changes are made t this screen: The Effective Date field is added in this screen. It is used when yu want t execute the rules which are effective n a particular date. The fllwing changes are made t this screen: The Generate Bill, Freeze and Cmplete, and Batch Status clumns are added in the Search Results sectin. The fllwing changes are made t this screen: The Freeze/Cmplete buttn is added in this screen. The fllwing changes are made t this screen: The Billable Charge ID clumn is added in the Search Results sectin. The fllwing changes are made t this screen: The Plicy, Plicy Characteristics, Plicy Persns, and Plicy Cntracts tabs are renamed t Main, Characteristics, Persns, and Cntracts, respectively, in this screen. The End Date field is added in the Cntracts tab. 14 Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
Screen Transactin Details Changes The fllwing changes are made t this screen: The fllwing table lists the clumns which are added in the Search Results sectin: Clumn Name Disaggregatin Status Errr Message Appears when the transactin status is UPLD, INVL, INPD, IGNR, EROR, CNCL, COMP INVL The fllwing table lists the fields which are added in the Search Criteria sectin: Field Name Disaggregated Appears when the transactin status is UPLD, INVL, INPD, IGNR, EROR, CNCL, COMP The Derived Sub-Transactins zne is added in this screen. It allws yu t view the legs f an UPLD, INPD, IGNR, EROR and COMP transactin. Cpyright 2014, Oracle and/r its affiliates. All rights reserved. 15
Supprted Platfrms The fllwing table lists the perating system and applicatin server cmbinatins n which Oracle Revenue Management and Billing Versin 2.3.0.1.0 is supprted: Operating System and Web Brwser (Client) Operating System (Server) Chipset Applicatin Server Database Server Windws 7 (IE 8.x, 9.x r 10.x) AIX 6.1 TL5 (64-bit), AIX 7.1 TL1 (64-bit) POWER 64-bit WebSphere 8.5 (64-bit) Oracle 11.2.0.4 Oracle Linux 5.8, 6.2, 6.4 and 6.5 (64-bit) x86_64 WebLgic 10.3.6.0.8 (64-bit) Oracle 11.2.0.4 Red Hat Enterprise Linux 5.8, 6.2, 6.4 and 6.5 (64-bit) x86_64 WebLgic 10.3.6.0.8 (64-bit) Oracle 11.2.0.4 Windws Server 2008 R2 (64-bit) x86_64 WebLgic 10.3.6.0.8 (64-bit) Oracle 11.2.0.4 Nte: Yu must enable the Cmpatibility View ptin fr Internet Explrer 9.x and 10.x. 16 Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
Technical Recmmendatins T imprve the verall batch perfrmance n Windws, AIX, and Linux platfrms, we recmmend yu t make changes in the fllwing files: File Name Change Frm Change T hibernate.prperties hibernate.c3p0.timeut = 300 hibernate.c3p0.timeut = 600 threadplwrker.sh MEM_ARGS="-Xms512m -Xmx1024m - XX:MaxPermSize=768m" MEM_ARGS="-Xms512m -Xmx4096m - XX:MaxPermSize=768m" Cpyright 2014, Oracle and/r its affiliates. All rights reserved. 17
Framewrk Upgrade Oracle Revenue Management and Billing Versin 2.3.0.1.0 is based n Oracle Utilities Applicatin Framewrk Versin 4.2.0.2.0. This versin f Oracle Utilities Applicatin Framewrk includes many enhancements that were nt available in the previus release f Oracle Revenue Management and Billing. Fr mre infrmatin abut these enhancements, refer t Oracle Utilities Applicatin Framewrk V4.2.0.2.0. 18 Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
Supprted Upgrades In case yu want t upgrade frm Oracle Revenue Management and Billing Versin 2.3.0.0.0 t 2.3.0.1.0, refer t the fllwing dcuments fr mre infrmatin: Oracle Revenue Management and Billing Upgrade Guide Oracle Revenue Management and Billing Upgrade Path Guide Fr upgrading frm any previus versin f Oracle Revenue Management and Billing ther than 2.3.0.0.0, cnsult with Oracle Supprt, Oracle Partner, r Oracle Cnsulting that may be supprting yur implementatin and upgrade prcess. Cpyright 2014, Oracle and/r its affiliates. All rights reserved. 19
Discntinued Features Oracle n lnger supprts the Off Cycle Billing feature intrduced in Oracle Revenue Management and Billing Versin 2.2.4.2. Instead, the On Demand Billing feature has been intrduced t facilitate adhc and regular billing. Hwever, this feature is develped mainly fr the Banking mdule and cannt be used seamlessly fr the Insurance mdule. If yu want t cntinue using the Off Cycle Billing feature fr the Insurance mdule, yu need t d the fllwing: 1. Create adhc billable charges using the Billable Charge screen. While creating adhc billable charges, ensure that the bill after date is specified and the Adhc Bill flag is set t Y. 2. Execute the Adhc Billing (C1-FABL) batch t generate adhc bills. The system cnsiders nly billable charges with the Adhc Bill flag set t Y during adhc billing. Nte that the adhc billable charges f all divisins are cnsidered during adhc billing. Fr mre infrmatin abut this batch, refer t Oracle Revenue Management and Billing Batch Executin Guide. 20 Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
Prduct Dcumentatin User manuals and ther technical dcuments are available in the Prtable Dcument Frmat (PDF) frmat. Yu can dwnlad Oracle Revenue Management and Billing release specific dcumentatin library (fr example, Oracle Revenue Management and Billing Versin 2.3.X.X.X Dcumentatin Library) using the fllwing URL: http://www.racle.cm/technetwrk/indexes/dcumentatin/fsgbu-1364781.html Cpyright 2014, Oracle and/r its affiliates. All rights reserved. 21
Media Pack Dwnlad Oracle Financial Services Revenue Management and Billing and Oracle Insurance Revenue Management and Billing media packs are available fr the fllwing platfrms: Windws (Micrsft Windws x64 (64-bit)) AIX (IBM AIX n POWER Systems (64-bit)) Linux (Linux x86-64) Each media pack includes multiple packages. Fr mre infrmatin, refer t the Oracle Revenue Management and Billing Media Packs sectin in the Oracle Revenue Management and Billing Quick Installatin Guide. T dwnlad a package frm a media pack: 1. Lgin t Oracle Sftware Delivery Clud. The Terms and Restrictins page appears. 2. Select the I have reviewed the terms f the License Agreement r Oracle Trial License Agreement and accept its terms check bx. 3. Select the YES, I accept these Exprt Restrictins check bx. 4. Click Cntinue. The Media Pack Search page appears. 5. Select the Oracle Financial Services Prducts ptin frm the Select a Prduct Pack list. 6. Select the required platfrm fr which yu want t dwnlad the media pack frm the Platfrm list. Fr example, select Linux x86-64. 7. Click G. A list f financial services prducts which are released fr the specified platfrm appears in the Search Results sectin. 8. Select the radi buttn crrespnding t the Oracle Financial Services Revenue Management and Billing Versin 2.3.0.1.0 r Oracle Insurance Revenue Management and Billing Versin 2.3.0.1.0 media pack depending n which yu want t dwnlad. 9. Click Cntinue. The Oracle Revenue Management and Billing fr <Platfrm> page appears. 10. Click the Dwnlad buttn crrespnding t the package that yu want t dwnlad. The File Dwnlad dialg bx appears. 11. Click Save. The Save As dialg bx appears. 12. Brwse t lcatin where yu want t dwnlad the package and then click Save. The package is dwnladed n the lcal machine. 22 Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
Bug Fixes The fllwing table lists the bugs that are fixed in this release: Bug Number Cpy f 17319301-17333357 - 17373377-17385404 - 17507863-17552403 - ACCOUNT IDENTIFIER IN THE ACCOUNT SEARCH WINDOW TRUNCATED TO 16 CHARACTERS ALL CUSTOMERS IN THE HIERARCHY NOT DISPLAYED WHEN RELATION END DATE IS SPECIFIED ALLOW SIMILAR COMBINATION OF PRODUCTS IN TWO DIFFERENT PRODUCT RELATIONSHIPS ABILITY TO USE EXCHANGE RATE APPLICABLE ON TRANSACTION DATE DURING CY CONVERSION CURRENCY CONVERSION IN TFM SHOULD BE BASED ON PRICING CURRENCY ONLY SAVE AND CANCEL BUTTONS ARE DISPLAYED IN THE ADD PRODUCT SCREEN 17572187 - A COBOL ERROR OCCURS WHILE BILLING 17479160 - BILL SEGMENT CALC LINE AMOUNT ROUNDING ISSUE 18028366-18023514 16815453 17978585 17812193 17918837 17656741 17879254 - CALC LINE AMOUNT IS NOT ROUNDED OFF IN THE RATE CHECK SCREEN SYSTEM ERROR OCCURS WHILE CANCELING A JOB STREAM WITH ERRORS ADD BILL/PAYMENT/ADJUSTMENT ID COLUMN IN THE ACCOUNT FINANCIAL HISTORY SCREEN PRICE LIST AGREED PRICE USED INSTEAD OF CUSTOMER AGREED PRICE ON POST-PROCESSING CONTRACT TYPE PRIORITY FLAG NOT CONSIDERED WHILE GENERATING BILL SEGMENTS 17849633 - PERFORMANCE ISSUE WHILE EXECUTING THE C1-TXNSQ BATCH 17778944-17796078 17778910 POST PROCESSING BILL SEGMENTS START AND END DATES CALCULATED INCORRECTLY ABLE TO DELETE A BILL CYCLE WHICH IS ASSOCIATED WITH A DIVISION Cpyright 2014, Oracle and/r its affiliates. All rights reserved. 23
Bug Number Cpy f 17786787 17645119 17778964-17778902 - 17667581 17658958 17668130 17549671 18151598 17158251 18130420-18121922 - 18047604 17337881 18008898 - POLICY SCREEN - POLICY STATUS DEFAULTS TO IN FORCE EVEN AFTER CHANGING THE VALUE DECIMAL PRECISION DEFINED FOR A CURRENCY NOT CONSIDERED WHILE ROUNDING OFF BILLABLE CHARGE END DATE NOT CONSIDERED WHILE GENERATING BILL SEGMENTS ADJUSTMENTS WITH APPROVAL PROFILE NOT FROZEN ON BILL COMPLETION ADD BILL/PAYMENT ID COLUMN IN THE ACCOUNT BILL/PAYMENT HISTORY SCREEN OVERLAPPING ERROR OCCURS ON ADDING A CHILD PERSON IN THE PERSON SCREEN AGGREGATE SERVICE QUANTITY NOT DISPLAYED AS PER PRECISION DEFINED FOR CURRENCY UNABLE TO MODIFY AND RESOLVE PRICE ASSIGNMENT REQUEST OF AN ACCOUNT AND CUSTOMER MANAGE PRODUCTS, MANAGE PRICELISTS - DIVISION NOT FILTERED BASED ON ACCESS GROUP PERFORMANCE ISSUE WHILE ASSIGNING GL ACCOUNTS TO FINANCIAL TRANSACTIONS 17947315 17947292 EXCEPTION OCCURS WHILE EXECUTING THE C1-ADUP1 BATCH 17947217 - EXCEPTION OCCURS WHILE EXECUTING THE C1-ADUP2 BATCH 17525824-17473950 17451010 17461503 17289638 17327486-17319932 - BILLING BATCHES WITH MULTI-THREADING BASED ON BILLABLE CHARGES INSTEAD OF ACCOUNT PAYMENT SCREEN - ADD THE BILL ID COLUMN IN THE MANUAL DISTRIBUTION TAB EFFECTIVE START DATE ON PRICE ASSIGNMENT AND PRICING SCREENS IS NOT SAME INCORRECT CANCELLED VOLUME IS DISPLAYED FOR A FEED CONTAINING MULTIPLE DIVISIONS UNABLE TO SEARCH PARENT PRICE LIST WHILE MODIFYING AND RESOLVING A PRICE LIST 24 Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
Bug Number Cpy f 17310225-17293099 - 17293078-18094504 - 18081489-17298680 16793582 17388257 17310906 17434024 17415098 CHANGES MADE IN THE TIERING RANGE ARE NOT HIGHLIGHTED IN THE APPROVE SCREEN MODIFY & RESOLVE SCREENS - ABLE TO EDIT SOME FIELDS WHICH SHOULD NOT BE EDITABLE BANKING DOCUMAKER - NOT ABLE TO GENERATE BILL PDF FOR INVOICE GROUP ACCOUNT BILL AMOUNT DISPLAYED ON THE BILL AND VIEW BILL DATA SCREENS IS NOT SAME UNABLE TO VIEW CHARACTERISTICS DEFINED FOR PRICE LIST IN EDIT PRICE LIST SCREEN ABLE TO ADD A PRODUCT IN A REGULAR BUNDLE WHEN THEIR PARAMETERS ARE DIFFERENT PARAMETER WARNING ON CHANGING DATE SHOULD APPEAR ONLY IF THERE IS ANY PARAMETER GL ASSIGN ALGORITHM SHOULD NOT BE TRIGGERED FOR UNFROZEN FINANCIAL TRANSACTIONS 17571965 17466140 UNABLE TO SEARCH FOR TRANSACTIONS IN THE ERROR STATUS 17572851 17554194 17344937 13843249 18022746 17606992 18022914 17502556 18156923 17828592 UDF CURRENCY SHOULD BE MANDATORY EVEN WHEN THE UDF AMOUNT IS ZERO TRANSACTIONS NOT SEARCHED BASED ON TRANSACTION SOURCE & RECORD TYPE COMBINATION USE STRINGBUILDER INSTEAD OF STRING TO ENHANCE PERFORMANCE IN APPROVAL WORKFLOW ADJUSTMENT STAGING CONTROL UNABLE TO ADD RECORD WHERE TOTAL AMOUNT IS ZERO BILL SEGMENT CALC LINES - ADD GO TO BILLABLE CHARGE OPTION IN THE CONTEXT MENU 16767414 - ADD BILL CYCLE AS A SOFT PARAMETER IN THE BILLING BATCH 17631435-18047686 17641599 BUNDLE PRICE USED INSTEAD OF INDIVIDUAL PRODUCT PRICE AT HIGHER PRECEDENCE LEVEL NEED ADDITIONAL INFORMATION IN THE RATE COLUMN IN THE EFFECTIVE PRICING SCREEN Cpyright 2014, Oracle and/r its affiliates. All rights reserved. 25
Bug Number Cpy f 18206925-18289428 17704193 18319193 17842436 18319021 17722080 18382574-18318956 18009552 C1-BLPPR ERRORS OUT IF ACCOUNT HAS MULTIPLE CONTRACTS WITH FT_GL_EXT ALGORITHM ADJ CURR SET TO DIV CURR IF ALLOW MULTI-CURR ACCOUNTS SET TO N IN C1_MLTCURACC C1-TXNVP BATCH - UNABLE TO SEARCH PRICING WHICH IS EFFECTIVE ON TRANSACTION DATE C1-TXNIP BATCH - UNABLE TO USE RULES WHICH ARE EFFECTIVE ON TRANSACTION DATE END DATE IS NOT CONSIDERED WHILE BILLING BILLABLE CHARGES GENERATED VIA TFM UNABLE TO IDENTIFY AND RESOLVE THE ERRORS WHILE EXECUTING THE C1-TXNVP BATCH 17433347 17238442 EXCEPTION OCCURS ON DELETING FINANCIAL TRANSACTIONS 17902606 17767721 18635802 18076099 18635344 18110510 18598717 18414530 18473589 18433286 18846769-18841908 18360785 18726082-17869548 - 19076035 18895853 NO. OF RECORDS PROCESSED SUCCESSFULLY SHOWN INCORRECTLY ON EXECUTING C1-ADUP1 MULTIPLE BILLS GENERATED FOR AN ACCOUNT WHICH HAS LARGE NUMBER OF CONTRACTS C1-ADJG-WO ALGORITHM TYPE RETURNS UNPAID AMOUNT FIELD MISSING ERROR INAPPROPRIATE CREDIT DISTRIBUTION CODE USED IN THE FT AFTER PAYMENT IS APPLIED PERFORMANCE ISSUE WHILE EXECUTING THE C1-TXNIP AND C1- TXNRB BATCHES CRITERION VALUE FIELD ACCEPTS MORE THAN 30 CHARS BUT SAVES ONLY 10 CHARS PRODUCT PARAMETERS ARE CLEARED WHEN EFFECTIVE DATES ON PRICE ASSIGNMENT MODIFIED C1-BLGEN BATCH JOB DOES NOT CONSIDER THE BATCH BUSINESS DATE INCORRECT BILL PERIOD SHOWN IN THE BILL SEGMENT ON EDITING INVOICE MATURITY DATE PERFORMANCE ISSUE WHILE EXECUTING THE CIPPMBSL:XQ070 QUERY 26 Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
Bug Number Cpy f 18758527 18655169 19149352 19170875 19147973-19125160 - 19076961-19075181 - 19067630 18887251 19192314-19372307 19239327 19372267 19354837 19480690 - UNABLE TO EDIT CHARACTERISTICS WHEN THE PAYMENT IS FROZEN OR CANCELLED CI_TXN_DTL_PRITM_SUMMARY TABLE IS NOT UPDATED ON EXECUTING THE C1-TXNIP BATCH UNABLE TO REMOVE PRODUCT FROM PRICELIST IF APPROVAL WORKFLOW IS SWITCHED ON MODIFY AND RESOLVE SCREENS ABLE TO SPECIFY PRODUCT PARAMETERS FOR RATIO BUNDLE ABLE TO ASSIGN MULTIPLE BUNDLES WITH SAME PRODUCTS AND PRODUCT PARAMETERS PRICE LIST ASSIGNMENT APPROVAL WORKFLOW - ASSIGNMENT STATUS VALIDATION MISSING CONDITIONAL APPROVAL WORKFLOW DOESN T WORK FOR PRICE ASSIGNMENT PRODUCT PRICING WHICH IS APPLIED ONLY TO NEW CUSTOMERS IS NOT WORKING RATE COMPONENT MAP DESCRIPTION DOES NOT APPEAR WHILE APPROVING PRICE ASSIGNMENT PORTUGUESE CHARACTERS DO NOT APPEAR PROPERLY WHILE APPROVING A REQUEST ERROR OCCURS WHILE RUNNING ARTIFACT GENERATOR IN JAVA SDK Cpyright 2014, Oracle and/r its affiliates. All rights reserved. 27
Knwn s This sectin lists the knwn issues in Oracle Revenue Management and Billing Versin 2.3.0.1.0 alng with wrkarunds available t handle these issues. The knwn issues are gruped int the fllwing categries: Banking Insurance Dcumentatin Banking FEED MANAGEMENT BATCHES CAN RUN IN ANY SEQUENCE GIVING INCORRECT RESULTS During the transactin aggregatin prcess, yu need t execute batches in the specified rder (as stated in the user manual). If yu d nt fllw the sequence, errneus results may ccur. The nly way t reslve this issue is t disaggregate and execute the aggregatin prcess nce again. THE FEED MANAGEMENT BATCHES CANNOT RUN CONCURRENTLY. Yu cannt execute the transactin feed management batches cncurrently. SEARCH RESULT FOR EXCHANGE RATE NOT DISPLAYED CORRECTLY Searching fr the lwest precisin rate (0.000000000000000001 /0.000000000000000011/ 0.000000000000000023) frm the Search Exchange Rate zne results in displaying the rate in expnential frmat IE -18. 28 Cpyright 2014, Oracle and/r its affiliates. All rights reserved.
VALIDATION RULES FOR ADHOC CHARACTERISTIC TYPES ARE NOT TRIGGERED IN THE MANAGE PRODUCTS, MANAGE PRICE LISTS, ADD PRODUCT PRICING, OVERRIDE PRODUCT PRICING, AND EDIT ASSIGNED PRICING SCREENS When yu assciate adhc characteristic types with a prduct, price list, and a price assignment, validatins defined fr adhc characteristic types are nt triggered in the Manage Prducts, Manage Price Lists, Add Prduct Pricing, Override Prduct Pricing, and the Edit Assigned Pricing screens. UNABLE TO CHANGE THE DIVISION STATUS FROM ACTIVE TO RETIRED When the apprval wrkflw functinality is enabled, the status f a divisin will nt get changed frm Active t Retired. LOCALIZATION ISSUE WHEN MAKER AND CHECKER CHOOSE DIFFERENT LANGUAGES When a maker and checker perate in different languages, a maker cannt see the apprved transactins. Maker shuld lgin with a language that checker is using t see the apprved transactins. PRE-VALIDATION ERROR MSG FOR INVOICING GROUP EVEN IF PRE- VALIDATION IS OFF If yu set the Pre-validatin flag fr bth the grups (that is, C1IGADD and C1IGUPD) t N, the validatin will still be triggered befre the apprval wrkflw request is created. Cpyright 2014, Oracle and/r its affiliates. All rights reserved. 29