[Home] [Help] [Dependency Information]
Object Name: | PN_PAYMENT_SCHEDULES_ALL |
---|---|
Object Type: | TABLE |
Owner: | PN |
FND Design Data: | PN.PN_PAYMENT_SCHEDULES_ALL |
Subobject Name: | |
Status: | VALID |
PN_PAYMENT_SCHEDULES_ALL stores rent schedules for both landlord and tenant. The schedules are generated by a concurrent batch process when a lease is finalized or the lease dates are altered by an amendment or an edit. The schedules are created based on the frequency of a payment term in the lease. For example, if the term is for a year and the frequency is monthly, twelve schedules are created, one representing each month.
Schedule date is always assigned to the first day of the month.
This table is partitioned by Org.
Tablespace: | APPS_TS_TX_DATA |
---|---|
PCT Free: | 10 |
PCT Used: |
Index | Type | Uniqueness | Tablespace | Column |
---|---|---|---|---|
PN_PAYMENT_SCHEDULES_U1 | NORMAL | UNIQUE | APPS_TS_TX_IDX | PAYMENT_SCHEDULE_ID |
PN_PAYMENT_SCHEDULES_N1 | NORMAL | NONUNIQUE | APPS_TS_TX_IDX | SCHEDULE_DATE |
PN_PAYMENT_SCHEDULES_N2 | NORMAL | NONUNIQUE | APPS_TS_TX_IDX |
LEASE_ID
LEASE_CHANGE_ID |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
PAYMENT_SCHEDULE_ID | NUMBER | Yes | Uniquely identifies a payment or billing schedule row. The value is populated using sequence PN_PAYMENT_SCHEDULES_S | |
LAST_UPDATE_DATE | DATE | Yes | Standard Who column - date when a user last updated this row. | |
LAST_UPDATED_BY | NUMBER | Yes | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). | |
CREATION_DATE | DATE | Yes | Standard who column - date when this row was created. | |
CREATED_BY | NUMBER | Yes | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). | |
LAST_UPDATE_LOGIN | NUMBER | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). | ||
SCHEDULE_DATE | DATE | Yes | The date on which a payment or a bill is scheduled | |
LEASE_CHANGE_ID | NUMBER | Yes | Associates a lease, amend or edit row in PN_LEASE_CHANGES_ALL with the schedule row | |
LEASE_ID | NUMBER | Yes | Associates the lease row in PN_LEASES_ALL with the schedule row | |
APPROVED_BY_USER_ID | NUMBER | User id of the user who has approved the payment or billing schedule. Associates the row in FND_USER with the schedule row | ||
TRANSFERRED_BY_USER_ID | NUMBER | User id of the user who initiated the transfer of payment or billing schedules to Oracle Payables or Oracle Receivables respectively. Associates the row in FND_USER with the schedule row | ||
PAYMENT_STATUS_LOOKUP_CODE | VARCHAR2 | (30) | Yes | Type of payment status. Valid values: APPROVED - Ready to be exported to Oracle Receivables or Oracle Payables, DRAFT - Not yet approved |
APPROVAL_DATE | DATE | Approval date of a schedule | ||
TRANSFER_DATE | DATE | The date on which the schedule items for this schedule were transferred to Oracle Payables or Oracle Receivables. | ||
PERIOD_NAME | VARCHAR2 | (15) | GL period name. | |
ATTRIBUTE_CATEGORY | VARCHAR2 | (30) | Descriptive flexfield structure definition column. | |
ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ORG_ID | NUMBER | (15) | Organization identifier | |
ON_HOLD | VARCHAR2 | (1) | On-hold field used put a payment schedule on hold. Checked during the Mass Approval. |
Cut, paste (and edit) the following text to query this object:
SELECT PAYMENT_SCHEDULE_ID
, LAST_UPDATE_DATE
, LAST_UPDATED_BY
, CREATION_DATE
, CREATED_BY
, LAST_UPDATE_LOGIN
, SCHEDULE_DATE
, LEASE_CHANGE_ID
, LEASE_ID
, APPROVED_BY_USER_ID
, TRANSFERRED_BY_USER_ID
, PAYMENT_STATUS_LOOKUP_CODE
, APPROVAL_DATE
, TRANSFER_DATE
, PERIOD_NAME
, ATTRIBUTE_CATEGORY
, ATTRIBUTE1
, ATTRIBUTE2
, ATTRIBUTE3
, ATTRIBUTE4
, ATTRIBUTE5
, ATTRIBUTE6
, ATTRIBUTE7
, ATTRIBUTE8
, ATTRIBUTE9
, ATTRIBUTE10
, ATTRIBUTE11
, ATTRIBUTE12
, ATTRIBUTE13
, ATTRIBUTE14
, ATTRIBUTE15
, ORG_ID
, ON_HOLD
FROM PN.PN_PAYMENT_SCHEDULES_ALL;
PN.PN_PAYMENT_SCHEDULES_ALL does not reference any database object
PN.PN_PAYMENT_SCHEDULES_ALL is referenced by following:
|
|
|