You are on page 1of 19

411 Legget Drive

Ottawa, ON K2K 3C9


Telephone: (613) 686-5291
Facsimile: (613) 271-0816

TDX Operation Manual

Revision: 1.1

This document contains confidential information, which is property of Telepin Software. No part of its contents may be used, copied,
disclosed or conveyed to any party in any manner whatsoever without prior written permission from Telepin Software.
Copyright 2009 Telepin Software Corporation. All Rights Reserved.

Telepin Software

TDX Operation Manual

Rev. 1.1

Table of Contents
1

INTRODUCTION ........................................................................................................................................ 1

GETTING STARTED .................................................................................................................................. 1


2.1
EXTRACT DATA ..............................................................................................................................................2
2.1.1
Quick Set ................................................................................................................................................3
2.2
EXTRACT DESCRIPTOR EDITOR ......................................................................................................................4
2.2.1
Descriptor Editor ...................................................................................................................................5
2.2.1.1

2.3
3

Condition Examples ........................................................................................................................................... 6

DATA VIEW EDITOR .......................................................................................................................................6

AVAILABLE VIEWS................................................................................................................................... 7
3.1
VIEW WINDOW ...............................................................................................................................................7
3.1.1
Configuring the view window ................................................................................................................7
3.1.2
Determining the actual date range ........................................................................................................7
3.1.3
List partitions covered by view window .................................................................................................8
3.2
BASE VIEWS ...................................................................................................................................................8
3.2.1
Base views in view window ....................................................................................................................8
3.2.2
Dynamic creation of base views ............................................................................................................9
3.3
PRODUCTION VIEWS .......................................................................................................................................9
3.3.1
V$$ACCOUNTUSERS ...........................................................................................................................9
3.3.2
V$$BRANDSDAILYREPORT ..............................................................................................................10
3.3.3
V$$CREDIT_TRANSFER ....................................................................................................................10
3.3.4
V$$CUSTOMER_QUOTA_TOPUPS ..................................................................................................11
3.3.5
V$$DCLTOPUPS ................................................................................................................................12
3.3.6
V$$DCLTRANSFERS ..........................................................................................................................12
3.3.7
V$$FINANCIAL_ACTIVITY ................................................................................................................13
3.3.8
V$$NUMBEROFTX .............................................................................................................................13
3.3.9
V$$OWNERBRANDSDAILYREPORT.................................................................................................14
3.3.10
V$$PDVA.............................................................................................................................................14
3.3.11
V$$QUOTA_CREDIT_TRANSFERES ................................................................................................14
3.3.12
V$$REFUNDSALESORDER ...............................................................................................................15
3.3.13
V$$SALESTRANSACTION ..................................................................................................................15

Proprietary Information subject to restrictions on cover page

Page ii

Telepin Software

TDX Operation Manual

Rev. 1.1

Proprietary Information subject to restrictions on cover page

Page iii

Index of Figures
No table of figures entries found.

Index of Tables
No table of figures entries found.

Telepin Software

TDX Operation Manual

Rev. 1.1

1 Introduction
Telepin is the commercial name for Telepin Software offering of on-demand purchase of electronic topup and value added switch for mobile operator. This document explains the
Telepin data extractor tool (TDX). TDX is part of the Telepin Admin suite and is used to exact generic data in XML, comma separated values (CSV) Excel format, and/or tab format (text). TDX gives the operator
the ability to define the target databases views and the selection criteria and generates extract descriptors. It enables the operator to write his own extract descriptors in simple XML format. The tool can run
interactively. This tool can be easily used to extract daily transaction for the operator data warehouse,
and proves to be a valuable tool for market analysis and research.
In this manual, the user will have an overview on how to use TDX in day-today operation and learn how
to build the report template. In addition, the manual contains a full description for the TDX views in the
database, which explain in the last chapter.

2 Getting Started
In order to login and use TDX tool, the user has to have the TDX privilege in the users access role. Run
the start.bat located in the local TDX home directory to start TDX and type username/password.

A drop-down menu enables the user to extract a report or create a new report template.

The following sections describe each of the drop-down functions in detail.

Proprietary Information subject to restrictions on cover page

Page 1

Telepin Software

TDX Operation Manual

Rev. 1.1

2.1 Extract Data


The Extract Data function allows a user to execute the database query (report template) and generate
the report. The user must choose the target report template from the Quick Set or by using the
browser. If the report template is not defined in Quick set, then Operator may use the Extract Descriptor
Editor to create one.

