DataSource-Transport in R/3 does not work

Question

Hello everybody,
we're currently having some trouble with transporting DataSources in the SAP R/3 out of the transactions RSA6 (for standard DataSources) or RSO2 (for generic DataSources).
system environment:
We're using three R/3-Systems (deployment, integration and production) and two BI-Systems (deployment/integration as one and production) with the folowing connections:
BI-production <- R/3-production
BI-deployment/integration <- R/3-integration
nothing <- R/3-deployment
This problem only occurs in the R/3-deployment-system.
problem:
Usually a transport request pops up if you edit a DataSource. In our case nothing happens. We can transport the ExtractStructure without any problems. But the DataSource itself cannot be transportet. So we have to do every single change in the R/3-integration-system again. This is leading to the issue that the two elements of a DataSource (the ExtractStructure and the DS itself) have two different original-systems.
Thanks for your help and kind regards
Sebastian.

Answer 1

Maybe its helpful to say that the key-problem is that the system doesn't create an a-version (object type OSOA) of the DataSource.
If you activate a content-DS in RSA5 you normally add an a-version of the DS to the already existing d-version (object type OSOD) of that DS. And if you create a generic DS you normally also create an a-version of that DS.
In our case that doesn't happen. And that's the reason why we cannot transport the DS.
But - as I sad - this problem only occurs in our development-system.