Solution : https://service.sap.com/sap/support/notes/204899 (SAP Service marketplace login required)
Summary :
In SAP collective processing for delivery generations, the goods recipient's name may not appear on index list type = 1 despite the relevant flag setting (T186-EXTENDED_SHIP_TO = 'X'). This issue arises because these functions were initially implemented only for item/schedule line lists. The solution includes setting the 'with ship-to party' flag to 'X', and modifying the ABAP Dictionary structures SHP_VL10_INDX and SHP_VL10_ITEM by adding a NAME1 field. Additionally, copying NAME1 to the delivery due list and managing potential delays in field catalog updates are essential steps. Field buffering can be deactivated for immediate changes using report BALVBUFDEL.
Key words :
transaction se11data type shp_vl10_itemchangeposition cursor, 'expand' componentinsert function line, user role/list profile, list profile/user role, item/schedule line list, terms vl10a/vl10b reason, delivery due list, component type name1activate, t186-extended_ship_to = 'x', data element name1
Related Notes :
| 489327 | VL10: missing user exit for document list of purchase orders |
| 421791 | VL10: Including new fields in the shipping due date list |
| 308119 | VL10: User field added to index list |
| 302966 | VL10: Address data in index list not in user exits |
| 198137 | VL10: Customer-specific enhancements / user exits |
| 113411 | Collective note: VL10 |