In ECC, we have the need to archive (actually delete) a specific type of purchase requiistion record created en mass by an interface. We do not want to retain (in the repository) these archived / deleted records, and we do not want to put them in the archive infostructure with other real requisitions, and we want to get rid of them very quickly.
All of these, the repository destination, archive infostructure, and residency, are controlled in configuration, so we thought we would copy the MM_EBAN object (to ZMM_EBAN) but use the same wirte and delete programs. (as their logic is still valid, only configuration would be different).
However when we tested our ZMM_EBAN object in SARA, program results were under MM_EBAN for "management" etc. SAP has told us we can not use the same write / delete program with cloned object. (object name is hard coded within the programs apparently.)
So I wondered, has anyone else needed to do something like this? Did you copy a standard object? Is the solution that we must also "copy" all the write / delete programs and change the hard-coded name? (and will that work ?)
Or should we push back on SAP that it SHOULD WORK to use the same program, if they were picking up object name you ran under, as they should from SARA... (except, as I think through that, if we "scheduled" these jobs to run, just the write program name, not running it from SARA, I guess the programs might not know what object they are, unless it is hard-coded in the program.... hummm).
Ruth Jones