<?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 Qnnnn structure? in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/qnnnn-structure/m-p/1368416#M181828</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt; Can anybody explain me the prominence of the sturucture "Qnnnn" in SAP-HR.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 May 2006 10:28:09 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-05-11T10:28:09Z</dc:date>
    <item>
      <title>Qnnnn structure?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/qnnnn-structure/m-p/1368416#M181828</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt; Can anybody explain me the prominence of the sturucture "Qnnnn" in SAP-HR.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 May 2006 10:28:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/qnnnn-structure/m-p/1368416#M181828</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-11T10:28:09Z</dc:date>
    </item>
    <item>
      <title>Re: Qnnnn structure?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/qnnnn-structure/m-p/1368417#M181829</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;These structures correspond to the screen fields of the infotype nnnn.&lt;/P&gt;&lt;P&gt;These screen fields appear on different infotype transactions.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 May 2006 10:42:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/qnnnn-structure/m-p/1368417#M181829</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-11T10:42:32Z</dc:date>
    </item>
    <item>
      <title>Re: Qnnnn structure?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/qnnnn-structure/m-p/1368418#M181830</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vijay,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Screen fields from Qnnnn structures (Q fields):&lt;/P&gt;&lt;P&gt;These fields are used like the infotype single screens when the external format is different&lt;/P&gt;&lt;P&gt;from the internal format.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Each Q field must have an invisible P field on the screen which contains the field contents in&lt;/P&gt;&lt;P&gt;the internal format, since only the contents of P fields can be passed on to the infotypes.&lt;/P&gt;&lt;P&gt;Field Q0002-ANREX (&amp;#145;Mr&amp;#146;, &amp;#145;Ms&amp;#146;) has invisible field P0002-ANRED (&amp;#145;1&amp;#146;, &amp;#145;2&amp;#146;) with the&lt;/P&gt;&lt;P&gt;value &amp;#145;001&amp;#146; in modif group 1.&lt;/P&gt;&lt;P&gt;Q fields are not assigned a value in modif group 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When defining screen fields in the ABAP Screen Painter, do not specify structural data (such as&lt;/P&gt;&lt;P&gt;the data type and length) directly when maintaining the screen. It is better to specify such data&lt;/P&gt;&lt;P&gt;indirectly so that it is taken from the definition of objects in the Data Dictionary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Individual fields are contained in various structures, depending on their meaning:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;_ Fields that are displayed for all infotypes are stored in structure RP50M.&lt;/P&gt;&lt;P&gt;Such fields include, for example, the headers for single screens.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;_ Fields that are infotype-specific are stored in structure PSnnnn.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You might want a screen to include screen fields that are not yet included in a structure. If this is&lt;/P&gt;&lt;P&gt;the case, you must create structure Znnnn in addition to structure PSnnnn. You can then use&lt;/P&gt;&lt;P&gt;structure Znnnn to store all of the fields that must be displayed on the screen but are not yet&lt;/P&gt;&lt;P&gt;included in a Data Dictionary structure. The name of the corresponding structure for infotypes in&lt;/P&gt;&lt;P&gt;the standard system is Qnnnn.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data Dictionary structures with the name Qnnnn are always stored within the SAP&lt;/P&gt;&lt;P&gt;name range.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may encounter problems assigning values to fields having the form QNNNN-FIELDNAME. These are fields that are visible on the infotype screen Examples are Q0082-datwc and Q0112-PZIN3. There lies a chance that these fields are overwritten by values computed during the PBO and PAI modules of the infotype screen. For this reason, assigning values to these fields in W statements may or may not have any practical effect. However, you can use them in your P statements. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Refer this link for more details.&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAXX/PYINT_INFOTYP.pdf" target="test_blank"&gt;http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAXX/PYINT_INFOTYP.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Susmitha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 May 2006 10:42:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/qnnnn-structure/m-p/1368418#M181830</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-11T10:42:40Z</dc:date>
    </item>
  </channel>
</rss>

