cancel
Showing results for 
Search instead for 
Did you mean: 

0fi_GL_4 data loading problem

Former Member
0 Kudos

Hi experts,

We have standard data source 0FI_GL_4 and DSO 0FIGL_O02,which is created in 3.x flow .

It loads daily delta.

Now we are missing few records from while exracting.

I want to know why tose records are missig and fix it.

Can any one help me on this.

I know FI data sources works on TIMESTAMP basis.But i would like to know which table will maintain this TIMESTAMP fields

either BSEG or BKPF or any other table...

when i go RSA3 and execute full laod ,it is extracting these records.

As per R/3 infomation these records are posted on 16.04.2011.

Can any one help me......

Regards

Laxman

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi....

Whwnever you will do a Init for the first time and for all the subsequent delta load an entry will get recorded in the table BWOM2_TIMEST......In this table Time Stamp field is there.....

For New records :

Depending on this timestamp data will get loaded from BSEG and BKPF on the basis of the field CPUDT (Created on date)........

It means suppose a document created on 4/07/2011........then the system will check the Time stamp in the table BWOM2_TIMEST....If 4/07/2011> the Timestamp...then this record will get fetched in the next delta........

For Changed records :

Mechanism is a bit different.....The Changed on date (AEDAT) field in the table BKPF....doesn't records the changes like.....suppose an FI document get cleared.......it will not get recorded in in AEDAT......

So for Changed records data get fetched from the table BWFI_AEDAT.........based on the TIMESTAMP field......In that case also the timestamp will get compared with BWOM2_TIMEST as explained above......

Regards,

Debjani..

Former Member
0 Kudos

Hi,

As per my knowledge G/L are coming in BSEG if you have DSO check the data in whcich perioed has been missed .and load the same to DSO and do selective deletion in infocube and load same perioed from DSO to Infocube .Hope your issue may solve.

Regards

sivaraju

Former Member
0 Kudos

Hi sivaraju,

Thanks for response.

Do you mean to do a full load with selection?

It effects my delta load. am i correct?

Former Member
0 Kudos

Hi,

qs1,Do you mean to do a full load with selection?

ans: absolutely correct and i think you aware that try to do full load +repair

qs2,it effects my delta load. am i correct?

ans: absolutely it wont effect your delta.

As per safe side do in dev system if it is prdouction in huge data.

Regards

sivaraju

Former Member
0 Kudos

Hi....

It may happen that a document was posted but not saved so it will not get fetched in the next delta run though as per the timestamp it should get fetched.....

It is really tough to recognize those records.......

Have you maintained safety lower limits ?

As a workaround you have to do a Full repair....not a Full load....since you are in BW3.5...........it doesn't support Full and delta in parallel in the ODS.....

But to fix the issue permanently check the safety limits..

Regards,

Debjani....

Former Member
0 Kudos

hi debjani,

Thanks for your response.

But As per my knowledge we do not maintain any safety interval..for FI and that data source is a standard data source.

If yes that we maintain can you please where we do maintain these settings.

Some more information:

I found the documents which are missing ,but those all are Reversal documents....

Former Member
0 Kudos

Hi,

We maintain the settings in BWOM_SETTINGS.......

Parameter : BWFILOWLIM (Lower Limit) and BWFISAFETY (Upper Limit)....

I think these two are already maintained........against OLTPSOURCE = <space>......it indicates that it is applicable for all FI and CO datasources.......

Please check.....if you want you can change the value there.....

Usually, for standard datasource data should not get missed out due to the timestamp......but it can happen.....

Please also check the log for the delta loads .....if there are some delta load failue.....after which repeat delta is not done..........also check the selective deletion log.........if someone has done any selective deletion........

Regards,

Debjani.....