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
      

 

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
      

 

1. Parameters for Dunning run
   
2. Run Date: Any Date
   
   
    
3. Identification: Any 6 digit to identify the dunning run
   
4. 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
      
   
    
    
5. 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
   

 

1. Exercises : Dunning
   
2. 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)
      
       
3. Dunning run does not update dunning data in line item account. Dunning data is updated when dunning notices are printed
   
    
4. 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 Certification Part-2

1. Assignment
   

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

• Company code:
  • Independent unit
    
  • Legal B/S, P/L for company code
    

• Business Area:
  • Separate financial unit
    
  • Can prepare separate B/S & P/L
    

• Chart of Depreciation:
  • Country Specific
    
  • SAP Provides model COD
    
  • COD contains depreciation area
    
  • Each depreciation area represents Book depreciation, Tax depreciation etc
    
  • One COA and COD can be assigned to one / more company codes
    
  • Depreciation area defined by two digit numeric code
    

• Assignment:
  • Assign COD to company code
    

1. Cost Accounting Assignment
   

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

1. Exercises
   

• Create a Chart of Depreciation
  • Tcode: EC08
    
  • Data:
    • Copy 1DE to MR03
      
  
  
  
   
• Change Description of Chart of Depreciation
  • Tcode: SPRO – FA – AA – Org. Structure – Copy Reference COD – Specify description of COD
    
  
  
  
   
• Delete depreciation Areas not required
  • Tcode: SPRO – FA – AA – Org. Structure – Copy Reference COD – Copy / Delete Depreciation Areas
    
  
  
  
   
• Assign COD to Company code
  • Tcode: SPRO – FA – AA – Org. structures – Assign COD to Company code
    
  • Tcode: OAOB
    
  
  
  
  
  
   
• Activate account assignment object
  • Tcode: SPRO – FA – AA – Integration with GL – Additional a/c assignment object – Activate a/c assignment object
    

1. Asset Classes
   

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

1. Depreciation Areas:
   

• Chart of Depreciation:
  • Country Specific catalog of Depreciation Areas
    
  • Copy COD supplied by SAP
    
  • Delete Depreciation Areas not required
    
  • Now assign this COD to the company code
    
  • COD defined at client level
    
  • Various company codes can be assigned at to the COD
    
  
   

• Depreciation Areas post to GL accounts in any of the following options:
  

Particulars	Depreciation Area
Post asset values (APC) : Online Depreciation : Periodically	01
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
  

1. Exercises:
   

• Define that the asset values in Depreciation areas is displayed in USD
  • Tcode: SPRO – FA – AA- Valuation – Currencies – Define depreciation areas for foreign currencies
    
  • Tcode: OAYH
    

 

• Check How Depreciation areas post values to GL
  • Tcode: SPRO – FA – AA – Integration with GL – Define how Depreciation Area Post to GL
    

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

 

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

1. Master Data
   

1. Functions of Asset Class
   

• Screen layout
  • Determine fields Displayed/ Optional/ Required in AMR
    
  • Tcode: FA – AA – MD – Screen layout – Define screen layout for Asset Master Data
    
  • Here decide what fields are Required / Optional / Suppressed / Displayed only in AMR
    
  • 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
    
  • Screen layout rule assigned to Asset Class in OAOA
    
  • Screen layout rule assigned to Depreciation areas in OAYZ
    

• Asset Master Record Tab Layout:
  • Tcode: AOLA
    
  • Here we define AMR Tab Layout
    
  • Also can define New Tabs
    

• Activate Account assignment Objects:
  • Tcode: SPRO – AA – Integration with GL – Additional account assignment – Activate a/c assignment
    
  • Can Post depreciation and APC to these objects
    

• Asset Class:
  • Tcode: OAOA
    
  • Assign Account Determination : Account determination determine the GL accounts to which depreciation & APC values posted for the AMR
    
  • 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:
  • 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
  • Display list of Assets : AR01
    
  • Create a Work List : AR01
    
  • Task Selection: Retirement w/o revenue, Retirement with revenue, Mass Change(Substitution Rule), Inter Company Asset Transfer
    
  • Create a Substitution rule for the Mass Asset Transfer
    
  • Release Work List : AR31
    
     
  
  
  
   

1. Asset Master Records
   

• Create AMR
  • Enter company code and Asset Class
    
  • Use existing AMR as reference
    

• Can create multiple similar Assets
  

• Time Dependent Data
  • AMR information managed on time basis in Cost center
    
  • Time Dependent Tab – Further Interval – Enter from date and Cost center
    

• Tcode:
  

View Changes to AMR	AS04
Create Asset Sub Number	AS11
Create AMR	AS01
Change AMR	AS02
Display AMR	AS03

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

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

1. 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
   1. Tcode : OAYZ
      
   2. Determine Depreciation areas for an Asset Class
      
   3. Depreciation Areas active for the Asset Class
      
   4. Depreciation Keys assigned to the Depreciation areas. Can be changed
      
   5. Screen layout assigned to the depreciation area
      
   6. 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.
      
       
4. Create an Asset Class (MA03) by copying another Asset Class 2100
   1. Tcode : OAOA
      
   2. When you copy Asset Class you get Asset class Master Data + Depreciation Data
      
       
5. Define Maximum value for LVA (Low Value Asset) for company code MR03
   1. Tcode : OAYK
      
   2. 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)
      
   3. LVA : 0 : No LVA check for this AC
      
   4. LVA : 1 : Each LVA with its own asset master record
      
       
6. Create Asset master Record (AMR) : AS01
   

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

 

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

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

1. Reverse Asset Acquition: AB08
   1. Tcode: Easy – FA – AA – Posting – Reverse Document – Other Asset Document
      
   
   
   
    
2. 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
      

1. 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	01
PK	50
A/C	820000
Select Asset Retirement	Check box
Select complete retirement check box
TT (For retirement with revenue)	210
On complete retirement AMR is de activated

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

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

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

1. Unplanned Depreciation: ABAA
   

1. Summary of Asset Accounting Tcode
   

Particulars	Tcode
Overview of Asset Class	OAOA
Account Determination	AO90
Define Screen Layout	SPRO – FA – AA – MD – Screen Layout
TAB Layout for AMR	AOLA
View Changes to AMR	AS04
External Asset Acquition with Vendor	F-90
External Asset acquition without vendor	ABZON
Asset Explorer	AW01N
Activate / Deactivate Depreciation areas for Asset Class in Chart of Depreciation	OAYZ
Create Sub Assets	AS11
Create / Change / Display AMR	AS01 / AS02 / AS03
Reverse Asset Document	AS08
Asset Transaction Type Details	AO73
Retire Asset to Customer	F-92
Asset Class Change	ABUMN
Inter Company Asset Transfer	ABT1N
AuC Settlement	AIAB
Define Asset Number Range	AS08
Share Asset Number Range with other company codes	AO11

 

1. 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.
   1. FI
      
   2. CO
      
   3. Asset Management
      
   4. Special Purpose ledger
      
   5. 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
      

1. Message Type
   

I	Information
W	Warning
E	Error
A	Cancel

1. Can use predefined message or create own message
   

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

1. Substitution Execution
   
2. 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	G03
Description	Telephone Cost

1. Click on step Insert
   
2. Data:
   
3. Double click BSEG-HKON- click = - Click constant and enter 473110 – click OR – Double click BSEG-HKONT – 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
      

1. The New GL
   
2. 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. New GL is optional for existing customer during a release upgrade
   
2. In a new installation new GL is active
   
3. Setting up System for New GL : SAP Note 756146
   
4. 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	V03
Real time integration	Select
Account Determination	Select
Document Type	AB
Ledger Group	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)