Click here to load reader
Upload
mohamed-abdelgawad-ali
View
214
Download
0
Embed Size (px)
Citation preview
8/10/2019 FICO_156
http://slidepdf.com/reader/full/fico156 1/6
General LedgerSAP Best Practices Baseline Package
SAP Best Practices
8/10/2019 FICO_156
http://slidepdf.com/reader/full/fico156 2/6
Scenario Overview – 1
Purpose
This scenario provides a comprehensive picture of external accounting andaccounts.
Benefits
Recording all business transaction ensures complete and accurate accounting
data.
Key process flows covered
Posting General Ledger Account Documents
Displaying the Document Journal
Displaying G/L Balances (List)
Carrying Out Recurring Entries Account Maintainance: Automatic and Manual Clearing
Purpose and Benefits:
8/10/2019 FICO_156
http://slidepdf.com/reader/full/fico156 3/6
Scenario Overview – 2
Required
SAP enhancement package 4 for SAP ERP 6.0
Company roles involved in process flows General Ledger Accountant
Finance Manager
SAP Applications Required:
8/10/2019 FICO_156
http://slidepdf.com/reader/full/fico156 4/6
Scenario Overview – 3
General Ledger The central task of G/L accounting is to provide a comprehensive picture of
external accounting and accounts. Recording all business transactions(primary postings as well as settlements from internal accounting) in asoftware system that is fully integrated with all the other operational areas ofa company ensures that the accounting data is always complete andaccurate.
The SAP FI General Ledger has the following features:
Free choice of level: corporate group or company Automatic and simultaneous posting of all sub-ledger items in the
appropriate general ledger accounts (reconciliation accounts)
Simultaneous updating of general ledger and cost accounting areas
Real-time evaluation of and reporting on current accounting data, in theform of account displays, financial statements with different financialstatement versions and additional analyses.
Essentially, the general ledger serves as a complete record of all business
transactions. It is the centralized, up-to-date reference for the rendering ofaccounts. Actual individual transactions can be checked at any time inrealtime processing by displaying the original documents, line items, andtransaction figures at various levels such as:
Account information
Journals
Totals/transaction figures
Balance sheet/profit and loss evaluations
Detailed Process Description:
8/10/2019 FICO_156
http://slidepdf.com/reader/full/fico156 5/6
Process Flow Diagram
General Ledger
G e n e r a l L e d g e r
A c c o u n t M a n a g
e r
E v e n t
G/L = General Ledger
Process
Decision
Posting (FI) ReversalDisplaying
Posting G/L
AccountDocument
Displaying andChanging Line
Items
Displaying aDocument
Displaying theCompact
DocumentJournal
Displaying theDocument
Journal
DisplayBalances
Reversing aDocument
Processing aRecurring Entry
Original
Document
List ofRecurring Entry
OriginalDocuments
Carrying OutRecurring
Entries
Clearing
Process
Decision
Displaying G/LBalances (List)
Displayingand Change
Process
Decision
AccountMaintenance:
Automatic
AccountMaintenance:
ManualClearing
8/10/2019 FICO_156
http://slidepdf.com/reader/full/fico156 6/6
Legend
Symbol Description Usage
Comments
Band: 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 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 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 twotasks in ascenario
process or anon-step event
Business Activity / Event: Identifies an action thateither leads into or out of the scenario, or an outsideProcess that happens during the scenario
Does notcorrespond to atask step in thedocument
Unit Process: Identifies a task that is covered in astep-by-step manner in the scenario
Corresponds toa task step inthe document
Process Reference: If the scenario references another
scenario in total, put the scenario number and namehere.
Corresponds to
a task step inthe document
Sub-Process Reference: If the scenario referencesanother scenario in part, put the scenario number,name, and the step numbers from that scenario here
Corresponds toa task step inthe document
Process Decision: Identifies a decision / branchingpoint, signifying a choice to be made by the enduser. Lines represent different choices emergingfrom different parts of the diamond.
Does notusuallycorrespond to atask step in thedocument;Reflects achoice to bemade after stepexecution
Symbol Description Usage Comments
To next / From last Diagram: Leads
to the 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 taskstep in a document; instead, it isused to reflect a documentgenerated by a task step; thisshape does not have any outgoingflow lines
Financial Actuals: Indicates afinancial posting document
Does not correspond to a taskstep in a document; instead, it isused to reflect a documentgenerated by a task step; thisshape does not have any outgoingflow lines
Budget Planning: Indicates abudget planning document
Does not correspond to a taskstep in a document; instead, it isused to reflect a documentgenerated by a task step; thisshape does not have any outgoingflow lines
Manual Process: Covers a taskthat is manually done
Does not generally correspond toa task step in a document;instead, it is used to reflect a taskthat is manually performed, suchas unloading a truck in thewarehouse, which affects theprocess flow.
Existing Version / Data: This blockcovers data that feeds in from anexternal process
Does not generally correspond toa task step in a document;instead, this shape reflects datacoming from an external source;this step does not have anyincoming flow lines
System Pass / Fail Decision: Thisblock covers an automaticdecision made by the software
Does not generally correspond toa task step in the document;instead it is used to reflect anautomatic decision by the systemthat is made after a step has beenexecuted.
< F u n c t i o n >
E x t e r n a l
t o
S A P
BusinessActivity /
Event
Unit Process
ProcessReference
Sub-Process
Reference
Process
Decision
DiagramConnection
Hardcopy /Document
FinancialActuals
BudgetPlanning
ManualProces
s
ExistingVersion /
Data
SystemPass/F
ailDecisio
n