Help with Aggregation Summation into DSO

[sap_cohort]

Hi, I have a question about Key Figure Aggregation Summation in transformation rules into a DSO from 2LIS_11_VAITM.

Currently had an old order for Order Qty of 600 pcs. Recent request came in to change it to 400. After Delta our Order Qty was -200. The Rule is for Summation and I figure it should work like 600 + -600 +400 = 400, but that is not what happened. It's almost like the rule considered the original order qty to be 0 and when the -600 and +400 delta came in they get summarized to get the -200. Does it have anything to do with the change logs only having recent last 30 days available?

Can anyone tell me what is wrong here?

[former_member188011 · Accepted solution]

Hi Kenneth:

Please refer to the Weblog "How does a datasource communicates "DELTA" with BW?" by Swapna Gollakota.

/people/swapna.gollakota/blog/2007/12/27/how-does-a-datasource-communicates-delta-with-bw

Regards,

Francisco Milán.

[sap_cohort · Accepted solution]

Thanks, I did read over the blog, but it doesn't seem to help out with my problem. Does anyone have any idea why this might be happening? Thanks

[former_member188011 · Accepted solution]

Kennet:

Could you please provide more details? For example:

- Is the problem (differences on the Key Figure values) at the DSO level or at the Cube level?

- Does your DataSource version have DSO capability? (please refer to SAP Note 440416 - "BW OLTP: Correction report for change of delta process").

- If your DataSource supports "ABR" extraction, Does the Data on the PSA looks ok? (After / Before and Reverse images).

- Have you enhanced the DataSource to include Custom Fields? If so, Does the ABAP Routine uses the SORT command?

- Do you update the DSO with the 2LIS_11_VAITM DataSource only? or Do you use another DataSource to send data to the same DSO?

- Have you considered changing the Rules to "Overwrite" instead of "Summation"?

- What fields are included as part your DSO Key?

- Do you have the ROCANCEL field mapped to 0STORNO / 0RECORDMODE InfoObjects?

Regards,

Francisco Milán.

Edited by: Francisco Milan on Jul 1, 2010 9:13 AM

[sap_cohort · Accepted solution]

1. The Problem is as the DSO KYF Level.

2. ABR, but the PSA has been cleared out.

3. Don't want to change yet to overwrite as some other calculated KYF (I think)

4. ROCANCEL is not mapped! I just checked and this is not mapped... I see lots of SDN thread time related to this so it's hard to get a good answer. Would this be causing the problem? It doesn't see to be a large problem all of the time.

Let me know what you think... Thanks

[former_member188011 · Accepted solution]

Hi Kennet:

My recommendations

1. Use "Overwrite" instead of "Summation".

2. Map the ROCANCEL field.

3. Make sure your DSO Key Fields are defined correctly.

4. In case you have ABAP code on DataSource enhancements or Start/End/Transformations/etc Routines, make sure the After/Before/Reverse images arrive in the correct order (when using the SORT command the original sequence can be affected).

5. Delete the contents of the PSA/DSO.

6. Reload the PSA, and afterwards reload the DSO.

Regards,

Francisco Milán.

[sap_cohort · Accepted solution]

Thanks for the detail...

Shouldn't "Summation" work as well as "Overwrite" when using ABD?

Thanks

[former_member188011 · Accepted solution]

Hi Kenneth:

Either "Summation" or "Overwrite" should work when loading data to DSO, however, I prefer using "Overwrite" because I have the advantage of using the "Request Full Repair" option.

Regards,

Francisco Milán.

Edited by: Francisco Milan on Jul 1, 2010 10:11 AM

[sap_cohort · Accepted solution]

I think Summation or Overwrite will work fine as long as Record Mode is Mapped. Of course in our case Record Mode is not mapped.

Here's what I'm thinking is happening, let me know if I'm going down the wrong path please:

+630 Original Qty in DSO

+449 Changed Qty

-181 New Value in DSO (INCORRECT)

Change Records Generated

-630 "X" Before Image

+449 " " After Image

Because 0RECORD Mode is not mapped you really have

-630 " " After Image

+449 " " After Image

If you aggregate these before update you have

-181 " " After Image

Now I suspect that "Summation" does not really work/matter for this situation (ABR) so the -181 just gets updated as the After Image.

[former_member188011 · Accepted solution]

Hi Kenneth:

Yes, that logic makes sense, I think you nailed it, mapping the ROCANCEL field should solve the problem.

Regards,

Francisco Milán.

[sap_cohort · Accepted solution]

OK, I booked some orders in dev and the problem does not seem to occur. so I am at a loss whey this might be happening. I will have to watch for the condition to occur again so i can review change logs... thanks!

[sap_cohort]

OK, I booked some orders in dev and the problem does not seem to occur. so I am at a loss whey this might be happening. I will have to watch for the condition to occur again so i can review change logs... thanks!