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

Delta load for lookup DSO...

Hi gurus,

I have this delta scenario:

DSO A consolidates and look up records from DSO B and C to the target DSO X. My question: if there are deltas in DSO C, how are these reflected in DSO A?

A pseudo example:

DSO A: doc_id, item_id, amount

DSO B: doc_id, customer_id, delivery_add

DSO C: doc_id, contract_id, discount_rate

DSO X: doc_id, item_id, customer_id, delivery_add, amount, contract_id, discount_rate

Is it possible to trigger a lookup in DSO A if there are changed records in DSO C?

Could you please provide some info on this type of delta scenario?

Thanks in advance.

Regards,

Meng

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jun 30, 2011 at 09:58 AM

    Hi Meng,

    I can see DSO B, DSO C is like simple master data having docid as key if so load this data to docid master data infoobject (create one infoobject) Use this docid info object in the transformation from DSO A to DSO X , or you can use navigational attributes of doc id.This will solve ur purpose

    Or

    If you design DSOX in such a way , so that you can also create a mapping from DSO C, DSO B so that the changes are reflected. Otherwise you always need to do a full load in this case. In Worst case you can go for an infoset while checking the keyfgures multiplicity.

    Regards

    vamsi

    Edited by: vamsi talluri on Jun 30, 2011 3:32 PM

    Edited by: vamsi talluri on Jun 30, 2011 3:33 PM

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Vamsi,

      it's great that you have understood the scenario quite well 😊 Yes, I am getting and versioning some of the contract master data from DSO C. The reason why I did not go for time-dependent attributes was due to the huge amount of data. It would probably cause performance problem during reporting because I am getting 30-40 fields from DSO C and many are used for navigation / filtering in reporting. So the idea was to integrate the master data with transaction data.

      How would be the solution if time-dependent attribute is not an option?

      Another question regarding the changes in DSO B. There would also be changes or correction in DSO B as well as A which contain transaction data e.g. amount or type..These changes should be reflected in the consolidated DSO X as well...

      Regards,

      Meng

      Edited by: Joon Meng Goh on Jun 30, 2011 3:00 PM

  • author's profile photo Former Member
    Former Member
    Posted on Jun 30, 2011 at 10:12 AM

    hi,

    A pseudo example:

    DSO A: doc_id, item_id, amount

    DSO B: doc_id, customer_id, delivery_add

    DSO C: doc_id, contract_id, discount_rate

    DSO X: doc_id, item_id, customer_id, delivery_add, amount, contract_id, discount_rate

    In your Pseudo example as can be seen that the keys will be as follows:

    DSO A: Doc_id, item_id

    DSO B: Doc_id

    DSO C: Doc_id

    DSO X: Doc_id, item_id

    Now in your case you can create new transformation from DSO B & DSO C to DSO X so that independent Delta's can flow to the target. In the transformation mark only the values coming from source rest fields should be set to no update.

    In the transformations lookup at DSO A for particular doc_id and get its item_id and populate in the transformation.

    regards,

    Arvind.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 30, 2011 at 01:14 PM

    Hi Joon,

    You can acheive your requirement By Creating Intermediate Delta DSO "DSO D".

    Explanation: -

    Create DSO D, which will contain DOC_ID as key field and

    Date, Timesheet as Data field.

    Now your Design will be

    DSO A, DSO B and DSO C will feed the data to DSO D.

    and then DSO D will feed the data to DSO X.

    All load are delta load.

    Here between DSO D to DSO X transformation you can use expert routine, which will look up all three DSOs -

    DSO A, DSO B and DSO C.

    Benefit of above design,

    Well managed Data flow

    Well managed Delta capability

    Only 1 transformation has routine - So easy to maintenance.

    Easy for support, etc....

    Regards,

    Ashish

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Ashish,

      Sorry that I still need some clarification from you, since I am quite new to BI 😊

      You said:

      Create DSO D, which will contain DOC_ID as key field and 
      Date, Timesheet as Data field.
      

      Did you refer to current date and timestamp with "Date" & "Timesheet" mentioned above? So, DSO D will only contain these 3 InfoObjects?

      Now your Design will be 
      DSO A, DSO B and DSO C will feed the data to DSO D.
      

      Which data to be fed to DSO D? DSO C does not have doc_id and how can data records from these 3 DSO (A, B, C) combined via standard transformation without routine to DSO D?

      Here between DSO D to DSO X transformation you can use expert routine, which will look up all three DSOs - 
      DSO A, DSO B and DSO C. 
      

      Why expert routine? Is it because I can access source fields from the 3 DSOs?

      Could you please elaborate in more details for newbies like me 😊

      Your help is greatly appreciated!!!

      Regards,

      Meng

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.