cancel
Showing results for 
Search instead for 
Did you mean: 

0FI_GL_4 Safety Delta

Former Member
0 Kudos

Hi all, i'm a newby in this land.

I have a question:

I know that 0FI_GL_4 DataSource has a 1 day safety delta set in upper limit interval. Is it possible to set this safety delta in lower limit in order to not wait one day for new data (duplicate data is not a problem since they are loaded in ODS)?

If it is not possible, anyone knows how it is possible to reduce this too long safety delta?

I promise a lot of rewards point!:p

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Fabio,

This OSS note 485958 (given by Mary Huang) in one of the earlier posts should solve your problem.

Thanks.

Former Member
0 Kudos

Thanks Govind,

i know this note, by now i'm not able to read it (i have no oss note account), i hope tomorrow (or few days) to be able to catch this note and find some useful information.

In the meantime someone could explain of what this note is talking about and if my idea (change safety interval in lower limit) is actualy applicable?.

Thanks so much

Former Member
0 Kudos

Fabio,

OSS 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.

Other terms

FI line item delta DataSources

0FI_AP_4; 0FI_AR_4; 0FI_GL_4

Reason and Prerequisites

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.

-


Hope that helps

Former Member
0 Kudos

It sounds good!

As soon as possible i try to apply the note and check if it 's the right solution to my problem (if it's, you, Govind, will have full points and all my greetings).

...but i'm not sure to have fully understood the "caution" at the end of the note:

Well, I have to leave the default value of BWFITIMBOR to 02:00:00, if i start loading at 6:00 A.M and then at 6:00 P.M, the extractor catches the data up to 6:00 P.M or not?

Many thanks

Former Member
0 Kudos

Ok, the note has solved our problem.

Former Member
0 Kudos

Fabio,

We tend to schedule the extract to happen around 3am so it would load the previous day's data. If there is a need to load more frequently than once a day, there is a work around for it but you need to think about the business reason behind it. We used that note 485958 I posted which Govind quoted before about 3 years ago with BW 3.0 and it works fine.

Hope this helps, Mary

Former Member
0 Kudos

Hi Fabio,

You said this note has solved your problem. I don't understand exactly what your requirement was.

I am trying to do multiple deltas in same day. Would it be possible if I apply this note?

Right now I am in 2.1C but in couple of months my system will be upgraded to 3.5 .

Please clarify me what exactly I have to do in 2.1C and 3.5 to run delta more than once in a day.

Advance Thanks to you...

Hima

Answers (0)