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

1fedfba788e9d50a2b63178f55b245f6.ppt

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

SAP TERP 10 Preparation Presentation 2 Dr. Gábor Pauler, Associate Professor, Private Entrepeneur Tax SAP TERP 10 Preparation Presentation 2 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: pauler@t-online. hu

Content of the presentation 2. Procurement scenario: 2. 1. Organizational environment 2. 2. Setting Content of the presentation 2. Procurement scenario: 2. 1. Organizational environment 2. 2. Setting organizational structure 2. 3. Plot/preconditions 2. 4. Create Master Data 2. 4. 1. Create Material Master References Object Symbols GUI Symbols

2. Procurement scenario: 2. 1. Organizational environment DEF: Procurement: A business process ensuring that 2. Procurement scenario: 2. 1. Organizational environment DEF: Procurement: A business process ensuring that all externally/internally produced materials/ parts/ services necessary for completing customer orders are acquired in right time, at right place. 2. 1. Targeted organizational environment: 2. 1. 1. Client: 903 2. 1. 1. 1. FI: Company: 1000 -ERP 2. 1. 1. LO: Plant: 1000 -Hamburg 2. 1. 1. 1. LO: Storage: 0110 -Hamburg 2. 1. 1. 2. LO: Storage: 0120 -Hamburg 2. 1. 1. 3. MM: Purchasing organization: 1000 (Plant-specific) 2. 1. 1. 1. 2. LO: Plant: 1100 -Munich 2. 1. 1. 1. 2. 1. LO: Storage: 1110 -Munich 2. 1. 1. 1. 2. 2. LO: Storage: 1120 -Munich 2. 1. 1. 1. 2. 3. LO: Storage: 1130 -Munich 2. 1. 1. 3. MM: Purchasing organization: 1100 (Plant-specific) 2. 1. 1. 1. 3. MM: Purchasing organization: 1999 (Cross-Plant: 1000, 1100 ) 2. 1. 1. 2. FI: Company: 2000 -UK branch 2. 1. 1. 2. 1. LO: Plant: 2000 -Heathrow 2. 1. 1. 3. FI: Company: 3000 2. 1. 1. 4. MM: Purchasing organization: C 100 (Cross-Company: 1000, 2000, 3000 ) 2. 1. 1. 4. 1. MM: Purchasing group: C 101 Group of purchasers dealing with purchasing the same materials regardless company and purchasing organization

2. Procurement scenario: 2. 2. Setting organizational structure Click MM IMG Click ck Cliick 2. Procurement scenario: 2. 2. Setting organizational structure Click MM IMG Click ck Cliick l C Click Clic k Clic ck k k Clic lick ck C Cli ck k lic C Step 2. 2. Set Organizational structure 2. 4. Create Master Data 2. 2. Setting organizational structure in customizing You can do it if you have SAP_ALL right. Be careful modifying it! 2. 2. 1. Tools|Customizing|IMG|SPRO Execute project 2. 2. 1. 1. BTN: SAP Reference IMG 2. 2. 1. 1. 1. Enterprise structure| 2. 2. 1. 1. Definition| FI Financial accounting| Edit Company| SPRO: Check COL: Company code, plants COL: Name, 1000 COL: Address, 1100 COL: Currency, 2000 COL: Language LO Logistics general| Define Plant| COL: Plant code, COL: Name, COL: Address, COL: Taxing, COL: Calendar For handling working days! MM Material management| MMF 1: Maintain purchase organizations| Create COL: Code, finished COL: Description material Maintain storage locations|Plant| Giga Instant assignment! Bike COL: Code, Name COL: Description 2. 2. 1. 1. 1. 2. Assignment| LO Logistic general| Plant to company| MM Material management| Purchasing org to company| Empty for Cross-Comp Purch. Org!

2. Procurement scenario: 2. 3. Plot/preconditions 1 2. 3. Plot of Procurement Scenario: 2. 2. Procurement scenario: 2. 3. Plot/preconditions 1 2. 3. Plot of Procurement Scenario: 2. 3. 1. MM: In Material Master (Anyagtörzs) define Finished product (Késztermék): Giga. Bike-Name 2. 3. 1. 1. At the following organization: 2. 3. 1. 1. 1. Client: 912 2. 3. 1. 1. Company: 1000 Plant: 1000 Storage: 0110 Channel: 10 Sales. Org: 1000 Controlling area: 1000 Purch. Org: 1000 2. 3. 1. 2. MM: Define Bill of Material, BOM (Darabjegyzék) for Giga. Bike-Name: it describes from which components (raw materials, semi finished materials) of which quantity it is assembled in Plant 1000 2. 3. 1. 2. 1. MM: In material master define Semi finished material (Félkésztermék): Base. Bike-Name: Material requirement: 1 pcs/main component, Assemble in Plant 1000 2. 3. 1. 2. 1. 1. MM: In material master define Raw material (Nyersanyag): Carb. Frame-Name: Material requirement: 1 pcs/main component, Order from Vendor-Name 2. 3. 1. 2. MM: In material master define raw material: Wheel-Name: Material requirement: 2 pcs/main component, Order from Vendor-Name 2. 3. 1. 2. 1. 3. MM: In material master define raw material: Chain-Name: Material requirement: 1 pcs/main component, Order from Vendor-Name

