sap fi overview
TRANSCRIPT
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 Settings1
23
Taxes4
3
The agenda Contd. …
Integration with MM
Integration with SD
Payments and Dunning5
67
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 helpSelect SAP
Library for help on IMG or transactions
10
Overview & Basic Settings1
11
SAP Modules
R/3Client/Server
ABAP/4
Sales &Sales &DistributionDistribution
SDSD
MMMM
PPPP
QMQM
PMPM
HRHR
FIFI
COCO
TRTR
PSPS
WFWF
ISIS
MaterialsMaterialsMgmt.Mgmt.
ProductProductPlanningPlanning
QualityQualityMgmt.Mgmt.
Plant Mainte-Plant Mainte-nancenance
HumanHumanResourcesResources
FinancialFinancialAccountingAccounting
ControllingControlling
TreasuryTreasury
ProjectProjectSystemSystem
WorkflowWorkflow
IndustryIndustrySolutionsSolutions
R/3Client/Server
ABAP/4
12
SAP Integration
13
SAP Financials Structure.
FIFI
General Ledger Legal Consolidation Accounts Receivable Accounts Payable Asset Accounting
COCO
Overhead CostControlling
Activity-BasedCosting
Product Costing Profitability
Analysis
TRTR
Cash Management
Treasury Management
Market RiskManagement
FundsManagement
Capital BudgetingCapital Budgeting PreparationPreparationIMIM Budget Budget release release
ExecutionExecution
EISEIS
EnterpriseEnterpriseManagementManagement
ConsolidationConsolidation BudgetingBudgeting
ECEC
Profit CentersProfit Centers
14
Basic Settings - FI Organizational Units
SAP AG 1999
Client 000
Company Code 1000
Business area 1000Business area 1000
Company Code 2000
Company Code 3000
Company Code 4000
Business area 2000Business area 2000
Client 001Client 400...
15
Creating new Company Code
SAP AG 1999
the definition
global parameters
customizing tables (approx. 315 tables)
general ledger accounts (if desired)
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 :
Define the chart of accounts,
Define the properties of the chart of accounts,
Assign the chart of accounts to company codes.
CAUSIKRINT
17
Contents of Chart of Accounts
SAP AG 1999
The definition of a chart of accounts contains:
Chart of accounts key
Description
General Information
Maintenance language
Length of the G/L account number
Controlling Integration
Manual or automatic creation of cost elements
Consolidation
Group chart of accounts
Status
“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
CC3000
CC2000
Inte
rnal
Rep
ort
ing
Ex
terna
l Rep
ortin
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
Inte
rnal
Rep
ort
ing
000001Operational Chart of Accounts INT
000001
Altern. Acc. no.0001
Company Code - Segments CC2000Altern. Acc. no.
0002
Ex
terna
l Rep
ortin
g
CC1000
CC20000001Country Chart of Accounts CAFR
0002
Altern. Acc. no.00010
Altern. Acc. no.00020
Company Code - Segments CC1000
00010Country Chart of Accounts CAUS
00020
++
+ +
... ...
... ...
... ...
21
Variant Principle
•Variant Principle is SAP’s 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 thanfiscal year
The posting periods correspond to the months in
the year
Jan.
Feb.
Mar
Apr.
May
JuneJuly
Aug.
Sept.
Oct.
Nov.
Dez.
0102
03
04
050607
1211
10
09
08
Apr.
May
June
July
Aug.
Sept.Oct.
Nov.
Dec.
Jan.
Feb.
Mar
01
02
0304
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
1100
11
28
Exchange rates - maintenance
SAP AG 1999
Exchange rate type
From
Ev
ery
us
ed
ex
ch
an
ge
ra
te t
yp
e !
Every currency combination !
Ev
ery
da
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 Data2
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
G/L Accounts
Customer/Vendor Accounts
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
Manual
Two - Step:
1. Chart of Accounts Segment, 2. Company Code Segment
One - Step: Create both segments simultaneously
Copying
Copying an individual GL account with reference to another GL account
Copy the entire company code segment
Copy the entire chart of accounts segment
Data Transfer
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
000001P+L statement acct type Balance sheet account
000002P+L statement acct type Balance sheet account
000001
yy
Ca
rry fo
rwa
rd
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
The number ranges of the GL accounts
Account group control
C
Gen
eral
Led
ger 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 - 099999Account
group
Chart of accts sgmnt
Company code segment
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:
?
Suppressed
Display
Required entry
Possible entry
G/L account
Joint Venture
Account control
Account management
1000
001111Chart of accountsCompany code
INT
Account currencyTax category
Alternative account number
Open item managementLine item display
Sort keyAuthorization group
Cost type
G/L account
Name
Short text
Account group
Control in chart of accounts
Partner company
Consolidation in chart of accounts
001111
INTChart of accounts
Group account number
G/L account long text
Sample accountP&L accountBalance 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
Ge
ne
ral
Le
dg
er
Su
b-le
dg
ers
Customer
aa bb
Acc
ts R
ec.
Acc
ts P
ay.
Vendor
cc dd
47
Account groups in AR and AP
SAP AG 1999
The account group controls:
The number ranges of the accounts,
The status of the fields in the master record,
If the account is a one time customer or vendor.
C
Acc
ou
nts
Pay
able AP
Dom.
For.
CPD
0001
...
000000 - 099999
100000 - 199999
200000 - 299999
300000 - 399999
400000 - 499999
500000 - 599999
600000 - 699999
AP accounts
C
Acc
ou
nts
Rec
eiva
ble
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
12345addressGeneral data
...
Client level
Company Code -Segment CC1000
Sales area segmentSales area 001
A AA
49
Vendor Account – Complete View
SAP AG 1999
Account 12345 in CC 2000
Company Code -Segment CC2000
Account 12345 in Purchasing Org 002
12345addressGeneral data
...
Clientlevel
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 specificinformation (bank details,...)
Account 1000
Address
Communication
Account CPD
Address
Communication
-
NameStreetCity...
LanguageTelephone...
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
1010
Cust. AClient level
Account control
Vendor
Vend. BClient 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
1010bank account
of Y or Z
To address or bank account of
M or N10
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 dataFSS4 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 keyHouse bk comm. data
House Bank Data
+ DME/EDI - data
House bank dataBank 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 currencyBank 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
Documents3
62
Purpose of documents in SAP
SAP AG 1999
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.
Different financial business transactions need different data within the documents. Some extra data may even be required for special
postings.
The accounting department wants to be sure that it is impossible to post to a previous
posting period.
Head accountants should have more posting authority than their staff.
63
Sample document types…
SAP AG 1999
Customer
InvoicesDR Customer
Credit
MemosD
G
Customer
PaymentsDZ
G/L account
Postings SA
Vendor
InvoicesKR Vendor
Credit
Memos
KG
Vendor
PaymentsKZ Vendor net
invoices
and credit
memos
KN
General
DocumentsAB
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 YearDocument Date Posting Date Period
Currency ... .....
001
002
Acct
Acct Description
Description Amount
Amount
+
-
.... .
Header
Amount
Tax Code
Business Area Cost Center
Text...
DT
PKPK
66
How is Field Status determined?
SAP AG 1999
Field
Account -
dependent
field status
Posting key -
dependent field
status
?
Prio
rityP
riority
Accountyes
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 CenterText...
Tax Code
69
Posting keys available
SAP AG 1999
010203040506070809
Customers
111213141516171819
313233343536373839
Vendors
212223242526272829
50909193949596
G/L
40808183848586
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
02EX
02
SB
01
DR
00
71
Open posting periods…
SAP AG 1999
Open posting periods during the fiscal year
Open posting periods during the closing procedure
0102
03
04
050607
1211
10
09
08
1514 1613
0102
03
04
050607
1211
10
09
08
open
open
open
72
Open and Close posting periods
73
Simple FI entries…
SAP AG 1999
5002
200000
Customer
220000 550011 2
Sales
Output tax
Vendor
1100 110000 112
Input tax
11
Expense
11
2
5000
Cash
5000
Bank
11 11
2
100000
11 10000
21000
100 2
1120000
50002
G/L account postings
Vendor invoices and
credit memos postings
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 100011 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
0003ZB
75
Document reversal
SAP AG 1999
Company
DocumentMMM
2,500
Account 1
2,050
Account 2
2,050
Account 1
2,500
Account 2
2,500
Company
DocumentMMM
2,500
Account 1
2,050
Account 2
2,050
Company
DocumentMMM
2,500
Document entered incorrectly
Document corrected by Reversal
Reverse with a standard reversal posting
Reverse with a negative posting
Document re - entered correctly
ItemsDocument
D Account 1C 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 20502050 2050
2050 2050- 2050 - 2050
Incorrect posting
0 0 0 0
2050
20500
0
Standard reversal posting
Negative posting
PostenBeleg
S Konto 1H 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 1Doc. Y, item 9Doc. Z, item 4
...
Doc. A, item 3Doc. B, item 2Doc. 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 DocumentFB03 Display DocumentFV50 Park GL DocumentFBV3 Display Parked DocumentFV50 Post parked Document
Accounts Receivable
FB70 InvoiceFB75 Credit Memo
Accounts Payable
FB60 InvoiceFB65 Credit MemoF-43 Vendor Invoice (With Special GL indicator)
FB08 Individual Reversal of Document
79
Hands-on exercises : Displaying Account balances
GL Accounting
FS10N Display BalancesFBL3N Display/ Change Line ItemsF.01 Balance Sheet/ P+L Statement
Accounts Receivable
FD10N Display BalancesFBL5N Display/ Change Line Items
Accounts Payable
FK10N Display BalancesFBL1N 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
furtherimportant
fields+
furtherimportant
fields+
Doc. Y, item 9Doc. Z, item 4
...
Doc. B, item 2Doc. C, item 7
...
Doc. X, item 1Doc. Y, item 9Doc. Z, item 4
...
Doc. A, item 3Doc. B, item 2Doc. C, item 7
...
82
Clearing concept
SAP AG 1999
February1 2 3 4 5 6 78 9 10 11 12 13 14
16 17 18 19 20 21 2223 24 25 26 27 28 2929 30 31
Open item account
2,000 5,000
Can be cleared
Check Deposit
Company
InvoiceMMM
Company
InvoiceMMMJanuary
1 2 3 4 5 6 78 9 10 11 12 13 14
16 17 18 19 20 21 2223 24 25 26 27 28 2929 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
Taxes4
85
Purpose of Tax codes
SAP AG 1999
The tax code is used to:
State
verify the amount of tax
calculate the amount of tax
calculate additional tax portion
verify the tax type
determine the G/L account
show tax correctly on tax forms
Taxcode
A0 V0
0O 0I 0I
86
Tax rate maintenance
SAP AG 1999
Level
110110
120120
100100
nnnnnn
Condition
BASB
MWAS
MWVS
xxxx
Fr. Level
100100
100100
00
nnnnnn
Tax type
Base amount
Output tax
Input tax
Any other tax
MWS
VST
xxx
Account key Rate
16.000
Taxcode
A0 V0
0O 0I 0I
87
Sample tax code (FTXP)
88
Posting of taxes
SAP AG 1999
ExpenseVendor Input tax
Posting as separate line item (standard case)
ExpenseVendor Input tax
Distribute to relevant expense/revenue items (process NVV for sales taxpayables or other non deductible input taxes)-
89
Account determination for taxes
SAP AG 1999
Account key
MWSOutput tax
Input tax VST
Chart of accounts
RULESRULES POSTING KEYSPOSTING KEYS
Accounts are determined based on
Posting key
INT
Chart of accounts: INTAccount key: MWS
Account: “Tax accrual”
Debit/CreditTax Code
Debit : 40Credit : 50
90
Account determination for taxes (OB40)
91
Payments and Dunning5
92
Manual payments
SAP AG 1999
Document header
Post
Process open items
1. Payment header
2. Bank data
3. Select open items1. 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 documentVendor
1010
Cash
10
Calculate the payment amount, taking account of cash discount periods
AutomaticManual
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
Cash discounts paid or received
Cash discount clearing (net method)
Tax adjustments
Exchange rate differences
Bank charges
Clearing entries for cross - company code payments
Over - or underpayments within tolerances
5,000
97
Exchange rate differences
SAP AG 1999
Foreign VendorOutgoing Payments
20 LC
Exchange Rate Differences
40 LC
20 LC
20 LC
40 LC
Open Item Rate : 0.5Rate : 0.25
10 FC10 FC10 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 5000Partial
Payment
Invoice reference
Residual Item
Customer/Vendor
8000 5000
3000
Payment Diff .
3000
Customer/Vendor
8000 5000
3000
Partial Payment
both items remain on the account
Residual Item
payment term
from cleared item
fixed payment term
new document referencing originals
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......
Line items cleared in error
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 SD6
106
Integration of GL with other sub-modules
SAP AG 1999
SD
CO
GeneralLedger
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 channel12 — Resellers
Distribution channel10 — Fin. cust . sales
Distribution channel14 — Service
Sales organization1000 — FrankfurtA A
A
Sales organization1020 — BerlinA A
A
Distribution channel16 — Factory sales
Distribution channel22 — Indust . customers
Distribution channel20 — 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 channel10 — Finalcustomer sales
Sales organization1000 — FrankfurtA A
A
Distribution channel 12 — Reseller
Sales organization1000 — FrankfurtA 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 channel10 — Final customer sales
Sales organization1000 — FrankfurtA 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 insales area 1000 - 10- 10
Company code -specific settings
Sales area -specific settings
Sales area1000 -10-10
CC 1000
Customer X
Generaldata
Account definitionat client level
111
Sales process & FI postings…
SAP AG 1999
Sales
...
...
Line items
DocumentOutbound delivery
SD FI
No documentSalesorder
Outbound delivery Transfer order Goods issue
Billing
Picking Goods issue
SD FI
Billingdocument ...
...
Line items
Invoice
MMSD
Shipping
112
Integration with MM7
113
MM Integration with FI
SAP AG 1999
CC 1000IDES Germany
Plant 1000Hamburg
Plant 1100Berlin
Plant 1200Dresden
Plant 1300Frankfurt
Plant 1400Stuttgart
114
Purchasing Organization
SAP AG 1999
CC 1000IDES Germany
Plant 1000Hamburg
Plant 1100Berlin
Plant 1200Dresden
Plant 1300Frankfurt
Plant 1400Stuttgart
Purchasing organization1000 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
MaterialGR/IR
Line items
Document
GR/IRVendorTax
Line items
Document
Material stock or consumption
1
12
2
Materialdocument
Goodsreceipt
MM FI
FI
Purchaseorder
Orderamount
MM
Invoiceverificationdocument
116
Recurring entry…
SAP AG 1999
The Recurring Entry Program
1000
Vendor
1000
Expense
Template: Recurring entry original document
Line items001 40 Expense 1000 002 31 Vendor 1000-
First posting 01.01.XXLast posting 12.01.XXNext posting 02.01.XXInterval in Months: 1
Recurring entry program
Batch input session
Settlement period:02.01.XX - 02.29.XX
Next posting on 03.01.XX
Actual posting
117
Hands-on exercises : Recurring Entries
FBD1 Recurring Entry DocumentFBD3 Display Recurring DocumentF.14 Execute Recurring EntriesF.15 Recurring Entry List
118
End of training!Time for
practice!!