<?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 Calling transactions with pre-filled screen in background processing in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/calling-transactions-with-pre-filled-screen-in-background-processing/m-p/5795978#M1310826</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;We are currently running the two standard SAP programs RVV50R10C and SDV03V02 in background mode with static variants. A new requirement has come up whereby we need to run these programs with changing selection criterions, i.e. depending on whether a certain material has had a movement during the day.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are currently looking at the following options, all of which must be executeable in background mode:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Create a Z-program which identifies the materials for which RVV50R10C and SDV03V02 should process, and then at the end of the Z-program save variants containing the materials for each of the two standard programs. The standard programs will be scheduled as step #2 and #3 in the same batch job by using the variant which has been overwritten by the Z-program. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) Create a Z-program which identifies the materials for which RVV50R10C and SDV03V02 should process, and then at the end of the Z-program call these programs by specifying the material numbers in addition to other relevant selection criterions by passing a batch input table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3) Copy the standard programs into Z-versions and enhance the selection criterias according to our needs. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Of the options above we would prefer not to use 3) since we rather use the standard programs due to SAP support etc. The preferred option would be 1). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone faced a similar requirement and have some ideas about standard SAP functions to save a variant and what issues we might face in option 1) and 2)?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 19 Jun 2009 09:16:06 GMT</pubDate>
    <dc:creator>geir_kronkvist1</dc:creator>
    <dc:date>2009-06-19T09:16:06Z</dc:date>
    <item>
      <title>Calling transactions with pre-filled screen in background processing</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/calling-transactions-with-pre-filled-screen-in-background-processing/m-p/5795978#M1310826</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;We are currently running the two standard SAP programs RVV50R10C and SDV03V02 in background mode with static variants. A new requirement has come up whereby we need to run these programs with changing selection criterions, i.e. depending on whether a certain material has had a movement during the day.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are currently looking at the following options, all of which must be executeable in background mode:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Create a Z-program which identifies the materials for which RVV50R10C and SDV03V02 should process, and then at the end of the Z-program save variants containing the materials for each of the two standard programs. The standard programs will be scheduled as step #2 and #3 in the same batch job by using the variant which has been overwritten by the Z-program. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) Create a Z-program which identifies the materials for which RVV50R10C and SDV03V02 should process, and then at the end of the Z-program call these programs by specifying the material numbers in addition to other relevant selection criterions by passing a batch input table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3) Copy the standard programs into Z-versions and enhance the selection criterias according to our needs. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Of the options above we would prefer not to use 3) since we rather use the standard programs due to SAP support etc. The preferred option would be 1). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone faced a similar requirement and have some ideas about standard SAP functions to save a variant and what issues we might face in option 1) and 2)?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jun 2009 09:16:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/calling-transactions-with-pre-filled-screen-in-background-processing/m-p/5795978#M1310826</guid>
      <dc:creator>geir_kronkvist1</dc:creator>
      <dc:date>2009-06-19T09:16:06Z</dc:date>
    </item>
    <item>
      <title>Re: Calling transactions with pre-filled screen in background processing</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/calling-transactions-with-pre-filled-screen-in-background-processing/m-p/5795979#M1310827</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Geir,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2nd option is good. Create a Z program to identify the material numbers which you want to process &amp;amp; then in the Z Program itself use SUBMIT statement to call the standard programs RVV50R10C and SDV03V02. Using SUBMIT statement you can populate the selection screen parameters for the calling programs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let us know if you need any additional details.&lt;/P&gt;&lt;P&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;Best regards,&lt;/P&gt;&lt;P&gt;Prashant&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jun 2009 09:22:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/calling-transactions-with-pre-filled-screen-in-background-processing/m-p/5795979#M1310827</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-06-19T09:22:49Z</dc:date>
    </item>
    <item>
      <title>Re: Calling transactions with pre-filled screen in background processing</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/calling-transactions-with-pre-filled-screen-in-background-processing/m-p/5795980#M1310828</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can use the function module RS_CREATE_VARIANT for creation of variant..and then pass the varaint name when calling the second program...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jun 2009 09:24:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/calling-transactions-with-pre-filled-screen-in-background-processing/m-p/5795980#M1310828</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-06-19T09:24:42Z</dc:date>
    </item>
    <item>
      <title>Re: Calling transactions with pre-filled screen in background processing</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/calling-transactions-with-pre-filled-screen-in-background-processing/m-p/5795981#M1310829</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks a lot for the replies! We will try both options and evaluate which gives us the better result.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jun 2009 09:32:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/calling-transactions-with-pre-filled-screen-in-background-processing/m-p/5795981#M1310829</guid>
      <dc:creator>geir_kronkvist1</dc:creator>
      <dc:date>2009-06-19T09:32:21Z</dc:date>
    </item>
    <item>
      <title>Re: Calling transactions with pre-filled screen in background processing</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/calling-transactions-with-pre-filled-screen-in-background-processing/m-p/5795982#M1310830</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Geir,&lt;/P&gt;&lt;P&gt;I know it's been a long time since your last message, but I have the same problem now..&lt;/P&gt;&lt;P&gt;Did you solved it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a report Z* that selects my order and then does a SUBMIT of rvv50r10c. If I execute the report in foreground mode it's ok but if I execute it in background mode, it doesn't create the delivery!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ilaria.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Mar 2011 11:28:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/calling-transactions-with-pre-filled-screen-in-background-processing/m-p/5795982#M1310830</guid>
      <dc:creator>alessandro_brunello</dc:creator>
      <dc:date>2011-03-02T11:28:57Z</dc:date>
    </item>
  </channel>
</rss>

