Custom fields · Custom Field Flow Doctor
Custom field not enabled for a required usage
- Default severity
- Major
- Finding code:
- FIELD_EXPOSURE_NOT_ENABLED
- Engine version:
- 2.0.0
What this finding means
Custom Field Flow Doctor reports this finding with the default severity “Major”.
About the engine: Extension field lineage from CDS views through BAPIs to UI
How to fix it
In the 'Custom Fields' app enable the field for the missing usages of the business context (tabs 'UIs and Reports', 'Form Templates', 'Email Templates', APIs) and publish it; re-check that the business context offers the usage in the target release.
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
- Custom Field Flow Doctor
- Accepted formats
- JSON
- What to export
Custom field registry JSON: {'field_name': 'YY1_…', 'hops': [{source_context, target_context, min_release?}], 'field_definitions': {context: {type, length, usages: ['UI', 'FORM', 'API', ...]}}, 'required_exposures': {context: ['FORM', 'API', 'ANALYTICS', 'UI', 'EMAIL']} (or a list for the final context), 'active_scenarios': [...], 'badi_implementations': [...]}.
- Required input
- field_name
- hops or field_definitions
- 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
- Each finding names the knowledge it relies on () and is capped by that source’s verification status.
- Target releases of the engine
- S4H_2022, S4H_2023, S4HANA_CLOUD_2402, S4HANA_CLOUD_2408
Related findings
- MajorCustom field name violates key-user naming
- CriticalCustom field not enabled in target business context
- CriticalCustom field cannot propagate across this hop
- MajorRequired Cloud BAdI implementation missing
- MajorPropagation hop needs a newer release than the target
- MajorIncompatible field type or length across a propagation hop
Terms used on this page
Background reading
- Custom fields with key user extensibility: why a field does not appear in the app, form or APIHow custom fields created with key user extensibility reach UIs, reports, forms and APIs, and why a field that exists on one document is missing on the follow-on document.