<?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: Password check in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/password-check/m-p/7056801#M1502773</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Uhm... Not sure why every approval should require a password (isn't authorization level security enough for this?), but you can always build your own screen/table for the password entry. Then you can declare the password field as big as you need.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 21 Jul 2010 22:04:53 GMT</pubDate>
    <dc:creator>Jelena_Perfiljeva</dc:creator>
    <dc:date>2010-07-21T22:04:53Z</dc:date>
    <item>
      <title>Password check</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/password-check/m-p/7056800#M1502772</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a reqmt where in material Master after change in material the QA approal should be done.&lt;/P&gt;&lt;P&gt;For that QA approval i have developed a report program where the report fetch the material number that has been changed.&lt;/P&gt;&lt;P&gt;From this report the user will click the button Select approval then a pop will prompt to give the password.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This password field i took it from structure RSYST and field  BCODE,  butit is accepting only 8 char even as per documentation it is explained.&lt;/P&gt;&lt;P&gt;But i need to pass more than 8 chars.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could anyone suggest me, what can be for thsi.&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, 21 Jul 2010 13:11:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/password-check/m-p/7056800#M1502772</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-07-21T13:11:07Z</dc:date>
    </item>
    <item>
      <title>Re: Password check</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/password-check/m-p/7056801#M1502773</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Uhm... Not sure why every approval should require a password (isn't authorization level security enough for this?), but you can always build your own screen/table for the password entry. Then you can declare the password field as big as you need.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Jul 2010 22:04:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/password-check/m-p/7056801#M1502773</guid>
      <dc:creator>Jelena_Perfiljeva</dc:creator>
      <dc:date>2010-07-21T22:04:53Z</dc:date>
    </item>
    <item>
      <title>Re: Password check</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/password-check/m-p/7056802#M1502774</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are re-inventing the wheel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The process you are describing is what Change Numbers (Cross-Application Components -&amp;gt; Engineering Change Management -&amp;gt; Change Number ...) are for: a regulated, linear process for changing (amongst others) material master. Combined with workflow and proper authorisations (see Jelena's answer) should do the trick nicely.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Programming passwords in Abap, which are not properly encoded (hashed?) and frequently used by numerous people who need them to work on a &lt;STRONG&gt;single process&lt;/STRONG&gt; are not security, but an obstacle!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which is why SAP invented Cross-Applications.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Jul 2010 07:04:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/password-check/m-p/7056802#M1502774</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-07-22T07:04:22Z</dc:date>
    </item>
    <item>
      <title>Re: Password check</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/password-check/m-p/7056803#M1502775</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you answered&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Aug 2010 13:09:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/password-check/m-p/7056803#M1502775</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-08-10T13:09:39Z</dc:date>
    </item>
  </channel>
</rss>

