eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

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

TABLE: AP.AP_PREPAY_HISTORY_ALL

Object Details

Object Name:	AP_PREPAY_HISTORY_ALL
Object Type:	TABLE
Owner:	AP
FND Design Data:	SQLAP.AP_PREPAY_HISTORY_ALL
Subobject Name:
Status:	VALID

AP_PREPAY_HISTORY_ALL countains the history of a prepayment which includes its related prepayment applications, prepayment unapplications and prepayment application adjustments. A row is created in APPH when the Prepayment Applied, Prepayment Unapplied or Prepayment Adjusted accounting events are captured.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
AP_PREPAY_HISTORY_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	PREPAY_HISTORY_ID
AP_PREPAY_HISTORY_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	ACCOUNTING_EVENT_ID
AP_PREPAY_HISTORY_N2	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	BC_EVENT_ID

Columns

Name	Datatype	Length	Mandatory	Comments
PREPAY_HISTORY_ID	NUMBER	(15)	Yes	Prepayment History Unique Identifier
PREPAY_INVOICE_ID	NUMBER	(15)	Yes	Unique Identifier of the Prepayment
PREPAY_LINE_NUM	NUMBER	(15)	Yes	Line number on the Prepayment
ACCOUNTING_EVENT_ID	NUMBER	(15)		Unique Identifier for the accounting event of the prepayment application, unapplication or adjustment
HISTORICAL_FLAG	VARCHAR2	(1)		Flag indicates if upgrade created record
INVOICE_ID	NUMBER	(15)	Yes	Unique Identifier of the recipient Invoice
INVOICE_ADJUSTMENT_EVENT_ID	NUMBER	(15)		Related adjusted invoice event that resulted in a cascade event
ORG_ID	NUMBER	(15)		Operating Unit unique identifier
POSTED_FLAG	VARCHAR2	(1)		Flag indicates whether the prepayment application, prepayment unapplication, or prepayment adjustment was successfully accounted or not
RELATED_PREPAY_APP_EVENT_ID	NUMBER	(15)		For cascade events, related prepayment application event
TRANSACTION_TYPE	VARCHAR2	(30)	Yes	Accounting transaction event type. Values can be Prepayment Application, Prepayment Unapplication, or Prepayment Adjustment
LAST_UPDATED_BY	NUMBER	(15)	Yes	Standar Who Column
LAST_UPDATE_DATE	DATE		Yes	Standard Who Column
LAST_UPDATE_LOGIN	NUMBER	(15)		Standard Who Column
CREATED_BY	NUMBER	(15)	Yes	Standard Who Column
CREATION_DATE	DATE		Yes	Standard Who Column
PROGRAM_APPLICATION_ID	NUMBER	(15)		Enhanced Who Column
PROGRAM_ID	NUMBER	(15)		Enhanced Who Column
PROGRAM_UPDATE_DATE	DATE			Enhanced Who Column
REQUEST_ID	NUMBER	(15)		Enhanced Who Column
INVOICE_LINE_NUMBER	NUMBER			Line number of the recepient invoice
ACCOUNTING_DATE	DATE			Accounting Date
BC_EVENT_ID	NUMBER	(15)		Identifier of Accounting Event raised for Encumbrance accounting
GAIN_LOSS_INDICATOR	VARCHAR2	(1)		Indicates whether the payment related transaction resulted in gain or loss (G or L)

Query Text

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


SELECT PREPAY_HISTORY_ID
,      PREPAY_INVOICE_ID
,      PREPAY_LINE_NUM
,      ACCOUNTING_EVENT_ID
,      HISTORICAL_FLAG
,      INVOICE_ID
,      INVOICE_ADJUSTMENT_EVENT_ID
,      ORG_ID
,      POSTED_FLAG
,      RELATED_PREPAY_APP_EVENT_ID
,      TRANSACTION_TYPE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      CREATED_BY
,      CREATION_DATE
,      PROGRAM_APPLICATION_ID
,      PROGRAM_ID
,      PROGRAM_UPDATE_DATE
,      REQUEST_ID
,      INVOICE_LINE_NUMBER
,      ACCOUNTING_DATE
,      BC_EVENT_ID
,      GAIN_LOSS_INDICATOR
FROM AP.AP_PREPAY_HISTORY_ALL;

Dependencies

[top of page]

AP.AP_PREPAY_HISTORY_ALL does not reference any database object

AP.AP_PREPAY_HISTORY_ALL is referenced by following:

APPS: AP_PREPAY_HISTORY; AP_PREPAY_HISTORY_ALL