Field/Button

Description

Browse

Browse the existing directory system to select a report template.

Quick Set

Quick Set is list of all the predefined report templates. A user can easily
choose one of the report templates to generate the report. All report
templates are stored in the xml directory located in the local TDX home
directory. In addition, the user always has the option to view or edit the
xml report template.
Select Quick Set button ~ Quick Set page appears.

Format

The data results can be saved as XML, CSV or tab format. The user must
Proprietary Information subject to restrictions on cover page

Page 2

Telepin Software

TDX Operation Manual

Rev. 1.1

set the output format before generating the report.


Output Directory

The report results and output files are stored in the target output directory. If the output directory is not set, then all results will be stored in
the output directory located in the local home directory of the TDX.

Log

Displays logs as data is queried and the report is generated according to


the report template.

Customize Output

This feature is not supported in the current version of TDX tool. Generate to start generate the report.

Generate

Starts the process to query data and generate the report.

Clear Log

That allows the user to monitor the report processing steps. The user
can always press clear log button to clear the log.

Clear Output
Close

2.1.1

Close the tool.

Quick Set

This section explains the page that appears when the Quick Set button is selected from the Data Extract
page.

Field/Button

Description

Select

Selects the report template.

View

View the report template.

Proprietary Information subject to restrictions on cover page

Page 3

Telepin Software

TDX Operation Manual

Edit

Edit the report template.

Cancel

Closes the Quick Set tool.

Rev. 1.1

2.2 Extract Descriptor Editor


The Extract Descriptor Editor is used to generate the report template. It is a GUI used to generate the
SQL statement and saved it as an XML report template.

Proprietary Information subject to restrictions on cover page

Page 4

Telepin Software

2.2.1

TDX Operation Manual

Rev. 1.1

Descriptor Editor

In the Descriptor Editor, the Operator is able to create the report template from available database
views. All views of the TDX start with V$$ i.e. V$$ACCOUNTUSERS (refer to Chapter 3 for more detail
about V$$ database views).

Field/Button

Description

Select View

Select a specific existing view from the pull-down list.

Available Columns

Add information to the report by selecting from the available columns


and using the > key and adding it to the selected columns list (and
removing it from the available columns list).

Selected Columns

Remove information from the report by selecting from the selected


columns and using the < key, adding it to the available columns list
(and removing it from the selected columns list).

Conditions

In the conditions tab, the Operator is able to set up to four standard


SQL conditions
Columns

Name of the column to be used

Proprietary Information subject to restrictions on cover page

Page 5

Telepin Software

TDX Operation Manual

Operators

Mathematical operators such as: <, >, =, +

Value 1

Value used in the condition.

Rev. 1.1

Save As

The report template is saved by default into the xml directory located
in the local TDX home directory unless otherwise specified by the user.

Save

Save the new version of template.

Close

Close the tool.

2.2.1.1 Condition Examples


As an example for the daily report, an operator may condition the current date as follow:
current_date > to_date(to_char(sysdate-1,'dd-mm-yy'),'dd-mm-yy')
and for the weekly report, the syntax of condition might be as follows:
current_date > to_date(to_char(sysdate-7,'dd-mm-yy'),'dd-mm-yy')

2.3 Data View Editor


This feature is not supported in the current release of the TDX.
Check for update to keep TDX up to date.
Options to set the XML format either to generate Data in Tags or generate Data in Attributes.

Proprietary Information subject to restrictions on cover page

Page 6

Telepin Software

TDX Operation Manual

Rev. 1.1

3 Available Views
This chapter describes all V$$ views available for the Telepin Cayman Platform database.

3.1 View Window


3.1.1

Configuring the view window

The view period can be configured by setting the newly added view_report_begin and view_report_end
fields in the SYSTEM_CONFIGURATION table. Here are the column definitions:
Column

Type

Description

VIEW_REPORT_BEGIN

NUMBER

Number of begin days backward from current date

VIEW_REPORT_END

NUMBER

Number of end days backward from current date

The view window covers the time from TRUNC (SYSDATE-[VIEW_REPORT_BEGIN]) to TRUNC (SYSDATE[VIEW_REPORT_END]).
For example, when VIEW_REPORT_BEGIN=2, VIEW_REPORT_END=0, it means the view window covers
the time from TRUNC (SYSDATE-2) to TRUNC (SYSDATE-0). The view will cover data from yesterday and
the day before yesterday.
The view window is calculated by the V$$DATE_RANGE view, which is described in the next section.
3.1.2

