lo extraction - delta failure

Generated by Jive on 2015-09-07+02:001

LO extraction - delta failure

LO extraction - delta failure 13 Nov, 2008 4:14 AMhi

i am uisng LO extraction for 2lis_13_vditm. i am running delta, now my delta is failed?

so i need delete the request. then if i run infopackage automaticcay its will repeat last delta . or i need follow

any settings.

second scenerio:

for this already i am running delta. i am not uisng any process chain.

i want run again full delta

so can follow this steps.

delete all request from cube.

at r/3 system need deltas at RSA7, delete setup tables and initialize setup tables and run full update laster run

v3 job and use as delta.

same scenerio if i alreasy process chain what steps i need to follow

Mihir Kiri 285 posts since 27 May, 2008

Re: LO extraction - delta failure 13 Nov, 2008 4:23 AM

Hi Sunil,

In case of failure of delta you need to do nothing with the setup tables.

Has the request reached PSA successfully. If yes just update PSA data to your data target after deleteing the

failed req. from your data target.

If the req. has not reached PSA, the rsa7 will still have records i.e the delta queue might not have got emptied.

I such a case delete failed req. and just rerun info package with option "Delta".

In case of process chains, you need to follow the same above steps. The changes in process chain will reflect

automatically.

thanks,

Mihir

http://scn.sap.com/people/mihir.kiri2





No new data since the last delta update

Diagnosis

The data request was a delta update, meaning, the data basis in the

source system has not changed since the last update.

System Response

Info IDoc received with status 8.



Hi Sunil,

"

No new data since the last delta update

Diagnosis

The data request was a delta update, meaning, the data basis in the

source system has not changed since the last update.

System Response

Info IDoc received with status 8.

"

For above response, can you see the job overview in source system. Pls let me know status on your job in

source system.

Also let me know the overall status in BI. Is it red or yellow ??

Your second senario...

You need to run full delta. I didnt understood this. Do u want to say you what to re-initialize delta ??

For that you need to take a downtime, load data into setup table (for the extent of history you want), run init

without data transfer, remove downtime and finally do a full load.

Include info package with selection only "delta" in your process chain.

Hope i am clear.

thanks,

mihir


for fist scenerio my status is red





2nd scenerio i am aksing my info package is running delta.

now they asked me again run fullupdate .

so what process i need to follwo now


what abt this scenerio

second scenerio:

for this already i am running delta. i am not uisng any process chain.

i want run again full delta

so can follow this steps.

delete all request from cube.

at r/3 system need deltas at RSA7, delete setup tables and initialize setup tables and run full update laster run

v3 job and use as delta.

Debjani Das 3,296 posts since 24 Oct, 2007


Hi.....

I am not getting u.......why u want to run full delta........Is your delta mechanismis corrupted............becoz if a

delta load fails..........first understand why it failed,,,,,,,,,then u have to delete the request from the target....after

making the QM status forcefully red...........this will set back the init pointer..........then repeat the delta

load..........while repeating system will ask u for repeat delta......becoz when u set back the pointer.......the delta

queue will hold all the failed data + new changed records(if any),,,,,,,,,,

If ur delta mechanism get corrupted then only u hav to do re-init...........

I mean delete init flag.........fill set up table.........init with data transfer or full repair followed by init without data

transfer....then delta..........

Hope this helps....

Regards,

Debjani.......


http://scn.sap.com/people/debjani.das




If ur delta mechanism get corrupted then only u hav to do re-init...........

I mean delete init flag.........fill set up table.........init with data transfer or full repair followed by init without data

transfer....then delta..........

delta is not corruptede any thing like..

they asked need full update again.

delete init flag......... at infopackge schduler (menubar and delete)

fill setup tables again run initialize with data transfer next delta

am i correct



Hi Sunil,

For your 1st senario, doing force red in QM monitor is the right way of doing. This will set back the delta

pointer. I think some one has already suggested above.

For your 2nd senario, I request pls dont just delete ur initialization for sake of doing it.

Whats ur defination of corrupt delta mechanism, arent your deltas getting successfully load or

something ?? If not what error u are getting ??

Thanks,

Mihir

