export from client000 contains DMIS add-ons?

[Former Member]

We used to create the target system by a client copy or using an existing system. Then do TDTIM, etc.

When using TDSHL to create the target, how do the DMIS add-ons get into the target?

As part of the TDSHL, there is an export of sender's client000 which is later imported into the shell. Is at this step the DMIS

add-ons get into the shell?

We try to access SAINT to verify above, but on SAINT we cannot see the normal screen. Instead, we get the error mesaag:

"Form S_docu_show language is not active and has no errors"

Same error shows up at shel system's SPAM.

Our concern is that can we assume that shell's DMIS add-ons have the same level (or content) as the other systems? Therefore

we can continue the TDMDC, etc. without concern about the DMIS level on the receiver?

Thanks!

[Former Member]

When you do a TDSHL process to create a shell system from a source system then all the SAP components along with all the SPs and note implementations are also copied to the shell system.

The same happens in two steps -

All the objects are copied as part of the system copy export and import step with shell.

All the SAP delivered customizings are copied when you do a copy of client 000 from source to shell.

So the shell system is exactly in sync with the source system as far as TDMS add-ons are considered, you just need to apply an SAP system licennse to the Shell system and then continue with executing TDMS data transfer packages.

I hope this answers your query.

[Sandeep_Kumar]

Our concern is that can we assume that shell's DMIS add-ons have the same level (or content) as the other systems? Therefore we can continue the TDMDC, etc. without concern about the DMIS level on the receiver?

The DMIS level should be same in all participating systems(sender/reciever/central) and make sure that you import the latest SPs for DMIS before start