Taking Dump of Ports, Partner Profiles etc before Client Deletion

Hi,
Let me firstly tell you about the requirement.
I need to delete a 9TB client using TDMS. And then re-create it again for users. Now the problem is , that the Partner Profiles, Ports will be deleted when I delete the client, which I cannot afford to loose are there are a lot of them.
So, what is the best way to take a dump of the ports and partner profiles and other relevant things. I tried taking the table entries into transports and thought of re-importing them. But I'm not sure what all tables will be there as there are many like :
EDPP1 (general partner profile),
EDP12 (Message Control),
EDP13 (outbound parameters)
EDP21 (inbound parameters)
Partner function exists in table TPAR
Outbound process code exists in table TEDE1
Logical message type exists in table EDMSG
Process code exists in table TEDE2
What is the table for Basic Idoc type
Port is defined in table EDIPORT but where is their assignment to the Logical Name its not in this table.
There would be so many tables that are interdependent and I don't wanna loose even a single one of them.
Please advice the best option, as I am nearing the deadline to delete this client.
Your help is really appreaciated.
Thanks.

Hi
Iam adding some pots to the above which may help you Take screenshots for some important Settings / Configurationsso that you can easily restore them afterclient refresh. For example
u2022     TMS Configuration (STMS)
u2022     Printer Settings (SPAD)
u2022     Logon Group (SMLG)
u2022     OP Mode (RZ04)
u2022     RFC Destinations (SM59)
u2022     WE20 u2013 Partner Profiles
u2022     WE21 u2013 Ports in IDOC Processing
u2022     Client Definitions (SCC4)
u2022     Logical System Names (SCC4 and SM30: V_TBDLS)
u2022     E-Mail Configuration (SCOT)
u2022     SAP House-Keeping Jobs and Customeru2019s Jobs (SM37)
u2022     SSL Configuration (STRUST) if using
u2022     Others
Se09 other request u2022object list Enter R3TR  TABU  RFCDES
Regards

Similar Messages

Interaction between Distribution model, partner profile, etc.

Hello,
I am a newbie in the SAP world, and I am a little bit lost in the behavior of the Outbound Processing (the send of an IDoc to an external non-SAP system).
Actually my question is how the following components interact during an outbound process :
- RFC Destination
- Logical Port
- Logical System
- Partner Profile
- Distribution Model
- SAP Gateway
- IDOC Repository
- ALE Service
Currently, the only thing I think I have really understood is that the RFC Destination allows to hide to SAP the Program ID of the registered external server...
Thanks a lot
Sebastien

For each logical system and each basic message type (for example, LOIBOM), a unique message type has to be defined by reducing the original one (for example, MYBOM).
If you reduce a message type, only the obligatory fields are automatically selected. You must select those segments and fields you want to have transferred. Fields that have not been selected for transfer always contain the value "/".
Maintain partner profile
Each of the message types of the customer distribution model (see above) must be assigned to the partner profile. Enter the receiver port (see above), package size, output mode and IDoc type in the detail screen of the receiver port. You must also define whether the IDocs should be sent immediately, or if they should be collected first.
Maintain customer distribution model directly
First define a customer model for a logical R/3 system. The displayed list shows which logical system is the sender and all the possible receiving systems that have been defined. "Create message type" defines which logical system receives information from the logical R/3 system.
When maintaining the customer distribution model, you usually add all (reduced) message types that should be sent from the R/3 system to the external system.

Define Port, Partner Profiles, Process Code

Hi All,
Please provide the following valueble information
Define the below and why do we create them?
1. Port
2. Partner Profile
3. IDOC type and IDOC
4. Process Code
5. Message Type
Thanks and Regards
Sowjanya

>>1. Port
Ports are channel through which idocs are exchanged.
>>2. Partner Profile
Partner Profile specifies the kind of message that we are going to exchange with our business partner
>>3. IDOC type and IDOC
IDoc type defines the structure of the idoc. IDoc is a container which carries the data from one system to the another.
>>4. Process Code
Process Code refers to inbound function module which will read the data from the idoc and post it in the system.
>>5. Message Type
Message Type defines the kind of data that you are exchanging with your business partner.
Cheers,
Hakim

While creating partner profile, if the partner type is u0093LIu0094 what r the sett

While creating partner profile, if the partner type is LI what r the settings we need to configure?

Hi Chiru,
For a IDOC to File scenario, just follow these steps:-
SLD-
1) Create a Product/Software Component
2) Technical System pointing to R/3 system
3) Business System for the above technical system
In the Repository
1) Import the Software component created in the sld
2) Create a namespace,
3) import the idoc and then create sender data type/message type etc and mapping
4) Mapping Rules is depends on the requirement
In the Directory
1) Create a Scenario /import the business system
2) Create Receiver/Interface determination
3) Create communication channels for sender and receiver
4) Sender Agreeement and Receiver Agreement.
Then the file adapter configuration is depend on the input file format.
Also you need to have Logical destionation created in the XI , and the IDX1 entry
In R/3 Port, Partner profiles etc should be created
Have a look into this document~
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
In addition do the following in XI:
1. SM 59 - Create RFC destination pointing to R3.
2. IDX1 - Create a port for R3
3. IDX2 - Import IDOC metadata.
I hope this provides you a solution.
Regards.
Praveen

Process code & Partner Profile Issue

Hi Experts ,
Hi ,
I need to configure partner profile with a external system . I will be receiving customer data from the ext System .
I though of using msg type DEBMAS and msg type
and process code DEBM. I see its uses function module IDOC_INPUT_DEBITOR.
So what exactly this function module does ?
I was wandering if I need to create new Process code / Function Module .
My requirement is receiving the customer data along with address , shipping informations , customer no . So that when I drop orders its becomes available.
Thanks
MM_sD

Hi ,
Check all the settings needed for an R/3 - XI- R/3 scenario..... In ur case R/3 to XI is working fine and u have to check the XI-R/3 side.
Check the RFC destination ( Both in XI and in R/3)
Check the logical system name
PORT, Partner profile .....
Regards,
Jude

Receiving IDoc SYPART01 (Transfer of partner profiles)

Hi, well this is not a special PI issue but we have the problem to receive the SYPART01-Idoc in target system.
This is due to not knowing the process code for inbound processing in target system. We already used BAPI, searched for Function Modules etc. - but with no success.
How do you guys transport partner profiles from one client or system to another?!
Or does someone know how to manage the inbound processing for IDoc SYPART01 ?!
br Fritz

Hello,
Any news on this subject ? I'm interested by this topic.
I noticed there must be some specific FM in Emmanuel Hadzipetros SAP Press book.
I guess there aren't any "standard" way !?
I tried to figure out something and notice in the SED package that there are RFC FM like EDI_AGREE_PARTNER_INSERT, maybe we could find out a LSMW solution.
Jon

How to transport the partner profiles

HI SAP gurus,
Please can any body explain me , how can we transport the partner profiles to different clients.
Regards,
Shwetha

Hi,
refer to this link...
Partner profiles!
Re: How can we transport the partner profiles and Port configurations
Edited by: Avinash Kodarapu on Jan 24, 2009 7:16 AM

TC related for IDOC (Defining Port,Defining Partner Profiles...etc) RFC and

Hi All
Can anyone pls give me all the TC related for IDOC (Defining Port,Defining Partner Profiles...etc) RFC and BAPI
Thanks
ss

Hi SS..
 SM59-For creating the RFC destination
 we21- For ports
 we20-Partner profiles.
For more inforamtion Please look at the below information:
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP XI towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
 Thanks and Regards,
 Chandu.
Message was edited by:
 Chandu
null

Regarding ports and partner profiles in ALE.

Hi All,
Please tell me how to transport the partner profiles and ports from Development to Quality systems.
Please reply asap.

SALE Area Menu for ALE configurations.It includes transactions for
Logical System definition and linking it to a client, Transactions for
RFC Destination and Port Definition Etc.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.
Reward points if helpful.
Thanks
Naveen khan
Message was edited by:
Pattan Naveen

Why T-RFC Port canu2019t handle Partner Profile Segment Release Version.

Can TRFC Port handle the segment release of each of the segment if configured in Partner Profile.
As per sap, in Partner Profile, if we maintain the two field "Seg. Release in IDoc Type" and "Segment Application release" to a SAP Release lower than the current release version then all the segment populated by the IDoc adapter should be populated as per the lower release structure.
For test Purpose I have created two IDoc using File Port and TRFC port and for both of then I have maintained the Partner Profile Fields "Seg Release in IDoc Type" and "Segment Application Release" as 46C although the latest release is 701.
In the IDoc there is a custom segment ZE1PMX with two Version Release 46C & 701. 46C is having 7 Fields and 701 is having 9 fields.
Test using TRFC Port: Using TRFC port the IDoc that is getting generated are not having the segment structure of release 46C instead of that it is taking the segment structure of latest release 701 which is having 9 fields.
Test using File Port: Using File port the IDoc that is getting generated are having the segment structure of release 46C instead of latest release 701 which is having 7 fields which is desirable.
I have also done these testing in other SAP release like 700 and found that while saving the partner profile with a lower segment release number it throws an warning message as "Segment definitions missing for release 620/620" and IDocs are not getting generated with a error status Code 2 "Segment E1BPMEPOITEM1 is unknown in Release 620 /". But from release 701 sap allows us to save the Partner Profile without warning and also creates the IDoc without error but the segments takes the latest release structure instead of the release maintained in the Partner Profile.
If any one has already done some investigation on this issue please let me know why there is a difference in TRFC Port and File Port. Is there any other configuration that is missing for T-RFC Port.

Hi Dennis
This forum is focused on [SAP NetWeaver Gateway|http://www.sdn.sap.com/irj/sdn/gateway], i.e. the (relatively) new OData/REST-orientated mechanism to expose ERP data and functions.
You're talking about the ('classic') Gateway i.e. the service that runs on port 33<SYSNR>. As a result, you are better off posting in the forum that covers that Gateway, i.e. [Application Server Infrastructure|SAP NetWeaver Application Server;
The names do make it confusing, for sure.
Good luck!
dj

Does it mean that, 1 CDM/Partner Profile/Port = 1 specific partner?

Hi experts,
As I am beginner to IDoc concept, hv few doubts, like,
1) Does it mean that the development of, 1 CDM(Distribution Model) / 1Partner Profile / 1Port = exclusively 1 specific partner? I mean, for instance the organisation possess 100 partners, so it means that it shuld hv 100 CDMs(Distribution Model) / 100 Partner Profiles / 100 Ports?
2) For out bound direction, for a newly created IDoc sending Does it not necessory to create/use the Process code?
3) If partner profiles r created, so the Ports r automatically cretaed in the system? Or we must create the ports explicitly?
4) Does it means that The distribution of CDM from sender to receiver = Creation of new CDM in the receiving system for that particular partner?
ThanQ in advance,
Rgds,
Sri.

Hi,
1) Does it mean that the development of, 1 CDM(Distribution Model) / 1Partner Profile / 1Port = exclusively 1 specific partner? I mean, for instance the organisation possess 100 partners, so it means that it shuld hv 100 CDMs(Distribution Model) / 100 Partner Profiles / 100 Ports?
It is not necessary exclusively but it can be (depend on your business process).
You could also have a single logical system and a single IDoc port for multi partner purposes. In this case, you can use message code and message function to segregate the partner data in receiver system/sender system.
2) For outbound direction, for a newly created IDoc sending Does it not necessory to create/use the Process code?
For transactional data i.e sales order, billing, delivery and etc., you still need to use process code via message control setup (in partner profile). However, for master data distribution i.e material master, vendor master, customer master and so on, you do not need to setup process code in the partner profile. The extraction program will call corresponding FM to generate and distribute the IDoc.
3) If partner profiles are created, so the Ports r automatically cretaed in the system? Or we must create the ports explicitly?
You can use existing IDoc port for new created partner profile or you can create new port via transaction WE21. System will not create automatically the port. You need to link to correponding message type in partner profile (WE20).
4) Does it means that The distribution of CDM from sender to receiver = Creation of new CDM in the receiving system for that particular partner?
If both sender and receiver systems are SAP then you need to setup distribution model (BD64) for both system. Otherwise, if only one SAP system involved and other is external system then you need only to setup one distribution model.
Hoep this will help.
Regards,
Ferry Lianto

Regenerating ports for Partner Profiles and Source System (RSA1)

Hello all you SAP gurus,
During a recent backcopy we have an issue after updating Logical System names using BDLS. This has updated the Partner Profiles (WE20) correctly.
BUT
These partner profiles are trying to use ports (WE21) that have been mistakenly deleted. But if we try to recreate the ports we get the message
-"Choose another name! Name range reserved!"-
This specific port is referenced in outbound parameters. Perhaps this is stopping the change?
We could create new ports and hook them up to the partner profiles, but I'm concerned that there might be other locations where the deleted ports are referenced.
Any help would be greatly appreciated!

Hi J,
You can try and disconnect and re-connect the BW System to R/3. That would force the recreation of the Partner Profile.
Take a look at the connection data in table RSBASIDOC, write down the parameters, especially the IDoc Type.
In SE37, run function RSAP_BIW_DISCONNECT_40 and specify parameters for BW System.
Then run RSAP_BIW_CONNECT_40 and specify those parameter again for the BW System.
This will recreate the Partner Profiles. Then check the assigned ports and see if you still have the same issue. Just make sure the RFC connection is set correctly and working in SM59 before doing all this.
In any case, you can create new ports in WE21 and allow the system to assign the numbers automatically and you won't have any issue.
Hope it helps.
Regards,
Luis
Edited by: Luis Sales on Mar 18, 2008 7:28 PM

Partner profiles and ports

How to transport the configuration of partner profiles and ports from Development to Quality systems.

Hi vidya,
Go through this hope u can get the solution.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
BD64 Distribution Model . Also known as Customer Distribution Model Used to
define all the messages that will be exchanged between remote systems
and the name of thes logical systems. Any filters can also be specified.
The model once created has to be distributed on every system which will
be communicating ,It can be maintained on only One system.
Reward points if helpful.
Thanks
Naveen khan

Partner profile...port....logical system....!!!!!!!

Hello Everyone,
few stupid questions came to my mind but no document cleard it, so thought that someone might throw some light on this.

What is logical system in R/3 and why do we create that ?
what do we mean by partner profile and what is its significance?
what is use of port...???
these all three parameters we look when we create outbound IDOCs for IDOC to file (of any other) scenario.
thanks,
Pranav

Hi Pranav,
What is logical system in R/3 and why do we create that ?
A logical system is your R/3 address where you can distribute data to and from an R/3 system.
http://download-west.oracle.com/docs/cd/B10464_05/integrate.904/b10299/ale.htm This link gives you a better idea of a logical system.
what do we mean by partner profile and what is its significance?
Based on an existing logical system, a partner profile is an identifier for a system used for communicating messages.
http://download-east.oracle.com/docs/cd/B10465_01/integrate.904/b10408/ale.htm gives you a very good idea regarding partner profiles and ports.
Hope these help,
Regards
Kiran..

How can we transport the partner profiles and Port configurations

Hi everybody,
How can we transport the partner profiles and Port configurations. While creating these , system will not ask for Dev class and we cant assign any Transport request number. Then How can we transport these settings?
Your replies are really apreciable.
Thanks and Regards,
Vijay.

Hi,
please have a look of the OSS note: 182172
>>
The partner profiles are stored in the following tables:
Table EDPP1: General partner profile
Table EDP12: Partner profile outbound, additional data NAST
Table EDP13: Partner profile outbound
Table EDP21: Partner profile inbound
Table EDIPHONE: Connection to SAP telephony (optional)
You can use R3TR TABU to manually set the tables into a Customizing request (as of Release 46, into a SYST-type request).
<<
Rgd
Frédéric

Taking Dump of Ports, Partner Profiles etc before Client Deletion

Similar Messages

Maybe you are looking for