IEX_DUN_CONF_DETAILS_
Stores dunning configuration details.
Details
-
Schema: FUSION
-
Object owner: IEX
-
Object type: TABLE
-
Tablespace: REFERENCE
Primary Key
Name | Columns |
---|---|
IEX_DUN_CONF_DETAILS_PK_ |
LAST_UPDATE_DATE, LAST_UPDATED_BY, DUNNING_CONF_DETAIL_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
DUNNING_CONF_DETAIL_ID | NUMBER | 18 | Yes | Primary key. | |
TEMPLATE_NAME | VARCHAR2 | 240 | The template name of the dunning letter. | ||
DUNNING_PLAN_ID | NUMBER | 18 | Foreign key to IEX_DUNNING_PLANS. Which dunning plan this detail belongs to. | ||
XDO_TEMPLATE_ID | NUMBER | 18 | Foreign key to XDO_TEMPLATES. What letter template is used by this plan detail. | ||
AGING_BUCKET_LINE_ID | NUMBER | 18 | Foreign key to AR_AGING_BUCKET_LINES This column is mutually exclusive with column stage_number. Only one will have a value, the other will be null. This represents what aging bucket this dunning detail is used against. If the oldest invoice of a customer falls in this aging bucket then the dunning letter stored here will be sent. | ||
STAGE_NUMBER | NUMBER | 18 | Foreign key to AR_AGING_BUCKET_LINES This column is mutually exclusive with column aging_bucket_line_id. Only one will have a value, the other will be null. This represents the stage of the customer's delinquencies, a stage is kept for every delinquent payment schedule, if the oldest invoice of a custemer is on the stage then the letter template stored here will be sent to the customer. | ||
CALLBACK_FLAG | VARCHAR2 | 10 | Valid values are 'Y' and 'N' and null, null means 'N'. This indicates if a follow up call should be automatically created by the application if the delinquency is not cured after the letter is received. | ||
CALLBACK_DAYS | NUMBER | 3 | Number of days to wait before creating a follow up call for a collector to call a delinquent customer. | ||
CREATED_BY | VARCHAR2 | 64 | Who column: indicates the user who created the row. | ||
CREATION_DATE | TIMESTAMP | Who column: indicates the date and time of the creation of the row. | |||
LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of 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 | 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. | ||
SET_ID | NUMBER | 18 | Identifies a set of reference data shared across business units and other entities. Also known as Reference Data Sets, they are used to filter reference data in transactional UIs. | ||
WAIT_DAYS | NUMBER | Number of days to wait before the system sends the next set of dunning letters. | |||
SEED_DATA_SOURCE | VARCHAR2 | 512 | Source of seed data record. A value of 'BULK_SEED_DATA_SCRIPT' indicates that record was bulk loaded. Otherwise, specifies the name of the seed data file. | ||
AUDIT_ACTION_TYPE_ | VARCHAR2 | 10 | Action Type - have values like INSERT, UPDATE and DELETE. | ||
AUDIT_CHANGE_BIT_MAP_ | VARCHAR2 | 1000 | Used to store a bit map of 1s and 0s for each column in the table. | ||
AUDIT_IMPERSONATOR_ | VARCHAR2 | 64 | Original Impersonator User. |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
IEX_DUN_CONF_DETAILSN1_ | Non Unique | Default | DUNNING_CONF_DETAIL_ID, LAST_UPDATE_DATE |
IEX_DUN_CONF_DETAILS_U1_ | Unique | Default | LAST_UPDATE_DATE, LAST_UPDATED_BY, DUNNING_CONF_DETAIL_ID |