[Home] [Help] [Dependency Information]
Object Name: | IBY_REMIT_ADVICE_SETUP |
---|---|
Object Type: | TABLE |
Owner: | IBY |
FND Design Data: | IBY.IBY_REMIT_ADVICE_SETUP |
Subobject Name: | |
Status: | VALID |
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 specifes 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 page.
Tablespace: | APPS_TS_TX_DATA |
---|---|
PCT Free: | 10 |
PCT Used: |
Index | Type | Uniqueness | Tablespace | Column |
---|---|---|---|---|
IBY_REMIT_ADVICE_SETUP_U1 | NORMAL | UNIQUE | APPS_TS_TX_IDX |
SYSTEM_PROFILE_CODE
ZD_EDITION_NAME |
IBY_REMIT_ADVICE_SETUP_N1 | NORMAL | NONUNIQUE | APPS_TS_TX_IDX | REMITTANCE_ADVICE_FORMAT_CODE |
Name | Datatype | Length | Mandatory | 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) | Y or N flag indicating whether multiple copies of the remittance advice can be created for a payment instruction | |
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 | NUMBER | (15) | Yes | Standard Who column |
CREATION_DATE | DATE | Yes | Standard Who column | |
LAST_UPDATED_BY | NUMBER | (15) | Yes | Standard Who column |
LAST_UPDATE_DATE | DATE | Yes | Standard Who column | |
LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
OBJECT_VERSION_NUMBER | NUMBER | Yes | Object version number | |
REMITTANCE_ADVICE_FORMAT_CODE | VARCHAR2 | (30) | Remittance format code | |
SRA_OVERRIDE_PAYEE_FLAG | VARCHAR2 | (1) | Yes | 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) | Yes | Y or N flag indicating whether the remittance advice should be submitted automatically at payment completion point. |
ZD_EDITION_NAME | VARCHAR2 | (30) | Yes |
Cut, paste (and edit) the following text to query this object:
SELECT SYSTEM_PROFILE_CODE
, DOCUMENT_COUNT_LIMIT
, ALLOW_MULTIPLE_COPY_FLAG
, SEEDED_FLAG
, PAYMENT_DETAILS_LENGTH_LIMIT
, CREATED_BY
, CREATION_DATE
, LAST_UPDATED_BY
, LAST_UPDATE_DATE
, LAST_UPDATE_LOGIN
, OBJECT_VERSION_NUMBER
, REMITTANCE_ADVICE_FORMAT_CODE
, SRA_OVERRIDE_PAYEE_FLAG
, REMIT_ADVICE_DELIVERY_METHOD
, AUTOMATIC_SRA_SUBMIT_FLAG
, ZD_EDITION_NAME
FROM IBY.IBY_REMIT_ADVICE_SETUP;
IBY.IBY_REMIT_ADVICE_SETUP does not reference any database object
IBY.IBY_REMIT_ADVICE_SETUP is referenced by following:
|
|
|