on 09-01-2014 3:21 PM
Recently we had a copyback activity using TDMS 4.0 for ECC system. After the copyback, we noticed that partner profiles has been deleted. One of our pre-steps is to delete the largest tables then delete the client(SCC5) and recreate a shell client. Would like to ask if how we could prevent the deletion of partner profiles during copyback? Or atleast, is there a way we could automate the configuration and return to previous state before the copyback this partner profiles? We're not sure other configurations being deleted during copyback.
Hope for your reply. Thanks in advance...
Philip,
It should be pretty easy to achieve this within TDMS itself.
Please refer to the note
CRM copy -1817939 - TDMS 4.0: Set ALE/IDOC tables to No Transfer and No Deletion
SCM copy - 1905459 - Exclusion of ALE/IDOC Data from Transfer
BI/BW Copy- 1667273 - To set ALE tables to no_transfer
Not sure what SP level of DMIS_CNT you are using for your TDMS 4.0 installation.
But normally by default the ALE /IDOC /Partner profile tables should be excluded from Deletion and Transfer in an ERP copy . In case this is not happening. You may use the attached program from
the note 1817939 and set correct package type to adjust the required customizing.
Thanks ,
Rajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Philip,
You can exclude partner profile tables from deletion and transfer within TDMS itself. Apart from partner profiles check for port data and workflow configuration. You can raise a message in component CA-TDM-BUS-ERP to know full list of tables and procedure as how to exclude these tables from transfer and deletion.
Thanks
Anita
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
You can keep backup of these tables and restore once copy is completed , you can put entries into Transport request or can use R3trans for backup and restore of these tables.
# WE20 tables
EDPP1
EDP12
EDP13
EDP21
# WE21 tables
EDIPOA
EDIPORT
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Philip,
There are many based on your landscape few examples below which i generally use
As Mentioned By Anitha , you can very much do this using TDMS itself , exclude these tables from copying.
#SCC4 |
T000 |
#OSS1 |
EWOSS |
#RFCs |
RFCDES |
RFCDOC |
RFCSYSACL |
RFCATTRIB |
RFCCHECK |
RFCDESSECU |
RFCTRUST |
RFCCMC |
RFCGO |
#RSA1 Transport conversion |
RSLOGSYSMAP |
#Transport Number |
E070L |
#SAP License |
SAPLIKEY |
#Access Keys |
ADIRACCESS |
DEVACCESS |
#Logon Group |
RZLLITAB |
#Transport |
TMSCROUTE |
#BD54 |
TBDLS |
TBDLST |
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.