On Test environment:
Prerequisites to Using the Reconciliation Open Interface
- Check the Use Reconciliation Open Interface check box in the System Parameters window. Setting Up 2 – 35
- Define Open Interface Float Status and Open Interface Cleared Status in system parameters.
- Customize the Reconciliation Open Interface package and view. The Reconciliation Open Interface objects include the following view and package, which you would have customized to work in your environment:
- CE_999_INTERFACE_V (view) – cev999in.sql (physical file)
- CE_999_PKG (package) – ceab999s.pls (physical file) – ceab999b.pls (physical file)
To enable the Use Reconciliation Open Interface checkbox:
- Choose Cash Management Superuser responsibility
- From the Navigator, choose Setup > System > System Parameters
- Check the Use Reconciliation Open Interface checkbox
- Click the Open Interface tab. Under Open Interface Status Code, enter into the following fields:
- Float Status: Negotiable
- Clear Status: Reconciled
Most likely, the CE_999_INTERFACE_V view already exists within the system. However, the CE_999_INTERFACE table does NOT exist. It must be created as follows:
CREATE TABLE CE.CE_999_INTERFACE AS SELECT * FROM APPS.CE_999_INTERFACE_V;
CREATE VIEW CE.CE_999_INTERFACE_V AS SELECT * FROM CE.CE_999_INTERFACE;
CREATE SYNONYM APPS.CE_999_INTERFACE FOR CE.CE_999_INTERFACE;
CREATE SYNONYM APPS.CE_999_INTERFACE_V FOR CE.CE_999_INTERFACE_V;
Then grant privileges on the table CE_999_INTERFACE:
Grant select, insert, update, delete, index, references, alter on CE_999_INTERFACE to public;
col grantee format a8
col grantor format a8
select * from dba_tab_privs
where table_name = 'CE_999_INTERFACE';
You may be required to rename OR delete the view in APPS with the same name:
RENAME CE_999_INTERFACE_V TO CE_999_INTERFACE_VS;
DROP VIEW APPS.CE_999_INTERFACE_V;
To validate views with status ‘INVALID’:
ALTER VIEW CE_999_RECONCILED_V COMPILE;
ALTER VIEW CE_999_REVERSAL_V COMPILE;
In order to recreate the original view APPS.CE_999_INTERFACE_V, see the file $CE_TOP/admin/odf/cevw.odf. You may be required to reconstruct the SQL code from that given in this file.
The CE_999_INTERFACE table seems to have been deleted. The script that was used to create the table must be rerun. To find this table, check the Stage11510 folder to locate the file:
mkdir ~/ce
for i in `find /emcb/Stage11510/oraApps/ -iname 'ce*'`; do cp $i ~/ce/; done
- Cash Management Superuser
- View > Available Transactions
- Bank Statements > Manual Clearing > Clearing Transactions
- In the Find Transactions form, choose an Account Number for Recurrent Account (1429625Rec).
On Production:
- Cash Management Manager
- View > Available Transactions
- Bank Statements > Manual Clearing > Clear Transactions
The CE_999_INTERFACE_V view should already have been created in the database when the database was set up.
To see the contents of the DBA_OBJECTS view:
Col owner format a6
Col object_name format a30
SELECT
OWNER,
OBJECT_NAME,
OBJECT_TYPE,
CREATED,
STATUS
FROM
DBA_OBJECTS
WHERE
OBJECT_NAME LIKE ‘CE_999%’
;
To see the contents of the DBA_SYNONYMS view:
SET LINESIZE 150
SELECT
OWNER,
SYNONYM_NAME,
TABLE_OWNER,
TABLE_NAME
FROM
DBA_SYNONYMS
WHERE
SYNONYM_NAME LIKE ‘CE_999%’
;
To see the contents of the DBA_VIEWS view:
SET LONG 800
SET LINESIZE 800
SET LONGCHUNKSIZE 800
SET WRAP OFF
SELECT
OWNER,
VIEW_NAME,
TEXT
FROM
DBA_VIEWS
WHERE
VIEW_NAME = ‘CE_999_INTERFACE_V’
;
To troubleshoot any problems viewing data in the application, the CE_999_TRANSACTIONS_V view must be analyzed. Specifically, the WHERE clause must be examined to determine if all criteria are met.
One of the views in the FROM clause is the AP_BANK_ACCOUNTS. The AP_BANK_ACCOUNTS view needs the CLIENT_INFO variable set in SQL*Plus to view the data in this view. To view the value of this variable, enter:
SELECT USERENV (‘CLIENT_INFO’) FROM DUAL;
OR
SELECT SYS_CONTEXT ('USERENV', 'CLIENT_INFO') FROM DUAL;
To set this parameter, use the DBMS_APPLICATION_INFO package:
EXEC DBMS_APPLICATION_INFO.SET_CLIENT_INFO (‘102’);
By removing all lines from the WHERE clause of then gradually adding them back one at a time in a SQL query, it was determined where the problem occurred. The last line of the WHERE clause was with the Transaction Date and only when this line was added was no rows returned.
Recent Comments