Source: http://omconsultancy.blogspot.

com/search/label/SAP%20FI%20Certification%20Material

SAP ECC 6.0 FI CERTIFICATION MATERIAL

Organizational Units

Client
o o o o

At highest level in ERP system Data entered at client level used for all organizational units Each client has its own set of master data

Important organizational units in FI

Company code: o Independent legal entity o For external purpose

o

Business Area o For internal purpose o Can be used across company codes o Can have financial statement for each Business Area

Create company code steps o Copy co. code o Copies : Definition (company name) Global parameters (COA, Fiscal year, Co code default) Tables G/L a/c's Account determination o Now edit this data Address Company code currency: This is company code / local currency. All other currencies are foreign currencies. Language Key Country key: This is home country. All other countries are foreign countries

Exercise: Organizational Units

Copy company code o Tcode: EC01 o Data : MR03

Change company code definition Tcode: SPRO ES- Def. FA- Edit, copy, Del- Check co. code- Edit company code data Data:

Co. code Country Currency Language

MR03 US USD EN

Enter company code Global Parameters

MR03 1000 INT 33 1000 MR05

Company code Company COA Fiscal Year Variant Field status variant Posting Period Variant

Variant Principle

Variant Principle: A 3 step method to assign properties to one / more objects Steps: o Define variant ( K4 Fiscal year variant) o Determine values for the variant defined: Variant properties o Assign variant to objects : Assign variant K4 to object company code Fiscal Year

Fiscal Year Variant: o Define a fiscal year with posting periods o Fiscal year contain posting periods + Special posting periods o Maximum periods = 16 o System derive period for a document from the posting date o Special posting period: o Used for yearend closing transactions. Posting date falls in last period, can post in special posting period th o E.g.: FY with PP = 12 and special period = 4. Transaction date falls in 12 posting period can post in th th 4 special (16 ) period. Year Independent Fiscal Year Variant: o FYV uses same number of periods each year o Posting period start and ends on the same date every year o Can be Calendar Year .Here PP = 12 months of the year o Can be non calendar year Here PP # 12 months of the year. PP can be from 1 to 16. Need to assign end date for each posting period Need to assign indicator -/+ as required e.g Apr to Mar. For Jan, Feb & Mar year shift of -1 as belongs to old fiscal year

1. Exercise: Fiscal Year

When is the year specific fiscal year variant used? o One fiscal year has fewer posting periods than others o Start and End dates of posting periods differ from year to year Maintain a Fiscal Year Variant o Tcode: OB29 o Data: FYV : 33 Assign Fiscal Year Variant (33) to company code MR03 o Tcode: OB37 Create a FYV (Non calendar year FYV) o Tcode: OB29 o Data:
64 4 periods 4 ( Each period has 4 months) 1

FYV Description Number of posting periods Number of special periods Provide necessary year shift

Define base currency: o Tcode: SAP Net weaver General settings Currencies Check Exchange Rate Type

Master Data:
1. General Ledger Accounts

Chart of Accounts: o A variant that contain basic of GL a/c o Has a 4 character ID o Define properties of GL a/c like language, Length of GL accounts o COA assigned to a company code Definition of Chart of Accounts o Tcode: OB13 o Define: COA key Description Maintenance language Length of GL a/c Manual / Automatic creation of cost elements Group chart of account Blocked / unblocked. If COA blocked, no GL a/c can be created for this COA Directory of GL a/c in COA: o Tcode: SE38 RFSKPL00

One COA can be assigned to one / more company codes (variant principle) COA contain information about GL in Company code segment and COA segment o Co. code Segment: To use one of the GL account from COA need to create a company code segment Control data Bank / Interest Information o Chart of Account Segment: Type / Description Key word in COA Information in COA Balance sheet a/c o Balance C/F to the same a/c P/L a/c:
o o

Balance carried forward to retained earnings a/c and balance set to zero A key is assigned to RE a/c which is the entered in the P/L statement a/c type

Account Group for GL a/c o Grouping of similar types of accounts. E.g. cash a/c, liquid funds a/c, fixed assets a/c, Expense a/c o Account group has a number range. For G/L accounts it's always internal number assignment o Account group controls the display of fields (Field status: Display/ Change ...) in the GL master (FS00) Field Status o Field status enable control and display of GL a/c' master data fields o Field status ranking:
Field Status Not used Field display only Field required value Rank 1 2 3 4

Status Hide Display Required Optional

Reconciliation account o This is a vendor / customer GL a/c in COA. Its corresponding account exist in vendor / customer sub ledger o All postings to sub ledger posted to reconciliation GL a/c in GL o Reconciliation a/c type: D: Customers, K: Vendors, Assets o Cannot post directly to reconciliation a/c o Details of customer / vendor reconciliation a/c: SE38 RFDKVZ00 Line Item Display o Show each transaction as a line in a GL a/c display o Line Item display not possible in following cases: o Reconciliation a/c (Line item display in sub ledger) o Revenue a/c (Sales) o Material Stock a/c o Tax a/c (Tax amount per line item checked when document displayed)

Open Item Management: o These a/c have line item display activated o Open Item display mandatory for a/c with offsetting entries o OI management used for following a/c types: Bank clearing a/c GRIR a/c Salary clearing a/c Account Currency o Can select company code currency / Local currency as Account currency o Can also select foreign currency as account currency o Where LC = A/C currency, can post in any currency o Where FC = A/C currency can post in only the FC to this GL a/c. Only balance in Local currency: o If selected transaction figures to this a/c posted in local currency only o To be selected for clearing a/c like GRIR to avoid difference due to exchange rates fluctuation o You would set this indicator for accounts in which you do not want the system to update transaction figures separately by currency. GL account creation
One step centrally COA Segment Co. Code segment Copy co. code segment from another company code Copy COA Segment from another COA

FS00 FSP0 FSS0 OBY2 OBY7

Customer / Vendor Accounts

Customer / Vendor Master Data have 3 segments o General data: At client level o Company code data: Any company code that wishes to do business with customer / vendor has to have a company code segment o Customer: Sales area segment o Vendor: Purchasing org. Segment SE38 RFBIDE10 / RFBIKR10: o To transfer customer / vendor master data from Source Company code to another company code Can activate automatic duplication check Account Group for customer / Vendor: o Once a customer / vendor created cannot change its a/c group in FI o Controls field status of customer / vendor master records o Controls customer / vendor number range

Number Range: o Can be internal / external o Each number range can be assigned to one / more account group Special Customer / Vendor master record o These are one time customer / vendor o No information about customer / vendor entered in the master record o Customer / Vendor information entered at the time of document posting o Special customer / vendor master record cam be used for more than one Customer / vendor Dual Control Principle o Can define certain customer / vendor fields in SPRO as sensitive. For e.g. vendor bank address o Now if these fields are changed customer /vendor is blocked for payment o Block removed when a second person with authorization confirms / reject such change

