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

Custom Datasource without FM and the value sent to BW system

Hi Gurus,

I'd like to know how to work the delta process of a custom datasource created on R/3 system with RSO2.

I know the delta works with a data or timestamps fields.

I'd like to know if the user delete a record on the source system which value the datasource will send in delta to BW about the key figures???

Thanks in advance and best regards,

Domenico.

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jan 19, 2008 at 02:50 PM

    Hi,

    I am affraid that a deleted record won't come at all since the generic delta selects all records having a timestamp greater than the timestamp (- safety lower if any) of the last delta load...

    If the transaction (process/user) would write a cancellation of the record to delete, that would work...

    The generic delta based on a field in a table is working when records are changed or added to the table...

    hope this helps...

    Olivier.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 19, 2008 at 03:12 PM

    Hi Oliver,

    Thanks for you quick answer!

    In your opinion the system could send nothing about a record deleted on the source system, but if a Key Figure has increased the value of 10 what's the record sent to bw in delta from the custom datasource in R/3?

    Ex:

    doc_num itm year qty doc_date

    10001 10 2008 5 10/01/08

    10001 20 2008 6 10/01/08

    What's happen if the qty value increase of 10 in both item of the document in the upload of the 11/01/08?

    Thanks in advance!!!!

    Domenico.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      in your example you have the following:

      doc_num itm year qty doc_date timstamp

      10001 10 2008 5 10/01/08 20080118

      10001 20 2008 6 10/01/08 20080118

      You extract your delta, the two records are provided as above.

      Now a process is executed today and this document is changed; it will depend of course of how this process is implemented...

      In the simplest case, an update of these two records is performed:

      10001 20 2008 5 10/01/08 20080119

      10001 30 2008 6 10/01/08 20080119

      You extract your delta again, you'll get the two records as above... In this case, your generic delta needs to be maintained with the option "new status for changed records"...

      Case #2: the process posts a delta in the source table (unlikely...)

      10001 10 2008 5 10/01/08 20080118

      10001 20 2008 6 10/01/08 20080118

      10001 10 2008 5 10/01/08 20080119

      10001 10 2008 6 10/01/08 20080119

      In this case your generic is an additive delta...

      Case #3: the process posts a delta in the source table (unlikely...)

      10001 10 2008 5 10/01/08 20080118

      10001 20 2008 6 10/01/08 20080118

      10001 -10 2008 5 10/01/08 20080119

      10001 -20 2008 6 10/01/08 20080119

      10001 20 2008 5 10/01/08 20080119

      10001 30 2008 6 10/01/08 20080119

      again, additive...

      Please keep in mind that the generic data sources are based on data stored permanently in the tables in contrast to LO DataSource ...

      With LO, when a process is changing a document for an active extract structure, the system will write the records like in the case #3 for instance; it depends on DataSource and the logic of the application; if a document is changed most of the sources will provide a cancellation of the document before update as well as the new version of the document so that it could be posted in BW...

      In your case, it depends on the process writing in this table... Usually you'll post this generic data in an ODS/DSO in BW. It will be the ODS/DSO generating the deltas to be posted to your cubes...

      hope this shed light on your issue... otherwise please explain a bit further what are you trying to achieve...

      Olivier.

      Edited by: Olivier Cora on Jan 19, 2008 4:36 PM

  • author's profile photo Former Member
    Former Member
    Posted on Jan 19, 2008 at 04:00 PM

    Thanks again Oliver for the quick answer!

    So to have something like the field Rocancel we need to write ABAP, else the datasource send to bw only the new value updated!

    In this case in the ODS arrives the record in overwrite mode and the ODS in Delta which and how many values send to the cube???

    Thanks in advance for your answers and your time,

    Domenico.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      it depends on the way the key figures are updated; overwrite or addition...

      Usually when a key figure has an update of addition you get a cancellation of the active record (record mode = X) and a version of the new record, e.g.:

      you have the follwing active record:

      Doc Qty ....

      10001 10

      You load now

      10001 20

      Since Qty is additive, your active record becomes:

      10001 30

      your change log will provide

      doc qty recordmode

      10001 -10 X

      10001 30

      hope this helps...

      Olivier.

  • author's profile photo Former Member
    Former Member
    Posted on Jan 21, 2008 at 09:03 AM

    Hi Oliver,

    Thanks a lot for your answers!!!

    So a custom datasource send to BW records in addition mode (without rocancel information and no information about deleted records) instead between ODS and CUBE there is 0RECORDMODE that send the informations about modified records!

    Have I understood the flow?

    Thanks in advance and best regards,

    Domenico.

    Add a comment
    10|10000 characters needed characters exceeded

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.