oracle® revenue management and billing · 2019. 11. 13. · oracle® revenue management and...

Oracle® Revenue Management and Billing

Version 2.6.0.1.0

Upgrade Guide

Revision 13.4

E90733-01

November, 2017

Oracle Revenue Management and Billing Upgrade Guide

ii Copyright © 2017, Oracle and/or its affiliates. All rights reserved.


E90733-01

Copyright Notice

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

Trademark Notice

Oracle and Java are registered trademarks of Oracle Corporation 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.

License Restrictions Warranty/Consequential Damages Disclaimer

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 de-compilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

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.

Restricted Rights Notice

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

U.S. GOVERNMENT RIGHTS

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 restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software 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 in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.


Copyright © 2017, Oracle and/or its affiliates. All rights reserved. iii

Third Party Content, Products, and Services Disclaimer

This software and documentation may provide access to or information on 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. 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.


iv Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

Preface

About This Document This document will help you to understand how to upgrade the Oracle Revenue Management and Billing application and its database. It also explains how to upgrade the application framework.

Intended Audience This document is intended for the following audience:

End-Users

System Administrators

Consulting Team

Implementation Team

Organization of the Document The information in this document is organized into the following sections:

Section No. Section Name Description

Section 1 Preparing for Upgrade Provides an overview of the upgrade process. It also lists the prerequisites for upgrading the application.

Section 2 Upgrading from ORMB Version 2.6.0.0.0 to 2.6.0.1.0

Explains how to upgrade from Oracle Revenue Management and Billing Version 2.6.0.0.0 to 2.6.0.1.0.

Section 3 Additional Tasks Lists and describes the additional tasks that you need to perform after upgrading the application.

Appendix A ORMB 2.6.0.1.0 Patch Numbers Lists the ORMB Version 2.6.0.1.0 domain-specific patch numbers along with its contents.

Appendix B Known Issues Lists the known issues in the current release of the Oracle Revenue Management and Billing application.

Appendix C Third Party Software Upgrade Provides a list of third party software that you need to upgrade before upgrading the application.

Appendix D New Tables Added in 2.6.0.1.0 Lists and describes the tables that are newly added in the Oracle Revenue Management and Billing Version 2.6.0.1.0 database.


Copyright © 2017, Oracle and/or its affiliates. All rights reserved. v

Section No. Section Name Description

Appendix E Existing Tables Modified in 2.6.0.1.0 Lists the existing tables and their columns that are modified in the Oracle Revenue Management and Billing Version 2.6.0.1.0 database.

Appendix F Algorithms and Algorithm Types Dropped in 2.6.0.1.0

Lists the algorithms and algorithm types which are dropped in Oracle Revenue Management and Billing Version 2.6.0.1.0.

Appendix G Parameters Added or Removed from Algorithm Types in 2.6.0.1.0

Lists the parameters which are added or removed from the algorithm types in Oracle Revenue Management and Billing Version 2.6.0.1.0.

Appendix H Option Types Added or Removed from Feature Configurations in 2.6.0.1.0

Lists the option types which are added or removed from the feature configurations in Oracle Revenue Management and Billing Version 2.6.0.1.0.

Appendix I Characteristic Types Dropped in 2.6.0.1.0

Lists the characteristic types which are dropped in Oracle Revenue Management and Billing Version 2.6.0.1.0.

Appendix J Upgrade Batch for Deferred Revenue Recognition (C1-RRUPG)

Describes the batch which is used for migrating data from Oracle Revenue Management and Billing Version 2.6.0.0.0 to 2.6.0.1.0.

Appendix K Changing the DB User Password Explains how to change the database user password.

Related Documents You can refer to the following documents for more information:

Document Description

Oracle Revenue Management and Billing Version 2.6.0.1.0 Release Notes

Provides a brief description about the new features, enhancements, UI and database level changes, supported platforms, framework upgrade, supported upgrades, and technology upgrade made in this release. It also highlights the discontinued features, bug fixes, and known issues in this release.

Oracle Revenue Management and Billing Upgrade Path Guide

Explains the path and pre-requisites for upgrading Oracle Revenue Management and Billing from one version to another.


vi Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

Change Log

Revision Last Update Updated Section Comments

13.1 12-Dec-2017 Appendix D: New Tables Added in 2.6.0.1.0 Added Information

Appendix E: Existing Tables Modified in 2.6.0.1.0

Appendix F: Algorithms and Algorithm Types Dropped in 2.6.0.1.0

Appendix G: Parameters Added or Removed from Algorithm Types in 2.6.0.1.0

Appendix H: Option Types Added or Removed from Feature Configurations in 2.6.0.1.0

Appendix I: Characteristic Types Dropped in 2.6.0.1.0

Appendix J: Upgrade Batch for Deferred Revenue Recognition (C1-RRUPG)

13.2 16-Mar-2018 Section 2.6.1: Installing ORMB Version 2.6.0.1.0 Added Information

13.3 28-June-2019 Section 2.2: Downloading the ORMB Packages and Patches

Updated Information

13.4 20-Aug-2019 Section 2: Upgrading from ORMB Version 2.6.0.0.0 to 2.6.0.1.0

Added Information about the Single-Step Utility


Copyright © 2017, Oracle and/or its affiliates. All rights reserved. vii

Contents

1. Preparing for Upgrade ........................................................................................................................................... 1

1.1 Upgrade Overview ................................................................................................................................................1

1.2 Upgrade Pre-requisites .........................................................................................................................................3

1.3 Supported Upgrades ............................................................................................................................................3

2. Upgrading from ORMB Version 2.6.0.0.0 to 2.6.0.1.0 ........................................................................................... 4

2.1 Prerequisites.........................................................................................................................................................4

2.2 Downloading the ORMB Packages and Patches ...................................................................................................5

2.3 Upgrading Framework on the Database ..............................................................................................................5

2.3.1 Installing Rollup Pack for OUAF Version 4.3.0.4.0 ......................................................................................... 5

2.4 Installing Framework on the Application Environment ........................................................................................9

2.4.1 Installing OUAF Version 4.3.0.4.0 .................................................................................................................. 9

2.4.2 Installing Rollup Pack for OUAF Version 4.3.0.4.0 ....................................................................................... 13

2.5 Installing the ORMB Application.........................................................................................................................15

2.5.1 Installing ORMB Version 2.6.0.1.0 ............................................................................................................... 15

2.5.2 Post Installation Tasks ................................................................................................................................. 18

2.5.3 Accessing the ORMB Application ................................................................................................................. 26

2.6 Upgrading the ORMB Database..........................................................................................................................26

2.6.1 Installing ORMB Version 2.6.0.1.0 ............................................................................................................... 28

2.6.2 Applying the 27142924 Patch ...................................................................................................................... 32



2.7 Migrating Data ....................................................................................................................................................39

3. Additional Tasks ................................................................................................................................................... 40

3.1 Generating the Application Viewer ....................................................................................................................40

3.2 Starting the Thread Pool Worker .......................................................................................................................41

3.3 Building Javadoc Index .......................................................................................................................................41

Appendix A : ORMB 2.6.0.1.0 Patch Numbers ...................................................................................................... 42

Appendix B : Known Issues ................................................................................................................................... 43

Appendix C : Third Party Software Upgrade ......................................................................................................... 44

Appendix D : New Tables Added in 2.6.0.1.0 ........................................................................................................ 45

D.1 CI_ACCT_APAY_CHAR .........................................................................................................................................45

D.2 C1_ACCRUAL_CHAR ...........................................................................................................................................46

D.3 CI_ADJ_CLR_STG ................................................................................................................................................47

D.4 CI_APPTXN_BOCHAIN_FLDRULE ........................................................................................................................48

D.5 CI_APPTXN_BOCHAIN_FLDRULE_THLD ..............................................................................................................49

D.6 CI_APAY_RT_TYPE_APAY_CHAR .........................................................................................................................50

D.7 C1_APAY_RULE ...................................................................................................................................................51

D.8 C1_APAY_RULE_CRITERIA ..................................................................................................................................51

D.9 C1_DRR_TMPLT_L ..............................................................................................................................................53

D.10 CI_REV_REC_SCH_CHAR .....................................................................................................................................53


viii Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

D.11 CI_REV_REC_SCH_LOG_PARM ...........................................................................................................................54

D.12 CI_REV_REC_SCH_LOG .......................................................................................................................................55

D.13 C1_DRR_TMPLT ..................................................................................................................................................57

D.14 C1_DRR_TMPLT_ALG .........................................................................................................................................58

D.15 C1_DISCREPANCY_RPT .......................................................................................................................................58

D.16 C1_DISCREPANCY_RPT_CHAR ............................................................................................................................59

D.17 C1_DISCREPANCY_RPT_K ...................................................................................................................................60

D.18 C1_DISCREPANCY_RPT_LN .................................................................................................................................61

D.19 C1_DISCREPANCY_RPT_LN_CHAR ......................................................................................................................62

D.20 C1_DISCREPANCY_RPT_LN_REL_OBJ .................................................................................................................63

D.21 C1_DISCREPANCY_RPT_LOG ..............................................................................................................................64

D.22 C1_DISCREPANCY_RPT_LOG_PARM ..................................................................................................................66

D.23 C1_DSC_RPT_TYPE .............................................................................................................................................67

D.24 C1_DSC_RPT_TYPE_CHAR ..................................................................................................................................67

D.25 C1_DSC_RPT_TYPE_L ..........................................................................................................................................69

D.26 C1_ENRL_PROD ..................................................................................................................................................69

D.27 C1_ENRL_PROD_REL ..........................................................................................................................................70

D.28 C1_ENRL_PROD_REL_SVC ..................................................................................................................................71

D.29 C1_ENRL_PROD_SVC ..........................................................................................................................................72

D.30 CI_FILE_REQUEST_TRANSFORM_DTL.................................................................................................................73

D.31 C1_PAY_INS ........................................................................................................................................................74

D.32 C1_PAY_INS_ADJ ................................................................................................................................................76

D.33 C1_PAY_INS_CHAR .............................................................................................................................................77

D.34 C1_PAY_INS_K ....................................................................................................................................................78

D.35 C1_PAY_INS_LOG ...............................................................................................................................................78

D.36 C1_PAY_INS_LOG_PARM ...................................................................................................................................79

D.37 C1_PAY_INS_REL_OBJ ........................................................................................................................................80

D.38 C1_PRODUCT_DIV_PRICELIST ............................................................................................................................82

D.39 C1_PRODUCT_ENRL ...........................................................................................................................................82

D.40 C1_PRODUCT_ENRL_CHAR ................................................................................................................................83

D.41 C1_PRODUCT_ENRL_K .......................................................................................................................................84

D.42 C1_PRODUCT_ENRL_LOG ...................................................................................................................................85

D.43 C1_PRODUCT_ENRL_LOG_PARM .......................................................................................................................86

D.44 C1_PRODUCT_LOG .............................................................................................................................................87

D.45 C1_PRODUCT_LOG_PARM .................................................................................................................................88

D.46 C1_PRODUCT_SERVICE.......................................................................................................................................89

D.47 C1_PRODUCT_SERVICE_CHAR ............................................................................................................................90

D.48 C1_PRODUCT_SERVICE_L ...................................................................................................................................91

D.49 C1_PRODUCT_SERVICE_PRITM ..........................................................................................................................91

D.50 C1_PRODUCT_VER .............................................................................................................................................92

D.51 C1_PRODUCT_VER_CHAR ..................................................................................................................................93

D.52 C1_PRODUCT_VER_ELIG ....................................................................................................................................94

D.53 C1_PRODUCT_VER_ELIG_DTL ............................................................................................................................95

D.54 C1_PRODUCT_VER_ELIG_L .................................................................................................................................96


Copyright © 2017, Oracle and/or its affiliates. All rights reserved. ix

D.55 C1_PRODUCT_VER_L ..........................................................................................................................................97

D.56 C1_PRODUCT_VER_LOG .....................................................................................................................................98

D.57 C1_PRODUCT_VER_LOG_PARM .........................................................................................................................99

D.58 C1_PRODUCT_VER_PLIST .................................................................................................................................100

D.59 C1_PRODUCT_VER_PROD ................................................................................................................................101

D.60 C1_PRODUCT_VER_PROD_SVC ........................................................................................................................102

D.61 C1_PRODUCT_VER_SVC ...................................................................................................................................103

D.62 C1_RECONCILIATION ........................................................................................................................................104

D.63 C1_RECONCILIATION_LOG ...............................................................................................................................105

D.64 C1_RECONCILIATION_LOG_PARM ...................................................................................................................106

D.65 C1_RECONCILIATION_CHAR .............................................................................................................................107

D.66 C1_RECONCILIATION_K ....................................................................................................................................108

D.67 C1_RECON_TYPE ..............................................................................................................................................108

D.68 C1_RECON_TYPE_ALG ......................................................................................................................................109

D.69 C1_RECON_TYPE_CHAR ...................................................................................................................................110

D.70 C1_RECON_TYPE_L ...........................................................................................................................................111

D.71 CI_REV_REC_SCH_REL ......................................................................................................................................112

Appendix E : Existing Tables Added in 2.6.0.1.0 ................................................................................................. 113

E.1 CI_APAY_STAGE_UP .........................................................................................................................................113

E.2 CI_APPTXN_CH_ELIGIBLE .................................................................................................................................113

E.3 CI_APPTXN_LOG ...............................................................................................................................................113

E.4 C1_FT_EXT ........................................................................................................................................................114

E.5 CI_ACCT_APAY ..................................................................................................................................................114

E.6 CI_ACCT ............................................................................................................................................................115

E.7 C1_PRODUCT ....................................................................................................................................................115

E.8 C1_PRODUCT_DIV ............................................................................................................................................115

E.9 CI_REV_REC_SCH ..............................................................................................................................................116

E.10 CI_CONSTRUCT_LINKED_ACCT .........................................................................................................................117

E.11 CI_CONSTRUCT_TEMPLATE ..............................................................................................................................117

E.12 CI_CONSTRUCT_TEMPLATE_CRIT.....................................................................................................................117

E.13 CI_CONSTRUCT_TEMPLATE_CRIT_L .................................................................................................................118

E.14 CI_CONSTRUCT_TEMPLATE_L ..........................................................................................................................118

E.15 CI_APPTXN ........................................................................................................................................................118

E.16 CI_APPTXN_BOCHAIN ......................................................................................................................................119

E.17 CI_FILE_REQUEST_TYPE ...................................................................................................................................119

E.18 CI_FILE_REQUEST_DETAIL ................................................................................................................................120

E.19 CI_MEMBERSHIP ..............................................................................................................................................120

E.20 CI_PRICEASGN ..................................................................................................................................................120

E.21 CI_PRICE_PARM ...............................................................................................................................................121

E.22 CI_FILE_REQUEST .............................................................................................................................................121

E.23 CI_RULE_TYPE_FLD ...........................................................................................................................................121

E.24 CI_RULE_TYPE ..................................................................................................................................................121

E.25 CI_BCHG_HSTG .................................................................................................................................................122

E.26 C$_0FILTER2 .....................................................................................................................................................122


x Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

E.27 C1_PAY_TNDR_REQ..........................................................................................................................................122

E.28 CI_ADJ_APREQ..................................................................................................................................................123