1. Exercise General Ledger, Customer, Vendor

Copy GL Account group o Tcode: OBD4 o Data:

Copy To CD05 AE05

Copy from SAKO ERG

Create a GL a/c in GL a/c group AE05

o o

Tcode: FS00 Data: 176499 (Expense a/c)

Display COA: o Tcode: SAP Easy FA GL Info System GL Reports Master Data GL a/c list Reconciliation a/c (Vendor / Customer) contain total of sub ledger transaction figures Create a/c group for customer o Tcode: SPRO FA AR/AP CA MD Preparation for creating CMD Define a/c group with screen layout o Data: Copy from KUNA to D05 Assign number range to a/c group (D05) o Tcode: SPRO FA AR/AP CA MD Preparation for creating CMD Create customer A/C in the account group D05 o Tcode: FD01 / Sap Easy Search term field in Vendor master record o Controlled by field status group o Search term A: Required entry so appear o Search Term B: Suppressed entry so not appear

Define sensitive fields for dual control o Tcode: SPRO FA AR/AP Vendor a/c Master data Preparation for creating vendor master Define sensitive fields for dual control Confirm customer / vendor master changes (Dual control) o Customer: FD09 o Vendor: FK09 Number Assignment o GL a/c: Only external number assignment o Customer / Vendor master Record: Can have either external / internal number assignment Create a Vendor a/c group o Tcode: SPRO- FA- AR/AP MD Preparation for creating vendor master record Define screen layout Assign number range to vendor a/c group Create Vendor a/c: o Tcode: FK01 Bank Accounts

Bank master Record o Bank master record table: BNKA o Change to bank master record / Display of bank changes: SE38 RFBKABL0 House Bank o House bank contain bank master data o Bank account information for electronic payment o GL a/c for each bank account in the HB Bank Type: o In customer / vendor master record field bank type is used to distinguish different banks o While processing vendor invoice (MIRO/FB60) user can chose the bank to which payment will be made by APP by selecting bank type in partner bank field Create Bank master record: FI01 Define HB: FI12 Create a saving a/c: FI12

Document Control
Document Structure

Document Principle: o A document is saved for every posting o Every document is identified by: Document number Company code Fiscal Year (Tcode: FB03)

Document Segment o Document Header o Document Line Items (2- 999 line items) Document Type o Tcode : OBA7 o Document Type defined at client level & applicable for all company codes o Document Types : AB (Post all GL ac), DG ( Customer and GL), RV (Customer Invoice), RE ( MM billing document) o Document Type Controls: Properties: Number Range Reverse Document Type Authorization group A/C Types Allowed: Asset Customer Vendor Material GL Control data: Negative Postings permitted Intercompany posting Net document Type: system automatically deduct cash discounts from vendor invoices that are posted with this document type Required during document Entry: Reference Number Document Header text Document Number Range: o Can be internal / external o Up to a Future Fiscal Year : Beginning of next fiscal year system uses number following the last number of the current fiscal year o For Each Fiscal Year: System starts with a new number each fiscal year o A document number range can be assigned to (02) multiple document types Posting Key o PK defined at client level & so valid for all company codes o PK Control: D/C indicator Account type that can be posted ( Customer / Vendor / GL/ Asset / Material) Other Attributes Whether line item connected with payment ( select where incoming / outgoing payment transactions) Indicator whether PK used for entering special GL transactions Maintain field status: (Field status : Suppress, Required, Optional) General Data (Assignment number, Text, Invoice reference) Additional a/c assignments (Cost center, PC, Sales Order) Payment transactions (Due date, Value date, Payment terms, Reason code) Field Status Variant o FSV is a Group of Field status groups ( G001, G003, G004, G005) o Field status group: Is a group of similar features. E.g FSG G001: general characteristic, G003: Material consumption a/c general data, additional a/c assignment etc master fields, G004 : Cost Account general data, payment transactions, additional a/c assignments etc o FSG assigned to GL a/c in tcode FS00 to decide field status of these GL a/c during transactions o FSV is assigned to a company code

Posting Periods

Posting Period o PP is defined in Fiscal Year Variant o Usually current PP is open and all other PP close to prevent posting to incorrect PP o Can have as many PP open as required Posting Period Variant o Several company codes can use the same PPV Posting period check o PP for a document is determined by the posting date o PPV must contain the a/c type + o Other a/c types are for further control of accounts D/K/S/M. o Account type + must always be open if posting to be made to any other a/c type Year End Closing o During year end 2 periods are open. Special PP for the last fiscal year and normal PP for the current fiscal year o E.g. FY: Apr to Mar. In Apr Special PP 13 and normal PP 1 are open

Posting Authorizations

Tolerance Group o Tcode: SPRO-FA-FAGS Document Line Item Define tolerance group per employee o Specify Upper limit for following: Amount per document: Maximum permitted posting amount per document for this user group. Amount per Open Item: Maximum posting amount permitted per customer or vendor item for this user group Cash discount per Line Item: Maximum cash discount percentage rate which may be assigned by an employee of the user group. The percentage rate is checked during the entry, change and clearing of open items Can create any number of tolerance group Tolerance group "_____" blank applies to all user not assigned to any specific tolerance group Exercises: Simple document posting

GL a/c posting Vendor Invoice Vendor Credit Memo Customer Invoice Customer Credit Memo Define/ Display / Copy document number range Display customer line item

FB50 FB60 FB65 FB70 FB75 FBN1 FBL1N

Button Tree: Access screen variants, A/C assignments, Held documents Make the text field mandatory for GL a/c o At client level: GL a/c posting document type: AB. For document type AB in tcode OBA7 make the text field as required entry o At company code level: Find out FSV for the company code in OBY6. For this FSV in field status group G001 (General) make the text field as required. Now assign this FSG to the GL a/c in FS00 Define variant for open PP o Tcode: SPRO-FA-FAGS-Document-PP- Define variant for open posting period Define which periods are open for a posting period variant o Tcode: OB52 Assign PPV to a company code o Tcode: SPRO-FA-FAGS-Document-PP- Define variant for open posting period Create a tolerance group SUPV o Tcode: SPRO-FA-FAGS Document Line Item Define tolerance group per employee Assign tolerance group SUPV to your ID SAPUSER o Tcode: SPRO-FA-FAGS Document Line Item Define tolerance group per employee

Posting Control
Default Values

Using editing option config screen for different views o Document entry: Fields hidden (for specified user) if not relevant o Document display: Use list viewer for different display options o Open Items: When user log in his ID has following properties: o Language o Date format o Decimal notation Can control: o Whether fiscal year is proposed when document displayed / changed o CPU date proposed as value date Maximum exchange rate difference between exchange rate in document header and exchange rate in table TCURR. If it exceed warning display can be set Change Control

Document Change Document header: Only text and reference fields can be changed Line Item: No change can be made to amount, account and PK When a document is changed following information is logged Fields that was changed New and Old values User who made changes

Time and date of change Display changed documents Tcode : SE38 RFBABL00 Document Reversal

Can reverse GL, Customer, and vendor document

Document can be reversed by: Normal reversal posting Negative posting

Reversal Reasons: The reason for the reverse posting is noted in the reversed document. The field is therefore used as information as to why a reversal was necessary. The reason for reversal also determines: o Whether the reverse document is allowed to have an alternative posting date o Whether the reverse document is to be created from negative postings Documents with cleared items cannot be reversed. Reset the cleared items in FBRA

Payment Terms and Cash Discounts

Terms of payment Enable the system to calculate cash discount and Invoice due date. To calculate Invoice due date and cash discount system needs following information: Base Line Date: Date from which Invoice due date is calculated Cash discount % and Cash discount Terms Terms of payment can be specified in customer / vendor master record in: Company code segment Sales Area segment Purchase Org. segment Terms of Payment defaulted: FI Invoice: Entered in company code segment Sales Order: Entered in Sales Area Segment Purchase Order: Entered in Purchase Org. Segment Credit Memos Credit Memos related to Invoices: o Enter Invoice number in Invoice reference field under payment Tab during credit memo entry. o Invoice Terms of Payment copied to the credit memo o Invoice and credit memo due on the same date Credit Memo not related to the Invoice o For credit memo terms of payment to be valid enter V in invoice reference under payment Tab Cross Company code Transactions

Cross company code transactions Transactions involve 2/ more company codes. E.g.:

o o o

1 company code purchase for multiple company codes 1 company code pays for multiple company codes 1 company code sells for multiple company codes

One document can be posted in one company code so in cross company code transaction system post document in both company codes The documents are linked by a clearing a/c There are two or more documents linked with a common reference : st st o 1 company code + 1 company code document number + Fiscal Year Tax posting in cross company code transactions Whole amount of tax posted to the company code of 1st line If tax is to be distributed use report: SE38 RFBUST10 Exercise

Ensure document assignment field is not changed in tcode FB02( Restriction at company code level) o Tcode : SPRO FA FAGS Document Line Item Document change rules o Ne w entries Field name assignment (BSEG-ZUNOR) Applicable for what a/c type (S/K/D/A) Company code Ensure document assignment field is not changed in tcode FB02( Restriction at client level) o Tcode : OBA7 Prerequisite for negative reversal: o Company code allow negative posting (OBY6) o Reversal reason code allow negative posting ( SPRO- FA- GL BT Adjustment posting Define reason for reversal) FI Document reversal : FB08 Reset cleared items: FBRA Create a new terms of Payment o Tcode : SPRO FA AR/AP- BT Incoming invoices / Credit Memos Maintain terms of payment New entries
AC03 Blank Select Posting date %% Blank 2% 14 30

Terms of payment Customer Blank Vendor Default base line date % No. of days % No. of days No. of days

Explanation area of payment terms automatically defaulted

Assign terms of payments to vendors o Tcode: Easy accounts FA AP MR Change Company code data Payment transactions

Baseline Date o Date system uses to calculate vendor/ customer invoice due date and cash discount amount Taxes steps: o Create a new tax code (FTXP) o Assign a GL A/C to tax code to enable automatic postings (FTXP) o Define the tax code to be used in enjoy transaction ( OBZT, SPRO FA FAGS AR/AP BT Outgoing invoice Define tax code per transaction) o Post a customer / vendor invoice to show automatic posting

Create a new tax code

o Country Tax code Account Type Acct Key Tax Percent COA Tax a/c

Tcode : FTXP
GB 03 Output tax MWS 20% INT 175000

Configure automatic postings for cross company code transactions o Tcode: OBYA Display cross company code documents o Tcode: Easy Accounts- FA AP Document Cross company code transactions o Tcode : FBU2 / FBU3 / FBU8

Clearing
Clearing: Two ways to clear OI
o o

Account clearing (F-32) Post with clearing

Documents with OI cannot be achieved Post a customer Invoice o Tcode: FB70

5000 5000

Customer a/c Dr To sales a/c

Post a customer credit memo

o

Tcode: FB75
5000 5000

Sales a/c Dr To Customer a/c

Posting with Clearing Invoice is posted to customer Customer pays invoice and payment assigned to the Open Item Invoice cleared with above payment & balance is zero Clearing transaction creates a clearing document Clearing document no line items as no account posting Clearing Tcode: Automatic: F.13 Manual: F-03 Automatic Clearing Program Program groups items in a GL a/c where they have same entries in the following fields: o GL a/c number o Currency o Special GL indicator o Five definition criteria ( Assignment field) If balance is Zero in Local currency, program clears the items Account to be cleared defined in SPRO Automatic Program does not clear following items:
o o o o

Noted Items (Only information) Statistical posting ( Same a/c both D/C posting) Down Payments Items with withholding tax entries

Assignment Field: Value comes from sort fields in FS00

Tolerances:

Tolerances: Rules that define acceptable differences during posting Types of Tolerances: Employee Tolerance Group: o Upper limit for posting transaction o Permitted payment differences GL a/c Tolerances o Permitted payment differences (Clearing a/c, GRIR) Customer / Vendor Tolerance Group provides for o Permitted payment differences o Posting residual item for payment differences

Tolerance Group defined in 2 steps: Group Definition: Tolerance group defined by: o Group key o Company code o Currency code The Key "___" blank is required as minimum tolerance group Tolerance Group Assignment: Employee Tolerance Group: Assigned to employees GL a/c Tolerance Group: Assigned to GL a/c in FS00 Customer / Vendor Tolerance Group: Assigned to customer / vendor in customer/ vendor master records If no tolerance group assigned then blank tolerance group applies Automatic clearing of Payment differences Payment differences should be with in both tolerance (amount & %) to be cleared automatically Entries in tolerance group always cleared in Local currency / company code currency Manual Processing of Payment Differences High payment differences can be manually processed as follows: o Partial Payment: Post as partial payment. Document remains open o Residual Item: Post payment differences as residual item. Original document and payments are cleared. A new document is created for the residual item o Write off: The difference is w/off to an a/c. Manual a/c assignment for w/off

1. Reason Codes:

Reason codes used to analyze and post payment differences To assign more than one reason code to a payment difference click distribute differences Reason code functions: o Control type of payment notice sent to the customer o Control account to which residual item posted o Exclusion of residual item from credit limit check

Exchange Rate Differences

