Phone UML

Added On: 06/12/12

SQL Table: PHONE

Module: UniBill

Type: Entity Status: Active

Java Class: Phone

Available Fields:

Address Source CL
Bad Reason
Create Date
Customer Account FK
Customer FK

Extention
Id
Is Bad
Is Skip Trace Allowed
Last Skip Trace Date

Last Update Date
Merchant Account Code
Phone
Phone CL
Ref Code

Ref Creator Code
Ref ID

Address Source CL

Added On: 06/12/12

SQL Column: ADDRESS_SOURCE_CL

Java Field: addressSourceCl

Status: Active

SQL Type: varchar(1)

Java Type: String

References Address Source Classifier

Attributes:

Reference to the entity that represents information about obtaining the merchant's phone number.

Bad Reason

Added On: 06/12/12

SQL Column: BAD_REASON

Java Field: badReason

Status: Active

SQL Type: varchar(255)

Java Type: String

Attributes:

The reason why the phone was marked as invalid.

Create Date

Added On: 06/12/12

SQL Column: CREATE_DATE

Java Field: createDate

Status: Active

SQL Type: datetime

Java Type: Date

Attributes:

Date when the record was created

Customer Account FK

Added On: 07/08/12

SQL Column: CUSTOMER_ACCOUNT_FK

Java Field: customerAccount

Status: Active

SQL Type: bigint(20)

Java Type: Long

References Customer Account

Attributes:

Reference to the entity that represents customer account in the system.

Customer FK

Added On: 06/12/12

SQL Column: CUSTOMER_FK

Java Field: customer

Status: Active

SQL Type: bigint(20)

Java Type: Long

References Customer

Attributes:

Reference to the entity that represents information about the customer.

Extention

Added On: 06/12/12

SQL Column: EXTENTION

Java Field: extention

Status: Active

SQL Type: varchar(4)

Java Type: String

Attributes:

Extension of the phone number.

Added On: 06/12/12

SQL Column: ID

Java Field: id

Status: Active

SQL Type: bigint(20)

Java Type: Long

Identifier / Primary Key

Attributes: Unique, Required, CreateOnly, ReadOnly

Identifier of the object used for references; auto-incremented integer value.

Is Bad

Added On: 06/12/12

SQL Column: IS_BAD

Java Field: isBad

Status: Active

SQL Type: tinyint(1)

Java Type: Boolean

Attributes: Default:false

Indicates whether the phone number is invalid.

Is Skip Trace Allowed

Added On: 06/12/12

SQL Column: IS_SKIP_TRACE_ALLOWED

Java Field: isSkipTraceAllowed

Status: Active

SQL Type: tinyint(1)

Java Type: Boolean

Attributes: Default:true

Indcates whether skip tracing is allowed for this phone.

Last Skip Trace Date

Added On: 06/12/12

SQL Column: LAST_SKIP_TRACE_DATE

Java Field: lastSkipTraceDate

Status: Active

SQL Type: datetime

Java Type: Date

Attributes:

The date when this phone was skip traced for the last time.

Last Update Date

Added On: 10/02/12

SQL Column: LAST_UPDATE_DATE

Java Field: lastUpdateDate

Status: Active

SQL Type: datetime

Java Type: Date

Attributes:

Date when the phone information was updated the last time.

Merchant Account Code

Added On: 06/12/12

SQL Column: MERCHANT_ACCOUNT_CODE

Java Field: merchantAccountCode

Status: Active

SQL Type: int(11)

Java Type: Integer

Attributes: Required

Code of Merchant Account to which instance of this object is attributed to.
Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.

Phone

Added On: 06/12/12

SQL Column: PHONE

Java Field: phone

Status: Active

SQL Type: varchar(15)

Java Type: String

Attributes: Max Length:15

Number of customer's phone.

Phone CL

Added On: 06/12/12

SQL Column: PHONE_CL

Java Field: phoneCl

Status: Active

SQL Type: varchar(1)

Java Type: String

References Phone Classifer

Attributes:

Reference to the entity that represents the available types of current (or selected) phone number.

Ref Code

Added On: 07/10/12

SQL Column: REF_CODE

Java Field: refCode

Status: Active

SQL Type: varchar(60)

Java Type: String

Attributes:

Secondary identifier which can be used to cross-reference records between UniPay and integrated systems.

Ref Creator Code

Added On: 06/12/12

SQL Column: REF_CREATOR_CODE

Java Field: refCreatorCode

Status: Active

SQL Type: varchar(60)

Java Type: String

Attributes:

Identifier of the creator of the record which can be used to cross-reference records between UniPay and integrated systems.

Ref ID

Added On: 09/21/16

SQL Column:

Java Field: refId

Status: Active

SQL Type:

Java Type: Long

Attributes: Transient

Secondary identifier which can be used to cross-reference records between UniPay and integrated systems.

All Logos and Trademarks used or mentioned on this page are copyrighted property of their respective owners and are used for display purposes only.