Previous	Next		Contents	Index	Navigation	Glossary	Library

Cash Management provides a template of this view in your Oracle database, to allow you to define your view more easily. Note that many elements of this table or view must join to other Oracle Financials reference tables. For example, you need to indicate a particular bank account, which must be defined in AP_BANK_ACCOUNTS.

Alternatively, if your proprietary system does not support real-time access from an Oracle database, you can create a table named CE_999_INTERFACE_V, then use SQL*Loader or another batch mechanism to populate the table with information about your open interface transactions.

Column specifications for CE_999_INTERFACE_V are as follows:

	Column Name	Type	Req.	Cat.	Description/Value
2	ROW_ID	ROWID	Yes	S	Transaction row ID.
4	TRX_ID	NUMBER	Yes	U	Transaction internal identifier (see note 2).
6	BANK_ACCOUNT_ID	NUMBER	Yes	M	AP_BANK_ACCOUNTS.BANK_ACCOUNT_ID.
8	TRX_TYPE	VARCHAR2	Yes	C	Transaction type of PAYMENT or CASH (see note 3).
10	TRX_TYPE_DSP	VARCHAR2	Yes	U	Displayed, translated transaction type.
12	TRX_NUMBER	VARCHAR2	Yes	U	Transaction number (see note 4).
14	TRX_DATE	DATE	Yes	U	Date of the transaction.
16	CURRENCY_CODE	VARCHAR2	Yes	D	Transaction currency code.
18	STATUS	VARCHAR2	Yes	U	Status of the transaction.
20	STATUS_DSP	VARCHAR2	Yes	U	Description of the status.
22	EXCHANGE_RATE_TYPE	VARCHAR2	No	O	NULL or GL_DAILY_CONVERSION_TYPES.CONVERSION_TYPE Required if transaction is foreign.
24	EXCHANGE_RATE_DATE	DATE	No	U	Date of exchange rate. Required if transaction is foreign.
26	EXCHANGE_RATE	NUMBER	No	U	Exchange rate. Required if transaction is foreign.
28	AMOUNT	NUMBER	Yes	U	Transaction amount (transaction currency).
30	CLEARED_AMOUNT	NUMBER	No	U	Cleared transaction amount (transaction currency).
32	CHARGES_AMOUNT	NUMBER	No	U	Transaction bank charges amount (transaction currency).
34	ERROR_AMOUNT	NUMBER	No	U	Transaction error amount (transaction currency).
36	ACCTD_AMOUNT	NUMBER	No	U	Transaction amount (functional currency).
38	ACCTD_CLEARED_AMOUNT	NUMBER	No	U	Transaction cleared amount (functional currency).
40	ACCTD_CHARGES_AMOUNT	NUMBER	No	U	Transaction charges amount (functional currency).
42	ACCTD_ERROR_AMOUNT	NUMBER	No	U	Transaction error amount (functional currency).
44	GL_DATE	DATE	Yes	U	GL date.
46	CREATION_DATE	DATE	Yes	S	Standard Who Column.
48	CREATED_BY	NUMBER	Yes	S	Standard Who Column.
50	LAST_UPDATE_DATE	DATE	Yes	S	Standard Who Column.
52	LAST_UPDATED_BY	NUMBER	Yes	S	Standard Who Column.

Key to Table Abbreviations

	Req.	Required
	Cat.	Category
		C = Constant value
		D = Defined in required tables
		U = User definable
		M = Mandatory join to defined tables
		O = Optional join to defined tables
		S = System Required

Notes:

1. Notes for specific columns:

2. Transaction identifiers (TRX_ID) must be unique within the view. You cannot use duplicate transaction identifiers at any time.

3. Transaction types:

4. Transaction numbers (TRX_NUMBER), used for matching in the automatic reconciliation program, should be:

• For payments, a payment number.

• For receipts, a receipt number.

Note: The transaction number, whether a payment or receipt number, appears throughout Cash Management -- on inquiry windows, reconciliation windows, and reports.

5. Available versus reconciled transactions. Cash Management automatically maintains information for transactions that are reconciled by the Cash Management program. You do not need to implement any logic in CE_999_PKG to track this information. When you reconcile bank statements to open interface transactions, Cash Management compares the transactions in CE_999_INTERFACE_V to the reconciled flags maintained internally by Cash Management. If a match is found, Cash Management knows that the transaction is no longer available for reconciliation.

See Also