<?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: Recording in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/recording/m-p/2104598#M439060</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;&amp;lt;b&amp;gt;No, you do not need to write "perform fill_bdc_field" for BDC_SUBSCR. Actually this code is for sub screens in MM01.&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;"BDC_SUBRC" is for subscreen on transaction MM01&amp;lt;/b&amp;gt;. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let's say you display one material in MM03. Look at the "&amp;lt;b&amp;gt;Basic data1&amp;lt;/b&amp;gt;" screen of this material. &amp;lt;b&amp;gt;You will see that there are subscreen&amp;lt;/b&amp;gt; called &amp;lt;b&amp;gt;'general data&amp;lt;/b&amp;gt;', &amp;lt;b&amp;gt;'material authorization group'&amp;lt;/b&amp;gt; , ' &amp;lt;b&amp;gt;dimensions/EANs'&amp;lt;/b&amp;gt; etc.  These are subscreen areas which you see in BDC.  You do not need to code them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, after you do the recording using SHDB, you can generate the test program from here. Generate the test program for your recording, you will se that SAP also does not include 'BDC_SUBRC' in the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope i clarify your doubt. Let me know if you still have question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;RS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 03 Apr 2007 21:14:12 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-04-03T21:14:12Z</dc:date>
    <item>
      <title>Recording</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/recording/m-p/2104597#M439059</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;When i have run the shdb recording for material ...i got something like bdc_subscr aprt from okcode  and fields.&lt;/P&gt;&lt;P&gt;what does bdc_subcr mean. Do I need to write perform fill_bdc_field using for this also ????&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;plz help&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2007 21:03:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/recording/m-p/2104597#M439059</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-03T21:03:34Z</dc:date>
    </item>
    <item>
      <title>Re: Recording</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/recording/m-p/2104598#M439060</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;&amp;lt;b&amp;gt;No, you do not need to write "perform fill_bdc_field" for BDC_SUBSCR. Actually this code is for sub screens in MM01.&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;"BDC_SUBRC" is for subscreen on transaction MM01&amp;lt;/b&amp;gt;. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let's say you display one material in MM03. Look at the "&amp;lt;b&amp;gt;Basic data1&amp;lt;/b&amp;gt;" screen of this material. &amp;lt;b&amp;gt;You will see that there are subscreen&amp;lt;/b&amp;gt; called &amp;lt;b&amp;gt;'general data&amp;lt;/b&amp;gt;', &amp;lt;b&amp;gt;'material authorization group'&amp;lt;/b&amp;gt; , ' &amp;lt;b&amp;gt;dimensions/EANs'&amp;lt;/b&amp;gt; etc.  These are subscreen areas which you see in BDC.  You do not need to code them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, after you do the recording using SHDB, you can generate the test program from here. Generate the test program for your recording, you will se that SAP also does not include 'BDC_SUBRC' in the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope i clarify your doubt. Let me know if you still have question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;RS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2007 21:14:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/recording/m-p/2104598#M439060</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-03T21:14:12Z</dc:date>
    </item>
    <item>
      <title>Re: Recording</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/recording/m-p/2104599#M439061</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thats "subscreen" and yes you have to write it to dbcdata too, value will look like&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;"SAPLKACB                                0003BLOCK1"&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&amp;lt;i&amp;gt;For the batch input processing, the system assigns all field names to one screen, the main screen. Field names are not assigned to embedded screens, that is, to subscreens.&lt;/P&gt;&lt;P&gt;However, the screen simulation requires information about the subscreens to be called. This information is retrieved from the batch input BDC_SUBSCR field.&lt;/P&gt;&lt;P&gt;Without the BDC_SUBSCR field values, the fields that are located in the relevant subscreens cannot be simulated. For the batch input processing, the BDC_SUBSCR fields are irrelevant.&amp;lt;/i&amp;gt; (From OSS  &amp;lt;a href="https://service.sap.com/sap/support/notes/728079"&amp;gt;Note 728079 - Batch input analysis: Display error in screen simulation&amp;lt;/a&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2007 21:18:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/recording/m-p/2104599#M439061</guid>
      <dc:creator>RaymondGiuseppi</dc:creator>
      <dc:date>2007-04-03T21:18:24Z</dc:date>
    </item>
    <item>
      <title>Re: Recording</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/recording/m-p/2104600#M439062</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks guys.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How do i generate the test program?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2007 21:28:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/recording/m-p/2104600#M439062</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-03T21:28:02Z</dc:date>
    </item>
    <item>
      <title>Re: Recording</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/recording/m-p/2104601#M439063</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You get an option in SHDB to generate a program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;+Before you can generate a data transfer program, you must record the transactions using which the data is imported into the R/3 System. You use the batch input recorder to do this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Procedure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Display the initial screen of the batch input recorder (Transaction SHDB). &lt;/P&gt;&lt;P&gt;Choose Overview.&lt;/P&gt;&lt;P&gt;The system displays an overview of all recordings. &lt;/P&gt;&lt;P&gt;Position the cursor on the relevant recording and choose Create program. &lt;/P&gt;&lt;P&gt;On the following screen, specify a program name. &lt;/P&gt;&lt;P&gt;You can also choose how the maintained field contents of the recorded screens are to be filled: &lt;/P&gt;&lt;P&gt;· Transfer the values that were used during the recording. If you require a flexible data transfer, you must modify this program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;· Set the parameters of the input values to be maintained and import these values from a data file. To set the parameters, the system creates a data structure and imports the data records from an external file into this data structure. The program assumes that the external file has been adapted to this data structure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have decided to set parameters for the input values to be maintained, it is useful if you create a test file when you generate the program. To do this, flag the checkbox and enter a name for the test file. For more information, see creating a test file. &lt;/P&gt;&lt;P&gt;Choose Continue. &lt;/P&gt;&lt;P&gt;The system displays the attribute screen of the program editor. Choose the relevant attributes here and save the program.&lt;/P&gt;&lt;P&gt;Result&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You have now generated a data transfer program that you can use to import data into the R/3 System. The program can execute the data transfer using batch input or CALL TRANSACTION .+&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2007 21:30:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/recording/m-p/2104601#M439063</guid>
      <dc:creator>RaymondGiuseppi</dc:creator>
      <dc:date>2007-04-03T21:30:16Z</dc:date>
    </item>
  </channel>
</rss>