Determining the actual date range

The actual date range can be determined by V$$DATE_RANGE view derived from the values of
VIEW_REPORT_BEGIN and VIEW_REPORT_END columns in SYSTEM_CONFIGURATION table. The
V$$DATE_RANGE view provides the following information:
Column

Type

Description

DATE_BEGIN

DATE

Begin date of view window

DATE_END

DATE

End date of view window

KEY_MONTH_BEGIN

NUMBER

Month partition key value of begin date

KEY_MONTH_END

NUMBER

Month partition key value of end date

KEY_DAY_BEGIN

NUMBER

Day partition key value of begin date

KEY_DAY_END

NUMBER

Day partition key value of end date

Proprietary Information subject to restrictions on cover page

Page 7

Telepin Software

3.1.3

TDX Operation Manual

Rev. 1.1

List partitions covered by view window

Two new views will list all the partition values covered by the view window for both MONTH partitions
and DAY partitions between DATE_BEGIN and DATE_END of V$$DATE_RANGE view. These views are:
V$$MONTH_LIST view
Column

Type

Description

MONTH_NUMBER

NUMBER

Partition values for month partitions

Column

Type

Description

DAY_NUMBER

NUMBER

Partition values for day partitions

V$$DAY_LIST view

These values are derived from a pre-created table called MONTH_DAY_LIST.


MONTH_DAY_LIST table
Column

Type

Description

MONTH_NUMBER

NUMBER

Month number

DAY_NUMBER

NUMBER

Day number

This table simply lists all the possible month and day values over the year, from Jan 01 through Dec 31. It
contains 366 rows, and should be read-only all the time.

3.2 Base Views


3.2.1

Base views in view window

The following views on the partitioned tables covering only the data within the partitions in the view
window:
View Name

Base Table

V$$SALES_ORDER

SALES_ORDER

V$$SALES_ORDER_DETAILS

SALES_ORDER_DETAILS

V$$PIN

PIN

V$$SALES_ORDER_DETAILS_PARTITI

SALES_ORDER_DETAILS_PARTITION

V$$SALES_ORDER_DEDICATED_ACCOU

SALES_ORDER_DEDICATED_ACCOUNT

Proprietary Information subject to restrictions on cover page

Page 8

Telepin Software

TDX Operation Manual

Rev. 1.1

In the production views, these views will replace the base tables.
3.2.2

Dynamic creation of base views

A database job is scheduled daily at midnight to automatically recreate the base views to keep up-todate to the view window. The job calls a stored procedure REFRESH_PART_VIEWS. The procedure automatically detects the Monthly and Daily Partitioning scheme and makes the base views to cover the
appropriate partitions.
Required system privileges for the user:
CREATE JOB
CREATE VIEW

3.3 Production Views


3.3.1

V$$ACCOUNTUSERS

The view contains all necessary information of the accounts and account creation date. This report can
be used to extract information about specific accounts, run daily or weekly report to show the new accounts, or/and list all accounts on a specific layer or group. Varity of templates with different business
needs can be designed for this view. The view columns are:
Column

Type

Description

CURRENT_DATE

DATE

Current system date

ACCOUNT_ID

Not Null Number (10)

Account Identification (ID)

ACCOUNT_NAME

Not Null VARCHAR2 (200)

Account Name

USER_ID

NUMBER(100)

Accounts User (Terminal) ID

CITY_ID

NUMBER(10)

City ID

CITY_NAME

VARCHAR2(30)

City Name

PROVINCE_NAME

VARCHAR2(30)

Province Name

ADDRESS

VARCHAR2(300)

Account Address

CONTACT_NAME

VARCHAR2(200)

Account Contact Name

ACCOUNT_MOBILE

VARCHAR2(15)

Accounts Mobile number

OWNER_ID

NUMBER(10)

Owner ID (ID of the owner of the Account)

DISCOUNT_PERCENT

NUMER(6,3)

Default Discount (Commission) for the Account.

DATE_CREATED

DATE

Date the Account was created.

Proprietary Information subject to restrictions on cover page

Page 9

Telepin Software

TDX Operation Manual

Rev. 1.1

UNIVERSAL_ID

VARCHAR2(30)

Accounts Universal ID

CURRENT_BALANCE

NUMBER

Current balance of the Account.

USER_NAME

VARCHAR2(30)

Accounts User (Terminal) Name

ACCESS_TYPE

VARCHAR2(3)

Terminal Access Type (POS, USSD, WEB,


Mobile, SMS).

ROLE_NAME

VARCHAR2(50)

Users Access Role name.

GROUP_ID

NUMBER(3)

Group ID where the Account belongs to.

GROUP_NAME

VARCHAR2(100)

Accounts Group Name.

LAYER_NAME

VARCHAR2(30)

Accounts Layer Name.

LAYER_ID

NUMBER(10)

Layer ID where the Account belongs to.

LANGUAGE

VARCHAR2(1)

Users Language setting.

3.3.2

V$$BRANDSDAILYREPORT

The view is a daily report that groups the number of transactions by brand and city. This report can be
used to extract sales information, customer behavioral, and information about top selling denominations and hot market spots. The report has to run for the past days in order to get accurate information.
Varity of templates with different business needs can be designed for this view. The view columns are:
Column

Type

Description

BRAND_NAME

VARCHAR2(100)

Products Brand Name

PROVINCE_NAME

VARCHAR2(30)

Province Name

CITY_NAME

VARCHAR2(30)

City Name

DAILY_DATE

DATE

Target day

NUMEROFTX

NUMBER

Number of Transactions.

3.3.3

V$$CREDIT_TRANSFER

The view columns are:


Column

Type

Description

TRANSACTION_ID

NUMBER(15)

Transaction ID

ACCOUNT_FROM_ID

NOT NULL NUMBER(10)

Account Identification (ID) transfer occurs from (the debit account).

ACCOUNT_FROM

NOT NULL VARCHAR2(200)

Account Name transfer from.

Proprietary Information subject to restrictions on cover page

Page 10

Telepin Software

TDX Operation Manual

Rev. 1.1

ACCOUNT_FROM_MOBILE

VARCHAR2(15)

Account Mobile number transfer from.

ACCOUNT_TO_ID

NOT NULL NUMBER(10)

Account Identification (ID) transfer occurs to (the credit account).

ACCOUNT_TO

NOT NULL VARCHAR2(200)

Account Name transfer to.

ACCOUNT_TO_MOBILE

VARCHAR2(15)

Account Mobile number transfer to.

TRANSFERE_DATE

NOT NULL DATE

Date the transfer occurs.

AMOUNT

NUMBER

Amount of the transfer.

3.3.4

V$$CUSTOMER_QUOTA_TOPUPS

The view contains all necessary information of the daily money transactions. This report can be used to
extract information about daily money flow (transfer or sales) within the system. This report cant be
used for reconciliation since the information is calculated daily starting from 00:00:01 till the moment of
the report creation and the account balance is showing the accumulated current balance. The report has
to run for the past days in order to get accurate information. Varity of templates with different business
needs can be designed for this view. The view columns are:
Column

Type

Description

ACCOUNT_ID

Not Null Number (10)

Account Identification (ID)

UNIVERSAL_ID

VARCHAR2(30)

Accounts Universal ID

ACCOUNT_NAME

Not Null VARCHAR2 (200)

Account Name

LEVEL_NAME

VARCHAR2(30)

Accounts Layer Name.

GROUP_NAME

VARCHAR2(100)

Accounts Group Name.

MOBILE_NUMBER

VARCHAR2(15)

Accounts Mobile number

CONTACT

VARCHAR2(200)

Account Contact Name

OWNER_ID

NUMBER(10)

Owner ID (ID of the owner of the Account)

ADDRESS

VARCHAR2(300)

Account Address

PROVINCE

VARCHAR2(30)

Province Name

CITY_NAME

VARCHAR2(30)

City Name

BALANCE

NUMBER

Current balance of the Account.

RECEIVED_QUOTA

NUMBER

The received money for parent accounts.

TRANSFERRED_QUOTA

NUMBER

The transferred money to other accounts.

TOPUP_AMOUNT

NUMBER

The total sales.

Proprietary Information subject to restrictions on cover page

Page 11

Telepin Software

3.3.5

TDX Operation Manual

Rev. 1.1

V$$DCLTOPUPS

The view lists the decline sales (Topup) transactions with the specific error message and date. In order
to create useful template from the view, date should be constrained from/to for having daily or weekly
report. Varity of templates with different business needs can be designed for this view. The view columns are:
Column

Type

Description

TRANSACTION_DATE

DATE

Transfer transaction date.

TRANSACTION_ID

NUMBER(10)

Transaction ID

