[Home] [Help]
[Dependency Information]
Object Name: | IBY_IRF_PMT_HIST_RANGE |
---|---|
Object Type: | TABLE |
Owner: | IBY |
FND Design Data: | ![]() |
Subobject Name: | |
Status: | VALID |
IBY_IRF_PMT_HIST_RANGE stores the frequency ranges pertaining to the payment history risk factor. The customer can set up multiple frequency ranges for a specific duration. During risk factor evaluation, the merchant can set up risk scores of low, medium, or high for multiple frequency ranges of low range and high range.
Tablespace: | ![]() |
---|---|
PCT Free: | 10 |
PCT Used: |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
PAYMENT_HIST_ID | NUMBER | (15) | Yes | Payment history Identifier |
FREQUENCY_HIGH_RANGE | NUMBER | High limit of purchase frequency | ||
FREQUENCY_LOW_RANGE | NUMBER | Low limit of purchase frequency | ||
SEQ | NUMBER | (15) | Yes | Sequence |
SCORE | VARCHAR2 | (30) | Yes | LOV of ranges of possible risk scores |
LAST_UPDATE_DATE | DATE | Yes | Standard Who column | |
OBJECT_VERSION_NUMBER | NUMBER | Yes | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. | |
LAST_UPDATED_BY | NUMBER | (15) | Yes | Standard Who column |
CREATION_DATE | DATE | Yes | Standard Who column | |
CREATED_BY | NUMBER | (15) | Yes | Standard Who column |
LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
SECURITY_GROUP_ID | NUMBER | Used in hosted environments |
Cut, paste (and edit) the following text to query this object:
SELECT PAYMENT_HIST_ID
, FREQUENCY_HIGH_RANGE
, FREQUENCY_LOW_RANGE
, SEQ
, SCORE
, LAST_UPDATE_DATE
, OBJECT_VERSION_NUMBER
, LAST_UPDATED_BY
, CREATION_DATE
, CREATED_BY
, LAST_UPDATE_LOGIN
, SECURITY_GROUP_ID
FROM IBY.IBY_IRF_PMT_HIST_RANGE;
IBY.IBY_IRF_PMT_HIST_RANGE does not reference any database object
IBY.IBY_IRF_PMT_HIST_RANGE is referenced by following:
|
|
|