FirstData Omaha Retail File Batch


Parent:    File Batch
Added On:  06/17/13 
Module:  UniCharge 
Type:  Entity  Status:  Active 
Java Class:  FirstDataOmahaRetailFileBatch 
FirstData Omaha specific File Batch representation for the settlement process. It represents a group of FirstData Omaha Capture Retail Transaction objects that are settled together as a group within a single file.

During Generation Process, FirstData Omaha Retail File Batch is converted into a settlement file, which is then registered into File Store for further processing.
Added On:  06/17/13
SQL Column:  ACTION_CODE
Java Field:  actionCode
Status:  Active
SQL Type:  varchar(1)
Java Type:  String
Attributes:
Code indicating a Host response.
Added On:  06/17/13
SQL Column:  AUTO_DOWNLOAD_INDICATOR
Java Field:  autoDownloadIndicator
Status:  Active
SQL Type:  varchar(1)
Java Type:  String
Attributes:
Character indicating the merchant profile needs an update or download of new parameter data values.
Added On:  06/17/13
SQL Column:  BATCH_ID_NUMBER
Java Field:  batchIdNumber
Status:  Active
SQL Type:  varchar(18)
Java Type:  String
Attributes:
Code identifying batch to the Host.
Added On:  06/17/13
SQL Column:  BATCH_NUMBER
Java Field:  batchNumber
Status:  Active
SQL Type:  varchar(1)
Java Type:  String
Attributes:
Number identifying the batch which is assigned by the POS device.
Added On:  06/17/13
SQL Column:  BATCHED_ITEMS
Java Field:  batchedItems
Status:  Active
SQL Type:  varchar(3)
Java Type:  String
Attributes:
Number of offline credit items being sent to the Host prior to the close transaction in the same dial-up session.
Added On:  06/17/13
SQL Column:  CREDIT_BATCH_AMOUNT
Java Field:  creditBatchAmount
Status:  Active
SQL Type:  varchar(9)
Java Type:  String
Attributes:
Total dollar-and-cent amount of all credit card transactions.
Added On:  06/17/13
SQL Column:  DEBIT_BATCH_AMOUNT
Java Field:  debitBatchAmount
Status:  Active
SQL Type:  varchar(9)
Java Type:  String
Attributes:
Total dollar-and-cent amount of all debit card transactions.
Added On:  06/17/13
SQL Column:  DEBIT_BATCH_COUNT
Java Field:  debitBatchCount
Status:  Active
SQL Type:  varchar(3)
Java Type:  String
Attributes:
Number of debit items in batch.
Added On:  06/17/13
SQL Column:  DEVICE_ID
Java Field:  deviceId
Status:  Active
SQL Type:  varchar(4)
Java Type:  String
Attributes:
Merchant-assigned code identifying the device at the merchant‘s location.
Added On:  06/17/13
SQL Column:  ITEM_NUMBER
Java Field:  itemNumber
Status:  Active
SQL Type:  varchar(3)
Java Type:  String
Attributes:
Number of the transaction in the batch; assigned by the POS.
Added On:  06/17/13
SQL Column:  MERCHANT_NUMBER
Java Field:  merchantNumber
Status:  Active
SQL Type:  varchar(19)
Java Type:  String
Attributes:
Number assigned by merchant‘s financial institution.
Added On:  06/17/13
SQL Column:  RESPONSE_CODE
Java Field:  responseCode
Status:  Active
SQL Type:  varchar(1)
Java Type:  String
Attributes:
Value defining how the System responded to the transaction.
Added On:  06/17/13
SQL Column:  RESPONSE_TEXT1
Java Field:  responseText1
Status:  Active
SQL Type:  varchar(16)
Java Type:  String
Attributes:
Message from the Host which appears on the POS device regarding close.
Added On:  06/17/13
SQL Column:  RESPONSE_TEXT2
Java Field:  responseText2
Status:  Active
SQL Type:  varchar(16)
Java Type:  String
Attributes:
Message from the Host which appears on the POS device regarding close. Field will only be present if POS device sends both credit & debit close batch information.
Added On:  06/17/13
SQL Column:  TERMINAL_ID
Java Field:  terminalId
Status:  Active
SQL Type:  varchar(9)
Java Type:  String
Attributes:
Code identifying the balancing features available to the POS from the Host.