When clearing open items against payment received exchange rate difference may occur due to exchange rate fluctuation. This is posted to exchange rate difference realized account Exchange rate difference also occurs when valuating foreign currency open items for financial statements. These are posted to separate Exchange rate difference account and reverse in next period. Create a Reason Code goods damaged in transit (Z03) to w/off difference to GL a/c mapped to this reason code o Tcode: SPRO FA AR/AP BT Incoming payments Incoming payments Global settings Overpayment / Underpayment Define Reason codes o Data:
Z03 Damaged in Transit Charge of difference via a separate a/c

Reason code Text C

Type of correspondence with customer

Map GL a/c to Reason code Tcode: OBXL Data: 881000

Cash Journal
Cash Journal

Cash Journal: A tool for managing cash. Supports posting cash receipt and payments Features:
o o o

Create separate cash journal for each currency Post to customer / vendor / GL account (D/K/S) Run several cash journal for a company code

Steps in creating a new cash Journal: Specify following o Company code in which cash journal will be created o GL a/c's to which CJ entries will be posted o Currency in which CJ runs

Special GL Transactions

Types of Special GL transactions o Down Payments: Down Payment Request Down Payment o Bill of Exchange BOE Request BOE o Other Transactions Individual value Adjustments (PBDD) Guarantee Interest Down payment Request o Noted Items, Not included in GL o Only 1 line o Reminders o Payment Program and Dunning Program can access noted items o FBL5N : Noted Items o DP Request Down payment received DP request considered Customer Invoice received DP cleared against customer Invoice Down Payment o Part of Financial statement. Create a proper posting in GL a/c o FBL5N Special GL items Guarantee o Automatic offsetting entries o Displayed in Notes to accounts

Customer alternative Reconciliation a/c Dr To Guarantee Clearing a/c Guarantee Clearing a/c Dr To Customer alternative reconciliation a/c

Configuration of Special GL Transactions: FBKP

Customer 21003 Reconciliation a/c (FD03) 140000 Alternative Reconciliation (FBKP) 196100 Spl. Transaction Type G

A/C Type (D/K/S/A/M) D D D D

Spl GL Indicator F A E G

Description Down Payment Request Down Payment Reserve for Bad Debt Guarantee

Reconciliation a/c 140000 140000 140000 140000

Alternative Reconciliation a/c 196000 170000 142000 196100

Exercises Enter a Guarantee:

Document Type PK Customer Due on

Tcode: F-38 Tcode: easy A/C FA AR Document Entry Other Statistical Posting Data:
DA 09 100196 After 3 months

Display Guarantee
o

Tcode: FBL5N (Select special GL transaction)

Reverse Statistical Posting / Guarantee o Tcode: F-19 o Tcode: easy A/C FA AR Document Special GL Transaction Reverse statistical posting

Create a Down Payment Request:

Tcode: F-37 Data: o Special GL indicator: A

Display Down Payment Request of Customer o Tcode: FBL5N o Select Noted Items Create a Down payment against the DP request created earlier o Tcode: F-29 Post a Customer Invoice o Tcode: FB70 Clear Customer Invoice against down payment o Tcode: F-39
100196

Customer Click process DP Double click Transfer Posting Save

1. Individual Adjustments (PBDD)

Use Special GL transaction E to make an individual value adjustment of 6000 Tcode: F-21 Tcode: Easy A/C FA AR DE Other Transfer w/o clearing Data:
Last day of current month 19 100196 E 40 210100

Posting date PK Customer Special GL Indicator PK GL a/c ( Bad Debt / Uncollectible) A/C Entry Bad Debt / Uncollectible Expense a/c (210100) Dr To Allowance for Bad debt (PBDD: 142000 alternative reconciliation a/c for customer 100196) B/S account

6000 6000

Reverse Individual Value Adjustment / PBDD o Tcode: FB08

Held / Park Documents

2 ways of saving FI documents w/o fully completing it: Held document: o Document is incomplete o No document number is assigned o No a/c balance are updated o Not considered for reports o Document can be found under only user ID Park Document: o Document number is assigned o Considered for reports o Document can be found with any user ID o Can be used as part of principle of dual control

FI ECC 6 Certification Part-2

1. Assignment

Client:
o o

Highest level in hierarchy Specifications apply to all company codes under it

Company code: o Independent unit o Legal B/S, P/L for company code Business Area: o Separate financial unit o Can prepare separate B/S & P/L Chart of Depreciation: o Country Specific o SAP Provides model COD o COD contains depreciation area o Each depreciation area represents Book depreciation, Tax depreciation etc o One COA and COD can be assigned to one / more company codes o Depreciation area defined by two digit numeric code Assignment: o Assign COD to company code

Cost Accounting Assignment

In Asset accounting master record can assign following cost accounting objects o Cost center o Internal Order o Activity Type o WBS Elements o Real Estate Objects An asset (AMR) can be assigned to only one cost center

Exercises: Create a Chart of Depreciation Tcode: EC08 Data: Copy 1DE to MR03 Change Description of Chart of Depreciation o Tcode: SPRO FA AA Org. Structure Copy Reference COD Specify description of COD Delete depreciation Areas not required o Tcode: SPRO FA AA Org. Structure Copy Reference COD Copy / Delete Depreciation Areas Assign COD to Company code
o o o o

Tcode: SPRO FA AA Org. structures Assign COD to Company code Tcode: OAOB

Activate account assignment object

o

Tcode: SPRO FA AA Integration with GL Additional a/c assignment object Activate a/c assignment object

Asset Classes

Asset Classes: o Fixed asset classified into Asset classes. E.g.: Furniture, Vehicles o Asset Class created a client level o Asset class can be assigned to 1 / more COD o Can suppress individual depreciation areas (01, 02) in chart of depreciation in each Asset class if required (Tcode: .) o Each asset can be assigned to only one Asset Class o Special Asset Classes: AuC, Low value Asset

Depreciation Areas:

Chart of Depreciation: o Country Specific catalog of Depreciation Areas o Copy COD supplied by SAP o Delete Depreciation Areas not required o Now assign this COD to the company code o COD defined at client level o Various company codes can be assigned at to the COD Depreciation Areas post to GL accounts in any of the following options:
Depreciation Area

Particulars Post asset values (APC) : Online

01 Depreciation : Periodically Post Asset value (APC) : Periodically Depreciation : Periodically Do Not Post any values Reporting purpose only

Only Post Depreciation : Periodically

Depreciation always posted on periodic basis

Exercises:

Define that the asset values in Depreciation areas is displayed in USD o Tcode: SPRO FA AA- Valuation Currencies Define depreciation areas for foreign currencies o Tcode: OAYH Check How Depreciation areas post values to GL o Tcode: SPRO FA AA Integration with GL Define how Depreciation Area Post to GL

0 1 2

Area does not post Area post in Real Time Area Post APC & Depreciation on Periodic basis

Enter a financial statement structure for the depreciation area for which B/S is prepared o Tcode: OAYN

Master Data
Functions of Asset Class

Screen layout o Determine fields Displayed/ Optional/ Required in AMR o Tcode: FA AA MD Screen layout Define screen layout for Asset Master Data o Here decide what fields are Required / Optional / Suppressed / Displayed only in AMR o Copy Check Box: If this indicator is set, if this asset is used as a reference to create another asset it's values copied to the other asset o Screen layout rule assigned to Asset Class in OAOA o Screen layout rule assigned to Depreciation areas in OAYZ Asset Master Record Tab Layout: o Tcode: AOLA o Here we define AMR Tab Layout o Also can define New Tabs Activate Account assignment Objects: o Tcode: SPRO AA Integration with GL Additional account assignment Activate a/c assignment o Can Post depreciation and APC to these objects Asset Class:
o o

Tcode: OAOA Assign Account Determination : Account determination determine the GL accounts to which depreciation & APC values posted for the AMR

o o o o

Assign Screen layout Assign Number range Status of AuC: Select Line Item Settlement in case of AuC Check Box : Asset Classes blocked for Posting

Account Determination:
o o o o o

Tcode: AO90 Select your COA INT Select the Account Determination One Account Determination can be assigned to several Asset Classes provided they use the same COA Select Depreciation Area 01 : Assign GL accounts for Acquisition, Retirement, Depreciation

Mass Master Data Change for Asset Class o Display list of Assets : AR01 o Create a Work List : AR01 o Task Selection: Retirement w/o revenue, Retirement with revenue, Mass Change(Substitution Rule), Inter Company Asset Transfer o Create a Substitution rule for the Mass Asset Transfer o Release Work List : AR31 Asset Master Records

Create AMR o Enter company code and Asset Class o Use existing AMR as reference Can create multiple similar Assets Time Dependent Data o AMR information managed on time basis in Cost center o Time Dependent Tab Further Interval Enter from date and Cost center Tcode:
AS04 AS11 AS01 AS02 AS03

View Changes to AMR Create Asset Sub Number Create AMR Change AMR Display AMR

Mass Changes 1. 2. 3. 4. Create a work list: AR01 Select Substitution Rule for mass Changes Release Work List: AR31 Check Assets for changes

Exercises Master Data

1. Make number range assignments for Asset Accounting for your company code MR03. Two options: 1. Define a separate number range interval. Copy from company code 1000 : AS08 2. Chose cross company code number range interval. Here find company code MR03 and enter company code 1000 so both company code use same number range interval for Asset Accounting: AO11 1. Call up transaction that provide overview of all Asset Classes: OAOA 1. Tcode: OAOA 2. Account Determination: Determine the reconciliation a/c in GL to which posting has to be made 3. Screen Layout: Determine for AMR which fields are Required/ Optional / Suppressed 4. Number range assigned to the Asset Class 5. Can block Asset class from posting 1. Set Chart of Depreciation: OAPL Which B/S a/c system post for an Asset Acquit ion

1. From AMR get Account determination. For this find GL a/c in AO90 2. Tcode: AO90 2. Show how field description & cost center of AMR defined ( R/O/S) 1. Tcode: SPRO FA AA Master Data Screen Layout Define Screen layout for Asset Master Data Select layout rule 2000 Select Logical Field group General / Time Dependent data Field group rules 2. Copy : If selected this field is copied is used as reference asset 3. Determine Depreciation Areas in the Asset Class 3. 4. 5. 6. 7. 8. Tcode : OAYZ Determine Depreciation areas for an Asset Class Depreciation Areas active for the Asset Class Depreciation Keys assigned to the Depreciation areas. Can be changed Screen layout assigned to the depreciation area Use: If a useful life is not entered in the asset class, and depreciation key is not 0000, this field is a required entry regardless of the settings in the screen layout control.

Create an Asset Class (MA03) by copying another Asset Class 2100 9. Tcode : OAOA 10. When you copy Asset Class you get Asset class Master Data + Depreciation Data

Define Maximum value for LVA (Low Value Asset) for company code MR03 11. Tcode : OAYK 12. Tcode: SPRO FA AA Valuation Amount Specification Specify Maximum amount for LVA and Asset Class Specify Asset Class (Here specify LVA Asset Class) / Specify Amount for LVA (Here specify Amount for LVA Asset Class) 13. LVA : 0 : No LVA check for this AC 14. LVA : 1 : Each LVA with its own asset master record

3. Create Asset master Record (AMR) : AS01

Account Determination 2100 1100 2100 3000 LINS Depreciation Key Asset 2000 1000 2100 3007 7000 4000 (AuC) 0000 7001 5000 (LVA) GWG 5000

Create similar Asset: AS01 1. Enter 5 in similar records 1. Create Sub Assets: AS11 1. List all AMR created in a company code 1. Tcode: AA- Information System Report on AA Day to Day Activities International Directory of un posted Assets 2. Create a Vendor master: FK01 1. Post Asset Acquition to Vendor: F-90 1. Tcode: Easy FA AA- Posting Acquition External Acquition with vendor 1. Check asset value using Asset Explorer: 1. Tcode: AW01N 2. Check B/S GL a/c to which asset acquition value posted: Double click on transaction 3. GOTO Call up Reports Acquition / History 4. GOTO master data

Post Asset acquition with automatic offsetting entry 1. Tcode: ABZON 2. Easy FA AA Posting Acquition External Acquition Acquition w/automatic offsetting entry 1. Post acquition in current year w/o first creating AMR 1. Tcode: ABZON 2. Select new Asset radio button 1. Post Acquition to multiple assets 1. Tcode; ABZON 2. Select Tab Multiple Assets Enter main Asset number in asset click sub number list of assets populated Add Amount and save

Reverse Asset Acquition: AB08 1. Tcode: Easy FA AA Posting Reverse Document Other Asset Document

Post an acquition to LVA: F-90 1. Ensure / restrict that only certain depreciation areas are posted with values 1. Tcode: SPRO FA AA- Transaction Acquition Define Transaction types for Acquition Limit transaction type to Depreciation Areas 2. Tcode: AO73 3. Tcode: OAYA Asset Transactions Retirement 1. Post Asset Retirement with revenue with customer 1. Tcode: F-92 2. Tcode: Easy AA Posting Retirement Retirement with revenue with customer 3. Data:
PK PK A/C Select Asset Retirement Select complete retirement check box TT (For retirement with revenue) On complete retirement AMR is de activated 210 01 50 820000 Check box

Scrapping the Asset 1. Tcode: ABAVN 2. Tcode: Easy AA Posting Retirement Asset Retirement by scrapping 3. AMR deactivated on scrapping 1. Asset Transactions Intra/ Inter Company 2. Perform an Intra company transfer between asset Class 3000 (Furniture) and AC 3100 (Vehicle) 1. Tcode: ABUMN 2. Tcode: Easy FA AA Posting Transfer Transfer within company code Transfer between company codes belonging to the same Company (Group) 1. Tcode: ABT1N 2. Tcode: FA AA Posting Transfer Intercompany asset transfer 3. Data:
Both company codes in same group company

