Transport Request destination

Hi Gurus,
My question is after we actually release the request through the transport request,
where can we see the released request no. or what is the destination of it.
one more scenario --> how can we transfer a request from one server to another, please elaborate with example.
Thanx.
Regards.

Hello,
Transport Request (TR) number will remain same during complete cycle of configuration/development. That means when you create it in SAP, depending upon number range/definition system generates an internal TR number and will remain the same till you move the changes to LIVE. So even after releasing it, TR number will remain same.
TR Transport: You can move TR's from one client to another and even one SAP instance to another.
TR Transport Strategy is being decided at the start of any project (By Administrator/Basis).
You can simply copy/move TR changes within Clients (single SAP instance) using SCC1 whereas from one SAP instance to another can be done by importing those using STMS.
Refer SAP link for more info: http://help.sap.com/saphelp_nw04/helpdata/en/44/b4a0137acc11d1899e0000e829fbbd/frameset.htm
Talk to your senior Basis person on it for more info.
Hope it will help.
Regards,
ANup

Similar Messages

Error while Transporting Request

Hi All,
we have ECC 6.0 on Unix environment.
we had copied a production client with group selection, as we wanted all the three system PRD,DEV,QLT in sync.
the export was succesfully done.i copied Cofiles & Datafiles which are generated in DEV & Quality server,then i add request no in transport queue. the time when i copied transport request was not releasing from development.we checked the destination it was full so we removed the old request. then req is releasing.
after that i deleted the Cofile & datafile from OS level of DEV & QLT & trying to delete the reques from request queue. it is deleted but when im refreshing the queue its coming back in the queue.
while transporting other request its giving me error.
please help out me.

Hi Aasmi Gawas,
Please could you post the error?
We don't have a crystal ball to see the errors in your system...
Best Regards,
Erick ILarraza

Error in FM DDIF_NAMETAB_GET when deleting BI objects via transport request

Dear all,
when importing a transport request in which several types of BI objects are deleted (Infocubes, DSO's, transformations, routines, DTP's, query elements, infosets, process chains). The import terminates only when transporting from acceptance to production with return code 12 due to an uncaught exception:
Transporting from development to acceptance did not raise this exception.
The ST22 dump (see below) refers in the "contents of system fields" section to a DSO, and to post-import activities. The DSO and the associated tables could not be found (rsa1 & se16), since they are deleted as desired.
Some of the relevant notes that I have found do refer to DSO related problems, but they all indicate to install SP19 which we already have installed (BW 7.0 Patch Level 23)
Could you please assist in pointing out potential solutions based on the information from the ST22 Runtime Error below?
Kind regards,
PJ
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_RS_PROGRAM_ERROR
Date and Time 08.02.2011 10:48:14
Short text
 An exception occurred that was not caught.
What happened?
 The exception 'CX_RS_PROGRAM_ERROR' was raised, but it was not caught anywhere
 along the call hierarchy.
 Since exceptions represent error situations and this error was not
 adequately responded to, the running ABAP program
 'CL_RSDD_DS====================CP' has to be
 terminated.
Error analysis
 An exception occurred which is explained in detail below.
 The exception, which is assigned to class 'CX_RS_PROGRAM_ERROR', was not caught
 and therefore caused a runtime error.
 The reason for the exception is:
 Error in BW: Error in DDIF_NAMETAB_GET
How to correct the error
 If the error occurs in a non-modified SAP program, you may be able to
 find an interim solution in an SAP Note.
 If you have access to SAP Notes, carry out a search with the following
 keywords:
 "UNCAUGHT_EXCEPTION" "CX_RS_PROGRAM_ERROR"
 "CL_RSDD_DS====================CP" or "CL_RSDD_DS====================CM001"
 "APPEND_DS_TEC_FIELDS"
System environment
 SAP-Release 700
 Application server... "dp1ci"
 Network address...... "<removed>"
 Operating system..... "HP-UX"
 Release.............. "B.11.23";
 Hardware type........ "ia64"
 Character length.... 16 Bits
 Pointer length....... 64 Bits
 Work process number.. 45
 Shortdump setting.... "full"
 Database server... "spisap02"
 Database type..... "ORACLE"
 Database name..... "DP1"
 Database user ID.. "SAPBIW"
 Terminal................. " "
 Char.set.... "C"
 SAP kernel....... 700
 created (date)... "Dec 14 2009 20:47:35"
 create on........ "HP-UX B.11.23 U ia64"
 Database version. "OCI_102 (10.2.0.1.0) "
 Patch level. 236
 Patch text.. " "
 Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
 SAP database version. 700
 Operating system..... "HP-UX B.11";
 Memory consumption
 Roll.... 5979936
 EM...... 0
 Heap.... 1459888
 Page.... 40960
 MM Used. 6988880
 MM Free. 415648
User and Transaction
 Client.............. 000
 User................ "DDIC"
 Language key........ "E"
 Transaction......... " "
 Transactions ID..... "4D5111661004210BE10000000AFA2502"
 Program............. "CL_RSDD_DS====================CP"
 Screen.............. "SAPMSSY0 1000"
 Screen line......... 6
