Partner Profiles overwritten by TDMS-Copy

[Former Member]

Hello,

our TDMS-Copy succeeded by overwriting an old client, but copied Partner Profiles (WE20) and Ports (WE21) too, which we didnu2019t want to be changed. Is there a way to save this data?

Regards

p121848

[former_member785122 · Accepted solution]

Hello,

Could you please mention the table names that you don't want to transfer means table name

which contains partner profile information ?

Regards,

Anita Rathi

[Former Member · Accepted solution]

Hi Anita Rathi,

thank you for your question. It would be very useful, if Iu2019d know exactly which tables must be regarded. With this information I could build a transport order, which has to be released before the client copy and could be imported afterwards. Do you have an other idea?

Regards Wolfrad

[Former Member · Accepted solution]

Hi,

The table names are

TBD00 EDIMSG

EDP21

EDP13

EDP12

EDIDD

EDIPHONE

EDP13

EDP21

EDPP1

EDMAT

EDMA

EDADM

EDAYTYPBLOCK

EDAYTYPBLOCKDEF

EDAYTYPBLOCKT

EDAYTYPE

EDAYTYPET

EDBDMSKY

EDCPIC

EDE1T

EDE2T

EDE5T

EDE6T

EDEREGPARCONF

EDEREGPARCONFT

EDEREGPARVAL

EDEREGPODGROUP

EDEREGPODGROUPT

EDEREGPROCPARDIS

EDEREGSCENAGREE

EDEREGSCENARIO

EDEREGSCENARIOT

EDEREGSCENCONTR

EDEREGSCENCONTRT

EDEREGSCENDATEX

EDEREGSCENSERV

EDEREGSCENSERVT

EDEREGSPAGREE

EDEREGSWITCHDIAL

EDEREGSWITCHPROC

EDEREGSWITCHSYST

EDEREG_SERIDENT

EDEREG_SERIDENTT

TBD001

TBD002

TBD00T

TBD03

TBD05

TBD06

TBD20

TBD30

TBD40

TBD41

TBD52

TBD55

TBD56

TBD61

TBD611

TBD61B

TBD62

TBD71

TBD71T

TBD72

TBD73

TBD74

TBDA1

TBDA2

TBDBANKC

TBDBR

TBDBRF

TBDC001

TBDC002

TBDIBAN

TBDLI

TBDLT

TBDMO

TBDMO_DET

TBDRCSTATE

TBDSE

TBDSET

EDEREG_SIDPRO

EDEREG_SIDPROINT

EDEREG_SIDPROT

EDEVCHECK_BACKUP

EDEVGR

EDEXCOMMFORMALE

EDEXCOMMFORMAT

EDEXCOMMFORMATT

EDEXCOMMFORMFTP

EDEXCOMMFORMINTR

EDEXCOMMFORMMAIL

EDEXCOMMFORMPART

EDEXCOMMFORMVERS

EDEXCOMMFORMXML

EDEXCOMMMAILADDR

EDEXDEFSERVPROV

EDEXDEFUI

EDEXDUECONTR

EDEXDUECONTRT

EDEXIDOCSEND

EDEXIDOCSENDT

EDEXPROC

EDEXPROCPAR

EDEXPROCPODGEN

EDEXPROCSPGEN

EDEXPROCT

EDEXPROCUI

EDEXTASK

EDEXTASKASS

EDEXTASKERROR

EDEXTASKIDOC

EDEXTASKREF

EDEXTASKWKFLOW

EDGE

EDICONFIG

EDID3

EDIDD_OLD

EDIDOCINDX

EDILOGADR

EDIPHONE

EDIPO2

EDIPOA

EDIPOACODPAG

EDIPOD

EDIPOF

EDIPOI

EDIPORT

EDIPOX

EDIPOXH

EDIPOXU

EDIQI

EDIQO

EDISCACT

EDISCDOC

EDISCOBJ

EDISCOBJH

EDISCORDSTATE

EDISCORDSTATET

EDISCPOS

EDISCREMOV

EDISCTYPE

EDISCTYPET

EDISCVAR

EDISCVART

EDIVDIM

EDI_MONIT

EDLTYP

EDMMS

EDMS_AT01

EDMS_CONDITION

EDMS_CT01

EDMS_CT01T

EDMS_FILTER

EDMS_LAYOUT

EDMS_LAY_DETAIL

EDMS_PREFS

EDP12

EDP13

EDP21

EDPAR

EDPI1

EDPO1

EDPO3

EDPP1

EDPPV

EDPST

EDPVW

EDRGPODGRASSIG

EDRGSPAGRTYPE

EDRGSPAGRTYPET

EDSC

EDSCH

EDSCHINDEXA

EDSCT

EDSDC

These tables are involved in transaction We20 and Bd64

[Former Member · Accepted solution]

Hi Raghuram,

that are a lot of tables and the most of them are empty in our client. These tables seem to me important:

EDIPHONE Telephony Data for Partner Profiles

EDIPOA Table for ALE Port Definitions

EDIPORT Summary Table for all Port Types for IDoc Processing

EDP12 Partner Profile: Outbound with Message Control

EDP13 Partner Profile: Outbound (technical parameters)

EDP21 Partner Profile: Inbound

EDPP1 EDI Partner (general partner profiles - inb. and outb.)

Is it possible to exclude these tables from transportation in the activity u201CMaintain table Reductionu201D (TD02P_TABLEREDUCTION)? If yes, isnu2019t this too dangerous because of data inconsistances?

Regards

Wolfrad

[Former Member · Accepted solution]

Hi,

If you do not want TDMS to overwrite data this approach has to be taken and

tested. Yes it can be excluded in "Maintain Tables for Reduction"

Regards

Raghuram