Last updated on APRIL 28, 2009
Applies to:Oracle Enterprise Performance Foundation - Version: 184.108.40.206
This problem can occur on any platform.
On 220.127.116.11, 11i.FEM.D.1 Rollup #4:
When attempting to use the WebADI FEM_BALANCES spreadsheet loader to load a new dataset to the
same Cal Period/Ledger with existing FEM_BALANCES data, the following error occurs:
Warning for Dataset parameter: Actual data has already been loaded into Dataset Default_Stats for this Ledger and Calendar Period. You should normally load all Actual data for one Ledger and Calendar Period into a single Dataset, or you may have double-counting in the Balances table.
Proceeding to load...
Registering current execution...
Either the loading process could not find any rows in the interface table (FEM_BAL_INTERFACE_T) that match the parameters entered for this execution, or the data slice columns are NULL for all matching rows. It is also possible that the Balances table is not properly registered.
The parameters entered resulted in the following values used for matching:
CAL_PERIOD_END_DATE: 28-FEB-09 00:00:00;
LEDGER_DISPLAY_CODE: AXP Legal Ledger;
The problem is triggered by an incorrect FEM_BAL_INTERFACE_T.LOAD_METHOD_CODE inserted by the WebADI upload. The value should be 'S' for snapshot for new dataset records, but it is inserting an 'I'. However, the External GL Data Loader concurrent request is then subsequently automatically launched by the WebADI upload with the OPPOSITE parameter value as above -- it uses the correct 'S' snapshot load. Since this parameter value does not match the 'I' records in the FEM_BAL_INTERFACE_T table, no records are loaded.
The opposite also occasionally appears where an incorrect FEM_BAL_INTERFACE_T.LOAD_METHOD_CODE = 'S' value is inserted and the External GL Data Loader launches with a concurrent request parameter of 'Incremental'.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms