1 / 18

Franz Birsel

Structures – Master Data. Franz Birsel. Agenda. Organisation Units – Enterprise Structure Structure of Sales Organisation Structure of Purchasing Organisation Master Data Material Master Customer Master Vendor Master . Client. The client is the highest entity of a SAP-System

apria
Download Presentation

Franz Birsel

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Structures – Master Data Franz Birsel

  2. Agenda • Organisation Units – Enterprise Structure • Structure of Sales Organisation • Structure of Purchasing Organisation • Master Data • Material Master • Customer Master • Vendor Master

  3. 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. 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. 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. 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. Example of anenterprise structure Ó SAP AG

  8. 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. Enterprise structure of a Purchasing Organisation Ó SAP AG

  10. 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. Enterprise structure of a Sales Organisation Ó SAP AG

  12. 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. 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. Type of MaterialViews 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. 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. 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. 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. Questions ???

More Related