Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 SAP Logistic Chair or Production & Operations Management University of Vienna All for One Vienna, Austria Franz Birsel Structures – Master Data.

Similar presentations


Presentation on theme: "1 SAP Logistic Chair or Production & Operations Management University of Vienna All for One Vienna, Austria Franz Birsel Structures – Master Data."— Presentation transcript:

1 1 SAP Logistic Chair or Production & Operations Management University of Vienna All for One Vienna, Austria Franz Birsel Structures – Master Data

2 2 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Agenda  Organisation Units – Enterprise Structure  Structure of Sales Organisation  Structure of Purchasing Organisation  Master Data  Material Master  Customer Master  Vendor Master

3 3 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Client  The client is the highest entity of a SAP-System  The client is in commercial, organizational, and technical terms, a self-contained unit in an R/3 System with separate master records and its own set of tables.  General material data applicable to the entire company is stored at client level.

4 4 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Company Code  The company code is a self-balancing unit inside a client  A client can include several company codes.  A client can e.g. be a organisation within a company or a subsidiary.  Accounting data and valuation data will be stored on company code level.

5 5 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Plant  A plant is an organisational unit to subdivide an enterprise according to production, procurement, maintenance, and materials planning aspects.  A plant is a place where either materials are produced or goods and services provided.  To this data, which are storded on plant level, there are also MRP-Data, Work Plans and und BOM‘s.

6 6 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Storage Location  Every storage location belongs to one plant.  A storage location allowing the differentiation of material stocks within a plant.  Physical inventory takes place at storage location level.  A storage area that can be defined for a warehouse in the Warehouse Management (WM) system and can be subdivided in:  Storage Number  Storage Type  Storage Place

7 7 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Example of an enterprise structure  SAP AG

8 8 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Purchasing Organisation  The purchasing organisation is responsible for the provision of materials and services.  The purchasing organisation negotiates with the provider purchasing conditions and is responsible for all purchasing activities verhandelt  The following types of purchasing organisations are possible:  There is only one single purchasing organisation responsible for the whole enterprise.  Each entry range has its own purchasing organisation.  Each factory has its own purchasing organisation.

9 9 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Enterprise structure of a Purchasing Organisation  SAP AG

10 10 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Sales Organisation  The sales organisation divides an enterprise in the demand of the sales.  The sales organisation is responsible for the sales of materials and services.  The sales organisation is divided in distribution channels and divisions.  Each sales organisation has its own entry range.  One sales organisation can be attached to different factories.

11 11 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Enterprise structure of a Sales Organisation  SAP AG

12 12 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Organisation structure for the course  Client: 100  Entry range: 1000  Factory : 0050  Storages:UFER  Finished products UHAL  Unfinished goods UROH  Raw material  Purchasing organisation:0050  Sales organisation:0050  Distribution channel:10  Division:00

13 13 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Master Data  Material data The material data contains all necessary information for the administration of the materials.  Customer- or Debitor data Here all data are filed which are necessary for the business relations to the customer.  Vendor- or Creditor data Here all data are filed which are necessary for the business relations to the vendor.

14 14 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Type of Material Views in The Material Data  Type of Material Each material must be allocated to a type of material at creation. The type of material defines certain characters of the material and it has important control functions.  Views With the selection and creation of views the usage of the material is defined. The views are in direct connection to the organisational structures.

15 15 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Transactions for The Material Data  Create Material Data  Transactionscode:MM01  Change Material Data  Transactionscode:MM02  Display Material Data  Transactionscode:MM03 For the initiation of the material data we use the following rules : Material number = ssss+nn+xxxxx ssss = Semester description nn= Number of the User xxxxx= free chosen text e.g.: „ss0701testmat“ The Material number must have max. 18-digits.

16 16 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Customer Data  Create Customer Data  Transactionscode:XD01  Change Customer Data  Transactionscode:XD02  Display Customer Data  Transactionscode:XD03 For the work in the course we use the customer „UNI-DEB“ in the examples. Further customer data can be created as you want.

17 17 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Vendor Data  Create Vendor Data  Transactionscode:XK01  Change Vendor Data  Transactionscode:XK02  Display Vendor Data  Transactionscode:XK03 For the work in the course we use the customer „UNI-KRED“ in the examples. Further vendor data can be created as you want.

18 18 Chair of Production & Operations Management University of Vienna All for One Vienna, Austria Questions ???


Download ppt "1 SAP Logistic Chair or Production & Operations Management University of Vienna All for One Vienna, Austria Franz Birsel Structures – Master Data."

Similar presentations


Ads by Google