oracle® revenue management and billing

Oracle® Revenue Management and Billing

Version 2.5.0.1.0

ODI Integration Guide for TFM

Revision 4.0

E68660-01

August, 2018

http://pdb.us.oracle.com/search.jsp?q=E68660

Oracle Revenue Management and Billing ODI Integration Guide for TFM

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


E68660-01

Copyright Notice

Copyright © 2018, 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 © 2018, 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 © 2018, Oracle and/or its affiliates. All rights reserved.

Preface

About This Document This document will help you to understand how to import the ODI artifacts for TFM. It also explains how to upload the transaction data from the flat file to various tables in the target database.

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 Overview Lists the prerequisites for importing ODI artifacts for TFM and specifies the CSV file format required to upload the transaction data. It also explains how to download and decompress the TFM ODI package.

Section 2 Viewing TFM ODI Artifacts Explains how to view the ODI artifacts for TFM. It also lists and explains a set of activities that you need to perform in ODI after the ODI artifacts are imported.

Section 3 Preparing the Target Database

Explains how to setup the target database before the transaction data is uploaded through ODI package.

Section 4 Uploading Transaction Data Explains how to upload the transaction data from the flat file to the target database using the packages in ODI.

Section 5 Troubleshooting Lists the possible errors that you may come across while uploading a transaction data file and how you can resolve such errors.

Section 6 Scheduling Lists the steps for scheduling the Table Insertion package execution.


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

Related Documents For more information, you can refer to the following:

Document Description

Oracle Revenue Management and Billing Banking User Guide

Lists and describes various banking features in Oracle Revenue Management and Billing. It also describes all screens related to these features and explains how to perform various tasks in the application.

Oracle Revenue Management and Billing Installation Guide

Lists the pre-requisites, supported platforms, and hardware and software requirements for installing the Oracle Revenue Management and Billing application. It also explains how to install the Oracle Revenue Management and Billing application.

Installing and Configuring Oracle Data Integrator Guide

Explains how to install and configure Oracle Data Integrator.


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

Contents

1. Overview ................................................................................................................................................ 7

1.1 Prerequisites ................................................................................................................................ 7

1.1.1 Downloading TFM ODI Package...................................................................................... 8

1.1.2 Installing the Integration .............................................................................................. 12

1.1.3 CSV File Format ............................................................................................................. 16

2. Viewing TFM ODI Artifacts ................................................................................................................... 21

2.1 Creating Login for Master Repository ........................................................................................ 21

2.2 Creating Login for Work Repository ........................................................................................... 25

2.3 Connecting to the Work Repository .......................................................................................... 26

2.4 Viewing Procedures, Mappings and Packages in the Work Repository .................................... 28

2.4.1 Viewing Procedures ...................................................................................................... 28

2.4.2 Viewing Mappings ........................................................................................................ 29

2.4.3 Viewing Packages.......................................................................................................... 30

2.5 Viewing Model of the Work Repository..................................................................................... 32

2.6 Editing the Physical Architecture of the Source File (VMA_FLATFILES) ..................................... 35

2.7 Editing the Physical Architecture of the Target Database (VMA_APP_DB) ............................... 36

2.8 Viewing the Logical Architecture of the Source File (VMA_FLATFILES) ..................................... 38

2.9 Viewing the Logical Architecture of the Target Database (VMA_APP_DB) ............................... 39

3. Preparing the Target Database ............................................................................................................ 41

3.1 Starting Agent ............................................................................................................................ 41

4. Uploading Transaction Data ................................................................................................................ 42

4.1 Executing the Table Insertion Package ...................................................................................... 42

5. Troubleshooting ................................................................................................................................... 46

5.1 Unique Constraint Violated ........................................................................................................ 46

5.2 Load Data is in Error ................................................................................................................... 46

5.3 No Files Found ............................................................................................................................ 47

5.4 File Name Exists ......................................................................................................................... 48

5.5 Missing Data ............................................................................................................................... 48

6. Scheduling ............................................................................................................................................ 50


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

1. Overview Oracle Revenue Management and Billing provides you with a facility to upload banking transactions received from various product processors or banking applications for billing. You can use Oracle Data Integrator (ODI) to upload transaction data files in .CSV format. The out of box sample interface with ODI maps the flat files in .CSV format to various tables such as, CI_TXN_DETAIL_STG, CI_TXN_HEADER, CI_TXN_REC_TYPE and CI_TXN_SOURCE in the database.

Note: You need to ensure that the CSV file is in the required format. For more information about the CSV file format, refer to Oracle Revenue Management and Billing Banking User Guide.

This section lists the prerequisites for importing ODI artifacts for TFM. It also explains how to download and decompress the TFM ODI package. It also includes the CSV file format supported while uploading the transaction data.

1.1 Prerequisites Before you import the ODI artifacts for TFM, you need to do the following:

1. Install Oracle Revenue Management and Billing (ORMB) Version 2.5.0.1.0.

Note: For more information on how to install ORMB, refer to the Oracle Revenue Management and Billing Installation Guide.

2. Install Oracle Data Integrator (ODI) 12.1.3.0.0.

Note:

While installing Oracle Data Integrator, you can select any combination of these options:

Standalone Installation and Developer Installation

Java EE Installation and Developer Installation

Oracle Data Integrator should have the following components – Agent, Designer, Operator, Security Manager, Topology Manager, and Software Development Kit (SDK).

For more information on how to install ODI, refer to the Installing Oracle Data Integrator section in the Installing and Configuring Oracle Data Integrator Guide.

3. Install Oracle Database Enterprise Edition Release 12.1.0.2.0.

4. Create the database for ODI.

5. Execute the Repository Creation Utility (RCU) to create master and work repository schema on the ODI Database.

Note: For more information on how to create repository schema, refer to the Creating the Master and Work Repository Schema section in the Installing and Configuring Oracle Data Integrator Guide.


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