Debjani Das 3,296 posts since 24 Oct, 2007


Hi Suneel......

they asked need full update again......

Look Full update is a different thing........is ur target is a cube?

As per my understanding.........I think that what to load a slection of records to the target........for that first ask

them is there is any selection criteria or not.........if so ........then fill the set up table with that selection........anf

then run full upload........

And if they simply ask u to run full upload........that means they just want to load all the data from r/3

again...........in that case....just fill the set up table.........and run full upload.........

If it is a cube.......then if u run full upload then delta mechanism will be fine........but there may be duplicacy of

records........which may effect ur reports.........







And is it is a DSO........then ur DSO activation will fail........since DSO does'nt support .......full upload and Delta

upload parallely..........in that case u hav to go for full repair.......Full repair and full upload is same...........we just

to full repair for DSO..........to this in the IP scheduler >> Scheduler tab >> Choose Repair full request.........and

check the box.........then ur request will be updated in the target as Full repair........Otherwise after full upload u

have to convert the request to Full repair using the program :RSSM_SET_REPAIR_FULL_FLAG..........

delete init flag......... at infopackge schduler (menubar and delete)

fill setup tables again run initialize with data transfer next delta

am i correct....

Yes u r right.................instead of init with data transfer...........u can also do full repair..followed by init without

data transfer..........

Hope this helps......

Regards,

Debjani.......


hi

i have anothert question here

they asked me full load again, leave abt selection creteria. can i go for setup table concept? or just at info

package full repair will be enough and do 2nd infopackage for delta only?

Swati Phadtare 468 posts since 18 Jul, 2008


Hi

You cant go for full update or full repair without deleting & refilling setup tables..

If u wont refill setup talbes then how will u get complete data from R/3..

You have to first delete setup tables.. refill them.. do full update.. do reinit(without data transfer).. and then set

deltas...

Regards

Swati

Comfortably Numb 150 posts since 24 Sep, 2008


Full Load or Repair Full Load is going to fetch the data from set up table only.

http://scn.sap.com/people/swati.phadtare

http://scn.sap.com/people/swati.phadtare

http://scn.sap.com/people/comfortably.numb

http://scn.sap.com/people/comfortably.numb



So without refilling the setup tables your full load wont end in red. But it will fetch the records from the setup

table that was filled with your last setup table fill run. Hence you will miss out all the changes happened after

your setup table was filled last time.

Thanks.

Ajeet Kumar Singh 3,387 posts since 18 Dec, 2006


Hi,

repeat delta:

Only needed when the load has failed and you still have a chance to recover the failed delta...just repeat the

load either in the process chain or scheduling the infopackage by turning the failed request red and deleting

it...... this will make system to create a new instance and the loads will start from fresh and will bring the last

delta as well as any new records that have got created.

Every delta qeueue in R/3 maintains two entries per record one for the delta and another one for the repeat

delta.

Leave the techincal things to system as it takes care of itself.

This is not depdendent on init and you need not delete the init or do anything with the set up table when

repeating a load.

Set up tables:

Only comes into picture when you want to load the historical load becasue LO data sources cannot have a full

update directly from the tables.Again no effect on exisiting delta and init you can do whenever you want while

filling the set up tables.Should always be done as full repair load to BW so that its not affecting the exiting init

and delta load that comes after that.

You cannot load full load and delta to DSO and it should be either full repair and delta.

When loading historical data.....

do an init without data transfer ..

fill the set up tables....

do full repair first for all the historical data

then schedule the delta to a DSO.

This was for the DSO in overwrite mode.

Hope it explains.

Thanks

Ajeet

http://scn.sap.com/people/ajeet.kumarsingh

http://scn.sap.com/people/ajeet.kumarsingh



Edited by: Ajeet Singh on Nov 13, 2008 6:19 AM


hi

in 3.0 i have ds , i am running delta( without process chain)

now i wnat fill again setup tables get full data?

so intitialize setup tables and run infopakcage will be enough or i need replicate ds again, i as per my know if

chnage any structure only i need to replicate again please let me know



Hi Sunil,

You need not replicate data source. You are right.

Thanks,

Mihir



lo extraction - delta failure

Documents