Recovery procedure of data loss from r/3 to BW

During data extraction process some LUW will not transferred to BW from SAP R/3. We need to mannuall process t!ese re"uest to in SAP R/3 so t!at it will transfered to BW. PLease #eep following points w!ile doing t!is. $.%a#e sure ou are !a&ingt t!e data in PSA. '.Delete t!e data from (u)e/*DS 3.%annuall +xecute t!e LUW ,.Reload t!e data from PSA to (u)e. -i +xperts. / am facing an unsual pro)lem related to /n&entor . / !a&e run t!e setup for 'lis0130B2 and 'lis0130B3 at +(( Production side. 4!e delta update mode is Unseriali5ed 63 Update. But t!ere is no "ueue %(+213 )eing created in LBW7 and no delta records are )eing captured in RSA8 too

Ans:----i. c!ec# t!e "ueue in S%7$ and in t9code S%$3 and c!ec# if it s!ows t!ere. :ou will !a&e to an init first for t!e delta records to go to RSA8 and t!en entr will s!ow up. 4!an#s A;eet -i Wit!out /nit Delta <ot possi)le. And LBW7 is t!e Delta 7ue for 63 ;o)s. S%7$/S%$3 s!ould !a&e t!e re"uest. *nce t!e data is replicated on B/ side tr to run Delta t!ru 63 (ollecti&e Run. -ope it !elps

-i. 4!e 7ueues in S%7$ are t!e +xtraction "ueue and t!ese are onl present n case of 7ueued delta and not in 63 Unseriali5er. /n case of 63 unseriali5er. we !a&e update ta)les=6BDA4A> and w!en ou will sc!edule t!e 63 collecti&e ;o) t!e data will )e pic#ed from Update ta)les to RSA8. Also please #eep in mind t!at in case of 63 Unseriali5er. t!e $st le&el target s!ould )e (u)e not DS* )ecause !a&ing DS* can result in inconsistent data.

Questions and answers related to T-Code: RSA7(Delta Queue) This note maintained here for my quick reference and for those dont have SAP Notes access :- ) Question 1: What does the number in the 'Total' column in Transaction RSA7 mean Answer: The 'Total' column dis!la"s the number o# $%Ws that were written in the delta &ueue and that ha'e not "et been con#irmed( The number includes the $%Ws o# the last delta re&uest (#or re!eatin) a delta re&uest) and the $%Ws #or the ne*t delta re&uest( An $%W onl" disa!!ears #rom the RSA7 dis!la" when it has been trans#erred to the +W S"stem and a new delta re&uest has been recei'ed #rom the +W S"stem( Question 2: What is an $%W in the delta &ueue Answer: An $%W #rom the !oint o# 'iew o# the delta &ueue can be an indi'idual document, a )rou! o# documents #rom a collecti'e run or a whole data !ac-et #rom an a!!lication e*tractor( Question 3:

Wh" does the number in the 'Total' column, in the o'er'iew screen o# Transaction RSA7, di##er #rom the number o# data records that are dis!la"ed when "ou call u! the detail 'iew Answer: The number on the o'er'iew screen corres!onds to the total number o# $%Ws (see also &uestion .) that were written to the &R/C &ueue and that ha'e not "et been con#irmed( The detail screen dis!la"s the records contained in the $%Ws( +oth the records belon)in) to the !re'ious delta re&uest and the records that do not meet the selection conditions o# the !recedin) delta init re&uests are #iltered out( This means that onl" the records that are read" #or the ne*t delta re&uest are dis!la"ed on the detail screen( The detail screen o# Transaction RSA7 does not ta-e into account a !ossibl" e*istin) customer e*it( Question 4: Wh" does Transaction RSA7 still dis!la" $%Ws on the o'er'iew screen a#ter success#ul delta loadin) Answer: 0nl" when a new delta has been re&uested does the source s"stem learn that the !re'ious delta was success#ull" loaded into the +W S"stem( The $%Ws o# the !re'ious delta ma" then be con#irmed (and also deleted)( 1n the meantime, the $%Ws must be -e!t #or a !ossible delta re&uest re!etition( 1n !articular, the number on the o'er'iew screen does not chan)e i# the #irst delta is loaded into the +W S"stem( Question 5: Wh" are selections not ta-en into account when the delta &ueue is #illed Answer: /ilterin) accordin) to selections ta-es !lace when the s"stem reads #rom the delta &ueue( This is necessar" #or !er#ormance reasons( Question 6: Wh" is there a DataSource with '2' records in RSA7 i# delta e*ists and has been loaded success#ull" Answer: 1t is most li-el" that this is a DataSource that does not send delta data to the +W S"stem 'ia the delta &ueue but directl" 'ia the e*tractor ( 3ou can dis!la" the current delta data #or these DataSources usin) TA RSA4 (u!date mode 5'D') Question 7: Do the entries in Table R01D0C6R7S ha'e an im!act on the !er#ormance o# the loadin) !rocedure #rom the delta &ueue Answer: The im!act is limited( 1# !er#ormance !roblems are related to the loadin) !rocess #rom the delta &ueue, then re#er to the a!!lication-s!eci#ic notes (#or e*am!le in the C0-6A area, in the lo)istics coc-!it area, and so on)( Caution: As o# 6lu)1n 8222(8 !atch 4, the entries in Table R01D0C6R7S are as e##ecti'e #or the delta &ueue as #or a #ull u!date( 9ote, howe'er, that $%Ws are not s!lit durin) data loadin) #or consistenc" reasons( This means that when 'er" lar)e $%Ws are written to the delta &ueue, the actual !ac-a)e si:e ma" di##er considerabl" #rom the 7A;S1<= and 7A;$19=S !arameters( Question 8: Wh" does it ta-e so lon) to dis!la" the data in the delta &ueue (#or e*am!le a!!ro*imatel" 8 hours) Answer: With 6lu)1n 822.(. the dis!la" was chan)ed: "ou are now able to de#ine the amount o# data to be dis!la"ed, to restrict it, to selecti'el" choose the number o# a data record, to ma-e a distinction between the 'actual' delta data and the data intended #or re!etition, and so on( Question 9: What is the !ur!ose o# the #unction 'Delete Data and 7eta Data in a Queue' in RSA7 What e*actl" is deleted Answer: 3ou should act with e*treme caution when "ou use the delete #unction in the delta &ueue( 1t is com!arable to deletin) an 1nitDelta in the +W S"stem and should !re#erabl" be e*ecuted there( 9ot onl" do "ou delete all data o# this DataSource #or the a##ected +W S"stem, but "ou also lose all the in#ormation concernin) the delta initiali:ation( Then "ou can onl" re&uest new deltas a#ter another delta initiali:ation( When "ou delete the data, this con#irms the $%Ws -e!t in the &R/C &ueue #or the corres!ondin) tar)et s"stem( 6h"sical deletion onl" ta-es !lace in the &R/C outbound &ueue i# there are no more re#erences to the $%Ws( The delete #unction is intended #or e*am!le, #or cases where the +W S"stem, #rom which the delta initiali:ation was ori)inall" e*ecuted, no lon)er e*ists or can no lon)er be accessed( Question 10: Wh" does it ta-e so lon) to delete #rom the delta &ueue (#or e*am!le hal# a da") Answer: 1m!ort 6lu)1n 8222(8 !atch 4( With this !atch the !er#ormance durin) deletion im!ro'es considerabl"( Question 11: Wh" is the delta &ueue not u!dated when "ou start the >4 u!date in the lo)istics coc-!it area Answer: 1t is most li-el" that a delta initiali:ation had not "et run or that the the delta initiali:ation was not success#ul( A success#ul delta initiali:ation (the corres!ondin) re&uest must ha'e Q7 status ')reen' in the +W S"stem) is a !rere&uisite #or the a!!lication data to be written to the delta &ueue( Question 12: What is the relationshi! between RSA7 and the &R/C monitor (Transaction S7Q.) Answer: The &R/C monitor basicall" dis!la"s the same data as RSA7( The internal &ueue name must be used #or selection on the initial screen o# the &R/C monitor( This is made u! o# the !re#i* '+W, the client and the short name o# the DataSource( /or DataSources whose name is shorter than 82 characters, the short name corres!onds to the name o# the DataSource( /or DataSources whose name is lon)er than .? characters (#or delta-ca!able DataSources onl" !ossible as o# 6lu)1n 822.(.) the short name is assi)ned in Table R00SS@0RT9( 1n the &R/C monitor "ou cannot distin)uish between re!eatable and new $%Ws( 7oreo'er, the data o# a $%W is dis!la"ed in

