<?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>Question Re: authorization issues in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/authorization-issues/qaa-p/14440048#M4945804</link>
    <description>&lt;P&gt;I believe this question is best addressed to the Security team within your organization. Based solely on the information provided, it would not be possible to give reliable advice without a proper understanding of your internal processes, security policies, and organizational requirements.&lt;/P&gt;&lt;P&gt;Your Security team will be in the best position to assess the situation and provide guidance that aligns with your organization's standards and controls.&lt;/P&gt;</description>
    <pubDate>Tue, 14 Jul 2026 10:04:19 GMT</pubDate>
    <dc:creator>DmytroMaslennikov</dc:creator>
    <dc:date>2026-07-14T10:04:19Z</dc:date>
    <item>
      <title>authorization issues</title>
      <link>https://community.sap.com/t5/technology-q-a/authorization-issues/qaq-p/12634645</link>
      <description>&lt;P&gt;we as the stores team, we are not authorize to use the below Tcodes of which i think its a neccessity.&lt;/P&gt;
  &lt;P&gt;MB22,MM01,MM02,MM03,MIGO_TR,MMAM, for MB90 we only have a right to make one print out which is a big challenge to us because you are not even able to select the printer hence once the print out is send to the wrong printer, then it means you have lost it for good. In short we should be able to have a reprint of the same output and we should be able to select the printer, get a print preview before you print. We are not able to change or edit MIGO incase of an error. kindly activate MIGO for change. Kindly, Mr. Mahendra Dahiya assist!!&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jul 2022 09:09:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/authorization-issues/qaq-p/12634645</guid>
      <dc:creator>former_member1080866</dc:creator>
      <dc:date>2022-07-20T09:09:56Z</dc:date>
    </item>
    <item>
      <title>Re: authorization issues</title>
      <link>https://community.sap.com/t5/technology-q-a/authorization-issues/qaa-p/12634646#M4739524</link>
      <description>&lt;P&gt;Hello Jane,&lt;/P&gt;&lt;P&gt;are you sure that this is the right place to address your issue?&lt;/P&gt;&lt;P&gt;Usually you should address it in your own company to the support-team / person who is responsible for the SAP authorization, to whom in detail depends on your company-own organization and processes.&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Kornelia Schierwath&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jul 2022 09:29:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/authorization-issues/qaa-p/12634646#M4739524</guid>
      <dc:creator>kornelia_schierwath</dc:creator>
      <dc:date>2022-07-20T09:29:15Z</dc:date>
    </item>
    <item>
      <title>Re: authorization issues</title>
      <link>https://community.sap.com/t5/technology-q-a/authorization-issues/qaa-p/14440048#M4945804</link>
      <description>&lt;P&gt;I believe this question is best addressed to the Security team within your organization. Based solely on the information provided, it would not be possible to give reliable advice without a proper understanding of your internal processes, security policies, and organizational requirements.&lt;/P&gt;&lt;P&gt;Your Security team will be in the best position to assess the situation and provide guidance that aligns with your organization's standards and controls.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jul 2026 10:04:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/authorization-issues/qaa-p/14440048#M4945804</guid>
      <dc:creator>DmytroMaslennikov</dc:creator>
      <dc:date>2026-07-14T10:04:19Z</dc:date>
    </item>
  </channel>
</rss>

