Function SD_DELIVERY_SAVE_VARK is called during the save of the route schedule to create the VARK entries. For example, if the itinerary of the route schedule contains 5 lines, there are 5 corresponding entries stored in database table VARK. Table VARK contains an entry for each individual line of the itinerary. If an itinerary is maintained for the route schedule, the data for this itinerary is stored in table VARK. Function SD_DELIVERY_SAVE_VAWK is called during the save of the route schedule to create the VAWK entries. The number of entries in table VAWK depends on the number of ship-to parties maintained in the route schedule for example, if there are 5 ship-to parties maintained in the route schedule, there will be 5 entries for the route schedule in table VAWK. These values are later passed to the function SD_DELIVERY_SAVE_VALW. During the save of the route schedule, SAPLV51B, FORM AULWE_INSERT (Include LV51BF0A) passes the route schedule values to the internal structure XVALW_UPD. When a route schedule is created, one entry will be created in table VALW for this route schedule. VAWK - Delivery Plan: Itinerary Determination, Customer-Specific VARK - Delivery Plan: Customer-Specific Itineraryģ. VALW - Delivery Plan: Definition of Route ScheduleĢ. The bulk of the data related to route schedules is contained in the following 3 tables:ġ. The route scheduling functionality allows you to plan accurate outbound deliveries to the ship-to parties on a route. It is intended as a debugging aide for any route scheduling problems. The purpose of this page is to give a technical overview in relation to how route scheduling is performed in the ECC system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |