Sie sind auf Seite 1von 118

Name:

Designation:
Date: February, 2004
Copyright Wipro Technologies 2004


Base Training
for SAP FI
Possible Consulting Inc
2
The agenda
Documents
Master Data
Overview & Basic Settings
1
2
3
Taxes
4
3
The agenda Contd.
Integration with MM
Integration with SD
Payments and Dunning
5
6
7
4
Navigation in SAP
5
Initial login screen to SAP
Enter the Client,
User name,
Password and
Language in this
screen

6
SAP Easy Access screen (First screen when you login)
Navigate
through the
menu to
access
transactions
Use the
command
field if you
know the t-
code
7
Tips on using Command Field
To call a transaction
in the same session (window)
Enter: /nxxxx (xxxx = transaction code).
in an additional session,
Enter: /oxxxx (xxxx = transaction code).

To end the current transaction
Enter: /n.
Caution: Unsaved changes are lost without warning

8
SAP Implementation Guide (IMG)
Use the menu
path to
configure
9
How to access help in SAP?
Click on
Application
Help, for
context-
dependent
help
Select SAP
Library for
help on IMG or
transactions
10
Overview & Basic Settings
1
11
SAP Modules
R/3

Client/Server
ABAP/4


Sales &
Distribution
SD
MM
PP
QM
PM
HR
FI
CO
TR
PS
WF
IS
Materials
Mgmt.
Product
Planning
Quality
Mgmt.
Plant Mainte-
nance
Human
Resources
Financial
Accounting
Controlling
Treasury
Project
System
Workflow
Industry
Solutions


R/3

Client/Server
ABAP/4

12
SAP Integration
13
SAP Financials Structure
.
FI
General Ledger
Legal Consolidation
Accounts Receivable
Accounts Payable
Asset Accounting
CO
Overhead Cost
Controlling
Activity-Based
Costing
Product Costing
Profitability
Analysis
TR
Cash
Management
Treasury
Management
Market Risk
Management
Funds
Management
Capital Budgeting
Preparation
IM
Budget
release
Execution
EIS
Enterprise
Management
Consolidation Budgeting
EC
Profit Centers
14
Basic Settings - FI Organizational Units

SAP AG 1999
Client 000
Company
Code 1000
Business area 1000 Business area 1000
Company
Code 2000
Company
Code 3000
Company
Code 4000
Business area 2000 Business area 2000
Client 001
Client 400
...
15
Creating new Company Code

SAP AG 1999
l the definition
l global parameters
l customizing tables (approx. 315 tables)
l general ledger accounts (if desired)
l account determination
After using this function, only the desired changes between the
original and the new company code have to be maintained.
To create a company code, copy an existing company code
using the organization copy function, which copies:
16
Defining Chart of Accounts

SAP AG 1999
The three steps to create and use a chart of accounts :
l Define the chart of accounts,
l Define the properties of the chart of accounts,
l Assign the chart of accounts to company codes.
CAUS
IKR INT
17
Contents of Chart of Accounts

SAP AG 1999
The definition of a chart of accounts contains:
l Chart of accounts key
l Description
General Information
l Maintenance language
l Length of the G/L account number
Controlling Integration
l Manual or automatic creation of
cost elements
Consolidation
l Group chart of accounts
Status
l Blocked indicator
INT
18
Assigning Chart of Accounts to Company Code

SAP AG 1999
CC1000
CC2000
CC3000
INT
CAUS
19
Group COA for internal reporting

SAP AG 1999
00010
Operational Chart of Accounts CAUS
00020
CC1000
CC2000
I
n
t
e
r
n
a
l

R
e
p
o
r
t
i
n
g

E
x
t
e
r
n
a
l

R
e
p
o
r
t
i
n
g

000001
Group Chart of Accounts INT
000002
0001 0002
Operational Chart of Accounts CAFR
... ...
group account
number: 000002
group account
number: 000001
group account
number: 000001
group account
number: 000002
20
Country COA for external reporting

SAP AG 1999
I
n
t
e
r
n
a
l

R
e
p
o
r
t
i
n
g

000001
Operational Chart of Accounts INT
000001
Altern. Acc. no.
0001
Company Code - Segments CC2000
Altern. Acc. no.
0002
E
x
t
e
r
n
a
l

R
e
p
o
r
t
i
n
g

CC1000
CC2000 0001
Country Chart of Accounts CAFR
0002
Altern. Acc. no.
00010
Altern. Acc. no.
00020
Company Code - Segments CC1000
00010
Country Chart of Accounts CAUS
00020
+ +
+ +
... ...
... ...
... ...
21
Variant Principle
Variant Principle is SAPs method of assigning special properties to R/3
objects.

Examples of Variants include
Fiscal year variant
Posting period variant
Field status variant

Steps in variants include
Define the variant
Populate the variant with values
Assign the variant to the R/3 Object (ex: Company code)

22
Fiscal Year Variants
SAP AG 1999
Calendar year = Fiscal year Calendar year different than
fiscal year
The posting periods
correspond to the months in
the year
Jan.
Feb.
Mar
Apr.
May
June July
Aug.
Sept.
Oct.
Nov.
Dez.
01
02
03
04
05
06 07
12
11
10
09
08
Apr.
May
June
July
Aug.
Sept. Oct.
Nov.
Dec.
Jan.
Feb.
Mar
01
02
03 04
05
06
- 1
- 1
- 1
Begin: April/1/2000
End: March/31/2001
Which fiscal year and posting period
was used on Jan.15, 2000 for
postings?
These postings were completed
in posting period 5 of the previous
fiscal year
23
Sample Fiscal year variants
24
Defining local currency
Local currency =
Company code currency
25
Currencies
A company code can have one local currency.

Transactions can occur in any different currency. This is called Transaction
Currency.

Exchange rates are maintained for converting Transaction Currency to Local
Currency.
26
Exchange rate maintenance
Translation ratios depict the relationship between a pair of currencies.

The translation ratios are usually maintained only once.

Exchange rate types facilitate maintenance of different exchange rates for a
currency pair (ex: Bank buying rate, Bank selling rate, Average rate, etc.)

The exchange rate is maintained with validity dates, per pair of currencies.

It is possible to automate this maintenance.
27
Exchange rates - ratios

SAP AG 1999
1
100
1
1
28
Exchange rates - maintenance
SAP AG 1999
Exchange
rate type
From
E
v
e
r
y

u
s
e
d

e
x
c
h
a
n
g
e

r
a
t
e

t
y
p
e

!

Every currency
combination !
E
v
e
r
y

d
a
y

?

A lot of daily work!
==> tools offer help
To Valid from Exchange rates
29
Exchange rate maintenance
30
Hands-on exercises
Login and navigate in SAP R/3
Calling functions
Create company code
Fiscal year variant

31


End of Day 1!
Time for
practice!!
32
Master Data
2
33
Configuration, Master Data and Transactional Data
Configuration is making settings in SAP. You choose the alternative most
suited to your business scenario.
Configuration is one-time activity. This is typically not changed, unless there
are basic changes in business scenario.

Master data remains unchanged for a long time, as compared to transaction
data.
Data is defaulted from Master data at the time of transactions.
Master data is created or changed on a need basis. Examples are Customer
master, Vendor master, etc.

Transactional data is captured while performing transactions in SAP.
Transactional data is created on a daily basis in SAP.
Only certain fields in transactional data are modifiable, subject to change
rules.
Examples of transactions are Invoices, Debit/ Credit memos, Journal entries,
etc.

34
Master Data in Financial Accounting
SAP AG 1999
l G/L Accounts
l Customer/Vendor Accounts
l Bank Master Data
35
Segments of GL Account master
GL Account master has got 2 segments
Chart of Accounts Segment
Company code Segment

Chart of Accounts segment contains data that is consistent across R/3
system.

Company Code segment data contains data that is relevant for a specific
company code.

For the GL account to be used in a company code, both the segments must
be maintained.
36
Creating GL Accounts

SAP AG 1999
l Manual
n Two - Step:
w
1. Chart of Accounts Segment, 2. Company
Code Segment
w
One - Step: Create both segments
simultaneously
l Copying
n Copying an individual GL account with reference to
another GL account
n Copy the entire company code segment
n Copy the entire chart of accounts segment
l Data Transfer
n Upload a new chart of accounts from an external
system e.g. flat file
37
Balance Sheet and P&L Accounts
In the Chart of Accounts segment of GL, you define if the account is a Balance
Sheet Account or Profit & Loss Account.

