sap培训时得到的

1、Period End Closing Financial AccountingSAP Best PracticesPurpose, Benefits, and Key Process StepsPurpose The closing operations component helps you prepare and carry out the activities required for day-end, month-end and year-end closing. For this purpose, the system provides a series of standard re

2、ports that can be used to generate evaluations and analyses of the posted account balances directly.Benefits The system helps you to carry out the following:create the balance sheets and P&L statementsdocument the posting dataKey Process StepsDay-end ClosingMonth-end ClosingYear-end ClosingRequired

3、SAP Applications and Company RolesRequired Enhancement package 6 for SAP ERP 6.0Company RolesFinance ManagerGeneral Ledger AccountantAccounts Payable ManagerAccounts Receivable ManagerDetailed Process DescriptionDay-end Closing in Financial AccountingUpdate Exchange RatesGaps in Document Number Assi

4、gnment Invoice Numbers Allocated TwiceDisplay Compact Document JournalDetailed Process DescriptionMonth-end Closing in Financial Accounting (I)Update Exchange RatesGaps in Document Number Assignment Invoice Numbers Allocated TwiceOpen and Close Posting PeriodsEnter Recurring EntriesPost Recurring En

5、triesRun Batch Input SessionAutomatic Clearing of GR/ IR Account special processAnalyze GR/ IR Clearing AccountsAutomatic Clearing of GR/ IR AccountPost Adjustment EntriesDetailed Process DescriptionMonth-end Closing in Financial Accounting (II)Foreign Currency RevaluationPost Tax PayableAdvance Ret

6、urn for Tax on Sales/ PurchasesEC Sales ListComparison Documents/ Transaction FiguresClose Previous Accounting PeriodBalance Interest CalculationDisplay Document JournalFinancial StatementDetailed Process DescriptionYear-end Closing in Financial AccountingCreate Factory Calendar for New YearCarry Fo

7、rward AP/ AR BalancesCarry Forward GL BalancesRe-grouping Receivables/ PayablesBalance Confirmation ReceivableBalance Confirmation PayableFinal Close and Release Financial ReportingClose Previous Accounting PeriodDisplay Document JournalProcess Flow DiagramProcess 1, Day-End ClosingFinance ManagerEv

8、entProcess DecisionUpdate Exchange RatesUpdatingEvaluationReportingDisplay Compact Document JournalInvoice Numbers Allocated TwiceGaps in Document Number AssignmentGeneral Ledger AccountantProcess Flow DiagramProcess 2, Month-End-Closing (I)Finance ManagerEventProcess DecisionUpdate Exchange RatesUp

9、datingEvaluationPostingOpen and Close Posting PeriodsClose Previous Accounting PeriodComparison Documents/ Transaction FiguresGaps in Document Number AssignmentInvoice Numbers Allocated TwicePost Adjustment EntriesForeign Currency RevaluationPost Tax PayableAdvance Return for Tax on Sales / Purchase

10、sPost Recurring EntriesEnter Recurring EntriesRun Batch Input SessionBalance Interest Calculation54632Process DecisionProcess DecisionProcess Flow DiagramProcess 2, Month-End-Closing (II)Finance ManagerAccounts Payable ManagerEventClearingReportingAnalyze GR/ IR Clearing AccountAutomatic Clearing of

11、 GR/ IR AccountEC Sales ListAutomatic Clearing of GR/ IR Account Special ProcessDisplay Document JournalFinancial Statement5 62 3 4Process Flow DiagramProcess 3, Year-End-ClosingFinance ManagerAccounts Payable ManagerEventAccounts Receivable ManagerProcess DecisionRegrouping Receivables/ PayablesUpd

12、atingGL = General LedgerCarry Forward GL BalancesCarry Forward AP/ AR BalancesCreate Factory Calendar for New YearDisplay Document JournalFinal Close and Release Financial ReportingBalance Confirmation PayableBalance Confirmation ReceivableReportingClose Previous Accounting PeriodFinance ManagerGene

13、ral Ledger AccountantLegendSymbolDescriptionUsage CommentsTo next / From last 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;

14、 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 Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this sh

15、ape 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 reflect a document generated by a task step; this shape does not have any outgoing flow linesManual Process: Covers a task that is m

16、anually 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 warehouse, which affects the process flow. Existing Version / Data: This block covers data that feeds in from an external proces

17、s 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 System Pass / Fail Decision: This block covers an automatic decision made by the software Does not generally correspond to a task

18、 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 / EventUnit ProcessProcess ReferenceSub-Process ReferenceProcess DecisionDiagram ConnectionHardcopy / DocumentFinancial ActualsBudget

19、 PlanningManual ProcessExisting Version / DataSystem Pass/Fail DecisionSymbolDescriptionUsage 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 sy

20、mbols in this table go into these rows. You have as many rows as required 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

21、indicates the normal sequence of steps and direction of flow in the scenario.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