Persistent Object Catch 22 - Base Class Inconsistency

[mike_mcinerney]

I have a persistent class that sits atop a single Z-Table. (Its long established and has various additional methods for business logic).

Recently, I added a currency field to the underlying base table.  Then I added the reference field WAERS.  I was having some issues, and went back and forth a few times. I regenerated the persistence model a few times as well.

Somehow, the base class (which I cannot edit) and the ZCL are out of synch.

I've tried two approaches:

I removed the fields from the underlying table, and from the persistence mapping.
When I activate the ZCL class, I get the message
  Field RECORDNAME of mapping is inconsistent (header <-> attribute)
And sure enough, when I try to use the object, it dumps, saying I have methods in the BASE class for the deleted attributes.

The other approach was to add the fields back, but when I use the persistence editor to move them up to the mapping, I am told that the WAERS field is a

Redefinition of existing mapping: Remove old mapping..
(SOS_MAPPING' type 'S' number '136'.)

Short of rebuilding the (productive) class, I’m not sure where to go from here…

Thoughts…?

[mike_mcinerney]

I no longer have this concern.  I just created a new class.