PP

• number, material type and industry sector

• basic data view, classification view (user-defined class assignments), materias planning view (level: plant), scheduling view (level: plant)

• MARA (client), MARC (plants): MRP and forcasting data, MARD (storage location): mainly stock data

• tables:

  • EINA/EINE: Purchasing info record data

  • MAKT: Material descriptions

  • MVKE: Sales data

  • MLGN: Warehouse Management

  • MBEW: material valuation

• Material types:

  • KMAT: Configurable material = can have different variants f.e. a car can haffe different engines (Motoren) or paintwork -> custom.: (x) configurable

  • INTR: Intra materials = exists temporarily between two processing steps -> no sales/PO data

  • FHMI: Production resources/tools = procured externally and used in production/plant maintenance -> can contain PO data but no sales data, is managed on quantity basis

• Material type determines:

  • Which screens appear and in which order

  • Which industry-specific data appears

  • Which branch of industry the material is assigned to

• Material number: defined on client level, internal = system gives number, internal number: 18 digits, external: possible to have 40 digits

• Basi UOM (Basic Data 1), order unit, sales unit, production unit (=unit in which goods reciept is created), unit of issue (work scheduling and warehouse management 1 -> unit for issuing material from stock, can be used for BOM item quantity)

Creating an article:

• MRP profile -> set default values for MRP data fields and defines: can values be changed?

• by defaut value OR copying a product

Assigning documents:

• documents can have any format, customzing entries control the display and change process of attached files

• in Basic data 1 -> Additional Data -> Document Data: select document type (f.e. Design Drawing), define Document (name?), part and version

• if a version is released, it can not be changed -> a new version needs to be created (released = depending on status --> status depends on status network which depends on document type)

Purpose: add fields to material master for information/information about existing inventory without modifying delivered SAP tables

• C can be used to describe or group objects(objects = classifiable unit f.e. material, vendor, work center). A Characteristic describes specifications of an object f.e. color, weight,…

• Characteristics: which values can be “maintained” fe. class: color, characteristic = blue, red

• How to set up:

  1. Define characteristics and the allowed characteristic values (f.e. characteristic = type of drive, values = diesel and electronic).

  2. Maintain the class (specify class type: for materal: 001 material class, 023 batch, 200 Material (configurable objects), 300 Variant materials)

  3. Assign characteristics to class type

  4. Maintain the objects (for example, materials), including assigning them to one or more classes and assigning values to them.

• object dependencies = rules that define which components are compatible with others = done for caracteristics and caracteristic values

• settings in material master, create configuration profile by specifying the configuration parameters and allocating the material to the class with the characteristics that describe it (The components and operations for a material are specified in super bills of material (BOM) and a super task list), Maintain object dependencies for the BOM components and task list operations that can only be selected for particular variants -> products with variants often have dependencies between the individual characteristics in witch all combinations of characteristics are not allowed

• create a material, assign a class -> all characteristics are shown: maintain values

• which view is created f.e. status A = work scheduling, B = Accounting

• MMCC = material master copier

  • can (unter anderem) simulate copy process, create more than one material

  • constrains (Einschränkungen): integrated material master data is not copied (classification data, documents, configuration data, MRP area data (but MRP data is copied), quality management inspection types, sales conditions, bills of material, routings, and production versions

  • custom:

    • settings from custom are used or whether the organizational units are to be proposed 1:1 from the reference material

    • specify (on user-specific basis or user = DEFAULT) from which source organizational unit to which target organizational unit the data is to be copied (for example, from plant 0001 to plant 0005)

•