I have observed this issue seems as a bug ,
CE2(config)#router bgp 20
CE2(config-router)#neighbor 192.168.45.4 remote-as 1234
% Create the peer-group first
Just reload the router , issue will ber resolved .
The issue is that 108sagarh have tried to apply route-map to a neighbour that haven't been configured with a remote-as number. And that is the first thing you have to do. If you want to have route-map in place for a neighbour right from the beginning, then your best bet is creating a peer-group first, applying your route-map to a peer-group and then adding a neighbour into that peer-group. Then you can be sure the route-map is applied straightaway and you can avoid situation, where BGP springs into action unrestricted before you put your route-map statement in place.