SAP ABAP IMG Activity OALE_DSTSCN_SOP (Sales and Operations Planning)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ MCP2 (Package) R/3 application development: Sales & Operations Planning
IMG Activity
ID OALE_DSTSCN_SOP Sales and Operations Planning  
Transaction Code S_ALR_87008593   IMG Activity: OALE_DSTSCN_SOP 
Created on 19990115    
Customizing Attributes OALE_DSTSCN_SOP   Sales and Operations Planning 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OALE_DSTSCN_SOP    

This IMG section describes the settings which must be defined for distribution of Sales and Operations Planning data.

Requirements

  • The information structures of SOP must have been created.
  • The message types in SOP must have been defined for the information structures.

Activities

To make settings in SOP, from the IMG initial screen, choose Production -> Sales and Operations Planning -> Functions -> Generate message type.

Here is the procedure (listed as main points):

  • In the Implementation Guide of the application in question, specify the information structure in which planning is to occur. A example information structure, S096, is provided with the standard SAP System.
  • Please remember in this case that simultaneous planning is implemented in several systems by using separate planning key figures for each system.
  • The information structure must be exactly the same in each of the distributed systems participating in the scenario.
  • Generate the message type for the information structure. LIPxxx is assigned as the name for the message type (where xxx is the number of the information structure).
  • The message type must be identical in each of the distributed systems participating in SOP.
  • When you generate a planning type ( = maintenance screen, planning table) for the information structure, pay attention to the following:
    • Define the fields which can be maintained in the system in question as input fields;
    • Define the fields which cannot be maintained in the system as entry fields.
    • Example: ZZ_PLANT is the planning type for a remote system, ZZ_CENTER the planning type for a central system.
  • In every system, the filtering of IDoc fields must be set so that only the key figure fields which can be maintained in the respective system are passed on to other planning systems. The key figure fields planned in other systems must be hidden.
  • Filtering occurs via ALE field conversion.
  • The key figure fields which cannot be maintained must be set to "/".
  • To determine the relationships between of IDoc fields and application fields, execute the function Maintain IDoc type in the chapter Enhancements ->IDoc types.
  • Enter the message type and, in the Environment menu, choose the menu option IDoc type/application fields.
  • For distribution, you must define the model, the partner profiles and so on.
  • Customizing in this book should be carried out for the message types LIPxxx.

For this scenario, the following data must be distributed to all participating systems:

Master Data

  • Material master (core data)
  • Product group master (in material master)

Control data

Description    Object

Company code    V_T001

Plant    T001W

Fiscal year variant    T009

Units of measurement    T006*

Language    T002

Sales organization    V_TVKO

Distribution channel    V_TVTW

Division    V_TSPA

Standard tasks

To ensure that work items are generated should an error occur, the following standard task must be assigned to items or to workflow organizational units.

Standard task: ID code    Description

SOPGEN_Error    SOPGEN Inbound error

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 OALE_DSTSCN_SOP 0 HLA0009522 Sales and Operations Planning 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  19990118 
SAP Release Created in