topic Re: SM36 - Job with variable fields in Application Development and Automation Discussions

SM36 - Job with variable fields

Former Member — Wed, 09 Sep 2009 20:13:38 GMT

Hi Gurus!

I'd like to know if its possible to schedule a job with a dynamic variable field. For example: I have to schedule a job monthly for a transaction and the field PERIOD should change according to the current period, automatically.

Is it possible?

Thanks!

rnishi

Re: SM36 - Job with variable fields

Former Member — Wed, 09 Sep 2009 20:22:46 GMT

Hi,

Yes you can when you would be creating a step in your job you would be using a variant now why dont you create a variant with dynamic values for the field that you want have a look at the below steps and you should be able to set a dynamic variant:


1. Enter the values in the selection screen
2. Save the variant using the SAVE button
3. In the next screen for the date variable select the 'Selection variable' checkbox (L) and click on the button 'Selection variable' in the toolbar.
4. Now you will see this variable in the next screen with 3 types of buttons. Click on the middle button (i.e. D - Dynamic date calculation).
5. Click on the down arrow button and select the option 'Current Date'.
6. Save the variant.

Regards,

Himanshu

Re: SM36 - Job with variable fields

Former Member — Fri, 18 Sep 2009 12:42:41 GMT

Hi, thanks for your help! But im using a field that does not support that. This configuration is not available...

Do you hav any other idea???

Thanks in advance!

rnishi

Re: SM36 - Job with variable fields

Former Member — Fri, 18 Sep 2009 13:03:39 GMT

hello.

this is how a demo goes.

parameter: p1 type sy-datum.

now in selection screen. click save. its take you to variant..

-click copy screen assignments

-then in objects for selection screen:-

===press F4 on selection variable,select the date one(D)

====name of variable, click F4 and choose current date,

from this in the report you can choose the period.

Re: SM36 - Job with variable fields

Former Member — Fri, 11 Dec 2009 12:02:32 GMT

We've solved this demand creating a program. The variant for this transaction should be the last open period in CO module (OKP1), so it was impossible to create by standard procedures....

Thanks for your help!

rnishi