Release Subworkflow for FI (FIPP, BSEG) 

Use

The workflow definition created is specially adapted for use as a subworkflow in the workflows FIPP_FRAME* and BSEG_FRAME*.

These workflows from the Financial Accounting area are distinguished by the fact that the actual approval procedures are implemented as subworkflows that are determined dynamically at runtime. The Workflow Wizard helps to provide these subworkflows.

In a hierarchical approval workflow, the type of object to be approved, the approval task, the levels and the specific agents for each level must be specified at definition time.

The approval procedure is otherwise such that every agent can reject the object to be approved with the consequence that the agents following know nothing of the approval procedure started, because it has already broken down at a lower level in the hierarchy.

Features

In the first step of every release procedure, the release status (element Level) is first initialized at one.

This initialization is followed by the approval steps nested in each other, all of which have at least two possible results (approved or rejected). The approval method of the object to be approved is executed and, optionally, its default method as a secondary method. This execution takes place asynchronously in a new session without influencing the execution of the workflow.

In the event of approval, the approval status is increased by one and the next approval step initiated.

In the event of rejection, nothing happens and the workflow goes immediately to its evaluation part. If the approval procedure is terminated in this way, the approval status is always less than the number of levels.

Enhancements to the workflow definition

The workflow definition created by the Workflow Wizard can only be used practically as part of a superordinate workflow definition. Steps still need to be added to it in which the object that is to be approved is created or established.

A reference to this object must be stored in the container element ApprovalObject in the workflow container.

Activities

A hierarchical approval procedure created by a wizard requires a few additional elements in the workflow container:

Data type

Short description
(name)

Explanation

Object reference

Approval object (ApprovalObject)

Reference to the object to be approved.

ABAP Dictionary reference

Release status (Level)

Status of the approval procedure.

The status is initialized at one at the start, and increased by one with each approval. If the status is equal to zero on evaluation, the object was approved. If it is greater than zero, the object was rejected.

 

Current agent (CurrentAgent)

The user who processes the work item is saved in this container element.

 

List of excluded agents (Activity_Excluded_Agents)

The list of agents contains all users, positons, jobs, organizational units and work centers which are involved in the approval process.

This list is used to exclude agents who have already granted an approval from approving the same object again.

You can also include the workflow initiator in this list. Thus, you prevent applicants from being able to approve their own requests.

 

Release result (Released)

This field contains the result of the approval procedure after the workflow:

X for approved
' ' for not approved