IBY_APPLICABLE_PMT_PROFS_
IBY_APPLICABLE_PMT_PROFS maps payment methods to payment process profiles. Since administrators can define both payment methods and payment process profiles, they must also choose which payment process profiles are associated with each payment method. Those choices are stored in this table. The relationship is many-to-many, which means that the same payment process profile may fulfill the requirements of more than one payment method. This table corresponds to the Usage Rules tab of the Update Payment Process Profile page.
Details
-
Schema: FUSION
-
Object owner: IBY
-
Object type: TABLE
-
Tablespace: REFERENCE
Primary Key
| Name | Columns |
|---|---|
|
IBY_APPLICABLE_PMT_PROFS_PK_ |
LAST_UPDATE_DATE, LAST_UPDATED_BY, APPLICABLE_PMT_PROF_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| APPLICABLE_PMT_PROF_ID | NUMBER | 18 | Yes | System-generated primary key. | |
| SYSTEM_PROFILE_CODE | VARCHAR2 | 100 | Unique primary key | ||
| APPLICABLE_TYPE_CODE | VARCHAR2 | 30 | Applicable type. Each type corresponds to one factor in determining the applicability of a payment process profile. Lookup values of IBY_PMT_PROF_USAGE_RULE_TYPES lookup type | ||
| SEEDED_FLAG | VARCHAR2 | 1 | Y or N flag controlling updatability of records. Y indicates record was seeded by Oracle and may have user updates limited. | ||
| APPLICABLE_VALUE_FROM | VARCHAR2 | 240 | From value of the applicability type. Used for the payment amount applicability only | ||
| APPLICABLE_VALUE_TO | VARCHAR2 | 240 | To value of the applicability type | ||
| 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. | ||
| 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 |
|---|---|---|---|
| IBY_APPLICABLE_PMT_PROFSN1_ | Non Unique | Default | APPLICABLE_PMT_PROF_ID, LAST_UPDATE_DATE |
| IBY_APPLICABLE_PMT_PROFS_U1_ | Unique | Default | LAST_UPDATE_DATE, LAST_UPDATED_BY, APPLICABLE_PMT_PROF_ID |