Question:
We perform delta-loads twice a day for the datasource 0FI_GL_4; one at
4AM and 1 at 6PM. However, only during the first delta-load are records
fetched and transferred from R/3 to BW. The second delta-load during
the day always gives as result 0 records.
Is it so that accounting documents are loaded using datasource 0FI_GL_4
only after the posting date completely is finished?
E.g.: We have an accounting document created at 3:50 AM on day X. We
have delta-loads scheduled at 4 AM and 6 PM that day, but none of these
delta-loads reads that accounting document, only at 4:00 AM day X+1 the
accounting document is loaded to BW.
Is it really so that day X must be finished before the accounting
documents on that day are extracted and sent to BW? Or is something
else causing this delay in loading to BW?
We must have the accounting data loaded in each delta load.
If anyone can help with this very critical problem, I would very much appreciate it.
Thanks,
Chris
Answer:
I might be wrong, but I think the delta management is based on the change date in documents,
so your assumption is right, the day must be closed before being able to upload the data for that particular day,
the extractor always load data for day -1.
Ch
Answer:
I might be wrong, but I think the delta management is based on the change date in documents,
so your assumption is right, the day must be closed before being able to upload the data for that particular day,
the extractor always load data for day -1.
Ch
Assuming this is the way it works, do you know if there is any way to configure SAP to force the accounting data to be loaded before day+1?
We are a worldwide company and our users absolutely will not accept having to wait a day to get revenue data.
Thanks for your help!
Answer:
hi ,
----------Just follow this note and i hope this will make things clear"---------
485958
Symptom
The FI line item delta DataSources can identify new and changed data only to the day because the source tables only contain the CPU date and not the time as time characteristic for the change.
This results in a safety interval of at least one day.
This can cause problems if the batch processing of the period-end closing is still running on the day following the period-end closing and all data of the closed period is to be extracted into BW on this day.
Example:
The fiscal year of the company ends on December 31, 2002.
On January 01, 2003, all data of the closed fiscal year is to be extracted into BW.In this case, the FI line item delta DataSources only extract the data with a safety interval of at least one day.
This is the data that was posted with a CPU date up to December 31, 2002.
However, the batch programs for closing the 2002 fiscal year are still running on January 01, 2003.
The postings created by these programs with a January 01 date for the 2002 fiscal year can therefore only be extracted with delta extraction on January 02, 2003. However, extraction should already be possible on January 01, 2003.
Additional key words
FI line item delta DataSources
0FI_AP_4; 0FI_AR_4; 0FI_GL_4
Cause and preconditions
This problem is caused by the program design.
Solution
The functions are enhanced as of PI 2002.1, standard version.
Due to a customized setting, it is now possible for the FI line item extractors to read the data up to the current date during the delta runs.
During the next delta run, the data is then read again from the day when the previous extraction was called, up to the current day of the call for the new extraction.This means that the delta extraction of the data always occurs with time intervals overlapping by one day.
The delta calculation by the ODS objects ensures that the repeatedly extracted data does not cause duplicate values in the InfoCube.
Activate the new functions as follows:
1. PI 2001.1 or PI 2001.2:
Implement the new functions with the correction instructions in this note.As of PI 2002.1, these changes are already implemented in the standard version.
1. Start a test run for an FI line item DataSource via transaction RSA3.
2. Two new parameters are now available in the BWOM_SETTINGS table.
3. Parameter BWFIOVERLA (Default _)
Set this parameter to "X" using transaction SE16, to activate the new function of overlapping time intervals.
Caution
The new function also uses a safety interval of one day to determine the To value of the selection, if the time limit set by BWFITIMBOR is not reached.This means that only data up to the day before the extraction was called is selected, if the extraction starts before 02:00:00 (default for BWFITIMBOR).
Correction: Parameter BWFITIMBOR (Format HH:MM:SS, default 020000)
The default value for this parameter is 02:00:00.Do not change this value.
If this time limit is not reached, only data up to the previous day (with BWFIOVERLA = 'X') or the day before this day (with BWFIOVERLA = ' ') is selected.
This logic prevents records with a CPU date of the previous day being contained in the posting when the extraction is executed.
Regards
_________________
Mrutyunjay