3731117 - Custom field validation error for Non-OIM accounts in "Create Supplier Invoice" in SAP S/4HANA Cloud Public Edition

When using the Create Supplier Invoice app (Fiori F0859), an error occurs during the validation of custom fields (e.g., fields published to the Accounting Coding Block). The validation logic triggers an error claiming the field is "empty" even when it has been populated on the UI.

This behavior is specifically observed under the following conditions:

• Account Type: The issue occurs only with G/L accounts that are NOT Open Item Managed (non-OIM) (e.g., standard expense accounts).
• Comparison: Accounts that are Open Item Managed (OIM) pass validation correctly.
• App: The error is specific to Fiori F0859; posting via the Post General Journal Entries app (F0718) may work correctly.

SAP S/4HANA Cloud Public Edition

1. Open the Create Supplier Invoice app (F0859).
2. Enter a supplier invoice using a G/L account that is not open item managed.
3. Populate the required custom coding block field(s) and proceed to validate/post.
4. Observe that validation fails, indicating the custom field is empty, and posting is blocked.

The root cause is related to Entry View Summarization (SSCUI 106716).

For non-OIM G/L accounts, the system often attempts to summarize line items to optimize the document structure. During this summarization process, custom coding block fields (like YY1_BUSIUNITCD2_COB) are cleared in the internal memory context used by the Manage Substitution/Validation Rules app (F4406) or BAdI FIN_ACDOC_ITEM_VALIDATION.

Because OIM accounts require individual line-item tracking, they are not summarized, which is why the validation works correctly for them.

1. Deactivate Entry View Summarization (Recommended)

To ensure custom fields are preserved during the validation call for non-OIM accounts:

1. Navigate to Manage Your Solution or SAP Central Business Configuration.
2. Locate SSCUI 106716 (Configure Summarization for Relev. to Fin. Accounting).
3. Deactivate the summarization for the relevant document type or process.
4. Retest the invoice posting; the custom fields should now be correctly populated in the validation context.

2. Verify Custom Field Publication

Ensure the custom fields are published to all required business contexts in the Custom Fields app:

1. Check contexts: Accounting: Coding Block and Journal Entry Item.
2. Go to the UI and Reports tab and ensure Supplier Invoice Item - Create and Journal Entry Item are enabled and published.

3. UI Adaptation

If the fields are published but not appearing correctly:

1. Open app F0859 and enter UI Adaptation mode.
2. Ensure the fields are explicitly added to the "Accounting" or "Cost Center" section.
3. Set the field properties to "Required" or "Optional" directly in the UI if needed.

• KBA 3715619 - Cost Center is blank in BAdI FIN_ACDOC_ITEM_VALIDATION despite being filled on UI.
• KBA 3503677 - Substitution/Validation rule is not working.

create supplier invoice, f0859, validation, custom field, coding block, non-open item managed, non-oim, entry view summarization, posting blocked, supplier invoice, gl account, item-level validation, field appears empty, public cloud, fin_acdoc_item_validation , KBA , MM-FIO-IV-2CL , Fiori UI for Invoice Verification (Public Cloud) , Problem