6. Create and configure the WebLogic domain for running the Standalone or Java EE Agent in ODI.

Note:

For more information on how to configure domain for standalone agent, refer to the Configuring the Domain for the Standalone Agent section in the Installing and Configuring Oracle Data Integrator Guide. And, for more information on how to configure domain for Java EE agent, refer to the Configuring the Domain for the Java EE Agent section in the Installing and Configuring Oracle Data Integrator Guide.

1.1.1 Downloading TFM ODI Package

To download and decompress the TFM ODI package:

1. Download the UPLOAD TFM-ODI PACKAGES FOR 2.5.0.1.0 patch (Patch Number: 28485768) from My Oracle Support. A zip file is downloaded.

2. Extract the zip file into a folder ODI_RMB_PROJECT. The folder structure after file extraction is as below:

3. Review the database scripts related to the static data required for integration.

4. Set the following variables for Unix and Windows OS:

Note: If you are executing the following script using Oracle Client, ensure that the Client Installation type is Administrator.

Variable Example

Linux and Windows OS

INT_INSTALL_HOME Set this to the directory where ODI_RMB_PROJECT.zip is extracted.

Examples:

Unix/Linux:

export

INT_INSTALL_HOME=/scratch/ODI_RMB_PROJECT/

Windows:

set INT_INSTALL_HOME=D:\ODI_RMB_PROJECT\

ODI_INST_HOME Examples:

Unix/Linux:

export ODI_INST_HOME=/scratch/ODI_EE

Windows:

set ODI_INST_HOME=D:\ODI12\

https://support.oracle.com/



Variable Example

JAVA_HOME Examples:

Unix/Linux:

export JAVA_HOME=/scratch/java/jdk1.7.0_79

Windows:

set ODI_INST_HOME=C:\Java\jdk1.7.0_79

ORACLE_HOME Examples:

Windows:

set

ORACLE_HOME=D:\app\client\product\12.1.0\clie

nt_1

Unix/Linux:

export

ORACLE_HOME=/scratch/app/oracle/product/12.1.

0.2

PATH Examples:

Unix/Linux:

export

PATH=$PATH:$ORACLE_HOME/perl/bin:$ORACLE_HOME/bin

Windows:

set PATH=<ORACLE_HOME>/perl/bin;<ORACLE_HOME>/bin

; %PATH%

LD_LIBRARY_PATH Examples:

Unix/Linux:

export LD_LIBRARY_PATH=$ORACLE_HOME/lib

Note: The syntax for INT_INSTALL_HOME are specific to the OS (Linux/Windows). The following sections refer to this as $INT_INSTALL_HOME in the Linux syntax. However, if you are installing on Windows, it should be referred to as: %INT_INSTALL_HOME%.

Make sure that JAVA_HOME and ORACLE_HOME are set to the paths as they were set during ODI installation.

5. Modify the $INT_INSTALL_HOME\config.properties file and ensure correct values are provided for server parameters where the integration product is to be installed. The following table lists the properties available in config.properties file along with their description.



Property Description Example

ODI Repository Supervisor Information

odiSupervisorUser Supervisor user as provided while running the RCU

SUPERVISOR

odiSupervisorPassword Supervisor Password as provided while running the RCU

SUPERVISOR

ODI Master Repository Database Information

masterRepositoryJdbcUrl Master Repository Database url

jdbc:oracle:thin:@<host>:<port>:<SID>

masterRepositoryJdbcDriver Oracle Driver oracle.jdbc.OracleDriver

masterRepositoryJdbcUser Master Repository database schema user

DEV_ODI_REPO

masterRepositoryJdbcPassword Master Repository database schema password

Welcome

ODI Work Repository Database Information

workRepositoryJdbcUrl Work Repository Database url

jdbc:oracle:thin:@<host>:<port>:<SID>

workRepositoryJdbcDriver Oracle Driver oracle.jdbc.OracleDriver

workRepositoryJdbcUsername Work Repository database schema user

DEV_ODI_REPO

workRepositoryJdbcPassword Work Repository database schema password

Welcome

workRepositoryName Work Repository Name as provided while running the RCU

ODIWORK

RMB Configurations

rmbUser RMB Database User <rmb_db_username>

rmbPass RMB Database Password <rmb_db_pwd>

rmbJdbcUrl RMB database URL jdbc:oracle:thin:@<host>:<port>:<SID>

rmbJdbcDriver Oracle Driver oracle.jdbc.OracleDriver

filePath The path where the csv files to be uploaded will be placed.

C:/VMA_ODI

emailId The administrator’s email [email protected]



Property Description Example

where execution emails are sent when a process fails.

hostName This specifies the mail host to be used for sending the email

For example: internal-mail-routerXXXX.example.com

olderVersion This is to be specified if upgrading from a previous version of ODI artifacts

For example: 2.4.0.1.0

setSenderEmail This specifies the sender email whose email id would be used to send mails.

For example: [email protected]

ODI Repository Details

repoType This is the work repository type to be created. In case of Development repository, enter “DEVELOPMENT” and for type execution, enter “EXECUTION” for production deployment

The valid values are

DEVELOPMENT

EXECUTION

workRepoPath Configure the work repository path based on the installation directory.

In Windows

E:\\ODI_RMB_PROJECT\\repo\WorkRepository.zip

In Unix

/scratch/ODI_RMB_PROJECT/repo/WorkRepository.zip

masterRepoPath Configure the master repository path based on the installation directory.

In Windows

E:\\ODI_RMB_PROJECT\\repo\\MasterRepository.zip

In Unix

/scratch/ODI_RMB_PROJECT/repo/MasterRepository.zip

scenariosPath Configure the scenarios path based on the installation directory

In Windows

E:\\ODI_RMB_PROJECT\\repo\\

In Unix

