Beruflich Dokumente
Kultur Dokumente
Presentation 0 Dr. Gbor Pauler, Associate Professor, Private Entrepeneur Tax Reg. No.: 63673852-3-22 Bank account: 50400113-11065546 Location: 1st Szchenyi str. 7666 Pogny, Hungary Tel: +36-309-015-488 E-mail: pauler@t-online.hu
Content of the Presentation Introduction Course agenda Availability of course materials Grading Setting up connection to ELTE SAP BSL Server SAP Scenarios Definition Usage Troubleshooting References List of Object/GUI symbols
Even the most streetsmart students sometimes worry about the morning after the groundbreaking graduation party, when you kick aside gals/guys sleeping on the rug drunk, see in a mirror, and ask: What I am gonna to do now? Until this point I was always told what to do! Aim of our 3 semester 10 weeks 2 45 minutes SAP TERP 10 preparatory course is that this morning should NEVER come: From my students, whoever takes SAP really seriously and learn it thoroughly will worry about how his boss will give him a day of to participate graduation ceremony Because these gals/guys will have quite nice paying SAP-related job already at the time of graduation ceremony! Why? Because SAP (Systems, Applications, Packages) is world leading supplier of Enterprise Resorce Planning, ERP Systems (Vllalatirnytsi Rendszerek, VIR): modular software package based on common Data warehouse (Adattrhz), automating Data processing (Adatkezels) and Decision support (Dntstmogats) on all mayor corporate activities: Sales, SD (rtkests), Material Management, MM (Anyagellts), Production Planning, PP (Gyrtstervezs) Financing, FI (Pnzgyek), Controlling, CO (Kontrolling) ERP market extended rapidly in recent years, as owning a working ERP system become a key of survival for companies in a global competition
Unit Presentation Semester 1: 10weeks245min 0 Introduction, Basic info SAP history, architecture, 1 SOA Procurement: Organization, 2 Plot 3 Procurement:Process Semester 2: 10weeks445min 4 Mat.planning:Master data 5 Mat.planning:SOP,MRP 6 PLM:Master data 7 8 9 10 11 12 13 Semester3: 10weeks445min 14 15 16 17 18 19 20 21 22 23
Quiz -
Course Agenda
% Practice - 15SAP IDES, GUI
10
SAP Install
15
SAP Architect. 15Procurement: set organiz, Create semi and master finished mat Procur.master 15Procurement:Invoicing Flex report
15
15
5Mat.planning:BOM,Routing Routings 5Mat.planning:Sales order Re-run MRP 5PLM:Material classification Product structure 5 5 5 5 5 5 5
5 5 5 5 5 5 5 5 5 5
5 5 5 5 5 5 5 5 5 5
5 5 5 5 5 5 5 5 5 5
All course materials are in English to comply with TERP10 But presentations are in Hungarian, and we have English Notes SAP GUI can be both
Grading
Mid-semester requirements: 10 5 points = 50 points from 5-question quizes at the beginning of presentations 10 5 points = 50 points from home assignments due to the beginning of next practice End-of-semester rquirements: None Grading limits: 0..59 points: Fail (1), not recommended to try TERP10 60..69 points: Sufficit (2), not recommended to try TERP10 70..79 points: Medium (3) 80..89 points: Fair (4) 90..100 points: Excellent (5) Consultation possibilities: Mondays 11.00-12.00, room 104, Department of Informatics, Faculty of science, please arrange meeting in advance by E-mail: pauler@tonline.hu Tracking results at mid-semester: A ftp://szentagothai.ttk.pte.hu/pub/pauler/sap-terp10/examsap-terp10/ You can find here an Excel worksheet Costs of course by semesters: 27000HUF/person/10weeks445min, Billed to you by e-Werk Bt. First 2 weeks can be visited free, without any further obligation Payment due to mid-semester
Content of the Presentation Introduction Course agenda Availability of course materials Grading Setting up connection to ELTE SAP BSL Server SAP Scenarios Definition Usage Troubleshooting References List of Object/GUI symbols
SAP Scenarios (Szcenri, Forgatknyv) mean complex business processes executed through series of Transactions (Tranzakci, SAP-program), used to teach working of SAPmodules. Each scenario has: Precondition (Elfelttel): what other scenarios are necsessary to run previously Organizational background (Szervezeti httr): what kind of organizational structure neccessary to run the scenario Plot (Akciterv): a plan of what changes/goals the scenario should complete Master data input (Trzsadat bevitel): static, slowly changing data is necessary to set Business Process (zleti folyamat ): at wich milestone, which transaction from which module should be launced at wich settings Output (Eredmny): displaying/reporting results You will experience running the scenarios that SAP R/3 GUI is sometimes shockingly complex and overcomplicated. Why is that? At each Data Warehouse (Adattrhz) effective Data Storage Structure (Adattrolsi struktra) can be seen on Entity Relationship Diagram, ERD (Egyedkapcsolati diagramm) of the underlying Normalized (Nomalizlt) Relational database (Relcis adatbzis) is completely different from optimal structure of electronic Forms (rlapok) at GUI: how user can conveniently overview business processes The structural difference is usually bridged by 100s of View Table SQL Queries (Nzettbls SQL lekrdezsek), which collect data source of forms from database tables, AND write back changes made by user on forms into database tables. However they are expensive to develope Therefore structure of forms of SAP transactions called Dynpro (Dinpr) are much more close to storage structure than optimal structure of users process overview, so even the most simple business processes (eg. Ordering a raw material, or selling some finished product) are performed sometimes series of 10-30 transactions! Of course there are utilities in SAP to assemble series of Dynpros to perform business processes, but this is still very far from Wizards (Varzsl) usual in other software, which lead unexperienced user through the whole process with explanations and advices of Logic interdependencies (Logikai sszefggsek) of data. Why? Developing wizards is damn expensive, and there should be 100000s of them SAP R/3 is for big companies, where single process is distributed among 20-30 employees doing just 1 phase of it, so they have to learn only 1-2 transactions However it is very inconvenient when you have to learn the whole process
Instead wizards, there are SAP Tutor simulations, but they You should take note just play scenarios like a movie, from one set of data, them in the red text without any interactivity or explanations boxes 1400000000531 How we present SAP scenarios in our course material to in your PPT file and make it more understandable: We will use 3 parallel views on save it, as SAP soour slides: metimes remembers At left: We can see the onoing process at flowchart the last code in the In the middle: There is the explanation of settings of next transaction, transactions and data interdependencies sometimes not! At right: There is animated screenshots of handling of current transaction Practicing scenarios, we should follow the rules below: Transactions should be launched from SAP menu, instead of writing their code in the textbox. The latter is faster, but at the former we will have better picture about the sometimes irrational complex structure of SAP menu of 1000s of items Use Technical Names (Mszaki nevek): to show transaction codes in SAP menu also, set at SAP GUI|Kiegsztsek|Bell-tsok (Extensions|Options) menu, checking Mszaki nevek hasznlata (Display tecnical names) checkbox Many students will create damn many objects on the same server, so there should be a strict naming convention to avoid confusion, using the PTTK-UserName-ObjectName schema Do not use objects created by utehr user, as SAP will block even reading data (irrationally) if more users try to use something simultaneosly, only 1 user can work with that! SAP many times creates new objects, which has no name just identified by a continously incrementing numeric key starting with 2-digit prefix showing the function of the key (eg. A sales order is coded by 140000000531).
You must aknowledge that as SAP is more difficult than womens soul, its natural is ERROR, and you are the guy who will be paid to resolve it! So whenever you face an error in the scenarios, please do not panic: DONT leave a transaction without save! In this case we do not make any harm but many of our work can be lost DONT save objects prematurely without missing data (we get error message at save about what is missing), because you can force SAP to save it uncompleted, but it will not work. But afterwards, you wont be able to delete or modify (you do not have the right for thet, just the main system administrator). In such case you can re-create the object on new name correctly, avoid using the old useless one. Please read error messages and help coming up at F1 hot key: as SAP is not Microsoft product, these have something to do with the reality and can contain useful explanations (38 years of developement worth something). Just sometimes they are in German Open new Modus (Mdusz): If you notice you have to step back to the previous transaction to check some preliminary setting, dont do it in the actual window as you will loose lot of time! Instead of it open new one with j mdusz ltrehozsa (Create new modus) ( ) button, launch the last transaction there, then close it, to avoid slowing down SAP. If the given transaction is stuck, but SAP GUI is not completely frozen: launch SAP GUI Windows tlca-ikon|Jobbkatt| Tranzakci megszaktsa (Taskbar icon|RightClick|Abort trans-action) menu If SAP GUI is completely frozen/session is aborted while transaction was running: Launch SAP GUI and Log-In again. There is a warning, wheter to Folytassa a rgivel vagy nyisson jat? (Continue aborted modus or open new one?)|Nyiss jat (Open new one). Start SM50 Processzttekints (Process overview) transaction. Serach your process stuck by user name and running time and Bejell (Check) it at the beginning of the row. Then launch menu Processz|Megszakts core nlkl (Process|Abort without core) to close process.
Cg (Company) Gyr (Plant) rtkestsi szervezet (Sales Department) zletkt csoport (Sales Representative Group) rtkestsi integrci (Sales Integration) Csatorna (Channel) Fldrajzi hely (Geographic Location) Kiszlltsi hely (Delivery Location) Szlltsi md (Transportation Mode) Rakodsi pont (Loading Point) rucsoport (Product Group) rtkestsi terlet (Sales Area)
Object Symbols Partner (Partner) Anyag (Material) Sarzs (Batch) Bevitt anyag (Partner material) Kszlet (Inventory) Raktr (Deposit) Gyri szm (Serial number) Darabjegyzk (Bill of materials) Szortiment (Sortiment) Anyagmeghatrozs (Material Identification) razs (Pricing) Engedmny (Allowance) Fizetsi md (Payment Method) Szmla (Invoice) Bizonylat (Voucher)
rtkests tmogats (Sales Promotion) Direkt mail (Direct mail) Ajnlat (Offer) razs (Pricing) Rendels (Order) Validci (Validation) Szerzds (Contract) Szllts (Transport) Hitel (Credit) temezs (Scheduling) Szerviz (Service) Vevszolglat (Customer Service) Kattints (Click) Dupla kattints (Double Click) Adatbevitel (Write) Csak olvashat (Read Only)
GUI Symbols
The difficult transactions at SAP GUI have usually a complex cavalcade of menus, buttons, dropdowns, checkboxes, tables, subscreens nested into each other in the wildest variations Which is a result of that differen development teams worked for 30 years using very different GUI development guidelines So most of the time you have to navigate among them very counter-intuitive way To make GUI usage descriptions more short and straightforward, we will use standardized denotions of GUI controls: 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 They can be nested into each other to shortly describe a more complex navigation on GUI (for example):