IBY_REMIT_ADVICE_SETUP_
IBY_REMIT_ADVICE_SETUP stores information on creating and delivering remittance information, or remittance advice, for a payee separately from the payment itself. Remittance advice setup is organized by payment process profile. Each payment process profile for which remittance advice is required has a row in this table, which specifies how the remittance advice is to be created and delivered to the payer. This table corresponds to the Separate Remittance Advice region on the Payment Process Profiles pages.
Details
-
Schema: FUSION
-
Object owner: IBY
-
Object type: TABLE
-
Tablespace: REFERENCE
Primary Key
| Name | Columns |
|---|---|
|
IBY_REMIT_ADVICE_SETUP_PK_ |
LAST_UPDATE_DATE, LAST_UPDATED_BY, SYSTEM_PROFILE_CODE |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| SYSTEM_PROFILE_CODE | VARCHAR2 | 100 | Yes | Unique primary key | |
| DOCUMENT_COUNT_LIMIT | NUMBER | This number acts as a rule for inclusion of a payment in a remittance advice. If the number of documents within a payment exceeds this number, then the payment is included in a remittance advice. | |||
| ALLOW_MULTIPLE_COPY_FLAG | VARCHAR2 | 1 | Yes or No flag indicating whether multiple copies of the remittance advice can be created for payments in the payment file. | ||
| 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. | ||
| PAYMENT_DETAILS_LENGTH_LIMIT | NUMBER | Maximum length of the payment detail record. Typically this is a type of description record in a payment format that allows concatenated details of the payment to be included, for example, invoices paid. If the length is exceeded, then the payment is included in a remittance advice. | |||
| 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. | ||
| REMITTANCE_ADVICE_FORMAT_CODE | VARCHAR2 | 30 | Remittance format code | ||
| SRA_OVERRIDE_PAYEE_FLAG | VARCHAR2 | 1 | Y or N flag indicating whether the delivery method preference in the payment process profile overrides the setting at the payee level. Y to override, N otherwise. | ||
| REMIT_ADVICE_DELIVERY_METHOD | VARCHAR2 | 100 | Remittance advice delivery method. Values from the lookup IBY_DELIVERY_METHODS include EMAIL, FAX, and PRINTED. | ||
| AUTOMATIC_SRA_SUBMIT_FLAG | VARCHAR2 | 1 | Y or N flag indicating whether the remittance advice should be submitted automatically at payment completion point. | ||
| 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_REMIT_ADVICE_SETUPN1_ | Non Unique | Default | SYSTEM_PROFILE_CODE, LAST_UPDATE_DATE |
| IBY_REMIT_ADVICE_SETUP_U1_ | Unique | Default | LAST_UPDATE_DATE, LAST_UPDATED_BY, SYSTEM_PROFILE_CODE |