/scratch/ODI_RMB_PROJECT/repo/



After modification, the config.properties file would look like:

1.1.2 Installing the Integration

1.1.2.1 Upgrade from Previous Versions

Note: This is only valid if you are upgrading ORMB ODI artifacts from 2.4.0.0.0 to 2.4.0.1.0 or above versions.

After you set the environment variables, install the integration package as per the following steps:

1. Launch the command prompt and execute the command:

cd ODI_RMB_PROJECT\



2. Execute: perl Installation.pl to invoke the deployment script for integration.

<ODI_RMB_PROJECT> perl Installation.pl

The deployment script displays menu options as shown below:

Figure 1: Perl Installation Menu

3. Execute ‘Step 5 – Upgrade ODI repositories’ to upgrade ORMB ODI artifacts from previous versions to current version. This step first creates a backup of the E$_CI_TXN_DETAIL_STG and E$_CI_TXN_HEADER tables and renames them with the previous version of the ORMB appended in the table name.

ODI artifacts will create the new E$_CI_TXN_DETAIL_STG and E$_CI_TXN_HEADER tables in the target database with the latest changes.

4. Ensure that all configuration settings are done in the config.properties prior to running the above step. Launch the ODI Studio. The Oracle Data Integrator screen appears.

5. Click ODI and then select Connect. The Oracle Data Integrator Login dialog box appears.

Figure 2: Oracle Data Integrator Login Dialog Box

6. Select the login name from the drop-down list (for example, Transaction_Feed_Management) that you want to use to connect to the work repository.

7. Click the Edit ( ) icon. The Repository Connection Information dialog box appears.



Figure 3: Repository Connection Information Dialog Box

8. Select the Work Repository option. The corresponding field is enabled.

9. Click the Search ( ) icon corresponding to the Work Repository field. The Select Repository dialog box appears.

Figure 4: Select Repository Dialog Box



10. Select the work repository name from the list and then click OK. The connection to the work repository is established and Select Repository Dialog Box closes.

11. Click OK. The Repository Connection is established.

Note: By default, the Designer tab appears when you login to the work repository.

1.1.2.2 First Time Installation of ODI Artifacts

After you set the environment variables, install the integration package as per the following steps:

1. Launch the command prompt and execute the command:

cd ODI_RMB_PROJECT\

Execute: perl Installation.pl to invoke the deployment script for integration.

The deployment script displays menu options as shown below:

Figure 5: Perl Installation Menu

2. Execute Steps 2 and 3 individually or Execute Step 4 which runs both steps (2 and 3) in the sequence defined.

Note: Ensure that all configuration settings are done in the config.properties prior to running all the steps.

3. To complete the end to end ORMB-ODI integration installation, follow the below steps:

a) Deploy the integration artifacts in the ODI repositories. It also updates the location of the files and the database username and password on the ODI end.



b) Create database tables/data required for RMB-ODI integration on RMB schema.

Table Name Description

ODI_FILE_NAMES Creates a table named ODI_FILE_NAMES in the target database to store the names of the files you want to process in the run.

RMB_ODI_INSTALL_OPTIONS Creates a table named RMB_ODI_INSTALL_OPTIONS in the target database to store the email Id and Mail Host details.

c) Execute steps 2 and 3 mentioned in the installation menu in the sequence defined.

d) To upgrade ODI Repositories, refer to the Upgrade from Previous Version section.

e) Update Administrator’s Email ID and mail host - This step updates the email Id and Mail Host where the execution mails would be sent.

1.1.3 CSV File Format

You need to ensure that the CSV file contains the following when you upload the transaction data using the sample interface:

File Header — Ideally, a file must have one header record. However, it is not mandatory. The header record should contain the following details:

Column Name

Contains Mandatory (Yes or No) Mapped to Column Data Type

A “HDR” Not applicable Not applicable Not applicable

B Transaction Source Yes TXN_SOURCE_CD VARCHAR2(30)

D Header Date (YYYYMMDD) Yes TXN_HEADER_DTTM DATE

E Transaction Header ID Yes TXN_HEADER_EXT_ID CHAR(60)

F File Name Yes FILENAME CHAR(60)

G Number of Transactions Yes HEADER_NBR_RECS NUMBER(18)

H Total Transaction Volume Yes HEADER_TXN_VOL NUMBER(36,18)

I Total Transaction Amount Yes HEADER_TXN_AMT NUMBER(36,18)

Note: If the header record does not exist in a CSV file, the default header record is created when you upload the CSV file via ODI. By default, the header date is set to the current date and file name is set to the name of the file that you are uploading via ODI.



Transaction Record — The file must have one or more transaction records. It should contain the following details:

Column Name

Contains Mandatory (Yes or No)

Mapped to Column Data Type

A Transaction Record Type Yes TXN_REC_TYPE_CD VARCHAR2(30)

B Transaction Source Yes TXN_SOURCE_CD VARCHAR2(30)

C Transaction Date (YYYYMMDD)

Yes TXN_DTTM

DATE

J External Reference Number

Yes EXT_TXN_NBR

VARCHAR2(256)

K Customer Reference Number

No CUST_REF_NBR

VARCHAR2(256)

L Division Yes CIS_DIVISION CHAR(5)

M Transaction Volume Yes TXN_VOL NUMBER(36,18)

N Transaction Amount Yes TXN_AMT NUMBER(36,18)

O Transaction Currency Yes CURRENCY_CD CHAR(3)

P Credit/Debit Indicator Yes HOW_TO_USE_TXN_FLG CHAR(1)

Q Account Identifier Type Yes ACCT_NBR_TYPE_CD CHAR(8)

R Account Identifier Yes ACCT_NBR VARCHAR2(30)

S UDF_NBR_1 No UDF_NBR_1 NUMBER(36,18)

T UDF_NBR_2 No UDF_NBR_2 NUMBER(36,18)

U UDF_NBR_3 No UDF_NBR_3 NUMBER(36,18)

V UDF_NBR_4 No UDF_NBR_4 NUMBER(36,18)

W UDF_NBR_5 No UDF_NBR_5 NUMBER(36,18)

X UDF_NBR_6 No UDF_NBR_6 NUMBER(36,18)

Y UDF_NBR_7 No UDF_NBR_7 NUMBER(36,18)

Z UDF_NBR_8 No UDF_NBR_8 NUMBER(36,18)

AA UDF_NBR_9 No UDF_NBR_9 NUMBER(36,18)

AB UDF_NBR_10 No UDF_NBR_10 NUMBER(36,18)

AC UDF_NBR_11 No UDF_NBR_11 NUMBER(36,18)

AD UDF_NBR_12 No UDF_NBR_12 NUMBER(36,18)

AE UDF_NBR_13 No UDF_NBR_13 NUMBER(36,18)

AF UDF_NBR_14 No UDF_NBR_14 NUMBER(36,18)



Column Name



AG UDF_NBR_15 No UDF_NBR_15 NUMBER(36,18)

AH UDF_NBR_16 No UDF_NBR_16 NUMBER(36,18)

AI UDF_NBR_17 No UDF_NBR_17 NUMBER(36,18)

AJ UDF_NBR_18 No UDF_NBR_18 NUMBER(36,18)

AK UDF_NBR_19 No UDF_NBR_19 NUMBER(36,18)

AL UDF_NBR_20 No UDF_NBR_20 NUMBER(36,18)

AM UDF_AMT_1 No UDF_AMT_1 NUMBER(36,18)

AN UDF_AMT_2 No UDF_AMT_2 NUMBER(36,18)

AO UDF_AMT_3 No UDF_AMT_3 NUMBER(36,18)

AP UDF_AMT_4 No UDF_AMT_4 NUMBER(36,18)

AQ UDF_AMT_5 No UDF_AMT_5 NUMBER(36,18)

AR UDF_AMT_6 No UDF_AMT_6 NUMBER(36,18)

AS UDF_AMT_7 No UDF_AMT_7 NUMBER(36,18)

AT UDF_AMT_8 No UDF_AMT_8 NUMBER(36,18)

AU UDF_AMT_9 No UDF_AMT_9 NUMBER(36,18)

AV UDF_AMT_10 No UDF_AMT_10 NUMBER(36,18)

AW UDF_CURRENCY_CD_1 No UDF_CURRENCY_CD_1 CHAR(3)

AX UDF_CURRENCY_CD_2 No UDF_CURRENCY_CD_2 CHAR(3)

AY UDF_CURRENCY_CD_3 No UDF_CURRENCY_CD_3 CHAR(3)

AZ UDF_CURRENCY_CD_4 No UDF_CURRENCY_CD_4 CHAR(3)

BA UDF_CURRENCY_CD_5 No UDF_CURRENCY_CD_5 CHAR(3)

BB UDF_CURRENCY_CD_6 No UDF_CURRENCY_CD_6 CHAR(3)

BC UDF_CURRENCY_CD_7 No UDF_CURRENCY_CD_7 CHAR(3)

BD UDF_CURRENCY_CD_8 No UDF_CURRENCY_CD_8 CHAR(3)

BE UDF_CURRENCY_CD_9 No UDF_CURRENCY_CD_9 CHAR(3)

BF UDF_CURRENCY_CD_10 No UDF_CURRENCY_CD_10 CHAR(3)

BG UDF_DTTM_1 (YYYYMMDD)

No UDF_DTTM_1 DATE

BH UDF_DTTM_2 (YYYYMMDD)

No UDF_DTTM_2 DATE



Column Name



BI UDF_DTTM_3 (YYYYMMDD)

No UDF_DTTM_3 DATE

BJ UDF_DTTM_4 (YYYYMMDD)

No UDF_DTTM_4 DATE

BK UDF_DTTM_5 (YYYYMMDD)

No UDF_DTTM_5 DATE

BL UDF_CHAR_1 No UDF_CHAR_1 VARCHAR2(60)

BM UDF_CHAR_2 No UDF_CHAR_2 VARCHAR2(60)

BN UDF_CHAR_3 No UDF_CHAR_3 VARCHAR2(60)

BO UDF_CHAR_4 No UDF_CHAR_4 VARCHAR2(60)

BP UDF_CHAR_5 No UDF_CHAR_5 VARCHAR2(60)

BQ UDF_CHAR_6 No UDF_CHAR_6 VARCHAR2(60)

BR UDF_CHAR_7 No UDF_CHAR_7 VARCHAR2(60)

BS UDF_CHAR_8 No UDF_CHAR_8 VARCHAR2(60)

BT UDF_CHAR_9 No UDF_CHAR_9 VARCHAR2(60)

BU UDF_CHAR_10 No UDF_CHAR_10 VARCHAR2(60)

BV UDF_CHAR_11 No UDF_CHAR_11 VARCHAR2(60)

BW UDF_CHAR_12 No UDF_CHAR_12 VARCHAR2(60)

BX UDF_CHAR_13 No UDF_CHAR_13 VARCHAR2(60)

BY UDF_CHAR_14 No UDF_CHAR_14 VARCHAR2(60)

BZ UDF_CHAR_15 No UDF_CHAR_15 VARCHAR2(60)

CA UDF_CHAR_16 No UDF_CHAR_16 VARCHAR2(60)

CB UDF_CHAR_17 No UDF_CHAR_17 VARCHAR2(60)

CC UDF_CHAR_18 No UDF_CHAR_18 VARCHAR2(60)

CD UDF_CHAR_19 No UDF_CHAR_19 VARCHAR2(60)

CE UDF_CHAR_20 No UDF_CHAR_20 VARCHAR2(60)

