3759966 - Delivery Priority is retrieved from Sold-to Party instead of Ship-to Party in Sales Order item in SAP S/4HANA Cloud Public Edition

When creating a sales order in SAP S/4HANA Cloud Public Edition, the item-level Delivery Priority is not determined from the Ship-to Party.

The Ship-to Party may have a Delivery Priority maintained in the customer sales-area data, but the sales order item either remains blank or receives the value from the Sold-to Party instead.

The business expectation may be that the Ship-to Party should determine the Delivery Priority because it represents the actual delivery destination.

SAP S/4HANA Cloud Public Edition

1. Open the Create Sales Order app (for example, VA01 or the corresponding Fiori app).
2. Enter a Sold-to Party that has no Delivery Priority maintained.
3. Enter a different Ship-to Party that has Delivery Priority maintained.
4. Add at least one item and save the order.
5. Check the Delivery Priority on the sales order item; the field remains blank instead of defaulting from the Ship-to Party.

Backend technical analysis

This is standard sales order item defaulting behavior.

The sales order item Delivery Priority is stored in field:

• VBAP-LPRIO = Delivery Priority on the sales order item

The customer sales-area Delivery Priority is stored in:

• KNVV-LPRIO = Delivery Priority in customer sales-area data

During standard sales order processing, the system fills item data from the Sold-to Party customer structure:

• KUAGV = Sold-to Party customer structure used during sales order processing

In this logic, data is moved from the Sold-to Party structure to the sales order item structure

As Delivery Priority is part of this data, the item field VBAP-LPRIO is proposed from the Sold-to/customer master source.

If a Customer-Material Info Record is relevant, the Delivery Priority can also be determined from:

• KNMT-LPRIO = Delivery Priority in Customer-Material Info Record

Therefore, the standard logic determines Delivery Priority from customer master / customer-material logic. It does not automatically use the separate Ship-to Party customer master data as the source for the sales order item Delivery Priority.

Workarounds

Option 1: Maintain Delivery Priority on the Sold-to Party

Maintain the required Delivery Priority on the Sold-to Party customer sales-area data.

This is only suitable if the same Delivery Priority can apply to the relevant Ship-to locations assigned to the Sold-to Party.

Option 2: Manual entry

Enter the Delivery Priority manually on the sales order item where business process permits.

This is technically possible if the field is available for input, but it is not recommended as a long-term automated process solution.

Option 4: Feature request

If the business requirement is to automatically derive the standard sales order item Delivery Priority from the Ship-to Party, submit a  Customer Influence/ feature request requesting standard support for one of the following:

• A configuration option to choose the source partner for Delivery Priority determination.
• A released Public Cloud enhancement option to set the standard sales order item field Delivery Priority / VBAP-LPRIO during sales order creation.

refer to: Data from Master Records (customer-material data includes Delivery Priority)

refer to: Searching for a Customer Material / Manage Customer Materials

refer to: Community: default Delivery Priority on sales order items from Ship-to

refer to: 3665055 - Ship-to party extension and shipping data (includes Delivery Priority)

Delivery Priority, VBAP-LPRIO, KNVV-LPRIO, KNMT-LPRIO, KUAGV-LPRIO, Sold-to Party, Ship-to Party, Sales Order item, Customer-Material Info Record, CMIR, Customer Material, SAP S/4HANA Cloud Public Edition, Create Sales Order, Manage Sales Orders, VA01, partner determination, delivery priority blank, delivery priority from Sold-to, delivery priority from Ship-to, Sales Document BAdI, custom logic. , KBA , SD-SLS-2CL , Sales (Public Cloud) , Problem