Recently read a Q&A about SD ODS in SearchSAP.com:

Q:Where is the logical breakdown of ODSs? We have one standard SD InfoCube we are planning on using. Later, we will add FI, PP, MM and InfoCubes. What is the best way to architect this so that using the InfoCubes and ODSs do not affect performance?

For SD, there is also a need to drill down to the line item level if and when needed.

A: Before creating the Cubes and ODSs for SD, I would advise you to check the Business Content InfoCubes and ODSs provided by SAP. In most cases these cubes will be sufficient for the reporting. You might be able to use these cubes and ODSs by doing the necessary customization.

If you are not able to use these cubes, you may check the design approach SAP has used to create these cubes. You may notice that all of the cubes contain summary level data and that ODSs contain document level data. Then you may follow the same method.

Personally, I do not think SAP content can fully satisfy your business requirement of SD. However, you still can use part of it, like in our project. We used 2LIS_13_V_DITM, then own ODSs -> ODSs -> Cubes. As the Answer said, ODSs provide item level data, then summarize in Cubes. The structure is like below:

 1st ODS                    xxx1

                                     I I

                                    I     I

 2nd ODS          xxxx2     xxxx3

                             I   I         I    I

                           I      I        I        I

  InfoCubes    ccc1  ccc2  ccc3  ccc4

For this kind of data model, there is one issue which is how to repair data at one side only. Here is the story:

Once we found that data in ODS (xxxx2) is not correct, and we planned to re-init only from ODS xxxx1 to ODS xxx2, and then to Cubes ccc1 and ccc2. Below are the steps to do that:

1. Transfer all! new deltas from ODS xxx1 to xxx2 and xxx3;

2. Take care that NO new request is activated in ODS xxx1;

3. Delete data in xxx2 and then Cubes ccc1 and ccc2;

4. Make a Repair FULL upload from xxx1 and xxx2;

5. Delete in the Init-InfoPackage from ODS xxx1 to other ODSs in the delta administration (Menu ->Scheduler/Init selections..)
6. Make an Init-simulation w/o data transfer with this Init-InfoPackage from ODS xxx1 to ODS xxx2 and ODS xxx3.

Then the next delta which will be created by ODS xxx1 will again move to both ODSs in next level and the data in both ODSs should be OK (then of course you also must activate the repair-full and the Init-simulation in the ODS xxx2 and transfer this to the 2 Cubes...). 

Please be careful, it MUST be a REPAIR-FULL (the flag can also be set in the menu of the scheduler menu, scheduler -> Repair Full Flag). If it is a normal FULL then the data in ODS xxx2 can not be activated. And you can NOT only initialize the ODS xxx2 alone, otherwise the next delta CAN NOT be activated in DOS xxx3; because then the latest Init won't be in ODS xxx3. 

Enjoy your SD ODSs!