Skip to content
ERP Preflight

Custom Field Flow Doctor

Extension field lineage from CDS views through BAPIs to UI annotations

Content reviewed September 26, 2026

Engine
CUSTOM_FIELD_FLOW_DOCTOR
Domain
Output & Extensibility
Version
2.0.0
Target releases
S4H_2022, S4H_2023, S4HANA_CLOUD_2402, S4HANA_CLOUD_2408
Accepted formats
JSON

Input contract

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
  • JSON only: the Custom Fields app has no machine-readable TXT/XML export this engine could rely on.

Finding codes

Finding codes (8)

  • FIELD_MISSING_TARGET_CONTEXTDefault severity: CriticalCategory: DATA_MODEL_INTEGRITY

    Custom field not enabled in target business context

    Remediation: In the 'Custom Fields' app open the field, tab 'UIs and Reports' / 'Business Scenarios', and enable it for the target business context; publish the field again.

  • FIELD_PROPAGATION_BLOCKEDDefault severity: CriticalCategory: DOCUMENT_FLOW

    Custom field cannot propagate across this hop

    Remediation: Activate the SAP-delivered business scenario for the hop (Custom Fields > Business Scenarios) or route the value through the supported intermediate document contexts.

  • FIELD_BADI_REQUIRED_NOT_FOUNDDefault severity: MajorCategory: CUSTOM_LOGIC

    Required Cloud BAdI implementation missing

    Remediation: Implement and publish the listed Cloud BAdI in the 'Custom Logic' app so the field value is copied into the target context (e.g. BADI_FINS_ACDOC_EXT_PERSISTENCE for journal entry items).

  • FIELD_EXPOSURE_NOT_ENABLEDDefault severity: MajorCategory: EXTENSIBILITY_GOVERNANCE

    Custom field not enabled for a required usage

    Remediation: 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.

  • FIELD_NAME_INVALID_PREFIXDefault severity: MajorCategory: EXTENSIBILITY_GOVERNANCE

    Custom field name violates key-user naming

    Remediation: Key-user custom fields must use the YY1_ prefix (developer extensibility: ZZ1_). Recreate the field in the 'Custom Fields' app with a compliant technical name and migrate data before transport.

  • FIELD_RELEASE_LIMITATIONDefault severity: MajorCategory: RELEASE_COMPATIBILITY

    Propagation hop needs a newer release than the target

    Remediation: The business scenario / propagation this hop relies on is available only from the listed release. Plan the flow for a target release at or after it, or route the value through a hop the target release already supports.

  • FIELD_TYPE_MISMATCHDefault severity: MajorCategory: DATA_MODEL_INTEGRITY

    Incompatible field type or length across a propagation hop

    Remediation: Align type and length of the custom field in both business contexts (a key-user field cannot change type after publishing — create a new field and migrate), otherwise values are truncated or rejected.

  • FIELD_PROPAGATION_REQUIRES_BADIDefault severity: InfoCategory: CUSTOM_LOGIC

    Propagation relies on custom BAdI logic

    Remediation: Keep the BAdI implementation under regression test; it must be re-validated after every upgrade.

Input validation codes (5)

  • FIELD_ARCHIVE_REJECTEDDefault severity: MajorCategory: INPUT_VALIDATION

    Archive rejected by ingestion safety limits

    Remediation: The archive exceeded the 100:1 expansion ratio, 500 MB total size, entry-count or 2-level nesting limit, or contained path traversal / encrypted members. Upload a flat, unencrypted archive of the export files. No verdict was produced. Re-export the artifact in one of the formats accepted by Custom Field Flow Doctor (JSON) and re-run the analysis.

  • FIELD_INVALID_INPUTDefault severity: MajorCategory: INPUT_VALIDATION

    Artifact does not match the engine input contract

    Remediation: Provide the artifact type documented for this engine; unrelated or structurally invalid documents are rejected. No verdict was produced. Re-export the artifact in one of the formats accepted by Custom Field Flow Doctor (JSON) and re-run the analysis.

  • FIELD_PARSE_ERRORDefault severity: MajorCategory: INPUT_VALIDATION

    Artifact could not be parsed

    Remediation: Fix the syntax error at the reported line/column (or re-export the file unmodified from SAP). No verdict was produced. Re-export the artifact in one of the formats accepted by Custom Field Flow Doctor (JSON) and re-run the analysis.

  • FIELD_PAYLOAD_TOO_LARGEDefault severity: MajorCategory: INPUT_VALIDATION

    Artifact exceeds the size limit

    Remediation: Split the export (e.g. per package, company code or date range) so each upload stays under the service payload limit. No verdict was produced. Re-export the artifact in one of the formats accepted by Custom Field Flow Doctor (JSON) and re-run the analysis.

  • FIELD_INSUFFICIENT_INPUTDefault severity: InfoCategory: INPUT_VALIDATION

    Required input missing

    Remediation: Supply every input the engine's contract marks as required (see the engine catalog entry). No verdict was produced. Re-export the artifact in one of the formats accepted by Custom Field Flow Doctor (JSON) and re-run the analysis.

Back to the documentation
Custom Field Flow Doctor — ERP Preflight Docs