Define the External Source Transaction View as a view that will access your proprietary application's database to include all open interface transactions that you want to select for cash forecasting and cash positioning.
Alternatively, if your proprietary application system does not support real-time access from an Oracle database, you can create a table for the External Source Transaction View, and use SQL*Loader or another batch mechanism to populate the table with information from the non-Oracle system transactions.
Cash forecasting and Cash positioning share the same Open Interface setup. However, you can only use the Cash Flow Open Interface feature for cash positioning if the External Transaction view includes the BANK_ACCOUNT_ID column. The BANK_ACCOUNT_ID column is optional when you use the Open Interface for cash forecasting.
Column specifications for the External Source Transaction View are outlined in the following table:
| Column Name | Type | Required? | Description/Value |
|---|---|---|---|
| ROW_ID | ROWID | Yes | Row ID |
| TRANSACTION_AMOUNT | NUMBER | Yes | Amount in transaction currency |
| FUNCTIONAL_AMOUNT | NUMBER | Yes | Amount in ledger currency |
| CURRENCY_CODE | VARCHAR2(15) | Yes | Transaction currency code, must be valid currency code defined in FND_CURRENCIES |
| FUNCTIONAL_CURRENCY | VARCHAR2(15) | Yes | ledger currency code, must be valid currency code defined in FND_CURRENCIES |
| CASH_ACTIVITY_DATE | DATE | Yes | Projected cash transaction date, date when the transaction has become or will become a cash transaction (e.g. check date) |
| BANK_ACCOUNT_ID | NUMBER | No | Bank Account ID, must be valid bank account id stored in BANK_ACCOUNT_ID column of AP_BANK_ACCOUNTS_ALL table |
| CRITERIA1...15 | VARCHAR2(150) | No | Selection criteria |
Note: Organization ID is not included as a default criterion. However, if you want to select transactions for a specific organization, you can define it as a common selection criterion for all external source types.
If your environment includes a distributed source transaction type, either you must import remote data to the local database, or you must establish a database link from the local database to the remote database. See: Associate External Forecast Source Types with Views.
Using Remote Databases
If you are planning to use the Cash External Cashflow Open Interface in a distributed database environment, your database administrator must install the necessary Cash Forecasting objects to each of the remote databases with your External Cashflow sources in your APPS account.
These objects are located in the $CE_TOP/sql directory:
CE_FORECAST_EXT_TEMP (table) - cefextmp.sql (physical file)
CE_FORECAST_EXT_TEMP_N1 (index) - cefextmp.sql (physical file)
These objects are located in the $CE_TOP/admin/sql directory:
CE_FORECAST_REMOTE_SOURCES (package) - cefremts.pls and cefremtb.pls (physical files)
If any of the above objects are patched for Release 11, the patched objects will be located in $CE_TOP/patch/110/sql. Therefore, apply the objects from the $CE_TOP/patch/110/sql directory instead of from the $CE_TOP/admin/sql and $CE_TOP/sql directories.
Use of Indexes on Views
To maximize performance when generating cash forecasts and cash positions that collect data using the External Cashflow Open Interface, we recommend that you create appropriate indexes on the tables accessed by the views you create. The columns that are frequently used as selection criteria, such as cash activity date, should be defined as indexes.
Associate External Forecast Source Types With Views
You need to associate your external source types with an external source transaction view, and if that view is on a remote database, then you need to specify the database link as well.
To associate external forecast source types and views:
Navigate to the External Forecast Sources window.
Choose an external forecast source Type. The list of values is the context field of the Forecast Selection Criteria Descriptive Flexfield.
Enter an external forecast source View. This field is not validated until you submit a forecast that uses the associated external forecast source type.
Optionally, enter a Database Link Name, if the source type is on a remote database. The list of values includes currently available links, but you can enter others as this field is not validated until you submit a forecast that uses the associated external forecast source type.
No comments:
Post a Comment