Duplicate Routing Error – Routing xxx already exists. Please select a unique name. (158, 2075)

by Apurva T. on August 2, 2013

in PeopleSoft Integration Broker

Routings in PeopleSoft Integration Broker are used to carry a predefined function. A routing definition defines the sending and receiving nodes for a transaction, specifies any inbound and outbound transformations to invoke and defines external aliases. It also defines overrides that the default integration gateway and the default target connector that the local node use to communicate with an integration endpoint.

When you define a new node, you will have to define routings for the same. When you rename or delete a node definition, PeopleSoft Integration Broker automatically handles most of the dependencies involved — such as deleting routings and other properties associated with the node. However, what I found was that it is not always so.

I renamed a node and found that the routing definition is still the old one. So, I decided to delete the routing and create it again. What I got instead was the error “Duplicate Routing Error – Routing xxx already exists. Please select a unique name. (158, 2075).”

Duplicate Routing Error

As shown in the screenshot above, if you search for the routing under: PeopleTools > Integration Broker > Integration Setup > Nodes and use Find functionality – you might not see the node name because it might be defined incorrectly. I feel this Find functionality is crap – it should be redesigned.

If you encounter a similar error, here is the easiest way to resolve the error.

Go to: PeopleTools > Integration Broker > Service Utilities > Service Administration in the Routings tab. The search will find any duplicate routings and allow you to select and delete them.

delete duplicate routings

Alternatively, you can also find the routing definitions in the table PSIBRTNGDEFN and perform the delete directly on the database. I prefer to use the delivered functionality though.

Related Posts Plugin for WordPress, Blogger...

{ 0 comments… add one now }

Leave a Comment

Previous post:

Next post: