SAP custom field problems: field not showing in app, form or API

Documented problems

• Critical
  Custom field not enabled in target business context

  FIELD_MISSING_TARGET_CONTEXT

• Critical
  Custom field cannot propagate across this hop

  FIELD_PROPAGATION_BLOCKED

• Major
  Required Cloud BAdI implementation missing

  FIELD_BADI_REQUIRED_NOT_FOUND

• Major
  Custom field not enabled for a required usage

  FIELD_EXPOSURE_NOT_ENABLED

• Major
  Custom field name violates key-user naming

  FIELD_NAME_INVALID_PREFIX

• Major
  Propagation hop needs a newer release than the target

  FIELD_RELEASE_LIMITATION

• Major
  Incompatible field type or length across a propagation hop

  FIELD_TYPE_MISMATCH

Informational findings

These findings confirm a good state or document a change. They are listed for completeness and are not problems.

• Info
  Propagation relies on custom BAdI logic

  FIELD_PROPAGATION_REQUIRES_BADI

Terms used in this area

• Key-user extensibility
• BAdI
• CDS view

Background articles

• 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.