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

1、Period-End Closing “General” PlantSAP Best PracticesPurpose, Benefits, and Key Process StepsPurpose Period-end closing in a plant insures that all costs incurred in production of company activities (such as materials manufactured in-house) are assigned to those activities / products. The costs are t

2、hen allocated to the respective products in profitability analysis.Benefits Transparent view of production costs for materials manufactured in-house.Automated efficient processing.Key Process StepsRun assessment cycle for quality costsEnsure goods movements and production transactions are completeOp

3、en new MM periodPeriod-end closing for production orders (overheads, WIP calculation, variances calculation, settlement of production orders)Close completed production ordersData collection for summarization hierarchy (reporting)Run actual assessment of all cost center costs to profitability analysi

4、s (COPA)Run profitability reportRequired SAP Applications and Company RolesRequired SAP Applications Enhancement package 7 for SAP ERP 6.0Company RolesEnterprise ControllerProduct Cost ControllerAccounts Payable AccountantShop Floor SpecialistGeneral Ledger AccountantProduction PlannerDetailed Proce

5、ss DescriptionPeriod-End Closing “General” PlantFirst, you allocate quality costs to production cost centers.Then you have to ensure that all ing invoices are registered for the period (release blocked invoices).The goods movements and production transactions have to be complete for the period.Open

6、new MM period.Then you start period-end closing activities for production orders: posting of actual overheads, calculation of WIP (work in progress), variances calculation, settlement of production orders. Completed production orders are closed.To facilitate reporting, you run a data collection for

7、summarization hierarchies. The data is registered at the different levels of the hierarchy, e.g. company, plant, order type, product hierarchy. The data extracts are used for reporting on production costs.To complete the allocation of production costs to products in COPA, you run the actual assessme

8、nt of all cost center costs to profitability analysis (COPA).In profitability reports, you can analyze costs and revenues for your products.Process Flow DiagramPeriod-End Closing “General” PlantEnterprise ControllerAccounts Payable AccountantProduct Cost ControllerEventShop Floor SpecialistPO Invoic

9、es Need to be Posted before Month-EndPO = Purchase Order; AP = Accounts Payable; MM = Mass Maintenance; WIP = Work in ProgressRelease Blocked InvoicesRecord Purchase-Order-Related AP TransactionsRun Assessment Cycle for Quality CostsEnsure Production Transactions are Complete Ensure Inventory Moveme

10、nts are Complete Open New MM PeriodGeneral Ledger AccountantPost Actual Overheads Calculation Prod. OrderPeriod-End Closing with Partially Delivered Production OrdersPreliminary Settlement for Co-Products Review WIP CalculationProduction and Process Order Variance CalculationSettle VariancesData Col

11、lection for Summarization Hierarchy Close Completed Production OrdersProduct Order Information SystemPerform Actual Assessment to CO-PAWIP CalculationProduction PlannerAnalyze VariancesRun Profitability ReportRun Assessment Cycle for Quality CostsLegendSymbolDescriptionUsage CommentsTo next / From l

12、ast Diagram: Leads to the next / previous 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

13、shape does not have any outgoing flow linesFinancial 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 budg

14、et planning 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 linesManual Process: Covers a task that is manually done Does not generally correspond to a task step in a document; i

15、nstead, it is used to reflect a task that 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, thi

16、s shape reflects data coming from an external 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

17、 by the system that is made after a step has been executed. External to SAPBusiness Activity / EventUnit ProcessProcess ReferenceSub-Process ReferenceProcess DecisionDiagram ConnectionHardcopy / DocumentFinancial ActualsBudget PlanningManual ProcessExisting Version / DataSystem Pass/Fail DecisionSym

18、bolDescriptionUsage CommentsBand: Identifies 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

19、to cover all of the roles in the scenario.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 scenar

20、io.Flow line (dashed): Line indicates flow 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 that 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 scenar