Program attached to wrong transport request and sent to QA, now what?

hi, while doing a program bymistake i have taken a request id of another program which has been send to quality
now my running program has been attach to that program please please help me out iam in great trouble...............
how to remove that from version management...............
Thanks
Edited by: Thomas Zloch on Jan 5, 2012 - subject enhanced

Hi,
If you want to retrieve the older version of that program in quality, then you need to go to -->version management and retrieve the older version of that program in development system. Capture it in a new transport and transport it to quality.
Or If it is a new report and you don't want that to be in quality then delete the new report and capture it in a new Transport and transport it to quality.
You can use this report RS_DELETE_KEY_IN_TRANSPORT2 in se38 to delete the objects from transport requests.
Regards,
Selva M
Edited by: Selva M on Jan 5, 2012 7:26 PM
Edited by: Selva M on Jan 5, 2012 7:32 PM

Similar Messages

Regarding Transport Request and related program names

Hi All,
I have a issue with picking Program Names from Transport Request names.
I am using E071 table to pick up all the Objects/Program Names based on TR's.
But for the TR's which are having D-Modifiable status i am not getting any entries from E071 table.
Can anybody give me alternate table which will give us All Program names under a TR based on TR for which status is D.
Thanks in advance.
Thanks,
Deep.

Hi Deep,
When the transport request is not released (i.e it is in Modifiable status) all the objects are linked to the tasks under the transport request. So if you are trying to get all the objects in the transport request(in modifiable status), first you have to get all the tasks under the transport request and get the objects under each task from E071 table.
You can get the taskes under the transport request by selecting from E070 table
select * from E070 where STRKORR = <your transport request numer>
then you can get all the objects for each task .
- Kalyan

How could we delete transport request and task(the released one)

Hello
We have a released transport task(not request). Transport request is not released.
How could we delete transport request and task(the released one). Namely we would not like to transport it to production

Hi, never delete directly in table.
There are more tables which depends each other...
Here, you can find nice example how to do it: Help on ABAP: Few Tips for Transport Request Manipulation
Using program: RDDIT076 and changing status.

Transport Request and Cross-Application techniques

Respected Members,
I want to know what is the difference between the transporting request and Cross-Application Technique( eg ALE)
Generally suppose you have made some object in development server and then a transport request will be created and through transporting to the production server same data can be transported to production server.
Same thing we do with ALE also that we can transport the data from one server to another server or from one client to another client.
THen what will be the difference between the transport objects and Cross-Application techniques.
Clear this picture by giving your valuable answers.
Thanks a Lot.
Manish

Hi Manish,
The applications transferred through Transport Requests and the data passed through ALE or EDI are completely different technologies.
The Transport requests transfer the programs and the configurations that you do within the development Server or rather the SAP system to the Production Server and then you execute them to get the desired result.
On the other hand,ALE(Application Linking and Enabling) or EDI(Electronic Data Transfer) transfers the data or rather business documents(for example vendor payments or making the payme nt through cheques) from one system to another system,i.e different Landscapes.
If suppose you want to transfer the data from one SAP system to another SAP system which are in completely different landscapes,then you use ALE and in case you transfer it from one SAP system to another Non-SAP system or vice-versa,you use EDI.
Moreover,you cannot view the coding or the configuration part in case of ALE or EDI whereas you can view the same in terms of Transport requests.
The landscape means all the clients within one SAP system.
I hope I have made it In case you have any further clarifications,do let me know.
Regards,
Puneet Jhari.clear.

Attach items to transport request

Hi all,
I have a need to attach few hundred tables to a transport request and I'm looking for an existing function module that can automate this task. Now, I still have to attach each item manually. Any help would be appreciated.
Regards,
Franck

In SE03, under 'Objects in requests', there is an option to 'Include objects in a transport request'. This might help if you have all your tables in the same package.
Sudha
Message was edited by: Sudha Mohan

My Mac laptop was running fine till I downloaded the latest itunes version this week, now all the programs are slow, ITUNEs cuts in and out. Anyone know what I did wrong?

My Mac laptop was running fine till I downloaded the latest itunes version this week, now all the programs are slow, ITUNEs cuts in and out. Anyone know what I did wrong?

Hello Mark Malecki,
Thanks for the question, and welcome to Apple Support Communities.
I understand you are having some issues with iTunes on your MacBook. You may want to isolate the issues further by testing to see if they persist in a new user account:
Isolating an issue by using another user account
http://support.apple.com/kb/TS4053
You can also try starting iTunes in safe mode:
iTunes: Troubleshooting issues with third-party iTunes plug-ins
http://support.apple.com/kb/TS3430
Thanks,
Matt M.

What's the difference between transport request and change request

Hi, I am reading TMS part of TADM12-1 now, and confused about two terms mentioned in this book, transport request and change request.
Is there any difference with them? Please advise. Thanks
James

In the context of course tadm12 transport request = change request

Transport request failed; recollected with new TR;what happens to first one

Hi,
I released a transport request and requested that the request be transported to the testing environment.
I received a message from Basis that the transport failed. I suspected that it might fail because I say many duplications in se09.
To fix this problem, I basically recollected the objects carefully and under a new transport request number; and released it.
I have requested that the Basis team move the new request to the testing environment.
1. What is wrong with what I did?
2. If the second request successfully gets moved to the testing environment, what becomes of the first request which was released, therefore no more available in development for me to delete? I tried to delete it under the "Released" section in se09 but got a message that it is not available to delete.
3. Could I have used the same Transport Request number the second time around, although the first number had been previously released?
Thanks

1. What is wrong with what I did?
It depends, did you check the Log.
Log should tell you why it failed or atleast give you some hints.
Ex : Missing objects ..might have been locked in an other request.
2. If the second request successfully gets moved to the testing environment, what becomes of the first request which was released, therefore no more available in development for me to delete? I tried to delete it under the "Released" section in se09 but got a message that it is not available to delete.
If the second request contains similar objects to the ones in first, everything will get overwritten in the target system.
TR1 - 10 Objects
If TR1 returns RC=8 due to one object, 9 objects will be successfully transported. You may only transport the failed one in the next request with its corrections.
3. Could I have used the same Transport Request number the second time around, although the first number had been previously released?
Yes, same released request can still be imported more than once but it may result in the same.
Try to find the reason the request failed, accordingly add objects in the next corrected request.
You can also copy requests into an other.
RClick on the request - Include Objects ( Ctrl + F11 ) - Enter Request Name.

I bought windows and have a Mac now what can I do?

I bought windows and have a Mac now what can I do?

Downloads are single platform, but if you have PSE13 you can swap it for a Mac version. If you have an earlier version. I'm sorry you are out of luck.
If you need to buy again it's worth looking around on-line as there are often cheaper deals in January.

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

Transport Request and Task

Hi,
Can someone explain a basic, when we transport a BI object, we see 2 things in se10/se09- one request and the other one task.
My question:
1. What is the significance of each of them and the use?
2. What process should be followed here and what sequence.
-TC

Ok.
Here is what I understand from youre replies above-
1. A request can have multiple tasks and each tasks corresponds to the work that is being transported.
2. One needs to release the tasks before we can release a request.
Suppose now, I have the following scenario:
I have changed an infoobject(ZABC) being used in multiple cubes (A,B,C). In this scenario how do I go about it. I understand that I need to transport and import the infoobject first and then the cubes.
So if I am working on a Transport Connection in RSA1. What would be the steps? I am writing the steps, correct me if I am wrong-
1. I select the infoobject and drag it to the right screen. I press the truck symbol and mention the package.
2. I drag the Cube A and press the truck symbol and mention the package
3. Same thing for other cubes.
Please let me know the optimum way.
-TC

Transport request and task releasing?

Hi all,
I've three systems dev,QA and prod.I'm working on dev client and I've a two reports(say A and B) under the same transport request with different tasks,If I want to release the report 'A',is it necessary that I shud be releasing th ewhoel request number or if I release the task it's enough.why a transport request will have different tasks,when the transportationof ht ese taks associated with the transport request is independent.
I've released the task to QA and the QA sytem had some problem and did nto get he task,what I shud be doing now,release the task again or ?
Can a report be assigned to different tasks(numbers) under the same transport request.can the report be assiged to different transport requests.please let me know.
thanks and regards
Message was edited by: henry

There is a transport route defined by your Basis Team for the transport scenarios. There, the possible ways through which request can be moved( from Dev --> QA & Dev --> Prod ) are defined.
But it does not mean that you can't transport your request to production without transporting it to QAS.
Furher, when you release a transport request, it does not automatically move to QAS or Production but someone from your Basis Team has to run the TP through Xn STMS, which in turn imports the objects from your Dev Request and put it on QAS / Production.
In case of any error encountered while importing to let's say QA, you need to check whether it's a problem with the transport buffer or is it because some objects are missing from the transports or dependent transports are not moved as yet.
Please understand that there is no concept of re-release.
You can only ask your Basis guy to re-import it.
According to the encountered problem, you need to decide whether you should just ask you Basis consultant to re-import the same Transport.
Or create a new request through SE10, and include all the objects from your last request. Release it and ask your Basis guy to import it to QAS.
Or first move the dependent transport and then ask your Basis guy to re-import your current transport.
Or create and group the changed objects, altogether in a new transport by changing all the objects which were contained in the original request.
Further, to your other queries, if two users are modifying the same program ( not exactly at the same time - that's not possible but one after other )then that program will be contained in two separate tasks of the same transport request.
I hope it answers a few of your queries.
Thanks,
Ram

Transport request and objects

hi experts,
can anybody tellme how u transport requets and how u transport objects.

hi,
You can check all the requests in SE01 or STMS.
You should know how STMS works at least.
In STMS you normally select the system (DEV/QA/PRD) for which you want to look at transport requests. After selecting the relevant system, you normally get to see the 'IMPORT QUEUE'. This means the following:
(make sure you press the REFRESH button first)
1) transport requests in the import queue of your QA system are not imported yet. (imported ones, you can find back via the menu by selecting the 'IMPORT HISTORY'.
So if you want to find out about requests that are already on your QA system, but NOT on your productive system, you just select PRD , and look at your import queue for this particular system. These transports that you see there are ALREADY imported on QA , but not yet on the production system.
Case Closed I would say, not??
The only thing that might make my statement 'uncertain' is if the company has a specific 'approval procedure'. For example, suppose you have released a new development on your development system. An automatic job imports every hour all released transports from your development system into your QA system. (ofcourse you can always manually import a request).
Now after an hour the request is automatically imported on your QA system and you can do the necessary Unit and Integration testing.
Now, under normal circumstances, after import of your request on the QA system, in STMS it will automatically appear in the import list of the production system.
In case of the approval procedure however, you first might need to select tested requests, select them, approve them (via an approval button ) and run a job to release all approved requests. Only after they are released by the job, they will appear in the Import Queue of the production system.
But ok, I only saw this in practice at one customer so far...but just that you know
regs,
hema.

Transport request and Message class?

Hi,
How to create a transport request for the changes I made in a content of the table (eg: T100 ) so that the changes can reflect in all clients. and please mention the name of message class for the object BUS2121 or else name the message class for the messages that has been used in shopping cart email templates.
regards,
George.

Hi,
The message for SC is BBP_PD, you will find in SE91 txn. and you would need to know the message number to customize it, you can do it in SPRO-Cross-application settings-> Message control, and then select BUS2121 and add new entry to change it from standard.
Award Pointsif helps.
Thanks.

Whats the diff between copying a Transport request and Importing a request?

Hi gurus,
Can some one explain me the difference between copying a transport request between clients and importing transport request between clients? say for eg: difference between copying a transport request containing a datasource being copied from client 100 to client 200 and importing the same request from client 100 to client 200?... When do we follow such scenario's?
thanks.
kishore

Hi Kishore,
A request copy applies only for customizing (client dependent) objects.
A request tracks object modifications since its last transport. if the object is created in source system and included in a transport request, when it is transported to another system, it will create the object in target system. Then if you modify the object, it will include modifications since last transport.
As i said, a request copy is only valid for customizing objects. This is entries in tables, you will see that you have two kind of requests, customizing and workbench. Workbench objects are client independent, so request copy doesn't applies.
it's very important to keep the order of requests when you transport and also not to delete requests in any system.
Hope this helps (and hope it is clear, if you have any doubt, just ask!).
Regards,
Diego

Program attached to wrong transport request and sent to QA, now what?

Similar Messages

Maybe you are looking for