Account determination · Account Determination Preflight
Conflicting determination entries for the same key
- Default severity
- Major
- Finding code:
- ACCT_DET_CONFLICTING_RULES
- Engine version:
- 1.1.0
What this finding means
Account Determination Preflight reports this finding with the default severity “Major”.
About the engine: OBYC, VKOA, automatic account determination rule validator
How to fix it
Remove the duplicate / conflicting OBYC or VKOA entries so each condition key resolves to exactly one account.
How ERP Preflight detects it
The analysis is deterministic: the same exported files and the same knowledge snapshot always produce the same findings. No SAP system connection is required — you upload exports.
- Engine
- Account Determination Preflight
- Accepted formats
- JSON, CSV
- What to export
Automatic account determination: JSON {'chart_of_accounts', 'company_code', 'obyc_rules': [...], 'vkoa_rules': [...], 'fi_rules': [...], 'ska1_accounts': [...], 'skb1_accounts': [...], 'valuation_classes': [...], 'movement_types': [{movement_type, transaction_key, account_modifier}], 'plants': [{plant, valuation_grouping_code}], 'expected_combinations': [{model, ..., expected_account}]} or CSV exports of T030 (KTOPL, KTOSL, BKLAS, KONTS/KONTU), C001/VKOA (VKORG, KTOSL, SAKNR), SKA1, SKB1. Company-code checks run only for an explicitly supplied company code.
- Required input
- OBYC, VKOA and/or FI determination entries
- Evidence
- Each finding points to the artifact path, line and column, the code snippet and the SHA-256 of the uploaded file. Findings without such a pointer are demoted to confidence UNKNOWN.
- Confidence
- The verdict rests on your artifacts only. Each finding carries a confidence class (VERIFIED, RULE_DERIVED, INFERRED or UNKNOWN) that shows how strong the evidence is.
- Target releases of the engine
- S4H_2022, S4H_2023, S4HANA_CLOUD_2402, S4HANA_CLOUD_2408
Related findings
- MajorCatch-all / default determination entry
- CriticalDetermined G/L account is blocked for posting
- CriticalDetermined account not created in the company code
- CriticalExpected combination resolves to no account
- CriticalNo G/L account determined for a required combination
- CriticalMovement type / plant / valuation class without OBYC account
Terms used on this page
Background reading
- SAP automatic account determination (OBYC and VKOA): preventing posting errors before go-liveHow MM account determination (OBYC) and SD revenue account determination (VKOA) resolve G/L accounts from valuation classes and account assignment groups, and why postings fail after transports.