Fiscal Year Variant Configuration guide:
Before learning about Fiscal year variant Configuration guide,
lets understand the concept of Fiscal year. SAP FICO introduced Fiscal year to
divide Company’s transactions into a specific accounting period, usually one
year, So that company can prepare Financial reports such as Balance sheet and Profit and loss Statement.
The main Benefits of Fiscal year in SAP FICO
i. To record Financial transaction.
ii. To prepare Financial Statements.
iii. To Compare business performance.
iv. To manage Accounting Periods.
v. To Support tax and legal reporting.
What is Fiscal year variant?
A Fiscal year variant in SAP defines the when the financial
year For accounting Starts and ends, how it is divided monthly accounting periods
also called number of posting periods (usually 12months) and 4 special periods
are needed to record year end adjustments for auditing and Tax purposes.
For Example: If a Company’s Financial year in India Starts in April and Ends in March the
following year, SAP Uses the fiscal Year variant to understand these 12 months as
its accounting period. For this reason Fiscal year variant should be Configured
Correctly.
How to Configure Fiscal year Variant in SAP S/4 HANA? Without Non Calender year
=the Above image shows how to configure Fiscal year Variant
in SAP S/4 HANA in Four steps namely:
Step1: use transaction Code -OB29 to open
Fiscal year Variant.
Step 2: Create Variant: Enter variant Z4,
Description, 12 normal posting periods and 4 Special periods.
Step3: Define periods: Map April to March into
posting periods 1-12.
Step 4: Use OB37 assign the fiscal year variant to company code 1000.
Important SAP FICO note: The screens are illustrative
SAP GUI-style screens, not actual captured system screenshots. The period
year-shift settings must be checked carefully before saving.
configuration path:-
1. Define / Maintain Fiscal Year Variant
IMG Path:
SPRO → SAP Reference IMG → Financial Accounting →
Financial Accounting Global Settings → Ledgers → Fiscal Year and Posting
Periods → Maintain Fiscal Year Variant (Maintain Shortened Fiscal Year)
T-Code: OB29
Calendar year Vs Non Calendar year:
A Calendar year means Company’s Financial year Starts
with Jan month and ends in December
In SAP 12 posting periods automatically match the 12 calender months
For Jan -posting period -1
For Feb-posting period -2 and so on.
Non Calender year:
A Non Calender year
means Company’s financial year doesnot starts with Jan or say it starts with April to march.
Example:
For April -Posting period -1
For May -posting period -2 and so on.
How to Configure Calender year in Sap s/4 HANA
For Non Calender year there is year shift of -1 , Say
Till December the posting period will be 9. After that January in the coming
year-posting period will be 10.
But the remaining months in the existing year are denoted by
-1.Apart from calendar year and non calendar year there is shortend calendar
year where the posting periods are fewer than 12 .
Fiscal year variant further divides as year independent where
posting periods and dates are same every year.
In year dependent, periods are different from year to year.
2. Assign Fiscal Year Variant to Company Code
IMG Path:
SPRO → SAP Reference IMG → Financial Accounting →
Financial Accounting Global Settings → Ledgers → Fiscal Year and Posting
Periods → Assign Company Code to a Fiscal Year Variant
T-Code: OB37
Configuration steps:
- Execute
transaction code OB37.
- Select
the required company code.
- Enter
the Fiscal Year Variant (e.g., V3 for April–March, if configured).
- Save
the changes.
|
Company Code |
Company Name |
Fiscal Year Variant |
|
1000 |
ABC India Pvt. Ltd. |
V3 |
Note: you can assign Company code to Controlling area using fiscal
year variant of 12 posting periods and Four special periods that has a fiscal year variant of 12 posting
periods and 1 special period to avoid Time period conflict.
Prerequisites before configuring Fiscal year Variant:
1.Understand the company’s Financial year, it mean
check if it is a calendar year -january to December or non calendar year- April
to march.
2. SAP System access and authorization
You should have required authorization to access SAP
Configuration activities.
Important transaction codes:
OB29 – Define Fiscal Year variant
OB37 – Assign Fiscal year variant to company code.
3.Decide the fiscal year variant
Decide Which Fiscal year Variant Code You want to use.
Example: K4-standard calendar year variant
V3 or Z1 examples for non calendar year or Non calendar year
4.Prepare posting period Details
For Non Calendar year, Collect the following information:
i.Month, ii. Day limit
iii. Posting period iv. Year Shift
For example if the financial year is April to march, January
to march require a year shift of -1 when the fiscal year is identified by its
starting year.
5.Basic Financial Accounting Setup:
Understand the company’s organizational and Accounting Stucture,
including:
Company Code, Chart of Accounts, Ledger Settings
You should know which company code will use the fiscal year
variant.
Practicle Example:
ABC India Pvt ltd wants to configure its financial year from
April 2026 to march 2027.
Before starting Fiscal year Variant configuration , the
consultant should know
Requirement Business
Decision
Company Code – 1000
Financial year starts-April
Financial year ends – March
Fiscal Year type – Non Calendar
Posting Periods -12
Special periods-4(if required)
Fiscal year variant- Z1(Example)
Fiscal Year Variant Configuration Sequence:
1.OB29 – Defjne fiscal
year variant
2.Define posting periods.
3. OB37 – assign the variant to company Code 1000
Common Mistakes in Fiscal year variant Configuration.
1.Selecting the wrong fiscal year type:
Mistake: Selecting the Calender year check box even
when financial year follows April to march.
How to avoid: Understand Company’s fiscal year before
Selecting calendar check box in OB29
How to rectify: Execute the transaction code
OB29,Open the relevant fiscal year
variant, check whether the calendar year check box is selected, If company
follows April to march , ensure the check box is not selected. Save and
validate Configuration.
2.Incorrect year shift settings:
Mistake: Forgetting to maintain the correct year
shift for January, February and march in an April- March financial year.
For example January 2027 should belong to April 2026, if the
year shift is incorrect, SAP may assign transactions to wrong fiscal year.
How to avoid: maintain the fiscal year -1 for January,
February, march when the fiscal year identified by its starting year.
How to rectify: Execute OB29, Select the relevant
Non-Calendar Fiscal Year Variant, Open the Periods section, Locate January,
February and March, Maintain Year Shift as -1 for these three months, Verify
the remaining months have the correct year shift, Save and test the period
determination.
3.Incorrect posting periods:
Mistake: Entering the incorrect number of posting
periods.
For Example, Company requires 12 postings and consultant
posts only 11.
How to avoid it: Confirm the company’s accounting
Requirements and configure correctly
How to rectify it: Execute OB29, Select the relevant
fiscal year variant, Check the number of
posting periods field. Change it to 12 , if the business requires 12 monthly
periods. Confirm the actual requirements first.
4.Incorrect Day limits:
Mistake: maintaining
february’s day limit 28 instead of 29.
How to avoid it: maintaining the correct day limits,
include 29days for february where required.
How to rectify it: Execute OB29, Select the fiscal
year variant.Open periods section, locate February, check the day limit Field,
maintain the 29 days where appropriate. Save and test the configuration,
including leap years.
5.Forgetting to configure special periods
Mistake: Not Configuring special periods required for
year end adjustments.
For example Finance
team wants to post audit adjustments after December posting period, but
consultant has not provided any Requred special period
How to avoid: Discuss year end adjustment
requirements with finance team aand Configure up to four special periods if
needed.
How to rectify: execute OB29, select fiscal year
variant, check the number of special periods field, If the business requires
them maintain up to 4., save the configuration.
6.Assigning Wrong Fiscal year variant to Company Code.
Mistake: assigning
an incorrect fiscal year variant to a company code in OB37
Example, ABC India pvt ltd follows April to march, where the
consultant assigns it to January to December variant.
How to Avoid: Verify the financial year followed by each company code
before assigning he variant.
How to rectify: Execute transaction code OB37, Locate
the relevant company code, Check its currently assigned fiscal year variant,
assign the correct variant according
tobusiness requirements, save and validate the assignment.
7. Duplicate Fiscal year variants:
Mistake: creating new
variant when existing standard
variant already meets the business requirements.
Example creating a new calendar year variant instead of
using the existing standard K4 variant.
How to avoid: Check the existing variant in OB29
before creating a new One.
How to rectify: Execute OB29, review the existing
fiscal year variant, Check Whether the
standard K4 variant meets the company’s claender year requirements., if it does use the existing variant instead of creating
other one.
If an unnecessary variant has already created, but is unused,
assess whether it can be removed.
8.Not testing Configuration:
Mistake : completing the configuration with out
checking whether SAP determines the Fiscal year variant and Posting periods.
Example: a transaction
dated 15 january 2027 should fall under the postring period of 10 for an April -march fiscal year.
How to avoid: test different posting dates,
especially dates around financial year boundary.
How to Rectify: Check the fiscal year variant in OB29, verify the
assignment in OB37, test representative
posting dates using the appropriate SAP
posting or period checking functionality. Verify the fiscal year and posting period determined by SAP.
Check year end dates and leap year dates.
9. Ignoring Company Code requirements:
Mistake:
Assigning the same fiscal year
variant to all company codes without checking their financial year
requirements.
For example , ABC company has @ company codes
1000 for April to march
2000 for January to february
How to avoid: understand the financial year requirements of each company
separately.
How to rectify it: Collect the financial year details of all company codes, identify which
company follows April to march, which follows January to December, select and
create the appropriate fiscal year variants, ssign them individually using OB37,
verify each assignment.
Important SAP FICO Interview questions
Q1. What is the difference between Calendar and Non
Calendar Year?
Calendar year Starts in January and ends in December, where
as Non Calendar year starts in Another month such as April and ends in
following year.
Q2: Why do we use Year shift -1 in April -March Fiscal year?
Because January tp march belong to the next calendar year
but still belong to previous Fiscal year.
Q3: What happens if we select the calendar year checkbox?
SAP Automatically considers January to December as 12
posting periods.
Q4: Why do we enter 29 for February while configuring a
NON calendar Year?
To Ensure SAP Correctly Handles February 29 during leap
years.
Q5: Which transaction codes are used?
OB29 – define fiscal year variant
OB37 – assign fiscal year variant to company code.


Comments
Post a Comment