Partner Profiles overwritten by TDMS-Copy

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

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

Similar Messages

Partner Profiles deleted after TDMS copyback

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...

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

BDLS: Partner profiles not change - System Landscape Copy (SRM+HCM+ERP)

Hello,
Can anybody help me for system copy i.e. production to quality.
System Landscape:
- 1 central HCM System
- 1 central SRM System
- 6 Backend Systems (ERP)
Problem: Change Log. Systemnames (SALE) and Partner Profiles (WE20) and ALE-Distribution Model (BD64).
We run BDLS (change RFC/log.Systemnames/ change BD64), but we have problems with Partner Profiles (WE20). Which do not change !
Anybody knows this problem?
What can I do?
Thanks, Silke

Running BDLS would not normally revert the setting for the partner profiles. You could either load it again via backup transport or make new entries accordingly to the specific settings prior to the system copy.

System copy : how to backup your rfc connections, partner profiles ...

system copy : how to backup your rfc connections, partner profiles (we20) amd ports in IDOC processing (we21) ???
Hi forum,
if you want to copy your production system to your quality assurance system you can export users and later on reimport
it to save work. That's good.
But how about RFC connections, partner profiles and ports in IDOC processing ? Anyway to export and reimport it later on ?
Thank you for your help.
Kind regards
O.Eggert

Hi forum,
in the meantime I found out how to handle this matter. May be this solution is not very elegant, but it works.
As for RFC-Connections there are several tables beginning with rfc. e.g., rfccheck. But 4 of it only differ from one system
to the next. These are rfcdes, rfcdoc, rfcattrib and rfccheck. What I did is the following : I used
brspace -u sapsr3/<password> -f tbexport -t "RFC3"
and quite simply exported these tables. Then I deleted some of the RFC-Connections, both ABAP and TCP/IP. After reimporting
what I exported before all these destinations were availlable again. As for ABAP the password had to be reentered but this
can be avoided, too. Have a look at transaction /nsecstore. The tables behind it are RSECTAB and RSECACTB, rspectively.
Export it after having exported the rfc* tables and reimport it after having reimported the rfc* tables. Very important : enable
the option "consistent export" !!!
It worked this way although there might be better and more elegant solutions.
As for transaction we20 check sap not 182172.
Hope that I could be of profit to this forum.
Kind regards
Olaf Eggert
p.s.
import command : brspace -u sapsr3/<password> -f tbimport.
Them select what you exported before.

Client Copy and Partner Profiles

Hi,
I have a doubt related to client copy and how it will affect the partner profiles.
We have a client which has quite a lot of partner profiles defined in it. Now the problem is that the Basis team is planning to perform periodic client copies on this System which will copy the data from another client say 010 to the client in discussion. My doubt is, when this happens what will happen to the partner profiles that are already there in the target? Will it be lost resulting in we creating it all over again? if so is there anyway to get around this issue?
I would appreciate any kind of input on this issue.
Thanks
Praveen

as far as i know a client copy is based on some parameter say it can be client copy based on master data, client copy based on application data etc. I guess partner profile is an application data so in tht case if client copy is done in its context no data will be lost.
just my thought, but please confirm on this with a BASIS team or try a post in the forum for Adminstration and BASIS.

EDI partner profile copying

I need to set up hundreds of trading partners for orders, deliverys, ship confirm, etc.
Has anyone used the function modules in the EDI6 group to do this automatically. I'd like to supply a list of customer numbers and have the WE20 partner profiles all come out the same.
There are two function modules: EDI_PARTNER_COPY_COMPLETE and EDI_AGREE_PARTNER_INSERT that look promising. But, I wanted to check with other forum users for recommendations.

Hi,
When we are sending the Idoc from XI / PI system, it is taking the partner number from Partner Profile used for sending the same from XI / PI System.
We are configuring the same into tcode IDX1, please check the same.
The same partner profile is used in your port number in IDX2, where you have imported the idoc matadata.
Sandeep

Partner profile in case of Idoc to File scenario

Hi
I have ECC system and PI system. Scenario as :
ECC will send the Idoc to PI ..PI system will Convert this to flat file and provide it to Legarcy system
I made Partner profile in sending system (ECC) and maintained Message type 'MATMAS' as Outbound.
Do i need to maintained the MATMAS in Partner profile of PI also?.
As PI has copied the Idoc MATMAS.MATMAS05 from ECC.
I am confused please suggest

Hi,
MATMAS05 should be configured as outbound paramters of ECC and no need to configure any thing at PI Partner Profile..
All you need to do is to create the Distribution model as sender (ECC) receiver (PI) and message type as MATMAS05...
with appropraite RFC destination name and port.....
if you are new to distribution model and like to know tcodes for the same just check the below link
http://pavelgk.pbworks.com/Step-by-step-tutorial-for-creating-Idocs#221Creationofanewdistributionmodelview
HTH
Rajesh

Partner Profile vanishes in BW system

Hi All,
We are facing a recurring issue which happens in BW QA system after we refresh is from the BW production system.
After about a week or so after the refresh, the data loads halt in the BW QA system and the BW team gets an error "EDI partner profile not available".
After i checked, i found that the logical system name entry for the EDW QA system (i.e. self system entry) is missing from the table EDPP1 and also from transaction WE20.
I re-created it in WE20 and the entry automatically got created in EDPP1 table.
My question is : I suspect that some job or application program is deleting this entry. We checked the background jobs but no luck.
How do i resolve this error. The client has come up with this question and he wants an answer as to why this
entry is being automatically.
Can you please help?
Regards,
Hari Kishan

Hi,
See the following SAP Notes:
SAP Note 886102 - System Landscape Copy for SAP NetWeaver BW
SAP Note 325470 - Activities after client copy in BW source systems
SAP Note 325525 - Copying and renaming systems in a BW environment
SAP Note 886102 - System Landscape Copy for SAP NetWeaver BW
SAP Note 1333302 - Special procedure for BW system copy
SAP Note 996238 - Dump 'RFC connection error' after BW system copy
Search for PDF in SDN
How Tou2026System Copy in SAP Business Intelligence System Landscapes
Thanks
Reddy

Source System Connection - Partner Profile Not Available

Alright guys,
My Basis Team have undertaken a 'copy-back' of PRD data in R3 to QA and this means I have lost my partner profiles in BW QA. I have looked at the other threads with regard to 'Partner Profiles', but one simple question - do I need to recreate the connection of just choose 'Restore'.
Thanks
Scott

Hi Scott,
Try to follow up all these .. hope ur issue wil resolved
http://help.sap.com/saphelp_bw31/helpdata/en/dc/6b808e43d711d1893e0000e8323c4f/content.htm
Very Urgent! Cannot execute RSA1
Partner Profile config?
https://www.sdn.sap.com/irj/sdn/advancedsearch?querystring= partner profile&searchpluginname=sdn_forums&selectedcustomprops=resourcetype(value=sdn_forum)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fbc21369-0601-0010-64bf-83b7b8c1ac92 --- PDF file(u can find here partner pfofile information)
Let m e know the futher inf
-Shreya

Wrong logical system for partner profile

Dear gurus,
we have been sending ORDERS Idocs for some time now, using to a logical system called MSC_MM_PRD, a RFC connection called MSC_MM_PRD and a port for Idoc processing called A000000003.
Now, we would like to send ORDERS Idocs to another logical system. We created that new logical system called MES001, a RFC connection (MES) and a Port for IDoc processing using that RFC destination (A00000004).
After that we maintained a partner profile for the new logical system MES001 with outbound parameters for ORDERS Idocs. So far, so good.
But then, I had to create a new message type for purchase orders to use that new connection (called ZEDI) and I guess that is where I made a mistake: I copied the existing message type for the old ALE connection and changed some parameters (like name etc.).
Now, when I create a new purchase order and add a message of the new type and save the order, I get an error message:
EDI: Partner profile outbound process code not available
Message no. E0335
Diagnosis
An outbound partner profile could not be found with the following key:
/MSC_MM_PRD/LS//EF/ZEDI//
[u2026]
Procedure
Please check the outbound partner profiles for the assignment of the process code:
As you can see, SAP tries to find an outbound partner profile using the old logical system (MSC_MM_PRD) and the new message type (ZEDI) as a key and obviously fails.
Can anyone please tell me why SAP uses the old logical system and how I can change that?
Cheers
Alicia

Hi,
problem was, that we had not created a proper distribution model for the message type (BD64). After we did that, it worked fine.
Cheers
Alicia

Partner profile,Message type

First time if I am configuring SAP R3 and SAP BW system
I need to create Partner profile and Port definition ,message type RSINFO,RSSEND,RSRQST.
Creating SAP R/3 source system in BW-I need to use RFC user or my user id is fine.
Any one help me out which message type goes to where or related any documents.
Please advise on this

Hi,
For info about source system connections see the following notes:
793717    Client copy into the BW client in Netweaver/mySAP ERP
606757    Naming conventions for logical systems
<b>524554    Storing destinations in the BW environment </b>
423184    ALE: Problems with logical system names
325470    Activities after client copy in BW source systems
<b>184971    Notes on BW source system connections </b>
184754    Procedure after BW database copy
184447    Building a BW-system landscape
184322    Procedure after DB copy of BW source systems
121163    BDLS: Converting logical system names
Kind regards, Patrick Rieken.

IDoc Receiver, Error in we02 - EDI: Partner profile inbound not available

Hi All,
I have a problem when creating a receiver IDoc from XI to R/3.
I have successfully tested the IDoc when populating the receiver information from the payload. However I want this information to be populated automatically based on the logical systems.
When I do this I get the following error in the IDoc in R/3:
EDI: Partner profile inbound not available
In the control record the sender information is all correct but in the recipient information the partner Number with type LS is populated, but port is not populated.
I have done the following steps.
     the sender is a Business Service so I have created a logical system directly adapter-specific identifiers in the sender service in the integration directory.
     In the receiver business system I have imported the logical system into the adapter-specific identifiers in the ID from that specified in the SLD.
     In the receiving R/3 system using SALE/BD54 I have created a logical system for the source system.
     In the receiving R/3 system using we20 I have created a partner profile of type LS with the same name as the source logical system.
     IN PI/XI system in transaction IDX1 Ive created a port (SAP<SID> where <SID> is the system ID of the receiving R/3 system) and the client of the R/3 system, and the RFC destination of that system (<SID>CLNT<clnt>, as specified in SM59).
     In the IDOC Adapter (receiver) I have entered the RFC destination and port matching those created above. All checkboxes are UN-checked eg. take sender from payload, take receiver from payload, Apply control record values from payload, etc. are all NOT checked.
I think that Ive done everything correctly, but I get the error in we02 in R/3: EDI: Partner profile inbound not available.
Any help will be greatly appreciated (and rewarded, obviously).
Thanks,
Matt.

HI Matt,
Can you please copy paste the exact error message....In your error message it will show you Exact partner Number / Logical System name and other parameters...just compared if you have all parameters set in your partner profile comparing to error message...
If you can giev screen shot of both..then probably would be easy to point out error.
Hope this will help.
Nilesh

Partner profile LI and unit of measure

Hi gurus,
I am experiencing a weird situation and probably you have any clue about it.
I have configured an output to send the Purchase order information via EDI. I have used the standard function and programs to create the output. I have created the condition record for that particular vendor and output.
Then i have created the LI partner profile in we20 with the vendor number and the message types ORDERS and ORDCHG and I have also included my output with the ME10 and the ME11 in each of the messages.
When i create the PO and the output is sent I have the PO number but then i have the standard error message " Update was terminated" with the error "There is no conversion factor for material and unit of measure !" I have reviewed the PO and i have used a UoM PC that i have as an ISO code.
the point is if I use a different LI partner profile with exactly the same information then the idoc is sent without any problem. I have deleted the partner LI that I orinally created and i created it again as a copy of the one that is working but without sucess.
I have reviewed the vendor master data...but all is exactly the same.
I think or there is some config missing or that I have created the partner profile incorrectly. But it is rare that the partner profile has any link to the UoM.
Do you have any idea what it can be?
thanks so much

I understand from your mail, you have maintained the ISO equivalence to your UOM. When you change your vendor in WE20, did you change that information in MN04? This is the place where the right output type is triggered.
Other than that make sure you configured all the necessary items in WE20 -> Outbound Parameters -> process code and all otehr necessary settings.
Let me know, how it works?
Regards,

EDI: Partner profile inbound not available Message no. E0337

Hi Friends,
I am facing very wiered issue for incoming vendor frieght invoice. When the IDOC is sent to SAP from the edi subsystem, it gets posted with status 56 and error message
EDI: Partner profile inbound not available
Message no. E0337
Diagnosis
An inbound partner profile could not be found with the following key:
/0040000010/LI/VN/INVOIC/MM///
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST test flag
I have created the partner profile in WE20 for Partner type LI, partner role VN and process code INVL, message type INVOIC, message code MM. I have also checked the entry in TABLE EDP21 and the entry exists.
When I open the IDOC in WE19, and click on standard inbound TAB it says partner profile not maintianed, however when i click on the control record it opens a dialog box, where we have all the entries for partner profile and when I just click on any field in the dialog box and click continue and when again click on standard inbound it say partner profile maintained.
None of the data is changed in the IDOC control record, I just click on any field and it finds the partner profile.
Please let me know your thoughts, what could be possible reason and a solution.
Thanks
Deepak

Hi Deepak,
I am facing the same problem with a different message type.
But same effect. I can copy the IDoc with WE19 and it will process nicely, completely unchanged.
Have you found the reason for this?
Thanks,
Florian

Delivery split through VLSP along with JIT Calls with AW Partner profiles

Hi SAP SD/LE Guru's,
I have one critical issue to resolve immediately in my implementation of SAP 4.6C system in multinational automotive industry. It's in the area of Delivery split along with AW - Duns number partner profile and JIT calls.
Here is the scenario:
1. JIT(Just In time) calls will be created through EDI based on the ship-to, PO Nos, Duns number.
2. The requirements will be updated in Scheduling Agreements JIT Delivery schedule.
3. Picking is done based on the requirements.
4. Packing, Deliveries and Handling units are created: Note: Each handling unit is linked to one JIT Call.
5. Based on the Shipments, Deliveries needs to be split into further sub-deliveries.
Ex. One Delivery has two HU's. This needs to be split into another delivery so that one HU need to be detached from original and attach to new delivery. At the same time corresponding JIT call also need to be detached from original delivery and attach to new delivery. This can be done through VLSP : Subsequent split(Outbound delivery). Split profile: 003 - split based on Quantities.
The issue: When executing delivery split using VLSP and split profile: 003, the system is terminating and giving short dump.
The error analysis says that AW - Duns number is creating the problem. The short dump occurs in SAPLV05I in Function module: SD_PARTNER_UPDATE.
There is an SAP note: 154766 related to this problem says that Partner header should be used only once in copy control.
But in customization of copy control from Sales order to Delivery, there is no VBPA Partner header.
I appreciate if you can provide solution for delivery split and resolve this short dump issue.
Thanks,
Murali Chintakunta

In reference to this change in the Custom Reports... Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
What is the customer confusion we are trying to stop here? I've got even more confused customers at the moment because all of a sudden they can't find the export to excel option but know it exists if they log in on a PC?
Mark

Partner Profiles overwritten by TDMS-Copy

Similar Messages

Maybe you are looking for