Sales and Distribution (SD) Workflow Scenarios

1 Sales and Distribution (SD) Workflow and Distribution (SD) Workflow Scenarios SAP AG2 December 1999 Copyright Copyright 2000 SAP AG. All rights part of this brochure may be reproduced or transmitted in any form or for any purpose withoutthe express permission of SAP AG. The information contained herein may be changed withoutprior software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software , WINDOWS , NT , EXCEL , Word and SQL Server are registered trademarks ofMicrosoft , DB2 , OS/2 , DB2/6000 , Parallel Sysplex , MVS/ESA , RS/6000 , AIX , S/390 ,AS/400 , OS/390 , and OS/400 are registered trademarks of IBM is a registered trademark of ORACLE Corporation, California, -OnLine for SAP and Informix Dynamic ServerTM are registered trademarks ofInformix Software , X/Open , OSF/1 , and Motif are registered trademarks of The Open , DHTML, XML, XHTML are trademarks or registered trademarks of W3C , World WideWeb Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute ofTechnology, 545 Technology Square, Cambridge, MA is a registered trademark of Sun Microsystems, Inc.

2 , 901 San Antonio Road, Palo Alto,CA 94303 is a registered trademark of Sun Microsystems, Inc., used under license fortechnology invented and implemented by , SAP Logo, , Marketplace, Workplace, Scenarios , Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP, SAPB usiness Workflow , SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, ManagementCockpit, SEM, are trademarks or registered trademarks of SAP AG in Germany and in severalother countries all over the world. All other products mentioned are trademarks or registeredtrademarks of their respective companies. SAP AGSales and Distribution (SD) Workflow ScenariosDecember 19993 IconsIconMeaningCautionExampleNoteRecomm endationSyntaxTipSales and Distribution (SD) Workflow Scenarios SAP AG4 December 1999 ContentsSales and Distribution (SD) Workflow Credit Memo Requests (SD-SLS-RE) .. 6 Example: Processing Credit Memo Requests .. 8 Technical Implementation of the Workflow (SD-SLS-RE) .. 9 Object Types (SD-SLS-RE).. 10 Initial Values (SD-SLS-RE).

3 11 Workflow Template (SD-SLS-RE) .. 12 Flow for Workflow 14 Standard Tasks (SD-SLS-RE).. 15 Preparation and Customizing (SD-SLS-RE) .. 17 Activate Event-Receiver Linkage .. 18 Using and Linking to the Application Functions (SD-SLS-RE).. 19 Change Master Contract (SD-SLS-OA) .. 20 Example: Using Workflow to Change the Master 22 Technical Implementation of the Workflow (SD-SLS-OA) .. 23 Object Types (SD-SLS-OA).. 24 Workflow Template (SD-SLS-OA) .. 25 Standard Tasks (SD-SLS-OA) .. 29 Preparation and Customizing (SD-SLS-OA) .. 31 Using and Linking to the Application Functions (SD-SLS-OA).. 33 Removing Errors in Internet Sales Orders (SD-SLS) .. 34 Technical Implementation (SD-SLS) .. 35 Object: Sales Order (SD-SLS) .. 36 Standard Task TS20000357: Error in Quotation (SD-SLS) .. 37 Standard Task TS20000347: Error in Order on Account (SD-SLS).. 38 Standard Task TS20000346: Error in Credit Card Order (SD-SLS) .. 39 Standard Task TS20000372: Error in Cash-on-Delivery Order (SD-SLS).

4 40 Standard Role AC2000045: Agent for Internet Sales Order (SD-SLS).. 41 Workflow Template: Correcting errors in Internet Sales orders (SD-SLS) .. 42 Preparation and Customizing (SD-SLS) .. 44 Handling of Exceptions at Store Goods Receipt (SD-POS) .. 46 Technical Implementation (SD-POS) .. 47 Preparation and Customizing (SD-POS) .. 48 Operation and Link to Application (SD-POS).. 49 SAP AGSales and Distribution (SD) Workflow ScenariosSales and Distribution (SD) Workflow ScenariosDecember 19995 Sales and Distribution (SD) Workflow ScenariosSee also:BC - Workflow Scenarios in Applications [Ext.] Sales and Distribution (SD) Workflow Scenarios SAP AGProcessing Credit Memo Requests (SD-SLS-RE)6 December 1999 Processing Credit Memo Requests (SD-SLS-RE)PurposeCredit memo requests normally need to be checked by the employee who entered them as wellas approved by an additional decision-maker. The value of the credit memo determines who isable to approve a credit memo request is created, the system normally creates a billing block.

5 This blockprevents you from billing the credit memo request and can only be removed by an the Workflow , you can represent the whole business process, with all the people involved,for approving credit memo requests within your company. This enables you to process creditmemo requests simply and efficiently. If you do not use the Workflow , the system does not controlthe process flow so you will have to organize the steps in credit memo processing the value of a credit memo request is below a minimum value, the system automaticallyreleases it for billing by removing the billing the credit memo request exceeds a certain value, the system automatically informs theemployee responsible. She or he receives a work item in their inbox and can process it directlyfrom employee responsible can cancel, release, or process a credit memo the employee cancels the request, the system automatically creates a reason for rejection inthe credit memo request and ends the employee releases the request, the system automatically removes the billing block in thecredit memo request and releases it for the employee processes the request, she or he can use all the functions available in thechange people informed by the Workflow do not need to know either the name of the transaction orthe menu path of the transactions You have configured the settings in Customizing for the Workflow and created anorganizational plan (see Preparation and Customizing (SD-SLS-RE) [Page 17]).

6 When you create credit memo requests, the system normally sets a billing block, whichprevents it from being billed. Only authorized employees may remove this billing block,thus releasing the document for billing. The person who is able to check the credit memobefore releasing it depends on the value of the credit create the billing block for credit memo requests in Customizing for Sales andDistribution when you define the order type ( Sales and Distribution = Sales =SalesDocuments Sales Document Header Define Sales document types).When using the Workflow for processing credit memo requests, we recommend that youshould only allow the billing block to be removed by the people who are authorized torelease credit memos of any value. SAP AGSales and Distribution (SD) Workflow ScenariosProcessing Credit Memo Requests (SD-SLS-RE)December 19997 Process FlowDepending on the value of the credit memo request, the system runs through one of the followingprocesses when you enter a credit memo request: If the value of the credit memo request is smaller or equal to a certain limit (L1), thesystem automatically releases the credit memo request.

7 The system removes thebilling block in the background, releasing the credit memo request for billing. If the value of the credit memo request is between limit L1 and limit L2, or equal to L2, thejob responsible is informed that the credit memo request should be checked. All thepeople assigned to this job receive a work item in their integrated inbox, where they cancancel, release or process the credit memo request. Cancel credit memo requestThe employee has to enter a reason for rejection. The system automatically transfersthe reason for rejection into the credit memo request and stops processing. Release credit memo requestThe system automatically removes the billing block in the credit memo request andreleases the document for billing. Process credit memo requestHere, the user branches into the Change Sales order transaction, where they canuse all the functions in this transaction. According to the user s authorization, he orshe can remove a billing block, enter a reason for rejection, or process individualitems (for example, delete or add order items, or change the order quantity).

8 The system checks whether the billing block was removed manually. If there is abilling block, the system re-checks the value of credit memo request and informs theemployee responsible. This process is repeated until the credit memo request haseither been rejected or and Distribution (SD) Workflow Scenarios SAP AGExample: Processing Credit Memo Requests8 December 1999 Example: Processing Credit Memo RequestsEach employee in the Sales department is allowed to release credit memo requests up to a valueof USD 300. The following authorization procedure has been defined for credit memo requeststhat exceed this limit: Credit memo requests with a value of between USD 300 and USD 5,000 may only bereleased by the group leader. Credit memo requests that exceed a value of USD 5,000, may only be released by the salesmanager. SAP AGSales and Distribution (SD) Workflow ScenariosTechnical Implementation of the Workflow (SD-SLS-RE)December 19999 Technical Implementation of the Workflow (SD-SLS-RE) Sales and Distribution (SD) Workflow Scenarios SAP AGObject Types (SD-SLS-RE)10 December 1999 Object Types (SD-SLS-RE)The interface between R/3 functionality and the Workflow system is created using the following scenario, the business application object forCredit memo requests is Object type BUS 2094.

9 SAP AGSales and Distribution (SD) Workflow ScenariosInitial Values (SD-SLS-RE)December 199911 Initial Values (SD-SLS-RE)In the Workflow , the person who releases or processes the credit memo request is decidedaccording to the value of the credit memo request. You can determine two limit values: Amountlimit 1 and amount limit order to ensure correct, cross-company code credit memo processing, you also need tospecify a reference currency. The document currency for the credit memo request is thenconverted into the reference following company codes and their house currencies exist in one company: Company code 1: House currency FRF Company code 2: House currency DEMThe employees assigned to the Sales organization process the credit memo requestsfor company code 1 and company code reference currency (for example, USD) is defined in the Workflow container. Thenet values in the Sales documents are converted into the reference currency whichmeans that the credit memo requests can then be processed and checked,independently of the currency in the company and Distribution (SD) Workflow Scenarios SAP AGWorkflow Template (SD-SLS-RE)12 December 1999 Workflow Template (SD-SLS-RE)DefinitionThe following two Workflow templates are delivered in the standard system for credit memoprocessing: Identification:WS20000009 Identification code: Credit memosLong text: Credit memo processing Identification: WS20000019 Identification code:CMR_CHECKLong text: Check credit memo requestsFor additional information, see:Flow of Workflow Template [Page 14].

10 UseWorkflow Template 20000009 Credit Memo ProcessingTriggering Event in Workflow TemplateUpdating the credit memo request triggers the event created for object type BUS2094 whichstarts the Workflow Container and Data FlowThe information needed for the Workflow is contained in the credit memo request. Thisinformation is available as an event parameter in the container for the triggered event and haveto be transferred into the Workflow container using data following data flow definition between the triggering event and the Workflow container istherefore defined in the standard system: Workflow ContainerEvent Parameter Container_WF_Initiator <--_EVT_Object (credit memo request)RefCurrency (reference currency)CUSTCOMPLAINTORDER(credit memo request)NetValue_Limit_1(amount limit 1)NetValue_Limit_2(amount limit 2)End_Flag(End indicator) SAP AGSales and Distribution (SD) Workflow ScenariosWorkflow Template (SD-SLS-RE)December 199913 The _WF_Initiator element is available in the Workflow container in the standard system, whilethe other elements listed here have been added to the Workflow EventsThe Workflow template for credit memo requests is terminated with the Release credit memorequest and Reject credit memo request Workflow Template 20000019 Credit Memo ProcessingWorkflow ContainerThe Workflow container contains the end indicator (End_Flag), information about the credit memorequest (CUSTCOMPLAINTORDER) and the employee responsible (ResponsibleAgents).