Show TOC

 Plant Change for Reorganization

Use

The workflow is triggered if, in the event of reorganization, the new higher-level force element is assigned to a different plant than the previous force element. Separate workflows are started for stocks and provisions.

If the system is changed at the same time, the person responsible is informed by means of a work item and changes the storage locations.

If the system is not changed at the same time, the person responsible must first decide whether or not to change the plant (user decision).

  • If the person responsible decides to change the plant, the next step is to change the storage locations.

  • If the person responsible decides not to change the plant, the storage locations are deleted in the next background step (table /ISDFPS/ORG_UM_W).

If a plant is to be changed again during the current workflow, the workflow is terminated and restarted (due to a parallel step).

If the force element concerned is deleted, the workflow is terminated.

For more information, see Support for Cross-Plant Reorganization .

Features

Technical Data

Workflow Template

WS11200034

ID

OF121WRKUMG

Name

OF: Plant Change for Reorganization

Triggering event

BUS1221.WERKS_CHANGE

Terminating event

None

Check function module

/ISDFPS/FORCE_WF_CHECK_WERK_CH

Workflow Standard Task

TS11200089

ID

OF121CHNLGO2

Name

Plant: Change Storage Locations

BOR object type

BUS1221

Method

CHANGEWERKSLGO

Type

Synchronous object method with dialog

Confirm end of processing

No

Agent (agent type: rule)

AC 11200006

Input parameters

  • Responsibility Rule: AC 11200007

  • Clearing Task: TS11200090

Terminating event

-

Workflow Standard Task

TS11200086

ID

OF121DECIS01

Name

Plant Change Decision

BOR object type

DECISION

Method

PROCESS

Type

User decision

Confirm end of processing

Yes

Agent (agent type: rule)

AC 11200006

Input parameters

  • Responsibility Rule: AC 11200007

  • Clearing Task: TS11200090

Terminating event

-

Workflow Standard Task

TS11200087

ID

OF121CHNLGO

Name

Plant: Change Storage Locations

BOR object type

BUS1221

Method

CHANGEWERKSLGO

Type

Synchronous object method with dialog

Confirm end of processing

No

Agent (agent type: rule)

&ACT_AGENT& (current agent of the previous step)

Terminating event

-

Workflow Standard Task

TS11200088

ID

OF121DELLGO

Name

Plant: Delete Storage Locations

BOR object type

BUS1221

Method

DELETEWERKSLGO

Type

Synchronous object method WITHOUT dialog (background processing)

Confirm end of processing

No

Agent (agent type: rule)

Workflow batch user

Terminating event

-

Activities

Customizing: Activate Event Type Linkage

Events

Object Type

Event

Event Receiver

Check Function Module

Type Linkage

BUS1221

WERKS_CHANGE

WS11200034

/ISDFPS/FORCE_WF_CHECK_WERK_CH

X
Customizing: Assign Agents

For general information about agent determination, see Agent Determination .

  • TS11200089 OF121CHNLGO2 Plant: Change Storage Locations

    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.

  • AC11200007 OF1950WRK Responsibility Plant Change Re. HRP1950

    You can define any responsibilities you wish. You define a responsibility to specify for which container element values (in this case, values for table HRP1950) processing is to be carried out by the same users. You assign Organizational Management objects (positions, persons, users) to a responsibility.

  • TS11200086 OF121DECIS01 Plant Change Decision

    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.

  • TS11200087 OF121CHNLGO Plant: Change Storage Locations

    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.

  • TS11200088 OF121DELLGO Plant: Delete Storage Locations

    An agent does not have to be assigned in this case, since this is a background step.

  • TS11200090 OFCLEARWRK OF: Clearing Task for Plant Reorganizat.

    Agent assignment by means of positions is made in this case in the Structures Workbench by means of personnel categories.

Additional Technical Information About the Workflow

The workflow is started indirectly when data is saved in the Structures Workbench . The relevant event is triggered by function module /ISDFPS/STACHG_MM_CHECK_WERK_C.

After the event has been triggered, the system uses the check function module to check the type linkage table (event WERKS_CHANGE).

This check function module enriches the event container with additional data:

  • FATHER_NEW_STEXT (short text from the new force element to be assigned)

  • FATHER_OLD_STEXT (short text from the old force element to be assigned)

  • UM_TYP_STEXT(value range for stock or provisions)

    Note Note

    The events BUS1221.DELETE and BUS1221.WERKS_CHANGE result in the workflow being terminated due to parallel steps.

    End of the note.