What is a Field Status Variant and how to assign to the company code in SAP FICO?

Field Status Variant

O Field status variant controls the fields of a transaction at a line item level

O For example, if you want to hide, display, required entry, optional entry for a field, then you can use it through field status variant / group assigned in company code segment of a G/L master

O Field status variant can be created by following the 3-step method of variant principle

O It is 4-digit alphanumeric key

O SAP provides pre-defined field status group which can be copied to create your own

O Define field status variant: T-code: OBC4

O Menu path: Display IMG -> Financial Accounting -> Financial Accounting Global Settings -> Ledgers -> Fields -> Define Field Status Variants

O If you do not maintain the field status, all fields will be hidden

O Assign company code to the field status variant: T-code: OBC5

O Menu path: Display IMG -> Financial Accounting -> Financial Accounting Global Settings -> Ledgers -> Fields -> Assign Company Code to Field Status Variants

1. What is Field Status Variant?

Q1. What is a Field Status Variant?

Answer

Field Status Variant controls field behavior during document posting at transaction level, such as whether a field is required, optional, or suppressed.

📌 From your content:

• Controls fields at line item level during transactions

---

🔥 Key Concept

FSV = Transaction Level Field Control

---

2. Where is it Used?

• During postings like:
  • FB50 (GL posting)
  • FB60 (Vendor invoice)
  • FB70 (Customer invoice)

---

3. Variant Principle (Important)

Q2. How is FSV configured?

1. Define Variant → OBC4
2. Maintain Field Status Groups
3. Assign to Company Code → OBC5

---

4. Field Status Groups (Inside FSV)

👉 FSV contains multiple Field Status Groups (FSG)

Example:

• G001 → General accounts
• G002 → Bank accounts
• G003 → Expense accounts

---

5. Field Control Options

Status	Meaning
Suppressed	Hidden
Required	Mandatory
Optional	User choice

📌 Note from your content:

• No direct “Display” option here

---

6. Assignment Logic

Company Code → Field Status Variant
G/L Account → Field Status Group

---

7. Real Flow

Company Code (FSV)
        ↓
G/L Account (FSG)
        ↓
Posting (Field Behavior)

---

8. Important Rule

Most restrictive setting wins

👉 Combined with:

• Posting Key
• Account Group

---

9. Difference from Account Group (Important)

Feature	Account Group	Field Status Variant
Level	Master Data	Transaction
Use	GL creation	Posting
Control	Field visibility in FS00	Field behavior in FB50

---

10. Real Interview Answer

“What is Field Status Variant?”

Answer:

Field Status Variant controls field behavior during transaction posting in SAP. It is assigned to company code and contains multiple field status groups, which are assigned to G/L accounts. It helps define whether a field is required, optional, or suppressed during document entry.

IV. Field Status Variants in SAP S/4HANA – Controlling Document Entry with Precision

In every SAP S/4HANA implementation, controlling what users can and must enter in accounting documents is critical for data quality, compliance, and process discipline.
This control is achieved through the configuration of Field Status Variants and Field Status Groups.

In this article, we will cover:

• What is a Field Status Variant

• What is a Field Status Group

• How Field Status controls document entry

• How to define and copy Field Status Variants

• How to maintain Field Status Groups

• How to assign Field Status Variant to Company Code

---

What is a Field Status Variant?

A Field Status Variant is a configuration object that contains a collection of Field Status Groups.

It controls:

• Which fields are Hidden / Suppressed

• Which fields are Display only

• Which fields are Required

• Which fields are Optional

during:

• Journal entry posting

• Vendor and customer postings

• Asset postings

• Clearing and adjustment postings

In simple words:

A Field Status Variant controls the screen layout and input behavior during financial document entry.

---

What is a Field Status Group?

A Field Status Group is a subset within a Field Status Variant that controls a specific group of fields.

Examples of Field Status Groups:

• General posting data

• Payment transactions

• Tax data

• Bank data

• Asset data

• Receivables / Payables clearing

Each G/L account is assigned one Field Status Group in its company code segment.

This determines:

• Which fields appear

• Which fields are mandatory

• Which fields are hidden

for that particular G/L account during posting.

---

Key Characteristics of Field Status Variants

• Field Status Variants are created at the client level

• They are independent of company codes

• One variant can technically be used by multiple company codes

• Best practice is to use separate variants per company code

• Field Status Groups are entered in the G/L master (company code segment)

---

Why Field Status Configuration Is Important

Proper Field Status configuration ensures:

• Mandatory business data is always captured

• Irrelevant fields are hidden

• Data quality is improved

• Posting errors are reduced

• Compliance and audit requirements are met

Example:

• Make Payment Terms mandatory for vendors

• Suppress Assignment for certain accounts

• Require Cost Center for expense accounts

---

Best Practice: Always Copy Standard Variants

SAP strongly recommends:

• Do not create Field Status Variants from scratch.

• Always copy a standard SAP variant and modify it.

Standard variants are supplied with:

• Company Code 0001

• Company Code 1000

• Company Code 1710 (S/4HANA best practice)

This avoids:

• Missing dependent tables

