Symptom
Customer has created a Finance (FI) custom field, and want to add this field for Customer line item management. This works, but the custom field is missing in "Data source Extensions function" in "Custom Fields and Logic" App.
Environment
- S/4Hana Cloud
- Custom Field
- Custom Data Source Extension
Reproducing the Issue
- Create Custom Field YY1_XXXField
- Enable oData for Post Journal Entries
- Add Custom Field to Post Journal Entries app
- Create New Data Source Extension YY1_XXXExt for FAR_CUSTOMER_LINE_ITEMS (CDS View I_JOURNALENTRY).
- Open data source extension and Custom Field YY1_XXXField is not in it
Cause
The “Journal Entry” node in the data source extension “YY1_XXXExt” is bound to the CDS view I_JOURNALENTRY, however, the custom field "YY1_XXXField" is not available in the CDS view I_JOURNALENTRY because this view is not registered for extensibility (TX: scfd_registry).
The business context FINS_CODING_BLOCK allows to extend the CDS view I_JOURNALENTRYITEM, but this CDS views is not available in the data source extension tool, because I_JOURNALENTRYITEM is connected via a 1-to-many association (_JournalEntryItem in I_JournalEntry). The Data source extension tool supports only 1:1 associations.
Resolution
There is no way to make the extension field visible in the Data Source Extension.
See Also
Keywords
Custom Field Data source extension , KBA , BC-SRV-APS-EXT-FLD , Custom Fields , Problem