Peoplesoft error “Unable To Find a Routing Corresponding To The Incoming Request Message”

Dealing with reports and files not posting can be a frustrating experience. The challenges are usually rooted in either infrastructure or development issues, and identifying the exact cause is crucial for resolving the problem efficiently.

Common Scenarios

1. All Reports Not Posting: If all reports display as “Not Posted” in the process monitor, this is often due to infrastructure issues.
2. Specific File or Report Not Posting: When a particular file or report fails to post, it could be related to development or infrastructure problems.

Where to Begin?

Start by checking the Administration tab in Report Manager. You’ll need to have the process instance and report ID (content ID) at hand. If you suspect an infrastructure issue, the first step is to restart the relevant process scheduler(s).

Key Tables to Investigate

Behind the scenes, several records are crucial for diagnosing report posting issues. Below is a list of important records and the information they provide:

Record	Purpose
PS_CDM_DIST_NODE	This record contains your report distribution nodes. Check its configuration if you face a system-wide reports not posting issue. (Navigation: PeopleTools > Process Scheduler > Report Nodes)
PS_CDM_AUTH	This record shows who the reports were distributed to. A DISTIDTYPE of 2 indicates a user, and 3 indicates a role. Security settings might prevent visibility.
PS_CDM_FILE_EXT	This record lists the file extension distribution options. Ensure new file extensions are properly configured and set to display (DISPLAY_OPTION = 1).
PS_CDM_FILE_LIST	This record provides a list of all files that should be visible. If a file is missing here, it likely wasn’t transferred to the report repository.
PS_CDM_LIST	This is one of the most useful tables, showing the process name, output storage, distribution destination, and distribution status.
PS_CDM_TRANSFER	This record logs cases where reports were transferred between servers.
PS_CDM_TRNFR_RJCT	This record logs cases where report transfers between servers were rejected or failed.

With this information, you can start investigating issues on your process scheduler server(s). If everything seems fine in the Administration tab but issues persist in the List or Explorer tabs, you might be facing an integration broker issue.

When working with PeopleSoft Integration Broker, there are several common issues that can prevent a Service Operation from successfully processing. Below are key troubleshooting steps to address these problems:

---

A. Missing Inbound Routing for the Service Operation

One common issue occurs when the receiving PeopleSoft system does not have a matching active inbound routing for the given Service Operation. To verify and correct this:

1. Navigate to: PeopleTools > Integration Broker > Integration Setup > Service Operation
2. Select the Service Operation and click on the Routing tab.
3. Ensure that a matching inbound routing is defined and that it is set to Active.

---

B. Incorrect External Alias Names for the Service Operation

If the external alias names are incorrect, the Service Operation may not be processed correctly. Follow these steps to verify and correct the external alias names:

1. On the Sending PeopleSoft System:
   • Navigate to PeopleTools > Integration Broker > Integration Setup > Service Operation.
   • Select the Service Operation in question and click on the Routing tab.
   • Click on the Routing Name for the target PeopleSoft system.
   • Go to the Parameter tab and note the External Alias name.
2. On the Receiving PeopleSoft System:
   • Navigate to PeopleTools > Integration Broker > Integration Setup > Service Operation.
   • Select the Service Operation and click on the Routing tab.
   • Click on the Inbound Routing Name and go to the Parameter tab.
   • Ensure that the External Alias Name and Version number match those on the sending system. If the operation is from an 8.48+ PeopleSoft system to an 8.1x/8.2x system, remove the Version number from the external alias.

---

C. Service Operation Sent to the Wrong PeopleSoft System

To ensure that the Service Operation is sent to the correct system, verify the configuration in the integrationGateway.properties file:

1. Navigate to: PeopleTools > Integration Broker > Configuration > Gateway
2. Click on the Gateway Properties link and enter the username/password.
3. Verify that the Application Server URL format, host, and JSL port are correctly defined for the receiving system.

---

D. Mismatched Node Passwords

If the node passwords on the sending and receiving systems do not match, the Service Operation may fail. To test this:

1. Change the Routing on the receiving system to ANY to Local and resubmit the Message/Service Operation.
2. If it processes successfully, the node passwords are likely mismatched.

To verify and correct the Node passwords:

1. Run the following SQL on both systems:sqlCopy codeselect MSGNODENAME, NODE_TYPE, AUTHOPTN, IBPASSWORD from PSMSGNODEDEFN where MSGNODENAME in ('<nodename1>', '<nodename2>');
2. Compare the IBPASSWORD fields for each node. They must match.
3. Navigate to PeopleTools > Integration Broker > Integration Setup > Nodes and update the Node password on both the sending and receiving systems.

---

E. Invalid Default UserID for the Inbound Node

If the default UserID for the inbound node is not valid, it can cause the Service Operation to fail. The default UserID must:

• Be able to log in to the PeopleSoft system as a user.
• Have full access to service operation security via a permission list.

Refer to the Integration Broker documentation for more details on setting up the default UserID and service operation security.

---

F. Corrupted Routing Definition Data

If the issue persists despite verifying all the above factors, the routing data might be corrupted. To test this:

1. (Re)generate any-to-local routing on the receiving side and test the Service Operation.
2. If the Service Operation is successful, the previous routing was likely corrupted.

---

G. Service Operation Not Set to “Active” in the Target Database

If the Service Operation is not set to “Active,” it will not process. To activate it:

1. Navigate to: PeopleTools > Integration Broker > Integration Setup > Service Operation.
2. On the General tab, check the Active checkbox.
3. Save the Service Operation.

---

H. User’s Permission List Lacks Permissions

If the user’s permission list does not include the necessary permissions for the Service Operation, follow these steps:

1. Navigate to: PeopleTools > Integration Broker > Integration Setup > Service Operation.
2. Click on the Service Operation Security link in the upper right corner.
3. Add the user’s permission list to the Service Operation and save the changes.

---

By following these troubleshooting steps, you can effectively diagnose and resolve common issues with PeopleSoft Service Operations, ensuring smooth and successful integration processes.