SRM Metadata entries after transport

Sometimes, problems occur in the metadata changes of SRM portal applications when you import new metadata entries from different system.Following are some scenarios which are usually practised while creating or updating entries of metadata views in SRM.

PROBLEM : You already have metadata entries in your system and there are some entries which mismatch when you compare with standard systems. You decide to import the metadata entries from the standard system into your system by importing a transport request.
After you import the entries in your system, sometimes the metadata changes are not reflected in the portal applications. Eventhough the new modified entries are present in the metadata views,sometimes they are not picked up when the portal applications are executed.

SOLUTION: Execute transaction SHMM (Shared objects monitor) in SRM system  and invalidate or delete the instance of the metadata class and re-login to the portal. Metadata changes will be reflected.
PROBLEM: You have maintained metadata entries in the customizing client for your SRM system and transported the request. Metadata entries will be passed to different SRM system. But the entries will not be reflected in the different clients of the same system.

SOLUTION: To reflect the changes you have made to SRM metadata views in various clients of the same system, you have to run a report : SCPR_ACTIVATE_SBCSETS and activate the switch BC sets changed. The report can be executed from any client, wherever you have development authorizations. It is not mandatory that you execute the report from customizing client of your SRM system.