'SQL object does not exist' error caused by eProfile Approval notifications wrongly refering to HR_MAR_STAT_CI_BIND and not HR_MAR_STATUS_CI_BIND
Last updated on OCTOBER 10, 2017
Applies to:PeopleSoft Enterprise HCM eProfile - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
The notifications that are sent out when an employee hits save depend upon whether there are approvals, and what the status of the data update is. For each situation, parameters are set-up for the notification, including the template to use, and the SQL object to extract the data fields. For two of the possible scenarios, the SQl object referenced is not delivered. These are highlighted in BOLD.
Error message : SQL object does not exist (“Failed to find a matching SQL statement”) HR_MAR_STATUS_CI_BIND, GBL, 2, 2017-04-27. (2,289) EOAW_CORE.NotificationManager.OnExecute Name:LoadTemplateData PCPC:2375 Statement:55 Called fro...
Component=HR_EE_MARITAL_FL; Market=GBL; Page=HR_EE_MARITAL_FL; Menu=EL_EMPLOYEE_FL
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms