Вы находитесь на странице: 1из 6

file:///G|/transports.

txt

jaleel ahmed http://help.sap.com/saphelp_nw04/helpdata/en/ Types of transports Transportable - Consolidation request (K transport) Transport Originals -Transport with change authorization(C type) Transport of Copies - Transport without change authorization (T type) K type: The system owner does not get changed with K type transport. This kind of transport is only allowed to consolidation and production system. After the K type of transport is done no correction is allowed to those objects. Any changes to K type transport objects in consolidation system are called repair. The repairs can be done to those objects if the change option is selected in SE06 and change option is there in client level selection in T00 table. Generally K type transport is used for stage and production environment C type: With the C type transport the ownership of that object is also transferred to the target. After the transport is done, the target system is the owner of the transported objects. The objects will be originals of the target system. These kind of transports are generally done in a four tier architecture, where a bundle of development objects can go from the sandbox environment to development environment or development environment to integration environment and vice versa. SAP recommends doing these transports when the objects should move to another system for further development work T type: T type is called a transport of copy. The ownership of the object remains with the source; the target system just gets the copy of the objects. When a sap patch is applied to the development system and transported to other systems, those are perfect example of T type transports. Table TSYST defines all the systems in the CTS pipeline Table DEVL contains all the transport layers This table defines all the systems in the CTS pipeline for which change request will be delivered automatically after the successful import into the consolidation system TWSYS This indicates the consolidation routes for the change requests. This table also must be identical in the CTS pipeline Important tips: A transport can be created manually through SE01 and different types of objects can be directly added to the editor to get transported to the target system R/3trans is the r/3 system transport program which can be used for transporting data between different sap systems ,even when they dont belong to the same group .R3trans normally is not used directorly but called from the tp controle program or by the R/3 upgrade.Tp is the basic tool for the transporting the request.
file:///G|/transports.txt (1 of 6)11/21/2006 11:25:38 PM

file:///G|/transports.txt

TP controls file at OS level and then calls R3trans. R3trans is the program that actually connects to the database and does the actual import/export

For manual transports at os level tp commands are used (tp add to buffer, tp import). TP is a C program delivered by SAP that runs independently of the R/3 system. TP program uses the appropriate files located in a common transport directory /usr/sap/trans. TP starts C programs, ABAP/4 programs and special operating system commands to its job. TP program is located in the run time directory /usr/sap/<SID>/SYS/exe/run directory.

Start the program RDDNEWPP once in every SAP System. Do this as user DDIC in client 000 and in all clients that are used as the source or target for a transport. tp can then start the background job RDDIMPDP in every SAP System if it is needed to perform a transport (export or import). TRJOB and TRBAT are the major tables in the CTS process. tp uses the tables TRBAT and TRJOB to communicate with the ABAP transport programs. To execute these steps, the R/3 System must be running with at least two background work processes. Furthermore, the batch job RDDIMPDP must be scheduled with the repeat-start option. We recommend scheduling this job event on a regular basis. If the job is not running, then start the program RDDNEWPP once in every R/3 System. Do this in client 000 and in all clients that are used as the source or target for a transport, and do it as a user that has CTS administration authorization, such as DDIC. After TP program has sent the event to the r3 system, RDDIMPDP checks table TRBAT in the target system to find out if there is an action to be performed. Mass activation, distribution, or table conversions are the examples of actions. If there is action to be performed, RDDIMPDP starts the appropriate program in the background task. RDDIMPDP then reschedules itself. By checking table TRJOB, RDDIMPDP automatically recognizes if a previous step was aborted, and restarts this step Once tp has sent the corresponding event to the R/3 System, RDDIMPDP checks table TRBAT to see if there is anything to do. If there is, it starts the required programs (for example, mass activation) in the background, schedules itself again, and then stops. RDDIMPDP automatically recognizes if a previous step was terminated and restarts the action. However, this can only be done with two background work processes. RDDIMPDP recognizes terminated import steps by checking table TRJOB. If you do a transport (tp import) and it fails it may leave entries in TRBAT and TBATG. Delete the entries from these two tables before trying anymore transports. If you leave the entries in these two tables all your transports will hang. If you do a transport (tp import) and it fails it may leave entries in TRBAT and TBATG. Delete the
file:///G|/transports.txt (2 of 6)11/21/2006 11:25:38 PM

file:///G|/transports.txt

