EARLY DELTA INITIALIZATION IN LO COCKPIT

HI EVERYBODY,
SORRY FOR ASKING A SILLY QUESTION --BUT I REALLY NEED AN EXPLANAITION
<b>WHAT IS EARLY DELTA INITIALIZATION</b>????(can we select this method the same way we do for Delta init)
I KNOW THAT BEFORE DOING DELTA WE WILL DO DELTA INITIALIZATION.
I HAVE READ A WEBLOG OF ROBERTO IT WAS WONDERFUL BUT I GOT STUCK WITH THIS <b>EARLY DELTA INITIALIZATION.</b> AND ABOUT DOCUMENT POSTINGS.
DOES THIS MEAN THAT BEFORE GOING FOR DELTA INITIALIZATION (i mean before filling setup tables ) DO WE NEED TO SHUT DOWN THE INSTANCE ON OUR OLTP --so no transaction data will be updated to the extract structure.
WHAT IS <b>FREE DOCUMENTS POSTING PHASE</b>
THANKS AND REGARDS
NEELKAMAL
Message was edited by: neelkamal moganti

You can find the option for Early Delta Init in the InfoPackage on the Update tab. Using this option, the source system update can continue and data can be written to the delta queue while the initialization request is being processed.
Early Delta Intialiation is the process in which we run the init of delta and load the delta queue in parallel.
Generally when we do Initialization we need to stop transactions in R/3 system till the initialization is completed if we do Early delta initialization we don't have to stop posting of transactions in R/3 even when we are doing initialization. Please see this for more explanation
Early Delta Initialization
With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the posting of data in the source system. The option of executing an early delta initialization is only available if the Data Source extractor called in the source system with this data request supports this.
Assign  points if it helps...
regards,
ashok

