Removing Errors in Internet Sales Orders (SD-SLS)
Purpose
In the Internet application component Online Store, customers can obtain quotes and enter orders over the Internet. They can choose to pay either by invoice, credit card or cash on delivery.
If a quotation or order cannot be created because certain master data or Customizing settings are missing or not properly maintained, the transaction is cancelled and an error message is displayed in the customer’s browser.
This workflow enables the relevant associates to be informed automatically about the error so that they can be corrected as quickly as possible.
Process Flow
The event triggering the workflow is generated automatically when an error occurs in the entry of a sales order or quotation in an Online Store.
A work item containing information about the errors that occurred and all the details required to correct the error is sent to the inbox of the sales associates responsible for the Online Store.
Technical Implementation (SD-SLS)
Object Types Used
Object technology is used to create the interface between the R/3 functions and the workflow system. The information given below is of a technical nature and is not necessary for an initial overview.
Standard Tasks
The standard tasks provided by SAP as single steps describe the basic business activities from an organizational point of view. A single-step task relates to a single object method (= technical link to R/3 functionality), and is linked to the agents possible from an organizational point of view.
Workflow Template
The actual operational procedure is implemented as a workflow template. You can find this workflow template in your R/3 system.
Object: Sales Order (SD-SLS)
Definition
The sales order business object (object type BUS2032) is a request from a customer to a company asking for a specific quantity of materials to be delivered, or services to be rendered, on a given date.
A sales order is sent to a sales area, and this sales area is then responsible for fulfilling the contract.
Use
It is also possible to simulate a sales order. In this process, prices are determined, taking account of customer-specific conditions, and current delivery data is determined for a sales order, but the sales order itself is not created. A simulated sales order is referred to as a quotation in this case (not to be confused with the customer quotation business object, object type BUS2031).
Location in object repository: Sales and distribution _ Sales _ Customer quotation
Standard Task TS20000357: Error in Quotation (SD-SLS)
Use
This standard task is used to decide whether an error that occurred during creation of a quotation (in this case, equivalent to the simulation of a sales order in the online store) is to be corrected.
The agent is provided with all information needed to reconstruct and correct the error. This includes the error message plus long text, the online store in which the error occurred, the sales are responsible, the ordering party (customer), all materials in the order items, the pricing date and the delivery date.
The agent can end processing of the task by choosing Error corrected. The agent can also cancel the task, in which case the task remains in the agent’s integrated inbox for further processing.
Object method referenced: object type DECISION, method: Process
Agent assignment: For the validity period, this standard task is addressed to the agents in the sales office or sales area which are responsible for the online store. These employees are determined via standard role 20000045 (agent for Internet sales orders).
Standard Task TS20000347: Error in Order on Account(SD-SLS)
Use
This standard task is used to decide whether an error that occurred during creation of a order for which an invoice is to be issued to the customer is to be corrected. As in standard task TS20000357, the agent is provided with all information needed to reconstruct and correct the error. In addition, the agent is told that the customer wanted the order to go on his/her account and that an invoice was to be issued.
The agent can end processing of the task by choosing Error corrected. The agent can also cancel the task, in which case the task remains in the agent’s integrated inbox for further processing.
Object method referenced: object type DECISION, method: Process
Agent assignment: For the validity period, this standard task is addressed to the agents in the sales office or sales area which are responsible for the online store. These employees are determined via standard role 20000045 (agent for Internet sales orders).
Standard Task TS20000346: Error in Credit Card Order (SD-SLS)
Use
This standard task is used to decide whether an error that occurred during creation of a credit card order is to be corrected. As in standard task TS20000357, the agent is provided with all information needed to reconstruct and correct the error. In addition, the agent is told that the customer wanted to pay by credit card, and is informed of the type of credit card, the card number, and the expiration date.
The agent can end processing of the task by choosing Error corrected. The agent can also cancel the task, in which case the task remains in the agent’s integrated inbox for further processing.
Object method referenced: object type DECISION, method: Process
agent assignment: For the validity period, this standard task is addressed to the agents in the sales office or sales area which are responsible for the online store. These employees are determined via standard role 20000045 (agent for Internet sales orders).
Standard Task TS20000372: Error in Cash-on-Delivery Order (SD-SLS)
Use
This standard task is used to decide whether an error that occurred during creation of a cash-ondelivery order is to be corrected. As in standard task TS20000357, the agent is provided with all information needed to reconstruct and correct the error. In addition, the agent is told that the customer wanted to pay by cash on delivery.
The agent can end processing of the task by choosing Error corrected. The agent can also cancel the task, in which case the task remains in the agent’s integrated inbox for further processing.
Object method referenced: object type DECISION, method: Process,
Agent assignment: For the validity period, this standard task is addressed to the agents in the sales office or sales area which are responsible for the online store. These employees are determined via standard role 20000045 (agent for Internet sales orders).
Saturday, October 18, 2008
Subscribe to:
Post Comments (Atom)
Archives
-
▼
2008
(167)
-
▼
October
(145)
- SAP ALE ABAP DETIAL
- SAP ABAP ALE IDOC'S
- SAP - DIFFERENCE BETWEEN CONVERSION AND INTERFACE
- BAPI AND IDOC ALE
- SAP ABAP MESSAGE CONTORL
- SAP IDOC'S IN ABAP INTRODUCTION
- SAP ABAP IDOC'S OUTLOOK
- SAP ABAP IDOC PROCESSING
- SAP ABAP IDOC'S BASIC TOOLS I
- SAP ABAP IDOC'S BASIC TOOLS II
- SAP ABAP IDOC'S INBOUND BASIC TOOLS III
- SAP IDOC OUT BOUND TRIGGERS II
- SAP IDOCS OUTBOUND TRIGGER II
- SAP IDOC'S OUTBOUND TRIGGER III
- SAP Work flow based outbound Idoc's
- SAP ALE Change Pointers
- SAP Dispatching ALE IDocs for Change Pointers
- SAP IDOC design and Processing
- SAP Creation of the IDoc Data
- SAP Developing an Outbound IDoc Function
- SAP Converting Data into IDoc Segment Format
- SAP Partner Profiles and Ports
- SAP Defining the partner profile for ALE IDOC
- SAP Data Ports ( WE21 ) in idoc
- SAP RFC in R/3
- SAP Workflow from Change Documents
- SAP ALE Distribution Scenario
- SAP Useful ALE Transaction Codes
- BAPI Creating IDocs and ALE Interface
- R/3 RFC from MS Office Via Visual Basic
- SD WORK FLOW SCENARIOS I
- SD WORK FLOW SCENARIOS II
- SD WORK FLOW SCENARIOS III
- SD WORK FLOW SCENARIOS IV
- SD WORK FLOW SCENARIOS V
- SD WORK FLOW SCENARIOS VI
- SD WORK FLOW SCENARIOS VII
- MM WORK FLOW SCENORIOS I
- MM WORK FLOW SCENORIOS II
- MM WORK FLOW SCENORIOS III
- MM WORK FLOW SCENORIOS IV
- MM WORK FLOW SCENORIOS V
- MM WORK FLOW SCENORIOS VI
- MM WORK FLOW SCENARIOS VII
- MM WORK FLOW SCENARIOS VIII
- MM WORK FLOW SCENARIOS IX
- MM WORK FLOW SCENARIOS X
- MM WORK FLOW SCENARIOS XI
- WORK FLOW SCENARIOS in SAP ABAP
- SAP ABAP WORK FLOW I
- SAP ABAP WORK FLOW II
- SAP ABAP WORK FLOW III
- SAP ABAP Work Flow IV
- SAP ABAP Workflow Technology
- SAP OPTIMIZATION
- abap type key ward
- PERFORMENCE TIPS
- SAP ABAP INTERNAL TABLES IN BRIEF
- SAP ABAP RUN TIME ANALASIS
- MEMORY In SAP ABAP
- NAVIGATION In SAP ABAP
- WORK BENCH AND TOOLS In SAP ABAP
- DATA OBJECTS AND STATEMENTS In SAP ABAP
- INTERNAL PROGRAM MODULARIZATION In SAP ABAP
- SAP ABAP CONSITENCEY THROUGH INPUT CHECKS
- RUN TIME ENVIRONMENT In SAP ABAP
- SAP ABAP INTER TABLE OPERATIONS
- STATEMENTS In SAP ABAP
- SAP ABAP INTERNAL TABLES
- SAP ABAP SUB ROUTIENS
- SAP ABAP FUNCTION MODULES AND GROUPS
- SAP ABAP QUARY ADMINSTRATION
- SAP ABAP SAVING LISTS AND BACK GROUND PROCESSING
- SAP ABAP PROGRAM INTERFACE
- SAP ABAP LOCK CONCEPT
- SAP ABAP AUTHORISATION CHECKS
- SAP ABAP PERFORMENCE TIPS
- In SAP SYSTEM FIELDS
- SAP ABAP CONTROL BLOCKS
- SAP ABAP BUFFERING
- SAP ABAP MATCH CODE OBJECTS
- SAP ABAP LOCKS
- SAP SAMPLE CODE FOR OUTPUT TO EXCEL AND IN PUT FIL...
- SAP MULTIPLE INTERACTIVE REPORT SAMPLE CODE
- MULTIPLE INTERACTIVE REPORT SAMPLE CODE II
- CALLING PROGRAM AND PASSING DATA
- SAP TECHNIQUES FOR LIST CREATION AND SAP QUARY
- SAP SELECTION SCREENS ABAP REPORT
- SAP ABAP FAQ ON SCRIPTS I
- SAP ABAP FAQ ON SCRIPTS II
- SAP ABAP FAQ ON SCRIPTS III
- IN SAP ABAP TABLE TYPES
- SAP ABAP TYPES OF VIEWS
- SAP ABAP DATA BASE UPDATES COMPLETE
- SAP ABAP LOCK CONCEPT
- SAP ORGANIZING DATABASE UPDATES
- SAP ENHANCEMENTS TO DICTIONERY ELEMENTS
- DATA BASE DIALOG IN ABAP
- ABAP DICTIONARY I
- PERFORMANCE DURING TABLE ACCESS
-
▼
October
(145)
No comments:
Post a Comment