The balance in Balance Sheet accounts are carried forward to the next year.

The balance in Profit & Loss Accounts are transferred to the Profit & Loss
statement via the Retained Earnings Account.

38
GL Account types & carry forward
SAP AG 1999
000001
P+L statement acct type
Balance sheet account
000002
P+L statement acct type
Balance sheet account
000001
yy
C
a
r
r
y

f
o
r
w
a
r
d
000001
yy
000001
yy
000001
0
900000
yy
X := 900000
Balance Sheet and P+L Statement Accounts
39
Sample GL Account - Balance Sheet
40
Sample GL Account P & L
41
Concept of Account Groups

SAP AG 1999
l The number ranges of the
GL accounts
Account group
control
C
G
e
n
e
r
a
l

L
e
d
g
e
r

Cash
Matl
P/L
Liab
...
000000 - 099999
100000 - 199999
200000 - 299999
300000 - 399999
400000 - 499999
500000 - 599999
600000 - 699999
Cash accounts
Asst
Cash
Konto 001111
000000 - 099999
Chart of accts sgmnt
Company code segment
l
The field status of the fields
in the company code
segment of the master
record
42
Field Status
Field Status determines whether a field must be
Suppressed
Displayed
Required
Optional

Field Status is relevant according to type of transaction:
Creation
Change
Display
43
Field Status concept

SAP AG 1999
Each field has one of the
following properties:
?
l Suppressed
l Display
l Required entry
l Possible entry
G/L account
Joint Venture
Account control
Account management
1000
001111
Chart of accounts
Company code
INT
Account currency
Tax category
Alternative account number
Open item management
Line item display
Sort key
Authorization group
Cost type
G/L account
Name
Short text
Account group
Control in chart of accounts
Partner company
Consolidation in chart of accounts
001111
INT Chart of accounts
Group account number
G/L account long text
Sample account
P&L account
Balance sheet acct
Chart of accts segment Company code segment
44
Example of Field Status Group
45
Reconciliation Accounts
Sub-ledger accounts are called as Reconciliation Accounts in SAP.

Examples of Reconciliation Accounts in SAP are:
Accounts Receivable
Accounts Payable
Fixed Assets
Stocks

The entries are always made in the sub-ledger, and not in the GL account.

Each transaction updates the Reconciliation and GL account in real-time.

This ensures that the sub-ledgers are never out of balance with the main
account.

46
Customer and Vendor reconciliation accounts

SAP AG 1999
Trade Receivables
aa bb
Recon. account. for
acct type: D
Trade Payables
cc dd
Recon. Account. for
acct type: K
G
e
n
e
r
a
l

L
e
d
g
e
r

Customer
aa bb
A
c
c
t
s

R
e
c
.

A
c
c
t
s

P
a
y
.

Vendor
cc dd
47
Account groups in AR and AP

SAP AG 1999
The account group controls:
l The number ranges of the
accounts,
l The status of the fields in the
master record,
l If the account is a one time
customer or vendor.
C
A
c
c
o
u
n
t
s

P
a
y
a
b
l
e

AP
Dom.
For.
CPD
0001
...
000000 - 099999
100000 - 199999
200000 - 299999
300000 - 399999
400000 - 499999
500000 - 599999
600000 - 699999
AP
accounts
C
A
c
c
o
u
n
t
s

R
e
c
e
i
v
a
b
l
e

AR
Dom.
For.
CPD
0001
...
000000 - 099999
100000 - 199999
200000 - 299999
300000 - 399999
400000 - 499999
500000 - 599999
600000 - 699999
AR
accounts
48
Customer Account complete view

SAP AG 1999
Account 12345
in CC 1000
Account 12345
in sales area 001
12345
address
General data
...
Client
level
Company Code -
Segment CC1000
Sales area segment
Sales area 001
A A
A
49
Vendor Account Complete View

SAP AG 1999
Account 12345
in CC 2000
Company Code -
Segment CC2000
Account 12345 in
Purchasing Org 002
12345
address
General data
...
Client
level
Purchasing
Organization
segment
50
One time customer/ vendor
Where the dealing is for one time, it is not worthwhile to create the master
data each time.

The option is provided to reduce the master data load in SAP.

One time customer/ vendor master is a collective master data. It is created
one time without any specific customer/ vendor data.