Information on where terminated
 Termination occurred in the ABAP program "CL_RSDD_DS====================CP" -
 in "APPEND_DS_TEC_FIELDS".
 The main program was "RDDEXECU ".
 In the source code you have the termination point in line 61
 of the (Include) program "CL_RSDD_DS====================CM001".
 The program "CL_RSDD_DS====================CP" was started as a background job.
 Job Name....... "RDDEXECL"
 Job Initiator.. "DDIC"
 Job Number..... 10475900
Source Code Extract
Line SourceCde
 31 RAISE EXCEPTION TYPE cx_rs_program_error
 32 EXPORTING
 33 text = 'Invalid DSO subtype'. "#EC NOTEXT
 34 ENDCASE.
 35
 36 * get table name from DDIC
 37 CALL METHOD cl_rsd_odso=>get_tablnm
 38 EXPORTING
 39 i_odsobject = n_infoprov
 40 i_tabt = l_tab
 41 IMPORTING
 42 e_tablnm = l_tablnm
 43 EXCEPTIONS
 44 OTHERS = 1.
 45
 46 IF sy-subrc <> 0.
 47 RAISE EXCEPTION TYPE cx_rs_program_error
 48 EXPORTING
 49 text = 'Error in CL_RSD_ODSO=>get_Tablnm'. "#EC NOTEXT
 50 ENDIF.
 51
 52 CALL FUNCTION 'DDIF_NAMETAB_GET'
 53 EXPORTING
 54 tabname = l_tablnm
 55 TABLES
 56 dfies_tab = l_t_comp
 57 EXCEPTIONS
 58 not_found = 1
 59 OTHERS = 2.
 60 IF sy-subrc <> 0.
>>>>> RAISE EXCEPTION TYPE cx_rs_program_error
 62 EXPORTING
 63 text = 'Error in DDIF_NAMETAB_GET'. "#EC NOTEXT
 64 ENDIF.
 65
 66
 67 ELSE.
 68 * model table only needed for standard datastore objects, for
 69 * write optimized DSOs target table is a changelog that is fully described by
 70 * dta_pro (infoobjects)
 71 CHECK n_s_dta-odsotype = rsdod_c_type-standard.
 72
 73 * get model table fields to add
 74 CALL METHOD cl_rsd_odso=>get_mod_tab
 75 IMPORTING
 76 e_mod_fld_ur = l_t_comp.
 77 ENDIF.
 78
 79 * according to T.B. ( 13.04.2007) the correct position is
 80 * not needed in the D version
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 1
SY-DBCNT 1
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Execute Post-Import Methods and XPRAs for Transport Request
SY-MSGTY E
SY-MSGID DA
SY-MSGNO 300
SY-MSGV1 /BIC/AV_AMOFCB40
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20110208
SY-UZEIT 104759
SY-XPROG SAPLSYST
SY-XFORM SYSTEM_HOOK_OPEN_DATASET

Hi All
We are also experiencing this same error when transporting deletions of multiple objects.
Although the transport was cancelled in the destination system (production) it appears to have largely deleted all objects successfully except for DSOs.
The DSOs still appear in the table RSDODSO (via SE11) but are not visible anywhere else. When you try to view the DSO via RSDODS a warning appears saying "DataStore object to be deleted by transport -> delete only allowed". If you try to delete them in this transaction the same ABAP runtime error as the transport appears.
Any assistance would be greatly appreciated!
Regards
David

Error when adding EPA file to transport request via CTS

I have a rather strange problem. Sometimes when attempting to add an EPA file to a Transport Request via CTS I get the following error in my logs with a corresponding short dump. This does not happen all the time.
#000255D36E8F005B00015391000003DC00046C0470FF1359#1244666238275#com.sap.portal.pcdadmintools#sap.com/irj#com.sap.portal.pcdadmintools#MOROZOWSKIJO#24750##rp1.conair.com_RP1_2406850#MOROZOWSKIJO#28167c7055fe11dea0f1000255d36e8f#SAPEngine_Application_Thread[impl:3]_10##0#0#Error#1#/System/Server#Java### [com.sapportals.portal.pcd.admintools.export.ExportCTSHandling] Could not attach epa file to transport request
[EXCEPTION]
{0}#1#com.sap.tc.di.draft.ts.TsExecutionException: Error executing function (check stacktrace for details):CTS_FILE_APPEND_TO_REQUEST, (service=com.sap.tms)
 at java.lang.Throwable.<init>(Throwable.java:216)
 at java.lang.Exception.<init>(Exception.java:59)
 at com.sap.tc.di.draft.ts.TsException.<init>(TsException.java:19)
 at com.sap.tc.di.draft.ts.TsServiceException.<init>(TsServiceException.java:16)
 at com.sap.tc.di.draft.ts.TsExecutionException.<init>(TsExecutionException.java:16)
 at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoExceptions.throwTsServiceException(TmsJCoExceptions.java:74)
 at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoExceptions.throwTsException(TmsJCoExceptions.java:35)
 at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.addFileToRequest(TmsJCoAdapter.java:536)
 at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsTransportService.handOverAsStream(TmsTransportService.java:253)
 at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsTransportService.requestUpdate(TmsTransportService.java:202)
 at com.sap.tc.di.draft.ts.impl.TransportRequestImpl.transmit(TransportRequestImpl.java:97)
 at com.sap.tc.di.draft.ts.impl.TransmissionPackageImpl.transmit(TransmissionPackageImpl.java:49)
 at com.sapportals.portal.pcd.admintools.export.ExportCTSHandling.attachFileToPackage(ExportCTSHandling.java:209)
 at com.sapportals.portal.pcd.admintools.export.pages.ExportStatusPage.prepareGenericPageSettings(ExportStatusPage.java:417)
 at com.sapportals.portal.pcd.admintools.export.pages.ExportStatusPage.dispatchPageRequest(ExportStatusPage.java:241)
 at com.sapportals.portal.pcd.admintools.export.ExportMain.doContent(ExportMain.java:89)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:166)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:111)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
 at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
 at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:438)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:404)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
 at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:79)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:332)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:0)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:335)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:963)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:249)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:0)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:92)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:35)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:103)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: The current application triggered a termination with a short dump.
 at java.lang.Throwable.<init>(Throwable.java:194)
 at java.lang.Exception.<init>(Exception.java:41)
 at java.lang.RuntimeException.<init>(RuntimeException.java:43)
 at com.sap.mw.jco.JCO$Exception.<init>(JCO.java:1117)
 at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)
 at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1224)
 at com.sap.mw.jco.JCO$Client.execute(JCO.java:3909)
 at com.sap.mw.jco.JCO$Client.execute(JCO.java:3417)
 at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.executeFunction(TmsJCoAdapter.java:112)
 at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.executeFunction(TmsJCoAdapter.java:133)
 at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapter.addFileToRequest(TmsJCoAdapter.java:531)
 ... 38 more
Edited by: Jon Morozowski on Jun 10, 2009 10:57 PM

Here is the short dump in the ABAP system.
Short text of error message:
INTERNAL ERROR UPDATING REQUEST DESC OF RP1K900690
Long text of error message:
Technical information about the message:
Message class....... "PU"
Number.............. 601
Variable 1.......... "INTERNAL ERROR UPDATING REQUEST DESC OF"
Variable 2.......... "RP1K900690"
Variable 3.......... " "
Variable 4.......... " "
I have checked the RFC destination in the J2EE Admin and that works OK. This has me kind of stumped.

Transport Request Ended with return code: === 12 ===

Hi
Good day to you.
We are able to move Transport Request from Development BW Client (with respect to an SEM-BCS Configuration) to Quality BW Client smoothly.
But when we move the same TR to Production client, we are getting the following error message. I would be very grateful if somebody could throw light on why it is happening, what could be its implications and what to do to avoid the same
Execution of programs after import (XPRA)
Transport request : DBWK901288
System : PBW
tp path : tp
Version and release: 340.16.37 640
Post-import methods for change/transport request: DBWK901288
 on the application server: sapbwpd
Post-import method FINB_TR_AFTER_IMP_METHOD started for UCREPGROUP T, date and time: 20081029144344
Post-processing taking place in client 300
Import carried out using RFC destination PBWCLNT300
Communication error: Destination PBWCLNT300 -> long text
Errors occurred during post-handling FINB_TR_AFTER_IMP_METHOD for UCREPGROUP T
FINB_TR_AFTER_IMP_METHOD belongs to package FINB_TRANSPORT_TOOL
The errors affect the following components:
 FIN-FB (Financials Basis)
Post-import method FINB_TR_AFTER_IMP_METHOD completed for UCREPGROUP T, date and time: 20081029144351
Post-import methods of change/transport request DBWK901288 completed
 Start of subsequent processing ... 20081029144344
 End of subsequent processing... 20081029144351
Execute reports for change/transport request: DBWK901288
 on the application server: sapbwpd
There are no reports to execute
Execution of programs after import (XPRA)
End date and time : 20081029144351
Ended with return code: ===> 12 <===
Regards
Siddique

Hi Siddique,
Looks like your RFC destination is wrong. The proper syntax is FINBTR@<system>CLNT <client>.
See also the note 644610.

How to set at the server level to log transport request in SAP ME

Hi:
when I do configuration in SAP ME, can I set at the system level to log for transport request ?
so I can use transport request for other client or server.

Hi!
There is no "transport request" in SAP ME, however, there is Configuration Data Transfer Export/Import activity which can export the data to ZIP file at the source site and then import that file at the destination site.
CDT activity can utilize CTS+ as a transport channel but I would suggest ZIP file instead because the file can be edited manually in case of any issue or if you want to remove some data.
For details, please consult this How-To Guide.
Regards,
Sergiy

Error during import of Transport Request in PI 7.1

Hi Friends,
I have installed PI 7.1 server on HP-UX 11.23 with Oracle 10g.
After completing all the post-installation activities,I configured CTS for moving objects developed by PI consultant to Quality & Production server.
Using CTS I Successfully imported all objects in Integration Repository but When Iam trying import objects of Integration directory,it is showing the error during deployment phase.
Copy File Between Transport Groups 23.10.2008 13:04:07 (0) Successfully Completed
Import 23.10.2008 13:04:26 (0) Successfully Completed
Check Versions 23.10.2008 13:04:26 (0) Successfully Completed
Deployment 23.10.2008 13:04:28 (12) Canceled
When I go to Log of above it displays follow
Deployment
Transport request : SPDK900031
System : SPT
tp path : tp
Version and release: 375.30.40 710
CTS Deploy Service - Version 0.92 06.03.2007
========================================================================
Deploy Web service destination = CTSDEPLOY
Directory = /usr/sap/trans/data
SDM Deploy URL =
SLD Deploy URL =
XI Deploy URL = http://srstlspt:50000
Double-stack system SPT
Deploy for XID
Deploy File = 60913470a0d511dd873000306eeac205
Communication error in Web service CTSDEPLOY , exception is CX_AI_SYSTEM_FAULT
SoapFaultCode:1 Authentication failed. For details see log entry 00306EEAC205004E0000091A00000EC703
>>>51C766E6CBB4F0 in security log.
Return Code = 12
Highest Return Code = 12
Deployment
End date and time : 20081023151500
Ended with return code: ===> 12 <===
Regards,
Sunil

hi,
I am looking forward to implement SAPKW70017, I need to know the CONS of SP17, what was the reason which made you implement SP17, just to have updated Version of SP or did you face with any problems and decided to update the SP? what was the previous SP which you had,
We have problems in F4 search help when running queries, SAP asked us to implement latest which is SP17, but wanted to make sure what would be the CONS before we do it, we are having SP15 in BI 7.0
Please update the post for this.

Problem transporting Request from Development to Quality Assurance Server

Hi All,
I m facing a problem of Transporting requests from one System to other.
When adjusting the Request ,the error message reads as follows :
RFC system error in system/destination
[email protected]_HSE
Now,when I check the RFC Connection for [email protected]_HSE,,
i get the message :
" License Check required "
Please respond to this query urgently.....
Thanks in advance

Hi!
I think it's better to call SAP support, if you have problems with the licenses...
Maybe your company forget to pay their fees since a while
Regards
Tamá

Program to Track the Transport Request

Hi Experts,
I got a requirement to write a program which can track and compare the Transport Request between the servers(Development ,Test and Production) .
If in case is there any descrepancy between the versions (In the server) it should throw an error saying that particular thing is missing or not synchronized.
For ex: If the program which is in Development server has some structure dependent to the code which is address to single TR.
where as same version of the program in Test don't have structure ,it has to throw an mismatch error.
If you guys have any clue on this please throw some light.
Higher points will be rewarded for every useful inputs.
Thanks in Advance,
Dharani

Hi Dharani,
Some sample Code. This I got debugging the SAP Standard.
TYPE-POOLS: strhi.
Data varaints for remote compare
INCLUDE rvscdcom.
INCLUDE rsvcutct. "Utilities, Constants, Types
INCLUDE rsvcvcct. "General Constants Types
INCLUDE rsvcvdct. "VRSD Constants Types
INCLUDE rsvctrct. "Tables for transports details
INCLUDE rsvcditd.
INCLUDE ole2incl.
DATA: application TYPE ole2_object.
DATA: remote_info_line LIKE abaptext-line,
 remote_info_line_a LIKE vrsinfolna,
 remote_info_line_b LIKE vrsinfolnb,
 remote_versno LIKE vrsd-versno,
 remote_objname LIKE vrsd-objname,
 remote_objtype LIKE vrsd-objtype,
 remote_system LIKE tadir-srcsystem,
 returncode LIKE sy-subrc.
DATA: srcsys LIKE tadir-srcsystem,
 author LIKE tadir-author,
 mslang LIKE tadir-masterlang,
 devcla LIKE tadir-devclass,
 notfnd LIKE bool.
INCLUDE rsvceudb.
INCLUDE rsvcvdtd. "VRSD Constants Types
INCLUDE rsvctrtd. "Tables for transports details
INCLUDE rsvctrfo. "Interface for transport details
INCLUDE rsvcrmck. "Remote Access Utilities: Checks
 PERFORM get_rfc_destination USING srcsys
 CHANGING w_destination1.
 SELECT SINGLE objname objtype korrnum FROM vrsd
 INTO CORRESPONDING FIELDS OF it_transports
 WHERE objname = it_abap_hdr-obj_name
 AND objtype = it_abap_hdr-object
 AND versno = '00000'.
 it_transports-trkorr = it_transports-korrnum.