an unstructured manner there( Question 13: Wh" is there data in the delta &ueue althou)h the >4 u!date has not "et been started Answer: 3ou !osted data in the bac-)round( This means that the records are u!dated directl" in the delta &ueue (RSA7)( This ha!!ens in !articular durin) automatic )oods recei!t !ostin) (7RRS)( There is no du!licate trans#er o# records to the +W s"stem( See 9ote A.7.B?( Question 14: Wh" does the 'Re!eatable' button on the RSA7 data details screen not onl" show data loaded into +W durin) the last delta but also newl"-added data, in other words, '!ure' delta records Answer: 1t was !ro)rammed so that the re&uest in re!eat mode #etches both actuall" re!eatable (old) data and new data #rom the source s"stem( Question 15: 1 loaded se'eral delta inits with 'arious selections( /or which one is the delta loaded Answer: /or delta, all selections made 'ia delta inits are summed u!( This means a delta #or the 'total' o# all delta initiali:ations is loaded( Question 16: @ow man" selections #or delta inits are !ossible in the s"stem Answer: With sim!le selections (inter'als without com!licated Coin conditions or sin)le 'alues), "ou can ma-e u! to about .22 delta inits( 1t should not be more( With com!licated selection conditions, it should be onl" u! to .2-82 delta inits( Reason: With man" selection conditions that are Coined in a com!licated wa", too man" 'where' lines are )enerated in the )enerated A+A6 source code which ma" e*ceed the memor" limit( Question 17: 1 intend to co!" the source s"stem, i(e( ma-e a client co!"( What will ha!!en with ma" delta Should 1 initiali:e a)ain a#ter that Answer: +e#ore "ou co!" a source client or source s"stem, ma-e sure that "our deltas ha'e been #etched #rom the delta &ueue into +W and that no delta is !endin)( A#ter the client co!", an inconsistenc" mi)ht occur between +W delta tables and the 0$T6 delta tables as described in 9ote A2D?A4( A#ter the client co!", Table R00S6R7SC will !robabl" be em!t" in the 0$T6 since this table is client-inde!endent( A#ter the s"stem co!", the table will contain the entries with the old lo)ical s"stem name which are no lon)er use#ul #or #urther delta loadin) #rom the new lo)ical s"stem( The delta must be initiali:ed in an" case since delta de!ends on both the +W s"stem and the source s"stem( ='en i# no dum! '7=SSAE=FT36=F;' occurs in +W when editin) or creatin) an 1n#o6ac-a)e, "ou should e*!ect that the delta has to be initiali:ed a#ter the co!"( Question 18. Am 1 !ermitted to use the #unctions in Transaction S7Q. to manuall" control !rocesses Answer: %se S7Q. as an instrument #or dia)nosis and control onl"( 7a-e chan)es to +W &ueues onl" a#ter in#ormin) +W Su!!ort or onl" i# this is e*!licitl" re&uested in a note #or Com!onent '+C-+W' or '+W-W@7-SA61'( Question 19. Des!ite the delta re&uest onl" bein) started a#ter com!letion o# the collecti'e run (>4 u!date), it does not contain all documents( 0nl" another delta re&uest loads the missin) documents into +W( What is the cause #or this Gs!littin)G Answer: The collecti'e run submits the o!en >8 documents to the tas- handler #or !rocessin)( The tas- handler !rocesses them in one or se'eral !arallel u!date !rocesses in an as"nchronous wa"( /or this reason, !lan a su##icientl" lar)e Gsa#et" time windowG between the end o# the collecti'e run in the source s"stem and the start o# the delta re&uest in +W( An alternati'e solution where this !roblem does not occur is described in 9ote D2D722( Question 20. Des!ite deletin) the delta init, $%Ws are still written into the DeltaQueue Answer: 1n )eneral, delta initiali:ations and deletions o# delta inits should alwa"s be carried out at a time when no !ostin) ta-es !lace( 0therwise, bu##er !roblems ma" occur: 1# "ou started the internal mode at a time when the delta initiali:ation was still acti'e, "ou !ost data into the &ueue e'en thou)h the initiali:ation had been deleted in the meantime( This is the case in "our s"stem( Question 21. 1n S7Q. (&R/C 7onitor) 1 ha'e status '90S=9D'( 1n the Table TR/CQ0%T, some entries ha'e the status 'R=AD3', others 'R=C0RD=D'( AR/CSSTAT= is 'R=AD'( What do these statuses mean Which 'alues in the #ield 'Status' mean what and which 'alues are correct and which are alarmin) Are the statuses +W-s!eci#ic or )enerall" 'alid in &R/C Answer: Table TR/CQ0%T and AR/CSSTAT=: Status R=AD means that the record was read once either in a delta re&uest or in a re!etition o# the delta re&uest( @owe'er, this still does not mean that the record has success#ull" reached the +W( The status R=AD3 in the TR/CQ0%T and R=C0RD=D in the AR/CSSTAT= means that the record has been written into the delta &ueue and will be loaded into the +W with the ne*t delta re&uest or a re!etition o# a delta( 1n an" case onl" the statuses R=AD, R=AD3 and R=C0RD=D in both tables are considered to be 'alid( The status =;=C%T=D in TR/CQ0%T can occur tem!oraril"( 1t is set be#ore startin) a delta e*traction #or all records with status R=AD !resent at that time( The records with status =;=C%T=D are usuall" deleted #rom the &ueue in !ac-a)es within a delta re&uest directl" a#ter settin) the status be#ore e*tractin) a new delta( 1# "ou see such records, it means that either a !rocess which con#irms and deletes records loaded into the +W is

success#ull" runnin) at the moment, or, i# the records remain in the table #or a lon)er !eriod o# time with status =;=C%T=D, it is li-el" that there are !roblems with deletin) the records which ha'e alread" been success#ull" been loaded into the +W( 1n this state, no more deltas are loaded into the +W( ='er" other status indicates an error or an inconsistenc"( 90S=9D in S7Q. means nothin) (see note 47B?24)( @owe'er the 'alue '%' in #ield '90S=9D' o# table TR/CQ0%T is o# concern( Question 22. The e*tract structure was chan)ed when the delta &ueue was em!t"( A#terwards new delta records were written to the delta &ueue( When loadin) the delta into the 6SA, it shows that some #ields were mo'ed( The same result occurs when the contents o# the delta &ueue are listed 'ia the detail dis!la"( Wh" is the data dis!la"ed di##erentl" What can be done Answer: 7a-e sure that the chan)e o# the e*tract structure is also re#lected in the database and that all ser'ers are s"nchroni:ed( We recommend resettin) the bu##ers usin) Transaction HS39C( 1# the e*tract structure chan)e is not communicated s"nchronousl" to the ser'er where delta records are bein) created, the records are written with the old structure until the new structure has been )enerated( This ma" ha'e disastrous conse&uences #or the delta( When the !roblem occurs, the delta needs to be re-initiali:ed( Question 23. @ow and where can 1 control whether a re!eat delta is re&uested Answer: >ia the status o# the last delta in the +W Re&uest 7onitor( 1# the re&uest is R=D, the ne*t load will be o# t"!e 'Re!eat'( 1# "ou need to re!eat the last load #or an" reason, manuall" set the re&uest in the monitor to red( /or the contents o# the re!eat, see Question .A( Delta re&uests set to red when data is alread" u!dated lead to du!licate records in a subse&uent re!eat, i# the" ha'e not alread" been deleted #rom the data tar)ets concerned( Question 24. As o# 61 8224(., the $o)istic Coc-!it o##ers 'arious t"!es o# u!date methods( Which u!date method is recommended in lo)istics Accordin) to which criteria should the decision be made @ow can 1 choose an u!date method in lo)istics Answer: See the recommendation in 9ote D2D722( Question 25. Are there !articular recommendations re)ardin) the ma*imum data 'olume o# the delta &ueue to a'oid dan)er o# a read #ailure due to memor" !roblems Answer: There is no strict limit (e*ce!t #or the restricted number area o# the 8A-di)it QC0%9T counter in the $%W mana)ement table which is o# no !ractical im!ortance, howe'er - or the restrictions re)ardin) the 'olume and number o# records in a database table)( When estimatin) Gso#tG limits, both the number o# $%Ws and the a'era)e data 'olume !er $%W are im!ortant( As a rule, we recommend bundlin) data (usuall" documents) as soon as "ou write to the delta &ueue to -ee! number o# $%Ws low (this can !artl" be set in the a!!lications, #or e*am!le in the $o)istics Coc-!it)( The data 'olume o# a sin)le $%W should not be much lar)er than .2I o# the memor" a'ailable to the wor- !rocess #or data e*traction (in a 48-bit architecture with a memor" 'olume o# about . E+"te !er wor- !rocess, .22 7+"te !er $%W should not be e*ceeded)( This limit is o# rather small !ractical im!ortance as well since a com!arable limit alread" a!!lies when writin) to the delta &ueue( 1# the limit is obser'ed, correct readin) is )uaranteed in most cases( 1# the number o# $%Ws cannot be reduced b" bundlin) a!!lication transactions, "ou should at least ma-e sure that the data is #etched #rom all connected +Ws as &uic-l" as !ossible( +ut #or other, +W-s!eci#ic, reasons, the #re&uenc" should not e*ceed one delta re&uest !er hour( To a'oid memor" !roblems, a !ro)ram-internal limit ensures that no more than . million $%Ws are e'er read and #etched #rom the database !er delta re&uest( 1# this limit is reached within a re&uest, the delta &ueue must be em!tied b" se'eral successi'e delta re&uests( We recommend, howe'er, to tr" not to reach that limit but tri))er the #etchin) o# data #rom the connected +Ws as soon as the number o# $%Ws reaches a D-di)it 'alue(

STEPS TO ADD NEW F E!DS TO DATASO"#$E %P#OD"$T ON S&S' #(3 S DE

Re&uirement ma" come u! to add new #ields to $0 coc-!it e*tractor which is u! J runnin) in !roduction en'ironment( This means the e*tractor is deli'erin) dail" deltas #rom SA6 RK4 to +W s"stem (Since this chan)e is to be done in RK4 6roduction s"stem, there is alwa"s a ris- that dail" deltas o# $0 coc-!it e*tractor would )et disturbed( 1# the delta mechanism is disturbed (delta &ueue is bro-en) then there no another wa" than doin) re-initiali:ation #or that e*tractor( @owe'er this re-init is not eas" in terms o# time J resource( 7oreo'er no or)ani:ation would be willin) to !ro'ide that much downtime #or li'e re!ortin) based on that e*tractor( As all o# us -now that initiali:ation o# $0 =*tractor is critical, resource intensi'e J time consumin) tas-( 6re-re&uisites to !er#orm #ill setu! tables are - we need to loc- the users #rom transactional u!dates in RK4 s"stem, Sto! all batch Cobs that u!date the base tables o# the e*tractor( Then we need to schedule the setu! Cobs with suitable date ran)esKdocument number ran)es( We also came across such scenario where there was a re&uirement to add 4 new #ields to e*istin) $0 coc-!it e*tractor 8$1SF.8F>C1T7( 1nitiali:ation was done #or this e*tractor . "ear bac- and the data 'olume was hi)h(We ado!ted ste! b" ste! a!!roach to minimi:e the ris- o# delta &ueue )ettin) bro-en Kdisturbed( @o!e this ste! b" ste! !rocedure will hel! all o# us who ha'e to wor- out similar scenarios( Step by Step Procedure:.(Carr" out chan)es in $0 Coc-!it e*tractor in SA6 RK4 De' s"stem(As !er the re&uirement add new #ields to =*tractor(These new #ields mi)ht be !resent in standard su!!ortin) structures that "ou )et when "ou e*ecute G7aintain Data sourceG #or e*tractor in $+W=( 1# all re&uired #ields are !resent in su!!ortin) structure mentioned abo'e then Cust add these #ields usin) arrow buttons !ro'ided and there is no need to write user e*it code to !o!ulate these new #ields(@owe'er i# these #ields (or some o# the re&uired #ields) are not !resent in su!!ortin) structures then "ou ha'e to )o #or a!!end structure and user e*it code( The codin) in user e*it is re&uired to !o!ulate the newl" added #ields( 3ou ha'e to write A+A6 code in %ser e*it under C70D J in 1nclude <;RSA%2.(All abo'e chan)es will as- "ou #or trans!ort re&uest( Assi)n a!!ro!riate de'elo!ment

classK6ac-a)e and assi)n all these obCects into a trans!ort re&uest( 8(Carr" out chan)es in +W De' s"stem #or obCects related to this chan)e(Carr" out all necessar" chan)es in +W De' s"stem #or obCects related to this chan)e (1n#o source, trans#er rules, 0DS, 1n#o cubes, Queries J wor-boo-s)( Assi)n a!!ro!riate de'elo!ment classK6ac-a)e and assi)n all these obCects into a trans!ort re&uest 4(Test the chan)es in QA s"stem(Test the new chan)es in SA6 RK4 and +W QA s"stems( 7a-e necessar" chan)es (i# needed) and include them in #ollow-u! trans!orts( A(Sto! >4 batch Cobs #or this e*tractor(>4 batch Cobs #or this e*tractor are scheduled to run !eriodicall" (hourl"Kdail" etc) AsRK4 S"stem Administrator to !ut on holdKcancel this Cob schedule( D($oc- out users, batch Cobs on RK4 side J sto! 6rocess chain schedule on +W(1n order to a'oid the chan)es in database tables #or this e*tractor and hence !ossible ris- o# loss o# data, as- RK4 S"stem Administrator to loc- out the users( Also batch Cob schedule need to be !ut on hold Kcancel(As- S"stem Administrator to clear !endin) &ueues #or this e*tractor (i# an") in S7Q.KS7Q8( Also !endin) Kerror out '4 u!dates in S7DB should be !rocessed(0n +W !roduction s"stem the !rocess chain related to delta 1n#o !ac-a)e #or this e*tractor should be sto!!ed or !ut on hold( L(Drain the delta &ueue to <ero #or this e*tractor(=*ecute the delta 1n#o !ac-a)e #rom +W and load the data into 0DS J 1n#o cubes( Mee! e*ecutin) delta 1n#o !ac-a)e till "ou )et 2 records with )reen li)ht #or the re&uest on +W side( Also "ou should )et 2 $%W entries in RSA7 #or this e*tractor on RK4 side( 7(1m!ort RK4 trans!orts into RK4 6roduction s"stem(1n this ste! we im!ort RK4 trans!ort re&uest related to this e*tractor( This will include user e*it code also( 6lease ensure that there is no s"nta* error in include <;RSA%2. and it is acti'e( Also ensure that obCects such as a!!end structure is acti'e a#ter trans!ort( B(Re!licate the data source in +W s"stem(0n +W !roduction s"stem, re!licate the e*tractor (data source)( ?(1m!ort +W trans!ort into +W 6roduction s"stem(1n this ste! we im!ort +W trans!ort related to this chan)e into +W 6roduction s"stem( .2(Run !ro)ram to acti'ate trans#er rules=*ecute !ro)ram RSFTRA9STR%FACT1>AT=FA$$( =nter the 1n#o source and source s"stem name and e*ecute( This will ma-e sure that trans#er rules #or this 1n#o source are acti'e ..(=*ecute >4 Cob 7anuall" in RK4 sideEo to $+W= and clic- on Nob Control #or A!!lication area related to this e*tractor (#or 8$1SF.8F>C1T7 it is a!!lication .8)( =*ecute the Cob immediatel" and it should #inish with no errors( .8(=*ecute delta 1n#o !ac-a)e #rom +W s"stemRun delta 1n#o !ac-a)e #rom +W s"stem( Since there is no data u!date, this e*traction re&uest should be )reen with :ero records (success#ul delta e*traction) .4(Restore the schedule on RK4 J +W s"stemsAs- S"stem Administrator to resume >4 u!date Cob schedule, batch Cob schedule and unloc- the users( 0n +W side, restore the !rocess chains schedule(/rom ne*t da" onwards (or as !er #re&uenc"), "ou should be able to recei'e the delta #or this e*tractor with data also !o!ulated #or new #ields(