| # |
PeopleSoft Field Name |
PeopleSoft Field Type |
Database Column Type |
Description |
| 1 |
 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
|
| 2 |
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
|
| 3 |
STATEMENT_ID |
Number(10,0) |
DECIMAL(10) NOT NULL |
Statement ID for bank statements, key on Bank Statement Header
Default Value: 0
|
| 4 |
BNK_LOAD_DTTM |
DateTime(26) |
TIMESTAMP |
The time and date a bank statement is loaded into the system.
Default Value: %Datetime
|
| 5 |
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
|
| 6 |
OPRID |
Character(30) |
VARCHAR2(30) NOT NULL |
A user's ID (see PSOPRDEFN).
Prompt Table:
OPRID_VW
|
| 7 |
ASOFDATE |
Date(10) |
DATE |
As of Date
Default Value: %date
|
| 8 |
ASOFTIME |
Time(15) |
TIMESTAMP |
As of Time
Default Value: %Time
|
| 9 |
RECEIVER |
Character(20) |
VARCHAR2(20) NOT NULL |
Receiver is used in bank reconciliation
|
| 10 |
SENDER |
Character(20) |
VARCHAR2(20) NOT NULL |
Sender will be used in bank statements
|
| 11 |
BTB_STATUS |
Character(1) |
VARCHAR2(1) NOT NULL |
Book to Bank ready flag.
N=No
Y=Yes
Y/N Table Edit
Default Value: N
|
| 12 |
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
|
| 13 |
AR_LOADED_SW |
Character(1) |
VARCHAR2(1) NOT NULL |
Loaded to A/R
Y/N Table Edit
Default Value: N
|
| 14 |
CURRENCY_CD |
Character(3) |
VARCHAR2(3) NOT NULL |
Currency Code
|
| 15 |
BNK_STMT_TYPE |
Character(1) |
VARCHAR2(1) NOT NULL |
Bank statement type
1=Current Day
2=Previous Day
3=Statement Analysis
|
| 16 |
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.
|
| 17 |
FILE_CREATE_DT |
Date(10) |
DATE |
File Creation Date
|
| 18 |
FILE_ID |
Character(30) |
VARCHAR2(30) NOT NULL |
File Identifier
|