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)

SAP FI Certification Material

1. Organizational Units
   

• Client
  • 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:
  • Independent legal entity
    
  • For external purpose
    
     
• Business Area
  • For internal purpose
    
  • Can be used across company codes
    
  • Can have financial statement for each Business Area
    

• Create company code steps
  • Copy co. code
    
  • Copies :
    • Definition (company name)
      
    • Global parameters (COA, Fiscal year, Co code default)
      
    • Tables
      
    • G/L a/c's
      
    • Account determination
      
  • 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
      

1. Exercise: Organizational Units
   

• Copy company code
  • Tcode: EC01
    
  • Data : MR03
    

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

Co. code	MR03
Country	US
Currency	USD
Language	EN

• Enter company code Global Parameters
  

Company code	MR03
Company	1000
COA	INT
Fiscal Year Variant	33
Field status variant	1000
Posting Period Variant	MR05

1. Variant Principle
   

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

1. Fiscal Year
   

• Fiscal Year Variant:
  • Define a fiscal year with posting periods
    
  • Fiscal year contain posting periods + Special posting periods
    
  • Maximum periods = 16
    
  • System derive period for a document from the posting date
    
  • Special posting period:
    
  • Used for yearend closing transactions. Posting date falls in last period, can post in special posting period
    
  • E.g.: FY with PP = 12 and special period = 4. Transaction date falls in 12^th posting period can post in 4^th special (16^th) period.
    

• Year Independent Fiscal Year Variant:
  
  • FYV uses same number of periods each year
    
  • Posting period start and ends on the same date every year
    
  • Can be Calendar Year .Here PP = 12 months of the year
    
  • 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?
  • One fiscal year has fewer posting periods than others
    
  • Start and End dates of posting periods differ from year to year
    
• Maintain a Fiscal Year Variant
  • Tcode: OB29
    
  • Data: FYV : 33
    

• Assign Fiscal Year Variant (33) to company code MR03
  • Tcode: OB37
    
• Create a FYV (Non calendar year FYV)
  • Tcode: OB29
    
  • Data:
    

FYV	64
Description	4 periods
Number of posting periods	4 ( Each period has 4 months)
Number of special periods	1
Provide necessary year shift

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

1. Master Data:
   

1. General Ledger Accounts
   

• Chart of Accounts:
  • A variant that contain basic of GL a/c
    
  • Has a 4 character ID
    
  • Define properties of GL a/c like language, Length of GL accounts
    
  • COA assigned to a company code
    

• Definition of Chart of Accounts
  • Tcode: OB13
    
  • 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:
  • 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
  • Co. code Segment:
    
    • To use one of the GL account from COA need to create a company code segment
      
    • Control data
      
    • Bank / Interest
      
    • Information
      
  • Chart of Account Segment:
    
    • Type / Description
      
    • Key word in COA
      
    • Information in COA
      

• Balance sheet a/c
  • Balance C/F to the same a/c
    

• P/L a/c:
  • 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
  • Grouping of similar types of accounts. E.g. cash a/c, liquid funds a/c, fixed assets a/c, Expense a/c
    
  • Account group has a number range. For G/L accounts it's always internal number assignment
    
  • Account group controls the display of fields (Field status: Display/ Change ...) in the GL master (FS00)
    

• Field Status
  • Field status enable control and display of GL a/c' master data fields
    
  • Field status ranking:
    

Status	Field Status	Rank
Hide	Not used	1
Display	Field display only	2
Required	Field required value	3
Optional		4

• Reconciliation account
  • This is a vendor / customer GL a/c in COA. Its corresponding account exist in vendor / customer sub ledger
    
  • All postings to sub ledger posted to reconciliation GL a/c in GL
    
  • Reconciliation a/c type: D: Customers, K: Vendors, Assets
    
  • Cannot post directly to reconciliation a/c
    
  • Details of customer / vendor reconciliation a/c: SE38 – RFDKVZ00
    

• Line Item Display
  • Show each transaction as a line in a GL a/c display
    
  • Line Item display not possible in following cases:
    
  • Reconciliation a/c (Line item display in sub ledger)
    
  • Revenue a/c (Sales)
    
  • Material Stock a/c
    
  • Tax a/c (Tax amount per line item checked when document displayed)
    

• Open Item Management:
  • These a/c have line item display activated
    
  • Open Item display mandatory for a/c with offsetting entries
    
  • OI management used for following a/c types:
    • Bank clearing a/c
      
    • GRIR a/c
      
    • Salary clearing a/c
      

• Account Currency
  • Can select company code currency / Local currency as Account currency
    
  • Can also select foreign currency as account currency
    
  • Where LC = A/C currency, can post in any currency
    
  • Where FC = A/C currency can post in only the FC to this GL a/c.
    