CF UDF_CHAR_21 No UDF_CHAR_21 VARCHAR2(60)

CG UDF_CHAR_22 No UDF_CHAR_22 VARCHAR2(60)

CH UDF_CHAR_23 No UDF_CHAR_23 VARCHAR2(60)

CI UDF_CHAR_24 No UDF_CHAR_24 VARCHAR2(60)

CJ UDF_CHAR_25 No UDF_CHAR_25 VARCHAR2(60)



Column Name



CK UDF_CHAR_26 No UDF_CHAR_26 VARCHAR2(60)

CL UDF_CHAR_27 No UDF_CHAR_27 VARCHAR2(60)

CM UDF_CHAR_28 No UDF_CHAR_28 VARCHAR2(60)

CN UDF_CHAR_29 No UDF_CHAR_29 VARCHAR2(60)

CO UDF_CHAR_30 No UDF_CHAR_30 VARCHAR2(60)

CP UDF_CHAR_31 No UDF_CHAR_31 VARCHAR2(60)

CQ UDF_CHAR_32 No UDF_CHAR_32 VARCHAR2(60)

CR UDF_CHAR_33 No UDF_CHAR_33 VARCHAR2(60)

CS UDF_CHAR_34 No UDF_CHAR_34 VARCHAR2(60)

CT UDF_CHAR_35 No UDF_CHAR_35 VARCHAR2(60)

CU UDF_CHAR_36 No UDF_CHAR_36 VARCHAR2(60)

CV UDF_CHAR_37 No UDF_CHAR_37 VARCHAR2(60)

CW UDF_CHAR_38 No UDF_CHAR_38 VARCHAR2(60)

CX UDF_CHAR_39 No UDF_CHAR_39 VARCHAR2(60)

CY UDF_CHAR_40 No UDF_CHAR_40 VARCHAR2(60)

CZ UDF_CHAR_41 No UDF_CHAR_41 VARCHAR2(60)

DA UDF_CHAR_42 No UDF_CHAR_42 VARCHAR2(60)

DB UDF_CHAR_43 No UDF_CHAR_43 VARCHAR2(60)

DC UDF_CHAR_44 No UDF_CHAR_44 VARCHAR2(60)

DD UDF_CHAR_45 No UDF_CHAR_45 VARCHAR2(60)

DE UDF_CHAR_46 No UDF_CHAR_46 VARCHAR2(60)

DF UDF_CHAR_47 No UDF_CHAR_47 VARCHAR2(60)

DG UDF_CHAR_48 No UDF_CHAR_48 VARCHAR2(60)

DH UDF_CHAR_49 No UDF_CHAR_49 VARCHAR2(60)

DI UDF_CHAR_50 No UDF_CHAR_50 VARCHAR2(60)



2. Viewing TFM ODI Artifacts This section explains how to view the ODI artifacts for TFM. It also lists and explains a set of activities that you need to perform in ODI after the ODI artifacts are imported.

2.1 Creating Login for Master Repository Once you have created the master repository schema in ODI, you need to create login for the master repository. To create the login for the master repository:

1. Launch ODI Studio. The Oracle Data Integrator screen appears.

Figure 6: Oracle Data Integrator Screen

2. Click File and then select New. The New Gallery dialog box appears.



Figure 7: New Gallery Dialog Box

3. Select the Create a New ODI Repository Login option from the list and then click OK. The Repository Connection Information dialog box appears.




The Repository Connection Information dialog box contains the following fields:

Field Description Mandatory (Yes or No)

Oracle Data Integrator Connection

Login Name Used to specify the login name for the repository. Yes

User Used to specify the ODI admin user name. You need to specify the user name that you have used while creating repositories.

Yes

Password Used to specify the password for the ODI admin user. You need to specify the password that you have used while creating repositories.

Yes

Database Connection (Master Repository)

User Used to specify the user name. You need to specify the user name that you have used while creating master repository schema.

Yes

Password Used to specify the password for the user name. You need to specify the user name that you have used while creating master repository schema.

Yes

Driver List Used to select the driver that you want to use to connect to the master repository.

Yes

Driver Name Used to specify the driver name.

Note: The driver name appears automatically for the pre-defined drivers.

Yes

URL Used to specify the JDBC URL that you want to use to connect to the master repository.

Yes

Work Repository

Master Repository Only

Used to indicate that you want to create login for the master repository.

Note: This field is required while creating login for the master repository.

Yes (Conditional)



Field Description Mandatory (Yes or No)

Work Repository Used to indicate that you want to create login for the work repository.

Note:

The corresponding field is enabled only when you select the Work Repository option. You need to specify the name of the work repository for which you want to create the login.

This field is required while creating login for the work repository.

Yes (Conditional)

Default Connection Used to indicate whether you want to set this as a default connection.

No

4. Enter the required details in the Oracle Data Integrator Connection section.

In Login Name, for example, type Transaction_Feed_Management.

In User Name, for example, type SUPERVISOR.

In Password, for example, type supervisor.

5. Enter the required details in the Database Connection (Master Repository) section.

In User, for example, type DEV_ODI_REPO

In Password, for example, type Welcome1.

In Driver List, select Oracle JDBC Driver from the drop-down list. The oracle.jdbc.OracleDriver automatically appears in the Driver Name field. In URL, for example, type jdbc:oracle:thin:@<SERVICE_NAME>:<PORT>:<DB_NAME>.

6. Select the Master Repository Only option in the Work Repository section.

7. Click Test. A message appears indicating that the connection to the master repository was established successfully.

8. Click OK. The login is created for the master repository.



2.2 Creating Login for Work Repository Once a login for the master repository is created, you need to create a login for the work repository. To create a login for the work repository:

1. Click the Topology tab. The Topology tab appears.

2. Expand the Repositories pane.

