Skip to main content

Introduction to Sales and Distribution Enterprise Structure

Organisation structure of a company is termed as Enterprise Structure in SAP.

This represents the skeleton of an organisation. Each functional department  of a company is represented by an individual organisational element or Unit in SAP.

Enterprise structure need to be designed from reporting perspective and this would be basis for the creation of the master data.

SAP recommends to keep organisational structure as lean as possible and this will have an impact during master data maintenance.

Enterprise structure is divided into two parts :

1. Definition

2. Assignment 

Individual Org. elements will be created stand alone in the definition

Relationship between independent Org. elements will be done in Assignment process.

Below is the mapping of Organisational structure to that of SAP

Functional Terminology                                    SAP Terminology

Group of Companies  -------------------- ----------->  Company

Each Industry Vertical or Business Unit ----------- > Company Code

Sales Department of an Corporate office------------> Sales Organisation

Product or Services distribution medium  ----------> Distribution Channel

Product Range  ------------------------------------------> Division

Subsidary of a company from where sales activities
takes place for a specific geographical location ----> Sales Office

Sales teams of a company  ------------------------- ---> Sales Group

Manufacturing facility or Depo ( Go Down)---- - ---> Plant

Ramps of a Depo from where loading activities -----> Shipping Point
Takes place

In the above Structure :

FI consultant will be responsible for creation and maintenance of the Company and company code of an enterprise structure.

MM or PP consultant will be responsible for the creation and maintenance of the Plant.

SD consultant will be responsible for rest of the Org. Units





Comments

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...