Best way to archive production objects with restore possibility

[PeterJonker]

Hi Everybody,

We want to archive and delete unused interfaces in production, what would be the best way to do this while keeping the possibility to restore the objects back, just in case.

We want to archive the actual production versions not those from acceptance or development because we are not sure if there are differences in the lower tiers that have not been transported.

A small test showed that if we want to restore the exported objects (ICO and com channels) from production into development we are getting an error Object Communication Component XXX_P does not exist.

My question is:

Is it possible to create a new transport group in the SLD (e.g. RESTORE) which points from the Production Business System (XXX_P) to the development Business System XXX_D to circumvent this error ?

Or are we going to get more problems by doing this.

Offcourse we can import it back to production but then we need to retrofit this into dev and qas.

Or is there another, better way to archive IB objects from production ?

Whats your opinion/experience with this.

I would appreciate your opinions.

Peter

[Ryan-Crosby]

Hi Peter,

I appreciate your precarious position with trying to archive objects.  At my previous job we did have a special secondary transport group setup in the SLD for SAP PO (for other reasons - high availability).  You need to pay very specific attention to the configuration to ensure normal transports don't get imported with incorrect information.  Some vague information I recall about the special setup:

1. Each business system can only have a single primary integration server, which is key for importing, so it requires toggling
2. Depending on how you configure the transport group, you may experience unexpected behavior in determination of target business system (seems to be alphabetical sorting and don't recall the exact specifics because it was years ago)
3. If a change list is imported with the wrong toggle settings then information can be lost - easiest course is to reject the change list and import again

I know this doesn't give clarity, but this was several years ago and it gives some things to look out for or consider.

Regards,

Ryan Crosby