Previous	Next		Contents	Index	Navigation	Glossary	Library

• Locking function: a routine to lock transactions in your proprietary application's database before reconciliation in Cash Management. You might want to lock transactions so that users cannot change the amounts while the reconciliation process is taking place.

• Clearing procedure: procedural logic to clear transactions in your proprietary application's database. You need to implement this routine to generate reconciliation accounting entries or update data in your proprietary application.

• Unclearing procedure: procedural logic to unclear transactions in your proprietary application's database. You need to implement this routine to generate reconciliation accounting entries or update data in your proprietary application.

Additional Information: Cash Management does not generate accounting entries when reconciling open interface transactions. Therefore, to meet your specific needs you may want to enhance the above described functionality of the CE_999_PKG function and procedures. For example, you can use the information passed to the clearing procedure to create journal entries for the differences between recorded and cleared transaction amounts.

Cash Management provides an empty version of CE_999_PKG in your Oracle database. You must modify this package and write the above described routines if you want to use the locking, clearing, and unclearing functionality from Cash Management. The remainder of this section describes information you will need before you can write the function and procedures.

Additional Information: CE_999_PKG is called by Cash Management after each transaction is processed, rather than in batch mode. Accordingly, your function and procedures should be written to handle transactional processing.

Locking Function

Parameter Name	Data Type	Description
X_CALL_MODE	VARCHAR2	'U' if calling from reconcile. 'M" if calling from unreconcile.
X_TRX_TYPE	VARCHAR2	The transaction type (TRX_TYPE)
X_TRX_ROWID	ROWID	ROWID of the transaction

When you write the function:

• Create CURSOR LOCK_OPEN that selects the open-interface transaction FOR UPDATE NOWAIT. For example:

CURSOR lock_open IS SELECT rowid FROM ap_checks WHERE rowid=X_trx_rowid

• Uncomment (remove the slashes and asterisks from) the code enclosed by /*---- .... ----*/

Clearing Procedure

Parameter Name	Data Type	Column in CE_999_INTERFACE_V
X_TRX_ID	NUMBER	TRX_ID
X_TRX_TYPE	VARCHAR2	TRX_TYPE (value is PAYMENT or CASH)
X_STATUS	VARCHAR2	STATUS
X_TRX_NUMBER	VARCHAR2	TRX_NUMBER
X_TRX_DATE	DATE	TRX_DATE
X_TRX_CURRENCY	VARCHAR2	CURRENCY_CODE
X_GL_DATE	DATE	GL_DATE
X_BANK_CURRENCY	VARCHAR2	AP_BANK_ACCOUNTS.BANK_CURRENCY_CODE
X_CLEARED_AMOUNT	NUMBER	CLEARED_AMOUNT
X_CHARGES_AMOUNT	NUMBER	CHARGES_AMOUNT
X_ERRORS_AMOUNT	NUMBER	ERROR_AMOUNT
X_EXCHANGE_DATE	DATE	EXCHANGE_RATE_DATE
X_EXCHANGE_TYPE	VARCHAR2	EXCHANGE_RATE_TYPE
X_EXCHANGE_RATE	NUMBER	EXCHANGE_RATE

Use the passed parameters to code the procedural logic needed to clear transactions in your proprietary application's database. You need to implement this routine if you want to generate reconciliation accounting entries or update data in the open interface transactions source application.

Unclearing Procedure

Parameter Name	Data Type	Column in CE_999_INTERFACE_V
X_TRX_ID	NUMBER	TRX_ID
X_TRX_TYPE	VARCHAR2	TRX_TYPE
X_STATUS	VARCHAR2	STATUS
X_TRX_DATE	DATE	TRX_DATE
X_GL_DATE	DATE	GL_DATE

Use the passed parameters to code the procedural logic needed to unclear transactions in your proprietary application's database. You need to implement this routine if you want to generate reconciliation accounting entries or update data in the open interface transactions source application.

See Also

CE_999_INTERFACE_V Description