SAP TERP10 Preparation Presentation 6 Dr. Gábor Pauler, Associate Professor, Private Entrepeneur

1. SAP TERP10 Preparation Presentation 6 Dr. Gábor Pauler, Associate Professor, Private Entrepeneur Tax Reg. No.: 63673852-3-22 Bank account: 50400113-11065546 Location: 1st Széchenyi str. 7666 Pogány, Hungary Tel: +36-309-015-488 E-mail: pauler@t-online.hu

2. Content of the presentation • 4.Product Lifecycle Management (PLM) Scenario • 4.1.PLM Definition • 4.1.1.Integration tools • 4.1.2.Document management tools • 4.1.3.Product Structure Browser • 4.1.4.Engineering Change&Configuration Management • 4.2.Plot of PLM Scenario • 4.3.CA:Create document info records • 4.3.1.DEF: Document Info Record • 4.3.2.Create Document Info Record: GigaBike-Name: CV01N • 4.3.3.Link Document to Material: GigaBike-Name: CV02N • References • Object Symbols • GUI Symbols

3. 4.Product Lifecycle Management (PLM) Scenario: 4.1.Definition • 4.1.DEF: Product Life Cycle Management (PLM) • Manages products and projects lifecycle from planning to phase out (Kivonás) • It is fully integrated with CRM and SCM, but it has limited activity when product/project is on peak, and it is very active before- and after that • It consists the following components: • 4.1.1.Integration tools • 4.1.1.1.Content objects handled (Import/export):CAD systems, GIS systems, Office systems, Product Classification systems • 4.1.1.2.Tools: • ALT:Remote function call (RFC) of Business Application programming Interface (BAPI) • ALT:Java Connector • 4.1.1.3.GUI: • ALT:Without SAP GUI: uses RFC-based dialog templates • ALT:With SAP GUI • 4.1.2.Document management tools • 4.1.2.1.Content objects handled:Paper-based documents, Folders of paper-based documents, Electronic documents • 4.1.2.2.DEF:Document Info Record(Dokumentum Törzslap): • Document fuction description • Secure Storage Area (Biztonságos Irattár) access • Versioning (Verziózás) • Status={Planned, Active, Archivated, Deleteable} • Classification • Bidirectional Links with SAP ECC parts: What will use it? • Bidirectional Links with ArchiveLink interface: How to import/export? • 4.1.2.3.GUI: • 4.1.2.3.1.Easy Document Management System (DMS) interface:Simplified tool without the need to learn SAP GUI • 4.1.2.3.2.EAI Viewer:View CAD plans even in animated form • 4.1.2.3.3.MS Office:View office documents • 4.1.2.3.4.WorkFlow:Organize documents into process flows

4. 4.PLM Scenario: 4.1.Definition: 4.1.3.Product Structure Browser • 4.1.3.DEF:Product StructureBrowser (Termék Struktúra Nézegető) • 4.1.3.1.Content object handled: • Material masters • BOM • Routings • Documents • 4.1.3.2.Tools • 4.1.3.2.1.Product/object classification • Define Attributes/Characteristics of products/objects: Data fields with given name, type, range  • Define Class Hierarchy: Attribute/Characteristics are assigned for each class  • Objects are assigned to class: • Their Attribute/Characteristics values are determined • A material and its document can go in separate classes • 4.1.3.2.2.Variant Configuration for Configurable materials: • Define Attributes/Characteristics of configurablematerial: Data fields with given name, type, range  • Assign characteristic values to variants of configurable material • General BOM and Super routing will contain all possible components/work steps for all versions  • Dependencies defined in BOM/Routing by characteristic valu-escreating Dynamic BOM/Routing of product versions  • Different type of BOMs can be defined: • Production Dynamic BOM: Normal production • Order BOM: specific variant assigned to 1 order • 4.1.3.3.General Structure of GUI: • FRM:Left:Product hierarchy • FRM:Right:Component detail

