SAP ABAP IMG Activity /SPE/CD_BASIC_CONFIG (Basic Settings for Transportation Cross-Docking)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ LO-SPM-X (Application Component) Cross-Application Topics
     ⤷ /SPE/CROSS_DOCKING (Package) Service Parts Management: Transportation Cross-Docking
IMG Activity
ID /SPE/CD_BASIC_CONFIG Basic Settings for Transportation Cross-Docking  
Transaction Code /SPE/52000794   (empty) 
Created on 20050331    
Customizing Attributes /SPE/CD_BASIC_CONFIG   Basic Settings for Transportation Cross-Docking 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /SPE/CD_BASIC_CONFIG    

Use

The following sections provide an overview of the Customizing activities needed for transportation cross-docking (CD).

Requirements

You can use transportation cross-docking only if you have activated Service Parts Management.

Activities

General Settings

To activate transportation cross-docking, you must carry out the following general activities:

  1. Define the organizational structure for the cross-docking warehouses along the planned route of the outbound delivery to the recipient or inbound delivery to the receiving plant.
    1. Define plants for cross-docking warehouses.
      Every cross-docking warehouse must be represented by a plant in ERP. You define plants as organizational units under the Logistics General menu option Define Plants.
    2. Define storage locations for CD stock within the supplying plants.
      The stocks that are forwarded through cross-docking warehouses remain assigned to the supplying plant until goods issue in the final cross-docking warehouse. Goods receipt into a cross-docking warehouse is reflected in the storage location for CD stock; this storage location is assigned to the supplying plant. You define storage locations as organizational units of Material Management in menu option Define Storage Locations.
    3. Define MRP areas for the supplying plant and the storage locations for CD stock.
      The purpose of these MRP areas is to exclude the inventory postings into the storage locations for CD stock from material requirements planning. You define MRP areas in menu option Define MRP Areas.
    4. Assign supplying plants and storage locations for CD stock to warehouse numbers.
      The cross-docking warehouses managed by the EWM system are addressed by warehouse numbers. You configure warehouse numbers as organizational units of Logistics Execution in menu options Define Warehouse Number and Assign Warehouse Number to Plant/Storage Location. Also perform the activities in "Integrate SPM with Other Components."
    5. Define shipping points and assign them to the supplying plant.
      The shipping points assigned to the cross-docking warehouses need to be defined and assigned to the supplying plant. You define shipping points as organizational units of Logistics Execution in menu option Define Shipping Points. You make the assignment between shipping points and plants in menu option Assign Shipping Point to Plant.
    6. Maintain the relationship between cross-docking plants, storage location for CD stock and shipping points in menu option Maintain Storage Locations and Shipping Points for CD Warehouses
    7. Maintain the relationship between the supplying storage location and the source plant of the process if transportation cross-docking starts at a contract packager warehouse in menu option Define Source Plants for Contract Packagers.
  2. Assign customers and vendors to the plants that represent the cross-docking warehouses.
    Source and target warehouses are stored as partners in the delivery, therefore you must configure a unique assignment between cross-docking plants and customers and vendors. You can assign a customer to the plant definition in menu option Define Shipping Data for Plants. You assign a vendor to the plant in the vendor master maintenance transaction.

Transportation Cross-Docking for Sales Orders and Stock Transfer Orders

If outbound deliveries created from CRM sales orders or from stock transfer orders are to be shipped through cross-docking warehouses before being shipped to the customer or the receiving warehouse, you must carry out the following activities in addition to the steps described above:

  1. Define delivery types and item categories for the cross-docking inbound deliveries that model the goods receipt into a cross-docking warehouse.
    You define delivery types in menu option Define Delivery Types, and item categories in menu option Define Item Categories for Deliveries. Delivery item categories must correspond to sales order item categories and you must also maintain copy control (menu option Specify Copy Control for Deliveries).
  2. Maintain a partner procedure for inbound deliveries that contains the roles EC (receiving cross-docking partner) and SC (supplying cross-docking partner) and assign it to the delivery type used for the cross-docking inbound delivery. Similarly, add the role EC to the partner procedure used for the outbound deliveries.
    You can maintain partner procedures for deliveries in menu option Set Up Partner Determination for Deliveries
  3. Maintain a time segment procedure that contains the event WS CD RECEIPT (Arrival at next Cross-Docking Warehouse) and assign it to the delivery type used for the outbound deliveries shipped to cross-docking plants. You do this in menu option Create Event Groups.
  4. Maintain movement types for the stock transfers between the warehouses along the transportation cross-docking chain with menu option Copy, Change Movement Types. Function code 'CROSS_DOCK_OUT' is used to determine the movement type for posting the goods to stock-in-transfer to a Cross-Docking Warehouse. Function code 'CROSS_DOCK_IN' is used for receiving goods from stock-in-transfer into a Cross Docking Warehouse. Standard movement types 313 and 315 are configured accordingly.
  5. Check the delivery category which is used for the movement type of the cross-docking inbound delivery and maintain the inbound delivery type determination for cross-docking inbound deliveries. You define the delivery category dependent on the movement type in menu option Set QM Check and Delivery Type for Each Movement Type. The inbound delivery types determination can be maintained in menu option Delivery Type Determination. Choose activity Set delivery type determination for inbound delivery and create a suitable entry for the used delivery category. SAP recommends using delivery type DIG or a copy of it for the transportation cross-docking process.
  6. Implement the Business Add-In (BAdI) for determination of receiving cross-docking warehouses, if needed. You do this in menu option BAdI: Determination of Receiving Cross-Docking Warehouse
  7. Maintain the output control to enable the processing of messages of type CDOD, which creates the cross-docking inbound and outbound delivery, in menu option Maintain Output Determination for Outbound Deliveries.
    Message type CDOD must be part of an output determination procedure with requirement routine 499.

Supplier Cross-Docking

Supplier cross-docking allows you to integrate a cross-docking warehouse into the inbound delivery process from the supplier to the destination warehouse. It is assumed that information about the cross-docking warehouse to which the goods from the supplier are to be shipped is provided by customer-specific enhancements in the ASN IDoc submitted by the supplier.

In addition to the activities mentioned for transportation cross-docking of outbound deliveries, you must also carry out the following activities in order to activate this functionality:

  1. Define the organizational structure for the cross-docking warehouses along the planned route of the inbound delivery to the destination warehouse, as described above. You must assign the storage locations for CD stock to the receiving plant of the inbound delivery.
  2. Enhance the ASN IDoc from the supplier with the information about the cross-docking warehouse to which the goods should be shipped first.
  3. Implement Business Add-Ins to transfer the information about the cross-docking warehouse to delivery processing
    1. Implement methods PARSING_IDOC and GN_DELIVERY_CREATE of BAdI /SPE/INB_ID_HANDLING in order to retrieve the information about the receiving cross-docking warehouse from the IDoc and to transfer this information to delivery processing. You implement this BAdI in menu option BAdI: Extensions for ID Handling
    2. As an alternative to the three steps mentioned previously, you can implement method PROPOSE_CD_PLANT of BAdI /SPE/BADI_DETERMINE_CD_PLANT to determine the receiving cross-docking information internally. You do this in menu option BAdI: Determination of Receiving Cross-Docking Warehouse
    3. Implement method FILL_OUTBOUND_DELIVERY of BAdI /SPE/CD_FILL_OUTBOUND_DELIVERY to determine essential data needed for creating the cross-docking outbound delivery. You do this in menu option BAdI: Enhance CD Outbound Delivery with Additional Data
  4. Define delivery types and item categories for the cross-docking outbound delivery as described above.
  5. Maintain the output control to enable processing of mess
Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 1   Mandatory 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 /SPE/CD_BASIC_CONFIG 0 AC00000096 Cross-Application Topics 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20050401 
SAP Release Created in 600