Table BWFI_AEDAT empty?

Question

Hi Guru's,
I am loading DS 0FI_AP_4 into our BI7 system.  However, I notice that even after running an init load and then a delta the next day, that the BWFI_AEDAT table is empty.
I perhaps do not understand the purpose of entries in this table?  I thought it was to store all rows already transferred via the delta load (for use in a repeat delta if required) if the corresponding date was still available in the BWOM2_TIMEST table for this DS?  And also for failed rows requested on a prior delta request?
If not, is there any config I need to do to enable entries to get written into this table?  Our BI system is fairly new and perhaps not fully set up, so maybe we still need to do some config settings?...
Thanks!
Darryl

Answer 1

Hi there,
Both 0FI_AP_4 and 0FI_AR_4 need to be run only after running 0FI_GL_4.
Did you run 0FI_GL_4 first?
Check in here:
[http://help.sap.com/saphelp_bw33/helpdata/en/3f/fbf83a0dfa5102e10000000a114084/content.htm]
In particular it says this:
Features of the Extractor
As the strict connectoin of DataSources has been abolished as of PlugIn2002.2, you can now load 0FI_GL_4, 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4 in any order you like. You can also use DataSources 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4 separately without 0FI_GL_4. The DataSources can then be used independently of one another (see note 551044).
Note
As soon as DataSource 0FI_GL_4 has been loaded, it is the leading DataSource with regard to accruals, such as the time and date (CPU date) by which extraction should be carried out.
From the transition of the data requirements in Delta-Init-Modus to Delta operation therefore, the data requirement in Delta mode 0FI_GL_4 should take place first.
Connecting the DataSources in delta operation helps to ensure consistent extraction of FI data. Consistency must be ensured using the Init selection criteria.
Diogo.
Edited by: Diogo Ferreira on May 27, 2009 4:05 PM