ACCOUNT_ID

NUMBER(10)

Account ID

ACCOUNT_NAME

VARCHAR2(200)

Account Name

AMOUNT

NUMER(10,3)

Declined Topup amount.

ERROR_CODE

VARCHAR2(260)

Declined Error Code.

USER_NAME

VARCHAR2(100)

Accounts User (Terminal) Name

ACCESS_TYPE

VARCHAR2(20)

Terminal Access Type (POS, USSD, WEB, Mobile, SMS).

OWNER_ID

NUMBER(10)

Owner ID (ID of the owner of the Account)

MSISDN

VARCHAR2(20)

Subscriber Mobile Number

ACCOUNT_MOBILE

VARCHAR2(15)

Accounts Mobile number

BRAND_NAME

VARCHAR2(100)

Products Brand Name

3.3.6

V$$DCLTRANSFERS

The view lists the decline transfer transactions with their specific error message and date. In order to
create useful template from the view, date should be constrained from/to for having daily or weekly
report. Varity of templates with different business needs can be designed for this view. The view columns are:
Column

Type

Description

TRANSFER_DATE

NOT NULL DATE

Transfer transaction date.

AGENT_ID

NUMBER(10)

Agent (Sender) ID

CUSTOMER_ID

NUMBER(10)

Customer (Receiver) ID

QUOTA

NUMER(15,3)

Declined transferred amount.

LOG_MESSAGE

VARCHAR2(1000)

Declined error message.

CUSTOMER_NAME

VARCHAR2(200)

Customer (Receiver) Name

Proprietary Information subject to restrictions on cover page

Page 12

Telepin Software

TDX Operation Manual

CUSTOMER_MOBILE_NUMBER

VARCHAR2(15)

Customer (Receiver) Mobile Number

AGENT_NAME

VARCHAR2(200)

Agent (Sender) Name

AGENT_MOBILE_NUMBER

VARCHAR2(15)

Agent (Sender) Mobile Number

CUSTOMER_OWNER_ID

NUMBER(10)

Customers Owner ID

AGENT_OWNER_ID

NUMBER(10)

Agents Owner ID

3.3.7

Rev. 1.1

V$$FINANCIAL_ACTIVITY

The view columns are:


Column

Type

Description

TRANSACTION_DATE

DATE

Transfer transaction date.

CUSTOMER_NAME

VARCHAR2(200)

Customer (Receiver) Name

DESCRIPTION

VARCHAR2(29)

User entered description information.

CREDIT

NUMBER

Amount of the credit. If non-zero, debit must


be zero.

DEBIT

NUMBER

Amount of the debit. If non-zero, credit must


be zero.

STATUS

VARCHAR2(4)

Transaction status. For details refer to the TDS


Portal User Guide section on Transaction Status.

BALANCE_AFTER

NUMBER

Balance remaining after the transaction occurred.

3.3.8

V$$NUMBEROFTX

The view is a daily report that groups the total sale by user and city. This report can be used to extract
sales information about agent sales activity and information about most active point of sale and hot
market spots. The report has to run for the past days in order to get accurate information. Varity of
templates with different business needs can be designed for this view. The view columns are:
Column

Type

Description

CITY_NAME

VARCHAR2(30)

City Name

PROVINCE_NAME

VARCHAR2(30)

Province Name

OWNER_ID

NUMBER(10)

Account Owner ID

USER_NAME

VARCHAR2(30)

User (Terminal or Point of Sale) Name

Proprietary Information subject to restrictions on cover page

Page 13

Telepin Software

TDX Operation Manual

DAILY_DATE

DATE

Target day

NUMEROFTX

NUMBER

Number of Transactions.

AMOUNT

NUMBER

Total Net Sale

3.3.9

Rev. 1.1

V$$OWNERBRANDSDAILYREPORT

The view columns are:


Column

Type

Description

OWNER_ID

NUMBER(10)

Account Owner ID

BRAND_NAME

VARCHAR2(100)

Products Brand Name

PROVINCE_NAME

VARCHAR2(30)

Province Name

CITY_NAME

VARCHAR2(30)

City Name

DAILY_DATE

DATE

Target day

NUMEROFTX

NUMBER

Number of Transactions.

3.3.10 V$$PDVA
The view columns are:
Column

Type

Description

CUSTOMER_ID

NUMBER(10)

Customer (Receiver) ID

CUSTOMER_NAME

VARCHAR2(200)

Customer (Receiver) Name

