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

1、 SAP Best Practices, - : . , , . SAP- SAP- 7 SAP ERP 6.0 Engineering SpecialistProduction PlannerSales AdministratorBilling AdministratorAccounts Receivable AccountantProduction SupervisorWarehouse ClerkShop Floor SpecialistProduct Cost Controller ( ). . . . SAP . , . . . . . . , , , , . : Sales Adm

2、inistrator ? (144) MTO MTO = ; DMS = , : Easy DMS : Sales AdministratorBilling AdministratorProduction PlannerAccounts Receivable Accountant (130) (108) -, : ; , Production PlannerSales Adminis-tration - Manu-facturing () ( )Product Cost ControllerPurcha-ser (130) (127) (139) (138) (149) , ( )Engine

3、ering SpecialistShop Floor SpecialistProduction Supervisor : ; ; Production PlannerAccounts Receivable Acc. Manufacturing : Billing Adminsitr. Sales AdministratorShop Floor Specialist: ( ) : (109) -, - -, - LegendSymbolDescriptionUsage CommentsTo next / From last Diagram: Leads to the next / previou

4、s page of the DiagramFlow chart continues on the next / previous 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 li

5、nesFinancial Actuals: Indicates a financial posting document 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

6、 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 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 tha

7、t is manually performed, such as unloading a truck in the warehouse, 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 ext

8、ernal source; this step does not have any ing flow lines System 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

9、 has been executed. External to SAPBusiness Activity / EventUnit ProcessProcess ReferenceSub-Process ReferenceProcess DecisionDiagram ConnectionHardcopy / DocumentFinancial ActualsBudget PlanningManual ProcessExisting Version / DataSystem Pass/Fail DecisionSymbolDescriptionUsage CommentsBand: Identi

10、fies a user role, such as Accounts Payable Clerk or Sales Representative. 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 scenari

11、o.Role band contains tasks common to that role.External Events: Contains events that start or end the scenario, or influence the course of events in the scenario.Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario.Flow line (dashed): Line indicates fl

12、ow to infrequently-used or conditional tasks in a scenario. Line can also lead to documents involved in the process flow.Connects two tasks in a scenario process or a non-step eventBusiness Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process th

13、at happens during the scenarioDoes 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 scenarioCorresponds to a task step in the document Process Reference: If the scenario references another scenario in total, put the scenari

14、o number and name here.Corresponds to a task step in the document Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario hereCorresponds to a task step in the document Process Decision: Identifies a decision / branching point, signifying a ch