With a field status you decide the status of a specific field on screen. Usually the status can be one of these: hide, display, optional, or required.
Example:
![]()
A field status group consist of many field statuses grouped in different areas or groups:

1. Field status group for G/L accounts #
In the field status group defined for an account group you set which are the relevant fields of the G/L accounts assigned to that group. When you change a field status of the group, all its G/L accounts are affected. See the following video for more detail.
2. Field status group for postings #
In order to define the field status when posting FI documents, you can use:
- A transaction-dependent field status group, assigned to the desired posting keys.
- An account-dependent field status group, assigned to the G/L account master data.
Since both options can be used, a field could have a different status when evaluating each option. The status that prevails is the one with a higher priority (1-Hide, 2-Required, 3-Optional). For instance, having the “Hide” and “Required” statuses in a field will mean that the field will be hidden.
See the following video for more detail:
2.1. Subledger account posting #
For an account of a subledger, such as a vendor or a client account, the field status group applied is the one assigned to the G/L reconciliaton account of the subledger account.
2.2. Field status variant #
The field status groups for postings are assigned to a field status variant, and this variant can be assigned to one or more company codes. Usually there’s only one field status variant assigned to all company codes.
3. Related objects #
The following topics have been mentioned in this topic and you should consider going over them:
4. Related transactions and apps #
These are some Fiori apps related to this topic:
- Manage G/L Master Records.
These are some transactions codes to access some of the points related to this topic:
| Transaction | Description |
|---|---|
| FSS0 | Edit and copy G/L accounts (company code segment) |
| OBD4 | Define the account group and its field status |
| OB26 | Define the screen layout for each activity/transaction (its field status group) |