/SAPAPO/RTSCOPY Key Figure 'Add Data'

[former_member717176]

All, I have used the program /sapapo/rtscopy to perform key figure copies.

The program contains the option to select 'add data' in the key figure selection and this allows me to copy multiple key figures and to sum the values from those key figures.

I use this option rather than using a macro key figure copy because the TSCOPY respects the storage bucket values when adding data.

SAP have advised against using the TSCOPY and to instead use a macro...however as mentioned above this does not respect the storage bucket and when drilling into information from a monthly bucket down to a storage bucket results are inconsistent.

Anybody have an alternate solution?

Thanks

Chris

[Former Member]

Hi Chris

Can you explain what you meant by "does not respect the storage bucket and when drilling into information from a monthly bucket down to a storage bucket results are inconsistent."?

TSCOPY acts at the storage bucket level directly and everything you do is at the lowest level of that periodicity in storage bucket.

The same thing with a macro works at planning book/Data view's ticket bucket profile.

These two above, macro and TSCOPY, are the only two most common and easy ways of doing a sum of keyfigures. I always prefer TSCOPY though for performance reasons and ease of use. Macro way is difficult to change and the exact same thing in TSCOPY take almost double or triple the time to finish up  in a batch job.

I don't know any other way of adding keyfigures, out of box in DP. Would be interested if any one else in this group knows.

Not sure I answered your question but if you can explain what you meant by the ""does not respect the storage bucket..." with an example, may be I can throw some light on it.

Thanks.

[former_member717176]

Thanks for the feedback.

My problem is that I need to sum two key figures into a third and to do this I want to use the TSCOPY with 'add data' selected.  This approach ensures that data is summed by storage bucket and means I have consistent results if I aggregate the time bucket or drill down to a storage bucket to review my data.

I encountered inconsistencies using this RTSCOPY approach to which SAP have responsded advising that the TSCOPY should not be used for adding key figures in DP. See quote below.

"/SAPAPO/TSCOPY was not designed to be

used this way. The values would not be

calculated correct since there

are sort statements that rearrange the KFs order during the execution.

So the KF values would be incorrect and add will

not work.

I kindly request you to use the macro for the addition of KFs.

This is

the correct way to perform what you expect."

SAP's own help documentation does not seem to place any such limit on the use of the RTSCOPY program,

The macro approach works just fine within a data view but then disaggregation rules determine the values stored at more detailed time buckets.  There is no summation at the lower levels just disaggregated values and so data is inconsistent.

Thanks

[Former Member]

Hi Christopher

The SAP's message is news to me. We have been using RTSCOPY for the addition in DP for the last 7-8 years and did not see any issues so far. Macros on other hand sucked in performance and are totally inflexible, needing IT team to make changes and transport.

Make sure you are not using any parallel processing profiles in RTSCOPY. Parallel processing hasn't been consistent so far, making the profiles useless.

I am not sure if I agree with SAP's statement. However it is SAP...so may be I am wrong.

"...disaggregation rules determine the values stored at more detailed time buckets"

Data is always stored at the lowest level ( characteristics in planning object structure) level. Whether you do the copy through TSCOPY or the macro, the disaggregation is defined at planing area level and so that disaggregation has to be same in both cases.

In TSCOPY, you specify aggregation level and the data is copied at that level, then disaggregated to lowest level.

In macro, you still have to specify a aggregation level in batch job and the data is copied at that level but saved at the lowest level.

I am not sure why there would be any difference. Just make sure the keyfigures being added are the same data type and aggregation level is same so that you can compare the macros Vs TSCOPY apples to apples.

Hope this helps.

[former_member717176]

I appreciate your help...I think we are on the same page with regards to the TSCOPY.

FYI my references to disaggregation in macros and TSCOPY are a reference to time based disaggregation.  I am happy that structural disaggregation is aligned.

I will close out this message.

Chris