Transport Error: Referenced characteristic 0BPARTNER not (actively) availab

[Former Member]

Hi SAP BI/DW Community,

Thanks for an excellent forum and impressing contributors.

I am experiencing a transport error from Dev to QA.

0bpartner is enhanced with a few Z fields as attributes. The development/config works fine in Dev. client. When transporting 0Bpartner to QA the transport fails with return code 8. In QA SE11 after the transport the /BI0/PBPARTNER table shows status as "partially active".

A subset of the error message in the transport log is:

"....

Structure change at field level (convert table /BI0/PBPARTNER)

Structure change at field level (convert table /BIC/PZXX)

Structure change at field level (convert table /BIC/PZYY)

...

Table /BI0/PBPARTNER could not be activated

Table /BIC/AZXXX could not be activated

Table /BIC/PZYYY could not be activated

...

Following tables must be converted

DDIC Object TABL /BIC/SZXXX has not been activated

Error when activating InfoObject ZXXX

DDIC Object TABL /BIC/SZYYY has not been activated

Error when activating InfoObject ZYYY

"

The infoobjects are clearly not activated in BWQ after the transport.

What I have done to remedy this so far:

- I have adjusted and forced conversion in SE14 in Dev. I would like to avoid doing this in QA.

- Transported the Z fields ahead of 0bpartner but it still fails.

My understanding is that since the Z infoobjects fail to activate in QA they cannot be activated as attributes for 0bpartner in QA and 0bpartner subsequently fails to activate, ending up as "Partial Activated".

Does anyone know how to remedy this? Thanks for any comments and guidance.

Regards,

M Petter.

[Former Member · Accepted solution]

Hi Petter,

I faces same kind of issue. I just reactivated all the Z-infobojects and transported them first. Once this transport moved successfully, I transported reactivated standard object. It worked for me.

Let me know if you still have issues.

Regards,

Rohit

[Former Member · Accepted solution]

Thanks for your input.

It turnes out our standard content infoobject has been assigned to $tmp by an accident. I've got a thread following this topic: