Export partner profiles and SM59 Entries before system refresh

Hello All,
How to Export partner profiles and SM59 Entries before system refresh in Netweaver
thanks
Shyam

In SDN search with name RFC export ..you will get so many answers ..
Once again please find the below prcoess for RFC export/import during system refresh.
RFC Export --
go to trans dir.. and then create .ctl file as below
#cd /usr/sap/trans/bin
#vi export_rfc_<sid>_<date>.ctl
#Please create the data file as u201Cexport_<SID>_rfc_<Date>.datu201D
Export
Client=<XXX>
file '/usr/sap/trans/data/export_<SID>_rfc_<Date>.datu2019
delete from rfcattrib
select * from rfcattrib
delete from rfcdes
select * from rfcdes
delete from rfcdoc
select * from rfcdoc
delete from rzllitab
select * from rzllitab
delete from ZTCA_USER_LANG
select * from ZTCA_USER_LANG
delete from rfcsysacl
select * from rfcsysacl
delete from rzllitab
select * from rzllitab
#After that excute export command as below.
R3trans u2013w <export_rfc_<targetSID>_date.log> export_rfc_<targetSID>_date.ctl>
(Format is: R3trans u2013w <logfile> <controlfile>)
Export is finished....
Import
Example:
#cd /usr/sap/trans/bin
#vi import_rfc_pta_11042004.ctl
#Please enter the exported RFC data file in the import control as follows:
import
file '/usr/sap/trans/data/export_pta_rfc_11042004.dat'
(Enter the file name, which is created during the export process)
Regards,
Srinivas Chapa.

Similar Messages

Exporting WE20, WE21 and SM59 Entries

Hi,
Can anyone knows how can we export or keep a copy of WE20, WE21 and SM59 Entries for later use. As We are going to refresh the development server with quality and wish to restore the orignal DEV servers parameter (Enteries) settings.
How can we do Export and Import. Pl. suggest me some solution.
Thanks,
Raj

Try this Script . Go to /usr/sap/trans/bin create a file ( <filename>.ctl > with the following entries
export
file '/usr/sap/trans/data/filename1.dat'
delete from rfcattrib
select * from rfcattrib
delete from rfcdes
select * from rfcdes
delete from rfcdoc
select * from rfcdoc
delete from rfcsysacl
select * from rfcsysacl
delete from rzllitab
select * from rzllitab
delete from rzlliclass
select * from rzlliclass
delete from sxroute
select * from sxroute
delete from rfccheck
select * from rfccheck
2 ) execute the command R3trans -w <filename>.log <filename.>.ctl , a log file will be created in /usr/sap/trans/bin with the file name <filename>.log , R3trans return code should be 000 0r 004.
3) If you want to reimport it to the same system at a later point of time create a script <filename2>.ctl in /usr/sap/trans/bin
import
file '/usr/sap/trans/data/filename1.dat'
4) R3trans -w filename2.log -u 1268 <filename2>.ctl
The return code should be 000 or 004 , compare the no of table enties in the exported and imported log files , they should be in sync .
Edited by: Mann Mohandas on Feb 20, 2010 8:33 AM

Retain background jobs and its variants before system refresh activity

Hello All,
I am going to perform system refresh activity on quaity system on monday. Customer wants to retain the background jobs and its variants in the quality system. Please guide me and let me know the steps to retain the background jobs and its variants before starting the system refresh activity.
Regards
Subbu

Dear Subbu,
You have to export the TBT* Tables to retain the jobs. You can do this with R3trans:
1. Make Export file
2. Make Import file
3. Make Export in Q System before Systemcopy
4. Start Database and not SAP
5. Make Import in Q after Systemcopy
6. Start sap
1. Make Export file /tmp/export_cmd
export
file='/tmp/export_Q.dmp'
client=<your client>
delete from TBTCA
delete from TBTCB
delete from TBTCCNTXT
delete from TBTCCTXTT
delete from TBTCCTXTTP
delete from TBTCI
delete from TBTCJCNTXT
delete from TBTCJSTEP
delete from TBTCO
delete from TBTCO_V01
delete from TBTCP
delete from TBTCPV
delete from TBTCR
delete from TBTCS
delete from TBTC_SPOOLID
delete from BTCEVTJOB
select * from TBTCA
select * from TBTCB
select * from TBTCCNTXT
select * from TBTCCTXTT
select * from TBTCCTXTTP
select * from TBTCI
select * from TBTCJCNTXT
select * from TBTCJSTEP
select * from TBTCO
select * from TBTCO_V01
select * from TBTCP
select * from TBTCPV
select * from TBTCR
select * from TBTCS
select * from TBTC_SPOOLID
select * from BTCEVTJOB
2. Make Import file /tmp/import_cmd
import
file='/tmp/export_Q.dmp'
3. Make Export in Q System before Systemcopy
R3trans -w /tmp/Q_export.log /tmp/export_cmd
4. Start Database and not SAP
sqlplus "/as sysdba"
SQL> startup
or
startsap
stopsap r3
5. Make Import in Q after Systemcopy
R3trans -w /tmp/Q_import.log /tmp/import_cmd
If you want to undo this, start the export script in P system and the Import script in Q system.
Don't be afraid of the delete statement but without delete it doesn't work!
6. Start sap
startsap
Best regards
Willi Eimler

How to save SM59 RFC entries during system refreshes

Hello,
I will be refreshing our NW04 ERP and SRM QA systems. Our platform is Oracle/Unix.
My question is how to export the SM59 RFC entries before the refresh, so I can reimport them after the refresh. I have done this successfully in R/3 4.6c, but cannot get it to work in NW04.
During the last refresh, I manually created transports and added the three standard objects, but after reimporting the transport in the newly refreshed system, I found that the RFC's were not restored.
Any help would be greatly appreciated!
Thank You,
Joyce

Hello Joyce,
I've created an RFC destination in a NW04 system while making a SQL trace.
It did
a DELETE in table RSECACTB
an UPDATE in table RFCDES
an UPDATE in table RSECTAB
an INSERT in table RFCDES
an UPDATE in table ATAB
an INSERT in table RFCATTRIB
a DELETE in RSECTAB
an INSERT in RSECTAB
an INSERT in RSESCACTB
an INSERT in ATAB
I think that the data model is much more complicated in NW04 than in R/3 4.6 and creating manually a transport is a challenge that I would not try !
Regards,
Olivier

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

Creation of a partner profile for an non sap system

hi,
I need to create a partner profile for an non sap system(SQL Server).
step by step procedure will be useful.

Hi,
1>goto SM59 create R/2 connections and give the connection type as 2 and give the receiver address.
2>create port in we21 tcode.
3>create partner profiles in we20 and give the receiver system (LS).
Regards,
nagaraj

Partner Profile and its configuration.

Hi all,
I am creating an SD IDoc using EDI and send it between two servers.
I need to know what is a partner profile and why should we create it.
what are the steps to be followed in maintaining a partner profile and its configuration.
Any pointers will be highly apppreciated.
Thanks in advance,
Regards,
Jose
Edited by: Jose Anthony Reddy on Dec 17, 2007 11:23 PM

Hi Jose,
Below is a material you can go through .
Creating an Outbound Partner Profile
Here you must enter the data manually. Alternatively, you can also transfer the default values from Customizing.
If you are not yet on the change screen of your desired partner, choose SAP Menu ® Tools ® IDoc Interface/ALE ® Administration ® Runtime Settings ® Partner Agreement (WE20).
1. Position the mouse on your partner in the required partner type node. Choose in the Outbound Parameter table.
Key Fields
2. You have already determined partner number and partner type in general partner processing. The partner function from the master data defines the addressee, that is, it is used for further classification purposes. If you have selected outbound processing under Message Control (MC), the function must be identical to the corresponding Message Control field. Otherwise, it is optional.
Partner A (customer 1110) wants to order a material from partner B (vendor 1014). Partner B is of the partner type LI (vendor) and must choose the Message Control value VD (vendor) as the partner function because orders must always be processed using Message Control.
3. Specify the business process with the logical message, within which the IDoc type is used. The logical message is described by three parameters: The message type is based on EDIFACT message types: For example, a purchase order is of type ORDERS. You can further divide the message type with the optional fields message code and message function.
4. Configure the test indicator if you want to send the message as a test.
Message, partner and test indicator are the seven key fields of the outbound partner profiles (the client comes in addition to these). Also see the graphic at the end of this section.
Other Fields
5. In the Outbound options tab page, you can determine whether IDocs are forwarded immediately to the receiving system. You should ensure that your entries are compatible with the Message Control priorities, if you have chosen outbound processing under Message Control. A list of recommended combinations is provided in the section Outbound Processing Under MC: Procedure.
6. You have already defined the Recipient port in Port definition.
7. If a port of type TRFC is used, the Queue Processing field is visible. You can use the indicator to specify whether IDocs are to be sent with qRFC. This sending technique is only possible for recipient SAP systems as of SAP Web AS 6.20.
You should only set this flag if it is really necessary that the IDocs sent are received in the receiving system in the same sequence as they were sent by the sender system. Queuing can cause posting delays in the receiving system, because an IDoc in the queue cannot be posted. In this case, the following IDocs in the queue cannot be posted until the error is resolved.
8. If you have set the Queue Processing indicator, the Rule Name field, which you must then also maintain, appears as well. The rule name defines the rules for queue names. You can specify these rules in the transaction qRFC IDoc Queue Name Rules (WE85).
9. Specify the IDoc type as the Basic type with or without extension. If you want to use a view of your IDoc type (for example, to improve the performance), specify this here.
The figure below shows the m-to-n relationship between logical messages (business meaning) and IDoc types (technical format). Message 1, for example, is always assigned to one IDoc type, while message 3 is assigned to two IDoc types. IDoc type 2, in turn, is also assigned to 2 logical messages.
10. The segment release specifies the release from which the segment definitions (not the IDoc type definition) originates. We recommend that you leave this field blank so that the most recent segment definition is used.
11. You can propose an EDI standard, version and EDI message type for the receiving system in the tab page EDI Standard. Most subsystems, however, should be able to determine these EDI settings themselves (from the logical message).
12. You can define permitted agents for cases in which exceptions occur. This entry overrides the entry in the general partner profiles. Depending on the message, therefore, the exception can be handled by different agents of the same partner.
13. You can specify whether syntax errors are to be ignored or are to lead to a processing error (Cancel Processing flag under syntax check in the tab page outbound options). For more information about exception handling and permitted agents, refer to the following section: Exception Handling
14. If your hardware supports it, create partner and message specific telephony data for outbound IDocs. For more information, see General Partner Profile.
Graphic: Outbound partner profile fields (general)
Key fields are shown in gray. The values for partner, message and test indicator (and client) therefore provide a unique ID for the IDoc type in outbound processing.
Regards,
Praveen

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

What is the difference between generate partner profile and creat partner

What is the difference between generate partner profile and creat partner profile ?

Create Partner ProfilesAlthough partner profiles are usually created automatically, because of the unusual inbound and outbound profiles needed on the same system, the manual generation of certain profiles is required.
The following subsections describe the partner profile settings for the standard client (assumed here to be ALExxxCyyy), as well as for the corresponding dummy client (assumed to be DUMxxxCyyy). The dummy client partner profiles should have been generated by the automatic generation process completed previously. Nevertheless, these should be checked to ensure that all profiles exist.
Generation of Partner Profiles
The following messages should be added to the 4xx-ORDR model for ALExxxCyyy to DUMxxxCyyy on the reference client:
ORDERS
ORDCHG
ZINVRV
ORDRSP
INVOIC
FIDCMT
The partner profiles should first be generated using the standard auto-generation procedure on the reference client (for SYNCH messages to be created).
This model should now be distributed to the both ALExxxCyyy and DUMxxxCyyy.
The partner profiles should now be generated on the client being configured (i.e. yyy) using the auto-generation procedure defined in the standard ALE configuration procedures.
Generate partner profiles for sending system. (Can only do this if at least 1 message type exists against the sending system's LS). This automatically generates the port if the LS and RFC name are the same.
generate partner profiles tcode BD82
creating partner profiles tcode WE20
 There are two methods for maintaining the partner profile:
 Maintain partner profile manually:
To navigate to the partner profile in the sender system, choose Partner profile -> Partner type of Logical System and click on the required Target system. Under Outbound parameters, choose the Create outbound parameters icon, and enter the values for the outbound parameters according to the slide Sender: Partner Profile (outbound).
To navigate to the partner profile in the sender system, choose Partner profile -> Partner type of Logical System and click on the required Sending system. Under Inbound parameters, choose the Create inbound parameters icon and enter the values for the inbound parameters according to the slide Sender: Partner Profile (inbound).
 Generate partner profile:
Prerequisite: The current distribution model is distributed to all participating systems.
In the sender system, choose: Generate Partner Profile, then check the result in the partner profile (outbound)
In the sender system, choose: Generate Partner Profile, then check the result in the partner profile (inbound)
Regards
Vasu

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

Doubt regaurding message server in IR, partner profile and transporting XI

Hi guys,
Can someone help me in figuring out the need of message server and group after importing IDOC into IR. where can i find the message server ip address?
I am also wondering in the partner profiles when we need to use logical system (LS) or Supplier/vendors (LI) or Customers/debtor (KU) or etc.?
Please explain how to transport developer xi system to production server?
Cheers
Ram

Hi,
>>>>----> how to transport XI objects to production system?
the easiest way is to use file transport
you can export a file from IR and ID and import it into QAT and then into PRD
all you need for ID is to create transport targets in SLD
http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
so the names of your systems will change
you can also refer to this:
/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
/people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
but as I mentioned file tranport is the easiest way
>>>>-------> How about the option group?
you can put everything in idoc import menu
and use separate option when asked
Regards,
michal

Partner profile and partner number in output of order/invoice.

Hello Experts,
I want to know how system pick partner profile from output type triggered in sales order/invoice??
I could see partner profile is different from partner number exist in output triggered in sales order/invoice.
I want to know the triggering point of idoc from SO/invoice.
Thanks

The phrase "ouptut goes to partner" indicates that the partner will be recipient of the output type. E.g., ship-to partner will be the recipient of the delivery and the delivery note.
The use of an output partner in the output condition record is used to control the output device used in the output determination - a completely separate issue.
Unless you are (e.g.) using different printers for outputs which will be sent to different partners, you would likely be better off using a more generic access for your output condition records.
HTH
James

Generating SRM Partner Profile in SAP R/3 system

Hi,
Please can someone shed some help as to why I get the message below when attempting to Generate SRM Partner Profile in SAP R/3:
"No messages have been defined for the selection conditions in the model"
I have in fact sucessfully generated this in SRM, but get this message when trying to do the same in R/3 backend.In B64, i have also set it to Transfer Idocs Immeditate.
Thank. You.
Pooja.

Hello Pooja
please check you have supplied correct logical system or not
in the modelview
cross check via scc4.
Re: No messages have been defined for the selection conditions in the model
muthu
Edited by: Muthuraman Govindasamy on Oct 3, 2008 2:48 PM

The change flag in partner profiles and how its used?

Hi,
can any one succinctly explain the use and purpose of the change flag in the message control part of the partner profile configuration?

Hello,
The value of this field is use internally in FM attached to the process code for Creation/Change and in case of change, only the relevent changed data is sent ( taken care by attched FM).
Thanks & Regards,
Pieter

Java Dispatcher Down but Server0 and SDM up after system refresh

Hello,
I have done system refresh from PRD to QAS of CRM system - dual stack.Once after the system refresh ABAP is up and running fine but Java is down (Only Dispatcher is down. Both SDM and Server0 are running fine).
I have followed Note 609603 - Problems with Multiple NICs and SAP J2EE Engine and have given the correct host name but the no luck..
std_dispatcher.out says the following error:
Cannot attach to the Message Server. Can't open port [3925] on host [<Source Host Name>/Source IP Address].
Could you please let me know if I need to do any changes in the Config tool?
Thanks,
Subbu

HI,
IN DB restore the hostname of java system stored in profiles would be your PRD.
Go to Configtool in Edit mode -- cluster --> change the hostnames in Instance profile -- and under other files like bootstrap etc whereever you find PRD hostname.
And otherwise for JAVA system you should use export/import option.
Regards,
Tajinder

Export partner profiles and SM59 Entries before system refresh

Similar Messages

Maybe you are looking for