Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
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.
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).
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:
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:
PeopleTools > Integration Broker > Integration Setup > 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:
PeopleTools > Integration Broker > Integration Setup > Service Operation
.PeopleTools > Integration Broker > Integration Setup > Service Operation
.To ensure that the Service Operation is sent to the correct system, verify the configuration in the integrationGateway.properties
file:
PeopleTools > Integration Broker > Configuration > Gateway
If the node passwords on the sending and receiving systems do not match, the Service Operation may fail. To test this:
To verify and correct the Node passwords:
select MSGNODENAME, NODE_TYPE, AUTHOPTN, IBPASSWORD from PSMSGNODEDEFN where MSGNODENAME in ('<nodename1>', '<nodename2>');
IBPASSWORD
fields for each node. They must match.PeopleTools > Integration Broker > Integration Setup > Nodes
and update the Node password on both the sending and receiving systems.If the default UserID for the inbound node is not valid, it can cause the Service Operation to fail. The default UserID must:
Refer to the Integration Broker documentation for more details on setting up the default UserID and service operation security.
If the issue persists despite verifying all the above factors, the routing data might be corrupted. To test this:
If the Service Operation is not set to “Active,” it will not process. To activate it:
PeopleTools > Integration Broker > Integration Setup > Service Operation
.If the user’s permission list does not include the necessary permissions for the Service Operation, follow these steps:
PeopleTools > Integration Broker > Integration Setup > Service Operation
.By following these troubleshooting steps, you can effectively diagnose and resolve common issues with PeopleSoft Service Operations, ensuring smooth and successful integration processes.