SAP ABAP IMG Activity SIMG_CFMENUOLSDOVDSP (Subsequent Delivery Split)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ VL (Package) WS-SHP: General Processing for Shipping
IMG Activity
ID SIMG_CFMENUOLSDOVDSP Subsequent Delivery Split  
Transaction Code S_ALR_87009595   (empty) 
Created on 19990308    
Customizing Attributes SIMG_CFMENUOLSDOVDSP   Subsequent delivery split 
Customizing Activity SIMG_CFMENUOLSDOVDSP   Subsequent delivery split 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUOLSDOVDSP    

Example

When you load a delivery at the loading ramp, the system recognizes that the available loading space is not sufficient for the entire delivery. Shipping documents, goods movement postings and invoices should be created on the basis of the quantity that was actually loaded. Using the subsequent delivery split function, you can divide up existing deliveries into various other deliveries.

Damage caused to data by errors

Check if local adjustments to the system (add-ons, user exits, own data, modification solutions) respond correctly to the delivery split:

The delivery split uses the document update of delivery processing and calls up the USEREXIT_SAVE_DOCUMENT and SAVE_DOCUMENT_PREPARE user exits in MV50AFZ1 (SAVE_DOCUMENT for delivery processing). It may also be the case that your own messages or statistical updates cannot process the new situation correctly. During a subsequent delivery split, the system simultaneously generates and changes deliveries during in one posting. There is no collective processing indicator and none of the traditional transaction types (T180-TRTYP) is set.

User-specific data is copied from the LIKP and LIPS tables. If the data is dependent on quantity or if the document numbers are not used in your own data, you have to update the data yourself.

Definition

Split result and split complement

If you call up the split, the system displays the quantities or handling units of one or more deliveries. After the split, these quantities make up the split result and the rest is called the split complement. You can enter several split result numbers (sequence numbers ) when calling up the split. Therefore, you can split a delivery into several split results. However, there is only one split complement per delivery. As a rule, the quantities of the split result after the split are processed differently from the quantities of the complement. Split Customizing accounts for this since some settings for the split result and the complement can be carried out separately.

A split result does not necessarily have to have a new document number. When carrying out the split, you can specify whether the original document number is to be changed to a sequence result number, and if so, you can specify the number.

Requirements

  1. Deliveries may NOT:
    1. Have goods movement posted or be billed
    2. Be inbound deliveries
  2. Items must:
    1. Not have serial numbers assigned
    2. Not be an inspection lot (QM)
    3. Retain a quantity after the split that is at least as large as the quantity of potentially unassigned transfer orders (WMS) that are n o t confirmed.
  3. If the items are packed, the packed quantity after the split must not be less than the packed quantity before the split. (In general, you have to call up the split by entering the shipping units).
  4. If the delivery is in a shipment, the following restrictions apply:
    1. If the delivery has already been transfered to an external transportation planning system, the delivery that was split cannot be included in the shipment nor can the original delivery be eliminated from the shipment. Both situations can be adapted for the split in Customizing.
    2. If both parts in the above example are also packed in handling units belonging to the shipment, it is not possible to split the delivery. The shipping units have to remain in the shipment and the new delivery cannot be included in the shipment.
    3. A similar example: both parts were packed in the shipment without an external transportation planning system. The split cannot take a delivery out of the shipment, but the split itself it is still possible (controllable error message).
    4. Deliveries in a finished shipment cannot be changed and therefore cannot be split.
  5. Special functions for delivery quantities packed in the shipment:
    1. Handling units with planning characteristics:
      Packed quantities can only be split when you enter a highest-level handling unit. In particular cases, you might want to be able to enter handling units or delivery quantities that are only visible on lower packaging hierarchy levels. For example, you may have already planned the assignment of delivery quantities to a truck. During loading, however, the boxes are to be scanned and split, if necessary. If this special function is not active, the system would only interpret the truck as the highest-level shipping unit and you would not be able to call up the split by entering the boxes. Split Customizing allows you interpret shipping units as planning units only. They will then be hidden. However, the above rules regarding the assignment of split result and complement to the shipment still apply if their quantities are packed in shipment. Note that the split is not unpacked. The packed quantity is simply re-distributed among the deliveries that were split.
      If 30 tons were packed in the truck and 29.5 tons is split, the split result contains the 29.5 tons that are packed in the truck. The split complement contains the 0.5 tons that are also still packed in the truck. If the packed quantity is smaller than the quantity of an original item, the packing quantity is first distributed to the split results (starting with the highest number) and then to the split complement.
    2. Packed quantities in transportation chains:
      If a delivery is in various shipments and if an item quantity is packed in these shipments, the split separately reassigns the packing quantities of the individual shipments during the distribution of packing quantities. In other words, the split supports multiple packing in transportation chains. As the split quantity entry, you may use only highest-level shipping units from the same shipment. If an item weighs 30 tons and if you can fit a maximum of 25 tons in a truck and a maximum of 27 tons on a ship (the truck plus 2 tons), you may only enter a maximum of 3 tons (smallest quantity of all the shipments that was not packed) without entering shipping units (as quantity not packed). You can deactivate the checks and calculations of this special function in Customizing.
  6. Groups of deliveries:
    1. The reassignment of deliveries within groups of deliveries formed in SD is supported and can be customized. Wave picks (group type "W") are the exeption to this rule. They are subject to the restrictions of WMS groups: deliveries may not be removed from wave picks by splitting.
    2. Split result (and the split complement, if you set it as such) are assigned to one or two new groups of deliveries. If no group type has been maintained for the main delivery, a group with group type 'D' is created. The error log of the split is recorded in split result's group.
    3. WMS groups: If there are deliveries in WMS groups (collective processing SO creation, two-step picking, ...) the new assignments (which can also be customized) cannot be carried out if processing steps have already been carried out for the group in WMS. In contrast to ordinary delivery groups, deliveries cannot be eliminated from WMS groups during the split.
  7. Groups of items: Delivery groups / Bills of Material (BOMs)
    1. According to your settings, changed or generated items with zero quantities from BOMs or delivery groups can be deleted.
    2. If the BOM still has its target correlation, some cases where items are automatically correlated, can be customized.
    3. Another control is planned for text items in groups of items.
    4. A generalization of this topic is a split of handling units if the delivery contains items that are not packed or that cannot be packed. If necessary, you can use the USEREXIT_INSERT_QSET user exit here in connection with USER_CREATE_OBJECTS_FROM_LIPS, which are both in LV53SFZ1.
  8. Prices:
    1. The quantity-dependent copying of conditions in the new delivery has the same control options as when you copy conditions from order to order.
  9. Delivery split in a decentralized WM system.

Deliveries were created in an ERP system and distributed to a WM system, where they are split.

  1. Outbound deliveries may not be packed directly in the ERP system, not even as a packing proposal. They may only be packed in the decentralized WM system, where they may also be packed as split deliveries.
  2. The following settings are switched off in the split profile, even if you have switched them on here already.
    3. - Reassign item numbers in a new delivery
    - Delete normal items with quantity 0
    - Do not split delivery groups
    - Do not delete items from delivery groups if
    quantity 0
    - Check no. of partial deliveries in delivery
    split

  1. Delivery split when confirming split outbound deliveries in the ERP system

    Split outbound delive

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_CFMENUOLSDOVDSP 0 HLA0006571 Delivery Processing 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
V_DSP C - View cluster OVDSP 00000001  
History
Last changed by/on SAP  19990308 
SAP Release Created in