Скачать презентацию SAP TERP 10 Preparation Presentation 4 Dr Gábor Скачать презентацию SAP TERP 10 Preparation Presentation 4 Dr Gábor

0ef1c863c70b8842ffbbdb0143b4344a.ppt

  • Количество слайдов: 18

SAP TERP 10 Preparation Presentation 4 Dr. Gábor Pauler, Associate Professor, Private Entrepeneur Tax SAP TERP 10 Preparation Presentation 4 Dr. Gábor Pauler, Associate Professor, Private Entrepeneur Tax Reg. No. : 63673852 -3 -22 Bank account: 50400113 -11065546 Location: 1 st Széchenyi str. 7666 Pogány, Hungary Tel: +36 -309 -015 -488 E-mail: [email protected] hu

Content of the presentation 3. Material Planning Scenario 3. 1. Organizational background 3. 2. Content of the presentation 3. Material Planning Scenario 3. 1. Organizational background 3. 2. Plot/Preconditions of Scenario 3. 3. Creating/Modifying master data 3. 3. 1. Material master: 3. 3. 1. 1. Modify Giga. Bike-Name: MM 02 3. 3. 1. 2. Create Mini. Bike-Name: MMF 1 3. 3. 1. 3. Practice: Create Base. Bike 2 -Name: MMB 1 3. 3. 1. 4. Practice: Create Alu. Frame-Name: MMR 1 3. 3. 2. Bill Of Material (BOM) 3. 3. 2. 1. BOM Theory Miracle Roof Example BOM as Matrix BOM as Non-fixed level hierarchy BOM as Network BOM as Set of Alternative Networks 3. 3. 2. 2. BOM In SAP 3. 3. 2. 2. 1. Header content 3. 3. 2. 2. 1. Item content Item types 3. 3. 2. 2. 3. Alternative item lists References Object Symbols GUI Symbols

3. Material Planning: 3. 3. Modifying master: 3. 3. 1. 1. Modify Giga. Bike-Name 3. Material Planning: 3. 3. Modifying master: 3. 3. 1. 1. Modify Giga. Bike-Name k Clicick l C PP MM k k Cl ic Name Cl ic Step 3. 3. 1. Material master data creation 3. 1. Organizational background Same as Procurement scenario But Production Planning(PP) is in focus: this will be more realistic, but more difficult: in a big company, usually materials are never ordered manually as it happened in procurement scenario! 3. 2. Plot/Preconditions of Scenario A lighter version of Giga. Bike-Name is defined in Company 1000 Plant 1000 Storage 0110 called Mini. Bike-Name It has 1 pc of Base. Bike 2 -Name Which has 1 pc of Alu. Frame-Name Everything will be assembled by work center XYCsava 3. 3. Creating/Modifying master data 3. 3. 1. Material master: MM 01 Some of the important views are maintained solely by PP, but others are in shared processing MM 02: Some views are general for company, others are plant- Modify related finished There are several specialized versions of MM 01 to create material Giga. Bike- certain types of material (eg. FERT, HALB, ROH) with Name preset of the settings below MMF 1: 3. 3. 1. 1. Modify Giga. Bike-Name: MM 02 Create LO|MM|Material master|Material|Change|MM 02 finished Immediately| material Mini. Bike 3. 3. 1. 1. 1. SCR: Start Name DDN: Material = Giga. Bike-Name MMB 1: 3. 3. 1. 1. 2. SCR: Main Create BTN: Organization levels semi finished DDN: Plant = 1000 material DDN: Storage = 0110 Base. BTN: Select views: Bike 2 - Click l Ckick lic C Click

3. Material Planning: 3. 3. Modifying master: 3. 3. 1. 1. Modify Giga. Bike-Name 3. Material Planning: 3. 3. Modifying master: 3. 3. 1. 1. Modify Giga. Bike-Name Cli ck Click Click PP MM Step 3. 3. 1. Material master data creation MM 02: Modify finished material Giga. Bike. Name MMF 1: Create finished material Mini. Bike. Name MMB 1: Create semi finished material Base. Bike 2 Name MMR 1: Create raw material Alu. Frame. Name 3. 3. 1. 1. 2. 1. PP|Plant: TAB: MRP 1 DDN: MRP type = PD(MRP planning): the system will use Bill of Material, BOM (Darabjegyzék) to determine the amount and time to order necessary components for this material automatically: Other options are: ALT: = No planning: very seldom, only for very cheap, easy-to-store components (eg. small nails) ALT: = Consumption based: for liquid or gaseous components (eg. glue, lubricants) ALT: = MPS(Master Production Scheduling): planning is made, but only at finished prod, not at component level DDN: Lot size = EX(Exact order quantity): you produce exactly the amount your customer ordered. Other options: ALT: = Week lots: at cheap, easy-to store finished products, you pre-produce without any order by an average weekly requirement 3. 3. 1. 1. 2. 2. PP|Plant: TAB: MRP 2 DDN: Procurement type = E(Own production). Other options are: ALT: = F(External): I cannot produce myself at all ALT: = X(Both): if I do not have capacity, I will buy it TBX: In-house production = 5 days: Only at own production, Does not depend on order ALT: TBX: Planned delivery time = 5 days: Only at external production TBX: Safety stock = 0: If stock goes under this level: Click C li ck Click

3. Material Planning: 3. 3. Modifying master: 3. 3. 1. 2. Create Mini. Bike-Name 3. Material Planning: 3. 3. Modifying master: 3. 3. 1. 2. Create Mini. Bike-Name k Clicck li C Cliick lc Cck k li C Click C lic k Cl ick PP MM Step 3. 3. 1. Material master data creation MM 02: Modify finished material Giga. Bike. Name MMF 1: Create finished material Mini. Bike. Name MMB 1: Create semi finished material Base. Bike 2 Name MMR 1: Create raw material Alu. Frame. Name 3. 3. 1. 2. Create Mini. Bike-Name: MMF 1: We will define a cheaper version of Giga. Bike-Name with alu-frame. We copy most of master data referencing to Giga. Bike-Name LO|MM|Material master|Material|Create(special)| MMF 1 Finished product| 3. 3. 1. 2. 1. SCR: Start DDN: Material = Mini. Bike-Name DDN: Industry = Mechanical engineering DDN: Reference = Giga. Bike-Name Click 3. 3. 1. 2. 2. SCR: Main 3. 3. 1. 2. 2. 1. BTN: Organization DDN: Plant = 1000 DDN: Copy from plant = 1000 DDN: Storage = 0110 DDN: Copy from Storage = 0110 DDN: Sales. Org = 1000 DDN: Copy from Sales. Org = 1000 DDN: Channel = 10 DDN: Copy from Channel = 10 3. 3. 1. 2. 2. 2. BTN: Select views: Basic 1 -2, Sales 1 -2 -G, MRP 1 -4, Work. Sched, Accounting 1 -2, Costing 1 -2 3. 3. 1. 2. 2. 3. MM: TAB: Basic 1: DDN: Description = Mini. Bike-Name 3. 3. 1. 2. 2. 4. SD: TAB: Sales general: TBX: Grossweight = 20 KG Cli TBX: Netweight = 17 KG ck 3. 3. 1. 2. 2. 5. FI: TAB: Accounting 1: TBX: Standard price = 2083 EUR 3. 3. 1. 2. 2. 6. BTN: Additional data DDN: Language = EN Click Click Click ck Cli

3. Material Planning: 3. 3. Modifying master: 3. 3. 1. 3. Create Base. Bike 3. Material Planning: 3. 3. Modifying master: 3. 3. 1. 3. Create Base. Bike 2 -Name PP MM Step 3. 3. 1. Material master data creation MM 02: Modify finished material Giga. Bike. Name MMF 1: Create finished material Mini. Bike. Name MMB 1: Create semi finished material Base. Bike 2 Name MMR 1: Create raw material Alu. Frame. Name 3. 3. 1. 3. Practice: Create Base. Bike 2 -Name: MMB 1 LO|MM|Material master|Material|Create(special)|MMB 1 Semi finished product| 3. 3. 1. SCR: Start DDN: Material = Base. Bike 2 -Name DDN: Industry = Mechanical engineering DDN: Reference = Base. Bike-Name 3. 3. 1. 3. 2. SCR: Main 3. 3. 1. 3. 2. 1. BTN: Organization DDN: Plant = 1000 DDN: Copy from plant = 1000 DDN: Storage = 0110 DDN: Copy from Storage = 0110 3. 3. 1. 3. 2. 2. BTN: Select views: Basic 1 -2, Sales 1 -2 -G, MRP 1 -4, Work. Sched, Accounting 1 -2, Costing 1 -2 3. 3. 1. 3. 2. 3. MM: TAB: Basic 1: DDN: Description = Base. Bike 2 -Name 3. 3. 1. 3. 2. 4. SD: TAB: Sales general: TBX: Grossweight = 15 KG TBX: Netweight = 13 KG 3. 3. 1. 3. 2. 5. FI: TAB: Accounting 1: TBX: Standard price = 1250 EUR 3. 3. 1. 3. 2. 6. BTN: Save

PP MM Step 3. 3. 1. Material master data creation 3. Material Planning: 3. PP MM Step 3. 3. 1. Material master data creation 3. Material Planning: 3. 3. Modifying master: 3. 3. 1. 4. Create Alu. Frame-Name 3. 3. 1. 4. Practice: Create Alu. Frame-Name: MMR 1 LO|MM|Material master|Material|Create(special)|MMR 1 Raw material| 3. 3. 1. 4. 1. SCR: Start MM 02: DDN: Material = Alu. Frame-Name Modify DDN: Industry = Mechanical engineering finished material DDN: Reference = Carb. Frame-Name Giga. Bike. Name 3. 3. 1. 4. 2. SCR: Main MMF 1: 3. 3. 1. 4. 2. 1. BTN: Organization Create DDN: Plant = 1000 finished material DDN: Copy from plant = 1000 Mini. Bike. Name DDN: Storage = 0110 MMB 1: DDN: Copy from Storage = 0110 Create semi 3. 3. 1. 4. 2. 2. BTN: Select views: finished Basic 1 -2, material Base. Purchasing, Bike 2 MRP 1 -4, Name Accounting 1 -2, MMR 1: Create Costing 1 -2 raw material 3. 3. 1. 4. 2. 3. MM: TAB: Basic 1: Alu. DDN: Description = Alu. Frame-Name Frame. Name 3. 3. 1. 4. 2. 4. FI: TAB: Accounting 1: TBX: Moving price = 208 EUR 3. 3. 1. 4. 2. 5. BTN: Save

Content of the presentation 3. Material Planning Scenario 3. 1. Organizational background 3. 2. Content of the presentation 3. Material Planning Scenario 3. 1. Organizational background 3. 2. Plot/Preconditions of Scenario 3. 3. Creating/Modifying master data 3. 3. 1. Material master: 3. 3. 1. 1. Modify Giga. Bike-Name: MM 02 3. 3. 1. 2. Create Mini. Bike-Name: MMF 1 3. 3. 1. 3. Practice: Create Base. Bike 2 -Name: MMB 1 3. 3. 1. 4. Practice: Create Alu. Frame-Name: MMR 1 3. 3. 2. Bill Of Material (BOM) 3. 3. 2. 1. BOM Theory Miracle Roof Example BOM as Matrix BOM as Non-fixed level hierarchy BOM as Network BOM as Set of Alternative Networks 3. 3. 2. 2. BOM In SAP 3. 3. 2. 2. 1. Header content 3. 3. 2. 2. 1. Item content Item types 3. 3. 2. 2. 3. Alternative item lists References Object Symbols GUI Symbols

