SAP Knowledge Base Article - Public

3773298 - Scheduling agreement items cannot be combined into a single inbound delivery due to different supplier address numbers (ADRNR) - SAP S/4HANA Cloud Public Edition

Symptom

  • When creating an inbound delivery with reference to multiple scheduling agreements for the same supplier, the system selects only one agreement/item and creates separate inbound deliveries instead of one combined document.
  • Combining items from multiple scheduling agreements is not possible if supplier address data differs.
  • In some cases, when attempting to select data, the message "No data satisfying selection criteria exists." can appear.

Environment

 SAP S/4HANA Cloud Public Edition

Reproducing the Issue

  1. Create or use multiple scheduling agreements for the same supplier where the supplier address data is not identical (for example, different email maintained in the address causing different ADRNR values).
  2. Start inbound delivery creation (for example, using Create Inbound Delivery/VL31N) and select the supplier intending to combine multiple agreements/items.
  3. Observe that only one scheduling agreement/item is proposed and separate inbound deliveries are created instead of one combined inbound delivery.

Cause

  • The supplier address number (ADRNR) differs between the scheduling agreements. Address number is split-relevant for inbound delivery; differing ADRNR values cause delivery split by standard design.
  • A custom implementation in BAdI YY1_DELIVERY_ITEM can filter or limit items, preventing multiple scheduling agreement items from appearing during inbound delivery creation.

Resolution

  1. Ensure supplier address data is consistent across all relevant scheduling agreements so that the same address number (ADRNR) is reused. Avoid changing address details (for example, email) that would create a new ADRNR.
  2. Where multiple ADRNR values already exist, align supplier address usage across the affected agreements (for example, reuse the same address entry) or recreate the agreements with a consistent supplier address so they share the same ADRNR.
  3. Review any custom logic in BAdI YY1_DELIVERY_ITEM. Temporarily disable or adjust the implementation to ensure it does not filter out items needed for consolidation.
  4. Recreate the inbound delivery with reference to the multiple scheduling agreements. The system will combine items only when split-relevant fields, including ADRNR, are identical.

Keywords

inbound delivery, delivery split, scheduling agreement, adrnr, address number, supplier address, combine items, consolidate delivery, vl31n, split criteria, address change, email change, public cloud, badi, yy1_delivery_item , KBA , MM-PUR-OA-SCH-2CL , Scheduling Agreement (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions