ODS Installation from BC Error

Question

Hi,
We are trying to install ODS 0PY_PP_C1 from Business content. It gives me following errors .
1. "Error while Creating Export DataSource and dependent Objects"
2. "Data source 80PY_PP_C1 not maintained in BWSYSTEMNAME version A."
And we have tried with generating custom ODS as well ,but was not successful.(Same Error Messages)
We feel that somewhere there is default system setting, and system is taking source system as bw system itself instead of R/3 . So its trying to create export data source. But Generation of export datasource is not needed in our scenario.
Please let us know how do we solve above said issues.
Thank you.
Regards
Nimesh

Answer 1

hi,
take a look oss note 597326-Activating ODS: Error when creating the export DataSource. it should solve your problem.
note 597326
Activating ODS: Error when creating the export DataSource
Symptom
When you activate or transport ODS objects, the following errors appear in the log:
"The creation of the export DataSource failed". Message number RSBM 035
"Error &1 in function module &2". Message number RSBM 006
"Error when creating the export DataSource and dependent Objects". Message number RSDODSO 169
"Error when activating the ODS object &1". Message number RSDODSO 168
Other terms
RSBM 035, RSBM 006, RSDODSO 169, RSDODSO 168
Reason and Prerequisites
A characteristic involved is active but it is using new or inactive attributes.
Characteristics involved are all characteristics used in the ODS object.
Solution
Check all characteristics involved as described in the following:
Check the Compounding and Attributes tabs in the characteristics maintenance.
All characteristics here must be active. This is displayed by a green icon.
If this is not the case for a characteristic involved (a gray icon is displayed on one of the two tabs), activate the characteristic involved. This also activates the inactive dependent characteristics.
After you have checked and repaired all the characteristics involved as described above, the loading/maintenance of master data should work again.