Search this blog for other interesting articles

Friday, 30 September 2011

Transport Error – Transport Control Program tp ended with error code 0247

This article answers the following queries:
  • How to resolve the transport error “Transport Control Program tp ended with error code 0247?
  • How to resolve the transport error – Errors: addtobuffer has problems with data- and/or cofile?
  •   How to resolve transport issue  encountered while adding a transport to import queue of target       system?
--------------------------------------------------------------------------------------
Sometimes, while you are adding a transport request into import queue of target system 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 screenshot 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 released 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 transports under this are released ( if there is tick mark after the transport, it means it was released).
If there is no tick mark on any of the  transports below the given transport number it means the transport is not yet released. In those cases, you can even view truck 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 as 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 respective 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 released. 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 and  cofiles will be generated for that transport request in the source system. Then no longer, the error mentioned above will be encountered will adding the transport request to import queue of the target system as the request was released and data and cofiles were also generated under /usr/sap/trans/data and /usr/sap/trans/cofiles directories of the system.



Related Link:






Enter your email address:


Delivered by FeedBurner






14 comments:

Suain Logistics said...

That's really amazing post. great diagram and content. Thanks for share..

DurgaPrasad said...

Thanks Suain...for your nice comment

Anonymous said...

This material is really helpful

Unknown said...

this blog is very useful with brief explaniation..i have a question.y we use trasport dir as comman

Diadem said...

Hi Sir,

How Many Types of Error we face in Transport.

Regards

Abhishek Sinha

Manoj Singh said...

Great post. I am looking forward to the follow up.

Anonymous said...

Good material for beginners...

sreeeeeeee said...

too good..keep up the good work

Harsha said...

ty durga prasad garu..

after releasing my request. i am getting that the request is released succesfully but cant find my request in trans directory. i have released both the request and sub... can you let me know why is this happening..

Thanks,
Harsha

Anonymous said...
This comment has been removed by a blog administrator.
Anonymous said...

For example if the request id was ABCK123456 where
ABC is the System id, and 123456 is req. no. , then
the datafile will be named as R123456.ABC , and cofile as K123456.ABC ... Search for these in the data & cofiles folder respectively in trans directory.

Unknown said...

hi durga very helpful thank you! Pls in brief ! Once a request is released in the source system and data and co files are available in the source system.......! will they be automatically get to target system when we search in the stms_import of the target system or manuall add data and co files to that system and the import to the paticular client.

please explain in brief ty and is theya ny different from export import process.

srkpvr said...

Hi Vipul, Normally the transports will appear automatically in the buffer of target system once it is relaesed from source system. If not try to add the transport manually ( Some configuration issue exists in your landscape try to figure it out)


Anonymous said...

Hi Vipul,
Usually in a landscape, trans directory is defined as shared directory. So when you release it in the source system, then you can import it in target system with stms_import tcode since trans directory is shared between those systems.

Search this blog for other interesting articles

Please subscribe & activate link received to your email id to receive latest articles

Enter your email address:

Delivered by FeedBurner