Transport Error Transport Control Program tp ended with error code 0247 This article answers the following

g queries: How to resolve the transport error Transport Control Program tp ended with error How to resolve the transport error Errors: addtobuffer has problems with datale? How to resolve transport issueencountered while adding a transport to import qu system? ---------------------------------------------------------------------------------------------Sometimes, while you are adding atransport request into import queue of target sy stem as shown below, you might encounter error as Transport Control Program tp ended with error code 0247 "? Errors: addtobuffer has problems with data- and/or cofile? (Please refer screens hot 3)

After pressing Yes in the above screen, you may encounter below error:

Most probable reasons for this issue could be, due to transport did not get rele ased from the source system. Please login to the source system of the transport and goto transaction SE01 and provide the transport number as shown below and click on display pushbutton to view the release status of the transport

In the below screen, please drill down the transport and check whether all the t ransports under this are released ( if there is tick mark after the transport, i t means it was released). If there is no tick mark on any of thetransports below the given transport number it means the transport is not yet released. In those cases, you can even view tr uck symbol in the active state.

In the above screenshot, all the underlying transports were released(as there is tick mark after those transports), but the main transport is not yet released a s indicated my active status of the truck. In these cases, just keep the cursor on the main transport number and click on truck symbol to release the transport. Please note that you can release the transport only if you have access to do the same. If basis administrator do not have access, he/she should approach the res pective team and get this transport released as per the process mentioned above. Please find below another scenario, in which 2 of the 3 child requests not relea sed. In this case, each of the individual transport to be selected and released (by clicking truck button) and finally release the main transport.

Once the main transport is released, data file andcofiles will be generated for th at transport request in the source system. Then no longer, the error mentioned a

bove will be encountered will adding the transport request to import queue of th e target system as the request was released and data and cofiles were also gener ated under /usr/sap/trans/data and /usr/sap/trans/cofiles directories of the sys tem.

TRANSPORT RELATED Q N ANS : 1. I have error messages about logs not found during the transport. This is usually caused by incorrect maintenance of the setting for the transport directory. Check in particular the parameters DIR_TRANS and TRANSDIR by referri ng to the advice given in note 556734, section "What do I need to consider when setting up the transport?". 2. The system reports a DB connect problem! What can I do? For the test and as a basis for a further analysis, the command "R3trans -d " or "R3trans -x " can be used as user <SID>adm. A file trans.log is then also writt en in addition to the message via the return code of the attempt in the current directory. In the case of a connection problem, this contains details on the err or message. R3trans mainly checks environment and database configuration files. If no error is found here, the parameters can also be checked from the transport profile with the call "tp connect <SID> pf=DIR_TRANS/bin/<transport profile>" ( use backslashes with NT). The connection test can also be carried out from the T MS (OVERVIEW -> SYSTEMS and there R/3SYSTEM -> CHECK -> CONNECTION TEST or TRANS PORT TOOL). There are also additional notes on the respective database systems: DB2: 152929, 83255, 136806 DB4: 515447, 67213, 69429 DB6: 80292, 53141, 167361 Informix: 85404, 112184 Microsoft SQL Server: 351586, 128126, 116735 Oracle: 193616, 400241, 403004, 134447, 443867, 445029, 437362, 505630 SAP DB: 39439 These notes do not apply to everything! They mostly only apply to certain R/3 or database releases. Only use the relevant notes that apply in each case! 3. When I create transport requests, they are always local! Check in the TMS at the domain controller whether the transport routes are there . Usually the development system is the source system (the objects are created/c hanged there). From there, there are consolidation routes into one or several sy stems that can also be virtual. The consolidation route with transport layer SAP is intended for repairs to SAP objects. With customer transport layers for cust omer objects, the object must have a development class which is assigned to this transport layer. The corresponding development class can be displayed via trans action SE80. 4. The tp does not write requests to buffers of the subsequent system. Check whether the transport routes are generally set up and fully activated and distributed. If it only concerns certain transports, check whether these are Wor kbench or Customizing requests or special transports (transport of copies/reloca tion). In particular with system copies and restores with incomplete recovery, y ou must be aware that afterwards the status of the buffer and the database may n o longer agree. (For example, you import request C11K901234 into the consolidati on system Q11 and then it is displayed in the Q11 buffer that the request is alr eady imported in Q11. The request is not imported into the P11 system. Now you m ake a system copy from P11 to Q11. Now the request C11K901234 is not contained i n Q11 (in SAP), however according to buffer Q11 it is imported). 5. An import seems to hang.

Check in the directory DIR_TRANS subdirectory tmp whether the import process reg ularly updates a log file for a certain import phase. The last entries in this l og file provide information about what the import process is currently doing. If the import hangs, you may find more error messages in the directory DIR_TRANS subdirectory log in the file SLOG<YY><WW>.<SID> (YY are the last 2 numbers of t he year and WW is the calendar week). The lines at the end of the file often eve n contain detailed messages on the error, such as RDDIMPDP is not scheduled. The following notes should also be checked: 12746, 71353, 26966, 449270. If no helpful information has been found in the SLOG, you should check in DIR_TR ANS subdirectory tmp whether there is a file there with extension .LO and this s hould be compared with note 12746. You can also check the tables TRBAT and TRJOB via SE16 or SM30 to see if there are old entries there. 6. Not all clients contain client-specific entries! For objects that enter the system via ADO or SDO import, you must check whether the corresponding jobs RDDIMPDP_CLIENTnnn were released here with the correspond ing authorizations. With transports that are to be imported into several clients of a system, you must check whether you worked here with the correct unconditio nal modes in each case (the first import must be imported with U0 and the follow ing one in each case with U1). Also, a further point which must be considered is the table delivery class belonging to the table. This controls which entries ar e imported with the various transports into which clients. You will find further information on this in note 2857. 7. An import supposedly has an error, but I cannot find an error in the log file s. This is usually due to the order-independent logs. In the order-independent step s, DDIC objects of other requests may also be edited. For example, the request t o adjust a table remains for so long in the internal transport tables and is the refore also processed during a subsequent transport until the adjustment was suc cessfully completed. An error can then be displayed for the subsequent request a lthough its objects were all imported without any errors. Explanatory notes for this are 413993, 512493, 407116 and 330378. After every import, the order-indepe ndent logs should therefore also be checked. If the system refers to canceled RDD* jobs, check the job log via SM37 and via S T22 the short dumps and via SM21 the syslog of the system. 8. A certain program has syntax errors after a transport into a non-development system. Check whether the syntax errors also occur in the development system. If this is not the case, compare the versions of the program and of the function modules u sed by the program with the versions in the development system. Different versio ns can arise if corrections were not yet transported further in the development system or if the sequence of the import does not correspond to the sequence of t he export. To solve the problem, import the last changes from the development sy stem into the subsequent system as well.