You are on page 1of 118

Base Training for SAP FI

Possible Consulting Inc


Name: Designation: Date: February, 2004

Copyright Wipro Technologies 2004

The agenda

1 2 3 4

Overview & Basic Settings Master Data

Documents

Taxes

The agenda Contd.

5 6 7

Payments and Dunning Integration with SD

Integration with MM

Navigation in SAP

Initial login screen to SAP

Enter the Client, User name, Password and Language in this screen

SAP Easy Access screen (First screen when you login)

Use the command field if you know the tcode

Navigate through the menu to access transactions

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

SAP Implementation Guide (IMG)

Use the menu path to configure

How to access help in SAP?

Select SAP Library for help on IMG or transactions

Click on Application Help, for contextdependent help

Overview & Basic Settings

10

SAP Modules

Sales & Distribution Materials Mgmt.

SD

Financial Accounting

FI

MM

Product Planning

PP

R/3 R/3
HR

CO
Controlling

TR
Treasury

Quality Mgmt.

Client/Server QM Client/Server PS ABAP/4 PM ABAP/4 WF


Plant Maintenance

Project System

Workflow

Human Resources

IS
Industry Solutions

11

SAP Integration

12

SAP Financials Structure


.
EC

Enterprise Management
EIS Consolidation Budgeting Profit Centers

TR

FI

CO

Cash
Management Treasury Management Market Risk Management Funds Management

General Ledger Legal Consolidation Accounts Receivable Accounts Payable Asset Accounting

Overhead Cost
Controlling Activity-Based Costing Product Costing Profitability Analysis

IM

Capital Budgeting

Preparation Budget
release

Execution
13

Basic Settings - FI Organizational Units

Client 000 Client 001 Client 400 ...

Company Code 1000

Company Code 2000

Company Code 3000

Company Code 4000

Business area 1000 Business area 2000

SAP AG 1999 14

Creating new Company Code

To create a company code, copy an existing company code using the organization copy function, which copies:
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.

SAP AG 1999 15

Defining Chart of Accounts

The three steps to create and use a chart of accounts : l l l Define the chart of accounts, Define the properties of the chart of accounts,

Assign the chart of accounts to company codes.

INT

IKR

CAUS

SAP AG 1999 16

Contents of Chart of Accounts

The definition of a chart of accounts contains:


l l Chart of accounts key Description

General Information
l l Maintenance language Length of the G/L account number

INT

Controlling Integration
l Manual or automatic creation of cost elements

Consolidation
l Group chart of accounts

Status l
Blocked indicator

SAP AG 1999 17

Assigning Chart of Accounts to Company Code

CC1000
INT

CC2000
CAUS

CC3000

SAP AG 1999 18

Group COA for internal reporting

Operational Chart of Accounts CAUS 00010 group account number: 000001 00020 group account number: 000002

CC3000

External Reporting

Internal Reporting

Group Chart of Accounts INT 000001 ... 000002 ...

Operational Chart of Accounts CAFR 0002 0001 group account group account number: 000001 number: 000002

CC2000

SAP AG 1999 19

Country COA for external reporting

Country Chart of Accounts CAUS 00010 00020 ... ... Company Code - Segments CC1000 Altern. Acc. no. Altern. Acc. no. 00010 00020 + + Operational Chart of Accounts INT 000001 000001 ... ... + + Company Code - Segments CC2000 Altern. Acc. no. Altern. Acc. no. 0001 0002 Country Chart of Accounts CAFR 0001 0002 ... ... CC1000

Internal Reporting

CC2000

External Reporting

SAP AG 1999 20

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)

21

Fiscal Year Variants

Calendar year = Fiscal year

Calendar year different than fiscal year


-1

Dez. Nov. 11 Oct. Sept. 10 09 08 07 July

Jan.

-1 Feb. Feb.

Mar 06

Apr. May 01 June 02 July

12

01
02

Mar 03

- 1 Jan. 05 Dec. Nov. 04 Oct. 03 Sept.

04
05 06 June

Apr. May

Aug.

Aug.

Begin: April/1/2000 End: March/31/2001 The posting periods correspond to the months in the year
SAP AG 1999

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

22

Sample Fiscal year variants

23

Defining local currency

Local currency = Company code currency

24

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.

25

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.

26

Exchange rates - ratios

1 1

1 100
SAP AG 1999 27

Exchange rates - maintenance

Exchange rate type


Every used exchange rate type !

From

To

Valid from

Exchange rates

Every day ?

A lot of daily work! ==> tools offer help

Every currency combination !


SAP AG 1999 28

Exchange rate maintenance

29

Hands-on exercises

Login and navigate in SAP R/3 Calling functions Create company code Fiscal year variant

30

End of Day 1! Time for practice!!


31

Master Data

32

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.

33

Master Data in Financial Accounting

l l l

G/L Accounts Customer/Vendor Accounts Bank Master Data

SAP AG 1999 34

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.

35

Creating GL Accounts

Manual
n

Two - Step:

w w
l

1. Chart of Accounts Segment, 2. Company Code Segment One - Step: Create both segments simultaneously

Copying
n

Copying an individual GL account with reference to another GL account Copy the entire company code segment

n n

Copy the entire chart of accounts segment

Data Transfer
n

Upload a new chart of accounts from an external system e.g. flat file

SAP AG 1999 36

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.

37

GL Account types & carry forward


Balance Sheet and P+L Statement Accounts

000001 P+L statement acct type Balance sheet account 000001 yy

000002 P+L statement acct type Balance sheet account 000001 yy

Carry forward

X := 900000 000001 yy 000001 0 900000 yy

SAP AG 1999
38

Sample GL Account - Balance Sheet

39

Sample GL Account P & L

40

Concept of Account Groups

Cash accounts Chart of accts sgmnt

Company code segment

Konto 001111

General Ledger

Cash
000000 - 099999

Cash
000000 - 099999

C
100000 - 199999

Asst
200000 - 299999

Matl
300000 - 399999

Account group control

400000 - 499999

P/L

l The number ranges of the GL accounts


l The field status of the fields in the company code segment of the master record

Liab
500000 - 599999

...
600000 - 699999

SAP AG 1999 41

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

42

Field Status concept

Chart of accts segment


G/L account Chart of accounts
Control in chart of accounts

Company code segment


G/L account Chart of accounts Company code
Account control Account currency Tax category Alternative account number Account management Open item management Line item display Sort key Authorization group Joint Venture Cost type

001111 INT

001111 INT 1000

Account group
Sample account P&L account Balance sheet acct Name Short text G/L account long text Consolidation in chart of accounts Partner company Group account number

Each field has one of the following properties:

l l l

Suppressed Display Required entry Possible entry


43

SAP AG 1999

Example of Field Status Group

44

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.

45

Customer and Vendor reconciliation accounts

General Ledger

Recon. account. for acct type: D Trade Receivables aa


bb

Recon. Account. for acct type: K Trade Payables cc dd

Accts Rec.

Accts Pay.

Customer bb aa

Vendor cc dd

SAP AG 1999 46

Account groups in AR and AP

AR accounts

AP accounts

The account group controls:

Accounts Receivable

000000 - 099999

Accounts Payable

AR C
100000 - 199999

AP
000000 - 099999

C
100000 - 199999

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.

Dom.
200000 - 299999

Dom.
200000 - 299999

For.
300000 - 399999

For.
300000 - 399999

CPD
400000 - 499999

CPD
400000 - 499999

0001
500000 - 599999

0001
500000 - 599999

...
600000 - 699999

...
600000 - 699999

SAP AG 1999 47

Customer Account complete view

Client level

12345 address General data ...

Account 12345 in CC 1000


Company Code Segment CC1000

Account 12345 in sales area 001


Sales area segment Sales area 001

A A A

SAP AG 1999 48

Vendor Account Complete View

Client level

12345 address General data ...

Account 12345 in CC 2000


Company Code Segment CC2000

Account 12345 in Purchasing Org 002


Purchasing Organization segment

SAP AG 1999 49

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.

50

One-Time Accounts usage


-

Account 1000
Address Name Street City ... Communication Language Telephone ...

Address

Account CPD
Address Name ...

Address

Communication Language ...

+ other customer/vendor specific information (bank details, etc.)

no customer/vendor specific information (no bank details, ...)

Document

Document
+ customer/vendor specific information (bank details,...)

SAP AG 1999 51

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.

52

Same party as customer and vendor

Cust. A Client level Account control Vendor and Autom. Paym. Tr. Clrg with vend. Vend. B Client level

Vend. B Account control Customer and Autom. Paym. Tr. Clrg with cust. Cust . A

Cust. A 10 10

Vend. B 10 10


SAP AG 1999


53

Payment to/ from a different party

Cust. A Client level Paym. Trans. Alt. Payer Cust. Y or Autom. Paym. Tr. + Alt. Payer Cust. Z Client level

Vend B.
Paym. Trans. Alt. Payee Vend. M or Autom. Paym. Tr.

Alt. Payee Vend. N

Cust. A 10 10


SAP AG 1999

bank account of Y or Z

To address or bank account of M or N

Vend. B 10 10


54

Hands-on exercises

FS00 FSS4 FD01 FK01

Edit G/L Account Company Code data Display changes in company code data Create customer Create Vendor

55

End of Day 2! Time for practice!!


56

Bank Master Data

House Bank Data


Company Code House Bank - ID House bank data Bank country Bank key House bk comm. data ... + DME/EDI - data

Bank Master Data Bank country Bank key Address ... Control data ...

Client level

Banks

SAP AG 1999 57

Sample Bank Master

58

Linking Bank accounts to GL accounts

Bank account at house bank

Bank Account House Bank - ID Account - ID Bank acc. data Bank account Currency G/L - Account

G/L Account Account no Account control Account currency Bank/Fin. details House bank Account ID

SAP AG 1999 59

Sample House bank

60

Documents

61

Purpose of documents in SAP

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.

SAP AG 1999 62

Sample document types

DR

DG

KG

KR

AB

SAP AG 1999 63

KN

KZ

SA

DZ

Document Type configuration

64

Structure of FI Document

Overview Document Number Document Date Currency .. Items 001 002 . PK PK . Acct Acct . Company Code Posting Date ... Fiscal Year Period ...

Detail

Document Header
Account Line Item 1 / Amount Tax Code

DT

Description Description .

Amount Amount

+ .

PK

Additional Details Business Area Cost Center Text ...

SAP AG 1999 65

How is Field Status determined?

Field relevant for postings on accounts of this type? Posted with which posting key?
PK PK

no

suppress

... ...

yes

Posted on which account?

Account

Priority

SAP AG 1999 66

Sample FI Document

67

Purpose of Posting Keys

Detail view
Account Line Item 1 / PK Amount Tax Code 2. debit, credit ? 1. S, D, K, A, M ?

The Posting Key has control functions within the line items. It controls: 1. on which type of account the line item can be posted to 2. if the item is posted as a debit or credit 3. the field status of additional details

Additional Details Business Area Cost Center Text ...

3. Field Status ?

SAP AG 1999 68

Posting keys available

Customers 01 02 03 04 05 06 07 08 09 11 12 13 14 15 16 17 18 19

Vendors 21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 39

G/L 40 80 81 83 84 85 86 50 90 91 93 94 95 96

Assets 70

Materials
89

For G/L - Postings out of Materials Management

75

99

SAP AG 1999 69

Internal and External number ranges

9999999999

02
9000000000 8000000000 7000000000 6000000000 5000000000 4000000000 3000000000 2000000000 1000000000 0000000000
SAP AG 1999 70

external numbering
current numbers 01 internal numbering defined until fiscal year in the future

current numbers
00 internal numbering defined per fiscal year 1998 1999 2000 2001...

Open posting periods

Open posting periods during the fiscal year

Open posting periods during the closing procedure open

12 11 10 09 08

01 02 03 04 05

13

14

15

16

12
11

01 02 03

10
09

07

06

04 08
07 06 05

SAP AG 1999 71

Open and Close posting periods

72

Simple FI entries

l G/L account postings

Cash 5000

Bank
5000

Expense

Vendor 2 2 1100 110000 1

l Vendor invoices and credit memos postings

100000

1000

Input tax 1 10000 100 2

Customer

Sales 2 2 5000 200000 1

l Customer invoices and credit memo postings


SAP AG 1999

220000

5500

2
2

Output tax 500 20000 1


73

Rules for changing documents

Different document change rules based on: Account type: A, D, K, M, S Special G/L transactions: Down payment,

Down payment requests, . . .


Company code

Prerequisites for field changes

Posting period open


Line item not cleared Posting as debit / posting as credit
1 Account 1000 Cr . memo Invoice relation / 1000 2

No invoice - related credit memo


No credit memo from down payment
SAP AG 1999

Z B 0003 /

74

Document reversal

Document
Items

Account 1 M Document
Company

D Account 1 C Account 2

2,050 Account 2

Document entered incorrectly

2,500

2,050

Account 1 M Document
Company

Document corrected by Reversal


n

2,050 Account 2

Reverse with a standard reversal posting Reverse with a negative posting

2,500

2,050

Account 1
M Document
Company

2,500

Account 2
2,500 SAP AG 1999 2,500

Document re

- entered correctly

75

Correction options

Beleg
Posten

S Konto 1 H Konto 2

l Standard reversal posting

Incorrect posting
Account 1 2050 2050 Account 2 2050 0 2050 0

Account 1 2050 2050 2050 2050

Account 2 2050 2050 2050 2050

l Negative posting Account 1 2050 2050 - 2050 0 0 0 2050 Account 2 2050 2050 2050 - 2050 0
76

SAP AG 1999

Line items for GL accounts

Account without line item display Index to documents Transaction figure / debit Transaction figure / credit

Account

with line item display Doc. A, item 3 Doc. B, item 2 Doc. C, item 7 ... Further important fields

Doc. X, item 1 Doc. Y, item 9 Doc. Z, item 4 ...

Further important fields

Transaction figure / debit

Transaction figure / credit

SAP AG 1999 77

Hands-on exercises : Document creation


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

Accounts Receivable

FB70 FB75

Invoice Credit Memo

Accounts Payable FB60 FB65 F-43 FB08 Invoice Credit Memo Vendor Invoice (With Special GL indicator) Individual Reversal of Document
78

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

79

End of Day 3! Time for practice!!


80

Open item managed accounts

Account Doc. X, item 1 Doc. Y, item 9 Doc. Z, item 4 ...

without

open item management Doc. A, item 3 Doc. B, item 2 Doc. C, item 7 ... Further important fields

Further important fields

Transaction figure / debit Account Doc. X, item 1 Doc. Y, item 9 Doc. Z, item 4 ...

Transaction figure / credit

with open item management

further + important fields

Doc. A, item 3 Doc. B, item 2 Doc. C, item 7 ...

further + important fields

Transaction figure / debit


SAP AG 1999

Transaction figure / credit

81

Clearing concept

Company

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

M
M

1
Open item account 2,000 3,000

2
Check Deposit

Company Invoice

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

Invoice

5,000

Can be cleared

3 CLEARING AN ACCOUNT POST WITH CLEARING

SAP AG 1999 82

Clearing within an account

ACCOUNT CLEARING

Open item account 2000 3000 Account clearing 5000 1000

Open item account 2000 3000 5000 1000

Clearing document
Items

SAP AG 1999 83

Taxes

84

Purpose of Tax codes

The tax code is used to:


n n

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

Tax code
A0 V0 0O 0I 0I

n n n n

State

SAP AG 1999 85

Tax rate maintenance

Tax code
A0 V0

0O 0I 0I

Tax type Base amount Output tax Input tax Any other tax

Account key

Rate

Level 100

Fr. Level 0 100 100 nnn

Condition

BASB
MWAS MWVS xxxx

MWS VST xxx

16.000

110 120 nnn

SAP AG 1999 86

Sample tax code (FTXP)

87

Posting of taxes

l Posting as separate line item (standard case) Vendor Expense Input tax

l Distribute to relevant expense/revenue items (process NVV for sales tax payables or other non deductible input taxes) Vendor Expense Input tax

SAP AG 1999 88

Account determination for taxes

Account key
Output tax Input tax MWS

VST

Chart of accounts INT

Chart of accounts: Account key: Account: RULES

INT MWS Tax accrual POSTING KEYS Posting key Debit Credit : 40 : 50
89

Accounts are determined based on Debit/Credit Tax Code


SAP AG 1999

Account determination for taxes (OB40)

90

Payments and Dunning

91

Manual payments

POST AND CLEAR

Document header
1. Payment header

2. Bank data
3. Select open items

Process open items


1. Activate items 2. Activate cash discount

Post
1. Display 2. Post
SAP AG 1999 92

overview

Outgoing payments

Select payment method and bank Select items for payment

S
Cash 10 Vendor 10 10

Calculate the payment amount, taking account of cash discount periods

Post the payment document

Print payment medium

Manual
SAP AG 1999

Automatic
93

Automatic Payment Program

94

Sample APP

95

When clearing, additional line items are created for

l l l
Open item account 2,000 3,000 5,000 5,000

Cash discounts paid or received Cash discount clearing (net method) Tax adjustments

l l l

Exchange rate differences


Bank charges Clearing entries for cross payments - company code

Can be cleared

Over - or underpayments within tolerances

SAP AG 1999 96

Exchange rate differences

Outgoing Payments

Foreign Vendor Rate : 0.25

Open Item Rate : 0.5


20 LC 20 LC 10 FC

40 LC

10 FC

40 LC

10 FC

Exchange Rate Differences 20 LC

SAP AG 1999 97

Accounting for incoming payments

Complete payment

Minor payment difference


(within tolerances)

Greater payment difference


(outside tolerances)

Post partial payment Customer 8000 5000

Generate residual item


Customer

Partial payment
Residual item

8000

5000

Invoice reference to open item


SAP AG 1999

3000

98

99

100

When the complete amount is not paid

Customer/Vendor
8000 5000 Partial Payment

Partial Payment
n

both items remain on the account

Invoice reference

l
Customer/Vendor

Residual Item
n

payment term

8000
3000

5000 Residual Item


n

w w

from cleared item

fixed payment term

new document referencing originals

Payment
3000

Diff .

Customer/Vendor
8000 5000 3000

Charge off difference

SAP AG 1999 101

When the clearing is wrong

Open item account


2000 3000 5000 1000 Reset cleared items

Open item account


2000 3000 5000 1000

l
l

Line items cleared in error Cancel clearing by resetting clearing document and cleared items
Items
... ...

Clearing document Reset

SAP AG 1999 102

Hands-on exercises : Clearing

F-03

Clear GL Account

F-32
F-44 F-53 F-28

Clear Customer
Clear Vendor Post outgoing payment (Partial Payment) Incoming Payment

103

End of Day 4! Time for practice!!


104

Integration with SD

105

Integration of GL with other sub-modules

CO

FI BL

FI TV

FI AA

MM

FI AP

FI GL

General Ledger

FI AR

SD

Balance Sheet ... P&L ... ...

SAP AG 1999 106

SD Organization structure

IDES Distribution

Chains in Germany
Company code Germany 1000

A A A

Sales organization 1000 Frankfurt

A A A

Sales organization 1020 Berlin

Distribution channel 10 Fin . cust . sales Distribution channel 12 Resellers Distribution channel 14 Service Distribution channel 16 Factory sales
SAP AG 1999

Distribution channel 20 Store chains Distribution channel 22 Indust . customers Distribution channel 24 Pharmaceutical customers

107

Logistics Integration with FI

Plant 1000 Hamburg

Company code Germany

1000

... sells goods from ...

... posts the sale in ...

A AA

Sales organization 1000 Frankfurt Distribution channel 10 Final customer sales Distribution chain 1000 10

A AA

Sales organization 1000 Frankfurt Distribution channel 12 Reseller Distribution chain 1000 12

SAP AG 1999 108

Sales area example

Divisions

Sales area 1000 10 02 02

A AA

Sales organization 1000 Frankfurt Distribution channel 10 Final customer sales Distribution chain 1000 10

Sales area 1000 10 03


03

Sales area 1000 10 05 05


SAP AG 1999 109

Sales area usage

Customer X General data

Account definition at client level

PLUS

PLUS

Company code specific settings

Sales area specific settings

CC 1000

Sales area 1000 - 10 - 10

Customer
SAP AG 1999

X in company code

1000

Customer X in sales area 1000 - 10 - 10


110

Sales process & FI postings

SD Sales
Sales order

FI No document

Shipping
Outbound delivery
Outbound delivery

Transfer
Picking

order

Goods issue
Goods issue
Document
Line items ... ...

SD

MM

SD
Billing
Billing document

FI
Invoice
Line items ... ...

SAP AG 1999 111

Integration with MM

112

MM Integration with FI

CC 1000 IDES Germany

Plant 1000 Hamburg


SAP AG 1999

Plant 1100 Berlin

Plant 1200 Dresden

Plant 1300 Frankfurt

Plant 1400 Stuttgart

113

Purchasing Organization

Plant 1000 Hamburg

Plant 1100 Berlin

Plant 1200 Dresden

Plant 1300 Frankfurt

Plant 1400 Stuttgart

Purchasing organization 1000 purchases for...

Purchasing organization 1000 IDES Germany

Purchasing is posted in...

CC 1000 IDES Germany

SAP AG 1999 114

The 3 way match (PO GR Invoice)


-

Goods receipt Purchase order MM


Purchase order Material document Goods receipt
Document
Line items Material GR/IR

Material stock or consumption


1

MM
Order amount

FI GR/IR
2 1

FI

Invoice receipt
Invoice verification document
Document
Line items GR/IR Vendor Tax

No document Vendor
2

MM
SAP AG 1999

FI

115

Recurring entry

116

Hands-on exercises : Recurring Entries

FBD1 FBD3 F.14 F.15

Recurring Entry Document Display Recurring Document Execute Recurring Entries Recurring Entry List

117

End of training! Time for practice!!


118

You might also like