<?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: Excise duty Miro Issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/excise-duty-miro-issue/m-p/9729891#M1772163</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;MIRO only checks whether the valid condition records exists for a chosen tax code. If yes, it reads them and show up the simulation or accounting entries accordingly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can set the message 8I 478 RG23 Part II posting not yet done in CIN Messages and check the scenarios both excisable and non excisable and confirm the message works as you desired.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 30 Aug 2013 06:12:25 GMT</pubDate>
    <dc:creator>former_member192897</dc:creator>
    <dc:date>2013-08-30T06:12:25Z</dc:date>
    <item>
      <title>Excise duty Miro Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/excise-duty-miro-issue/m-p/9729888#M1772160</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I made PO with excisable tax code , I did GR without capturing excise duty &amp;amp; user post miro by selecting exciseable tax code. why should system allow to post MIRO with excisable tax code.&amp;amp; How should I validate so that if excise invoice is not post then user should not able to post miro with excisable tax code ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Aug 2013 17:23:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/excise-duty-miro-issue/m-p/9729888#M1772160</guid>
      <dc:creator>former_member193587</dc:creator>
      <dc:date>2013-08-26T17:23:08Z</dc:date>
    </item>
    <item>
      <title>Re: Excise duty Miro Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/excise-duty-miro-issue/m-p/9729889#M1772161</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please read the link to get a better understanding on system expectancy on Inv. posting .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_47x200/helpdata/en/a8/b99f58452b11d189430000e829fbbd/frameset.htm"&gt;http://help.sap.com/saphelp_47x200/helpdata/en/a8/b99f58452b11d189430000e829fbbd/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Its a Business need to capture excise when ever a exc. material comes in and out of an exc. plant.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;are you following using Taxinj or Taxinn -just fyi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Manu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Aug 2013 05:33:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/excise-duty-miro-issue/m-p/9729889#M1772161</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-08-27T05:33:57Z</dc:date>
    </item>
    <item>
      <title>Re: Excise duty Miro Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/excise-duty-miro-issue/m-p/9729890#M1772162</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 style="font-size: 12px; background-color: #ffffff; color: #333333;"&gt;SPRO - Logistics General - Tax on Goods Movement - India - Tools - Messsage control&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 12px; background-color: #ffffff; color: #333333;"&gt;Click on New Entreis&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 12px; background-color: #ffffff; color: #333333;"&gt;Application area: 8I&lt;/P&gt;&lt;P style="font-size: 12px; background-color: #ffffff; color: #333333;"&gt;Message Number: 478&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 12px; background-color: #ffffff; color: #333333;"&gt;Set the above message as Error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 12px; background-color: #ffffff; color: #333333;"&gt;This is will prevent you from MIRO postings with excise tax codes if Part 2 excise posting is not completed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 12px; background-color: #ffffff; color: #333333;"&gt;Thanks n Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Aug 2013 18:28:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/excise-duty-miro-issue/m-p/9729890#M1772162</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-08-29T18:28:00Z</dc:date>
    </item>
    <item>
      <title>Re: Excise duty Miro Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/excise-duty-miro-issue/m-p/9729891#M1772163</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;MIRO only checks whether the valid condition records exists for a chosen tax code. If yes, it reads them and show up the simulation or accounting entries accordingly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can set the message 8I 478 RG23 Part II posting not yet done in CIN Messages and check the scenarios both excisable and non excisable and confirm the message works as you desired.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Aug 2013 06:12:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/excise-duty-miro-issue/m-p/9729891#M1772163</guid>
      <dc:creator>former_member192897</dc:creator>
      <dc:date>2013-08-30T06:12:25Z</dc:date>
    </item>
    <item>
      <title>Re: Excise duty Miro Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/excise-duty-miro-issue/m-p/9729892#M1772164</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;Pls check the note &lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;&lt;A&gt;&lt;/A&gt;1535398 the msg 8I478 is maintained as warnning/error msg &lt;/P&gt;&lt;P&gt;In the SPRO settings you need to maintain it was warning/error as per your needs.&lt;/P&gt;&lt;P&gt;SPRO&amp;gt;Logistics General&amp;gt;Tax on Goods Movement&amp;gt;India&amp;gt;Tools&amp;gt;&lt;BR /&gt;Message Control.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ((((((((((OR)))))))))))))))))))&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please use the user exit given in the note :&lt;/P&gt;&lt;P&gt;858772 &amp;gt; RG 23 Part II message not coming during MIRO&lt;/P&gt;&lt;P&gt;This note will allow you to write you own logic on when &amp;amp; what parameter&lt;BR /&gt;the system should consider to get the message in MIRO.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rajasree R&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Sep 2013 05:40:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/excise-duty-miro-issue/m-p/9729892#M1772164</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-09-04T05:40:13Z</dc:date>
    </item>
  </channel>
</rss>

