WORK FLOW SCENARIOS IN SD 5

Standard Tasks (SD-SLS-OA)

Standard tasks are single-step tasks supplied by SAP that describe basic business activities.

The following standard tasks are delivered:
TS20000140
TS20000141
TS20000409
TS20000233

Standard task: TS20000140

Identification code: SD_KK_CHANGE

Description: Change customer contract in the background
Referenced method, attributes Object type: BUS2034 (master contract)
Method: CHANGEINBACKGROUND
Attributes: Background processing
In this task, the system tries to change the lower level contracts, according to the changes in the group contract, in the background. If a temporary error occurs (for example, the document is locked), the system calls up task TS20000409. If this task cannot be implemented because of an application error, the system calls up task TS20000141.

Standard task: TS20000141
Identification code: SD_KK_EDIT
Description: Change customer contract online
Referenced method, attributes
Object type: BUS2034 (master contract)
Method: EDIT (online method)
Attributes: None
If the system could not change the lower level contract in background processing, the person who changed the master contract in task TS20000141 receives a work item in the inbox and can then make the change online.

Maintain Processor Assignment We recommend that you classify TS20000141 as a general task so that the person who changed the master contract is also permitted to process the lower level contracts. If any errors occur, the person who changed the master contract receives a work item in their inbox.

Standard task: TS20000409

Standard Tasks (SD-SLS-OA)
30 April 2001
Identification code: SD_KK_EDIT
Description: Change customer contract in the background (inbox)
Referenced method, attributes
Object type: BUS2034 (master contract)
Method: CHANGEINBACKGROUND
Attributes: Background processing
If a temporary error occurs (for example, the document is blocked), the system will try to change the master contract again in the background at a later point. You can define the time span at which this occurs in Customizing. If the system cannot make the changes, the person who changed the master contract receives a work item in their integrated inbox.

Starting the work item causes the system to try and change the lower level contract in the background. The work item stays in the employee’s inbox until the changes could be made or an application error occurs.
If an application error occurs, task TS200000141 is called up and the person who changed the document receives another work item in their integrated inbox that can only be processed online.

Standard task: TS20000233
Identification code: SD_GK_DQ
Description: Unlock master contract
Referenced method, attributes
Object type: BUS2095 (master contract)
Method: DEQUEUE (synchronous method)
Attributes: Background processing
Once workflow has started, the system automatically sets the ENQUEUE_GRP indicator (block master contract until all lower level contracts have been updated) in table VBAK (sales document header data). Once the whole workflow has finished, the system deselects this indicator using task TS20000233.

Preparation and Customizing (SD-SLS-OA)

Application-Specific Customizing

You need to make the following settings in Customizing for Sales and Distribution:

Update lower level contracts Select the Update lower level contract field for sales document type group contract, so that the workflow copies all the changes in the master contract into the assigned lower level contracts, according to the referencing procedure.

Make this setting by going to Customizing for Sales and Distribution and choosing Sales __Sales Documents __Sales Document Header _ Define sales document types for the
sales document type group contract.

Processor assignment

Assign a processor by going to Customizing for Sales and Distribution and choosing
Sales __Sales Documents __Contracts _ Master Contract __Activate Workflow for
Master Contracts.

Event linkage

You must activate event linkage for object types BUS2095 and BUS2034. You can do
this by going to Customizing for Sales and Distribution and choosing Sales Documents
__Contracts _ Master Contract _ _Activate Workflow for Master Contracts. For more
information on this Customizing activity, see the online Implementation Guide.
Customizing for SAP Business Workflow.


Note that the changes in the lower level contracts are made according to the
referencing procedure for the master contract that was agreed on in Customizing.
See the relevant chapter in the Implementation Guideline for master contracts.
Organizational Plan You can also assign the people who can change the master contract to other organizational units.

Organizational units are areas within a company that belong together for organizational and business purposes, such as a department. However, they are not normally required for the workflow scenario. Only those employees who are authorized to change master contracts and who have changed a master contract, receive a work item in their inbox if an application error occurs, for example, if the workflow is incorrectly implemented. The work item can be forwarded to all the people who are listed in the employee assignment but the employees who process it must also be authorized to change the contracts.


You can set up the organizational plan in Customizing for Basis. In the Implementation Guide, choose Basis Components _ Business Management _ SAP Business Workflow _ Edit organizational plan.

Change customer contract in the background: Set time span
If a temporary error occurs when you change the contract (for example, the lower-level contract is blocked), the system will try to change the master contract again in the background at a later point. You can define the time span at which this occurs in Customizing.

You can define the time span in Customizing for Workflows (Basis Components _ SAP Business Workflow _ Basic Settings (System, SAP Business Workflow) _ Activate automatic monitoring of incorrect work items).


Using and Linking to the Application Functions (SDSLS- OA)

Prerequisites

You have created the link to the workflow (see application-specific Customizing), created a master contract, and assigned the lower level contracts to the master contract.

Process Flow

1. Change a field in the master contract for which there is a rule in the referencing
procedure (Customizing for master contracts).
2. This triggers the changed event for business object BUS2094 (master contracts) and
initiates the workflow template WS20000049.
3. The workflow template WS2000048 is called up for each lower level contract related to the changed master contract.
4. The system implements the standard task TS20000140 (change in background) for all
the lower level contracts:

The system calls up standard task TS20000141 (implement change online) for all
lower level contracts that cannot be changed in the background (change failed event
for object type BUS2094).
The person who changed the master contract receives a work item in their inbox.
The employee can change the lower level contract directly from the inbox using the
information displayed in another window about the changes made in the master
contract. The whole workflow finishes if all the lower level contracts are changed.

The system calls up task TS20000409 (background change of customer contract) for
all lower level contracts that contain a temporary error (blocked by processing).

After a certain time span, which has been defined in Customizing for workflows, the
system tries to change the lower level contracts in the background again. The
workflow is complete once all the lower level contracts have been changed. If the
system cannot change the contract because it is still blocked, for example, the
person who changed the master contract receives a work item in their integrated
inbox.

When they execute the work item, the system changes the lower level
contract in the background. The work item remains in the inbox until the lower level
contract has been changed. If an application error occurs when the system changes
the contract in the background, it calls up task TS20000141. The employee receives
a work item in their integrated inbox that can only be processed online.

Once all the workflows are finished for the lower level contracts, the whole workflow ends.

In order to guarantee consistent data retention, all the lower level contracts that are to be changed are blocked until the relevant workflow has finished for the lower level contract.