2671183 - Errors "No email recipient has been maintained" and "Sender email address can't be initial" in app Manage Automatic Payments

In Application Log of app Manage Automatic Payments (App ID F0770), any of the below errors is raised: 

• No email recipient has been maintained.
• Sender email address can't be initial.
• A technical error occurred when sending the email. Sender domain in && is not allowed.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

• Financial Accounting (FI)
• SAP S/4HANA Cloud Public Edition

1. Create Payment parameter in app Manage Automatic Payments.
2. Schedule Payment.
3. Enter the Payment Processed tab. 
4. Choose the desired payment, press View Log and observe Error messages.

The error is raised for the output requests with email channel not correctly maintained for the payment advice.

Error: No email recipient has been maintained

The receiver email address is not maintained in APP Maintain Business Partner (App ID BP)

Please maintain receiver email address in the BP master data - Role Supplier (Fin. Accounting) - Tab Vendor: Correspondence - Field Clrk's Internet add:  (Internet address of partner company clerk)

Or there is no address maintained on Email Recipient rule for Payment Advice in Output Parameter Determination app (App ID APOC_WD_BRF_DEC_TAB_MAINTAIN).

Please maintain the default email address and additional email addresses for one recipient.

Error: Sender email address can't be initial
In app Output Parameter Determination (App ID APOC_WD_BRF_DEC_TAB_MAINTAIN), check if Sender Email Address is blank or invalid.

See below guided references to maintain sender email address:

• Test SCRIPT J60

2.5.3 BRF+ Settings for Payment Advice

• Help Portal Configuring the Output of Payment Advice Forms

Enter a valid email address as the sender email. The email template FFO_PAYM_ADVICE_EMAIL_TEMPLATE is delivered by SAP. You can adapt the email content based on it. 

See all information below on Sender Email

Error: A technical error occurred when sending the email. Sender domain in && is not allowed
Please review Setting Up Output Management (1LQ). In particular, see below sections:

3.1.2 Email
Emails are sent using the e-mail server provided with the system. The purpose of this task is to define the
technical setup for sending emails. This includes defining the sender domains, sender email addresses, and email
addresses for testing

4.2 Setting Up Email
With the SAP S/4HANA Cloud Public Edition Output Management framework, you can automatically send configured application
documents in PDF format to business partners via e-mail. SAP provides you with pre-delivered email templates for
several application objects. You can customize the email templates by cloning the generic ones, and populating the
subject line and body of the email.

During the technical setup procedure, an individual email domain is assigned to each tenant to send emails in the
SAP S/4HANA Cloud Public Edition environment. The my3XXXXX.mail.s4hana.ondemand.com domain is used in the technical
communication with the cloud email infrastructure. However, in business communication, it's expected that the
readable email header contains addresses from a customer's email domains (for example,
John.Doe@company.com). During tests, it's necessary to control which addresses the test system can send emails
to. This section describes the relevant settings.

4.2.1 Define an Email Sender Domain
In business communication, it's expected that the readable email header contains addresses from a customer's
email domain or domains. In this setting, you can define which domain is allowed in the readable email header. You
may also specify a list of domains if multiple domains are allowed.

Examples:
● company.com would allow all email addresses in this domain such as John.Doe@company.com
● *.company.com would allow all email addresses in company.com subdomains such as
John@sales.company.com or Doe@service.company.com

(With regard to Error Message Domain in sender email address &1 is not allowed.(APOC_OC_CONFIG052 ) issued in Output Parameter Determination. Ensure that domain is set up correctly in accordance with instructions 4.2.1 Define an Email Sender Domain.  Do NOT define domain with @ Character. Remove the character @ from domain, Follow example guide.)

4.2.2 Define a Default Email Sender Address
Generally, the output control functionality determines a sender email address and adds it to the email header.
Within this setting, you may define a default sender address if no sender address has been determined.
Example:
● do.not.reply@company.com

SPAM EMAIL:

4.2.6 Publish SPF Record for Sender Domain
The purpose of this task is to prevent that emails sent by your SAP S/4HANA system are classified as spam and do not reach the recipients.

Add the following SPF record in your DNS, if you mentioned SPF as Strict in your DMARC settings:

v=spf1 include:_spf.cmail.ondemand.com include:amazonses.com ~all 

• TEST SCRIPT J60 BRF+ Settings for Payment Advice
• Configuring the Output of Payment Advice Forms
• 2808603 - Output Parameter Determination - Creation of condition Field
• 2756062 - Email address from customer master data is not considered for output of payment advice in "Manage Automatic Payments" app
• Create and Send Payment Advices to Payees
• 3090392 - Payment advice and note to payee- Cloud
• Setting Up Output Management (1LQ)

F0770, F110,  CLOUD, SAP_BR_AP_ACCOUNTANT, SAP_BR_AR_ACCOUNTANT, SAPF110S, ACH, application log, vendor, BP, EMAIL , Supplier, payment advice, OBPM4, LFB1, INTAD, US_ACH_FSN, J60, output, APOC_OR_MESSAGES APOC_OR_MESSAGES359, APOC_OR_MESSAGES051, manage automatic payment , KBA , FI-FIO-AP-PAY-2CL , Payment Apps (Public Cloud) , FI-AP-AP-B , Payment Progam / Payment transfer (DE, JP, US) , FI-FIO-AP , Fiori UI for Accounts Payable , FI-AP-AP-B1 , Payment transfer (w/o DE, US) , FI-FIO-AP-2CL , Fiori UI for Accounts Payable (Public Cloud) , FI-FIO-AP-PAY , Payment Apps , How To