3. 3. 2. Bill Of Material: 3. 3. 2. 1. Definition: Miracle Roof Example 3. 3. 2. Bill Of Material: 3. 3. 2. 1. Definition: Miracle Roof Example We build roofs with: 2 pcs seat beams 0. 15× 6. 3 m 40 m 2 aluminium foil radiation shield 2 m× 1 mm 49 pcs 0. 9× 0. 05 m hard polyfoam heat insulation 40 m 2 polyethylene water insulation 2 m× 0. 5 mm 1 pcs ridge beam 0. 15× 6. 3 m 16 pcs rafters 0. 15× 5. 4 m 2 pcs fascias 0. 15× 0. 05× 6. 3 m 16 pcs collars 0. 15× 0. 05× × 2. 7 m 16 pcs bolts 25 × 300 mm 1. 8 0. 6 2. 3. 3 7 5. 4 18 pcs 6. 3 roof battens 0. 05× 0. 025× 6. 3 m 6. 6 144 pcs screws 5× 100 mm 7 pcs drip edge 0. 1× 0. 1 × 2 m (with 0. 2 m overlap) 70 m 2 safety foil 2 m× 0. 5 mm 3. 5 pcs ridge flashing 0. 1× × 2 m (with 0. 2 m overlap) 12 pcs water ducts L-plates 0. 1× 2 m (with 0. 2 m overlap)

3. 3. 2. Bill Of Material: 3. 3. 2. 1. Definition: BOM as Matrix 3. 3. 2. Bill Of Material: 3. 3. 2. 1. Definition: BOM as Matrix Bill Of Materials, BOM (Darabjegyzék): it records the buildup of the finished product from predefined Materials (Cikk) as Components (Komponens). It is used for 2 purposes: To aggregate total requrement from components for 1 product unit, which enables us to make Material Requirement Planning, MRP (Anyagszükségleti Tervezés) later And aggregating direct unit cost of a product from unit cost its components as: Direct. Unit. Cost, EUR = Sc. Aggr. Requremt(c), units × Unit. Cost(c), EUR (4. 1) BOM in simple form is described as a matrix(see Miracle. Roof. Demo. BOM. xls for the example given above), where rows contain ID, Name, Specifications, Measure unit (eg. pieces, m, m 2, kg, etc. ), Unit. Cost, Total requirement of Sub-Components (Al-komponensek), and their detailed requirements at Main Components (Fő-komponensek) in columns. The upper triangle of the matrix is empty, because sub-components cannot contain main-components =Sum. Product(Material. Cost, Total. Requirmt) =Sum(Bolts)