Similar Messages

  • How to Use Early Delta Initialization

    Hi BW Experts,
    We are in BI 7.0 Version. Only for Reporting we are using BI 7.0. For modeling, still we are using BW 3.1C only.
    We want to use Early Delta Initialization. But this is in Disable Mode in our system
    I am getting the following Messages:
    <b>"Extractors supporting early delta initialization are not available before plug-in (-A) 2002.1"</b>
    <b>"You cannot execute an initialization simulation together with an early delta"</b>
    Please can anyone give me the suggestion.
    Regards
    Anjali

    Hi,
    you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the updating of data in the source system. You can only execute an early delta initialization if the DataSource extractor called in the source system with this data request supports this..Use the Early Delta Initialization indicator in the InfoPackage if you want to avoid a period when no updates can be made (no document processing and update) in the source system while the delta process is being initialized. In some applications (such as LO Cockpit), an update-free period is nevertheless needed to fill the setup tables. In such cases, the update-free time is merely reduced. If you want to carry out early delta initialization, the update in the source system can continue  and the data can be written to the delta queue while the initialization requests are being processed. Note: DataSources that support early delta initialization are available as of the release Plug-In 2002.1. The field ZDD_ABLE (characteristic value = X) for table RSOLTPSOURCE (in BW) or ROOSOURCE (in the source system) indicates whether a DataSource can support early delta initialization.Not always on our systems an important downtime is possible in the initialization process during the reconstruction and the delta init request (just thinking when you need to ask a billing stop period...a real nightmare in some company !)
    For this reason, as of PI 2002.1 and BW Release 3.0B, you can use the early delta initialization to perform the initialization for selected datasources (just checking in infopackage update mode tab if this function is available): in this way you can readmit document postings in the OLTP system as early as possible during the initialization procedure..In fact, if an early delta initialization infopackage was started in BW, data may be written immediately to the delta queue.
    But, if you are working with the queued delta method, using early delta initialization function doesn’t make sense: as described before, it’s the same method definition that permits to reduce downtime phase.
    But leaving aside that, don’t forget that, regardless of the update method selected, it’s ALWAYS necessary to stop any document postings (for the relevant application) during setup tables recompilation run

  • Early Delta Initialization option in Production system

    Hi Experts,
    I have seen some threads related to Early Delta initialization in this forum. I have a question regarding this option.
    To minimize the downtime/block users in the R/3 production system during set up tables fillup I would like to use the Early delta option. Please give your suggestions on the following procedure:
    For Sales Orders, billing and Deliveries
    1. Initialize Early delta in the BI system.
    2. Go and fill setup tables
    3. Do a full load to BI
    4. Run delta job in R/3 (LBWE)
    5. Run delta job in BI Info package
    Do we miss any documents in this process for e.g. during set up tables fill up changes to existing documents or newly created sales orders.
    I feel we won't miss. All changes will be reflected in Delta queue. And even newly created orders also will be coming to delta queue.
    Please let me know if I am wrong.
    Thank you.

    Need Clarification on this thread,
    According to my understanding, during the filling of set up table if a user does any posting, then the data available in BW will be incorrect.
    am i right?
    In your sequence the 4th step
    4. Run delta job in R/3 (LBWE),     this means you are using queued or unseriallized v3 update.
    Early delta iniliazation essentially of no advantage because, as conventional initialization procedures, you can readmit document
    postings after successfully filling the setup tables.
    can anybody clear my doubt. is it possible during setup table filling user can post a document.
    I know the documents will be collected in the queue. But the data loaded to bw will be incorrect right?
    Regards,
    Anand.
    Edited by: araj123 on May 26, 2010 11:41 AM

  • BW early delta initialization request failed

    Dear all,
    the early delta initialization request of a info package failed for the data source 2LIS_11_VAITM & 2LIS_18_I3OPER due to disk space problems (log overflow).
    Is there a possibility to rerun the early delta initialization load without destroying the delta queue and without a new source system initialization? The job has to been already scheduled to push the data into delta queue and the delta info package was not started jet.
    Regards
    Edited by: Claudio Forte on Oct 11, 2010 11:22 PM

    Hi,
    Take a look on the information given in below links:
    Re: Early Delta Intialization!!!
    Re: Early Delta Initialization
    Re: Early Delta Initialization
    Re: Lo Extraction
    Re: reg:early delta andinit delta with out data transfer
    With rgds,
    Anil Kumar Sharma .P

  • When are init entries done in source system?And early delta initialization?

    Hi Friends,
    Q1) When are the init entries done in source system?
    If INIT entries are done when I run INIT that means:
    If my setup job finishes at 6AM and I run the INIT at 1 PM will I loose all data between 6AM and 1PM?
    If INIT entries are done when I run setup table i.e. when setup table load finish then
    If my setup job finishes at 6AM and I run the INIT at 1 PM...it will load data till 6AM
    and after that data would bere there in Delta queue. So, this is ok...as no loss of data.
    Q2) I  have read on help.sap that "With early delta initialization, you have the option of writing the data into the
    delta queue or into the delta tables for the application during the initialization request in the source
    system. This means that you are able to execute the initialization of the delta process (the init request),
    without having to stop the updating of data in the source system."
    Does this mean when I run INIT at 1PM, no V1 updates will happen for that DS in Source System?
    If Yes, that means I should always (when users are online) run INIT with early delta initialization
    during times when users would be online?
    Thanks!

    Hello,
    You will find the answers to the questions that you ask and the correct procedure to follow in the SAP note 602260.
    Best Regards,
    Des

  • Early delta initialization

    Hello Gurus,
    What are the scenarios we use Early Delta Init.
    Is it available for Logistics datasources.
    Full points to right answers.
    Thanks in advance.

    hi BW,
    check this
    http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/frameset.htm
    Early Delta Initialization
    With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the updating of data in the source system. You can only execute an early delta initialization if the DataSource extractor called in the source system with this data request supports this.
    Extractors that support early delta initialization were delivered with Plug-Ins as of Plug-In (-A) 2002.1.
    You cannot run an initialization simulation together with an early delta initialization.
    yes, it's available for logistics - oss note 505700, you can cross check the infopackage.
    hope this helps.
    505700-LBWE: New update methods as of PI 2002.1
    g) Early delta initialization in the logistics extraction:
    As of PI 2002.1 and BW Release 3.0B, you can use the early delta initialization to perform the delta initialization for selected DataSources.
    Only the DataSources of applications 11, 12 and 13 support this procedure in the logistics extraction for PI 2002.1.
    The early delta initialization is used to admit document postings in the OLTP system as early as possible during the initialization procedure. If an early delta initialization InfoPackage was started in BW, data may be written immediately to the delta queue of the central delta management.
    When you use the "direct delta" update method in the logistics extraction, you do not have to wait for the successful conclusion of all delta Init requests in order to readmit document postings in the OLTP if you are using an early delta initialization.
    When you use the "queued delta" update method, early delta initialization is essentially of no advantage because here, as with conventional initialization procedures, you can readmit document postings after successfully filling the setup tables, provided that you ensure that no data is transferred from the extraction queue to the delta queue, that is, an update collective run is not triggered until all of the delta init requests have been successfully posted.
    Early Delta Initialization

  • Enabling Early Delta Initialization option for LO DataSource 2LIS_06_INV

    Hi Guyz,
    I want to enable Earlt Delta Initialization option for LO DataSource 2LIS_06_INV, as of now its greyed out.
    please tell me if its possible or not, and if yes then please let me know the steps in detail.
    cheerz,
    raps.

    hi,
    Not all Data sources support Early Delta Initialization. Early delta initialization is done to capture the deltas when the initialization is being done between BW and source system (init with data transfer). As init with data transfer takes large time and during this time any records created will also be not captured so we do early delta initialization, also the same can be achieved by executing the init without data transfer and then loading a full repair request. The init without data transfer creats a time stamp and delta is generated for newly posted records.
    regards,
    Arvind.

  • Early delta initialization and update methods

    Hi gurus
    Can we use EDI with "queued delta" as update method?
    If yes where we need to do that setting and if no then would you pl tell me which functionality we need to use in infopkg to load delta from R/3 with Queued delta as a update method?
    Pl help to understand this.
    Thanks

    In the 'update' mode in your infopackage, if you see an 'early delta init' option, you can use it for that datasource (for queued or any other delta). This is where you choose to run an 'early delta init'.

  • Need for locking system for delta initialization (BW-R3-LO)

    Hello all,
    Could someone please help me with the following,
    Please be kind, don't get impatient for the lengthy post
    1. Do we need to lock the system (or posting-free the system) to do early delta initialization or not? If yes, please explain me how that work?
    2. Someone somewhere mentioned that early delta initialization is not preferable compared to normal delta initialization, even though early delta initialization is advantageous. Why is that so?
    3. Imagine, while scheduling Queued Delta Init or un-serialized V3 delta Init, if I choose certain end date and time (say, 10pm, 12-31-2007) for the records, then all the records till that point would be loaded to setup tables and all the records after that point of time will be moved to extraction queue or update tables. My question is, if this is true why would we ever need to lock the system during setup tables filling?
        If you say the records after that particular time and date (10pm, 12-31-2007) will not be collected in extraction queue and update tables, why don't we do the following
                 a). say, I do full load with end date and time (10pm 12-31-2007)
                 b). Next, I do delta init with start date and time (10pm 12-31-2007) (this time I lock the postings)
             If we do this way, we can actually reduce the down time of the system. Is my conclusion right?
             If you say it's not practicable as some transactions' saving time differs from time stamp and some transactions' delta is even measured by pointer.......if this is the case we can use Delta offset. What do you say about this?
    4. How this scenario differs to early delta initialization?
    Your responses would be greatly appreciated
    Thank you

    Hello,

    >
    curious maven wrote:
    > Do we need to lock the system (or posting-free the system) to do early delta initialization or not? If yes, please explain me how that work?
    No,you don't need to lock the Source System which is the advantage of Early Delta Init.
    With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the posting of data in the source system. The option of executing an early delta initialization is only available if the DataSource extractor called in the source system with this data request supports this.
    [Business Information Warehouse 3.0 Overview Presentation|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9a0e9990-0201-0010-629b-dc2735cb9c81]
    2
    >
    curious maven wrote:
    > 2. Someone somewhere mentioned that early delta initialization is not preferable compared to normal delta initialization, even though early delta initialization is advantageous. Why is that so?
    Early delta is not supported by all the extractors. See Lo Extraction
    3
    >
    curious maven wrote:
    Imagine, while scheduling Queued Delta Init or un-serialized V3 delta Init, if I choose certain end date and time (say, 10pm, 12-31-2007) for the records, then all the records till that point would be loaded to setup tables and all the records after that point of time will be moved to extraction queue or update tables. My question is, if this is true why would we ever need to lock the system during setup tables filling?
    >
    >     If you say the records after that particular time and date (10pm, 12-31-2007) will not be collected in extraction queue and update tables, why don't we do the following
    >            
    >              a). say, I do full load with end date and time (10pm 12-31-2007)
    >              b). Next, I do delta init with start date and time (10pm 12-31-2007) (this time I lock the postings)
    >
    >          If we do this way, we can actually reduce the down time of the system. Is my conclusion right?
    >
    >          If you say it's not practicable as some transactions' saving time differs from time stamp and some transactions' delta is even measured by pointer.......if this is the case we can use Delta offset. What do you say about this?
    This is applicable to Generic Delta where you can set the Safety Interval (Upper Limit and lower Limit) for the extractor based on ALE Pointer, or Time Stamp or Calendar day.
    If you excute a extractor with early delta init, during the setup table fill, the delta records will be directly written to the delta queue. The delta management handles these functionality.
    [How to Create Generic Delta|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]
    [SAP BI Generic Extraction Using a Function Module|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33]
    4
    >
    curious maven wrote:
    How this scenario differs to early delta initialization?
    If you do a Init without Early Delta init, then the user cannot post new documents and you have to either schedule in the weekend or request for a Source System downtime.
    But if you use Early delta , then you don't need the source system down time and the user can post new records during the init, which will be written to the delta queue directly.
    [How to Minimize Effects of Planned Downtime (NW7.0)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/901c5703-f197-2910-e290-a2851d1bf3bb]
    [How to Minimize Downtime for Delta Initialization (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5d51aa90-0201-0010-749e-d6b993c7a0d6]
    Thanks
    Chandran

  • Early Delta Init

    Hi,
    Can you please anybody solve my doubts
    1.What is importance ' Early Delta Init '?
    2. And which Data Sources are comes under this?
    3. In which Scenario  we will use this ?
    Regards,
    Ali

    Hi,
    Early Delta Initialization
    With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the posting of data in the source system. The option of executing an early delta initialization is only available if the DataSource extractor called in the source system with this data request supports this.
    Extractors that support early delta initialization are delivered with Plug-Ins as of Plug-In (-A) 2002.1.
    You cannot run an initialization simulation together with an early delta initialization.
    Hope this link may make you clear about Early Delta Initialization
    http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/frameset.htm
    Early delta Initialization
    Hope this helps.
    Regards
    Raj

  • Delta Initialization for infocube 0FIAR_C03

    Hi Frends
      We r uploading data to infocube 0FIAR_o03 with infosource 0fi_ar_4.and subcequently to infocube 0fiar_c03. first time we r loading data with delta initialization then delta uploading.one typical problem we r facing here that.yesterday we have changed 3 records in our quality clint and delta loaded for same.the no of records transferd yesterday was zero.we have also checked same in transaction rsa7 there was no record with our data sorce.again today  we have checked with transaction rsa7. the no of records was zero. but when we have loaded with delta update mode.there are 3 records in delta extraction(yesterday change records)
    pl let me know some hints on this
    Awaiting ur early reply/
    Thanks & Rgds
    Tukuna

    Tukuna,
    On which filed you have created Delta.
    1. If delta field is Date (Record Create Date or change date), then use Upper Limit of 1 day.
    <i>This will load Delta in BW as of yesterday. Leave Lower limit blank.</i>
    2. If delta field is Time Stamp, then use Upper Limit of equal to 1800 Seconds (30 minutes).
    <i>This will load Delta in BW as of 30 minutes old. Leave Lower limit blank.</i>
    3. If delta field is a Numeric Pointer i.e. generated record # like in GLPCA table, then use Lower Limit. Use count 10-100. Leave upper limit blank. If value 10 is used then last 10 records will be loaded again.
    Hope its help.
    Thanks
    Ramu

  • K8T Neo-FIS2R No boot - Early Chipset Initialization LED

    Went from a MSI K7N2 Delta-ILSR with XP 2500+ O/C'd to 3200+ to an MSI K8T Neo-FIS2R board with a retail Athlon 64 3200+ and a Thermaltake Silent Boost Heatsink/Fan combo.
    RAM = 2 x 512MB Apacer PC2700 (MSI approved).
    Video= ATI 9800 Pro AIW
    Antec Sonata case with 380Watt True Power +12V-18A, +5V-35A, 3.3V-28A
    Seagate 160GB SATA 7200.7 drive.
    On boot, system hangs at #1 red LED indicating Early Chipset Initialization.
    Video is blank, all switches work, all drives spin up, no beep codes, just dead.
    Tried just CPU, Fan/Heatsink, Video and still same.
    Without any RAM, system beep codes for RAM.
    Tried RAM in slots 1 and 2, 3 and 4 and just one by itself.  Never a change to the DBracket light.
    Cleared BIOS and retried.  Nothing.  No video at all.
    What does that "Early Chipset Initialization" mean anyway?  I guess the board is bad.  This is it's first boot attempt.

    Well, I think I know what the problem is, aside from the PSU... I tried my brother-in-laws 550 PSU that pushes 24A on the +12V and it did not budge.  I think it is the board.  I did an RMA with Newegg and will be sending it in for a replacement.
    Thanks for the advice on the PSU's... I will be heading back to Newegg to get one.
    As an aside, I did get a new PSU since my last post.  It was a Maddog Multimedia 550 that is made by Thermaltake.  The voltage is not listed on the outside of the box, so, once I opened it, I noticed a couple things.  One, it is a 480 not a 550, and two, the +12V is a paltry - abismal - 18A!  This was CompUSA's best power supply and cost $140 after taxes! (I wanted one now, not in the few days it takes Newegg to get me one).  Needless to say, it is going back.  Since the numbers were not on the outside of the box, they are taking it back without a restock fee.
    I will quell my desire for now now now and wait until a good one from Newegg arrives.  I will let you know of my results!
    ps -  I am toying with the idea of the PC Power one... !

  • K7N2: Early Chipset Initialization. Help needed.

    Hi all. My box used to work perfectly until a few days ago. Then, the other day I switched it on as usual and all I got was a series of long beeps every two or three seconds, and I have to power off. The leds in the back say it's Early Chipset Initialization.
    What's up?  
    Can anyone help me with this? ... please.
    Here are my specs:
    MOBO: MSI K7N2 Delta-L nForce2-400Ultra K7 FSB400
    CPU: AMD Athlon XP 3000+, Freq 2167MHz, FSB 333, 512KB cache L2
    RAM: 3 x DIMM 512MB DDR/333 KINGSTON KVR333X64
    HD: 2 x Hard Disk Maxtor DiamondMax Plus 9, 120GB EIDE, Ultra ATA/133
    VIDEO CARD: 3D PROPHET 9600 256MB HERCULES, AGP 8X, TV Out, DVI
    AUDIO CARD: CREATIVE SOUND BLASTER AUDIGY 2
    DVD-RW: Plextor PX504A
    ETH: Netgear 10/100 FA311-50, 10/100Base-TX

    Thank you Raven.
    Actually, the only thing I'd like to know then... do you think the kingston RAM is causing the problem? Btw, what sort of problem do you think it is? just *incompatibility*?
    If so, I guess I'll try to get another brand (which one do you suggest?)
    What I'm worried about, is to find myself removing one piece after the other until I remain only with monitor and mouse  
    I chose all the components for my box, but I had it assembled by one of those internet shops that are supposed to advise you if you are not expert and you are making mistakes, such as choosing incompatible mobo and ram
    Probably I should have searched the forums like this before...
    Thanks a lot. Really.

  • Delta Initialization vs Delta Update

    We're having some issues with performance when loading our GL cube.  What I would like to do is perform many delta initializations, each delta inititialization containing one month/period.
    My confusion is in the fact that the last time I attempted this, when I subsequently went to run my delta UPDATE the same selection criteria was automatically inserted into my delta update.
    So for example my INIT may look like this;
    REQUEST1: Selection = 001.2005
    REQUEST2: Selection = 002.2005
    etc........etc...
    REQUEST12: Selection = 012.2005
    Next the UPDATE info package seems to inherit the same criteria... doesn't this mean it will not update anything beyond that criteria??
    I'm just wondering if it is possible to do an incremental initialization and still be able to enable delta updates for future periods?
    Thanks!

    Hi Patrick,
    The delta update will load the data as per the selections made in the Init run. A delta requested after several initializations, contains the sum of all the successful initial selections as a selection condition. This selection condition can then no longer be changed for the delta.
    Take a look here for more info:
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/content.htm
    Hope this helps...

  • Extraction, Flat File, Generic Data Source, Delta Initialization

    Extraction, Flat File, Generic Data Source, Delta Initialization
    I have couple of questions regarding data extraction.
    1.     If you have Data Source a Flat File e.g. Excel file I know that you have to create Data Source at BW side. How do you upload updates, by selecting Delta Update when executing next Data Load? Do you ever u201Cconvertu201D this Excel file into Application Tables to become SAP Source 
    2.     Can you please give me example of situation where you had to create Generic Data Source? What is difference between Time Stamp, Calend. Day and Numeric Pointer. Which one is most common to select?
    3.     I read somewhere that Generic Data Source does not have Setup Table. I thought that you have to have Setup Table in order to load transaction Data otherwise you will lock the Application Tables. Where am I going wrong im my thinking please?
    4.     What are steps in terms of IP before, under and after Delta Initialization. I belive that you can do two ways:
    Full Update - Initialize Delta Process (without Data Transfer) u2013 Delta Update  or
    Initialize Delta Process (with Data Transfer) u2013 Delta Update
    Am I right? What is most common method and why?
    5.     If you want to add a filed in Data Source after 6 month using it, you want to do it without re-init Delta Queue. You add field in RSA6, then provide info for ABAP to populate new filed (info u2013 name of Data Source, Extract Structure, field added, name of Application Table which contains the field). How does it work now as there is no SetUp table it has been deleted after Initialisation? How does Delta Queue know that it is going to receive data which has been  expanded by one field or it may does not need to know at all?
    THANKSSSSSSSSSs

    Hi,
    1. If you have Data Source a Flat File e.g. Excel file I know that you have to create Data Source at BW side. How do you upload updates, by selecting Delta Update when executing next Data Load? Do you ever u201Cconvertu201D this Excel file into Application Tables to become SAP Source
    Once you create Datasource for A flat file extraction then it is file source system specific hence you cont change to Application table source Data source
    In info package you can change the source as application server instead of desktop no need to change the DS
    2. Can you please give me example of situation where you had to create Generic Data Source? What is difference between Time Stamp, Calend. Day and Numeric Pointer. Which one is most common to select?
    When we don't find any standard extractor then we can go for Generic(if i want information sales along with finance information in a data source then generally we dont get standard one hence we can go for generic DS)
    Check the below link for More about generic DS .
    http://wiki.sdn.sap.com/wiki/display/BI/Generic+Extraction
    for Delta capturing you can use
    Timestamp(if the table has time stamp filed  so it can stamp the last changed record in that table hence it is easy to get delta based on the time stamp)
    Calday- (If the table doesn't have the Timestamp filed then search for Calday where you can stamp the delta based on the date when documents are changed )
    Numericpointer : If the table doesn't above both then we go for this option where you can the numeric value change stamp )
    3. I read somewhere that Generic Data Source does not have Setup Table. I thought that you have to have Setup Table in order to load transaction Data otherwise you will lock the Application Tables. Where am I going wrong im my thinking please?
    Generic datasource nothing but we extracting data directly from the database table without any interface between the application/systems
    4. What are steps in terms of IP before, under and after Delta Initialization. I belive that you can do two ways:
    Full Update - Initialize Delta Process (without Data Transfer) u2013 Delta Update or
    Initialize Delta Process (with Data Transfer) u2013 Delta Update
    Am I right? What is most common method and why?
    Correct
    5. If you want to add a filed in Data Source after 6 month using it, you want to do it without re-init Delta Queue. You add field in RSA6, then provide info for ABAP to populate new filed (info u2013 name of Data Source, Extract Structure, field added, name of Application Table which contains the field). How does it work now as there is no SetUp table it has been deleted after Initialisation? How does Delta Queue know that it is going to receive data which has been expanded by one field or it may does not need to know at all?
    Once you add the new field to structure(DS) you will get the data as on date onwards not historical data hence what is the concept of setup table  ( delta records come from the Delta Que not from the setup table )
    If you want histaric data to new field then you need to setp table deletion ...etc...
    Hope it is clear..
    Regards,
    Satya

Maybe you are looking for

  • Content Conversion Issue

    I am performing content conversion on a file in the file receiver adapter.  Everything works well but one item.  My xml is set up as <ns0:MT_Delivery xmlns:ns0="http://abc.com"> <Header>              <BOF>$BOF 20111220</BOF> </Header> <BOB>      <BOB

  • Server-side includes in cs5

    have used all previous versions of dw. no prior problem with server-side includes. now, they are not showing up in design view. Yes, I have marked preferences to include hidden items/server side includes. any thoughts anyone?

  • Need help in Load script

    Hi All, I have recorded a Load script with 5 classes(5 check boxes) and i press select all button,so if script is having 5 classes it will pass and if it is having less than 5 classes it is failing. http.solveXPath("web.input.selected",".//INPUT[@nam

  • Very basic Objective-C Question

    Okay, I am completely new to Objective-C so forgive me. I am trying to run a command when the MainView is initially loaded, so I figured I would need to override the constructor. I tried overriding init and initWithFrame, but it didn't work. How can

  • Efficiency Question - Cutting Clips

    Efficiency Question - Cutting Clips. So I was wondering if there is a better way to cut my clips that I am not using. Basically I often have large long clips of raw footage that I cut down to the usable segments. Each raw file may be over an hour lon