transport log

[Former Member]

Dear all,

can anyone provide me information on

1. what is the purpose of releasing a request?

2. can we check a transport request for errors,i mean transport log before it is released.

3. what are the ways to check aTR for any errors.

any help wud be gratefull

[Former Member]

Short answer: No

When you check the syntax of a transport that only means that all objects in that transport are syntax error free. But this check does not tell you, if you have all relevant objects included in that request.

e.g. You are referring to a data element that has been defined under another request which has NOT yet been transported. The syntax check in your development system would be successful, because all the objects are there. However when you import that transport into your QA system you will get a return code of 8 because the data element you are referring to is NOT in the QA system yet.

Unfortunately there is no check that would find those kind of errors. This is something you have to check manually. And that's why you should always check the transport log to see if other objects are missing in your QA system.

Hope that helps,

Michael

[Former Member]

Hi,

1. what is the purpose of releasing a request?

By releasing the request , we mean that aur work in development system is done and the object is ready to be imported to target system. You can not import to target system before releasing the transport

2. can we check a transport request for errors,i mean transport log before it is released.

If you have any error in object you have develop then then you will get error while releasing, but there may be error which only arise when transport is imported to target system and that can only be check after import( in transport log)

3. what are the ways to check aTR for any errors.

Check the transport log ,go to SE10 in target system and click on import tab. it will show you the log. There are many other ways also.

[Former Member]

1. If you don't release a transport you cannot import it into another system. Releasing a transport request will export all the objects into a file that can then be imported into your QA and live system

2. The transport log is only written if the transport has been imported into another system and at that point it will tell you if there was a problem during the import or not

3. You can check a transport request by right clicking on it in SE10 and selecting 'Check Syntax' from the context menu, but that will only show you if there are errors in the objects included in that transport. It will not tell you if there are dependencies to other transports that is something you have to check manually. And that is something the transport log will show you after the transport has been imported into another system.

Hope that helps,

Michael

[Former Member]

Thanks all for your replies,

i have one more query that is ,i have released my request but not yet transported ,now when i have checked the syntax and transport log i have found no errors.so does that mean everything is fine.

im asking you this becoz i have transported 2 requests before but they ended with a return code 8.

[Sandra_Rossi]

> \[...\] transport log i have found no errors \[...\] ended with a return code 8

You have probably not expanded the log, by default everything is not shown. Moreover there is sometimes a detail button in the log. So, every time you have a RC 8, you'll have a corresponding message

[Former Member]

Short answer: No

When you check the syntax of a transport that only means that all objects in that transport are syntax error free. But this check does not tell you, if you have all relevant objects included in that request.

e.g. You are referring to a data element that has been defined under another request which has NOT yet been transported. The syntax check in your development system would be successful, because all the objects are there. However when you import that transport into your QA system you will get a return code of 8 because the data element you are referring to is NOT in the QA system yet.

Unfortunately there is no check that would find those kind of errors. This is something you have to check manually. And that's why you should always check the transport log to see if other objects are missing in your QA system.

Hope that helps,

Michael

[Former Member]

thanks for your reply michael,

i have to transport 4 tables with more than 300 fields,i have transported all ,but some of them where deactive so now i have activated them,and the name tab of few tables were not generated,i have activated and assigned to a new request,so now my concern is how can i check the name tab whether it is generated or not for the table.

regards

[Former Member]

Sometimes, for table related transports,

1. First activate all the objects/tables wherever you have made the changes.

2. Include all the relevant transport requests into one final request, if you have multiple requests.

3. Release all the tasks under the final request and sort the final request and compress it. So that all the duplicate objects available in the object list will be deleted.

4. Now release and import the final request to target system.

5. Check manually whether all the changes are being taken place or not.

6. If do not see the changes, try activating the objects directly in the target system itself. Especially when screens related changes.

7. If the changes are related to any standard tables, it will take around 30 minutes to reflect the changes and all the jobs which are making use of those tables may get failed some times.

Please check the points as applicable.