<?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 Re: domain security in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/domain-security/m-p/2751083#M639857</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi thinker.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scenerio - 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;any object - domain, dataelement, field, table, program, screen etc..,&lt;/P&gt;&lt;P&gt;is created on a development system and is assigned a TRANSPORT REQUEST.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then the object is moved to quality or production.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now once the object is assigned to a key -( which in turn is assigned to a user), then the object cannot be modifed by another user.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This beautiful way of doing things in SAP, automatically takes care of your concern- data validity.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scenerio 2.&lt;/P&gt;&lt;P&gt;Now lets assume that you have created this object as a local object- no key attached and it is not going to be transported to another system ( quality / production). Then it can be modified by other users.  which is the situation you are facing.&lt;/P&gt;&lt;P&gt;or &lt;/P&gt;&lt;P&gt;you may be facing this situation because all user are using the same logon id and password.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Sep 2007 18:01:59 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-09-12T18:01:59Z</dc:date>
    <item>
      <title>domain security</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/domain-security/m-p/2751082#M639856</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hai in se11 we generally create domain for the field names or for other use,my query is if we r creating a domain and that domain is used for any use ,after the crstion of thst domain it will be in the data base with out any security in the sence any  third person can use the domain to his own use so in order to avoid third person usage on the damin which is crated byu us what the methodology or how can we authnticate a domain from preventing others to use it&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Sep 2007 17:20:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/domain-security/m-p/2751082#M639856</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-12T17:20:53Z</dc:date>
    </item>
    <item>
      <title>Re: domain security</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/domain-security/m-p/2751083#M639857</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi thinker.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scenerio - 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;any object - domain, dataelement, field, table, program, screen etc..,&lt;/P&gt;&lt;P&gt;is created on a development system and is assigned a TRANSPORT REQUEST.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then the object is moved to quality or production.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now once the object is assigned to a key -( which in turn is assigned to a user), then the object cannot be modifed by another user.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This beautiful way of doing things in SAP, automatically takes care of your concern- data validity.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scenerio 2.&lt;/P&gt;&lt;P&gt;Now lets assume that you have created this object as a local object- no key attached and it is not going to be transported to another system ( quality / production). Then it can be modified by other users.  which is the situation you are facing.&lt;/P&gt;&lt;P&gt;or &lt;/P&gt;&lt;P&gt;you may be facing this situation because all user are using the same logon id and password.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Sep 2007 18:01:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/domain-security/m-p/2751083#M639857</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-12T18:01:59Z</dc:date>
    </item>
    <item>
      <title>Re: domain security</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/domain-security/m-p/2751084#M639858</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Raj,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can provide access restrictions by LOCK OBJECTS  concept.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you know lock objects  provides the locking the access to a record, or filed ie domain or dataelement, or table.&lt;/P&gt;&lt;P&gt;SO better way is to be create lock object by using SE11.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward with points if useful.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Vijay&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Sep 2007 10:06:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/domain-security/m-p/2751084#M639858</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-13T10:06:33Z</dc:date>
    </item>
  </channel>
</rss>

