Quick Answer — SAP Field Selection Inconsistent Error
- The error means a field is set as "Required" in one source and "Suppressed" in another. SAP cannot make a field mandatory and invisible at the same time, so it rejects the posting.
- The two main sources are: the posting key field status (OB41) and the G/L account field status group (OBD4, assigned via FS00).
- Fix: change the conflicting field from Required or Suppressed to Optional in one of the two sources. Optional satisfies both: it allows the field to be filled if relevant or left blank if not.
- Always diagnose first: press F1 on the error message to see which field is causing the conflict. Check OB41 for the posting key and OBD4 for the field status group side by side.
- Changes go through transport — do not change OB41 or OBD4 directly in production without a development and quality system test first.
The conflict is always Required vs Suppressed. Optional vs Required or Optional vs Suppressed do not cause the error — they are compatible. Only Required vs Suppressed creates an irresolvable contradiction that SAP rejects.
The fix is almost always Optional. Changing the conflicting field to Optional in either OB41 or OBD4 resolves the conflict without forcing entry or hiding the field. This is the safest and most common resolution.
The error is G/L account-specific. The same posting key works fine for some accounts and fails for others because different accounts have different field status groups. The posting key setting is global; the field status group is account-level.
Test in development before production. Changes to OB41 and OBD4 affect all documents using that posting key or field status group — not just the one causing the current error. Always transport through the landscape.
This error often appears after a new GL account is created. If someone creates a new GL account and assigns a field status group with settings that conflict with the posting key for that account type, every posting to the new account will fail until the configuration is corrected.
What Is Field Selection in SAP FICO?
Field selection is the SAP mechanism that controls which input fields appear on an accounting document line item — and whether they are mandatory, optional, or hidden. It exists because different GL accounts need different information. A bank account posting needs a bank reference; a cost centre posting needs a cost centre; a customer posting needs a business area. SAP uses field selection to enforce these rules without creating a different transaction for every account type.
Every accounting document line in SAP is validated against field selection rules from two main sources. The posting key (a two-character code like 40 for GL debit or 31 for vendor credit) has its own field status settings, maintained in OB41. The G/L account has a field status group assigned in its master record (visible in FS00), and that field status group is defined in OBD4. SAP combines both sets of rules. Most of the time they are compatible. When they are not, you get the field selection inconsistency error.
Plain English explanation: Think of OB41 as the rules set by the transaction type ("when posting a debit to any GL account, cost centre is required") and OBD4 as the rules set by the specific account ("for this particular account, cost centre is suppressed — do not show it"). If both rules apply to the same posting, SAP has a contradiction and cannot proceed. The fix is to make at least one of the two sources agree on Optional, which means the field can be there if needed or absent if not.
Field Status Priority Rules — How SAP Combines the Three Sources
When SAP evaluates a document line item, it reads the field status from all active sources simultaneously and applies a combining rule. The rule is simple: the strictest setting wins — except when the settings are mutually contradictory.
| OB41 (Posting Key) | OBD4 (Field Status Group) | Combined Result | Error? |
|---|---|---|---|
| Required | Required | Required | No |
| Required | Optional | Required | No — stricter wins |
| Required | Suppressed | Impossible | YES — this error |
| Optional | Required | Required | No — stricter wins |
| Optional | Optional | Optional | No |
| Optional | Suppressed | Suppressed | No — stricter wins |
| Suppressed | Required | Impossible | YES — this error |
| Suppressed | Optional | Suppressed | No — stricter wins |
| Suppressed | Suppressed | Suppressed | No |
Only two combinations produce the error: Required + Suppressed and Suppressed + Required. Both are logically impossible — SAP cannot make a field both mandatory and invisible. The fix is always to move one of the two conflicting sources to Optional, which satisfies both: Optional + Required = Required (fine), Optional + Suppressed = Suppressed (fine).
Which source to change — OB41 or OBD4? If the conflict involves a balance sheet account where the field genuinely should never appear (for example, cost centre on a bank account), change OBD4 — it affects only accounts using that field status group. If the conflict involves a posting key that should not require a field for any account type (for example, posting key 50 should not require profit centre), change OB41 — but be aware this affects every account using that posting key across the entire system. When in doubt, OBD4 is the lower-risk change.
The Three Field Status Sources — and How They Conflict
Field status in SAP FI comes from three sources. The third (document type) rarely causes issues; the first two are responsible for almost all field selection errors.
- Applies to ALL document lines using that posting key
- 40 = GL debit, 50 = GL credit, 01 = customer debit, 31 = vendor credit, etc.
- Configured globally — one setting affects every account
- Commonly sets cost centre Required for certain posting keys
- Change via OB41 → select posting key → field status
- Applies only to G/L accounts assigned to that specific group
- Assigned to each account individually in FS00
- Account-level control — different accounts can have different groups
- Often Suppresses cost centre for balance sheet accounts
- Change via OBD4 → select field status group → field status
SAP combines the two sources using a "stricter wins" rule — except for Required vs Suppressed, which is impossible to resolve. If OB41 says Required and OBD4 says Optional, the result is Required (stricter wins — no error). If OB41 says Optional and OBD4 says Suppressed, the result is Suppressed (stricter wins — no error). But if OB41 says Required and OBD4 says Suppressed, SAP cannot satisfy both rules simultaneously — this is the field selection inconsistency error.
The third source — Document Type (OBC4): Document types can also have a field status, but in most SAP configurations document type field status is set to Optional for all fields and does not cause conflicts. If you have checked OB41 and OBD4 and still cannot find the source of the conflict, check the document type field status via OBC4 as a third diagnostic step.
A quick way to confirm the field causing the conflict without navigating OB41 and OBD4 separately: in the failing document entry screen, press F1 on the error message. The long text of the field selection message typically names the field explicitly (for example, "Field Cost Center" or "Field Business Area"). This saves the diagnostic step of comparing both sources field by field.
Identifying the Conflicting Field
Before you can fix the error, you need to know exactly which field is conflicting and which of the two sources has the incompatible setting. This takes two steps.
Step-by-Step Fix — Resolving the Conflict
Impact assessment before changing OB41. Posting key field status changes affect every document line using that posting key across the entire system. If you change posting key 40 (GL debit), the change applies to every GL debit posting from every user in every company code. Always assess the full impact before changing a posting key setting — changing the field status group (OBD4) for a specific account is almost always the lower-risk option.
Field Selection Errors After a New GL Account is Created
This is the single most common trigger for field selection inconsistency errors in production support — a new GL account is created and given a field status group that was copied from the wrong type of account. The error only surfaces when someone tries to post to the new account for the first time.
Changing a field status group affects every GL account that shares it. Before changing OBD4, run a where-used check to see all accounts assigned to the field status group you are modifying. A change that fixes one account may break a different account that legitimately needed the Suppressed setting. If multiple accounts share a field status group but need different field settings, create a new field status group rather than modifying the shared one.
Useful SAP transactions for field status investigation: SE16N on table SKB1 filtered by ZUAWA (field status group) shows all GL accounts using a specific field status group. SE16N on table T004F shows the field status group definitions. These allow you to assess the full impact of any field status group change before making it.
When Does This Error Typically Appear?
Scenario 1 — New GL account with wrong field status group. A new expense GL account is created for a cost centre that posts to it directly. The field status group assigned in FS00 is copied from a balance sheet account (which has cost centre Suppressed), but posting key 40 (GL debit) has cost centre Required. Every debit posting to this new account fails immediately. Fix: change the field status group in FS00 to one where cost centre is Optional or Required.
Scenario 2 — Balance sheet account with CO requirement. A balance sheet reconciliation account is posted to directly (which is unusual but sometimes done for clearing purposes). The balance sheet account field status group has cost centre Suppressed (correct for balance sheet accounts). But the posting key used requires cost centre. Fix: change the field status group for this account to one where cost centre is Optional, or use a different posting key that does not require cost centre.
Scenario 3 — Clearing transaction fails. A customer or vendor clearing transaction (F-32, F-44) fails with field selection inconsistency even though the original invoice posted fine. The clearing posting uses a different posting key (25, 37) than the original invoice posting key, and that clearing posting key has a different field status that conflicts with the reconciliation account's field status group. Fix: review the clearing posting key field status in OB41.
Trainer insight — the most common real-world scenario: In implementation projects, this error almost always appears in user acceptance testing when end users try to post to GL accounts that were configured quickly without cross-checking the posting key settings. The FICO consultant who set up OBD4 field status groups did not always check OB41 posting key settings for the same fields. The fix takes minutes once you know where to look — the diagnosis is the skill.
SAP Field Selection Inconsistent — 20 Questions Answered
The field selection inconsistent error (typically message F5 354 or similar) appears when the field status of a posting key (configured in OB41) conflicts with the field status of a G/L account's field status group (configured in OBD4). Specifically, when one source says a field is Required and the other says it is Suppressed, SAP cannot satisfy both rules simultaneously and rejects the document.
The error is caused by a conflict between two or more of the three field status sources in SAP FI: (1) the posting key field status (OB41), (2) the G/L account field status group (OBD4/FS00), and less commonly (3) the document type field status (OBC4). The conflict occurs when one source marks a field as Required and another marks it as Suppressed. These two settings are mutually exclusive.
The fix involves changing either the posting key field status (OB41) or the field status group assigned to the G/L account (OBD4). First identify which field is conflicting using the error message details. Then go to OB41 to check the posting key settings, and OBD4 to check the field status group. Change the conflicting field from Required or Suppressed to Optional in one of the two sources so that both can be satisfied.
OB41 is the SAP configuration transaction for maintaining posting key field statuses. Each posting key (40 for GL debit, 50 for GL credit, 01 for customer invoice, 31 for vendor invoice, etc.) has a field status that defines which fields are Required, Optional, or Suppressed for documents using that posting key. OB41 settings apply to every document line that uses the corresponding posting key, regardless of which G/L account is posted to.
OBD4 is the SAP configuration transaction for maintaining field status groups. A field status group is a set of field settings (Required, Optional, Suppressed) for accounting document line items. Each field status group is assigned to one or more G/L accounts via the G/L account master record (FS00). OBD4 defines the rules; the G/L account master record links those rules to specific accounts.
A field status group is a SAP configuration object (maintained in OBD4) that controls which fields are available, required, or hidden on accounting document line items for a specific G/L account. For example, field status group G001 might make the cost center field Required, while G004 makes it Optional. The field status group is assigned to each G/L account in the G/L account master record (FS00, field: Field Status Group).
Press F1 on the error message and read the long text. SAP typically identifies the specific field name that is in conflict. You can also look at the posting key in OB41 and the field status group in OBD4 side by side, comparing the setting for each field. The conflicting field is the one where one source says Required and the other says Suppressed.
Required means the field must be filled for the posting to succeed. Optional means the field may be filled or left blank. Suppressed means the field is hidden and cannot be filled. The conflict that causes the inconsistency error is specifically Required versus Suppressed — SAP cannot make a field both mandatory and invisible at the same time. The resolution is to change one of the conflicting settings to Optional.
Yes, but with caution. Field status group changes in OBD4 and posting key changes in OB41 are configuration changes that require a transport request in a properly maintained SAP landscape. Changes affect all documents using that posting key or field status group going forward. Always test in a development or quality system first. In an emergency, changes can sometimes be made directly in production with appropriate authorisation, but this bypasses the transport process and should be avoided.
Setting the field to Optional in one of the two sources resolves the conflict without forcing users to fill a field they may not need. Optional means the field can be filled if relevant or left blank if not. This is the safest resolution in most cases. Only change from Required to Suppressed if you are certain the field should never appear for that account or posting key combination.
The posting keys most commonly involved in field selection conflicts are 40 (GL account debit), 50 (GL account credit), 01 (customer invoice), 11 (customer credit memo), 31 (vendor invoice), and 21 (vendor credit memo). Posting key 40 often conflicts with G/L accounts that have a cost center field status of Suppressed because some field status groups set cost center as Required for debit postings.
Yes, but less commonly than posting key and field status group. Document type field status (OBC4) is a third source that can contribute to field selection conflicts. However, in most configurations the document type field status is set to Optional for all fields and does not cause conflicts. The most common conflicts are between OB41 (posting key) and OBD4 (field status group).
OB41 controls field status at the posting key level — it applies to all documents using that posting key regardless of which G/L account is posted to. OBD4 controls field status at the field status group level — it applies to specific G/L accounts that have that field status group assigned. When a document line is posted, SAP combines the field status from OB41 (posting key) and OBD4 (account field status group) and applies the stricter rule, except when one says Required and the other says Suppressed — which is the conflict.
During clearing transactions (F-32 for customers, F-44 for vendors, F-03 for G/L accounts), SAP uses the posting keys for clearing items (posting key 25, 37, etc.) combined with the G/L account field status group. If the clearing posting key has a field (such as cost center) set as Required but the reconciliation account has it as Suppressed, the inconsistency error can appear during clearing even if posting worked fine.
FS00 is the transaction for maintaining G/L account master records at the company code level. It includes the Field Status Group field (under the Document Entry tab). This field controls which OBD4 field status group is assigned to the account. Changing the Field Status Group in FS00 immediately changes which field status rules apply to that account for all future postings.
Because each G/L account has its own Field Status Group assigned in FS00. Different accounts can have different field status groups with different settings. An account with field status group G001 (cost centre Required) will conflict with posting key 50 (cost centre Suppressed) while an account with G004 (cost centre Optional) will not. The error is account-specific because the field status group is account-specific.
In a properly maintained three-system landscape (Development, Quality, Production), configuration changes to OB41 and OBD4 must go through the transport process. Emergency changes directly in production are sometimes permitted with explicit authorisation but bypass controls and should be reversed through the transport pipeline as soon as possible. Changes to FS00 (G/L account master) in production may be possible depending on the change management policy.
OBC4 is the SAP transaction for maintaining field status variants and groups. It is used to create and maintain the field status groups that are then assigned to G/L accounts via FS00. OBC4 is the higher-level configuration transaction that contains all the field status groups for a field status variant. OBD4 links to OBC4 and allows you to navigate directly to the group details. In practice, most organisations use OBD4 for day-to-day field status group maintenance.
Always make and test changes in the development system first, then transport to quality for user acceptance testing, then to production. In development, you can create a test document that uses the same posting key and G/L account combination to verify that the change resolves the error without introducing new issues. Never change field status groups directly in production without prior testing.
Yes. VoiSAP's SAP FICO training covers document configuration including posting keys, field status groups, document types, and the interaction between OB41 and OBD4. You practise configuring these settings on a live SAP S/4HANA system and understand why each setting exists — not just how to change it. Book a free demo to discuss your background and how the training is structured.
Book a free demo — discuss document configuration, your SAP career goals, and how VoiSAP trains you on real S/4HANA systems.