Setting Process Definition Options
Field | Description | Default Value |
---|---|---|
Default Output Format | The format of the output files when the extension can not be mapped | Text |
Default Log Format | The format of the log files when the extension can not be mapped | Text |
Overview Format | Formatting used in the overview diagrams. This allows you to distinguish processes based on parameter values, especially useful for duplicates of the SAP_AbapRun process definition. You cannot change the overview format of built-in process definitions. You may insert parameter values using the syntax ${parameters.<name>} , such as ${parameters.VARIANT} | |
Template | Template process definitions are used to create new process definitions, they cannot be submitted or part of a chain definition. | false |
Maintenance | Maintenance process definitions are low profile process definitions; processes of these are not to be displayed in the default filters. | false |
Top Level | Top level process definitions are listed in the submit wizard as processes you can submit. Process definitions that should only be submitted as part of a chain definition should not have this set to true | true |
Critical Process | Critical Process processes are shown in the scorecard under Critical Processes. | |
Reaction Process Type | CheckReaction Process Type processes can be called from a process server when a process server check fails. AnyReaction Definition Type processes can be called from a process server as well as other objects. Promote Further PusherReaction Definition Type processes can be called on System_Import_Archive processes to promote the attached CAR file to another systemPush AcceptorReaction Process Type processes can be called when an inbound CAR file arrives to validate it PusherReaction Process Type processes can be called by a Remote System when you promote objects to it | [None] |
Evaluate Runtime Parameters With User | The subject to use for evaluating runtime parameter expressions | process definition owner |
Format
Processes can potentially generate output files. These can be log files that are guaranteed to contain log records in standard format, text files containing freely formatted information or error messages, or more complex files such as PDF or HTML files. Which files can be generated is dependent on the type of process that is executed.
The system will set the Format of the files created by the process.
Reaction Process Type
Reaction processes are processes that can react to a particular type of event. Unlike process definitions and wait events, reaction process definitions have a set of parameters that are filled automatically by the caller; there is no need to write REL to fill the parameters. Reaction processes have the following parameters in common:
SourceObject
- Name of the object that called the reaction processSourceObjectUniqueId
- UniqueId of the object that called the reaction processSourceObjectType
- Object type that called the reaction processAddress
- destination/recipient addressData
- a free form expression
See Reaction Process Definitions for more information.
Runtime Parameter Evaluation
When runtime parameters are evaluated, a session is created as the owner for evaluation, by default. You can set this to the process definition owner in which case the process definition owner needs permissions to all objects used by the call in the expression you specified, not the process owner.
JobChain JobDefinition ProcessDefinition