
You can display technical attributes, display or create documents for a process chain, and specify how process chains behave when they are executed.
Using the menu command you can display or edit the following process chain attributes:
|
Process Chain > Attribute >... |
What you need to know |
|---|---|
|
Name ( |
You can change the name of a process chain. |
|
|
Display components act as the sort criterion in process chain maintenance. Assigning process chains to display components makes it easier to access the chain you want. You can use the process chain attributes to change the assignment of the current chain. You can also change the descriptions of display components or create new display components. To create a new display component, in the Assign Display Components window, choose the input help. In the Display Grouping dialog box that appears, assign a technical name and a description to the display component. You can also change the description of a display component using the input help. |
|
|
You can create and display documents for a process chain. More information: Documents |
|
|
Displays the technical attributes of the process chain:
|
|
Evaluation of Process Status |
If you set this flag and you have scheduled a successor process with errors or Always, the system classifies all the incorrect processes of the chain as successful (with regard to the overall status of the run). The flag is relevant for the use of metadata: Errors in processes in subchains can be evaluated as "unimportant" for the metachain run. The subchain is evaluated as successful, regardless of errors in such processes of the subchain. If the successor of the subchain is scheduled upon success in the metachain, the metachain run continues regardless of errors in the "unimportant" processes of the subchain. This flag does not apply to mailing or alerting; these functions are still triggered if there are incorrect processes with a successor processor scheduled with errors. |
|
Polling Flag |
This flag allows you to control how the main process behaves with distributed processes. With distributed processes, such as loading processes, a number of different work processes are involved in the relevant tasks. You use the polling flag to specify whether you want to keep the main process until the process itself has ended. Note
Selecting the flag - ensures a high level of certainty in the process flow and - provide external scheduling tools with the status of the distributed processes. However, the system resource consumption is increased, and an additional background process is required. |
|
Monitoring |
The flag in the Remove Chain from Automatic Monitoring? dialog box allows you to specify that you want to remove a process chain from automatic monitoring using CCMS. In the default setting, automatic process chain monitoring is activated by CCMS. For more information about the CCMS-context process chains, see section BW Monitor in CCMS. |
|
Alerting |
You use alert management to send alerts if errors occur during a process chain run. For more information, see Sending Alerts for Process Chains. |
|
Background Server |
Here you can specify the server or server group, where you want to schedule all the jobs in the chain. If you do not specify a server or server group, background management distributes the jobs across the available servers. |
|
Processing Client |
If you are using process chains in a client-dependent application, here you specify one exclusive client in which the chain can be used. Then the process chain can only be displayed, edited, scheduled, and executed in this client. If you do not set this attribute, you can display, edit, schedule, and execute the process chain in all clients. Process variants of the General Services category that are included in a process chain that has this attribute are also only displayed in the specified client. This attribute is transported. You can change it during the import by specifying an import client. In the target system, you have to create a destination for import post-processing in the client that is specified here (transaction RSTPRFC). After the import, the chain is activated and scheduled, if required, in this client. |
|
Execution User |
With the default setting, a BW background user executes the process chain. You can change the default setting so that you can see the user who executes the process chain and the processes. This information is shown in the job overview (transaction SM37). You can select the current dialog user, who schedules the process chain job, or specify a different user. The setting is transported. The BW background user has all the required authorizations to execute all BW process types. Other users have to assign themselves these authorizations so that authorization errors do not occur during processing. |
|
Job Priority |
You use this attribute to set the job priority for all the jobs in a process chain. |
|
Reset Previous Run |
If processes fail in the process chain run, it may be the case that the instances of these processes still exist in the data target. These instances can have a negative impact on the next process chain run. Using the Reset Previous Run function, you can remove and delete these failed processes from the data targets before the next process chain run, provided that this is supported by the process type. The function is supported, for example, by load processes (such as InfoPackages or data transfer processes). A dialog box opens. Choose Automatically Reset Errors in Previous Run. The process chain makes all failed processes clean their previously failed instances before a new process chain is started. |