SAP Knowledge Base Article - Public

3765185 - Restrict Mandatory Section Code To Create Supplier Invoice - Advanced via Business Transaction Type Condition – SAP S/4 HANA Cloud Public Edition

Symptom

  • The Section Code field must be mandatory only when creating a supplier invoice in the "Create Supplier Invoice - Advance" Fiori tile for accounting document type "RE".
  • A validation configured via Manage Substitution/Validation Rules applies globally to all transactions using document type "RE".
  • Other tiles/posting transactions (for example, Create Inbound Invoices for STO) are also affected.

Environment

  • Product: SAP S/4HANA Cloud Public Edition
  • Fiori UI for Invoice Verification (Public Cloud)

Reproducing the Issue

  1. Configure a validation in Manage Substitution/Validation Rules to make Section Code mandatory for accounting document type "RE".
  2. Post or simulate postings in different apps that use document type "RE" (for example, Create Inbound Invoices for STO).
  3. Create a supplier invoice using "Create Supplier Invoice - Advance" and observe that the validation is enforced globally, not limited to this app.

Cause

There is no standard key-user configuration to make Section Code mandatory specifically for the Create Supplier Invoice - Advanced app, and the validation framework does not support using "Fiori App ID" as a condition.

Resolution

  1. Post one test invoice via MIRO (Create Supplier Invoice - Advanced) in a test/quality system.
  2. Post one test STO inbound invoice via J_1IG_INV in the same system.
  3. Open Manage Journal Entries (F1053) and locate both posted documents in ACDOCA.
  4. Compare the Business Transaction Type field (JrnlEntryBusinessTransType) between the two documents.
  5. If the values differ, edit your existing validation rule and add a second condition JrnlEntryBusinessTransType = [value observed for MIRO]. This restricts the mandatory Section Code check to MIRO-originating invoices only.
  6. If the values are the same, note that achieving app-specific validation will require a custom developer enhancement, as the key-user validation does not support "Fiori App ID" as a condition.

See Also

Keywords

section code, create supplier invoice advanced, miro, document type re, validation rules, substitution and validation, jrnlentrybusinesstranstype, business transaction type, acdoca, manage journal entries f1053, sto inbound invoice, j_1ig_inv, fiori app-specific validation, invoice verification, mandatory field configuration , KBA , MM-FIO-IV-2CL , Fiori UI for Invoice Verification (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions