Step 6 - SAP FI/CO Configuration Quick Notes
 


 

This is a complete FI/CO Configuration Quick Notes covering all the FI/CO modules. This can be used as a reliable reference guide in the workplace by beginners and medium level users since it is straight to the point, hence they don't have to flip through thick manuals or books. It is also can be used as an examination guide for SAP certification exam. The configuration steps are illustrated step by step in detail without leaving out a single step by a team high caliber SAP senior consultants having more than 7 years of experience.
 
MODULES COVERED  
ENTERPRISE STRUCTURE SETUP (COMPANY CODE SETUP)  
CHART OF ACCOUNT SETUP  
GENERAL LEDGER CONFIGURATION  
ACCOUNTS RECEIVABLE CONFIGURATION  
ACCOUNTS PAYABLE CONFIGURATION  
ASSET ACCOUNTING  
COST CENTER ACCOUNTING  
INTERNAL ORDERS  
COST ELEMENT ACCOUNTING  
PROFIT CENTER ACCOUNTING  
PROFITABILITY ANALYSIS  
ACTIVITY BASED COSTING  
PRODUCT COSTING  
TREASURY  
SALES AND DISTRIBUTION CONFIGURATION RELATED TO FI/CO  
MATERIALS MANAGEMENT CONFIGURATION RELATED TO FI/CO  
 
 
SEE THE FOLLOWING EXAMPLE FOR COMPANY CODE SETUP :-  
ENTERPRISE  STRUCTURE  

IMG/ES/DEFI/FA  : DEFINE  COMPANY  :  Define company, enter address etc.

  
DEFINE / DELETE / CHECK COMPANY CODE  :  Define company code / copy from another company code etc.  [ OX02 ]  

IMG/ES/ASSIG/FA  : ASSIGN COMPANY CODE TO COMPANY  :  Assign the company created under 1 to the company code created under 2.

  
  TO CHECK GLOBAL SETTINGS  -  [ OBY6 ]

  
IMG/FA/GLOBAL SETTINGS/FISCAL YEAR  -  [ OB29 ]  

  • Maintain Fiscal Year Variant  :  fiscal year can be
  1. Year dependent
  2. Year independent
  3. Calender
  4. Shortened
  
  • Period  :  Fiscal year is made up of periods 1 – 12. There can be a maximum of 12 normal posting periods and 4 special 13-16 posting periods. Thus for a General Ledger there can be a maximum of 16 posting periods, and for a Special Ledger ( where cross flow exists like PCA, PCC etc ) there can be a maximum of 65 posting periods. Once the FYV is defined, periods can be accessed and defined. Every business transaction is allocated to a posting period. Weekly will have 52 posting periods.
  • Day  :  Last valid calender date to be specified for each period. FYV 24 PP     
        
Month
Day
Period
Year Shift
1 15 1 +1  for next yr
1 31 2 -1 for last yr
2 14 3  0 for cur yr
2 28 4 periods cannot be maintained for calender dependent FYV.  FYV does not contain info whether a period is open or closed. This is accessed thru open / close posting periods.

  • Year dependent fiscal year means the start and end date of the PP of some FY will be different from the dates of other FY, and / or if some FY use a different no of PP.  If one year of a FYV has less posting periods than others, it is called a shortened FY. This could be required if closing has to be made before the end of the normal FY. The shortened FY and its no of PP has to be specified before the definition of period dates and for this year only, a lesser no of PP can be assigned. FY can be defined separately in different modules, which will take precedence over global settings for that module.   Year Independent FY
Month
Day
Period
Year Shift
Jan 31 10 -1
Feb 28 11 -1 for last yr
Mar 31 12 -1
April 30 1 0
May 31 2 0
June 30 3 0
July 31 4 0
Aug 31 5 0
Sept 30 6 0
Oct 31 7 0
Nov 30 8 0
Dec 31 9 0

IMG/FA/GLOBAL SETTINGS/DOCUMENT
  • Posting Periods  :  The variant principle is widely used in the R/3 system to assign special properties to one or more R/3 objects. The advantage of using variants is that it is easier to maintain properties which are common among several business objects ( FSV, FYV, PPV )
  1. Steps  :  Define the variant  -  K4
  2. Populate the variant  -  calender year
  3. Assign the variant to the appropriate company code.
  • Define Variants for Open Posting Periods  :  define as necessary. [OBBO]
  • Open & Close Posting Periods  :  In case of a FY which spills over 2 years, define 2002-03 as 2002,2003 with periods 1-12, & 13-16. OB52
  • Assign Posting Period Variants to Company Code  :  assign. [ OBBP ]
  • Document Number Ranges   :  Copy from. Once copied, internal no range is given. External No range if checked, is to be given by the user. [OBA7]
  • Define Document Number Ranges  :  not necessary if copied earlier.
  • Copy to Company Code  :  not necessary if copied earlier.
  • Copy to Fiscal Year  :  not necessary if copied earlier.
 
IMG/FA/GLOBAL SETTINGS/DOCUMENT HEADER  
 
  • Define Document Type  :  [ OBA7 ] Predefined document types are already in place. SA – G/L a/c type. A/c type allowed  :
  
 
  1. Assets
  2. Customers
  3. Vendors
  4. Material
  5. G/L  Account.
 
 
  • Control Data  : 
  
 
  1. Net Doc Tyoe – whether NETT
  2. Customer vendor check
  3. Negative postings allowed
  4. Inter Company Posting
 
 
  • Required during Document Entry  : 
 
 
  1. Reference No.
  2. Document Header Text.
 
 
  • Special Usage  :
  
 
  1. Batch Input only
  2. Rollup – minimum details saved
  3. Planning
  4. Account Allocation
 
 
  • Default Value  :  Exchange rate type for foreign currency document …….. [  M   avg translation rate ]
  
 
  • Assignment of Document Class to Document Type  :  Document class for Cr Memo would be C.
  
 
  1. A     -     Invoice
  2. B     -     Payment
  3. C     -     Credit Memo
  4. D     -     Debit  Memo
  5. E     -     Customs Document
  6. F     -     RG ----
  7. G    -     RG ----
 
 
  • Maximum Exchange Rate Difference  :  in %age terms for each co code.
    DEFINE RETAINED EARNINGS A/C  [  OB53 ]
  
IMG/FA/GLOBAL SETTINGS/LINE  ITEM/CONTROLS  
 
  • Posting Key  [ OB41 ] :  40/50   Dr  /  Cr   GL  A/c  [ global ]
  • Field Status Variant  [ OBC4 ] :  [ local ]  -  normally copy as. You group several field status groups into one field status variant. Assign a company code to a FSV. This allows you to work with the same FSG in any no of co codes. A FSG determines the screen layout for doc entry. Fields can have the following statuses. Optional / Required / Suppresed entry. Enter the FSG in the master record of the GL a/c. When a doc is entered, the definitions stored for the group are effective. The FSG determines which fields are ready for input, required and hidden. Bear in mind that additional assignments [ i.e. cost centers or orders ] are only possible if data can be entered in the corresponding fields.
  • Assign FSV to Company Code  : assign.  [ OBC5 ]
  • Screen Variants for Doc Entry  : 
  
 
  1. Standard  -  to be used.
  2. Austria & Switzerland
  3. France & Witholding Tax – for TDS.
 
 
  • Define Tolerance Groups for Employees  : Not defining tolerance groups will restrict data entry.  [ OBA0 / OBA4 ]
  
 
  1. Valuewise  [upto 1,000,000 etc ]
  2. Cash Discounts
  3. Payment Difference [not recd full amount]
 
 
  • Assign User / Tolerance Groups  :  assign.
  
 
 

CD Package costs only USD$50



Click here for non-credit card payments





See other SAP products on sale