Delete Append Structure from BSEG

[Former Member]

Hi,

One of my colleagues appended a zstructure in BSEG table and deleted the same. Now the table is partially active. Due to this most of the SD transactions ends up in dump. When I tried with SE14, I found the newly created (and deleted) structure's fields are in use in view V_QCMBSEG. Due to this adjustments using SE14 always fails. How can I solve this issue?

[Former Member]

Hi,

One of my colleagues appended a zstructure in BSEG table and deleted the same. Now the table is partially active. Due to this most of the SD transactions ends up in dump. When I tried with SE14, I found the newly created (and deleted) structure's fields are in use in view V_QCMBSEG. Due to this adjustments using SE14 always fails. How can I solve this issue?

[archanapawar]

Hi Ahamed,

You just have to use transaction SE11 and enter the name of the appended structure that you wish to remove.

Press the delete button to delete this particular structure. The system then prompts you that it will reactivate the object that you appended the structure to.

This solves the problem.

[Former Member]

Thanks for the reply Archana,

The append structure is already deleted. Still I tried your suggestion, but the message said 'ZZBSEG does not exist' (ZZBSEG is the append structure's name). But it is still visible in BSEG table but not in Append Structure dialog (F5). And the fields of ZZBSEG are in use in V_QCMBSEG.

[archanapawar]

Now, your append structure is deleted, are you able to adjust BSEG using SE14?

[Former Member]

No. It says the fields from ZZBSEG is in use in V_QCMBSEG in the error log.

[archanapawar]

There is a function module DD_APPD_DEL to delete the append structures. Try using this FM.

[Former Member]

I tried with DD_APPD_DEL with parameters APPEND_NAME = 'ZZBSEG' DEPENDENT_NAME = 'BSEG'  DEL_STATE = 'A'. But it returns 8. It does not do anything to the table/view. Is there any alternative solution?

[matt]

It is not advisable to use these low level function modules for database changes. The risk of messing things up is too high.

You need to talk to your basis team. The table probably needs fixing at a db level. You may also need to raise a message with SAP.

[archanapawar]

Try to recreate the structure and activate BSEG and then repeat the procedure, see if it works.

[Former Member]

Objects with a name like *QCM* are used in the table conversion process. I'd say something went wrong there. If I were you and this was my system, I'd rather not mess things up further but call in the cavalry (SAPnet message). This should not have happened and needs to befixed, preferably without breaking the entire system.

[Former Member]

Thanks for the advice Volker. I shall look into it.

Thanks every one.

[Former Member]

Did you try using SE14 utility with this VIEW as well ?

I guess it should solve.

I had faced a very similar issue and SE14 helped me out.

So give it a try .

[Former Member]

Unfortunately V_QCMBSEG can't be manipulated using SE14, Sijin.

[Former Member]

Okay .

[karthik_snair]

Hi,

How you have achieved this.

I am facing the same issue now.

Please let me know how fixed this.

Thanks,

Karthik.S

[kiran_k8]

Matt,

I had gone through similar kind of threads many times.Isn't there are any SOP which is considered as SAP Best practice in terms of append structures and their activation.Basically,I want to know if there is a way through which we can avoid these kind of issues while adding append structure.To my knowledge sometimes it is beyond a developer's knowledge as we are not sure when it works and when it doesn't.(when it doesn't we need to seek the help of Basis team).

K.Kiran.

[matt]

Normally adding append structures works.That's the SOP. When it goes wrong (which is rarely, in fact), then something has happened at the database level - then you need a DBA to fix it. Or as I say - open a call with SAP. If something like adding append structures is going wrong it means a problem with a database or the SAP software itself. This is not something a developer should ever address.