Open tranport number with object name
 SELECT SINGLE trkorr pgmid object obj_name FROM e071
 INTO CORRESPONDING FIELDS OF it_transports
 WHERE trkorr = it_transports-trkorr
 WHERE trkorr NE 'SW3_P00001'
 WHERE pgmid EQ it_abap_hdr-pgmid
 AND object EQ it_abap_hdr-object
 AND obj_name EQ it_abap_hdr-name
 AND lockflag EQ 'X'.
Open tranport number with object name
 SELECT SINGLE as4user as4date FROM e070
 INTO CORRESPONDING FIELDS OF it_transports
 WHERE trkorr = it_transports-trkorr.
Remote compare
 IF p_rcomp = 'X'.
 CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
 EXPORTING
 text = 'Remote Comparison started'.
 IF w_destination1 NE space.
 PERFORM remote_compare USING w_destination1.
 IF it_transports-korrnum EQ it_transports-trkorr.
 it_abap_hdr-in_qa = 'Same version'.
 ELSEIF it_transports-korrnum IS INITIAL.
 it_abap_hdr-in_qa = 'Not found'.
 ELSE.
 it_abap_hdr-in_qa = 'Not Same version'.
 ENDIF.
 MODIFY it_abap_hdr.
 ENDIF.
FORM get_rfc_destination USING pi_orgsys
 CHANGING po_destination.
Baustein zur Auswahl von R/3-Destinationen.
FUNKTION(EN):
ruft einen FB, der den Anwender eine Destination für den
Aufruf der Versionsverwaltung als REMOTE-Function-Call
auswählen läßt.
Parameter:
PI_ORGSYS LIKE TADIR-SRCSYSTEM
PO_DESTINATION LIKE RFCDES-DESTINATION
DATA: dest_note(60). " für STRA Baustein
IF pi_orgsys = space.
 po_destination = space.
 dest_note = space.
ELSE.
 IF pi_orgsys <> sy-sysid.
 po_destination = pi_orgsys.
 ENDIF.
 CONCATENATE
 'Note: The original system of the object is the system'(l11)
 pi_orgsys INTO dest_note SEPARATED BY space.
 CONCATENATE dest_note '.' INTO dest_note.
ENDIF.
CALL FUNCTION 'SVRS_GET_RFC_DESTINATION'
 EXPORTING
 p_text = dest_note
 IMPORTING
 remote_dest = po_destination
 EXCEPTIONS
 no_destination = 1
 OTHERS = 2.
IF sy-subrc <> 0.
Falls keine Destination ausgewählt wurde:
 po_destination = space.
ENDIF.
ENDFORM. "get_rfc_destination
INCLUDE LSVRLF07 *
FORM get_version_list_remote USING pi_objtype pi_objname
 CHANGING po_no_entry.
DATA: old_state LIKE bool.
REFRESH: vrs_dir_vrs, logvers_dir.
PERFORM check_vc_state_remote CHANGING old_state.
IF old_state = true.
 PERFORM get_old_fashioned_versdir USING pi_objtype pi_objname
 CHANGING po_no_entry.
ELSE.
 CALL FUNCTION 'SVRS_GET_VERSION_DIRECTORY_46'
 EXPORTING
 destination = dir_destination
 objname = pi_objname
 objtype = pi_objtype
 TABLES
 version_list = vrs_dir_vrs
 lversno_list = logvers_dir
 EXCEPTIONS
 no_entry = 1
 system_failure = 2
 communication_failure_ = 3.
 CASE sy-subrc.
 WHEN 0.
 po_no_entry = false.
 WHEN 1.
 po_no_entry = true.
 WHEN 2.
 'Fehler im Zielsytem'.
 MESSAGE W123.
 LEAVE.
 WHEN 3.
 'Keine Verbindung zum Zielsystem'.
 MESSAGE W124.
 LEAVE.
 ENDCASE.
ENDIF.
ENDFORM. "get_version_list_remote
 FORM CHECK_VC_STATE_REMOTE *
FORM check_vc_state_remote CHANGING po_old_state.
DATA: head_entry LIKE vrsd.
PERFORM get_vrsd_entry_remote
 USING head_type head_objname head_versno
 CHANGING head_entry po_old_state.
ENDFORM. "check_vc_state_remote
 FORM GET_VRSD_ENTRY_REMOTE *
FORM get_vrsd_entry_remote USING pi_objtype pi_objname pi_versno
 CHANGING vrsd_entry po_no_entry.
CALL FUNCTION 'GET_VRSD_ENTRY_46'
 EXPORTING
 destination = dir_destination
 objname = pi_objname
 objtype = pi_objtype
 versno = pi_versno
 IMPORTING
 vrsd_entry = vrsd_entry
 EXCEPTIONS
 no_entry_found = 1
 system_failure = 2
 communication_failure = 3.
CASE sy-subrc.
 WHEN 0.
 po_no_entry = false.
 WHEN 1.
 po_no_entry = true.
 WHEN 2.
 'Fehler im Zielsytem'.
 MESSAGE W123.
 LEAVE.
 WHEN 3.
 'Keine Verbindung zum Zielsystem'.
 MESSAGE W124.
 LEAVE.
ENDCASE.
ENDFORM. "get_vrsd_entry_remote
 FORM GET_OLD_FASHIONED_VERSDIR *
--> PI_OBJTYPE *
--> PI_OBJNAME *
--> PO_NO_ENTRY *
FORM get_old_fashioned_versdir USING pi_objtype pi_objname
 CHANGING po_no_entry.
DATA: vrsd_entry LIKE vrsd.
DATA: object_not_found LIKE bool.
PERFORM get_vrsd_entry_remote
 USING pi_objtype pi_objname null_versno
 CHANGING buffer0 po_no_entry.
IF po_no_entry = false.
 CALL FUNCTION 'GET_VERSION_LIST_46'
 EXPORTING
 destination = dir_destination
 objname = pi_objname
 objtype = pi_objtype
 TABLES
 version_list = vrs_dir_vrs
 EXCEPTIONS
 system_failure = 1
 communication_failure = 2.
 CASE sy-subrc.
 WHEN 1.
 'Fehler im Zielsytem'.
 MESSAGE W123.
 LEAVE.
 WHEN 2.
 'Keine Verbindung zum Zielsystem'.
 MESSAGE W124.
 LEAVE.
 ENDCASE.
 SORT vrs_dir_vrs DESCENDING BY versno.
 LOOP AT vrs_dir_vrs.
 logvers_dir-versno = vrs_dir_vrs-versno.
 APPEND logvers_dir.
 ENDLOOP.
 READ TABLE vrs_dir_vrs INDEX 1.
 IF vrs_dir_vrs-versmode = impt_mode.
 Es gibt einen offenen Import, setze Flag zurück:
 vrs_dir_vrs-versmode = corr_mode.
 ENDIF.
 vrs_dir_vrs-versno = 0.
 MODIFY vrs_dir_vrs INDEX 1.
ENDIF.
vrsd_entry = buffer0.
PERFORM add_active_version_remote
 CHANGING vrsd_entry object_not_found.
IF object_not_found = false.
 po_no_entry = false.
ENDIF.
Möglicherweise gibt es eine überarbeitete Version.
PERFORM add_modif_version_remote
 CHANGING vrsd_entry object_not_found.
IF object_not_found = false.
 po_no_entry = false.
ENDIF.
ENDFORM. "get_old_fashioned_versdir
 FORM ADD_ACTIVE_VERSION_REMOTE *
--> VRSD_INFO *
--> PO_NOT_FOUND *
FORM add_active_version_remote CHANGING vrsd_info STRUCTURE vrsd
 po_not_found.
DATA: object_not_found LIKE vrsd-versmode.
DATA: nplus1 LIKE vrsd-versno.
DATA: retcode LIKE bool.
CALL FUNCTION 'FIND_OBJECT_40'
 EXPORTING
 destination = dir_destination
 objname = vrsd_info-objname
 objtype = vrsd_info-objtype
 IMPORTING
 object_not_found = object_not_found
 EXCEPTIONS
 system_failure = 1
 communication_failure = 2.
CASE sy-subrc.
 WHEN 1.
 'Fehler im Zielsytem'.
 MESSAGE W123.
 LEAVE.
 WHEN 2.
 'Keine Verbindung zum Zielsystem'.
 MESSAGE W124.
 LEAVE.
ENDCASE. " SY-SUBRC.
IF object_not_found = space.
 po_not_found = false.
ELSE.
 po_not_found = true.
ENDIF.
CLEAR: vrsd_info-korrnum, vrsd_info-author,
 vrsd_info-datum, vrsd_info-zeit.
IF po_not_found = false.
 IF vrsd_info-versmode = impt_mode.
 Es gibt einen offenen Import, und einen Satz n+1 der
 uns verschwiegen wurde. Er beschreibt die aktive Version
 nplus1 = vrsd_info-lastversno + 1.
 PERFORM get_vrsd_entry_remote
 USING vrsd_info-objtype vrsd_info-objname nplus1
 CHANGING vrsd_info retcode.
 ELSE.
 PERFORM get_korrinfo_remote CHANGING vrsd_info.
 ENDIF.
 MOVE-CORRESPONDING vrsd_info TO vrs_dir_vrs.
 vrs_dir_vrs-versno = null_versno.
 logvers_dir-versno = acti_versno.
 INSERT vrs_dir_vrs INDEX 1.
 INSERT logvers_dir INDEX 1.
ENDIF.
ENDFORM. "add_active_version_remote
 FORM ADD_MODIF_VERSION_REMOTE *
FORM add_modif_version_remote CHANGING vrsd_info STRUCTURE vrsd
 po_not_found.
DATA: mod_dd_exists LIKE vrsd-versmode.
CALL FUNCTION 'TEST_MOD_DD_40'
 EXPORTING
 destination = dir_destination
 objname = vrsd_info-objname
 objtype = vrsd_info-objtype
 IMPORTING
 mod_dd_exists = mod_dd_exists
 EXCEPTIONS
 system_failure = 1
 communication_failure = 2.
