BNK_RCN_CYC_E(SQL Table) |
Index Back |
---|---|
BTF: Bank Recon Load (Cycle)Batch Testing Framework |
# | PeopleSoft Field Name | PeopleSoft Field Type | Database Column Type | Description |
---|---|---|---|---|
1 | TEST_CASE | Character(30) | VARCHAR2(30) NOT NULL | BTF Test Case |
2 | BNK_ID_NBR | Character(20) | VARCHAR2(20) NOT NULL |
A literal alphanumeric attribute that uniquely identifies a given bank or counterparty.
Prompt Table: BANK_ID_VW |
3 | BANK_ACCOUNT_NUM | Character(35) | VARCHAR2(35) NOT NULL |
The literal unique identifier associated with a given bank/counterparty account.
Prompt Table: BANK_ACCTNUM_VW |
4 | RECON_CYCLE_NBR | Number(10,0) | DECIMAL(10) NOT NULL | The bank statement ID. |
5 | BNK_LOAD_DTTM | DateTime(26) | TIMESTAMP |
The time and date a bank statement is loaded into the system.
Default Value: %Datetime |
6 | CYCLE_STATUS | Character(1) | VARCHAR2(1) NOT NULL |
Cycle Status
C=Complete E=Load Failed F=Fatal Error I=EDI Loaded L=Loading N=Ready P=Selected R=Ready X=Reconciling Default Value: R |
7 | OPRID | Character(30) | VARCHAR2(30) NOT NULL |
A user's ID (see PSOPRDEFN).
Prompt Table: OPRID_VW |
8 | ASOFDATE | Date(10) | DATE |
As of Date
Default Value: %date |
9 | ASOFTIME | Time(15) | TIMESTAMP |
As of Time
Default Value: %Time |
10 | RECEIVER | Character(20) | VARCHAR2(20) NOT NULL | Receiver is used in bank reconciliation |
11 | SENDER | Character(20) | VARCHAR2(20) NOT NULL | Sender will be used in bank statements |
12 | BTB_STATUS | Character(1) | VARCHAR2(1) NOT NULL |
Book to Bank ready flag.
N=No Y=Yes Y/N Table Edit Default Value: N |
13 | BTB_RECON_STATUS | Character(1) | VARCHAR2(1) NOT NULL |
Book to bank Reconciliation Status
1=Confirmed 2=Awaiting Confirmation 3=Calculating 4=New Default Value: 4 |
14 | AR_LOADED_SW | Character(1) | VARCHAR2(1) NOT NULL |
Loaded to A/R
Y/N Table Edit Default Value: N |
15 | CURRENCY_CD | Character(3) | VARCHAR2(3) NOT NULL | Currency Code |
16 | BNK_STMT_TYPE | Character(1) | VARCHAR2(1) NOT NULL |
Bank statement type
1=Current Day 2=Previous Day 3=Statement Analysis |
17 | EVENT_TRACKING_ID | Number(10,0) | DECIMAL(10) NOT NULL | The event tracking ID is used in order to correlate objects with an event. Each object (i.e. Payment) will store the tracking ID with a given payment. That way the system can obtain all the events for a given payment via the tracking ID. |
18 | FILE_CREATE_DT | Date(10) | DATE | File Creation Date |
19 | DTTM_REFRESHED | DateTime(26) | TIMESTAMP | Specifies the date and time of the last refresh of the expected results data. This field is used in the Batch Test Framework process. |