T000 record deleted after deleting Ztable record on SE16 debug

[Former Member]

Hi

We're facing a situation where, after using the debug for changing the SE16 tcode to DELE to delete a Ztable record, it automatically deletes also the client record from the T000 table.

The SE16 debug is not the official way but I know it is largelly used, so I wondered if anybody has faced the same problem and, most important, the reason for the client deletion.

I appreciate the help.

Regards !!!

[Former Member]

Is the Z table actually a view?

Rob

[Former Member]

No, it's a Transparent Table.

[Former Member]

Hi Fabio,

your problem is really strange and a little bit unbelievable. I do not know how to avoid client deletion, but you can try transaction SE16n, instead of SE16. There you can use a different trick.

1.) Go to transaction SE16n. Enter the name of table which you want to edit.

2.) In the command field type u2018&SAP_EDITu2019 and press enter.

3.) Press F8 and you will see records and you will be able to edit them, delete them or add a new records

4.) On save button, changes will be written to DB

Regards,

Adrian

[Former Member]

Thanks. I know this is not easy to believe, but it's the second time it happens only in one specific environment. So it must be something on this environment.

I know other tricks to the delete records but I'm really trying to explain why the client was deleted from T000.

I appreciate the help anyway.

[Former Member]

What are the details of the foreign key relationship of the client in the Z table.

Rob

[Former Member]

It checks the verification table on field MANDT (T000) .

The screen check is required with no error message related.

and the semantic attributes are marked as "not specified" (no cadinality).

[Former Member]

Hi Fabio,

I faced the same problem, we opened a message at SAP to get some response about this issue.

[Former Member]

OK. Please, let me know once you have a reply.

Really appriciate the help.

Tks

[Former Member]

Ok, I'll.

But just to let you know, We add the entrie in the table T000 and the environment is OK.

[Former Member]

Hi Ricarod , We have faced the same issue as well. Please provide me the OSS # once you get it.

Edited by: Basudeb Datta on Apr 15, 2010 10:23 PM

[Former Member]

Hi,

SAP said that this isn't a STANDARD scenario, so they didn't give us a solution.

What we did here, was to create the entrie directly to the table t000 to represent the mandant, and it worked well.

Best regards.

[ioan_radulescu2]

Hi,

Same problem here. It was really painful to find out what I did at all, because I had no recollection of doing anything in that direction. I checked with function DBLOG_READ_WITH_STATISTIC which  entries I have changed. It was fortunately only T000. After running ST03N to check what on Earth I did (my name was in the log as the one who deleted the client), I saw that I was until time xx:xx:43 in se16 for my z* table and then starting at xx:xx:44 till xx:xx:59 i was in se16 for table T000. Except that I wasn't. It was weird that for my table work in ST03n was still shown having sent FCODEs but the T000 was shown with no FCODE whatsoever.

So no more se16 for me, this is really unbelievable - this worked for almost 20 years. I would actually expect that this situation also could happen without debug, after all we're just simulating clicking buttons in debug.

Kind regards,

I.

[Former Member]

Hi,

I faced the same problem today.

I created a Z-table type transparent. Mandt was one of the key fields in the table.

in SE16 debugging I deleted 2 records from the table.

in one of them was a record where only mandt was filled and all other fields were empty. Being it an invalid record I deleted that record.

but to our surprise, client entry got deleted from T000 and it is showing my user id in the log.

Please help to find out the problem.

Regards.

Sanchari

[gokul_radhakrishnan3]

Hi,

This happened one or two times in our company also. But the reason was mainly around the 'Check table' button in SE16. So when you change the OKcode to 'DELE' and when you press 'Check table' button by mistake instead of 'Delete record' button, it looks like it deletes the check table entry. In this case, since ur cursor is in CLIENT field, it deletes the T000 entry. But this is what we understood based on the details we were told by the person who did that. Since we didn't want to repeat it again we assumed that this is the reason. So this may not be 100% true.

With regards,

Gokul

[Former Member]

Hi Gokul,

Thank you for your response.

It is appreciated if anybody else also share their views on the issue.

Regards.

Sanchari