2. Procurement scenario: 2. 3. Plot/preconditions 2 2. 3. 1. 2. 1. 4. MM: 2. Procurement scenario: 2. 3. Plot/preconditions 2 2. 3. 1. 2. 1. 4. MM: In material master define Trading good (Sztenderd áru): Gearing-Name: Material requirement: 1 pcs/main component, Order from Vendor-Name 2. 3. 1. 2. MM: Define Bill of Material, BOM (Darabjegyzék) for Giga. Bike-Name: 2. 3. 1. 2. 2. MM: Use already defined raw material: Pedal: Material requirement: 2 pcs/main component, On stock 2. 3. 1. 2. 3. MM: Use already defined raw material: Brakes: Material requirement: 2 pcs/main component, On stock 2. 3. 1. 2. 4. MM: Use already defined raw material: Handlebar: Material requirement: 1 pcs/main component, On stock 2. 3. 1. 2. 5. MM: Use already defined raw material: Saddle: Material requirement: 1 pcs/main component, On stock 2. 3. 1. 3. MM: Define Vendor (Beszállító): Vendor-Name an organization delivering materials for us: Chain Reaction Cycles Ltd. , Kilbride Rd 6, Doagh, Ballyclare, BT 39 0 QA, United Kingdom, Tel: +44 (0)28 9335 2976, Fax: 44 (0)28 9334 9461, E -mail: customerservice@chainreactioncycles. com 2. 3. 1. MM: Define Purchase Info Records (Beszállítói könyv): description of materials purchased from vendor, 2. 3. 1. 4. MM: Order (Rendel) missing parts from vendor

Content of the presentation 2. Procurement scenario: 2. 1. Organizational environment 2. 2. Setting Content of the presentation 2. Procurement scenario: 2. 1. Organizational environment 2. 2. Setting organizational structure 2. 3. Plot/preconditions 2. 4. Create Master Data 2. 4. 1. Create Material Master References Object Symbols GUI Symbols

