<?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: bdc in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2096776#M436664</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ramu,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to execute the job in background .There are 2 options.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.Online&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Goto se38--&amp;gt;enter program name &lt;DEL&gt;&amp;gt;(On menu bar) program&lt;/DEL&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;Exceute--&amp;gt;Background.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.Schedule&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scheduling Background Jobs:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Background jobs are scheduled by Basis administrators using transaction SM36.&lt;/P&gt;&lt;P&gt;2. To run a report in a background, a job needs to be created with a step using the report name &lt;/P&gt;&lt;P&gt;and a variant for selection parameters. It is recommended to create a separate variant for each &lt;/P&gt;&lt;P&gt;scheduled job to produce results for specific dates (e.g. previous month) or organizational units (e.g. company codes).&lt;/P&gt;&lt;P&gt;3. While defining the step, the spool parameters needs to be specified&lt;/P&gt;&lt;P&gt;(Step-&amp;gt; Print Specifications-&amp;gt;Properties) to secure the output of the report and help authorized users to find the spool request. The following parameters needs to be maintained:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a. Time of printing: set to &amp;#147;Send to SAP spooler Only for now&amp;#148;&lt;/P&gt;&lt;P&gt;b. Name &amp;#150; abbreviated name to identify the job output&lt;/P&gt;&lt;P&gt;c. Title &amp;#150; free form description for the report output&lt;/P&gt;&lt;P&gt;d. Authorization &amp;#150; a value defined by Security in user profiles to allow those users to access &lt;/P&gt;&lt;P&gt;this spool request (authorization object S_SPO_ACT, value SPOAUTH). Only users with matching authorization value in their profiles will be able to see the output.&lt;/P&gt;&lt;P&gt;e. Department &amp;#150; set to appropriate department/functional area name. This field can be used in &lt;/P&gt;&lt;P&gt;a search later.&lt;/P&gt;&lt;P&gt;f. Retention period &amp;#150; set to &amp;#147;Do not delete&amp;#148; if the report output needs to be retained for more &lt;/P&gt;&lt;P&gt;than 8 days. Once the archiving/document repository solution is in place the spool requests could &lt;/P&gt;&lt;P&gt;be automatically moved to the archive/repository. Storage Mode parameter on the same screen &lt;/P&gt;&lt;P&gt;could be used to immediately send the output to archive instead of creating a spool request.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Configuring user access:&lt;/P&gt;&lt;P&gt;1. To access a report output created by a background job, a user must have at least access to SP01 (Spool requests) transaction without restriction on the user name (however by itself it will not let the user to see all spool requests). To have that access the user must have S_ADMI_FCD authorization object in the profile with SPOR (or SP01) value of S_ADMI_FCD parameter (maintained by Security).&lt;/P&gt;&lt;P&gt;2. To access a particular job&amp;#146;s output in the spool, the user must have S_SPO_ACT object in the profile with SPOAUTH parameter matching the value used in the Print Specifications of the job &lt;/P&gt;&lt;P&gt;3. Levels of access to the spool (display, print once, reprint, download, etc) are controlled by SPOACTION parameter of S_SPO_ACT. The user must have at least BASE access (display).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this resolves your query.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward all the helpful answers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 29 Mar 2007 05:57:58 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-03-29T05:57:58Z</dc:date>
    <item>
      <title>bdc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2096774#M436662</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;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to run a bdc program scheduled to run in the background in batch mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&amp;amp;Regards.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ramu.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Mar 2007 04:24:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2096774#M436662</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-29T04:24:47Z</dc:date>
    </item>
    <item>
      <title>Re: bdc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2096775#M436663</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;There are two methods to run bdc in background.&lt;/P&gt;&lt;P&gt; one is programatically i.e. in the program you can use JOB_OPEN fucntion module and after that you can submit you program and after that you can close the job by using funcnction module JOB_CLOSE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Second method is by using SM36 transaction you can do this.&lt;/P&gt;&lt;P&gt;Generally functional guys can do this method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;shyla&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Mar 2007 05:39:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2096775#M436663</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-29T05:39:09Z</dc:date>
    </item>
    <item>
      <title>Re: bdc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2096776#M436664</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ramu,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to execute the job in background .There are 2 options.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.Online&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Goto se38--&amp;gt;enter program name &lt;DEL&gt;&amp;gt;(On menu bar) program&lt;/DEL&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;Exceute--&amp;gt;Background.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.Schedule&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scheduling Background Jobs:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Background jobs are scheduled by Basis administrators using transaction SM36.&lt;/P&gt;&lt;P&gt;2. To run a report in a background, a job needs to be created with a step using the report name &lt;/P&gt;&lt;P&gt;and a variant for selection parameters. It is recommended to create a separate variant for each &lt;/P&gt;&lt;P&gt;scheduled job to produce results for specific dates (e.g. previous month) or organizational units (e.g. company codes).&lt;/P&gt;&lt;P&gt;3. While defining the step, the spool parameters needs to be specified&lt;/P&gt;&lt;P&gt;(Step-&amp;gt; Print Specifications-&amp;gt;Properties) to secure the output of the report and help authorized users to find the spool request. The following parameters needs to be maintained:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a. Time of printing: set to &amp;#147;Send to SAP spooler Only for now&amp;#148;&lt;/P&gt;&lt;P&gt;b. Name &amp;#150; abbreviated name to identify the job output&lt;/P&gt;&lt;P&gt;c. Title &amp;#150; free form description for the report output&lt;/P&gt;&lt;P&gt;d. Authorization &amp;#150; a value defined by Security in user profiles to allow those users to access &lt;/P&gt;&lt;P&gt;this spool request (authorization object S_SPO_ACT, value SPOAUTH). Only users with matching authorization value in their profiles will be able to see the output.&lt;/P&gt;&lt;P&gt;e. Department &amp;#150; set to appropriate department/functional area name. This field can be used in &lt;/P&gt;&lt;P&gt;a search later.&lt;/P&gt;&lt;P&gt;f. Retention period &amp;#150; set to &amp;#147;Do not delete&amp;#148; if the report output needs to be retained for more &lt;/P&gt;&lt;P&gt;than 8 days. Once the archiving/document repository solution is in place the spool requests could &lt;/P&gt;&lt;P&gt;be automatically moved to the archive/repository. Storage Mode parameter on the same screen &lt;/P&gt;&lt;P&gt;could be used to immediately send the output to archive instead of creating a spool request.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Configuring user access:&lt;/P&gt;&lt;P&gt;1. To access a report output created by a background job, a user must have at least access to SP01 (Spool requests) transaction without restriction on the user name (however by itself it will not let the user to see all spool requests). To have that access the user must have S_ADMI_FCD authorization object in the profile with SPOR (or SP01) value of S_ADMI_FCD parameter (maintained by Security).&lt;/P&gt;&lt;P&gt;2. To access a particular job&amp;#146;s output in the spool, the user must have S_SPO_ACT object in the profile with SPOAUTH parameter matching the value used in the Print Specifications of the job &lt;/P&gt;&lt;P&gt;3. Levels of access to the spool (display, print once, reprint, download, etc) are controlled by SPOACTION parameter of S_SPO_ACT. The user must have at least BASE access (display).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this resolves your query.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward all the helpful answers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Mar 2007 05:57:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2096776#M436664</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-29T05:57:58Z</dc:date>
    </item>
  </channel>
</rss>

