Workflow Customizing

In document Store Business Offline EPOS en CUST V147[1] (Page 139-146)

The workflow tool assigns open tasks (work items) to employees and sends them to their SAPoffice inbox. You can use transaction PFTC to display the workflow objects, such as standard tasks or workflow templates.

The employee responsible is determined from the organizational plan in the R/3 System. An area of responsibility can be defined for a job a position or a work center. If a work item falls in an area of responsibility, it is forwarded to the employees responsible. More than one employee can be responsible for one work item.

Work items can be executed individually or in groups and can be forwarded if the task is the responsibility of another employee/area. All the steps carried out when processing a work item are recorded in a log and can be analyzed statistically (processing time, number of work items per employee, and so on).

In this activity, you make all the settings required to adjust the standard tasks and workflow templates shipped by SAP. Only carry out this activity if you want to use the scenarios supported by SAP.

Possible agents must be specified for each standard task in order to clearly define the organizational responsibility for processing.

Workflow templates can only be started online by their possible agents. If a scenario

requires that the particular workflow template be started online, this workflow template must be assigned to its possible agents.

A standard task or workflow template can be started as a reaction to events created by the

PRECONDITIONS

Check that all the basic Customizing settings for the application component WFM (workflow management) have been made.

Activities

1. Carry out the activity and, from the displayed component hierarchy, select the application component for which you can/want to

o Assign possible agents to standard tasks

o Activate triggering events for standard tasks and workflow templates (poss.)

2. Expand the branch “Assign agents to tasks”.

3. Select a standard task for processing.

Assign the task to its possible agents. This assignment determines the total number of persons who are allowed to process this task.

Specify all the relevant agents:

Alternatively, you can classify a standard task as a “general task”.

4. Expand the branch “Assign agents to tasks”.

5. Select a standard task or workflow template for processing.

Only some of the standard tasks and workflow templates have triggering events. This is indicated by the folder icon in front of the task name. If you double-click this icon, the event entered as a triggering event is displayed.

6. Activate the linkage.

Activating event/receiver linkages determines which of the linkages in question you actually want to use.

You will usually assign a standard task to an organizational unit, job, or position so if personnel changes occur in the organizational plan, no changes are required in the workflow components.

Further Notes

For further information, refer to Customizing for the application component in question.

This Customizing activity gives you the opportunity to set up all the standard tasks and workflow templates that you want to use in the implementation phase. It is also possible, however, to execute the steps required from the task definitions at a later date.

The settings cannot be transported and must, therefore, not be integrated in BC Sets.

The application transaction is PFTC. To maintain and display the assignment, choose  Additional Data  Agent Assignment.

Path:

 Tools  Development  Workflow  Definition Tools  Tasks/Task Groups  Create For more detailed workflow information, take a look at the article discontinuation scenario.

Merchandise-Driven Master Data_EN_DOCU_V147.doc

3.10.1 Store Order, New WF

WF template: WS 65400051

The assignment of the workflow template is fixed in the program coding. So assignment is not necessary. In contrast to standard tasks, using new workflows to process exceptions covers a whole series of possible errors by assigning a workflow template. This means that rather than assigning several tasks you simply have to assign the workflow template in the control of the store order. You execute this assignment only if you want to use your own workflow template.

The assignment of agents remains the same as it is in the old workflow processing. In addition it is possible now to assign an agent to the hole task group.

PRECONDITIONS:

All the basic workflow Customizing settings have been made.

The store’s EDI partner profile has been maintained for message type WGSREQ.

The POS inbound profile has been created and the control settings made for the store order.

PATH: (SPRO)

IMG  Sales and Distribution  POS Interface  Workflow  Store Order PROCEDURE:

1. Call up the Customizing activity mentioned above.

2. Carry out the first option “Assign agents to tasks”.

3. Select the entry for your task (in this case 65400070) and choose Agent Assignment  Create.

4. In the dialog box that appears, choose the organizational unit that is to be notified for exception processing. Here, select “USER” and confirm with [ENTER].

5. The system now asks you to specify the appropriate organizational unit. Enter the system user name for the user that is to be notified (see point 4).

6. When you confirm your selection, the agent/organizational unit is assigned to the task.

Now press BUTTON [REFRESH INDEX].

7. Finally, call up your SAPoffice inbox and choose Office  Workplace  Settings  Workflow Settings  Refresh Organizational Environment.

PARAMETER SETTINGS:

BACKGROUND:

First assign an agent to the standard task who is to be notified when an exception occurs in the POS interface inbound. Then refresh the organizational environment so that this assignment takes immediate effect without having to log on again.

REMARKS:

3.10.2 Store Order, Old WF

WF tasks: 900060 Post sales order 900071 Error log

900073 POST PURCHASE ORDER 900075 Create purchase requisition 900079 Post delivery

Task 900073 ‘Post purchase order’ is set up as an example.

PRECONDITIONS:

All the basic workflow Customizing settings have been made.

The store’s EDI partner profile has been maintained for message type WGSREQ.

The POS inbound profile has been created and the control settings are made for the store order.

PATH: (SPRO)

IMG  Sales and Distribution  POS Interface  Workflow  Store Order PROCEDURE:

Process analogically as described in 3.10.1 PARAMETER SETTINGS:

BACKGROUND:

First assign an agent to the standard task who is to be notified when an exception occurs in the POS interface inbound. Then refresh the organizational environment so that this assignment takes immediate effect without having to log on again.

REMARKS:

For more detailed workflow information, take a look at the article discontinuation scenario.

3.10.3 Store Goods Receipt (New Workflow, as of 4.6A)

Task: TS 20000706 Store goods receipt: Processing step PRECONDITIONS:

All the basic workflow Customizing settings have been made.

The POS inbound profile has been created.

The store’s EDI partner profile has been maintained for message type WPDWBW.

The new workflow for exception processing has been chosen in the POS inbound profile.

PATH: (SPRO)

IMG  Sales and Distribution  POS Interface  Workflow  Master Data PROCEDURE:

Process analogically as described in 3.10.1 PARAMETER SETTINGS:

BACKGROUND:

REMARKS:

3.10.4 Store Goods Receipt (Old Workflow)

WF tasks:

TS 00900059 Store GR for Purchase order TS 00900061 Store GR for anonym. PO

TS 00900063 Store GR with autom. PO creation TS 00900065 Store GR with diff. quantities TS 00900067 Store GR for delivery TS 00900069 Store GR for shipping element

The workflow for task 900061 ‘Store GR for anonym. PO’ is set here as an example.

PRECONDITIONS:

All the basic workflow Customizing settings have been made.

PATH: (SPRO)

IMG  Sales and Distribution  POS Interface  Workflow  Store Goods Receipt (Old Workflow, Release Independent)

PROCEDURE:

Process analogically as described in 3.10.1 PARAMETER SETTINGS:

BACKGROUND:

First assign an agent to the standard task who is to be notified when an exception occurs in the POS interface inbound. Then refresh the organizational environment so that this assignment takes immediate effect without having to log on again.

REMARKS:

3.10.5 Incoming Master Data

Tasks: 900048 POS inbound article master data 900049 POS inbound EAN references 900051 Error in WP_EAN

900050 Error in WP_PLU Task 900049 is used here as an example.

PRECONDITIONS:

All the basic workflow Customizing settings have been made.

Message type WP_EAN/WP_PLU has been set up for the store.

PATH: (SPRO)

IMG  Sales and Distribution  POS Interface  Workflow  Master Data PROCEDURE:

Process analogically as described in 3.10.1 PARAMETER SETTINGS:

BACKGROUND:

First assign an agent to the standard task who is to be notified when an exception occurs in the POS interface inbound. Then refresh the organizational environment so that this assignment takes immediate effect without having to log on again.

REMARKS:

In document Store Business Offline EPOS en CUST V147[1] (Page 139-146)