SAP Knowledge Base Article - Public

3679381 - Inconsistency in Custom Field Display Across AP and GL Applications

Symptom

  • A custom field of type URL (YY1_URL) was created using the Custom Fields application.

  • The field is enabled for UI usage and appears in both applications:

    • Display Line Items in General Ledger

    • Manage Supplier Line Items

  • The field correctly displays URL values in the Display Line Items in General Ledger app.

  • In the Manage Supplier Line Items app, the field is visible but appears empty (no data).

Environment

SAP S/4HANA Cloud Public Edition

Reproducing the Issue

  1. Create a custom field of type URL with the business context Journal Entry Item (FINS_JOURNAL_ENTRY_ITEM) using the Custom Fields app.

  2. Enable the field for UI usage and relevant apps.

  3. Implement substitution logic in the BAdI FIN_ACDOC_EXT_SUBSTITUTION to populate the field value.

  4. Post a journal entry and verify the field values:

    1. In the Display Line Items in General Ledger app -> field value is displayed.

    2. In the Manage Supplier Line Items app -> field appears empty.

Cause

  • The BAdI FIN_ACDOC_EXT_SUBSTITUTION updates data only in the ACDOCA table.

  • The Display Line Items in General Ledger app reads data from ACDOCA, so the field value is displayed correctly.

  • The Manage Supplier Line Items app reads data from BSEG, where the custom field value is not updated.

  • Hence, the field appears empty in apps based on BSEG, even though it is visible in the UI.

Resolution

  • Implement the substitution logic using the BAdI FIN_ACDOC_SUBSTITUTION instead of FIN_ACDOC_EXT_SUBSTITUTION.

  • This BAdI supports substitution at the item level and ensures data is updated in both ACDOCA and BSEG tables during journal entry posting.

  • Steps to resolve:

    1. Create or open an implementation under FIN_ACDOC_SUBSTITUTION.

    2. Move the existing substitution logic from FIN_ACDOC_EXT_SUBSTITUTION to FIN_ACDOC_SUBSTITUTION.

    3. Test posting a journal entry and verify the URL field now appears populated in both applications.

  • For detailed information, refer to KBA 0002453614 -  FAQ: Universal Journal Extensibility and BAdI documentation confirming respective data update scopes. 

See Also

Keywords

custom field, YY1_URL, manage supplier line items, display line items in general ledger, empty field, ACDOCA, entry view, substitution logic, BAdI, FIN_ACDOC_EXT_SUBSTITUTION, FIN_ACDOC_SUBSTITUTION, SAP S/4HANA Cloud Public Edition , KBA , FI-FIO-AP-IS-2CL , Reporting Apps: Public Cloud , Problem

Product

SAP S/4HANA Cloud Public Edition all versions