• Incomplete configuration

• Technical inconsistencies

---

Step 1 – Define (Copy) Field Status Variant

T-Code: OBC4

IMG Path:
Financial Accounting → Financial Accounting Global Settings → Ledgers → Fields → Define Field Status Variants

The Change View “Field Status”: Overview screen is displayed.

Steps:

• Use Position to search for standard variant (e.g. 0001 or 1710)

• Select the variant

• Click Copy As…

Maintain:

Field	Example
Field Status Variant	AT01
Description	Field Status Variant – AT01

Click Copy and choose:

• Copy All → Copies variant and all dependent Field Status Groups

This creates your own variant with all standard groups.

---

Step 2 – Display and Review Field Status Groups

After copying:

• Select your Field Status Variant

• Double-click Field Status Groups

You will see a list of groups such as:

• G001 – General

• G012 – Receivables/Payables Clearing

• G067 – Asset Posting

• Payment Transactions

• Taxes

• Additional Account Assignments

These groups control different sections of the posting screen.

---

Step 3 – Maintain a Field Status Group

Let us take a practical example.

Business Requirement

During receivables and payables clearing,
Due Date and Payment Terms must be mandatory.

Steps:

• Open Field Status Group G012 – Receivables/Payables Clearing

• Double-click Payment Transactions

Set:

Field	Status
Due Date	Required
Payment Terms	Required

Save your changes.

This ensures:

• User cannot post or clear a document without entering these fields.

---

Field Status Options (Priority Order)

For every field, SAP offers four options:

• Hidden / Suppressed – Field is not visible

• Display – Field is visible but not editable

• Required – Field must be entered

• Optional – Field may be entered

Priority rule:

Hidden > Display > Required > Optional

If multiple controls exist, the most restrictive setting applies.

Error message if required field is not provided - An entry is required in Value date field for account GL Code,

---

Step 4 – Assign Field Status Variant to Company Code

T-Code: OBC5

IMG Path:
Assign Company Code to Field Status Variant

Assign:

Company Code	Field Status Variant
AT01	AT01
AT02	AT01
AT03	AT01
AT04	AT01

Best Practice:
Use separate Field Status Variants per company code so that changes in one do not impact others.

Save your entries.

---

Where Field Status Is Used in Practice

Field Status is applied in:

• FB50 – G/L Posting

• FB60 – Vendor Invoice

• FB70 – Customer Invoice

• F-02 – General Posting

• Clearing transactions

• Asset postings

It directly controls what the user sees and must fill.

---

Interview Key Points

What is a Field Status Variant?
“A Field Status Variant controls the field behavior during document posting by grouping Field Status Groups.”

What is a Field Status Group?
“A Field Status Group controls which fields are required, optional, displayed, or hidden for a specific G/L account.”

Best practice?
“Always copy a standard SAP Field Status Variant and modify it, instead of creating from scratch.”

Where is Field Status Group assigned?
“In the company code segment of the G/L account master.”

A Field Status Variant controls which fields are mandatory, optional, display or suppressed in various accounting documents such as GL postings, customer invoices, and vendor invoices.

---

What is Field Status Variant?

Field Status Variant controls:

👉 Which fields are Mandatory
👉 Which fields are Optional
👉 Which fields are Hidden (Suppressed)
👉 Which fields are Display only

During document posting.

So earlier we controlled WHEN you can post (posting period).
Now we control WHAT you must enter while posting.

---

Why This Exists (Real Scenario)

Imagine users posting GL entries freely.

Someone posts a Bank GL entry but forgets to enter:

• Value date

• Assignment

• Text

Bank reconciliation becomes a mess.

Finance complains:

“Why are important fields blank??”

Solution → Field Status control.

---

The Hierarchy (Very Important)

This topic has a hierarchy. Memorize this chain.

1️⃣ Field Status Variant → assigned to Company Code
2️⃣ Field Status Group → assigned to GL Account
3️⃣ Field Status → controls fields during posting

This chain is frequently asked in interviews.

---

What is Field Status Group?

Field Status Group is where real control happens.

It is assigned in GL Account master.

Example:

• Bank GL → special fields required

• Expense GL → cost center mandatory

• Vendor reconciliation → different fields required

Different GL accounts need different fields.

So we assign Field Status Group to each GL.

---

Four Field Status Options

During posting, each field can be:

Status	Meaning
Suppress	Hidden completely
Optional	User may enter
Required	Mandatory
Display	Visible but cannot edit

This is core interview content.

---

Example (Bank GL Posting)

When posting to Bank account, system may require:

• Value date → Required

• Assignment → Optional

• Cost center → Hidden

• Amount → Required

This behavior comes from Field Status Group.

---

Real Consultant Insight

Field status ensures:

• Data quality

• Standardization

• Error prevention

• Easier reporting

Without this → inconsistent postings.

---

Interview Answer Version

If asked:

What is Field Status Variant?

Answer:

Field Status Variant controls which fields are mandatory, optional, suppressed, or display-only during document posting. It is assigned to the company code and works together with Field Status Groups assigned to G/L accounts.

Clean. Strong.