3.3.11 V$$QUOTA_CREDIT_TRANSFERES
The view is a daily report showing the money transfer activities between agents. The report has to run
for the past days in order to get accurate information. Varity of templates with different business needs
can be designed for this view. The view columns are:
Column

Type

Description

DAILY_DATE

DATE

Target day

AGENT_ID

NUMBER(10)

Agent (Sender) ID

AGENT_NAME

VARCHAR2(200)

Agent (Sender) Name

AGENT_MOBILE

VARCHAR2(15)

Agent (Sender) Mobile Number

AGENT_CITY

VARCHAR2(30)

Agent (Sender) City Name

AGENT_PROVINCE

VARCHAR2(30)

Agent (Sender) Province Name

Proprietary Information subject to restrictions on cover page

Page 14

Telepin Software

TDX Operation Manual

AGENT_OWNER_ID

NUMBER(10)

Agents Owner ID

CUSTOMER_OWNER_ID

NUMBER(10)

Customers Owner ID

CUSTOMER_ID

NUMBER(10)

Customer (Receiver) ID

CUSTOMER_NAME

VARCHAR2(200)

Customer (Receiver) Name

CUSTOMER_MOBILE

VARCHAR2(15)

Customer (Receiver) Mobile Number

CUSTOMER_CITY

VARCHAR2(30)

Customer (Receiver) City Name

CUSTOMER_PROVINCE

VARCHAR2(30)

Customer (Receiver) Province Name

AMOUNT

NUMBER

The amount of money transferred.

Rev. 1.1

3.3.12 V$$REFUNDSALESORDER
The view lists the refunded sales (Topup) transactions with the specific reason and date. In order to
create useful template from the view, date should be constrained from/to for having daily or weekly
report. Varity of templates with different business needs can be designed for this view. The view columns are:
Column

Type

Description

TRANSACTION_ID

NUMBER(10)

Refunded Transaction ID (Sales Order Number).

TRANSACTION_DATE

DATE

Transaction date.

ACCOUNT_ID

NUMBER(10)

Account ID

ACCOUNT_NAME

VARCHAR2(200)

Account Name

OWNER_ID

NUMBER(10)

Owner ID (ID of the owner of the Account)

ACCESS_TYPE

VARCHAR2(20)

Terminal Access Type (POS, USSD, WEB, Mobile, SMS).

USER_NAME

VARCHAR2(100)

Accounts User (Terminal) Name

SUB_MSISDN

VARCHAR2(20)

Subscriber Mobile Number

AMOUNT

NUMBER(10,3)

Refunded Topup Amount

REFUND_REASON

VARCHAR2(100)

Refunded Reason

3.3.13 V$$SALESTRANSACTION
The view lists all sales (Topup) transactions declined, posted, hold...etc. for all or specific account. In
order to create useful template from the view, date should be constrained from/to for having daily or
weekly report. Varity of templates with different business needs can be designed for this view. The view
columns are:
Column

Type

Description

Proprietary Information subject to restrictions on cover page

Page 15

Telepin Software

TDX Operation Manual

Rev. 1.1

TRANSACTION_DATE

DATE

Transaction date.

TRANSACTION_ID

NUMBER(10)

Topup Transaction ID (Sales Order Number).

GROUP_ID

NUMBER(3)

Group ID where the Account belongs to.

GROUP_NAME

VARCHAR2(100)

Accounts Group Name.

LAYER_ID

NUMBER(10)

Layer ID where the Account belongs to.

LAYER_NAME

VARCHAR2(30)

Accounts Layer Name.

ACCOUNT_ID

NUMBER(10)

Account ID

ACCOUNT_NAME

VARCHAR2(200)

Account Name

AMOUNT

NUMBER(10,3)

Topup Amount

ERROR_CODE

VARCHAR2(260)

Error Code

USER_NAME

VARCHAR2(100)

Accounts User (Terminal) Name

ACCESS_TYPE

VARCHAR2(20)

Terminal Access Type (POS, USSD, WEB, Mobile, SMS).

OWNER_ID

NUMBER(10)

Owner ID (ID of the owner of the Account)

MSISDN

VARCHAR2(20)

Subscriber Mobile Number

ACCOUNT_MOBILE

VARCHAR2(15)

Accounts Mobile number

BRAND_NAME

VARCHAR2(100)

Products Brand Name

STATUS

VARCHAR2(4)

Transaction Status

Proprietary Information subject to restrictions on cover page

Page 16