yes,for some reason i can’t import master data infoobject that is having only text infosource .I can import master data infoobject having both text and attribute .
if infosource has only text then i can’t import…
other issue i found today on extractors…i can see extractors with text datasource but they are disabled.i can import extractors only attribute data sources .
Ah, did reminded me of something. Can you please double and triple check that transfer structure and everything else is actually activated(!) in BW. I have seen interesting combinations, where a transfer structure was activated but the underlying InfoSource was not or the other way around, things showed as activated but after activating them another time it worked. I don’t believe it is related to attributes, text or something like that.
Did you get any further with this? We are encountering a similar error (we are on DS 4.0 SP02 and BW 7.0.1 SP8).
The connection works fine when attributes and text are set up in the InfoObject, however when only text is set up the InfoSource metadata can’t be imported in BODS.
This works fine in the previous DS 3.1 installation we have.
We are about to upgrade our SAP BI System from 7.x to 7.3
We use DS 3.2.0.0.0 - well, simply 3.2 without patches or anything else.
Right now everything runs fine for our 7.x and 3.2 systems.
I have jobs that receive data from BW, and the other way round, Jobs that send data to BW.
Now, as we have this testing environment with BW 7.3 and DS 3.2 I was able to get jobs running, that receive data from BW.
But, when I try to setup a job the other way around, I created (successfully) a new Datastore pointing to our new 7.3 system.
When I then open that datastore and try to import the transaction transfer structure - I can see those structures, but I cannot import them - as I receive the same errormessage as mentioned in this thread.
I have checked the transformations as suggested, (re-)activated them although they were already active - Still I get this BODI-1112339 error.
I cannot find anywhere any real solution - does anyone of you experts know anything that will help me?
So, the installation was succesful and I managed to import the transaction communication structure into DS 3.2(version 12.2.0.0).
When I ran the job, the next error occurs: The Infopackage in BW cannot be adressed - or rather - 0 rows are transmitted.
One day later, DS told me that the communication structure had changed and I need to import it again.
And - interestingly - I cannot import structures (meta-data or transactional) anymore…I have the initial errormessage again.
So I checked the ZAW0 functions - checked the ABAP syntax…and it doesn’t work (the code is erraneous).
Therefore - I must conclude that DS 3.2 (with the initial version 12.2.0.0 - no support package) is definitely NOT compatible with NW7.3