Understanding Changing Processing Options
You can change the processing option values for an existing batch version to meet your business needs. You can change the processing option values at runtime or from the Row menu on the Work With Batch Versions-Available Versions form. Use the Row menu when you want to define default values to execute blindly. For example, you can change the processing option values for a batch version of an address book report to select a search type of C for customers. If you also select to execute the processing options blindly, the processing option template does not appear at runtime. Therefore, the user does not have the opportunity to change the search type value; only customer records display in the report.
Not all batch versions have processing options associated with them; for example, a list of addresses might not require special prompting. If processing options do not exist, or if you have been secured from changing processing options, a message box appears when selecting Processing Options from the Row menu on the Work With Batch Versions-Available Versions form. Otherwise, the Processing Options form appears for the application.
Processing option values are stored in blob binary format in the Versions List (F983051) table for each batch version run. Unlike other changes to versions, changes to processing option values do not require you to check in or check out the version if the changes are made using the row exit in Batch Versions and not made at runtime. Anyone who uses that version after you make the change is affected by the new processing option values. You can define different processing options values for individual versions and set the processing options to process as a blind execution.