Table can not activate again after changing

Question

Hi, everybody
For some reason that we create one more field call EKORG(Purchasing organisation) in table LFA1 and made choice for both Key and Initial value. Now, we are going to delete this field and activate table again, system show the following message, please kindly give us a hand and let me know how to solve this issue in more detail. We  use T-code: se14 and try to Activate and adjust database that system show the same message as below.
Thanks you All.
<b>Primary key change not permitted for value table LFA1
Message no. AD300
Diagnosis
This table is defined as a check table. For reasons of consistency, changes to the primary key of the table are not allowed.
Procedure
If it is essential that you change the primary key, you must delete the relevant foreign keys. Refer to the where-used list to find all tables containing a field that is checked against this table. Delete the foreign keys for these fields.
If necessary, maintain the deleted foreign keys again.</b>
Message was edited by:
        Alfred

Answer 1

Alfred,
If you can't figure this out you should stop what you are doing and get help from someone who knows how to fix this mess.  I'll give you a hint, it isn't Programs...  And it might be something to do with tables...  Once you've got a list of all tables where LFA1 is used you will have to check them 1 by 1 to see if they use LFA1 as a check table.
I'd still love to know what posessed you to mess around with the primary key of a standard SAP table?  And I'd also love to know why everyone is giving you help and suggestions on how to activate the table whilst no-one seems to care that you are changing a standard SAP primary key.  I can't believe you managed to get an access key to change the table in this way and no-one in your company/client questioned what and why you were doing it!
LFA1 is a pretty important table in the SAP system (Vendor Master table) so to mess around with its primary key is utterly ridiculous.
The only thing you should learn here is that changing SAP standard objects is usually a no-no.  Trying to change the primary key on a standard SAP table is a complete no-no.  There must have been an alternative to whatever it is you are trying to achieve.
Gareth.