[Home] [Help]
[Dependency Information]
Object Name: | IBY_EXTERNAL_PAYEES_ALL |
---|---|
Object Type: | TABLE |
Owner: | IBY |
FND Design Data: | ![]() |
Subobject Name: | |
Status: | VALID |
"This table contains payment details of an external payee automatically created by the source product. For example when supplier or supplier site is created manually system automatically inserts row in to the IBY_EXTERNAL_PAYEES_ALL table.
A party can have multiple payees at following levels -
Party or
Site or
Address or
Address operating unit
This table contains the details of all such payees.
IBY_EXTERNAL_PAYEES_ALL stores payment-related attributes for the funds disbursement payment process for external party payees. "
Tablespace: | ![]() |
---|---|
PCT Free: | 10 |
PCT Used: |
Index | Type | Uniqueness | Tablespace | Column |
---|---|---|---|---|
IBY_EXTERNAL_PAYEES_ALL_U1 | NORMAL | UNIQUE |
![]() |
![]() |
IBY_EXTERNAL_PAYEES_ALL_N1 | NORMAL | NONUNIQUE |
![]() |
![]() |
IBY_EXTERNAL_PAYEES_ALL_N2 | NORMAL | NONUNIQUE |
![]() |
![]() |
IBY_EXTERNAL_PAYEES_ALL_N3 | NORMAL | NONUNIQUE |
![]() |
![]() |
IBY_EXTERNAL_PAYEES_ALL_N4 | NORMAL | NONUNIQUE |
![]() |
![]() |
IBY_EXTERNAL_PAYEES_ALL_N5 | NORMAL | NONUNIQUE |
![]() |
![]() |
IBY_EXTERNAL_PAYEES_ALL_N6 | NORMAL | NONUNIQUE |
![]() |
![]() |
IBY_EXTERNAL_PAYEES_ALL_N7 | NORMAL | NONUNIQUE |
![]() |
![]() |
IBY_EXTERNAL_PAYEES_ALL_N8 | NORMAL | NONUNIQUE |
![]() |
![]() ![]() ![]() ![]() ![]() ![]() |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
EXT_PAYEE_ID | NUMBER | (15) | Yes | Unique internal Identifier for this record. Generated using a database sequence. |
PAYEE_PARTY_ID | NUMBER | (15) | Yes | TCA party Identifier |
PAYMENT_FUNCTION | VARCHAR2 | (30) | Yes | Function or purpose of the payment. Values from the lookup IBY_PAYMENT_FUNCTIONS include SUPPLIER_PAYMENT, CUSTOMER_REFUNDS, and others. |
EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | Yes | Y or N flag indicating whether each document should be paid alone without grouping with any other document payable. |
CREATED_BY | NUMBER | (15) | Yes | Standard who column - unique internal identifier of user who created this row. Foreign key to the USER_ID column of the FND_USER table. |
CREATION_DATE | DATE | Yes | Standard who column - date when this row was created. | |
LAST_UPDATED_BY | NUMBER | (15) | Yes | Standard who column - unique internal identifier user who last updated this row. Foreign key to the USER_ID column of the FND_USER table. |
LAST_UPDATE_DATE | DATE | Yes | Standard Who column - date when a user last updated this row. | |
LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row. Foreign key to the LOGIN_ID column of the FND_LOGINS table. | |
OBJECT_VERSION_NUMBER | NUMBER | Yes | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. This number is incremented for every update to the row through the application. | |
PARTY_SITE_ID | NUMBER | (15) | Party Site identifier Party Site Unique identifier from TCA tables. Validated against HZ_PARTY_SITES.PARTY_SITE_ID. | |
SUPPLIER_SITE_ID | NUMBER | (15) | The supplier site Id for which the payment details are being entered. If the payment details are entered at supplier level, the Party side id is NULL. | |
ORG_ID | NUMBER | (15) | When the payment details are defined for a site, address operating unit, etc., the organization details are updated along with the site id or address operating unit. | |
ORG_TYPE | VARCHAR2 | (30) | Organization type. Values from the lookup IBY_ORGANIZATION_TYPES include Operating Unit, Business Group, and Legal Entity. | |
DEFAULT_PAYMENT_METHOD_CODE | VARCHAR2 | (30) | The default payment method at the time defining the Payee. While creating a Payee, default payment method is updated in both iby_external_payees_all and iby_ext_party_pmt_mthds. Later, the changes are update only in IBY_EXT_PARTY_PMT_MTHDS. | |
ECE_TP_LOCATION_CODE | VARCHAR2 | (60) | Trading partner location code for e-Commerce Gateway | |
BANK_CHARGE_BEARER | VARCHAR2 | (30) | This field indicates the bearer of the bank charges. The bank charge bearer values are defined in the lookup IBY_BANK_CHARGE_BEARER. The possible values are Payer, Payee, Shared, etc. | |
BANK_INSTRUCTION1_CODE | VARCHAR2 | (30) | The instructions to the bank can be selected here. There is a separate setup for defining the bank instruction code. | |
BANK_INSTRUCTION2_CODE | VARCHAR2 | (30) | The instructions to the bank can be selected here. There is a separate setup for defining the bank instruction code. | |
BANK_INSTRUCTION_DETAILS | VARCHAR2 | (255) | It is a free text field that can be included for additional bank instructions. | |
PAYMENT_REASON_CODE | VARCHAR2 | (30) | There is a separate setup for defining the payment reasons. The values mentioned in the payment details of the supplier setup are defaulted on the invoice workbench. | |
PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | The Payment reason comments is a free text field. The value mentioned in the payment details of the supplier setup are defaulted on the invoice workbench. | |
INACTIVE_DATE | DATE | Inactive date | ||
PAYMENT_TEXT_MESSAGE1 | VARCHAR2 | (150) | It is a free text field that can be used payment processing. | |
PAYMENT_TEXT_MESSAGE2 | VARCHAR2 | (150) | It is a free text field that can be used payment processing. | |
PAYMENT_TEXT_MESSAGE3 | VARCHAR2 | (150) | It is a free text field that can be used payment processing. | |
DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | There is a separate setup for defining the Delivery Channel codes. The values mentioned in the payment details of the supplier setup are defaulted on the invoice workbench. | |
PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | Payment format attached under the payment specification tab of the suppliers payments details screen. | |
SETTLEMENT_PRIORITY | VARCHAR2 | (30) | Priority with which the financial institution or payment system settles payments for this payee. The available values for this column come from the FND lookup IBY_SETTLEMENT_PRIORITY. | |
REMIT_ADVICE_DELIVERY_METHOD | VARCHAR2 | (30) | Default delivery method for the Separate remittance advice report. The value can be set at Payee or payee site level also. If the override with Payee delivery option is checked in the Payment process profile, the setting at the payee and payee site level is ignored. Values from the lookup IBY_DELIVERY_METHODS include EMAIL, FAX, and PRINT | |
REMIT_ADVICE_EMAIL | VARCHAR2 | (255) | E-mail address at which the payee wishes to receive remittance advice | |
REMIT_ADVICE_FAX | VARCHAR2 | (100) | Fax number at which the payee wishes to receive remittance advice |
Cut, paste (and edit) the following text to query this object:
SELECT EXT_PAYEE_ID
, PAYEE_PARTY_ID
, PAYMENT_FUNCTION
, EXCLUSIVE_PAYMENT_FLAG
, CREATED_BY
, CREATION_DATE
, LAST_UPDATED_BY
, LAST_UPDATE_DATE
, LAST_UPDATE_LOGIN
, OBJECT_VERSION_NUMBER
, PARTY_SITE_ID
, SUPPLIER_SITE_ID
, ORG_ID
, ORG_TYPE
, DEFAULT_PAYMENT_METHOD_CODE
, ECE_TP_LOCATION_CODE
, BANK_CHARGE_BEARER
, BANK_INSTRUCTION1_CODE
, BANK_INSTRUCTION2_CODE
, BANK_INSTRUCTION_DETAILS
, PAYMENT_REASON_CODE
, PAYMENT_REASON_COMMENTS
, INACTIVE_DATE
, PAYMENT_TEXT_MESSAGE1
, PAYMENT_TEXT_MESSAGE2
, PAYMENT_TEXT_MESSAGE3
, DELIVERY_CHANNEL_CODE
, PAYMENT_FORMAT_CODE
, SETTLEMENT_PRIORITY
, REMIT_ADVICE_DELIVERY_METHOD
, REMIT_ADVICE_EMAIL
, REMIT_ADVICE_FAX
FROM IBY.IBY_EXTERNAL_PAYEES_ALL;
IBY.IBY_EXTERNAL_PAYEES_ALL does not reference any database object
IBY.IBY_EXTERNAL_PAYEES_ALL is referenced by following:
|
|
|