When there is an error transmitting or creating any of the integration messages or documents into Banner, the Banner APIs produce an error. The Interface logs the API error in the FZBEPRC and messages from Unimarket in the FZRCXML table. The Interface also triggers error emails to one or multiple email addresses defined in the FTVSDAT records (FZKEPRC-UM ERROR EMAIL-TO). The emails are sent using the Oracle UTL_MAIL function from the underlying Oracle database of Banner.
Interface Logs
FZBEPRC Request log table – cXML messages from Unimarket to Interface
FZRCXML Banner PO and Invoice API log table
Unimarket-Banner Interface Error Emails
The Interface error emails utilize the Oracle UTL_MAIL.SEND. If you are not getting the error emails, the issue is likely with the smtp_out_server setup or the permissions granted to the Oracle user or schema in the access control list (ACL) are insufficient or have been removed. This section below will focus on the troubleshooting and setup for the Error Emails using the oracle UTL_MAIL.SEND.
Error Email Test
login as FISHRS try this simple test:
begin
UTL_MAIL.SEND(sender => 'somebody@school.edu',
recipients => 'somebody@school.edu',
cc => 'somebody@school.edu',
subject => 'Just test',
message => 'test');
end;
Setup and Troubleshooting:
Script: utlmail_grant_080500.sql
Note: change the '<SERVER_NAME>.<DOMAIN>' fields below to match your own SMTP server and domain.
start /u01/app/oracle/product/11.2.0/db11203/rdbms/admin/utlmail.sql
start /u01/app/oracle/product/11.2.0/db11203/rdbms/admin/prvtmail.plb
grant EXECUTE ON utl_mail TO BANINST1;
ALTER SYSTEM SET smtp_out_server = '<SERVER_NAME>.<DOMAIN>' SCOPE=BOTH;
Script: utlmail_acl_11g.sql
begin
dbms_network_acl_admin.create_acl (
acl => 'utl_mail.xml',
description => 'Allow mail to be sent',
principal => 'BANINST1',
is_grant => TRUE,
privilege => 'connect'
);
commit;
end;
/
begin
dbms_network_acl_admin.add_privilege (
acl => 'utl_mail.xml',
principal => 'WWW_USER',
is_grant => TRUE,
privilege => 'connect'
);
commit;
end;
/
Note: change the '<SERVER_NAME>.<DOMAIN>' fields below to match your own SMTP server and domain – should match what you entered for the “smtp_out_server” init parameter above.
begin
dbms_network_acl_admin.assign_acl(
acl => 'utl_mail.xml',
host => '<SERVER_NAME>.<DOMAIN>',
lower_port => 25,
upper_port => 25
);
commit;
end;
/
ACL (run later)
begin
dbms_network_acl_admin.add_privilege (
acl => 'utl_mail.xml',
principal => 'FISHRS',
is_grant => TRUE,
privilege => 'connect'
);
commit;
end;
/
Customer is not receiving errors via email
If a customer is not receiving their error emails, they can check that the FISHRS user in Oracle has access to the UTL_Mail or if they can use ACL permissions, check that FISHRS is included in the ACLs. If that's not the issue, it could be an SMTP_Out configuration issue with the email server on the customer side.