Workflow: Automatic Further Processing of a Purchase Requisition

Use

This workflow is started if a high-priority purchase requisition (PReq) is created or changed. If the PReq is subject to a release procedure, the workflow is not triggered until the PReq is released.

In the context of this workflow, a PReq is classed as “high priority” if at least one PReq item is defined (in Customizing for prioritized materials planning) for automatic subsequent processing. The determining factor is the requirement priority of the purchase requisition item.

If a suitable entry has been made in Customizing, the PReq is processed further in the background in accordance with the specifications defined in Customizing. The system creates a log that specifies what subsequent processing has been carried out and whether any errors occurred. Depending on the Customizing settings, the system also generates work items for the log display (always or in the event of errors only), or does not generate any notifications.

Work item recipients are derived from the MRP controllers in the material master for the requested materials and are determined on the basis of a responsibility rule (11200019).

The workflow is closed when the work item is expressly completed for the log display.

Features

Technical Data

Workflow Template	WS11200056
Abbr.	MM002PReqAut
Name	PReq Workflow: Automatic Further Procg
Triggering Event	BUS1230: HighPrioItemCreated_02
Terminating Event	-

Workflow Standard Task	TS11200133
Abbr.	MM002GetUser
Name	Get User for PRPL Log
BOR Object Type	BUS1230
Method	PRIOPLANAUTOBACKGR
Type	Synchronous object method WITHOUT dialog (background processing)
Confirm End of Processing	No
Agent	Workflow batch user
Terminating Event	-

Workflow Standard Task	TS11200134
Abbr.	MM002ShowLog
Name	Display Log for Autom. Prior. Matls Plng
BOR Object Type	BUS1230
Method	DISPLAYPRIOPLANLOG
Type	Synchronous object method with dialog
Confirm End of Processing	Yes
Agent (Agent Type: Expression)	&PRPLUSERDISPOTAB[&_WF_PARFOREACH_INDEX&].ACTOR& (All users who are determined as MRP controllers for the PReq to be processed, on the basis of the responsibility rule 11200019)
Terminating Event	-

Activities

Customizing: Activate Event Type Linkage

Call up the event type linkage (standard transaction PFWS) and activate the following events:

Events

Object Category	Object Type	Event	Receiver Type	Type Linkage
BOR Object Type	BUS1230	HIGHPRIOITEMCREATED_02	WS11200056	X

Customizing: Assign Agent

Agents are assigned in transaction PFAC, rule 11200019.

This rule is a responsibility rule with the input parameters MRP Controller and Plant .

Accordingly, responsibilities can be created with different MRP controller/plant combinations and the required priority. The values for the MRP controller must match those of the MRP controller stored in the material master for the materials that are procured by means of a purchase requisition.

Enter the receiving plant of the purchase requisition item as the plant.

You have to assign agents for each responsibility created. You can insert positions, persons, and/or users. We recommend you avoid creating overlaps. For example, if you assign a user for a responsibility both directly and through a position, the user receives two identical work items.

To ensure that in each case at least one user receives a work item when a high-priority PReq is created/changed/released, create the following generic responsibility with the lowest priority 01:

Responsibilities

Name	of	to
MRP Controller	*	*
Plant	*	*

If the program logic cannot determine a user as the work item recipient for the MRP controller/plant combination(s) specified by the PReq, use the agent assignment function to insert for this responsibility the user who is to receive a notification.

TS11200134 MM002ShowLog Display Log for Autom. Prior. Matls Plng

The agent assignment is carried out directly for the standard task. Examples of agent types include organizational unit, position, and user. Classify this task as a general task.

General tasks do not have to be assigned agents, since all users are allowed to perform them. The agent is determined on the basis of the context of the workflow, using the responsibility rule mentioned above.

Additional Technical Information About the Workflow

The workflow is started when event HighPrioItemCreated_02 is triggered explicitly in function module /ISDFPS/WF_PRPL_REQ_POSTED (in accordance with the Customizing settings for prioritized materials planning).

The above function module is called up in method IF_EX_ME_REQ_POSTED~POSTED of the Business Add-In implementation /ISDFPS/REQ_POSTED when purchase requisitions are created/changed/released.