PMT_ACK_FILE_IDC=Complete
E=Error
P=In Process
E=EBICS
F=File
M=Integration Broker
01=Transit Number
02=Swift ID/BIC
03=CHIPS Participant ID
04=Canadian Bank Branch/Institute
05=CHIPS Universal ID
ZZ=Mutually Defined
PMT_ACK_HEADER(SQL Table) |
Index Back |
|---|---|
Payment Ack File InfoPayment Ack File Info |
| # | PeopleSoft Field Name | PeopleSoft Field Type | Database Column Type | Description |
|---|---|---|---|---|
| 1 | PMT_ACK_FILE_ID |
Character(12) | VARCHAR2(12) NOT NULL | Payment file id |
| 2 | ACK_FILE_STATUS | Character(1) | VARCHAR2(1) NOT NULL |
File status
C=Complete E=Error P=In Process |
| 3 | BANK_FILE_ID | Character(36) | VARCHAR2(36) NOT NULL | Bank file id |
| 4 | BANK_SEND_DTTM | DateTime(26) | TIMESTAMP | Send dttm |
| 5 | FORMAT_ID | Character(10) | VARCHAR2(10) NOT NULL | Format ID |
| 6 | OUTPUT_TYPE | Character(1) | VARCHAR2(1) NOT NULL |
Output type
E=EBICS F=File M=Integration Broker |
| 7 | PMT_FILE_PATH | Character(254) | VARCHAR2(254) NOT NULL | Payment file path |
| 8 | FILENAME | Character(80) | VARCHAR2(80) NOT NULL | File Name |
| 9 | CREATE_DTTM | DateTime(26) | TIMESTAMP | Creation Datetime |
| 10 | CREATED_BY_USER | Character(30) | VARCHAR2(30) NOT NULL | Created By |
| 11 | PMT_CRYPTO_ID | Character(30) | VARCHAR2(30) NOT NULL | Payment encrypted ID |
| 12 | PUBNODE | Character(30) | VARCHAR2(30) NOT NULL | Application Messaging Publication Node. This refers to the Node that the Application Message Instance was published from. |
| 13 | MSGNAME | Character(30) | VARCHAR2(30) NOT NULL | Application Message Name. Name of the Application Message Definition. (see PSMSGDEFN). |
| 14 | APMSGVER | Character(30) | VARCHAR2(30) NOT NULL | Message Version |
| 15 | CHNLNAME | Character(30) | VARCHAR2(30) NOT NULL | Channel Name (see PSCHNLDEFN). |
| 16 | PUBID | Signed Number(11,0) | DECIMAL(10) NOT NULL | Publication Identifier |
| 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 | BANK_SETID | Character(5) | VARCHAR2(5) NOT NULL | The PeopleSoft tableset ID associated with a given bank/counterparty. |
| 19 | BANK_CD | Character(5) | VARCHAR2(5) NOT NULL | Bank Code |
| 20 | BANK_ID_QUAL | Character(3) | VARCHAR2(3) NOT NULL | "A bank/counterparty attribute that determines |
| 21 | BNK_ID_NBR | Character(20) | VARCHAR2(20) NOT NULL | A literal alphanumeric attribute that uniquely identifies a given bank or counterparty. |
| 22 | DFI_ID_NUM | Character(12) | VARCHAR2(12) NOT NULL | A banking industry convention identifier utilized to drive electronic settlements processing for a given bank/coun |
| 23 | DFI_ID_QUAL | Character(2) | VARCHAR2(2) NOT NULL |
A banking industry convention identifier utilized to drive data validation for a given bank/counterparty.
01=Transit Number 02=Swift ID/BIC 03=CHIPS Participant ID 04=Canadian Bank Branch/Institute 05=CHIPS Universal ID ZZ=Mutually Defined |