Transfer variant Used Transfer Variant : Specify Asset valuation method in the receiving company code Transaction Type (Retirement/ Acquit ion) used for transfer

1. Copy start date of depreciation to the New Asset 1. Tcode: AA Transaction Intercompany asset transfer Automatic Intercompany Asset Transfer Define transfer variant Asset Transactions AuC 1. Assign a settlement profile (AI) to your company code 1. Tcode: SPRO FA AA Transactions Capitalization of AuC Assign Settlement Profile

2. Acquition to AuC: 1. Tcode: ABZON 1. Distribute AuC (7000) Acquition document to Final Assets (2005, 2006) 1. Tcode : AIAB 2. Tcode: FA Posting Capitalize AuC Distribute 3. Steps : Chose Documents Execute Edit Enter Distribution rules Save

2. Execute Settlement 1. Tcode: FA Posting Capitalize AuC - Settlement Unplanned Depreciation: ABAA

Summary of Asset Accounting Tcode

Particulars Overview of Asset Class Account Determination Define Screen Layout TAB Layout for AMR

Tcode OAOA AO90 SPRO FA AA MD Screen Layout AOLA

View Changes to AMR External Asset Acquition with Vendor External Asset acquition without vendor Asset Explorer Activate / Deactivate Depreciation areas for Asset Class in Chart of Depreciation Create Sub Assets Create / Change / Display AMR Reverse Asset Document Asset Transaction Type Details Retire Asset to Customer Asset Class Change Inter Company Asset Transfer AuC Settlement Define Asset Number Range Share Asset Number Range with other company codes

AS04 F-90 ABZON AW01N OAYZ AS11 AS01 / AS02 / AS03 AS08 AO73 F-92 ABUMN ABT1N AIAB AS08 AO11

Validation / Substitutions
1. Validation & Substitution General 2. To Validate or Substitute an entry

3. Steps in Validation & substitution: 1. Identify area of application 2. Call up point for validation / Substitution 3. Define Validation / Substitution 4. Assign Validation / Substitution to company code (An Org. unit) 5. Activate validation / substitution 4. Application Area: Area where validation / substitution rule is used. e.g. 6. 7. 8. 9. 10. FI CO Asset Management Special Purpose ledger PCA

5. Application Area Key: Specify Application area where validation / substitution is used

1. Call Up Point: Point at which Validation / Substitution processing starts 1. Call Up Point for FI 1. Document Header : Call up point 1 2. Document Line Item : Call up point 2 3. Complete Document : Call up point 3 4. At this call up point can use only numeric field, used for mathematical calculation

2. Formula Editor: 1. Interface for editing arithmetic & Logical statements

3. Assign Validation / Substitution to Organization Unit (Company code, Controlling area...) 1. A validation / Substitution can be valid for several company codes

1. Activate Validation / Substitution 1. 0 : Inactive 2. 1: Active (Dialog + batch) 3. 2: Active (Dialog but not Batch)

1. Only one validation / Substitution can be activated for a company code for 1 call up point 1. Validation Execution 1. Validation has following 3 parts 1. Prerequisite 2. Check 3. Message 2. If prerequisite is true : 1. Check performed 2. If check false, message displayed

Message Type
I W E A Information Warning Error Cancel

1. Can use predefined message or create own message

Validation Can do following Logical Statements 1. Compare fields with one another. BKFP-BUDAT <>BKPF-BLDAT. Statement true if date in field BUDAT is not equal to date in field BLDAT 2. Validate field contents for certain values. BKPF-BLART = "SA". Statement true if document type = SA 3. Check / compare only a part of the field. Details refer notes

Substitution Execution 1. Substitution steps has two parts 1. Prerequisite: If prerequisite is true substitution is performed 2. Replacement: Substitution 3. Substitution Methods: 1. Constant Values 2. User Exit: Name of the Exit to be carried at Run Time 3. Field-Field Assignment: Name of field whose content can be used for Substitution 1. Rule: 1. A Rule is a prerequisite or a check of validation 2. A rule is normally created for a prerequisite that is frequently used. Rule can be used repeatedly

2. Set: 1. A data structure having a range of GL accounts

1. Exercise: Validation / Substitution

1. Create a validation rule that for GL a/c (telephone expense) 473110 / 473120 cost center must be 3336 1. Tcode: OB28 2. Steps: 3. Double click on call up point 2 for company code MR03 4. Click on validation create 5. Data:
Validation Description G03 Telephone Cost

1. Click on step Insert 2. Data: 3. Double click BSEG-HKON- click = - Click constant and enter 473110 click OR Double click BSEGHKONT click = - Click constant and enter 473120 Double click on BSEG-KOSTL click = and enter 3336 4. Define the required message "Assign cc 3336"

5. Activate Validation Go to Step 1 for call up point 2 select Validation G03 and activate it 1. Create a Substitution rule that when customer invoice posted and Sales a/c = 810301 and Segment = SEG03 Then Substitute PC = PC05 1. Tcode: SPRO FA FAGS Document Line Item Define Substitution in account document 2. For company code MR03 & call up point 02 create substitution rule G03 3. Chose Insert Select BSEG-PRCTR Continue 4. Enter the prerequisite 5. Select Substitution and Enter PC as PC05 6. Save and Activate

The New GL
1. Total tables when classic FI component used are: 1. Classic FI: GLTO 2. Cost of Sales Ledger: GLFUNCT 3. Reconciliation Ledger: COFIT 4. EX-PCA: GLPCT 1. New GL Advantage 1. It has an extended data structure. Thus new fields like cost center, Segment etc can be added to GL total table 2. Balance sheet can be created for entities called segment. Real time document splitting between segment 3. Real time FI & CO reconciliation 4. 1. 2. 3. 4. New GL is optional for existing customer during a release upgrade In a new installation new GL is active Setting up System for New GL : SAP Note 756146 Features of Leading Ledger: 1. Manages additional local currencies assigned to a company code 2. Uses Fiscal Year variant assigned to a company code 3. Uses Posting Period Variant assigned to a company code 4. Only Leading Ledger values posted to controlling

5. Define additional currencies for leading ledger for a company code 1. Tcode: SPRO FA(N)- FAGS(N)- Ledger Ledger Define currencies of Leading Ledger

6. Assign Fiscal Year variant and Posting Period to company code and Leading Ledger 1. Tcode: SPRO FA(N) FAGS(N) Ledger Fiscal Year and Posting Period

7. There are non leading ledger: Can be assigned currencies and Fiscal Year variant different from leading ledger

8. New GL Total Tables: 1. New GL total table: FAGLFLEXT 2. Classic GL Total Table : GLTO 3. New fields in new GL total table: 1. Cost Center 2. Profit Center 3. Segment 4. Can also add new fields predefined / new custom fields 1. What is a scenario 1. A scenario defines which fields are updated in ledger (Leading and non leading ledger) during posting 2. Cannot define own scenario 3. Scenarios provided by SAP: 1. Cost Center update ( Update sender / receiver cost center) 2. Profit Center Update ( Update Profit Center / Partner PC field) 3. Segmentation ( Update segment, Partner segment and PC fields) 4. Preparation for consolidation

4. Display available scenarios 1. Tcode: SPRO FA(N) FAGS(N) Ledger Fields Display scenario for GL 5. Assign scenarios to ledger: 1. Tcode: SPRO FA(N) FAGS (N) Leading ledger Ledger - Assign

2. Multiple non leading ledgers useful to show accounts as per different accounting principles

3. In new GL FA documents has two views : FB03 1. Entry View: In account field vendor number appear 2. GL View: In account field vendor reconciliation account number appear

4. Segment Field 1. It is one of the standard account assignment object 2. Enable analysis below company code level 3. Alternative account assignment used earlier 1. Profit Center 2. Business Area 3. Profit Segment 4. A segment is assigned to master record of Profit Center. Posting is made to segment when profit center is posted 5. Derive Segment from PC. Can have own rules through user exist (BADI). BADI is FAGL_DERIVE_SEGMENT 5. Document Splitting 6. 1st define for which FI characteristic document splitting is performed. FI characteristic: 1. Business Area

2. Profit Center 3. Segment 4. Tcode: SPRO FA(N) GL (N) BT Document splitting Define document splitting characteristic for GL 5. Zero Balance indicator: Useful if balance sheet is to be prepared for a characteristic

7. Activate Document splitting 1. Document splitting activated at client level 2. Tcode: SPRO FI (N) GL(N) BT Document splitting Activate document splitting 3. Inheritance: In entry view 2 accounts (purchase services and travelling cost) plus 1 tax a/c. In GL view tax a/c amount split in two in the proportion of amount in purchase service and travelling cost

8. Configuring New GL 1. Activate New GL 1. Tcode: SPRO FA FAGS Activate New GL

2. Check ID of Leading ledger 1. Tcode: SPRO FA(N) FAGS(N) Ledger Ledger Define Ledger for GL 2. Data: OL

3. Check scenarios assigned to leading ledger OL 1. Tcode: SPRO FA(N) FAGS(N)- Ledger Ledger Assign Scenarios to Ledger 2. Scenarios assigned 1. Cost Center update 2. Preparation for consolidation 3. Profit Center Update 4. Segmentation 5. Cost of Sales account

4. Create a new Segment SEG03 1. Tcode: ES Definition FA Define Segment 1. Create a Profit Center 1. Tcode: KE51 2. Data: PC04

2. Update Cost center 3336 with Profit Center PC04 1. Tcode: KS02

3. Check that cost center / Profit Center / Segment defined as OPTIONAL in Field Status Group of GL a/c 417000 1. Tcode: FS00 Enter a/c 417000 Create Bank Double click FSG G033

4. Check Segment splitting defined for GL 1. Tcode: SPRO FA (N) GL(N) BT Document Splitting Define Document splitting . GL 2. Zero balance indicators checked: System checks that the balance of the characteristic (Segment) is zero during posting. If not system creates additional line item to achieve zero balance 3. Mandatory indicator checked : System checks that all line items in the posting are assigned appropriate characteristic (Segment) after split

5. Activate document splitting for company code MR03 1. Tcode: SPRO FA(N) GL(N) BT Document splitting Activate document splitting

6. Assign Item category to GL a/c

7. Assign Segment SEG03 to PC04 1. Tcode: KE52

8. Enter Vendor Invoice & split to cost center 3336 and 3338 so post to different characteristics

9. Create segment SEGA and assign to cost center 1. Create PC PC05 : KE51 2. Create a new segment : SEGA 3. Assign SEGA to PC05 4. Create a CC 3339 and assign PC PC05 to it

10. Assign company code MR03 to controlling area 1000 1. Maintain controlling area 2. Create cost center, Profit Center, Segment 3. Assign Segment to Profit Center 4. Assign Profit center to Cost Center

11. Create a variant for Real time FI and CO integration 1. Tcode: SPRO FI (N) FAGS(N) Ledger Real time integration of controlling with Financial Accounting Define variant for real time integration 2. Data:
Variant Real time integration Account Determination Document Type Ledger Group V03 Select Select AB 0L

1. Assign Variant to company code (MR03) 1. Tcode: SPRO FI(N) FAGS (N) Ledger Real time integration of controlling with FI Assign variant for real time integration

