0CALDAY as a key field

[Former Member]

Hello All,

I made some changes to tansformation for calculation of some keyfigures from one DSO to another. The changes were calculating the keyfigure correctly. But in the target DSO the 0CALDAY is selected as a key field, due to which the records from the past are getting deleted. How can make sure that the deletion doesnt happen.

Thanks in advance.

Regards,

NK

[former_member324993]

About for DSO do delete or select which record will delete it,You use the 0recordmode select it.if 0recordmode = 'D',then the record will delete it.

[Former Member]

Hi,

Addition of extra key field will not delete or overwrite any records from the DSO for eg. if you have A,B, C as key fields in source and in target you have A,B,C & date then in target you will have more records in target DSO than source.

Give more details about your scenario, If you are loosing some data then you might be missing some field from key field.

Regards,

Durgesh.

[Former Member]

Hello All,

The changes to the calculation of keyfigures has a negative values on different dates in the past. Because 0CALDAY is a keyfield in each data set. So values should not be changed in the past because of different 0CALDAY values.

Please inform how can this be done.

Regards,

NK

[former_member182470]

Hi,

After you made the changes to your base DSO with a new date field(0calday), the subsequent data in target DSO is getting changed as per your post.

If you feel everything is OK in base DSO, please drop the contents completely from the target DSO and upload again from your base DSO. This should knock off the inconsistency between the two DSOs.

Regards,

Suman

[KulDeepJain]

Hi Nike,

Please make sure what should be the fields for this DSO, Bcz DSO should have key-fields by which we remove duplicate.

Else describe what were previously structure have DSO and what calculation you are doing so I can do somewhat better for you.

[Former Member]

Hello,

Any one has some reply to this?

Regards,

NK