AC010 Financial Accounting and Reporting
AC010 Financial Accounting and Reporting
AC010
AC010
AC010 Financial Accounting and Reporting
Financial Accounting
and Reporting
SAP AG 1999
SAP AG
R/3 System
Release 4.6B
December 1999
Material number 5003 4194
SAP AG 1999
Trademarks:
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered
trademarks of Microsoft Corporation.
IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®,
OS/390®, and OS/400® are registered trademarks of IBM Corporation.
ORACLE® is a registered trademark of ORACLE Corporation.
INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of
Informix Software Incorporated.
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web
Consortium, Massachusetts Institute of Technology.
JAVA® is a registered trademark of Sun Microsystems, Inc.
JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology
invented and implemented by Netscape.
SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow,
SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com
are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over
the world. All other products mentioned are trademarks or registered trademarks of their respective
companies.
SAP AG 1999
Participants:
Members of the FI project team
Employees from accounting departments
Duration: 5 Days
SAP AG 1999
User information
The course materials are not intended for self-study. Only in combination with the instructions from the
trainer do you have the complete course materials. There is space on your materials to note down
additional information.
Contents:
Navigation in the system
User-specific settings
Navigation in the mySAP.com Workplace
SAP AG 1999
SAP AG 1999
SAP AG 1999
SAP R/3
New Password
Language
SAP AG 1999
SAP R/3 Systems are client systems. The client concept enables the parallel operation, in one system, of
several enterprises that are independent of each other in business terms. The components SAP Business
Information Warehouse (BW) and SAP Knowledge Warehouse (KW) are exceptions to this: in these
cases only one client is used. During each user session you can only access the data of the client selected
during logon.
A client is, in organizational terms, an independent unit in the system. Each client has its own data
environment and therefore its own master data and transaction data, assigned user master records and
charts of accounts, and specific Customizing parameters.
For a user to log on to the system, a master record must exist in the system for that user. To protect
access, a password is required for logon. The password is hidden as you type (you only see asterisks).
SAP R/3 Systems are available in several languages. Use the Language input field to select the logon
language for each session.
Multiple logons are always logged in the system beginning with SAP R/3 4.6. This is for security as well
as licensing reasons. A warning message appears if the same user attempts to log on twice or more. This
message offers three options:
Continue with current logon and end any other logons of the same user in the system
Continue with current logon without ending any other logons in the system (logged in system)
Terminate current logon attempt
You can place your own text on the initial screen in a number of ways. For more information, see the
SAP Note mentioned above. The GuiXT (covered at the end of this chapter) offers a further option.
Input field
Application
Tick Toolbar
Selection 1
Selection 2
Selection 3 This screen is made up of
Selection 4
Checkboxes various screen elements. It
Options Radio Buttons does not match an actual
Option 1
Pushbuttons screen in the system.
Option 2
Option 3
Overview
Option 4
Option 5
Positive
Display Edit Neutral
Tab Page
System Message T70 (1) (400) iwdf5070 INS Status Bar
SAP AG 1999
Command field: You can use the command field to go to applications directly by entering the
transaction code. You can find the transaction code either in the SAP Easy Access menu tree (see the
page User-Specific Personalization) or in the appropriate application by choosing System→ Status.
Standard toolbar: The icons in the standard toolbar are available on all SAP R/3 screens. Any icons
that you cannot use on a particular screen are dimmed. If you leave the cursor on an icon for a moment, a
QuickInfo appears with the name (or function) of that icon. You will also see the corresponding function
key. The application toolbar shows you which functions are available in the current application.
Checkboxes: Checkboxes allow you to select several options simultaneously within a group.
Radio buttons: Radio buttons allow you to select one option only.
Tabs: Tabs provide a clearer overview of several information screens.
Status bar: The status bar displays information on the current system status, for example, warnings or
error messages.
Other elements are:
Menu bar: The menus shown here depend on which application you are working in. These menus contain
cascading menu options.
Title bar: The title bar displays your current position and activity in the system.
Favorites
SAP Menu
Office
Logistics
Accounting
Human Resources
Information Systems
Tools
SAP AG 1999
SAP Easy Access is the standard entry screen displayed after logon. You navigate through the system
using a compact tree structure.
You can include an image on the right-hand side of the screen such as your company logo. This image
can only be entered systemwide, and is a cross-client setting. Assuming you have the appropriate
authorization, you can find a detailed description of the necessary settings by choosing Extras →
Administration Information. Note that this image is stored in the system and transported to the SAP
Frontend every time it is called by SAP Easy Access. Although this transfer is compressed, the image for
the initial screen should not be bigger than around 20 kB. You can prevent this image being called either
by using the setting Low Speed Connection in the SAPLogon program (see SAP Note 161053), or by
switching off the calling of the image under Extras→Settings. See also User-Specific Personalization.
SAP AG 1999
Favorites
Great Transactions
SM50 - Prcoess Overview
Favorites chosen by the user
VA01 - Create Sales Order
Interesting WWW Pages reduce navigation time
URL - The Herald Tribune
URL - Time Magazine
Important Files
URL - Vacation Planning
Enjoy User Menu
URL - SAP Notes (User / PW req.)
Accounts Receivable
FD02 - Change Customer (Accountin
Materials Management
Sales and Dsitribution
Tools
SAP AG 1999
A Role describes a set of logically linked transactions in the system. These represent the range of
functions users typically need for their work.
User roles (previously “activity groups”) have to be set up using the Profile Generator so that SAP R/3
System users can work with user-specific or position-related menus.
The authorizations for the activities listed in the menus are also assigned to the users using user roles.
With Release 4.6, predefined user roles from all application areas are included in the standard system.
Users who have been assigned a user role can choose between the user menu and the SAP standard
menu.
The above screen shows the role-based user menu for a user with the name "Enjoy". You can find roles
that are supplied in the standard SAP R/3 System by choosing Other menu on the SAP Easy Access
initial screen.
Every enduser can personalize the initial screen using Favorites. You can create your own Favorites list
containing the transactions, reports, files, and Web addresses that you use most often.
You can add favorites either by choosing Favorites or by using the mouse to “drag & drop” items into
the Favorites directory.
Display Customer:
Customer: Initial Screen
System.
Procedure
When creating a customer master record, the user either enters the
City
F4 Help: Displays
Currency Possible Entries
Co... Company Name City Cur...
Restrict Number to SAP A.G. Walldorf EUR
IDES AG 1000 Frankfurt UNI
IDES Canada Toronto CAD
IDES AG Frankfurt UNI
SAP AG 1999
Implementation Guide
Glossary
SAP AG 1999
SAP R/3 Systems provide comprehensive online help. You can display the help from any screen in the
system. You can always request help using the Help menu or using the relevant icon (the yellow
question mark).
You can access the SAP Library quickly and comfortably by using the SAP Service Marketplace. There
you can find the SAP Help Portal under Knowledge and Training, where you can not only access Help
in HTML format, but can also perform efficient full-text searches in the SAP Library. If you have the
SAP Library installed, you also have, of course, these opportunities within your company.
You can access the Help Portal directly at http://help.sap.com
SAP AG 1999
Settings
SAP AG 1999
The end user has many possibilities for personalizing the system. Some are described below:
You can alter the layout of your initial screen under Extras → Settings, for example by switching off
the image in the right-hand part of the window or by turning on the option to display the technical
names (transaction codes) in the SAP Easy Access Menu.
Among other things, you can activate a quick cut and paste in the Options menu. Using Options you
can change the reaction speed of the QuickInfo that is displayed when you hold your mouse cursor
over an icon or a push button.
By following the path System→ User profile→ Own data, you can set personal standard values. You
can choose the tabs Address, Defaults, and Parameters. As an example, the setting of Parameters is
explained here:
Parameters: Here you can set defaults for frequently used input fields. In order to be able set a
default value for a field, it must have been assigned a Parameter ID.
Procedure for finding the Parameter ID: Go to the field for which you wish to set a default
value. Select the F1 help, and then choose Technical Info. The system displays an information
window that contains the relevant parameter ID under the heading Field Data (as long as the field
has been assigned a Parameter ID).
Table Settings
Choose Variants
Current setting My variant
Standard setting Basic setting
Maintain Variants
Variant
Use as standard setting
Create
Delete
Save Administrator
SAP AG 1999
Use the Table Settings function to change, in the table control, the individual basic table settings that are
supplied with the system. This is particularly useful for tables where you do not need all the columns.
You can use the mouse to drag & drop column positions and widths, or even make the column
disappear.
Save the changed table settings as a variant. The number of different variants you can create per table is
not restricted.
The first variant is called the basic setting; the SAP System defines this setting. You cannot delete the
basic setting (you can delete the variants you define yourself).
The table settings are stored with your user name. The system uses the variant currently valid until you
exit the relevant application. If you then select the application again, the system will use the standard
settings valid for this table.
Note: you can change table settings wherever you see the table control icon in the top right-hand corner
of a table.
SAP R/3 Systems offer numerous options for settings and adjustments:
Define default values for input fields
Hide screen elements
Deactivate screen elements (dimmed)
You can do this by, for example, defining transaction variants.
SAP offers GuiXT, as of SAP R/3 Release 4.6. In addition to all of the above functions, you can now:
Include graphics
Convert fields and add pushbuttons and text
Change input fields (or their F4 help results) into radio buttons
GuiXT scripts are stored on the Frontend. In accordance with local scripts (which can also be stored
centrally), the GUIXT scripts determine how data sent from the application server is displayed. These
scripts can be standard throughout a company, or they can be different for each Frontend.
NOTE: The GuiXT will support the mySAP.com Workplace only as of the end of the year 2000. This
means that until then you should use either the SAP GUI for the Windows Environment and the GuiXT
or the mySAP.com Workplace with the SAP GUI for HTML (or the SAP GUI for Java or the SAP GUI
for Windows).
SAP AG 1999
Unit: Navigation
Topic: Basic Functions
As a new user of an SAP R/3 System, you begin to navigate the system
using the menu paths and transaction codes. You also begin to access the
various types of online help.
All menu paths in the exercises refer to the SAP standard menu.
1-2 What is the maximum number of sessions (windows in the SAP R/3 System) you can have
open simultaneously? __
1-4 Help
1-4-1 If you choose Application help in the SAP Easy Access initial screen (System
menu), which area of the SAP Library does it take you to?
_________________________________________________________
1-4-2 Use F1 help on the Customer field. What is this field used for?
Write a brief summary of the business-related information.
______________________________________________________
______________________________________________________
1-4-4 Which icon do you need to use on the F1 help screen to find the parameter ID
for the Company code field?
Hint: See the notes on the slide User-Specific Personalization
______________________________________________________
1-4-5 Use F4 help on the Customer field to find the customer number for Becker ##.
To do this, use the Search term "Becker*" after calling the F4 help.
Note: ## corresponds to your assigned group number.
___________________________________________________
2-1-1 Assign a parameter value for the Company code field to your user profile.
Note: The instructor will tell you what parameter value to enter (for example
1000). For information about defaults, see the notes on the slide User-Specific
Personalization.
2-2 Defining User-Specific Settings using System → User profile → Own Data
2-2-1 In your user profile, set your logon language to the value used for the course.
2-2-2 In your user profile, set the decimal notation and date format of your choice.
2-3-1 Insert at least one new folder under the Favorites folder.
2-3-2 Add any two of your favorite transactions to the corresponding folders.
2-3-3 Add the Internet address http://www.sap.com with the text SAP Homepage.
2-4-1 Enter a transaction of your choice as the initial transaction. You will then need
to log off and on again for the change to take effect.
Note: If desired, you can change the initial transaction back to the default value
simply by deleting the transaction code that you entered.
Unit: Navigation
Topic: Basic Functions
1-1 Log on to the system specified by the instructor and change your initial password.
1-2 To open and close sessions, choose System → Create session (or use the appropriate
icon) or System → End session.
The maximum number of sessions you can have open simultaneously is six (6),
depending on your system settings.
1-3 To find the transaction code, choose System → Status. These function names and
transaction codes correspond to the menu paths:
1-3-1 Transaction: SM04 for Function Name: User list
1-3-2 Transaction: FD03 for Function Name: Display Customer: General Data
1-4 Help
1-4-1 The section of the unit Getting Started that deals with using SAP Easy Access
is displayed.
1-4-2 Suggestion: The customer is a unique key (account number) used to clearly
identify the customer within the system.
1-4-3 FI – Accounts Receivable and Accounts Payable
1-4-4 To find the Parameter ID: BUK, choose Technical Info
1-4-5 Customer ## (## corresponds to your assigned group number)
When you select F4 in the Customer field, the Restrict Value Range window
appears. You can explore the various tabs to see the different search criteria
available. Find a tab that includes the Search term field and enter the
following:
2
Course Overview
Contents:
Curriculum Progression
Course Goals
Course Objectives
Course Content
Course Overview Diagram
Main Business Scenario
Getting Started
SAP AG 1999
IMG
Global Settings
Countries
Currencies
Calenda rs
SAP AG 1999
SAP AG 1999
SAP AG 1999
Preface
Appendix
SAP AG 1999
CO
Balance sheet
... ...
P&L
...
SAP AG 1999
The general ledger contains a record of all relevant accounting transactions from a business point of
view in the G/L accounts. In order to retain a clear overview, the general ledger often contains collective
postings. In such cases, the information posted is displayed in more detail in the subsidiary ledgers,
which provide their information to the general ledger in summarized form:
Accounts Payable records all accounting transactions for dealings with suppliers. Much of its data is
obtained from procurement (Materials Management).
Accounts Receivable records all accounting transactions for dealings with customers. Much of its
data is obtained from Sales and Distribution.
Asset Accounting records all accounting transactions relating to the management of assets.
Travel Management manages and calculates travel costs and supports travel planning and travel
expenses
Bank ledger supports the posting of cash flows.
All G/L account postings that post to business expense accounts automatically send the expenses as costs
to Controlling. The balances of G/L accounts are used to calculate financial statements.
SAP AG 1999
SAP
System
Hardware Clients
Delivery client
(000 & 001)
Production client
(for example, 100)
Test client
(for example, 999)
Training client
(for example, 400)
SAP AG 1999
Clients are used to divide data in a SAP System into various data areas for various purposes. If a
company, for example, wants to use its SAP System for both test and training purposes, a client is
created for each purpose.
A client is identified via a three character code. Data can be moved via transports and corrections from
one client to another.
When logging on to the system, the user has to select a client in which he/she wants to work. The user
can then only access data in this client.
EC
Enterprise Controlling
TR FI CO
Cash
management Overhead cost
and forecast General accounting
Ledger
Treasury Accounting Product cost
Management accounting
Subsidiary
Cash Profitability
ledgers
Management analysis
Investment Project
IM PS RE Real Estate
Management System
SAP AG 1999
Various financial applications offer different views of the financial position and performance of a
company and allow various control levels.
FI Financial Accounting
CO Controlling (Managerial accounting)
TR Treasury
IMInvestment Management
EC Enterprise Controlling
RE Real Estate
PS Project System
In this course, you learn primarily about the application component FI.
Journalists
Media Banks
Tax Shareholders Legal
authorities authorities
Insurance
Financial
Auditors analysts
Executive officers
Administrative Senior
staff management
Accountants Employees
SAP AG 1999
Content:
Organizational Elements for Financial
Statements
G/L Account Master Records
Accounting Transactions within a Period in
General Ledger Accounting
SAP AG 1999
SAP AG 1999
CO
Balance sheet
... ...
P&L statement
...
SAP AG 1999
The general ledger contains a record of all relevant accounting transactions from a business point of
view in the G/L accounts. In order to keep a clear overview, the general ledger often only contains
collective postings. In such cases, the information posted is displayed in more detail in the subsidiary
ledgers, which provide their information to the general ledger in summarized form.
SAP AG 1999
Presentation:
SAP AG 1999
Independent Company
=
accounting code
entity
SAP AG 1999
A company code is an independent accounting entity (the smallest organizational element for which a
complete self-contained set of accounts can be drawn up). An example is a company within a corporate
group. It has a unique, four character key.
The general ledger is kept at the company code level and is used to create the legally required balance
sheets and profit and loss statements.
A company code designation is required for every financially based transaction entered into R/3. This is
done either manually or automatically by deriving the company code from other data elements.
Paris / France
Barcelona / Spain
SAP AG 1999
IDES operates worldwide and has subsidiaries in North America, Europe, and Asia. Each affiliate
(company code) is a business entity that is required by law to provide financial records according to
country-specific regulations.
2200 France
2300 Spain
SAP AG 1999
The affiliates of IDES are set up as company codes in the R/3 system and are uniquely identified by
four character codes. Each company code has a local currency. Amounts posted in foreign currencies are
automatically converted to the local currency.
The worldwide implementation of R/3 Financial Accounting was quite problem-free since the standard
system came complete with country-specific templates for the countries in which IDES operates.
Plant
construction = 2000 Plant
construction
SAP AG 1999
The business segments or branches in which a group operates can be set up in the R/3 System as
business areas. They provide an additional evaluation level for the purpose of segment reporting, for
example.
2200 France
2300 Spain
1000
1000 Machinery
Machinery 2000
2000 Plant
Plant constr.
constr. 3000
3000 Automotive
Automotive
SAP AG 1999
Business areas are generally company-code independent, that is, you can make postings to them from
any company code.
On the slide, you can see three business areas of the IDES group. If certain company codes are not active
in specific business areas, you can use a validation to prevent postings to this business area from the
company codes specified.
Presentation:
Charts of accounts
Account groups
Financial statement
versions
Reconciliation accounts
SAP AG 1999
SAP AG 1999
Each general ledger is set up according to a chart of accounts. The chart of accounts contains the
definitions of all G/L accounts in an ordered form. The definitions consist mainly of the account number,
account name, and the type of G/L account, that is, whether the account is a P&L type account or a
balance sheet type account.
You can define an unlimited number of charts of accounts in the R/3 System. Many country-specific
charts of accounts are included in the standard system.
Chart of
accounts
SAP AG 1999
For each company code, you have to specify one chart of accounts for the general ledger. This chart of
accounts is assigned to the company code. A chart of accounts can be used by multiple company codes
(see diagram). This means that the general ledgers of these company codes have the identical structure.
INT
Account definition
in chart of accounts
Account X
PLUS PLUS
CC 1000 CC 3000
Before you can use an account in a company code, you have to maintain the account definition at the
chart of accounts level. You then create company code-specific settings, which are only valid in the
company code. An example of a company code-specific setting is defining the account currency. Most of
the accounts in company code 1000 use the UNI currency, whereas company code 3000 uses USD for
most of its accounts.
Cash
accounts
Cash
000000-099999 Company code specific
C settings
General ledger
100000-199999
Asset
200000-299999 Account definition
in chart of
Material
300000-399999 accounts
P/L
400000-499999 Account groups Account 001111
Cash
Liab. unt
000000-099999 Acco
500000-599999
up
gro
...
600000-699999
SAP AG 1999
In order to organize and manage a large number of G/L accounts better, they are arranged in account
groups.
The accounts of an account group normally have similar business functions. You could, for example,
have an account group for cash accounts, one for expense accounts, one for revenue accounts, and one
for other balance sheet accounts, etc.
Customers
Vendors
Assets
Subsd. ledger
ledgers
accounts
aa bb
SAP AG 1999
Reconciliation accounts connect subsidiary ledgers with the general ledger in real-time. This means
that a posting to a subsidiary ledger also posts to the corresponding reconciliation account in the general
ledger at the same time.
The subsidiary ledgers which are connected to the general ledger via reconciliation accounts are the A/P,
A/R, and asset ledgers.
G/L account
1000
1000 Transaction figure / Transaction figure /
Mechanical engineering
Mechanical engineering debit credit
2000
2000 Transaction figure / Transaction figure /
Plant
Plant engineering
engineering debit credit
3000
3000 Transaction figure / Transaction figure /
Automotive
Automotive debit credit
SAP AG 1999
A transaction figure is the total of all debit or credit postings. In general, the R/3 System keeps one
transaction figure for debits and one transaction figure for credits per account. The financial statements
for the company code are calculated using these transaction figures.
If using business areas, transaction figures are also kept per business area (see diagram). If you create a
financial statement for the business area, the transaction figures for that specific business area are used to
supply the information for the financial statements.
SAP AG 1999
A general ledger is kept in order to provide the information needed to create a balance sheet and a profit
and loss statement. These reports have to meet country-specific requirements, that is, IDES, for example,
would need to create financial statements based on HGB (German standard) for company code 1000
(Germany) and based on US-GAAP for company code 3000 (USA).
To meet the various reporting requirements, various financial statement versions have be created in the
R/3 System. In these financial statement versions, you define exactly which accounts are to appear in
which line items of the financial statement. Many financial statement versions are included in the R/3
Standard System.
When running financial statement reports, you select a financial statement version that contains the
details of the report structure.
Financial
statement
per IAS Valuation
per IAS
1000
Germany
Valuation
Financial per US-GAAP
statement
per US-GAAP
SAP AG 1999
For many companies, it may be necessary to create additional financial statements based on standards
other than country-specific requirements, such as IAS or US-GAAP. Reasons for this could be:
To gain access to international capital markets
To meet the needs of foreign investors
To accommodate global restructuring and acquisitions
To provide a better overview of the company’s position
Parallel accounting methods can be carried out in the R/3 System by:
Using different valuation methods with post to different G/L accounts
Using these G/L accounts in various financial statement versions
Presentation:
Präsentation:
Accounting
Innerperiodische Transactions
Geschäftsvorfälle Within a
in der Hauptbuchhaltung
Period in G/L Accounting
Enjoy - G/L Account Postings
Account Status
Standard/Complex Postings
SAP AG 1999
Header Information
information area
Work
templates
SAP AG 1999
Beginning with Release 4.6 (Enjoy Release), you can comfortably create and post a G/L account
document using a one-screen transaction. The entry screen is divided into the following areas:
Work templates (here, you can select creation variants, account assignment templates, or marked
documents as references)
Header data (here, the data for the document header is compiled)
Line item information (here, the line items for the document are entered)
Information area (here, the debit and credit totals are displayed)
Document
header entry
Order of screens
1. Item screen
Entry of
Access to
first
First line item
doc. line item
Entry of
Access to
second
second line item
line item
additional
Access to
line item
third line item screens
SAP AG 1999
Complex or general postings in Release 4.6 correspond to the old, more difficult to use standard
posting transaction FB01.
Since not all of the posting transactions were revamped for Release 4.6, it is often still necessary to have
a good command of the general/complex posting method.
In the initial screen, you enter the data for the document header. Additionally, you enter the posting
key and the account for the first line item. The posting key provides the system with information
regarding the account type (G/L account, customer, vendor, asset, material) and determines the layout
of the entry screen for the line item.
With this information, the entry screen for the first line item is set up. You enter the data for the first
line item and access the next screen by entering the posting key and account for the next line item.
In the next screen, you enter the information for the second line item and continue to the next line
item(s) as needed in the same manner.
DG
DR
en
SA
DZ
invoi
ce credi
tm
paym
en docum
or
Vend
or Vend ices
or or vo
Vend s t Vend ts net in dit
credi s
KG
KN
KR
KZ
ce en re
invoi mem
o paym and c
os
mem
SAP AG 1999
In order to distinguish between the various FI documents, document types are used. Each document is
assigned to one document type, and this is entered in the document header. Document numbers are
provided by the document number ranges assigned to one or more document types.
For G/L account postings, document type SA is used, although other document types are possible (such
as accrual/deferral documents, valuation documents, and so on).
Detail view
SAP AG 1999
Each document line item contains one posting key. This is an instrument that is used for internal control
and is used during complex postings to tell the system:
The account type to be posted
Whether it is a debit or credit posting
Which fields of the line item may have or require an entry
In the new Enjoy transaction, you no longer need to enter the posting key. It does, however, appear in
the document and its control functions are still relevant.
SAP AG 1999
In the R/3 System, there are a large number of standard posting keys which should be used. Each
posting key is used for postings to a certain side of accounts of certain account types.
For postings in the general ledger, you only need two posting keys:
40 for debit items
50 for credit items
Account 100000
Line item list Optically
January 100000+ archived
February 400000+
March 300000- Account 100000
April 100000+ 1.3.2000 400000-
... ... 10.3.2000 300000- Optional
12.3.2000 100000+
15.3.2000 500000+
18.3.2000 200000+ Document
20.3.2000 200000-
25.3.2000 200000-
03/18/2000
Line items
01 100000 200000-
02 113100 200000+
SAP AG 1999
For account information, balance display and line item display are available. They are separate from
each other, but can be used in connection with each other.
The balance display is an overview of the saved transaction figures of an account. You can drilldown
from the transaction figure to a list of the list items that make up the transaction figure.
From this line item list, you can drilldown from the line item to the document containing this line item.
If there is an original document for this R/3 document, and if it was archived optically, you can display it
as well.
SAP AG 1999
SAP AG 1999
SAP AG 1999
Check that the default entries are correct and remove the alternative account
number.
Save the account.
Select "Expand subtree" (second icon from the left on the pushbutton bar).
The financial statement version is expanded completely. With the "Find"
button, search for account 70000 (Ordinary Share Capital). The account is
found under the financial statement item "Subscribed capital".
Select "Subscribed capital" and choose the "Assign accounts" button. Insert the
interval of 700## to 700##.
Continue.
Save the financial statement version.
Basic data:
Field name or data type Values
Document date Today's date
Posting date Today's date
Continue
Basic data:
Field name or data type Values
Short text Increase in capital ##
Continue
1. Item
Field name or data type Values
G/L account 700##
D/C Credit
Doc. currency amount 200000
Business area BA##
2. Item
Field name or data type Values
G/L account 78200
D/C Debit
Doc. currency amount 200000
Business area BA##
Select the post button.
Document Display
PK: Posting key_______________________________________
40: Posting key for debit postings in general ledger
50: Posting key for credit postings in general ledger________________
You see a balance of 200000 UNI because you have limited the selection your
own business area BA##. All other groups posted to different business areas.
Since the transaction figures are kept per business area, you can view the
account balance for your business area.
To view the total balance for all business areas, choose "Other business area"
and select "All business areas".
Contents:
SAP AG 1999
SAP AG 1999
CO
Balance Sheet
... ...
P&L
...
SAP AG 1999
Accounts Payable records all accounting transactions for dealings with vendors. Much of its data is
obtained from purchasing (Materials Management).
Presentation:
SAP AG 1999
Con-
trolling
area
Chart of
accounts
SAP AG 1999
The controlling area identifies a self-contained organizational structure for which costs and revenues
can be managed and allocated. It represents a separate unit of cost accounting.
One or more company codes can be assigned to a controlling area, which enables you to carry out cross-
company code cost accounting between the assigned company codes. However, this is only possible if
the assigned company codes and the controlling area all use the same operating chart of accounts.
6000 5000
Mexico Asia
1000
Europe
6000 5000
Mexico 2000 2300 Japan
United Kingdom Spain
2000
3000 France
America
1000 2100
Germany Portugal
1000
Europe
INT
SAP AG 1999
It was particularly important to the IDES board of directors that the European company codes, Germany,
United Kingdom, Portugal, and Spain, all belong to the same controlling area, since a great deal of
activity takes place between these company codes. Therefore, all four company codes had to adopt the
operating chart of accounts (INT) of the controlling area. However, in order for it to be possible for
external reports to contain the account numbers usually used in the individual countries, a country-
specific chart of accounts was created for the company codes Germany, the United Kingdom, and Spain.
These country-specific charts of accounts meet the requirements of the separate countries.
INT CAUS
SAP AG 1999
The two companies in North America were originally independent firms but were purchased by the
IDES group. Both companies were already live with R/3 and were using the chart of accounts CAUS as
the operating chart of accounts
Management determined that cost accounting for Europe and the USA together is not necessary. For this
reason, management decided to retain the operating chart of accounts CAUS for the two U.S. company
codes and to assign them to a separate controlling area.
For consolidation purposes, a group chart of accounts was set up for the two operating charts of
accounts.
Internal orders
Make-to-order
sales orders
SAP AG 1999
A controlling area contains CO objects that take on various functions within Controlling, such as:
Internal orders
Cost objects
Networks
Projects
Cost centers
Make-to-order sales orders
A distinction is made between true and statistical CO objects:
True objects can allocate their costs to other CO objects.
Statistical objects cannot reallocate their costs and only bear their costs for information purposes.
Presentation:
SAP AG 1999
Vendor X
Account definition
General at client level
data
PLUS PLUS
CC 1000 CC 2000
Vendor
accounts
Vend.
000000-099999
C
Company code
Accounts Payable
100000-199999
data
Dom.
200000-299999
General Purchasing
data organization
For.
300000-399999
data
One-time
400000-499999
0001
500000-599999
Account groups Account 001111
Vend. t
un
... 000000-099999 Acco
oup
600000-699999 gr
SAP AG 1999
In the same way as G/L accounts, vendor accounts can be combined in various account groups, so that
they can be organized and managed more easily.
The accounts in an account group usually have similar characteristics. For example, you could have one
account group for domestic vendors, one for vendors abroad, one for affiliated vendors, and one for one-
time accounts.
Presentation:
SAP AG 1999
Information
Header and area
vendor data
Templates
SAP AG 1999
Since Release 4.6 (Enjoy Release), you can easily create and post a vendor invoice or credit memo
using a one-screen transaction. The entry screen is divided into the following areas:
Work templates (here, you can select creation variants, account assignment templates, or held
documents as references)
Header and vendor data (document header and vendor line item data is entered here)
Line item information (the line items for the document are entered here)
Information area (the document balance and information about the vendor is displayed here)
This transaction can also be used to create documents in foreign currency. The foreign currency amount
is translated into local currency using defined exchange rates.
Statistical CO object
Debit
Cost element Amount
SAP AG 1999
When entering an expense item for an operating expense, you must also enter one true CO object. This
means that when the item is posted, a CO document is created as well as an FI document. The CO
document posts the costs corresponding to the expense to the true CO object.
As well as the true CO object, you can also enter additional statistical CO objects to which the costs are
statistically posted (which means they are "not allocatable").
Actual posting
Next posting
on 03.01.XX
Expense Vendor
1000 1000
SAP AG 1999
For postings that recur on a regular basis, such as payments for rent or interest, legal fees, and property
taxes, you can use the recurring entry program to have the necessary documents generated
automatically.
The recurring business transactions must be stored in the system as recurring entry original documents
for this to be possible. Each recurring entry original document contains the date of the first and last
posting, the frequency at which posting should be made, and the date of the next planned posting.
The recurring entry program must be started at regular intervals within a specified period. The
program selects all recurring entry original documents in which the date of the next posting falls
within the specified period, and then generates a batch input session.
When the session is processed, an FI document that corresponds to the original document is posted,
and the date of the next posting is changed accordingly in the recurring entry original document.
Expend. Vendor
10 10 10 Post payment document
Manual Automatic
SAP AG 1999
SAP AG 1999
The payment program was developed for international payment transactions with customers and
vendors, and can be used for both incoming and outgoing payments. However, it is more commonly
used for outgoing payments.
The automatic payment process comprises several stages.
The first stage involves maintaining the parameters. You use the parameters to define which accounts
and items the payment program is to include in the automatic payment run.
SAP AG 1999
The second stage is the proposal run. During the proposal run, the system:
Checks the accounts and documents specified in the parameters for due items
Groups due items for payment
Selects the relevant payment methods, house banks, and partner banks
SAP AG 1999
The third stage involves checking and editing the payment proposal. This step can be omitted, but you
are advised to check that the data is accurate before actually running the payment program.
SAP AG 1999
SAP AG 1999
Presentation:
Presentation:
Integration with Materials Management
Integration with Materials Management
Plants
Purchasing organizations
MM view of the vendor master record
Purchase order, goods receipt, invoice
verification
SAP AG 1999
CC 1000
IDES Germany
Plant 1000 Plant 1100 Plant 1200 Plant 1300 Plant 1400
Hamburg Berlin Dresden Frankfurt Stuttgart
SAP AG 1999
The central organizational object in Logistics in the plant. Multiple plants be contained in a company
code. That is, they are assigned to the same company code.
IDES company code 1000 (Germany) contains, for example, the plants:
1000 (Hamburg)
1100 (Berlin)
1200 (Dresden)
1300 (Frankfurt)
1400 (Stuttgart)
All company-code relevant transactions from these plants are posted in company code 1000.
Plant 1000 Plant 1100 Plant 1200 Plant 1300 Plant 1400
Hamburg Berlin Dresden Frankfurt Stuttgart
SAP AG 1999
Purchasing for the plants is completed by the purchasing organization. Each country, in which IDES
plants operate, has one purchasing organization. They purchase for all plants in the country and post the
purchases in the company code of that country.
In Germany, for example, purchasing organization 1000 takes care of purchasing for all German plants
(Hamburg, Berlin, Dresden, Frankfurt, Stuttgart). Postings are made in German company code 1000.
Vendor X
Account definition
General
data
at client level
PLUS PLUS
PO 1000
CC 1000
The purchasing organizations purchase goods and services from suppliers, who are paid by accounts
payable. The various purchasing organizations of the group have to enter data specific to purchasing in
the vendor master record before the supplier's master record can be used.
Goods receipt
Material stock or
Material
Purchase order
Document consumption
document Line items
Material
MM Goods GR/IR
1
Purchase receipt
order
MM FI
Order
GR/IR
amount 2 1
FI
Invoice receipt
No document
Invoice Document
verification Line items Vendor
document GR/IR
Vendor
Tax 2
MM FI
SAP AG 1999
The three-step verification is the standard procedure for posting procurement transactions in FI. The
procedure contains the following three steps:
Creating a purchase order
This transaction is completed in MM. No postings are made in FI.
Goods receipt
To update the inventory, a material document is created in MM. At the same time, a document is
created in FI, with which the value of the goods is posted to the materials account (debit) and the
goods receipt/invoice receipt account (credit) in the general ledger.
Invoice receipt
The vendor invoice is posted in MM, which automatically creates a document in FI. The FI document
contains the invoice amount that is posted to the goods receipt/invoice receipt account (debit) and the
vendor account (credit).
The last two steps can be completed in reverse order, depending on the order the goods and the invoice
are received.
The goods receipt/invoice receipt account ensures that goods were received for each invoice and vice
versa.
Presentation:
Presentation:
Closing
ClosingOperations in Accounts
Operations in Accounts Payable
Payable
Overview: Accounts Payable closing operations
Balance confirmations
Foreign currency valuation
Reclassification of payables
SAP AG 1999
Time line
SAP AG 1999
Accounting Vendors
Balance confirmations
Letter
Reply
Lists
Reply
Check
list
Results
table
Checkpo
int
SAP AG 1999
The program for creating balance confirmations creates the balance confirmations including reply
requests for a freely definable number of vendors, a reconciliation list, and a results table. The balance
confirmations and reply requests are sent to the vendors; the lists are used as a control measure. For
IDES, this control is carried out by the internal audit department.
The vendors check the balance information they receive and send their replies to the control center audit
department), which compares the replies with the reconciliation list and enters the results in the results
table.
Adjustment account
Vendor
500 USD
1000 UNI
SAP AG 1999
500 USD
1000 UNI
Adjustment account
Vendor
100 UNI
500 USD
1000 UNI
Valuation
difference
100 UNI
SAP AG 1999
A foreign currency valuation is necessary if vendor accounts contains open items in a foreign
currency. The amounts of these open items were translated into the local currency at the time they were
entered using the current exchange rate (for example, 500 USD to 1000 UNI, the local currency).
The exchange rate is probably different at the time of closing, and open items need to be valuated again.
A program valuates the open items using the new exchange rate and enters the valuation difference (100
UNI on the slide) in the valuated line items. It also creates the valuation postings:
Expense from valuation to adjustment account (see slide)
or
Adjustment account to revenue from valuation
A valuation cannot be made by posting to the payables account, since reconciliation accounts cannot be
directly posted to. For this reason, the amount is posted to an adjustment account, which appears in the
same line of the balance sheet as the reconciliation account.
A valuation method determines how the individual line items are valuated. This has to be set up in
conjunction with the country-specific valuation regulations. It defines, for example, whether the lowest
value principle, the strict lowest value principle, or a general principle (also with revenue from the
valuation) is to be used for valuation.
RT >5 years
SAP AG 1999
RT >5 years
SAP AG 1999
RT >5 years
SAP AG 1999
RT >5 years
4000
SAP AG 1999
Payables and receivables have to be listed separately in the balance sheet. Since it is possible for some
vendors to have a debit balance, these accounts need to be changed to vendors with a debit balance prior
to creating the financial statements.
In many countries it is also required to group payables in the balance sheet based on their remaining life.
This also makes it necessary to regroup payables.
Both regroupings are carried out using a special program. At the same time, these regrouping are
removed for the first day of the next period, since regrouping are not necessary for daily processing.
On the slide, you can see that the receivables with long remaining terms have be reposted to different
accounts to facilitate the creation of the financial statements. Additionally, vendors with a debit balance
are regrouped. An adjustment account is used as the offsetting account here as well, since adjustments
cannot be posted directly to a reconciliation account.
Note: The foreign currency valuation as well as the regrouping can be completed in different ways to
meet various legal requirements. The results are then posted to various accounts that are used by
different financial statement versions.
SAP AG 1999
SAP AG 1999
It is important that you use only the recurring entry documents for
your own user, AC010##, so that each group can carry out its own
recurring entries.
Warning: Process only the session that you have created yourself.
SAP AG 1999
To access Purchasing:
Logistics Materials Management Purchasing
Check whether a flat screen has actually been ordered and that the cost center
CC## and the business area BA## have been debited for it.
(C) SAP AG AC010 11-135
Write down the purchase order number.
______________________________________________________
SAP AG 1999
For the purposes of the following exercises, we will assume that the closing procedures have
already been completed for the previous month.
G/L Accounting:
Account Display balances
SAP AG 1999
Save
Basic data
Field name or data type Values
Vendor AGENCY##
Continue
Basic data
Field name or data type Values
Invoice date Yesterday’s date
Posting date Today’s date
Continue
The master record of the vendor is displayed on the upper right hand side of the
screen.
In the left column, select the "with cost center" screen variant.
Line items
Field name or data type Values
G/L account 470000
D/C Debit
Doc. currency amount 4000
Tax code 1I
Cost center CC##
Post by choosing the Save icon.
A message should appear in the status bar, informing you that session
SAPF120-## has been created. If this message does not appear, one of the
following has happened:
• The recurring entry original document was not created correctly
• Your selections for the recurring entry program were incorrect
• Another group has generated your recurring entry
On the overview screen, select the session SAPF120-## and enter your user,
AC010-##, in the “Created by” field. Choose “Process”.
Select the run mode “Visible”, choose process in the dialog box.
Now observe how the system enters values from the session on a sequence of
screens. Accept each screen by choosing “Continue” (enter).
At the bottom of the screen, you see all the due and non-due items ordered by days.
The column on the left contains the characteristics you can use to restrict the display. If
you select the characteristic “Vendor”, for example, a list of all vendors and the totals
of each of their due and non-due open items is displayed on the right.
To access Purchasing:
Logistics Materials Management Purchasing
To display the items, choose the pushbutton next to “Item overview”. Select the
item and choose “Select purchase order item”. You can check the account
assignment on the “Account assignment” tab page.
Save
Write down the purchase order number; you will need this number later.
Execute
Basic data
Field name or data type Values
Vendor AGENCY##
Continue
Basic data
Field name or data type Values
Invoice date 15th of the previous month
Posting date Last day of the previous month
Continue
A warning appears, informing you that a posting is being made to the previous
period. Confirm this message by pressing “Enter”.
The master record of the vendor is displayed on the upper right hand side of the
screen.
Basic data
Field name or data type Values
Amount 5000 USD
Tax amount 0 (tax code 0I – no input tax)
Reference 2##
In the left column, select the "with cost center" entry variant.
Line items
Field name or data type Values
(C) SAP AG AC010 11-163
G/L account 470000
D/C Debit
Doc. currency amount 5000
Tax code 0I
Cost center CC##
Post
Execute
Basic data
Field name or data type Values
Vendor AGENCY##
Continue
Basic data
Field name or data type Values
Invoice date 15th of the previous month
Posting date 15th of the previous month
Continue
A warning appears, informing you that a posting is being made to the previous
period. Confirm this message by pressing “Enter”.
The master record of the vendor is displayed on the upper right hand side of the
screen.
(C) SAP AG AC010 11-165
Basic data
Field name or data type Values
Amount 6000 UNI
Tax amount 0 (tax code 0I – no input tax)
Reference 3##
In the left column, select the "with cost center" entry variant.
Line items
Field name or data type Values
G/L account 470000
D/C Debit
Doc. currency amount 6000
Tax code 0I
Cost center CC##
Post.
Confirm any warning messages by pressing enter.
Menu:
System Services Batch input Sessions
The transaction figures show that 6000 UNI were posted to this account for the
last period. This is your regrouping for the purpose of creating the financial
statement. You can also see that the 6000 UNI were charged off again in the
current period.
Contents:
Organizational Structures of Revenue Controlling
Master Data in Accounts Receivable
Daily Accounting Transactionsin Accounts
Receivable
Integration with Sales and Distribution
Credit Management
Closing Operations in Accounts Receivable
SAP AG 1999
SAP AG 1999
CO
Balance Sheet
... ...
P&L
...
SAP AG 1999
Accounts Receivable records all accounting transactions related to business with customers. Much of its
data is obtained from Sales and Distribution.
SAP AG 1999
Presentation:
Presentation:
The
The Organizational
Organizational Structures
Structures of Sales of
Revenue Controlling
Revenue Controlling
Operating
concern
Profitability
segments
SAP AG 1999
Operating
Concern
Co
st s
Con- Con-
trolling trolling
area area
Re
ve
nu
e
Company code
SAP AG 1999
An operating concern is the central organizational structure in profitability analysis. Each operating
concern represents an area in which a market (or customer-defined) segment of a business can be
monitored and its profitability analyzed.
A corporate group usually only requires one operating concern. This operating concern is assigned to all
existing controlling areas that assign their costs to that operating concern. Revenues are assigned directly
to the operating concern from FI.
IDES also uses only one operating concern, to which all the controlling areas in the whole corporate
group are assigned. This enables IDES to carry out international market and profitability analyses.
Profitability analysis
for profitability
segment
Divisions
s e
Profit-
tri
un
ability
segment
Co
Distribution channels
Characteristics
SAP AG 1999
The operating concern is divided into individual market segments for which profitability analyses can be
carried out. These market segments are known as profitability segments. The profitability segments are
defined using characteristics selected by the user.
The IDES operating concern uses the following characteristics to define its profitability segments:
Customer
Sales organization
Distribution channel
Division
Product
Strategic business unit
Sales district
Country
Presentation:
Presentation:
Master Data in Accounts Receivable
Master Data in Accounts Receivable
SAP AG 1999
Customer X
Account definition
General
at client level
Data
PLUS PLUS
CC 1000 CC 2000
As with G/L accounts and vendor accounts, customer accounts are also made up of two areas:
A customer account is defined for all company codes as client level. General data, such as the
customer's address, is also stored here.
Postings cannot be made to the account in a company code until company code-specific settings have
been made, such as the agreed terms of payment.
Customer
accounts
Accounts Receivable
Cust
000000-099999
C
100000-199999
Company code
Dom. data
200000-299999
One-time
400000-499999
0001
500000-599999
Account groups Account 001111
Cust
... unt
000000-099999 Acco
600000-699999
oup
gr
SAP AG 1999
In the same way as G/L accounts and vendor accounts, customer accounts can be combined in various
account groups, so that they can be organized and managed more easily.
The accounts in an account group usually have similar characteristics. For example, you could have one
account group for domestic customers, one for customers abroad, one for affiliated customers, and one
for one-time accounts.
Presentation:
Presentation:
Daily Accounting
Daily Accounting Transactions
Transactions in
in Accounts Receivable
Accounts Receivable
Invoices, credit memos
Payment differences
Automatic dunning
Correspondence
SAP AG 1999
Information
Header and area
customer data
Templates
SAP AG 1999
Almost all customer invoices and credit memos reach Accounts Receivable via the integrated SD
module, but it is also possible to use the Enjoy transaction for invoice/credit memo entry in
exceptional cases. The entry screen is divided into the areas:
Work templates (here, you can select creation variants, account assignment templates, or held
documents as references)
Header and customer data (document header and customer line item data is entered here)
Line item information (the line items for the document are entered here)
Information area (the document balance and information about the customer is displayed here)
This transaction can also be used to create documents in foreign currency. The foreign currency amount
is translated into local currency using defined exchange rates.
Note: When entering revenue line items, you must also enter a profitability segment to which the
revenues are posted, so that the profitability analysis is carried out for that segment.
Complete payment
Customer Customer
Partial
8000 5000
payment 8000 5000
Residual
Invoice reference 3000
item
to open item
SAP AG 1999
Incoming payments can be dealt with in a number of ways in different companies and countries. This
subject is described in greater detail in the "Bank Accounting" unit. However, incoming payments are
basically posted as shown on this slide:
If the customer pays his or her open items to the full amount, or with an authorized deduction of cash
discount, the items are cleared.
If a minor payment difference exists, this can be charged off automatically. The maximum amount
that constitutes a minor payment difference is defined in your system settings.
Any greater payment difference must be dealt with manually. There are two methods of posting
underpayments:
Partial payment: A new open item in the amount of the payment is created on the credit side, and
an invoice reference is created to the open invoice.
Residual item: The open invoice is cleared and a new open item (residual item) in the amount of
the payment difference is created.
4
3
2 Calculating dunning levels
1
..........
.......... Managing dunning history
..........
The R/3 System provides you with a tool that automatically analyzes all the open items and duns any
items that are overdue. The system determines a dunning level, which is in accordance with the number
of days in arrears. The dunning level determines which dunning charges and interest are charged, as well
as which dunning text is selected. A dunning history keeps a record of which dunning notices have been
issued.
You can trigger automatic dunning for a single account (individual dunning notice), or you can have
the dunning program carry out automatic dunning for a selected number of accounts.
Customer Correspondence
Company code
Dunning data
Dunning procedure 0001
Dunning
procedure
SAP AG 1999
Dunning is controlled by the dunning procedure. A dunning procedure must be entered in every
account that is to be included in automatic dunning.
A dunning procedure that is valid for one-time customers is entered in one-time accounts.
You can define as many different dunning procedures as you wish. The R/3 System comes with a
number of standard dunning procedures that can be used as a template for additional procedures.
SAP AG 1999
You can specify how the dunning run is to be executed by entering parameters in the dunning program.
You can use the parameters of an existing dunning run as a template and adjust the dates to meet your
requirements. Typical parameters are the company codes and accounts that are to be included in the
dunning run.
SAP AG 1999
During the dunning run, accounts are selected and checked for overdue items. The system then checks
whether dunning notices should be sent and assigns the relevant dunning levels. All dunning data is
stored in a dunning proposal.
SAP AG 1999
The dunning proposal can be edited, deleted, and recreated as often as required until the accounting
clerk is satisfied with the result.
This step can be omitted. Dunning notices can be printed as soon as the dunning run is finished.
SAP AG 1999
In one step, the system prints the dunning notices and updates the dunning data in the accounts and
documents, which is to say that the dunning dates and levels are entered in the documents and accounts.
Correspondence requests
Corre-
spond-
ence
requests
Trigger program
Print programs
SAP AG 1999
Correspondence relating to daily business first has to be requested before it can be printed. A
correspondence request can be carried out in the following ways:
Automatically when special transactions, such as bill of exchange charges (bill of exchange charges
statement) or payment differences (payment notice) are posted.
Manually by the accounting clerk
Using a request program that creates a high volume of correspondence requests simultaneously
(periodic account statements, internal documents, standard letters)
Requested correspondence is stored in a correspondence request table and can be printed via a trigger
program.
Payment history
Currency analysis
Overdue items
DSO analysis
Terms offered/
Display terms taken
evaluations
Create
evaluations
SAP database
SAP AG 1999
The Accounts Receivable information system enables you to carry out quick analyses of important
accounting data, such as:
Due date breakdown
Customer payment history
Currency risk for customers abroad
Overdue items
Number of days ("DSO days") that a customer takes on average to pay an invoice
Customer cash discount history (terms offered/terms taken)
These analyses are based on preselected datasets (views) that have to be generated or updated at regular
intervals by means of a background run from the SAP database.
Note 1: Accounts Payable contains an Accounts Payable information system that is structured in the
same way.
Note 2: You can use the account analysis evaluations to analyze individual customer accounts.
Presentation:
Presentation:
Integration withwithSales
Integration and
Sales and Distribution
Distribution
SAP AG 1999
Distribution channel
16 — Factory sales
SAP AG 1999
The sales organizations are legally responsible for sales in R/3. One company code may contain several
sales organizations. The IDES company code 1000 includes the sales organizations 1000 (Frankfurt) and
1020 (Berlin), for example. This means that any accounting-relevant transactions in either of these sales
organizations are posted in company code 1000.
Each sales organization can use different distribution channels to sell goods. In principle, a distribution
channel can also be used by two different sales organizations. Distribution channels used by IDES are:
Final customer sales
Resellers
Service
Factory sales
Store chains
Industrial customers
Pharamceutical customers
The combination of a sales organization and a distribution channel is also known as a distribution
chain.
SAP AG 1999
Distribution chains sell goods from the plants. Both of the IDES distribution chains, 1000-10 and 1000-
12, sell goods from the IDES plant in Hamburg and post the sales in IDES company code, 1000, which
is also assigned to the plant.
Divisions
Division 02 —
Motorcycles
Division 03 —
Paints
Material
Division 05 —
Foods
SAP AG 1999
Materials are divided into divisions in the R/3 System so that a large volume of different materials can
be managed and processed more efficiently. The IDES group uses the divisions motorcycles, paints, and
foods, for example.
Divisions
Sales organization
A
AA 1000 — Frankfurt
Sales area 1000
Distribution channel — 10 — 03
10 — Final 03
customer sales
Distribution chain 1000 — 10
05
SAP AG 1999
The divisions are assigned to the distribution chain from which they can be sold. The combination of
distribution chain and division is a sales area.
Customer-specific arrangements, regarding partial deliveries or terms of payment, for example, can be
made for each sales area. Statistics can be created and separate marketing activities carried out within a
sales area.
Customer X
Account definition
General
at client level
data
PLUS PLUS
Sales area
1000-10-10
CC 1000
A sales area (combination of sales organization, distribution channel, and division) must define sales
area-specific settings for a customer before it can start doing business with that customer. These could
be special conditions and terms of payments that the customer has arranged with the specific sales area.
SD FI
Sales
Sales order No document
Shipping
Outbound delivery Transfer order Goods issue
Document
Outbound Picking Goods
Line items
delivery issue ...
...
SD MM
SD FI
Invoice
Billing
Billing document
Line items
...
...
SAP AG 1999
The sales order forms the basis of the sales process. Once a customer has placed an order, a sales order
must be created at the start of the process. The sales order is generated at the distribution chain level.
The ordered items can be from different divisions. The sales order is a document in SD and does not
cause any postings in Financial Accounting. When the sales order has been entered, the system carries
out an availability check for the required delivery date.
On the day of shipping, an outbound delivery document is created. Billing for the delivery can only
take place when the goods have been taken from the warehouse stock and posted as a goods issue.
The warehouse management function is used for picking. A transfer order has to be created, which
generates the pick order. The requested goods are taken from the warehouse and prepared for delivery.
The goods to be delivered are posted as a goods issue. A goods issue document is created in MM, and an
accounting document is created in FI so that the goods issue is posted to the correct G/L accounts.
The last stage in the sales process is billing. A billing document is created in SD, and a printed invoice is
sent to the customer. At the same time, a document is created in FI so that the receivables and revenues
can be posted to the correct accounts.
Presentation:
Presentation:
Credit Management
Credit Management
SAP AG 1999
6000 5000
1000
6000 5000
Mexico Japan
2000 2300
United Kingdom Spain
3000
1000 2100
Germany Portugal
2200
3000 4000 France
USA Canada
SAP AG 1999
The organizational unit used for credit control is the credit control area. A credit control area can be
assigned to individual company codes (decentralized organization) or to a group of company codes
(centralized organization).
A credit control area is generally managed by a separate credit department, which is divided into a
number of credit representative groups, with each group consisting of several credit representatives.
The IDES group uses four credit control areas:
Mexico and Japan each have a separate credit department (credit control area 5000 and 6000)
The USA and Canada have centralized credit control in credit control area 3000
Credit control is also centralized for all company codes in Europe (credit control area 1000)
Overview
Customer General
master record data
SAP AG 1999
The credit department sets up a separate credit management master record, which is an extension of
the customer master record, so that data relevant to credit management can be maintained and
monitored.
The credit management master record consists of the following sections:
General data, which is relevant for all credit control areas. This could be the customer's address and
communication data, or the maximum total limit that can be permitted for the sum of all granted credit
limits.
Credit control area data, which is only relevant for a specific credit control area. This could be the
credit limit at credit control area level, or a customer's risk category.
An overview, which contains the most important data from all sections.
Sales
order Credit
control
Order block
Rejection
Review
Further processing
Delivery Billing d
No Yes
Release? ...
SAP AG 1999
Presentation:
Presentation:
Closing Operations in Accounts
Closing Operations in Accounts Receivable
Receivable
Overview: Accounts Receivable closing
operations
Value adjustments
SAP AG 1999
Technical/organizational tasks
Legal tasks
Time line
SAP AG 1999
At the start of the new fiscal year, the balance carry forward program is run, which ensures that the
balance of the customer accounts is carried forward to the new fiscal year. The posting periods of the old
fiscal year are then blocked and the special periods for closing entries are opened. Technical
reconciliation guarantees that documents are posted without any technical errors.
After this, balance confirmations are sent, foreign currency documents are valuated, value adjustments
are carried out, and receivables are reclassified for the financial statement.
The special periods can then be closed.
Balance confirmations, foreign currency valuations, and reclassifications are carried out in the same way
as in Accounts Payable. For this reason, this unit only concentrates on how value adjustments are
performed.
Note: Different financial statement preparations may be necessary in certain countries. Your trainer will
be able to explain the main features that are peculiar to your country.
Document
Account Run date 03.01.XXXX Document
Items
Account
Identification AC200 PK ...
Document
Items
PK ...
Account PK ...
Line...items
PK ...
C or V Status PK... ...
PK ...
10 20
Maintain parameters ...
... ...
SAP AG 1999
From 4.5, you can use a valuation program to carry out value adjustments. The program functions in the
same way as the dunning and payment programs. Each valuation run is clearly identified by the two
fields, "run date" and "identification".
You can specify how the valuation is to be executed by entering parameters for the valuation run. You
can use the parameters of an existing valuation run as a template. These parameters include the valuation
method, valuation area, and posting specifications.
Document
Account Run date 03.01.XXXX Document
Items
Account
Identification AC200 PK ...
Document
Items
PK ...
Account PK ...
Line...items
PK ...
C or V Status PK... ...
PK ...
10 20
Maintain parameters ...
... ...
SAP AG 1999
The valuation run analyzes the accounts and documents defined in the parameters and creates a
valuation proposal, which can then be edited, if necessary. The valuations can be:
entered manually in the document at an earlier date (individual value adjustment)
determined using a value adjustment key contained in the customer master record. A valuation that is
a certain percentage of the overdue amount is determined, based on the number of days in arrears
(flat-rate individual value adjustment)
Document
Account Run date 03.01.XXXX Document
Items
Account
Identification AC200 PK ...
Document
Items
PK ...
Account PK ...
Line...items
PK ...
C or V Status PK... ...
PK ...
10 20
Maintain parameters ...
... ...
Clearing
SAP AG 1999
The last stage of the valuation process is the transfer. G/L documents are created that post the valuation,
and the valuation is also entered in the valuated documents, so that the valuation can be traced at any
time.
Note 1: The valuations can be carried out in different ways if the financial statement is created using
different sets of accounting standards. The differing results are then posted to separate accounts that are
used in different financial statement versions.
Note 2: The valuation run can also be used to discount open receivables, which means they are valuated
at their net present value.
SAP AG 1999
SAP AG 1999
Document Display
Account Analysis
SAP AG 1999
Customer invoices are not usually posted directly in FI, but are posted to
Accounts Receivable from billing in SD. A normal sales process at IDES
consists of receiving a sales order, creating an outbound delivery, and
billing.
To access Sales:
Logistics Sales and Distribution
3-1-3 Billing
The customer must then be charged for the delivery. Bill the customer for the
delivery.
Display the billing document on the screen and from here, go to the
accompanying accounting document. What information does the accounting
transaction contain?
_______________________________________________________
_______________________________________________________
SAP AG 1999
SAP AG 1999
For the purposes of the following exercises, we will assume that the closing procedures where
already completed for the previous month.
SAP AG 1999
Search for the open item using 800000## (order number) under allocation, and
double-click it.
Switch to change mode ("Display -> Change" button).
Change the payment terms to ZB01.
Write down the number of the document you are changing.
Save
Confirm warnings.
In the "Res. items" tab: Double-click on the empty field labeled "Resi" next to
the item. The residual item is calculated and entered in the field automatically.
Post by choosing save.
Record the document number.
Search for the item with the allocation number 800000##. It should now be a
cleared item.
Search for the item using the document number you wrote down. It is the
residual item and should be an open item.
"Correspondence" tab: The "Last dunned" and "Dunning level" fields should
contain entries.
The message "Deliver xxx has been saved" appears This is the
changed delivery for which the goods issue is now ready.
3-1-3 Billing
Billing Billing document Create
Click on "Accounting"
Choose “Accounting document”.
CUSTOMER## should appear in this list. Use the search function to find your
customer in the list.
AB has to be entered in the "Value adjustment" field. If not there, enter it and
save the change to the master record. Confirm message regarding VAT
reg. No.
Click on "Maintain"
Field name or data type Values
Key date Last day of the previous month
Val. method 3 (Reserve for bad debt)
Currency type 10
Postings Select
Posting date Last day of the previous month
Rev.post.date First day of current month
Document type SB (in left section of screen)
Click on "Dispatch"
Select “Start immediately”.
Continue (press enter)
The account should have a credit balance of 1000 UNI in the previous period.
In the current month, the posting was reversed.
Contents:
Asset Master Data
Standard Accounting Transactions in Asset
Accounting
Closing Procedures in Asset Accounting
SAP AG 1999
SAP AG 1999
CO
Balance sheet
... ...
P&L
...
SAP AG 1999
Asset Accounting records all accounting transactions relating to the management of assets.
SAP AG 1999
Presentation:
Presentation:
Asset Master Data
Asset Master Data
Asset classes
Depreciation areas
SAP AG 1999
SAP AG 1999
Each asset belongs to a company code and business area. All postings made for the asset (acquisitions,
retirements, depreciation, etc.) are applied in the assigned company code and business area.
Additionally, you can assign the asset to various CO objects (cost center, internal order, activity type)
and logistic organizational units (for selection purposes only).
Asset 001111
Accounts for buildings
1000
t
000000-099999 Asse
class
1000 Buildings
000000-099999
C
Asset Accounting
100000-199999
4000
400000-499999
Assets under construction
5000
500000-599999
Low-value assets
...
600000-699999
SAP AG 1999
The asset class is the main criteria for defining the asset. Each asset has to be assigned to an asset class.
In the asset class, you can define certain control parameters and default values for depreciation and other
master data.
Assets that do not appear in the same line item of the balance sheet (such as buildings and equipment)
have to be assigned to different asset classes. Additionally, there is at least one special asset class for
assets under construction and one for low-value assets. The asset classes used by IDES for this are:
4000 For assets under construction
5000 For low-value assets
Note 1: You can also create asset classes for intangible assets and leased assets. There are functions
available for processing leases.
Note 2: The application component PM (Plant Maintenance) is used for the technical management of
assets. The application component TR (Treasury) is used for managing financial assets.
Trade
100 000 40 000 60 000
law
Legal
100 000 40 000 60 000
Cost
100 000 10 000 90 000
accounting
Parallel
100 000 10 000 90 000
valuation
SAP AG 1999
It often occurs that asset balances and transactions need to be valuated differently for various purposes.
You may, for example, use various valuation methods for:
Financial statements based on regional requirements
Financial statements for tax purposes (if a different deprecation method is allowed)
Controlling (costing)
Parallel accounting methods for group financial statements (per IAS, US-GAAP, etc.)
In order to keep more than one valuation basis, so-called depreciation areas are kept in the R/3 System.
Separate transaction figures are kept in each area:
per asset and depreciation area
for individual value components such as balances, depreciation, remaining book value, etc.
Calendar
Normal depreciation 01 When was the asset placed
start date Jan in service?
SAP AG 1999
Various data is stored in the asset master data for depreciation areas and controls the calculation of
normal and special depreciation for the special depreciation area. You can thus use a different
depreciation method for general business procedures than the depreciation method required by the tax
authorities.
Depreciation
Balance
areas sheet
accounts
Trade
law
Depreciation
accounts
Asset X
Balance
sheet
accounts
Parallel e.g. for IAS
depreciation
Depreciation
accounts
e.g. for IAS
SAP AG 1999
Since the depreciation areas in asset accounting do not exist in the general ledger, these values have to
be posted to various G/L accounts in the general ledger. The G/L accounts are then used in various
financial statement versions (financial statements per GAAP, financial statements for tax authorities,
group financial statements, and so on).
These G/L accounts are:
Balance sheet accounts, which record the adjustments to the asset's value
Depreciation accounts for depreciation and appreciation
The assignment of the G/L accounts to various valuation areas is saved in a single account assignment
key, which is entered in the asset master record. Assets of the same asset class all have the same account
assignment key, that is, their values are all posted to the same reconciliation accounts.
Note: Many companies prefer to keep parallel valuations in Asset Accounting (either statistically or for
information purposes) and not in the general ledger. In this case, you do not need to make the related
G/L account assignments.
Group
asset
3000 / 0000
Assets
1000 / 0000 2000 / 0000
Asset sub-numbers
1000 / 0100 1000 / 0200
SAP AG 1999
For reporting purposes, parts of an asset can be kept under asset sub-numbers, and assets can be
combined in group assets.
The main asset is assigned the sub-number 0000, allowing the asset sub-numbers to be assigned as
desired.
A group asset has its own master data. Several main assets can be assigned to a group. This is important
in the USA.
Presentation:
StandardPresentation:
Accounting Transactions in
Asset
Daily Accounting
Accounting
Asset Accounting
Transactions in
Transaction type
Asset transactions
Unplanned depreciation
Assets under construction
Asset Explorer
SAP AG 1999
Asset posting
such as acquisition, asset retirement, allocation, depreciation,
appreciation
$
+ - Depr.
SAP AG 1999
The transaction type is an addition to the asset posting keys 70 and 75 and it has to be included when
posting to an asset account. The transaction type is necessary for asset accounting, since it specifies
exactly where the asset posting is listed in the asset history sheet.
The transaction type is the distinguishing characteristic of the various asset postings, which include:
Buying and selling
Credit memos
Acquisitions from internal production
Adjustment postings
Retirements without revenue
Depreciation and appreciation
and so on
Assets Vendors
Asset transaction integrated
Asset Vendor
with accounts payable or
100 100 accounts receivable
Assets Vendors
SAP AG 1999
Asset transactions (acquisitions, retirements) can be posted in various ways to meet the organizational
and business requirements of the company. In FI-AA you can post:
Without a vendor or a purchase order. The offsetting entry is made in a G/L clearing account.
Integrated with A/P but without reference to a purchase order.
Via materials management using the MM functions (purchase order, goods receipt, invoice receipt).
When posting to accounts of two subsidiary ledgers, the reconciliation accounts of both subsidiary
ledgers are updated in the general ledger.
Cost
10 000
accounting
Parallel
10 000
valuation
SAP AG 1999
Unplanned depreciation is posted if something happens to the asset which permanently lowers the
asset's value.
As with every asset transaction, you need to use a specific transaction type for unplanned depreciation.
It is possible to enter different values in the various valuation areas for the damages incurred. For
example, the company may set the loss higher for cost accounting than for the company's financial
statements.
After posting the transaction, the unplanned depreciation is saved as planned values. The actual amounts
are posted when the depreciation posting run is carried out during closing.
Asset 1
IM
In
or ves
de tm 40%
rs en
t Assets under
construction
o Settlement of
r asset under
construction
s
according to
t i on distribution rule
u isi 60
cq % Asset 2
ta
s se
A
FI-
AA
SAP AG 1999
The expenses for assets under construction can be managed in two ways:
In the application component IM (Investment Management), you can create, post, and manage
investment orders. These orders are then reconciled with the asset under construction. IM provides
extensive functions for supporting investment procedures.
If IM is not used, the asset under construction can be posted to directly in Asset Accounting, since
assets under construction rarely occur.
Once the asset is complete,
master data has to be created for the completed assets
The values from the asset under construction account have to be posted again as completed assets, and
the assets have to be activated. To do so, the expenses can be distributed to several asset accounts
using a distribution rule.
Overview:
Transactions posted/
in fiscal year planned
depreciation
Tab
SAP AG 1999
Beginning in Release 4.6, the Asset Explorer offers a clear overview per depreciation area, asset, and
fiscal year for:
Planned values
Posted transactions
Posted amounts
Posted and planned depreciation
Depreciation parameters
Presentation:
Presentation:
Closing Procedures
Closing Procedures in Asset
in Asset Accounting
Accounting
Inventory
Depreciation
posting run
Asset history
sheet
SAP AG 1999
End of year
Beginning of new fiscal year
Year-end closing
Time line
SAP AG 1999
Asset Accounting
Inventory
list
Inventory
Inventory
list
Make corrections
SAP AG 1999
You can create one or several inventory lists with the R/3 System for the inventory process. The lists are
given to the employees who complete the inventory check. They note any discrepancies and return the
list to the accounting department, and the accountants enter the corrections in the system.
FI- FI-
AA GL
Trade law
Depreciation
Planned Posted accounts
depreciation Depreciation posting run depreciation trade law
Parallel depreciation
SAP AG 1999
All depreciation (normal depreciation, special depreciation, unplanned depreciation) is initially kept in
the form of planned values in Asset Accounting. Only after the depreciation posting run has been
completed is the depreciation actually posted in Asset Accounting. Additionally, a batch input is created
which contains the postings for the G/L accounts. When this is run, the depreciation is posted to the
corresponding depreciation accounts.
DM DM
+ - Dep.
$ $
SAP AG 1999
The asset history sheet is the most important and most complete evaluation available for closing. As
with financial statements, the structure of the asset history sheet is based heavily on country-specific
requirements. It is thus possible to create various asset history sheet versions.
Each asset history sheet version contains various history sheet groups such as:
Book values at the beginning of the fiscal year
Acquisitions
Retirements
Adjustment postings
Depreciation
Book values at the end of the fiscal year
SAP AG 1999
SAP AG 1999
How can you tell that the amount is due in three payments?
_______________________________________________________
_______________________________________________________
SAP AG 1999
For the purposes of the following exercises, we will assume that the closing procedures where
already completed for the previous month.
SAP AG 1999
The book values for area 01 (book depreciation) are all zero. This is due to the
nature of low value assets, since they can be completely written off.
In cost accounting deprecation area 20, the book values are greater than zero,
since all costs are to be calculated in controlling (even small amounts).
"Time-dependent" tab
Field name or data type Values
Business area BA##
Cost center CC##
Plant 1000
Save
You can see that the amount is due in three payments, since the total is divided
into three items in account payable.
"Time-dependent" tab
Field name or data type Values
Business area BA##
Cost center CC##
Plant 1000
Save
Contents:
Master Data in Travel Management
Accounting Transactions in Travel
Management
SAP AG 1999
Maintain travel
privileges
Plan trips
Enter trip costs
SAP AG 1999
CO
Balance sheet
... ...
P&L
...
SAP AG 1999
Travel Management manages and calculates travel costs and supports travel planning and travel
reimbursement.
SAP AG 1999
Presentation:
Presentation:
Master Master
DataData
ininTravel Management
Travel Management
SAP AG 1999
Organi- (Completed)
Personal personnel Bank
zational Addresses
information actions information
assignment
HR master record
SAP AG 1999
Employee data is saved as HR master data. Since the HR master data can be quite large, its data is
stored in data groups that are organized based on contents. One such data group is an infotype. For
example, city, street, and number are part of the address of an employee and are thus saved (along with
other data) in the infotype Addresses.
IDES Group is using the HR application component and is thus able to save and valuate a large amount
of data in the infotypes of HR master data.
Companies, which are not using HR, are also able to create smaller HR master data, the so-called mini
master record in Travel Management. The FI-TV mini master record only contains the following
infotypes:
Personnel actions (list of all completed personnel actions)
Organizational assignment (such as company code, business area, and cost center)
Personal information
Addresses
Bank Details
Travel privileges (control parameters such as assignment of travel restrictions for the employee and
for determining travel reimbursement)
Travel preferences (a row of infotypes for the support of travel planning)
SAP AG 1999
A personnel action includes all infotypes to be processed as part of a personal procedure, such as hiring,
organizational change, promotion, and so on. The relevant infotypes are made available for processing
one after another, to ensure that no important information is forgotten. Each completed action is entered
in the ”action" infotype, so that the ”actions" infotype has a log of all procedures completed for this
person.
Personnel actions are normally completed in HR. If HR is not implemented, FI-TV offers two actions for
maintaining FI-TV mini master records:
Create TV mini master records
Organizational change
When completing the "Create TV mini master record" action, the infotypes "measures", "organizational
assignment", "personal information", and "travel privileges" are made available. With the
"Organizational change" action, only the infotypes ”actions" and "organizational assignment" are made
available.
Travel preferences have to be manually entered, if Travel Management is to be implemented.
FI- FI-
AP TV
Personnel number
Vendor X 1000
Report and
Personnel batch input
number: 1000
Infotypes
SAP AG 1999
The IDES group reimburses employees for travel expenses using Financial Accounting. In order for the
payment program to be able to complete this work, a vendor master record has to be created for every
employee who travels. These personnel-related vendor records can be created automatically using a
program. The program creates a batch input that then has to be run.
The personnel number is entered in the vendor master record.
Presentation:
Presentation:
Accounting Transactions in Travel
Accounting Transactions in Travel Management
Management
Enter travel information
Enter travel costs
Transfer travel data to FI
SAP AG 1999
Name of
employee
Travel
➨ Travel requests
➨ Travel plans
➨ Travel expenses
Overview
of created
travel objects
SAP AG 1999
In Travel Manager, the employee has a complete overview of all his/her travel and the related travel
objects. There are three types of travel objects: travel requests, travel plans, and travel reimbursement.
Each of these objects can be created or changed with the Travel Manager.
Depending on how travel management is organized in the company, all travel objects or only part of
them can play a role in the travel process.
With travel request, the employee notifies the company that he/she is to take a business trip, and,
depending on configuration, sends this information on to an internal travel office.
The travel plan can be used to plan the details of a trip and to book the means of travel. This takes the
travel preferences that are saved as infotypes into consideration. A travel plan can be entered by an
internal travel agent or by the employee.
Travel expenses are a collection of expense-related travel information. They are the basis for the
calculation of travel reimbursement according to country-specific regulations and the posting in
Financial Accounting. If the amounts are taxable for the employee, these amounts can be transferred
to Human Resources.
Travel Travel
request plans
Open
travel Simulation
expenses
Vendor
x
Transfer
to FI
Approval Calculation Travel expense
x
SAP AG 1999
Travel Expenses are the central object in the travel process. The travel information is entered manually
or can be obtained from the travel request or travel plan and then corrected. Although travel requests and
travel plans offer optional functions, travel expenses are necessary for Travel Management. Prior to the
actual calculation, the results can be simulated.
The travel expenses can be entered by the employee or by the expense department. If the data was
entered by the employee, the accounting department has to check and approve the documents prior to
payment.
For the settlement, the system calculates a total amount to be paid based on the travel information,
reimbursement records, and settlement rules, and saves this information in the database.
The settlement calculations are then sent to FI using a special posting run.
SAP AG 1999
SAP AG 1999
Travel manager
2-4 Transferring to FI
The transfer of receipts to FI consists of two steps. Carry these out one after another.
Maintain travel
privileges
Enter travel information
Enter travel costs
SAP AG 1999
The Infotypes possible in the mini master record FI-TV are displayed. If there is a tick
next to it this means that the respective Infotype has been created. There is no tick next
to the "Travel Privileges" Infotype so you can now create the travel privileges.
Select "Travel Privileges"
Click on "Create"
Do not make any changes
Save
1-2-1 Starting Report for Creating Vendors from Personnel Master Records
Person-related master data Create vendors
Goto Variants Get
Double-click on variant "AC010"
Replace ## with your group number
(C) SAP AG AC010 11-321
Field Name or Data Type Values
Personnel number 20##
User in workfile AC010##
File name D:\usr\sap\<system>\SYS\glob
al\APACT
Note: Replace the placeholder
<system> with the name of
your training system, such as
T20.
Execute
On the left you see a list of all the trips for Angie Miller. To display more information
in the overview, click on "Open navigation area".
Her second trip took her to Munich to an EnjoyProject. She left on 02.01.98 at 10:00
and returned on 04.01.98 at 17:00.
Click on the arrow to the left of the trip and then double-click on Travel Expenses. The
travel expenses are displayed.
At the bottom you can see the reimbursement amount (692.70 UNI) and the cost
assignment (company code 1000, business area 9900, cost center 1110).
Expense receipts
Field Name or Data Type Values
Exp. receipt 001 Airfare paid
On Today
Amount 900 UNI
Click on "Add to table"
The receipt is displayed in the receipt list.
Click on "Results"
The employee receives a reimbursement of 280 UNI.
The total cost of the trip amounts to 1180 UNI.
Back
Save.
2-4 Transferring to FI
Contents:
Master Data in Bank Accounting
Accounting Transactions in Bank
Accounting
SAP AG 1999
SAP AG 1999
CO
Balance sheet
... ...
P&L
...
SAP AG 1999
SAP AG 1999
Presentation:
Presentation:
Master Data in Bank Accounting
Master Data in Bank Accounting
Bank master
records
Bank G/L accounts
Cash ledgers
SAP AG 1999
Customer / Vendor
Country
Bank key Client Bank details
Client level Country Bank key Account
level Address... Bank type Direct debit
Tax info..
Banks
SAP AG 1999
The bank directory contains the addresses and valid control data (such as Swift code) of all banks used in
the SAP System.
The bank directory can either be:
Automatically imported, as long as the bank directory is available on diskette and a import program
exists for this data
or
manually created
If a bank is set up in the bank directory, this information could then, for example, be accessed when
entering the bank information in a customer or vendor master record. You would only need to enter the
country of the bank and the country key; the system would determine the name and address in the
background.
Account number
Account control
Account currency
Bank account in the SAP System
Bank/fin. details
House bank ID House bank
Acct ID Acct ID
Bank
Bank account
at house bank
SAP AG 1999
For controlling the payment program, the house bank ID and the bank account ID were already used.
Each bank account is represented in the SAP System by a combination of house bank ID and account ID.
This combination is then entered in a G/L account and represents a bank account in the general ledger.
There is thus a relationship:
Bank account at house bank <--> combination house bank and account ID <--> G/L account
The represented relationships should always be a one-to-one relationship.
SAP AG 1999
Since the Enjoy Release (4.6), SAP offers a transaction for managing cash amounts. You can create cash
journals that are uniquely identified by a four character name.
Each cash journal should be assigned to one G/L account, which represents the cash journal in the
general ledger. It is however possible, to connect multiple cash journals with one G/L account. Cash
transactions are saved separately in the cash journal and are transferred periodically (for example, daily)
to the general ledger.
Presentation:
Presentation:
Accounting Transactions
Accounting Transactions in Bank
in Bank Accounting
Accounting
Cash procedures
Check deposits
Lockbox
Account statement
Check management
SAP AG 1999
Balance display
Data selection
for display period
Accounting transactions
(Cash in / cash out)
SAP AG 1999
The cash journal has the form of a new ENJOY transaction. The screen is divided into three sections:
Data selection: Here, the time period of the data can be selected.
Balance display: Displays the totals of incoming and outgoing cash and the beginning and ending
balance.
Accounting transactions Here, the cash journal transactions can be entered.
Accounting transactions are saved separately in the cash journal and are transferred periodically (for
example, daily) to the general ledger. The transferred transactions can be printed as a journal.
A receipt can be printed for each individual transaction.
Cash Customer
Customer payment
X X
Cash Vendor
Vendor payment
X X
Cash Revenue
Revenue posting
X X
Cash Expense
Expense posting
X X
SAP AG 1999
On this slide, the possible types of cash journal transactions and their corresponding posting records
are represented.
There can be many concrete accounting transactions with specified bank clearing accounts, revenue
accounts, and expense accounts, all with a descriptive text. An example of an accounting transaction of
type "expense posting" would be "cash purchase of office supplies" using the expense account "Office
supplies". The accounting transactions are set up in Customizing but can also be created directly from
the application, if a new accounting transaction is deemed necessary during daily operations.
1. Note: Customer and vendor payments cannot be executed using clearing, that is, an open item is first
posted for the payment, and this open item is then cleared with a paid item in a second step in accounts
payable or accounts receivable.
2. Note: Incoming and outgoing bank payments are not posted directly to bank accounts. Rather, they
are first posted to bank clearing accounts. The bank clearing accounts are then cleared using the account
statement.
Checks and
deposit slip Account Lockbox file
statement
SAP AG 1999
The processing of incoming checks in handled differently internationally. The two most common
procedures are represented on the slide based on IDES company codes 1000 (Germany) and 3000
(USA). In Germany, payments are often made using bank transfers. In the USA, checks are the most
common method of payment. For this reason, the number of incoming checks in Germany is relatively
small and can be handled by the accounting department. In the USA, many companies take advantage of
a special service provided by their banks, the so-called lockbox, which relieves them of considerable
work.
Germany: The checks are sent directly from the customers to the accounting department. The paid items
are cleared, the checks received are posted to special incoming check accounts, and the checks and a
check deposit slip are sent to the bank. The bank collects the money and posts it to the bank account. The
posting appears on the account statement and the amount received clears the incoming check account in
the general ledger.
USA: The checks are sent directly from the customers to the company's lockbox. The bank collects the
money and records the checks and payment information in a lockbox file. The bank sends this file to the
accounting department. By posting the lockbox data, the paid items are cleared and the check amounts
are posted directly to the bank (G/L) account. With a lockbox account, the processing of the account
statement is thus not necessary.
Note: The lockbox account is only intended for incoming cash. Outgoing money is transferred to a
different bank account, which is used to complete all other accounting transactions, such as travel costs,
cash payments, and so on. The account statement has to be processed for these transactions.
Inventory
Batch input session
or direct posting
Manual
entry
Manual post-
processing
SAP AG 1999
OI 2 2 1 1
Open
Item
SAP AG 1999
Two batch input sessions are created from the check deposit lists, and both sessions have to be
processed in order to create the related postings. These two sessions are: a subledger accounting session
and a bank accounting session.
The subledger accounting session is generally processed from accounts receivable and clears the
open items paid. The offsetting posting is made to a check clearing account. The items to be cleared
are found based on the data included on the check deposit slip provided (such as delivery number,
document number, and so on).
The bank ledger accounting session is generally processed by the banking department (or cash
management) and posts the check amounts to the incoming check account; the offsetting posting is
posted to the check clearing account.
The bank ledger accounting session should be processed first, so that cash management receives the
most up-to-date information in a timely manner. When processing the subledger accounting session,
payment differences may, in certain cases, need to be dealt with. If processing was completed without
using a batch input, there is a special transaction for postprocessing.
Note: For a smaller company, which does not have these various departments, the use of a check
clearing account may not be necessary. The posting from the subledger accounting session could then be
posted directly to the incoming checks account.
Customer
Lockbox OI 1
file
Check receipt
Data Amounts Import
transfer and 1 2
House payment
bank information Bank
SAP AG 1999
When using a lockbox, the customers send their checks and payment information directly to the bank.
The bank saves the check information and payment information in a file and sends it to the accounting
department using data transfer (diskette, data line, EDI). The lockbox file is recorded in the SAP System
with a program, the incoming check postings are activated, and the paid items cleared. Complete
payment information allows the R/3 System to proceed reliably with the clearing. If an assignment is not
possible, the payment information has to be processed afterwards using a special transaction.
House
bank
Data transfer
Account statements in
bank-data memory
Batch input session
account Import or direct posting
statement
file
The bank informs the accounting department of the transactions in the bank account of the company
using an account statement. The postings listed have to be understandable to the accounting
department.
The account statement can be sent to the company in one of two ways:
As a form: In this case, the account statement information has to be manually entered in the SAP
System.
As a file: The file is either sent as a diskette or can be accessed from the bank using a (bank-specific)
transfer program. A SAP program imports the information in the file to the bank temporary storage of
the SAP System.
The process continues as follows:
The account statements in the bank temporary storage can be printed for documentation purposes.
Batch input sessions are created from the account statements in the bank temporary storage, and the
sessions have to then be processed in order to create the related postings. Beginning with 4.0, posting
can be completed directly, that is, without a batch input.
Postprocessing, if needed, is completed by either running the batch input session online or by making
the postings directly using a special postprocessing transaction.
Outgoing checks
2 2 1 1 OI
Incoming checks
OI 1 1 2 2
During this course, you were introduced to various programs that provide accounting with support for
processing checks. This slide contains an overview showing the programs and the various postings made
with them.
Outgoing checks: The payment program creates the check, posts the outgoing check, and clears the
open item of the vendor. The outgoing check is posted to an outgoing check account. Once the check has
been deposited by the vendor and the bank account debited, it will appear on the account statement, and
the bank accounting session of the account statement function posts this as "outgoing check to bank".
When using check management, this posting is activated by the check deposit.
Incoming checks: You have already been introduced to two ways of doing this. In the USA, all required
postings are completed using the lockbox functions. With the other procedure, you first post the
incoming checks to an incoming check account and clear the open items. In a second step, the bank
accounting session posts the incoming cash with the posting record "bank to incoming check".
2 2 1 1 OI
OI 2 2 1 1
Bank transfers are used quite extensively in many countries. This slide contains an overview showing
the programs which are responsible for various postings.
Outgoing bank transfers: The payment program creates the bank transfer and posts in to the outgoing
payment account. At the same time, the open vendor items are paid. The cash flow appears on the
account statement and the bank accounting session creates the posting "Outgoing cash to bank".
Incoming bank transfers: Incoming bank transfers appear on the bank statement. The account
statement function posts the incoming cash using the bank accounting session. The posting record is
"bank to incoming cash". The subledger accounting session clears the paid items in the customers
account. The account statement function obtains the assignment information from the "notes to payee"
field.
Vendor
Check register
Payment program
Check 1000
Check 2000
Bob Jones
...
Payment
method C
Bank Outgoing check Vendor
1
2 2 1 1 OI
Check extract
House
bank CC 3000
Cashed checks list / file 2
USA
SAP AG 1999
Check management is used to establish the status of a check (open, cashed, void). SAP offers two
payment methods for which check management can be completed:
Payment method S (not shown): The check contains the same number as the corresponding payment
document. The payment documents are posted to the outgoing check account. The status of a check
can be determined by viewing the outgoing check account, which is open item managed.
Payment method C (see slide) The check is pre-numbered or obtains a sequential number from a
predetermined number range. The status of such checks is contained in a special check register. This is
used quite frequently in the USA.
The payment process using payment method C is as follows:
The payment program clears the open item, prints the check, and enters the check as open in the check
register. A list of all sent checks is sent to the bank for confirmation of checks cashed (check extract).
The vendor receives the check and deposits it at his bank, which sends the check to the house bank of
the company code.
The check payments appear on the account statement of the bank; they are ignored when the statement
is read. Accounting receives a list of cashed checks or a file with this information from the bank. This
is electronically or manually entered, the outgoing check postings are cleared, and the check(s) are
marked as "cleared" in the check register.
SAP AG 1999
Account: ___________________________________________________________
G/L Accounting:
Master records Individual processing In company code
SAP AG 1999
2-1-3 Forwarding to FI
At the end of every day, all entered transactions are forwarded to the general
ledger where they are updated. Carry out this procedure and then display the
accounting documents generated for each item.
Use this information to enter the items in the check deposit transaction list and
then save your entries.
First process the batch input session "Bank ##" and then the session "Customer
##".
Go back to the screen "Edit check deposit list ".
First process the batch input session "Bank ##" and then the session "Persons
##", both in the foreground.
The system is unable to perform the selection of the open item for
the updating of the incoming cash payment per bank transfer on its
own, as it has found more than one customer with the search term
"Becker*". This means you must manually intervene in the batch
input processing by choosing "CUSTOMER##" from the proposed
selection list of customers. This is precisely how the bank employee
would react if the item cannot be found automatically.
SAP AG 1999
Back
2-1-3 Forwarding to FI
Click on "Post" (all entries to G/L)
To display the documents generated, select an item and then choose "FI follow-
on documents". Select the accounting document.
The item created by the batch input session can be found with the cleared items.
The item text includes the check number, the account number and the bank key
(in Germany: Bank identification number).
Double-click on the item
Click on "Document overview"
The document items include:
113117 Incoming checks clearing account 9700.00
880000 Customer cash discount 258.62
CUSTOMER## Becker ## 10000.00-
175000 Output tax 41.38
Choose the document header symbol. Here you will see that the document has
been created by the session "Customers ##".
Now go back to the SAP Easy Access menu.
Double-click the item for 10000 UNI with document type DZ and the highest
clearing document number (meaning the document last posted)
Click on "Document overview"
The document items include:
113109 Customer incoming cash account 10000.00
CUSTOMER## Becker ## 10000.00-
Contents:
SAP AG 1999
SAP AG 1999
CO
Balance sheet
... ...
P&L
...
SAP AG 1999
The account balances in the general ledger as used to create the balance sheet and profit and loss
statement.
SAP AG 1999
Presentation:
Closing Procedures in the General
Ledger
Schedule Manager
Overview: General ledger closing
Accruals/deferrals, GR/IR analysis
Balance audit trail, creating financial
statements
Reporting
SAP AG 1999
Task plan
Task groups
Monthly overview
Tasks
Daily overview
SAP AG 1999
In Release 4.6 (ENJOY Release), the Schedule Manager is available for planning, completing, and
monitoring complex work processes.
A work process is created as a task plan in the Schedule Manager. Such a task plan contains nothing
more than a list of tasks. Within the work plan, the tasks can be grouped in task groups. Tasks can be:
Transactions or programs to be run online
Programs with a variant to be run in the background
Workflow definitions
Notes acting as place holders to describe tasks not processed in the R/3 System
The employees who are given responsibility for a task can plan their task from the task plan, from the
daily overview, or, if necessary, complete it online.
The Schedule Manager is especially useful for closing procedures, but can also be used for daily
processing. It can be used in all subsidiary ledgers of FI and in CO.
Reporting
Time line
SAP AG 1999
At the start of the new fiscal year, the balance carry forward program is run. This ensures that the
balances of the G/L accounts are carried forward to the new fiscal year.
The posting periods of the old fiscal year are then blocked and special periods for closing entries are
opened. Technical reconciliation between transaction figures and documents guarantees that documents
are posted without any technical errors.
The foreign currency documents are then valuated, accrual/deferral postings are made, and the GR/IR
clearing accounts are analyzed, updating the account affected.
If you wish to create business area financial statements, you need to make adjustment postings for the
business areas. The balances of the business areas are then set to zero.
The special periods can then be closed.
For documentation purposes, the balance audit trail is made and the financial statements are created.
Additional reports are prepared for legal reporting purposes.
Note: Different financial statements may be necessary in certain countries. Your trainer will be able to
explain the main features that are specific to your country.
Invoice
120
10 10 10 10 10 10 10 10 10 10 10
Expenses
Periods
Anticipated Transitory
accruals/deferrals accrual/deferrals
SAP AG 1999
Revenues and expenses, which were posted in a specific posting period, often originate in a different
period. For this reason, such revenues and expenses have to be accrued, that is, they have to be
divided up over the periods in which they are incurred.
There are two methods available in the system to make these postings: accruals and deferrals.
Accruals
Situation: The expense or revenue belongs to the current period, from an accounting point of view, but
is not posted until a later period, because the invoice has not yet been sent/received.
Deferrals
Situation: The expense or revenue was posted in the current period (invoice sent/received), but the
actual business transaction, or part of it, is actually incurred in a future period.
Accruals and deferrals are handled in FI in different ways.
In the figure, you see an example of an invoice that is received and posted in the seventh period. Since
this invoice was created for property that will be used during the entire year, the expense of 120 must be
evenly divided over all periods. Accrual postings thus need to be made for the first six periods, each with
the amount of 10. An amount of 50 has to be distributed over the last five months, once the invoice is
received.
Accruals always have to be made if an expense or a revenue will occur in the future, but the actual
business transaction is completely or partially paid for in the current period. The recurring entry program
is ideal for this situation, since the same amount (10) is posted in every period to the same accounts.
The posting record for each period would be "Expense to other payables (provisions)". A posting is
made to the account
Other payables: If the amount and reason for the accrual are known.
Provisions: If either the amount or reason for the accrual is uncertain and can thus only be estimated.
With each period in which accruals are made, the credit balance of the ”Accrued liabilities" account
increases.
Invoice
120
Other
Vendor
payables/res.
120 60 60*
10 10 10 10 10
Expenses
Expenses AR/AP
Periods
60 50 50 50
Period 7
Post invoice Period 8
50
Post accrual
Reverse accrual posting * Accumulated accruals
SAP AG 1999
Deferrals always have to be made if an expense or a revenue is posted in the current period, although
the actual business transaction is completed (fully or partially) in the future. Transactions have been
developed to facilitate the posting of deferrals.
Continuing with the example from the previous figures, the process is completed as follows:
The invoice for 120 is received in the seventh period and is posted to this period. The payables or
provisions created by accruals are cleared in the process. The posting record would be:
Other payables (provisions) and expense to vendor.
The other payables (provisions) are changed to actual payables and an expense of 60 is posted in
period 7.
However, only an amount of 10 belongs to period seven. The remaining 50 needs to be transferred to
the next period. This is completed using an accrual document. The posting record would be:
Prepayments and accrued income to expense
The accrual document is usually posted on the last day of the period and contains a reversal date
(normally the first day of the next month).
A reverse posting program posts a document automatically on the reversal day. This document re-
posts the expense of the prepayment and accrued income as an expense.
At the end of the eighth period, this process is repeated again, using the amount 40.
Balance Balance
Sheet Sheet
Assets Liabilities & equity
... ...
Billed but not Shipped but not
received billed
20 20
or
Appendix Appendix
GR/IR account GR/IR account
100 80 80 100
SAP AG 1999
The GR/IR clearing account contains a list of all goods and invoices received. If, at the end of a period,
the balance of this account is not zero, there are either
goods that were billed but yet delivered, or
goods that were delivered, but not yet invoiced
The balance then needs to be listed as either an asset or a liability.
A special program analyzes the GR/IR account and posts the balance to either a "Invoiced, but not
received" account or a "Received, but not billed" account. The posting is reversed on the first day of the
next period, since re-postings during daily business would lead to erroneous figures.
A clearing posting is normally completed using a correction account. The GR/IR clearing account and its
correction account are an appendix to the financial statement.
Periodic Working
file
Database Yearly
Journal
Account
Balance carry
forward
... Line items
Account balance
SAP AG 1999
Normally, there are legal requirements that make it necessary to determine (even years later) the balance
of an account by totaling the document line items posted to the account. As long as the documents
related to this account and period are still in the system, this is not a problem.
It is usually necessary, however, to archive and delete older documents from the system, in order to
improve system performance. To be able to track the account balance after archiving, you need to run
the balance audit trail program prior to archiving. This program creates a compact journal and puts it in
a file.
Once a year, the accumulated contents of this working file can be archived or printed out.
Note: If archiving is only completed once a year, a working file does not need to be created, since the
compact journal can be created directly from the database.
Company code
financial
Financial statement versions statements
CAUS
Fin. statement USA Business area
GKR financial
Statement Germany statements
INT
Financial statement
IDES Operating chart
of accounts
Country-specific
chart of accounts
SAP AG 1999
To assist in creating financial statements, there are two options available in the R/3 System:
Using an ABAP program
Using the G/L account information system
Both options allow you to
Use various financial statement versions
Create individual and total financial statements for company codes
Create individual and total financial statements for business areas
Create financial statements using the operating chart of accounts
Create financial statements using the country-specific chart of accounts
Create comparative financial statements for comparing two fiscal years or for comparing plan and
actual data
Company code
reporting
Tax
authority
Law
Consolidated report (EU) VAT tax reports Other legally required reports
SAP AG 1999
To support legal reporting requirements, there are currently a number of reports that meet country-
specific requirements. There is a list of country-specific reports for completing VAT tax forms, support
for the consolidated EU report, and other reports for additional legal reporting requirements (such as a
report for international trade as required by German law).
Presentation:
SAP AG 1999
P&L based on
period accounting
Sales revenue
Material expenses
Personnel costs
+ Depreciation Total costs for period
broken down by cost type
+ Other business expenses
=Total expenses
SAP AG 1999
Two basic methods for structuring profit and loss statements are available:
Period accounting
Cost of sales accounting
Both methods result in the same profit or loss for the period. The method used is
either legally required
not legally required. In this case, the decision is made based on business considerations (for example,
which would be better for international investors?).
With period accounting, the total production for the period is used along with the entire costs for the
period:
The total production for a period is calculated by adjusting the sales revenue by the change in
inventory.
The total costs of a period are broken down by expense types, that is, the balances of similar expense
accounts are added together (such as various accounts for personnel expense). This breakdown
distributes the expenses to the various production factors.
SAP AG 1999
With cost of sales accounting, the sales revenue for a period are used as well as the cost of sales for the
period.
The sales revenue for a period is determined in the same manner as in period accounting. The changes
to stock on hand, however, are not considered.
The cost of sales of the period quantify the expenses incurred to achieve the sales revenue for the
period. Unlike period accounting, in which the expenses are broken down by expense types, the
expenses are listed according to their origin, such as manufacturing, sales, administration, research
and development (R&D), production, and so on.
The manufacturing cost of the sales is calculated when the goods are shipped. When using period
accounting , the posting record is "GR/IR clearing account to change in inventory". When using cost of
sales accounting, the posting record is "GR/IR clearing account to manufacturing costs".
To assign the remaining expenses to their origin, the SAP System requires an additional characteristic,
the functional area. Typical functional areas are sales, production, marketing, administration, research
and development.
Document
Line items
Account Functional area Co object Amount
40 Expense 0400 1000 10
50 Balance sheet acct 10-
SAP AG 1999
When cost of sales accounting is selected, an additional field is included in the coding block (that is, the
list of all account assignment objects) for the functional area. An entry is made in this field with:
A manual entry
Automatic copying of the functional area entered from the master data of the CO object
Automatic copying of the functional area entered from the master data of the P&L account
Automatic entry of the functional area through means of a substitution
The aforementioned order is also the order of priority for deriving the functional area. In other words,
manual entries have the highest priority and substitutions the lowest. The system should, however, be set
up, so that a manual entry is normally not necessary, but rather that the functional area is derived from
the CO object, the P&L account, or a substitution.
Cost of sales
FI-
FI- General FI-
FI-
GL GL accounting
Ledger
ledger
SAP AG 1999
To create financial statements based on cost of sales accounting, the SAP System needs transaction
figures for the functional areas. In the standard general ledger, however, transaction figures are only kept
for the organizational elements company code and business area. For this reason, a cost of sales
accounting ledger has to be used, so that transaction figures for the functional areas can be kept as well.
Using a special financial statement report, these transaction figures can be accessed and a profit and loss
statement can be made based on cost of sales accounting.
If additional transaction figures need to be kept for existing or new account assignment fields, the
application component Special Purpose Ledger can facilitate this by:
Extend the coding block
Using a customer-defined ledger that contains additional transaction figures. These figures can then be
valuated with the tools of the Special Purpose Ledger (Report Painter, Report Writer).
Presentation:
Consolidation
EC-CS, SEM-BCS
SAP AG 1999
CO-
CO-PA EIS BP
Executive Business
HR Information Planning
System
EC-CS Consolidation View
EC-PCA
Profit Center Accounting
Profit center, company code
EC-CS consolidates at the organizational units company, business area, and profit center. If the
operating applications and the consolidation system are in one system and client, the data can be sent
online to the consolidation system
Additionally, data can be retrieved from other R/3 Systems per periodic extract or rollup.
Periodic extract:
In the sender system, you extract the reporting data with the financial statement program.
In the receiver system, a program reads the data extract and posts the information.
Rollup:
Rollup is a standard tool in the SAP System for transferring data records from a sender table to a
receiver table. It is used for the transfer of EC-PCA data to EC-CS. You can also implement it if you
want to transfer data from various R/3 Systems or clients from EC-CS and want to set up the profit
and loss statement based on cost of sales accounting.
For data transfer from non-SAP Systems, you can send the data offline with EC-CS creation forms, MS-
Access, or MS Excel.
Consolidation World
group (part of
group company)
North America Europe
Consolidation
unit United Canada Germany Great France
(company) States Britain
With EC-CS, you can perform legal and management consolidations. The basis for this are the
organizational units company, business area, and profit center. For each consolidation type, a view is
created.
The group structure with a view can be represented in various hierarchies. IDES uses a hierarchy for
legal representation and one for regional representation.
EC-CS forms the company structure using consolidation groups and units. Per hierarchy, consolidation
groups are defined. They represent the levels at which the consolidation is completed. Consolidation
groups can be: Subgroups (company consolidation), business areas (business area consolidation), profit
centers, and hierarchy nodes (profit center consolidation).
The objects to be consolidated that lie below consolidation groups are consolidation units. Depending
on the consolidation type, these are companies, combinations of companies and business areas, or
combinations of companies and profit centers.
Procedures
Hierarchy of Total
groups/units status Data transfer Validation Conversion ...
- Segments
+ Cons.goods Non-food
- Pharma
+ USA
+ Germany
+ Australia
+ Electronic
+ Other
Milestone
SAP AG 1999
Consolidation is performed with the help of two monitors. They contain all the procedures to be carried
out.
Data monitor: Prior to consolidation, the data to be consolidated has to be prepared at the level of the
consolidation units.
The data monitor contains all preparatory procedures and their current status. Procedures in the data
monitor could be: Creation of financial data and additional financial data (additionally, for the
consolidation of relevant data), validation of the financial data, manual adjustment postings, currency
translation, apportionment, validation of adjusted financial data.
Consolidation monitor: At the level of the consolidation group, the prepared data of the
consolidation units is finally consolidated.
Procedures in the consolidation monitor could be: Consolidation of payables, sales, costs and
expenses, investment income, and capital. Also, the validation of consolidated values.
If the system settings are correct and the financial data was properly created, the system carries out the
consolidation steps via the press of a button. The automatically created postings are displayed in the log.
Milestones are used to stop the automatic consolidation update at the procedures that are marked
accordingly. The next procedure is started separately.
CO Consolidation
Cost elements Direct update chart of accounts
”Group”- Rollup Balance sheet
FI chart of
EC-
EC-CS
”Operating" accounts
chart of P&L
”Country”
1
chart
accounts N:
of accounts Cash flow
1
1: N:1 Financial
(legal require.) statement
version Statistical items
Postings
Key figures
B/S
P&L B/S
P&L
Periodic
extract
Consolidated
Operating sender systems financial
statements
SAP AG 1999
The manner in which data is transferred to consolidation depends on the data transfer method.
Direct update/rollup:
Value items with the same names as the accounts of the group chart of accounts have to be in the
consolidation chart of accounts for EC-CS. You create the group account of the sender system in the
master data of the operating chart of accounts.
Periodic extract:
The operating accounts are assigned to a group financial statement version in the sender system.
The items of the consolidation chart of accounts in the receiver system correspond to the line items of
this financial statement version. In the FI sender system, you extract the financial data with the
financial statement program.
In the EC-CS receiver system, a program reads the data extract and posts the information.
The EC-CS consolidation chart of accounts consists of value items, under which the values are kept, and
totals items, which contain the totals of the value items below them in the structure.
You can use multiple consolidation charts of accounts to meet various requirements.
Consolidation chart of accounts for financial accounting (group financial statement based on US-
GAAP, for example)
Condensed chart of accounts
Chart of accounts with key figures
R/3 BW
OLTP structures OLAP structures
fixed partially
flexible
EC-CS SEM-BCS
Consolidation Business Consolidation
SAP AG 1999
SAP SEM
BPS: Connection between strategic
planning and enterprise planning/ Stakeholder
simulation relationship
CPM: Balanced scorecards, Corporate management Business
Management cockpit, Key figure systems performance (SRM)
Consoli-
SRM: Inclusion of stakeholder monitor dation
expectations in company goals (CPM) (BCS)
BCS: Legal and management
consolidation with the press of a button Business
Business
BIC: Automatic information collection planning & Information
from external and internal company data simulation Collection
(BPS) (BIC)
BW: Integration of strategic, operative
information and financial data
BW
SAP AG 1999
SAP AG 1999
At the end of the fiscal year, the companies in the IDES group have to
create financial statements based on the requirements of the countries in
which they operate.
The profit and loss statement of some companies is based on period
account, while other companies use the cost of sales accounting method.
For the purposes of the following exercises, we will assume that the closing procedures where
already completed for the previous month.
Normally, IDES runs the program for all business areas. For
practice, you ran the program specifically for your business area
BA##.
SAP AG 1999
SAP AG 1999
Unit: Closing
Topic: Closing procedures in the general ledger
Basic data
Field name or data type Values
Vendor 1921
Continue
Basic data
Field name or data type Values
Invoice date First day of the previous
month
Posting date First day of the previous
month
Continue
Confirm message.
Basic data
Field name or data type Values
Amount 6000
Tax amount 0 (0I Input tax training 0%)
Reference 100##
In the left column, select the "with cost center" screen variant.
Line items
Field name or data type Values
G/L account 466000
D/C Debit
Doc. currency amount 6000
Tax code 0I
Cost center CC##
Post
By looking at the transaction figures, you will see that the balance of the
account in the previous period is only 500 UNI, which is also the amount that
was supposed to be charged to this period.
The remaining insurance premium paid of 5500 UNI was moved forward to the
current period.
A warning appears that no goods receipt has been received for this invoice
(quantity delivered is zero).
Confirm warning.
Confirm information if prompted to.
For the last period, the balance has to be 100 UNI. The 100 UNI have to appear
in the "Billed but not received" account for closing.
The account should have a balance in the previous month of 100 UNI. This
amount is reversed in the following period.
Select the balance for the previous period to display the line item list.
Select the line item to display that item.
Select "Document overview"
The financial report for the last period compared to the same period of the previous
year is displayed. You can drilldown for the transaction figures of the accounts in the
financial statement.
Return to the selection screen and limit the selection to your business area BA##.
You see the functional area here, such as 400 for administrative costs.
The P&L based on cost of goods sold is displayed for company code 1000.
Return to the selection screen and run the same report for your business area BA##.
Contents:
SAP AG 1999
Operating
Concern
Controlling Controlling
area area
Business
areas
Company codes
SAP AG 1999
Divisions
Distribution
channel
Distribution chain
SAP AG 1999
SAP AG 1999
SAP AG 1999
SAP AG 1999
Contents:
Posting tips
Glossary
Menu paths
SAP AG 1999
Contents:
Reference documents
Set/hold data
Parameter IDs
Document parking
Validations and substitutions
Report variants
SAP AG 1999
SAP AG 1999
Reference documents, sample documents, and the hold/set data function all aid in reducing the
number of entries necessary in a new document.
Reference documents are previously posted documents, which can be used as a template.
Sample documents are model documents which may also be copied into a new posting.
The hold/set data function allows for the automatic entering of certain data when repeating a
posting.
Line items:
PK Account Amount
40 123000 5000
50 345560 2000
50 907902 3000
Document # 2:
Header: 01/23/1995 Comp. Code: 0001
Line items:
PK Account Amount
40 123000 5000
50 345560 2000
50 907902 3000
SAP AG 1999
When posting a document, it is sometimes easier to use a previously (or frequently) used account
assignment. This is done with reference documents.
In this example, the user copies an existing document to post a new one. This is done by simply
indicating the "Reference document" at the time of posting.
Screen Variants
SAP01 Standard 1 line
Line items:
PK Account Amount St BA Cst Cntr Order PK
40 415000 5000 i0 9900 3200 3000
40 415000 4000 i0 990 310 3000
50 113100 9000 3000
SAP AG 1999
There is a separate screen for fast entry of G/L account line items.
In regular line item posting, each line item requires a new screen with the possible fields available
presented to the user. G/L fast entry uses line item templates which have only the predefined fields
available. The limited selection usually has a length of 1 or 2 rows. This allows multiple line items to
appear on the same screen. This simplifies the entry of multiple document line items.
In Customizing, it is possible to configure various entry variants to fulfill different end-user
requirements.
Posted document
Header: 1/ 21/1995 Company code: 0001
Items:
PK Account Amount
40 123000 5000
50 345560 2000
50 907902 3000
SAP AG 1999
The account assignment model includes the line items that will be defaulted into the document.
The account assignment model can contain an indefinite number of line items and includes the posted
amount and the posted document.
The posting in the account assignment model does not need to be complete. For example, the account
might be included in the model whereas cost center and amount fields are left blank to be completed in
the final posting when the model is used.
Account number ?
Account number
Company code
SAP AG 1999
Parameter IDs are used to determine the default value for a field in the user master record.
The advantage of this procedure for the user is that he or she no longer has to specifically enter a
field value on the screen.
Example: If the user only has authorization for company code 1000, the system automatically enters
the value 1000 in fields that display the company code.
Document parking
Account 470000
Amount 1000
Document number: 505021
Cost center ??? Transaction figures not updated
Park User: MacDonald
SAP AG 1999
An incomplete document can be parked and posted at a later date. This can be completed by the same
user or a different one.
Document parking has the advantage, that document data can be used for online evaluations. However,
is does not have to be maintained until the document(s) are completely entered and posted. For example,
you can use amounts from parked documents for the advance tax on sales/purchase report.
Substitutions and validations are not available for document parking. However, they can be used when
the document is posted.
Parked
Parked document:
document:505021
505021 Document
Document completed/posted
completed/posted
SAP AG 1999
You can post parked documents either individually or via a list. If you post several parked documents
via a list, the system issues a list when you have finished which details which documents were
successfully posted.
From this list you can then carry out any necessary post-processing to any parked documents that could
not be posted due to missing vital information such as missing account assignment. You can also create
a batch input session to post the parked documents.
SAP AG 1999
SAP AG 1999
SAP AG 1999
Contents:
Set up of Special Purpose Ledger
Reporting capabilities in the Special Purpose Ledger
SAP AG 1999
CO SD
FI
Ext. data
MM
SAP AG 1999
XXXXX XXXXXXXXX
SAP AG 1999
Reporting
using Report
General Ledger
Painter
ASSETS LIABILITIES PROFIT & LOSS
Accts rcvble Sales Special Purpose Ledger
760 760 XX .... Dimensions Data ....
Account BA Cost Ct X .... Amount TC Quantity
Electric XX -760 -650 USD 900 KG
XXX... Accts
Accts pybl.
pybl. Water expense
expense
150 900 JPY 400 PCS
900
900 150
150 .... YY Water YY
150
760 650 USD
Heat
-150 -900 JPY
XXXX -900 720 GBP 3 PCS
SAP AG 1999
SAP AG 1999
FI
REPORT REPORT
REPORT
WRITER WRITER
PAINTER
CO
MM
Cost elements Actual Plan Variance
SAP AG 1999
REPORT PAINTER
Report A1
General data
selection
Characteristics?
FI/CO/MM databases
Characteristics Key figures
xxxxx ##### xxxxxxx ######
##### xxxxxxx ###### A1 1997 1998 Der.
xxxxx
xxxxx ##### xxxxxxx ######
xxxxx ##### xxxxxxx ###### 250 300 50
380 310 70 -
xxxxx ##### xxxxxxx ######
45 10 35 -
xxxxx ##### xxxxxxx ######
##### xxxxxxx ###### 235 330 95
xxxxx
xxxxx ##### xxxxxxx ######
SAP AG 1999
Columns
Key
Key column
column ------------- ----------- ------------ -------------
SAP AG 1999
SAP AG 1999
Unit: Appendix
Topic: Glossary
ABAP/4 Query ABAP/4 Queries provide user with basic lists, sorted and totalled by various
criteria. Statistics and ranked lists are also available.
Account Assignment Model The account assignment model is a template for posting documents.
It includes the line items that will be defaulted into a document to facilitate data entry. It can
contain an indefinite number of line items and include the posted amount or it can use an
equivalency factor to spread an amount proportionally.
Account Groups Account Groups are a classifying feature for G/L, Vendor and Customer master
records. The account group assists in screen display and account numbering. Each master record
must be assigned to an account group.
Account Types When posting line items, there are 5 types of accounts that may be entered:
Customer, Vendor, G/L Account, Asset and Material. The posting key defines which type of
account is being used.
Accrual Entries Accrual & Deferral Entries are adjustment postings which are necessary at the
end of a posting period. They are typically reversed in the following period. R/3’s accrual
program books the accrual to the G/L, then specifies the date upon which the reversal should be
effective. A reversal program is executed to select and reverse the applicable accrual documents.
Activity Types Activity Types describe the activity produced by a cost center and are measured
in units of time or quantity. Examples: Machine hours, Labor hours.
Additional Account Assignments All entries that are made in the line item in addition to the
account number, amount and posting key. These include terms of payment, payment method, cost
center and others.
12
Asset Class The asset class provides the classification for fixed assets. It provides account
determination, number ranges and screen display options.
Automatic Account Assignment Automatic function (in financial accounting) during posting
transactions, whereby the system assigns the items to their appropriate accounts, without the user
having to make any entries.
Balance Audit Trail Recording of all transactions in an account within a certain period. The
balance audit trail shows the balance at the beginning of the period and the development of the
account until period end.
Balance Carried Forward The transfer of an account balance from the previous year. A balance
is carried forward for balance sheet accounts.
Balance Sheet Readjustment Program Program SAPF180 ensures zero balances per business
area necessary for creating business area balance sheets. If profit center accounting is activated,
readjustments are made for profit centers as well. It distributes Receivables & Payables, tax
postings, cash discount postings and valuated exchange rate differences.
Balance Sheet Account Valuation Program RFSBEW00 valuates General Ledger accounts
managed in a foreign currency at a key date specified in the selection parameters.
Bank master data Information on a bank that is required in order to carry out business
transactions with the bank. It is stored in the bank directory, which contains data on all the banks
required. Bank master data includes, for example, the name of the bank, the address and country
specifications.
Baseline Date The Baseline Date defines the date on which terms of payment are to begin. R/3
allows customization of this date to meet user requirements.
Branch Account Account that is used to represent the head office/branch relationship of a
customer or vendor in the R/3 system. Purchase orders, deliveries or invoices entered for branch
accounts are posted to the head office account. Every branch account must refer to a head office
account.
Business Area Business areas are used for internal purposes to create balance sheet and profit
and loss statements or alternatively can be used to meet external segment reporting requirements.
Chart of Accounts Systematically organized list of all the G/L account master records that are
required in a company code or several company codes. The COA contains the account number,
the account name and control information for G/L account master record. There are several types
of charts. See Operating COA, Corporate COA and Country COA.
Clearing Procedure where open items in an account are marked as cleared. You ca clear open
items if you can assign an amount of equal value to the opposite side of the account. Example: if
a customer pays an invoice, you can clear the open items belonging to it.
Client Each client is a self-contained technical unit. It does not have any business related
meaning. General data and tables which are used by multiple organizational structures are usually
stored at this level. Data records carry a client key. There are only a few client independent tables
(item sorting, for example). A user master record must be created for each user needing access to
the client.
Company Code Currency/ Local Currency This is the currency of the company code in
which the document is attached. R/3 will always store the company code currency.
Controlling Area A controlling area identifies an independent organizational structure for which
costs and revenues are collected. Each controlling area can have one or more company codes
assigned to it.
Corporate Chart of Accounts The Corporate Chart of Accounts groups dissimilar charts of
accounts together for consolidated reporting. It is sometimes referred to as the Group Chart of
Accounts.
Cost Element A cost element is used to classify and assign values to the consumption of
productive resources.
Country Chart of Accounts The Chart of Accounts provides an alternative account number
structure to meet localized reporting requirements. It is sometimes referred to as the Alternative
Chart of Accounts.
Credit Control Area The Credit Control Area is the organizational structure that tracks and
monitors customers’ credit in R/3. It is used by the Sales & Distribution components of R/3 as
well as the Accounts Receivable component to provide integrated credit management.
Cross Company Posting Posting transaction involving several company codes. The system
creates a document for each company code involved. Cross company code posting are used to
process centralized purchasing or payments.
Correspondence All evaluations and reports sent to business partners are considered
correspondence. Correspondence includes, account statements and open item lists in letter form,
individual and standard letters, balance confirmations, document extracts, payment notices and
statements of bill of exchange charges.
Document Change Rules Documents can be changed using the original document number based
on Document Change Rules. They determine which fields and under what circumstances fields
can be changed.
Document Principle The R/3 system records at least one document for every business
transaction. Each document receives a unique document number. The document remains as a
complete unit and can be displayed at any time until it is archived.
Document Type Accounting documents are managed within R/3 through the use of Document
Types. The document type is located on the header portion of every document. Documents can
be viewed, sorted and archived by document type.
Drill Down Reporting User definable reporting tool which allows interactive data evaluation.
Dunning The structured process of reminding overdue customers of the status of their accounts.
Within R/3 customers are assigned to a dunning procedure which defines exactly how and when
the dunning will take place.
Exchange Rate Tables Exchange Rate Tables are user maintainable. They contain dates
with applicable translation rates for foreign currency transactions. The system will default
to the rates entered in this table if no rate is specifically entered on a transaction.
Exchange Rate Types Exchange Rate Types allow multiple rates to be stored and used for
different purposes. You can use Exchange Rate Types to define a bank buying & selling rate, an
average rate for translation of foreign currency amounts, rates for financial report translations, or a
rate for any specialized currency requirement within your company.
FI-CO Reconciliation Program The RKAKALFI report is used when a business has one or
more companies tied to the same controlling area and cross-company CO allocations and cross-
business area postings take place. This report will then compare total postings in FI and CO per
company and create adjusting entries.
Field Status The goal of R/3 is to ensure accurate and efficient data entry. The use of field status
functionality allows the appropriate combination of fields to be presented at data entry time
preventing errors of inclusion and exclusion. Individual fields can be required, suppressed or
optional, depending on the user defined configuration of R/3.
Financial Calendar The Financial Calendar provides a quick, centralized overview of Accounting
Activities planned or already performed, where the user can monitor and plan Financial
Accounting tasks centrally as they arise.
13
Financial Management Area The financial management area is found in the treasury component
of R/3. It subdivides an enterprise into units that can carry out independent cash budget
management and independent funds management.
Financial Statement Version Versions are created to provide row and hierarchy structure to the
balance sheet and profit and loss statement. You can define versions for a special chart of
accounts, for a corporate chart of accounts, or without any special allocation. You assign groups
of accounts to the items at the lowest levels of the hierarchy.
Functional Area Functional areas classify operating expenses according to the requirements of
cost-of- sales accounting by production, administration, sales and distribution, marketing, research
and development etc. By breaking costs down into these functional areas, cost-of-sales accounting
shows why costs accrued in an enterprise and indicates the economic purpose of the expense.
General Ledger Information System The general ledger information system, which is based on
R/3’s Executive Information System (EIS) functionality, is a dialog-oriented information system
that is capable of evaluating a dataset according to all characteristics contained in the data
description. Both G/L account transaction figures as well as balance sheet and P&L structures
serve as the primary database for the general ledger information system. Balance sheet key figure
reports and financial statement versions are available as report types.
G/L Fast Entry In regular line item posting, each line item requires a new screen with the
possible fields available presented to the user. G/L fast entry uses line item templates that have
only the predefined fields available. This limited selection is usually 1 or 2 lines in length,
therefore many line items fit on the same screen, making multiple line item entry much quicker for
standardized entries.
14GR/IR Account This General Ledger account that includes postings for goods received but
not yet invoiced, and also postings for goods invoiced but not yet received.
Goods Received / Invoice Received Reclass This program, (RFWERE00), analyzes goods
receipts and invoices received clearing accounts and generates adjustment posting to classify
business transactions correctly for balance sheet presentation.
Group Company A group Company is the legal unit of consolidation to which company codes
are assigned.
IMG (Implementation Guide) The IMG or Implementation Guide is the central element of
Customizing. It leads the user online through all the steps required for the implementation of the
R/3 system, for subsequent changes and for system upgrades and release upgrades. The IMG is
valid system wide and is client independent.
Internal Order Internal orders are used to plan, collect, monitor, and settle the costs of specific
operations and tasks performed within a controlling area. The SAP R/3-System allows you to
Invoice Verification Invoice verification is the R/3 process of matching a vendor’s invoice with
the purchase order for the goods, and the actual receipt of the goods.
Lockbox Processing Payment transactions in the USA are largely made in the form of checks. In
order to process these payments quickly, banks offer lockbox services where customers can send
their payments directly to a lockbox at a bank. The bank deposits the checks and sends check
deposit information to the payee via file transfer.
Net procedure Procedure where cost or inventory postings are reduced automatically by the
expected cash discount when an invoice is posted. As a result, it is possible to post exact
acquisition values less the cash discount.
14.2.3Noted Item Special item that does not affect the account balance. When
you post a noted item, a document is generated; the item can be displayed via a
line item display. Certain noted items are processed by the payment program
or dunning program. Example: down payment request
Number Ranges Within the Financial Modules number ranges are configured to meet individual
business requirements. Number Ranges can be an externally or internally defined. Several
number ranges are reserved for special uses in R/3. Number ranges are defined for master
records and documents.
One time accounts One time accounts are managed for business partners with whom business is
carried out only once or rarely One special master record is needed for all one time accounts.
Specific data on the business partner, such as address and bank data, is not entered in the
master record but in the document itself.
Open FI Interface The standard financial accounting functions are not always sufficient to meet
the specific demands of certain customers or industries. It is not always practical to extend the
standard system. At the same time modifications to the standard system should be avoided or at
least kept to a minimum. The Open FI Interface enables enhancement of standard functions
without having to modify the standard system.
15Open Item Management Specification that the items in an account must be cleared by other
items in the account. The sum of the items involved in the clearing procedure must be zero. As a
result, the account balance always results from the sum of the open items.
Open Item Valuation Open Item Valuation (SAPF100) carries out foreign currency valuation for
accounts managed on an open item basis such as A/P and A/R.
Parameter ID’s (PID’s) Parameter ID’s are used to determine the default value for a field in the
user master record. The advantage of this procedure for the user is that he or she no loner has to
specifically enter a field value on the screen.
Parked Document An incomplete document may be temporarily stored within R/3 and then
posted at a later date; this may be done by the same or a different user.
Parallel Currency R/3 always stores the transaction currency and the local currency of a
transaction. It is possible to configure R/3 to capture 2 additional or parallel currencies. The
user can display the transaction in any of the currencies being stored. Postings to exchange rate
difference accounts are made automatically.
16
Personnel Area The personnel area is an organizational unit that represents a specific area of the
company and is organized according to aspects of personnel, time management and payroll. Each
personnel area is allocated to one company code.
Payment Program The payment program has been developed for international payment
transactions with vendors and customers, and it handles both outgoing and incoming payments. It
is flexible enough to allow you to define those payment features that vary from country to country
such as payment method, payment form or data carrier specifications.
Plant The Plant is an operating area or branch within an enterprise. It plays an important role in
material valuations, inventory management, MRP, production, costing and plant maintenance. In
configuration a plant is assigned to a company code. A plant can only belong to one company
code; however, multiple plants can be assigned to the same company code.
Posting Period Variant Company codes are attached to a posting period variant. This variant
controls the opening and closing of fiscal periods within R/3.
Primary Cost Primary elements are cost or revenue items in the chart of accounts with
corresponding general ledger (G/L) accounts in Financial Accounting. When creating a primary
cost element or revenue element, it must be listed first as a G/L account in the Financial Chart of
Accounts.
Profit Center Profit centers collect revenues, and costs from the cost centers for which they are
responsible.
Reconciliation Account A general ledger account that ensures real-time integration of subledger
accounts with the general ledger. Each subledger account has a reconciliation account defined
within the company code portion of its master record. In this way, all postings to subledger
account are also posted automatically to the G/L reconciliation account.
Recurring Journal Entries Recurring Journal Entries are business transactions that are repeated
regularly. Therefore recurring reference documents can be created within R/3 to speed periodic
processing. These reference documents are then selected and processed at periodic intervals. The
actual update to the G/L uses batch entry processing.
Reference Documents or Master Records are previously posted documents or master records,
which can be copied, then modified to aid in data entry.
Report Painter An ABAP/4 coded generator, which allows the end user the opportunity to define
report rows and columns for customized reporting. Painter has a GUI front end for definitions.
Report Variant A report variant provides a way of storing predefined selection criteria for a
report. An individual report can have multiple report variants defined for it. However an
individual variant can be used for only one report. They allow
standardized report settings in order to provide consistent report output.
Sales Organization A sales organization represents a selling unit in the legal sense and is
allocated to a company code. This establishes a link between the SD and FI systems. Since a sales
organization belongs to just one company code all financial transactions for this sales organization
are posted to the linked company code. More than one sales organization can be linked to the
same company code.
Sapscript Sapscript is the integrated text management system of the SAP R/3 System. It is
tightly integrated into the R/3 System. You will therefore be using it for many different text-
processing tasks all over the R/3 System.
Secondary Cost Element Secondary cost elements are created and maintained exclusively in
Controlling (CO). They serve to assist in internal value flows, such as in internal activity
allocation, surcharge accounting, and settlement transactions.
Special G/L Indicator Indicator that identifies a special G/L transaction. Special G/L
transactions include down payments and bills of exchange. The indicator triggers the use of an
alternative reconciliation account for special business transactions in the subledger. These
transactions are not balanced with the receivables and payables form goods and services.
Special Period Special posting perod that divides the last normal posting period for closing
operations. Up to 4 special periods are possible with FI.
Special Purpose Ledgers (Customer Defined) Customer Defined Special Purpose Ledgers are
collections of information from R/3 applications (FI, MM, CO, SD), external data transfers and
FI-SL adjustment postings in customer defined tables. These customer-defined tables then
provide a database for user defined reporting.
Standard Hierarchy One main hierarchy reflects the overall structure of a company’s profit and
cost center management, and is mandatory. This is called the standard hierarchy within R/3.
Substitution A Substitution is the process of replacing one value with another as it is input into
R/3. Substitutions are transparent to the user inputting the data.
Tax Code Two digit code that reporesents the information required for identifying and
calculating tax. It controls the tax rate, type of tax and calculation method.
Transaction Currency This is the currency that is input on the header of the document. R/3 will
always store the document in transaction currency.
18Validation A validation is the process of checking values as they are entered into the R/3
system. If the conditions of the validation are not met, the resulting message can be either an error
or warning message depending on user defined configuration.
Valuation Balance Sheet term: the calculation of the value of all goods belonging to fixed and
current assets as well as all payables at a certain time point according to legal requirements.
Vendor Master Record Data record containing all the information on the vendor that is required
to carry out business transactions. It includes, for example, address and bank data.
Worklist When displaying account balances or line items, you can use work lists to rapidly
query a series of accounts at the same time. Work lists can be defined for the following objects:
BUKRS (company code), KUNNR (customer), LIFNR (vendor) and SAKNR (G/L
account).
Unit: Appendix
Topic: Menu Paths
G/L Accounting:
Initial screen Accounting Financial accounting General ledger
Master Data
Display chart of accounts Information system General ledger reports Master
data Chart of accounts
Display G/L account list Information system General ledger reports Master
data G/L account list
Maintain account definition Master records Individual processing Chart of
accounts
Maintain company code- Master records Individual processing In company
specific settings code
Business Transactions
G/L account posting Posting G/L account posting
(ENJOY)
Complex/general posting Document entry Others General posting
Accounts Payable:
Initial screen Accounting Financial accounting Accounts payable
Master Data
Create vendor list Information system Reports for accounts payable
accounting Master data Vendor list
Create vendor master record Master records Create
Change vendor master record Master records Change
Display vendor master record Master records Display
Track changes in an Master records Display changes
individual master record
Display changes to multiple Information system Reports for accounts payable
accounts accounting Master data Display changes to vendors
Business Transactions
Post a vendor invoice Document entry Invoice
Balance display Account Display balances
Line item display Account Display/change line items
Display documents Document Display
Display document changes Document Display changes
Manual outgoing payment Document entry Outgoing payment Post + print forms
with form printout
Create recurring document Document entry Reference documents Recurring
document
Execute recurring entry Periodic processing Recurring entries Execute
program
Automatic payment Periodic processing Payments
Reporting
(C) SAP AG AC010 11-453
Activities Menu Path
Carry out due date analysis Information system Reports for accounts payable
accounting Vendors: Items Due date analysis for
open items
Purchasing
Initial screen Logistics Materials Management Purchasing
Create a purchase order Purchasing: Purchase order Create Vendor/supplying
plant known
Post a goods receipt Purchasing: Purchase order Follow-on functions
Goods receipt
Carry out invoice verification Purchasing: Purchase order Follow-on functions
Logistics invoice verification
Closing Activities
Print balance confirmations Periodic processing Closing Check/count Balance
confirmations: Print
Carry out foreign currency Periodic processing Closing Valuate Open items in
valuation foreign country
Regroup receivables and Periodic processing Closing Regroup
payables Receivables/payables
Accounts Receivable:
Initial screen Accounting Financial accounting Accounts
receivable
Master Data
Create customer list Information system Reports for accounts receivable
accounting Master data Customer list
Create customer master Master records Create
record
Change customer master Master records Change
record
Display customer master Master records Display
record
Track changes in an Master records Display changes
individual master record
Display changes to multiple Information system Reports for accounts receivable
accounts accounting Master data Display changes to customers
Business Transactions
Asset Accounting
Initial screen Accounting Financial accounting Fixed assets
Master Data
Create asset balance lists Info system Reports on Asset Accounting Asset
balances Balance lists Asset balances
Create asset master data Asset Create Asset
Business Transactions
Post asset acquisition Assets Posting Acquisition External acquisition
(integrated with Accounts With vendor
Payable)
Asset query Asset Asset Explorer
Schedule unplanned Posting Manual val. correction Unplanned
depreciation depreciation
Scrapping Posting Retirement Scrapping
Asset under construction: Posting Cap. asset u. const .Distribute
Define distribution rules
Asset under construction: Posting Cap. asset u. const .Settle
Complete settlements
Reporting and Closing
Print asset charts Info system Reports on Asset Accounting History
Asset History
Print inventory lists Info system Reports on Asset Accounting Asset
balances Inventory lists Inventory list
Asset history sheet Info system Reports on Asset Accounting Balance
(C) SAP AG AC010 11-456
Activities Menu Path
sheet explanations International Asset history sheet
Travel Management:
Initial screen Accounting Financial accounting Travel
management
Master Data
Create travel privileges Person-related master data Maintain
Create vendors Person-related master data Create vendors
Business Transactions
Maintain trip Travel manager
Settle trip Travel expenses Periodic processing Settle trips
Create trip transfer document Travel expenses Periodic processing Transfer to
Accounting Create posting run
Create accounting documents Travel expenses Periodic processing Transfer to
Accounting Manage posting runs
Bank Accounting:
Initial screen Accounting Financial accounting Banks
Master Data
Maintain list of banks Master records Bank master record Change
Business Transactions
Manage cash journal Outgoings Cash journal or
Incomings Cash journal
Manual check deposit Incomings Check deposit Manual entry
transaction
Manual bank statement Incomings Bank statement Manual entry