1. Repost a line item in controlling from cost center 3338 to cost center 3339 1. Tcode: Easy Accounting Controlling CCA Actual Posting Repost line items Enter Tcode: KB61 ( It's reversal KB64)

FI ECC 6 Certification Part-3

1. Dunning 2. Dunning Run 1. System check account for items that is overdue 2. Check whether dunning notice to be sent 3. Dunning level to be assigned 4. Dunning proposal can be edited / deleted 5. Dunning Notices printed 6. Dunning data updated in: 1. Document 2. Customer / Vendor master record

3. 4 steps of dunning process 1. Maintain parameters 2. Proposal Run 3. Edit dunning proposal 4. Print dunning notices

1. Customer without dunning procedure in Master Record cannot be dunned

2. Dunning notices can be sent both to customer and vendor 3. Dunning Program Configuration 4. Maintain Dunning Procedure 1. Controls how dunning is done 2. Every customer / vendor that needs to be dunned needs to have a dunning procedure 3. Dunning procedure can process both standard & special GL transactions

5. For each dunning procedure define 1. Dunning procedure key 2. Dunning Procedure description 3. Interval in days at which accounts have to be dunned. System check dunning date is after the number of days specified here from the last dunning run date 4. Minimum days in arrears for which an item in an account must be overdue for dunning notices to be created for the account 5. Grace period per line item: Grace period >= minimum days in arrear for an item to be dunned 6. Number of dunning levels: The highest dunning level possible in this procedure 7. Grace Period: Not considered for calculating dunning level. Thus an item whose days in arrears <= Grace period is not due for dunning notice 8. Interest Indicator : If selected interest is calculated for this account

6. Dunning Levels 1. Days in Arrear: Item dunning Level = (Item due date + Days in arrear) 2. Calculate Interest : Can specify whether interest is to be calculated for each dunning level 3. Print Parameters : 1. Always Dun: If selected a dunning notice is sent even if no changes have been made to the dunning proposal since last Dun 2. A Dun proposal changes: At least one item in the account reaches next level or/and a new item is added. 4. Print All Items: All open items printed in the dunning notice. Dunning notice has dunning level of the item with highest dunning level

7. Dunning Charges 1. Dunning charges defined for each dunning level 2. Dunning charges can be fixed amount or % of dunned amount

8. Minimum Amount: 1. Minimum amount of an overdue item necessary for dunning notice at this dunning level 2. Minimum Amount for Interest : Minimum amount of interest necessary for dunning at the dunning level

9. Dunning Texts: 1. SAP Forms / scripts to be used for dunning at each dunning level

Parameters for Dunning run 1. Run Date: Any Date

2. Identification: Any 6 digit to identify the dunning run 3. Parameters: 1. Dunning Date: Issue date for dunning note. Basis for calculating days in arrears 2. Document Posted Up to: Items posted up to this date are included in the proposal 3. Company code 4. Vendor / Customer 5. Additional Log: Activate if more details required

4. The Dunning Run 1. Dunning Run has 3 steps 1. Account Selection: Program selects customer / vendor accounts as per parameters 2. Dun Line Items: Program selects line item for dunning, i.e. overdue line items

1. Account Selection Criteria 1. Dunning procedure entered in customer / vendor master record 2. (Date of last dunning run entered in customer / vendor master record by the system + Dunning interval ) > dunning date in the dunning procedure

1. Due Line Items 1. Customer Invoices: Due on date for net payment. Due date is date after missing all cash discount periods 2. Credit memos: If a credit memo refers to an invoice then invoice due date applies to the credit memo

2. Clearing with credit memos & vendor line items 1. Customers net due debit items cleared with net due credit items ( credit memos) 2. Where customer = vendor. Customer net due credit item cleared against vendor net due debit item. Same dunning procedure assigned to both the customer & vendor.

3. Dunning Dates: 1. Due Date: Date by which Item must be paid 2. Item Overdue: After deducting grace period from days in arrears

4. Dunning block in Item / a/c's 1. If a dunning block exist in customer / vendor master records system add these accounts to blocked account list 2. Similarly for items

5. Each dunning procedure can have: 1. Up to 9 levels 2. Each line item assigned it's dunning level according to its days in arrear in Dunning procedure 3. No dunning procedure can be skipped

6. Payment Reminder : Dunning Procedure with one dunning level

7. Dunning Keys: 1. Can assign dunning keys to the line item to restrict maximum dunning level for the line item ( FB03 Customer line item Change)

8. Minimum days in arrears: 1. Customer / Vendor account can only be dunned if at least one line item has reached the minimum days in arrears 9. Dunning run updates master record with dunning level

Exercises : Dunning 1. Reason why overdue items may not be dunned 1. Customer / Vendor account not in dunning parameters 2. Item w/I grace period 3. Item / account blocked for dunning 4. Overdue amount < Minimum amount in dunning procedure 5. Net due item can be cleared with due on credit side 6. None of the item in the account exceed minimum days in arrears 7. (Dunning data has not changed since last dunning run + Always DUN not selected)

2. Dunning run does not update dunning data in line item account. Dunning data is updated when dunning notices are printed

3. Dunning proposal can be edited as many times as required. Dunning database not changed. Dunning database is changed when DUN notice is printed

1. Automatic Payment Program APP Config: FBZP 1. FBZP: All company codes 1. Sending Company code : Company code whose invoices are paid 2. Paying company code: Company code responsible for outgoing payments. Normally same but can be different 3. Vendor / Customer special GL transaction: Specify which special GL transaction can be paid / considered during APP run. E.g.: A (Down Payment), F (DP request), G (Guarantee)

2. FBZP : Paying Company code: For each company code define: 1. Minimum amount for incoming and outgoing payments 2. Forms used for payment advice & EDI 3. BOE Specification : You should flag the field if you wish to use bills of exchange, bill of exchange payment requests in the paying company code

3. FBZP: Payment Method per Country: For each country define: 1. Payment method to be used (I, W, C...) 2. Vendor / Customer master record requirements (Bank details, Vendor address..) 3. Payment & Clearing document type 4. Payment Medium ( Classic payment medium / PMWB) 5. Permitted currencies: 1. Currencies specified: Payment restricted in these currencies 2. Currency not specified: Payment in any currency

4. Payment Method in Company code 1. A line item whose payment method differ from one specified here are excluded 2. Specify minim um and maximum amount of payment that can be made for this payment method and company code 3. Foreign business partner: If selected payment can be made to customer / vendor outside paying company code country 4. Foreign Currency Allowed: If selected payment can be made in FC. 5. Form for the payment medium : Form to be used by payment medium program entered in Payment method in Country 6. Payment Advice Control: Whether a payment advice to be permitted or not permitted

1. Bank Determination 1. Ranking Order: HB rank in which APP picks them up for payment 2. Bank Accounts: Entry for paying company code. GL account to which posting made by this HB. If currency field is blank any currency can be used 3. Available Amounts: Maximum amount available for outgoing payments 4. Expenses / Charges: If applicable deducted from incoming payment and added to the outgoing payment 2. House Bank: HB Config FI12

1. Reasons for Exception List 1. Invoice blocked / Vendor blocked for payments 2. Bank details / Address missing in vendor / customer master record 3. Payment method not defined in the customer / vendor master records 4. Debit balance (Not due) 5. Payment amount < minimum permitted payment amount in FBZP 6. Invalid House bank

FI ECC 6 Part-4
1. Customer / Vendor Master Record Segments 2. Customer / Vendor Master Record Segments 1. General data ( Client Level) 1. Address 2. Control Data 2. Company code Data 1. Account management 2. Payment Transactions 3. W/H Tax 3. Sales Area 4. Purchase Org 3. Field status in MR : Controlled by account group 4. Alternate Payee / Payer 1. Can be defined at client level / Company code level 2. Customer : Amount received from alternate payee 3. Vendor : Amount paid to alternate payee 4. Report : SE38 RFDKVZ00 / RFKKVZ00: Shows alternate payee for all customer / vendor

1. Document is uniquely identified by: FB03 1. Document number 2. Fiscal Year 3. Company code 2. A document can have lines : 1 999 line 3. Document is controlled by : 1. Document Type 2. Posting Key

4. Running APP: 1. Run date : Date to identify the run 2. Posting Date : Date on which posting made to the GL 3. Doc's entered up to : All documents entered up to this date included in the payment run 4. Multiple company codes : Can enter multiple company codes separated by comma in the same country 5. Payment Method: Select payment method applicable for the country. Can enter more than one payment method. Considered in the order entered.

5. Ways to configure a payment block: 1. Payment block applied by a credit check 2. Payment block during invoice entry (FB60) 3. Payment block in the vendor Master record

6. Payment Run: 1. Post payment documents 2. Clear Open Item 3. Supply the print program with necessary data 7. Print Run: 1. Transfer DME payment data to DME administration 2. Transfer payment medium / payment advice note and payment summary to print administration 3. Create intermediate document (iDoc) for selected payments which can be forwarded to EDI