SAP FI Overview

Designation:

Date: February, 2004

Copyright Wipro Technologies 2004

Base Training for SAP FI

Possible Consulting Inc

The agenda

Documents

Master Data

Overview & Basic Settings1

Taxes4

The agenda Contd. …

Integration with MM

Integration with SD

Payments and Dunning5

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)

Navigate through the

menu to access

transactions

Use the command field if you know the t-

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?

Click on Application

Help, for context-

dependent helpSelect SAP

Library for help on IMG or transactions

Overview & Basic Settings1

SAP Modules

R/3Client/Server

ABAP/4

Sales &Sales &DistributionDistribution

MaterialsMaterialsMgmt.Mgmt.

ProductProductPlanningPlanning

QualityQualityMgmt.Mgmt.

Plant Mainte-Plant Mainte-nancenance

HumanHumanResourcesResources

FinancialFinancialAccountingAccounting

ControllingControlling

TreasuryTreasury

ProjectProjectSystemSystem

WorkflowWorkflow

IndustryIndustrySolutionsSolutions

R/3Client/Server

ABAP/4

SAP Integration

SAP Financials Structure.

General Ledger Legal Consolidation Accounts Receivable Accounts Payable Asset Accounting

Overhead CostControlling

Activity-BasedCosting

Product Costing Profitability

Analysis

Cash Management

Treasury Management

Market RiskManagement

FundsManagement

Capital BudgetingCapital Budgeting PreparationPreparationIMIM Budget Budget release release

ExecutionExecution

EISEIS

EnterpriseEnterpriseManagementManagement

ConsolidationConsolidation BudgetingBudgeting

Profit CentersProfit Centers

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...

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:

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

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

Assigning Chart of Accounts to Company Code

SAP AG 1999

CC1000

CC2000

CC3000

Group COA – for internal reporting

SAP AG 1999

Operational Chart of Accounts CAUS

CC3000

CC2000

000001

Group Chart of Accounts INT

000002

0001 0002

Operational Chart of Accounts CAFR

... ...

group account number: 000002

Country COA – for external reporting

SAP AG 1999

000001Operational Chart of Accounts INT

000001

Altern. Acc. no.0001

Company Code - Segments CC2000Altern. Acc. no.

CC1000

CC20000001Country Chart of Accounts CAFR

Company Code - Segments CC1000

00010Country Chart of Accounts CAUS

... ...

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)

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

JuneJuly

050607

Sept.Oct.

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

Sample Fiscal year variants

Defining local currency

Local currency = Company code

currency

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.

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.

Exchange rates - ratios

SAP AG 1999

Exchange rates - maintenance

SAP AG 1999

Exchange rate type

Every currency combination !

A lot of daily work!

==> tools offer help

To Valid from Exchange rates

Exchange rate maintenance

Hands-on exercises

Login and navigate in SAP R/3

Calling functions

Create company code

Fiscal year variant

End of Day 1!

Time for practice!!

Master Data2

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.

Master Data in Financial Accounting

SAP AG 1999

G/L Accounts

Customer/Vendor Accounts

Bank Master Data

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.

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

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.

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

rry fo

000001

900000

X := 900000

Balance Sheet and P+L Statement Accounts

Sample GL Account - Balance Sheet

Sample GL Account – P & L

Concept of Account Groups

SAP AG 1999

The number ranges of the GL accounts

Account group control

ger Cash

000000 - 099999

100000 - 199999

200000 - 299999

300000 - 399999

400000 - 499999

500000 - 599999

600000 - 699999

Cash accounts

Konto 001111

000000 - 099999Account

Chart of accts sgmnt

Company code segment

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

record

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

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

001111Chart of accountsCompany code

Account currencyTax category

Alternative account number

Open item managementLine item display

Sort keyAuthorization group

Cost type

G/L account

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

Example of Field Status Group

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.

Customer and Vendor reconciliation accounts

SAP AG 1999

Trade Receivables

Recon. account. for acct type: D

Trade Payables

Recon. Account. for acct type: K

Customer

Vendor

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.

able AP

000000 - 099999

100000 - 199999

200000 - 299999

300000 - 399999

400000 - 499999

500000 - 599999

600000 - 699999

AP accounts

000000 - 099999

100000 - 199999

200000 - 299999

300000 - 399999

400000 - 499999

500000 - 599999

600000 - 699999

AR accounts

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

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

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.

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...

Language

Address Address

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.

Same party as customer and vendor…

SAP AG 1999

and and

Cust. A

Vend. B

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

Payment to/ from a different party…

SAP AG 1999

Cust. A

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.

Hands-on exercises

FS00 Edit G/L Account Company Code dataFSS4 Display changes in company code data

FD01 Create customer

FK01 Create Vendor

End of Day 2!

Time for practice!!

Bank Master Data

SAP AG 1999

Bank country

Client level

Address

Control data

Bank Master Data

Bank keyHouse bk comm. data

House Bank Data

+ DME/EDI - data

House bank dataBank country

Company Code

Bank key

House Bank - ID

Sample Bank Master

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

Sample House bank

Documents3

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.

Sample document types…

SAP AG 1999

Customer

InvoicesDR Customer

Credit

MemosD

Customer

PaymentsDZ

G/L account

Postings SA

Vendor

InvoicesKR Vendor

Credit

Vendor

PaymentsKZ Vendor net

invoices

and credit

General

DocumentsAB

Document Type configuration

Structure of FI Document

SAP AG 1999

Document

Overview Detail

Additional Details

Line Item 1 /

Account

Document Number Company Code Fiscal YearDocument Date Posting Date Period

Currency ... .....

Acct Description

Description Amount

Amount

.... .

Header

Amount

Tax Code

Business Area Cost Center

Text...

How is Field Status determined?

SAP AG 1999

Account -

dependent

field status

Posting key -

dependent field

status

riority

Accountyes

no suppress

Posted with which posting key?

Posted on which account?

PK ...

relevant for postings on accounts of this type?

Sample FI Document

Purpose of Posting Keys

SAP AG 1999

1. on which type of account the line item can be posted

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

Posting keys available

SAP AG 1999

010203040506070809

Customers

111213141516171819

313233343536373839

Vendors

212223242526272829

50909193949596

40808183848586

Assets

Materials

For G/L - Postings out of Materials Management

Internal and External number ranges

SAP AG 1999

0000000000

1000000000

2000000000

3000000000

4000000000

5000000000

6000000000

7000000000

8000000000

9000000000

9999999999

internal numbering defined per fiscal

external numbering

internal numbering defined until fiscal year in the future

current numbers

1999 2000 2001...

Open posting periods…

SAP AG 1999

Open posting periods during the fiscal year

Open posting periods during the closing procedure

050607

1514 1613

050607

Open and Close posting periods

Simple FI entries…

SAP AG 1999

200000

Customer

220000 550011 2

Output tax

Vendor

1100 110000 112

Input tax

Expense

100000

11 10000

1120000

G/L account postings

Vendor invoices and

credit memos postings

Customer invoices and

credit memo postings

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

Document reversal

SAP AG 1999

Company

DocumentMMM

Account 1

Account 2

Account 1

Account 2

Company

DocumentMMM

Account 1

Account 2

Company

DocumentMMM

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

Correction options…

SAP AG 1999

Account 1

Account 2

Account 1

Account 2

Account 1

Account 2

2050 2050

2050 20502050 2050

2050 2050- 2050 - 2050

Incorrect posting

0 0 0 0

Standard reversal posting

Negative posting

PostenBeleg

S Konto 1H Konto 2

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

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

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

End of Day 3!

Time for practice!!

Open item managed accounts

SAP AG 1999

Account without open item management

Doc. X, item 1 Doc. A, item 3

Further important

fields+

Further important

fields+

Account with open item management

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

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

CLEARING AN ACCOUNT

POST WITH CLEARING

Clearing within an account

SAP AG 1999

Open item account

2000 5000

3000 1000

Open item account

2000 5000

3000 1000

Account clearing

Clearing document

ACCOUNT CLEARING

Taxes4

Purpose of Tax codes

SAP AG 1999

The tax code is used to:

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

0O 0I 0I

Tax rate maintenance

SAP AG 1999

110110

120120

100100

nnnnnn

Condition

Fr. Level

100100

nnnnnn

Tax type

Base amount

Output tax

Input tax

Any other tax

Account key Rate

16.000

Taxcode

0O 0I 0I

Sample tax code (FTXP)

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)-

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

Chart of accounts: INTAccount key: MWS

Account: “Tax accrual”

Debit/CreditTax Code

Debit : 40Credit : 50

Account determination for taxes (OB40)

Payments and Dunning5

Manual payments

SAP AG 1999

Document header

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

Outgoing payments

SAP AG 1999

Print payment medium

Select payment method and bank

Select items for payment

Post the payment documentVendor

Calculate the payment amount, taking account of cash discount periods

AutomaticManual

Automatic Payment Program

Sample APP

When clearing, additional line items are created for…

SAP AG 1999

Open item account

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

Exchange rate differences

SAP AG 1999

Foreign VendorOutgoing Payments

Exchange Rate Differences

Open Item Rate : 0.5Rate : 0.25

10 FC10 FC10 FC

Accounting for incoming payments

SAP AG 1999

Customer

8000 5000

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)

When the complete amount is not paid…

SAP AG 1999

Customer/Vendor

8000 5000Partial

Payment

Invoice reference

Residual Item

Customer/Vendor

8000 5000

Payment Diff .

Customer/Vendor

8000 5000

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

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

Clearing document

Reset......

Line items cleared in error

Cancel clearing by resetting clearing document and cleared

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

End of Day 4!

Time for practice!!

Integration with SD6

Integration of GL with other sub-modules

SAP AG 1999

GeneralLedger

Balance Sheet

... ...

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

Sales organization1020 — BerlinA A

Distribution channel16 — Factory sales

Distribution channel22 — Indust . customers

Distribution channel20 — Store chains

Company code 1000 — Germany

Distribution channel 24 — Pharmaceutical customers

Logistics Integration with FI

SAP AG 1999

Company code 1000 — Germany

Plant 1000 — Hamburg

Distribution channel10 — Finalcustomer sales

Distribution channel 12 — Reseller

... sells goods from ...

... posts the sale in ...

Distribution chain 1000 — 10 Distribution chain 1000 — 12

Sales area example

SAP AG 1999

Distribution channel10 — Final customer sales

Distribution chain 1000 — 10

Sales area 1000 — 10 — 02

Sales area 1000 — 10 — 03

Sales area 1000 — 10 — 05

Divisions

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

Sales process & FI postings…

SAP AG 1999

Line items

DocumentOutbound delivery

No documentSalesorder

Outbound delivery Transfer order Goods issue

Billing

Picking Goods issue

Billingdocument ...

Line items

Invoice

Shipping

Integration with MM7

MM Integration with FI

SAP AG 1999

CC 1000IDES Germany

Plant 1000Hamburg

Plant 1100Berlin

Plant 1200Dresden

Plant 1300Frankfurt

Plant 1400Stuttgart

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...

The 3 way match (PO – GR – Invoice)

SAP AG 1999

Purchase order

Goods receipt

Invoice receipt

Vendor

No document

MaterialGR/IR

Line items

Document

GR/IRVendorTax

Line items

Document

Material stock or consumption

Materialdocument

Goodsreceipt

Purchaseorder

Orderamount

Invoiceverificationdocument

Recurring entry…

SAP AG 1999

The Recurring Entry Program

Vendor

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

Hands-on exercises : Recurring Entries

FBD1 Recurring Entry DocumentFBD3 Display Recurring DocumentF.14 Execute Recurring EntriesF.15 Recurring Entry List

End of training!Time for

practice!!

SAP FI Overview

Documents

Transcript of SAP FI Overview

SAP FI - globalcoach.in

SAP Audit Issues - SAP FI/CO Training

SAP FI Currencies |

Transacoes FI SAP

SAP FI Config

Sap fi gl_configuration

Overview Tfin50 Sap Fi

SAP FI Blueprint Document

Academia SAP FI

81818903 SAP FI Overview

SAP Overview - The Basics of SAP FI/CO

Sap Fi Pagos

SAP FI - 2

Sap Overview-fi Co

Sap Fi Tcodes

Sap Fi Accounts Payable Overview

Basics SAP Fi

SAP FI BSCI

SAP FI Module

SAP FI Training