<p>H.</p>
<p>I&#8217;ve decided to test procedures infotype 0130. It allows to restrict access to history records for some infotypes. You know that regular permission system doesn&#8217;t allow to manage access over the period. If you have access you can change record independently of its date. What if we need to restrict access in &#8220;closed periods&#8221;? Use infotype 0130.</p>
<p>Test procedure &#8211; subtype of 130&#8217;s infotype. Infotypes are assigned to test procedure. For example, &#8220;Time data&#8221; test procedure with 7, 2001, 2002, 2003 infotypes could restrict access to previous records. Just to avoid any changes in history.</p>
<p>Set AUTSW APPRO value in OOAC transaction.</p>
<p>The procedure itself is quite easy. It&#8217;s need to create 130 infotype with correct subtype &#8211; test procedure &#8211; for employees whom you need to restrict history data change. Let&#8217;s say it&#8217;s May 1st is entered into infotype. It means data before May couldn&#8217;t be changed for time infotypes (in case you set Time test procedure).</p>
<p>You&#8217;d better to use LSMW to create infotype 130.</p>
<p>To lock or unlock data entry in mass use RPTAPPU0 program.</p>
<p>Advice. To setup procedure don&#8217;t forget to add infotype 130 into P_ORGIN object in your roles. And split it by subtypes of 130 infotype. Everybody entering time data should have read access to 130 infotype. Administrator should have change access.</p>