EB_INV_MIS_PYMT(SQL Table) |
Index Back |
---|---|
EB alert context recordEB alert context record for payment missed for invoices |
# | PeopleSoft Field Name | PeopleSoft Field Type | Database Column Type | Description |
---|---|---|---|---|
1 | EOEN_PRCS_NAME | Character(30) | VARCHAR2(30) NOT NULL | EOEN Process Name |
2 | EOEN_CATEGORY | Character(30) | VARCHAR2(30) NOT NULL | EOEN Category |
3 | SEQ_NBR_EOEN | Number(15,0) | DECIMAL(15) NOT NULL | EOEN Sequence Nbr |
4 | EOEN_EMAIL_GROUP | Number(10,0) | DECIMAL(10) NOT NULL | Email group id |
5 | EOEN_NOTIFY_TO | Character(30) | VARCHAR2(30) NOT NULL | Notification receiver |
6 | EMAIL_ADDRESS | Long Character | CLOB | Email Addresses |
7 | QRYNAME | Character(30) | VARCHAR2(30) NOT NULL | Query Name |
8 | BUSINESS_UNIT | Character(5) | VARCHAR2(5) NOT NULL | Business Unit |
9 | EOEN_LAST_DTTIME | DateTime(26) | TIMESTAMP | Last Date Time |
10 | EOEN_EMAIL_SUBJECT | Character(100) | VARCHAR2(100) NOT NULL | EOEN Email subject field |
11 | EOEC_UL_ID | Character(30) | VARCHAR2(30) NOT NULL | Identifies the user list to be used when creating the approval process. |
12 | SETID | Character(5) | VARCHAR2(5) NOT NULL | SetID |
13 | CUST_ID | Character(15) | VARCHAR2(15) NOT NULL | Uniquely identifies an organizational entity that purchases goods or services from the enterprise. Represents the sold-to customer which is the customer organization that places orders. The CUST_ID may or may not be the same as the identifiers for the bill-to and ship-to locations. |
14 | ITEM | Character(30) | VARCHAR2(30) NOT NULL | Uniquely identifies an invoice credit memo or debit memo. The item ID is also called the invoice number. |
15 | ITEM_LINE | Number(6,0) | INTEGER NOT NULL | Item Line |
16 | NAME1 | Character(40) | VARCHAR2(40) NOT NULL | Name 1 |
17 | ACCOUNTING_DT | Date(10) | DATE | The accounting entry construction date for a given transaction (a generic field that crosses multiple |
18 | PYMNT_TERMS_CD | Character(5) | VARCHAR2(5) NOT NULL | Specifies how the payment due date and discount due date are calculated. A payment terms code is associated with various business units bill-to customers vendors as well as sales orders purchase orders and vouchers. |
19 | DUE_DT | Date(10) | DATE | Specifies the date that a transaction is due. It is a generic field used in multiple PeopleSoft applications including Receivables Payables and Purchasing. For example it represents the date that payment is due for a voucher or the date that a scheduled shipment is due to be received. |
20 | DISPUTE_STATUS | Character(3) | VARCHAR2(3) NOT NULL | Specifies the reason that an item or customer is in dispute. For example the dispute status code might represent pricing error. |
21 | BAL_AMT | Signed Number(28,3) | DECIMAL(26,3) NOT NULL | Item Balance |
22 | ITEM_STATUS | Character(1) | VARCHAR2(1) NOT NULL |
Item Status
C=Closed O=Open |
23 | COLLECTION_STATUS | Character(3) | VARCHAR2(3) NOT NULL | Specifies a collection agency or the reason for placing a customer in collection. Collection status indicates that the customer is delinquent in making payments or the invoice is more than 120 days past due. |
24 | ENTRY_TYPE | Character(5) | VARCHAR2(5) NOT NULL | Specifies the type of transaction associated with a pending item. The entry type remains with the item after it is posted and affects many areas of Receivables processing. Some examples of entry types are Invoices Credit Memo Prepayment and Deduction. |
25 | BAL_CURRENCY | Character(3) | VARCHAR2(3) NOT NULL | Currency Code - Bal Amount |
26 | DEDUCTION_STATUS | Character(5) | VARCHAR2(5) NOT NULL |
Deduction Status
C=Closed I=In Process O=Created/Opened W=On Worksheet |
27 | OPRID | Character(30) | VARCHAR2(30) NOT NULL | A user's ID (see PSOPRDEFN). |