<?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: Infotype screen extension in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/infotype-screen-extension/m-p/7696427#M1577536</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Got the requirement wrong &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt; ... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But just to have the fields open for input when you raise a error message you need the fields to be added between CHAIN ... ENDCHAIN. I agree with your current design only the Z field will be open for input when  you raise error message.&lt;/P&gt;&lt;P&gt;But the infotype framwork is designed such that. Ideally uou should not be adding the Z field to the standard module pool of the infotype, as doing it may allow the std. infotype to work in right way. Check in SAP help for exact places you need to make changes if you are modifying the std. screen. There is a detailed topic regarding that, which details which modules in PBO and PAI you can modify, and also if you are adding custom modules where exactly you need to add them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ranganath&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 22 Feb 2011 16:13:11 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2011-02-22T16:13:11Z</dc:date>
    <item>
      <title>Infotype screen extension</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/infotype-screen-extension/m-p/7696424#M1577533</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I extended an infotype. I modified the Structure, and the screen, and everything works perfectly, &lt;STRONG&gt;but&lt;/STRONG&gt; there is a problem:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the standard screen there is a FIeld P0004-SBGRU&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to implement a check in the PAI, where I check if the P004-SBGRU  = 'H2' then P0004-SBPRO OR P0004-ZZ_SBPRO  must be filled.&lt;/P&gt;&lt;P&gt;pseudo code:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
IF P0004-SBGRU EQ 'H2'.
  IF P0004-SBPRO IS INITIAL  AND P0004-ZZ_SBPRO IS INITIAL
     MESSAGE e055(00). "one of the field is obligatory
  ENDIF.
ENDIF.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problemis that in my customer subscreen, I can only acces the Z fields:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
CHAIN.
    FIELD P0004-ZZ_SBPRO.
    MODULE INPUT_STATUS_SUBSCREEN ON CHAIN-REQUEST.
    MODULE CHECK_CATEGORY ON CHAIN-REQUEST.
 ENDCHAIN.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;My question is:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;:Is it possible to check the main screen's field in the subscreen?  (without modifying SAP standard screen)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;N.G.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Feb 2011 10:39:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/infotype-screen-extension/m-p/7696424#M1577533</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-22T10:39:40Z</dc:date>
    </item>
    <item>
      <title>Re: Infotype screen extension</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/infotype-screen-extension/m-p/7696425#M1577534</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;Yes you can access your screen values from the main program by reading the call stack.&lt;/P&gt;&lt;P&gt;You can use the below code,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
field-symbols : &amp;lt;fs1&amp;gt; type any.
field-symbols : &amp;lt;fs2&amp;gt; type any.
constants : lv_char1 type string value '(MP000400)P0004-SBPRO'.
constants : lv_char2 type string value '(MP000400)P0004-SBGRU'.

assign (lv_char1) to &amp;lt;fs1&amp;gt;.
assign (lv_char2) to &amp;lt;fs2&amp;gt;.

if &amp;lt;fs2&amp;gt; = 'H2'.
  IF &amp;lt;fs1&amp;gt; IS INITIAL  AND P0004-ZZ_SBPRO IS INITIAL
     MESSAGE e055(00). "one of the field is obligatory
  ENDIF.
endif.

&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ranganath&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Feb 2011 12:56:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/infotype-screen-extension/m-p/7696425#M1577534</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-22T12:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: Infotype screen extension</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/infotype-screen-extension/m-p/7696426#M1577535</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ranganath,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your answer, but this is not a solution for my problem. You don't need to use the stack in the infotype subscreen, because the whole pnnnn structure is available, so you can use the P0004-SBPRO directly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My problem is int he module. the CHAIN-ENDCHAIN section. As you know, you should specify the every field which is relevant for the check here. In this case two field is relevant:&lt;/P&gt;&lt;P&gt;- P0004-SBPRO (standard field on the standard screen)&lt;/P&gt;&lt;P&gt;- P0004-ZZ_SBPRO  (customer field on the customer screen)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is that in the customer module (ZP000400) I can only add the P0004-ZZ_SBPRO  between the CAHIN-ENDCHAIN segment, because the P0004-SBPRO is definied in the infotype main module (MP000400) But I need this field in the check , because I have to check both of them in the same CHAIN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As I see there is no other option, I have to add it to the customer inculde of the main module MP000400&lt;/P&gt;&lt;P&gt;Bye&lt;/P&gt;&lt;P&gt;N.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Feb 2011 14:17:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/infotype-screen-extension/m-p/7696426#M1577535</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-22T14:17:34Z</dc:date>
    </item>
    <item>
      <title>Re: Infotype screen extension</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/infotype-screen-extension/m-p/7696427#M1577536</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Got the requirement wrong &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt; ... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But just to have the fields open for input when you raise a error message you need the fields to be added between CHAIN ... ENDCHAIN. I agree with your current design only the Z field will be open for input when  you raise error message.&lt;/P&gt;&lt;P&gt;But the infotype framwork is designed such that. Ideally uou should not be adding the Z field to the standard module pool of the infotype, as doing it may allow the std. infotype to work in right way. Check in SAP help for exact places you need to make changes if you are modifying the std. screen. There is a detailed topic regarding that, which details which modules in PBO and PAI you can modify, and also if you are adding custom modules where exactly you need to add them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ranganath&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Feb 2011 16:13:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/infotype-screen-extension/m-p/7696427#M1577536</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-22T16:13:11Z</dc:date>
    </item>
    <item>
      <title>Re: Infotype screen extension</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/infotype-screen-extension/m-p/7696428#M1577537</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ranganath,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't want to change the SAP standrd screen. So I impemented the check is the Standard customer function of the infotype screen checks.  This is is not the best solution because if there is an error, then not just the two questionable field is highlighted, all of the fields are editable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, thanks for the help, now I 100% sure, that this is the only acceptable solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bye&lt;/P&gt;&lt;P&gt;N.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Feb 2011 16:29:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/infotype-screen-extension/m-p/7696428#M1577537</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-22T16:29:59Z</dc:date>
    </item>
  </channel>
</rss>

