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

Delta behavior for setting flag on DSO and Info Cube

Hello Experts,

I have a scenario for reporting where I have to set flag for certain data, Consider I have an installation number and that installation have multiple operands,

And I have to set flag for Installations where Operand is "ZABC". I will check for operand "ZABC" into installation 112233 and set flag 'X' into a flag field.

for e.g. If installation 112233 have 20 records and any of them have operand "ZABC" then it should set flag 'X' for all 20 records.

let's say I extracted an installation from source system and 10 records came into BI and none of them have "ZABC" hence no flag set,Problem is later I did delta and 5 records came and one of which have operand "ZABC" for same installation at that Time only five records will set flag 'X' what about other 10 which are in DSO.

what should I do, shall I re model my data flow? or any suggestion that I can overcome flagging issue on delta ?

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Posted on Sep 08, 2013 at 03:06 AM

    Hi Gupta,

    As you said first 10 records don't have operand as 'ZABC' then why are you worrying about them.

    You need to check at source system how the respective installation have values of operands? then only you can take action accordingly.

    As my guess during first time load same installation don't have the operand as ZABC. for next loads source team may changed to operand value to ZABC for the same installation.

    First check at source system side and later think about bw side.

    When we load data from DSO to Cube(BW 7.x setting at DTP level)

    Full load - Always need to load from Active table

    Delta load - always need to load from Change log table


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 08, 2013 at 04:31 AM

    Hope you have written some routine to update flag. You need to enhance your code to update flag for all entries for a particular installation num when any of the operand is ZABC.

    Are you an ABAper too? Otherwise, ask an ABAPer to write this simple logic. It is not complicated one.

    You should have a Flag field in your Infoprovider. SO this column should be filled whenever the installation num meets the above logic.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 08, 2013 at 07:12 AM


    You need to include an field routine to have the Flag gets populated as per the required logic for installation number. Would simply include may be something like below in field routine

    If source_field- Operand = "ZABC".

    result = 'X'.

    else .

    result = ' '.

    Something like that can be done taking into consideration it would run for all the installation number.

    You have to delete and reload data to have the Operand updated for previous records.


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 08, 2013 at 11:56 AM


    I assume your keyfield in dso are installations and operand. Your DSO contains the flagfield which you feed with the logic:

    IF SOURCE_FIELD-operand = 'ZABC'.

    RESULT = 'X'.


    RESULT = ' '.


    Now every installtion with operand ZABC will get a flag X. Later when the delta request contains a installation with operand ZABC it will flag them and overwrite the existing record which had no flag as your key is installation and operand.

    hope it helps


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Just adding to Martin's reply:

      It is NOT necessary that "Installation" or "Operand" have to be DSO Keys for this to work.

      Say your key is 'Machine Number" ....and "Installation" and "Operand" are data fields in DSO. If for the same Machine number, "Installation" OR "Operand" value changes, it will still overwrite the same machine number record in target DSO with new values of Installation and/or Operand. It will also generate Delta records correctly in change log table so that this data can be further updated to targets.



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.