3. Right-click on the Work Repositories node. A shortcut menu appears.

4. Select the New Work Repository option from the shortcut menu. The Work Repository Creation Wizard appears.

5. Select Specify ODI Work Repository connection properties option to view the respective fields in the right pane.

Figure 9: Work Repository Creation Wizard

6. Enter the work repository connection details, such as JDBC Driver, JDBC URL, User Name, and Password. You need to specify the details that you used while creating work repository.

7. Click Next. The Specify ODI Work Repository properties page appears.



Figure 10: Specify ODI Work Repository properties Page

8. Enter the work repository details such as Id, Name, Password and select the Work Repository Type from the drop-down list. You need to specify the details that you used while creating work repository.

9. Click Finish. The login is created for the work repository.

2.3 Connecting to the Work Repository To connect to the Work repository:

1. Launch the ODI Studio. The Oracle Data Integrator screen appears.

2. Click ODI and then select Connect. The Oracle Data Integrator Login dialog box appears.

Figure 11: Oracle Data Integrator Login Dialog Box



The Oracle Data Integrator Login dialog box contains the following fields:

Field Name Description Mandatory (Yes or No)

Login Name Used to select the login name that you want to use to connect to the work repository.

Yes

User Indicates the ODI admin user name through which the connection will be established.

Not applicable

Password Indicates the ODI admin password through which the connection will be established.

Not applicable

3. Select the login name from the drop-down list (for example, Transaction_Feed_Management) that you want to use to connect to the work repository.

4. Click the Edit ( ) icon. The Repository Connection Information dialog box appears.


5. Select the Work Repository option in the Work Repository section.



6. Click the Search ( ) icon corresponding to the Work Repository field. The Select Repository dialog box appears.

Figure 13: Select Repository Dialog Box

7. Select the work repository name from the list and then click OK. The connection to the work repository is established.

Note: By default, the Designer tab appears when you login to the work repository.

2.4 Viewing Procedures, Mappings and Packages in the Work Repository

Once you import the ODI artifacts for TFM, you can view the procedures, mappings, and packages imported in the work repository.

2.4.1 Viewing Procedures

To view procedures, follow the below steps:

1. In the Designer tab, expand the Projects pane.

2. Click the Expand ( ) icon corresponding to the First Folder node. A node tree appears.

3. Click the Expand ( ) icon corresponding to the Procedures node to view the procedures imported in the work repository.



Figure 1: Procedures

There are following four sub-procedures:

Initial Setup - involves following procedures:

o Creates a table named ODI_FILE_NAMES in the target database to store the file names that you want to process at the time of Run

o Creates a folder named Processed_Files to store the processed files.

Insert Dummy Data - This procedure creates default header when a CSV file does not contain the header record. This default header is stored in the CI_TXN_HEADER table.

Multi File Processor – This procedure creates a file named Filenames.txt inside the user defined location to store the names of the files that you want to upload to the target database.

Truncate Tables – This procedure deletes all data from the CI_TXN_HEADER and CI_TXN_DETAIL_STG tables in the target database. Therefore, do not use this procedure.

In case the description in the email needs to be changed, the following steps need to be followed:

1. Open Procedure “Send Mail” and open the task named “SendMail”.

2. Change the subject line and body of the mail as per the needs and regenerate the scenarios.

2.4.2 Viewing Mappings

To view mappings, follow the below steps:

1. Click the Expand ( ) icon corresponding to the Mappings node to view the mappings imported in the work repository.



Figure 2: Mappings

There are following three sub-mappings:

CI_TXN_HEADER – This mapping helps to move header record from the flat file to the CI_TXN_HEADER table in the target database.

ODI_FILE_NAME – This mapping helps to move file names from the Filenames.txt file to the ODI_FILE_NAMES table in the target database.

TXN_STAGING_TABLE – This mapping helps to move transaction record from the flat file to the CI_TXN_DETAIL_STG and CI_TXN_DETAIL_K table in the target database.

2.4.3 Viewing Packages To view packages, follow the below steps:

1. Click the Expand ( ) icon corresponding to the Packages node to view the packages imported in the work repository.



Figure 3: Packages

There are following two packages:

TableInsertion – This is the main package which inserts the data from the flat file to the target database using the packages, mappings, and procedures imported in the work repository. This package internally runs following processes in the specified order:

a. Creates the Filenames.txt file using the Multi_File_Processor procedure.

b. Moves the file names listed in the Filenames.txt file to the ODI_FILE_NAMES table using the ODI_FILE_NAME mapping.

c. Reads the file names sequentially from the ODI_FILE_NAMES table using variables.

d. Calls the SingleFileExecution package for uploading data from each file.

This package contains the following two scenarios:

TABLEINSERTION_SYNCHRONOUS – In this scenario, one file is uploaded at a time. The consecutive file is uploaded only when the previous file upload is complete. If any error occurs while uploading a file, the process stops and the remaining files in the queue are not uploaded.

TABLEINSERTION_ASYNCHRONOUS – In this scenario, the files are uploaded in parallel. Therefore, we strongly recommend you to use this scenario to overcome the above stated problem.

SingleFileExecution – This package is internally used by the TableInsertion package. It processes one file at a time and uploads the data to the target database using the CI_TXN_HEADER and TXN_STAGING_TABLE mappings. Once the file is successfully processed, it is moved to the Processed_Files folder. In case there is an error in



execution, the file is moved to the Error_files folder. Note that this package should not be executed separately.

2.5 Viewing Model of the Work Repository Once you import the ODI artifacts for TFM, you can view the model of the work repository. To view the model of the work repository:

1. In the Designer tab, expand the Models pane to view the structure of the work repository.

2. Click the Expand ( ) icon corresponding to the VMA_ODI node. It contains three sub nodes:

FILE_NAME

VMA_APP_DB

VMA_FLAT_FILES

