Workflow for Cost Center Lock on Planned Costs
Use
The person responsible is informed of any organizational changes (structural changes to the organizational structure or operational structure) that require the removal of the cost center lock against plan postings.
If another change is made (while a workflow is running already), the workflow is terminated and restarted.
When the workflow is completed, the initiator is informed of the approval or rejection by means of a work item.
If the force element is deleted, the workflow is terminated.
Features
Workflow Template |
WS11200031 |
ID |
OF118ACCCOLP |
Name |
Approval Accounting CO Plan Costs |
Triggering event |
BUS1221.ACC_GEN_CO_LP |
Closing event |
BUS1221.ACC_GEN_CO_LP |
Check function module |
/ISDFPS/FORCE_WF_CHECK_ACC_LP |
Workflow Standard Task |
TS11200052 |
ID |
OF118ACCAPP |
Name |
Approve Accounting CO LP - Plan Posting |
BOR object type |
BUS1221 |
Method |
MAINTAINACCOUNTINGCO_LP |
Type |
Synchronous object method with dialog |
Confirm end of processing |
Yes |
Agent (agent type: rule) |
AC 11200001 Input parameters
|
Terminating event |
- |
Workflow Standard Task |
TS11200057 |
ID |
OF118ACCDIS |
Name |
Display Accounting LP |
BOR object type |
BUS1221 |
Method |
DISPLAYACCOUNTING |
Type |
Synchronous object method with dialog |
Confirm end of processing |
Yes |
Agent (agent type: rule) |
&_WF_INITIATOR& |
Terminating event |
- |
Activities
Customizing: Activate Event Type Linkage
Object Type |
Event |
Event Receiver |
Check Function Module |
Type Linkage |
|---|---|---|---|---|
BUS1221 |
ACC_GEN_CO_LP |
WS11200031 |
/ISDFPS/FORCE_WF_CHECK_ACC_LP |
X |
Customizing: Assign Agents
For general information about agent assignment, see Agent Determination .
TS11200052 OF118ACCAPP Approval Accounting CO LP - Plan Posting
Agent assignment is carried out directly for the standard task. Examples of agent types include organizational unit, position, and user. This task is to be classified as a general task. General tasks do not have to be assigned an agent, since all users are allowed to perform them. The agent is determined on the basis of the workflow context.
TS11200039 OFTSACCCO Rule for Accounting CO - Approval
You can assign any number of positions here. To do so, create a separate force element, assign it the relevant personnel categories, and link it to this workflow standard task.
User determination at runtime: At least one of these positions should appear in the relevant force element (for which the workflow is started) under the personnel categories. This forms the intersection.
TS11200040 OFCLEARACC OF: Clearing Task for Accounting
Agent assignment by means of positions is made in this case in the
Structures Workbench
by means of personnel categories.TS11200057 OF116ACCDIS Display Accounting LP
Agent assignment is carried out directly for the standard task. Examples of agent types include organizational unit, position, and user. This task is to be classified as a general task. General tasks do not have to be assigned an agent, since all users are allowed to perform them. The agent is determined on the basis of the workflow context.
Additional Technical Information About the Workflow
The workflow is started indirectly in the
Structures Workbench
when data is saved. The system then checks the follow-up actions defined in Customizing for changing the status of the force element from
Requested
to
Approved
.
Function module /ISDFPS/STACHG_AC_NOTIFY_CC_LP is run and the relevant event is triggered.
The system then uses the check function module to check the type linkage table (event ACC_GEN_CO_LP).
This check function module is shipped empty.
Note
If the force element concerned is deleted, the workflow is terminated (event BUS1221.DELETE).
In the workflow, the version-dependent basic data defines that the workflow is terminated at the same time as the event is triggered. This means that the current workflow is terminated and a new one is started.