<?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: Write protect for transaction in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767310#M331563</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi arna,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. For such scenarios, using memory id is not the way.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Lock objects should be created via se11,&lt;/P&gt;&lt;P&gt;   and used in the program,&lt;/P&gt;&lt;P&gt;   to detect the locks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;amit m.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 06 Dec 2006 11:16:05 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-12-06T11:16:05Z</dc:date>
    <item>
      <title>Write protect for transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767308#M331561</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 dialog program callable by a transaction. In this program there are&lt;/P&gt;&lt;P&gt;many tab strips with a database table for each tab strip. You can see, change&lt;/P&gt;&lt;P&gt;and delete the data of the database tables on each tab strip.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now it should be possible, that only one user can change and delete data at&lt;/P&gt;&lt;P&gt;the same time. So I have thought about writing a value in the memory and read&lt;/P&gt;&lt;P&gt;it every time at the beginning of the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If one user is starting the program and there isn´t an entry in the memory, the&lt;/P&gt;&lt;P&gt;memory should be set now. If another user is starting the program now, there&lt;/P&gt;&lt;P&gt;should be an entry in the memory, that I can protect the tables for changing and&lt;/P&gt;&lt;P&gt;deleting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried it like that:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
  DATA:  user  TYPE  sy-uname.

  IMPORT user FROM MEMORY ID 'user'.

  IF user IS INITIAL.
    user = sy-uname.
    EXPORT user TO MEMORY ID 'user'.
    CLEAR user.
  ENDIF.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is working, if You call the transaction at once. The username is stored in the&lt;/P&gt;&lt;P&gt;memory.&lt;/P&gt;&lt;P&gt;But when I now start the transaction in another mode the same time, I´m not&lt;/P&gt;&lt;P&gt;getting any entry for the field 'user' in the memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas? Or do You have any better ways how to protect the data?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank You very much!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points guaranteed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Dec 2006 11:11:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767308#M331561</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-06T11:11:26Z</dc:date>
    </item>
    <item>
      <title>Re: Write protect for transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767309#M331562</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;better use the sap lock concept to lock the database entries.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;use ENQUE AND DEQUE function modules of the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you can generate these for table from the transaction SE11. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REgards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Dec 2006 11:15:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767309#M331562</guid>
      <dc:creator>dani_mn</dc:creator>
      <dc:date>2006-12-06T11:15:28Z</dc:date>
    </item>
    <item>
      <title>Re: Write protect for transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767310#M331563</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi arna,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. For such scenarios, using memory id is not the way.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Lock objects should be created via se11,&lt;/P&gt;&lt;P&gt;   and used in the program,&lt;/P&gt;&lt;P&gt;   to detect the locks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;amit m.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Dec 2006 11:16:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767310#M331563</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-06T11:16:05Z</dc:date>
    </item>
    <item>
      <title>Re: Write protect for transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767311#M331564</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;you have to use lock objects for solving your purpose...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;use the following links...&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21eef3446011d189700000e8322d00/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21eef3446011d189700000e8322d00/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;pavan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Dec 2006 11:19:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767311#M331564</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-06T11:19:48Z</dc:date>
    </item>
    <item>
      <title>Re: Write protect for transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767312#M331565</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank You!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can You tell me very to set the table lock in TA SE11?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Dec 2006 11:19:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767312#M331565</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-06T11:19:55Z</dc:date>
    </item>
    <item>
      <title>Re: Write protect for transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767313#M331566</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The better idea to implement SAP Standard Locking Mechanism to prevent data should be deleted from other users.  If you are dealing with HR Module, then you can try using these FM's &amp;lt;b&amp;gt;BAPI_EMPLOYEE_ENQUEUE &amp;amp; BAPI_EMPLOYEE_DEQUEUE&amp;lt;/b&amp;gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To know more about this, please visit the below link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;a href="http://help.sap.com/saphelp_nw04s/helpdata/en/c2/2d7037ecc92a7ee10000009b38f8cf/frameset.htm"&amp;gt;Locking&amp;lt;/a&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ramki.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Dec 2006 11:26:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767313#M331566</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-06T11:26:34Z</dc:date>
    </item>
    <item>
      <title>Re: Write protect for transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767314#M331567</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In t-code SE11 there is a radio button for Lock object select that and create a lock object for ur table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Enter the primary and secondary tables there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ur lock name must start with EZ&amp;lt;name&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Dec 2006 11:27:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767314#M331567</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-06T11:27:04Z</dc:date>
    </item>
    <item>
      <title>Re: Write protect for transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767315#M331568</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;          use lock objects for your requirement&lt;/P&gt;&lt;P&gt;           lockobject is created using se11 &lt;/P&gt;&lt;P&gt;   by default enqueue_&amp;lt;lock objectname&amp;gt;      &lt;/P&gt;&lt;P&gt;              dequeue_&amp;lt;lock objectname&amp;gt; are created &lt;/P&gt;&lt;P&gt;   by SAP.&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;   you can create at table level or row level lock.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     CALL FUNCTION 'ENQUEUE_EZPPX0010A'&lt;/P&gt;&lt;P&gt;       EXPORTING&lt;/P&gt;&lt;P&gt;            MODE_ZPPDORD   = 'E'&lt;/P&gt;&lt;P&gt;            MANDT          = SY-MANDT&lt;/P&gt;&lt;P&gt;            WERKS          = S_WERKS&lt;/P&gt;&lt;P&gt;            AUFNR          = X_LOCK_LEVEL&lt;/P&gt;&lt;P&gt;       EXCEPTIONS&lt;/P&gt;&lt;P&gt;            OTHERS       = 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;delete lock after each insertion&lt;/P&gt;&lt;P&gt;or use call function 'DEQUEUE_ALL'           &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  CALL FUNCTION 'DEQUEUE_EZPPX0010A' &lt;/P&gt;&lt;P&gt;       EXPORTING&lt;/P&gt;&lt;P&gt;            MODE_ZPPDORD   = 'E'&lt;/P&gt;&lt;P&gt;            MANDT          = SY-MANDT&lt;/P&gt;&lt;P&gt;            WERKS          = S_WERKS&lt;/P&gt;&lt;P&gt;            AUFNR          = X_LOCK_LEVEL&lt;/P&gt;&lt;P&gt;       EXCEPTIONS&lt;/P&gt;&lt;P&gt;            OTHERS       = 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;amole&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REgards&lt;/P&gt;&lt;P&gt;amole&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Dec 2006 11:40:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/write-protect-for-transaction/m-p/1767315#M331568</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-06T11:40:58Z</dc:date>
    </item>
  </channel>
</rss>