• Only balance in Local currency:
  • If selected transaction figures to this a/c posted in local currency only
    
  • To be selected for clearing a/c like GRIR to avoid difference due to exchange rates fluctuation
    
  • 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
  

FS00	One step centrally
FSP0	COA Segment
FSS0	Co. Code segment
OBY2	Copy co. code segment from another company code
OBY7	Copy COA Segment from another COA

1. Customer / Vendor Accounts
   

• Customer / Vendor Master Data have 3 segments
  • General data:
    • At client level
      
  • Company code data:
    • Any company code that wishes to do business with customer / vendor has to have a company code segment
      
  • Customer:
    • Sales area segment
      
  • Vendor:
    • Purchasing org. Segment
      

• SE38 – RFBIDE10 / RFBIKR10:
  • To transfer customer / vendor master data from Source Company code to another company code
    

• Can activate automatic duplication check
  

• Account Group for customer / Vendor:
  • Once a customer / vendor created cannot change its a/c group in FI
    
  • Controls field status of customer / vendor master records
    
  • Controls customer / vendor number range
    

• Number Range:
  • Can be internal / external
    
  • Each number range can be assigned to one / more account group
    

• Special Customer / Vendor master record
  • These are one time customer / vendor
    
  • No information about customer / vendor entered in the master record
    
  • Customer / Vendor information entered at the time of document posting
    
  • Special customer / vendor master record cam be used for more than one Customer / vendor
    

• Dual Control Principle
  • Can define certain customer / vendor fields in SPRO as sensitive. For e.g. vendor bank address
    
  • Now if these fields are changed customer /vendor is blocked for payment
    
  • Block removed when a second person with authorization confirms / reject such change
    

1. Exercise General Ledger, Customer, Vendor
   

• Copy GL Account group
  • Tcode: OBD4
    
  • Data:
    

Copy from	Copy To
SAKO	CD05
ERG	AE05

• Create a GL a/c in GL a/c group AE05
  • Tcode: FS00
    
  • Data: 176499 (Expense a/c)
    

• Display COA:
  • 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
  • Tcode: SPRO – FA – AR/AP – CA – MD – Preparation for creating CMD – Define a/c group with screen layout
    
  • Data: Copy from KUNA to D05
    

• Assign number range to a/c group (D05)
  • Tcode: SPRO – FA – AR/AP – CA – MD – Preparation for creating CMD
    

• Create customer A/C in the account group D05
  • Tcode: FD01 / Sap Easy
    

• Search term field in Vendor master record
  • Controlled by field status group
    
  • Search term A: Required entry so appear
    
  • Search Term B: Suppressed entry so not appear
    

• Define sensitive fields for dual control
  • 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)
  • Customer: FD09
    
  • Vendor: FK09
    

• Number Assignment
  • GL a/c: Only external number assignment
    
  • Customer / Vendor master Record: Can have either external / internal number assignment
    

• Create a Vendor a/c group
  • 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:
  • Tcode: FK01
    

1. Bank Accounts
   

• Bank master Record
  • Bank master record table: BNKA
    
  • Change to bank master record / Display of bank changes: SE38 – RFBKABL0
    

• House Bank
  • House bank contain bank master data
    
  • Bank account information for electronic payment
    
  • GL a/c for each bank account in the HB
    

• Bank Type:
  • In customer / vendor master record field bank type is used to distinguish different banks
    
  • 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
  

1. Document Control
   

1. Document Structure
   

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

• Document Segment
  • Document Header
    
  • Document Line Items (2- 999 line items)
    

• Document Type
  • Tcode : OBA7
    
  • Document Type defined at client level & applicable for all company codes
    
  • Document Types : AB (Post all GL ac), DG ( Customer and GL), RV (Customer Invoice), RE ( MM billing document)
    
  • 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:
  • Can be internal / external
    
  • Up to a Future Fiscal Year : Beginning of next fiscal year system uses number following the last number of the current fiscal year
    
  • For Each Fiscal Year: System starts with a new number each fiscal year
    
  • A document number range can be assigned to (02) multiple document types
    

• Posting Key
  • PK defined at client level & so valid for all company codes
    
  • 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
  • FSV is a Group of Field status groups ( G001, G003, G004, G005)
    
  • 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
    
  • FSG assigned to GL a/c in tcode FS00 to decide field status of these GL a/c during transactions
    
  • FSV is assigned to a company code
    

1. Posting Periods
   

• Posting Period
  • PP is defined in Fiscal Year Variant
    
  • Usually current PP is open and all other PP close to prevent posting to incorrect PP
    
  • Can have as many PP open as required
    

• Posting Period Variant
  • Several company codes can use the same PPV
    

• Posting period check
  • PP for a document is determined by the posting date
    
  • PPV must contain the a/c type +
    
  • Other a/c types are for further control of accounts D/K/S/M.
    
  • Account type + must always be open if posting to be made to any other a/c type
    

• Year End Closing
  • During year end 2 periods are open. Special PP for the last fiscal year and normal PP for the current fiscal year
    
  • E.g. FY: Apr to Mar. In Apr Special PP 13 and normal PP 1 are open
    

1. Posting Authorizations
   

• Tolerance Group
  • Tcode: SPRO-FA-FAGS – Document – Line Item – Define tolerance group per employee
    
  • 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
  

1. Exercises:
   

• Simple document posting
  

GL a/c posting	FB50
Vendor Invoice	FB60
Vendor Credit Memo	FB65
Customer Invoice	FB70
Customer Credit Memo	FB75
Define/ Display / Copy document number range	FBN1
Display customer line item	FBL1N

• Button Tree: Access screen variants, A/C assignments, Held documents
  

• Make the text field mandatory for GL a/c
  • At client level: GL a/c posting document type: AB. For document type AB in tcode OBA7 make the text field as required entry
    
  • 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
  • Tcode: SPRO-FA-FAGS-Document-PP- Define variant for open posting period
    

• Define which periods are open for a posting period variant
  • Tcode: OB52
    

• Assign PPV to a company code
  • Tcode: SPRO-FA-FAGS-Document-PP- Define variant for open posting period
    

• Create a tolerance group SUPV
  • Tcode: SPRO-FA-FAGS – Document – Line Item – Define tolerance group per employee
    

• Assign tolerance group SUPV to your ID SAPUSER
  • Tcode: SPRO-FA-FAGS – Document – Line Item – Define tolerance group per employee
    

1. Posting Control
   
2. Default Values
   

• Using editing option config screen for different views
  • Document entry: Fields hidden (for specified user) if not relevant
    
  • Document display: Use list viewer for different display options
    
  • Open Items:
    

• When user log in his ID has following properties:
  • Language
    
  • Date format
    
  • Decimal notation
    

• Can control:
  • Whether fiscal year is proposed when document displayed / changed
    
  • 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
  

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

1. 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:
  • Whether the reverse document is allowed to have an alternative posting date
    
  • Whether the reverse document is to be created from negative postings
    

• Documents with cleared items cannot be reversed. Reset the cleared items in FBRA
  
   

1. 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:
  • Enter Invoice number in Invoice reference field under payment Tab during credit memo entry.
    
  • Invoice Terms of Payment copied to the credit memo
    
  • Invoice and credit memo due on the same date
    
     
• Credit Memo not related to the Invoice
  • For credit memo terms of payment to be valid enter V in invoice reference under payment Tab
    
  
   

1. Cross Company code Transactions
   

• Cross company code transactions
  
• Transactions involve 2/ more company codes. E.g.:
  • 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 :
  • 1^st company code + 1^st company code document number + Fiscal Year
    

• Tax posting in cross company code transactions
  
• Whole amount of tax posted to the company code of 1^st line
  
• If tax is to be distributed use report: SE38 – RFBUST10
  

1. Exercise
   

• Ensure document assignment field is not changed in tcode FB02( Restriction at company code level)
  • Tcode : SPRO – FA – FAGS – Document – Line Item – Document change rules
    
  • 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)
  • Tcode : OBA7
    
• Prerequisite for negative reversal:
  • Company code allow negative posting (OBY6)
    
  • 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
  • Tcode : SPRO – FA – AR/AP- BT – Incoming invoices / Credit Memos – Maintain terms of payment – New entries
    

Terms of payment	AC03
Customer Blank	Blank
Vendor	Select
Default base line date	Posting date
%	%%
No. of days	Blank
%	2%
No. of days	14
No. of days	30

 

Explanation area of payment terms automatically defaulted

• Assign terms of payments to vendors
  • Tcode: Easy – accounts – FA – AP – MR – Change – Company code data – Payment transactions
    
     
• Baseline Date
  • Date system uses to calculate vendor/ customer invoice due date and cash discount amount
    
• Taxes steps:
  • Create a new tax code (FTXP)
    
  • Assign a GL A/C to tax code to enable automatic postings (FTXP)
    
  • Define the tax code to be used in enjoy transaction ( OBZT, SPRO – FA – FAGS – AR/AP – BT – Outgoing invoice – Define tax code per transaction)
    
  • Post a customer / vendor invoice to show automatic posting
    
     
• Create a new tax code
  • Tcode : FTXP
    

Country	GB
Tax code	03
Account Type	Output tax
Acct Key	MWS
Tax Percent	20%
COA	INT
Tax a/c	175000

 

 

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

1. Clearing
   
2. Clearing
   

• Two ways to clear OI
  • Account clearing (F-32)
    
  • Post with clearing
    

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

Customer a/c Dr	5000
To sales a/c	5000

• Post a customer credit memo
  • Tcode: FB75
    

Sales a/c Dr	5000
To Customer a/c	5000

• 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:
  • GL a/c number
    
  • Currency
    
  • Special GL indicator
    
  • 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:
  • 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
  

1. Tolerances:
   

• Tolerances:
  
• Rules that define acceptable differences during posting
  

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

• Tolerance Group defined in 2 steps:
  
• Group Definition: Tolerance group defined by:
  • Group key
    
  • Company code
    
  • 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:
  • Partial Payment: Post as partial payment. Document remains open
    
  • Residual Item: Post payment differences as residual item. Original document and payments are cleared. A new document is created for the residual item
    
  • 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:
  • Control type of payment notice sent to the customer
    
  • Control account to which residual item posted
    
  • Exclusion of residual item from credit limit check
    

1. 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
  • Tcode: SPRO – FA – AR/AP – BT – Incoming payments – Incoming payments Global settings – Overpayment / Underpayment – Define Reason codes
    
  • Data:
    

Reason code	Z03
Text	Damaged in Transit
C	Charge of difference via a separate a/c
Type of correspondence with customer

 

 

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

1. Cash Journal
   
2. Cash Journal
   
   
    

• Cash Journal: A tool for managing cash. Supports posting cash receipt and payments
  
   
• Features:
  • 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
  • Company code in which cash journal will be created
    
  • GL a/c's to which CJ entries will be posted
    
  • Currency in which CJ runs
    

1. Special GL Transactions
   

• Types of Special GL transactions
  • Down Payments:
    • Down Payment Request
      
    • Down Payment
      
  • Bill of Exchange
    • BOE Request
      
    • BOE
      
  • Other Transactions
    • Individual value Adjustments (PBDD)
      
    • Guarantee
      
    • Interest
      

• Down payment Request
  • Noted Items, Not included in GL
    
  • Only 1 line
    
  • Reminders
    
  • Payment Program and Dunning Program can access noted items
    
  • FBL5N : Noted Items
    
  • DP Request – Down payment received – DP request considered – Customer Invoice received – DP cleared against customer Invoice
    

• Down Payment
  • Part of Financial statement. Create a proper posting in GL a/c
    
  • FBL5N – Special GL items
    

• Guarantee
  • Automatic offsetting entries
    
  • 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	Reconciliation a/c (FD03)	Alternative Reconciliation (FBKP)	Spl. Transaction Type
21003	140000	196100	G

A/C Type (D/K/S/A/M)	Spl GL Indicator	Description	Reconciliation a/c	Alternative Reconciliation a/c
D	F	Down Payment Request	140000	196000
D	A	Down Payment	140000	170000
D	E	Reserve for Bad Debt	140000	142000
D	G	Guarantee	140000	196100

1. Exercises
   
2. Enter a Guarantee:
   

• Tcode: F-38
  
• Tcode: easy – A/C – FA – AR – Document Entry – Other – Statistical Posting
  
• Data:
  

Document Type	DA
PK	09
Customer	100196
Due on	After 3 months

• Display Guarantee
  • Tcode: FBL5N (Select special GL transaction)
    

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

1. Create a Down Payment Request:
   

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

• Display Down Payment Request of Customer
  • Tcode: FBL5N
    
  • Select Noted Items
    

• Create a Down payment against the DP request created earlier
  • Tcode: F-29
    

• Post a Customer Invoice
  • Tcode: FB70
    

• Clear Customer Invoice against down payment
  • Tcode: F-39
    

Customer	100196
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:
  

Posting date	Last day of current month
PK	19
Customer	100196
Special GL Indicator	E
PK	40
GL a/c ( Bad Debt / Uncollectible)	210100
A/C Entry
Bad Debt / Uncollectible Expense a/c (210100) Dr	6000
To Allowance for Bad debt (PBDD: 142000 alternative reconciliation a/c for customer 100196) B/S account	6000

• Reverse Individual Value Adjustment / PBDD
  • Tcode: FB08
    

1. Held / Park Documents
   

• 2 ways of saving FI documents w/o fully completing it:
  
   
• Held document:
  • Document is incomplete
    
  • No document number is assigned
    
  • No a/c balance are updated
    
  • Not considered for reports
    
  • Document can be found under only user ID
    

• Park Document:
  • Document number is assigned
    
  • Considered for reports
    
  • Document can be found with any user ID
    
  • Can be used as part of principle of dual control