Amex Chargeback Document Batch UML


Parent:    File Batch
Added On:  12/08/15 
Module:  UniCharge 
Type:  Entity  Status:  Active 
Java Class:  AmexChargebackDocumentBatch 
Added On:  06/06/16
SQL Column:  
Java Field:  accountNumber
Status:  Active
SQL Type:  
Java Type:  String
Attributes: Transient
Account number of the credit card holder.
Added On:  05/17/16
SQL Column:  BATCH_ERROR_STATUS
Java Field:  batchErrorStatus
Status:  Active
SQL Type:  varchar(100)
Java Type:  String
Attributes:
Added On:  02/01/16
SQL Column:  BTCH_ID
Java Field:  btchId
Status:  Active
SQL Type:  varchar(7)
Java Type:  String
Attributes:
Added On:  12/08/15
SQL Column:  CASE_NO
Java Field:  caseNo
Status:  Active
SQL Type:  varchar(15)
Java Type:  String
Attributes:
Added On:  12/08/15
SQL Column:  CHARGEBACK_CASE_FK
Java Field:  chargebackCase
Status:  Active
SQL Type:  bigint(20)
Java Type:  Long
References Chargeback Case
Attributes:
Reference to the entity that represents chargeback case information.
Added On:  02/01/16
SQL Column:  DOCUMENT_COUNT
Java Field:  documentCount
Status:  Active
SQL Type:  int(11)
Java Type:  Integer
Attributes:
Added On:  12/08/15
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.
Added On:  12/08/15
SQL Column:  SE_ACCOUNT_NO
Java Field:  seAccountNo
Status:  Active
SQL Type:  varchar(10)
Java Type:  String
Attributes: