sap培訓(xùn)時(shí)得到的

1、Engineer-to-Order (ETO) Quotation Processing (232)SAP Best PracticesPurpose, Benefits, and Key Process StepsPurposeThis scope item describes the quotation processing in a standard Engineer-to-Order (ETO) environment. SAP functionalities of Sales & Distribution (SD) and of Project System (PS) are use

2、d to control the complete process, from customer inquiry to the handover to project assembly (described in the scope item 240, ETO Project Assembly). In addition to the SAP reporting functionality also the special purchasing functionality “l(fā)ong lead time procurement” is part of the process.BenefitsD

3、eep integration to the project structuring and calculation allows for a consistent controlling of all steps and values Copy functionalities e.g. from inquiry to quotation are facilitating compliance with the process rulesAll values and parameters for the subsequent process (ETO 240) are available as

4、 default parametersThe option for the creation of project versions are allowing a continuous recording of all relevant values along the controlling process and a later comparison of the several situationsThe long lead time procurement process is an important step to guarantee material availability o

5、n timeCost planning, budgeting and comprehensive reporting functionality allows for a detailed controlling of the projectKey Process StepsCreation of inquiry with linkage to projectEasy Cost PlanningCreation of quotation with reference to the inquiryIntegration to the project system including calcul

6、ation and scheduling functionalitiesControlling and reporting along the complete processRequired SAP Applications and Company RolesRequired SAP enhancement package 7 for SAP ERP 6.0Company RolesSales Administrator Project Manager Detailed Process DescriptionEngineer-to-Order (ETO) Quotation Processi

7、ngThis scope item describes a business process in a typical engineer-to-order (ETO) environment. Sales & Distribution (SD) and the Project System (PS) are used to control the complete process from the customer inquiry to the accepted quotation. The process has a final step with the start of the long

8、 lead time procurement. First process step is the creation of the inquiry and the linkage of a customer project to the inquiryCreation of the quotation with reference to the inquiryProject structuring is the prerequisite for the above-mentioned step Project scheduling and calculation (basis for the

9、quotation) are carried out Cost Planning, Budget Planning and Pricing are carried out while processing the projectReporting and project versions are completing the scope itemLong lead time procurement starts with the customer acceptance of the changed quotationEngineer-to-Order (ETO) Quotation Proce

10、ssingProject ManagerSalesAdministrationLinking project (WBS-element) with inquiryCreation of InquiryCreation of project based on templateUpdate quotation with price conditionsProject schedulingProject cost reportingCustomer Activity / EventCreating quotation with reference to inquiryProject costingP

11、roject ManagerSalesAdministrationCreation of project versionChanging quotation according to customer needProject Re-SchedulingProject Costing1Project cost reportingProcess ETO 240Project AssemblyEasy cost planning calculationTransfer milestones to quotation1Update project activities and componentsPe

12、rform budgetingCompare project version with actual dataPerform long lead time procurementUpdate quotation with price conditionsProcess Flow DiagramLegendSymbolDescriptionUsage CommentsTo next / From last Diagram: Leads to the next / previous page of the DiagramFlow chart continues on the next / prev

13、ious pageHardcopy / Document: Identifies a printed document, report, or form Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow linesFinancial Actuals: Indicates a financial posting document

14、 Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow linesBudget Planning: Indicates a budget planning document Does not correspond to a task step in a document; instead, it is used to reflec

15、t a document generated by a task step; this shape does not have any outgoing flow linesManual Process: Covers a task that is manually done Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the wa

16、rehouse, which affects the process flow. Existing Version / Data: This block covers data that feeds in from an external process Does not generally correspond to a task step in a document; instead, this shape reflects data coming from an external source; this step does not have any ing flow lines Sys

17、tem Pass / Fail Decision: This block covers an automatic decision made by the software Does not generally correspond to a task step in the document; instead it is used to reflect an automatic decision by the system that is made after a step has been executed. External to SAPBusiness Activity / Event

18、Unit ProcessProcess ReferenceSub-Process ReferenceProcess DecisionDiagram ConnectionHardcopy / DocumentFinancial ActualsBudget PlanningManual ProcessExisting Version / DataSystem Pass/Fail DecisionSymbolDescriptionUsage CommentsBand: Identifies a user role, such as Accounts Payable Clerk or Sales Re

19、presentative. This band can also identify an organization unit or group, rather than a specific role.The other process flow symbols in this table go into these rows. You have as many rows as required to cover all of the roles in the scope item.Role band contains tasks common to that role.External Ev

20、ents: Contains events that start or end the scope item, or influence the course of events in the scope item.Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scope item.Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a sc

21、ope item. Line can also lead to documents involved in the process flow.Connects two tasks in a scope item process or a non-step eventBusiness Activity / Event: Identifies an action that either leads into or out of the scope item, or an outside Process that happens during the scope itemDoes not correspond to a task step in the document Unit Process: Identifies a task that is covered in a step-by-step manner in the