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: XTR.XTR_LIMIT_EXCESS_LOG

Object Details

Object Name:	XTR_LIMIT_EXCESS_LOG
Object Type:	TABLE
Owner:	XTR
FND Design Data:	XTR.XTR_LIMIT_EXCESS_LOG
Subobject Name:
Status:	VALID

XTR_LIMIT_EXCESS_LOG contains the limit exception information for deal transactions. Each row contains a limit exception and all the information relevant to that exception, such as company, limit party, dealer, excess amount, date, and deal number. The LOG_ID column groups the set of limit exceptions that are generated for each transaction. The deal and transaction numbers in this table are used to find all of the limit exceptions that were generated for a specific deal transaction.
This table corresponds to the Limit Utilizations window.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
XTR_LIMIT_EXCESS_LOG_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	LOG_ID
XTR_LIMIT_EXCESS_LOG_N2	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	EXCEEDED_ON_DATE

Columns

Name	Datatype	Length	Mandatory	Comments
AMOUNT_DATE	DATE			Date that the deal finishes and is paid off. Date on which the principal amount of a note, draft, acceptance, bond, short term or other debt instrument becomes due and payable.
AUTHORISED_BY	VARCHAR2	(10)		Treasury user who authorized the limit exceptions
COMPANY_CODE	VARCHAR2	(7)		Company code
DEALER_CODE	VARCHAR2	(10)		Code for Treasury users
DEAL_NUMBER	NUMBER		Yes	Unique number assigned to each deal
DUAL_AUTHORISED_BY	VARCHAR2	(10)		Not currently used
DUAL_AUTHORISED_ON	DATE			Not currently used
EXCEEDED_BY_AMOUNT	NUMBER			Amount that a transaction exceeded the limit
EXCEEDED_ON_DATE	DATE		Yes	Date on which the limit exception occurred
EXCEPTION_TYPE	VARCHAR2	(8)	Yes	Type of limit exception (WARNING, EXCEEDED, or NO_LIMIT)
HCE_AMOUNT	NUMBER		Yes	Exceeded amount in reporting currency equivalent
LIMITING_AMOUNT	NUMBER			Maximum amount allowed by the limit
LIMIT_CHECK_TYPE	VARCHAR2	(8)	Yes	Type of limit that exceeded (for example, company, counterparty, currency, and dealer)
LIMIT_CODE	VARCHAR2	(7)		Code for user-defined limits imposed on deals and transactions
LIMIT_PARTY	VARCHAR2	(7)		Party against which limits are checked
LOG_ID	NUMBER		Yes	Limit exception log batch identifier
TRANSACTION_NUMBER	NUMBER			Unique reference number assigned to a transaction
CURRENCY	VARCHAR2	(15)		Currency code for currency limits

Query Text

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


SELECT AMOUNT_DATE
,      AUTHORISED_BY
,      COMPANY_CODE
,      DEALER_CODE
,      DEAL_NUMBER
,      DUAL_AUTHORISED_BY
,      DUAL_AUTHORISED_ON
,      EXCEEDED_BY_AMOUNT
,      EXCEEDED_ON_DATE
,      EXCEPTION_TYPE
,      HCE_AMOUNT
,      LIMITING_AMOUNT
,      LIMIT_CHECK_TYPE
,      LIMIT_CODE
,      LIMIT_PARTY
,      LOG_ID
,      TRANSACTION_NUMBER
,      CURRENCY
FROM XTR.XTR_LIMIT_EXCESS_LOG;

Dependencies

[top of page]

XTR.XTR_LIMIT_EXCESS_LOG does not reference any database object

XTR.XTR_LIMIT_EXCESS_LOG is referenced by following:

XTR: XTR_LIMIT_EXCESS_LOG#