Upload
dhiman-ghoshal
View
223
Download
0
Embed Size (px)
Citation preview
8/6/2019 159 Scen Overview en KR
1/13
Period End Closing FinancialAccountingSAP Best Practices Baseline Package(Korea)
SAP Best Practices
8/6/2019 159 Scen Overview en KR
2/13
Scenario Overview 1
Purpose The closing operations component helps you prepare and carry out the activitiesrequired for day-end, month-end and year-end closing.For this purpose, the system provides a series of standard reports that can beused to generate evaluations and analyses of the posted account balancesdirectly.
BenefitsThe system helps you to carry out the following:
create the balance sheets and P&L statements anddocument the posting data.
Key process flows coveredday-end closing,month-end closing andyear-end closing.
Purpose and Benefits:
8/6/2019 159 Scen Overview en KR
3/13
Scenario Overview 2
RequiredEHP3 for SAP ERP 6.0
Company roles involved in process flowsFinance Manager Accounts Payable Manager
Accounts Receivable Manager
SAP Applications Required:
8/6/2019 159 Scen Overview en KR
4/13
Scenario Overview 3
Day-end closing in Financial AccountingUpdate Exchange RatesGaps in Document Number AssignmentInvoice Numbers Allocated TwiceDisplay Compact Document Journal.
Detailed Process Description:
8/6/2019 159 Scen Overview en KR
5/13
Scenario Overview 4
Month-end closing in Financial Accounting (I)Update Exchange RatesGaps in Document Number AssignmentInvoice Numbers Allocated TwiceOpen and Close Posting Periods
Enter Recurring EntriesPost Recurring EntriesRun Batch Input SessionAutomatic Clearing of GR/ IR Account special processAnalyze GR/ IR Clearing AccountsAutomatic Clearing of GR/ IR Account
Post Adjustment Entries
Detailed Process Description:
8/6/2019 159 Scen Overview en KR
6/13
Scenario Overview 5
Month-end closing in Financial Accounting (II)Foreign Currency RevaluationPost Tax PayableComparison Documents/ Transaction FiguresClose Previous Accounting PeriodBalance Interest CalculationDisplay Document JournalFinancial Statement.
Detailed Process Description:
8/6/2019 159 Scen Overview en KR
7/13
Scenario Overview 6
Year-end closing in Financial AccountingCreate Factory Calendar for New Year Carry Forward AP/ AR BalancesCarry Forward GL BalancesRe-grouping Receivables/ PayablesBalance Confirmation ReceivableBalance Confirmation PayableFinal Close and Release Financial ReportingClose Previous Accounting PeriodDisplay Document Journal.
Detailed Process Description:
8/6/2019 159 Scen Overview en KR
8/13
Process Flow DiagramProcess 1, Day-End Closing
Finance Manager
Event
ProcessDecision
Update ExchangeRates
Updating Evaluation Reporting
DisplayCompact
DocumentJournal
Invoice NumbersAllocated Twice
Gaps inDocument
Number Assignment
8/6/2019 159 Scen Overview en KR
9/13
Process Flow DiagramProcess 2, Month-End-Closing (I)
Finance Manager
Event
Process
Decision
UpdateExchange
Rates
Updating Evaluation Posting
Process
Decision
Process
Decision
Open andClose
PostingPeriods
ClosePrevious
AccountingPeriod
ComparisonDocuments/Transaction
Figures
Gaps inDocument
Number Assignment
InvoiceNumbersAllocated
Twice
PostAdjustment
Entries
ForeignCurrency
Revaluation
Post TaxPayable
PostRecurring
Entries
Enter Recurring
Entries
Run BatchInput
Session
BalanceInterest
Calculation3
2
1
8/6/2019 159 Scen Overview en KR
10/13
Process Flow DiagramProcess 2, Month-End-Closing (II)
Finance Manager
Accounts
Payable
Manager
Event
Clearing Reporting
Analyze GR/IR Clearing
Account
AutomaticClearing of
GR/ IRAccount
AutomaticClearing of GR/
IR AccountSpecial Process
DisplayDocument
Journal
FinancialStatement
3
1
2
8/6/2019 159 Scen Overview en KR
11/13
Process Flow DiagramProcess 3, Year-End-Closing
Finance Manager
Accounts
Payable
Manger
Event
Accounts
Receivable
Manager
Process
Decision
RegroupingReceivables/
Payables
Updating
GL = General Ledger
Carry ForwardGL Balances
Carry ForwardAP/ AR
Balances
Create FactoryCalendar for
New Year
DisplayDocument
Journal
Final Close andRelease
FinancialReporting
BalanceConfirmation
Payable
BalanceConfirmation
Receivable
Reporting
Close PreviousAccounting
Period
8/6/2019 159 Scen Overview en KR
12/13
Legend
Symbol Description Usage Comments
Band: Identifies a user role, such as Accounts Payable
Clerk or Sales Representative. This band can alsoidentify an organization unit or group, rather than aspecific role.
The other process flow symbols in this table go intothese rows. You have as many rows as required to cover all of the roles in the scenario.
Role band contains
tasks common tothat role.
External Events: Contains events that start or end thescenario, or influence the course of events in thescenario.
Flow line (solid): Line 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 alsolead to documents involved in the process flow.
Connects two tasksin a scenarioprocess or a non-step event
Business Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Processthat happens during the scenario
Does notcorrespond to a taskstep in thedocument
Unit Process: Identifies a task that is covered in a step-by-step manner in the scenario
Corresponds to atask step in thedocument
Process Reference: If the scenario references another scenario in total, put the scenario number and namehere.
Corresponds to atask step in thedocument
Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and thestep numbers from that scenario here
Corresponds to atask step in thedocument
Process Decision: Identifies a decision / branching point,signifying a choice to be made by the end user. Linesrepresent different choices emerging from different partsof the diamond.
Does not usuallycorrespond to a taskstep in thedocument; Reflectsa choice to be madeafter step execution
Symbol Description Usage Comments
To next / From last Diagram: Leads tothe next / previous page of theDiagram
Flow chart continues on the next /previous page
Hardcopy / Document: Identifies aprinted document, report, or form
Does not correspond to a task step ina document; instead, it is used toreflect a document generated by a taskstep; this shape does not have anyoutgoing flow lines
Financial Actuals: Indicates a financialposting document
Does not correspond to a task step ina document; instead, it is used toreflect a document generated by a taskstep; this shape does not have anyoutgoing flow lines
Budget Planning: Indicates a budgetplanning document
Does not correspond to a task step ina document; instead, it is used toreflect a document generated by a taskstep; this shape does not have anyoutgoing flow lines
Manual Process: Covers a task that ismanually done
Does not generally correspond to atask step in a document; instead, it isused to reflect a task that is manuallyperformed, such as unloading a truckin the warehouse, which affects theprocess flow.
Existing Version / Data: This blockcovers data that feeds in from anexternal process
Does not generally correspond to atask step in a document; instead, thisshape reflects data coming from anexternal source; this step does nothave any incoming flow lines
System Pass / Fail Decision: This blockcovers an automatic decision made bythe software
Does not generally correspond to atask step in the document; instead it isused to reflect an automatic decisionby the system that is made after a stephas been executed.
External
to SAP
BusinessActivity /
Event
Unit Process
ProcessReference
Sub-Process
Reference
Process
Decision
DiagramConnection
Hardcopy /Document
FinancialActuals
BudgetPlanning
ManualProces
s
ExistingVersion /
Data
SystemPass/F
ailDecisio
n
8/6/2019 159 Scen Overview en KR
13/13
Copyright 2008 SAP AGAll rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changedwithout prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayedare the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of t he SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy,and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitationshall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.