Skip to Content
author's profile photo Former Member
Former Member

Delta Types & the Extractors

Dear Experts of SAP BW,

I got confused by the terms used in the books.

For Delta Type (PULL) 'E', its said that BW Extractor in Delta Mode writes the records to the Delta Queue. This delta type applies to LIS & CO-PA.

1. 'SAPI reads the selection filter ranges inclusive from all prior initialization runs'. Where is this SAPI mentioned reside? BW or R/3 since both sides have SAPI.

Also, is the selection filtering done via the InfoPackage 'Data Selection' Tab? If so, what is meant by including all previous init run selections? All added up?

2. Is the 'BW Extractor in Delta mode' = 'Application Extractor' = 'Datasource Extractor called in delta mode'?

3. LO uses Delte Type (PUSH) 'D'. This type is used by LO V3 Update & Direct write by FI-AR/AP. Does this type also apply to the other 2 LO Update Methods Queued & Direct? FI-AR/AP uses this type to write Directly. Is this the same as LO's Direct writing to Delta Queue?

Regards,

bworbust

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Feb 21, 2005 at 02:13 PM

    Hi bworbust,

    where are you reading these sentences ?

    However, take a look to SAP tables RODELTAM (here you can find all delta procedures and related properties) and ROOSOURCE (where, for every datasource in your system, you can find which type of delta is associated to)....surfing through these tables I'm seeing that delta type D is not supported by datasources you mentioned...

    However, push and pull (delta type) are different datawaerehousing delta concept (not formerly coded by SAP) because in a pull delta a DW pulls data out of a source system, in a push delta a source system push delta records into a DW.

    For your second question, I think that BW, application or datasource (this last one seems to be more correct) refer to the same thing...

    about initializations...when you make an init run, API reads if previous inits have been performed and if the selection conditions (in your infopackage) don't overlap the previous ones...if not, all (previous and actual) selections are merged in order to manage only one delta queue (it's not possible to have several delta channel for the same datasource/BW destination)...otherwise, you have to delete old init before doing a new one !

    Bye,

    Roberto

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      for sentences no.1 and 2 no problem, you can refer to my previous reply....for the third one, ok, maybe these documents refer to a SAPI version not installed on my system (and I've never seen before!)

      Waiting for some contribution from someone else...

      Bye,

      Roberto

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.