2. 3. 3 7 Part Level. ID Total. Method Part. Descr 6. Part. Dim. 2. 3. 3 7 Part Level. ID Total. Method Part. Descr 6. Part. Dim. X 6 Part. Dim. Y Part. Dim. Z Part. Dim. Unit Part. Quantity Part. MUnit Sub. Part. Descr Relation. Type Main. Part. Descr Part. Status Supplier. ID Parts Lev Supplier. Part. ID e Part Supplier. Lag l Descr Unit. Value Total. Reqirmt ID Total. Value 0 Miracle Start. Date Roof • Time. Period 5. 4 The matrix is a straightforward, easy to understand, but practically useless method of handling BOM at complex products/services: BOM is a huge, but Sparsely(Ritka) filled matrix: It wastes limited computing resources (most spreadsheet programs can handle max 256 columns in 1 worksheet, which is far from enough in any practical application of BOM It is not very easy to describe Intermediary products/modules (Félkész-termékek/modulok) because of limited number of colums: (Eg. in Miracle Roof Demo, 1 pair of rafters, 1 pair of collars and 3 bolts form a structure called A-section, which is repeated 8 times. It would be easier to collect quantities for this module, and simply multiply by 8) So Enterprise Resource Planning, ERP (Vállalatirányítási rendszerek) handles it as data- base table storing non-fixed level hierarchy: There we can create unlimited number of levels of buildup with Main. Part. Desc many: 1 relations (Eg. Rafters, Collars, Bolts will the have main part: A-section, A section will have the main part: Miracle Roof Demo, etc. ) As many levels could be confused up, we will introduce a Level. ID field, which shows on which level we are 1. 8 3. 3. 2. Bill Of Material: 3. 3. 2. 1. Definition: BOM as Non-fixed level hierarchy Main. Part Descr Miracle

3. 3. 2. Bill Of Material: 3. 3. 2. 1. Definition: BOM as Network 3. 3. 2. Bill Of Material: 3. 3. 2. 1. Definition: BOM as Network of Components The disadvantage of simple non-fixed level hierarchy BOMs that you have to describe standard components several times (eg. You will need the same type of screws for fixing roof batens, facias, and many other places. So, you have to define them again and again). However adding som extra fields to the latter table it enables us storing Network(Háló) of components, thus it eliminates redundancy: Totaling sign (Total. Method) (eg. negative (-): buying screws will Part Level. ID cost you money) Total. Method Unique identification name (Part. Desc) (eg. Screw) Part. Descr Size specifications, for its lenght (Part. Dim. X) (eg. 100), diameter Part. Dim. X (Part. Dim. Y) (eg. 5), head height (Part. Dim. Z) (eg. 3) in a specific Part. Dim. Y measure unit (Part. Dim. Unit) (eg. mm) Part. Dim. Z Its measure unit (Meas. Unit) (eg. pieces) Supplier data (Supplier. ID) (eg. Iron & Steel Ltd. ), its code number Part. Dim. Unit Part. Quantity in suppliers catalog (Supplier. Part. ID) (eg. SCR 100× 5), and the Part. MUnit lenght of delivery from supplier (Supplier. Lag) (eg. 7 days) Sub. Part. Descr Status of the part (Part. Status) (eg. Designed: you just Relation. Type negotiating future cooperation with supplier, Active: active Main. Part. Descr delivery, Deleted: supplier messed up, you kill him) Part. Status Purchase price of it (Unit. Value) (eg. EUR 0. 5) in a given Supplier. ID (Time. Period) from (Start. Date) as prices may vary in time Supplier. Part. ID You will leave its Part. Quantity empty (eg. because you do not Supplier. Lag know in advance how much screws you will need) Unit. Value Then, wherever you need screws (eg. Part. Desc=Fascias), you just set Total. Reqirmt there their quantity required (Part. Quantity) and give a reference to the Total. Value previously defined standard component (Sub. Part=Screw). Then system Start. Date • Time. Period can pick up data from there. Totaling quantities of parts referencing to screws, the system can compute total requirement of screws (Total. Requirmt) and multiplicate it with (Unit. Value) and the sign from (Total. Method) it can computed (Total. Value) for a given (Time. Period), how much the total screw requirement will cost you.

3. 3. 2. Bill Of Material: 3. 3. 2. 1. Definition: BOM as Set 3. 3. 2. Bill Of Material: 3. 3. 2. 1. Definition: BOM as Set of alternative Networks A very nasty disadvantage of single network BOM that it can not handle Part Level. ID special type of buildup relations: Total. Method Mutually exclusive components (XOR) (Egymást kizáró beépülés) (eg. fascias can be fixed either with screws, or bolts if they are Part. Descr Part. Dim. X more sizeable, but the 2 methods cannot be mixed) Part. Dim. Y Optional components (Opcionális beépülés) (eg. putting the last Part. Dim. Z pair roof battons over fascias is optional as upper edge of Part. Dim. Unit fascia can also serve as batton) Part. Quantity To resolve this, we will have a Relation. Type field it the database Part. MUnit table to describe special relations Sub. Part. Descr Relation. Type Another disadvantage of single network BOM is lack of parametered Material Requirement Planning (MRP) (Paraméteres anyagszükségleti Main. Part. Descr tervezés) (eg. for 1 Miracle Roof Demo, we need 24 m of water duct Part. Status Supplier. ID L-plates. Therefore, if suppliers have 2 m long plates on stock, we Supplier. Part. ID need 12 pieces, but if they have only 1. 5 m plates, we need 16 of them). There are tons of changes of components and design sizes. It is Supplier. Lag Unit. Value very nasty if we have to recompute thousands of quantities manually Total. Reqirmt after each change. Total. Value This can be resolved if quantities can be given as formulas also Start. Date • Time. Period

3. 3. 2. Bill Of Material: 3. 3. 2. 2. BOM structure in SAP 3. 3. 2. Bill Of Material: 3. 3. 2. 2. BOM structure in SAP 1 3. 3. 2. 2. BOM structure in SAP: Its content is stored in single-leveled (Egy szintet leíró) records: 3. 3. 2. 2. 1. Header (Fejléc): contains all general settings: Described material ID BOM usage Business applications of BOM Lot size range where BOM valid Validity dates Status of BOM(Planned/Actual/Archived) 3. 3. 2. 2. 2. Items list (Tétel lista): 3. 3. 2. 2. 2. 1. ALT: Components (Komponensek): Raw material ID Description Quantity Control code Item category: Stock items: fix quantity warehoused material Non-stock items: non-warehoused item No material master record necessary, instead of that it can be stored in material groups Can be ordered directly at Production Order, PO (Gyártás elrendelés) eg. Consumable goods (Fogyóeszközök) Variable size items: their quantity may change with final product size eg. Area of steel plate Text items: text comments necessary to instruct assembly workers during manufacturing process Document items: documentation of manufacturing algorithm Class items: fictive components grouping together multiple similar materials (eg. all kind of nails (Szög), if does not matter which one

3. 3. 2. Bill Of Material: 3. 3. 2. 2. BOM structure in SAP 3. 3. 2. Bill Of Material: 3. 3. 2. 2. BOM structure in SAP 2 3. 3. 2. 2. 2. Items list (Tétel lista): (Continued) 3. 3. 2. 2. ALT: Assemblies (Modulok): they are materials composed from components according to their own BOM So multi-level hierarchy can be built from several interlinked BOM records! The Down-Top Rule (Alulról felfele szabály): We always define chain of BOMs from the simplest assembly made from raw materials upwards to finished products! 3. 3. 2. 2. 3. Alternative items list at multiple BOMs: Different lot sizes of production may require different material composition (eg. if you produce 2 bicycles in a lot you will buy only a small household amount of paint you need to paint them, but if you produce 10000 bicycles in a lot, you can buy a large barrel of paint from diferent manufacturer, which is relatively more cheap!)

References http: //www. sap-img. com/abap. htm http: //erpgenie. com/ http: //help. sap. com/search/sap_trex. jsp References http: //www. sap-img. com/abap. htm http: //erpgenie. com/ http: //help. sap. com/search/sap_trex. jsp http: //sap. ittoolbox. com/groups/technical-functional/sap-abap/

Értékesítés támogatás (Sales Promotion) Direkt mail (Direct mail) Ajánlat (Offer) Árazás (Pricing) Rendelés (Order) Értékesítés támogatás (Sales Promotion) Direkt mail (Direct mail) Ajánlat (Offer) Árazás (Pricing) Rendelés (Order) Validáció (Validation) Szerződés (Contract) Szállítás (Transport) Hitel (Credit) Ütemezés (Scheduling) Szerviz (Service) Vevőszolgálat (Customer Service) Kattintás (Click) Dupla kattintás (Double Click) Adatbevitel (Write) Csak olvasható (Read Only) t ick igh k Cl RClic Cég (Company) Gyár (Plant) Értékesítési szervezet (Sales Department) Üzletkötő csoport (Sales Representative Group) Értékesítési integráció (Sales Integration) Csatorna (Channel) Földrajzi hely (Geographic Location) Kiszállítási hely (Delivery Location) Szállítási mód (Transportation Mode) Rakodási pont (Loading Point) Árucsoport (Product Group) Értékesítési terület (Sales Area) Object Symbols Partner (Partner) Anyag (Material) Sarzs (Batch) Bevitt anyag (Partner material) Készlet (Inventory) Raktár (Deposit) Gyári szám (Serial number) Darabjegyzék (Bill of materials) Szortiment (Sortiment) Anyagmeghatározás (Material Identification) Árazás (Pricing) Engedmény (Allowance) Fizetési mód (Payment Method) Számla (Invoice) Bizonylat (Voucher)

GUI Symbols To make GUI usage descriptions more short and straightforward, we will use GUI Symbols To make GUI usage descriptions more short and straightforward, we will use standardized denotions of GUI controls, which can be nested into each other: DEF: -definition, PRC: -process, ALT: -alternatives, CYC: -cycle, -follows, -(dis)advantage, Aaa|Bbb|-Menu/Submenu, SCR: -Screen, FRM: -Frame, ID-Unique. ID, BTN: -Button, TXB: -Textbox, DDN: -Dropdown, TAB: -Page tab, CHK: -Checkbox (any of them can be checked) RAD: -Radiobox (one can be checked only), LIN: -Tableline, KEY: -Hotkey, WRN: -Warning box ERR: -Errorbox