Question:
We created a transport request using transaction RSA1->Transport connection, by selecting our InfoCube with the option of collecting all objects before and after.
We see all our objects in the transport request -- a good sign.
But when we actually transport the request to QAS, only a few of the objects were transported successfully.
For example, only the InfoCube and one or two infoObjects made it to QAS, but we are are missing all other InfoObjects, InfoSources, InfoPackages in QAS.
We received errors such as "InfoObect 0SALESORG (IN COMPOUND OF CHARACTERISTIC 0cust_sales) not active or available in the transport error log.
Also we had previously created a source system in QAS.
Does anyone know why when we specified all objects before and after the cube, that all objects were not transported.
Several forum participants have suggested transported each InfoObject individually. While this make work, it strikes us very burdensome.
Answer:
Let's take a simple sample :
Infoobject A has as attribute infoobject B.
Both A and B are in the same transport and not yet present in QAS.
If A is "transported" and "activated" before B, he will complain about the fact B is not present and stop further actions.
At this time, A will be present in QAS but not active,
and B may even not be present in QAS because of the stop.
This sample is applicable for each and every component linked to another : infosource needs all its infoobject to be present and active before being able to activate himself.
That's why we (we, as I am one of those telling not to use 'before and after' option, at all, any time, never) suggest to do it piece by piece.
For your current transport, you may try to re-import it a second time to see wether it goes further, this trick sometimes work, seldom ; especially when it is the very first time you transport a whole project.
Good luck
Ch