<?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 BTE 1030 problem with Inter-CO document in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bte-1030-problem-with-inter-co-document/m-p/6485767#M1419649</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I implemented business transaction event 1030 because this event has the document number available. Within the custom function module I call a screen for some line items that match certain criteria. From that screen I am populating a custom table with the document #, CO, year, line #, and the additional data that the user enters on the screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This business transaction event works fine for documents that are not inter-company. Inter-company documents cause an error when the screen is called:  the transaction ends and the document is not saved.  This is the text of the error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN __default_attr="green" __jive_macro_name="color"&gt;Call screen (not modal) in modal dialog box not allowed .&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At this point I don't see any way around this problem. Has anybody else seen this? If so, what did you do?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Bruce&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 11 Jan 2010 19:42:13 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2010-01-11T19:42:13Z</dc:date>
    <item>
      <title>BTE 1030 problem with Inter-CO document</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bte-1030-problem-with-inter-co-document/m-p/6485767#M1419649</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I implemented business transaction event 1030 because this event has the document number available. Within the custom function module I call a screen for some line items that match certain criteria. From that screen I am populating a custom table with the document #, CO, year, line #, and the additional data that the user enters on the screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This business transaction event works fine for documents that are not inter-company. Inter-company documents cause an error when the screen is called:  the transaction ends and the document is not saved.  This is the text of the error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN __default_attr="green" __jive_macro_name="color"&gt;Call screen (not modal) in modal dialog box not allowed .&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At this point I don't see any way around this problem. Has anybody else seen this? If so, what did you do?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Bruce&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jan 2010 19:42:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bte-1030-problem-with-inter-co-document/m-p/6485767#M1419649</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-01-11T19:42:13Z</dc:date>
    </item>
    <item>
      <title>Re: BTE 1030 problem with Inter-CO document</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bte-1030-problem-with-inter-co-document/m-p/6485768#M1419650</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 are hitting a technical limitation of SAP. So it looks like your only way is to define your custom screen as modal dialog box. I am not sure if it is acceptable for you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jan 2010 22:47:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bte-1030-problem-with-inter-co-document/m-p/6485768#M1419650</guid>
      <dc:creator>mvoros</dc:creator>
      <dc:date>2010-01-11T22:47:54Z</dc:date>
    </item>
    <item>
      <title>Re: BTE 1030 problem with Inter-CO document</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bte-1030-problem-with-inter-co-document/m-p/6485769#M1419651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Martin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I needed my screen to be normal screen because there is a fair amount of logic in the PBO and PAI as well as data entry on the screen. A modal window would not have met my needs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I got past the limitation I was experiencing by removing the "call screen" statement and instead writing a new ABAP program which calls the screen and submitting that program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Changed  &lt;SPAN __default_attr="green" __jive_macro_name="color"&gt;call screen ...&lt;/SPAN&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;to                &lt;SPAN __default_attr="green" __jive_macro_name="color"&gt;submit Z...  and return&lt;/SPAN&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bruce&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Bruce Tjosvold on Jan 12, 2010 12:16 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Jan 2010 17:13:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bte-1030-problem-with-inter-co-document/m-p/6485769#M1419651</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-01-12T17:13:37Z</dc:date>
    </item>
  </channel>
</rss>