3. Click the Expand ( ) icon corresponding to the VMA_APP_DB node to view the tables in which the transaction data is uploaded.

Note: The transaction data is uploaded in the CI_TXN_HEADER, CI_TXN_DETAIL_STG and CI_TXN_DETAIL_K tables. The CI_TXN_REC_TYPE and CI_TXN_SOURCE tables are used to check whether the transaction record type and transaction source mentioned in the flat files are valid.

4. Click the Expand ( ) icon corresponding to the VMA_FLAT_FILES node to view the flat file used while uploading the transaction data.

5. Click the Expand ( ) icon corresponding to the FILE_NAME node to view the text file that contains the file names.



Figure 4: Models Pane

To view the list of scenarios present, you first need to select ‘EXECUTION’ type work repository. Click the Expand ( ) icon corresponding to the Load Plans and Scenarios node. You will see the list of load plans and scenarios within the Operator tab.



Figure 18: Load Plans and Scenarios



2.6 Editing the Physical Architecture of the Source File (VMA_FLATFILES)

To view the physical architecture of the VMA_FLATFILES:

1. In the Topology tab, expand the Physical Architecture.

2. Click the Expand ( ) icon corresponding to the Technologies node. A node tree appears.

3. Click the Expand ( ) icon corresponding to the File node. A node tree appears.

4. Click the Expand ( ) icon corresponding to the VMA_FLATFILES node. A node tree appears,

5. Double-click the VMA_FLATFILES.<Directory> node. The VMA_FLATFILES.<Directory> page appears in the right pane.

Note:

The flat files must be stored at a particular location. The flat files will be uploaded from this location to the target database via ODI. The flat file location is fetched from the config.properties file to the Directory field. You can either save your flat files in this folder or you can create a new folder in the desired location and update the path accordingly in the config.properties file.

Ensure that the flat file location is specified in both Directory (Schema) and Directory (Work Schema) fields.

Use Forward Slash (/) in the flat file path.

The folder where the flat files are placed must have both read and write privileges.

Figure 19: VMA_FLATFILES.<Directory> Page



2.7 Editing the Physical Architecture of the Target Database (VMA_APP_DB)

To view the physical architecture of the VMA_APP_DB:

1. In the Topology tab, expand the Physical Architecture pane.


3. Click the Expand ( ) icon corresponding to the Oracle node. A node tree appears.

4. Double-click the VMA_APP_DB node. The VMA_APP_DB page appears in the right pane.

Figure 20: VMA_APP_DB Tab

5. Enter the target database connection details such as User Name and Password.

6. Click the JDBC link in the left pane. The JDBC page appears.



Figure 21: JDBC Page

7. Enter oracle.jdbc.OracleDriver in the JDBC Driver field.

8. The JDBC URL to connect to the target database is entered as specified in the config.properties file. The JDBC URL must be in the jdbc:oracle:thin:@<host>:<port>:<SID> format.

9. Save the changes made to the physical architecture of the target database.

10. Expand the VMA_APP_DB node in the Topology tab.

11. Double-click the VMA_APP_DB.<Schema> node. The VMA_APP_DB.<Schema> page appears.



Figure 22: VMA_APP_DB.<Schema> Page

Note:

The schema owner using which you want to upload the data to the target database must be specified in

the Schema (Schema) and Schema (Work Schema) fields. By default, CISADM is specified in these fields. You can edit the schema owner, if required.

The schema owner name must be specified in the capital letters.

2.8 Viewing the Logical Architecture of the Source File (VMA_FLATFILES)

To view the logical architecture of the VMA_FLATFILES:

1. In the Topology tab, expand the Logical Architecture pane.


3. Click the Expand ( ) icon corresponding to the File node. A node tree appears.

4. Double-click the VMA_FLATFILES node. The VMA_FLATFILES page appears in the right pane.



Figure 23: VMA_FLATFILES Page

5. View the logical schema details of the source file.

2.9 Viewing the Logical Architecture of the Target Database (VMA_APP_DB)

To view the logical architecture of the VMA_APP_DB:

1. In the Topology tab, expand the Logical Architecture pane.


3. Click the Expand ( ) icon corresponding to the Oracle node. A node tree appears.

4. Double-click the VMA_APP_DB node. The VMA_APP_DB page appears in the right pane.



Figure 24: VMA_APP_DB Page

5. View the logical schema details of the target database.



3. Preparing the Target Database This section explains how to setup the target database before the transaction data is uploaded through ODI package. This task is a one-time activity.

3.1 Starting Agent TFMagent is available in the TFM ODI package. You can use this agent as standalone agent or Java EE agent after making the Standalone or Java EE specific changes to the agent. You can also create a custom agent as per your requirement.

Before you start the Standalone or Java EE agent, you need to configure the domain for Standalone or Java EE agent.

Note: For more information on how to configure the domain for Standalone or Java EE agent, refer to the Configuring the Domain for the Standalone Agent or Configuring the Domain for the Java EE Agent section, respectively in the Installing and Configuring Oracle Data Integrator Guide.

You can also define maximum number of sessions while configuring the agent. More number of sessions leads to more files being processed simultaneously in the asynchronous mode. To set the maximum number of sessions for TFMagent, double-click on the TFMagent node in the Physical Architecture pane and then set the value in the Maximum number of sessions field (in the right pane).

For example, to start the standalone agent:

1. Change to the BIN directory using the following command:

AIX, Linux:

cd <ODI_HOME>/user_projects/domains/<DOMAIN_NAME>/bin

Windows:

cd <ODI_HOME>\user_projects\domains\<DOMAIN_NAME>\bin

Note: The <ODI_HOME> is the location where Oracle Data Integrator is installed.

2. Start the standalone agent for the repository connection using the following command:

AIX, Linux:

./agent.sh -NAME=TFMagent

Windows:

agent.cmd -NAME=TFMagent



Figure 25: Starting Agent

Note: For more information on how to start Java EE agent, refer to the Configuring the Domain for the Java EE Agent section in the Installing and Configuring Oracle Data Integrator Guide.

4. Uploading Transaction Data This section explains how to upload the transaction data from the flat file to the target database using the packages in ODI.

4.1 Executing the Table Insertion Package To upload the transaction data from the flat file to the target database, you need to execute the TableInsertion package. You can execute this package in asynchronous or synchronous mode. To execute the TableInsertion package, following steps should be followed:



3. Click the Expand ( ) icon corresponding to the Packages node. A node tree appears.

4. Click the Expand ( ) icon corresponding to the TableInsertion node. A node tree appears.

5. Click the Expand ( ) icon corresponding to the Scenarios node. A node tree appears.

6. Right-click on the TABLEINSERTION_ASYNCHRONOUS or TABLEINSERTION_SYNCHRONOUS scenario. A shortcut menu appears.



Figure 26: Scenario Shortcut Menu



7. In the Operator tab, expand the Session List pane.

8. Click the Expand ( ) icon corresponding to the All Executions node. A node tree appears.

9. Double-click on the session name to view its details. The Session page appears in the right pane.

Figure 27: Session Details

Note that new session is created to upload each flat file. The icon corresponding to each session

in the left pane indicates the current status of the session. The ( ) icon indicates that the

session was successfully executed, whereas the ( ) icon indicates that an error occurred

while executing the session. In addition, the ( ) icon indicates that the session was completed, but with some warnings due to bad data.

You can double-click each session to view whether the flat file is uploaded successfully to the target database. The transactions are uploaded only when the transaction record type and transaction source mentioned in the flat files exist in the target database.

The default header is created in the CI_TXN_HEADER table when the header record does not exist in the CSV file. Once the transaction data file is successfully uploaded, the file is moved to the Processed_Files folder.

Note:

The temporary tables prefixed with I$ and C$ are created for each flat file that you have uploaded. A unique alphanumeric code is appended at the end of the temporary table names. This helps to avoid overlapping when multiple files are processed simultaneously. However, only temporary table prefixed with E$ is created to store errors that occurred in all sessions.

The Knowledge modules named LKM File to SQL, CKM SQL, and IKM SQL Incremental Update in the above scenarios are slightly modified.



While uploading the transactions if all the files present at the folder have already been processed before, an email alert is generated stating “No new files present at <location>”.

In case only some files have been processed and others are new for processing, then flow will be executed as usual and the already processed files will remain at the same location. Other executed files are either moved to Processed_Files or Error_files folder.



5. Troubleshooting If the data is corrupt, the transaction data file is not successfully uploaded to the target database. This section lists the possible errors that you may come across while uploading a transaction data file and how you can resolve such errors.

5.1 Unique Constraint Violated There might be situations when you will notice “Unique constraint violated” error in the Error Message field. This is because more than one header record is available in the flat file.

Figure 28: Unique Constraint Violated Error

5.2 Load Data is in Error There might be situations when you will notice “Load Data is in Error” error in the Error Message field. This is because the data in any column has exceeded the maximum field length. You need to immediately check whether the following files are created in the folder where the flat files are available:

<File Name>.csv.bad – Contains the usage record which has corrupt data.

<File Name>.csv.error – Lists the columns which have exceeded the maximum field length.



Figure 29: Field Length Error

5.3 No Files Found There might be situations when you will notice “No Files Found” error in the Error Message field. This is because no flat files are available in the specified directory.

Figure 30: No Files Found Error



5.4 File Name Exists There might be situation when you will notice the “File Name already exists” error. This error is because the same file already exists in the CI_TXN_HEADER table i.e. a file with a similar name has already been processed.

Figure 31: File Name Exists Error

5.5 Missing Data There might be situations when the number of errors exceeds 0. You need to check the ODI_ERR_MESS column corresponding to the session in the E$_CI_TXN_DETAIL_STG or E$_CI_TXN_HEADER table. The error might have occurred due to the following:

Mandatory data is missing

Transaction record type does not exist in the target database

Transaction source does not exist in the target database



Figure 32: Missing Data Error

Note that if error occurs while uploading any transaction data file, the session is roll-backed and the transaction data is not uploaded to the target database. However, the temporary files created for the session are not deleted. You will have to manually delete these temporary tables prefixed with I$ and C$ from the target database.



6. Scheduling Follow the steps below to schedule the TableInsertion package execution at given intervals in ODI:



3. Click the Expand ( ) icon corresponding to the Packages node. A node tree appears.

4. Click the Expand ( ) icon corresponding to the TableInsertion node. A node tree appears.

5. Click the Expand ( ) icon corresponding to the Scenarios node. A node tree appears.

6. Click the Expand ( ) icon corresponding to the TABLEINSERTION_ASYNCHRONOUS or TABLEINSERTION_SYNCHRONOUS scenario depending on the mode you want to schedule the package in.

7. Right-click on the Scheduling node. A shortcut menu appears.

Figure 33: Scheduling

8. Select the New Scheduling option. The Scenario Scheduling page appears in the right pane.



Figure 34: Scenario Scheduling Page

9. Select TFMagent option from the Logical Agent drop-down list.

10. Select the required frequency from the Execution section.

11. Click Save. The changes are saved.

12. In the Topology tab, expand the Physical Architecture pane.

13. Click the Expand ( ) icon corresponding to the Agents node. A node tree appears.

14. Double-click on the TFMagent node. The TFMagent page appears in the right pane.



Figure 35: TFMagent Page

15. Click Update Schedule tab. The Select Repositories dialog box appears.

Figure 36: Select Repositories Dialog Box



16. Ensure that the required work repository is selected and then click OK. A message appears indicating that the schedule update is complete.

Figure 37: Information Dialog Box