Question:
Hi Fans,
I have a problem when deleting my ZBILLODS.
I get 4 error "Object directory entry cannot be deleted, since the object is distibuted."
Error when deleting objects from TADIR.
For objects
ISTD 8ZBILLODS " InfoSource Transaction Data
ISCS 8ZBILLODS " Communication Structure
ISTS 8ZBILLODS " Transfer Structure
ISMP 8ZBILLODS " Transfer Rules
I was able to dele the last 3 by deleting the transfere rules, transfer structure and comunication structure.
But I cannot delete the entry ISTD 8ZBILLODS, no error I just don't know where.
Any one knows what to delete to remove the entry in TADIR ?
_________________
Rasmus ;o)
- One small step for man, one giant leap for mankind
Answer:
you might try the following:
1. Put it in a transport request first before trying to delete it. Once it's captured in the request, try to delete it.
2. Change the development class... that sometimes works too
cheers,
El Belgio
Answer:
Original the four object was in the $tmp package so i had to change the object directory entry to our package ZBW0100.
So i got all entrys in my request.
Modifiable
BWTK907822 RAS.EXT R1 - Delete ZBILLODS
BWTK907823 RAS.EXT Development/Correction
Communication structure
8ZBILLODS
Transfer Rules
8ZBILLODS BWT200
InfoSource transaction data
8ZBILLODS
Transfer structure
8ZBILLODS_AA
When i delete the transfere rules, transfer structure and comunication structure, I can't change the object directory entry under the infosource any more, except for ISTD.
_________________
Rasmus ;o)
- One small step for man, one giant leap for mankind
Answer:
Ok, so what's actually left in the Administrator Workbench now?
El Belgio
PS Do I understand you correctly in that you changed the development class right before deleting? Sounds pretty weird... 'cause if it was still in $TMP it means you could have deleted it without a request (after all, it had never been transported)
Answer:
InfoProver: The ODS is still there, but no update rules and no infoset's, the queries still show up when i try to delete the ods.
InfoSources: The infosource is stil there but it is inactive, because it has no comm structure, transfer structure and no transfer rules.
PS Do I understand you correctly in that you changed the development class right before deleting? Sounds pretty weird... 'cause if it was still in $TMP it means you could have deleted it without a request (after all, it had never been transported)
Yes that is correct, but the objects have been transported but long time ago when we were BW 1.2. The object are also on our Test and Production systems, but also in $tmp.
_________________
Rasmus ;o)
- One small step for man, one giant leap for mankind
Answer:
If i look in TADIR i can see that the ISTD has a 'S' as CPROJECT.
F1 says.
Identifies distribution status of an object at SAP
Possible values: L (Local) Object was not yet transported.
S (Distributed SAP) Object was exported at least once.
_________________
Rasmus ;o)
- One small step for man, one giant leap for mankind
Answer:
InfoProver: The ODS is still there, but no update rules and no infoset's, the queries still show up when i try to delete the ods.
that's normal behaviour... you need to delete the queries first (it should actually give you that option)
InfoSources: The infosource is stil there but it is inactive, because it has no comm structure, transfer structure and no transfer rules.
I think it might still be there because of the existing ODS... however, I'm not 100% sure of that. Is your ODS empty?
Anyway, if you can't delete it after you deleted the ODS, you need to find the tables in which there is still an entry for this InfoSource (through debugging - put "/H" in the command field and try to delete the InfoSource again, now you're in debug mode though)
cheers,
El Belgio
PS it can't have been transported... it was probably just braught over via a system copy
Answer:
(it should actually give you that option)
It does, and I says delete but they never get deleted.
I think it might still be there because of the existing ODS... however, I'm not 100% sure of that. Is your ODS empty?
The ODS is empty.
Anyway, if you can't delete it after you deleted the ODS, you need to find the tables in which there is still an entry for this InfoSource (through debugging - put "/H" in the command field and try to delete the InfoSource again, now you're in debug mode though)
There is no way to delete an InfoSource.
_________________
Rasmus ;o)
- One small step for man, one giant leap for mankind
Answer:
There is always a way... trust me! I've done it before.
Hey, I wouldn't mind taking care of that myself on your system... haven't been in Copenhagen yet
Shall I give you my boss' number?
Answer:
Of course there is a way, but i don't think that it is a SAP way...
Did you do it by deleting all entries where it is mentioned, and there by just removing its exsistens. Throgh some ABAP or what.
Do you think it would be possible just to delete the entry in TADIR.
And the try to delete the ods ?
Shall I give you my boss' number?
I don't think we have come to that yet
_________________
Rasmus ;o)
- One small step for man, one giant leap for mankind
Answer:
Now i think I've tried everything.
I couldn't even change the S to and L in TADIR through an ABAP.
In the code is was ok, but when i debuged it wouldn't recognize TADIR as a table. It said it was a field.
So i got sy-subrc = 4
I tried to delete R3TR ISTD 8ZBILLODS from TADIR throgh SM31.
But i got "could not delete the entry because the object exsists."
So, it would be really helpfull if you (or anyone else) could remember how to delete an infosource.
_________________
Rasmus ;o)
- One small step for man, one giant leap for mankind
Answer:
Wow, hold your horses!!! You can't just go around and change entries in TADIR unless you are really sure what you are doing!
Listen, it's very hard to just give you information without having the specific situation in front of me. And since I assume you're not too familiar with debugging and changing table entries, I'm not even going to try and post options here. SAP does not support this kind of stuff anyway and there are way too many people on this forum that might just "try"these things and totally mess up their system.
I suggest you check it out in debugging (or have it checked out by someone who is more experienced - no offence by the way) or post it on OSS (but that one's going to cost big bucks).
Cheers,
El Belgio
Answer:
Ok, El Belgio.
Thanks for the effort, i'm gonna try posting it on the OSS.
_________________
Rasmus ;o)
- One small step for man, one giant leap for mankind