CASE sy-subrc.
 WHEN 1.
 'Fehler im Zielsytem'.
 MESSAGE W123.
 LEAVE.
 WHEN 2.
 'Keine Verbindung zum Zielsystem'.
 MESSAGE W124.
 LEAVE.
ENDCASE.
IF mod_dd_exists <> space.
 po_not_found = false.
 PERFORM get_korrinfo_remote CHANGING vrsd_info.
 MOVE-CORRESPONDING vrsd_info TO vrs_dir_vrs.
 vrs_dir_vrs-versno = modi_versno.
 logvers_dir-versno = modi_versno.
 INSERT vrs_dir_vrs INDEX 1.
 INSERT logvers_dir INDEX 1.
ELSE.
 po_not_found = true.
ENDIF.
ENDFORM. "add_modif_version_remote
 FORM GET_KORRINFO_REMOTE *
FORM get_korrinfo_remote CHANGING vrsd_info STRUCTURE vrsd.
CALL FUNCTION 'GET_KORRNUM_AUTHOR_DATUM_40'
 EXPORTING
 destination = dir_destination
 objname = vrsd_info-objname
 objtype = vrsd_info-objtype
 IMPORTING
 author = vrsd_info-author
 datum = vrsd_info-datum
 korrnum = vrsd_info-korrnum
 zeit = vrsd_info-zeit
 EXCEPTIONS
 system_failure = 1
 communication_failure = 2.
CASE sy-subrc.
 WHEN 1.
 'Fehler im Zielsytem'.
 MESSAGE W123.
 LEAVE.
 WHEN 2.
 'Keine Verbindung zum Zielsystem'.
 MESSAGE W124.
 LEAVE.
ENDCASE.
IF vrsd_info-korrnum <> space.
 Korrektur ist offen, Zeitstempel korrigieren:
 vrsd_info-datum = sy-datum.
 vrsd_info-zeit = sy-uzeit.
ENDIF.
ENDFORM. "get_korrinfo_remote

Import GP Local Transport Request Package

Hi, SDN Expert.
I am trying to move my GP Process from one system to another system.
I have create the transport package in sda format in to my local drive through "GP Transport" --> "Create transport request". When I tried to import the transport package through "GP Transport" --> "Import transport request". The only option for me to import the package is through End Point Alias. I do not have the End Point Alias setup, as I plan to import the transport package locally.
My question is what is the right channel to import the sda package that I have exported? Is that through "GP Transport" --> "Import transport request" (but I don't see that option to import sda). Or I can use SDM tool to do so?
Thanks,
KC

Hello,
if you are using netweaver 7.0 :
After exporting there is an option "download sca file", click there , download it to your pc and then you will have to use SDM to upload it in the destination system.
Then you have to release the transported objects:
After uploading it, log in into the destination system , go to guided procedures -> administration -> Import transport requests --> go to the process you transported and select it so you can release it for use.
Regards,
Marco.

Error within General Task: Register transport request in task list

Dear all,
I would like to register transports into a task list. When I try to do so I get the following error:
Error RFC destination SPROJECT_GET_SMI_DATA_R: Projekt: ZCHARM_DQ
Message no. /TMWFLOW/TASKLIST191
Some one got an idea where the problem might be?
Any help would be much appreciated.
Best regards
Daniel

Hi Daniel,
This error is reported in SDN blog /people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-questions-and-known-errors
in point 21
21. Missing authorization for READ RFC connections
Our default authorizations for remote READ RFC users (created in SMSY) do not allow us to read transport requests information. But READ RFC users are used extensively in Charm to get those information. It is a bug in SMSY which has not been fixed by now. So currently for such kind of messages we have to ask our customer to manually add appropriate authorizations (e.g. profile S_TMW_CREATE) to those READ RFC users.
- Open transport requests are not marked as red when release them from task list.
Note 1279558 - Red Question Mark Icon Missing from Charm Transport Release
- "Error RFC destination SPROJECT_GET_SMI_DATA_R" when register outside transport requests into Charm.
Please assign enough authorizations to all those READ RFC users on their DEV system (including client 000).
- Cannot complete maintenance cycle due to "Error RFC destination /TMWFLOW/TL_COMPL_CHK_TR_WO_TL"
Please assign enough authorizations to all those READ RFC users on their DEV system (including client 000).
- Transport request information is missing in the result of Charm Reporting.
Please assign enough authorizations to all those READ RFC users on their DEV system (including client 000). And after that they should re-execute background job SM:TMWFLOW_CMSSYSCOL to update those information on Solution Manager system again.
Hope this helps,
Dolores

How to remotely control objects from transport request

Hi all,
I have to perform some task but can't find the way to get it done. What I have to do is:
a) get list of transport requests for given SAP system (i.e. its import queue)
b) let the user choose transport requests from the list
c) get list of all objects from chosen transport requests
d) control these objects in source and destination (from point a) ) SAP system.
Points a) to c) are easy and already done (using appropriate function modules and ALV objects). But I have no idea how to do things from point d). Control means comparison of dates (i.e. last modified) of objects in source and destination SAP system. The main goal of this approach is to avoid transportation of older objects from source system (DEV) and overwritting newer versions of the objects in destination system (PRD). I tried to use SAP versioning system to check versions remotely (the same way as it can be done from standard SAP transactions, e.g. SE38 for program source) with RFC and it worked fine (see function module SVRS_DISPLAY_REMOTE_DIR). But what about other objects not covered with versioning system? There are 932 objects that can be transported (at least TR_OBJECT_TABLE function module says so). Versions management system covers about 30 (program source, function module, object methods, table definitions, lock objects, and so on) of them. The problem is with the rest (900 transportable objects).
How can I check their dates remotely in source and destination SAP system. Any clues? Manual retrieval of the information about dates of 900 various SAP elements must be very difficult (if possible at all) because so many objects must be spreaded out in many tables. Is there any universal or standard way (report, RFC function module) to get required information?
Thanx in advance,
Jacek Witczak

