Preparing to Use the Forecasting Open Interface
To use the Forecasting Open Interface effectively, you need to perform these steps in the following sequence. Each step has substeps that are explained in the referenced section.
Define External Source Types and Selection Criteria
1. Determine the external source types that you want to include in your cash forecasts.
2. Determine appropriate selection criteria for each type.
3. Identify the selection criteria common to all external source types.
4. Identify the selection criteria appropriate only for specific external source types.
5. Design the use of criteria segments.
Use the Descriptive Flexfields worksheets located in the appendix of the Oracle Applications Flexfields Guide to help you with your design.
See Also
Planning Your Descriptive Flexfields (Oracle Applications Flexfields Guide)
Defining Descriptive Flexfield Structures (Oracle Applications Flexfields Guide)
Descriptive Flexfield Segments Window (Oracle Applications Flexfields Guide)
Context Field Values (Oracle Applications Flexfields Guide)
Define Value Sets for Selection Criteria
You need to define value sets that determine the values users can enter for selection criteria for open interface inflow and outflow source types when defining forecast templates.
1. Navigate to the Value Sets window (Descriptive Flexfield Segments window > Segments button > Value Sets button).
2. Define your value set and give it a validation type, and enter the appropriate validation information to suit your selection criteria.
See Also
Defining Value Sets (Oracle Applications Flexfields Guide)
Define Forecast Selection Criteria Descriptive Flexfield Segments
1. Navigate to the Descriptive Flexfield Segments window.
2. Enter Oracle Cash Management in the Application field, and Forecast Selection Criteria in the Title field.
3. Uncheck the Freeze Flexfield Definition check box.
4. Refer to the worksheet you filled out in designing your descriptive flexfield.
- Include the common selection criteria that are applicable to all external source types.
- Specify external source types in the Context Field region.
- For each external source type defined as a context field value, define the criteria segments that are used by the specific external source type as the context-sensitive segments. These are the selection criteria that depend on the external source types.
- All segments must be enabled and non-required.
- Choose the value sets that you predefined in the Value Set field.
- Do not update any existing default entries.
5. Check the Freeze Flexfield Definition check box and save your work.
Define External Source Views
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.
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.
Column specifications for the External Source Transaction View are outlined in the following table:
|
ROW_ID
| ROWID
| Yes
| Row ID
|
TRANSACTION_AMOUNT
| NUMBER
| Yes
| Amount in transaction currency
|
FUNCTIONAL_AMOUNT
| NUMBER
| Yes
| Amount in functional currency
|
CURRENCY_CODE
| VARCHAR2(15)
| Yes
| Transaction currency code, must be valid currency code defined in FND_CURRENCIES
|
FUNCTIONAL_CURRENCY
| VARCHAR2(15)
| Yes
| Functional 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)
|
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 your remote database does not have Oracle Applications installed, your database administrator needs to create one table (CE_FORECAST_EXT_TEMP) and one PL/SQL package (CE_FORECAST_REMOTE_SOURCES) on the remote database, using the following SQL scripts in the $CE_TOP/sql directory:
Use of Indexes on Views
To maximize performance when generating cash forecasts that collect data using the Forecasting 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:
1. Navigate to the External Forecast Sources window.
See Also
Creating Cash Forecast Templates