Stored Procedure
- Last UpdatedMar 17, 2016
- 1 minute read
A valid stored procedure name from the MES database, if the type of Extensibility Hook is stored procedure.
The parameter names, data types, and presence of default values in the custom (hook) stored procedure must match exactly those of the parameter names, data types, and presence of default values in the middleware stored procedure (stored procedures configured in the Middleware SP Name column). However, there can be additional parameters in the custom (hook) stored procedure that might not be matching the parameters in the middleware stored procedure, but those additional parameters must be defaulted to NULL in the custom stored procedure. If they are not defaulted to NULL, an exception might be raised by the database layer for not supplying enough values for those additional parameters. It is recommended that the list of stored procedure parameters, data types, and default values (if any) be copied from the middleware stored procedure to the custom stored procedure to ensure all these properties are identical between them. However, the default values for the custom (hook) stored procedure do not have to exactly match the default values in the middleware stored procedure.
The values supplied for the middleware stored procedure (configured in the Middleware SP Name column) are the same values supplied to the custom (hook) stored procedure.