SAP ABAP IMG Activity /SPE/OUTB_BASIC_SETE (Basic Settings for Outbound Processing)
Hierarchy
SAP_APPL (Software Component) Logistics and Accounting
   LE-IEW (Application Component) Extended Warehouse Management Integration
     /SPE/IMG_IEW (Package) IMG Activities Related to ERP-EWM Integration
IMG Activity
ID /SPE/OUTB_BASIC_SETE Basic Settings for Outbound Processing  
Transaction Code /SPE/23000699   (empty) 
Created on 20060830    
Customizing Attributes /SPE/OUTB_BASIC_SETE   Basic Settings for Outbound Processing 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /SPE/OUTB_BASIC_SETE    

Use

The following provides an overview of the Customizing activities needed for outbound processing.

Standard settings

There are no standard settings for outbound processing in Extended Warehouse Management Integration.

Activities

General Settings

To use outbound processes in ERP you must generate and activate integration models for the integration of EWM. These integration models have to include the material masters and the plants.

In the activity Assign warehouse number to plant/storage location you must ensure that a warehouse number is assigned to all combinations of plants and storage locations. In the activity Maintain Extended WM-Specific Parameters, you must define EWM as the allocated external warehouse management system for each warehouse number, in order to have queued and serialized communication and the immediate distribution of deliveries. In addition, you must create a distribution model for the distribution of outbound deliveries from ERP to EWM in the activityGenerate Distribution Model ERP => EWM.

Settings in Outbound Delivery Customizing

In the activity Define Delivery Types, you must activate the delivery split by warehouse number for the used delivery types, to enable the distribution of outbound deliveries to EWM.

Settings for Kit to Order

In the Kit-to-Order process, you must define the item categories, schedule line types and requirement classes for the kit headers, kit components and substituted kit components as follows:

  1. Kit Header

    There are two methods of processing for the kit header:

    1. Goods movements for kit header
    2. In the activity Set Goods Receipt Movement Type for Kit Headers, you must define the goods receipt movement type for the item category of the kit header, in order to have a goods receipt and a goods issue posting for the kit header. In the activity Define Schedule Line Categories, you must also define a goods issue movement type for the assigned schedule line category. The goods movement postings for the kit header are mandatory in transportation cross docking and for billing the kit header.
    3. No goods movements for kit header
    4. If no goods movement postings are required for the kit header, you are only required not to maintain the goods issue movement type in the assigned schedule line category in the activity Define Schedule Line Categories.

      You must deactivate the availability check for the kit header in the item category in the activity Define Item Categories for Deliveries or in the requirement class. In addition, you must switch off the transfer of requirements in the requirement class in the activity Define Requirements Classes.

  2. Kit Component

    The settings for kit components are very similar to normal delivery items. However, you must ensure that the billing relevancy is not set for both the kit header and the kit components at the same time.

You can use KITH as the item category for the kit header and COMP for the kit components. The item category KITH is configured for posting goods movements for the kit header.

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/OUTB_BASIC_SETE 0 PR00000022 Outbound Process 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20061221 
SAP Release Created in 700