2. Procurement scenario: 2. 4. Create Master Data: 2. 4. 1. Create Material 1 2. Procurement scenario: 2. 4. Create Master Data: 2. 4. 1. Create Material 1 Click C Click Click ck Cli MM Cl ick Click Click Cli ck IMG Step 2. 2. Organ 2. 4. Create Master Data 2. 4. Define Master Data (Prefixes at headings signal the corresponding organizational level of data!) 2. 4. 1. MM: Create Material Master (Anyagtörzs): Description of a „theoretically described” material to be purchased LO|MM|Material master|Material|Create special| 2. 4. 1. 1. |MMF 1 Finished product (Késztermék): Giga. Bike-Name: SCR: Start: TBX: Material = Giga. Bike-Name DDN: Sector = Mechanical engineering SPRO: BTN: Organization|SCR: Organization| Check DDN: Plant = 1000 (Hamburg) plants 1000 DDN: Chanel = 10 (Retail(Kisker) 1100 DDN: Storage = 0110 (Hamburg) MMF 1: DDN: Sales. Org = 1000 (Hamburg) Create BTN: View (Nézet) selection: group of Fields (Mező) finished from Database tables (Adatbázis tábla) stored in SAP material Giga Data Dictionary, DDIC (Adatszótár) connected with a Bikespecial topic. Views are not created automatically Name to save storage space. If you forget to create a MMB 1: necessary one, the material won’t work until you Create re-run material creation in MM 01 and create it! semifinished Some views are neccessary to create even if you material won’t fill anything there! Base DDN: Basic 1 -2, Sales 1 -2 -General, MRP 1 -2 -3 -4, Bike. Name Work. Sched, Warehouse 1 -2, Accounting 1 -2, Costing 1 -2 (This is the minimal set of views workable) MMR 1: Create 2. 4. 1. 1. 1. Client: TAB: Basic data 1 raw. mat DDN: Material Description = Giga. Bike-Name Carb DDN: Unit of Measure = PC (Piece) Frame DDN: Division = 01 /Wheel /Chain. TBX: Gross weight = 18 KG Name TBX: Net weight = 15 (Gross wgt. - packaging weight) Click

2. Procurement scenario: 2. 4. Create Master Data: 2. 4. 1. Create Material 2 2. Procurement scenario: 2. 4. Create Master Data: 2. 4. 1. Create Material 2 MM IMG Step 2. 2. Organ 2. 4. Create Master Data Click Click Cli ck Click ck Cli SPRO: Check plants 1000 1100 MMF 1: Create finished material Giga Bike. Name MMB 1: Create semifinished material Base Bike. Name MMR 1: Create raw. mat Carb Frame /Wheel /Chain. Name 2. 4. 1. 1. 2. Client: TAB: Basic data 2 2. 4. 1. 1. 3. Sales. Org: TAB: Sales 1 DDN: Deliv plant = 1000 DDN: Tax=Half tax(Value Added Tax(ÁFA) 2. 4. 1. 1. 4. Sales. Org: TAB: Sales 2 2. 4. 1. 1. 5. Sales. Org: TAB: Sales General DDN: Availability check = 02 (Individual) DDN: Trans. Grp = 0001(Pallet(Raklap) DDN: Load. Grp = 1100(Forklift(Targonca) 2. 4. 1. 1. 6. Company|Plant: TAB: MRP 1 DDN: MRP type = PD (Material Requirements Planning, MRP (Anyagszükségleti tervezés/Diszpozíció): SAP should compute parts requirement and deadlines automatically from quantity and deadline of finished product DDN: MRP controller = 001 (Disponent 001: the responsible postion for MRP) DDN: Lot size = EX (Lot-for-lot order quantity (Pontosan a rendelés mértékét): for small finished products - eg. screws/bolts – it is worth to produce larger Lot sizes (Sorozatnagyság) than orders in advance, to make it more profitable. This is not the case at Giga. Bike-Name) 2. 4. 1. 1. 7. Company|Plant: TAB: MRP 2 DDN: Procurement type = E(Own product) DDN: In-house production = 5 days DDN: Sched. Margin key = 000 (Code of MRP scheduling (Ütemező) algorithm) DDN: Prod. stor. location = 0110 (Where to put finished product) Cli ck

2. Procurement scenario: 2. 4. Create Master Data: 2. 4. 1. Create Material 3 2. Procurement scenario: 2. 4. Create Master Data: 2. 4. 1. Create Material 3 Click ic Cl k MM IMG Click k Clic Step 2. 2. Organ 2. 4. Create Master Data SPRO: Check plants 1000 1100 MMF 1: Create finished material Giga Bike. Name MMB 1: Create semifinished material Base Bike. Name MMR 1: Create raw. mat Carb Frame /Wheel /Chain. Name 2. 4. 1. 1. 8. Company|Plant: TAB: MRP 3 DDN: Tot. repl. lead time = 15 days (If nothing left on Inventory (Készlet) it takes so many time to reorder and deliver it) DDN: Availability check = 02 (Individual requirement: it should reserve exactly the required amount of components for finished product from inventory) 2. 4. 1. 1. 9. Company|Plant: TAB: MRP 4 2. 4. 1. 1. 10. Company: TAB: Work scheduling 2. 4. 1. 1. 11. Company: TAB: Accounting 1 DDN: Price control = S (Standard price: it will not change until manually changed) DDN: Standard price = 2500 EUR DDN: Valuation class = 7920 (finished products: in which Bookeeping Account Class (Könyvelési számlaosztály) in General Ledger, G/L (Számlakeret) to Book (Könyvel) value of finished products: it is a 4 -5 level hierachy of 400 -500 accounts with different purposes identified by unique code number. It can vary from county to country, but there is a European standard G/L. We will use German G/L here!) 2. 4. 1. 1. 12. Company: TAB: Accounting 2 2. 4. 1. 1. 13. Company: TAB: Costing 1 CHK: Material Origin = True (Compute material costs from order costs) CHK: With Quantity Structure = True (Consider cost of its components) 2. 4. 1. 1. 14. Company: TAB: Costing 2 Click

2. Procurement scenario: 2. 4. Create Master Data: 2. 4. 1. Create Material 4 2. Procurement scenario: 2. 4. Create Master Data: 2. 4. 1. Create Material 4 MM IMG Step 2. 2. Organ 2. 4. Create Master Data Other views of material master, which are not created now: 2. 4. 1. 1. 15. Company|Plant|Storage: Stock level 2. 4. 1. 1. 16. Company|Plant: Storage location 2. 4. 1. 1. 17. Company: Warehousing data 2. 4. 1. 1. 18. Purch. Org: Purchasing data 2. 4. 1. 1. 19. Company: Quality management 2. 4. 1. 1. 20. Company: Forecasting 2. 4. 1. 1. 21. Company: Product Classification Closing steps of creating finished material: SPRO: Check 2. 4. 1. 1. 22. BTN: Additional data plants DDN: Language = EN 1000 TBX: Description = Giga. Bike-Name 1100 2. 4. 1. 1. 23. BTN: Save( )STS: mater. created MMF 1: What we have now: Create finished Material Description = Giga. Bike-Name material Unit of Measure = PC (Piece) Giga Division = 00 (cross-division) Bike. Name Gross weight = 18 KG MMB 1: Net weight = 15 KG Create Delivery plant = 1000 semi. Storage location = 0110 finished material Tax = medium (VAT) Base Transportation = Pallet Bike. Load with = Forklift Name MRP controller = 001 MMR 1: Create In-house production = 5 days raw. mat Tot. repl. lead time = 15 days Carb Standard price = 2500 EUR Frame /Wheel What we do not have yet: /Chain. What kind of components it has? Name From where they will come? Click

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