How to model ABAP classes in a correct manner?
I'm creating a conceptual design for an ABAP Objects program. The program should collect some data from standard tables like VBAK, VBAP, etc. (SD environment) in one flat structure/table, calculate some characteristic numbers for each dataset and finally write the datasets to my own flat DDIC table.
This program should run every day as a planned job. There are some hundred up to 5000 datasets to be collected by my program every day...
Now the question: Is it an usual manner to model a ABAP class representing one dataset. Every collected dataset would be represented by its own object at running time...
I hope there are no performance issues!!