<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic CUA Security Issue - Communication Method in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/cua-security-issue-communication-method/m-p/11325567#M1919461</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tend to see lot of scul warning message as below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. No data maintained for standard communication type 'Remote Mail'&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;Temporary solution : I am&amp;nbsp; maintaining the &lt;SPAN style="font-size: 13.3333px;"&gt;Remote mail on both the Master and child systems so idoc gets cleared. But this is laborious process to do for multiple users.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;STRONG&gt;My question -&lt;/STRONG&gt; Is there way i can standardize the communication method to be Email&amp;nbsp; and Title and push the same to all the child systems.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;2. Other error on Title field on User master (SU01) Form of address key Dear Mr. is not defined.&lt;/P&gt;&lt;P&gt;Title fields were differently maintained in master client vs Child systems&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Question&lt;/STRONG&gt; - Is there any way i can standardise these values as well&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks much in advance.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 Sep 2015 16:26:26 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2015-09-23T16:26:26Z</dc:date>
    <item>
      <title>CUA Security Issue - Communication Method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/cua-security-issue-communication-method/m-p/11325567#M1919461</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tend to see lot of scul warning message as below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. No data maintained for standard communication type 'Remote Mail'&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;Temporary solution : I am&amp;nbsp; maintaining the &lt;SPAN style="font-size: 13.3333px;"&gt;Remote mail on both the Master and child systems so idoc gets cleared. But this is laborious process to do for multiple users.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;STRONG&gt;My question -&lt;/STRONG&gt; Is there way i can standardize the communication method to be Email&amp;nbsp; and Title and push the same to all the child systems.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;2. Other error on Title field on User master (SU01) Form of address key Dear Mr. is not defined.&lt;/P&gt;&lt;P&gt;Title fields were differently maintained in master client vs Child systems&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Question&lt;/STRONG&gt; - Is there any way i can standardise these values as well&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks much in advance.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Sep 2015 16:26:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/cua-security-issue-communication-method/m-p/11325567#M1919461</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-09-23T16:26:26Z</dc:date>
    </item>
    <item>
      <title>Re: CUA Security Issue - Communication Method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/cua-security-issue-communication-method/m-p/11325568#M1919462</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Venkat,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Please check sap note 496819. It may be helpful for what you are looking for.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) Please explore the maintenance of table TSAD3T and if it serves your purpose you can manually synchronize it across landscape. However maintaining the word 'Dear' in title may be over doing it in case some email templates are using this field then the outgoing emails can read Dear Dear Mr.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Shivraj Singh &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Sep 2015 22:17:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/cua-security-issue-communication-method/m-p/11325568#M1919462</guid>
      <dc:creator>shivraj_singh2</dc:creator>
      <dc:date>2015-09-23T22:17:00Z</dc:date>
    </item>
    <item>
      <title>Re: CUA Security Issue - Communication Method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/cua-security-issue-communication-method/m-p/11325569#M1919463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;maybe that &lt;A href="http://search.sap.com/notes?id=1320166"&gt;SAP note 1320166 &lt;/A&gt; helps....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Sep 2015 06:00:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/cua-security-issue-communication-method/m-p/11325569#M1919463</guid>
      <dc:creator>Bernhard_SAP</dc:creator>
      <dc:date>2015-09-25T06:00:40Z</dc:date>
    </item>
  </channel>
</rss>

