Unable to find transport route TR000022 with selected status- Retrofit

[Former Member]

Dear All,

We have a retrofit configuration setup and till now everything worked fine but suddenly we face this issue while retrofitting requests in one of our dev system.

Unable to find transport route TR000022 with selected status.

We have already checked all the RFCs and the shipment routes check in SOLAR_PROJECT_ADMIN. Could not find out what exactly is the problem.

Could anyone please help on this?

Regards,

Tripti

[Former Member · Accepted solution]

Hi Tripti,

Did you check the Project Check for both the projects Maintenance and Implementation.

Also, can you check the IMG projects for both ?

Also, check in SMSY for all the involved systems in the Header data --> Domain is maintained for 'Central Domain controller'

Was there any change in the transport routes ?

Also, is this error appearing for any particular transport / RD only ?

Regards,

Kaustubh.

[Former Member · Accepted solution]

Hi Kaustubh,

Thanks for your reply.

I have already checked the projects for both implementation and maintenance. In implementation cycle while creating requests it gives warning that landscape is not in sync guess we can avoid it? or no?

SMSY check is done too.. everything is working fine. I will check for domain controller and let you know.

Yes, there has been a constant change in the transport routes cos we are undergoing upgrade of all the systems involved from 4.6c to ECC6.0. I think that might be the reason we are getting this problem.

Error is appearing for every TR we are retrofitting.

Regards,

Tripti

[Former Member · Accepted solution]

Hey Tripti,

No you may not ignore the warnings / errors in the checks for the implementation project.

If the landscape is not in sync, that means the systems defined in Project, systems defined in SMSY ( including the product versions / SLD data ) and the Domain data coming into SMSY from STMS systems definitions and the Systems definitions in STMS itself is not correct.

First do a complete check on the systems defined in STMS, even the smallest of parameter defined like CTC =1 on all systems. Second check the transport route and systems in STMS -- like if all systems are client specific transport routes, with the correct transport layer and groups.

Then you can start checking with the SMSY definitions. For this first check with the SLD data if the systems are in sync with the SLD itself, then check if SMSY_UPDATE is running / you can try running the SMSY_FETCH_SYSTEM_UPDATE report for specific systems as well ( in case there are JAVA systems ) . Second run the "update system data from remote" for the Solution manager system itself in SMSY. This will update the same for all the other systems as well.

If anything is changed in the above, you may need to close the maintenance cycle and reopen a new one.

Refer to :

Change Request Management scenario: Usual questions and known errors

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/15116

Known Questions.

http://scn.sap.com/people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-qu...

http://scn.sap.com/people/dolores.correa/blog

If you have inconsistencies in the maintenance cycles / release documents.

Not all suggestions may work in the exact same manner, refer to the original SAP notes to apply for your particular landscape.

Regards,

Kaustubh.