Hi
There is no automatic way to delete the unnecessary objects from the transport reqeust.
1. Go to Tcode se09 and select the request which contains the unnecessary objects.
2. Select the unnecessary objects and delete manually.
Also if you want to delete the entire request then unlock the request in the tcode SE03 and then delete the request completely.
Also note that if the request is released then you will not be able to delete the objects in that request.
Hope it helps.
Regards
Sadeesh

Export Transport Request to a File

Hi Everyone,
I have a package that contains number of programs and tables and I would like to ship this package to a customer.
I need some help in creating a new transport request that will allow me to export this transport as a file that I can give to
the customer so that they import the transport in easy and fast way.
Thanks
Misbah

I run this transaction to perform a test (RSTPTEST ):
Check Transport Tool                                       16.12.2009 14:27:47
|
---   NSP System NSP
      |
      |--   tp Interface
      |   |
      |   |-----Host Name             thinkpad
      |   |-----Version               1.80
      |   |-----Transport Directory   \\thinkpad\sapmnt\trans
      |   ------Logging               On (TPLOG contains 1760 entries)
      |
      |--   Transport Profile
      |   |
      |   |-----Path                  \\thinkpad\sapmnt\trans\bin\TP_DOMAIN_..
      |   |-----Profile               Cannot read tp profile
      |   ------Version               tp profile has an invalid format
      |
      |--   RFC Destination
      |   |
      |   |-----Destination           CALLTP_WindowsNT
      |   |-----tp Path               C:\SAP\NSP\SYS\exe\run\tp.EXE
      |   |-----tp Executable         Size: 5.709.824 bytes
      |   ------RFC Ping              timeout during allocate / CPIC-CALL: '..
      |
      ---   tp Call
          |
          |-----RFC Link              timeout during allocate / CPIC-CALL: '..
          |-----tp Version
          |-----DB Connect
          ------Offline Call          timeout during allocate / CPIC-CALL: '..
Edited by: Misbah on Dec 16, 2009 9:31 PM

Transport Request in ChangeRequest Mamnagement

Hi all,
While creating a transport request from solution manager,it creates 2 request-one customization and one work bench.Why it creates 2 request?Pls help on the above issue.

It creates one transport request for ABAP changes and another for configuration changes. You use whichever one you need to make the required changes. Later in the process, when you perform the "Complete Development" on the Normal Correction, Solution Manager will delete any Transport Tasks or Transport Requests that you did not use.
Having said all of that, I ofen get the error "System cancel RFC destination SM_TSHCLNT030_TMW, Call TR40_ORDER_DELETE: Trying to establish a connection using RFC destina tion SM_TSHCLNT030_TMW" when Solution Manager tries to perform this action. I end up having to delete the empty Transport Tasks and Transport Requests manually on the satellite system in order to be able to "Complete Development" on the Normal Correction. For Urgent Corrections, the equivalent process works fine.

Porblem while transfering objet from one transport request to another

Hello all,
My goal was to change objets from a task TA(source) into a transport request RA to the task TB(destintaion) into the transport request RB.
I used SE10 function on transport request RB(destination) and used function "Include objects" (Ctrl+F11) and then provided the source transport request (RA).
Te result is :
- source transport request RA remain unchanged
- in destination transport request RB a line as been added :
comment : object list included : and the name of source request RA, it look like a reference
Expected result was :
- objet are no more in source request RA
- the are assigned to destination request RB
What point did I miss ?
What can I do from this point to obtain expected result ?
Thans for your help,
Regards

I found an easy way to delete the reference line :
in SE01, display TR that contain reference line, double click to get the objects list, switch to change mode and use delete row function.
So at this point, my question is :
what is the appropriate way to change object from a transport task to another ?
Thanks for help,
Regards

Transport Request destination

Similar Messages

Maybe you are looking for