Professional Documents
Culture Documents
How To Retain Deltas When You Change LO in Production System
How To Retain Deltas When You Change LO in Production System
How To Retain Deltas When You Change LO in Production System
Production system!
created by Todor Peev on Jul 19, 2013 1:10 PM, last modified by Todor Peev on Dec 18, 2013 2:55 PM
Version 2
Requirement may come up to add new fields to LO cockpit extractor which is up & running in production environment.
This means the extractor is delivering daily deltas from SAP R/3 to BW system .
Since this change is to be done in R/3 Production system, there is always a risk that daily deltas of LO cockpit
extractor would get disturbed. If the delta mechanism is disturbed (delta queue is broken) then there no another way
than doing re-initialization for that extractor. However this reinit is not easy in terms of time & resource. Moreover no
organization would be willing to provide that much downtime for live reporting based on that extractor.
As all of us know that initialization of LO Extractor is critical, resource intensive & time consuming task. Prerequisites
to perform fill setup tables are - we need to lock the users from transactional updates in R/3 system, Stop all batch
jobs that update the base tables of the extractor. Then we need to schedule the setup jobs with suitable date
ranges/document number ranges.
2.Carry out changes in BW Dev system for objects related to this change.
Carry out all necessary changes in BW Dev system for objects related to this change (Info source, transfer rules,
ODS, Info cubes, Queries & workbooks). Assign appropriate development class/Package and assign all these objects
into a transport request
5.Lock out users, batch jobs on R/3 side & stop Process chain schedule on BW.
In order to avoid the changes in database tables for this extractor and hence possible risk of loss of data, ask R/3
System Administrator to lock out the users. Also batch job schedule need to be put on hold /cancel.
Ask System Administrator to clear pending queues for this extractor (if any) in SMQ1/SMQ2. Also pending /error out
v3 updates in SM58 should be processed.
On BW production system the process chain related to delta Info package for this extractor should be stopped or put
on hold.
From next day onwards (or as per frequency), you should be able to receive the delta for this extractor with data also
populated for new fields.