WORK FLOW SCENARIOS IN SD 7

Standard Role AC2000045: Agent for Internet Sales

Order (SD-SLS)

Use

This standard role determines positions or organizational units that are assigned to a sales office or sales area transferred in a role container.
If this container includes a reference to a sales office (parameter Sales office), the employees responsible for this sales office are determined. If this role resolution leads to no employees being determined, or the container does not contain a sales office (because one is no defined for the online store), the employees responsible for the sales area (parameter SalesAndDistribArea)
are selected.


The structure and assignment of SAP organizational object types Sales office and Sales area to object types of organizational management in Customizing is described later in this document.


Workflow Template: Correcting errors in Internet sales

orders (SD-SLS)

Use

If an error occurs in a sales order or quotation in the IAC “Online Store”, the system starts a workflow based on the template SD_KI_WF.
Workflow template: 20000169, abbreviation: SD_KI_WF, name: Correct errors in Internet sales order Triggering events of the workflow template
The event erroInternetCreate (error creating in the Internet) for object type BUS2032 (sales order) is the triggering event for the workflow template.

This “link” between the event and the workflow template to be triggered is
deactivated in the standard system and must first be activated in Customizing for
SAP Business Workflow, before the workflow template is actually triggered.

Preparation and Customizing (SD-SLS)

Workflow container and binding

As the workflow can only be started if a sales order or quotation is not created because of an error, no object reference to a sales order is available. Event parameter _Evt_Object in the container of the triggering event is initially empty.
The information exists as event parameters in the container of the triggering event and must be transferred to the workflow container via a binding.

As a result, the following binding definition between the triggering event and the
workflow container is defined in the standard system:

Workflow container Event parameter container
MessageType MessageType
MessageID MessageID
MessageNumber MessageNumber
MessageText MessageText
MessageDetail MessageDetail
OnlineStore OnlineStore
OstoreDescription OstoreDescription
SalesDocumentType SalesDocumentType
RequestedDelivDate RequestedDelivDate
PricingDate PricingDate
SalesOffice SalesOffice

SalesAndDistribArea SalesAndDistribArea
OrderingParty OrderingParty
MaterialList MaterialList
SalesOrderSimulate SalesOrderSimulate
PaymentMethod PaymentMethod
PaymentCardType PaymentCardType
CardNumber CardNumber
ExpirationDate ExpirationDate
These elements have been created in addition to the elements available in the standard system.

Preparation and Customizing (SD-SLS)

Use

In addition to the general Customizing procedures that must be performed to make sure workflow system functions properly, several other customizing steps are necessary for this workflow template.

Activities

Processing the organizational structure
Various users are able to check and correct errors in Internet sales orders. These users must be entered in Customizing for SAP Business Workflow. Only those users responsible for handling incorrect Internet sales orders in the sales office or sales areas are to be selected.

First assign a sales order to the online store by choosing Logistics - General _ Logistics Basic Data: Product Catalog _ Internet-application components.
In the container of the triggering event, the sales office and sales area are copied to parameters SalesOffice and SalesAndDistribArea. From here, they are transferred via a binding to the workflow container, and from there to the role container for standard role 20000045 (agent for Internet sales orders), which carries out role resolution in workflow. If this container includes a reference to a sales office, the employees responsible for this sales office are determined. If this role resolution leads to no employees being determined, or the container does not contain a
sales office (because one is not defined for the online store), employees transferred for the sales area are selected.

Enter your organizational plan by choosing Customizing activity Basis Components _ Business Management _ SAP Business Workflow _ Edit organizational plan.
Execute Customizing activity Basis Components _ Business Management _ SAP Business
Workflow _ Basic Settings _ Maintain assignments for SAP organizational object types, and enter the SAP organizational object types Sales office (object type TVBUR) and Sales area (object type BUS0006003), if necessary. List all organizational management object types that are used to correct errors in Internet store orders, such as positions and/or organizational units.

You then use transaction PFOM to assign the appropriate sales office (object type TBVUR) or sales area (object type BUS0006003) to the organizational units and/or positions that represent the sales office or sales area responsible.

Performing task-specific Customizing

Classify the general tasks.

You assign tasks in Sales and Distribution as follows:
1. Execute the Customizing activity (Basis _ Business Management _ SAP Business
Workflow _ Perform task-specific Customizing.
2. Here, under Sales and Distribution _ Sales, choose the activity Assign tasks to agent.
3. Classify the standard tasks TS20000357 (error in quotation), TS20000347 (error in order on account), TS20000346 (error in credit card orders) and TS20000372 (error in cashon- delivery order) as general tasks.
Activating event-receiver linkage
Event ErrorInternetCreate (error creating in Internet) for object type BUS2032 (sales order) is the triggering event for workflow template 20000169 (correct error in Internet sales order) and as such is entered as standard in the event linkage table. So that the workflow template is actually started, you must activate the linkage between the triggering event and the workflow template, as the receiver of the event, in Customizing for SAP Business Workflow.

Activate the workflow template SD_KI_WF in your system as follows:
1. Execute the Customizing activity Basis Component _ Business Management _ SAP
Business Workflow _ Perform task-specific Customizing.
2. Activate the event linkage for the workflow template (Sales and Distribution _ Sales _ Activate event linking).
(Alternatively, you can activate event-receiver linkage by working directly in the workflow template)

Handling of Exceptions at Store Goods Receipt (SDPOS)
Purpose You can use the functions of store goods receipt for stores that donot have a direct link to the central SAP System and therefore post their goods receipt in a store merchandise management system. This goods receipt data is then transferred in the form of an IDoc to the central SAP System, where it is processed automatically. If the data is complete and error-free, the goods receipts of the stores are posted in the central system.

In IDoc inbound processes, exceptions may occur, and you can process these using workflow.

Exceptions are situations in which the system is not able to process data automatically, because information on the goods movement item is missing.
Exceptions therefore usually apply to a single goods movement item. Exception handling is required, for example, if one of the following situations occurs:

The open goods receipt quantity is too low
Quantity variances were determined in the goods receipt check
The system could not uniquely assign a purchase order or delivery to the store goods receipt
The system could not determine a purchase order or delivery to the store goods receipt
The system could not expand a shipping unit into its individual articles

The workflow described below is used to handle these exceptions.

Process Flow

A store associate enters goods receipts and other goods movements in a store's merchandise management system.
As a result, IDocs of type WPUWBW01 are created and used to transfer the information relating to goods receipt to the central SAP System automatically. The central SAP System posts the IDocs in the background.

If one of the above-mentioned exceptions occurs during inbound processing for the IDoc, the system triggers workflow for the item concerned, and creates a work item. The person responsible for processing the exception receives the work item in his/her integrated inbox.

Workflow is complete when no further errors occur for a goods movement item, which means that the data can be successfully posted in the central SAP System.

Technical Implementation (SD-POS)

The following information is of a technical nature. You need the information if you are interested in the details of implementation, or want to carry out enhancements yourself.

Object Types

Object technology is used to create the interface between the SAP functions and the Workflow system.
During POS inbound processing, an IDoc of type WPUWBW01 is created. This contains the data that the central SAP System needs to process the goods receipts that were posted in the store.

The methods for processing work items are provided by business object IDOCPUWB (POS
inbound goods movements). This object type represents the purely technical interface for executing work items, not a concrete IDoc.

Task Group

Task groups are collections of standard tasks, workflow templates and other task groups that are used in a common context.

For this workflow, two technical solutions were implemented that are assigned to the following task groups:

The single-step task for workflow linkage of store goods receipt are grouped together under task group 20000029.

A revised version, in the form of a workflow template (implemented as of Release 4.6) is stored under task group 20000023.
If you want to use this workflow, you must select one of these two solutions in Customizing for POS Interface.

Preparation and Customizing (SD-POS)

Use

Several other specific customizing steps are necessary for this workflow template in addition to the general customizing that is necessary to make sure that the workflow system functions correctly.

Prerequisites

You have carried out the general customizing for SAP Business Workflow.
Customizing Activities for Workflow "Handling Exceptions at Store Goods
Receipt" In the "POS Goods Movements Control " section of Customizing for POS Interface, you define whether you use "old" workflow exception processing (single-step tasks) or "new" workflow exception processing (workflow template), or whether you want to completely deactivate workflow exception processing.

Here, you can also define whether the system handles exceptions for goods receipts for PO items for which the "Delivery complete" indicator has been selected by triggering workflow, or whether the quantity is to be posted directly providing the quantity requirements (such as tolerances) are met.

You choose Workflow _ Store goods receipt to find the Customizing activities generated for old and new workflow exception processing. You can use these Customizing activities to perform task-specific Customizing for both workflow solutions. At this point, you can use the organizational plan to assign the person responsible for processing the exception.

Operation and Link to Application (SD-POS)

Use

When goods receipts are posted in the store, an IDoc of type WPUWBW01 is created.
When the information contained in this IDoc is transferred to the central SAP System, checks are automatically carried out. If exceptions are determined during these checks, the data relating to the goods receipt item(s) concerned is written to the workflow container. This data is transferred to a work item, which is displayed in the integrated inbox of the person responsible for processing the exception. You use the organizational plan to assign the people responsible for processing exceptions.

The methods for processing the work items are provided by business object IDOCPUWB, on which IDoc WPUWBW01 is based.

New Workflow Link (Workflow Template)

In the new version, workflow is executed using a workflow template. This contains the following single-step tasks:

Store goods receipt: Processing step
When the work item is executed, a user dialog is called in a separate window. In this
window, the prepared data for the incorrect goods receipt item is displayed from the
relevant IDoc segment for which workflow was started. An error message relating to the specific problem is also displayed.

Depending on the exception that occurred, the person responsible has various options
for pocessing the item. For example, the person responsible can reject, or post the data, or create an automatic purchase order.
It is possible to process partial quantities of the transferred quantities in sequence. Once a partial quantity has been posted successfully, a new work item is created for the remaining quantity, and you can continue processing with this work item.

Concrete posting of the item is carried out by batch input, which means that the
corrected information is transferred to the central system in the background. If a problem occurs during processing, background processing is terminated so that the person responsible can intervene online at the point where the problem occurred.

Background processing then continues.

Store goods receipt: Delete error log for exception processing
Workflow is complete when there are no remaining quantities to be processed. At this
point, the error log that is displayed in the POS monitor for this POS goods receipt item is deleted.

Old Workflow Link

The old version of workflow is executed with the following single-step tasks:
Store goods receipt for purchase order
Store goods receipt for unknown purchase order
Store goods receipt with automatic purchase order
Operation and Link to Application (SD-POS)

Store goods receipt with quantity variance
Store goods receipt for delivery
Store goods receipt for shipping unit
When the work item is executed, these single-step tasks are run in batch input, with the exception of the single-step task for processing quantity variances. For this step a dialog box is displayed in which the person responsible can correct the quantity variances. Background processing is starts.

All the data determined by the system is transferred to the batch input. If a problem occurs during processing, batch input continues online, so that the person responsible can analyze the problem.

Workflow is complete when the item can be successfully posted.
The error log displayed in the POS monitor for the POS goods receipt item is updated once the work item has been processed successfully.