The actual customer/ vendor data is captured at the time of invoice entry.
51
One-Time Accounts usage

SAP AG 1999
no customer/vendor specific
information (no bank details, ...)
Document Document
+ other customer/vendor specific
information (bank details, etc.)
+ customer/vendor specific
information (bank details,...)
Account 1000
Address
Communication
Account CPD
Address
Communication
-
Name
Street
City
...
Language
Telephone
...
Name
...
Language
...
Address Address
52
Clearing Customers and Vendors
It may sometimes happen that the same person is the customer and vendor.

In these cases, these balances can be offset while paying.

Enter the customer number in the vendor account.

Enter the vendor number in the customer account.

Select Clearing with vendor in customer account, and vice versa in vendor
account.
53
Same party as customer and vendor

SAP AG 1999
and
and
Cust. A
10 10
Vend. B
10 10
Cust. A
Client
level
Account control
Vendor
Vend. B
Client
level
Account control
Customer
Autom. Paym. Tr.
Clrg with vend.
Autom. Paym. Tr.
Clrg with cust.


Vend. B Cust . A
X
X
54
Payment to/ from a different party

SAP AG 1999
or or
Cust. A
10
Vend. B
10 10
bank account
of Y or Z
To address or
bank account of
M or N
10
Client
level
Cust. A
Alt. Payer Cust. Y
Paym. Trans.
+
Alt. Payer Cust. Z
Autom. Paym. Tr.
Client
level
Vend B.
Alt. Payee Vend. M
Paym. Trans.
+
Alt. Payee Vend. N
Autom. Paym. Tr.



55
Hands-on exercises
FS00 Edit G/L Account Company Code data
FSS4 Display changes in company code data

FD01 Create customer

FK01 Create Vendor


56


End of Day 2!
Time for
practice!!
57
Bank Master Data

SAP AG 1999
Bank country
Client
level
Address
Control data
Bank Master Data
Banks
Bank key
House bk comm. data
House Bank Data
+ DME/EDI - data
House bank data
Bank country
Company Code
Bank key
...
House Bank - ID
...
...
58
Sample Bank Master
59
Linking Bank accounts to GL accounts

SAP AG 1999
G/L Account
Bank/Fin. details
House bank
Account control
Account no
Account currency
Bank acc. data
House Bank - ID
Account - ID
Bank Account
Currency
G/L - Account
Bank account
Account ID
Bank account
at house bank
60
Sample House bank
61
Documents
3
62
Purpose of documents in SAP

SAP AG 1999
l Every day hundreds of financial documents are
created in the enterprise. To support the filing
of original documents, the documents have to
be divided into several categories.
l Different financial business transactions need
different data within the documents. Some
extra data may even be required for special
postings.
l The accounting department wants to be sure
that it is impossible to post to a previous
posting period.
l Head accountants should have more posting
authority than their staff.
63
Sample document types

SAP AG 1999
D
R

D
G

D
Z

S
A

K
R

K
G

K
Z

K
N

A
B

64
Document Type configuration
65
Structure of FI Document

SAP AG 1999
Items
Document
PK
PK
Overview Detail
Additional Details
Line Item 1 /
Account
Document Number Company Code Fiscal Year
Document Date Posting Date Period
Currency ... ...
..
001
002
Acct
Acct Description
Description Amount
Amount
+
-
. . . . .
Header
Amount
Tax Code
Business Area
Cost Center
Text
...
DT
PK PK
66
How is Field Status determined?

SAP AG 1999
Field
?
P
r
i
o
r
i
t
y

P
r
i
o
r
i
t
y

Account
yes
no
suppress
Posted with which
posting key?
Posted on
which account?
PK ...
PK ...
relevant for postings
on accounts of this type?
67
Sample FI Document
68
Purpose of Posting Keys

SAP AG 1999
1. on which type of account
the line item can be posted
to
Detail view
The Posting Key has
control functions
within the line items.
It controls:
2. if the item is posted as a
debit or credit
3. the field status of additional
details
Line Item 1 / PK
Account
Amount
1. S, D, K, A, M ?
2. debit,
credit ?
3. Field Status ?
Additional Details
Business Area
Cost Center
Text
...
Tax Code
69
Posting keys available

SAP AG 1999
01
02
03
04
05
06
07
08
09
Customers
11
12
13
14
15
16
17
18
19
31
32
33
34
35
36
37
38
39
Vendors
21
22
23
24
25
26
27
28
29
50
90
91
93
94
95
96
G/L
40
80
81
83
84
85
86
75
Assets
70 99
Materials
89
For G/L - Postings out of
Materials Management
70
Internal and External number ranges

SAP AG 1999
0000000000
1000000000
2000000000
3000000000
4000000000
5000000000
6000000000
7000000000
8000000000
9000000000
9999999999
internal
numbering
defined per fiscal
year
external numbering
internal numbering
defined until fiscal
year in the future
current numbers
1998
current numbers
1999 2000 2001...
00
01
02
71
Open posting periods

SAP AG 1999
Open posting periods during
the fiscal year
Open posting periods during the
closing procedure
01
02
03
04
05
06 07
12
11
10
09
08
15 14 16 13
01
02
03
04
05
06 07
12
11
10
09
08
open
72
Open and Close posting periods
73
Simple FI entries

SAP AG 1999
500 2
200000
Customer
220000 5500
1 1 2
Sales
Output tax
Vendor
1100 110000
1 1 2
Input tax
1 1
Expense
1 1
2
5000
Cash
5000
Bank
1 1 1 1
2
100000
1 1 10000
2 1000
100 2
1 1 20000
5000 2
l G/L account postings
l Vendor invoices
and
credit memos postings
l Customer invoices
and
credit memo postings
74
Rules for changing documents

SAP AG 1999
Different document change rules based on:
Account type: A, D, K, M, S
Special G/L transactions: Down payment,
Down payment requests, . . .
Company code
Account
1000 1000
1 1 2
Cr . memo
/ /
Invoice relation
Prerequisites for field changes :
Posting period open
Line item not cleared
Posting as debit / posting as credit
No invoice - related credit memo
No credit memo from down payment
0003 Z B
75
Document reversal

SAP AG 1999
Company
Document
M M M
2,500
Account 1
2,050
Account 2
2,050
Account 1
2,500
Account 2
2,500
Company
Document
M M M
2,500
Account 1
2,050
Account 2
2,050
Company
Document
M M M
2,500
l Document entered incorrectly
l Document corrected by Reversal
n Reverse with a standard reversal
posting
n Reverse with a negative posting
l Document re - entered correctly
Items
Document
D Account 1
C Account 2
76
Correction options

SAP AG 1999
Account 1
2050
Account 2
2050
Account 1
2050
Account 2
2050
Account 1
2050
Account 2
2050
2050 2050
2050 2050
2050 2050 2050 2050
2050 2050
- 2050 - 2050
Incorrect posting
0 0 0 0
2050
2050 0
0
l Standard reversal posting
l Negative posting
Posten
Beleg
S Konto 1
H Konto 2
77
Line items for GL accounts

SAP AG 1999
Account without
line item display
Transaction
figure / debit
Transaction
figure / credit
Account with line item
display
Doc. X, item 1
Doc. Y, item 9
Doc. Z, item 4
...
Doc. A, item 3
Doc. B, item 2
Doc. C, item 7
...
Transaction figure / debit Transaction figure / credit
Further
important
fields
+
Further
important
fields
+
Index to
documents
78
Hands-on exercises : Document creation
GL Accounting

FB50 Enter GL Account Document
FB03 Display Document
FV50 Park GL Document
FBV3 Display Parked Document
FV50 Post parked Document

Accounts Receivable

FB70 Invoice
FB75 Credit Memo

Accounts Payable

FB60 Invoice
FB65 Credit Memo
F-43 Vendor Invoice (With Special GL indicator)

FB08 Individual Reversal of Document

79
Hands-on exercises : Displaying Account balances
GL Accounting

FS10N Display Balances
FBL3N Display/ Change Line Items
F.01 Balance Sheet/ P+L Statement

Accounts Receivable

FD10N Display Balances
FBL5N Display/ Change Line Items

Accounts Payable

FK10N Display Balances
FBL1N Display/ Change Line Items

80


End of Day 3!
Time for
practice!!
81
Open item managed accounts

