DBA Data[Home] [Help] [Dependency Information]

TABLE: IBY.IBY_PMT_CREATION_RULES

Object Details
Object Name: IBY_PMT_CREATION_RULES
Object Type: TABLE
Owner: IBY
FND Design Data: TableIBY.IBY_PMT_CREATION_RULES
Subobject Name:
Status: VALID


IBY_PMT_CREATION_RULES specifies how documents payable are grouped into payments. Creation rules are determined by payment process profiles. This table corresponds to the Payment Creation tab of the Update Payment Process Profile page.


Storage Details
Tablespace: TablespaceAPPS_TS_TX_DATA
PCT Free: 10
PCT Used:
Indexes
Index Type Uniqueness Tablespace Column
IBY_PMT_CREATION_RULES_U1 NORMAL UNIQUE TablespaceAPPS_TS_TX_IDX ColumnSYSTEM_PROFILE_CODE
Columns
Name Datatype Length Mandatory Comments
SYSTEM_PROFILE_CODE VARCHAR2 (100) Yes Unique primary key
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
GROUP_BY_PAYMENT_DETAILS_FLAG VARCHAR2 (1) Yes Y or N flag specifying whether documents payable are grouped by the length of the payment detail record
GROUP_BY_BANK_CHARGE_BEARER VARCHAR2 (1) Yes Y or N flag specifying whether documents payable are grouped by the bank charge bearer
GROUP_BY_DELIVERY_CHANNEL VARCHAR2 (1) Yes Y or N flag specifying whether documents payable are grouped by delivery channel
GROUP_BY_REMITTANCE_MESSAGE VARCHAR2 (1) Yes Y or N flag specifying whether documents payable are grouped by remittance message
GROUP_BY_MAX_DOCUMENTS_FLAG VARCHAR2 (1) Yes Y or N flag specifying whether there is a limit on how many documents can be grouped into a payment
GROUP_BY_UNIQUE_REMIT_ID_FLAG VARCHAR2 (1) Yes Y or N flag specifying whether documents with unique remittance Identifiers are paid alone
GROUP_BY_SETTLE_PRIORITY_FLAG VARCHAR2 (1) Yes Y or N flag specifying whether documents payable are grouped by the settlement priority value
GROUP_BY_PAYMENT_REASON VARCHAR2 (1) Yes Y or N flag specifying whether documents payable are grouped by the payment reason
GROUP_BY_DUE_DATE_FLAG VARCHAR2 (1) Yes Y or N flag specifying whether documents payable are grouped into payments by due date
MAX_DOCUMENTS_PER_PAYMENT NUMBER (15)
Maximum number of documents that can be grouped into a single payment. This value will only be used if GROUP_BY_MAX_DOCUMENTS_FLAG is set to Y.
PAYMENT_DETAILS_LENGTH_LIMIT NUMBER (15)
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, invoice numbers. If this length is exceeded, then the payment will be split into multiple payments.
PAYMENT_DETAILS_FORMULA VARCHAR2 (240)
SQL function to be used to concatenate the document attributes into the payment details information
Query Text

Cut, paste (and edit) the following text to query this object:


SELECT SYSTEM_PROFILE_CODE
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      OBJECT_VERSION_NUMBER
,      GROUP_BY_PAYMENT_DETAILS_FLAG
,      GROUP_BY_BANK_CHARGE_BEARER
,      GROUP_BY_DELIVERY_CHANNEL
,      GROUP_BY_REMITTANCE_MESSAGE
,      GROUP_BY_MAX_DOCUMENTS_FLAG
,      GROUP_BY_UNIQUE_REMIT_ID_FLAG
,      GROUP_BY_SETTLE_PRIORITY_FLAG
,      GROUP_BY_PAYMENT_REASON
,      GROUP_BY_DUE_DATE_FLAG
,      MAX_DOCUMENTS_PER_PAYMENT
,      PAYMENT_DETAILS_LENGTH_LIMIT
,      PAYMENT_DETAILS_FORMULA
FROM IBY.IBY_PMT_CREATION_RULES;

Dependencies

[top of page]

IBY.IBY_PMT_CREATION_RULES does not reference any database object

IBY.IBY_PMT_CREATION_RULES is referenced by following:

SchemaAPPS
SynonymIBY_PMT_CREATION_RULES