E.29 CI_APAY_CLR_STG ............................................................................................................................................123

E.30 CI_APAY_STAGE_UP_REM ................................................................................................................................123

E.31 CI_BILL_ROUTING .............................................................................................................................................124

E.32 CI_CUSTOMER_HIERARCHY_VW ......................................................................................................................124

E.33 CI_EFF_ACCT_PRICING_VW .............................................................................................................................124

E.34 CI_EFF_PER_PRICING_VW ................................................................................................................................125

E.35 CI_ENRL_PER_NM ............................................................................................................................................125

E.36 CI_EXT_STMT_ITEM .........................................................................................................................................125

E.37 CI_MEMBERS_VW ............................................................................................................................................126

E.38 CI_MEMBER_ACCOUNT_VW ............................................................................................................................126

E.39 CI_PAY_TNDR ...................................................................................................................................................126

E.40 CI_PAY_TNDR_ST..............................................................................................................................................127

E.41 CI_PER ..............................................................................................................................................................127

E.42 CI_PER_NAME ..................................................................................................................................................127

E.43 CI_PER_PRIM_VW ............................................................................................................................................128

E.44 CI_PEVT_DTL_ST ...............................................................................................................................................128

E.45 CI_QUOTE_RTG ................................................................................................................................................128

E.46 CI_STM_PER_VW ..............................................................................................................................................129

E.47 CI_TRL_BILL_ROUTING .....................................................................................................................................129

Appendix F : Algorithms and Algorithm Types Dropped in 2.6.0.1.0.................................................................. 130

F.1 Algorithm Type .................................................................................................................................................130

F.2 Algorithm ..........................................................................................................................................................130

Appendix G : Parameters Added or Removed from Algorithm Types in 2.6.0.1.0 .............................................. 131

Appendix H : Option Types Added or Removed from Feature Configurations in 2.6.0.1.0 ................................ 132

Appendix I : Characteristic Types Dropped in 2.6.0.1.0 ......................................................................................... 133

Appendix J : Upgrade Batch for Deferred Revenue Recognition (C1-RRUPG) ....................................................... 134

Appendix K : Changing the DB User Password .................................................................................................... 135


Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 1

1. Preparing for Upgrade This section provides an overview of the upgrade process. It also lists the pre-requisites for upgrading Oracle Revenue Management and Billing from one version to another.

1.1 Upgrade Overview The following figure provides an overview of the steps that need to be taken for upgrading Oracle Revenue Management and Billing.


2 Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

Figure 1 : Upgrade Process



1.2 Upgrade Pre-requisites Before you upgrade Oracle Revenue Management and Billing, you need to upgrade the application framework as mentioned in the Oracle Revenue Management and Billing Upgrade Path Guide. While upgrading the application framework, you might have to apply some patches (additional single fixes) as pre-requisites or post-requisites.

Also, before you upgrade the application framework, you might have to upgrade some of the third party software. For more information, refer to the Upgrade Prerequisites section in the Oracle Revenue Management and Billing Upgrade Path Guide.

1.3 Supported Upgrades In this release, we support the following upgrades:

Upgrade from Oracle Revenue Management and Billing Version 2.6.0.0.0 to 2.6.0.1.0

Note: For upgrading from any other version of Oracle Revenue Management and Billing other than 2.6.0.0.0, consult with Oracle Support, Oracle Partner, or Oracle Consulting that may be supporting your implementation and upgrade process.



2. Upgrading from ORMB Version 2.6.0.0.0 to 2.6.0.1.0

This section explains how to upgrade from Oracle Revenue Management and Billing Version 2.6.0.0.0 to 2.6.0.1.0. The high-level steps include:

1. Downloading the ORMB Packages and Patches

2. Upgrading Framework on the Database

3. Installing Framework on the Application Environment

4. Installing the Oracle Revenue Management and Billing Application

5. Upgrading the Oracle Revenue Management and Billing Database

6. Migrating Data

Note: Before you upgrade the application, you must take a backup of the application and the database.

You can upgrade the database either manually by following the steps listed in this document or automatically using the single-step utility. Oracle Revenue Management and Billing provides the single-step utility which helps to upgrade the database from any previous version (not older than V2.3.0.2.0) to the current version. You can download the single-step utility from the UTILITIES PROVIDING A SINGLE STEP PROCESS FOR DATABASE UPGRADE patch (Patch Number: 25895460) which is available on My Oracle Support. To understand how to execute the single-step utility, refer to the documentation available in the patch. At present, the single-step utility is only supported on the Windows environment.

To improve the performance of the SQL queries executed for data migration, you can execute a Java utility for setting degree of parallelism. This Java utility must be used in conjunction with the single-step utility. It must be executed before executing the single-step utility. You can download this utility from the JAVA UTILITY FOR SETTING DEGREE OF PARALLELISM IN DATA MIGRATIONS SQLS patch (Patch Number: 28226772) which is available on My Oracle Support. To understand how to execute this Java utility, refer to the documentation available in the patch. At present, this utility is only supported on the Windows environment.

2.1 Prerequisites If you are already using the Transaction Feed Management feature and want to upgrade to Oracle Revenue Management and Billing Version 2.6.0.1.0, then you need to ensure the following (before upgrading):

All bills generated in the system are in the Complete status. In other words, there should not be any bills in the Pending status. If there are any bills in the Pending status or if any billable charge (generated through TFM) is not yet billed, disaggregation and cancellation of transactions which are uploaded using 2.6.0.0.0 will not happen successfully.

Transactions which are uploaded using 2.6.0.0.0 must not be in the Initial Product Determined (INPD) status. They can be in the Uploaded (UPLD), Invalid (INVL), Error (EROR), Completed (COMP), or Cancelled (CNCL) status.

Equal to (=) or tilde (~) symbol is not used in any existing price item parameter code or value. Otherwise, erroneous results might occur.

https://support.oracle.com/





2.2 Downloading the ORMB Packages and Patches For upgrading from Oracle Revenue Management and Billing Version 2.6.0.0.0 to 2.6.0.1.0, you must download the following package from the Oracle Revenue Management and Billing V2.6.0.0.0 media pack which is available on Oracle Software Delivery Cloud:

Oracle Utilities Application Framework V4.3.0.4.0 Multiplatform

In addition, you must download the following patches from My Oracle Support:

RMB V2.6.0.1.0 - <Domain>

Note: For more details about the patch number, refer to Appendix A: ORMB 2.6.0.1.0 Patch Numbers.

MANDATORY PATCH 1 FOR ORMB VERSION 2.6.0.1.0 (Patch Number: 27142924)



UPDATE ORMB VERSION 2.6.0.1.0 ONLINE HELP (Patch Number: 27190574)

The downloaded files will be in the ZIP format.

2.3 Upgrading Framework on the Database Oracle Revenue Management and Billing Version 2.6.0.1.0 supports Oracle Database Server 12.2.0.1. Therefore, before you upgrade the database, you need to upgrade from Oracle Database Server 12.1.0.2 to Oracle Database Server 12.2.0.1. For more information on how to upgrade Oracle Database Server, refer to the Oracle Database documentation.

While upgrading from Oracle Revenue Management and Billing Version 2.6.0.0.0 to 2.6.0.1.0, you need to install the following on the database:

1. Rollup Pack for Oracle Utilities Application Framework (OUAF) Version 4.3.0.4.0

To install the framework and its service packs on the database, you must have ability to connect to the database.

2.3.1 Installing Rollup Pack for OUAF Version 4.3.0.4.0

You can install the rollup pack for Oracle Utilities Application Framework Version 4.3.0.4.0 from a Windows machine and UNIX Standalone server. To install the rollup pack for Oracle Utilities Application Framework (OUAF) Version 4.3.0.4.0 on the database:

1. Login to the database server using the administrator’s credentials.

2. Create a temporary folder or directory (for example, TEMPDIR) on the database server using the following command:

mkdir TEMPDIR

3. Copy the RMB V2.6.0.1.0 - <Domain> patch to the TEMPDIR folder using the following command:

AIX, Linux:

cp <PATH>/<filename>.zip <PATH>/TEMPDIR

https://edelivery.oracle.com/




Windows:

copy <PATH>\<filename>.zip <PATH>\TEMPDIR

Note: You can also use File Transfer Protocol (FTP) to transfer the downloaded file from one host to another. You must use the binary mode while copying files through FTP.

4. Change to the TEMPDIR folder using the following command:

AIX, Linux:

cd <PATH>/TEMPDIR

Windows:

cd <PATH>\TEMPDIR

5. Unzip the RMB V2.6.0.1.0 - <Domain> patch using the following command:

AIX, Linux:

unzip <filename>.zip –d <PATH>/<DESTINATION_FOLDER_1>

Windows:

unzip <filename>.zip –d <PATH>\<DESTINATION_FOLDER_1>

The contents of the zip file are extracted in the <DESTINATION_FOLDER_1> folder. For more information about the contents of the RMB V2.6.0.1.0 - <Domain> patch, refer to Appendix A: ORMB 2.6.0.1.0 Patch Numbers.

6. Change to <DESTINATION_FOLDER_1> using the following command:

AIX, Linux:

cd <PATH>/<DESTINATION_FOLDER_1>

Windows:

cd <PATH>\<DESTINATION_FOLDER_1>

7. Unzip the RMB-V26010-FW-PREREQ-MultiPlatform file using the following command:

AIX, Linux:

unzip RMB-V26010-FW-PREREQ-MultiPlatform.zip –d

<PATH>/<DESTINATION_FOLDER_2>

Windows:

unzip RMB-V26010-FW-PREREQ-MultiPlatform.zip –d

<PATH>\<DESTINATION_FOLDER_2>

The contents of the zip file are extracted in the <DESTINATION_FOLDER_2> folder. The contents include the ORMB-V26010-FW-PREREQ-MultiPlatform.jar file.


AIX, Linux:




Windows:


9. Decompress the JAR file using the following command:

jar -xvf ORMB-V26010-FW-PREREQ-MultiPlatform.jar

A sub-directory named FW-V4.3.0.4.0-Rollup is extracted. It contains the following two sub-folders:

Application

Database


AIX, Linux:

cd <PATH>/TEMPDIR

Windows:

cd <PATH>\TEMPDIR

11. Create a directory named dbpatch_tools using the following command:

mkdir dbpatch_tools

12. Copy the db_patch_standalone.jar file to the dbpatch_tools folder.

13. Change to the dbpatch_tools folder using the following command:

AIX, Linux:

cd <PATH>/TEMPDIR/dbpatch_tools

Windows:

cd <PATH>\TEMPDIR\dbpatch_tools


jar -xvf db_patch_standalone.jar

The contents are extracted in the dbpatch_tools folder. The contents include the following three sub-folders:

bin

config

lib

15. Set the TOOLSBIN environment variable using the following command:

AIX, Linux:

export TOOLSBIN=/TEMPDIR/dbpatch_tools/bin

Windows:

SET TOOLSBIN=TEMPDIR\dbpatch_tools\bin



16. Change to the Database directory using the following command:

AIX, Linux:

cd <DESTINATION_FOLDER_2>/FW-V4.3.0.4.0-Rollup/Database

Windows:

cd <DESTINATION_FOLDER_2>\FW-V4.3.0.4.0-Rollup\Database

Note: The <DESTINATION_FOLDER_3> folder is the location where you have extracted the contents of the ORMB-V26010-FW-PREREQ-MultiPlatform.jar file.

17. Execute the ouafDatabasePatch utility using the following command:

AIX, Linux:

ouafDatabasePatch.sh

Windows:

ouafDatabasePatch.cmd

Note:

In the previous versions of Oracle Revenue Management and Billing, you used to execute the cdxpatch utility while installing the rollup pack for Oracle Utilities Application Framework. Henceforth, the cdxpatch utility is no longer supported and you need to use the

ouafDatabasePatch utility.

This utility prompts you to enter values for the following parameters:

Parameter Value

Enter the target database type (O/M/D) [O] O (if you have Oracle database)

OR

M (if you have MySQL database)

Enter the username that owns the schema <DB_USER>

Example: CISADM

Enter the password for the <DB_USER> user <DB_USER_PASSWORD>

Enter the name of the Oracle Database Connection String

<DB_Server:DBPORT:ORACLE_SID>

Note: If you have changed the database user password, you will not be able to install the rollup pack for Oracle Utilities Application Framework Version 4.3.0.4.0. You will have to first change the database user password. For more information on how to change the database user password, refer to Appendix K: Changing the DB User Password.

18. Enter the required parameter values. The following message appears in the command line:

Ready to process patches, Do you want to continue? (Y/N)

19. Type Y and then press Enter. A message appears indicating that the patches are applied successfully.



2.4 Installing Framework on the Application Environment

Once you install the framework service pack on the database and define security for all database objects, you must install the framework and its service packs on the application environment. You need to install the following on the application environment:

1. Oracle Utilities Application Framework (OUAF) Version 4.3.0.4.0

2. Rollup Pack for Oracle Utilities Application Framework (OUAF) Version 4.3.0.4.0

You cannot perform these steps on the existing environments. You need to create new development and production/UAT environments on the application server and then perform the steps listed in this section.

2.4.1 Installing OUAF Version 4.3.0.4.0

To install Oracle Utilities Application Framework (OUAF) Version 4.3.0.4.0 on the application environment:

1. Login to the application server using the administrator’s credentials.

2. Create a temporary folder or directory (for example, TEMPDIR) on the application server using the following command:

3. mkdir TEMPDIR

4. Copy the Oracle Utilities Application Framework V4.3.0.4.0 Multiplatform package to the TEMPDIR folder using the following command:

AIX, Linux:


Windows:




AIX, Linux:

cd <PATH>/TEMPDIR

Windows:

cd <PATH>\TEMPDIR

6. Unzip the Oracle Utilities Application Framework V4.3.0.4.0 Multiplatform package using the following command:

AIX, Linux:


Windows:




The contents of the zip file are extracted in the <DESTINATION_FOLDER_1> folder. The contents include FW-V4.3.0.4.0-MultiPlatform.jar file.

7. Decompress the FW-V4.3.0.4.0-MultiPlatform.jar file using the following command:

jar -xvf FW-V4.3.0.4.0-MultiPlatform.jar

The contents of the JAR file include a folder named FW.V4.3.0.4.0.

8. Install and configure the required third-party software for the application server.

Note: You must install the prerequisite third party software depending on the platform on which you want to install Oracle Utilities Application Framework. For more details, refer to the Installing Application Server Prerequisite Software section in Oracle Revenue Management and Billing Installation Guide.

9. Set the Java Home path using the following command:

export PATH=/<Java_Home>/bin:$PATH

Note: The <Java_Home> is the location where you have installed Java 1.8.

The above command is applicable only for AIX and Linux platforms.

10. Change to the FW.V4.3.0.4.0 folder using the following command:

AIX, Linux:

cd <DESTINATION_FOLDER_1>/FW.V4.3.0.4.0

Windows:

cd <DESTINATION_FOLDER_1>\FW.V4.3.0.4.0

Note: The <DESTINATION_FOLDER_1> folder is the location where you have extracted the contents of the FW-V4.3.0.4.0-MultiPlatform.jar file.

11. Execute the install utility using the following command:

AIX, Linux:

ksh ./install.sh

Windows:

install.cmd

The following message appears in the command line:

Enter Oracle Client Home Directory (<Enter> quit):

12. Type <ORACLE_CLIENT_HOME>, and then press Enter. The following environment installation menus appear in the command line:

1. Environment ID, Roles, Third Party Software Configuration

2. Keystore Options

50. Environment Installation Options



Note:

The <ORACLE_CLIENT_HOME> is the location where Oracle Database Client is installed. This is required to execute the Perl installation utilities.

If the ORACLE_CLIENT_HOME environment variable is set, the installation utility will not request you to provide this information.

13. Type 1 to define values for the third party software configuration, and then press Enter. The utility prompts you to enter values for a list of menu options.

14. Specify the required value for menu options, and then press Enter.

Note: For more details about these menu options, refer to the Environment ID, Roles, Third Party Software Configuration section in Oracle Revenue Management and Billing Installation Guide.

15. Type 2 to define values for the keystore options, and then press Enter. The utility prompts you to enter values for a list of menu options.


Note: For more details about these menu options, refer to the Keystore Options section in Oracle Revenue Management and Billing Installation Guide.

17. Type 50 to define values for the environment installation options, and then press Enter. The utility prompts you to enter values for a list of menu options.

18. Specify the required value for menu options, and then press Enter. The specified values are stored in the $SPLEBASE/etc/ENVIRON.INI file.

Note:

$SPLEBASE or %SPLEBASE% is the path where the application environment is installed.

Before you specify the environment installation options, ensure that you have created an output directory named Log File Mount Point. If this output directory does not exist, the installation will not be successfully executed.

For more details about these menu options, refer to the Environment Installation Options section in Oracle Revenue Management and Billing Installation Guide.

19. Type P to proceed with the installation. The following environment configuration menus appear in the command line:

Environment Description

Business Application Server Configuration

Web Application Server Configuration

Database Configuration

General Configuration Options

SSL Certificate Keystore

OUAF TrustStore Options

20. Type 1, and then press Enter. The utility prompts you to enter the environment description.

21. Specify the environment description, and then press Enter.



Note: For more details, refer to the Environment Description section in Oracle Revenue Management and Billing Installation Guide.

22. Type 2 to define values for the business application server configuration, and then press Enter. The utility prompts you to enter values for a list of menu options.


Note: For more details, refer to the Business Application Server Configuration section in Oracle Revenue Management and Billing Installation Guide.

24. Type 3 to define values for the web application server configuration, and then press Enter. The utility prompts you to enter values for a list of menu options.


Note: For more details, refer to the Web Application Server Configuration section in Oracle Revenue Management and Billing Installation Guide.

26. Type 4 to define values for the database configuration, and then press Enter. The utility prompts you to enter values for a list of menu options.


Note: For more details about these menu options, refer to the Database Configuration section in Oracle Revenue Management and Billing Installation Guide.

28. Type 5 to define values for the general configuration options, and then press Enter. The utility prompts you to enter values for a list of menu options.


Note: For more details about these menu options, refer to the General Configuration Options section in Oracle Revenue Management and Billing Installation Guide.

30. Type 6 to define values for the SSL certificate keystore options, and then press Enter. The utility prompts you to enter values for a list of menu options.


Note: For more details about these menu options, refer to the SSL Certificate Keystore section in Oracle Revenue Management and Billing Installation Guide.

32. Type 7 to define values for the OUAF TrustStore Options, and then press Enter. The utility prompts you to enter values for a list of menu options.


Note: For more details about these menu options, refer to the OUAF TrustStore Options section in Oracle Revenue Management and Billing Installation Guide.

34. Type P to proceed with the installation. The Oracle Utilities Application Framework Version 4.3.0.4.0 is installed on the application server.

Note:

The utility contains default values for some of the menu options. If required, you can change their values. While executing the install utility, you must set the value for all menu options. Otherwise, the installation process will not be completed successfully.



The values that you specify for the menu options are stored in the $SPLEBASE/etc/ENVIRON.INI file.

Once the installation process is completed, the following utilities are automatically executed in the specified order:

1. initialSetup - The initialSetup utility updates the configuration files including the WAR files on the system. On the UNIX machine, this utility is available in the $SPLEBASE/bin directory. And, on the Windows machine, this utility is available in the %SPLEBASE%\bin directory.

2. splenviron – The splenviron utility sets the environment variables using the ENVIRON.INI

file. On the UNIX machine, this utility is available in the $SPLEBASE/bin directory. And, on the Windows machine, this utility is available in the %SPLEBASE%\bin directory. The following are some of the key environment variables that are set using the splenviron utility:

$PATH

$SPLEBASE (%SPLEBASE%) – Indicates the <SPLDIR>/<SPLENVIRON> directory

$SPLOUTPUT (%SPLOUTPUT%) - Indicates the <SPLDIROUT>/<SPLENVIRON> directory

$SPLENVIRON (%SPLENVIRON%) – Indicates the environment name

For future operations or any post installation steps, you need to first execute the following command to connect your session to the new environment:

AIX, Linux:

$SPLEBASE/bin/splenviron.sh -e $SPLENVIRON

Windows:

%SPLEBASE%\bin\splenviron.cmd -e %SPLENVIRON%

You need to execute this script each time you want to be connected to the specific environment before performing manual operations such as shutdown, startup or performing an additional application product installation.

When you have finished the install process, your current online session will be connected to the new environment.

2.4.2 Installing Rollup Pack for OUAF Version 4.3.0.4.0

To install the rollup pack for Oracle Utilities Application Framework Version 4.3.0.4.0 on the application environment:

1. Copy the RMB-V26010-FW-PREREQ-MultiPlatform file to the TEMPDIR folder using the following command:

AIX, Linux:


Windows:


Note:



The RMB-V26010-FW-PREREQ-MultiPlatform.zip file is available at the location where you have extracted the contents of the RMB V2.6.0.1.0 - <Domain> patch.

You can also use File Transfer Protocol (FTP) to transfer the downloaded file from one host to another. You must use the binary mode while copying files through FTP.


AIX, Linux:

cd <PATH>/TEMPDIR

Windows:

cd <PATH>\TEMPDIR

3. Unzip the RMB-V26010-FW-PREREQ-MultiPlatform file using the following command:

AIX, Linux:


Windows:


The contents of the zip file are extracted in the <DESTINATION_FOLDER_2> folder. The contents include the ORMB-V26010-FW-PREREQ-MultiPlatform.jar file.


jar -xvf ORMB-V26010-FW-PREREQ-MultiPlatform.jar

A sub-directory named FW-V4.3.0.4.0-Rollup is extracted. It contains the following two sub-folders:

Application

Database

5. Initialize the application environment where you want to install the rollup pack using the following command:

AIX, Linux:


Windows:


6. Change to the Application directory using the following command:

AIX, Linux:

cd <DESTINATION_FOLDER_2>/FW-V4.3.0.4.0-Rollup/Application

Windows:

cd <DESTINATION_FOLDER_2>\FW-V4.3.0.4.0-Rollup\Application

Note: The <DESTINATION_FOLDER_2> folder is the location where you have extracted the contents

of the ORMB-V26010-FW-PREREQ-MultiPlatform.jar file.



7. Execute the installSFgroup utility using the following command:

AIX, Linux:

chmod a+x installSFgroup.sh

chmod a+x FW*/*.sh

./installSFgroup.sh

Windows:

installSFgroup.cmd


Ready to process patches, Do you want to continue? (Y/N)

8. Type Y in the command line, and then press Enter. A message appears indicating that the process has been completed successfully.

2.5 Installing the ORMB Application This section explains how to install the application. You need to install the following on the application environment:

1. Oracle Revenue Management and Billing (ORMB) Version 2.6.0.1.0

Note: If you have updated the template files in the $SPLEBASE/etc folder, you must also take a backup of these files. Once the application is installed on the new application environment, you need to

copy the latest template files in the $SPLEBASE/etc folder.

2.5.1 Installing ORMB Version 2.6.0.1.0

To install Oracle Revenue Management and Billing (ORMB) Version 2.6.0.1.0 on the application environment:


2. Copy the RMB-V2.6.0.1.0-MultiPlatform file to the TEMPDIR folder using the following command:

AIX, Linux:


Windows:


Note:

The RMB-V2.6.0.1.0-MultiPlatform.zip file is available at the location where you have extracted the contents of the RMB V2.6.0.1.0 - <Domain> patch.





AIX, Linux:

cd <PATH>/TEMPDIR

Windows:

cd <PATH>\TEMPDIR

4. Unzip the RMB-V2.6.0.1.0-MultiPlatform file using the following command:

AIX, Linux:


Windows:


The contents of the zip file are extracted in the <DESTINATION_FOLDER_3> folder. The contents include ORMB.V2.6.0.1.0 folder.

5. Initialize the application environment (on which you want to install the application) using the following command:

AIX, Linux:


Windows:


6. Stop the application environment using the following command:

AIX, Linux:

$SPLEBASE/bin/spl.sh stop

Windows:

%SPLEBASE%\bin\spl.cmd stop

7. Set the Java Home path using the following command:

AIX, Linux:

export PATH=<Java_Home>/bin:$PATH

Note:

The <Java_Home> is the location where you have installed Java 1.8.


8. Change to the ORMB.V2.6.0.1.0 folder using the following command:

AIX, Linux:

cd <DESTINATION_FOLDER_3>/ORMB.V2.6.0.1.0

Windows:

cd <DESTINATION_FOLDER_3>\ORMB.V2.6.0.1.0



9. Execute the install utility using the following command:

AIX, Linux:

./install.sh

Windows:

install.cmd


Do you wish to proceed with the installation? Y/N:

10. Type Y and then press Enter. A message appears informing you to type P if you want to proceed with the installation.

11. Type P, and then press Enter. The installation process might take some time to generate the WAR files. Once the build is deployed successfully, the following message appears in the command line:

Do you wish to start the environment now? Y/N:

12. Type N and then press Enter.

Note:

If you want to set the advanced menu options, execute the configureEnv utility using the following command:

AIX, Linux:

$SPLEBASE/bin/configureEnv.sh –a

Windows:

%SPLEBASE%\bin\configureEnv.cmd -a

You cannot set the advanced menu options during the installation process. These options can be set only after the application is installed. For more information, refer to the Advanced Menu Options

section in the Oracle Revenue Management and Billing Installation Guide.

13. Execute the initialSetup utility using the following command:

AIX, Linux:

$SPLEBASE/bin/initialSetup.sh

Windows:

%SPLEBASE%\bin\initialSetup.cmd

14. If you are using demo certificates, execute the following commands before starting the environment:

AIX, Linux:

cd $SPLEBASE/bin

perl demo_gen_cert.plx



Windows:

cd %SPLEBASE%\bin

perl demo_gen_cert.plx

2.5.2 Post Installation Tasks

Once you install Oracle Revenue Management and Billing (ORMB) Version 2.6.0.1.0, you need to apply the following patches on the application environment:




UPDATE ORMB VERSION 2.6.0.1.0 ONLINE HELP (Patch Number: 27190574)

2.5.2.1 Applying the 27142924 Patch

Once you install ORMB, you need to apply the MANDATORY PATCH 1 FOR ORMB VERSION 2.6.0.1.0 patch (Patch Number: 27142924). To apply the MANDATORY PATCH 1 FOR ORMB VERSION 2.6.0.1.0 patch:

1. Copy the MANDATORY PATCH 1 FOR ORMB VERSION 2.6.0.1.0 patch to the TEMPDIR folder using the following command:

AIX, Linux:


Windows:




AIX, Linux:

cd <PATH>/TEMPDIR

Windows:

cd <PATH>\TEMPDIR

3. Unzip the MANDATORY PATCH 1 FOR ORMB VERSION 2.6.0.1.0 patch using the following command:

AIX, Linux:


Windows:




The contents of the zip file are extracted in the <DESTINATION_FOLDER_4> folder. The contents

include three files - README.txt, MultiPlatform.zip, and Bug_27142924_Product_Fix_Design.pdf.

4. Unzip the MultiPlatform file using the following command:

AIX, Linux:

Unzip <DESTINATION_FOLDER_4>/MultiPlatform.zip –d


Windows:

unzip <DESTINATION_FOLDER_4>\MultiPlatform.zip –d


The contents of the zip file are extracted in the <DESTINATION_FOLDER_5> folder. The

contents include the V2.6.0.1.0-27142924_MultiPlatform folder.

5. Change to the V2.6.0.1.0-27142924_MultiPlatform folder using the following command:

AIX, Linux:

cd <DESTINATION_FOLDER_5>/V2.6.0.1.0-27142924_MultiPlatform

Windows:

cd <DESTINATION_FOLDER_5>\V2.6.0.1.0-27142924_MultiPlatform

Note: The <DESTINATION_FOLDER_5> folder is the location where you have extracted the contents of the MultiPlatform.zip file.

The contents include a file named CCB.V2.6.0.1.0-27142924.jar and a folder named database.

6. Decompress the CCB.V2.6.0.1.0-27142924.jar file using the following command:

jar -xvf CCB.V2.6.0.1.0-27142924.jar

The contents include two folders - META-INF and CCB.V2.6.0.1.0-27142924.

7. Initialize the application environment (on which you want to install the patch) using the following command:

AIX, Linux:


Windows:


8. Change to the CCB.V2.6.0.1.0-27142924 folder using the following command:

AIX, Linux:

cd <DESTINATION_FOLDER_5>/V2.6.0.1.0-

27142924_MultiPlatform/CCB.V2.6.0.1.0-27142924



Windows:

cd <DESTINATION_FOLDER_5>\V2.6.0.1.0-

27142924_MultiPlatform\CCB.V2.6.0.1.0-27142924

Note: The V2.6.0.1.0-27142924_MultiPlatform folder is the location where you have

extracted the contents of the CCB.V2.6.0.1.0-27142924.jar file.

9. Install the patch using the following command:

AIX, Linux:

./installSF.sh

Windows:

installSF.cmd


Once you apply the MANDATORY PATCH 1 FOR ORMB VERSION 2.6.0.1.0 patch, you need to apply the MANDATORY PATCH 2 FOR ORMB VERSION 2.6.0.1.0 patch (Patch

Number: 27167578). To apply the MANDATORY PATCH 2 FOR ORMB VERSION 2.6.0.1.0 patch:

1. Copy the MANDATORY PATCH 2 FOR ORMB VERSION 2.6.0.1.0 patch to the

TEMPDIR folder using the following command:

AIX, Linux:


Windows:




AIX, Linux:

cd <PATH>/TEMPDIR

Windows:

cd <PATH>\TEMPDIR


AIX, Linux:


Windows:





contents include three files - README.txt, MultiPlatform.zip, and

Bug_27167578_Product_Fix_Design.pdf.


AIX, Linux:

unzip <DESTINATION_FOLDER_6>/MultiPlatform.zip –d


Windows:






AIX, Linux:


Windows:





jar -xvf CCB.V2.6.0.1.0-27167578.jar



AIX, Linux:


Windows:



AIX, Linux:





Windows:






AIX, Linux:

./installSF.sh

Windows:

installSF.cmd


Once you apply the MANDATORY PATCH 2 FOR ORMB VERSION 2.6.0.1.0 patch, you need to apply the MANDATORY PATCH 3 FOR ORMB VERSION 2.6.0.1.0 patch (Patch

Number: 27183538). To apply the MANDATORY PATCH 3 FOR ORMB VERSION 2.6.0.1.0 patch:

1. Copy the MANDATORY PATCH 3 FOR ORMB VERSION 2.6.0.1.0 patch to the

TEMPDIR folder using the following command:

AIX, Linux:


Windows:




AIX, Linux:

cd <PATH>/TEMPDIR

Windows:

cd <PATH>\TEMPDIR


AIX, Linux:


Windows:





contents include three files - README.txt, MultiPlatform.zip, and Bug_27183538_Product_Fix_Design.pdf.


AIX, Linux:



Windows:






AIX, Linux:


Windows:





jar -xvf CCB.V2.6.0.1.0-27183538.jar



AIX, Linux:


Windows:



AIX, Linux:





Windows:






AIX, Linux:

./installSF.sh

Windows:

installSF.cmd


Once you apply the MANDATORY PATCH 3 FOR ORMB VERSION 2.6.0.1.0 patch, you need to apply the UPDATE ORMB VERSION 2.6.0.1.0 ONLINE HELP patch (Patch Number: 27190574). To apply the UPDATE ORMB VERSION 2.6.0.1.0 ONLINE HELP patch:

1. Copy the UPDATE ORMB VERSION 2.6.0.1.0 ONLINE HELP patch to the TEMPDIR folder using the following command:

AIX, Linux:


Windows:




AIX, Linux:

cd <PATH>/TEMPDIR

Windows:

cd <PATH>\TEMPDIR

3. Unzip the UPDATE ORMB VERSION 2.6.0.1.0 ONLINE HELP patch using the following command:

AIX, Linux:


Windows:


The contents of the zip file are extracted in the <DESTINATION_FOLDER_10> folder. The contents include three files - README.txt, MultiPlatform.zip, and





AIX, Linux:



Windows:



The contents of the zip file are extracted in the <DESTINATION_FOLDER_9> folder. The contents include the V2.6.0.1.0-27190574_MultiPlatform folder.


AIX, Linux:


Windows:



The contents include a file named CCB.V2.6.0.1.0-27190574.jar.


jar -xvf CCB.V2.6.0.1.0-27190574.jar



AIX, Linux:


Windows:



AIX, Linux:



Windows:



Note: The V2.6.0.1.0-27190574_MultiPlatform folder is the location where you have extracted the contents of the CCB.V2.6.0.1.0-27190574.jar file.




AIX, Linux:

./installSF.sh

Windows:

installSF.cmd

10. Start the application environment using the following command:

AIX, Linux:

$SPLEBASE/bin/spl.sh start

Windows:

%SPLEBASE%\bin\spl.cmd start

A log file is generated. It indicates whether the application environment has started successfully or not. If any error occurred during startup, the same is recorded in the log file. By default, the log file is stored in the $SPLSYSTEMLOGS (%SPLSYSTEMLOGS% on Windows) directory.

2.5.3 Accessing the ORMB Application

The following table lists the URLs that you can use to access the application on various application servers:

Application Server URL

WebLogic https://<hostname>:<WebLogic_Port_Number>/ouaf/loginPage.jsp

2.6 Upgrading the ORMB Database This section explains how to upgrade the database. When you upgrade the database, the system overwrites the database schema and the metadata present in the database. However, the transactional data is not affected.

While upgrading from Oracle Revenue Management and Billing Version 2.6.0.0.0 to 2.6.0.1.0, you need to install the following on the database:

1. Oracle Revenue Management and Billing (ORMB) Version 2.6.0.1.0

2. MANDATORY PATCH 1 FOR ORMB VERSION 2.6.0.1.0 (Patch Number: 27142924)



Note:

Before you upgrade the database, you must take a backup of the existing database.

When you upgrade the database, any metadata with the Owner flag set to CM is not overridden during the upgrade process.



Pre-requisites:

Before installing Oracle Revenue Management and Billing Version 2.6.0.1.0 on the database, you need to set the MAX_STRING_SIZE parameter to EXTENDED. If you have a non-container database, you need to perform the following steps to set the MAX_STRING_SIZE parameter to EXTENDED:

1. Set the ORACLE_HOME and ORACLE_SID environment variables.

Note: You need to connect as system administrator while executing the below steps.

2. Shutdown the target database using the following command:

shutdown immediate

3. Start the database in the Upgrade mode using the following command:

startup upgrade

4. Set the MAX_STRING_SIZE parameter to EXTENDED using the following command:

alter system set max_string_size=extended scope=both;

5. Execute the utl32k.sql file using the following command:

@?/rdbms/admin/utl32k.sql;

6. Restart the database in the Normal mode using the following commands:

shutdown immediate

startup

However, if you have a container database, you need to perform the following steps to set the MAX_STRING_SIZE parameter to EXTENDED:

1. Set the ORACLE_HOME and ORACLE_SID environment variables.

Note: You need to connect as system administrator while executing the below steps.

2. Set the MAX_STRING_SIZE parameter to EXTENDED using the following command:

alter system set max_string_size=extended scope=spfile;

3. Start all pluggable databases in the Upgrade mode using the following command:

shutdown immediate

startup upgrade

alter pluggable database all open upgrade;

exit

4. Create the utl32k_cdb_pdbs_output folder to store the log files using the following command:

mkdir /scratch/mydir/utl32k_cdb_pdbs_output

5. Execute the utl32k.sql from the catcon.pl file for all pluggable databases using the following command:

cd $ORACLE_HOME/rdbms/admin

$ORACLE_HOME/perl/bin/perl $ORACLE_HOME/rdbms/admin/catcon.pl -u

SYS -d ORACLE_HOME/rdbms/admin –l

'/scratch/mydir/utl32k_cdb_pdbs_output' –b

utl32k_cdb_pdbs_output utl32k.sql

6. Restart the database in the Normal mode using the following commands:



shutdown immediate

startup

alter pluggable database all open read write;

2.6.1 Installing ORMB Version 2.6.0.1.0

You can install Oracle Revenue Management and Billing (ORMB) Version 2.6.0.1.0 either using the Interactive or Command Line mode of the OraDBI (Java) utility. To install Oracle Revenue Management and Billing (ORMB) Version 2.6.0.1.0 using the Interactive mode of the utility:

1. Copy the RMB-V2.6.0.1.0-Oracle-Database-MultiPlatform file to the TEMPDIR folder using the following command:

AIX, Linux:


Windows:


Note:

The RMB-V2.6.0.1.0-Oracle-Database-MultiPlatform.zip file is available at the location where you have extracted the contents of the RMB V2.6.0.1.0 - <Domain> patch.



AIX, Linux:

cd <PATH>/TEMPDIR

Windows:

cd <PATH>\TEMPDIR

3. Unzip the RMB-V2.6.0.1.0-Oracle-Database-MultiPlatform file using the following command:

AIX, Linux:


Windows:


The contents of the zip file are extracted in the <DESTINATION_FOLDER_2> folder. The contents include the following sub-folders:

FW

RMB

4. Set the JAVA_HOME environment variable using the following command:

Windows:

SET JAVA_HOME=<JAVA_HOME_PATH>



AIX, Linux:

export JAVA_HOME=<JAVA_HOME_PATH>

Note: The <JAVA_HOME_PATH> is the location where Java Development Kit Version 8.0 is installed.

5. Set the JAR_PATH environment variable using the following command:

AIX, Linux:

export JAR_PATH=<DESTINATION_FOLDER_2>/RMB/jarfiles

Note:


6. Set the CLASS_PATH environment variable using the following command:

Windows:

SET CLASS_PATH=<DESTINATION_FOLDER_2>\RMB\jarfiles\*

AIX, Linux:

export CLASS_PATH=${JAR_PATH}/ojdbc7-

12.1.0.2.jar:${JAR_PATH}/log4j-1.2.17.jar:${JAR_PATH}/commons-

collections-3.2.2.jar:${JAR_PATH}/commons-codec-

1.9.jar:${JAR_PATH}/commons-cli-1.1.jar:${JAR_PATH}/spl-shared-

4.3.0.4.0.jar:${JAR_PATH}/oradbi.jar

7. Change to the Install-Upgrade directory using the following command:

Windows:

cd <DESTINATION_FOLDER_2>\RMB\Upgrade\Oracle\Install-Upgrade

AIX, Linux:

cd <DESTINATION_FOLDER_2>/RMB/Upgrade/Oracle/Install-Upgrade

8. Execute the OraDBI (Java) utility using the following command:

Windows:

<Java_Home>\bin\java -Xmx1500M -cp

<DESTINATION_FOLDER_1>\RMB\jarfiles\*

com.oracle.ouaf.oem.install.OraDBI

AIX, Linux:

${JAVA_HOME}/bin/java -Xmx1500M -cp ${CLASS_PATH}

com.oracle.ouaf.oem.install.OraDBI

This utility prompts you to enter values for the following parameters:

Parameter Value

Enter the database server hostname <DB_SERVER>

Enter the database port number(e.g. 1521) <DB_PORT>

Enter the database name/SID <DB_NAME>



Parameter Value

Enter your database username <DB_USER>

Example: CISADM

Enter your password for username <DB_USER> <DB_USER_PASSWORD>

Enter the location for Java Home (e.g. C:\Java\jdk1.6.0_18) ..\jdk1.8.0_111

Enter the Oracle user with read-write privileges to Database Schema(e.g. CISUSER)

<DB_USER>

Example: CISUSER

Enter the Oracle user with read-only privileges to Database Schema(e.g. CISREAD)

<DB_USER>

Example: CISREAD

Enter the database role with read-write privileges to Database Schema(e.g. CIS_USER)

<DB_USER_ROLE>

Example: CIS_USER

Enter the database role with read-only privileges to Database Schema(e.g. CIS_READ)

<DB_USER_ROLE>

Example: CIS_READ

Enter the name of the target Schema where you want to install or upgrade

<Schema_Name>

9. Enter the required parameter values. The following message appears in the command line:

Ready to upgrade the target database from V2.6.0.0.0 to

V2.6.0.1.0, do you want to continue (Y/N)?

10. Type Y and then press Enter. A message appears indicating that the process is completed successfully.

To install Oracle Revenue Management and Billing (ORMB) Version 2.6.0.1.0 using the Command Line mode of the utility:

1. Copy the RMB-V2.6.0.1.0-Oracle-Database-MultiPlatform file to the TEMPDIR folder using the following command:

AIX, Linux:


Windows:


Note:

The RMB-V2.6.0.1.0-Oracle-Database-MultiPlatform.zip file is available at the location where you have extracted the contents of the RMB V2.6.0.1.0 - <Domain> patch.



AIX, Linux:

cd <PATH>/TEMPDIR



Windows:

cd <PATH>\TEMPDIR

3. Unzip the RMB-V2.6.0.1.0-Oracle-Database-MultiPlatform file using the following command:

AIX, Linux:


Windows:


The contents of the zip file are extracted in the <DESTINATION_FOLDER_2> folder. The contents include the following sub-folders:

FW

RMB

4. Set the JAVA_HOME environment variable using the following command:

Windows:

SET JAVA_HOME=<JAVA_HOME_PATH>

AIX, Linux:

export JAVA_HOME=<JAVA_HOME_PATH>

Note: The <JAVA_HOME_PATH> is the location where Java Development Kit Version 8.0 is installed.

5. Set the JAR_PATH environment variable using the following command:

AIX, Linux:

export JAR_PATH=<DESTINATION_FOLDER_2>/RMB/jarfiles

Note: The above command is applicable only for Linux platform.

6. Set the CLASS_PATH environment variable using the following command:

Windows:

SET CLASS_PATH=<DESTINATION_FOLDER_2>\RMB\jarfiles\*

AIX, Linux:

export CLASS_PATH=${JAR_PATH}/ojdbc7-

12.1.0.2.jar:${JAR_PATH}/log4j-1.2.17.jar:${JAR_PATH}/commons-

collections-3.2.2.jar:${JAR_PATH}/commons-codec-

1.9.jar:${JAR_PATH}/commons-cli-1.1.jar:${JAR_PATH}/spl-shared-

4.3.0.4.0.jar:${JAR_PATH}/oradbi.jar

7. Create the detail.txt file with the following details:

-d jdbc:oracle:thin:@<Database-host>:<port>/<DB-SID>,<schema-

user>,<schema-password>,<read-write-user>,<read-user>,<read-

write-role>,<read-role>,<schema-user> -l 1,2 -j <JAVA_HOME> -q

true

8. Change to the Install-Upgrade directory using the following command:



Windows:

cd <DESTINATION_FOLDER_2>\RMB\Upgrade\Oracle\Install-Upgrade

AIX, Linux:

cd <DESTINATION_FOLDER_2>/RMB/Upgrade/Oracle/Install-Upgrade

9. Execute the OraDBI (Java) utility using the following command:

Windows:

<Java_Home>\bin\java -Xmx1500M -cp

<DESTINATION_FOLDER_1>\RMB\jarfiles\*

com.oracle.ouaf.oem.install.OraDBI -f detail.txt

AIX, Linux:

${JAVA_HOME}/bin/java -Xmx1500M -cp ${CLASS_PATH}

com.oracle.ouaf.oem.install.OraDBI -f detail.txt

A message appears indicating that the process is completed

successfully.

2.6.2 Applying the 27142924 Patch

Once you install ORMB, you need to apply the MANDATORY PATCH 1 FOR ORMB VERSION 2.6.0.1.0 patch (Patch Number: 27142924). You can apply this patch from a Windows machine and UNIX Standalone server.

To apply the MANDATORY PATCH 1 FOR ORMB VERSION 2.6.0.1.0 patch:


AIX, Linux:


Windows:




AIX, Linux:

cd <PATH>/TEMPDIR

Windows:

cd <PATH>\TEMPDIR




AIX, Linux:


Windows:


The contents of the zip file are extracted in the <DESTINATION_FOLDER_3> folder. The contents include three files - README.txt, MultiPlatform.zip, and



AIX, Linux:



Windows:






AIX, Linux:


Windows:




6. Change to the ORACLE folder using the following command:

AIX, Linux:

cd database/ORACLE

Windows:

cd database\ORACLE

The contents include a zip file named CDXPatch.

7. Unzip the CDXPatch file using the following command:

AIX, Linux:

unzip CDXPatch.zip –d <PATH>/<DESTINATION_FOLDER_5>



Windows:

unzip CDXPatch.zip –d <PATH>\<DESTINATION_FOLDER_5>

The contents of the zip file are extracted in the <DESTINATION_FOLDER_5> folder. The contents include utility files and a folder named 27142924.

8. Ensure that TOOLSBIN environment variable is set using the following command:

AIX, Linux:


Windows:


Note: The dbpatch_tools folder is the location where you have extracted the contents of

db_patch_standalone.jar file.


AIX, Linux:


Windows:



AIX, Linux:


Windows:



Once you apply the MANDATORY PATCH 1 FOR ORMB VERSION 2.6.0.1.0 patch, you need to apply the MANDATORY PATCH 2 FOR ORMB VERSION 2.6.0.1.0 patch (Patch Number: 27167578). You can apply this patch from a Windows machine and UNIX Standalone server.



AIX, Linux:


Windows:






AIX, Linux:

cd <PATH>/TEMPDIR

Windows:

cd <PATH>\TEMPDIR


AIX, Linux:


Windows:



include three files - README.txt, MultiPlatform.zip, and



AIX, Linux:



Windows:





AIX, Linux:


Windows:





AIX, Linux:

cd database/ORACLE



Windows:

cd database\ORACLE



AIX, Linux:


Windows:




AIX, Linux:


Windows:


Note: The dbpatch_tools folder is the location where you have extracted the contents of db_patch_standalone.jar file.


AIX, Linux:


Windows:



AIX, Linux:


Windows:





Once you apply the MANDATORY PATCH 2 FOR ORMB VERSION 2.6.0.1.0 patch, you need to apply the MANDATORY PATCH 3 FOR ORMB VERSION 2.6.0.1.0 patch (Patch Number: 27183538). You can apply this patch from a Windows machine and UNIX Standalone server.



AIX, Linux:


Windows:




AIX, Linux:

cd <PATH>/TEMPDIR

Windows:

cd <PATH>\TEMPDIR


AIX, Linux:


Windows:



include three files - README.txt, MultiPlatform.zip, and



AIX, Linux:



Windows:







AIX, Linux:


Windows:





AIX, Linux:

cd database/ORACLE

Windows:

cd database\ORACLE



AIX, Linux:


Windows:




AIX, Linux:


Windows:


Note: The dbpatch_tools folder is the location where you have extracted the contents of db_patch_standalone.jar file.


AIX, Linux:


Windows:





AIX, Linux:


Windows:


2.7 Migrating Data If you are already using the Deferred Revenue Recognition feature and want to upgrade to the ORMB V2.6.0.1.0, you need to execute the Upgrade Batch for Deferred Revenue Recognition (C1-RRUPG) batch to migrate the data from the previous release to the new release. It considers all existing deferred revenue recognitions which are in the Draft or Active status. It then derives the deferred revenue recognition template for the distribution code and contract type combination on the financial transaction and stamps it in the DRR_TEMPLATE_CD column corresponding to the record in the CI_REV_REC_SCH table. If all lines in the schedule are recognized, the status of the deferred revenue recognition is set to Closed in the BO_STATUS_CD column of the CI_REV_REC_SCH table. If few or all lines in the schedule are not recognized, the status of the deferred revenue recognition is set to Active in the BO_STATUS_CD column of the CI_REV_REC_SCH table.

Note:

For more information about the Upgrade Batch for Deferred Revenue Recognition (C1-RRUPG) batch, refer to Appendix J: Upgrade Batch for Deferred Revenue Recognition (C1-RRUPG).

Before executing this batch, you need to create deferred revenue recognition template for each distribution code and contract type combination for which deferred revenue recognitions exist in the system.



3. Additional Tasks This section describes the following tasks that you need to perform after upgrading the application:

Generating the Application Viewer

Starting the Thread Pool Worker

Building Javadoc Index

3.1 Generating the Application Viewer Once you upgrade the application, you need to regenerate the application viewer. To regenerate the application viewer:


2. Initialize the application environment (on which you want to regenerate the application viewer) using the following command:

AIX, Linux:


Windows:


Where, $SPLEBASE or %SPLEBASE% is the path where the application environment is

installed, and $SPLENVIRON or %SPLEBASE% is the name of the application environment for which you want to set the environment variables.

3. Set the ANT_OPTS environment variable using the following command:

Windows:

Set ANT_OPTS= -Xms512m -Xmx1024m -XX:PermSize=256M

Note: This command helps to process some tasks which require more memory. This command is only applicable for Windows and not for Linux machine.

4. Execute the genappvieweritems utility using the following command:

AIX, Linux:

$SPLEBASE/bin/genappvieweritems.sh

Windows:

%SPLEBASE%\bin\genappvieweritems.cmd

If the application viewer is generated successfully, the response code is set to 0. However, if you get any other response code other than 0, it means an error has occurred while generating the application viewer. A log file is created in the $SPLEBASE/logs folder.



5. Execute the initialSetup utility using the following command:

AIX, Linux:


Windows:


Where, $SPLEBASE or %SPLEBASE% is the path where the application environment is installed.

The initialSetup utility updates the configuration files including the WAR files on the system.

3.2 Starting the Thread Pool Worker Once you upgrade the application, you need to start the thread pool worker. The thread pool worker is required when you execute batches either online or through batch scheduler.

You can use the Distributed Thread Pool property of the thread pool worker to set the number of threads that can run concurrently. By default, 5 threads run concurrently. You can change the default

value by editing the following line in the threadpoolworker.properties file:

com.splwg.grid.distThreadPool.threads.DEFAULT=5

To start the thread pool worker, use the following command once you initialize the application environment:

AIX, Linux:

$SPLEBASE/bin/threadpoolworker.sh

Windows:

%SPLEBASE%\bin\threadpoolworker.cmd


3.3 Building Javadoc Index Once you upgrade the application, you may want to regenerate the index file of Javadoc documentation. You must regenerate the Javadoc index file only when some modifications are made to the Java code.

To regenerate the Javadoc index file, use the following command:

AIX, Linux:

$SPLEBASE/bin/buildJavadocsIndex.sh

Windows:

%SPLEBASE%\bin\buildJavadocsIndex.cmd




Appendix A : ORMB 2.6.0.1.0 Patch Numbers Oracle Revenue Management and Billing Version 2.6.0.1.0 application service pack (patch) is common for all platforms. The following table lists the contents of each domain-specific patch:

Domain Patch Number Contents Include

Banking 27167595 RMB-V2.6.0.1.0-MultiPlatform

RMB-V26010-FW-PREREQ-MultiPlatform

RMB-V2.6.0.1.0-Oracle-Database-MultiPlatform

Insurance 27167643 RMB-V2.6.0.1.0-MultiPlatform

RMB-V26010-FW-PREREQ-MultiPlatform

RMB-V2.6.0.1.0-Oracle-Database-MultiPlatform



Appendix B : Known Issues To view a list of known issues in the current release, refer to Oracle Revenue Management and Billing Version 2.6.0.1.0 Release Notes.



Appendix C : Third Party Software Upgrade To view a list of third party software that you need to upgrade before upgrading the application, refer to the Upgrade Prerequisites section in the Oracle Revenue Management and Billing Upgrade Path Guide.



Appendix D : New Tables Added in 2.6.0.1.0 This section lists and describes the tables that are newly added in the Oracle Revenue Management and Billing Version 2.6.0.1.0 database.

D.1 CI_ACCT_APAY_CHAR

Purpose: Used to store characteristics defined for an auto pay instruction of an account.

Total Number of Columns: 12

Column Details:

Column Name Data Type Nullable (Yes or No) Default Value

ACCT_APAY_ID CHAR(10) No -

CHAR_TYPE_CD CHAR(8) No -

CHAR_VAL CHAR(16) No ' '

ADHOC_CHAR_VAL VARCHAR2(254) No ' '

CHAR_VAL_FK1 VARCHAR2(50) No ' '





SRCH_CHAR_VAL VARCHAR2(254) No ' '

VERSION NUMBER(5) No 1

SEQ_NUM NUMBER(5) No -

Primary Key:

Key Type Column Name

COMPOSITE ACCT_APAY_ID

CHAR_TYPE_CD

SEQ_NUM



Indexes:

Sr. No. Index Name Index Type Column Name

1. XF732P0 Unique ACCT_APAY_ID

CHAR_TYPE_CD

SEQ_NUM

XF732S01 Normal SRCH_CHAR_VAL

D.2 C1_ACCRUAL_CHAR

Purpose: Used to store characteristics defined for an accrual.


Column Details:


ACCR_ID CHAR(19) No -


EFFDT DATE No -

ADHOC_CHAR_VAL VARCHAR2(254) Yes -

CHAR_VAL CHAR(16) Yes -

CHAR_VAL_FK1 VARCHAR2(50) Yes -





SRCH_CHAR_VAL VARCHAR2(254) Yes -


Primary Key:


COMPOSITE ACCR_ID

CHAR_TYPE_CD

EFFDT



Indexes:


1. XF744P0 UNIQUE ACCR_ID

CHAR_TYPE_CD

EFFDT

D.3 CI_ADJ_CLR_STG

Purpose: Used to store the details of an adjustment clearing staging record.


Column Details:


APAY_CLR_ID CHAR(12) No -

ACCT_APAY_ID CHAR(10) No ' '

BILL_ID CHAR(12) No ' '

SCHED_EXTRACT_DT DATE Yes -

BATCH_CD CHAR(8) No ' '

BATCH_NBR NUMBER(10) No -

APAY_SRC_CD CHAR(12) No ' '

APAY_RTE_TYPE_CD CHAR(10) Yes ' '

EXT_ACCT_ID VARCHAR2(50) No ' '

EXPIRE_DT DATE Yes -

ENTITY_NAME VARCHAR2(254) No ' '


ACH_ENTITY_ID CHAR(14) No ' '

ACH_ENTITY_TYPE_FLG CHAR(4) No ' '

Primary Key:


SINGLE APAY_CLR_ID



Indexes:


1. XT819P0 UNIQUE APAY_CLR_ID

2. XT819S0 NORMAL BILL_ID

3. XT819S1 NORMAL BATCH_CD

BATCH_NBR

SCHED_EXTRACT_DT

4. XT819S2 NORMAL ACH_ENTITY_ID

D.4 CI_APPTXN_BOCHAIN_FLDRULE

Purpose: Used to store approval rules defined for a field in an approval workflow group chain linkage.


Column Details:


FIELD_RULE_ID CHAR(15) No -

FLD_NAME CHAR(30) No -

APPTXN_BUS_OBJ_CD CHAR(30) No -

APPTXN_CHAIN_REL_ID CHAR(10) No -

APP_CHAIN_CD CHAR(10) No -

VALUE_RANGE_FLG CHAR(1) Yes -

HIERARCHAL_APPR_FLG CHAR(1) Yes 'N'

RULE_APPLICABILITY CHAR(4) Yes 'N'

VERSION NUMBER(5) No -

SEQNO NUMBER(5) No -

Primary Key:


SINGLE FIELD_RULE_ID



Indexes:


1. XF733P0 UNIQUE FIELD_RULE_ID

D.5 CI_APPTXN_BOCHAIN_FLDRULE_THLD

Purpose: Used to store threshold criteria defined in an approval rule for a numeric field.


Column Details:


FIELD_RULE_ID CHAR(15) No -

THRSHLD_SEQ NUMBER(5) No -

APPROVAL_LEVEL NUMBER(5) No -

TD_TYPE_CD CHAR(8) Yes -

CK_ROLE_ID CHAR(10) Yes -


CI_THLD_AMOUNT NUMBER(15,2) Yes -

Primary Key:


COMPOSITE FIELD_RULE_ID

THRSHLD_SEQ

Indexes:


1. XF734P0 UNIQUE FIELD_RULE_ID

THRSHLD_SEQ



D.6 CI_APAY_RT_TYPE_APAY_CHAR

Purpose: Used to store auto pay characteristics associated with an auto pay route type.


Column Details:


APAY_RTE_TYPE_CD CHAR(10) No -












REQUIRED_SW CHAR(1) No ' '

DEFAULT_SW CHAR(1) No ' '

Primary Key:


COMPOSITE APAY_RTE_TYPE_CD

CHAR_TYPE_CD

SEQ_NUM



Indexes:


1. XT722P0 UNIQUE APAY_RTE_TYPE_CD

CHAR_TYPE_CD

SEQ_NUM

2. XT722S1 NORMAL SRCH_CHAR_VAL

D.7 C1_APAY_RULE

Purpose: Used to store the details of a rule based auto pay instruction of an account.


Column Details:


APAY_RULE_ID CHAR(12) No -

ACCT_APAY_ID CHAR(10) No -

DESCR VARCHAR2(60) No ' '


Primary Key:


SINGLE APAY_RULE_ID

Indexes:


1. XF705P0 UNIQUE APAY_RULE_ID

2. XF730S01 NORMAL ACCT_APAY_ID

D.8 C1_APAY_RULE_CRITERIA

Purpose: Used to store the criteria for an auto pay rule.




Column Details:


APAY_RULE_ID CHAR(12) No -


FLD_NAME CHAR(30) No ' '

OPERATOR CHAR(10) No ' '

FLD_VALUE VARCHAR2(254) No ' '


RULE_CRITERIA_TYPE_FLG CHAR(4) No -

RULE_CRITERIA_ENTITY_FLG CHAR(4) No ' '

CHAR_TYPE_CD CHAR(8) No ' '









Primary Key:


COMPOSITE APAY_RULE_ID

SEQ_NUM

Indexes:


1. XF731P0 UNIQUE APAY_RULE_ID

SEQ_NUM

2. XF731S01 NORMAL SRCH_CHAR_VAL



D.9 C1_DRR_TMPLT_L

Purpose: Used to store the description of a deferred revenue recognition template.


Column Details:


DRR_TEMPLATE_CD CHAR(30) No -

LANGUAGE_CD CHAR(3) No -


DESCRLONG VARCHAR2(4000) No ' '


Primary Key:


COMPOSITE DRR_TEMPLATE_CD

LANGUAGE_CD

Indexes:


1. XF737P0 UNIQUE

DRR_TEMPLATE_CD

LANGUAGE_CD

D.10 CI_REV_REC_SCH_CHAR

Purpose: Used to store characteristics defined for a deferred revenue recognition.


Column Details:


REV_REC_ID CHAR(12) No -





EFFDT DATE No ' '










Primary Key:


COMPOSITE REV_REC_ID

CHAR_TYPE_CD

EFFDT

Indexes:


1. XF812P0 UNIQUE REV_REC_ID

CHAR_TYPE_CD

EFFDT


D.11 CI_REV_REC_SCH_LOG_PARM

Purpose: Used to store deferred revenue recognition's log parameters.




Column Details:




PARM_SEQ NUMBER(3) No -

MSG_PARM_TYP_FLG CHAR(4) No ' '

MSG_PARM_VAL VARCHAR2(2000) No ' '


Primary Key:



SEQNO

PARM_SEQ

Indexes:


1. XF703P0

UNIQUE REV_REC_ID

SEQNO

PARM_SEQ

D.12 CI_REV_REC_SCH_LOG

Purpose: Used to store logs of a deferred revenue recognition.


Column Details:




LOG_DTTM DATE No -

LOG_ENTRY_TYPE_FLG CHAR(4) No ' '





BO_STATUS_CD CHAR(12) No ' '

BO_STATUS_REASON_CD VARCHAR2(30) Yes -

MESSAGE_CAT_NBR NUMBER(5) No -

MESSAGE_NBR NUMBER(5) No -









USER_ID CHAR(8) No ' '



Primary Key:



SEQNO

Indexes:


1. XF813P0

UNIQUE

REV_REC_ID

SEQNO

2. XF813S0

NORMAL

CHAR_TYPE_CD

CHAR_VAL_FK1

3. XF813S1

NORMAL

CHAR_TYPE_CD

CHAR_VAL



D.13 C1_DRR_TMPLT

Purpose: Used to store the details of a deferred revenue recognition template.


Column Details:



DST_ID CHAR(10) No ' '

SA_TYPE_CD CHAR(8) No ' '

BUS_OBJ_CD CHAR(30) No ' '


BO_DATA_AREA CLOB Yes -

ALLOW_DRR_EDIT_SW CHAR(1) Yes 'N'

ADJ_TYPE_CD CHAR(8) No ' '

DRR_SCHED_FLG CHAR(4) No ' '

ALLOW_PRO_SW CHAR(1) Yes 'N'

HI_PRO_LIMIT NUMBER(5) Yes -

LO_PRO_LIMIT NUMBER(5) Yes -


DRR_TYPE_FLG CHAR(4) No ' '

C1_ACTIVE_INACTIVE_FLG CHAR(4) No ' '

CIS_DIVISION CHAR(5) No ' '

Primary Key:


SINGLE DRR_TEMPLATE_CD

Indexes:


1. XT989P0 UNIQUE DRR_TEMPLATE_CD



D.14 C1_DRR_TMPLT_ALG

Purpose: Used to store the algorithms associated with a deferred revenue recognition template.


Column Details:



DRR_ALG_ENTITY_FLG CHAR(4) No -

ALG_CD CHAR(12) No ' '



Primary Key:


COMPOSITE DRR_TEMPLATE_CD

SEQNO

DRR_ALG_ENTITY_FLG

Indexes:


1. XT986P0 UNIQUE DRR_TEMPLATE_CD

SEQNO

DRR_ALG_ENTITY_FLG

D.15 C1_DISCREPANCY_RPT

Purpose: Used to store the details of a discrepancy report.




Column Details:


DISCREPANCY_RPT_ID CHAR(12) No -

DSC_RPT_TYPE_CD CHAR(30) Yes ' '

EXTERNAL_REF_ID CHAR(50) Yes ' '

ACCT_ID CHAR(10) Yes ' '

BUS_OBJ_CD CHAR(30) Yes ' '

BO_STATUS_CD CHAR(12) Yes ' '

BO_STATUS_REASON_CD VARCHAR2(30) Yes ' '


STATUS_UPD_DTTM DATE Yes -

CRE_DTTM DATE Yes -

ILM_ARCH_SW CHAR(1) Yes ' '

ILM_DT DATE Yes -

VERSION NUMBER(5) Yes 1

Primary Key:


SINGLE DISCREPANCY_RPT_ID

Indexes:


1. XF818P0 UNIQUE DISCREPANCY_RPT_ID

2. XF818S0 NORMAL ACCT_ID

3. XF818S1 UNIQUE BUS_OBJ_CD

DISCREPANCY_RPT_ID

BO_STATUS_CD

4. XF818S2 NORMAL EXTERNAL_REF_ID

D.16 C1_DISCREPANCY_RPT_CHAR

Purpose: Used to store characteristics defined for a discrepancy report.




Column Details:




EFFDT DATE No -

CHAR_VAL CHAR(16) Yes ' '

ADHOC_CHAR_VAL VARCHAR2(254) Yes ' '

CHAR_VAL_FK1 VARCHAR2(50) Yes ' '





SRCH_CHAR_VAL VARCHAR2(254) Yes ' '


Primary Key:


COMPOSITE DISCREPANCY_RPT_ID

CHAR_TYPE_CD

EFFDT

Indexes:



CHAR_TYPE_CD

EFFDT


D.17 C1_DISCREPANCY_RPT_K

Purpose: Used to store discrepancy report ID.




Column Details:



ENV_ID NUMBER(6) No -

Primary Key:



ENV_ID

Indexes:



ENV_ID

D.18 C1_DISCREPANCY_RPT_LN

Purpose: Used to store the details of each line in the discrepancy report.


Column Details:




ACCT_NBR_TYPE_CD CHAR(8) No ' '

ACCT_NBR VARCHAR2(30) No ' '

ID_TYPE_CD CHAR(8) No ' '

POLICY_NBR VARCHAR2(64) No ' '

PLAN_NBR VARCHAR2(30) No ' '

PER_ID_NBR VARCHAR2(90) No ' '

COV_START_DT DATE Yes -

COV_END_DT DATE Yes -

BILLED_AMT NUMBER(15,2) Yes 0




PAID_AMT NUMBER(15,2) Yes 0

COMMENTS VARCHAR2(254) Yes -

DSC_CAT_FLG CHAR(4) Yes -



ACCT_ID CHAR(10) No ' '

Primary Key:



SEQNO

Indexes:


1. XT909P0 UNIQUE DISCREPANCY_RPT_ID

SEQNO

2. XF820S0 Normal POLICY_NBR

3. XF820S1 Normal PLAN_NBR

4. XF820S2 Normal PER_ID_NBR

5. XF820S3 Normal ACCT_NBR_TYPE_CD

6. XF820S4 Normal ACCT_NBR

7. XF820S5 Normal ID_TYPE_CD

D.19 C1_DISCREPANCY_RPT_LN_CHAR

Purpose: Used to store characteristics defined for each line in the discrepancy report.


Column Details:


DISCREPANCY_RPT_ID CHAR(12) No ' '

SEQNO NUMBER(5) No ' '














Primary Key:



SEQNO

CHAR_TYPE_CD

Indexes:



SEQNO

CHAR_TYPE_CD

D.20 C1_DISCREPANCY_RPT_LN_REL_OBJ

Purpose: Used to store information about the objects related to each line in the discrepancy report.


Column Details:


DISCREPANCY_RPT_ID CHAR(12) No ' '

MAINT_OBJ_CD CHAR(12) No ' '

SEQNO NUMBER(5) No ' '




SEQ_NUM NUMBER(3) No ' '

PK_VALUE1 VARCHAR2(254) Yes ' '





RECON_REL_OBJ_TYPE_FLG CHAR(4) No ' '


Primary Key:



SEQNO

SEQ_NUM

MAINT_OBJ_CD

RECON_REL_OBJ_TYPE_FLG

Indexes:



SEQNO

SEQ_NUM

MAINT_OBJ_CD


2. XF821S0 NORMAL PK_VALUE1

D.21 C1_DISCREPANCY_RPT_LOG

Purpose: Used to store logs of a discrepancy report.




Column Details:




LOG_ENTRY_TYPE_FLG CHAR(4) Yes ' '

LOG_DTTM DATE Yes -

BO_STATUS_CD CHAR(12) Yes ' '

DESCRLONG VARCHAR2(4000) Yes ' '

MESSAGE_CAT_NBR NUMBER(5) Yes 0

MESSAGE_NBR NUMBER(5) Yes 0

CHAR_TYPE_CD CHAR(8) Yes ' '


CHAR_VAL_FK1 CHAR(50) Yes ' '







USER_ID CHAR(8) Yes ' '



Primary Key:



SEQNO



Indexes:



SEQNO

2. XF823S0 NORMAL CHAR_TYPE_CD

CHAR_VAL


CHAR_VAL_FK1

D.22 C1_DISCREPANCY_RPT_LOG_PARM

Purpose: Used to store discrepancy report's log parameters.


Column Details:



MESSAGE_PARM VARCHAR2(30) No ' '





Primary Key:



SEQNO

PARM_SEQ



Indexes:



SEQNO

PARM_SEQ

D.23 C1_DSC_RPT_TYPE

Purpose: Used to store the details of a discrepancy report type.


Column Details:


DSC_RPT_TYPE_CD CHAR(30) No -


TRANS_BUS_OBJ_CD CHAR(30) No ' '


C1_ACTIVE_INACTIVE_FLG CHAR(4) Yes ' '


Primary Key:


SINGLE DSC_RPT_TYPE_CD

Indexes:


1. XF815P0 UNIQUE DSC_RPT_TYPE_CD

D.24 C1_DSC_RPT_TYPE_CHAR

Purpose: Used to store characteristics defined for a discrepancy report type.




Column Details:














Primary Key:


COMPOSITE DSC_RPT_TYPE_CD

CHAR_TYPE_CD

SEQ_NUM

Indexes:



CHAR_TYPE_CD

SEQ_NUM

2. XF817S0 UNIQUE SRCH_CHAR_VAL



D.25 C1_DSC_RPT_TYPE_L

Purpose: Used to store the description of a discrepancy report type.


Column Details:




DESCR VARCHAR2(60) Yes ' '

DESCRLONG VARCHAR2(4000) Yes ' '


Primary Key:


COMPOSITE DSC_RPT_TYPE_CD

LANGUAGE_CD

Indexes:



LANGUAGE_CD

D.26 C1_ENRL_PROD

Purpose: Used to store the details of a product to which an account is enrolled.


Column Details:


ENROLLMENT_ID CHAR(10) No -

PRODUCT_CD CHAR(30) No -

PRODUCT_EFFDT DATE No -




START_DT DATE No -

END_DT DATE Yes -

PRIORITY NUMBER(3) No 0


Primary Key:


COMPOSITE ENROLLMENT_ID

PRODUCT_PAR_CD

PRODUCT_PAR_EFFDT

PRODUCT_CHLD_CD

PRODUCT_CHLD_EFFDT

Indexes:


1. XF792P0 UNIQUE ENROLLMENT_ID

PRODUCT_PAR_CD

PRODUCT_PAR_EFFDT

PRODUCT_CHLD_CD

PRODUCT_CHLD_EFFDT

D.27 C1_ENRL_PROD_REL

Purpose: Used to store the inclusion information for the standard products which are associated with the enrolled product.


Column Details:



PRODUCT_PAR_CD CHAR(30) No -

PRODUCT_PAR_EFFDT DATE No -

PRODUCT_CHLD_CD CHAR(30) No -




PRODUCT_CHLD_EFFDT DATE No -

START_DT DATE Yes -

END_DT DATE Yes -

INCLUSION_SW CHAR(1) No 'N'


Primary Key:



PRODUCT_PAR_CD

PRODUCT_PAR_EFFDT

PRODUCT_CHLD_CD

PRODUCT_CHLD_EFFDT

Indexes:



PRODUCT_PAR_CD

PRODUCT_PAR_EFFDT

PRODUCT_CHLD_CD

PRODUCT_CHLD_EFFDT

D.28 C1_ENRL_PROD_REL_SVC

Purpose: Used to store the inclusion information for the services associated with the standard products which are enrolled through a packaged product.


Column Details:










SERVICE_CD CHAR(30) No -

START_DT DATE Yes -

END_DT DATE Yes -


ADD_ON_SVC_SW CHAR(1) No 'N'


Primary Key:



PRODUCT_PAR_CD

PRODUCT_PAR_EFFDT

PRODUCT_CHLD_CD

PRODUCT_CHLD_EFFDT

SERVICE_CD

Indexes:


1. XT627P0 UNIQUE ENROLLMENT_ID

PRODUCT_PAR_CD

PRODUCT_PAR_EFFDT

PRODUCT_CHLD_CD

PRODUCT_CHLD_EFFDT

SERVICE_CD

D.29 C1_ENRL_PROD_SVC

Purpose: Used to store the inclusion information for add-on services which are associated with the enrolled product.




Column Details:




PRODUCT_EFFDT DATE No -


START_DT DATE Yes -

END_DT DATE Yes -

ADD_ON_SVC_SW CHAR(1) No 'N'



Primary Key:



PRODUCT_CD

PRODUCT_EFFDT

SERVICE_CD

Indexes:


1. XT627P0 UNIQUE ENROLLMENT_ID

PRODUCT_CD

PRODUCT_EFFDT

SERVICE_CD

D.30 CI_FILE_REQUEST_TRANSFORM_DTL

Purpose: Used to store the details of file request transformation.




Column Details:


REQUEST_TYPE CHAR(20) No -

FILE_SEGMENT_TYPE CHAR(4) No -


OBJ_PROPERTY_NAME VARCHAR2(60) No ' '

START_POSITION NUMBER(5) Yes -

END_POSITION NUMBER(5) Yes -

MAP_OBJ_PROPERTY_NAME VARCHAR2(255) No ' '



DEFAULT_VALUE VARCHAR2(255) No ' '

RECORD_IDENTIFIER_SW CHAR(1) No 'N'

Primary Key:


COMPOSITE REQUEST_TYPE

FILE_SEGMENT_TYPE

OBJ_PROPERTY_NAME

Indexes:


1. XC1011P0 UNIQUE REQUEST_TYPE

FILE_SEGMENT_TYPE

OBJ_PROPERTY_NAME

2. XC1011S1 NORMAL REQUEST_TYPE

D.31 C1_PAY_INS

Purpose: Used to store the details of a pay instruction.




Column Details:


PAY_INS_ID CHAR(12) No -

RECONCILIATION_ID CHAR(12) No ' '

COV_START_DT DATE No -

COV_END_DT DATE No -

PAY_INS_AMT NUMBER(15,2) No 0





STATUS_UPD_DTTM DATE No -

CRE_DTTM DATE No -

ILM_ARCH_SW CHAR(1) Yes -

ILM_DT DATE Yes -


ACCT_NBR_TYPE_CD CHAR(8) No ' '

ACCT_NBR VARCHAR2(30) No ' '

POLICY_NBR VARCHAR2(64) No ' '


PLAN_NBR VARCHAR2(30) No ' '

ID_TYPE_CD CHAR(8) No ' '

PER_ID_NBR VARCHAR2(90) No ' '


Primary Key:


SINGLE PAY_INS_ID

Indexes:


1. XF750P0 UNIQUE PAY_INS_ID

2. XF750S0 NORMAL RECONCILIATION_ID



3. XF750S1 UNIQUE BO_STATUS_CD

BUS_OBJ_CD

PAY_INS_ID

D.32 C1_PAY_INS_ADJ

Purpose: Used to store the adjustments created with respect to a pay instruction.


Column Details:



SEQNO NUMBER(5) No 1

XFER_ADJ_ID CHAR(12) No ' '

PI_XFER_TYPE_FLG CHAR(4) No ' '

XFER_FT_ID CHAR(12) No ' '

OFFSET_ADJ_ID CHAR(12) No ' '

PI_ADJ_REL_OBJ_FLG CHAR(4) No ' '

PK_VALUE1 VARCHAR2(254) No ' '


Primary Key:


COMPOSITE PAY_INS_ID

SEQNO

Indexes:



SEQNO

2. XF751S0 NORMAL PAY_INS_ID

PI_ADJ_REL_OBJ_FLG

PK_VALUE1



D.33 C1_PAY_INS_CHAR

Purpose: Used to store characteristics defined for a pay instruction.


Column Details:






CHAR_VAL_FK1 CHAR(50) No ' '








Primary Key:



CHAR_TYPE_CD

SEQ_NUM

Indexes:



CHAR_TYPE_CD

SEQ_NUM




D.34 C1_PAY_INS_K

Purpose: Used to store pay instruction ID.


Column Details:




Primary Key:



ENV_ID

Indexes:


1. XM524P0 UNIQUE PAY_INS_ID

ENV_ID

D.35 C1_PAY_INS_LOG

Purpose: Used to store logs of a pay instruction.


Column Details:





LOG_DTTM DATE Yes -






MESSAGE_CAT_NBR NUMBER(5) No 0

MESSAGE_NBR NUMBER(5) No 0













Primary Key:



SEQNO

Indexes:



SEQNO


CHAR_VAL


CHAR_VAL_FK1

D.36 C1_PAY_INS_LOG_PARM



Purpose: Used to store pay instruction's log parameters.


Column Details:








Primary Key:



SEQNO

PARM_SEQ

Indexes:



SEQNO

PARM_SEQ

D.37 C1_PAY_INS_REL_OBJ

Purpose: Used to store information about the objects related to a pay instruction.


Column Details:



RECON_REL_OBJ_TYPE_FLG CHAR(4) No -




MAINT_OBJ_CD CHAR(12) No -








Primary Key:




MAINT_OBJ_CD

SEQ_NUM

Indexes:




MAINT_OBJ_CD

SEQ_NUM

2. XF756S0 NORMAL MAINT_OBJ_CD

PK_VALUE1

PK_VALUE2

PK_VALUE3

PK_VALUE4

PK_VALUE5

3. XF756S1 NORMAL PAY_INS_ID

MAINT_OBJ_CD



D.38 C1_PRODUCT_DIV_PRICELIST

Purpose: Used to store price lists associated with the divisions to which the product is associated.


Column Details:


PRICELIST_ID CHAR(10) No -

CIS_DIVISION CHAR(5) No -


START_DT DATE No -

END_DT DATE Yes -


Primary Key:


COMPOSITE PRODUCT_CD

CIS_DIVISION

START_DT

PRICELIST_ID

Indexes:


1. XF720P0 UNIQUE PRODUCT_CD

CIS_DIVISION

START_DT

PRICELIST_ID

D.39 C1_PRODUCT_ENRL

Purpose: Used to store the details of a product enrollment.




Column Details:


ENROLLMENT_ID ENROLLMENT_ID No -

ACCT_ID ACCT_ID No -

ENROLL_CHANNEL_FLG ENROLL_CHANNEL_FLG No -

START_DT START_DT No -

END_DT END_DT Yes -

COMMENTS COMMENTS Yes ' '

BUS_OBJ_CD BUS_OBJ_CD No ' '

BO_DATA_AREA BO_DATA_AREA Yes -

BO_STATUS_CD BO_STATUS_CD No ' '

ILM_ARCH_SW ILM_ARCH_SW Yes -

ILM_DT ILM_DT Yes -

VERSION VERSION No 1

ENROLL_END_BY_SYS_SW ENROLL_END_BY_SYS_SW No 'N'

Primary Key:


SINGLE ENROLLMENT_ID

Indexes:



D.40 C1_PRODUCT_ENRL_CHAR

Purpose: Used to store characteristics defined for a product enrollment.


Column Details:




EFFDT DATE No -













Primary Key:



CHAR_TYPE_CD

EFFDT

Indexes:



CHAR_TYPE_CD

EFFDT

D.41 C1_PRODUCT_ENRL_K

Purpose: Used to store product enrollment ID.


Column Details:






Primary Key:



ENV_ID

Indexes:



ENV_ID

D.42 C1_PRODUCT_ENRL_LOG

Purpose: Used to store logs of a product enrollment.


Column Details:




LOG_ENTRY_TYPE_FLG CHAR(4) No -

LOG_DTTM DATE No -


DESCRLONG VARCHAR2(4000) No -















USER_ID CHAR(8) No -



Primary Key:



SEQNO

Indexes:



SEQNO

D.43 C1_PRODUCT_ENRL_LOG_PARM

Purpose: Used to store product enrollment's log parameters.


Column Details:





MSG_PARM_TYP_FLG CHAR(4) No -





Primary Key:



SEQNO

PARM_SEQ

Indexes:



SEQNO

PARM_SEQ

D.44 C1_PRODUCT_LOG

Purpose: Used to store logs of a product.


Column Details:






LOG_DTTM DATE No -



















Primary Key:



SEQNO

Indexes:



SEQNO

D.45 C1_PRODUCT_LOG_PARM

Purpose: Used to store product's log parameters.


Column Details:










Primary Key:



SEQNO

PARM_SEQ

Indexes:



SEQNO

PARM_SEQ

D.46 C1_PRODUCT_SERVICE

Purpose: Used to store the details of a product service.


Column Details:



START_DT DATE No -

END_DT DATE Yes -


Primary Key:


SINGLE SERVICE_CD

Indexes:


1. XF605P0 UNIQUE SERVICE_CD



D.47 C1_PRODUCT_SERVICE_CHAR

Purpose: Used to store characteristics defined for a product service.


Column Details:




EFFDT DATE No -










Primary Key:


COMPOSITE SERVICE_CD

CHAR_TYPE_CD

EFFDT

Indexes:



CHAR_TYPE_CD

EFFDT



D.48 C1_PRODUCT_SERVICE_L

Purpose: Used to store the description of a product service.


Column Details:




DESCR VARCHAR2(60) No -


Primary Key:



LANGUAGE_CD

Indexes:



LANGUAGE_CD

D.49 C1_PRODUCT_SERVICE_PRITM

Purpose: Used to store price items associated with a product service.


Column Details:



PRICEITEM_CD CHAR(30) No -

START_DT DATE No -

END_DT DATE Yes -




Primary Key:



PRICEITEM_CD

START_DT

Indexes:



PRICEITEM_CD

START_DT

D.50 C1_PRODUCT_VER

Purpose: Used to store the details of a product version.


Column Details:



EFFDT DATE No -


BO_STATUS_CD CHAR(12) Yes -

BUS_OBJ_CD CHAR(30) Yes -

TC_TYPE_CD CHAR(12) Yes -


Primary Key:



EFFDT



Indexes:



EFFDT

D.51 C1_PRODUCT_VER_CHAR

Purpose: Used to store characteristics defined for a product version.


Column Details:



EFFDT DATE No -


CHAR_EFFDT DATE No -










Primary Key:



EFFDT

CHAR_TYPE_CD

CHAR_EFFDT



Indexes:



EFFDT

CHAR_TYPE_CD

CHAR_EFFDT

D.52 C1_PRODUCT_VER_ELIG

Purpose: Used to store the details of a product version eligibility criteria.


Column Details:



EFFDT DATE No -

ELIG_RULE_FLG CHAR(4) No -

START_DT DATE No -

END_DT DATE Yes -


Primary Key:



EFFDT

ELIG_RULE_FLG

START_DT



Indexes:


1. XF696P0

UNIQUE PRODUCT_CD

EFFDT

ELIG_RULE_FLG

START_DT

D.53 C1_PRODUCT_VER_ELIG_DTL

Purpose: Used to store the rules defined in a product version eligibility criteria.


Column Details:



EFFDT DATE No -


START_DT DATE No -

SEQUENCE_NUM NUMBER(5) No -

LHS_PRICE_PARM_CD VARCHAR2(30) No -

OPERATOR CHAR(10) No -

RHS_PRICE_PARM_CD VARCHAR2(30) Yes -

RHS_PRICE_PARM_TYPE_FLG CHAR(4) No -

RHS_PRICE_PARM_VAL VARCHAR2(254) Yes -

TRUE_FLG CHAR(4) No -

FALSE_FLG CHAR(4) No -

INSF_FLG CHAR(4) No -




Primary Key:



EFFDT

ELIG_RULE_FLG

START_DT

SEQUENCE_NUM

Indexes:



EFFDT

ELIG_RULE_FLG

START_DT

SEQUENCE_NUM

D.54 C1_PRODUCT_VER_ELIG_L

Purpose: Used to store the description for the product version eligibility criteria.


Column Details:



EFFDT DATE No -


START_DT DATE No -






Primary Key:



EFFDT

ELIG_RULE_FLG

START_DT

LANGUAGE_CD

Indexes:



EFFDT

ELIG_RULE_FLG

START_DT

LANGUAGE_CD

D.55 C1_PRODUCT_VER_L

Purpose: Used to store the description for the product version.


Column Details:



EFFDT DATE No -






Primary Key:



EFFDT

LANGUAGE_CD

Indexes:



EFFDT

LANGUAGE_CD

D.56 C1_PRODUCT_VER_LOG

Purpose: Used to store logs of a product version.


Column Details:



EFFDT DATE No -




LOG_DTTM DATE No -



















Primary Key:



EFFDT

SEQNO

Indexes:



EFFDT

SEQNO

D.57 C1_PRODUCT_VER_LOG_PARM

Purpose: Used to store product version's log parameters.


Column Details:



EFFDT DATE No -









Primary Key:



EFFDT

SEQNO

PARM_SEQ

Indexes:



EFFDT

SEQNO

PARM_SEQ

D.58 C1_PRODUCT_VER_PLIST

Purpose: Used to store the price list associated with a product version.


Column Details:



EFFDT DATE No -

PRICELIST_ID CHAR(10) No -




Primary Key:



EFFDT

PRICELIST_ID

Indexes:



EFFDT

PRICELIST_ID

D.59 C1_PRODUCT_VER_PROD

Purpose: Used to store standard products added in a product version.


Column Details:







Primary Key:


COMPOSITE PRODUCT_PAR_CD

PRODUCT_PAR_EFFDT

PRODUCT_CHLD_CD

PRODUCT_CHLD_EFFDT

Indexes:




1. XF796P0 UNIQUE PRODUCT_PAR_CD

PRODUCT_PAR_EFFDT

PRODUCT_CHLD_CD

PRODUCT_CHLD_EFFDT

D.60 C1_PRODUCT_VER_PROD_SVC

Purpose: Used to store the inclusion information for services associated with the standard products which are added in the product version.


Column Details:









Primary Key:


COMPOSITE PRODUCT_PAR_CD

PRODUCT_PAR_EFFDT

PRODUCT_CHLD_CD

PRODUCT_CHLD_EFFDT

SERVICE_CD



Indexes:


1.

XF795P0 UNIQUE PRODUCT_PAR_CD

PRODUCT_PAR_EFFDT

PRODUCT_CHLD_CD

PRODUCT_CHLD_EFFDT

SERVICE_CD

D.61 C1_PRODUCT_VER_SVC

Purpose: Used to store the details of add-on services included in the product version.


Column Details:



EFFDT DATE No -


MANDATORY_SW CHAR(1) No 'N'


Primary Key:



EFFDT

SERVICE_CD

Indexes:



EFFDT

SERVICE_CD



D.62 C1_RECONCILIATION

Purpose: Used to store the details of a reconciliation.


Column Details:


RECONCILIATION_ID CHAR(12) No -

RECON_TYPE_CD CHAR(30) No ' '

EXTERNAL_REF_ID CHAR(50) No ' '


PAY_ID CHAR(12) No ' '



BO_STATUS_REASON_CD VARCHAR2(30) No ' '


STATUS_UPD_DTTM DATE No -

CRE_DTTM DATE No -

ILM_ARCH_SW CHAR(1) No ' '

ILM_DT DATE Yes -


Primary Key:


SINGLE RECONCILIATION_ID

Indexes:


1. XF806P0 UNIQUE RECONCILIATION_ID

2. XF806S0 NORMAL ACCT_ID

3. XF806S1 NORMAL PAY_ID

4. XF806S2 UNIQUE BUS_OBJ_CD

RECONCILIATION_ID



BO_STATUS_CD

5. XF806S3

NORMAL EXTERNAL_REF_ID

D.63 C1_RECONCILIATION_LOG

Purpose: Used to store logs of a reconciliation.


Column Details:





LOG_DTTM DATE No -



MESSAGE_CAT_NBR NUMBER(5) No 0

MESSAGE_NBR NUMBER(5) No 0











BO_STATUS_REASON_CD VARCHAR2(30) No ' '




Primary Key:


COMPOSITE RECONCILIATION_ID

SEQNO

Indexes:



SEQNO


CHAR_VAL_FK1


CHAR_VAL

D.64 C1_RECONCILIATION_LOG_PARM

Purpose: Used to store reconciliation's log parameters.


Column Details:








Primary Key:



SEQNO

PARM_SEQ



Indexes:



SEQNO

PARM_SEQ

D.65 C1_RECONCILIATION_CHAR

Purpose: Used to store characteristics defined for a reconciliation.


Column Details:




EFFDT DATE No -










Primary Key:



CHAR_TYPE_CD

EFFDT



Indexes:



CHAR_TYPE_CD

EFFDT


D.66 C1_RECONCILIATION_K

Purpose: Used to store reconciliation ID.


Column Details:




Primary Key:



ENV_ID

Indexes:



ENV_ID

D.67 C1_RECON_TYPE

Purpose: Used to store the details of a reconciliation type.




Column Details:


RECON_TYPE_CD CHAR(30) No -


TRANS_BUS_OBJ_CD CHAR(30) No ' '


C1_ACTIVE_INACTIVE_FLG CHAR(4) No ' '


Primary Key:


SINGLE RECON_TYPE_CD

Indexes:


1. XF740P0 UNIQUE RECON_TYPE_CD

2. XF740S1 NORMAL BUS_OBJ_CD

D.68 C1_RECON_TYPE_ALG

Purpose: Used to store the algorithms associated with a reconciliation type.


Column Details:



RECON_TY_ALG_ENTITY_FLG CHAR(4) No -


ALG_CD CHAR(12) No ' '




Primary Key:


COMPOSITE RECON_TYPE_CD

RECON_TY_ALG_ENTITY_FLG

SEQ_NUM

ALG_CD

Indexes:



RECON_TY_ALG_ENTITY_FLG

SEQ_NUM

ALG_CD

D.69 C1_RECON_TYPE_CHAR

Purpose: Used to store characteristics defined for a reconciliation type.


Column Details:
















Primary Key:



CHAR_TYPE_CD

SEQ_NUM

Indexes:



CHAR_TYPE_CD

SEQ_NUM


D.70 C1_RECON_TYPE_L

Purpose: Used to store the description of a reconciliation type.


Column Details:







Primary Key:



LANGUAGE_CD



Indexes:



LANGUAGE_CD

D.71 CI_REV_REC_SCH_REL

Purpose: Used to store the details of the related deferred revenue recognitions.


Column Details:



REL_REV_REC_ID CHAR(12) No -

CRE_DTTM DATE Yes current_date

FT_ID CHAR(12) No ' '



ALLOW_EDIT_SW CHAR(1) Yes 'N'

Primary Key:



SEQNO

Indexes:


1. XF811P0 Unique REV_REC_ID

SEQNO



Appendix E : Existing Tables Added in 2.6.0.1.0 This section lists the existing tables which are modified in Oracle Revenue Management and Billing Version 2.6.0.1.0. It also indicates the columns that are newly added, dropped, or modified in these tables.

E.1 CI_APAY_STAGE_UP

The following table lists the columns that are either newly added or modified in the CI_APAY_STAGE_UP table:

Sr. No. Column Name Modification Type Data Type in V2.6.0.0.0

Data Type in V2.6.0.1.0

Data Migration Required (Yes or No)

Column Value After Data Migration

1. ACH_ACK_TYPE_FLG Newly Added - CHAR(4) No -

E.2 CI_APPTXN_CH_ELIGIBLE

The following table lists the columns that are either newly added or modified in the CI_APPTXN_CH_ELIGIBLE table:





1. APP_REASON_REQ_FLG Newly Added - CHAR(1) No -

E.3 CI_APPTXN_LOG

The following table lists the columns that are either newly added or modified in the CI_APPTXN_LOG table:





1. APP_CHAIN_CD Newly Added - CHAR(10) No -

2. FIELD_RULE_ID Newly Added - CHAR(15) No -



E.4 C1_FT_EXT

The following table lists the columns that are either newly added, modified, or deleted in the C1_FT_EXT table:

Sr. No. Column Name Modification Type





1. ACCT_APAY_ID Newly Added - CHAR(10) No -

2. C1_BILLED_MEM_CNT Dropped NUMBER(9) - - -

3. C1_BILLED_SUB_CNT Dropped NUMBER(9) - - -

4. C1_CHG_LN_CD Dropped CHAR(10) - - -

5. C1_ELIGIBILITY_STAT_TYPE_CD Dropped CHAR(1) - - -

6. C1_FROZEN_MKT_SEG Dropped CHAR(1) - - -

E.5 CI_ACCT_APAY

The following table lists the columns that are either newly added or modified in the CI_ACCT_APAY table:





1. APAY_TYPE_FLG Newly Added - CHAR(4) No -

2. RULE_TYPE_CD Newly Added - CHAR(12) No -

3. ENTITY_NAME Format Change VARCHAR2 (64) VARCHAR2 (254) - -



E.6 CI_ACCT

The following table lists the columns that are either newly added or modified in the CI_ACCT table:





1. CLOSING_DT Newly Added - DATE No -

2. DD_CR_SW Newly Added - CHAR(1) No -

3. RULE_APAY_SW Newly Added - CHAR(1) No -

E.7 C1_PRODUCT

The following table lists the columns that are either newly added or modified in the C1_PRODUCT table:






1. COMPLIANCE_NBR Newly Added - VARCHAR2(30) No -

2. PROD_MNGR_TD_ROLE Newly Added - CHAR(10) No -

3. PRODUCT_TYP_FLG Newly Added - CHAR(4) No -

4. PRODUCT_CAT_FLG Newly Added - CHAR(4) No -

E.8 C1_PRODUCT_DIV

The following table lists the columns that are either newly added or modified in the C1_PRODUCT_DIV table:





1. DEFAULT_PL Dropped CHAR(10) - - -



E.9 CI_REV_REC_SCH

The following table lists the columns that are either newly added or modified in the CI_REV_REC_SCH table:





1. DRR_TEMPLATE_CD Newly Added - CHAR(30) Yes The column value is set to the deferred revenue recognition template defined for the distribution code and contract type combination available on the financial transaction.

2. VALID_UNTIL_DT Newly Added - DATE Yes If the type of the corresponding financial transaction is Bill Segment, the column value is set to the bill segment end date. However, if the type of the corresponding financial transaction is Adjustment and the Use Contract Expiration Date (Y or N) parameter in the C1-REVRECSCH algorithm is set to Y, the column value is set to the contract expiration date. However, if the type of the corresponding financial transaction is Adjustment and the Use Contract Expiration Date (Y or N) parameter in the C1-REVRECSCH algorithm is set to N, the column value is set to the financial transaction arrears date.



E.10 CI_CONSTRUCT_LINKED_ACCT

The following table lists the columns that are either newly added or modified in the CI_CONSTRUCT_LINKED_ACCT table:





1. ACCT_EFF_END_DATE Newly Added - DATE No -

2. PRIORITY_NUM Newly Added - NUMBER(5) No -

3. TEMPLATE_CD Newly Added - CHAR(14) No -

E.11 CI_CONSTRUCT_TEMPLATE

The following table lists the columns that are either newly added or modified in the CI_CONSTRUCT_TEMPLATE table:





1. EFF_START_DATE Newly Added - DATE No -

2. EFF_END_DATE Newly Added - DATE No -

E.12 CI_CONSTRUCT_TEMPLATE_CRIT

The following table lists the columns that are either newly added or modified in the CI_CONSTRUCT_TEMPLATE_CRIT table:






2. EFF_END_DATE Newly Added - DATE No -



E.13 CI_CONSTRUCT_TEMPLATE_CRIT_L

The following table lists the columns that are either newly added or modified in the CI_CONSTRUCT_TEMPLATE_CRIT_L table:







E.14 CI_CONSTRUCT_TEMPLATE_L

The following table lists the columns that are either newly added or modified in the CI_CONSTRUCT_TEMPLATE_L table:






E.15 CI_APPTXN

The following table lists the columns that are either newly added or modified in the CI_APPTXN table:





1. FIELD_RULE_FLG Newly Added - CHAR(1) No -

2. FIELDRULE_ID_LIST Newly Added - VARCHAR2(4000) No -



E.16 CI_APPTXN_BOCHAIN

The following table lists the columns that are either newly added or modified in the CI_APPTXN_BOCHAIN table:





1. FIELD_RULE_FLG Newly Added - CHAR(1) No -

E.17 CI_FILE_REQUEST_TYPE

The following table lists the columns that are either newly added or modified in the CI_FILE_REQUEST_TYPE table:






1. FILE_ATOMICITY_SW Newly Added - CHAR(1) No -

2. UPLOAD_AND_PROCESS_SW Newly Added - CHAR(1) No -

3. SERVICE_LOG_SW Newly Added - CHAR(1) No -

4. SKIP_DUPLICATE_SW Newly Added - CHAR(1) No -

5. VALIDATE_REQUEST_PAYLOAD_SW Newly Added - CHAR(1) No -



E.18 CI_FILE_REQUEST_DETAIL

The following table lists the columns that are either newly added or modified in the CI_FILE_REQUEST_DETAIL table:

Sr. No. Column Name Modification Type Data Type in V2.6.0.0.0 Data Type in V2.6.0.1.0 Data Migration Required (Yes or No)


1. OPERATION Newly Added - CHAR(30) No -

2. REQUEST_PAYLOAD Newly Added - VARCHAR2(32000) No -

3. REQUEST_HASH Newly Added - CHAR(50) No -

4. RESPONSE_OBJECT Dropped CLOB(1073741824) - - -

E.19 CI_MEMBERSHIP

The following table lists the columns that are either newly added or modified in the CI_MEMBERSHIP table:





1. PAID_THR_DT Newly Added - DATE No -

E.20 CI_PRICEASGN

The following table lists the columns that are either newly added or modified in the CI_PRICEASGN table:





1. ELIGIBILITY_SW Newly Added - CHAR(1) No -



E.21 CI_PRICE_PARM

The following table lists the columns that are either newly added or modified in the CI_PRICE_PARM table:






1. PARM_AVL_PRD_SW Newly Added - CHAR(1) No -

E.22 CI_FILE_REQUEST

The following table lists the columns that are either newly added or modified in the CI_FILE_REQUEST table:






1. REQUEST_TYPE Newly Added - CHAR(20) No -

E.23 CI_RULE_TYPE_FLD

The following table lists the columns that are either newly added or modified in the CI_RULE_TYPE_FLD table:






1. RULE_FLD_SRCH_ZONE Newly Added - CHAR(12) No -

E.24 CI_RULE_TYPE

The following table lists the columns that are either newly added or modified in the CI_RULE_TYPE table:






1. C1_RULE_USAGE_FLG Newly Added - CHAR(4) No -



E.25 CI_BCHG_HSTG

The following table lists the columns that are either newly added or modified in the CI_BCHG_HSTG table:





1. FILE_NAME Dropped CHAR(60) - - -

2. UPLD_FLTY_CD Dropped CHAR(60) - - -

E.26 C$_0FILTER2

The following table lists the columns that are either newly added or modified in the C$_0FILTER2 table:






E.27 C1_PAY_TNDR_REQ

The following table lists the columns that are either newly added or modified in the C1_PAY_TNDR_REQ table:






2. NAME1 Format Change VARCHAR2 (64) VARCHAR2 (254) - -



E.28 CI_ADJ_APREQ

The following table lists the columns that are either newly added or modified in the CI_ADJ_APREQ table:






E.29 CI_APAY_CLR_STG

The following table lists the columns that are either newly added or modified in the CI_APAY_CLR_STG table:







E.30 CI_APAY_STAGE_UP_REM

The following table lists the columns that are either newly added or modified in the CI_APAY_STAGE_UP_REM table:






1. APAY_UPL_SUB_RSN_CD Format Change CHAR (4) VARCHAR2 (30) - -



E.31 CI_BILL_ROUTING

The following table lists the columns that are either newly added or modified in the CI_BILL_ROUTING table:






1. ENTITY_NAME1 Format Change VARCHAR2 (64) VARCHAR2 (254) - -



E.32 CI_CUSTOMER_HIERARCHY_VW

The following table lists the columns that are either newly added or modified in the CI_CUSTOMER_HIERARCHY_VW table:






1. CHILD_NAME Format Change VARCHAR2 (64) VARCHAR2 (254) - -

E.33 CI_EFF_ACCT_PRICING_VW

The following table lists the columns that are either newly added or modified in the CI_EFF_ACCT_PRICING_VW table:






1. CUSTOMER_NAME Format Change VARCHAR2 (64) VARCHAR2 (254) - -

2. PARENT_CUSTOMER Format Change VARCHAR2 (64) VARCHAR2 (254) - -



E.34 CI_EFF_PER_PRICING_VW

The following table lists the columns that are either newly added or modified in the CI_EFF_PER_PRICING_VW table:






1. CUSTOMER_NAME Format Change VARCHAR2 (64) VARCHAR2 (254) - -

2. PARENT_CUSTOMER Format Change VARCHAR2 (64) VARCHAR2 (254) - -

E.35 CI_ENRL_PER_NM

The following table lists the columns that are either newly added or modified in the CI_ENRL_PER_NM table:







2. ENTITY_NAME_UPR Format Change VARCHAR2 (64) VARCHAR2 (254) - -

E.36 CI_EXT_STMT_ITEM

The following table lists the columns that are either newly added or modified in the CI_EXT_STMT_ITEM table:









E.37 CI_MEMBERS_VW

The following table lists the columns that are either newly added or modified in the CI_MEMBERS_VW table:








E.38 CI_MEMBER_ACCOUNT_VW

The following table lists the columns that are either newly added or modified in the CI_MEMBER_ACCOUNT_VW table:






1. CHILD_NAME Format Change VARCHAR2 (64) VARCHAR2 (254) - -

E.39 CI_PAY_TNDR

The following table lists the columns that are either newly added or modified in the CI_PAY_TNDR table:









E.40 CI_PAY_TNDR_ST

The following table lists the columns that are either newly added or modified in the CI_PAY_TNDR_ST table:







E.41 CI_PER

The following table lists the columns that are either newly added or modified in the CI_PER table:






1. OVRD_MAIL_NAME1 Format Change VARCHAR2 (64) VARCHAR2 (254) - -



E.42 CI_PER_NAME

The following table lists the columns that are either newly added or modified in the CI_PER_NAME table:










E.43 CI_PER_PRIM_VW

The following table lists the columns that are either newly added or modified in the CI_PER_PRIM_VW table:







E.44 CI_PEVT_DTL_ST

The following table lists the columns that are either newly added or modified in the CI_PEVT_DTL_ST table:






1. ENTITY_NAME Format Change VARCHAR2 (64) CHAR2 (254) - -


E.45 CI_QUOTE_RTG

The following table lists the columns that are either newly added or modified in the CI_QUOTE_RTG table:











E.46 CI_STM_PER_VW

The following table lists the columns that are either newly added or modified in the CI_STM_PER_VW table:







2. LEGAL_NAME Format Change VARCHAR2 (64) VARCHAR2 (254) - -

E.47 CI_TRL_BILL_ROUTING

The following table lists the columns that are either newly added or modified in the CI_TRL_BILL_ROUTING table:











Appendix F : Algorithms and Algorithm Types Dropped in 2.6.0.1.0 This section lists the algorithms and algorithm types which are dropped in Oracle Revenue Management and Billing Version 2.6.0.1.0.

F.1 Algorithm Type

No algorithm types are dropped in Oracle Revenue Management and Billing Version 2.6.0.1.0.

F.2 Algorithm

The following table lists the algorithms that are dropped in Oracle Revenue Management and Billing Version 2.6.0.1.0:

Algorithm Description

C1-BILLTOL Test Bill Tolerance COFT



Appendix G : Parameters Added or Removed from Algorithm Types in 2.6.0.1.0 The following table lists the parameters which are added or removed from algorithm types in Oracle Revenue Management and Billing Version 2.6.0.1.0:

Algorithm Type Parameters (Removed from 2.6.0.0.0)

Parameters (Added in 2.6.0.1.0)

APAY-CREATE - Open-Item Account Match Type Code To Be Used For Rule Based Auto Payments

C1_ACCR_CAL - Do you want to consider bill cycle period as Multiplication Factor (Y/N)



Appendix H : Option Types Added or Removed from Feature Configurations in 2.6.0.1.0 The following table lists the options types which are added or removed from feature configurations in Oracle Revenue Management and Billing Version 2.6.0.1.0:

Feature Configuration Option Types (Removed from V2.6.0.0.0)

Option Types (Added in V2.6.0.1.0)

C1_AXENTITY - Display Existing Panel on Left Side (Y/N)

C1_FM - Consolidated Batch Sequence

- Remove Duplicates - Accumulated Rule Output

- Rule Output Accumulation



Appendix I : Characteristic Types Dropped in 2.6.0.1.0 No characteristic types are dropped in Oracle Revenue Management and Billing Version 2.6.0.1.0.



Appendix J : Upgrade Batch for Deferred Revenue Recognition (C1-RRUPG) The Upgrade Batch for Deferred Revenue Recognition (C1-RRUPG) batch does the following:

Updates the column values of the records in the respective table:

Table Name Column Name Column Value After Data Migration

CI_REV_REC_SCH DRR_TEMPLATE_CD The column value is set to the deferred revenue recognition template defined for the distribution code and contract type combination available on the financial transaction.

BO_STATUS_CD If all lines in the schedule are recognized, the column value is set to Closed. If few or all lines in the schedule are not recognized, the column value is set to Active.

VALID_UNTIL_DT If the type of the corresponding financial transaction is Bill Segment, the column value is set to the bill segment end date. However, if the type of the corresponding financial transaction is Adjustment and the Use Contract Expiration Date (Y or N) parameter in the C1-REVRECSCH algorithm is set to Y, the column value is set to the contract expiration date. However, if the type of the corresponding financial transaction is Adjustment and the Use Contract Expiration Date (Y or N) parameter in the C1-REVRECSCH algorithm is set to N, the column value is set to the financial transaction arrears date.



Appendix K : Changing the DB User Password If you have changed the database user password, you need to execute the following steps before installing the rollup pack for Oracle Utilities Application Framework Version 4.3.0.4.0:

1. Download and apply the single fix available for Bug 22505470 - PATCHES APPEND EXTRA SPACE TO STRINGS AND ADD DB SERVICE CONNECTION SUPPORT on the application and database environments.

2. Perform the following steps on the application environment:

a. Change the DB Name using the configureEnv command.

b. Execute the initialSetup utility using the following command:

AIX, Linux:


Windows:


c. Execute the invokeDBUpdatePatch utility to change the database user name and password using the following command:

AIX, Linux:

$SPLEBASE/bin/invokeDBUpdatePatch.sh -b

Windows:

%SPLEBASE%\bin\invokeDBUpdatePatch.cmd –b