AR_CASH_EXCEPTION_TRENDS_ALL
This table is used to store the exception reasons of applying the transaction manually.
Details
-
Schema: FUSION
-
Object owner: AR
-
Object type: TABLE
-
Tablespace: FUSION_TS_TX_DATA
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| CUSTOMER_ID | NUMBER | 18 | Customer identifier. | ||
| EXCEPTION_CODE | VARCHAR2 | 30 | Reason a receipt was applied manually. | ||
| LAST_OCCURRENCE | DATE | Last time a receipt was applied manually for a customer. | |||
| NUMBER_OF_OCCURRENCE | NUMBER | Number of times a receipt was applied manually for a customer. | |||
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
| CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
| CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
| OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. | |
| BU_ID | NUMBER | 18 | Yes | Business unit identifier. |