How to delete field from CI_COBL include structure?

[himanshu_gupta13]

Dear Gurus,

I have include a field LCNO  in cl_cobl include structure which is in RKPF and assign it to the package of $temp. But now I want to delete this field from structure and want to make it like as before.

Kindly, please help me to short out this problem.

Many Thanks / Himanshu gupta

[Former Member]

You can delete the field directly if not used anywhere

since it is not in a package it will not ask for request.

But I suppose once you activate a CI - Customer include you need to keep one field always.

Similar is case when you activate the PO exits..... I suppose you will need to keep one field with DUMMY....

BR

[himanshu_gupta13]

Dear Sir,

I got your point, so should I replace that LCNO field with dummy field and activate it.

However, I assign it to $tmp, hence, will it not cause any problem in future.

Many Thanks / Himanshu Gupta

[raymond_giuseppi]

Is this the only field of CI_COBL

• Many tables and views use this Include, so you will most likely need to call SE14
• In some case creating a DUMMY or ZZDUMMY (to respect namespace) field can solve problem.

Which error message did you get, what did you try to do ?

Regards,

Raymond

[Former Member]

In which system you add field in ci_cobl? If it was only in DEV you could delete this field and after that you need call se14. CI_Cobl is used in a lot of CO and MM tables. Adding additional fields to this structure should be absolutely necessary.

[himanshu_gupta13]

Dear Gorgori,

It is in DEV only but I added only single field in it LCNO and their is not any way to delete it so I replace this LCNO by the dummy field .

As shown in screen shot.

[Former Member]

It's weird. In se11 I could edit ci_cobl but change of this object was registred in SAP.

In spro Fin Acc -> Fin Acc Global Setting -> Legers -> Fields -> Customer Fields you could find tutorial how expand cobl.

Regards,

JG

[himanshu_gupta13]

Hi All,

I want to just confirm that, If I enter a dummy field in it and activate it. After that, adjust it through the se14, the table RKPF, then it should not create problem to any transactions.

Please help me to short out.

Many Thanks / Himanshu Gupta

[raymond_giuseppi]

Yes no problem should arise as no program should use DUMMY field name, but as CI_COBL is included in many tables, so check its activation log, as more tables may require an adjustment.

Regards,

Raymond