SAP AG 1999
Account without open item management
Doc. X, item 1 Doc. A, item 3
Transaction figure / debit Transaction figure / credit
Further
important
fields
+
Further
important
fields
+
Account with open item management
Transaction figure / debit Transaction figure / credit
further
important
fields
+
further
important
fields
+
Doc. Y, item 9
Doc. Z, item 4
...
Doc. B, item 2
Doc. C, item 7
...
Doc. X, item 1
Doc. Y, item 9
Doc. Z, item 4
...
Doc. A, item 3
Doc. B, item 2
Doc. C, item 7
...
82
Clearing concept

SAP AG 1999
February
1 2 3 4 5 6 7
8 9 10 11 12 13 14
16 17 18 19 20 21 22
23 24 25 26 27 28 29
29 30 31
Open item account
2,000 5,000
Can be cleared
Check Deposit
Company
Invoice
M M M
Company
Invoice
M M M
January
1 2 3 4 5 6 7
8 9 10 11 12 13 14
16 17 18 19 20 21 22
23 24 25 26 27 28 29
29 30 31
1 2
CLEARING AN
ACCOUNT
POST WITH
CLEARING
3
3,000
83
Clearing within an account

SAP AG 1999
Open item account
2000 5000
3000 1000
Open item account
2000 5000
3000 1000
Account
clearing
Items
Clearing document
ACCOUNT
CLEARING
84
Taxes
4
85
Purpose of Tax codes

SAP AG 1999
The tax code is used to:
State
n verify the amount of tax
n calculate the amount of tax
n calculate additional tax portion
n verify the tax type
n determine the G/L account
n show tax correctly on tax forms
Tax
code
A0 V0
0O 0I 0I
86
Tax rate maintenance

SAP AG 1999
Level
110
110
120
120
100
100
nnn
nnn
Condition
BASB
MWAS
MWVS
xxxx
Fr. Level
100
100
100
100
0
0
nnn
nnn
Tax type
Base amount
Output tax
Input tax
Any other tax
MWS
VST
xxx
Account key Rate
16.000
Tax
code
A0 V0
0O 0I 0I
87
Sample tax code (FTXP)
88
Posting of taxes

SAP AG 1999
Expense Vendor Input tax
l Posting as separate line item (standard case)
Expense Vendor Input tax
l Distribute to relevant expense/revenue items (process NVV for sales tax
payables or other non deductible input taxes) -
89
Account determination for taxes

SAP AG 1999
Account key
MWS Output tax
Input tax VST
Chart of accounts
RULES RULES POSTING KEYS POSTING KEYS
Accounts are
determined based on
Posting key
INT
Chart of accounts: INT
Account key: MWS
Account: Tax accrual
Debit/Credit
Tax Code
Debit : 40
Credit : 50
90
Account determination for taxes (OB40)
91
Payments and Dunning
5
92
Manual payments

SAP AG 1999
Document header
Post
Process open items
1. Payment header
2. Bank data
3. Select open items
1. Activate items
2. Activate cash discount
1. Display overview
2. Post
POST AND
CLEAR
93
Outgoing payments

SAP AG 1999
Print payment medium
Select payment method and bank
Select items for payment
Post the payment document
Vendor
10 10
Cash
10
Calculate the payment amount, taking
account of cash discount periods

Automatic Manual
94
Automatic Payment Program
95
Sample APP
96
When clearing, additional line items are created for

SAP AG 1999
5,000
Open item account
2,000
3,000
Can be cleared
l Cash discounts paid or received
l Cash discount clearing (net method)
l Tax adjustments
l Exchange rate differences
l Bank charges
l Clearing entries for cross - company code
payments
l Over - or underpayments within
tolerances
5,000
97
Exchange rate differences

SAP AG 1999
Foreign Vendor
Outgoing Payments
20 LC
Exchange Rate Differences
40 LC
20 LC
20 LC
40 LC
Open Item
Rate : 0.5 Rate : 0.25
10 FC 10 FC 10 FC
98
Accounting for incoming payments

SAP AG 1999
Customer
8000 5000
3000
Generate residual item
Residual
item
Partial
payment
Customer
8000 5000
Invoice reference
to open item
Post partial payment
Complete payment
Minor payment difference
Greater payment difference
(within tolerances)
(outside tolerances)
99
100
101
When the complete amount is not paid

SAP AG 1999
Customer/Vendor
8000 5000
Partial
Payment
Invoice reference
Residual
Item
Customer/Vendor
8000 5000
3000
Payment Diff .
3000
Customer/Vendor
8000 5000
3000
l Partial Payment
n both items remain on the
account
l Residual Item
n payment term
w
from cleared item
w
fixed payment term
n new document referencing
originals
l Charge off difference
102
When the clearing is wrong

SAP AG 1999
Open item account
2000 5000
3000 1000
Open item account
2000 5000
3000 1000
Reset
cleared
items
Items
Clearing
document
Reset
...
...
l Line items cleared in error
l Cancel clearing by resetting
clearing document and cleared
items
103
Hands-on exercises : Clearing
F-03 Clear GL Account

F-32 Clear Customer

F-44 Clear Vendor

F-53 Post outgoing payment (Partial Payment)

F-28 Incoming Payment


104


End of Day 4!
Time for
practice!!
105
Integration with SD
6
106
Integration of GL with other sub-modules

SAP AG 1999
SD
CO
General
Ledger
FI -
GL
FI -
AA
FI -
AP
FI -
TV
FI -
BL
FI -
AR
MM
Balance Sheet
P&L
...
... ...
107
SD Organization structure

SAP AG 1999
IDES Distribution Chains in Germany
Distribution channel
12 Resellers
Distribution channel
10 Fin . cust . sales
Distribution channel
14 Service
Sales organization
1000 Frankfurt
A A
A
Sales organization
1020 Berlin
A A
A
Distribution channel
16 Factory sales
Distribution channel
22 Indust . customers
Distribution channel
20 Store chains
Company code 1000
Germany
Distribution channel
24 Pharmaceutical customers
108
Logistics Integration with FI

SAP AG 1999
Company code 1000
Germany
Plant 1000
Hamburg
Distribution channel
10 Final
customer sales
Sales organization
1000 Frankfurt A A
A
Distribution channel
12 Reseller
Sales organization
1000 Frankfurt A A
A
... sells goods
from ...
... posts the
sale in ...
Distribution chain 1000 10 Distribution chain 1000 12
109
Sales area example

SAP AG 1999
Distribution channel
10 Final
customer sales
Sales organization
1000 Frankfurt A A
A
Distribution chain 1000 10
Sales area 1000
10 02
Sales area 1000
10 03
Sales area 1000
10 05
Divisions
02
03
05
110
Sales area usage

SAP AG 1999
PLUS
PLUS
Customer X in company code 1000 Customer X in
sales area 1000 - 10 - 10
Company code -
specific settings
Sales area -
specific settings
Sales area
1000 - 10 - 10
CC 1000
Customer X
General
data
Account definition
at client level
111
Sales process & FI postings

SAP AG 1999
Sales
...
...
Line items
Document
Outbound
delivery
SD FI
No document
Sales
order
Outbound delivery
Transfer order Goods issue
Billing
Picking
Goods
issue
SD FI
Billing
document
...
...
Line items
Invoice
MM
SD
Shipping
112
Integration with MM
7
113
MM Integration with FI

SAP AG 1999
CC 1000
IDES Germany
Plant 1000
Hamburg
Plant 1100
Berlin
Plant 1200
Dresden
Plant 1300
Frankfurt
Plant 1400
Stuttgart
114
Purchasing Organization

SAP AG 1999
CC 1000
IDES Germany
Plant 1000
Hamburg
Plant 1100
Berlin
Plant 1200
Dresden
Plant 1300
Frankfurt
Plant 1400
Stuttgart
Purchasing organization
1000 IDES Germany
Purchasing
is posted in...
Purchasing organization 1000 purchases for...
115
The 3 way match (PO GR Invoice)

SAP AG 1999
-
Purchase order
Goods receipt
Invoice receipt
Vendor
GR/IR
MM
FI
No document
Material
GR/IR
Line items
Document
GR/IR
Vendor
Tax
Line items
Document
Material stock or
consumption
1
1 2
2
Material
document
Goods
receipt
MM FI
FI
Purchase
order
Order
amount
MM
Invoice
verification
document
116
Recurring entry
117
Hands-on exercises : Recurring Entries


FBD1 Recurring Entry Document
FBD3 Display Recurring Document
F.14 Execute Recurring Entries
F.15 Recurring Entry List

118


End of training!
Time for
practice!!