5. 4.PLM Scenario: 4.1.Definition: 4.1.4.ECM • 4.1.4.Engineering Change&Configuration Management • 4.1.4.1.Content objects handled:Material master, BOM, Routing, Documents • 4.1.4.2.Tools • 4.1.4.2.1.Engineering Change Management (ECM): • Enables to store historic steps of content object changes • Grouped into Change groups described by Change Master Record: • Header • Change number ID • Reason • Validity dates • Status • Items: Object management records: • References of changed objects or extra documents • Their change can be effected by: • Validity dates • Validity conditions • Propagates through whole LO process • 4.1.4.2.2.Engineering Configuration Management: • Configuration Folder: Enables to store contents assigned to different replicates of product structure • Configuration folders are assigned to product lifecycle phases • For different purposes: engineering/production • 4.1.4.3.GUI • 4.1.4.3.1.Engineering Workbench (EWB) • Can process BOMs and Routings simultaneously in Worklists • Multi user environment: does not lock all the BOMs/Routings, just that part of hierarchy, which is maintained • 4.1.4.3.2.Releasing changes has 2 alternative ways: • ALT: By 1 user in 1 step: Release Change Master Record • ALT: By multiple user in more steps with status change (allocates responsibility and rights): • Engineering Change Record (ECR)  • Engineering Change Order (ECO)

6. Content of the presentation • 4.Product Lifecycle Management (PLM) Scenario • 4.1.PLM Definition • 4.1.1.Integration tools • 4.1.2.Document management tools • 4.1.3.Product Structure Browser • 4.1.4.Engineering Change&Configuration Management • 4.2.Plot of PLM Scenario • 4.3.CA:Create document info records • 4.3.1.DEF: Document Info Record • 4.3.2.Create Document Info Record: GigaBike-Name: CV01N • 4.3.3.Link Document to Material: GigaBike-Name: CV02N • References • Object Symbols • GUI Symbols

7. 4.PLM Scenario: 4.2.Plot, 4.3.Create Document Info Records • 4.2.Plot of PLM Scenario: • Add BOM picture of GigaBike-Name:BOMGigaBike.GIFtoitsDocumentInfoRecord • Product class Bike-Name will be defined with 2 characteristics: • Bike-Type-Name: Possible values:={Men,Women} • Frame-Type-Name: Possible values:={Carbon,Aluminium} • Our finished products will be configurable materials classified into BikeName class with characteristic values: • GigaBike-Name:Bike-Type-Name = Men,Frame-Type-Name = Carbon • MiniBike-Name:Bike-Type-Name = Women, Frame-Type-Name = Aluminium • 4.3.CA:Create DocumentInfoRecords • 4.3.1.DEF: Document Info Record:It connects material with its complex documentation. Now, we will store only BOMs in that • 4.3.2.CreateDocument InfoRecord: GigaBike-Name: CV01N • LO|Centralfunctions|Doc.mngmt|Document|CV01N Create| • 4.3.2.1.SCR:Start • DDN:Document = GigaBike-Name • DDN:Document type = DRW(Engineeringdrawing) • DDN:Document part = 000 • DDN:Document version = 00 • 4.3.2.2.SCR:Main • 4.3.2.2.1.TAB:Document data • TBX:Description = GigaBike-BOM-Name • DDN:Lab./Office = 001(Laboratory1) • 4.3.2.2.1.1.FRM:Originals • BTN:Create new( ) • FRM:Create doc:Basics • TBX:Log = Document Attachment • FRM: Create doc:Details • DDN:WS-Appl. = GIF • DDN:Carrier = Internet • TBX:Original = BOMGigaBike.GIF • 4.3.2.3.BTN:Save( ) Click Click Click Click Click Click CV01N: Create DocInfo Record Giga- Bike- Name Click CV02N: Link DocInfo Record to Mater. Giga- Bike- Name Click

8. 4.PLM Scenario: 4.3.Create Document Info Records • 4.3.3.Link Document to Material: GigaBike-Name: CV02N • LO|Centralfunctions|Document management|Document|CV02N Modify| • 4.3.3.1.SCR:Start • DDN:Material = GigaBike-Name • DDN:Document type = DRM • DDN:Document part = 000 • DDN:Document version = 00 • 4.3.3.2.SCR:Main • 4.3.3.2.1.TAB:Objectlinks • 4.3.3.2.1.1.TAB:Material master • LIN:Empty: • DDN:Material = GigaBike-Name • 4.3.3.3.BTN:Save( ) Click Click CV01N: Create DocInfo Record Giga- Bike- Name Click Click Click Click CV02N: Link DocInfo Record to Mater. Giga- Bike- Name Click Click

9. 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/

10. 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) É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) • 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) Click Right Click

11. 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-UniqueID, • 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