entries from these two tables before trying anymore transports. If you leave the entries in these two tables all your transports will hang. You can use the TPALOG table to view transport logging. This enables you to see who created the request and what user id was used to do the actual transport. There is much more information than in the TPLOG table, but you still have all the usual search and filter capabilities If you were doing a transport and had to kill it halfway, SAP shut down, the server crashed or anything similiar, the transport may hang. When you do the next transport, the little clock just keep turning in the bottom left corner but the transport does not continue. This can be fixed by deleting all entries from tables TRBAT and TRJOB. Use SE16 to delete the entries or use sqlplus (delete * from sapr3.TRBAT and delete * from ************** sapr3.TRBAT) Operating System Users - UNIX All owners of SAP Systems (at UNIX level) must be in the group sapsys. The group sapsys must have the same group identification number (gid) on all the computers of the transport group. (This is proposed, but not guaranteed by the installation tools.) Operating System Users - Windows If you call a transport program directly from the operating system level, only use the operating system user <SAPSID> ADM If you call a transport program from the SAP System (Change and Transport Organizer or Transport Management System), the user under which the SAP System was started is used. This user is SAPService<SAPSID> for a standard installation of the operating system user. Operating System Users IBM eServer iSeries Each user who wants to use the transport system at operating system level must be a group member in the group profile <sapsid>OFR. Note that at present user names and passwords must be exactly the same in all SAP systems. This is a restriction required for remote access using /QFileSvr.400 from OS/400 Each time tp is started, it must know the location of the global parameter file. You can specify the location with pf=... (see Using a Special Transport Profile under tp Options). The transport profile TP_<domain>.PFL is a global parameter file for the program tp UNIX: tp pf=/usr/sap/trans/bin/TP_DOMAIN_PRD.PFL import all P11Windows: tp pf=\\<HOST1>\sapmnt\trans\bin\TP_DOMAIN_PRD.PFL import all P11 IBM eServer iSeries: tp pf=/usr/sap/trans/bin/TP_DOMAIN_PRD.PFL import all P11
file:///G|/transports.txt (3 of 6)11/21/2006 11:25:38 PM

file:///G|/transports.txt

If the transport profile is not specified in this way, tp searches for the transport profile in the current directory. tp connect <SID> Tests the connection to <SID> tp locksys <SID> tp unlocksys <SID> tp showbuffer <SID> Lock the SAP-system for all users except SAP* Unlock the SAP-system, giving access to all users Show the buffer

tp addtobuffer <changerequest><SID> Add the changerequest to the buffer. possible par.: u1 tp delfrombuffer <changerequest><SID> Delete the changerequest from the buffer tp import <changerequest> <SID> u.x request will be created by functional or abap people and will be released by them and packages wil be assigned to the created request using tcode se80 to transport at os level, or to transport manually use commands at the command level tp addtobuffer <request no> <sid> here <sid> is target system sid to which to be imported then go to usr\sap\sid\trans\buffer directory, to check whether the request has been added or not tp import <request no> <sid> <client no> <u1_ _un> Import command, parameter u: (u=uncondidional mode) u0: overtaker, leave the respective task in the buffer, mark it to be imported again (1 or I). u1: Import regardless if it is already imported or not u2: Overwrite the originals. u3:overwrite system-specific objects u4:Import into system other than the target system that was defined in the transport request. u6: overwrite repaired objects in unconfirmed repairs. u8: During import ,ignore restrictions arising from table classes u9:Import into system even if it is locked against this type of transport. Values for Parameter TRANSDIR Dependent on the Operating System UNIX and IBM eServer iSeries TRANSDIR=/usr/sap/trans/ Windows
file:///G|/transports.txt (4 of 6)11/21/2006 11:25:38 PM

file:///G|/transports.txt

When using a central transport host with ALIAS SAPTRANSHOST: TRANSDIR=\\$(SAPTRANSHOST)\sapmnt\trans\ otherwise: TRANSDIR=\\<transport host>\sapmnt\trans\ RSSPACECHECK report from abap se38 to chech space for each client Importing the user data with the transport will take about 30 mins. 1 hour. Be patient. Cd /usr/sap/trans/bin tp addtobuffer PFCKT00025 PFC u1 tp import PFCKT00025 PFC client100 u1 -------------------------------------------------------------------------------------------------After the client export procedure is completed, if you chose the client independent data then three transports are created in /usr/sap/trans/cofiles or there will be two transports: KO for the client-independent data ( if selected). For example if the client export is done from development client 100 then the file will look like DEVKO0001. KT for the client-specific data. For example DEVKT0001 KX for the SAPscript objects as Texts and forms. For example DEVKX0001 The data export is performed automatically. The output of the export includes the name of the COMMFILE that has to be imported. The following data files will be created in /usr/sap/trans/data directory using the same example given above: For client dependent data: /usr/sap/trans/data/RT00001.DEV /usr/sap/trans/data/DX00001.DEV For client independent customizing data: /usr/sap/trans/data/RO00001.DEV

For SAPscript data of a client: /usr/sap/trans/data/SX00011.DEV Tips: Make sure that all the cofiles and the datafiles exist in the data and cofile directories before starting the import phase.
file:///G|/transports.txt (5 of 6)11/21/2006 11:25:38 PM

file:///G|/transports.txt

Then add all the command files to the buffer by using the TP command in /usr/sap/trans/bin directory as following: tp addtobuffer Using the above example cofile: tp addtobuffer devkt00001 qas (if qas is our target system) tp addtobuffer devko00001 qas tp addtobuffer devkx00001 qas Then logon as adm to the target system and then use then import the transports as following: tp import devkt00001 qas client100 u148 - For the client dependent data tp import devko00001 qas client100 u148 - For client independent data

file:///G|/transports.txt (6 of 6)11/21/2006 11:25:38 PM

Вам также может понравиться