Terp10 Notes

Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25.
PaulerSoft CANAL notes, page: 1 2.8. Cross-module integration of MM:Procurement.........................................11 2.8.1. Financial accounting (FI): Invoice accounting documents:...............11 SAP TERP10 Preparatory Course Notes 2.8.2. Sales&Distribution (SD): Sales order................................................11 2.8.3. Production Planning(PP):...................................................................11 1. Introduction.........................................................................................................5 2.8.4. Maintenance( MT):.............................................................................11 1.1. DEF: Enterprise Resource Planning (ERP)................................................5 2.8.5. Warehouse Management System (WMS).........................................11 1.2. SAP Architecture History............................................................................5 2.9. Reporting...................................................................................................12 1.2.1. 1972 SAP R/1, R/2 .............................................................................5 2.9.1. MM:List display:ME2L.......................................................................12 1.2.2. 1992 SAP R/3......................................................................................5 2.9.2. MM:LIS standard analysis:MCE3......................................................12 1.2.3. 1994 Win NT porting............................................................................5 3. Material Planning Scenario...............................................................................13 1.2.4. 1998 EnjoySAP: user friendly GUI......................................................5 3.1. Organizational background.......................................................................13 1.2.5. 1999 MySAP: e-business....................................................................5 3.2. Plot/Preconditions of Scenario..................................................................13 1.2.6. 2002 SAP B1: for small companies.....................................................5 3.3. Creating/Modifying master data................................................................13 1.2.7. 2003 SAP ERP....................................................................................5 3.3.1. Material master: MM01......................................................................13 1.2.8. 2008 SAP ERP 6.0..............................................................................5 3.3.2. Bill Of Material (BOM): CS01.............................................................13 1.3. SAP ERP Organizational hierarchy: Client/Mandant (901)........................6 3.3.3. Routings.............................................................................................14 1.3.1. FI, CO: Credit Control Area.................................................................6 3.4. Material planning.......................................................................................15 1.4. SAP ERP Data Structure............................................................................6 3.4.1. DEF:Material Planning.......................................................................15 1.4.1. DEF: Master data................................................................................6 3.4.2. Change material: MM02....................................................................16 1.4.2. Transactions data................................................................................6 3.4.3. Create Product Groups: MC84..........................................................16 1.5. SAP ERP Process examples......................................................................6 3.4.4. Create Sales and Production Plan: MC82.........................................16 1.5.1. Purchase to pay...................................................................................6 3.4.5. Disaggregation of Production Plan: MC75........................................16 1.5.2. Order to Cash......................................................................................6 3.4.6. Material Requirement Planning: MD02.............................................16 1.5.3. Produce a service................................................................................6 3.4.7. Create Sales Order: VA01.................................................................17 1.6. SAP ERP Reporting hirearchy....................................................................6 3.4.8. Material Requirement Re-Planning: MD02........................................17 1.6.1. On-Line Transaction Processing (OLTP)............................................6 4. Lifecycle Data management scenario..............................................................18 1.6.2. Data Warehousing (DW).....................................................................6 4.1. DEF: Product Life Cycle Management (PLM)..........................................18 1.6.3. On-Line Analitical Processing (OLAP).................................................6 4.1.1. Integration..........................................................................................18 1.7. SAP model company: Internet demonstration and evaluation system 4.1.2. Document management....................................................................18 (IDES)..................................................................................................................6 4.1.3. Product structure browser.................................................................18 1.7.1. Organizational structure......................................................................6 4.1.4. Engineering Change&Configuration Management............................18 1.7.2. Customizing.........................................................................................6 4.2. Plot of PLM Scenario:...............................................................................18 1.7.3. Master data..........................................................................................6 4.3. CA:Create document info records............................................................18 1.7.4. Transaction data..................................................................................6 4.3.1. DEF: Document Info Record.............................................................18 1.7.5. Business processes.............................................................................6 4.3.2. Document info record: SpeedStar-0005: CV01N..............................18 1.7.6. Tutorials...............................................................................................6 4.3.3. Link Document to Material: SpeedStar-0005: CV02N......................19 1.8. SAP GUI 7.2 For Win7................................................................................6 4.4. CA:Classification of material.....................................................................19 1.8.1. Menu bar..............................................................................................6 4.4.1. Create characteristics: Bike-Type-0005: CT04.................................19 1.8.2. Function button bar..............................................................................6 4.4.2. Create characteristics: Frame-Type-0005: CT04.............................19 1.8.3. Application title bar..............................................................................6 4.4.3. Create class: Bike0005: CL02...........................................................19 1.8.4. Application function button bar............................................................6 4.4.4. Classify material: SpeedStar-0005: MMF1.......................................19 1.8.5. SAP Easy Access menu......................................................................6 4.4.5. Classify material: SpeedStarlett-0005: MMF1..................................19 1.8.6. Application work area..........................................................................6 4.4.6. Checking out materials in a class with values: Bike0005: CL30N....19 1.8.7. Status bar............................................................................................6 4.5. CA:Product Structure Browser: SpeedStar-0005: CC04..........................19 1.8.8. Hot keys...............................................................................................6 4.5.1. SCR:Start...........................................................................................19 2. Procurement scenario.........................................................................................7 4.5.2. SCR:Main...........................................................................................19 2.1. Organizational environment........................................................................7 5. Manufacturing Execution Scenario...................................................................20 2.1.1. Client: 901............................................................................................7 5.1. Plot of scenario.........................................................................................20 2.2. Setting organizational structure in customizing..........................................7 5.1.1. Plot of master data............................................................................20 2.2.1. Tools|Customizing|IMG|SPRO Execute project..................................7 5.1.2. Plot of Production-On-Order Preparation..........................................20 2.3. Plot/Preconditions of the scenario..............................................................7 5.1.3. Production Order Process.................................................................20 2.3.1. Finished product: Speedstar-0005......................................................7 5.1.4. Production Closing Operations..........................................................20 2.4. Master data.................................................................................................7 5.2. Modify BOM and Routing master data.....................................................20 2.4.1. MM: Create Material Master:MM01 ...................................................7 5.2.1. Processed data structures.................................................................20 2.4.2. MM: Display material list: MM60.........................................................8 5.2.2. Display Work Center: 1420: CR03....................................................20 2.4.3. MM: Modify materials: MM02..............................................................8 5.2.3. Display Routing: SpeedStar-0005: CA02..........................................20 2.4.4. MM: Create Vendor Master: XK01......................................................8 5.3. Production-On-Order Preparation.............................................................21 2.4.5. MM: Create Purchasing Info records:ME11........................................8 5.3.1. DEF: Production types.......................................................................21 2.5. Procurement process..................................................................................9 5.3.2. PROC:Production on Order...............................................................21 2.5.1. MM: Create Purchasing Requisition:ME51N......................................9 5.3.3. CO:Product Costing...........................................................................21 2.5.2. MM: Create Purchasing Order:ME21N...............................................9 5.3.4. MM:Re-run MRP:SpeedStar-0005:MD02..........................................22 2.5.3. MM: Display Purchasing Order:ME23N..............................................9 5.4. PP:Production order:SpeedStar-0005.......................................................22 2.5.4. MM: Display Messages:ME9F............................................................9 5.4.1. DEF:Production Order process.........................................................22 2.5.5. MM: Processing status of purchase requisition:ME53N.....................9 5.4.2. MM:Check MRP status:SpeedStar-0005:MD04...............................22 2.6. Goods processing.....................................................................................10 5.4.3. PP:Create Production Order (Semi-Finished):Basis-Module-0005 2.6.1. DEF: Stock Usability Types:.............................................................10 1371PC:MD04...............................................................................................23 2.6.2. DEF: Goods movement documents:.................................................10 5.4.4. PP:Create Production Order (Finished):SpeedStar-0005 2.6.3. MM:Checking stock movement types:ME23N..................................10 1371PC:MD04...............................................................................................23 2.6.4. MM:Check Stock Overview:MMBE...................................................10 5.4.5. MM:Create Purchase Order (RawMat):Gearing-0005 2185PC:MD04 2.6.5. MM: Post Goods Receipt:MIGO........................................................10 .......................................................................................................................23 2.6.6. MM: Display Material/Accounting Document:MIGO.........................10 5.4.6. MM:Create Purchase Order (RawMat):Wheel-0005 4570PC:MD04 23 2.6.7. MM: Material transfers in unrestricted use stock:MIGO...................10 5.4.7. MM:Create Purchase Order (RawMat):Chain-0005 2285PC:MD04.23 2.6.8. MM: Display new Material Document:MIGO.....................................10 5.4.8. MM:Create Purchase Order (RawMat):Carb-Frame-0005 2.6.9. MM: Display Stock Overview:MMBE................................................10 1371PC:MD04...............................................................................................23 2.6.10. MM: Display Order History:ME23N.................................................10 5.4.9. MM:Post Goods Receipt: Gearing-0005:MIGO.................................23 2.7. Invoice processing....................................................................................11 5.4.10. MM:Post Goods Receipt: Wheel-0005:MIGO.................................23 2.7.1. MM: Enter Vendor Invoice:MIRO......................................................11 5.4.11. MM:Post Goods Receipt: Chain-0005:MIGO..................................23 2.7.2. MM: Display Invoice Document and Order History:MIRO................11 5.4.12. MM:Post Goods Receipt: Carb-Frame-0005:MIGO........................23 2.7.3. FI:Check subledger account of vendor:FBL1N.................................11 5.4.13. MM:Goods Issue: Basis-Module-0005: MB1A................................23 2.7.4. FI: Payment:F58................................................................................11 5.4.14. PP:Confirm production order: Basis-Module-0005: CO15..............23 2.7.5. Checking paid items:FBL1N..............................................................11 5.4.15. MM:Check production confirmation: Basis-Module-0005:MD04.....23 Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage, Aaa|Bbb| -Menu/Submenu, SCR-Screen, FRM-Frame, IDUniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft CANAL notes, page: 2 5.4.16. MM:Goods Issue: SpeedStar-0005: MB1A.....................................23 7.4.5. MM:Run MRP:SpeedStarlett-0005, Plant1000:MD02.......................31 5.4.17. PP:Confirm production order: SpeedStar -0005: CO15..................23 7.4.6. MM:Check Stock-Req List:SpeedStarlett-0005, Basis-Modul25.4.18. MM:Check production confirmation: SpeedStar -0005:MD04........23 0005:MD04....................................................................................................31 5.5. Production Closing Operations.................................................................24 7.4.7. PP:Create Production Order:Basis-Modul2-0005, 500PC:MD04.....31 5.5.1. MM:Check Goods Movement Documents: SpeedStar-0005: MB51 24 7.4.8. PP:Create Production Order:SpeedStarlett-0005, 500PC:MD04.....31 5.5.2. PP:Variance and cost analysis: SpeedStar-0005: CO03..................24 7.4.9. MM:Purchasing info record:Alu-Frame-0005, Vendor100268:ME11 31 5.5.3. FI:Period end summary of cost variances by category: SpeedStar7.4.10. PP:Order materials:Alu-Frame-0005, 500PC:MD04.......................32 0005: KKS2...................................................................................................24 7.4.11. MM:Goods receipt:Alu-Frame-0005, 500PC:MIGO........................32 5.5.4. PP:Order Settlement: SpeedStar-0005: KO88..................................24 7.4.12. MM:Goods issue:Basis-Modul2-0005:MB1A...................................32 5.5.5. PP:Order Completion and Closing: SpeedStar-0005: CO02............24 7.4.13. PP:Confirm Production Order:Basis-Modul2-0005:CO15...............32 5.6. Order Information System.........................................................................24 7.4.14. MM:Goods issue:SpeedStarlett-0005:MB1A...................................32 5.6.1. PP:Production Order Report: SpeedStar-0005: COOIS...................24 7.4.15. PP:Confirm Production Order: SpeedStarlett-0005:CO15..............32 6. Warehouse Management Scenario..................................................................25 7.4.16. MM:Update Sales order|Schedule lines for pre-date 6.1. Plot of Scenario.........................................................................................25 delivery:13370:VA02.....................................................................................32 6.1.1. MM:Material master:..........................................................................25 7.4.17. SD:Create delivery:13370:VL01N...................................................32 6.1.2. LO:Warehouse management:...........................................................25 7.4.18. SD:Picking/Create Transfer order:80016247:LT03.........................32 6.1.3. LO:Physical inventory management..................................................25 7.4.19. SD:Delivery|Goods issue:80016247:VL02N...................................32 6.2. DEF:Goods Movements............................................................................25 7.4.20. SD:Create Billing Document:80016247:VF01.................................33 6.2.1. DEF:Goods receipt............................................................................25 7.4.21. FI:Enter Incoming payment:1309000EUR to BankAcct113109:F-28 6.2.2. DEF:Goods issue..............................................................................25 .......................................................................................................................33 6.2.3. DEF:Inter Stock Transfer..................................................................25 7.4.22. SD:Display Document Flow summary: 80016247:VL02N..............33 6.3. DEF:Organizational hierarchy...................................................................25 7.5. SD:Reporting.............................................................................................33 6.3.1. Client..................................................................................................25 7.5.1. DEF:SD:Sales Information System (SIS)..........................................33 6.4. DEF:LO:Logistics Execution process, Warehouse Mngmt......................25 7.5.2. SD:Display Sales Orders:50005:VA05..............................................33 6.4.1. Goods Receipt...................................................................................25 7.5.3. SD:Carry out Standard Analysis: 50005:MCTA................................33 6.4.2. Goods Issue.......................................................................................25 8. Human Capital Management (HCM) Scenario.................................................34 6.5. MM:Maintain master data.........................................................................26 8.1. Plot of Scenario:........................................................................................34 6.5.1. MM:Extend material master to new plant:Speedstar8.1.1. Maintain organizational structure master data..................................34 0005Plant1200:MM01...............................................................................26 8.1.2. Recruitment process..........................................................................34 6.6. LO:Warehouse management....................................................................26 8.1.3. Hiring process....................................................................................34 6.6.1. LO:Display stock overview: SpeedStar-0005: MMBE.......................26 8.1.4. Personell planning&development......................................................35 6.6.2. LO:Create stock transport order: SpeedStar-0005: 1000PC: ME21N 8.1.5. Training management........................................................................35 ......................................................................................................................26 8.2. Organizational levels of HCM...................................................................35 6.6.3. LO:Post Goods Issue: SpeedStar-0005: Plant1000, Storage0001, 8.2.1. Enterprise structure ........................................................................35 1000PC: MIGO..............................................................................................26 8.2.2. Personell structure ..........................................................................35 6.6.4. LO:Display material document:4900038468:MB03...........................26 8.2.3. Organizational structure.....................................................................35 6.6.5. LO:Display material document: 4900038468: MIGO........................26 8.3. DEF:HCM-PA Infotypes:...........................................................................35 6.6.6. LO:Post Goods Receipt: SpeedStar-0005: Plant1200, Storage0140, 8.3.1. Content:.............................................................................................35 1000PC: MIGO..............................................................................................26 8.3.2. GUI: PA30:.........................................................................................35 6.6.7. LO:Display Accounting Document:5000012473: MB03....................27 8.3.3. GUI:PA40:..........................................................................................35 6.6.8. LO:Display target storage type and transfer req. 8.4. PROC:HCM...............................................................................................36 number:5000012473: MIGO.........................................................................27 8.4.1. Personnel Management (SAP HCM-PA)...........................................36 6.6.9. LO:Convert Transfer req. into Transfer order (Putaway): 12: LB11. 27 8.4.2. Time Management (SAP HCM-PT)...................................................36 6.6.10. LO:Check total stock: SpeedStar-0005, Warehouse0140: LS26....27 8.4.3. Payroll Administration (SAP HCM-PY)..............................................36 6.6.11. LO:Confirm transfer order: 0000000012: LT12...............................27 8.4.4. Training and event management (SAP HCM-PE).............................36 6.7. Physical inventory management...............................................................27 8.4.5. Travel Planning (SAP FI-TV).............................................................37 6.7.1. DEF:Stock Management Unit (SMU)................................................27 8.4.6. Employee Self-Services (SAP HCM-ESS)........................................37 6.7.2. PROC: Physical inventory (PI)..........................................................27 8.4.7. Human Resources Information Sytem (HIS).....................................37 6.7.3. PROC:Cycle Counting.......................................................................27 8.5. Maintain organizational structure master data..........................................37 6.7.4. MM:Create PI Document:Speedstar-0005, Plant1000, 8.5.1. CO:Display Profit Center standard hierarchy:H1100:KCH6N...........37 Storage0001:MI01.........................................................................................28 8.5.2. CO:Create Profit Center:PROF-0005 into H1100:KE51...................37 6.7.5. MM:Carry out PI Count:100001240:MI04.........................................28 8.5.3. CO:Display Cost Center standard hierarchy/Create Cost Center 6.7.6. MM:Display difference list and post it:100001240:MI20...................28 Group:H10005 into H1300:OKEON..............................................................37 6.7.7. MM:Display PI Doc/statistics:100001240:MI03................................28 8.5.4. CO: Create Marketing&Sales Cost Center:CCMSD-0005 into 6.7.8. MM:Set Cycle Counting: Mat.type=FERT, Plant1000: MIBC...........28 H10005:KS01................................................................................................37 7. Sales Scenario..................................................................................................29 8.5.5. CO: Create Marketing Cost Center:CC-MA-0005 into H10005:KS01 7.1. Plot of Scenario.........................................................................................29 .......................................................................................................................37 7.1.1. SD:Create Customer Master:............................................................29 8.5.6. CO: Create Sales Cost Center:CC-SD-0005 into H10005:KS01.....37 7.1.2. SD:Create Product-specific condition:..............................................29 8.5.7. HCM:Create Organizational units|Subunits:DepBike-0005|SD7.1.3. SD:Create Customer-specific condition:...........................................29 0005,Mark-0005:PPOCE..............................................................................37 7.1.4. SD:Create Sales Order:.....................................................................29 8.5.8. HCM:Create Jobs|General tasks:Manage-0005|Mgmt-0005, Secret7.1.5. PP:Manufacture Sales Order:............................................................29 0005|Corresp-0005,Orga-0005:PPOME.......................................................38 7.1.6. SD:Create delivery:...........................................................................29 8.5.9. HCM:Create Positions:SD-DC-0005, SD-SE-0005, MA-DC-0005, 7.1.7. FI:Enter Incoming payment:..............................................................29 MA-SE-0005:PPOME....................................................................................38 7.2. SD:Organizational levels...........................................................................29 8.5.10. HCM:Assign Jobs|Positions:Manage-0005|SD-DC-0005, MA-DC7.2.1. Client..................................................................................................29 0005, Secret-0005|SD-SE-0005, MA-SE-0005:PPOME...............................38 7.3. Create Master data...................................................................................29 8.5.11. HCM:Create Positions|Individual tasks:SD-DC-0005|Acquise-0005, 7.3.1. DEF: Data sources of SD documents...............................................29 MA-DC-0005|Advert-0005:PPOME...............................................................38 7.3.2. SD:Create Customer Master:50005 at Comp1000, SlsOrg1000, 8.5.12. HCM:Update Positions|Job/task shares:SD-DC-0005|ManageChn10, Div00:XD01......................................................................................29 0005=50%/Acquise-0005=50%, MA-DC-0005|Manage-0005=50%/Advert7.3.3. SD:Extend Customer Master:50005,Chn12:VD01............................29 0005=50%:PPOME.......................................................................................38 7.3.4. SD:Display Customer Master:50005:XD03.......................................30 8.5.13. HCM-PA:Check Infotypes:1001:PA30............................................38 7.3.5. SD:Create Product-specific condition:SpeedStarlett-0005:MM02....30 8.6. Recruitment process.................................................................................38 7.3.6. SD:Create Customer-specific condition:50005:VK31.......................30 8.6.1. HCM:Check vacancy status:SD-DC-0005:PPOME..........................38 7.4. SD:Sales order process............................................................................30 8.6.2. HCM:Create Job Ads:SD-DC-0005:PBAW.......................................38 7.4.1. PROC:Order-to-cash backward scheduling milestones....................30 8.6.3. SAP Business Workplace:Job adverts 0005.....................................39 7.4.2. DEF:Sales Order Document Flow by Milestones.............................30 8.6.4. HCM:Create Applicant master:00001561:PB10................................39 7.4.3. SD:Create Sales Order:50005, 500PC SpeedStarlett-0005, 8.6.5. HCM:Update Applicant qualifications:00001561:PB30.....................39 Plant1000, SalOrg1000, Chnl10:VA01.........................................................31 8.6.6. HCM:Vacancy assignment:00001561:PB30.....................................39 7.4.4. MM:Check MRP Status:SpeedStarlett-0005, Basis-Modul2-0005, 8.6.7. HCM:Check Applicant activities:00001561:PB60.............................39 Plant1000:MD04...........................................................................................31 8.6.8. HCM:Evaluate Applicants:ProjMan=very high, Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage,Aaa|Bbb| -Menu/Submenu, SCR-Screen, FRM-Frame, IDUniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft CANAL notes, page: 3 KnowlExcelAboveAvg:PBAQ......................................................................39 BuinArea3000:S_ALR_87011965.................................................................48 8.6.9. HCM:Make Selction decision:00001561:PB60.................................40 9.9.3. FI: Display asset in Balance Sheet:Comp1000, 8.7. Hiring process...........................................................................................40 BuinArea3000:S_ALR_87012284.................................................................48 8.7.1. HCM:Prepare transfer of applicant data:00001561:PB40.................40 9.9.4. FI:Post Asset Acquisition:Buy Forklift-0005 from Vendor1000 for 8.7.2. HCM:Check Applicant activities:00001561:PB60.............................40 35000EUR+10%Tax:F-90.............................................................................48 8.7.3. HCM:Update Applicant master, infotypes bank details, 9.9.5. FI:Asset Explorer:Comp1000, 3414 0 (Forklift-0005):AW01N..........48 prev.employer, education:00001561:PB30...................................................40 9.10. Balance Sheet and Profit&Loss Statement.............................................48 8.7.4. HCM:Hiring Applicant:00001561:PBA7.............................................40 9.10.1. FI:Modify Balance Sheet and P&L Report structure:Acct900005 8.7.5. HCM:Display Personell master data:120005:PA30..........................41 FinStatmt INT:FSS0.................................................................................48 8.8. Personell planning&development..............................................................41 9.10.2. FI:Create Balance Sheet and P&L Report:Comp1000, FinStatmt 8.8.1. HCM:Update Position requirements profile:MA-DC-0005:PPPM.....41 INT:S_ALR_87012284..................................................................................48 8.8.2. HCM:Display Career opportunities:1000(Ms. Anja Mueller):PPCP. .41 10. Managerial Accounting Scenario....................................................................49 8.8.3. HCM:Positions succession planning suitable employees to fill a 10.1. Plot of Scenario.......................................................................................49 position:MA-DC-0005:PPSP.........................................................................41 10.1.1. Create master data..........................................................................49 8.8.4. HCM:Display profiles:(Ms. Schnuck):PPPD.....................................41 10.1.2. Cost Center Planning.......................................................................49 8.8.5. HCM:Proposed employees to position profile matchup reporting:(Ms. 10.1.3. Manual Expenses Posting...............................................................49 Mueller Ms. Scnuck):PEPM................................................................41 10.1.4. Internal Orders.................................................................................49 8.8.6. HCM:Create employee appraisal:120005(Gabor 10.1.5. CO-PC:Product Costing..................................................................49 Pauler):APPCREATE....................................................................................42 10.2. DEF:FI-CO:Managerial Accounting........................................................49 8.8.7. HCM:Modify employee appraisal:120005(Gabor 10.2.1. DEF:FI-CO:Managerial accounting/Controlling...............................49 Pauler):APPCHANGE...................................................................................42 10.3. CO:Data structures.................................................................................49 8.9. Training management...............................................................................42 10.3.1. DEF: CO-OM Master Data Groups.................................................49 8.9.1. HCM:Book training:120005(Gabor Pauler):PSV1.............................42 10.3.2. DEF:CO-OM Master Data: Cost objects.........................................50 8.9.2. HCM:Traveling cost:120005(Gabor Pauler)Walldorf:TRIP...........42 10.3.3. DEF:Statistical objects....................................................................50 9. Financial Accounting Scenario.........................................................................43 10.4. CO:Processes.........................................................................................50 9.1. Plot of Scenario.........................................................................................43 10.4.1. CYC:CO-OM:Cost Center Planning Overview................................50 9.1.1. General Ledger..................................................................................43 10.4.2. PROC:CO:Posting...........................................................................50 9.1.2. Accounts Payable..............................................................................43 10.4.3. PROC:CO:Cost Allocation...............................................................50 9.1.3. Accounts Receiveable.......................................................................43 10.4.4. PROC:CO:Internal Orders...............................................................50 9.1.4. Asset Accounting...............................................................................43 10.4.5. PROC:CO-PC:Product Costing.......................................................51 9.1.5. Balance Sheet and Profit&Loss Statement.......................................43 10.4.6. PROC:CO-PA:Profitability Analysis.................................................51 9.2. DEF:Structures of FI.................................................................................43 10.4.7. PROC:EC-PCA:Profit center accounting........................................51 9.2.1. DEF:Chart of Accounts......................................................................43 10.5. CO-OM:Create master data....................................................................51 9.2.2. DEF:FI-GL:General Ledger (G/L)......................................................43 10.5.1. CO:Create Cost center:CC-CA-0005(Cafteria):KS01:....................51 9.2.3. DEF:New SAP General Ledger.........................................................44 10.5.2. CO:Create Cost center: CC-MT-0005(Maintenance): KS01:.........51 9.3. TYPES:Accounting....................................................................................44 10.5.3. CO:Create Cost center: CC-MF-0005(Manufacturing): KS01:.......51 9.3.1. DEF:FI-FI:Financial accounting.........................................................44 10.5.4. CO:Create Statistical key Figure:EM0005(Employees):KK01........52 9.3.2. DEF:FI-CO:Managerial accounting/Controlling.................................44 10.5.5. CO:Create Secondary Cost Element:CAF-0005:KA06...................52 9.4. PROC:Accounting.....................................................................................44 10.5.6. CO:Create Secondary Cost Element: MNT-0005:KA06.................52 9.4.1. G/L Account posting document.........................................................44 10.5.7. CO:Create Secondary Cost Element: MFT-0005:KA06.................52 9.4.2. FI-AP:Accounts payable handling.....................................................44 10.5.8. CO:Create Activity Types:MT0005:KL01........................................52 9.4.3. FI-AR:Accounts Receiveable handling..............................................45 10.5.9. CO:Create Activity Types:MF0005:KL01........................................52 9.4.4. PROC:Asset Accounting...................................................................45 10.5.10. CO:Create Cost Center Gropup:Group-0005:KSH1.....................52 9.5. Customizing Organizational levels............................................................45 10.6. CO-OM:Cost Center Planning................................................................52 9.5.1. IMG:Display Currency:Company1000:SPRO...................................45 10.6.1. CO:Set Planner Profile:SAPALL:KP04............................................52 9.5.2. IMG:Display companies of:Controlling Area 1000:SPRO.................45 10.6.2. CO:Planning number of employees:EM0005=20 at CC-MF9.5.3. IMG:Display Fiscal Year variant:Controlling Area 1000:SPRO........46 0005:KP46.....................................................................................................52 9.5.4. IMG:Display Operating Concern:Controlling Area 1000:SPRO........46 10.6.3. CO:Planning number of employees:EM0005=5 at CC-MT9.5.5. IMG:Display Cost Center Accounting:ContArea1000:SPRO............46 0005:KP46.....................................................................................................52 9.6. General Ledger..........................................................................................46 10.6.4. CO:Planning Activity Output:MT0005=10000H at CC-MT9.6.1. IMG:Display Chart of Accounts:International(INT):SPRO................46 0005:KP26.....................................................................................................52 9.6.2. IMG:Display Chart of Accounts:Company1000:SPRO.....................46 10.6.5. CO:Planning Activity Output:MF0005=40000H at CC-MF9.6.3. IMG:Display Chart of Accounts:ContrArea1000:SPRO....................46 0005:KP26.....................................................................................................52 9.6.4. FI:Display Accounts in Chart of Accounts:International(INT):F.10...46 10.6.6. CO:Planning Primary Cost Input:417000(PurchServ)=150000EUR 9.6.5. FI:Create G/L account in Chart of Account:CONS|312600| at CC-CA-0005:KP06....................................................................................52 900005INT:FSP0......................................................................................46 10.6.7. CO:Planning Primary Cost Input:430000(Salaries)=150000EUR at 9.6.6. FI:Create G/L account:Company1000|900005:FSS0.......................46 CC-MT-0005:KP06........................................................................................52 9.6.7. FI:Enter G/L Account Document:Credit:113000Bank Debit:900005 10.6.8. CO:Planning Primary Cost 5000EUR:FB50.............................................................................................46 Input:420000(DirectLabour)=600000EUR at CC-MF-0005|MF0005:KP06..52 9.6.8. FI:Check Account:Comp1000|Acct900005:FS10N...........................47 10.6.9. CO:Planning Activity Input transfer:CC-MT9.7. Accounts Payable.....................................................................................47 0005MT0005=1000HCC-MF-0005:KP06.............................................53 9.7.1. FI:Enter Vendor Invoice:Vend100268 10000EUR to CCMSD10.6.10. CO:Check Planning:CC-CA-0005, CC-MT-0005, CC-MF0005:FB60.....................................................................................................47 0005:KSBL....................................................................................................53 9.7.2. FI:Display open items at Vendor Invoice:Comp1000, 10.6.11. CO:Plan cafeteria cost assessment: CC-CA-0005|CAFVend100268:FBL1N......................................................................................47 0005=150000EUR Group-0005|by EM0005:KSUB..................................53 9.7.3. FI:Automatic payment run:Comp1000, Vend100268, next 10.6.12. CO:Auto price calculation of activity types:Group-0005:KSPI......53 month:F111...................................................................................................47 10.7. CO-OM:Posting Actual Expenses Manually...........................................53 9.7.4. FI:Display cleared items:Comp1000, Vend100268:FBL1N..............47 10.7.1. CO:Plan/Actual comparison:Group-0005: S_ALR_87013611.........53 9.7.5. FI:Display cleared items:ReconcAcct160000:FAGLB03..................47 10.7.2. CO:Direct activity allocation:CC-MT-0005MT0005=200HCC9.8. Accounts Receiveable...............................................................................47 MF-0005:KB21N...........................................................................................53 9.8.1. FI:Display customer with incomplete master data:Comp1000, 10.7.3. FI:Post external expenses: 417000(ExternServic)=12500EUR at Cust50005:F.32............................................................................................47 CC-CA-0005:FB50........................................................................................53 9.8.2. FI:Create Credit Management Master:Cust50005, TotLim:500000, 10.7.4. CO:Period-end closing assesment cycle:CC-CA-0005|CAFLimCredContArea1000:10000:FD32............................................................47 0005Group-0005|by EM0005:KSU5.........................................................54 9.8.3. SD:Create Sales Order:50005, 10PC SpeedStarlett-0005, Plant1000, 10.8. CO-OM-OPA:Internal Orders..................................................................54 SalOrg1000, Chnl10:VA01............................................................................47 10.8.1. CO:Create internal order:100291 at 4500(R&D):KO04...................54 9.8.4. FI:Release Blocked SD Document:Cust50005:VKM1......................48 10.8.2. MM:Purchase order:100PC Gearing-0005 from 100268:ME21N...54 9.9. Asset Accounting......................................................................................48 10.8.3. MM:Display Commitments:100291: S_ALR_87012999..................54 9.9.1. FI:Create Asset Master Record:Asset Forklift-0005 in CostCtr 10.8.4. MM:Goods Receipt for Order:4500017613:MIGO..........................54 CCMSD-0005:AS01......................................................................................48 10.8.5. CO:Direct activity allocation: CC-MF9.9.2. FI:Display asset in P&L statement:Comp1000, 0005MF0005=100H100291:KB21N.....................................................55 Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage, Aaa|Bbb| -Menu/Submenu, SCR-Screen, FRM-Frame, IDUniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft CANAL notes, page: 4 10.8.6. FI:Post expenses: CC-MF-0005|CostElmt420000=1845EUR, CC12.4.1. Scheduling...................................................................................63 MT-0005|CostElmt430000=3600EUR: FB50...............................................55 12.4.2. Resource and Cost planning.......................................................63 10.8.7. MM:Display Real Costs:100291: S_ALR_87012999......................55 12.4.3. Assigning Orders to project.........................................................64 10.8.8. CO:Add cost element MF-0005 to allocation cost element group 12.4.4. CYC:Budgeting Approval............................................................64 OAS_ORDERS:KAH2...................................................................................55 12.4.5. Project Execution........................................................................64 10.8.9. CO:Settle internal order:100291:KO88............................................55 12.4.6. Project Billing...............................................................................64 10.9. EC-PCA:Profit Center Accounting..........................................................55 12.4.7. PS:Project Period end closing.....................................................64 10.9.1. EC-PCA:Profit Center Assignment Monitor:CC-MF-0005:1KE4....55 12.4.8. Project Reporting.............................................................................65 10.9.2. EC-PCA:Profit Center Report:PROF-0005:S_ALR_87009712.......55 12.5. LO-PS:Project GUI:.................................................................................65 10.10. CO-PA:Profitability analysis..................................................................55 12.5.1. LO-PS:Project Builder......................................................................65 10.10.1. CO-PA:Profitability analysis:SalesOrg1000:KE30........................55 12.5.2. LO-PS:Project Planning Board........................................................65 10.11. CO-PC:Product Costing........................................................................56 12.6. Enter master data:...................................................................................65 10.11.1. PP:Create new Work Center:PL-0005:CR01................................56 12.6.1. MM:Create Dummy material for project:Techno-0005:MMS1........65 10.11.2. PP:Integrate work center into Routing:PL-0005 SpeedStarlett12.6.2. CO:Create activity types:T-0005(Test driver):KL01........................65 0005:CA02....................................................................................................56 12.6.3. CO:Planning Activity Output/Prices:T-0005=100EUR/H at 10.11.3. CO:Run Product cost estimate:SpeedStarlett-0005:CK11N........56 4280(QualContr):KP26..................................................................................65 11. Enterprise Asset and Service Management Scenario....................................57 12.6.4. CO:Assign Act.Type T-0005 to Group:TestDriver: KLH2...............65 11.1. Plot of Scenario.......................................................................................57 12.6.5. HCM:Create personell master record:9900005:PA40.....................65 11.1.1. LO-PM:Corrective Maintenance......................................................57 12.6.6. HCM:Maintain Personell master data:9900005:PA30.....................66 11.1.2. LO-CS:Service Order Processing....................................................57 12.7. LO-PS:Create Project Structure, Sceduling, Resources:.......................66 11.2. Organizational levels of Maintenance and Service.................................57 12.7.1. LO-PS:Project Builder:A-10005:CJ20N...........................................66 11.2.1. Client................................................................................................57 12.8. LO-PS:Project planning:..........................................................................66 11.3. Data Structures of Maintenance and Service.........................................57 12.8.1. LO-PS:Auto Schedule Project:A-10005:CJ20N..............................66 11.3.1. DEF:Technical Objects Master.......................................................57 12.8.2. LO-PS:Manual Easy Cost Planning:WBS Blueprint by template 11.3.2. Equipment Install/Dismantle Goods movements............................58 ZPS101(Elevator):CJ20N.............................................................................66 11.4. PROC:LO-PM:Corrective Maintenance..................................................58 12.8.3. LO-PS:Automatic Network Costing:Prototype network:CJ20N......67 11.4.1. Notification list.............................................................................58 12.8.4. LO-PS:Graphical Project planning tools:A-10005:CJ20N...............67 11.4.2. Create Maintenance Order..........................................................58 12.8.5. LO-PS:Project release:A-10005:CJ20N..........................................67 11.4.3. Scheduling...................................................................................58 12.9. SD:Sales order management:.................................................................67 11.4.4. Execution and Completion..........................................................58 12.9.1. SD:Create Sales Order Milestone Billing:13488: Proj:A-10005 1PC 11.4.5. LO-PM-IS:Plant Maintenance Information System|History.............59 50000EUR for Cust:50005:VA01..................................................................67 11.5. PROC:LO-CS:Service Order...................................................................59 12.9.2. SD:Create Sales Order Resorce-related Billing:13489: 11.5.1. Create Service Notification .........................................................59 Mat:Testdriver1 1HR, 200EUR for Cust: 50005:VA01.................................67 11.5.2. Create Service Order..................................................................59 12.9.3. FI:Credit Management|Release orders manually:Cust:50005:VKM1 11.5.3. Service planning..........................................................................59 .......................................................................................................................68 11.5.4. Control.........................................................................................59 12.10. LO-PS:Project execution:......................................................................68 11.5.5. Execution.....................................................................................59 12.10.1. LO-CO:Manual Actual cost Allocation: CostCtr4290| 11.5.6. Completion..................................................................................59 ActTyp1429WBS:Blueprint 420H, CostCtr4290| 11.5.7. CS:Cost analysis.........................................................................59 ActTyp1430WBS:Blueprint 180H :KB21N................................................68 11.6. LO-PM:Display Master Data...................................................................60 12.10.2. LO-PS:Confirm&Release bill:WBS Blueprint:CJ20N....................68 11.6.1. LO-PM:Display Functional Locations: Plant1000|Sys00(Water 12.10.3. LO-PS:Auto entry Actual cost&Confirm&Bill: Netw:Prototype| clarification):IH06..........................................................................................60 Act:Specification=180HR, Act:Construction=270HR :CJ20N......................68 11.6.2. LO-PM:Display Equipment Master:TEQ-00:IE03............................60 12.10.4. HCM:Project hours:CostCtr:4280|ActTyp:T-0005| 11.7. LO-PM:Corrective Maintenance..............................................................60 Emp:9900005WBS:Special expenses 58HR:CAT2...............................68 11.7.1. LO-PM:Create Maintenance Request:00-B01|TEY-00|Frame:IW26 12.10.5. HCM:Transfer project hours to CO:Emp:9900005: CAT7............68 ......................................................................................................................60 12.11. SD:Billing:..............................................................................................68 11.7.2. LO-PM:Create Maintenance Order from request:817854:IW22.....60 12.11.1. SD:Milestone Billing:WBS Blueprint, WBS Prototype:VF04.........68 11.7.3. LO-PM:Run Plan/Actual Comparison Cost Analysis and 12.11.2. SD:Create Resource-related Billing Request:WBS:Special Release:817854:IW32..................................................................................60 expenses:DP91.............................................................................................68 11.7.4. LO-PM:Planned Material Withdrawal fro Maint.Order: 817854| 12.11.3. SD:Create Customer bill from Billing Request:WBS:Special Mat100-600(Support base):MB11.................................................................60 expenses:VF04.............................................................................................69 11.7.5. LO-PM:Maint.Order Confirmation:817854:IW42.............................60 12.12. LO-PS:Info system:...............................................................................69 11.7.6. LO-PM:Technical Completion and Cost Analysis of 12.12.1. LO-PS:Info system|Project cost/revenues:AMaintOrder:817854:IW32..............................................................................60 10005:S_ALR_87013531..............................................................................69 11.7.7. CO-OM:Cost Settlement of MaintOrder:817854:KO88...................61 11.7.8. LO-PM:Business Completion of MaintOrder:817854:IW32............61 11.7.9. LO-PM:Cost Reporting:817854:IW38..............................................61 11.7.10. LO-PM:Location Reporting:MaintPlant1000:MCI3........................61 11.8. LO-CS:Service Order Processing...........................................................61 11.8.1. LO-PM:Display Equipment Master:Cust:T-CSD00|Equip:TCSE100:IE03................................................................................................61 11.8.2. LO-CS:Create Service Order:502732:T-CSE100(server down):IW54 ......................................................................................................................61 11.8.3. LO-PM:Service Order Confirmation:502732:IW42..........................61 11.8.4. LO-CS:Service Order Billing:502732:DP90.....................................61 11.8.5. LO-CS:Display printed bill:90038160:VF03.....................................61 12. Project Management Scenario.......................................................................62 12.1. Plot of scenario:......................................................................................62 12.1.1. Enter master data:...........................................................................62 12.1.2. LO-PS:Create project structure.......................................................62 12.1.3. LO-PS:Project Planning...................................................................62 12.1.4. SD:Project Orders............................................................................62 12.1.5. LO-PS:Project execution.................................................................62 12.1.6. SD:Billing:........................................................................................62 12.2. LO-PS:Project Organization Structure:...................................................62 12.3. LO-PS:Project Master Data:...................................................................62 12.3.1. DEF:LO-PS:Project:........................................................................62 12.3.2. DEF:Work Breakdown Structure (WBS) Element:..........................62 12.3.3. DEF: Network:.................................................................................63 12.3.4. Related SD documents....................................................................63 12.4. PROC:LO-PS:Project:.............................................................................63 Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage,Aaa|Bbb| -Menu/Submenu, SCR-Screen, FRM-Frame, IDUniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox
1.Introduction
1.1.DEF: Enterprise Resource Planning (ERP)
- Manage all business processes inside a company and external links - On standardized computing platform consisting of separately installable modules - Supported by central data warehouse
1.2.SAP Architecture History 1.2.1.1972 SAP R/1, R/2 1.2.2.1992 SAP R/3
- Mainframe, central processing
- Client-server, 2 layer architecture - Real time appliaction - Did not support full integration of supply chain (suppliers/ vendors) - 2 layers can be upgraded only together! - Monolithic, applications are linked to business logic 1.2.2.1.Technology layer: SAP R/3 Basic 1.2.2.2.Application layer: 1.2.2.2.1.Finance modules - FI: Finance - CO: Controlling - TR: Treasury - IM: Investment management - PS: Project system 1.2.2.2.2.Logistic modules - SD: Sales distribution - MM: material management - PP: Production planning - QM: Quality management - PM: Plant management - HR: Human resource - IS: Industry solutions
- Full supply chain integration with external partners - Better management of upgrading layers 1.2.7.1.Technology layer: SAP NetWeaver 1.2.7.2.Application layer: 1.2.7.2.1.SAP R/3 Enterprise 1.2.7.2.2.Additional applications - Self service - Internet sales - Strategic enterprise 1.2.8.1.DEF: Service-oriented architecture (SOA) 1.2.8.1.1.DEF: Service: - Small, reusable part of business logic functionality - Often encapsulates parts of original R/3 modules/submodules 1.2.8.1.2.Protocols used in automatic communication of services - In order of usage, from top to down in hierarchy: 1.2.8.1.2.1.Universal Description Discovery Integration (UDDI): - Dictionary of business services to search a requested service eg. Credit-worthiness checking 1.2.8.1.2.2.Web Service Description Language (WSDL): - Stores I/O structures of the given service 1.2.8.1.2.3.Simple Object Access Protocol (SOAP): - Organizes function calls among services 1.2.8.1.2.4.Extended Markup Language (XML) - Content of I/O communication of function calls 1.2.8.1.2.5.Business Process Execution Language (BPEL) - Synchronizing process steps among services 1.2.8.1.3.DEF: Enterprise Service Architecture (ESA) - Hierarchy of protocols in auto-communication of services - From small units to large ones 1.2.8.1.3.1.Simple function - Piece of code 1.2.8.1.3.2.Web compatible function - Piece of code prepared to communicate through web 1.2.8.1.3.3.Application service - Given function running as web service on WebAS 1.2.8.1.3.4.Enterprise service - Grouping of the above by business processes 1.2.8.1.3.5.Composite application
1.2.3.1994 Win NT porting 1.2.4.1998 EnjoySAP: user friendly GUI 1.2.5.1999 MySAP: e-business 1.2.6.2002 SAP B1: for small companies 1.2.7.2003 SAP ERP
1.2.8.2008 SAP ERP 6.0
PaulerSoft CANAL notes, page: 5 - Grouping of the above by corporate functions (SD, FI, CO, etc.) 1.2.8.1.3.6.Packed Composite application - Distrubuted software package grouping of above by SAP 1.2.8.1.3.7.xApps - Same as above by SAP or external company. Not every part of SAP is transformed to xApp yet! 1.2.8.2.Technology layer: SAP NetWeaver - Opennes towards .Net, IBM, etc. - Instant integration, incereases Return on investment (ROI) - Lower total cost of ownment (TCO): easier upgrading 1.2.8.2.1.People integration: 1.2.8.2.1.1.SAP Enterprise Portal: - GUI - User accounts - Roles/Rights - Collaboration - Multi channel access (web, mobile) 1.2.8.2.2.Information integration: 1.2.8.2.2.1.Master Data Management (MDM): - Central data warehouse - Imp/Exp interfaces 1.2.8.2.2.2.Knowledge Management (KM) - Storing unstructured external text/image/sound, etc. Files 1.2.8.2.2.3.Business Intelligence (BI) - Reporting from MDM 1.2.8.2.3.Process integration: 1.2.8.2.3.1.Integration Broker - Synchronization of internal SAP components via ESA 1.2.8.2.3.2.Business Process Manager - Eclipse-based Business Process Diagrams (BPD) - Process monitioring 1.2.8.2.3.3.Exchange Infrastructure (XI) - DEF: Integration Repository : dictionary of protocls - DEF: Proxy: simulation of a protocol/document format in a given programming language - SAP-SAP: Idoc, remote function call (RFC) - SAP-External: Files, Java , http, SOAP, .Net - B2B: EDIFACT 1.2.8.2.4.Application integration: 1.2.8.2.4.1.Web Application Server (Web AS) - Handles basic applications of SAP can be found in all distributed SAP packages 1.2.8.2.4.2.Development tools: - Java - ABAP 1.2.8.2.4.3.Lifecycle management: for SAP components 1.2.8.3.Application layer: 1.2.8.3.1.SAP ERP Central Component (ECC) Solution Map: - Analitics flow: - StrategicFinancialOperationsWorkforce - Financial flow: - SCM financeFinac AcctMan AcctCorp.Gover - HR/HCM flow: - TalentWorkforce process Workforce deploy - Logistics flow: - ProcurementSupplierInventoryI/O logistTrans - Manufacturing flow: - PPManuf exeAsset manProd devLifecyc - Sales/Service flow: - OrderSalesServiceIncentives - Corporate service flow: - RealestProjectTravelEnvironQM 1.2.8.3.2.Additional applications - Self service - Internet sales - Strategic enterprise
Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage, Aaa|Bbb| -Menu/Submenu, SCR-Screen, FRM-Frame, IDUniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 1.2.8.4.SAP Product packages: 1.2.8.4.1.SAP Business Suite 1.2.8.4.1.1.ERP: Common basic applications 1.2.8.4.1.2.PLM: Project Lifecycle management 1.2.8.4.1.3.SCM: Supply Chain Management 1.2.8.4.1.4.SRM: Supplier Resource Management 1.2.8.4.1.5.CRM: Customer Relationship Management
PaulerSoft CANAL notes, page: 6 Goods Receipt FI: Invoice Receipt, verification FI: Payment 1.5.2.1.Ex stock sales - SD: Sales order 1.5.2.2.Sales on order - SD: Delivery note SD: Transport order MM: Goods receipt FI: Billing FI: Post payment
1.5.2.Order to Cash
1.3.SAP ERP Organizational hierarchy: Client/Mandant (901)

- Separate enterprise: - Legally, - Database structure, - Work area
1.5.3.Produce a service
- SD: Cost bearer SD: Sales order FI: Billing FI: Order settlement - From down to top
- Group of companies where creditworthiness of a customer is checked together 1.3.1.1.FI, CO: Company (1000) - Self contained set of bookkeeping accounts 1.3.1.1.1.FI, CO: Business Area - Product-based subgrouping of a company 1.3.1.1.2.FI, CO: Controling Area - Group of companies sharing costs and revenues 1.3.1.1.2.1.FI, CO: Operating Concerns - Standatdized sets of controling measures in a controling area reported together 1.3.1.1.3.LO: Plant - One company can have several branch plants - Central unit of logistics 1.3.1.1.3.1.MM: Storage location - Basic unit of inventory management 1.3.1.1.4.MM: Purchasing organization - Part of a company - Negotiates procorement and conditions with vendors 1.3.1.1.5.SD: Sales organization (1000-Frankfurt) - Part of a company, accounted at company level - Can sell products from multiple plants - Divided usually by regions 1.3.1.1.5.1.SD: Sales Office - There can be more sales office for a sales organization 1.3.1.1.6.SD: Distribution Channel (10-Final customers) - There can be more chanels 1.3.1.1.7.LO: Division/Product group (02-Bike, 03-Paint, 05Food) - Producs subject to common delivery and pricing terms for a given customer - Sold in a given distribution channel 1.3.1.1.7.1.SD,LO:Sales Area(1000-10-02,1000-10-03,1000-1005) - Combination of Sales Org Distribution channel Division 1.3.1.1.8.HR: Personell Area - HR Admin - Time management - Billing 1.3.1.1.8.1.HR: Personell Subarea - HR: Employee group: - Retirement and other conditions - HR: Employee subgroup:
1.3.1.FI, CO: Credit Control Area
1.6.SAP ERP Reporting hirearchy 1.6.1.On-Line Transaction Processing (OLTP)

- Operative environment: SD, MM, PP, FI, HR - Administrator Workbench (AWB): Monitoring
1.6.2.Data Warehousing (DW)
- Information environment 1.6.3.1.Logistic Information System (LIS) - Aggregate transaction data by - Time periods - Key figures 1.6.3.2.Sales Information Syste (SIS)
1.6.3.On-Line Analitical Processing (OLAP)
1.7.SAP model company: Internet demonstration and evaluation system (IDES) 1.7.1.Organizational structure 1.7.2.Customizing 1.7.3.Master data 1.7.4.Transaction data 1.7.5.Business processes 1.7.6.Tutorials 1.8.SAP GUI 7.2 For Win7 1.8.1.Menu bar
1.8.1.1.Extras| 1.8.1.1.1.Settings| 1.8.1.1.1.1.Display technical names: - Shows transaction codes in SAP menu 1.8.1.2.Help| 1.8.1.2.1.Application help: Local 1.8.1.2.2.SAP Library: On-line
1.4.SAP ERP Data Structure 1.4.1.DEF: Master data
- Permanent data in time, mor general 1.4.1.1.Customer data - ID - Client - Company - Sales area - Bookkeeping account 1.4.1.2.Material data 1.4.1.3.Vendor data 1.4.2.1.DEF: Transaction: program running business logic 1.4.2.2.DEF: Document: record generated by transaction 1.4.2.2.1.Master reference part - Any document can be created only referencing pre-defined master data 1.4.2.2.2.Transaction part - Rapidly changing data in time, more specific
1.8.2.1.TBX:Transaction code box 1.8.2.1.1.SEARCH_SAP_MENU 1.8.2.2.BTN:Back screen 1.8.2.3.BTN:Up screen 1.8.2.4.BTN:Abort transaction 1.8.2.5.BTN:New modus 1.8.2.6.BTN:Shortcut - Place shortcut of transaction on desktop 1.8.2.7.BTN:Help 1.8.2.8.BTN:Settings 1.8.2.8.1.Options| 1.8.2.8.1.1.Design visualization| - Show keys in dropdown lists: displays technical codes in dropdown lists!
1.8.2.Function button bar
1.8.5.1.Favorites
1.8.3.Application title bar 1.8.4.Application function button bar 1.8.5.SAP Easy Access menu 1.8.6.Application work area 1.8.7.Status bar 1.8.8.Hot keys
1.4.2.Transactions data
1.8.8.1.KEY:F1:Cursor specific help 1.8.8.2.KEY:F4:Dropdown list of fill aid
1.5.SAP ERP Process examples 1.5.1.Purchase to pay
- Algorithms of transactions involving several modules - MM: Material requirement MM: Purchase Order MM:
Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage,Aaa|Bbb| -Menu/Submenu, SCR-Screen, FRM-Frame, IDUniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox
PaulerSoft CANAL notes, page: 7 - DEF: Description of a theoretically described material to be purchased - LO|MM|Material master|Material|Create special| 2.4.1.1.|MMF1 Finished product: Speedstar-0005: - SCR:Start: - TBX:Material = Speedstar-0005 - DDN:Sector = Mechanical engineering - BTN:View selection - SCR:Organization - DDN:Plant = 1000 - DDN:Chanel = 10 - DDN:Storage =0001 - DDN:SalesOrg = 1000 2.4.1.1.1.Client: TAB:Basic data 1 - DDN:Material Description = Speedstar-0005 - DDN:Unit of Measure = PC (piece) - DDN:Division = 00 (cross-division) - TBX:Gross weight = 18 KG - TBX:Net weight = 15 2.4.1.1.2.Client: TAB:Basic data 2 2.4.1.1.3.SalesOrg: TAB:Sales 1 - DDN: Deliv plant = 1000 - DDN: Tax = 1 (full) 2.4.1.1.4.SalesOrg: TAB:Sales 2 2.4.1.1.5.SalesOrg: TAB:Sales General - DDN:TransGrp = 0001(Pallet) - DDN:LoadGrp = 0002(Forklift) 2.4.1.1.6.Company|Plant: TAB:MRP 1 - DDN:MRP type = PD (Material Requirements Planning) - DDN:MRP controller = 001 (Disponent 001) - DDN:Lot size = EX (Lot-for-lot order quantity) 2.4.1.1.7.Company|Plant: TAB:MRP 2 - DDN:Procurement type = E (in-house production) - DDN:In-house production = 5 days - DDN:SchedMargin key = 000 - DDN:Prod.stor.location = 0001 2.4.1.1.8.Company|Plant: TAB:MRP 3 - DDN:Tot.repl. lead time = 15 days - DDN:Availability check = 02 (individual requirement) 2.4.1.1.9.Company|Plant: TAB:MRP 4 2.4.1.1.10.Company: TAB:Work scheduling - DDN:Prod.stor.loc. = 0001 2.4.1.1.11.Company: TAB:Accounting 1 - DDN:Price control = S (Standard price) - DDN:Standard price = 3000 - DDN:Valuation class = 7920 (finished products) 2.4.1.1.12.Company: TAB:Accounting 2 2.4.1.1.13.Company: TAB:Costing 1 - CHK:Material Origin = True - CHK:With Quantity Structure = True 2.4.1.1.14.Company: TAB:Costing 2 - Other views of material master record, which are not created now: - In case of forgetting creating a view, re use MM01 for the material instead trying to modify at MM02! 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.PurchOrg: Purchasing data 2.4.1.1.19.Company: Quality management 2.4.1.1.20.Company: Forecasting 2.4.1.1.21.Company: Classification 2.4.1.1.22.BTN:Additional data - DDN:Language = DE - TBX:Description = Speedstar-0005 2.4.1.1.23.BTN:Save
2.Procurement scenario
2.4.1.MM: Create Material Master:MM01
- DEF: Scenarios are case studies to practice business processes
2.1.Organizational environment 2.1.1.Client: 901
2.1.1.1.FI: Company: - 1000-Frankfurt - 2000-UK 2.1.1.1.1.LO: Plant: - 1000-Hamburg - 1100-Berlin - 2000-Heathrow 2.1.1.1.1.1.LO: Storage: - 0001-Hamburg - 0002-Hamburg - 0001-Berlin - 0002-Berlin - 0003-Berlin 2.1.1.1.2.MM: Purchasing organization: - Procurement organizational unit, which negotiates pricing conditions 2.1.1.1.2.1.Plant-specific: - A-Plant1000 - B-Plant1100 2.1.1.1.2.2.Cross-plant, one company: - 1000-Company1000 2.1.1.1.2.3.Cross-company: - C100-Company1000, 2000, 3000 2.1.1.2.MM: Purchasing group: - Group of purchasers dealing with purchasing the same materials regardless company and purchasing organization
2.2.Setting organizational structure in customizing 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.1.1.Definition| - FI Financial accounting| - Edit Company| - Company code, Name, Address, Currency, Language - LO Logistics general| - Define Plant| - Plant code, Name, Address, Taxing, Calendar(for handling working days) - MM Material management| - Maintain purchase organizations| - Code, Description - Maintain storage locations|Plant code|-instant assign! - Code, Description 2.2.1.1.1.2.Assignment| - LO Logistic general| - Plant to company| - MM Material management| - Purchasing org to company| -Empty for cross-company purcahsing org!
2.3.Plot/Preconditions of the scenario 2.3.1.Finished product: Speedstar-0005
2.3.1.1.At organization 2.3.1.1.1.Client: 901 2.3.1.1.1.1.Company: 1000 - Channel: 10 - Storage: 0001 - SalesOrg: 1000 - Cotrolling area: 1000 2.3.1.2.Bill of material (BOM) 2.3.1.2.1.1pcs Semi finished: Basis-Module-0005 2.3.1.2.1.1.1pcs Raw mat: Carb-Frame-0005: Order 2.3.1.2.1.2.2pcs Raw mat: Wheel-0005: Order 2.3.1.2.1.3.1pcs Raw mat: Chain-0005: Order 2.3.1.2.1.4.1pcs Trading good: Gearing-0005: Order 2.3.1.2.2.2pcs Raw mat:Pedal: On stock 2.3.1.2.3.2pcs Raw mat:Brakes: On stock 2.3.1.2.4.1pcs Raw mat:Handlebar: On stock 2.3.1.2.5.1pcs Raw mat:Saddle: On stock 2.3.1.3.Task - Order missing parts - Prefixes signal the corresponding organizational level of data and GUI part to launch their view!
2.4.Master data
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 2.4.1.2.|MMB1 Semi-Finished product: Basis-Module-0005 - Only differences from previos shown! 2.4.1.2.1.TAB:Basic Data 1 - DDN:Material Description = Basis-Module-0005 - TBX:Gross weight = 13KG - TBX:Net weight = 11 2.4.1.2.2.TAB:MRP 2 - TBX:In-house production = 3 days 2.4.1.2.3.TAB:Accounting 1 - DDN:Standard price = 2000 - DDN:Valuation class = 7900 (semi finished products) 2.4.1.3.|MMR1 Raw material: Carb-Frame-0005 - Only differences from previos shown! 2.4.1.3.1.TAB:Basic Data 1 - DDN:Material Description = Carb-Frame-0005 - DDN:Material Group = 020(vehicle) - TBX:Gross weight = N/A - TBX:Net weight = N/A 2.4.1.3.2.TAB:Purchasing - DDN:PurchasingGrp = 000(Chef) 2.4.1.3.3.TAB:MRP 2 - DDN:Procurement type = F (External) - TBX:Planned delivery time = 3 days - DDN:Stor.location = 0001 2.4.1.3.4.TAB:Accounting 1 - DDN:Standard price = 750 - DDN:Valuation class = 3000 (raw materials) 2.4.1.4.|MMR1 Raw material: Wheel-0005 - Only differences from previos shown! - Use the previous as Reference material on start screen! 2.4.1.4.1.TAB:Basic Data 1 - DDN:Material Description = Wheel-0005 2.4.1.4.2.TAB:Accounting 1 - DDN:Standard price = 100 2.4.1.5.|MMR1 Raw material: Chain-0005 - Only differences from previos shown! - Use the previous as Reference material on start screen! 2.4.1.5.1.TAB:Basic Data 1 - DDN:Material Description = Chain-0005 2.4.1.5.2.TAB:MRP 2 - TBX:Planned delivery time = 4 days 2.4.1.5.3.TAB:Accounting 1 - DDN:Standard price = 75 2.4.1.6.|MMH1 Trading good: Gearing-0005 - DEF: Highly standardized products - Only differences from previos shown! 2.4.1.6.1.TAB:Basic Data 1 - DDN:Material Description = Gearing-0005 2.4.1.6.2.TAB:MRP 2 - TBX:Planned delivery time = 6 days 2.4.1.6.3.TAB:Accounting 1 - DDN:Standard price = 500 - DDN:Valuation class = 3100(Finished prod)
PaulerSoft CANAL notes, page: 8 2.4.4.2.Client:TAB:Control - TBX:VAT reg. no. = DE987654321 - DDN:Industry = TRAD 2.4.4.3.Client:TAB:Payment Transaction - FRM:Alternative payee - RAD:Individual spec = True 2.4.4.4.Client:TAB:Contact 2.4.4.5.Company:TAB:Accounting Info Accounting - DDN:Recon. Account = 160000 - DDN:Sort key = 002 - DDN:Cash mgmnt group = A1 - DDN:Release group = 1000 - DDN:Interest indic. = 02 - DDN:Interest freq. = 1 2.4.4.6.Company:TAB:Payment Transaction Accounting - DDN:Paymnt terms = 0001 - DDN:Tolerance group = 1000 - CHK:Double inv. = True - DDN:Payment methods = SU 2.4.4.7.Company:TAB:Correspondence 2.4.4.8.PurchOrg|Plant|VendorSubRange: TAB:Purchasing data - DDN:Order currency = EUR - DDN:Terms of payment = 0001 - DDN:Incoterms = EXW - TBX:Salesperson = Mr. Schneider - TBX:Telephone = 010/32323 - CHK:GR based inv. verif. = True - DDN:ABC indicator = A - CHK:Automatic purchase order = True 2.4.4.9.BTN:Save - Take note of assigned Vendor ID: 100268 from stausbar - DEF: Description of a given material can be purchased from given vendor - LO|MM|Purchasing|Master data|Info record|ME11 Create - SCR:Start 2.4.5.1.Carb-Frame-0005: - DDN:Vendor number = 100268 - DDN:Material = Carb-Frame-0005 - DDN:Purchasing Org. = 1000 - DDN:Plant = 1000 - TBX:Info record = - Leave empty! - FRM:InfoCtegory - RAD:Standard = True 2.4.5.1.1.Material|Vendor:TAB:General data - Data here are merged from material master and vendor: - Price history, discount, freight payment - Delivery time and tolerance, Texts - Do not change it! 2.4.5.1.1.1.Material|Vendor:BTN:PurchOrgData1 - TBX:Standard Quantity = 100 pieces - TBX:Net price = 750 EURO - Material|Vendor|PurchOrg:BTN:Conditions: - DEF: Set of rules describing the actual price/properties of a given material in a purchasing order purchased by given purchasing org from a given vendor in a given contract - LIN:Condition type:PB00 - DEF: Different types of conditions can be bound to different objects: - PB00:Purchasing Info Records : Vendor material type - Contract: All purchased items of an order - Extra conditions: Flexibly can be bound to anything - BTN:Scales - DEF:Lookup table of quantity discount prices/tresholds - LIN1:Quantity=1, Amount=750 - LIN2:Quantity=500, Amount=650 2.4.5.1.2.BTN:Save - Take note of assigned Info record ID: 5300006197 from stausbar 2.4.5.2.Wheel-0005:1pc-100EUR,1000pc-80EUR: 5300006198 2.4.5.3.Chain-0005:1pc -75EUR,500pc-65EUR: 5300006199 2.4.5.4.Gearing-0005:1pc -500EUR,500pc-450EUR: 5300006200
2.4.5.MM: Create Purchasing Info records:ME11
2.4.2.MM: Display material list: MM60
- LO|MM|Material master|Other|MM60 Material list| - SCR:Start - DDN:Created by = WIP-00-05 LO|MM|Material master|Material|Change|MM02 Immediately| - SCR:Start - DDN:Material = Speedstar-00-05
2.4.3.MM: Modify materials: MM02
- DEF: Description of the companys crediting partner - LO|MM|Purchasing|Master data|Vendor|Central|XK01 Create| - SCR:Start - DDN:Company = 1000 - DDN:PurchOrg = 1000 - DDN:AccountGrp = KRED - TBX:Vendor = - Leave empty, automatic assignment! - WRN: Ignore! 2.4.4.1.Client:TAB:Address - TBX:Name = Gabor Pauler - TBX:Search term = Gabor Pauler - TBX:Street = University Street - TBX:House number = 9 - TBX:Postal code = 45141 - TBX:City = Essen - TBX:Country = DE
2.4.4.MM: Create Vendor Master: XK01
2.5.Procurement process 2.5.1.MM: Create Purchasing Requisition:ME51N
2.5.1.1.DEF: Standard Purchase Requisition Process - Quantified requirement for purchasing a given material - Coming from the following sources: 2.5.1.1.1.Manual entry - By procurement agent of material (Purchasing group = 000) 2.5.1.1.2.Material Requirement Planning (MRP) - If MRP method = PD set for the material, SAP automatically calculates material requirement from its requisition quantity with the help of Bill Of Material (BOM) - And considers possible sources of material: - 1. Stock available - 2. Own production if Method = X (both external/internal production) is set - 3. Then purchasing requirement is computed and reqest for quotation (RFQ) is sent to vendors 2.5.1.1.3.Supply Chain Management (SCM)|Advanced Planning Optimization (APO) - This module sold separately from SAP ERP 2.5.1.1.4.Supplier Relationship Management (SRM)|Enterprise Buyer Professional (EBP) - This module sold separately from SAP ERP 2.5.1.2.DEF: Special Purchase Requirement: Consumable goods - DEF: Purchased materials do not form valuated inventory, - Their value is booked manually/automatically directly to some Account assignment category: - A: Asset - K: Cost center - P: Project - F: Production order - C: Sales order - Within that, a manually/automatically assigned stock/consumption account 2.5.1.2.1.ALT:Without material master record - All these fields are entered at order manually: - Text, Material group, Order measure unit, - Account assignment and its category, 2.5.1.2.2.ALT:With material master record - It always has automatic account assignment in material master 2.5.1.2.2.1.ALT:Material type: Non-stock material (NLAG): - quantity and value are not updated 2.5.1.2.2.2.ALT:Material type: Non-valuated material (UNBW): - quantity is updated, but value is not. 2.5.1.3.LO|MM|Purchasing|Purchasing requisition|ME51N Create| 2.5.1.3.1.SCR:Main 2.5.1.3.1.1.BTN:Item oveview on - Fill columns linewise left to right otherwise will not work! LI AccAss Material Q Date Pla N Cat u nt a nt 1 Gearing10 Now+1 10 0005 0 wk 00 2 K(Cost Gearing10 Now+1 10 cent) 0005 wk 00 This is purchased as commodity, therefore setting the account assignment is required! FRM:Item TAB:Account assignment DDN:Cost center = 4298(Engineering test bench) - WRN:If dates on weekend: Ignore, weekend will work! 2.5.1.3.1.2.BTN:Save - Take note of assigned Purchase requisition ID: 10013838 2.5.2.1.DEF:Purchasing Order(PO): - Document detailing materials to purchase in given quantities at given prices/conditions from given vendors 2.5.2.1.1.Ways of creation: 2.5.2.1.1.1.ALT:Manually by purchaser 2.5.2.1.1.2.ALT:From rference to purchasing requisition: - Purchaser/ or SAP automatically selects best price bidding vendors by their Purchase Info Record|Conditons, for others rejection letter is posted automathically - Or Purchaser creates individual Outline Agreement with vendor 2.5.2.1.1.3.ALT:From reference to another purcasing order - Reduces the need of data entry work at repeating orders 2.5.2.1.2.Data sources - Material master
PaulerSoft CANAL notes, page: 9 - Vendor - Info record 2.5.2.1.3.Content: 2.5.2.1.3.1.Header: Whole order related data 2.5.2.1.3.2.Items: Material related data - Item category: - ALT:Standard - ALT:Subcontract: vendor delivers finished goods - ALT:Consignment: Vendor keeps inventory of finshed goods in our stock, liability arises taking out from it - ALT:Stock-transport: goods movement between two of our plant stock locations - ALT:Third paty : Vendor will directly deliver to third party end costumer - Material - Quantity - UnitPrice - Conditions 2.5.2.1.4.Purchase order can be sent to: - ALT:Vendor - ALT:Another plants stock transfer 2.5.2.1.5.Goods can be delivered to: - ALT: Plant - ALT: Place of consumption for consumable goods 2.5.2.2.LO|MM|Purchasing|Purchasing order|Create|ME21N Vendor known| 2.5.2.2.1.SCR:Main 2.5.2.2.1.1.BTN: Document overview on 2.5.2.2.1.2.FRM:Document overview(left panel) - BTN: Selection variant |My purchase requisitions - LIN: Previously created purchase requistiton: 10013838 Do not doubleclick to read contents! - BTN: Adopt: Copies data to purchase order 2.5.2.2.1.3.ERR:Data missing - DDN:Vendor = 100268 - DDN:PurchOrg = 1000 2.5.2.2.1.4.WRN:Discount available from 500:Skip! 2.5.2.2.1.5.BTN:Items detail:Check items are there! 2.5.2.2.1.6.BTN:Save 2.5.2.2.1.7.WRN:Message cannot be issued: Skip! - Take note of assigned Purchase order ID: 4500017337 2.5.3.1.LO|MM|Purchasing|Purchasing order|ME23N Display 2.5.3.1.1.SCR:Main 2.5.3.1.1.1.BTN: Document overview on 2.5.3.1.1.2.FRM:Document overview(left panel) - BTN: Selection variant |My purchase orders - LIN: Previously created purchase order: 4500017337 2.5.3.1.1.3.FRM:Header: - TAB:Status: Check status of order! 2.5.3.1.1.4.FRM:Item: - TAB:Delivery schedule: - LIN1:PurchaseReq.=10013838Check correct reference! - TAB:Purchase order history: here one can see history of all operations done with the item later - DEF: Appearence of a purchasing order in a given communication channel (e-mail, fax, etc). It can be customized channelwise - LO|MM|Purchasing|Purchasing order|Message|ME9F Print| - SCR:Start - DDN:Purchase order = 4500017337 - DDN:PurchOrg = 1000 2.5.4.1.SCR:Main - LIN:Purchase order = 4500017337 - BTN:Display message
2.5.3.MM: Display Purchasing Order:ME23N
2.5.4.MM: Display Messages:ME9F
2.5.2.MM: Create Purchasing Order:ME21N
2.5.5.MM: Processing status of purchase requisition:ME53N
- DEF: The purchaser can track purchasing process in time - LO|MM|Purchasing|Purchasing requistion|ME53N Display| - SCR:Main - FRM:Overview - LIN: Purchase requistion = 10013838 - FRM:Items - TAB:Status: Observe status of orders!
2.6.Goods processing 2.6.1.DEF: Stock Usability Types:
2.6.1.1.ALT:Unrestricted 2.6.1.2.ALT:Quality inspection 2.6.1.2.1.ALT:Material master-based: - Material regularly inspected, set at: - MM01|TAB:Purchasing|CHK:Post to insp. Stock = True 2.6.1.2.2.ALT:Purchase/Production order-based: - Material inspected only once, set at: - Purchase/Production Order|Stock type|Quality inspection 2.6.1.3.ALT:Blocked 2.6.2.1.DEF: Material documents - At least one is created for all types of material movement - Primary key: MatDocNumber + MaterialYear - Header: contains general data - Items: contain material related data 2.6.2.1.1.ALT:Goods receipt: - Comes from a vendor or internal production - Increases stock - Performs important auxiliary functions: - The system proposes quantity of materials ordered from rferenced purchase/production order - The receiving department checks under/over delivery and vendor/producing plant is dunned if there is any - Order history updated - Quality inspection lot defined - Warehouse transport requirement created - Output is printed: eg. Goods receipt as pallet label - Stock level updated - Vendor/producing plant notified back 2.6.2.1.2.ALT:Goods issue: - For material issue from stock/consumption/consignment - Decreases stock 2.6.2.1.3.ALT:Stock transfer: - Inter-plant physical stock movement 2.6.2.1.4.ALT:Transfer posting: - Non-physical stock movement within one plants storages - Among different usability types 2.6.2.2.DEF: Accounting documents - They created only if valued stock moves, simultaneously with material document - But they are independent documents. Corresponding material and accounting documents are linked through they are referencing the same source document (eg. Delivery Note) - Primary key: Company+AcctDocNum+FiscalYear - Header: contain general data - Items: contain General ledger (G/L) account numbers and amounts 2.6.3.1.DEF: Stock movement type - 3-digit codes of all stock movement (material/nonmaterial, valued/nonvalued) which control accounting and material document display layout. They can be set at: 2.6.3.2.LO|MM|Purchasing|Purchasing order|ME23N Display 2.6.3.2.1.FRM:Item| 2.6.3.2.1.1.LIN##| - TAB:Delivery| - Transaction type = - (101)Goods receipt for purchase order - (122)Return delivery to vendor - (201)Goods receipt for a cost center - (301)Transfer posting - (321)QualInspectUnrestricted - (322) UnrestrictedQualInspect - (343) Blocked Unrestricted - (344) Unrestricted Blocked - (349) Blocked QualInspect - (350) QualInspect Blocked - (501)Goods receipt without purchase order 2.6.4.1.DEF: Stock Overview - Static report of material stock materials (does not show planned purchases in time) - Broken up in the following hierarchy: Client|Company|Plant| Storage - ALT:Usability type - ALT:Production batch - ALT:Stock Movement Transaction type - ALT:Special types (eg. Consignment)
PaulerSoft CANAL notes, page: 10 - Can be displayed in several layouts set in customizing 2.6.4.2.LO|MM|Inventory|Environment|Stock|MMBE Stock Overview| 2.6.4.2.1.SCR:Start - DDN:Material = Gearing-0005 - DDN:Plant = 1000, BTN:Run 2.6.4.2.2.SCR:Main:Check out stock types/levels! - DEF:Acknowledgement that vendor delivered the order - LO|MM|Inventory|Goods movement|Goods receipt|For purchase order|MIGO PO number known| 2.6.5.1.SCR:Main: 2.6.5.1.1.FRM:Header: - DDN:Operation = A01(Create goods receipt) - DDN:Reference doc type = R01(Purchase order) - TBX:Reference doc number = 4500017337 2.6.5.1.1.1.TAB:General: - TBX:Document date = Now - TBX:Delivery date = Now - DDN:Delivery note = * (No delivery note) 2.6.5.1.2.FRM:Items: 2.6.5.1.2.1.LIN1:100pc Gearing-0005 - FRM:Item Detail - TAB:Where - DDN:Stock type = 2(Quality inspection) 100pc gearings are quality inspected before putting on unrestricted stock - DDN:StoreLoc = 0001 - CHK:ItemOK = True 2.6.5.1.3.BTN:Save - Take note of assigned Goods receipt ID: 5000012369 - LO|MM|Inventory|Goods movement|Goods receipt|For purchase order|MIGO PO number known| 2.6.6.1.SCR:Main: 2.6.6.1.1.FRM:Header: - DDN:Operation = A04(Display) - DDN:Reference doc type = R02(Material document) - TBX:Reference doc number = 5000012369 - BTN:Run 2.6.6.1.1.1.TAB:DocInfo - BTN:FI Documents - DDN:Documents in accounting = Accounting document - Check booked accounts! 2.6.6.1.2.FRM:Items: 2.6.6.1.2.1.LIN1:100pc Gearing-0005 - FRM:Item Detail: - TAB:Where: - BTN:View:Shows stock overview with changes
2.6.5.MM: Post Goods Receipt:MIGO
2.6.2.DEF: Goods movement documents:
2.6.6.MM: Display Material/Accounting Document:MIGO
2.6.3.MM:Checking stock movement types:ME23N
2.6.7.MM: Material transfers in unrestricted use stock:MIGO
- DEF: It is necessary after the delivery inspected and found OK. - LO|MM|Inventory|Goods movement|Goods receipt|For purchase order|MIGO PO number known| 2.6.7.1.SCR:Main: 2.6.7.1.1.FRM:Header: - DDN:Operation = A08(Transfer posting) - DDN:Reference doc type = R10(Other) - DDN:Movement type = 321 2.6.7.1.1.1.TAB:Transfer posting - FRM:From and FRM:Dest : - DDN:Material = Gearing-0005 - DDN:Plant = 1000 - DDN:Storage Location = 0001 - DDN:Unit of Entry = 100pc, KEY:Enter 2.6.7.1.2.BTN:Post:MIGO may give false errors if you do not click things EXACTLY in the sequence above, restart it! - Take note of assigned Material movement ID: 4900038343
2.6.4.MM:Check Stock Overview:MMBE
2.6.8.MM: Display new Material Document:MIGO 2.6.9.MM: Display Stock Overview:MMBE 2.6.10.MM: Display Order History:ME23N
PaulerSoft CANAL notes, page: 11 2.7.4.1.DEF:Payment - ALT:Manual outgoing payment - Select payment method and bank - Select items to pay - Calculate pay amount with cash discounts - Post payment document - Print payment medium - ALT:Automatic outgoing payment 2.7.4.2.Accounting|FI|Accounts payable|Document entry| Outgoing|F58 Post+Print Forms 2.7.4.2.1.SCR:Header data - DDN:Company code = 1000 - DDN:Payment method = C(Check) - DDN:House bank = 1000 - DDN:Check lot number = 0001 - DDN:Printer for forms = LOCL(Standard local printer) - CHK:Print immediately = True 2.7.4.2.1.1.BTN:Enter payments: - TBX:Amount = 59500 - DDN:Vendor = 100268 2.7.4.2.1.2.BTN:Process open items: - Check open positions list! 2.7.4.2.1.3.BTN:Save - Take note of assigned Payment document ID: 1500000001
2.7.Invoice processing 2.7.1.MM: Enter Vendor Invoice:MIRO
2.7.4.FI: Payment:F58
- Plot: Vendor submits an invoice of 55.000 EURO (500 * 110 PC Gearing-0005) plus 10.450 EURO (19 % VAT) 2.7.1.1.PRC: Invoice verification - Invoice is checked formally and by content (quantity, unit price, tax) comparing: - Vendor invoice - Referenced document. It can be: - ALT:Purchase Order: Always settles the whole order, irrespective to partial delivery - ALT:Delivery Note: - ALT:Goods Receipt: Always settles only that part of the order what was received on it, quantity cannot be more! - ALT:In case of variance, invoice gets blocked - ALT:If material is moving average price valued: in material master, moving average price is recalculatedInvoice is revalued with new price altered quantity - ALT:If material is standard valuedInvoice is re-valued with altered quantity - ALT:If everything is OK, invoice is posted to SAP FI and CO: - Provisional liability stored in Goods Receipt (GR)/Invoice Receipt (IR) account from issuing goods receipt is cleared as - Invoice Receipt is issued as proof of liability towards vendor - Vendor account will have a new open item - Accounting document is prepared - Purchase Requistion History is updated with invoice document 2.7.1.2.LO|MM|Logistics invoice verification|Document entry| MIRO Enter Invoice| 2.7.1.2.1.SCR:Start: - DDN:Company = 1000 2.7.1.2.2.SCR:Main: 2.7.1.2.2.1.TAB:Basic data: - TBX:Invoice date = Now - TBX:Posting date = Now - TBX:Amount = 59500 EUR - CHK:Calculate tax = True - DDN:Tax code = VA(domestic input tax 19%) 2.7.1.2.2.2.TAB:PO Reference - DDN:Reference document = 1(Purchase order) - TBX:Reference document number = 4500017337 - KEY:Enter:amount with tax recomputed correctly 2.7.1.2.2.3.BTN:Save - Take note of assigned Invoice document ID: 5105608892
2.7.5.Checking paid items:FBL1N 2.8.Cross-module integration of MM:Procurement 2.8.1.Financial accounting (FI): Invoice accounting documents:
- Account 160000:Reconciliation account for all vendors, paired with that - Sub-ledger creditor accounts are defined for each vendor at vendor master - Can result in purchase requisition if sold finished products and its parts through BOM ar not in stock - Can result purchase requistions if semi-finished goods or raw material are not in stock - Goods receipt can contain reference to a BOM: eg. a raw material is ordered andelivered because BOM of finished product requires it - Maintenance can hold back spare parts from these - While inventory management only contains material type and quantity info - It adds handling and storage place allocation data
2.8.2.Sales&Distribution (SD): Sales order 2.8.3.Production Planning(PP): 2.8.4.Maintenance( MT):
2.8.5.Warehouse Management System (WMS)
2.7.2.MM: Display Invoice Document and Order History:MIRO
2.7.2.1.LO|MM|Logistics invoice verification|Document entry| MIRO Enter Invoice| 2.7.2.1.1.SCR:Start: - DDN:Company = 1000 2.7.2.1.2.SCR:Main: - DDN:Transaction = 1 Invoice - TBX:Invoice number = 5105608892 2.7.2.1.2.1.Invoice documens|Display| - BTN:Follow-on documents: - LIN:Accounting documents: - SCR:Display document:One can see that accounting documents generated have separate ID from invoice ID, to enable partial settlement of an invoice: - Take note Accounting doc ID: 5100000001 2.7.2.1.2.2.TAB:PO Reference - FRM:Item overview: - LIN:Purchase order = 4500017337 - FRM:Item detail: - Purchase order, goods movement, invoice documents should appear in list, and status should be invoiced 2.7.3.1.Accounting|FI|Accounts payable|Account|FBL1N Diplay/Change line items| 2.7.3.1.1.SCR:Start - DDN:Vendor Account = 100268 - DDN:Company Code = 1000 - RAD:Open items = True:Show unpaid items, select this! - RAD:Cleared items = False:Show paid items - BTN:Run: 2.7.3.1.2.SCR:Main:Check amount due!
2.7.3.FI:Check subledger account of vendor:FBL1N
2.9.Reporting 2.9.1.MM:List display:ME2L
2.9.1.1.DEF:List dislay tools in SAP: - ListView: Character-based table display tool, simple, older - ALV Grid: Flexible graphic table display with standardized controls 2.9.1.2.LO|MM|Purchasing|Purchase order|List display|ME2L By vendor| 2.9.1.2.1.SCR:Start - DDN:Plant = 1000 - DDN:Purchasing organization = 1000 - DDN:Document date = 01.01.2003 .. Now - DDN:Scope of list = BEST_ALV:Information structure to show - BTN:Run 2.9.1.2.2.SCR:ALV Grid 2.9.1.2.2.1.Simple operations: Toolbar controls: - BTN:Show detail - BTN:Filter - BTN:Short - BTN:Totals - BTN:Subtotals - BTN:Change layout - BTN:Save layout 2.9.1.2.2.2.Complex operations: Settings|Layout|Change| - TAB:Short order - BTN:Add/Remove field 2.9.1.2.2.3.BTN:Save - TBX:Name = myLayout-0005 2.9.2.1.DEF: Logistic Information System (LIS) - On-Line Analitical Processing (OLAP) system of logistical managerial reporting 2.9.2.1.1.LIS Data sources: 2.9.2.1.1.1.Master data - Material - Vendor - Purchase info record 2.9.2.1.1.2.Documents(transaction data): - Purchase requisition/order - Material documents - Incoice documents - Payment documents 2.9.2.1.2.LIS Structure: 2.9.2.1.2.1.DEF:Information structure - Building block of PURCHIS - Statistical table collected from transaction data and updated regularly - It has predefined field structure from 3 functional type of fields: - Characteristics : Possible aggregation hierarchy levels of transaction data: Client|Company|Plant|Storage|Material - Period units: Possible aggregation hierarchy levels of time: Period|Month|Week|Day - Key figures: Aggregates (Count, Sum, Avg, Max, Min) of transactional data field in a given level of hierarchy 2.9.2.1.2.2.DEF:Analysis - An OLAP data cube computed from source data defined by: - Object of analysis:Set of characteristics and period units aggregate by - Selections :Set of key figures to aggregate - Initial/Drill-down lists : show detailed level data behind aggregated ones - ALT:Standard Analaysis:predefined by SAP - ALT:Flexible Analysis:can be edited on GUI 2.9.2.1.2.3.Functions: - Statistics can be performed on analysis results: - ABC analysis - Classification - Segmentation - Plan/Actual comparison - Cumulated frequencies - Correlation - Time series 2.9.2.1.3.LIS Parts: 2.9.2.1.3.1.Sales Information System(SIS) 2.9.2.1.3.2.Purchasing Information System(PURCHIS) 2.9.2.1.3.3.Inventory Controlling(INVCO) 2.9.2.1.3.4.Transportation Information System(TIS) 2.9.2.1.3.5.Shop Floor Information System(SFIS) 2.9.2.1.3.6.Quality Management Information System(QMIS) 2.9.2.1.3.7.Plant Maintenance Information System(PMIS)
PaulerSoft CANAL notes, page: 12 2.9.2.2.LO|LO controlling|Purchasing information system| Standard analyses|MCE3 Vendor| 2.9.2.2.1.SCR:Start - DDN:PurchOrg = 1000 - DDN:Months = 01.2004..Now - BTN:Run 2.9.2.2.2.SCR:ListView 2.9.2.2.2.1.COL:Vendor(Characteristics column) - Settings|Characteristic display| - |Key and text:Shows vendor Ids also - DobleClick|Change column width :extend column 2.9.2.2.2.2.Edit| - Choose key figures:select fields to show 2.9.2.2.2.3.COL:PO Value(Key figure column) - Edit| - ABC-analysis:classifies vendors by: - DDN:Strategy = Total % PO value - In 3 categories: - A = 70%, - B = 20%, - C = 10% - BTN:Graphics:Draws diagram - Record most important vendor: 1235 K.F.W.London 2.9.2.2.2.4.Extras| - |Select log: shows which information structures were usied by which reporting operation
2.9.2.MM:LIS standard analysis:MCE3
3.Material Planning Scenario

3.1.Organizational background
- Same as Procurement scenario - But Production Planning(PP) is in focus - A lighter version of Speedstar-0005 is defined in Company 1000 Plant 1000 Storage 0001 called Speedstarlett-0005 - It has 1pc of Basis-modul2-0005 - Which has 1pc of Alu-frame-0005 - Everything will be assembled by work center 1420(Assembly IV)
3.2.Plot/Preconditions of Scenario
3.3.Creating/Modifying master data 3.3.1.Material master: MM01
- Some of the iportant views are maintained solely by PP, but others are in shared processing - Some views are general for company, others ar-plant related - There are several specialized versions of MM01 to create certain types of material (eg. FERT, HALB, ROH) with preset of the settins below 3.3.1.1.Modify Speedstar-0005:MM02 - LO|MM|Material master|Material|MM02 Modify current| 3.3.1.1.1.SCR:Start - DDN:Material = Speedstar-0005 3.3.1.1.2.SCR:Main - BTN:Organization levels - DDN:Plant = 1000 - DDN:Storage = 0001 - BTN:Select views: 3.3.1.1.2.1.PP|Plant:TAB:MRP1 - DDN:MRP type = PD(MRP planning) - ALT: = No planning - ALT: = Consumption based - ALT: = MPS(Master Production Scheduling) - DDN:Lot size = EX(Exact order quantity) - ALT: = Week lots 3.3.1.1.2.2.PP|Plant:TAB:MRP2 - DDN:Procurement type = E(Own production) - ALT: = F(External) - ALT: = X(Both) - TBX:In-house production = 5days:Own production, Does not depend on order - ALT: TBX:Planned delivery time = 5days:External, Does not depend on order - TBX:Safety stock = 0:If stock goes under: - ALT:Notification issued - ALT: Planned Production Order issued at ownprod. - ALT:Purchase requisition issued at external 3.3.1.1.2.3.PP|Plant:TAB:MRP3 - DDN:Strategy group = 40(Pre-Planning with final assembly) - DDN:Availability check = 02(Individual requirement) 3.3.1.2.Create Speedstarlet-0005:MMF1 - LO|MM|Material master|Material|Create(special)|MMF1 Finished product| 3.3.1.2.1.SCR:Start - DDN:Material = Speedstarlet-0005 - DDN:Industry = Mechanical engineering - DDN:Reference = Speedstar-0005 3.3.1.2.2.SCR:Main 3.3.1.2.2.1.BTN:Organization - DDN:Plant = 1000 Copy from plant = 1000 - DDN:Storage = 0001 Copy from Storage = 0001 - DDN:SalesOrg = 1000 Copy from SalesOrg = 1000 - DDN:Channel = 10 Copy from Channel = 10 3.3.1.2.2.2.BTN:Select views: - Basic, Sales, MRP, WorkSched, Accounting, Costing 3.3.1.2.2.3.MM:TAB:Basic1: - DDN:Description = Speedstarlett-0005 3.3.1.2.2.4.SD:TAB:Sales general: - TBX:Grossweight = 20KG - TBX:Netweight = 17KG 3.3.1.2.2.5.FI:TAB:Accounting1: - TBX:Standard price = 2500 3.3.1.2.2.6.BTN:Additional data - DDN:Language = DE 3.3.1.2.2.7.BTN:Save 3.3.1.3.Create Basis-modul2-0005:MMB1 - LO|MM|Material master|Material|Create(special)|MMB1 Semi finished product| 3.3.1.3.1.SCR:Start - DDN:Material = Basis-modul2-0005 - DDN:Industry = Mechanical engineering
PaulerSoft CANAL notes, page: 13 - DDN:Reference = Basis-module-0005 3.3.1.3.2.SCR:Main 3.3.1.3.2.1.BTN:Organization - DDN:Plant = 1000 Copy from plant = 1000 - DDN:Storage = 0001 Copy from Storage = 0001 3.3.1.3.2.2.BTN:Select views: - Basic, Sales, MRP, WorkSched, Accounting, Costing 3.3.1.3.2.3.MM:TAB:Basic1: - DDN:Description = Basis-modul2-0005 3.3.1.3.2.4.SD:TAB:Sales general: - TBX:Grossweight = 15KG - TBX:Netweight = 13KG 3.3.1.3.2.5.FI:TAB:Accounting1: - TBX:Standard price = 1500 3.3.1.3.2.6.BTN:Save 3.3.1.4.Create Alu-frame-0005:MMR1 - LO|MM|Material master|Material|Create(special)|MMR1 Raw material| 3.3.1.4.1.SCR:Start - DDN:Material = Alu-frame-0005 - DDN:Industry = Mechanical engineering - DDN:Reference = Carb-frame-0005 3.3.1.4.2.SCR:Main 3.3.1.4.2.1.BTN:Organization - DDN:Plant = 1000 Copy from plant = 1000 - DDN:Storage = 0001 Copy from Storage = 0001 3.3.1.4.2.2.BTN:Select views: - Basic, Purchasing, MRP, WorkSched, Accounting, Costing 3.3.1.4.2.3.MM:TAB:Basic1: - DDN:Description = Alu-frame-0005 3.3.1.4.2.4.FI:TAB:Accounting1: - TBX:Standard price = 250 3.3.1.4.2.5.BTN:Save 3.3.2.1.DEF: BOM: - Describes list of materials necessary to produce Base quantity from a given material 3.3.2.1.1.BOM content is always single-leveled: 3.3.2.1.1.1.Header: 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/Archuved) 3.3.2.1.1.2.Items list: - ALT: Components: - 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 to Production Order (PO) - eg. Consumable goods - Variable size items : their quantity may change with final product size eg. Area of steel plate - Text items: - Document items : documentation of manufacturing algorithm - Class items: - Intra materials: - ALT: Assemblies: they are materials composed from componets according to their own BOM - So multi-level hierearchy can be built from several interlinked BOMs! - We define chain of BOMs always from simplest assebly made from raw materials towards finished product up! 3.3.2.1.1.3.Alternative items list at multiple BOMs: - different lot sizes of production may require different material composition 3.3.2.2.Create BOM:Basis-module-0005:CS01 - LO|PP|Master|BOM|BOM|Material BOM|CS01 Create| 3.3.2.2.1.SCR:Start - DDN:Material = Basis-module-0005 - DDN:Plant = 1000
3.3.2.Bill Of Material (BOM): CS01
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft CANAL notes, page: 14 - DDN:BOM usage = 1(Production) - DDN:Plant = 1000 - TBX:Valid = 01.01.CurrYear - DDN:BOM application = PP01(Production) 3.3.2.2.2.SCR:Main - BTN: Select view Item ItemCateg Component Quan - CHK:Change list = True ory tity - BTN:Run 0010 L(Stock Carb-frame1 PC - SCR:Tabular multilevel BOM in TableView item) 0005 - Goto|Graphics| 0020 L(Stock Wheel-0005 2 PC - SCR:Graphic multilevel BOM item) - BTN:Run 0030 L(Stock Chain-0005 1 PC 3.3.2.6.2.SCR:Main:Tabular multilevel BOM in ALVGrid item) 3.3.3.Routings 0040 L(Stock Gearing1 PC 3.3.3.1.DEF: Routing item) 0005 - Description of a production process of a material - BTN:Save 3.3.3.1.1.Contents 3.3.2.3.Create BOM:Basis-modul2-0005:CS01 - Material ID - LO|PP|Master|BOM|BOM|Material BOM|CS01 Create| - Plant ID 3.3.2.3.1.SCR:Start - Routing group - DDN:Material = Basis-modul2-0005 - Group counter - DDN:Plant = 1000 - Standard sequence - DDN:BOM usage = 1(Production) - Process step ID - TBX:Valid = 01.01.CurrYear - Description 3.3.2.3.2.SCR:Main - Work center:responsible position Item ItemCateg Component Quan - Standard value:amount of time neccessary for step ory tity - Base quantity :How much units material are procesed together 0010 L(Stock Alu-frame1 PC in a step item) 0005 - Production resource usages:how to share tools, machinery 0020 L(Stock Wheel-0005 2 PC - Paralel sequences:alternatives depend on item) - Make to stock 0030 L(Stock Chain-0005 1 PC - Special orders item) 3.3.3.1.2.Export options 0040 L(Stock Gearing1 PC - Can be transferred from SAP ERP to separate SAP APO, SAP item) 0005 SCM products in Production Process Model (PPM) format - BTN:Save 3.3.3.2.Create routing:Basis-module-0005:CA01 3.3.2.4.Create BOM:Speedstar-0005:CS01 - LO|PP|Master|Routing|Routing|Normal routing|CA01 - LO|PP|Master|BOM|BOM|Material BOM|CS01 Create| Create| 3.3.2.4.1.SCR:Start 3.3.3.2.1.SCR:Start - DDN:Material = Speedstar-0005 - DDN:Material = Basis-module-0005 - DDN:Plant = 1000 - DDN:Plant = 1000 - DDN:BOM usage = 1(Production) - TBX:Key date = 01.01.CurrYear - TBX:Valid = 01.01.CurrYear 3.3.3.2.2.SCR:Head 3.3.2.4.2.SCR:Main - DDN:Usage = 1(Production) Item ItemCateg Component Qua - DDN:Staus = 4(Released) ory ntity 3.3.3.2.2.1.BTN:Operations 0010 L(Stock Basis-module1 Oper StdTimesofOperat WorkCtr CtrlKey Stand item) 0005 PC Txt 0020 L(Stock Pedal 2 0010 |DoubleClick: 1420 PP01 P000 item) PC Setup = 30 MIN (Normal) 001 0030 L(Stock Brakes 2 1422(Setup hour) (Stag item) PC e 0040 L(Stock Handlebar 1 mater item) PC ial) 0050 L(Stock Saddle 1 0020 |DoubleClick: 1420 PP01 P000 item) PC Machine = 15 MIN (Normal) 002 - BTN:Save 1420(Machin hour) (Asse 3.3.2.5.Create BOM:Speedstarlett-0005:CS01 Labor = 45 MIN m- LO|PP|Master|BOM|BOM|Material BOM|CS01 Create| 1421(Wage hour) bly) 3.3.2.5.1.SCR:Start 0030 |DoubleClick: 1420 PP99 P000 - DDN:Material = Speedstarlett-0005 Labor = 24 MIN (Milestone 005 - DDN:Plant = 1000 1421(Wage hour) put to (Deliv - DDN:BOM usage = 1(Production) stock) e-ry) - TBX:Valid = 01.01.CurrYear 3.3.3.2.2.2.BTN:Save 3.3.2.5.2.SCR:Main - Take note of Routing ID: 50001319 Item ItemCateg Component Qua 3.3.3.3.Create routing:Basis-modul2-0005:CA01 ory ntity - LO|PP|Master|Routing|Routing|Normal routing|CA01 0010 L(Stock Basis-modul21 Create| item) 0005 PC 3.3.3.3.1.SCR:Start 0020 L(Stock Pedal 2 - DDN:Material = Basis-modul2-0005 item) PC - DDN:Plant = 1000 0030 L(Stock Brakes 2 - TBX:Key date = 01.01.CurrYear item) PC 3.3.3.3.2.SCR:Head 0040 L(Stock Handlebar 1 - BTN:Copy item) PC - Routing = 50001319 0050 L(Stock Saddle 1 - DDN:Reference material = Basis-module-0005 item) PC 3.3.3.3.2.1.BTN:Save - BTN:Save - Take note of Routing ID: 50001320 3.3.2.6.Check multi-level BOM: CS12 3.3.3.4.Create routing:Speedstar-0005:CA01 - DEF: Hierachic view of network of interlinked BOMs - LO|PP|Master|Routing|Routing|Normal routing|CA01 - LO|PP|Master|BOM|Reporting|BOM Explosion|Material Create| BOM|SC12 Multi level BOM| 3.3.3.4.1.SCR:Start 3.3.2.6.1.SCR:Start - DDN:Material = Speedstar-0005 - DDN:Material = Speedstar-0005 Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage,Aaa|Bbb| -Menu/Submenu, SCR-Screen, FRM-Frame, IDUniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. - DDN:Plant = 1000 - TBX:Key date = 01.01.CurrYear 3.3.3.4.2.SCR:Head - BTN:Copy - Routing = 50001319 - DDN:Reference material = Basis-module-0005 3.3.3.4.2.1.BTN:Save - Take note of Routing ID: 50001321 3.3.3.5.Create routing:Speedstarlett-0005:CA01 - LO|PP|Master|Routing|Routing|Normal routing|CA01 Create| 3.3.3.5.1.SCR:Start - DDN:Material = Speedstarlett-0005 - DDN:Plant = 1000 - TBX:Key date = 01.01.CurrYear 3.3.3.5.2.SCR:Head - BTN:Copy - Routing = 50001319 - DDN:Reference material = Basis-module-0005 3.3.3.5.2.1.BTN:Save - Take note of Routing ID: 50001322
PaulerSoft CANAL notes, page: 15 - Occouring at delivery deadline production time 3.4.1.3.2.3.Planning strategies: - They make balance among stock, production, froecast, orders - Make-to-Stock : - Can be done with finished product or easy to assemble subassemblies - More consistent production capacity usage - More expensive inventory - Make-to-order: - Mainly for finished product - Low inventory costs - Uneven capacity usage - Planning with final assembly:40 - Independent requirement is designed as make-to-stock - But if sales orders consume all the planned quantity, the difference is incorporated in planned independent requirement of future time periods. How it is done can be set in Material master or MRP group: - Consumption periods: by default it is days - Direction of sales order consumption from planned independent requirement: 3.4.Material planning - Consumption mode Backward:01: sales orders are 3.4.1.DEF:Material Planning incorporated into plan before their delivery date, so they - It has the following stages: will be produced preliminary 3.4.1.1.CO:Profitability Analysis (PA) - Requires less safety stock 3.4.1.1.1.Revenue plan: - Creates excess stock if order cancelled - Broken up by Regions - Consumption mode Forward:03: sales orders are 3.4.1.1.2.Sales Plan incorporated into plan after their delivery date, so they - Broken up by Aggregate quantity of product categories will be delivered from stock 3.4.1.2.LO:Sales and Operations Planning (SOP) - Requires more safety stock - Long-term planning linking marketing based sales forecasting - Excess stock is not created if order cancelled with manufacturing based capacity planning - Consumption mode Mixed:02/04: mix of the two above - Aggregated: does not deal with BOM explosion and parts to reach best compromise requirement, just final products - Finally, dependent requirement is computed from modified 3.4.1.2.1.SD|SIS:Sales Plan independent requirement in periods, considering production - It is broken up by time of components 3.4.1.2.1.1.Product Groups: - Tries to preserve even capacity use, but stay flexible for - Hierarchy of product(groups) demand changes - With similar planning properties - More difficult than simple strategies - And Proportion Factor: % share from group 3.4.1.3.3.Master Production Scheduling Adjustment (MPS) - They can contain: - It makes Standard Planning table for main profit generator - Finished Products finished products only to compute their independent requirement - Semi-finished products sellable as spare parts - Then first level dependent requirement of their assemblies is 3.4.1.2.2.PP:Aggregate Production Plan computed, and no already planned orders for these assemblies 3.4.1.2.2.1.Key resources: machinery, etc. are considered! - Their availability in time(YR|MO|WK|DY) - Resources reserved for 1st level dependent reqirement to 3.4.1.2.2.2.Standard Planning Table: prevent other less important products to drain them - By product group hierarchy: 3.4.1.4.Material Requirement Planning (MRP) methods: - By time periods(YR|MO|WK|DY): - Guarantees material availability - Sales plan 3.4.1.4.1.ALT:No MRP: - Production plan - Manual entry - Stock level 3.4.1.4.2.ALT:PD(MRP): - Days supply calculated 3.4.1.4.2.1.Multi level MRP - With the following possible goal functions: - Design along fully extracted BOM, for all levels it computes - ALT:Stock level to zero with backward scheduling: - ALT:Target Stock level - Available quantity = stock + fixed receipts safety - ALT:Target days supply stock 3.4.1.2.3.LO:Feasibility estimate - Net requirement = Gross requirement available - Examines probability that key resources will cover the need of quantity planning table in time, as demand and sometimes availability of - Procurement proposal = Round( NetReq/LotSize ) resources are uncertain LotSize 3.4.1.3.PP:Master Product Sceduling (MPS) - Component due time = Head due time component 3.4.1.3.1.SD:Incoming Sales orders pruduction|delivery time - Customer 3.4.1.4.2.2.Single level MRP: - Product type - same just for lowest 1 level of BOMs - Quantity 3.4.1.4.3.ALT:Consumption-based planning: - Delivery deadline - For low valued, simple, stanardized components consumed at 3.4.1.3.2.MM:Demand Management high quantity (eg. Consumable goods) 3.4.1.3.2.1.Data sources: - Do not use BOM explosion to compute dependent requirement, - Sales Orders instead it forecast future consumption from past: - Historic Aggregated Sales - Reorder quantity method: - Sales forecast - It automaticly orders fixed lot size quantity when stock goes 3.4.1.3.2.2.Content: under - Independent requirement: - Reorder quantity = safety stock + daily fix - Required quantity of product groups|finished products consumptionreplenishment time. - At a given deadline - Optimal if transport is flexible in time but inflexible in size (eg. - According to sales forecast Concrete) - Dependent requirement: - Periodic reorder method: - Required quantity components and assemblies back- Periodicly orders changing quantity. chained through BOM - Optimal if transport inflexible in time and flexible in size (eg. Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage, Aaa|Bbb| -Menu/Submenu, SCR-Screen, FRM-Frame, IDUniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. Newspaper) - Simple automated ordering - Higher cost of inventory 3.4.1.4.4.MRP Run levels - Total for Plant and reevaluates BOMs:NEUPL - MRP group - Refined manual selection - Single Material - For net changes only:NETCH - For a given time period (usually 30days): NETPL - Online/Background job 3.4.1.4.5.MRP Outputs 3.4.1.4.5.1.Types: - Stock/requirement list: - Dynamic list summing up results from all Stocks, Orders, and MRP runs - MRP lists : - Static list with the results of 1 MRP run - Can contain error list of inconsistencies in BOMs 3.4.1.4.5.2.Content: - SCR:Top: Variable header - SCR:Left: Material BOM tree - SCR:Right: MRP items requirement/stock 3.4.1.5.PP/MM:Production/Procurement Execution 3.4.1.5.1.MRP Consequence Documents 3.4.1.5.1.1.At internal products it creates: - Planned order - Production order - Planned reservation for dependents 3.4.1.5.1.2.At external materials it creates: - If there is no scheduling agrrement in source list of material: - Purchase requisitions: No vendor yet - Purchase orders: Vendor assigned - If there is Scheduling agrrement in Source list of material: - Schedule Line Release - Schedule Line 3.4.2.1.DEF: Consumption setting of material - Set that Planned orders will consume (will be subtracted from) Planned independent requirement: the plan should be reduced, if one part of it becomes actual order - Set the direction of consumption in time 3.4.2.2.Set consumption: SpeedStar-0005: MM02 - LO|PP|Master data|Material master|Material| MM02 Change| 3.4.2.2.1.SCR:Start - DDN:Material = SpeedStar-0005 - BTN:Organiz - Plant = 1000 - Storage = 0001 - BTN:View = MRP3 3.4.2.2.2.MM:TAB:MRP3 - DDN:Consumption mode = 2(Consume) - TBX:Backward period = 30 - TBX:Forward period = 30 3.4.2.2.3.BTN:Save 3.4.2.3.Set consumption: SpeedStarlett-0005: MM02 - Same as above 3.4.3.1.DEF: Product Group: - Groups similar products into common maintenance 3.4.3.2.Create product group: Racing-Bike-0005: MC84 - LO|PP|SOP|Product group|MC84 Create| 3.4.3.2.1.SCR:Start - DDN:Product Group = Racing-Bike-0005 - TBX:Product Group = Racing-Bicycle-0005 - DDN:Plant = 1000 - DDN:Unit = PC - RAD:Members = Material 3.4.3.2.2.SCR:Main Material Aggregation Proportio factor n SpeedStar-0005 0 60 SpeedStarlett0 40 0005 3.4.3.2.3.BTN:Save 3.4.4.1.DEF: Sales and Production Plan content: - Aggregated plans for product groups broken up by months - Target Days Supply:How many days production should be kept on safety stock
PaulerSoft CANAL notes, page: 16 - Production is computed from sales plan and safety stock 3.4.4.2.Create Plan: MC82 - LO|PP|SOP|Planning|Product group|MC82 Change| 3.4.4.2.1.SCR:Start - DDN:Group = Racing-Bike-0005 - DDN:Plant = 1000 - BTN:Active version: creates A00(Active) plan 3.4.4.2.2.SCR:Create rough plan Month No No No No No No w+ w+ w+ w+ w+ w+ 2 3 4 5 6 7 Sales 20 15 10 15 20 17 00 00 00 00 00 50 TargetDaysSupp 3 3 3 3 3 3 ly - KEY:Enter: - LIN:Stock level:calculated automatically with negative quantities - Edit|Create production plan|Target days supply| - LIN:Production: calculated automatically (may vary little bit because different lenght of the months) - LIN: Stock level:shifts to positive 3.4.4.2.3.BTN:Save 3.4.5.1.DEF: Disaggregation: - Breaks up aggregate plans to individual products by their proportion factor - Transfers them to demand management as planned independent requirement - But no dependent requirements are created 3.4.5.2.Disaggregate group: Racing-Bike-0005: MC75 - LO|PP|SOP|Disaggregate|MC75 Transfer Product Group| 3.4.5.2.1.SCR:Start - DDN:Product group = Racing bike-0005 - DDN:Plant = 1000 - DDN:Version = A00 - CHK:Prod. plan for mat. as a proportion = True - DDN:From date = Now - CHK:Invisible transfer = False(Show manual override screen) - CHK:Active = True - BTN:Transfer now 3.4.5.2.2.SCR:Manual override plan - Take note of 5th months production quantity of Speedstar-0005: 3.4.5.2.3.BTN:Save:Speedstar-0005 3.4.5.2.4.BTN:Save:Speedstarlett-0005 3.4.5.3.Display Stock/Requirements list: SpeedStar-0005: MD04 - LO|PP|MRP|Evaluations|MD04 Stock/Requirements list| 3.4.5.3.1.SCR:Start - DDN:Product = SpeedStar-0005 - DDN:Plant = 1000 3.4.5.3.2.SCR:Main - COL:MRP Element,Reqirement,Available are updated 3.4.5.4.Display Stock/Requirements list: SpeedStarlett-0005: MD04 - Same as above - Take note of last months unrestriced use stock of Speedstarlett0005: -3966 3.4.6.1.DEF:MRP - Create dependent requirement for independent requirement - After BOM explosion 3.4.6.2.MRP Run: SpeedStar-0005: MD02 - LO|PP|MRP|Planning|MD02 Single item, multi level| 3.4.6.2.1.SCR:Start - DDN:Material = SpeedStar-0005 - DDN:Plant = 1000 - DDN:Processing key = NETCH(Only net change) - DDN:Create purchase req. = 2(In opening period) - DDN:Delivery schedules = 3(Apply) but now there isnt any - DDN:Create MRP list = 1(Create list) - DDN:Planning mode = 1(New plan) - DDN:Scheduling = 1(Basic dates will be determined) - CHK:Also plan unchanged components = False - CHK:Display results before they are saved = False - CHK:Display material list = False - CHK:Simulation mode = False - KEY:Enter,Enter 3.4.6.2.2.SCR:MRP Summary - Dependent components not in stock will generate exceptions
1232
3.4.5.Disaggregation of Production Plan: MC75
3.4.2.Change material: MM02
3.4.3.Create Product Groups: MC84
3.4.6.Material Requirement Planning: MD02
3.4.4.Create Sales and Production Plan: MC82
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 3.4.6.3.Display Stock/Requirements list: SpeedStar-0005: MD04 - LO|PP|MRP|Evaluations|MD04 Stock/Requirements list| 3.4.6.3.1.SCR:Start - DDN:Product = SpeedStar-0005 - DDN:Plant = 1000 3.4.6.3.2.SCR:Main - Independent planned orders show up for months - They consume (balance) up independent requirements to 0 3.4.6.3.2.1.LIN:MRPElmt = PlOrd(Planned order):DoubleClick - SCR: Follow-up documents : could be created here - BTN:Production Order - BTN:Partial Production Order - BTN:Process Order - BTN:Partial Process Order - BTN:Purchase Requisition 3.4.6.4.Display MRP list: SpeedStar-0005: MD05 - LO|PP|MRP|Evaluations|MD05 MRP list| 3.4.6.4.1.SCR:Start - DDN:Product = SpeedStar-0005 - DDN:Plant = 1000 3.4.6.4.2.SCR:Main - Goto|Stock/requirements list comparison| - Differences can be check out - If there was no production sice last MRP run, there should be no differences 3.4.6.5.MRP Run: SpeedStarlett-0005: MD02 - Same as above 3.4.7.1.DEF: Sales Order - Creates actual requrements besides planned independent requirements 3.4.7.2.Create Sales Order: Plant 1000 to Becker, Berlin: VA01 - LO|SD|Sales|Order|VA01 Create| 3.4.7.2.1.SCR:Start - DDN:Order type = OR - DDN:Sales organization = 1000 - DDN:Distribution channel = 10 - DDN:Division = 00 3.4.7.2.2.SCR:Create standard order, overview 3.4.7.2.2.1.SCR:Head - DDN:Sold-to-party = 1000(Becker, Berlin) - DDN:Ship-to-party = 1000(Becker, Berlin) - DDN:PO number = Order-0005 - DDN:Req. deliv. date. = 15.Now+3months.201#( No weekend!) 3.4.7.2.2.2.SCR:Item LINMaterial Quantity 10 SpeedStar-0005 100 20 SpeedStarlett-0005 100 - Select both lines - Goto|Item|Conditions| 3.4.7.2.2.3.SCR:Item detail - BTN:Item navigation:10 SpeedStar-0005 - TAB:Conditions - LIN:First empty - COL:CondType = Pr00(Price) - COL:Amount = 3000 - KEY:Enter:to update - BTN:Item navigation:10 SpeedStarlett-0005 - TAB:Conditions - LIN:First empty - COL:CondType = Pr00(Price) - COL:Amount = 2500 - KEY:Enter:to update 3.4.7.2.3.BTN:Save - Take note of the Sales order number: 13336 3.4.7.3.Display Stock/Requirements list: SpeedStar-0005: MD04 - Stock/req list should show 100PC bigger requirement than MRP list, as MRP is not re-run yet. 3.4.8.1.MRP Run: SpeedStar-0005: MD02 - Same as above 3.4.8.2.MRP Run: SpeedStarlett-0005: MD02 - Same as above 3.4.8.3.Display Stock/Requirements list: SpeedStar-0005: MD04 - Sales order now consumed from planned independent requirement: reduces it, as one part of the planned quaninty is really ordered! - MRP and Stoc/Req list should be synchronized now
PaulerSoft CANAL notes, page: 17
3.4.7.Create Sales Order: VA01
3.4.8.Material Requirement Re-Planning: MD02
4.Lifecycle Data management scenario

4.1.DEF: Product Life Cycle Management (PLM)
Manages products and projects lifecycle From planning to phase out Integrated with CRM and SCM Has limeted activity when product/project is on peak Consists of following components:
4.1.1.1.Content objects handled (Import/export): - CAD systems - GIS systems - Office systems - 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-base dialog templates - ALT:With SAP GUI 4.1.2.1.Content objects handled: - Paper - Folder - Electronic 4.1.2.2.Tools:Document Info Record: - Document fuction description - Secure Storage Area access - Versioning - Status - Classification - Bidirectional Links with SAP ECC parts: what will use it? - Bidirectional Links with PLM and ArchiveLink interfaces: how to import/export? 4.1.2.3.GUI: 4.1.2.3.1.Easy Document Management System (DMS) interface: - Simplified tool no need to learn SAP GUI 4.1.2.3.2.EAI Viewer: - View CAD Animated 4.1.2.3.3.MS Office: - View office documents 4.1.2.3.4.WorkFlow: - Organize documents into process flows 4.1.3.1.Content object handled: - Material masters - BOM - Routings - Documents 4.1.3.2.Tools 4.1.3.2.1.Product classification - Define Attributes/Characteristics: 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: 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 values store Dynamic BOM/Routing of product versions - Different type of BOMs can be defined: - Production BOM: Normal production - Order BOM: specific variant assigned to 1 order 4.1.3.3.GUI: - SCR:Left:Product hierarchy - SCR:Right:Component detail 4.1.4.1.Content objects handled: - Material master - BOM - Routing - Documents
4.1.1.Integration
4.1.2.Document management
PaulerSoft CANAL notes, page: 18 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 cotents 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)
4.2.Plot of PLM Scenario:
4.1.3.Product structure browser
- Add SpeedStar-0005 BOM picture BOMSpeedStar0005.JPG as document info record - Product class Bike-0005 will be defined with 2 characteristics: - Bike-Type-0005: Possible values: Men,Women - Frame-Type-0005: Possible values: Carbon,Aluminium - Our finished products will be configurable materials classified into Bike-0005 class with characteristic values: - SpeedStar-0005: - Bike-Type-0005 = Men - Frame-Type-0005 = Carbon - SpeedStarlett-0005: - Bike-Type-0005 = Women - Frame-Type-0005 = Aluminium
4.3.CA:Create document info records 4.3.1.DEF: Document Info Record
- It connects material with its complex documentation - Now we will store only BOM in that
- LO|Central functions|Document management|Document| CV01N Create| 4.3.2.1.SCR:Start - DDN:Material = SpeedStar-0005 - DDN:Document type = DRM - DDN:Document part = 000 - DDN:Document version = 00 4.3.2.2.TAB:Document data - TBX:Description = Speedstar-BOM-0005 - DDN:Lab./Office = KB1 4.3.2.2.1.FRM:Original - BTN:Create new 4.3.2.2.1.1.SCR:Create doc:Basics - TBX:Log = Document Attachment 4.3.2.2.1.2.SCR: Create doc:Details - DDN:WS-Appl. = JPG - TBX:Description = BOM - DDN:Data carrier = INTERNET - TBX:Original = BOMSpeedStar-0005.JPG 4.3.2.3.BTN:Save
4.3.2.Document info record: SpeedStar-0005: CV01N
4.1.4.Engineering Change&Configuration Management
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. - LO|Central functions|Document management|Document| CV02N Modify| 4.3.3.1.SCR:Start - DDN:Material = SpeedStar-0005 - DDN:Document type = DRM - DDN:Document part = 000 - DDN:Document version = 00 4.3.3.2.TAB:Object links 4.3.3.2.1.TAB:Material master - LIN:Empty - DDN:Material = SpeedStar-0005 4.3.3.3.BTN:Save
4.3.3.Link Document to Material: SpeedStar-0005: CV02N
PaulerSoft CANAL notes, page: 19 4.4.6.1.SCR:Start - DDN:Class = Bike0005 - DDN:ClassType = 001(Material) 4.4.6.2.SCR:Main - DDN:Bike-Type-0005 = Men - DDN:Frame-Type-0005 = Aluminium - BTN:Find in initial class - Take note of result: Nothing, there is no such
object
4.5.CA:Product Structure Browser: SpeedStar-0005: CC04

- Cross-application|Engineering change management| Environment|CC04 Product Sturcture| - DDN:Material = SpeedStar-0005
4.4.CA:Classification of material 4.4.1.Create characteristics: Bike-Type-0005: CT04
4.5.1.SCR:Start
- Cross application|Classification|Master data|CT04 Create characteristics| 4.4.1.1.SCR:Start - TBX:Characteristics = Bike-Type-0005 - BTN:New 4.4.1.2.SCR:Create characteristics 4.4.1.2.1.TAB:Basic data - TBX:Description = Bike-Type-0005 - DDN:Data type = character format - DDN:Status = 1(Released) - TBX:Number of characters = 20 4.4.1.2.2.TAB:Values Value Description Men Bicycle-For-Men-0005 WomenBicycle-For-Women-0005 4.4.1.3.BTN:Save
4.5.2.1.FRM:Product structure - LIN:Document - LIN:BOM - LIN:SpeedStar-0005|RightClick|Cange| - LIN:Classification - LIN:Routing 4.5.2.2.FRM:Right panel - COL:Text:Description - COL:Original:View original document in viewer - COL:Values:Valid class values - Take screenshot of product structure browser opened:
ProdStructSpeedStar-0005.JPG
4.5.2.SCR:Main
4.4.2.Create characteristics: Frame-Type-0005: CT04

- Same as above except: Value Description Carbon Carbon-Frame-0005 AluminiumAluminium-Frame-0005
- Cross application|Classification|Master data|CL02 Classes| 4.4.3.1.SCR:Start - TBX:Class = Bike0005(without - character!) - DDN:Class type = 001(Material class) - BTN:New 4.4.3.2.SCR:Create class - TBX:Name = Bike0005 - DDN:Status = 1(Released) 4.4.3.2.1.TAB:Characteristics Char Bike-Type-0005 Frame-Type-0005 4.4.3.3.BTN:Save - LO|MM|Material master|Material|Create|MMF1 Finished products| 4.4.4.1.SCR:Start - DDN:Material = SpeedStar-0005 - BTN:Select view = Classification 4.4.4.2.SCR:Main 4.4.4.2.1.TAB:Classification - DDN:ClassType = 001(material class) 4.4.4.2.1.1.FRM:Assignments Class Bike0005 - KEY:Enter 4.4.4.2.1.2.FRM:Values Characteristics Value Bike-Type-0005 Men Frame-Type-0005Carbon 4.4.4.3.BTN:Save
4.4.3.Create class: Bike0005: CL02
4.4.4.Classify material: SpeedStar-0005: MMF1
4.4.5.Classify material: SpeedStarlett-0005: MMF1

- Same as above except: Characteristics Value Bike-Type-0005 Women Frame-Type-0005Aluminium
4.4.6.Checking out materials in a class with values: Bike0005: CL30N
- Cross-application|classification|Classification find|CL30N Objects in class|
5.Manufacturing Execution Scenario

5.1.Plot of scenario 5.1.1.Plot of master data
- In routing for SpeedStar-0005, its BOM-components Pedal, Brakes, Handlebar, Saddle should be assigned to operation 0020 instead of the default 0010, as these components are needed only at final assembly
5.1.2.1.Product costing: - Do product costing, price mark, price release: - Basis-Module-0005: 1588EUR - SpeedStar-0005: 2377EUR - Basis-Modul2-0005: 1088EUR - SpeedStarlett-0005: 1877EUR 5.1.2.2. Re-run MRP - As routings changed, re-run MRP for SpeedStar-0005 5.1.3.1.Production orders - Planned orders of (semi)finished should be converted to production orders: - Basis-Module-0005: 1371PC - SpeedStar-0005: 1371PC 5.1.3.2.Purchase orders - Planned orders of raw materials should be converted to production orders: - Gearing-0005: 1371(for Basis-Module-0005)+914(for BasisModul2-0005)-100(Already on stock) = 2185PC - Wheel-0005: 2742(for Basis-Module-0005)+1828(for BasisModul2-0005) = 4570PC - Chain-0005: 1371(for Basis-Module-0005)+914(for BasisModul2-0005) = 2285PC - Carb-Frame-0005: 1371PC(for Basis-Module-0005) 5.1.3.3.Post goods receipts - All purchased material arrives on same day to inventory 5.1.3.4.Goods Issue - Issue all components from inventory on same day to manufactoring of: - Basis-Module-0005 - SpeedStar-0005 - Manually modify quantity of Breaks from 2742 to 2942PC becasue 200 Breaks destroyed 5.1.3.5.Confirm production order - Confirm production orders on same day for: - Basis-Module-0005 - SpeedStar-0005
5.1.2.Plot of Production-On-Order Preparation
PaulerSoft CANAL notes, page: 20 - Setup - Processing - Fixed time element - Variable time element - Tear down - HR Position responsible - Required qualifications - Employees assigned - DEF:Production Resources&Tools (PRT): - Material, Equipment, Document 5.2.1.1.4.DEF:BOM-Routing assignment: - By default BOM components of a material are assigned to 1st operation of materials routing - But this can be changed if components has to arrive Just in Time (JIT) to a given operation in routing - Also routed resources can be assigned to a given operation - LO|PP|Master|Work center|Work center|CR03 Display| 5.2.2.1.SCR:Start - DDN:WorkCenter = 1420 - DDN:Plant = 1000 5.2.2.2.SCR:Main 5.2.2.2.1.TAB:Basic: - DDN:WorkCenterCategory = 0003(Labor) 5.2.2.2.2.TAB:Costing: - DDN:CostCenter = 4210(Motocycle assembly) - DDN:ControlingArea = 1000(Europe) - FRM:ActivityTypes 5.2.2.2.3.TAB:Capacities: - FRM.Capacities CategoryDescriptionCapacity Formula 002 Labor ### BTN:View Form Machine Person - DDN:FactoryCalendarID = 01(German standard) - LIN:WorkingDay - TBX:StartHour = 06.00 - TBX:EndHour = 22.00 5.2.2.2.4.TAB:Default values: 5.2.2.2.5.TAB:Scheduling : - LO|PP|Master|Routing|Routing|Standard|CA02 Change| 5.2.3.1.SCR:Start - DDN:Material = SpeedStar-0005 - DDN:Plant = 1000 5.2.3.2.SCR:Main 5.2.3.2.1.FRM:Head - DDN:Status = 04(Released) - DDN:TaskListGroup = 50001321(Purpose of routing) - TBX:GroupCounter = 1(Unique ID of routing inside group) - TBX:LotSizeRange = 0 - 99.999.999 (Lot size range in which current routing is valid, operation sequence may depend on lot size) - BTN:Sequences 5.2.3.2.2.SCR:Sequence types: - LIN:Standard - BTN:Operation 5.2.3.2.3.SCR:Standard sequence operations: 5.2.3.2.3.1.LIN:0010|Detail|Operation| - TBX:BaseQuantity = 1 - DDN:UnitOfMeasure = PC - FRM:Standard values - LIN:Personell time - TBX:BaseQuantity = 45 - DDN:UnitOfMeasure = MIN 5.2.3.2.4.BTN:CompAlloc|SCR:ComponentAssignment - LIN:Pedal, Breaks, Handlebar, Saddle select - BTN:New assignment|SCR:New assignment| - DDN:Operation = 0020 5.2.3.2.5.BTN:Save
5.2.2.Display Work Center: 1420: CR03
5.1.3.Production Order Process
5.2.3.Display Routing: SpeedStar-0005: CA02
5.1.4.Production Closing Operations 5.2.Modify BOM and Routing master data 5.2.1.Processed data structures
5.2.1.1.1.Material master - Material ID - Measure unit 5.2.1.1.2.BOM 5.2.1.1.2.1.Header - For Material ID - BOM type:Production/Order 5.2.1.1.2.2.Item - Type:Material/Document - Material ID - Quantity 5.2.1.1.3.DEF:Task lists: 5.2.1.1.3.1.ALT:Rate routings 5.2.1.1.3.2.ALT:Master recipe 5.2.1.1.3.3.ALT:Equipment task list 5.2.1.1.3.4.ALT:Inspection plan 5.2.1.1.3.5.ALT:Routing groups|Routings: - Head - For Material ID - Standard/alternative sequences: - Operations: - Control key:PP01 normal/PP03 milestone - DEF:Work centers: - Cost center - Activity types - Tariffs - Capacity formula key - Scheduling formula key - Cost formula key - Standard values of activity types:
5.3.Production-On-Order Preparation 5.3.1.DEF: Production types
5.3.1.1.ALT:Order controlled - It needs Sales Order 5.3.1.1.1.1.ALT: With Production Order - Involves manufacturing Lots: series of fully identical products 5.3.1.1.1.2.ALT: With Process Order - Involves continous manufacturing process, eg. Chemicals 5.3.1.2.ALT:Repetitive manufacturing - No order related - Assembly line 5.3.1.3.ALT:Project - Given unique featured lot - Completed on given deadline 5.3.1.4.ALT:Kanban - Procurement driven - Self controlled cycles of - Unique identified kanban-containers - Alternating between full/empty states - Carrying given lots - Involves: - External procurement - In-house production - Stock transfer among storage 5.3.2.1.Production Order request 5.3.2.2.Production Order creation 5.3.2.2.1.Ways - ALT:Without routing and BOM manually - ALT:With routing only - ALT:With routing and BOM - ALT:With planned order 5.3.2.2.2.Production Order Content 5.3.2.2.2.1.Head - Status:CreatedReleased - Type:PP01/.. - Cost summary - Cost settlement rule in Cost Object Controlling (COC) - Links to Document Management System (DMS) 5.3.2.2.2.2.Items - Standard/parallel/alternate operation sequences - Operations: tehre should be at least 1 routing operation - Material BOM components: by default all components of BOM are attached to first operation - PRTs - Trigger Points - Confirmations - Work centers - Cost calculation - Capacity splits - Persons - Machinery 5.3.2.3.Availability check 5.3.2.3.1.ALT:Manual: - If OrderType = PP01 5.3.2.3.2.ALT:Auto 5.3.2.4.Machine reservation 5.3.2.5.Order release 5.3.2.5.1.Scope - ALT:Single order - ALT:Mass release 5.3.2.5.2.Source data - BOM - Routing - Work center capacity scheduling 5.3.2.5.3.Launch - ALT:Auto - ALT:manual 5.3.2.5.4.Results - ALT:Confirm - ALT:FMAT Material shortage - ALT:FFHM Part Missing - ALT:FKAP No capacity 5.3.2.6.Download to PDC system 5.3.2.7.Auto:Order print 5.3.2.8.PROC:Movement:261 Goods Issue (GI) posting - Update stock - Update material reservations - Compute actual cost of order - Issue documents
5.3.2.PROC:Production on Order
PaulerSoft CANAL notes, page: 21 - Material - Accounting - Cost accounting 5.3.2.9.Auto:Material withdrawal posting 5.3.2.10.Upload from PDC system 5.3.2.11.Auto:Confirmatioon 5.3.2.11.1.ALT:Order related 5.3.2.11.2.ALT:Operation related - ALT:Time ticket - ALT:Collective - ALT:Milestone - ALT:Progress - ALT:Time event 5.3.2.12.Work-in-Process (WIP) determination 5.3.2.13.Auto:Movement:101 Goods receipt - Issue documents - Material - Accounting - Cost accounting - Print Goods Issue Document - Delivered quantity updated - Receipt evaluated, credit amount is added to orders credit - Results in Stock Receipt 5.3.2.14.Variance calculation 5.3.2.15.Order settlement, Cost Debit/Credit 5.3.2.15.1.Result - Production order is a Cost object in Cost Object Controlling (COC) - After settlement cost is allocated to General Ledger Accounts and it will be no more cost object, can be closed 5.3.2.15.2.Types 5.3.2.15.2.1.ALT:Order related - Flexible manufacturing of valuable complex products 5.3.2.15.2.2.ALT:Product related 5.3.2.15.3.Controled by Settlement Profile - Settlement period - Price control - Settlement receiver(s) and their account(s) - Distribution rules - Plant activity accounts - Difference account - Settlement parameters 5.3.2.16.Archive/delete 5.3.3.1.DEF:Product Costing Data Structure 5.3.3.1.1.DEF:Standard price: - Cost estimate in material master - Of a material purchased/produced in one time 5.3.3.1.2.DEF:Moving average price: - Lot size-weighted moving average cost - Of a material purchased/produced in more lots in time 5.3.3.1.3.DEF:Planned price: - Material/Manufacturing cost of (semi)finished product Cost objects - Calculated by Cost Object Controlling (COC) Product costing 5.3.3.1.3.1.Data sources: - BOM: - Standard material prices - Moving material prices - Routing|Operations|Workstations: - Setup/machine/labour cost - Based on the utilized activity types: - Tariffs - Standard quantities 5.3.3.1.3.2.PROC: - Always goes upward in BOM/Routing hierarchy from simplest semifinished product towards finished product
5.3.3.CO:Product Costing
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 5.3.3.1.4.DEF:Actual price: - Planned price marked up and released for the material 5.3.3.1.5.DEF:Sales price. - Gross Sales Price Condition negotiated with customer by SalesOrg - Contains overhead/margin above actual price 5.3.3.2.CO:Product Costing: Basis-Module-0005: CK11N - FI|CO|Product Cost Controlling|Product Cost Planning| Material costing|Cost estimate with quantity structure| CK11N Create| 5.3.3.2.1.SCR:Start - DDN:Material = Basis-Module-0005 - DDN:Plant = 1000 - DDN:Costing variant = PPC1(Standard costing Mat) - DDN:Costing version =1(TP ProfitCenter) - DDN:Costing lot size = 1 - KEY:Enter - DDN:Costing date from = Now 5.3.3.2.2.SCR:Main 5.3.3.2.2.1.FRM:Left:Costing structure - BOM hierarchy of materials 5.3.3.2.2.2.FRM:Right:Selected material - TAB:Costs: Cost TotalFixedVariableCurr Goods Manufactured 1588 54 1534EUR Goods Sold 2144 73 2071EUR - FRM:Item: Itemized view 5.3.3.2.3.BTN:Save(Do not save in case of serious difference!) - CHK:Itemization = True - CHK:Log = True 5.3.3.3.CO:Mark price: Basis-Module-0005: CK24 - FI|CO|Product Cost Controlling|Product Cost Planning| Material costing|CK24 Price update| 5.3.3.3.1.SCR:Start - BTN:Marking allowance(It needs only in case nobody used the current month yet!) - SCR:Marking allowance - DDN:Posting period = current month - LIN:Company = 1000|DoubleClick| - DDN:Costing variant = PPC1(Standard) - DDN:Costing version = 01 - BTN:Save - DDN:Posting period = current month - DDN:Company Code = 1000 - DDN:Plant = 1000 - DDN:Material = Basis-Module-0005 - CHK:With list output = True - CHK:Test run = False - BTN:Run 5.3.3.3.2.SCR:Output - LIN:Planned price = 1588 5.3.3.4.MM:Check price marking: Basis-Module-0005: MM03 - LO|MM|Master master|Material|Display|MM03 Display current| 5.3.3.4.1.SCR:Start - DDN:Material = Basis-Module-0005 - BTN:Select View:Costing2 - DDN:Plant = 1000 5.3.3.4.2.SCR:Main 5.3.3.4.2.1.TAB:Costing2 Price FutureActualFuture Planned price 1588 0 0 Standard price 2000 5.3.3.5.CO:Release price: Basis-Module-0005: CK24 - FI|CO|Product Cost Controlling|Product Cost Planning| Material costing|CK24 Price update| 5.3.3.5.1.SCR:Start - BTN:Release(Make planned price to standard) - DDN:Posting period = current month - DDN:Company Code = 1000 - DDN:Plant = 1000 - DDN:Material = Basis-Module-0005 - CHK:With list output = True - CHK:Test run = False - BTN:Run 5.3.3.5.2.SCR:Output - LIN:Standard price = 1588 5.3.3.6.MM:Check current price: Basis-Module-0005: MM03 - LO|MM|Master master|Material|Display|MM03 Display current|
PaulerSoft CANAL notes, page: 22 5.3.3.6.1.SCR:Start - DDN:Material = Basis-Module-0005 - BTN:Select View:Costing2 - DDN:Plant = 1000 5.3.3.6.2.SCR:Main 5.3.3.6.2.1.TAB:Costing2 Price FutureActualFuture Planned price 0 1588 0 Standard price 1588 5.3.3.7.CO, MM: Product Costing, Mark, Release: SpeedStar-0005: CK11N, CK24, MM03 - Planned/Stanard price = 2377EUR 5.3.3.8.CO, MM: Product Costing, Mark, Release: Basis-Modul20005: CK11N, CK24, MM03 - Planned/Stanard price = 1088EUR 5.3.3.9.CO, MM: Product Costing, Mark, Release: SpeedStarlett0005: CK11N, CK24, MM03 - Planned/Stanard price = 1877EUR 5.3.3.10.MM:Check out material changes: MM60 - LO|MM|Material master|Material|MM60 Material list| 5.3.3.10.1.SCR:Start - DDN:User = wip-00-05 - BTN:Run 5.3.3.10.2.SCR:Main Material Price Basis-Module-0005 1588EUR SpeedStar-0005 2377EUR Basis-Modul2-0005 1088EUR SpeedStarlett-0005 1877EUR
5.3.4.MM:Re-run MRP:SpeedStar-0005:MD02
- LO|PP|MRP|Planning|MD02 Single item, multi level| 5.3.4.1.1.SCR:Start - DDN:Material = SpeedStar-0005 - DDN:Plant = 1000 - DDN:Processing key = NETCH(Only net change) - DDN:Create purchase req. = 2(In opening period) - DDN:Delivery schedules = 3(Apply) but now there isnt any - DDN:Create MRP list = 1(Create list) - DDN:Planning mode = 2(Re-explode BOM!) - DDN:Scheduling = 1(Basic dates will be determined) - CHK:Also plan unchanged components = False - CHK:Display results before they are saved = False - CHK:Display material list = False - CHK:Simulation mode = False - KEY:Enter,Enter 5.3.4.1.2.SCR:MRP Summary - Dependent components not in stock will generate exceptions
5.4.PP:Production order:SpeedStar-0005 5.4.1.DEF:Production Order process

-
First its MRP status is checked Semi-finished components are ordered upward in hierarchy Finished product is ordered External materials are ordered
- LO|PP|MRP|Eavuation|MD04 Stock/Req list| 5.4.2.1.SCR:Start - DDN:Material = SpeedStar-0005 - DDN:Plant = 1000 5.4.2.2.SCR:Main - Planned orders should be created - They should cover dependent requirement of components also - Breaks, Pedal, HandleBar, Sadle should be on stock sufficient quantity
5.4.2.MM:Check MRP status:SpeedStar-0005:MD04
5.4.3.PP:Create Production Order (Semi-Finished):BasisModule-0005 1371PC:MD04
- LO|PP|MRP|Eavuation|MD04 Stock/Req list| 5.4.3.1.SCR:Start - DDN:Material = Basis-Module-0005 - DDN:Plant = 1000 5.4.3.2.SCR:Main - LIN:PlOrd:Basis-Module-0005 1370PC|DoubleClick| - SCR:Additional data of MRP element - BTN:Prod.Order|SCR:New Production Order (Ignore document not valid warning! ) - BTN:Material|SCR:Availability check - BTN:Missing parts|SCR:Missing Parts Overview - BTN: Components:Auto-ordered dependent components by BOM can be seen: they will change from Dependent requirement Reserved Order - BTN: Operations:Auto-ordered operations by routing can be seen (The last has to have StadardKey = P00005 to initiate auto-goods issue) - BTN: Release:Status shifts from CRTD REL - BTN:Save, Take note of prod.order number:60003525 - BTN:Update:MRP element shifts from LIN:PlOrd - LIN:ProdOrd Basis-Module-0005 1370PC
PaulerSoft CANAL notes, page: 23 finished product - DDN:DelivNote = * 5.4.9.1.2.FRM:Item detail - CHK:ItemOk = True - TAB:Where - DDN:Storage = 0001 5.4.9.1.3.BTN:Save - Take note of goods receipt number: 5000012423
5.4.10.MM:Post Goods Receipt: Wheel-0005:MIGO

- Take note of goods receipt number: 5000012424 - Take note of goods receipt number: 5000012425 - Take note of goods receipt number: 5000012426
5.4.11.MM:Post Goods Receipt: Chain-0005:MIGO 5.4.12.MM:Post Goods Receipt: Carb-Frame-0005:MIGO

- LO|MM|Inventory|Goodsmovement|MB1A Goods issue| 5.4.13.1.SCR:Start - BTN:To order - DDN:OrderNum = 60003525 (Basis-Module-0005) 5.4.13.2.SCR:Main - FRM:Items:Check that all components issued from inventory 5.4.13.3.BTN:Save - Take note of document number: 4900038401
5.4.13.MM:Goods Issue: Basis-Module-0005: MB1A
5.4.4.PP:Create Production Order (Finished):SpeedStar0005 1371PC:MD04

- Same as above, Take note of prod.order number:60003526
5.4.14.PP:Confirm production order: Basis-Module-0005: CO15

- LO|PP|Production control|Confirmation|Enter|CO15 For order| 5.4.14.1.SCR:Start - DDN:OrderNum = 60003525 (Basis-Module-0005) - RAD:Final Confirmation = True 5.4.14.2.SCR:Main - Check goods movement list: it will show only Basis-Module0005, but as this finishes with PP03 Milestone type operation: - All components will be auto-confirmed - Their warehouse goods receipt will be auto-issued 5.4.14.3.BTN:Save
5.4.5.MM:Create Purchase Order (RawMat):Gearing-0005 2185PC:MD04
- LO|PP|MRP|Eavuation|MD04 Stock/Req list| 5.4.5.1.SCR:Start - DDN:Material = Gearing-0005 - DDN:Plant = 1000 5.4.5.2.SCR:Main - LIN:PlOrd:Gearing-0005 2185PC|DoubleClick| - SCR:Additional data of MRP element - BTN:Purch.Req.|SCR:New Purchase Requisition - TBX:Converted Quantity = 2185 (In case of numeric diference, its possible to manually override quantity here!) - BTN:Save, Take note of purch.req number: - BTN:Update:MRP element shifts from LIN:PlOrd - LIN:PurchReq Gearing-0005 2185PC|DoubleClick| - SCR:Additional data of MRP element - BTN:Purch.Ord.|SCR:New Purchase Order - FRM:Left - LIN:All open purchase requisitions select - BTN:Copy(copies them to a purchase order) - FRM:Right:Observe order Header|Item|Item detail - BTN:Save, Take note of purch.ord number: - BTN:Update:MRP element shifts from LIN:PurchReq - LIN:PurchOrd Gearing-0005 2185PC
4500017392 1001389000010
5.4.15.MM:Check production confirmation: Basis-Module0005:MD04

- LO|PP|MRP|Evaluation|MD04 Stock/Req list| 5.4.15.1.SCR:Start - DDN:Material = Basis-Module-0005 - DDN:Plant = 1000 5.4.15.2.SCR:Main - LIN:OrdRes, Basis-Module-0005, Demand=1371, Available=1371(Should be equal!) - LIN:Components:available stock should be reduced
5.4.16.MM:Goods Issue: SpeedStar-0005: MB1A
- Manually modify quantity of Breaks from 2742 to 2942PC becasue 200 Breaks destroyed - Take note of document number: 4900038403
5.4.6.MM:Create Purchase Order (RawMat):Wheel-0005 4570PC:MD04 5.4.7.MM:Create Purchase Order (RawMat):Chain-0005 2285PC:MD04
- 4386PC, Take note of purch.req number: 1001389100010 - Take note of purch.ord number: 4500017393
5.4.17.PP:Confirm production order: SpeedStar -0005: CO15 5.4.18.MM:Check production confirmation: SpeedStar -0005:MD04
5.4.8.MM:Create Purchase Order (RawMat):Carb-Frame0005 1371PC:MD04

- LO|MM|Inventory|Goods move|Goods receipt|For purchase order|MIGO PO number known| 5.4.9.1.SCR:Start 5.4.9.1.1.FRM:Head - DDN:Document = GoodsReceipt - DDN:Reason = With Purchase Order - TBX:DocNumber = 4500017392 - KEY:Enter - DDN:DocumentDate = Now( Vendor immediately delivers!: - PurchaseOrder will be eliminated, - Stock created, - But OrderReserved still there! because of Prod.Order of Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage, Aaa|Bbb| -Menu/Submenu, SCR-Screen, FRM-Frame, IDUniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox
5.4.9.MM:Post Goods Receipt: Gearing-0005:MIGO
5.5.Production Closing Operations 5.5.1.MM:Check Goods Movement Documents: SpeedStar-0005: MB51
- LO|MM|Inventory|Environment|List displays|MB51 Material docs| 5.5.1.1.SCR:Start - DDN:Material = SpeedStar-0005 - DDN:Plant = 1000 5.5.1.2.SCR:Material document list 5.5.1.2.1.FRM:Head - LIN: SpeedStar-0005, Take note of document number: 4900038404 |DoubleClick| 5.5.1.2.2.FRM:Item detail 5.5.1.2.2.1.TAB:DocInfo - BTN:FI Documents - LIN:Costing document| - Observe actual costing = 2377EUR - LIN:Accounting document| - Observe actual stock value = 1371PC 2377EUR
PaulerSoft CANAL notes, page: 24 Individal processing| 5.5.4.2.SCR:Start - DDN:ControllingArea = 1000 - DDN:Order = 60003526 (Speedstar-0005) - DDN:Period = Current month - DDN:Fiscal year = Current year - DDN:ProcessType = Auto - CHK:Test run = False - BTN:Run 5.5.4.3.SCR:List 5.5.4.3.1.BTN:Column selector 5.5.4.3.1.1.SCR:Detailed list: - BTN:Sender:Observe senders - BTN:Receiver:Observe receivers
5.5.2.PP:Variance and cost analysis: SpeedStar-0005: CO03
- LO|PP|Prod control|Order|CO03 Display| 5.5.2.1.SCR:Start - DDN:ProdOrder = 60003526 ( SpeedStar-0005) 5.5.2.2.SCR:Production order header 5.5.2.2.1.BTN:Components 5.5.2.2.1.1.LIN:Breaks - Component|Component details| - TBX:Requirement quantity = 2742 - TBX:With drawal quantity = 2942 (Observe difference! ) 5.5.2.2.2.BTN:Operations 5.5.2.2.2.1.LIN:0010 - Operation|Operation details| - TAB:Quantities/Activities - TBX:Confirmed yield = 1371 - TBX:Opertaion quant = 1371(Should be equal! ) 5.5.2.2.3.Goto|Cost|Analysis|SCR:Target/Actual comparison| Cost Planned Actual Variance Material Goods Issue Operations Setup Machine Labor Total 3,249,976- 19,862- 3,230,1135.5.2.2.4.Header|Settlement rule| 5.5.2.2.4.1.LIN:SpeedStar-0005 - Cat = Mat(Costs are debited on material) - Price control = - V:Cost variation is spread over entire stock with moving average - S:Cost variation is incorporated only in current standard price
5.5.5.1.DEF:OrderStatus = TECO(Technical completion) - Staus takes out order from MRP, but not dlete it - However, all its dependents documents are deleted - Order reservations - Capacity requistions - Purchase requistions 5.5.5.2.DEF:OrderStatus = CLSD(Closed) 5.5.5.2.1.Prerequisites: - Order status: CRT REL TECO - Balance is 0 - No open dependent documents: purch req. 5.5.5.2.2.Properties: - Cannot be changed together with all existing dependents - LO|PP|Prod contr|Order|CO02 Change| 5.5.5.3.SCR:Start - DDN:Order = 60003526 (Speedstar-0005) 5.5.5.4.SCR:Main 5.5.5.4.1.Goto|Costs|Analysis|SCR:Target/Actual comparison| Cost PlannedActualVariance Material Goods Issue Operations Setup Machine Labor Total 9,9050- 9,905 5.5.5.4.2.Functions|Restrict processing| 5.5.5.4.2.1.|Complete technically 5.5.5.4.2.2.|Close 5.5.5.5.BTN:Save
5.5.5.PP:Order Completion and Closing: SpeedStar-0005: CO02
5.6.Order Information System 5.6.1.PP:Production Order Report: SpeedStar-0005: COOIS
5.5.3.FI:Period end summary of cost variances by category: SpeedStar-0005: KKS2
- LO|PP|Prod contr|Period end closing|Variations|KKS2 Individal processing| 5.5.3.1.SCR:Start - DDN:ControllingArea = 1000 - DDN:Order = 60003526(Speedstar-0005) - DDN:Period = Current month - DDN:Fiscal year = Current year - CHK:Selected Target Cost Version 000 = True - CHK:Test run = False - CHK:Detail list = True 5.5.3.2.SCR:List 5.5.3.2.1.FRM:Head 5.5.3.2.1.1.LIN: Order = 60003526 (Speedstar-0005) - BTN:Cost elements 5.5.3.2.2.FRM:Item 5.5.3.2.2.1.LIN:Brakes - BTN:Variances - Observe variance type: Input Quantity - Observe reason it was calculated: 30000 5.5.4.1.DEF:Order settlement: - Automatically balances order costs by settlement rules among senders and receivers - LO|PP|Prod contr|Period end closing|Settlement|KO88
- LO|PP|Shop floor control|Information system|COOIS Order information system| 5.6.1.1.SCR:Start - DDN:List = PPIOH000(Order Headers) - DDN:Layout = 000000000001(Standard layout) - DDN:Material = SpeedStar-0005 - DDN:Production Plant = 1000 - CHK:Plnnd orders = True - BTN:Run 5.6.1.2.SCR:ALV Grid - Realign columns: Material number, Material description - BTN:Sum:Add Sum to column Target quantity - BTN:SaveLayout - TBX:Save layout = Manu-0005 - TBX:Name = Manufacturing 0005 Layout - CHK:User-specific = True
5.5.4.PP:Order Settlement: SpeedStar-0005: KO88
6.Warehouse Management Scenario

6.1.Plot of Scenario 6.1.1.MM:Material master:
- Create material SpeedStar-0005 at new organizational level: - Plant = 1200(Dresden) - Storage location = 0140 - Warehouse number = 140 - Storage type = 002 - Make stock transfer order 1000PC of SpeedStar-0005 To: - Plant = 1200(Dresden) - Storage location = 0140 - Warehouse number = 140 - Storage type = 002 - From: - Plant = 1000(Hamburg) - Storage location = 0001 - Warehouse number = 001 - Perform PI for material SpeedStar-0005, Plant1000, Storage0001: - Minus 21 difference (350 instead 371) found, post it - Set cycle counting for all FERT materials at Plant 1000 based on consumption from 2004
6.1.2.LO:Warehouse management:
6.1.3.LO:Physical inventory management
6.2.DEF:Goods Movements 6.2.1.DEF:Goods receipt 6.2.2.DEF:Goods issue
PaulerSoft CANAL notes, page: 25 6.2.3.2.1.3.ALT:Inter-Company Stock to Stock - Same as above - Just 2 accounting documents are created: - Issuing Companys G/L account: - Offset entry - Moving stock valuated - Receiving Companys G/L account 6.2.3.2.1.4.ALT:Without Stock Transport Order - Manual handling 6.2.3.2.1.5.ALT:With Stock Transport Order - Provides integrated handling: - Can be auto-created from Purchase Orders - Can store carrier and freight cost data - Goods receipt can be directed to - Warehouse:(Unrestricted/QualInsp/Blocked) - Directly for Consumption - Creates Order history entry - Has separate control codes: - 351:UnrestrictedInTransfer with Transport order - 101:InTransfer Unrestricted/QualInsp/Blocked with Transport order 6.2.3.2.2.ALT:Transfer posting - Results in change of Stock ID, Stock Category, - But does not necessarily involves physical movement 6.2.3.2.2.1.Material to Material 6.2.3.2.2.2.Blocked Quality inspection Unrestricted 6.2.3.2.2.3.Consigment to Warehouse
- Increase of warehouse stock from vendor, production, stock transfer - Decrease of warehouse stock to customer, production, stock transfer
6.3.DEF:Organizational hierarchy 6.3.1.Client
- Transferring stock from one storage to another 6.2.3.1.PROC: 6.2.3.1.1.ALT:Single step - Two documents created simultaneously 6.2.3.1.1.1.Goods Issue 6.2.3.1.1.2.Goods Receipt 6.2.3.1.2.ALT:Two step - Two documents created separately 6.2.3.1.2.1.Goods Issue - Creates accounting document, stock is valuated at issuing storage 6.2.3.1.2.2.Stock is In transfer status - Cannot be opened at Inventory Times, as this cannot be accounted there 6.2.3.1.2.3.Goods Receipt 6.2.3.2.Types: 6.2.3.2.1.ALT:Stock Transfer - Always involves physical movement 6.2.3.2.1.1.ALT:Intra-Plant Stock to Stock - One step - 2 documents simultaneously - Goods issue document - Goods receipt document - No accounting document, except material valuation changes - Can transfer all Stock categories: - 311:UnrestrictedUnrestricted - 323:QualInspQualInsp - 325:RestrictedRestricted - 321: QualInspUnrestricted - 349: RestrictedQualInsp 6.2.3.2.1.2.ALT:Inter-Plant Stock to Stock - Two step - 2 documents separately - Goods issue document: Removal from storage - Transfers stock into receiving location - But in transfer status - Creates 1 accounting document if 2 plants are not in the same valuation area:Moving stock is valuated at the price of issuing storage - Goods receipt document: Putaway/Placement in storage - At receiving location changes in transfer status to unrestricted usage - Does not create accounting document - Can transfer only unrestriced stock throgh in transfer state: - 303:UnrestrictedInTransfer - 305:InTransferUnrestricted - 301:UnrestrictedUnrestricted
6.2.3.DEF:Inter Stock Transfer
6.3.1.1.Company 6.3.1.1.1.DEF:Transportation planning point: - Settlement of transportation costs/profits - Can be assigned only one company 6.3.1.1.1.1.DEF:Shipping point: - Can serve multiple plants 6.3.1.1.1.2.Plant: - Can have multiple shipping points and - DEF:Storage: - Site of quantitative inventory management - Assigned to one plant - Can be assigned to maximum one warehouse, but it is not compulsory to assign any 6.3.1.1.2.DEF:Warehouse: - PK: Warehouse Number - Can be assigned to multiple Plant|Shipping point|Strorage combination 6.3.1.1.2.1.DEF:Storage type:(Goods receipt/issue) - DEF:Storage area - DEF:Picking area - DEF:Storage section - DEF:Storage bin: Form master dat recors - Connects MM and SD in LO module
6.4.DEF:LO:Logistics Execution process, Warehouse Mngmt.

6.4.1.1.ALT: Initiated by Delivery 6.4.1.1.1.Purchase order 6.4.1.1.2.Inbound delivery 6.4.1.1.3.Putaway with transfer order 6.4.1.1.4.Confirm transfer order 6.4.1.1.5.Goods receipt posting 6.4.1.2.ALT: Initiated by Document Posting 6.4.1.2.1.Goods receipt posting - Examines whether Plant|Shipping point|Storage combination is assigned to warehouse. If yes, then: 6.4.1.2.2.Transfer Requirement - Material is placed in goods receiving area of warehouse with registered Quant quantity 6.4.1.2.3.Putaway with Transfer order - Destination Storage type|Area|Section|Bin is determined 6.4.1.2.4.Confirm transfer order 6.4.2.1.ALT: Initiated by Delivery 6.4.2.1.1.Sales order 6.4.2.1.2.Outbound delivery 6.4.2.1.3.Picking with transfer order 6.4.2.1.4.Confirm transfer order 6.4.2.1.5.Goods issue posting 6.4.2.2.ALT: Initiated by Document Posting 6.4.2.2.1.Goods issue posting 6.4.2.2.2.Transfer Requirement
6.4.1.Goods Receipt
6.4.2.Goods Issue
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 6.4.2.2.3.Picking with transfer order 6.4.2.2.4.Confirm transfer order
6.5.MM:Maintain master data 6.5.1.MM:Extend material master to new plant:Speedstar0005 Plant1200:MM01

- LO|MM|Master|Material|Material|Create|MM01 6.5.1.1.SCR:Start - DDN:Material = SpeedStar-0005 - DDN:Sector = Mechanical engineering - DDN:Type = FERT(Finished product) - DDN:Copy from = SpeedStar-0005 - BTN:SalesOrg: - FRM:Organizational level - DDN:plant = 1200(Dresden) - DDN:storage location = 0140 - DDN:warehouse number = 140 - DDN:storage type = 002 - FRM:Copy from - DDN:plant = 1000(Hamburg) - DDN:storage location = 0001 - DDN:warehouse number = 001 - BTN:Views: General plant1-2, Warehouse1-2, Accounting1 6.5.1.2.SCR:Main 6.5.1.2.1.TAB:General plant1: - KEY:Enter to copy 6.5.1.2.2.TAB:General plant2: - KEY:Enter to copy 6.5.1.2.3.TAB:Warehouse1: - KEY:Enter to copy 6.5.1.2.4.TAB:Warehouse2: - KEY:Enter to copy 6.5.1.2.5.TAB:Accounting1: - KEY:Enter to copy 6.5.1.2.6.BTN:Save
PaulerSoft CANAL notes, page: 26 - CHK:ItemOK = True 6.6.3.1.2.BTN:Save - Take note of material document number: 4900038468 - 371PC will stay unrestricted stock in Plant 1000 - 1000PC will be stock on order in Plant 1200 - LO|MM|Inventory|material doc|MB03 Display 6.6.4.1.SCR:Start - DDN:Material doc number = 4900038468 - DDN:Year = Current 6.6.4.2.SCR:Main Item Material PlantStorageMovCodeSign 01 SpeedStar-0005 1000 0001 351 02 SpeedStar-0005 1200 351 + 6.6.4.2.1.BTN:Accounting documents 6.6.4.2.1.1.SCR:List documents in accounting - LIN:Accounting document|DoubleClick AccountAmount 792000 2.377.740,00792000 2.377.740,00
6.6.4.LO:Display material document:4900038468:MB03
- LO|MM|Inventory|Goods movement|Goods receipt|For purchase order|MIGO PO number known 6.6.5.1.SCR:Main - DDN:Document = Display - DDN:Reason = Material document - DDN:Document number = 4900038468 6.6.5.1.1.FRM:Item 6.6.5.1.1.1.TAB:Transfer posting - FRM:Destination - BTN:View|SCR:Item detail screen - LIN: 0140 LE Dresden|BTN:Detailed Display - Take note of on-order stock quantity: 1000
6.6.5.LO:Display material document: 4900038468: MIGO
6.6.LO:Warehouse management 6.6.1.LO:Display stock overview: SpeedStar-0005: MMBE
6.6.6.LO:Post Goods Receipt: SpeedStar-0005: Plant1200, Storage0140, 1000PC: MIGO

6.6.6.1.SCR:Main - DDN:Document = Goods receipt - DDN:Reason = Purchase order - DDN:Stock transport order number = 4500017440 - DDN:Plant = Empty! 6.6.6.1.1.FRM:Head - TBX:Delivery note = * 6.6.6.1.2.FRM:item detail 6.6.6.1.2.1.TAB:Material - DDN:Material = SpeedStar-0005 6.6.6.1.2.2.TAB:Quantity - TBX:Quantity = 1000 6.6.6.1.2.3.TAB:Where - DDN:Plant = 1200 - DDN:Storage = 0140 - CHK:ItemOK = True 6.6.6.1.3.BTN:Save - Take note of material document number2: 5000012473
- LO|LO Ex|Inernal Warehouse Proc|Bins and Stock|Display| MMBE Total stock per material 6.6.1.1.SCR:Start - DDN:Material = SpeedStar-0005 - DDN:Plant = 1000 1200 6.6.1.2.SCR:Main - SpeedStar-0005 - Hamburg - 1371PC
6.6.2.LO:Create stock transport order: SpeedStar-0005: 1000PC: ME21N

- LO|MM|Purchase|Purchase Order|Create|ME21N Vendor/Plant known 6.6.2.1.SCR:Main - DDN:Document = GST(GTS Stock Transf Ord) - DDN:Suppl Plant = 1000 6.6.2.1.1.FRM:Head 6.6.2.1.1.1.TAB:Org.Data - DDN:Company = 1000 - DDN:Purch.Org = 1000 - DDN:Purch.Group = 000 6.6.2.1.2.FRM:Item 6.6.2.1.2.1.LIN:10: - COL:Material = Speedstar-0005 - COL:PO quantity = 1000 - COL:Plant (Plnt) = 1200 (Dresden) - COL:Storage location (SLoc) = 0140 (LE Dresden) 6.6.2.1.3.BTN:Save - Take note of stock transport order number: 4500017440 - 1371PC will stay unrestricted stock in Plant 1000 - 1000PC will be stock on order in Plant 1200
6.6.3.LO:Post Goods Issue: SpeedStar-0005: Plant1000, Storage0001, 1000PC: MIGO

- LO|MM|Inventory|Goods movement|Goods receipt|For purchase order|MIGO PO number known 6.6.3.1.SCR:Main - DDN:Document = Goods Issue - DDN:Reason = Purchase order - DDN:Document number = 4500017440 - DDN:Plant = Empty!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 6.6.3.1.1.FRM:item detail 6.6.3.1.1.1.TAB:Where - DDN:Storage = 0001
6.6.7.LO:Display Accounting Document:5000012473: MB03
- LO|MM|Inventory|material doc|MB03 Display 6.6.7.1.SCR:Start - DDN:Material doc number = 5000012473 - DDN:Year = Current 6.6.7.2.SCR:Main 6.6.7.2.1.BTN:Accounting documents - No accounting doc here, as this is the recieving side!
6.6.8.LO:Display target storage type and transfer req. number:5000012473: MIGO

6.6.8.1.SCR:Main - DDN:Document = Display - DDN:Reason = Material document - DDN:Document number = 5000012473 - DDN:Plant = Empty! 6.6.8.1.1.FRM:item detail 6.6.8.1.1.1.TAB:WM(Warehouse management) - Take note of storage type1: 902(GR Area External Receipts) - Take note of TR number: 12
6.6.9.LO:Convert Transfer req. into Transfer order (Putaway): 12: LB11
- LO|LO Exec|Inbound proc|Goods receipt|Putaway|Create transfer order|LB11 For material 6.6.9.1.SCR:Start - DDN:Warehouse number = 140 - DDN:Material = SpeedStar-0005 - DDN:Plant = Empty! 6.6.9.2.SCR:Main - LIN: TR Number = 12|Select - BTN:TO in Foreground|SCR:Create TR and TO: - Edit|Putaway|Background| - SCR:Prepare for putaway - LIN:10 - Take note of new storage type: 002 - Take note of storage bin: 01-03-02 6.6.9.2.1.BTN:Save - Take note of transfer order number: 0000000012
6.6.10.LO:Check total stock: SpeedStar-0005, Warehouse0140: LS26
- LO|LO Exec|Internal Warehouse Proc|Storage and Bin| Display|LS26 Total stock per material 6.6.10.1.SCR:Start - DDN:Warehouse = 140 - DDN:Material = SpeedStar-0005 6.6.10.2.SCR:Main - Take note of putaway type: 002 - Take note of pick type: 902 - LO|LO Exec|Inbound Proc|Goods receipt|Putaway|Confirm transfer order|Single document|LT12 In one step 6.6.11.1.SCR:Start - DDN:Transfer order number = 0000000012 - DDN:Warehouse number = 140 6.6.11.2.SCR:Main 6.6.11.2.1.BTN:Save - Plant 1000 Hamburg: 371PC SpeedStar-0005 Unrestricted stock - Plant 1200 Dresden: 1000PC SpeedStar-0005 Unrestricted stock, type 002
6.6.11.LO:Confirm transfer order: 0000000012: LT12
PaulerSoft CANAL notes, page: 27 - Storage bin/Material group - Batch 6.7.2.1.2.Content 6.7.2.1.2.1.Header - PK: PI Document number - FK: PI Number:groups PI documents in processing groups - Status:(Preprocess,Count,Post,Recount) - Planned count date - Deleted flag - Posting block indicator: - Block stock any direction transfer of material in SMU - Updating Material master|Storage location|Block = X(Blocked by PI) - Freeze book inventory flag: - If full blocking is not feasible for the material during recount (eg. Production needs it continously) - It freezes book inventory for a time period, collecting changes in the meantime separately - Then at the end it summarizes differences 6.7.2.1.2.2.Items - Stock type - Material - Batch - Quantity - Status:(Preprocess,Count,Post,Recount) - Deleted flag 6.7.2.2.Enter count results - Can be done with or without reference to PI document - Variance % can be set for automatic difference warning - Zero count can be set: default value of uncounted items - Differences from book inventory balances are computed at saving - List of differences is a report of Item(counted,book,difference)( quantity,value) with the following functions: - Display PI document - Re-count PI Document|Item at important SMUs - Post PI Document 6.7.2.3.Post inventory differences 6.7.2.3.1.Create material document - Update stock quantity - Update stock value - Reason of difference:(Theft, etc.) - Inventory tolerance group of user - Document tolerance: exceeding blocks all posting activity of user - Item tolerance: exceeding blocks only posting current document 6.7.2.3.2.Create accounting document - Update stock G/L accounts - Posting date is automatically set to Counting date (Back-posting should be allowed in customizing) - All posting should be within the current fiscal year + 1 months tolerance 6.7.3.1.Determine Cycle Count Indicator (CCI) of materials - Time period to launch periodic PIs 6.7.3.1.1.ALT:ABC analysis - More frequently consumed materials in consumption frequency distribution of historic data at storage will get more frequent inventory 6.7.3.1.2.ALT:Actual consumption analysis - The same, from actual consumption data of material master 6.7.3.1.3.ALT:Requirement analysis - Use all planned MRP items data for analysis 6.7.3.1.4.ALT:Manual set - Overrides automatic settings 6.7.3.2.Launch Periodic PIs: - For all materials, date of last inventory is stored - PI Documents are created by batch input session taking in consideration cycle lenght and last inventory date of materials
6.7.3.PROC:Cycle Counting
6.7.Physical inventory management 6.7.1.DEF:Stock Management Unit (SMU)
- Indivisible part of material inventory - Separate inventory item in bookkeeping - Their inventory differences are posted to: - MRP: Modify planning - Accounting: Correct value of Current assets
6.7.2.1.Create Physical Inventory (PI) Document - Generates printed output - Of selected range of SMUs - To record their counting 6.7.2.1.1.Grouping - Plant - Storage - Stock Type/special stock:(Unrestr,QualInsp,Blocked) - Vendor/Customer/Project Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage, Aaa|Bbb| -Menu/Submenu, SCR-Screen, FRM-Frame, IDUniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox
6.7.2.PROC: Physical inventory (PI)
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 6.7.3.3.Count entry methods: - ALT: Auto-create non-existing PI Doc at entering count then post it - ALT: Enter count in existing PI Doc then post it - ALT: Enter count, PI Doc is not created before posting
6.7.4.MM:Create PI Document:Speedstar-0005, Plant1000, Storage0001:MI01

- LO|MM|PI|PI Doc|MI01 Create 6.7.4.1.SCR:Start - DDN:Date = Now - DDN:Plant = 1000 - DDN:Storage = 0001 - CHK:Post block = True(Block material until inventory counted) - This should set also Material master|TAB:Stor.loc.stock| CHK:Phys Inv Block = True - TBX:PI Number = INV0005 6.7.4.2.SCR:Main 6.7.4.2.1.LIN:01 - Material = SpeedStar-0005 6.7.4.2.2.BTN:Save - Take note of PI Doc number: 100001240 - LO|MM|PI|Inventory count|MI04 Enter 6.7.5.1.SCR:Start - DDN:PI Doc number = 100001240 6.7.5.2.SCR:Main 6.7.5.2.1.LIN:SpeedStar-0005 - TBX:Quantity = 350 6.7.5.2.2.BTN:Save
6.7.5.MM:Carry out PI Count:100001240:MI04
6.7.6.MM:Display difference list and post it:100001240:MI20
- LO|MM|PI|Difference|MI20 Difference list 6.7.6.1.SCR:Start - DDN:PI Doc number = 100001240 6.7.6.2.SCR:Main 6.7.6.2.1.LIN:SpeedStar-0005 21PC|Select - BTN:Post difference 6.7.6.3.SCR:Start 6.7.6.3.1.BTN:Save - Take note of Material Doc number: 4900038469 - Check out reduction of unrestricted stock in MD04 - Check out material doc in MB03 and its accounting docs - LO|MM|PI|PI Doc|MI03 Display 6.7.7.1.SCR:Start - DDN:PI Doc number = 100001240 - BTN:View|SCR:OverView - BTN:Statistics|SCR:Statistics - Check out counting statistics
6.7.7.MM:Display PI Doc/statistics:100001240:MI03
6.7.8.MM:Set Cycle Counting: Mat.type=FERT, Plant1000: MIBC
- LO|MM|PI|Special proc|Cycle counting|MIBC Set CC Indicator 6.7.8.1.SCR:Start - DDN:Material type = FERT - CHK:All materials held in stock = True - DDN:Consumption/usage = 01.01.2004 - Now - CHK:Display list first = True - BTN:Run 6.7.8.2.SCR:Main 6.7.8.2.1.LIN:SpeedStar-0005|Select 6.7.8.2.1.1.BTN:Change CC Indicator - SCR:Change CC indicator - TBX:CC Phys Inv = C(C category material in ABC analysis) 6.7.8.2.2.BTN:Save
7.Sales Scenario
7.1.Plot of Scenario 7.1.1.SD:Create Customer Master:
Create customer 50005 At Copany1000, SalesOrg1000, Channel10,12, Divis00 Gabor Pauler, Customer-0005, Stuttgart , DE Account 140000, SalesDistr 000002, ShipCond 02(Standard), Incoterms EXW, PayTerm 0001(Immediate), Tax 1(Assesible)
7.1.2.SD:Create Product-specific condition:
- SpeedStarlett-0005|Division 00: PR00: 1-499PC 2500EUR, 5002300EUR - Customer 50005:PR00: 1-499PC 2400EUR, 500- 2200EUR - 0005-Order:500PC SpeedStarlett-0005 by customer 50005 - Confirm on date: Now
PaulerSoft CANAL notes, page: 29 7.3.1.4.5.Freight cost 7.3.1.4.6.Incoterms 7.3.1.5.Output master - Electronic/paper documents send to external party: - Output type: Based on a given SAP doc - Media: EDI, fax, e-mail, etc, tools to send - Partner function to send to - Conditions to send at - Time periods to send 7.3.1.6.Customizing control tables
7.1.3.SD:Create Customer-specific condition: 7.1.4.SD:Create Sales Order:
7.3.2.SD:Create Customer Master:50005 at Comp1000, SlsOrg1000, Chn10, Div00:XD01
7.1.5.PP:Manufacture Sales Order: 7.1.6.SD:Create delivery:

- Create and deliver on date: Now - Enter Incoming payment:1309000EUR to BankAcct 113109 of Cust 50005
7.1.7.FI:Enter Incoming payment: 7.2.SD:Organizational levels 7.2.1.Client
7.2.1.1.Company 7.2.1.1.1.Sales Area - Combination of: 7.2.1.1.1.1.Sales Org - Assigned to 1 company - Negotiates sales conditions - Carries resposibility for Customer recourse - It has min 1, max any number of: 7.2.1.1.1.2.Distribution channel 7.2.1.1.1.3.Division: - Product or service group 7.2.1.1.2.Plant 7.2.1.1.2.1.Storage - Can be assigned to one plant 7.2.1.1.2.2.Shipping point - Can be assigned to more plants
7.3.Create Master data 7.3.1.DEF: Data sources of SD documents
7.3.1.1.Customer master 7.3.1.1.1.TAB:General data 7.3.1.1.2.TAB:Sales area related 7.3.1.1.2.1.Partner functions - Sold-to-party - Ship-to-party - Bill-to-party - Payer 7.3.1.1.3.TAB:Company related 7.3.1.2.Material master 7.3.1.2.1.TAB:Basic 7.3.1.2.2.TAB:SalesOrg 7.3.1.2.3.TAB:Salesgeneral/Plant 7.3.1.2.4.TAB:Purchasing 7.3.1.3.Customer-material inforecord - FK:Customer - FK:SalesOrg - FK:Channel - FK:Material - FK:Customer material number - FK:Condition - Material description at customer - Shipping details 7.3.1.4.Condition master 7.3.1.4.1.Price 7.3.1.4.1.1.Types - Material - Customer - Price list 7.3.1.4.1.2.Can be specified by any combination of - Cust group|Customer - Material group|Material - Pricing group 7.3.1.4.2.Surcharge 7.3.1.4.3.Discount 7.3.1.4.4.Tax
- LO|SD|Master data|Business parners|Customer|Create| XD01 Complete 7.3.2.1.SCR:Start - DDN:Account group = 0001(sold-to-party) - DDN:Customer = 50005 - DDN:Company code = 1000 - DDN:Sales organization = 1000 - DDN:Distribution channel = 10 - DDN:Division = 00 7.3.2.2.SCR:Main 7.3.2.2.1.TAB:Address - TBX:Name = Gabor Pauler - TBX:Search term = Customer-0005 - TBX:City = Stuttgart - DDN:Country = DE (Germany) - DDN:Transportation zone = 0000000001 - DDN:Language = German 7.3.2.2.2.TAB: Control|KEY:Enter 7.3.2.2.3.TAB: Payment|KEY:Enter 7.3.2.2.4.TAB: Marketing|KEY:Enter 7.3.2.2.5.TAB: Unloading|KEY:Enter 7.3.2.2.6.TAB: Export|KEY:Enter 7.3.2.2.7.TAB: Contact pers|KEY:Enter 7.3.2.2.8.BTN:Company code data 7.3.2.2.8.1.TAB:Account management - DDN:Reconciliation account = 140000 7.3.2.2.8.2.TAB:Paym trans|KEY:Enter 7.3.2.2.8.3.TAB:Correspondence|KEY:Enter 7.3.2.2.8.4.TAB:Insurance|KEY:Enter 7.3.2.2.9.BTN:Sales area data 7.3.2.2.9.1.TAB:Sales - DDN:Sales district = 000002 7.3.2.2.9.2.TAB:Shipping - DDN:Shipping conditions = 02 (Standard) - DDN:Delivering plant = 1000 7.3.2.2.9.3.TAB:Billing documents - DDN:Incoterms = EXW(Ex Works) Hamburg - DDN:Terms of Payment = 0001(Immediately payable without deductions) - DDN:Tax classification = 1 (Assessable) 7.3.2.2.9.4.TAB:Partner functions|KEY:Enter 7.3.2.2.10.BTN:Save - LO|SD|Master data|Business parners|Customer|Create| VD01 Sales and Distr 7.3.3.1.SCR:Start - DDN:Account group = 0001(sold-to-party) - DDN:Customer = 50005 - DDN:Sales organization = 1000 - DDN:Distribution channel = 12 - DDN:Division = 00 7.3.3.1.1.FRM:Reference to - DDN:Customer = 50005 - DDN:Sales organization = 1000 - DDN:Distribution channel = 10 - DDN:Division = 00 7.3.3.2.SCR:Main 7.3.3.2.1.BTN:Save
7.3.3.SD:Extend Customer Master:50005,Chn12:VD01
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. - LO|SD|Master data|Business parners|Customer|Display| XD03 Complete 7.3.4.1.SCR:Start - DDN:Customer = 50005 - DDN:Company = 1000 - DDN:Sales organization = 1000 - DDN:Distribution channel = 12 - DDN:Division = 00 7.3.4.2.SCR:Main 7.3.4.2.1.BTN:Sales area data 7.3.4.2.1.1.TAB:Sales - Take note of code and function of customer group: Empty,
Identifies a particular group of customers for the purpose of pricing or generating statistics
7.3.4.SD:Display Customer Master:50005:XD03
7.3.4.2.1.2.TAB:Billing documents - Take note of code and function of terms of paymt: Sets
cash discount and payment periods 0001,Payable immediately due net
7.3.4.2.2.BTN:Company code data 7.3.4.2.2.1.TAB:Account management - Take note of code and function of reconciliation account:
account which is updated parallel to the subledger account for normal postings, 140000
7.3.5.SD:Create Product-specific condition:SpeedStarlett0005:MM02

- LO|SD|Master data|Products|Material|Other|MM02 Change 7.3.5.1.SCR:Start - DDN:Material = SpeedStarlett-0005 - BTN:OrgLevel|SCR:OrgLevel - DDN:Plant = 1000 - DDN:SalesOrg = 1000 - DDN:Channel = 10 Valid only for this channel! - BTN:View = SalesOrg1 7.3.5.2.SCR:Main 7.3.5.2.1.TAB:SalesOrg1 - DDN:Division = 00 7.3.5.2.1.1.BTN:Conditions|SCR:Condition PR00 - DDN:Valid from = Now - DDN:Valid to = 31.12.9999 - FRM:Scales QuantAmount 1 2500 500 2300 7.3.5.2.2.BTN:Save
PaulerSoft CANAL notes, page: 30 - 01:Daily check - 02:Individual reqirement: recommended for finished products 7.4.1.3.2.Scope - Current stock - Available To Promise (ATP) 7.4.1.4.MRP - Material Availability Date = Loading Date Max(Pick/Pack Time, Transp.Lead Time) 7.4.1.5.Procurement 7.4.1.5.1.ALT:Production - Production Order Datei = Material Availability Datej Production Timei - Where: i, j = 1..m components, j-main component, i-sub component 7.4.1.5.2.ALT:Purchasing - Purchase Order Datei = Material Availability Datej Inbound Delivery Timei - Where: i, j = 1..m components, j-main component, i-sub component 7.4.1.6.Shipping - Transport Plan Date = Loading Date Transp.Lead Time - Loading Date = Goods Issue Date Loading Time - Goods Issue Date = Required Delivery Date Transit Time - Required Delivery Date 7.4.1.7.Billing 7.4.1.8.Payment - All documents have header and item parts - They inherit data from each other through the process - One ascendant document can have multiple descendants (eg. 1 sales order can generate more deliveries) formin a document hierarchy 7.4.2.1.Optional pre-sales documents - Contact - Inquiry - Quotation - Contract - Sceduling Agreement 7.4.2.2.Sales Order 7.4.2.2.1.Header - Reference to ascendent pre-salesdocument - Sales area - Customer Master - Shipping - Billing 7.4.2.2.2.Item - Material Master - Conditions 7.4.2.2.3.Schedule lines - Date, Quantity 7.4.2.2.4.Incompletion log - Mandantory fields set at customizing - Left empty by user 7.4.2.3.Shipping 7.4.2.3.1.1.Create Outbound Delivery: - Header - Can reference 1 or more sales orders - Shipping point - Due date - Ship-to-party - Item - Material, Quantity, Stock type/Area/Bin to pick from 7.4.2.3.1.2.Picking: - Header - Can reference 1 or more outbound deliveries - Assign warehouse to delivery - Create Transfer Requests Transfer Order MM:Good movements - Item - Material, Quantity, Stock type/Area/Bin to pick from
7.4.2.DEF:Sales Order Document Flow by Milestones
- LO|SD|Master data|Conditions|VK31 Create 7.3.6.1.SCR:Main 7.3.6.1.1.FRM:Left 7.3.6.1.1.1.LIN:Prices - LIN:Individual|DoubleClick 7.3.6.1.2.FRM:Right 7.3.6.1.2.1.FRM:Head - LIN:Cnty Sorg Dchl Cust Mater|BTN:New 7.3.6.1.2.2.FRM:Item - DDN:SalesOrg = 1000 - DDN:Channel = 10 - DDN:Customer = 50005 - FRM:Customer/Material with release status Cond Mat AmntPerUnitValid fromValid to PR00SpeedStarlett-0005 2400 1 PC Now 31.12.9999 - BTN: Scales|FRM:Scales QuantAmount 1 2400 500 2200 7.3.6.1.3.BTN:Save
7.3.6.SD:Create Customer-specific condition:50005:VK31
7.4.SD:Sales order process 7.4.1.PROC:Order-to-cash backward scheduling milestones

7.4.1.1.Pre-sales/CRM 7.4.1.1.1.Mailing campaign 7.4.1.1.2.Tracking lost sales 7.4.1.2.Sales Order - Sales Order Date 7.4.1.3.Availability check - Done at sales order date 7.4.1.3.1.Modes
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 7.4.2.3.1.3.Packing: - Creates Shipping Unit hierarchy: - Container - Pallet - Carton - Can contain mutliple items from multiple deliveries 7.4.2.3.1.4.Goods issue posting: - MM: Re-run MRP - FI:Material stock account decrease - FI:Transfer data for billing due list 7.4.2.3.1.5.Transport planning 7.4.2.3.1.6.Shipment monitoring 7.4.2.4.Billing 7.4.2.4.1.1.Billing document: - FI:Increase Accounts receiveable - FI:Create invoice - FI:Track incoming payments - CO:Update reporting systems - Header - Reference to multiple deliveries - Destination country|Payer - Due date - Item - Material, Quantity, Value, Tax 7.4.2.5.Payment 7.4.2.5.1.1.FI:Update G/L accounts: - Debit payment, - Credit Customer Receivable
PaulerSoft CANAL notes, page: 31 7.4.5.1.2.SCR:MRP Summary - Dependent components not in stock will generate exceptions
7.4.6.MM:Check Stock-Req List:SpeedStarlett-0005, BasisModul2-0005:MD04

- LO|MM|Inventory|Environment|Stock|MD04 Stock/Req list 7.4.6.1.SCR:Start - DDN:Material = SpeedStarlett-0005, Basis-Modul2-0005 - DDN:Plant = 1000 7.4.6.2.SCR:Main - LIN:Sales order, SpeedStarlett-0005, -500PC - LIN:New Planned order, SpeedStarlett-0005, -500PC - LIN:Old Planned order, SpeedStarlett-0005, -914PC-414PC The new sales/planned order will consume old planned order quantity, as this is realization of previously estimated sales!
7.4.7.PP:Create Production Order:Basis-Modul2-0005, 500PC:MD04
7.4.3.SD:Create Sales Order:50005, 500PC SpeedStarlett0005, Plant1000, SalOrg1000, Chnl10:VA01
- LO|SD|Sales|Order|VA01 Create 7.4.3.1.SCR:Start - DDN:Order type = OR(Standard order) - DDN:SalOrg = Empty! - DDN:DistChan = Empty! - DDN:Division = Empty! 7.4.3.2.SCR:Main 7.4.3.2.1.FRM:Head - DDN:Standard order = Empty! - DDN:Sold-to-party = 50005 - TBX:PO Number = 0005-Order - KEY:Enter|SCR:Sales area - LIN:Sorg=1000,Chnl=10,Div=00|Select 7.4.3.2.2.TAB:Sales - DDN:Req. deliv.date = Now + 2 month 7.4.3.2.2.1.FRM:Item LINMaterial Order quantity 01 SpeedStarlett-0005 500PC - KEY:Enter:Autofills master- and condition data - BTN: Conditions: check out preset customer condition price 2200EUR/PC 500PC It overrides material condition! 7.4.3.2.3.BTN:Save - Take note of sales order number: 13370
- Always order first level semi-finished products first! - LO|PP|MRP|Eavuation|MD04 Stock/Req list| 7.4.7.1.SCR:Start - DDN:Material = Basis-Modul2-0005 - DDN:Plant = 1000 7.4.7.2.SCR:Main - LIN:PlOrd:Basis-Modul2-0005 500PC|DoubleClick| - SCR:Additional data of MRP element - BTN:Prod.Order|SCR:New Production Order (Ignore document not valid warning!) - BTN:Material|SCR:Availability check - BTN:Missing parts|SCR:Missing Parts Overview - Only Alu-Frame-0005 is missing, other components are already ordered by previous scenarios - BTN: Release:Status shifts from CRTD REL - BTN:Save, Take note of prod.order number: 60003565 - BTN:Update:MRP element shifts from LIN:PlOrd - LIN:ProdOrd Basis-Modul2-0005 500PC
7.4.8.PP:Create Production Order:SpeedStarlett-0005, 500PC:MD04 7.4.9.MM:Purchasing info record:Alu-Frame-0005, Vendor100268:ME11
- Go upward along BOM hierarchy with production ordering! - Same as above, take note of prod.order number: 60003566
7.4.4.MM:Check MRP Status:SpeedStarlett-0005, BasisModul2-0005, Plant1000:MD04
- LO|MM|Inventory|Environment|Stock|MD04 Stock/Req list 7.4.4.1.SCR:Start - DDN:Material = SpeedStarlett-0005, Basis-Modul2-0005 - DDN:Plant = 1000 7.4.4.2.SCR:Main - LIN:Sales order, SpeedStarlett-0005, -500PC - LIN:No dependent requirements yet!: Basis-Modul2-0005 or any other components
- LO|MM|Purchasing|Master data|Info record|ME11 Create 7.4.9.1.SCR:Start - DDN:Vendor number = 100268 - DDN:Material = Alu-Frame-0005 - DDN:Purchasing Org. = 1000 - DDN:Plant = 1000 - TBX:Info record = Leave empty! - FRM:InfoCtegory - RAD:Standard = True 7.4.9.2.SCR:Main 7.4.9.2.1.BTN:PurchOrgData1 - TBX:Standard Quantity = 100 pieces - TBX:Net price = 250 EURO - BTN:Conditions: - LIN:Condition type:PB00 - BTN:Scales - LIN1:Quantity=1, Amount=250 - LIN2:Quantity=500, Amount=200 7.4.9.2.2.BTN:Save - Take note of Purchase Info Record ID: 5300006331
7.4.5.MM:Run MRP:SpeedStarlett-0005, Plant1000:MD02

- LO|PP|MRP|Planning|MD02 Single item, multi level| 7.4.5.1.1.SCR:Start - DDN:Material = SpeedStarlett-0005 - DDN:Plant = 1000 - DDN:Processing key = NETCH(Only net change) - DDN:Create purchase req. = 2(In opening period) - DDN:Delivery schedules = 3(Apply) - DDN:Create MRP list = 1(Create list) - DDN:Planning mode = 3(Delete and recreate plan) - DDN:Scheduling = 1(Basic dates will be determined) - CHK:Also plan unchanged components = False - CHK:Display results before they are saved = False - CHK:Display material list = False - CHK:Simulation mode = False - KEY:Enter,Enter
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. - LO|PP|MRP|Eavuation|MD04 Stock/Req list| 7.4.10.1.SCR:Start - DDN:Material = Alu-Frame-0005 - DDN:Plant = 1000 7.4.10.2.SCR:Main - LIN:PlOrd:Alu-Frame-0005 500PC|DoubleClick| - SCR:Additional data of MRP element - BTN:Purch.Req.|SCR:New Purchase Requisition - TBX:Converted Quantity = 500 (If <>500, change manually!) - BTN:Save, Take note of purch.req number: 10013953 - BTN:Update:MRP element shifts from LIN:PlOrd - LIN:PurchReq Alu-Frame-0005 500PC|DoubleClick| - SCR:Additional data of MRP element - BTN:Purch.Ord.|SCR:New Purchase Order - FRM:Left - LIN:All open purchase requisitions|Select - BTN:Copy(copies them to a purchase order) - FRM:Right:Observe order Header|Item|Item detail - BTN:Save, Take note of purch.ord number: - BTN:Update:MRP element shifts from LIN:PurchReq - LIN:PurchOrd Alu-Frame-0005 500PC - LO|MM|Inventory|Goods move|Goods receipt|For purchase order|MIGO PO number known| 7.4.11.1.SCR:Start 7.4.11.1.1.FRM:Head - DDN:Document = GoodsReceipt - DDN:Reason = With Purchase Order - TBX:DocNumber = 4500017470 - KEY:Enter - DDN:DocumentDate = Now(Vendor immediately delivers!) - DDN:DelivNote = * 7.4.11.1.2.FRM:Item detail - CHK:ItemOk = True - TAB:Where - DDN:Storage = 0001 7.4.11.1.3.BTN:Save - Take note of goods receipt number: 5000012499 - Before that check stock of Chain-0005, Gearing-0005, Wheels0005 in MD04! - LO|MM|Inventory|Goodsmovement|MB1A Goods issue| 7.4.12.1.SCR:Start - BTN:To order - DDN:OrderNum = 60003565 (Basis-Modul2-0005) 7.4.12.2.SCR:Main - FRM:Items:Check that all components issued from inventory 7.4.12.3.BTN:Save - Take note of document number: 4900038523
4500017470 00010
7.4.10.PP:Order materials:Alu-Frame-0005, 500PC:MD04
PaulerSoft CANAL notes, page: 32 - RAD:Final Confirmation = True 7.4.15.2.SCR:Main - Check goods movement list: SpeedStarlett-0005 7.4.15.3.BTN:Save - Check MD04 for stock
7.4.16.MM:Update Sales order|Schedule lines for pre-date delivery:13370:VA02

- If this is not done, we get ERR:No schedule lines due delivery! - LO|SD|Sales|Order|VA02 Modify 7.4.16.1.SCR:Start - DDN:Standard order = 13370 7.4.16.2.SCR:Main 7.4.16.2.1.BTN: Schedule lines 7.4.16.2.1.1.FRM:Quantities/Deliveries LINDeliveryQuantity 1 Now 500PC 7.4.16.2.2.BTN:Save
7.4.11.MM:Goods receipt:Alu-Frame-0005, 500PC:MIGO
- LO|SD|Ship&Transp|Outbound deliv|Create|Single doc| VL01N With ref to Sales order| 7.4.17.1.SCR:Start - DDN:shipping point = 1000 - DDN:Selection date = Now - DDN:Sales order number = 13370 7.4.17.2.SCR:Main 7.4.17.2.1.TAB:Picking 7.4.17.2.1.1.FRM:Item LINMat PlantStorage 1 SpeedStarlett-0005 1000 0001 7.4.17.2.2.BTN:Save - Take note of Delivery Document Number: 80016247 - DEF:Transfers product in outbound stock area - LO|SD|Ship&Transport|Pick|Create|Transfer order|LT03 Single doc| 7.4.18.1.SCR:Start - DDN:Warehouse number = 010. - DDN:Delivery number = 80016247 - DDN:Run at = Foreground. - DDN:Adopt picking quantity = 1(Include pick quant in deliv) 7.4.18.2.SCR:Main 7.4.18.2.1.BTN:Save - Take note of Transfer Order Number: 0000003150
7.4.17.SD:Create delivery:13370:VL01N
7.4.18.SD:Picking/Create Transfer order:80016247:LT03
7.4.12.MM:Goods issue:Basis-Modul2-0005:MB1A
7.4.13.PP:Confirm Production Order:Basis-Modul20005:CO15
- LO|PP|Production control|Confirmation|Enter|CO15 For order| 7.4.13.1.SCR:Start - DDN:OrderNum = 60003565 (Basis-Modul2-0005) - RAD:Final Confirmation = True 7.4.13.2.SCR:Main - Check goods movement list: Basis-Modul2-0005 7.4.13.3.BTN:Save - Check MD04 for stock
- LO|SD|Ship&Transp|Outbound deliv|Change|VL02N Single doc| 7.4.19.1.SCR:Start - DDN:Delivery doc number = 80016247 7.4.19.2.SCR:Main 7.4.19.2.1.TAB:Picking 7.4.19.2.1.1.FRM:Item LINMat DelivQuantPickQuant 1 SpeedStarlett-0005 500PC 500PC Modify if <> 7.4.19.2.2.Post Goods Issue 7.4.19.2.3.BTN: Document flow: Document DateStatus - Standard order Now Complete - Delivery Now Not complete until billing!
Being proc.
7.4.19.SD:Delivery|Goods issue:80016247:VL02N
- Transfer order Now Complete - Goods Issue Now Complete
- LO|MM|Inventory|Goodsmovement|MB1A Goods issue| 7.4.14.1.SCR:Start - BTN:To order - DDN:OrderNum = 60003566 (SpeedStarlett-0005) 7.4.14.2.SCR:Main - FRM:Items:Check that all components issued from inventory 7.4.14.3.BTN:Save - Take note of document number: 4900038525
7.4.14.MM:Goods issue:SpeedStarlett-0005:MB1A
7.4.15.PP:Confirm Production Order: SpeedStarlett0005:CO15
- LO|PP|Production control|Confirmation|Enter|CO15 For order| 7.4.15.1.SCR:Start - DDN:OrderNum = 60003566 (SpeedStarlett-0005)
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. - LO|SD|Billing|Billing doc|VF01 Create| 7.4.20.1.SCR:Start - DDN:Delivery doc number = 80016247 7.4.20.2.SCR:Main 7.4.20.2.1.TAB:Sales 7.4.20.2.1.1.FRM:Item LINMat Quant Net Value 1 SpeedStarlett-0005 500PC 1100000 7.4.20.2.2.BTN:Coditions Item Amount +Net value 1100000 -Variable cost,Transfer price938870 =Profit margin 161130 =Total amount 1309000 7.4.20.2.3.BTN:Save - Take note of Invoice Number: 90038102
7.4.20.SD:Create Billing Document:80016247:VF01
7.4.21.FI:Enter Incoming payment:1309000EUR to BankAcct113109:F-28
PaulerSoft CANAL notes, page: 33 7.5.1.2.2.1.DEF:Initial list: - Selected infostructure(Characteristics, Key figures) - Time range 7.5.1.2.2.2.DEF:DrillDown - Editor/Display transactions of objects come up 7.5.1.2.2.3.Charting 7.5.1.2.2.4.Statistic tools - Frequencies - Correlations - ABC-analysis - Time series - Classification - Top N - Planned/Actual 7.5.1.2.2.5.Export - Print - Excel - SAP Workplace - LO|SD|Sales|SIS|Order|VA05 List of Sales Orders| 7.5.2.1.SCR:Start - DDN:Customer = 50005 - BTN:OrgData|SCR:OrgData - DDN:SalesOrg = 1000 - DDN:Channel = Empty! - DDN:Division = Empty! 7.5.2.2.SCR:Main ALV Grid - BTN: Change fields| - Select:Plant, Shipping point, Confirmed quant - LO|SD|Sales|SIS|Standard analysis|MCTA Customer| 7.5.3.1.SCR:Start - DDN:SalesOrg = 1000 - DDN:Month from = 01. 2004 - DDN:Month until = Current - Leave other fields empty! 7.5.3.2.SCR:Main - BTN:Save|SCR:Save: - DDN:Name = S0005 - DDN:Descr = Sales Report 0005 - BTN:Save - COL:Sales|Select - BTN:Top N|TBX:Freq = 10 - Take note of biggest customer: Motomarkt Stuttgart - COL:Sold-to-part|Select - Settings| - Characteristics display|Keys&Descriptions :Shows PK - ColWidth|Characteristic|Chars=40 - Edit|Choose key figures| - Add:Open sales order quantity, Billing quantity - Remove:Credit memo - LIN: Motomarkt Stuttgart|Doubleclick| - F5|SCR:Chart fields|Sales
7.5.2.SD:Display Sales Orders:50005:VA05
- FI|FI|Customers|Doc entry|F-28 Incoming payment| 7.4.21.1.SCR:Head - DDN:Document date = Now 7.4.21.1.1.FRM:Bank data: - TBX:account = 113109 - TBX:Amount = 1309000 7.4.21.1.2.FRM:Open item selection - DDN:Account = 50005 - DDN:Account type = D(Customer) 7.4.21.1.3.KEY:Enter 7.4.21.1.4.BTN:Save - Take note of Accounting Doc Number: 1400000034
7.5.3.SD:Carry out Standard Analysis: 50005:MCTA
7.4.22.SD:Display Document Flow summary:

80016247:VL02N
- LO|SD|Ship&Transp|Outbound deliv|Change|VL02N Single doc| 7.4.22.1.SCR:Start - DDN:Delivery doc number = 80016247 7.4.22.2.SCR:Main 7.4.22.2.1.BTN: Document flow: Document DateStatus - Standard order Now Complete - Delivery Now Complete - F2 type Invoice Now FI doc generated - Account doc Now Cleared
7.5.SD:Reporting 7.5.1.DEF:SD:Sales Information System (SIS)

7.5.1.1.Data sources: Document lists 7.5.1.1.1.Online lists 7.5.1.1.1.1.By document area - Sales - Delivery - Billing 7.5.1.1.1.2.By document status - Open - Completed 7.5.1.1.2.Worklists 7.5.1.1.2.1.By User|Role|Right - Sales order - Delivery - Picking - Goods issue - Billing 7.5.1.2.Reports 7.5.1.2.1.Types: 7.5.1.2.1.1.Standard: - Info Structures S001-S500 reserved: - S001:Customer - S002:SalesOffice - S003:SalesOrg - S004:Material - S005:Shipping point - S009:Sales support - S060:Rebate - S066:Credit limit 7.5.1.2.1.2.Flexible: 7.5.1.2.1.3.Individual: - Info Structures S501-S999 in customizing 7.5.1.2.2.Tools:
8.Human Capital Management (HCM) Scenario

8.1.Plot of Scenario: 8.1.1.Maintain organizational structure master data
- Set up a new organizational unit to market and sale products SpeedStar-0005 and SpeedStarlett-0005 8.1.1.1.CO:Create Profit Center: - PROF-0005 into H1100 8.1.1.2.CO:Create Cost Center Group: - H10005 into H1300 8.1.1.3.CO: Create Cost Centers: - Marketing&Sales:CCMSD-0005,CostCtrCat=5 - Marketing:CC-MA-0005,CostCtrCat=8 - Sales:CC-SD-0005,CostCtrCat=8 - Into: - Plant 1000 - CostCtrGrp H10005 - ProfitCtr PROF-0005 8.1.1.4.HCM:Create OrgUnit|Job|Position|Task: - At Company 1000 - Bike Department: DepBike-0005 CCMSD-0005 - Sales SubDepartment: SD-0005 CC-SD-0005 - SalesChief Position:SD-DC-0005 Job: Manage-0005 - Tasks: Mgmt-0005,Acquise-0005 - SalesSecr Position:SD-SE-0005 Job: Sekret-0005 - Tasks: Corresp-0005,Orga-0005 - Marketing SubDepartment: Mark-0005 CC-MA-0005 - MarkChief Position:MA-DC-0005 Job: Manage-0005 - Tasks: Mgmt-0005,Advert-0005 - MarkSecr Position:MA-SE-0005 Job: Secret-0005 - Tasks: Corresp-0005,Orga-0005 8.1.2.1.HCM:Create Job Ads: - 00000365:SD-DC-0005, 100.000,-EUR salary, Secretary 8.1.2.2.HCM:Create Applicant master: - 00001561:Mr. Gabor Pauler to ad 00000365: - Birth dt. = 11.05.1971 - Language = DE (German) - Nationality = DE (German) - Street = Universitaetsstrasse 0005 - Postal code = 45141 - City = Essen - Telephone = +49201-3330005 - Email = Gabor.Pauler@uni-due.de 8.1.2.3.HCM:Update Applicant qualifications: 8.1.2.3.1.Qualifications LINID Name Proficiency 01 50027189 Mangement Experience 0009(Excellent) 02 50025440 Project Management skills 0008(Very high) 03 50025402 Communication Skills 0006(Above-average) 04 50000551 Knowledge of Excel 0007(High) 8.1.2.3.2.Potentials LINID Name 01 50000405 Market research skills 8.1.2.3.3.Preferences LINID Name 01 30010189 Knowledge wordprocessing 8.1.2.3.4.Dislikes LINID Name 01 50034171 French 02 50010176 Presentation sofware 8.1.2.4.HCM:Vacancy assignment: - Applicant 00001561(Gabor Pauler) to Position 50011085 (SDDC-0005) 8.1.2.5.HCM:Evaluate Applicants: Req- RelaLINID Name Proficiency rd tion 0008(Very 01 50025440 Project Man skills Yes = high) 0006(Above 02 50000551 Knowledge of Excel average)
8.1.2.Recruitment process
PaulerSoft CANAL notes, page: 34 - Valid to = 30.LastMo.CurrYr - Employer = Linde AG - City = Essen - Country Key = DE(Germany) - Industry = HITE(High Tech.) - Job = 13(Manager) 8.1.3.1.3.Education - Valid from = 01.01.1999 - Valid to = 31.12.2004 - School = Whatever 8.1.3.2.HCM:Hiring Applicant: 8.1.3.2.1.Create at - Personnel area = 1000 - Position = 50011085(SD-DC-0005) - Personnel number = 120005 - Reason = Empty! - Ref.person = Empty! - Employee group = 1(Active) - Employee subgroup = DS(Managerial employees) 8.1.3.2.2.Personal data - Title = Mr. - Initials = G.P. - Maiden name = Empty - Place of birth = Pecs - Country of birth = HU - Nationality = HU - Marital status = Single - Religion = No church tax liability - Number of children = Empty 8.1.3.2.3.Organizational assignment - Valid from = 02.09.2010 - Valid to = 31.12.9999 - CoCode = 1000 - Pers. area = 1000 - Cost Ctr = CC-SD-0005 - EE group = 1 - EE subgroup = DS - Payr.area = D2 - Percentage = 100 - Position = 50011085(SD-DC-0005) - Job key = 50053257 (Manage-0005) - Org. Unit = 50005461(SD-0005) - Org. Key = 1000 - Subarea = Empty! - Contract 01 Comm. employee - PersAdmin = 001(Hilde Person) - Time = 002(Thomas Zeit) - PayrAdmin = 003(Gerhardt Abrechner) 8.1.3.2.4.Delimit vacancy - Valid to = 01.09.2010 8.1.3.2.5.Addresses - Distance = 20km 8.1.3.2.6.Planned working time - Weekly days = 5 - Daily hours = 8 8.1.3.2.7.Basic pay - Valid from = 02.09.2010 - Valid to = 31.12.9999 - pay scale Type = 10 - pay scale Area = 01 - pay scale Group = AT - Wages Wage Type Amount MA90(standard monthly salary)10,800.00 EUR
8.1.3.1.HCM:Update other Applicant master data: 8.1.3.1.1.Bank details - Bank key = ####(Deutsche Bank Franfurt) - Bank account = 1290005 - Purpose = Salary 8.1.3.1.2. Previous employer - Valid from = 01.01.2005 Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage,Aaa|Bbb| -Menu/Submenu, SCR-Screen, FRM-Frame, IDUniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox
8.1.3.Hiring process
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. - Hire internal applicant Ms. Anja Mueller for position 50011087(MA-DC-0005) 8.1.4.1.HCM:Update Position requirements profile: Qualification/Requirement name Objec Proficien t ID cy Ability to organize and act 30000 Average 442 Management Experience 50027 Adequat 189 e Verbal, written communicative skills 30000 Adequat 444 e MBA 30000 Yes 680 Company Finance knowledge 30000 Rudimen 402 tary HR Management skills 30000 Very 401 good Customer Service Orientation 50016 High 737 Modification readiness 50025 Average 437 8.1.4.2.HCM:Run Positions succession planning and compare proposed employees profile: - Ms. Mueller and Ms. Schnuck for 50011087(MA-DC-0005) 8.1.4.3.HCM:Employee appraisal: - 120005(Gabor Pauler) by manager Alexander Meier by Managers Appraisal method Kathami - Develope Communication Skills for 120005(Gabor Pauler) 8.1.5.1.HCM:Book training: - 01.01.2011-01.02.2011 Waldorf 8.1.5.2.HCM:Traveling cost: - 120005(Gabor Pauler) - Flight 500 - Hotel 120 - Entertainment 200
8.1.4.Personell planning&development
PaulerSoft CANAL notes, page: 35 - By functional areas(Marketing, Sales, Production, etc.) 8.2.3.1.1.1.DEF: Job: - Shift planning - Cost planning - Personal development - DEF: Task:Collection of responsibilities - DEF: Position:An object inherits properties of Job - Can contain extra tasks - Status(Filled,Partly filled,Vacant) - DEF: Person:An object inherits properties of Position - DEF: User:Authorization to participate in workflows
8.3.DEF:HCM-PA Infotypes: 8.3.1.Content:
- HCM-Personell Administration(PA) data warehouse:
8.1.5.Training management
8.2.Organizational levels of HCM
- Can be changed only in customizing: - Display:Tools|Customizing|IMG|SPRO Execute|BTN:SAP Ref IMG|Enterpr.Struct|Definition|HumanRes| - Modify:Tools|Customizing|IMG|SPRO Execute|BTN:SAP Ref IMG|Enterpr.Struct|Assignment|HumanRes|
8.2.1.1.Client 8.2.1.1.1.Company 8.2.1.1.1.1.Personell Area - Display:|PersArea|Copy,Del,Check|BTN:Struct|BTN:Navig - Modify:|Assgn PersArea to Company| - Reporting group - Authorization group - Default values - Personell Subarea: - Display:|PersSubArea|Create| - Contry|Legal person group - Valid work calendar - Time management group - Wage type - Basic pay - Pay scales - Employee 8.2.2.1.Employee group(Emplyee, Retiree, Contractor) - Display:|EmplGroup| 8.2.2.1.1.Employee subgroup(Trainee, Salary, Hourly wage, NonPayScale) - Display:|EmplSubGroup|Define| 8.2.2.1.1.1.Payroll area - Payperiod(Weekly paid, Monthly wage/salary):Can be shifted only at period end! - Reporting group - Authorization group - Employee - Intra-company structure - Can be changed dynamically with transaction PPOCA 8.2.3.1.Company: 8.2.3.1.1.DEF: OrgUnit: - They itself can create a multi-level hierarchy
8.2.1.Enterprise structure
- Data structures - Recods have validity period - Data substructures: Field groups - Fields - Cross field plausibility rules - Connected with relations 8.3.1.1.Infotypes 0000-0999:Personell Administration 8.3.1.1.1.Infotype 0000:Action-Assign Person to Position - Job and OrgUnit cannot be changed here just displayed - Default Enterprise and Personell hierarchy assignment is offered 8.3.1.1.2.Infotype 0001:Organizational assignment - Assigns employee to a combination of structures: 8.3.1.1.2.1.Enterprise - Company - PersArea - PersSubArea - CostCtr 8.3.1.1.2.2.Personell - EEGroup - EESubGroup - PayrollArea - Contract 8.3.1.1.2.3.Organizational - OrgUnit - Job - Position 8.3.1.1.2.4.Content: - Authorization - Payroll accounting - Time management accounting - Auxiliary data 8.3.1.1.3.Infotype 0002: Personell data 8.3.1.1.4.Infotype 0006: Address 8.3.1.1.5.Infotype 0009: Bank details 8.3.1.2.Infotypes 1000-1999:Personell Planning&Developement 8.3.1.2.1.Infotype 1013: Employee group/subgroup 8.3.1.3.Infotypes 2000-2999:Time management 8.3.1.4.Infotypes 3000-3999:LO integration 8.3.1.5.Infotypes 4000-4999:Recruitment 8.3.1.6.Infotypes 8000-9999:Customer-specific - Single screen maintenance: 1 infotype for 1 person - Fast entry: 1 infotype for more person 8.3.2.1.Content 8.3.2.1.1.FRM:Left:Object search hierachy: - By Person - By Collective 8.3.2.1.2.FRM:Right:Personal master - DDN:Personell Number 8.3.2.1.2.1.TAB:Thematic grouping - FRM:Validity - FRM:Infotype list of theme - LIN:Infotype 8.3.2.1.2.2.BTN:View:Personell file - Infotypes in ascending order - Infotype records in creation time sequence
8.3.2.GUI: PA30:
8.2.2.Personell structure
8.3.3.GUI:PA40:
8.2.3.Organizational structure
- Personell actions: more changed infotypes for 1 person - Guides through a sequence of infotypes - Stores personell action at Personell master|Infotype 0000
8.4.PROC:HCM 8.4.1.Personnel Management (SAP HCM-PA)
8.4.1.1.Recruiting (SAP HCM-PA-RC) 8.4.1.1.1.Identification of vacancies:personnel requirements 8.4.1.1.2.Creating job advertisements 8.4.1.1.2.1.Web application: Employment opportunities - Filtered ad display - Application - Direct to ad - Unsolicited - Attach files - Modify application later 8.4.1.1.2.2.Employee-self-service: Job ads 8.4.1.1.3.Short-listing applicants 8.4.1.1.3.1.Match up qualifications 8.4.1.1.3.2.Line managers select applicants 8.4.1.1.4.Managing applicant correspondence 8.4.1.1.4.1.Approve 8.4.1.1.4.2.Hold 8.4.1.1.4.3.Reject 8.4.1.2.Personnel Administration (SAP HCM-PA-PA) 8.4.1.2.1.Hiring:Transfer applicant to personell administration 8.4.1.2.2.Application Create Personell Master 8.4.1.2.3.Create auto-contract option 8.4.1.3.Training and Personnel Development (SAP HCM-PA-PD) 8.4.1.3.1.Central Qualifications Catalog 8.4.1.3.2.Positions 8.4.1.3.2.1.Future requirements Qualification 8.4.1.3.3.Emplyees 8.4.1.3.3.1.Current qualifications Qualification 8.4.1.3.4.Personal preferences 8.4.1.3.5.Qualifying actions 8.4.1.3.5.1.Personal Development Plans - Training propsals: - Training/business events - Direct book - Pre-book for certain type - Minimal required qualifications - Position transfer/rotation: 8.4.1.3.6.Continous performnce feedback - In yearly cycles 8.4.1.3.6.1.Planning - Skills - Desired levels - Actions to improve 8.4.1.3.6.2.Review - Coaching - Update objectives - Compare with performance 8.4.1.3.6.3.Appraisal - Evaluation - Actions 8.4.1.3.7.Career planning - Motivate employees professional career 8.4.1.3.8.Succession planning - Ensure suitable candidates for positions 8.4.1.4.Compensation (SAP HCM-PA-CM) 8.4.1.4.1.Job|Position pricing 8.4.1.4.2.OrgUnit|Budgeting 8.4.1.4.3.Compensation administration:distributes budget 8.4.1.4.4.Long term incentives:stock option plans 8.4.1.4.4.1.Incentive/non-qualified stock options - Vesting rules: how long option valid (max. 3 years) - Change events(Promotion, Demotion) - Live events(Marriage, Retirement, Death) 8.4.1.4.4.2.Performance shares/units 8.4.1.4.4.3.Restricted stock 8.4.1.5.Benefits (SAP HACM-PA-BN) 8.4.1.5.1.Benefit plan 8.4.1.5.1.1.Contribution sharing - Emplyees contribution - Employer contribution 8.4.1.5.1.2.Types - health, - insurance, - savings, - stock purchase, - credit, - car, - fitness
PaulerSoft CANAL notes, page: 36 8.4.1.6.Personnel Cost Planning and Simulation (SAP HCM-PACPS) 8.4.1.6.1.Data sources - By TimePeriod|OrgUnit|Job|Position|Employee - Collects basic pay + pay scale + premiums - deductions - For current and planned payroll data 8.4.1.6.2.GUI: Web-based BI-OLAP - Payroll budget planning - Training budget planning - Cost run in different simulation scenarios and compare them 8.4.2.1.Data sources - Employee Self-Service: Cross-Application Time Sheets (CATS): - Create accounts - Enter times - Release times - Approve times by manager - Follow up in othe modules - Time managers workplace: Handles individual variations - Time recording systems - Online menus 8.4.2.2.Evaluation - Time accounts - Provision - Attendace/Absence - Overtime - Leaves/Illness/Business trip - Substitution - Payroll/incentives 8.4.2.3.Integration - LO: Capacity planning - HR: Gross payments - FI: Costs - HCM-PE: schedule trainings - PLM: Project advancement - SCM: external employees 8.4.3.1.Tasks 8.4.3.1.1.Renumeration - Basic pay + Pay scales - Bonuses - Overtime - Leave - Deductions - Taxes - Benefit contributions 8.4.3.1.2.Bank transfers 8.4.3.1.3.Check payments 8.4.3.2.PROC: - Release, Master data locked - Start - SEL:Results OK? - ALT:Not OK: Corrections, Retry - ALT:OK. Exit, Master data released 8.4.3.3.Integration - FI: Payroll accounts, taxes
8.4.2.Time Management (SAP HCM-PT)
8.4.3.Payroll Administration (SAP HCM-PY)
8.4.4.1.Create business event catalog - Event groups - Events - Resurces - Scheduling/location - Provided qualifications 8.4.4.2.Day-to-day activities - Pre-book/Book/Replace/Cancel participants - Correspondence 8.4.4.3.Periodic activities - Firmly book/Lock/Unlock/Cancel events - Participant appraisal - Billing, integration with FI, MM, HCM-PA-PD, HCM-PT modules
8.4.4.Training and event management (SAP HCM-PE)
8.4.5.Travel Planning (SAP FI-TV)
- Travel can be put in settled status and costs transferred to FI if it finishes before the end of payroll period
8.5.4.CO: Create Marketing&Sales Cost Center:CCMSD0005 into H10005:KS01

- FI|CO|CostCtr Acct|Master|CostCtr|Individ proc|KS01 Create| 8.5.4.1.SCR:Start - TBX:Cost Center = CCMSD-0005 - DDN:Valid from = 01.01.CurrYr - DDN:Valid to = 31.12.9999 8.5.4.2.SCR:Main - TBX:Name = Mark-SD-0005 - TBX:Description = Marketing and SD root 0005 - TBX:Person Responsible = Gabor Pauler - DDN:Cost center category = 5 - DDN:Hierarchy area = H10005 - DDN:Company code = 1000 - DDN:Business area = 3000(Vehicles) - DDN:Profit center = PROF-0005 8.5.4.2.1.BTN:Save
8.4.6.1.Content: - Office - Time management - Payment - Benefits - Personal information - Training and event management - Qualifications - Appraisals 8.4.6.2.GUI: mySAP.com workplace
8.4.6.Employee Self-Services (SAP HCM-ESS)
8.4.7.1.Standard reports: - HR|HIS|Reports|Personell management|Administration| Employee| 8.4.7.2.Ad-hoc queries: - Managers desktop set at customizing
8.4.7.Human Resources Information Sytem (HIS)
8.5.Maintain organizational structure master data 8.5.1.CO:Display Profit Center standard hierarchy:H1100:KCH6N
8.5.5.CO: Create Marketing Cost Center:CC-MA-0005 into H10005:KS01

- Same as above except: CC-MA-0005, Marketing-0005, Marketing Dept 0005, CostCtrCat = 8
- FI|CO|ProfitCtr|Master|StdHier|KCH6N Display| 8.5.1.1.SCR:Start - DDN:ContrArea = 1000 8.5.1.2.SCR:Main 8.5.1.2.1.FRM:Left - LIN:ProfitCtr - LIN:ProfitCtrGrp|Select 8.5.1.2.2.FRM:Right - LIN:H1 - LIN:HE - LIN:H1100:Externalservices|Select 8.5.2.1.DEF:Profit center: - A collector object of costs and incomes - Profit/Loss analysis unit by period/cost-of-sales accounting - Fixed asset evaluation unit - FI|CO|ProfitCtr|Master|ProfitCtr|Individual proc|KE51 Create| 8.5.2.2.SCR:Start - TBX:Name = PROF-0005 - FRM:Copy from - DDN:ProfitCtr = 1015 - DDN:COArea = 1000 8.5.2.3.SCR:Main - DDN:Analysis Period from = 01.01.CurrYr - DDN:Analysis Period to = 31.12.9999 - TBX:Name = Bicycle-0005 - TBX:Long text = Bicycle-0005 - TBX:Person Respons. = Gabor Pauler - DDN:Profit Ctr. Group = H1100 (External Service) - DDN:Segment = MANF 8.5.2.3.1.BTN:Save 8.5.2.3.2.BTN: Activate
8.5.6.CO: Create Sales Cost Center:CC-SD-0005 into H10005:KS01
- Same as above except: CC-SD-0005, SD-0005, SD Dept 0005, CostCtrCat = 8
8.5.7.HCM:Create Organizational units|Subunits:DepBike0005|SD-0005,Mark-0005:PPOCE

- HR|Org Man|OrgPlan|Org&Staff|PPOCE Create| 8.5.7.1.SCR:Start - Valid from = 01.01.CurrYr - Valid to = 31.12.9999 8.5.7.2.SCR:Main - Settings|Query timeperiod/Create several objects| - CHK:Query timeperiod/Create several objects = True 8.5.7.2.1.FRM:Right - LIN:New OrgUnit|Select 8.5.7.2.2.FRM:Item detail 8.5.7.2.2.1.TAB:Basic data - TBX:Name = DepBike-0005 - TBX:Additional description = Department Bike-0005 Gabor Pauler 8.5.7.2.2.2.TAB:Account assignment - DDN:Cost center = CCMSD-0005 - DDN:Company code = 1000 - DDN:Personnel area = 1000 8.5.7.2.2.3.KEY:Enter 8.5.7.2.3.FRM:Right - LIN:DepBike-0005|RightClick|Create|LIN:Is line supervisor of OrgUnit| - LIN:New OrgUnit|Select 8.5.7.2.4.FRM:Item detail 8.5.7.2.4.1.TAB:Basic data - TBX:Name = SD-0005 - TBX:Additional description = SD-0005 Gabor Pauler 8.5.7.2.4.2.TAB:Account assignment - BTN: Replace CostCtr|DDN:Cost center = CC-SD-0005 - DDN:Company code = 1000 - DDN:Personnel area = 1000 8.5.7.2.4.3.KEY:Enter - Repeat it for Mark-0005(Marketing-0005 Gabor Pauler) DepBike-0005, CC-MA-0005, Comp1000, PersArea1000! 8.5.7.2.5.BTN:Save
8.5.2.CO:Create Profit Center:PROF-0005 into H1100:KE51
8.5.3.CO:Display Cost Center standard hierarchy/Create Cost Center Group:H10005 into H1300:OKEON
- FI|CO|CostCtr Acct|Master|Standard hier|OKEON Change| 8.5.3.1.SCR:Start - DDN:ContrArea = 1000 8.5.3.2.SCR:Main 8.5.3.2.1.FRM:Left - LIN:CostCtr - LIN:CostCtrGrp|Select 8.5.3.2.2.FRM:Right - LIN:H1 - LIN:H1000 - LIN:H1300:Marketing&sales|RightClick| - |Create group (lower level)|SCR:Create group| - DDN:Group name = H10005 - DDN:Description = Marketing and SD Bycicle-0005 8.5.3.2.3.BTN:Save
8.5.8.HCM:Create Jobs|General tasks:Manage-0005|Mgmt0005, Secret-0005|Corresp-0005,Orga-0005:PPOME

- HR|Org Man|OrgPlan|Org&Staff|PPOME Maintenance| 8.5.8.1.SCR:Main 8.5.8.1.1.FRM:Left - LIN:OrgUnit - LIN:Search|Name = DepBike-0005|KEY:Enter 8.5.8.1.2.FRM:Right - BTN: Colums - Show columns: - ID(Show object IDs) - LIN: DepBike-0005|Select - Edit|Create jobs|SCR:Create jobs| - Valid from = 01.01.CurrYr - Valid to = 31.12.9999 - FRM:Jobs: Abbreviation Description Manage-0005 Manager function 0005 Secret-0005 Secretary 0005 8.5.8.1.3.FRM:Left - LIN:Job - LIN:Search|Name = Manage-0005|KEY:Enter 8.5.8.1.4.FRM:Right - LIN: Manage-0005|Select - BTN:New|SCR:Create task| - Valid from = 01.01.CurrYr - Valid to = 31.12.9999 - FRM:Task: AbbreviationDescription Mgmt-0005 Management task 0005 - Repeat it for Corresp-0005, Orga-0005 Secret-0005! 8.5.8.1.5.BTN:Save
8.5.11.HCM:Create Positions|Individual tasks:SD-DC-0005| Acquise-0005, MA-DC-0005|Advert-0005:PPOME

- HR|Org Man|OrgPlan|Org&Staff|PPOME Maintenance| 8.5.11.1.SCR:Main 8.5.11.1.1.FRM:Left - LIN:Position - LIN:Search|Name = SD-DC-0005|KEY:Enter 8.5.11.1.2.FRM:Right - LIN:SD-DC-0005|RightClick|Create|LIN:Is described by task| - Valid from = 01.01.CurrYr - Valid to = 31.12.9999 - FRM:Task: Abbreviation Description Acquise-0005 Acquisition task 0005 - Repeat it for MA-DC-0005 Advert-0005! 8.5.11.1.3.BTN:Save
8.5.12.HCM:Update Positions|Job/task shares:SD-DC0005|Manage-0005=50%/Acquise-0005=50%, MA-DC-0005| Manage-0005=50%/Advert-0005=50%:PPOME

- HR|Org Man|OrgPlan|Org&Staff|PPOME Maintenance| 8.5.12.1.SCR:Main 8.5.12.1.1.FRM:Left - LIN:Position - LIN:Search|Name = SD-DC-0005|KEY:Enter 8.5.12.1.2.FRM:Right - LIN:SD-DC-0005 - LIN:Manage-0005|RightClick|Change percentage|50% - LIN:Acquis-0005|RightClick|Change percentage|50% - Repeat it for MA-DC-0005|Manage-0005=50%/Advert0005=50%! 8.5.12.1.3.BTN:Save
8.5.9.HCM:Create Positions:SD-DC-0005, SD-SE-0005, MADC-0005, MA-SE-0005:PPOME

- HR|Org Man|OrgPlan|Org&Staff|PPOME Maintenance| 8.5.9.1.SCR:Main 8.5.9.1.1.FRM:Left - LIN:OrgUnit - LIN:Search|Name = SD-0005|KEY:Enter 8.5.9.1.2.FRM:Right - LIN:SD-0005|RightClick|Create|LIN:Postions incorporated| SCR:Create position| - Valid from = 01.01.CurrYr - Valid to = 31.12.9999 - FRM:Position: Abbreviation ID Description SD-DC-0005 50011085 Department chief SD 0005 SD-SE-0005 50011086 Secretary SD 0005 - Repeat it for Mark-0005: Abbreviation ID Description MA-DC-0005 50011087 Department chief Mark 0005 MA-SE-0005 50011088 Secretary Mark 0005 8.5.9.1.3.BTN:Save
- HR|Personell management|Administration|HR Master|PA30 Maintain| 8.5.13.1.SCR:Start - DDN:Personell number = 1001 8.5.13.2.SCR:Main 8.5.13.2.1.FRM:Right:Personell master 8.5.13.2.1.1.TAB:Core Empl Info - FRM:Direct infotype selection - DDN:Infotype = Basic pay - DDN:Subtype by actions = Empty! 8.5.13.2.2.BTN:Display 8.5.13.2.2.1.SCR:Infotype basic pay - Take note TBX:Standard salary = 1714,87EUR 8.5.13.2.3.Goto|Personell File|SCR:Personell file|BTN:Display 8.5.13.2.3.1.SCR:First Infotype: 0000 Action 8.5.13.2.3.2.SCR:Second Infotype: 0001 OrgAssign
8.5.13.HCM-PA:Check Infotypes:1001:PA30
8.6.Recruitment process 8.6.1.HCM:Check vacancy status:SD-DC-0005:PPOME

- HR|Org Man|OrgPlan|Org&Staff|PPOME Maintenance| 8.6.1.1.SCR:Main 8.6.1.1.1.FRM:Left - LIN:Position - LIN:Search|Name = SD-DC-0005|KEY:Enter 8.6.1.1.2.FRM:Right - LIN:SD-DC-0005|50011085|Select 8.6.1.1.3.FRM:Item detail 8.6.1.1.3.1.TAB:Basic - DDN:Staffing status = V(Open) 8.6.1.1.4.BTN:Save
8.5.10.HCM:Assign Jobs|Positions:Manage-0005|SD-DC0005, MA-DC-0005, Secret-0005|SD-SE-0005, MA-SE0005:PPOME

- HR|Org Man|OrgPlan|Org&Staff|PPOME Maintenance| 8.5.10.1.SCR:Main 8.5.10.1.1.FRM:Left - LIN:Position - LIN:Search|Name = SD-DC-0005|KEY:Enter 8.5.10.1.2.FRM:Right - LIN:SD-DC-0005|Select 8.5.10.1.3.FRM:Item detail 8.5.10.1.3.1.TAB:Basic - DDN:Job = Manage-0005 8.5.10.1.3.2.TAB:Tasks - It will inherit Mngmt-0005 from job - Repeat it for SD-SE-0005 Secret-0005, MA-DC-0005 Mngmt-0005, MA-SE-0005 Secret-0005! 8.5.10.1.4.BTN:Save
- HR|Personell mngmt|Recriutment|Advertising| Advertisement|PBAW Maintain| 8.6.2.1.SCR:Start 8.6.2.1.1.BTN:Run 8.6.2.2.SCR:Main 8.6.2.2.1.BTN:New advert|SCR:New advert| - BTN:Next free number|Ad number: 00000365 - DDN:Instrument = 00000001(FAZ) - DDN:Publication date = Now - DDN:Advertisement end = Now+1wk - TBX:Publication costs amount = 15,000.00 EUR. - TBX:Text name = Job advertisement Sales Manager 0005 - BTN:Display text|SCR:Microsoft Word| - TYPE: Job ad for Sales Manager, salary 100.000,-EUR - BTN:Save - BTN:Add|SCR:Choose vacancy| - LIN:50011085, Department Chief SD 0005|Select
8.6.2.HCM:Create Job Ads:SD-DC-0005:PBAW
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 8.6.2.2.2.BTN:Save 8.6.2.2.3.BTN:Export| 8.6.2.2.3.1.|Local file|SCR:Local file| - TBX:Title = Job adverts 0005 - DDN:Format = HTML - TBX:Path = C:\Job adverts 0005.html(attach) 8.6.2.2.3.2.|Office|SCR:Export| - TBX:Title = Job adverts 0005 - TBX:Where = PRIV.FOLDERS - BTN:Move 8.6.3.1.DEF:Business Workplace: - OOP GUI where user can overview his authorized task from: 8.6.3.2.DEF:SAP Business Workflow: - Tool for setting up algorithms from: - Sequence of transactions to call - Agents responsible for transactions - To cover repeating, multi-step, multi-agent Business Processes not covered by single transaction yet in SAP. 8.6.3.3.SCR:SAP Easy access 8.6.3.3.1.BTN: Business workplace|SCR:Workplace wip-0005| 8.6.3.3.1.1.FRM:Left - LIN:Priv.folders|Select 8.6.3.3.1.2.FRM:Right - Check out copying Job adverts 0005 - HR|Personell mngmt|Recriutment|Appl. master|PB10 Initial data entry| 8.6.4.1.SCR:Start - DDN:Reason = 04 (New application) - DDN:Per. Area = 1000 (Hamburg) - DDN:Ap. Group = 1 (Active (external)) - DDN:Appl range = 3 (Managerial staff) - DDN:Pers. Off = DAU (Helmut Dauber) - DDN:Title = Mr - TBX:F.name = Gabor - TBX:Last name = Pauler - DDN:Birth dt. = 11.05.1971 - DDN:Language = DE (German) - DDN:Nationality = DE (German) - TBX:Street = Universitaetsstrasse 0005 - TBX:Postal code = 45141 - TBX:City = Essen - TBX:Telephone = +49201-3330005 - TBX:Email = Gabor.Pauler@uni-due.de - DDN:Country = DE (Germany) - TBX:Advertisement = 00000365 8.6.4.1.1.BTN:Save+Add data - Take note of applicant number: 00001561 - HR|Personell mngmt|Recriutment|Appl. master|PB30 Maintain| 8.6.5.1.SCR:Start - DDN:Applicant number = 00001561 - KEY:Enter 8.6.5.1.1.FRM:Infotypes 8.6.5.1.1.1.LIN:Qualifications - BTN:New 8.6.5.2.SCR:Main 8.6.5.2.1.TAB:Qualifications 8.6.5.2.1.1.BTN:New - Search for Name LINID Name Proficiency 01 50027189 Mangement Experience 0009(Excellent) 02 50025440 Project Management skills 0008(Very high) 03 50025402 Communication Skills 0006(Above-average) 04 50000551 Knowledge of Excel 0007(High) 8.6.5.2.2.TAB:potentials 8.6.5.2.2.1.BTN:New - Search for Name LINID Name 01 50000405 Market research skills 8.6.5.2.3.TAB:Preferences 8.6.5.2.3.1.BTN:New - Search for Name LINID Name 01 30010189 Knowledge wordprocessing 8.6.5.2.4.TAB:Dislikes
8.6.3.SAP Business Workplace:Job adverts 0005
PaulerSoft CANAL notes, page: 39 8.6.5.2.4.1.BTN:New - Search for Name LINID Name 01 50034171 French 02 50010176 Presentation sofware 8.6.5.2.5.BTN:Save 8.6.5.2.6.BTN:Short profile|SCR:Short profile| - System|List|Save| - |Office folders|ShortProf-0005 - |Local file|ShortProf-0005.htm(Attach) - HR|Personell mngmt|Recriutment|Appl. master|PB30 Maintain| 8.6.6.1.SCR:Start - DDN:Applicant number = 00001561 - KEY:Enter 8.6.6.1.1.FRM:Infotypes 8.6.6.1.1.1.LIN:Vacancy asignment - BTN:New 8.6.6.2.SCR:Main - DDN:Start date = Now - DDN:To date = 31.12.9999 - DDN:Vacancy priority = 1 - DDN:Vacancy ID = 50011085(SD-DC-0005) - DDN:Vac.assign.stat = 1(In process) - DDN:Status reason = 04(New application) 8.6.6.2.1.BTN:Save - HR|Personell mngmt|Recriuting|Appl. activity|PB60 Maintain| 8.6.7.1.SCR:Start - DDN:Applicant number = 00001561 - BTN:Run 8.6.7.2.SCR:Main 8.6.7.2.1.FRM:Planned activities 8.6.7.2.1.1.LIN:Receipt of application - BTN:Activity|SCR:Receipt| - DDN:Perform to datetime = Now - DDN:Position ID = 50011085(SD-DC-0005) - BTN:Letter|SCR:MS Word| - TYPE:Text - BTN:Save|C:\Receipt-0005.doc(Attach) 8.6.7.2.2.BTN:PlannedCompleted 8.6.7.2.3.BTN:Save
8.6.6.HCM:Vacancy assignment:00001561:PB30
8.6.4.HCM:Create Applicant master:00001561:PB10
8.6.7.HCM:Check Applicant activities:00001561:PB60
8.6.8.HCM:Evaluate Applicants:ProjMan=very high, KnowlExcelAboveAvg:PBAQ
8.6.5.HCM:Update Applicant qualifications:00001561:PB30
- HR|Personell mngmt|Recriuting|Selection proc|Applicat pool|Via qualifications|PBAQ External applicants| 8.6.8.1.SCR:Start 8.6.8.1.1.FRM:Left 8.6.8.1.1.1.LIN:Qualification - LIN:Search = *Excel* 8.6.8.1.2.FRM:Right LINID Name Req Relat Proficiency 01 50025440 Project Man skills Yes = 0008(Very high) 02 50000551 Knowledge of Excel 0006(Above aver) 8.6.8.1.3.BTN:Save - RAD:User specific = True - TBX:User = Gabor Pauler 8.6.8.1.4.BTN:Run 8.6.8.2.SCR:Main - LIN:Gabor Pauler|Select 8.6.8.2.1.BTN:Short profile|SCR:Short profile| - System|List|Save| - |Office folders|ShortProf2-0005 - |Local file|ShortProf2-0005.htm(Attach)
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. - HR|Personell mngmt|Recriuting|Appl. activity|PB60 Maintain| 8.6.9.1.SCR:Start - DDN:Applicant number = 00001561 - BTN:Run 8.6.9.2.SCR:Main 8.6.9.2.1.FRM:Completed activities 8.6.9.2.1.1.LIN:Receipt of application - BTN:Follow-up Activity|SCR:Select activity| - LIN:Tel.invitation|Select|SCR:Tel.invitation| - TBX:Standard text = Empty! - DDN:Responsible = Mike Anderson - DDN:Vacancy ID = 50011085(SD-DC-0005) 8.6.9.2.2.BTN:PlannedCompleted 8.6.9.2.3.BTN:Save 8.6.9.2.4.FRM:Completed activities 8.6.9.2.4.1.LIN:Tel.invitation - BTN:Follow-up Activity|SCR:Select activity| - LIN:Interview invitation|Select|SCR:Interview invitation| - DDN:Responsible = Mike Anderson - DDN:Vacancy ID = 50011085(SD-DC-0005) 8.6.9.2.5.BTN:PlannedCompleted 8.6.9.2.6.BTN:Save
PaulerSoft CANAL notes, page: 40 - HR|Personell mngmt|Recriutment|Appl. activity|Transfer applicant data|PBA7 Execute| 8.7.4.1.SCR:Direct data transfer - DDN:Action for hiring = 01(Hiring) - DDN:Applicant number = 00001561 - BTN:Run 8.7.4.2.SCR:Create action - DDN:Personnel area = 1000 - DDN:Position = 50011085(SD-DC-0005) - TBX:Personnel number = 120005 - DDN:Reason = Empty! - DDN:Ref.person = Empty! - DDN:Employee group = 1(Active) - DDN:Employee subgroup = DS(Managerial employees) 8.7.4.2.1.BTN:Save 8.7.4.3.SCR:Personal data - DDN:Title = Mr. - TBX:Initials = G.P. - TBX:Maiden name = Empty - TBX:Place of birth = Pecs - DDN:Country of birth = HU - DDN:Nationality = HU - DDN:Marital status = Single - DDN:Religion = No church tax liability - TBX:Number of children = Empty 8.7.4.3.1.BTN:Save 8.7.4.4.SCR:Organizational assignment - DDN:Valid from = Now - DDN:Valid to = 31.12.9999 - DDN:CoCode = 1000 - DDN:Pers. area = 1000 - DDN:Cost Ctr = CC-SD-0005 - DDN:EE group = 1 - DDN:EE subgroup = DS - DDN:Payr.area = D2 - DDN:Percentage = 100 - DDN:Position = 50011085(SD-DC-0005) - DDN:Job key = 50053257(Manage-0005) - DDN:Org. Unit = 50005461(SD-0005) - DDN:Org. Key = 1000 - DDN:Subarea = Empty! - DDN:Contract 01 Comm. employee - DDN:PersAdmin = 001(Hilde Person) - DDN:Time = 002(Thomas Zeit) - DDN:PayrAdmin = 003(Gerhardt Abrechner) 8.7.4.4.1.BTN:Save 8.7.4.4.2.FRM:Delimit vacancy - DDN:Valid to = Now-1Day 8.7.4.5.SCR:Addresses - TBX:Distance = 20km 8.7.4.5.1.BTN:Save 8.7.4.6.SCR:Planned working time - TBX:Weekly days = 5 - TBX:Daily hours = 8 8.7.4.6.1.BTN:Save 8.7.4.7.SCR:Basic pay - DDN:Valid from = Now - DDN:Valid to = 31.12.9999 - DDN:pay scale Type = 10 - DDN:pay scale Area = 01 - DDN:pay scale Group = AT - FRM:Wages Wage Type Amount MA90(standard monthly salary)10,800.00 EUR 8.7.4.7.1.BTN:Save 8.7.4.8.SCR:Bank Account: 8.7.4.8.1.BTNSave 8.7.4.9.SCR:Capital formation: 8.7.4.9.1.BTN:Next,BTN:Yes 8.7.4.10.SCR:Fiscal data: 8.7.4.10.1.BTN:Next 8.7.4.11.SCR:Social insurance: 8.7.4.11.1.BTN:Next 8.7.4.12.SCR:DEUEV: 8.7.4.12.1.BTN:Next 8.7.4.13.SCR:Contract Elements: 8.7.4.13.1.BTNSave 8.7.4.14.SCR:Monitoring of Tasks: 8.7.4.14.1.BTNSave
8.6.9.HCM:Make Selction decision:00001561:PB60
8.7.4.HCM:Hiring Applicant:00001561:PBA7
8.7.Hiring process 8.7.1.HCM:Prepare transfer of applicant data:00001561:PB40
- HR|Personell mngmt|Recriuting|Applicant master|PB40 Applicant actions| 8.7.1.1.SCR:Start - DDN:Applicant ID = 00001561 - DDN:Valid from = Now - FRM:Action type - LIN:Prepare to hire|Select 8.7.1.1.1.BTN:Run 8.7.1.2.SCR:Main 8.7.1.2.1.BTN:Save - HR|Personell mngmt|Recriuting|Appl. activity|PB60 Maintain| 8.7.2.1.SCR:Start - DDN:Applicant number = 00001561 - BTN:Run 8.7.2.2.SCR:Main 8.7.2.2.1.FRM:Planned activities 8.7.2.2.1.1.LIN:Transfer data - BTN:Del: Delete extra lines if there are repetitive entries ! 8.7.2.2.1.2.LIN:Hiring - BTN:Del: Delete extra lines if there are repetitive entries ! - These 2 planned activities will enable to transfer applicant to personell master
8.7.2.HCM:Check Applicant activities:00001561:PB60
8.7.3.HCM:Update Applicant master, infotypes bank details, prev.employer, education:00001561:PB30
- HR|Personell mngmt|Recriutment|Appl. master|PB30 Maintain| 8.7.3.1.SCR:Start - DDN:Applicant number = 00001561 - KEY:Enter 8.7.3.1.1.FRM:Infotypes 8.7.3.1.1.1.LIN:Bank details - BTN:New 8.7.3.2.SCR:Main 8.7.3.2.1.SCR:Bank details - DDN:Bank key = ####(Deutsche Bank Franfurt) - TBX:Bank account = 1290005 - DDN:Purpose = Salary 8.7.3.2.2.SCR: Previous employer - DDN:Valid from = 01.01.2005 - DDN:Valid to = 30.LastMo.CurrYr - TBX:Employer = Linde AG - TBX:City = Essen - DDN:Country Key = DE(Germany) - DDN:Industry = HITE(High Tech.) - DDN:Job = 13(Manager) 8.7.3.2.3.SCR:Education - DDN:Valid from = 01.01.1999 - DDN:Valid to = 31.12.2004 - TBX:School = Whatever 8.7.3.2.4.BTN:Save
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 8.7.4.15.SCR:Absence quotas: 8.7.4.15.1.BTNSave 8.7.4.16.SCR:Travel privileges: 8.7.4.16.1.BTNSave 8.7.4.17.SCR:Time Sheet Defaults: 8.7.4.17.1.BTNSave 8.7.4.18.SCR:Education: 8.7.4.18.1.BTNSave 8.7.4.19.SCR:Previous Employers: 8.7.4.19.1.BTNSave 8.7.4.20.SCR:Communication: 8.7.4.20.1.BTNSave - HR|Personell management|Administration|HR Master|PA30 Maintain| 8.7.5.1.SCR:Start - DDN:Personell number = 120005 8.7.5.2.SCR:Main 8.7.5.2.1.FRM:Right 8.7.5.2.1.1.FRM:Infotypes - The following infotypes should be OK, - If not, create them with BTN:New! - Basic data person: - Activities, - organizational assignment, - personnel data, - address, - bank account - Basic data work relationship: - Organizational assignment, - personnel data, - planned working time, - travel privileges - Payroll gross/net: - basic pay - Payroll net: - organizational assignment, - payroll status - Payroll extras: - organizational assignment, - payroll status - Planning data: - organizational assignment, - education, - qualifications
Modification readiness 8.8.1.2.4.BTN:Save
PaulerSoft CANAL notes, page: 41 50025 Average 437
8.8.2.HCM:Display Career opportunities:1000(Ms. Anja Mueller):PPCP
8.7.5.HCM:Display Personell master data:120005:PA30
- HR|Personell mngmt|Personell dev|Planning|PPCP Carreer| 8.8.2.1.SCR:Start - DDN:For = P(Person) - DDN:Employee = 1000(Ms. Anja Mueller) - CHK:Include career options = True - BTN:Run 8.8.2.2.SCR:Carrer options hierachy 8.8.2.2.1.FRM:Header - TBX:Name = Ms. Anja Mueller|Select - Goto|Ranking list|SCR:Ranking list| LINSuitable postion Match 1 50000659 Executive Board 65% - Goto|Profile|SCR:Qualifications list| LINQualifications 1 30000451 Adaptability - Goto|HR master data|SCR: HR Master| - DDN:Position = 50011087 - DDN:Cost center = 2200 8.8.2.2.2.FRM:Career plans - Areas - Jobs - Positions
8.8.3.HCM:Positions succession planning suitable employees to fill a position:MA-DC-0005:PPSP

- HR|Personell mngmt|Personell dev|Planning|PPCP Succession| 8.8.3.1.SCR:Start - DDN:Position = 50011087(MA-DC-0005) - DDN:Additional career = Business carreer - BTN:Run 8.8.3.2.SCR:Main 8.8.3.2.1.FRM:Head - Goto|Ranking list|SCR:Ranking list| Employee Match% Hannah Schnuck 21.13% 8.8.3.2.2.FRM:Successions - Area - Employees
8.8.Personell planning&development 8.8.1.HCM:Update Position requirements profile:MA-DC0005:PPPM

8.8.1.1.DEF:Profile: - An object with properties called characteristics - Describing current qualifications or future plans - Can be organized in hierarchies and assigned to a position - Profile hierarchies of positions can be compared - HR|Personell mngmt|Personell dev|Profile|PPPM Maintenance| 8.8.1.2.SCR:Main 8.8.1.2.1.FRM:Left - LIN:Position - LIN:Search 8.8.1.2.2.FRM:Right - DDN:Position = MA-DC-0005 8.8.1.2.3.TAB:Requriements 8.8.1.2.3.1.BTN:New Qualification/Requirement name Objec Proficien t ID cy Ability to organize and act 30000 Average 442 Management Experience 50027 Adequat 189 e Verbal, written communicative skills 30000 Adequat 444 e MBA 30000 Yes 680 Company Finance knowledge 30000 Rudimen 402 tary HR Management skills 30000 Very 401 good Customer Service Orientation 50016 High 737
- HR|Personell mngmt|Personell dev|Profile|PPPD Display| 8.8.4.1.SCR:Main 8.8.4.1.1.FRM:Left - LIN:Person - LIN:Search = *Scnuck* 8.8.4.1.2.FRM:Right - Qualifications|List|SCR:Qualifications| LINQualifications 1 Initiative - BTN:Export|Local file|C:\QualiScnuck0005.htm(Attach) - Goto|HR Master|SCR:HR Master| - DDN:Birth date = 05.11.1968
8.8.4.HCM:Display profiles:(Ms. Schnuck):PPPD
8.8.5.HCM:Proposed employees to position profile matchup reporting:(Ms. Mueller Ms. Scnuck):PEPM
- HR|Personell mngmt|Personell dev|Information system| Reports|PEPM Profile matchup| 8.8.5.1.SCR:Start 8.8.5.1.1.FRM:Left - DDN:P(Person) - DDN:Number = 1000(Anja Mueller) - KEY:Enter - DDN:Number = #####(Hannah Schnuck) - KEY:Enter 8.8.5.1.2.FRM:Right - DDN:S(Position) - DDN:Number = 50011087(MA-DC-0005) - KEY:Enter 8.8.5.1.3.BTN:Run 8.8.5.2.SCR:Main - Give a simple unordered list of Person|Qaulification differences in ALV grid, therefore: - Col:Difference|Select|BTN:Sum - Col:Object name|Select|BTN:GroupSum
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. - Take note of the winner and why won: Anja Mueller -16
diff against Hannah Scnuck -22 diff
8.8.6.HCM:Create employee appraisal:120005(Gabor Pauler):APPCREATE
8.9.2.HCM:Traveling cost:120005(Gabor Pauler) Walldorf:TRIP
- HR|Personell mngmt|Personell dev|Appraisal|APPCREATE Create| 8.8.6.1.SCR:Main - DDN:Aprraisal method = Managers Appraisal Khatami - DDN:Manager = Alexander Meier - DDN:Employee = 120005(Gabor Pauler) - DDN:Valid from = 02.09.2010 - DDN:Valid to = Now - FRM:Appraisals Competency Level Note Communication Skills rudimentary Leadership average Problem Solving excellent Authority very high Department/Proj. above average Productivity Process Management excellent Operational Improvement high Willingness to learn adequate Appraisal after inerview 8.8.6.1.1.BTN:Execute 8.8.6.1.2.BTN:Save
- HR|Travel management|TRIP Travel manager| 8.9.2.1.SCR:Travel manager - DDN:personnel number = 120005(Gabor Pauler) - KEY:Enter - BTN:Create travel expense report 8.9.2.2.SCR:Travel expense report 8.9.2.2.1.FRM:General - DDN:Start date = 01.01.2011 - DDN:End date = 01.02.2011 - DDN:First destination = Walldorf - DDN:Reason for the trip = Training 8.9.2.2.2.FRM:Expense receipts Expense receiptAmount Flight 500 Hotel 150 Entertainment 200 8.9.2.2.3.BTN:Save 8.9.2.3.SCR:Travel manager - TBX:Reimburse amount = 1594EUR - CHK:Change travel expense report = True - Take note of travel expense report number: 2000649
8.8.7.HCM:Modify employee appraisal:120005(Gabor Pauler):APPCHANGE
- HR|Personell mngmt|Personell dev|Appraisal|APPCHANGE Modify| 8.8.7.1.SCR:Start - DDN:Aprraisal method = Managers Appraisal Khatami - DDN:Manager = Alexander Meier - DDN:Employee = 120005(Gabor Pauler) - DDN:Valid from = 02.09.2010 - DDN:Valid to = Now 8.8.7.2.SCR:Main 8.8.7.2.1.FRM:Appraisals Competency Level Note Management skills average Organizational develop average Willingness to learn Bove avgAppraisal chgd inerview 8.8.7.2.2.BTN:Complete 8.8.7.2.3.BTN:Save - Take note of overall appraisal: 7 High
8.9.Training management 8.9.1.HCM:Book training:120005(Gabor Pauler):PSV1
- HR|Training and events|Training and events menu|PSV1 Attendance| 8.9.1.1.SCR:Start 8.9.1.1.1.FRM:Left - LIN:Current plan - LIN:Management and Leadership - LIN:Business leadership - LIN: 02.09.2010-17.09.2012 EN Communication| RightClick|Book|SCR:Book| - DDN:Person = 120005(Gabor Pauler) - TAB:Book/payment info - DDN:Fee and assignment = Free of charge - DDN:CostCtr = 1000 8.9.1.1.2.BTN:Save
9.Financial Accounting Scenario

9.1.Plot of Scenario 9.1.1.General Ledger
9.1.1.1.FI:Create G/L account in Chart of Account: - CONS|312600|900005INT 9.1.1.2.FI:Create G/L account: - Company1000|900005 9.1.1.3.FI:Enter G/L Account Document: - Credit:113000BankDebit:900005 5000EUR 9.1.2.1.FI:Enter Vendor Invoice - Vendor = 100268 - Amount = 10000EUR - CostCtr = CCMSD-0005 - ReconAcct = 470000 - Date = Yesterday 9.1.2.2.FI:Automatic payment run: - Company = 1000 - Vendor = 100268 - Date = next month 9.1.3.1.FI:Create Credit Management Master: - Customer = 50005, - TotLim = 500000EUR, - IndivLim = 100000 EUR, - CredContArea = 1000: - IndivLim = 10000 EUR 9.1.3.2.SD:Create Sales Order: - Customer = 50005, - Plant = 1000, - SalOrg = 1000, - Chnl = 10 - Division = 00 - SpeedStarlett-0005, 10PC 9.1.3.3.FI:Release Blocked SD Document - Customer = 50005 9.1.4.1.FI:Create Asset Master Record: - Asset = 3414 0 (Forklift-0005) - CostCtr = CCMSD-0005 9.1.4.2.FI:Post Asset Acquisition: - Buy asset = 3414 0 (Forklift-0005) - Vendor = 1000 - Amount = 35000EUR+10%Tax: 9.1.5.1.FI:Create Balance Sheet and P&L Report
9.1.2.Accounts Payable
PaulerSoft CANAL notes, page: 43 - FK:Cost type - FK:Cost center - Free fields - Created date - Modified date - Viewed date - Status: Supress/Display, Required/Optional 9.2.1.2.DEF:Collective Positions 9.2.1.3.DEF:Reconciliation accounts - Connects balance of subledgers into general ledger real time - Items cannot be posted manually here - An instance of Chart of Accounts class - 1:1 related wity Company 9.2.2.1.Contains subledgers 9.2.2.1.1.FI-AP:Accounts Payable - Mainly used by MM to pay vendors 9.2.2.1.1.1.Account - Credit - Debit 9.2.2.1.2.FI-AR:Accounts Receiveabe - Mainly used by SD to receive payment from customers 9.2.2.1.2.1.Account - Credit - Debit 9.2.2.1.3.FI-AA:Asset Accounting - Mainly used by Treasury (TR) to track financial resources 9.2.2.1.3.1.Account - Credit - Debit 9.2.2.1.4.FI-BL:Bank Ledger - Cash-flow movement 9.2.2.1.4.1.Account - Credit - Debit 9.2.2.2.Contains reports 9.2.2.2.1.FI:DEF:Balance Sheet Report - Account-based period-end closing of a company inkey date - Assembled from subledger by Countrywise-defined standards: US-GAAP, IAS 9.2.2.2.1.1.DEF:Assets:Application of funds - FI-AA:Assets - MM:Material - SD:Recieveables - FI-BL:Bank 9.2.2.2.1.2.DEF:Liabilities:Source of funds - TR:Equity capital - TR:Loans - FI-AP,MM:Liabilities 9.2.2.2.1.3.OrgLevels - Operational/Country Charts of Accounts:CAUS,GKR,INT - Company - Business Area - Cost center:only in new system! - Profit center:only in new system! - Functional area:only in new system! - Planned data - Actaual data - Variance 9.2.2.2.1.4.GUI Transactions - Old ABAP Report:RFBILA00: - Less flexible - New G/L Accounts Info System: Fin.Statm:Act/ActCompar: - More detailed OLAP-like filtering 9.2.2.2.2.FI:DEF:Profit&Loss Statement - Comparison of a revenue and expenditure of a compny in a given period 9.2.2.2.2.1.Expenditure 9.2.2.2.2.2.Revenue
9.2.2.DEF:FI-GL:General Ledger (G/L)
9.1.3.Accounts Receiveable
9.1.4.Asset Accounting
9.1.5.Balance Sheet and Profit&Loss Statement
9.2.DEF:Structures of FI 9.2.1.DEF:Chart of Accounts
- 1:m related with Company - Object class describes fixed level-number hierarchy of: 9.2.1.1.DEF:G/L Accounts Master 9.2.1.1.1.Header 9.2.1.1.1.1.Account specific part - PK:ID - Description - Account type: P&L/Balance Sheet - FK:Superior category in General Ledger(G/L) - FK:Superior category in Balance Sheet - FK:Superior category in Profit&Loss Report (P&L) - FK:Account Group: user defined free grouping 9.2.1.1.1.2.Company specific part - Account control/management - Financial/interest details - Joint ventures sharing - Document control - Created date - Modified date - Viewed date - Status: Supress/Display, Required/Optional 9.2.1.1.2.Line/Position - Amount - Currency - Type: Credit/Debit - FK:Debit/Credit account number - FK:Project/Cost center/Internal order - FK:Profit center - FK:Segment - FK:Partner Profit center - FK:Functional area
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 9.2.3.1.Extended data structure of G/L accounts and their standard reporting - Functional area - Profit center - Partner Profit center - Cost type - Cost center - Segment - Free fields 9.2.3.2.Document split: - All lines of accounting documents can be split along the following structure - For split lines, a zero balance option can be set with extra balance row - Enables real time data entry segmentwise, insead of adjustment in period end closing in the old system 9.2.3.2.1.Project/Cost center/Internal order 9.2.3.2.1.1.Profit center - Segment 9.2.3.3.Real time COFI data transfer 9.2.3.3.1.DEF:Types of CO documents: 9.2.3.3.1.1.Has no consequence in FI - Allocation 9.2.3.3.1.2.Has consequence in FI - Assessments, - Distributions, - Confirmations, - CO-internal settlements 9.2.3.3.2.Handling CO docs with FI consequence - These are automatically transferred with FICO transaction - Related FICO documents can be accessed from both direction - Document lines can be split in following structure: - Project/Cost center/Internal order - Profit center - Segment 9.2.3.3.3.Scope of data transfer can be delimited by OrgUnit: - Company - Business Area - Functional area - Public Fund - Public Grant 9.2.3.4.Multiple Books in GL 9.2.3.4.1.DEF:Leading ledger - 1:1 related for Client - Controls the: 9.2.3.4.1.1.General ledgers - 1:1 related for Companies in different Countries - With different charts of accounts: US:US-GAAP, DE:HGB - With different fiscal year version
PaulerSoft CANAL notes, page: 44 - Internal planning and evaluation prurpose - International standard - Communicates with financial accounting through reconciliation accounts - Uses P&L statement from financial accounting 9.3.2.1.Parts 9.3.2.1.1.Cost center accounting 9.3.2.1.2.Profitability accounting 9.3.2.1.3.Product Costing 9.3.2.1.4.Job Costing 9.3.2.2.Organization 9.3.2.2.1.Client 9.3.2.2.1.1.Operational Chart of Account - Company - Controling Area - Cost accounting unit - Can collect revenues and costs - m:m related with companies using the same chart of accounts with same version of fiscal year 9.3.2.2.1.2.Operating Concern - 1:m with controling areas
9.2.3.DEF:New SAP General Ledger
9.3.2.DEF:FI-CO:Managerial accounting/Controlling
9.4.PROC:Accounting 9.4.1.G/L Account posting document
9.4.1.1.Work template - Screen variants - Account assignment template - Held docs template 9.4.1.2.Header - ID - Date - Control info - Scanned paper documents reference - Show only balance or lines 9.4.1.3.Line - Posting key - Valid account types - Credit/Debit - Sales relevant - Screen selectionEntry check rules - Amount - Account - Payment terms - Cost center - Explanatory text 9.4.1.4.Information section - Credit/debit balance - Attached scanned documents 9.4.2.1.DEF:Vendor master data 9.4.2.1.1.Client specific part - Name - Address 9.4.2.1.1.1.Company specific part 9.4.2.1.1.2.PurchaseOrg specific part 9.4.2.2.PROC:Procurement 9.4.2.2.1.Transactions StepCredit Debit GoodsReceipt 1 Material 2 GoodsReceipt(GR/IR) Liabilities Bank 3 Bank Alloc Bank Alloc 4 Liabilites 9.4.2.2.2.Documents 9.4.2.2.2.1.Purchase Order - MM:ID, Amount - FI:9.4.2.2.2.2.Goods receipt - MM:Material doc - FI:Cred:MaterialDeb:GR/IR 9.4.2.2.2.3.Invoice receipt - MM:Invoice verification - FI:Cred:GR/IR Deb:Vendor,Tax
9.4.2.FI-AP:Accounts payable handling
9.3.TYPES:Accounting 9.3.1.DEF:FI-FI:Financial accounting
- External legal obligation - Changes countrywise 9.3.1.1.Parts: 9.3.1.1.1.FI-GL - FI-AP/AR - FI-AA - FI-BL 9.3.1.1.2.Cash journal 9.3.1.1.3.Inventory 9.3.1.1.4.Tax accounting 9.3.1.1.5.Accrual accounting 9.3.1.2.Organization 9.3.1.2.1.Client 9.3.1.2.1.1.Operational Chart of Account - Company - Smallest organizational units having Balance Sheet - Country:Company is strictly 1:m - Business Area - Optional, it is created only if it is required by legal ruling - Or required internally for partial balance sheets - Can represent subsidiaries or product lines - m:m related with companies
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 9.4.2.3.PROC:Payment 9.4.2.3.1.Maintain parameters 9.4.2.3.2.Parameters entered 9.4.2.3.3.Start payment proposal run 9.4.2.3.4.Payment proposal Created 9.4.2.3.5.Edit proposal:Select items to pay 9.4.2.3.6.Start payment run:Calculate payment 9.4.2.3.7.Post payment order document 9.4.2.3.8.Print payment medium - EDI: Electronic data Interchange - DTA - LPT: printer 9.4.3.1.DEF:Customer master 9.4.3.1.1.Client specific part - Name - Address 9.4.3.1.1.1.Company specific part 9.4.3.1.1.2.SalesArea specific part 9.4.3.2.DEF:Credit control area 9.4.3.2.1.Company 9.4.3.2.1.1.Credit management department - Credit management representative groups - Credit management representatives 9.4.3.3.DEF:Credit management master 9.4.3.3.1.General data - Address - Communication - Max total limit 9.4.3.3.2.Credit control area specific - Credit control area limit - Customer risk group limit 9.4.3.4.PROC:Sales order 9.4.3.4.1.Sales 9.4.3.4.1.1.SD:Sales order 9.4.3.4.2.Delivery 9.4.3.4.2.1.SD: - Delivery doc 9.4.3.4.2.2.FI-AR: - Credit:Stock change FG P/LDebit:Material G/L 9.4.3.4.3.Picking 9.4.3.4.3.1.MM: - Transfer order 9.4.3.4.4.Goods issue 9.4.3.4.4.1.MM: - Goods issue doc 9.4.3.4.4.2.FI-AR: - Cred:InventoryDebit:Cost of goods sold 9.4.3.4.5.Billing 9.4.3.4.5.1.SD: - Print invoice 9.4.3.4.5.2.FI-AR: - Credit:Receiveables|Customer G/LDebit:ExpendIncome P/L 9.4.3.4.6.Payment 9.4.3.4.6.1.SD: - Proof of payment 9.4.3.4.6.2.FI-AR: - IF:Payment = Invoiced amount +/- tolerance group - ALT:Yes:Credit:Bank G/LDebit:Receiveables|Customer G/L - ALT:NO - Create partial payment - Create residual item on customer account 9.4.3.5.PROC:Credit control - Order placed - IF: Within customer credit limit? - ALT:Yes, Release order - ALT:NO - Block order - Notify/report to credit control representative - Contact customer - IF: Cleared? - ALT:Yes, Release order - ALT:NO, Refuse order
PaulerSoft CANAL notes, page: 45 9.4.4.1.DEF:Asset: - Economic good used long term 9.4.4.2.DEF:Organizational levels 9.4.4.2.1.FI:Company 9.4.4.2.1.1.Business Area 9.4.4.2.2.CO:Cost center/Projec/Internal order/Activity type 9.4.4.2.2.1.Profit center 9.4.4.2.3.Plant Maintenance (PM),TR:Asset Classes - 1000:Buildings - 2000:Machinery - 3000:Equipment - 4000:Under construction - 5000:Low valued 9.4.4.2.4.FI:Asset master|Depreciation areas 9.4.4.2.4.1.General:Internal customizaton of computing: - Asset value - Depreciation - Remaining value 9.4.4.2.4.2.Special:Forced by tax authority 9.4.4.3.PROC:Asset history 9.4.4.3.1.Book value (FiscYr begin) 9.4.4.3.2.Asset transaction types by sign 9.4.4.3.2.1.+ Acquisition: 75:Credit:Asset account Debit:Vendor account - With/without Purchase Order - With/without vendor:Clearing G/L account will be offseted instead of vendor - Through MM:Purchase OrderGoods ReceiptInvoice Receipt 9.4.4.3.2.2.- Retirement: 70:Debit Asset account 9.4.4.3.2.3.+/- Transfer 9.4.4.3.2.4.+/- Appreciation/Depreciation Runs: - Book deperecitaion - Cost accounting depreciation - Parallel externally legal forced depreciation 9.4.4.3.3.Asset transaction types by reason: - Buying and selling - Credit memos - Acquisitions from internal production - Adjustment postings - Retirements without revenues - Depreciations and appreciations 9.4.4.3.4.Book value (FiscYr end) 9.4.4.4.GUI:Asset explorer 9.4.4.4.1.FRM:Left:Depreciation areas 9.4.4.4.2.FRM:Right: - DDN:Asset, - DDN:Year 9.4.4.4.2.1.TAB:Depreciation parameters 9.4.4.4.2.2.TAB:Planned/Actual 9.4.4.4.2.3.TAB:Book value/Transactions
9.4.4.PROC:Asset Accounting
9.4.3.FI-AR:Accounts Receiveable handling
9.5.Customizing Organizational levels 9.5.1.IMG:Display Currency:Company1000:SPRO
- Tools|Customizing|IMG|SPRO Execute project| 9.5.1.1.SCR:Start - BTN:SAP Reference IMG 9.5.1.2.SCR:Display IMG - EnerprStruct|Def|FI|Edit Company code| SCR:Company| - LIN:1000 - DDN:Currency = EUR
9.5.2.IMG:Display companies of:Controlling Area 1000:SPRO
- Tools|Customizing|IMG|SPRO Execute project| 9.5.2.1.SCR:Start - BTN:SAP Reference IMG 9.5.2.2.SCR:Display IMG - CO|General CO|Org|Maint Contr Area| SCR:Basic data| - FRM:Right - LIN:1000|Select - FRM:Left - LIN:Display assigned companies|Select
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. - FRM:Right:Company list: 0005IDES AG NEW GL 0007IDES AG NEW GL 1000IDES AG 2000IDES UK 2100IDES Portugal
PaulerSoft CANAL notes, page: 46 - LIN:1000|Select - FRM:Left - LIN:Activate components|Select - FRM:Right: - DDN:Chart of Accts = INT
9.5.3.IMG:Display Fiscal Year variant:Controlling Area 1000:SPRO

- Tools|Customizing|IMG|SPRO Execute project| 9.5.3.1.SCR:Start - BTN:SAP Reference IMG 9.5.3.2.SCR:Display IMG - EnerprStruct|Def|CO|Maint Contr Area| SCR:Basic data| - FRM:Right - LIN:1000|Select - FRM:Left - LIN:Basic data|Select - FRM:Right: - DDN:Fiscal year variant = K4
9.6.4.FI:Display Accounts in Chart of Accounts:International(INT):F.10
InfSys|Accounting|FI|G/L|F.10 Chart of accounts| 9.6.4.1.SCR:Start - DDN:Chart of Acct = INT - BTN:Run 9.6.4.2.SCR:Main - LIN:140000 Trade receivabeles Domestic: reconciliation account from FI-AR subledger
9.6.5.FI:Create G/L account in Chart of Account:CONS| 312600|900005 INT:FSP0
9.5.4.IMG:Display Operating Concern:Controlling Area 1000:SPRO

- Tools|Customizing|IMG|SPRO Execute project| 9.5.4.1.SCR:Start - BTN:SAP Reference IMG 9.5.4.2.SCR:Display IMG - EnerprStruct|Assign|CO|Contr AreaOpConcern| SCR:Basic data| - FRM:Right - LIN:1000|Select - FRM:Left - LIN:Basic data|Select - FRM:Right: - DDN:Operating concern = IDEA
- Acc|FI|G/L|Master|G/L Acc|Individ Proc|FSP0 In Chart of Acc| 9.6.5.1.SCR:Start - TBX:G/L account = 900005(It will be sub-account of 900000 retained earnings) - DDN:Chart of accounts = INT 9.6.5.1.1.BTN:New 9.6.5.2.SCR:Main - DDN:Account group = SAKO General G/L accounts - CHK:P&L statement acct = True - DDN:P&L statmt. acct type = X - DDN:Functional area = 0400 - TBX:Short text = Expenses SD&M 0005 - DDN:Group account number = 312600: Account number in CONS enterprise chart of Accounts 9.6.5.2.1.BTN:Save - Acc|FI|G/L|Master|G/L Acc|Individ Proc|FSS0 In Company| 9.6.6.1.SCR:Start - TBX:G/L account = 900005 - DDN:Company = 1000 9.6.6.1.1.BTN:New 9.6.6.2.SCR:Main 9.6.6.2.1.TAB:Control data - DDN:Tax category = - (only input tax allowed) - CHK:Posting without tax permitted = True - CHK:Line item display = True - DDN:Sort key = 002(DocNum,FiscYr) 9.6.6.2.2.TAB:Create/Bank/Interest - DDN:Field status group = G033(Cost acct ext serv) - DDN:Commitment item = 1423(Misc expense investm) 9.6.6.2.3.BTN:Save
9.6.6.FI:Create G/L account:Company1000|900005:FSS0
9.5.5.IMG:Display Cost Center Accounting:ContArea1000:SPRO
- Tools|Customizing|IMG|SPRO Execute project| 9.5.5.1.SCR:Start - BTN:SAP Reference IMG 9.5.5.2.SCR:Display IMG - CO|General CO|Org|Maint Contr Area| SCR:Basic data| - FRM:Right - LIN:1000|Select - FRM:Left - LIN:Activate components|Select - FRM:Right: - DDN:Cost Center = H1
9.6.General Ledger 9.6.1.IMG:Display Chart of Accounts:International(INT):SPRO
- Tools|Customizing|IMG|SPRO Execute project| 9.6.1.1.SCR:Start - BTN:SAP Reference IMG 9.6.1.2.SCR:Display IMG FI (New)| GL Accounting (New)| Master| G/L Accounts| Preparations|Edit chart of account List| LIN:INT|Select| 9.6.1.2.1.SCR:Details| - DDN:Group Chart of Accts = CONS:For each company 1 Enterprise chart of accounts group (here CONS) can be assigned, which can have more National chart of accounts (eg. INT) to comply legal ruling in several countries. Enterprise and national accounts can be translated forth and back - Tools|Customizing|IMG|SPRO Execute project| 9.6.2.1.SCR:Start - BTN:SAP Reference IMG 9.6.2.2.SCR:Display IMG FI (New)| GL Accounting (New)| Master| G/L Accounts| Preparations|Assign company to chart of accounts| - LIN:Company = 1000, ChartOfAcc = INT, Country ChartOfAcc = GKR
9.6.7.FI:Enter G/L Account Document:Credit:113000Bank Debit:900005 5000EUR:FB50
9.6.2.IMG:Display Chart of Accounts:Company1000:SPRO
- Acc|FI|G/L|Posting|FB50 Enter G/L Acct Doc| 9.6.7.1.SCR:Start - DDN:Company = 1000 9.6.7.2.SCR:Main 9.6.7.2.1.TAB:Basic data 9.6.7.2.1.1.FRM:Lines - LIN:01: - DDN:Document date = Now - DDN:currency = EUR - DDN:G/L account = 900005 - DDN:D/C = S(Debit) - TBX:Amount in doc. Curr = 5000 - DDN:Tax code = V0(0% domestuc input tax) - LIN:02: - DDN:G/L account = 113100 - DDN:D/C = H(Credit) - TBX:Amount in doc. curr = 5000 9.6.7.2.2.BTN:Save - Take note of G/L Acct Doc: 100000051
9.6.3.IMG:Display Chart of Accounts:ContrArea1000:SPRO
- Tools|Customizing|IMG|SPRO Execute project| 9.6.3.1.SCR:Start - BTN:SAP Reference IMG 9.6.3.2.SCR:Display IMG - CO|General CO|Org|Maint Contr Area| SCR:Basic data| - FRM:Right
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. - Acc|FI|G/L|Acct|FS10N Display Balance| 9.6.8.1.SCR:Start - DDN:G/L account = 900005 - DDN:Company code = 1000 - DDN:Fiscal year = CurrYr - DDN:Business area = Empty! - BTN:Run 9.6.8.2.SCR:Main 9.6.8.2.1.FRM:Balance 9.6.8.2.1.1.LIN:Month = CurrMonth - COL:Debit = 5000|DoubleClick|SCR:Line items - lines can be seen, as accunt has line item property set! - LIN:Type=SA,Amount=5000|Select|BTN:View|SCR:Details| - TBX:Document number = 100000051
9.6.8.FI:Check Account:Comp1000|Acct900005:FS10N
9.7.4.FI:Display cleared items:Comp1000, Vend100268:FBL1N
- Acct|FI|AP|Acct|FBL1N Display/Change line item| 9.7.4.1.SCR:Start - DDN:Vendor account = 100268 - DDN:Company code = 1000 - DDN:All items = True - DDN:Posting date = Now - BTN:Run 9.7.4.2.SCR:Main - LIN:Text = Rent 0005, 10000EUR, Cleared? = Not yet - LIN:New, DocType = ZP - LIN:Balance = 0
9.7.Accounts Payable 9.7.1.FI:Enter Vendor Invoice:Vend100268 10000EUR to CCMSD-0005:FB60

- Acct|FI|AP|Doc entry|FB60 Invoice| 9.7.1.1.SCR:Start - DDN:Company = 1000 9.7.1.2.SCR:Main 9.7.1.2.1.TAB:Basic data - DDN:Vendor = 100268 - DDN:Invoice date = Yesterday - DDN:Posting date = Now - TBX:Amount = 10000 - TBX:Tax amount = 0 - DDN:Tax code = 0I(income tax 0%) - TBX:Text = rent 0005 9.7.1.2.1.1.FRM:Lines - Line:01: - DDN:G/L account = 470000 - DDN:D/C = S(Debit) - DDN:Amount in doc. curr = 10000 - DDN:Cost center = CCMSD-0005 9.7.1.2.2.BTN:Save - Take note of vendor invoice number: 1900000020
9.7.5.FI:Display cleared items:ReconcAcct160000:FAGLB03
- Acct|FI|G/L|Acct|FAGLB03 Display balances| 9.7.5.1.SCR:Start - DDN:Account Number = 160000 - DDN:Company = 1000 - DDN:Fiscal Year = CurrYr - BTN:Run 9.7.5.2.SCR:Main - LIN:Month:Balances are influenced by all vendors assigned to 160000 reconciliation account!
9.8.Accounts Receiveable 9.8.1.FI:Display customer with incomplete master data:Comp1000, Cust50005:F.32
- Acct|FI|AR|Credit mngmt|Credit mngmt Info Sys|F.32 Incomplete data| 9.8.1.1.SCR:Start - DDN:Company = 1000 9.8.1.2.SCR:Main - LIN:Cust = 50005: credit master should be empty!
9.8.2.FI:Create Credit Management Master:Cust50005, TotLim:500000, LimCredContArea1000:10000:FD32
9.7.2.FI:Display open items at Vendor Invoice:Comp1000, Vend100268:FBL1N

- Acct|FI|AP|Acct|FBL1N Display/Change line item| 9.7.2.1.SCR:Start - DDN:Vendor account = 100268 - DDN:Company code = 1000 - DDN:Open items = True - DDN:Open to key date = Now - BTN:Run 9.7.2.2.SCR:Main - LIN:Text = Rent 0005, 10000EUR|DoubleClick|SCR:Detail| - DDN:Reconc Acct = 160000:The whole vendor subledger (100248) communicates with G/L through 160000 reconciliation account
9.7.3.FI:Automatic payment run:Comp1000, Vend100268, next month:F111

- Acct|FI|AP|Periodic proc|F111 Payments| 9.7.3.1.SCR:Start - DDN:Run date = Now - TBX:Identification = P0005 9.7.3.1.1.TAB:Parameters - DDN:Posting date = Now - DDN:Documents entered up to = Now - DDN:Company code = 1000 - DDN:Pmnt meths = S(Check) - DDN:Next p/date = Now+1Month - DDN:Vendor = 100268 9.7.3.1.2.BTN:Save 9.7.3.1.3.BTN:Proposal|SCR:Create Proposal - CHK:Start immediately = True - KEY:Enter Wait 1 minute! 9.7.3.1.4.BTN:Update status - TBX:Status = Payment proposal created 9.7.3.1.5.BTN:Display proposal|SCR:View Proposal - In case of error Edit|Proposal|Delete, retry 9.7.3.1.6.BTN:Paymennt run|SCR:Create payment run - CHK:Start immediately = True - KEY:Enter 9.7.3.1.7.BTN:Update status - TBX:Status = Postings created completed
- Acct|FI|AR|Credit mngmt|Master|FD32 Change| 9.8.2.1.SCR:Start - DDN:Customer = 50005 - DDN:Credit control area = 1000 - CHK:Central data = True - CHK:Status = True 9.8.2.2.SCR:Main 9.8.2.2.1.FRM:Central data - TBX:Total amount = 500000 - TBX:Individual limit = 100000(In one order) - DDN:Currency = EUR 9.8.2.2.2.FRM:Status data - TBX:Credit limit = 10000(In one order, one credit control area) Dont press Enter here! - DDN:Risk category = 001(Low) - DDN:Credit rep. group = 001 9.8.2.2.3.BTN:Save
9.8.3.SD:Create Sales Order:50005, 10PC SpeedStarlett0005, Plant1000, SalOrg1000, Chnl10:VA01

- LO|SD|Sales|Order|VA01 Create 9.8.3.1.SCR:Start - DDN:Order type = OR(Standard order) - DDN:SalOrg = 1000 - DDN:DistChan = 10 - DDN:Division = 00 9.8.3.2.SCR:Main 9.8.3.2.1.FRM:Head - DDN:Standard order = Empty! - DDN:Sold-to-party = 50005 - TBX:PO Number = 10005 9.8.3.2.2.TAB:Sales - DDN:Req. deliv.date = Now + 1 week 9.8.3.2.2.1.FRM:Item LINMaterial Order quantity 01 SpeedStarlett-0005 10PC - KEY:Enter:Autofills master- and condition data 9.8.3.2.3.BTN:Save 9.8.3.2.3.1.ERR:Dynamic credit check exceeded - This is normal because 10 SpeedStarlett-0005 costs 24000>10000 limit - KEY:Enter - Take note of sales order number: 13408
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. - Acct|FI|AR|Credit mngmt|Exceptions|VKM1 Release blocked doc| 9.8.4.1.SCR:Start - DDN:Credit control area = 1000 - DDN:Representative group = 001 - DDN:Credit account = 50005 - BTN:Run 9.8.4.2.SCR:Main - LIN:CCArea = 1000, CredAcct = 50005|Select - BTN:Release - BTN:Save
9.8.4.FI:Release Blocked SD Document:Cust50005:VKM1
9.9.5.FI:Asset Explorer:Comp1000, 3414 0005):AW01N
0 (Forklift-
9.9.Asset Accounting 9.9.1.FI:Create Asset Master Record:Asset Forklift-0005 in CostCtr CCMSD-0005:AS01

- Acct|FI|Fixed assets|Asset|Create|AS01 Asset| 9.9.1.1.SCR:Start - DDN:Asset class = 3100(vehicles) - DDN:Company code = 1000 - DDN:Number of similar assets = 1 - BTN:Master data 9.9.1.2.SCR:Main - TBX:Descr = Forklift-0005 9.9.1.2.1.TAB:Time.-dependent - DDN:Business Area = 3000(vehicles) - DDN:Cost Center = CCMSD-0005 - DDN:Plant = 1000 9.9.1.2.2.BTN:Save - Take note of asset number: 3414 0
- Acct|FI|Fixed assets|Asset|AW01N Asset explorer| 9.9.5.1.SCR:Main - DDN:Company = 1000 - DDN:Asset = 3414 0 (Forklift-0005) 9.9.5.2.SCR:Main 9.9.5.2.1.FRM:UpLeft - LIN:DeprecArea = 01(Book deprec US-GAAP)|Select 9.9.5.2.2.FRM:Right 9.9.5.2.2.1.TAB:Planned values - LIN:Months - COL:Depreciation = 2333 9.9.5.2.2.2.TAB:Posted values - LIN:Months - COL:Depreciation = 0(Computed after depreciation run!)
9.10.Balance Sheet and Profit&Loss Statement 9.10.1.FI:Modify Balance Sheet and P&L Report structure:Acct900005 FinStatmt INT:FSS0
9.9.2.FI:Display asset in P&L statement:Comp1000, BuinArea3000:S_ALR_87011965
- Acct|FI|Fixed assets|InfoSys|Reports AssAcct| 9.9.2.1.SCR:Start - DDN:Company = 1000 - DDN:Business area = 3000 - BTN:Run 9.9.2.2.SCR:Main - Asset cannot be found in list because asset master was not posted!
9.9.3.FI: Display asset in Balance Sheet:Comp1000, BuinArea3000:S_ALR_87012284
- Acct|FI|Fixed assets|InfoSys|Reports AssAcct| 9.9.3.1.SCR:Start - DDN:Chart of accounts = INT - DDN:Company Code = 1000 - DDN:Business Area = 3000 - DDN:Financial statement version = INT - BTN:Run 9.9.3.2.SCR:Main - Asset cannot be found in list because asset master was not posted!
- Acc|FI|G/L|Master|G/L Acc|Individ Proc|FSS0 In Company| 9.10.1.1.SCR:Start - TBX:G/L account = 900005 - DDN:Company = 1000 9.10.1.1.1.BTN:Modify 9.10.1.2.SCR:Main 9.10.1.2.1.BTN:Edit FinStatemt|SCR: Edit FinStatemt| - DDN:FinStatemt = INT - By default all unassigned account are in 8000000 Unassigned node 9.10.1.2.1.1.LIN:3000000 - LIN:3080000 - LIN:3082000 - LIN:3082090|Select - BTN:Assign Accts|SCR:Change Accts| - BTN:New line down: FromAcct ToAcct DebitCredit 900005 900005Yes Yes - There can be only 40 accounts in 1 node, if no more free space, modify an existing account! 9.10.1.2.2.BTN:Save|SCR:Change request| - BTN:New - TBX:Description = ChangeReq-0005 - BTN:Save
9.10.2.FI:Create Balance Sheet and P&L Report:Comp1000, FinStatmt INT:S_ALR_87012284

- Acct|FI|Fixed assets|InfoSys|Reports AssAcct| 9.10.2.1.SCR:Start - DDN:Company Code = 1000 - DDN:FinStatmt = INT - DDN:Fiscal year = Current - DDN:Period = Current - BTN:Run - LIN:New Selection|Select 9.10.2.2.SCR:Main 9.10.2.2.1.FRM:Right 9.10.2.2.1.1.LIN:Balance sheet - LIN:P&L statement - LIN:Other operating charges - LIN:Other operating charges - LIN:Other operating charges - LIN:Expenses SD&M 0005:Check 9.10.2.2.2.BTN:Save
9.9.4.FI:Post Asset Acquisition:Buy Forklift-0005 from Vendor1000 for 35000EUR+10%Tax:F-90
- Acct|FI|Fixed assets|Posting|Aquisition|External|F-90 With vendor| 9.9.4.1.SCR:Main 9.9.4.1.1.FRM:Header - DDN:Document date = Now - DDN:Posting date = Now 9.9.4.1.2.FRM:Line item 1 - DDN:Posting key (Pstky) = 31(invoice) - DDN:Vendor Account = 1000 9.9.4.1.2.1.KEY:Enter - TBX:Amount = 38500 - TBX:Tax amount = 3500 - DDN:Tax Code = 1I(income tax 10%) 9.9.4.1.3.FRM:Line item 2 - DDN:Posting key (Pstky) = 70(assets debit) - DDN:Account = 3414 0 (Forklift-0005) - DDN:Transaction type = 100(external acquisition) - DDN:New Company Code = Empty! 9.9.4.1.3.1.KEY:Enter - DDN:Amount = 35000 - DDN:Tax Code = 1I(income tax 10%) 9.9.4.1.4.BTN:Save - Take note of asset document number: 1900000021 - Asset should show up in P&L statement and balance!
10.Managerial Accounting Scenario

10.1.Plot of Scenario 10.1.1.Create master data
10.1.1.1.CO:Create Cost centers: - CC-CA-0005(Cafeteria) - CC-MT-0005(Maintenance) - CC-MF-0005(Manufacturing) 10.1.1.2.CO:Create Statistical key Figure: - EM0005(Employees) 10.1.1.3.CO:Create Secondary Cost Element: - CAF-0005(Cafeteria, for assessment) - MNT-0005(Maintenance, for allocation) - MFT-0005(Manufacturing, for allocation) 10.1.1.4.CO:Create Activity Types: - MT0005(for allocation Maintenance) - MF0005(for allocation Manufacturing) 10.1.1.5.CO:Create Cost Center Gropup: - Group-0005:Containing: - CC-MT-0005(Maintenance) - CC-MF-0005(Manufacturing) 10.1.2.1.CO:Planning number of employees: - EM0005=20 at CC-MF-0005 - EM0005=5 at CC-MT-0005 10.1.2.2.CO:Planning Activity Output: - MT0005=10000H at CC-MT-0005 - MF0005=40000H at CC-MF-0005 10.1.2.3.CO:Planning Primary Cost Input: - 417000(PurchServ)=150000EUR at CC-CA-0005 - 430000(Salaries)=150000EUR at CC-MT-0005 - 420000(DirectLabour)=600000EUR at CC-MF-0005|MF0005 10.1.2.4.CO:Planning Activity Input transfer: - CC-MT-0005MT0005=1000HCC-MF-0005:KP06 10.1.2.5.CO:Plan cafeteria cost assessment: - CC-CA-0005|CAF-0005=150000EURGroup-0005|by EM0005 10.1.2.6.CO:Auto price calculation of activity types: - Group-0005 10.1.3.1.CO:Direct activity allocation: - CC-MT-0005MT0005=200HCC-MF-0005 10.1.3.2.FI:Post external expenses: - 417000(ExternServic)=12500EUR at CC-CA-0005 10.1.3.3.CO:Period-end closing assesment cycle: - CC-CA-0005|CAF-0005Group-0005|by EM0005 10.1.4.1.CO:Create internal order: - 100291 at 4500(R&D) 10.1.4.2.MM:Purchase order to internal order: - 100PC Gearing-0005 from 100268 10.1.4.3.MM:Goods Receipt for Order: - 4500017613 10.1.4.4.CO:Direct activity allocation: - CC-MF-0005MF0005=100H100291 10.1.4.5.FI:Post expenses: - CC-MF-0005|CostElmt420000=1845EUR, CC-MT-0005| CostElmt430000=3600EUR 10.1.4.6.CO:Add cost element to allocation cost element group: - MF-0005OAS_ORDERS 10.1.4.7.CO:Settle internal order: - 100291 10.1.5.1.PP:Create new Work Center: - PL-0005 10.1.5.2.PP:Integrate work center into Routing: - PL-0005SpeedStarlett-0005 10.1.5.3.CO:Run Product cost estimate: - SpeedStarlett-0005
10.1.2.Cost Center Planning
10.1.3.Manual Expenses Posting
10.1.4.Internal Orders
PaulerSoft CANAL notes, page: 49 - Allocated costs are shared as overhead cost on product units - Recives data mainly from: - FI-GL:Stock, - FI-AP:Vendor invoice, - FI-AA:Depreciations 10.2.1.1.1.1.Cost Element Accounting (CO-OM-CEL) - Receives detailed data from: CO-OM-CCA - Aggregates cost occoured at cost centers in Cost elements - Reconcialtes costs and revenues with FI-GL 10.2.1.1.1.2.Activity Based Costing (CO-OM-ABC) - Cost can collected by Activity types|Work Centers - Recives data mainly from: HCM:Personell costs 10.2.1.1.2.Internal Orders (CO-OM-OPA) - Jobs and tasks given in Internal order can also serve as cost collectors 10.2.1.2.Product Cost Controlling (CO-PC) - Collects allocated planned/actual costs from: - CO-OM-CCA:Cost centers|SubCostCenters - CO-OM-ABC:Activities|WorkStation - CO-OM-OPA:Internal Orders - And all they possible cross-cost-flow combinations - Receives other data from: - PP:BOMs - Allocates it to product/service units of production orders - Transfers back data to: MM:Product cost 10.2.1.3.Profitability Analysis (CO-PA) - Recives data mainly from: - FI:Expense/revenue postings - SD:Revenue postings - Measures efficiency in external market segmentwise 10.2.1.4.Profit Center Accounting (EC-PCA) - Recives data mainly from: - FI:Expense/revenue postings - SD:Revenue postings - Measures efficiency in internal market of company 10.2.1.5.Organization 10.2.1.5.1.Client 10.2.1.5.1.1.Operating Concern - Represents market segments in CO-PA - Controling Area - Cost accounting unit - Revenues and costs can be collected and allocated within that - m:m related with companies using the same Operating chart of accounts with same Version of fiscal year - Works in Controlling Area Currency, eg. EUR - Business Area - Company - Can have parallely different Local charts of accounts also - Works with Company/Cost object currency: eg. USD - Purchasing/Sales Organization - Plant - Transaction - Works with Transaction currency: eg. GBP
10.3.CO:Data structures 10.3.1.DEF: CO-OM Master Data Groups
10.1.5.CO-PC:Product Costing
10.3.1.1.Controling area 10.3.1.1.1.Standard hierarchy (compusory) - No-fixed level hierarchy containing master data cost objects 1:m related (cannot contain twice the given master data) - With unique ID name 10.3.1.1.2.Custom hierearchies (optional) - Alternaive non-fixed level hierarchies for reporting purpose, 1 master data can be assigne to m alternative hierarchies - With unique ID name
10.2.DEF:FI-CO:Managerial Accounting 10.2.1.DEF:FI-CO:Managerial accounting/Controlling
- Plans, Tracks actual events, Evaluates internal/external performance of Company - International standard, independent from counry of operation 10.2.1.1.DEF:Overhead Cost Controlling (CO-OM) - DEF:Overhead cost: cost cannot be directly assigned to product units, they are collected at different Cost objects: 10.2.1.1.1.Cost Center Accounting (CO-OM-CCA) - Origin of costs are registered at Cost centers - They can be re-allocated
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 10.3.2.1.DEF:Cost Element - Classification of production factors within controlling area 10.3.2.1.1.Primary cost elements - Created at external service providers/vendors - Have G/L account (in Class 4 Expenses) in operating chart of accounts - Number of G/L account and primary cost category is the same! 10.3.2.1.2.Revenue cost elements - Have G/L account (in Class 8 Revenue) in operating chart of accounts 10.3.2.1.3.Secondary cost elements - CO Internal category - Do not have G/L account in operating chart of accounts, internal operations 10.3.2.2.DEF:Cost Center - Delimited location of cost occourence, OrgUnit in ContrArea - Cost can be originated and reallocated among them - They form non-feyed level hierarchy based on geography| Corporate functions|Subfunctions 10.3.2.3.DEF:Activity Type - Activities of cost centers - Tracing factor of cost allocation among them - Internall allocation is done with the help of secondary cost elements - 1 activity type can be assigned to max 8 cost centers 10.3.2.3.1.For Cost centersActivity type we determine: 10.3.2.3.1.1.Activity output - Manual allocation - Automatic allocation 10.3.2.3.1.2.Activity price: always by sender activity - Planned - Actual 10.3.2.4.DEF:Statistical key figures - Scalar variables assigned to cost center - Tracing factors: serving as the basis of cost allocation - They ar objects in Logistic Information System - Types: 10.3.2.4.1.1.Fixed value: - Cannot be changed over time 10.3.2.4.1.2.Total vatue: - Has to be entered manually in each time period - Cost objects, which can receive only costs from other sender objects for statistical/analysis prurpose - But cannot send costs themselves: 10.3.3.1.Statistical order 10.3.3.2.Statistical object 10.3.3.3.Profit center
PaulerSoft CANAL notes, page: 50 - CO Posting occours among Secondary cost elements - There is no related FI docoment and G/L Accounts - Types: 10.4.3.1.Manual allocation: - Costs: Actual - Date: Manual, executed at period-end closing - Sender (credited): Cost center - Receiver (debited): Usually an external order without automatic processing - Amount: Manualy entered cost 10.4.3.2.Direct activity allocation: - Can happen among cost objects containing the same activity type with activity prices determined - Costs: Planned/Actual - Date: - For planned costs: Auto-Assesment cycles|Segments - For actual costs: Period-end closing assesment cycle - Sender (credited): Only 1 Cost center - Receiver (debited): Can be 1 or more real (not statistical) cost objects - Amount: Cost calculated by manually entered activity amounts activity prices of master data 10.4.3.3.Periodic/indirect allocations: 10.4.3.3.1.Assessment - Can happen among cost objects containing the same: - Statistical key figure: with its values determined (eg. Number of employees), it will be base of allocation, the tracing factor - Cost element: can be primary/secondary - Costs: Planned/Actual - Date: - For planned costs: Auto-Assesment cycles|Segments - For actual costs: Period-end closing assesment cycle - Sender (credited): can only be 1 cost center/business process - Receiver (debited): Can be 1 or more real (not statistical) cost objects (eg. Cost Center Group) - Amount can be: - Auto-proportionated, sender can hold back Residual% optionally: - CostElemt(Receiver) = - StatKeyVal(Receiver) (CostElemt(Sender)-Residual%) / ReciverStatKeyVal(Receiver) - Given by percentages or portions - Manually entered amounts to override automatic ones - Tracback cost elements: we cannot navigate back from reciver cost element to sender cost element) - Except if primary cost elments are grouped into assesment cost element group, and it is used as cost element of assesment, - However this eats up lot of machine resources 10.4.3.3.2.Indirect Activity Allocation - Same as direct allocation, just activity outputs and activity prices are determined automatically 10.4.3.3.3.Distribution 10.4.3.3.4.Template Allocation 10.4.3.3.5.Periodic Reposting - Flexible tool for planning/allocation/monitoring costs 10.4.4.1.TYPE:Validity 10.4.4.1.1.Real 10.4.4.1.2.Statistical 10.4.4.2.TYPE:Scope 10.4.4.2.1.Overhead Orders - Handles hard to allocate overhead costs (eg. Trade fair) 10.4.4.2.2.Investment Orders - Handles costs producing a fixed assed (eg. Warehouse) 10.4.4.2.3.Accrual Orders - Used for offset postings from secondary costs elements calculated internally in CO 10.4.4.2.4.Orders with Revenue - Handles revenues/costs not processed by SD 10.4.4.3.TYPE:Planning of Internal Orders - Plans long lifecycle internal orders only 10.4.4.3.1.Overall planning 10.4.4.3.2.Cost element planning 10.4.4.3.2.1.Primary cost elements 10.4.4.3.2.2.Secondary cost elements/activity types 10.4.4.3.2.3.Revenues 10.4.4.3.3.Unit costing
10.3.2.DEF:CO-OM Master Data: Cost objects
10.4.3.PROC:CO:Cost Allocation
10.3.3.DEF:Statistical objects
10.4.CO:Processes 10.4.1.CYC:CO-OM:Cost Center Planning Overview
10.4.1.1.CO-PA,SD:Sales Plan 10.4.1.2.PP:Required Activity|Process input planning 10.4.1.3.CO-OM:Allocation of requirement among cost centers 10.4.1.4.CO-OM:Computing Activity|Process prices 10.4.1.5.CO-PC:Product costing 10.4.1.6.CO-PA:Measuring profitability, back to sales plan 10.4.2.1.FI:Accounting document - Always has both credit-debit sides! 10.4.2.2.CO:Related CO document - Created only if primary or revenue cost elemnts are affected by FI operation - Related documents can be drilled down from each other - PK:Unique ID - Posted amount - FK:Cost element (optionally ref. to a reconciliation G/L acct) - FK:Receiver:Cost object debited - FK:Sender:Cost object credited (optional): usually there is no credit side, it is a one-sided journal, except if at transfer between 2 cost objects: - Initiated by credit-debit FI document - Or internal CO operation - FK:Reference to accounting document
10.4.4.PROC:CO:Internal Orders
10.4.2.PROC:CO:Posting
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 10.4.4.4.PROC:Posting Internal Order - One sided line item debited at cost centers in a given cost element 10.4.4.5.PROC:Commitment at Internal Order - Special type of posting at overhead internal orders: 10.4.4.5.1.MM-PUR:Pruchase requisition Purchase Order 10.4.4.5.2.Attached Overhead Internal Order - It stores Commitment/Obligo: planned costs of an order 10.4.4.5.3.Goods Receipt - Orders arriving consume this planned commitment - Until it goes to zero - And actual costs of ggods receipt are posted to Internal Order 10.4.4.6.PROC:Settlement of Internal Order - Posting cost of internal order to final receiver cost centers periodically - Arranged by Internal Order master|Settlement rule - Cost can be settled to any type of cost object allowed by customizing 10.4.5.1.DEF:Product Costing - Estimates cost of a product or service 10.4.5.2.Cost data sources: 10.4.5.2.1.With quantity structure: BOM 10.4.5.2.2.Manual entry 10.4.5.2.3.External import 10.4.5.3.PROC:Product costing 10.4.5.3.1.MM:Material master|Production version 10.4.5.3.1.1.Multi-level BOM 10.4.5.3.1.2.Routing 10.4.5.3.1.3.Material prices - Types: - Planned 1/2/3:Rawmat - Tax based and commercial prices:Semi/Finshed - Price control: - Standard - Moving average - Process(once in a period): - CalculatedMarkedReleasedStandard cost estimate 10.4.5.3.2.FI:Post Real expenses of Material G/L Accunts - FI settles actual material costs with the help of Invoice Receipts - Variances are posted to CO-PA:Profitability Analysis 10.4.5.3.3.CO:Debit cost objects (CostCtr/Proj/IntOrd) - Done at period end closing: 10.4.5.3.3.1.Cost structure/split - Product - Cost Component:(Material, Labour, Process, Overhead) - Cost Element/Activity type - Itemization:from BOM and Routing - Cost splits 10.4.5.3.3.2.Plan/Actual/Variance computation - Compares Standard price of material at period end closing - With real costs entered - Variances are posted in CO-PA:Profitability Analysis 10.4.5.3.3.3.Standard price estimate of material is created - Inventory movements are valuated on this price 10.4.6.1.DEF:Profitability Analysis - Analysis of external profitability on OLAP GUI of - Grouping by Market Segments defined by Chacteristics: - Company| - Business Area - SalesOrg| - SalesGrp| - SalesRep - Region - CustGroup| - Customer - ProdCat| - Product
10.4.5.PROC:CO-PC:Product Costing
PaulerSoft CANAL notes, page: 51 - With Value Fields of StatKeyFigs: - Sales quantity - Standard Material Price - = Sales revenue: - + Revenue - - Discounts - - Comissions - - Direct Sales Costs - = Net Revenue: - - Direct material - - Production variable cost - = Contribution margin I: - - Material overhead - - Fixed costs - = Contribution margin II: - +/- Variances of actual/planned standard material prices - = Contribution margin III: - - Other overhead - = Operative Profit - /Cost of capital: - + FI-AP:Payables - + FI-AR:Receivables - + FI-AA:Fixed Assets - + FI-AA,MM:Inventory - = Return On Investment (ROI) 10.4.7.1.DEF:Profit Center Accounting: - Internal evaluation of 1 year profitability on OLAP reporting GUI - Based on StatKeyFigs: - (same as CO-PA) 10.4.7.2.DEF:Profit Center: - Autonom part of Company can be grouped by product line geography corporate function 10.4.7.3.PROC:Profit Center posting - Profit centers are not real but statistical accounting objects, therefore: 10.4.7.3.1.FI-AP,FI-AR:Accounting Doc Entry - Debit Real Expenses - Credit Real Revenues 10.4.7.3.2.CO-OM:Posted first on real cost objects - CostCtr/InternalOrder/Projec/BusinessProc| - CostElemnt/Activity type - CO-PA:Collects external revenues, profits 10.4.7.3.3.EC-PCA: Assigned profit centers statistically posted - Evaluates internal profitability of profit centers
10.4.7.PROC:EC-PCA:Profit center accounting
10.5.CO-OM:Create master data 10.5.1.CO:Create Cost center:CC-CA-0005(Cafteria):KS01:

- FI|CO|CostCtr Acct|Master|CostCtr|Individ Proc|KS01 Create| 10.5.1.1.SCR:Start - DDN:ContrArea = 1000 - TBX:Cost center = CC-CA-0005 - DDN:Validity from = 01.01.CurrYr - DDN:Validity to = 31.12.9999 10.5.1.2.SCR:Main - TBX:Name = Cafeteria-0005 - TBX:Description = Cafeteria-0005 - DDN:Person Responsible = Gabor Pauler - DDN:Cost Center Category = 2(service cost center) - DDN:Hierarchy area = H10005 - DDN:Company Code = 1000 - DDN:Business Area = 9900(Corporate/other) - DDN:Profit Center = PROF-0005 10.5.1.2.1.BTN:Save
10.4.6.PROC:CO-PA:Profitability Analysis
10.5.2.CO:Create Cost center: CC-MT-0005(Maintenance): KS01:

- Same as above, except: - TBX:Name = Maintenance-0005 - TBX:Description = Maintenance-0005
10.5.3.CO:Create Cost center: CC-MF-0005(Manufacturing): KS01:

Same as above, except: TBX:Name = Manufacturing-0005 TBX:Description = Manufacturing-0005 DDN:Cost Center Category = 1(production cost center)
10.5.4.CO:Create Statistical key Figure:EM0005(Employees):KK01
- FI|CO|CostCtr Acct|Master|StatKeyFig|Individ Proc|KK01 Create| 10.5.4.1.SCR:Start - DDN:StatKeyFigure = EM0005 10.5.4.2.SCR:Main - TBX:Name = Number of employees - DDN:Unit = PC - CHK:Fixed = True 10.5.4.2.1.BTN:Save
10.6.2.CO:Planning number of employees:EM0005=20 at CC-MF-0005:KP46

- FI|CO|CostCtr Acct|Planning|StatKeyFig|KP46 Change| 10.6.2.1.SCR:1-301:Stat key figure standard - DDN:Version = 0(planned/actual) - DDN:From period = 1 - DDN:To period = 12 - DDN:Fiscal year = CurrYr - DDN:Cost center = CC-MF-0005(Manufacturing) - DDN:Stat. key figure = EM0005(number of employees) - All others empty! 10.6.2.1.1.BTN:View 10.6.2.2.SCR:Main - COL:Current planned value = 20 10.6.2.2.1.BTN:Save
10.5.5.CO:Create Secondary Cost Element:CAF0005:KA06
- FI|CO|CostCtr Acct|Master|CostElemt|Individ Proc|KA06 Create Secondary| 10.5.5.1.SCR:Start - DDN:ContrArea = 1000 - TBX:Cost center = CAF-0005 - DDN:Validity from = 01.01.CurrYr - DDN:Validity to = 31.12.9999 10.5.5.2.SCR:Main - TBX:Name = Assessment CC-CA-0005 - TBX:Description = Assessment CC-CA-0005 - DDN:Cost Element Category = 42(Assessment) 10.5.5.2.1.BTN:Save
10.6.3.CO:Planning number of employees:EM0005=5 at CC-MT-0005:KP46

- Same as above, except data
10.6.4.CO:Planning Activity Output:MT0005=10000H at CC-MT-0005:KP26
10.5.6.CO:Create Secondary Cost Element: MNT0005:KA06
Same as above, except: TBX:Name = Maint-Alloc-0005 TBX:Description = Maint-Alloc-0005 DDN:Cost Element Category = 43(Internal activity allocation)
10.5.7.CO:Create Secondary Cost Element: MFT0005:KA06
Same as above, except: TBX:Name = Manuf-Alloc-0005 TBX:Description = Manuf-Alloc-0005 DDN:Cost Element Category = 43(Internal activity allocation)
- FI|CO|CostCtr Acct|Planning|Activity output/Prices|KP26 Change| 10.6.4.1.SCR:1-201:Activity output/Prices standard - DDN:Version = 0(planned/actual) - DDN:From period = 1 - DDN:To period = 12 - DDN:Cost center = CC-MT-0005(Maintenance) - DDN:Activity type = MT0005(Maintenance) - All others empty! 10.6.4.1.1.BTN:View 10.6.4.2.SCR:Main - COL:Plan activity = 10000 - COL:Price unit = 00001 10.6.4.2.1.BTN:Save
10.6.5.CO:Planning Activity Output:MF0005=40000H at CC-MF-0005:KP26

- FI|CO|CostCtr Acct|Master|Activity Type|Individ Proc|KL01 Create| 10.5.8.1.SCR:Start - DDN:ContrArea = 1000 - TBX:Cost center = MT0005 - DDN:Validity from = 01.01.CurrYr - DDN:Validity to = 31.12.9999 10.5.8.2.SCR:Main - TBX:Name = Maint-Hour-0005 - TBX:Description = Maint-Hour-0005 - DDN:Activity unit = H - DDN:CostCtrCat = *(All) - DDN:Atyp = 1(Manual entry, alloc) - DDN:Allocation cost element = MNT-0005(Maint-Alloc-0005) 10.5.8.2.1.BTN:Save
10.5.8.CO:Create Activity Types:MT0005:KL01
10.6.6.CO:Planning Primary Cost Input:417000(PurchServ)=150000EUR at CC-CA-0005:KP06

- FI|CO|CostCtr Acct|Planning|Costs/Activity inputs|KP06 Change| 10.6.6.1.SCR:1-101:Costs/Activity inputs standard - DDN:Version = 0(planned/actual) - DDN:From period = 1 - DDN:To period = 12 - DDN:Cost center = CC-CA-0005(Cafeteria) - DDN:Cost element = 417000(PurchService) - All others empty, even activity type! 10.6.6.1.1.BTN:View 10.6.6.2.SCR:Main - COL:Fixed planned cost = 150000 10.6.6.2.1.BTN:Save
10.5.9.CO:Create Activity Types:MF0005:KL01

-
Same as above, except: TBX:Name = Manuf-Hour-0005 TBX:Description = Manuf-Hour-0005 DDN:Allocation cost element = MFT-0005(Manuf-Alloc-0005)
10.6.7.CO:Planning Primary Cost Input:430000(Salaries)=150000EUR at CC-MT-0005:KP06

- FI|CO|CostCtr Acct|Master|Cost Ctr Grp|KSH1 Create| 10.5.10.1.SCR:Start - DDN:ContrArea = 1000 - TBX:CostCtrGroup = Group-0005 10.5.10.2.SCR:Main - LIN01:Group-0005, Description = Receiver of cafeteria cost| Select - BTN:Insert cost center - COL:Left - LIN02:CC-MT-0005 - LIN03:CC-MF-0005 10.5.10.2.1.BTN:Save
10.5.10.CO:Create Cost Center Gropup:Group-0005:KSH1
10.6.8.CO:Planning Primary Cost Input:420000(DirectLabour)=600000EUR at CC-MF-0005| MF0005:KP06

Same as above, except data and: DDN:Activity type = MF0005(Manufacturing) COL:Planned variable cost = 600000 Wages are variable cost therefore we need activity type!
10.6.CO-OM:Cost Center Planning 10.6.1.CO:Set Planner Profile:SAPALL:KP04
- FI|CO|CostCtr Acct|Planning|KP04 Set Planner Profile| 10.6.1.1.SCR:Start - DDN:Planner profile = SAPALL 10.6.1.1.1.BTN:Save user master record
10.6.9.CO:Planning Activity Input transfer:CC-MT0005 MT0005=1000H CC-MF-0005:KP06
- FI|CO|CostCtr Acct|Planning|Costs/Activity inputs|KP06 Change| 10.6.9.1.SCR:1-101:Costs/Activity inputs standard 10.6.9.1.1.BTN:Next 10.6.9.2.SCR:1-102:Activity input dependentindependent standard - DDN:Version = 0(planned/actual) - DDN:From period = 1 - DDN:To period = 12 - DDN:Cost center = CC-MF-0005(Manufacturing) - DDN:Sender Cost center = CC-MT-0005(Maintenance) - DDN:Sender Activity Type = MT0005(Maintenance) - All others empty, even activity type! 10.6.9.2.1.BTN:View 10.6.9.3.SCR:Main - COL:Planned Fixed consumption = 1000 - COL:Planned fixed cost = 0:Because MNT-0005(Maintenance) cost element is not priced yet!!! 10.6.9.3.1.BTN:Save
10.6.12.CO:Auto price calculation of activity types:Group0005:KSPI

- FI|CO|CostCtr Acct|Planning|Allocation|KSPI Price calculation| 10.6.12.1.SCR:Start - DDN:CostCtrGroup = Group-0005 - CHK:No Business Proc = True - DDN:From period = 1 - DDN:To period = 12 - DDN:FiscYr = CurrYr - CHK:Test run = False 10.6.12.1.1.BTN:Run 10.6.12.2.SCR:Main CostCtr ActType FixPriceVarPriceTotPrice CC-MT-0005MT0005 18.00 18.00 CC-MF-0005MF0005 3.45 15.00 18.45 - Irreally high prices can be if SAP accidentally resets pricing unit set at activity outputs!
10.7.CO-OM:Posting Actual Expenses Manually
10.6.10.CO:Check Planning:CC-CA-0005, CC-MT-0005, CCMF-0005:KSBL

- FI|CO|CostCtr Acct|InfSys|Report CostCtrAcct|Planning report|KSBL Cost Center Planning Overwiev| 10.6.10.1.SCR:Start - DDN:Cost center = CC-CA-0005(Cafeteria) 10.6.10.1.1.BTN:Run
- Until this point all data were just planned, now we enter actual data
10.7.1.CO:Plan/Actual comparison:Group-0005: S_ALR_87013611
10.6.11.CO:Plan cafeteria cost assessment: CC-CA-0005| CAF-0005=150000EUR Group-0005|by EM0005:KSUB
- Assesses only planned costs! - FI|CO|CostCtr Acct|Planning|Allocation|KSUB Assessment| 10.6.11.1.SCR:Start - Extras|Cycle|Create|SCR:Create Cycle| - TBX:Cycle = CY0005 - DDN:Start at = 01.01.CurrYr - KEY:Enter - TBX:Descr = Assesment-cycle-CC-CA-0005 10.6.11.1.1.BTN:Attach segment 10.6.11.2.SCR:Segment| - TBX:Name = SEGM-0005 - TBX:Descr = Segment-0005 10.6.11.2.1.TAB:Segment header: - DDN:Assesment cost element = CAF-0005: It collects whatever costs are received by cafeteria previosly! 10.6.11.2.2.TAB:Sender/receiver 10.6.11.2.2.1.COL:From - LIN:Sender - LIN:Cost Ctr = CC-CA-0005 10.6.11.2.2.2.COL:Group - LIN:Receiver - LIN:CostCtr = Group-0005 10.6.11.2.3.TAB:Receiver tracing factor - DDN:Var. Portion type = 6(StatKeyFig) - KEY:Enter 10.6.11.2.3.1.COL:From - LIN:Version = 0(Plan/Actual) - LIN:StatKeyFig = EM0005 10.6.11.2.4.TAB:Receiver weight factors - LIN:CC-MT-0005 = 100% - LIN:CC-MF-0005 = 100% 10.6.11.2.5.BTN:Save 10.6.11.3.SCR:Execute plan assessment:Initial screen - DDN:From period = 1 - DDN:To period = 12 - DDN:FiscYr = CurrYr - CHK:Test run = False 10.6.11.3.1.FRM:Cycle - LIN01:CY0005 10.6.11.3.2.BTN:Run - In case of system capacity problem, retry later! - Allocates 15000EUR cafeteria costs from CC-CAF-0005 to: - CC-MT-0005: 30000EUR + 150000EUR original = 180000EUR/10000H = 18EUR/H - CC-MF-0005:12000EUR + 600000EUR original - But prices of activity transfers are still 0, eg. the 1000H transfer from CC-MT-0005 to CC-MF-0005 instead of 1000H18EUR/H
- FI|CO|CostCtr Acct|Info Sys|Reports CostCtrAcct| Plan/Actual Compare|S_ALR_87013611 CostCtr:Plan/Actual/Variance| 10.7.1.1.SCR:Start - DDN:ContrArea = 1000 - DDN:FiscYr = CurrYr - DDN:From period = 1 - DDN:To period = 12 - DDN:Version = 0(planned/actual) - DDN:CostCtrGroup = Group-0005 - Leave all others Empty! - CHK:Test run = False 10.7.1.1.1.BTN:Run 10.7.1.2.SCR:Main - There should be no actual data!
10.7.2.CO:Direct activity allocation:CC-MT0005 MT0005=200H CC-MF-0005:KB21N
- FI|CO|CostCtr Acct|Actual posting|Activity Alloc|KB21N Enter| 10.7.2.1.SCR:Start 10.7.2.1.1.TAB:Entry data - DDN:ContrArea = 1000 - DDN:DocDate = Now - DDN:PostDate = Now - DDN:Version = 0(planned/actual) - DDN:Screen variant (Scrn var.) = 01(SAP Cost center) - DDN:Input type = L(List Entry) 10.7.2.1.2.FRM:Item SenderCostCtrActivity Type RecCostCtr Amount CC-MT-0005 MT0005 CC-MF-0005200 10.7.2.1.3.BTN:Save - Take note of activity alloc doc number: 900060811
10.7.3.FI:Post external expenses: 417000(ExternServic)=12500EUR at CC-CA-0005:FB50

- Acc|FI|G/L|Posting|FB50 Enter G/L Acct Doc| 10.7.3.1.SCR:Start - DDN:Company = 1000 10.7.3.2.SCR:Main 10.7.3.2.1.TAB:Basic data 10.7.3.2.1.1.FRM:Lines - LIN:01: - DDN:Document date = Now - DDN:Posting date = Now - DDN:currency = EUR - DDN:G/L account = 417000(ExtServic) - DDN:D/C = S(Debit) - TBX:Amount in doc. Curr = 12500 - DDN:Tax code = V0(0% domestuc input tax) - DDN:CostCtr = CC-CA-0005(Cafeteria) - LIN:02: - DDN:G/L account = 113100(Bank) - DDN:D/C = H(Credit) - TBX:Amount in doc. curr = 12500 - DDN:Due on date = Now 10.7.3.2.2.BTN:Save - Take note of G/L Acct Doc: 100000073
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. - Manually entered external cost wont be auto-assessed, it needs period end closing!
10.7.4.CO:Period-end closing assesment cycle:CC-CA0005|CAF-0005 Group-0005|by EM0005:KSU5

- Assesses only real costs! - FI|CO|CostCtr Acct|Period-end-close|Singel function| Allocation|KSU5 Assessment| 10.7.4.1.SCR:Start - Extras|Cycle|Create|SCR:Create Cycle| - TBX:Cycle = PU0005 - DDN:Start at = 01.01.CurrYr - KEY:Enter - TBX:Descr = Real Assesment-0005 - Goto|Cycle run group|BTN:New|SCR:Cycle Run Grp| - TBX:ID = 0005 - TBX:Descr = Group 0005 - KEY:Enter, Enter - We need to create cycle run group to enable it run parallelly with the planning! 10.7.4.1.1.BTN:Attach segment 10.7.4.2.SCR:Segment| - TBX:Name = SEGM-0005 - TBX:Descr = Segment-0005 10.7.4.2.1.TAB:Segment header: - DDN:Assesment cost element = CAF-0005 10.7.4.2.2.TAB:Sender/receiver 10.7.4.2.2.1.COL:From - LIN:Sender - LIN:Cost Ctr = CC-CA-0005 10.7.4.2.2.2.COL:Group - LIN:Receiver - LIN:CostCtr = Group-0005 10.7.4.2.3.TAB:Receiver tracing factor - DDN:Var. Portion type = 6(StatKeyFig) - KEY:Enter 10.7.4.2.3.1.COL:From - LIN:Version = 0(Plan/Actual) - LIN:StatKeyFig = EM0005 10.7.4.2.4.TAB:Receiver weight factors - LIN:CC-MT-0005 = 100% - LIN:CC-MF-0005 = 100% 10.7.4.2.5.BTN:Save 10.7.4.3.SCR:Execute plan assessment:Initial screen - DDN:From period = Curr - DDN:To period = Curr - DDN:FiscYr = CurrYr - CHK:Test run = False 10.7.4.3.1.FRM:Cycle - LIN01:PU0005 10.7.4.3.2.BTN:Run - Actual cost assessments are executed now!
10.8.2.MM:Purchase order:100PC Gearing-0005 from 100268:ME21N

- LO|MM|Purchase|Purchase Order|Create|ME21N Vendor/Plant known 10.8.2.1.SCR:Main 10.8.2.1.1.FRM:Head 10.8.2.1.1.1.TAB:Org.Data - DDN:Vendor = 100268 - DDN:Purch.Org = 1000 - DDN:Purch.Group = 000 - DDN:Company = 1000 10.8.2.1.2.FRM:Item 10.8.2.1.2.1.LIN:10: - COL:Asset category (A) = F(Order) - COL:Material = Gearing-0005 - COL:PO quantity = 100 - COL:DelivDate = Now - COL:Plant (Plnt) = 1000 - KEY:Enter 10.8.2.1.3.FRM:Item detail 10.8.2.1.3.1.TAB:AcctAssignmt - DDN:G/L Acct = 410000 - DDN:Business area = 9900 - DDN:Order = 100291 - DDN:Profit center = PROF-0005 10.8.2.1.4.BTN:Save - Take note of purchase order number: 4500017613
10.8.3.MM:Display Commitments:100291: S_ALR_87012999
- FI|CO|Internal orders|InfSys|Report InternOrd|Plan/Act Compar|Additional Key Fig|S_ALR_87012999 Plan/Act/Commit| 10.8.3.1.SCR:Start - DDN:ContrArea = 1000 - DDN:Fiscal year = CurrYr - DDN:From period = CurrMo - DDN:To period = CurrMo - DDN:Plan version 0(Plan/Actual) 10.8.3.1.1.FRM:Orders 10.8.3.1.1.1.LIN1: 100291 10.8.3.1.2.BTN:Run 10.8.3.2.SCR:Main CostElmt ActCommit AssignPlanAvailabl 410000 0 50000 50000 0 -50000 - LO|MM|Inventory|Goods movement|Goods receipt|For purchase order|MIGO PO number known| 10.8.4.1.SCR:Main: 10.8.4.1.1.FRM:Header: - DDN:Operation = A01(Create goods receipt) - DDN:Reference doc type = R01(Purchase order) - TBX:Reference doc number = 4500017613 - DDN:Movement type = 101 10.8.4.1.1.1.TAB:General: - TBX:Document date = Now - TBX:Delivery date = Now - DDN:Delivery note = * (No delivery note) 10.8.4.1.2.FRM:Items: 10.8.4.1.2.1.LIN1:100PC Gearing-0005 - FRM:Item Detail - TAB:Where - DDN:Stock type = 1(Unrestricted) - DDN:StoreLoc = 0001 - CHK:ItemOK = True 10.8.4.1.3.BTN:Save - Take note of assigned Goods receipt ID: 5000012642
10.8.4.MM:Goods Receipt for Order:4500017613:MIGO
10.8.CO-OM-OPA:Internal Orders 10.8.1.CO:Create internal order:100291 at 4500(R&D):KO04
- FI|CO|Internal orders|Master|KO04 Order manager| 10.8.1.1.SCR:Start - DDN:ContrArea = 1000 - BTN:New 10.8.1.2.SCR:Main - DDN:Order type = 0100(Internal order, development) - KEY:Enter - TBX:Description = Product development costs 0005 10.8.1.2.1.TAB:Assignments: - DDN:Business area = 9900 - DDN:Profit center = PROF-0005 - DDN:Responsible CCtr. = CC-MF-0005(Manufacturing) 10.8.1.2.2.TAB:Control data - BTN:Release - TBX:Status = Released 10.8.1.2.3.BTN:Settlement rule 10.8.1.2.3.1.LIN01: - DDN:Category (Cat) = CTR(CostCtr) - DDN:Settlement receiver = 4500(Research&Development) - TBX:% = 100 - DDN:Settlement type = PER(Periodic) 10.8.1.2.4.BTN:Save - Take note of internal order number: 100291
PaulerSoft CANAL notes, page: 55 - FI|CO|Internal Orders|Period end closing|Single funct| Settlemt|KO88 Individ Proc| 10.8.9.1.SCR:Start - DDN:Order Number = 100291 - DDN:Settlement period = CurrMo - DDN:Posting period = CurrMo - DDN:Fiscal year = CurrYr - DDN:Processing type = Automatic - CHK:Test Run = False 10.8.9.1.1.BTN:Run 10.8.9.2.SCR:Main 10.8.9.2.1.BTN: Select columns Sender ReceiverValContrAreaCurr
ORD100291 CTR4500 51845
10.8.5.CO:Direct activity allocation: CC-MF0005 MF0005=100H 100291:KB21N
10.8.9.CO:Settle internal order:100291:KO88
- FI|CO|CostCtr Acct|Actual posting|Activity Alloc|KB21N Enter| 10.8.5.1.SCR:Start 10.8.5.1.1.TAB:Entry data - DDN:ContrArea = 1000 - DDN:DocDate = Now - DDN:PostDate = Now - DDN:Version = 0(planned/actual) - DDN:Screen variant (Scrn var.) = 02(Order) - DDN:Input type = L(List Entry) 10.8.5.1.2.FRM:Item SenderCostCtrActivity Type RecOrderAmount 100291 100 CC-MF-0005 MF0005 10.8.5.1.3.BTN:Save - Take note of activity alloc doc number: 900060812
- DoubleClick| CostElemt ValContrAreaCurr

410000 650000 50000 1845
10.8.6.FI:Post expenses: CC-MF-0005| CostElmt420000=1845EUR, CC-MT-0005| CostElmt430000=3600EUR: FB50
- Acc|FI|G/L|Posting|FB50 Enter G/L Acct Doc| 10.8.6.1.SCR:Start - DDN:Company = 1000 10.8.6.2.SCR:Main 10.8.6.2.1.TAB:Basic data 10.8.6.2.1.1.FRM:Lines - DDN:Document date = Now - DDN:Posting date = Now - DDN:currency = EUR - LIN:01: - DDN:G/L account = 420000 - DDN:D/C = S(Debit) - TBX:Amount in doc. Curr = 1845 - DDN:Tax code = V0(0% domestuc input tax) - DDN:CostCtr = CC-MF-0005(Manufacturing) - LIN:02: - DDN:G/L account = 430000 - DDN:D/C = S(Debit) - TBX:Amount in doc. Curr = 3600 - DDN:Tax code = V0(0% domestuc input tax) - DDN:CostCtr = CC-MT-0005(Maintenance) - LIN:03: - DDN:G/L account = 113100(Bank) - DDN:D/C = H(Credit) - TBX:Amount in doc. curr = 5445 - DDN:Due on date = Now 10.8.6.2.2.BTN:Save - Take note of G/L Acct Doc: 100000077 - FI|CO|Internal orders|InfSys|Report InternOrd|Plan/Act Compar|Additional Key Fig|S_ALR_87012999 Plan/Act/Commit| 10.8.7.1.SCR:Start - DDN:ContrArea = 1000 - DDN:Fiscal year = CurrYr - DDN:From period = CurrMo - DDN:To period = CurrMo - DDN:Plan version 0(Plan/Actual) 10.8.7.1.1.FRM:Orders 10.8.7.1.1.1.LIN1: 100291 10.8.7.1.2.BTN:Run 10.8.7.2.SCR:Main CostElmt Act Commit AssignPlanAvailabl 410000 500000(order arrived!) 50000 0 -50000 MFT-0005 1845 0 1845 0 -1845
10.9.EC-PCA:Profit Center Accounting 10.9.1.EC-PCA:Profit Center Assignment Monitor:CC-MF0005:1KE4

- FI|CO|ProfCtrAcct|Master|1KE4 Assignment monitor| 10.9.1.1.SCR:Start - Assignment monitor|Cost centers|Not assigned| - DDN:CostCtrCateg = 1(Production) - DDN:Date = Default - CHK:Display Assigned Cost Centers = False - BTN:Run 10.9.1.2.SCR:Main - CC-MF-0005 should not be in list!
10.9.2.EC-PCA:Profit Center Report:PROF0005:S_ALR_87009712
10.8.7.MM:Display Real Costs:100291: S_ALR_87012999
- FI|CO|ProfCtrAcct|InfSys|Reports ProfCtrAcct|List-Orened rep|S_ALR_87009712 Plan/Actual/Variance| 10.9.2.1.SCR:Start - DDN:Controlling area = 1000 - DDN:Fiscal year = CurrYr - DDN:From period = CurrMo - DDN:To period = CurrMo - DDN:Plan version = 0(Plan/Actual) - DDN:Profit center group = 8A-ALL-PRCTR.GLPTC(Contains PROF-0005) - BTN:Run 10.9.2.2.SCR:Main - LIN:PROF-0005|Doubleclick - LIN: PRCtrGrp: Quarter comp, actual|Doubleclick Period Costs CurrMo 1845 Total 26100
10.10.CO-PA:Profitability analysis 10.10.1.CO-PA:Profitability analysis:SalesOrg1000:KE30

- FI|CO|ProfAnalysis|InfSys|KE30 Execute report| 10.10.1.1.SCR:Setting opertaing concern - DDN:Operating concern = IDEA - BTN:Cost based 10.10.1.2.SCR:Start 10.10.1.2.1.FRM:Left 10.10.1.2.1.1.LIN:IDES50|DoubleClick 10.10.1.2.2.FRM:Right - DDN:Sales Org. = 1000 - DDN:Period from = 001.2010 - DDN:Period to = 012.2010. - DDN:Plan/Act Indicator = 0 - DDN:Version = Empty! - DDN:Record = F - CHK:Graphical report output = True - BTN:Run
10.8.8.CO:Add cost element MF-0005 to allocation cost element group OAS_ORDERS:KAH2
- FI|CO|CostElmt Acct|Master|Cost Elmt Grp|KAH2 Change| 10.8.8.1.SCR:Start - Extras|Set ContrArea| - DDN:ContrArea = 1000 - TBX:CostElemnzGroup = OAS_ORDERS 10.8.8.2.SCR:Main - BTN:Insert cost element - COL:Left - LIN02:MFT-0005 10.8.8.2.1.BTN:Save
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 10.10.1.2.3.SCR:OLAP 10.10.1.2.3.1.FRM:Left:Characteristic selection 10.10.1.2.3.2.FRM:Middle:Charact values, Value fields 10.10.1.2.3.3.FRM:LowLeft:StatKeyFig 10.10.1.2.3.4.FRM:LowRight:Chart - Take note of max. gross revenue customer in division 00:Becker Stuttgart
10.11.CO-PC:Product Costing 10.11.1.PP:Create new Work Center:PL-0005:CR01

- LO|PP|Master|WorkCtr|WorkCtr|CR01 Create| 10.11.1.1.SCR:Start - DDN:Plant = 1000(Hamburg) - DDN:Work center = PL-0005 - DDN:Work center cat. = 0003(Person) - DDN:Copy from Plant = 1000(Hamburg) - DDN:Copy from work center = 1420(Manufacturing). 10.11.1.2.SCR:Copy views - BTN:Copy 10.11.1.3.SCR:Main 10.11.1.3.1.TAB:Costing - DDN:Start date = Now - DDN:Cost Center = CC-MF-0005 10.11.1.3.1.1.FRM:Activity type Setup Funct ActType Formula SteupMF0005 SAP001(Prod. Setup time). 10.11.1.3.2.BTN:Save
10.11.2.PP:Integrate work center into Routing:PL0005 SpeedStarlett-0005:CA02
- LO|PP|Master|WorkCtr|Routing|Routing|Stand Routing| CA02 Change| 10.11.2.1.SCR:Start - DDN:Material = SpeedStarlett-0005 - DDN:Plant = 1000(Hamburg) - DDN:Key date = Now 10.11.2.2.SCR:Main 10.11.2.2.1.LIN01: WorkCtr Setup MachineLabor PL-0005 MF0005=15min Empty! Empty! 10.11.2.2.2.BTN:Save - Sometimes it does not acknlowledge changes, repeat it!
10.11.3.CO:Run Product cost estimate:SpeedStarlett0005:CK11N
- FI|CO|ProdCostAcct|ProdCostPlan|Material Costing|Cost Estim with Quant Struct|CK11N Estimate| 10.11.3.1.SCR:Start - DDN:Plant = 1000 - DDN:Material = SpeedStarlett-0005 10.11.3.2.SCR:Main 10.11.3.2.1.TAB:Costing data - DDN:Costing variant = PPC1(Stand cost estim) - DDN:Costing version = 01 - DDN:Costing lot size = 1 10.11.3.2.2.TAB:Dates - KEY:Enter 10.11.3.2.3.BTN:Save 10.11.3.2.4.TAB:Costs 10.11.3.2.4.1.FRM:Itemization LINResorce CostElmt TotalValue 01 CC-MF-0005 PL-0005 MF0005 MFT-0005 4,61EUR
11.Enterprise Asset and Service Management Scenario

11.1.Plot of Scenario 11.1.1.LO-PM:Corrective Maintenance
11.1.1.1.LO-PM:Create Maintenance Request: - 00-B01 pump station| - TEY-00 electric pump| - Frame broken, weld it 11.1.1.2.LO-PM:Create Maintenance Order from request: - 817854 11.1.1.2.1.LO-PM:Run Plan/Actual Cost Analysis, Release 11.1.1.2.2.LO-PM:Planned Material Withdrawal: - 100-600(Support base) 1PC 11.1.1.2.3.LO-PM:Maint.Order Confirmation 11.1.1.2.4.LO-PM:Technical Completion and Cost Analysis 11.1.1.2.5.CO-OM:Cost Settlement 11.1.1.2.6.LO-PM:Business Completion 11.1.1.2.7.LO-PM:Cost Reporting 11.1.1.3.LO-PM:Location Reporting: - MaintPlant = 1000 11.1.2.1.LO-CS:Create Service Order: - 502732:T-CSE100(server down) 11.1.2.2.LO-PM:Service Order Confirmation: 11.1.2.2.1.Time confirmation Act. Act. Final Clear NoWork Operat WorkCtr Plant Type Work Conf Reserv Remain 0010 PC-SERV 1200 1410 3HRTrue True True 0010 PC-SERV 1200 1413 1HRTrue True True 11.1.2.2.2.Goods movements for operation 0010 MaterialQuantityPlantStorageMovement R-1120 1PC1200 0001 261 11.1.2.3.LO-CS:Service Order Billing:
11.1.2.LO-CS:Service Order Processing
11.2.Organizational levels of Maintenance and Service 11.2.1.Client
11.2.1.1.Company 11.2.1.1.1.Plant 11.2.1.1.1.1.DEF:Planning Plant: - Planning unit of maintenance/service - Maintenance Planning Group is resposible for that, in 2 ways: - DEF:Plant specific maintenance : Plan.Plant:Oper.Plant = 1:1 - DEF:Cross-Plant maintenance: Plan.Plant:Oper.Plant = 1:m 11.2.1.1.1.2.DEF:Operating Plant: - Physical place where Operation systems installed - DEF:Plant Sections: - Part of plant with separated maintenance contact person - Locations - Buildings - Coordinates - DEF:Maintenance/Service Work Centers: - Organizational units of operating system - With types : - ALT:Machine group|Machine - ALT:Person group|Person - With functions: - Capacity Planning:compares requirement with number of employees in work center hierarchy - Scheduling:WorkCtr|Formulas|Standard values of time - Costing:by CostCtr|WorkCtr|ActType|ActPriceActInput - With Employees assigned
11.3.Data Structures of Maintenance and Service 11.3.1.DEF:Technical Objects Master
PaulerSoft CANAL notes, page: 57 11.3.1.1.3.1.PK:Compound with fields auto assigned: - Coding template:max. 40char string mask to generate PK, assembled from: - A:Alphabetic wildcard - N:Numeric wildcard - X:Alphanumeric wildcard - Hierarchy level signal - Example: C.1|C.1.1|C.1.1.1, etc. 11.3.1.1.3.2.TAB:General - Object Class - Object Instance - Manufacturer - Linked docs/drawings/permits/manuals 11.3.1.1.3.3.TAB:Location - Address - Coordinate 11.3.1.1.3.4.TAB:Organization - Company - CostCtr - Planning/Operational Plant 11.3.1.1.3.5.TAB:Structure - FK:Equipment - FK:Construction type:references to a material number with BOM defined to describe structure - FK:MainFunctLoc in hierarchy 11.3.1.2.DEF:Pieces of Equipment|Serial numbers - Independent physical objects - Can be installed in functional locations - Can be linked with material master if equipment needs inventory management (eg. more numerous) 11.3.1.2.1.Used for: - Data collection, - Monitoring, - Costing, - Efficiency analysis 11.3.1.2.2.Described by Equipment master data: 11.3.1.2.2.1.PK:Compound:Material num,Serial Number (S/N) - ALT:Can be adopted from manufacturer S/N, but it should form compound unique ID with ameterial number! - ALT:Own serial numbering 11.3.1.2.2.2.TAB:Serial data - Plant - Storage - Customer sold to - Batch number - FK:Material number - FK:Stock item 11.3.1.2.2.3.TAB:General - Object Class - Object Instance - Manufacturer - Linked docs/drawings/permits/manuals 11.3.1.2.2.4.TAB:Location - Address - Coordinate 11.3.1.2.2.5.TAB:Organization - Company - CostCtr - Planning/Operational Plant 11.3.1.2.2.6.TAB:Structure - FK:FunctLocation where installed - FK:Construction type:references to a material number with BOM defined to describe structure - Status:(Installed/Dismantled)
- Used as reference in maintenance/service documnets 11.3.1.1.DEF:Technical systems|Functional locations - Locations where pieces of equipment can be installed 11.3.1.1.1.Used for: - Data collection, - Monitoring, - Costing, - Efficiency analysis 11.3.1.1.2.Segmented by: 11.3.1.1.2.1.Space - Eg. Buildings 11.3.1.1.2.2.Technique - Eg. Hydraulics 11.3.1.1.2.3.Process - Eg. Polymerization 11.3.1.1.3.Described by data:
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 11.3.1.3.Maintenance Bill of Materials (BOM) - Describes the assemblies of location and equipment - These are not related to production as normal BOMs 11.3.1.3.1.ALT:Can describe class of technical objects with identical internal structure - Create a material master record representing a certain class of equipment - Create a BOM for the material - Reference the material number at each instaces of technical objects at Equipment/FunctLoc Master|Structure|Construction field 11.3.1.3.1.1.Material BOM: 11.3.1.3.1.2.Equipment BOM 11.3.1.3.1.3.Functional location BOM 11.3.1.3.2.ALT:Can describe spare parts assembly for a technical object 11.3.1.3.2.1.For Maintenace orders 11.3.1.3.2.2.For Task Lists - Equipment should reference to a material number with inventory 11.3.2.1.DEF:Installing: - Withdraw from stock as material - Install in functional location 11.3.2.2.DEF:Dismantling: - Dismantle from functional location - Put stock as material
11.3.2.Equipment Install/Dismantle Goods movements
PaulerSoft CANAL notes, page: 58 11.4.2.2.4.Materials Required list - FK:Material or BOM - Quantity - FK:Storage 11.4.2.2.4.1.Auto-checks availability: - ALT:Stock items: - Creates Stock Reservations - ALT:Out of stock items - Creates Purchase Requisitions 11.4.2.2.5.Tools required list 11.4.2.2.6.Settlement rule - FK:Cost bearer object - Percentage 11.4.2.2.7.Costing views - Estimated/Planned/Actual costs in 11.4.2.2.7.1.LO-PM view - By Value categories 11.4.2.2.7.2.CO view - By Value categories|Cost elements 11.4.3.1.Capacity check 11.4.3.2.Final material availability check 11.4.3.3.Release (can be done with missing parts also!) - Status:REL(Released) 11.4.3.4.Withdraws materials from stock 11.4.3.4.1.Planned issues 11.4.3.4.1.1.ALT:Stock items: - Stock ReservationGoods Issue references to that 11.4.3.4.1.2.ALT:Out of stock items: - Purchase RequisitionPurchase Order references to thatGoods ReceiptInvoice receiptAccounting Doc Credit/debit Maintenance Order 11.4.3.4.2.Unplanned issues 11.4.3.4.2.1.ALT:Stock items: - Maintenance orderGoods Issue references to that 11.4.3.5.Print Paper-based Docs 11.4.3.5.1.Job ticket: - Contains Maint.Order|Header data for monitor person 11.4.3.5.2.Operation control ticket - Contains Maint.Order|Header data for responsible person 11.4.3.5.3.Material pick list - Summary list for inventory clerk 11.4.3.5.4.Object list - Summary list for inventory clerk 11.4.3.5.5.Material withdrawal slip - Authorizes responsible person to obtain materials 11.4.3.5.6.Time ticket - Standard times and deadlines of operations for workers 11.4.3.5.7.Confirmation slip - Entering actually worked hours for workers 11.4.4.1.SCR:Individual - Time confirmation - Activity reports - Status:PCNF(Partially confirmed) 11.4.4.2.SCR:Collective 11.4.4.2.1.Enter Measurement readings 11.4.4.2.2.Technical confirmation - Status:CNF(Fully confirmed) 11.4.4.2.3.Technical completion at reference date - Status:TECO(Technically completed) - Still can debit Invoice receipts - But open stock/capacity reservations and purchase requisitions are closed! - If there is any problem with maintenance, TECO can be reversed back to REL status, re-opening reservations and requisitions 11.4.4.3.SCR:Cross Application Time Sheets (CATS) - CO order settlement
11.4.3.Scheduling
11.4.PROC:LO-PM:Corrective Maintenance 11.4.1.Notification list

11.4.1.1.Header - CreationDate - Creator 11.4.1.2.Items - FK:Functional location (optional) - FK:Equipment S/N (optional) - FK:Material number (optional) - FK:BOM assembly (optional) - Description of malfunction - Cause - Required activites - Required tasks
11.4.2.1.Ways of creation 11.4.2.1.1.Automatic: - At maintenance plan period, notif.item:maint.order = 1:1 11.4.2.1.2.Combined: - At maintenance plan period,Notif.item:maint.order = m:1 11.4.2.1.3.Direct: - Manually entered in same time, notif.item:maint.order = 1:1 11.4.2.1.4.Unnoticed: - Order entered without preliminary notification 11.4.2.1.5.Urgent: - Order entered after maintenance with technical completion 11.4.2.2.Content 11.4.2.2.1.Header - PK:Number - FK:Type - Description - ScheduledDate - Responsible person for monitor - Creator - Creationdate - LastModifier 11.4.2.2.2.Object list - FK:FuncLoc - FK:Eqipmt - FK:Assembly - FK:S/N - The assigned object themselves do not create control of costs automatically, see settlement rule! 11.4.2.2.3.Operation/Task list - FK:Reference to notification item - FK:Responsible WorkCtr|ActType|ActPriceActInput
11.4.2.Create Maintenance Order
11.4.4.Execution and Completion
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 11.4.4.4.SCR:Display Document Flow 11.4.4.4.1.Notification list 11.4.4.4.1.1.Maintenance Orders - Purchase Requisitions - Purchase Orders - Goods Receipt - Invoice Receipt - Accounting Doc Cred/Deb Maint.Order - Goods Issue 11.4.4.4.1.2.Confirmations 11.4.4.5.SCR:Action log
PaulerSoft CANAL notes, page: 59 11.5.3.3.Material list - Checks material availability: 11.5.3.3.1.ALT:Non-stock items/external services 11.5.3.3.2.ALT:Stock items 11.5.3.4.Tools list 11.5.3.5.Technical Object list 11.5.3.6.Cost/Revenue list 11.5.3.7.Settlement rule - Who receives costs/revenues 11.5.4.1.Final check capacity 11.5.4.2.Final check material availability 11.5.4.3.Auto-create settlement rule 11.5.4.4.Release order:Status=REL 11.5.4.5.Print documents: 11.5.4.5.1.Service Sheet - Controls external services 11.5.4.5.1.1.Service Entry - Records working time of external service providers 11.5.5.1.ALT:Stock materials document flow - Service notificationService OrderSock reservationMaterial withdrawal from stock 11.5.5.2.ALT:Non-stock materials/external services doc. flow - Service notificationService OrderPurchase requisitonPurchase OrderGoods receipt/Service EntryInvoice Receipt, +/-DifferencesAccounting doc to debit by ServicOrder|SettleRule|CostReceiver 11.5.6.1.Overall Technical Completion 11.5.6.1.1.Confirm tasks - Confirm internal work hours - Completion texts 11.5.6.1.2.Accept external services - Good receipt - Service entries 11.5.6.1.3.Confirm materials - Planned/Unplanned withdrawal - Goods receipt 11.5.6.1.4.Confirm travels 11.5.6.1.5.Record technical object changes - Record measure reading values 11.5.6.1.6.Sets status = TECO(Technically completed) - Mark open purchase requistions to delete - Close Stock reservations - Costs and settlement rule can be still changed! 11.5.6.2.CO:Cost posting - Costs are posted:CostCtr|WorkCtr|ActType Service Order 11.5.6.3.CO:Revenue posting 11.5.6.3.1.CS:Create Billing Request - Basis of billing document - List of dynamic items with FK:Material number, which can be: - Pre-summarized - Items can be removed/added back - Summarized again 11.5.6.3.2.CO:Create Billing Document 11.5.6.3.2.1.Single: BillReq:BillDoc = 1:1 11.5.6.3.2.2.Collective: BillReq:BillDoc = m:1 11.5.6.3.2.3.Due list: BillReq(t>t*):BillDoc = m:1 11.5.6.3.3.ALT:Cost bearing Service order - Revenue posted to CS:ServiceOrder - Result:(= Revenue Costs) posted to CO-PA|Result cost object 11.5.6.3.4.ALT:Non-cost bearing Service order - Revenue posted to SD:SalesOrder|Item - Result posted to SD:SalesOrder 11.5.6.4.CO:Order Settlement - Post ServiceOrder costs/revenues - By its Settlement rule - To final settlement reciever:(CO-OM:CostCtr,CO-PA|Segment,.) 11.5.6.5.CS:Business completion 11.5.6.5.1.Sets status = CLSD(Closed) - No further changes can be made
11.5.4.Control
11.4.5.LO-PM-IS:Plant Maintenance Information System| History

11.4.5.1.Content - Completed notifications - Completed orders - Material Where/When Used List - Planned - Unplanned 11.4.5.2.Analysises - Standard - Flexible 11.4.5.3.GUI:OLAP - Data range:FuncLoc|Equipmt|Assembly|S/N - Key figures - Grahic tools:(Frequencies, ABC)
11.5.5.Execution
11.5.PROC:LO-CS:Service Order 11.5.1.Create Service Notification

-
PK:Service Notif Number FK:Customer FK:Material|Finished product (optional) FK:FunctLoc|Assembly|Equipment (optional) FK:PlanningPlant Log(Recorded, Recorder)
11.5.6.Completion
11.5.2.1.Types of creation 11.5.2.1.1.SM02:Revenue bearing: 11.5.2.1.1.1.Direct: - Without notification 11.5.2.1.1.2.Auto: - Notification:Order = 1:1 11.5.2.1.1.3.Combined: - Notification:Order = m:1 11.5.2.1.1.4.From Maintenance Order: - In regular planned intervals 11.5.2.1.2.Non-revenue bearing, created from Sales Order: - FK:Sales Order number 11.5.2.1.2.1.SM01:Pre-planned, assigned to SalesOrd|Item: - FK: Service products| - FK: Material number 11.5.2.1.2.2.SM03:Return/repair, assigned to RepairOrd|Item: - FK:Requirement class - FK:Reqirement type 11.5.2.2.Content 11.5.2.2.1.Header - PK:Service Order Number - FK:Customer - FK:Material|Finished product (optional) - FK:FunctLoc|Assembly|Equipment (optional) - FK:PlanningPlant - Log(Recorded, Recorder, Modified, Modifier, Status) 11.5.2.2.1.1.Task/Operation list - FK:WorkCtr responsible - Deadline - Description - FK:ControlCode - Adds the following views to service order: 11.5.3.1.Employees list - Checks capacity - Schedules work 11.5.3.2.Partner list - External service providers
11.5.2.Create Service Order
11.5.3.Service planning
11.5.7.CS:Cost analysis
- By Value category|CostElmt - Estimated/Planned/Actual costs
11.6.LO-PM:Display Master Data 11.6.1.LO-PM:Display Functional Locations: Plant1000| Sys00(Water clarification):IH06
11.7.3.LO-PM:Run Plan/Actual Comparison Cost Analysis and Release:817854:IW32

- LO|PM|Maint. Proc|Order|IW32 Change| 11.7.3.1.SCR:Start - DDN:Maint.Order number = 817854 11.7.3.2.SCR:Main - Extras|Cost reports|Plan/Actual comparison| CostElemt Descr Amount 400000 RawMat 176,85 655901 Overhead 35,37 11.7.3.2.1.BTN:Release - DDN:Status = REL(Released) 11.7.3.2.2.BTN:Save - Material 100-600 Support base 1PC appears reserved now in MD04 Stock/Req list!
- LO|PM|Mngmt TechObj|FuncLoc|List Edit|IH06 Display| 11.6.1.1.SCR:Start - DDN:PlanningPlant = 1000 - BTN:Run 11.6.1.2.SCR:Main 11.6.1.2.1.LIN00:Plant:Water Clarification|DoubleClick| SCR:Master data| - TAB:Organization: - DDN:Company = 1000 - DDN:CostCtr = 4110 - DDN:WorkCtr = MECHANIK/1000 11.6.1.2.1.1.LIN00-B:Area:Biological clarification - LIN00-B01:Function:Pump station 1 - LIN:TEY-00:Elect.pump 001|DoubleClick|SCR:Master data| - BTN:Structure: - DDN:Construction type = P1000 - LIN00-B01-1:Pump set 1 - LIN00-B01-1A:Valve 1 - LIN00-B01-1B:Valve 2 - LIN00-B01-2:Pump set 2 - LIN00-B01-2A:Valve 1 - LIN00-B01-2B:Valve 2 - LO|PM|Mngmt TechObj|Equipment|IE03 Display| 11.6.2.1.SCR:Start - DDN:Equipment = TEQ-00 11.6.2.2.SCR:Main - TBX:Descr = Electric pump 001 11.6.2.2.1.TAB:Organization - DDN:MaintPlant = 1000 - DDN:CostCtr = 4110 11.6.2.2.2.BTN:Structure - DDN:ConstrType = P-1000 - DDN:FunctLoc = 00-B02 Filter building 11.6.2.2.2.1.BTN:Levels above - LIN00B:Biological cleaning
11.7.4.LO-PM:Planned Material Withdrawal fro Maint.Order: 817854|Mat100-600(Support base):MB11

- LO|PM|Maint. Proc|Completion confirmation|Good movements|MB11 Goods movement| 11.7.4.1.SCR:Main - DDN:Movement type = 261 - DDN:Plant = 1000 - DDN:Storage = 0001 11.7.4.1.1.BTN:To order|SCR:To order| - DDN:Maint.Order number = 817854 - KEY:Enter 11.7.4.1.1.1.FRM:Items - LIN01: 100-600, Support base, 1PC 11.7.4.1.2.BTN:Save - Take note of material document number: 4900038800
11.6.2.LO-PM:Display Equipment Master:TEQ-00:IE03
11.7.LO-PM:Corrective Maintenance 11.7.1.LO-PM:Create Maintenance Request:00-B01|TEY00|Frame:IW26
- LO|PM|Maint. Proc|Notification|Create|IW26 Maint.Reques| 11.7.1.1.SCR:Start - TBX:Descr = Weld broken 0005 - DDN:Equipment = TEY-00(Electric pump) - KEY:Enter 11.7.1.1.1.BTN:Save - Take note of maint.request number: 10001962
- LO|PM|Maint. Proc|Completion confirmation|Entry|IW42 Overall completion confirmation| 11.7.5.1.SCR:Main - Extras|Settings|SCR:Settings| - DDN:Profile = PM0002(Controls content of screen) - BTN:Save - DDN:Maint.Order number = 817854 - KEY:Enter 11.7.5.1.1.FRM:Time confirmation Act. Final Clear NoWork WorkCtr Plant Work Conf Reserv Remain MECHANIK 1000 2HR True True True 11.7.5.1.2.BTN:Save
11.7.5.LO-PM:Maint.Order Confirmation:817854:IW42
11.7.6.LO-PM:Technical Completion and Cost Analysis of MaintOrder:817854:IW32

- LO|PM|Maint. Proc|Order|IW32 Change| 11.7.6.1.SCR:Start - DDN:Maint.Order number = 817854 11.7.6.2.SCR:Main - Order|Functions|Complete|Complete (technically)| SCR:Complete| - CHK:Complete notifications = True - KEY:Enter - DDN:Status = TECO: Reservations cleared, Purchase requisitions flagged for deletion, no further changes allowed! 11.7.6.2.1.BTN: Document flow - LIN:MaintRequest 10001962 - LIN:MaintOrder 817854 - LIN:GoodsIssue 4900038800 - LIN:Confirmation 107722 11.7.6.2.2.TAB:Costs Value category Actual cost Labor 131,57 Materials 176,85 Overhead 0,00 - Take note of costs - Order|Functions|Complete|Complete (business)| SCR:Complete| - ERR: Balance not zero take note of error
11.7.2.LO-PM:Create Maintenance Order from request:817854:IW22
- LO|PM|Maint. Proc|Notification|IW22 Change| 11.7.2.1.SCR:Start - DDN:Maint.Request = 10001962 - BTN:New order 11.7.2.2.SCR:New order - DDN:Order type = PM01 - DDN:Planning plant = 1000 - DDN:Business area = 9900 - DDN:Responsible work center = MECHANIK/1000 11.7.2.3.SCR:Main - DDN:Status = CRTD(Created) 11.7.2.3.1.TAB:Components 11.7.2.3.1.1.BTN:List - LIN:P-1000(Electric pump BOM) - LIN:100-600:Support base|DoubleClick 11.7.2.3.1.2.LIN10:100-600, Support Base, Quantity = 1|Select - BTN: Check material availability|SCR:Confirm.proposal| - DDN:Date = Now - BTN:Continue 11.7.2.3.2.BTN:Save - Take note of Maint.Order number: 817854
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. - Goto|Settlement rule|SCR:Settlement rule| - DDN:Account assignment category = CTR - DDN:Cost Receiver = 4110 - Take note of settings 11.7.6.2.3.BTN:Save
11.8.2.LO-CS:Create Service Order:502732:TCSE100(server down):IW54
11.7.7.CO-OM:Cost Settlement of MaintOrder:817854:KO88
- FI|CO|Internal Orders|Period end closing|Single funct| Settlemt|KO88 Individ Proc| 11.7.7.1.SCR:Start - DDN:Order Number = 817854 - DDN:Settlement period = CurrMo - DDN:Posting period = CurrMo - DDN:Fiscal year = CurrYr - DDN:Processing type = Automatic - CHK:Test Run = False 11.7.7.1.1.BTN:Run 11.7.7.2.SCR:Main 11.7.7.2.1.BTN: Select columns Sender Receiver ValContrAreaCurr
ORD817854 CTR4110 308,42
11.7.8.LO-PM:Business Completion of MaintOrder:817854:IW32
- LO|PM|Maint. Proc|Order|IW32 Change| 11.7.8.1.SCR:Start - DDN:Maint.Order number = 817854 11.7.8.2.SCR:Main - Order|Functions|Complete|Complete (business)| SCR:Complete| - DDN:Status = CLSD(Closed) - LO|PM|Maint. Proc|History|List of order|IW38 Change| 11.7.9.1.SCR:Start - CHK:Open = True - CHK:InProcess = True - CHK:Completed = True - CHK:Historical = True - DDN:From = 01.01.2004 - DDN:To = Now - BTN:Run 11.7.9.2.SCR:Main - BTN: Field selection|COL:Total Planned costs,Total Act costs - COL:Order num|BTN:Sort descending - LIN:Order 817854|Doubleclick|SCR:Order| - Can it be changed? No,because it is in CLSD status - LO|PM|Inf Sys|Standard analysis|IW38 Location| 11.7.10.1.SCR:Start - DDN:MaintPlant = 1000 - DDN:From = 01.01.2004 - DDN:To = Now - BTN:Run 11.7.10.2.SCR:Main - BTN:Switch drilldown|CHK:Equipment=True|KEY:Enter - COL:Total actual costs|BTN:Sort descending - BTN: Field selection|COL:Key and descr - COL:Key and descr|Settings|ColWidth|Characterist| Char=40 - Take note of second highest total cost: 3015.45 at equipment:Electric pump 005
- LO|CS|Service processing|Notification|Create special|IW54 Problem notification| 11.8.2.1.SCR:Main - DDN:Notification = 200000661 - DDN:Descr = Server down 11.8.2.1.1.TAB:Notification 11.8.2.1.1.1.FRM:Referece object - DDN:Equipment = T-CSE100 - KEY:Enter 11.8.2.1.1.2.FRM:Processing - DDN:Priority = 2(High) - KEY:Enter - WRN:Want specify new dates? = No 11.8.2.1.2.BTN:Service Order - DDN:Order type = SM02(Revenue bearing) - DDN:Planning plant = 1200 - DDN:Business area = 8000 - DDN:Responsible work center = PC-SERV(Server technicians) - KEY:Enter 11.8.2.1.2.1.TAB:Operations - LIN10:PC-SERV, 1200, TBX:Work = 4HR 11.8.2.1.2.2.BTN: Process - CHK:Without print = True - KEY:Enter - Take note of service order number (first number): 502732 - LO|CS|Servic. Proc|Completion confirmation|Entry|IW42 Overall completion confirmation| 11.8.3.1.SCR:Main - Extras|Settings|SCR:Settings| - DDN:Profile = CS0001(Controls content of screen) - BTN:Save - DDN:Serv.Order number = 502732 - KEY:Enter 11.8.3.1.1.FRM:Time confirmation Act. Act. Final Clear NoWork Operat WorkCtr Plant Type Work Conf Reserv Remain 0010 PC-SERV 1200 1410 3HRTrue True True 0010 PC-SERV 1200 1413 1HRTrue True True 11.8.3.1.2.FRM:Goods movements for operation 0010 MaterialQuantityPlantStorageMovement R-1120 1PC1200 0001 261 11.8.3.1.3.BTN:Technical completion 11.8.3.1.4.BTN:Save - LO|CS|Servic. Proc|Completion|Billing request|DP90 Individual processing| 11.8.4.1.SCR:Start - DDN:Serv.Order number = 502732 - BTN:Save billing request 11.8.4.2.SCR:Service contract overview 11.8.4.2.1.TAB:Item overview - DDN:Billing blck = Empty! - Sales document|Billing| SCR:Billing| 11.8.4.2.2.BTN:Save - Take note of billing document number: 90038160 - LO|CS|Servic. Proc|Completion|Billing doc|VF03 Display| 11.8.5.1.SCR:Start - DDN:Billing doc number = 90038160 - Billing document|Issue output to| BTN: Print preview|
11.8.3.LO-PM:Service Order Confirmation:502732:IW42
11.7.9.LO-PM:Cost Reporting:817854:IW38
11.7.10.LO-PM:Location Reporting:MaintPlant1000:MCI3
11.8.4.LO-CS:Service Order Billing: 502732:DP90
11.8.5.LO-CS:Display printed bill:90038160:VF03
11.8.LO-CS:Service Order Processing 11.8.1.LO-PM:Display Equipment Master:Cust:T-CSD00| Equip:T-CSE100:IE03

- LO|PM|Mngmt TechObj|Equipment|IE03 Display| 11.8.1.1.SCR:Start - DDN:Equipment = T-CSE100(Server) 11.8.1.2.SCR:Main 11.8.1.2.1.TAB:Partner - DDN:Customer = T-CSD00 11.8.1.2.2.BTN:Structure 11.8.1.2.2.1.BTN:Levels above 11.8.1.2.2.2.BTN:Levels above - LIN:TCST00:HiTech - LIN:TCST00-Admi:HiTech administration - LIN:T-CSE100:Network server - LIN:R-1120:Cable with grounded plug
12.Project Management Scenario

12.1.Plot of scenario: 12.1.1.Enter master data:
12.1.1.1.MM:Create Dummy material for project: - Techno-0005, - Item type = 0005(Milestone billing) - Disposition = ND(No dispo) 12.1.1.2.CO:Create activity types: - T-0005(Test driver) 12.1.1.3.CO:Planning Activity Output/Prices: - T-0005=100EUR/H at 4280(QualContr) 12.1.1.4.CO:Assign Act.Type: - T-0005 to Group TestDriver 12.1.1.5.HCM:Create personell master record: - 9900005 12.1.1.6.HCM:Maintain Personell master data: - OrgUnit = 1300 - CostCtr = 4280(QualContr) - ActType = T-0005(Test driver) 12.1.2.1.PROJ:Techno-doping-0005 12.1.2.1.1.WBS:Development-fixed price 0005: Plan/Bill/AcctAssign 12.1.2.1.1.1.WBS:Blueprint 0005: Plan/Bill/AcctAssign - MLST:Blueprint 0005: Finish specif, CreateSalesDate, Bill=30% 12.1.2.1.1.2.WBS:Prototype 0005: Plan/Bill/AcctAssign - NETW:Prototype-network 0005 - ACT|Internal:Specification 0005 - REL:FS(Follow) - ACT|Internal:Construction 0005 - MLST:Milestone prototype 0005: Close, Milestone, CreateSalesDate, Bill=70% 12.1.2.1.2.WBS:Special expenses 0005: Bill/AcctAssign 12.1.3.1.LO-PS:Auto Schedule Project 12.1.3.2.LO-PS:Manual Easy Cost Planning: - WBS Blueprint by template ZPS101(Elevator) 12.1.3.3.LO-PS:Automatic Network Costing: - Prototype network 12.1.3.4.LO-PS:Project release 12.1.4.1.SD:Create Sales Order Milestone Billing: - 13488: Proj A-10005 1PC 50000EUR for Cust 50005 12.1.4.2.SD:Create Sales Order Resorce-related Billing: - 13489: Mat=Testdriver1 1HR, 200EUR for Cust 50005 - An internal ActType = T-0005(TestDriver-0005) Price=100EUR/H is also created as: - SD:Marketable dummy material = Testdriver1, Standard price = 200EUR/H previously. - At a given WBS = A-10005-2(Special expenses), - Customer 50005 orders it 1HR amount 12.1.4.3.FI:Credit Management|Release orders manually: - Cust50005 12.1.5.1.LO-CO:Manual Actual cost Allocation: - CostCtr4290|ActTyp1429WBS:Blueprint 420H - CostCtr4290|ActTyp1430WBS:Blueprint 180H 12.1.5.2.LO-PS:Confirm&Release bill: - WBS Blueprint 12.1.5.3.LO-PS:Auto entry Actual cost&Confirm&Bill: - Netw:Prototype| - Act:Specification=180HR - Act:Construction=270HR 12.1.5.4.HCM:Project hours: - CostCtr:4280|ActTyp:T-0005|Emp:9900005 - WBS:Special expenses 58HR 12.1.5.5.HCM:Transfer project hours to CO: - Emp:9900005 12.1.6.1.SD:Milestone Billing: - WBS Blueprint, - WBS Prototype 12.1.6.2.SD:Create Resource-related Billing Request: - WBS:Special expenses 12.1.6.3.SD:Create Customer bill from Billing Request: - WBS:Special expenses
PaulerSoft CANAL notes, page: 62 - Different elements can involve different organization levels (see below)
12.3.LO-PS:Project Master Data: 12.3.1.DEF:LO-PS: Project:
- Unique hierarchy of tasks involving multiple corporate functions - With given goal, budget and deadline - Incurring separable cost/revenues/results - Should be done only once or in small number of times 12.3.1.1.Possible OrgLevels - ContArea - Company - BusiArea - ProfCtr - Plant
12.3.2.DEF: Element:
Work Breakdown Structure (WBS)
12.1.2.LO-PS:Create project structure
12.1.3.LO-PS:Project Planning
12.1.4.SD:Project Orders
12.1.5.LO-PS:Project execution
- Optional element of project (some of them have only Networks) - Basic building blocks of project structure forming non-fixed level hierarchy with max. 99 levels, max.10000 WBS - Used for controlling purposes 12.3.2.1.Possible OrgLevels - Company - BusiArea - ProfCtr - Plant - CostCtr - FunctLoc - Equipmt 12.3.2.2.WBS Content: 12.3.2.2.1.Hierachy by: - ALT:Time phases of project - ALT:Product functions of project - ALT:Corporate functions/OrgUnits 12.3.2.2.2.Operative Indicators: 12.3.2.2.2.1.OPT:Planning Element - Allows costs to be assigned 12.3.2.2.2.2.OPT:Account Assignment Element - Allows Network|Activities, Sales Orders to be assigned 12.3.2.2.2.3.OPT:Billing Element - Allows revenues and partial billing to be assigned 12.3.2.2.2.4.OPT:Statistical - Virtual WBS for reporting, cannot work without related real WBS 12.3.2.2.3. Milestones: - Represents an Event in WBS hierarchy: - PK:Auto ID - Short text - Long text - Planned Date - Actual Date (if set, event is considered occoured) - Can be refereced by several operations (eg. partial billing) 12.3.2.2.4.Documentation: - Linked to Document Management System (DMS) - PS:SAP Script text, Word, Excel, CAD, etc. files 12.3.2.3.WBS functions (supports all planning process): 12.3.2.3.1.Budgeting 12.3.2.3.2.Deadlines/Scheduling 12.3.2.3.3.Cost planning 12.3.2.3.4.Purchase Req.Order planning 12.3.2.3.5.Revenue planning 12.3.2.3.6.Payment/Billing planning 12.3.2.3.7.Period end closing 12.3.2.3.8.Aggregated evaluation and reporting 12.3.2.4.WBS GUI:Hierarchy Chart - Horizontally aligned hierarchic block diagram - Displays selected WBS properties, which can be edited
12.1.6.SD:Billing:
12.2.LO-PS:Project Organization Structure:

- No fixed organization! Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage,Aaa|Bbb| -Menu/Submenu, SCR-Screen, FRM-Frame, IDUniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. - Optional elements of project (Some of them have only WBS) - Describing logistic process flow of the project with: 12.3.3.1.Possible OrgLevels - BusiArea - ProfCtr - Plant 12.3.3.2.Network content: 12.3.3.2.1.Header: - FK:Company - FK:ContrArea - FK:Plant - Network type and profile 12.3.3.2.2. Activities: - Represent process steps - Can be connected to: - OPT:Netwok:Activity = m:m (max. m:500) with Relationships - OPT:WBS Element:Activity = 1:m directly in WBS hierarchy - Activity level costs are aggregated into WBS Element, checked against its budget - Only one activity per network can be processed simultaneosly in SAP Network Manager! 12.3.3.2.2.1.PS:Activity Categories|Functions: - Iternal processing - Deadline, - Cost - FK:OrgLevel - BusiArea - ProfCtr - Plant - CostCtr - WrkCtr - External processing - Deadline, - Cost - Purchase Requisition - FK:OrgLevel - PurchOrg - PurchGrp - Plant - BuisArea - ProfCtr - Service - Deadline, - Cost - Purchase Requisition - FK:OrgLevel - PurchOrg - PurchGrp - Plant - BuisArea - ProfCtr - Material Components - Material number - Required quantity - Material Availability, - Purchase Requisition - FK:OrgLevel - PurchOrg - PurchGrp - Plant - Storage - Miscellaneous costs - Most of them are unplanned (eg. unexpected travel) 12.3.3.2.2.2.Activities can contain: - Activity Elements - For further detailing Activities - Has the same Categories|Functions - But cannot be connected with relationships - Documentation: - Linked to Document Management System (DMS) - PS:SAP Script text, Word, Excel, CAD, etc. files 12.3.3.2.3. Relationships: - Connects Activities into Network - From ancestor activity to successors in logic sequence - With 4 types of time synchronization 12.3.3.2.3.1.ALT:FS: - Ancestor(FinishDate)Successor(StartDate) 12.3.3.2.3.2.ALT:SS - Ancestor(StartDate)Successor(StartDate)
12.3.3.DEF:
Network:
PaulerSoft CANAL notes, page: 63 12.3.3.2.3.3.ALT:FF - Ancestor(FinishDate)Successor(FinishDate) 12.3.3.2.3.4.ALT:SF - Ancestor(StartDate)Successor(FinishDate) 12.3.3.2.4.DEF:Multi-networked projects - When WBS Element|Activities are linked to more than one network with relationships - LO-PS executes Critical Path Method (CPM)-type optimization to determine feasible start/finish dates of activities in all of the networks simultaneously 12.3.3.3.Network functions: 12.3.3.3.1.Budgeting 12.3.3.3.2.Deadlines/Scheduling 12.3.3.3.3.Cost planning 12.3.3.3.4.Purchase Req. Order planning 12.3.3.3.5.Revenue planning 12.3.3.3.6.Payment/Billing planning 12.3.3.3.7.Period end closing 12.3.3.3.8.Aggregated evaluation and reporting 12.3.3.4.Network GUI:Network Structure Graphic 12.3.3.4.1.FRM:Process flowchart - Mouse drag&drop edit - Process cycle checking function 12.3.3.4.2.FRM:Activity details form 12.3.3.4.3.FRM:Insertable Activity template list - Project is always related with: 12.3.4.1.DEF:Dummy material - Material symbolizing result of the project 12.3.4.2.Sales Order - Assigns Customer to bill for a project
12.3.4.Related SD documents
12.4.PROC:LO-PS:Project: 12.4.1.Scheduling
12.4.1.1.WBS Elements: - Their dates are not strictly related as they are not connected with relationships! 12.4.1.1.1.ALT:Manual entry: - Project Start/End, WBS dates 12.4.1.1.2.ALT:Inheritance of dates in hierarchy:top down 12.4.1.1.3.ALT:Extrapolation:down top 12.4.1.2.Networks: - Auto-scheduled with CPM algorithm along relationship types 12.4.1.2.1.Types: 12.4.1.2.1.1.Forward: - From earliest possible start date - Of starting activities (no predessor) - Determines earliest start date of activities 12.4.1.2.1.2.Backward: - From latest possible end dates - Of closing activities (no successor) - Determines latest start date of activities 12.4.1.2.2.Scope: - Single network - Related networks - Related networks of WBS Element|Activity - Requests a certain budget for the project - Building it ip from down to top 12.4.2.1.WBS Elements: - Only manual cost planning 12.4.2.1.1.ALT:Overall hierarchic planning - Period|WBS|TotalCost 12.4.2.1.2.ALT:Detailed planning - Period|WBS|CostElement|ActivityType|InputQuant 12.4.2.1.3.ALT:Unit Costing - Period|WBS|CostElement|ActivityType|InputQuantUnitPrice 12.4.2.1.4.ALT:Easy Cost Planning Tool - Provides cost plant templates by - Period|WBS|CostElement|QuantUnitPrice - From template or former projects
12.4.2.Resource and Cost planning
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 12.4.2.2.Networks: - Automatic cost planning - Transferable to other project 12.4.2.2.1.ALT:Internal Process - WrkCtr| - ActType| - Employee| - Capacity, - Planned output (Actual output will consume it) - Price 12.4.2.2.2.ALT:External Process 12.4.2.2.2.1.Purchasing Info Record - Prices - Delivery times 12.4.2.2.2.2.Purchase Requisition - Purchasing Group - Material - Quantity - Unit - Deadline 12.4.2.2.2.3.Purchase Order 12.4.2.2.2.4.Goods Receipt 12.4.2.2.2.5.Invoice Receipt 12.4.2.2.3.ALT:Services - Same as external process, except at good receipt service has to be accepted 12.4.2.2.4.Material planning 12.4.3.1.WBS 12.4.3.1.1.SD:Sales Order 12.4.3.2.Networks 12.4.3.2.1.Assign to Network Header 12.4.3.2.1.1.SD:Sales Order 12.4.3.2.2.Assign to Network Item 12.4.3.2.2.1.CO:Internal Order 12.4.3.2.2.2.PP:Production Order 12.4.3.2.2.3.PM:Maintence Order
PaulerSoft CANAL notes, page: 64 12.4.5.2.1.2.ALT:Internal processing: - Storage Reservation - Commit assigned project element - Record actual cost - It consumes from budget - Production Order - Goods Issue - Accounting doc debiting assigned project element 12.4.5.2.2.Confirmation - By any level of hierarchy Network|Activity|ActivityElement - Puts project element in Status = CNF(Confirmed) 12.4.5.2.2.1.ALT:Collective 12.4.5.2.2.2.ALT:Individual - ALT:Internal: Cross Application Time Sheet (CATS) - ALT:Internet - ALT:From Palm/PocketPC - ALT:Open PS interface - ALT:Process data Capturing (PDC) inerface 12.4.6.1.DEF:Milestone billing: - When a project element closed with milestone is completed - Blocking status of partial bills are released 12.4.6.2.DEF:Resource-related billing: 12.4.6.2.1.DEF:Dummy material for resource-related billing - A previously created internal ActType - Is also created as SD:Marketable dummy material, even with different, higher unit price! - It is assigned to a given WBS of project - And sold to the customer of the project in a given amount - On a separate sales order from Sales Order of Project material: 12.4.6.2.2.DEF:Sales Order of Resource-related billing: - Contains: 12.4.6.2.2.1.DEF:Dynamic Items - Non-fixed data (Dynamic) item of bills summarized during billing process - May be influenced by differences of plan/actual at confirming billed activities 12.4.6.2.2.2.Dynamic Item Processor (DIP) Profile: - Controls their aggregation trough following (m:1) relations: - CATS|WorkHourEmployeeWBS| ActivityActTypAcTypGroupDIP ProfileDummy material - Pricing condition PR00Dummy material - Dummy materialSales OrderResource-related Bill - Computes Resource-related Bill|Dynamic Item|Value = CATS| WorkHour Pricing condition PR00 - It does not use original ActTyp|Unit price for computation! 12.4.7.1.DEF:Full credit/debit settlement of project - Periodically settles costs, which are hard to relate to any activity 12.4.7.1.1.Source data of costs/rebenues - MM:Goods receipt, Stock withdrawal - FI-AR: Vendor Invoices, - SD: Customer Billing - CO-OM: Activity allocations/assesments, Overheads - PS: Confirmations 12.4.7.1.2.Setlement rule - Sender - Receivers - Distribution percentages - Type: - Direct:Project elemnt is settled against a cost object directly - Multiple:Project element is settled with its superior project element with assigned cost object 12.4.7.1.3.Receivers can be - FI-GL:G/L Accoutnts - FI-AA:Assets - CO-PA:Profit cost bjects - LO-PS:Other projects
12.4.6.Project Billing
12.4.3.Assigning Orders to project
- Approves budget limit for the project - Breaking it up top to down 12.4.4.1.Create original budget - Creates consistent budget hierarchy by - Period|WBS|Original costs - Determines rights of user groups to modify 12.4.4.2.Budget update - Compares original - With budget consumers: - Actually incurred costs - Future commitments, orders - Takes eavsive action: 12.4.4.2.1.Supplement 12.4.4.2.2.Return 12.4.4.2.3.Transfer 12.4.4.3.Budget release 12.4.4.4.Budget carryforward between time periods 12.4.5.1.WBS|Activity and 12.4.5.2.Network|Activity|ActivityElemt: 12.4.5.2.1.Record document flows 12.4.5.2.1.1.ALT:External process/Service/Material: - Purchase Requisition - Request vendor Quotation/Bid Invitation - Quotation Entry - Vendor selection - Commit assigned project element - Record actual cost - It consumes from budget - Purchase Order - Goods Receipt - At service:Entry - At service:Acceptance - Invoice receipt/verifivation - Accounting doc debiting assigned project element - ALT:Automatic by project structure - ALT:Manual entry for special expenses
12.4.4.CYC:Budgeting Approval
12.4.7.PS:Project Period end closing
12.4.5.Project Execution
12.4.8.Project Reporting
12.4.8.1.1.Project structure information system - By WBS|Network|Activity|ActivityElement - ActType|Employee|CATS WorkHours 12.4.8.1.2.Cost element report - By WBS|Network|Activity|ActivityElement|CostElemt - Actual/Commited/Total/Plan costs - Export to excel
PaulerSoft CANAL notes, page: 65 - DDN:Activity unit = HR - DDN:CostCtrCat = *(All) - DDN:Atyp = 1(Manual entry, alloc) - DDN:Allocation cost element = 616000(DAA Inspection) 12.6.2.2.1.BTN:Save
12.6.3.CO:Planning Activity Output/Prices:T0005=100EUR/H at 4280(QualContr):KP26
12.5.LO-PS:Project GUI: 12.5.1.LO-PS:Project Builder
12.5.1.1.1.FRM:LeftBottom:Worklist and templates 12.5.1.1.1.1.Last 5 projects 12.5.1.1.1.2.Template projects - Template WBS struct - Template Networks 12.5.1.1.1.3.Project Element templates - WBS|Milestone/Text/Doc, Network|Activity|ActElemt 12.5.1.1.2.FRM:Left:Project structure 12.5.1.1.3.FRM:Right:Details - Horizontally aligned hierarchic block diagram - Displays selected properties of WBS|Milestone/Text/Doc, Network|Activity|ActElemt, which can be edited
12.5.2.LO-PS:Project Planning Board
- FI|CO|CostCtr Acct|Planning|Activity output/Prices|KP26 Change| 12.6.3.1.SCR:1-201:Activity output/Prices standard - DDN:Version = 0(planned/actual) - DDN:From period = 1 - DDN:To period = 12 - DDN:Fiscal year = CurrYr - DDN:Cost center = 4280(QualContr) - DDN:Activity type = T-0005(Test driver-0005) - All others empty! 12.6.3.1.1.BTN:View 12.6.3.2.SCR:Main - COL:Fixed Price = 100EUR/HR 12.6.3.2.1.BTN:Save
12.6.4.CO:Assign Act.Type T-0005 to Group:TestDriver: KLH2

- FI|CO|CostCtr Acct|Master|Act Type Grp|KLH2 Change| 12.6.4.1.SCR:Start - DDN:ActTypeGrp = TestDriver 12.6.4.2.SCR:Main - LIN01:TestDriver, Description = TestDriver|Select - BTN:Insert activity type - COL:Left - LIN02:T-0005 12.6.4.2.1.BTN:Save
12.6.Enter master data: 12.6.1.MM:Create Dummy material for project:Techno0005:MMS1
- LO|MM|Material master|Material|Create special|MMS1 Service| 12.6.1.1.SCR:Start - DDN:Material = Techno-0005 - DDN:Industry = 3(Service provider) 12.6.1.2.SCR:Main - BTN:Organization levels - DDN:Plant = 1300(Frankfurt) - DDN:SalesOrg = 1000(Frankfurt) - DDN:Channel = 10 - DDN:Storage = Empty!(Project cannot be stored) - BTN:Select views:Basic1-2, Sales 1-2-General, MRP 1-2-3-4 12.6.1.2.1.TAB:Basic1: - TBX:Long text = Techno-doping-0005 - DDN:Basic unit of measure = PC(Piece) - DDN:Division = 00(Cross-divisions) - DDN:GenIitemCatGroup 0005 (Milestone - billing) 12.6.1.2.2.TAB:Basic2: - KEY:Enter 12.6.1.2.3.TAB:Sales1: - DDN:Delivering plant = 1300(Frankfurt) - DDN:Tax classification = 1(Full tax) 12.6.1.2.4.TAB:Sales2: - DDN:Matl statistics grp = 1(statistically relevant) - DDN:General Item category group = 0005(Milestone - billing) - DDN:Item category group = 0005(Milestone - billing)!!! 12.6.1.2.5.TAB:SalesGen: - DDN:Material availability check = KP(No checks) 12.6.1.2.6.TAB:MRP1: - DDN:Purchasing group = 000(Chef, H.) - DDN:MRP type = ND(NO MRP) 12.6.1.2.7.TAB:MRP2: - TBX:Planned delivery time = 60DAY 12.6.1.2.8.TAB:MRP3: - DDN:Strategy group = 21(Sales order related settlement):Using this we can link project with sales order 12.6.1.2.9.TAB:MRP4: - KEY:Enter 12.6.1.2.10.BTN:Additional data - DDN:Language = DE - DDN:Descr = Techno-Dope-0005 12.6.1.2.11.BTN:Save - FI|CO|CostCtr Acct|Master|Activity Type|Individ Proc|KL01 Create| 12.6.2.1.SCR:Start - DDN:ContrArea = 1000 - TBX:Cost center = T-0005(Test driver-0005) - DDN:Validity from = 01.01.CurrYr - DDN:Validity to = 31.12.9999 12.6.2.2.SCR:Main - TBX:Name = Test driver-0005 - TBX:Description = Test driver-0005
- HR|Personell mngmnt|Admin|HR Master|PA40 Personell actions| 12.6.5.1.SCR:Start - DDN:Personell number = 9900005 - DDN:StartDate = 01.01.CurrYr! 12.6.5.2.SCR:Main 12.6.5.2.1.FRM:Actions - LIN:Time recording mini master|Select: - This is sipmlified HCM master record suitable for working time recording in CATS! 12.6.5.2.2.BTN:Run 12.6.5.3.SCR:EmployeeGrp - DDN:Personnel area = 1300(Frankfurt) - DDN:Employee (EE) group = 1(active) - DDN:Employee (EE) subgroup = DU(salary staff). 12.6.5.3.1.BTN:Save 12.6.5.4.SCR:PersData - DDN:Title = Mr. - TBX:Last name = Test - TBX:First name = Tom-0005 - DDN:BirthDate = 01.01.1980 12.6.5.4.1.BTN:Save 12.6.5.5.SCR:OrgAssign - DDN:BusinArea = 9900(Corporate/other) 12.6.5.5.1.BTN:Save 12.6.5.6.SCR:BankData 12.6.5.6.1.BTN:Continue 12.6.5.7.SCR:PlannedWorkTime - TBX:Daily working hours = 8 - TBX:Weekly working days = 5 12.6.5.7.1.BTN:Save
12.6.5.HCM:Create personell master record:9900005:PA40
12.6.2.CO:Create activity types:T-0005(Test driver):KL01
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. - HR|Personell management|Administration|HR Master|PA30 Maintain| 12.6.6.1.SCR:Start - DDN:Personell number = 9900005 - DDN:Infotype = 0315(Time Sheet default values) - BTN:New 12.6.6.2.SCR:InfoType0315(Time Sheet default values) - DDN:Sender Cost Center = 4280(quality control) - DDN:Activity type = T-0005 - DDN:Plant = 1300(Frankfurt) 12.6.6.2.1.BTN:Save
12.6.6.HCM:Maintain Personell master data:9900005:PA30
12.7.LO-PS:Create Project Structure, Sceduling, Resources: 12.7.1.LO-PS:Project Builder:A-10005:CJ20N
- LO|PS|Project|CJ20N Project builder| 12.7.1.1.SCR:Welcome - CHK:Skip in future - KEY:Enter 12.7.1.2.SCR:Main 12.7.1.2.1.FRM:Left:Project structure - BTN:New|Project 12.7.1.2.2.FRM:Right:Details - TBX:Project Def. = A-10005 - TBX:Text = Techno-Doping-0005 - DDN:Project Profile = US50(Open PS US) - KEY:Enter 12.7.1.2.2.1.TAB:BasicData - FRM:Organization - DDN:Controlling area = 1000 (CO Europe) - DDN:Company code = 1000 (IDES AG) - DDN:Business area = 9900 (Corporate/other) - DDN:Plant = 1300 (Frankfurt) - FRM:Dates - DDN:Factory calendar = 01(Germany standard): It controls holidays! - DDN:Start date = Now(It can be weekend!) - DDN:End date = 30.CurrMo.CurrYr+3Months( Also!) - FRM:Status - DDN:Status = CRTD(Created) 12.7.1.2.3.CYC:Build Project Structure, Scheduling, Resorces 12.7.1.2.3.1.Drag&drop element - From FRM:Template|WBS/Milest/Netw/Activ/Relat - To FRM:ProjStruct|Superior element of current 12.7.1.2.3.2.Enter element data at FRM:details - TBX:Project definition = Autofilled by system, do not change! - TBX:Desc = Fill manually - KEY:Enter:Add element to structure as soon as possible! Temporary WBS elements cannot processed simultaneously for multiple users by SAP, and they can damage each other unnoticed!!! - DDN,CHK,TBX:Complete other detailed data 12.7.1.2.3.3.Relationships can be created after creating connected Activities PROJ:Techno-doping-0005 WBS:Development-fixed price 0005 - TAB:BasicData|FRM:OperatIndicator| - CHK:Planning element = True - CHK:AcctAssign element = True - CHK:Billing element = True - TAB:Dates|FRM:Basic dates| - DDN:BscStart = Now(Can be weekend) WBS:Blueprint 0005 - TAB:BasicData|FRM:OperatIndicator| - CHK:Planning element = True - CHK:AcctAssign element = True - CHK:Billing element = True - TAB:Dates|FRM:Basic dates| - DDN:BscStart = Now(Can be weekend) - DDN:BscFin = Now+14DY(Can be weekend) MLST:6355:Milestone blueprint 0005 - DDN:Usage = 0003(Finish specification) - CHK:SalesDocDate = True(Copy CPM-scheduled milestone date to sales documents) - TBX:InvoicePercent = 30%(Share in partial billing) - DDN:BasicFixDate = Now+14DY(Can be weekend)
PaulerSoft CANAL notes, page: 66 WBS:Prototype 0005 - TAB:BasicData|FRM:OperatIndicator| - CHK:Planning element = True - CHK:AcctAssign element = True - CHK:Billing element = True - TAB:Dates|FRM:Basic dates| - DDN:BscStart = Now+14DY(Can be weekend) NETW:Prototype-network 0005 - TAB:Control| - DDN:NetwType = PS02 - KEY:Enter - TAB:Scheduling| - DDN:Start date = Now+14DY - DDN:End date = Empty!(CPM-scheduled) - DDN:Scheduling type = 1(Forward from start) - CHK:Schedule automat = False - CHK:Capacity requirement = False - CHK:Exact break times = False ACT|InternalProc:Specification 0005| - BTN: Relationships - TAB:Mixed LIN SuccessorType Operation Construction 0005 0010 Yes FS(Follow) Create it before this! - TAB:Internal - DDN:WrkCtr = 2100 /DDN:Plant = 1300 - KEY:Enter - DDN:ActType = 1421(Personell time) - TBX:Normal duration = 20DY - TBX:Work = 180HR - CHK:Project sum = True ACT|InternalProc:Construction 0005 - TAB:Internal - DDN:WrkCtr = PS01 /DDN:Plant = 1300 - KEY:Enter - DDN:ActType = 1421(Personell time) - TBX:Normal duration = 30DY - TBX:Work = 270HR - CHK:Project sum = True MLST:6356:Milestone prototype 0005 - DDN:Usage = 0006(Close) - CHK:SalesDocDate = True (Copy CPMscheduled milestone date to sales documents) - CHK:MileStoneFunctions = True - TBX:InvoicePercent = 70%(Share in partial billing) WBS:Special expenses 0005 - TAB:BasicData|FRM:OperatIndicator| - CHK:Planning element = False - CHK:AcctAssign element = True - CHK:Billing element = True 12.7.1.2.4.BTN:Save -
12.8.LO-PS:Project planning: 12.8.1.LO-PS:Auto Schedule Project:A-10005:CJ20N

- LO|PS|Project|CJ20N Project builder| 12.8.1.1.SCR:Main 12.8.1.1.1.FRM:Left:Project structure PROJ:Techno-doping-0005|Select - Edit|Dates|Schedule 12.8.1.1.2.BTN:Save
12.8.2.LO-PS:Manual Easy Cost Planning:WBS Blueprint by template ZPS101(Elevator):CJ20N

- LO|PS|Project|CJ20N Project builder| 12.8.2.1.SCR:Main 12.8.2.1.1.FRM:Left:Project structure PROJ:Techno-doping-0005 WBS:Blueprint 0005|Select - Goto|Easy Cost Plan|
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 12.8.2.2.SCR:Easy Cost Plan| - DDN:Costing variant = PS06 - BTN:Create cost estimate 12.8.2.2.1.FRM:Right - BTN:Choose Planning Form|KEY:Enter - LIN:ZPS101(Elevator)|Select|DoubleClick 12.8.2.2.2.FRM:Right - TBX:Internal labor hours = 600 - TBX:Additional costs = Empty! - BTN:Confirm 12.8.2.2.3.FRM:Left:Project structure PROJ:Techno-doping-0005 WBS:Blueprint 0005: 23640EUR|Select - BTN:Show Item View 12.8.2.2.4.FRM:RightDown: - LIN:Engineering1|Select - LIN:Engineering2|Select - BTN:Confirm 12.8.2.2.5.FRM:Left:Project structure PROJ:Techno-doping-0005 WBS:Blueprint 0005: 23640EUR|Select - BTN:Release 12.8.2.3.SCR:Main 12.8.2.3.1.BTN:Save
12.8.3.LO-PS:Automatic Network Costing:Prototype network:CJ20N

- LO|PS|Project|CJ20N Project builder| 12.8.3.1.SCR:Main 12.8.3.1.1.FRM:Left:Project structure PROJ:Techno-doping-0005 WBS:Blueprint 0005 WBS:Prototype 0005 NETW:Prototype-network 0005|Select - Edit|Costs|Calculate costs| - Edit|Costs|Costs itemization| - LIN:Total 10575EUR 12.8.3.2.SCR:Main 12.8.3.2.1.BTN:Save
PaulerSoft CANAL notes, page: 67 12.9.1.2.2.TAB:Sales 12.9.1.2.2.1.FRM:Item LINMaterial Quantity 01 Techno-0005(Proj A-10005) 1PC - ERR:Pricing error: Ignore, project will be priced by individual negotiation! - BTN: Conditions|SCR:Conditions| - TAB:Conditions: ConditionType Amount PR00(Gross price) 50000 Total 59500 - KEY:Enter - TAB:Account Assignment: - DDN:WBS Element = A-10005-1(Development): You can set this only if project material Techno-0005 was set in MM01: - Strategy group = 21(Project with sales order) - Both General and Item group = 0005(Milestone billing) - TAB:Billing plan:(Delete auto-created template rows!) - BTN:Milestone|SCR:Milestone Selection| - DDN:WBS Element = A-10005-1(Development) - KEY:Enter - LIN01:Milestone blueprint|Select - LIN02:Milestone prototype|Select - BTN:Copy - FRM:Milestones LIN Date MlstText Amt % Block Now+ Finish 02(Block bill until 01 15000 30 14DY spec Mlst completed) Now+ 02(Block bill until 02 Close 35000 70 34DY Mlst completed) 12.9.1.2.3.BTN:Save - WRN:Customer exceeded credit limit, order blocked!: Ignore, order will be released manually! - Take note of milestone billing sales order number: 13488
12.8.4.LO-PS:Graphical Project planning tools:A10005:CJ20N

- LO|PS|Project|CJ20N Project builder| 12.8.4.1.SCR:Main 12.8.4.1.1.FRM:Left:Project structure PROJ:Techno-doping-0005|Select 12.8.4.1.2.BTN: Hierarchy graphic: - Horizontally aligned hierarchic bloc diagram of WBS 12.8.4.1.3.BTN: Network graphic: - Flowchart of network activities 12.8.4.1.4.BTN: Project Planning Board: 12.8.4.1.4.1.FRM:Left:Budget Planner 12.8.4.1.4.2.FRM:Right:Business Process Diagram - LO|PS|Project|CJ20N Project builder| 12.8.5.1.SCR:Main 12.8.5.1.1.FRM:Left:Project structure PROJ:Techno-doping-0005|Select - Edit|Status|Release| - Status = REL(Released) 12.8.5.1.2.BTN:Save
12.9.2.SD:Create Sales Order Resorce-related Billing:13489: Mat:Testdriver1 1HR, 200EUR for Cust: 50005:VA01
12.8.5.LO-PS:Project release:A-10005:CJ20N
12.9.SD:Sales order management: 12.9.1.SD:Create Sales Order Milestone Billing: 13488: Proj:A-10005 1PC 50000EUR for Cust:50005:VA01
- LO|SD|Sales|Order|VA01 Create 12.9.1.1.SCR:Start - DDN:Order type = OR(Standard order) - DDN:SalOrg = 1000 - DDN:DistChan = 10 - DDN:Division = 00 12.9.1.2.SCR:Main 12.9.1.2.1.FRM:Head - DDN:Standard order = Empty! - DDN:Sold-to-party = 50005 - TBX:PO Number = 12340005 - KEY:Enter
- An internal ActType = T-0005(TestDriver-0005) Price=100EUR/H is also created as: - SD:Marketable dummy material = Testdriver1, Standard price = 200EUR/H previously. - At a given WBS = A-10005-2(Special expenses), - Customer 50005 orders it 1HR amount - LO|SD|Sales|Order|VA01 Create 12.9.2.1.SCR:Start - DDN:Order type = OR(Standard order) - DDN:SalOrg = 1000 - DDN:DistChan = 10 - DDN:Division = 00 12.9.2.2.SCR:Main 12.9.2.2.1.FRM:Head - DDN:Standard order = Empty! - DDN:Sold-to-party = 50005 - TBX:PO Number = 12340005 - KEY:Enter 12.9.2.2.2.TAB:Sales 12.9.2.2.2.1.FRM:Item LINMaterial Quantity 01 Testdriver1 1HR - BTN: Conditions|SCR:Conditions| - TAB:Conditions: ConditionType Amount PR00(Gross price) 200EUR/HR - TAB:Account Assignment: - DDN:WBS Element = A-10005-2(Special expenses) - KEY:Enter, KEY:Enter - TAB:Sales B: - DDN:DIP Profile = WIP 12.9.2.2.3.BTN:Save - WRN:Customer exceeded credit limit, order blocked!: Ignore, order will be released manually! - Take note of resource-related billing sales order number: 13489
12.9.3.FI:Credit Management|Release orders manually:Cust:50005:VKM1
- Acct|FI|AR|Credit mngmt|Exceptions|VKM1 Release blocked doc| 12.9.3.1.SCR:Start - DDN:Credit control area = 1000 - DDN:Representative group = 001 - DDN:Credit account = 50005 - BTN:Run 12.9.3.2.SCR:Main - LIN1|Select - LIN2|Select - BTN:Release - BTN:Save
12.10.4.HCM:Project hours:CostCtr:4280|ActTyp:T-0005| Emp:9900005 WBS:Special expenses 58HR:CAT2

- HR|Time mngmt|Time sheet|CATS Classic|CAT2 Record working times| 12.10.4.1.SCR:Start - DDN:Data entry profile = 1303(Post to WBS without check) - DDN:Personell number = 9900005 - DDN:Key date = Now - BTN:Change 12.10.4.2.SCR:Main 12.10.4.2.1.FRM:Entry view LINSndCstCtr ActTypRecWBS MoTuWeThFr 01 4280 T-0005A-10005-2(SpecExp) 8 8 8 8 8 - BTN:Release view 12.10.4.2.2.FRM:Release view - LIN01|Select - BTN: Release:HCM can see data entry 12.10.4.2.3.BTN:Save - This will account ActTyp:T-0005 with predefined 100EUR/HR price: 58HR100EUR/HR = 4000EUR!
12.10.LO-PS:Project execution: 12.10.1.LO-CO:Manual Actual cost Allocation: CostCtr4290|ActTyp1429 WBS:Blueprint 420H, CostCtr4290|ActTyp1430 WBS:Blueprint 180H :KB21N
- FI|CO|CostCtr Acct|Actual posting|Activity Alloc|KB21N Enter| 12.10.1.1.SCR:Start 12.10.1.1.1.TAB:Entry data - DDN:ContrArea = 1000 - DDN:DocDate = Now - DDN:PostDate = Now - DDN:Version = 0(planned/actual) - DDN:Screen variant (Scrn var.) = 04(SAP WBS/Order) - DDN:Input type = L(List Entry) 12.10.1.1.2.FRM:Item SenderCostCtr Activity Type WBS Amount 4290(Engineers) 1429 A-10005-11(Blueprint) 420 4290(Engineers) 1430 A-10005-11(Blueprint) 180 12.10.1.1.3.BTN:Save - Take note of blueprint activity alloc doc number: 900060977
12.10.5.HCM:Transfer project hours to CO:Emp:9900005: CAT7

- HR|Time mngmt|Time sheet|Transfer|CAT7 Accounting| 12.10.5.1.SCR:Start - DDN:Personell number = 9900005 - BTN:Run 12.10.5.2.SCR:Main - 3 documents should be posted!
12.11.SD:Billing: 12.11.1.SD:Milestone Billing:WBS Blueprint, WBS Prototype:VF04
12.10.2.LO-PS:Confirm&Release bill:WBS Blueprint:CJ20N
- LO|PS|Project|CJ20N Project builder| 12.10.2.1.SCR:Main 12.10.2.1.1.FRM:Left:Project structure PROJ:Techno-doping-0005 WBS:Blueprint 0005|Select 12.10.2.1.2.FRM:Right - DDN:ActualStart = Now - DDN:ActualFin = Now: When this filled, it means confirmed! 12.10.2.1.3.BTN:Save - Milestone blueprint bill is unlocked and on due list now!
- LO|SD|Billing|Billing doc|VF04 Billing due list| 12.11.1.1.SCR:Start - DDN:Billing date to = Now+4MO - DDN:Sold to party = 50005 - CHK:Order-related = True: Against normal SD billing, PS references to Sales Order instead of Delivery!!! - BTN:Display Bill List 12.11.1.2.SCR:Main 12.11.1.2.1.LIN:15000EUR|Select|BTN:Individual billing doc| 12.11.1.2.1.1.BTN:Save - Take note of blueprint milestone billing doc num: 90038185 12.11.1.2.2.LIN:35000EUR|Select|BTN:Individual billing doc| 12.11.1.2.2.1.BTN:Save - Take note of prototype milestone billing doc num: 90038183
12.10.3.LO-PS:Auto entry Actual cost&Confirm&Bill: Netw:Prototype|Act:Specification=180HR, Act:Construction=270HR :CJ20N
12.11.2.SD:Create Resource-related Billing Request:WBS:Special expenses:DP91
- LO|PS|Project|CJ20N Project builder| 12.10.3.1.SCR:Main 12.10.3.1.1.FRM:Left:Project structure PROJ:Techno-doping-0005 WBS:Blueprint 0005 WBS:Prototype 0005 NETW:Prototype-network 0005 ACT|InternalProc:Specification 0005|Select - Edit|Activity|Confirm |SCR:Confirm| - FRM:Confirm - TBX:Hours = 180HR - KEY:Enter, KEY:Enter - DDN:Status = CNF(Confirmed) ACT|InternalProc:Construction 0005|Select - Edit|Activity|Confirm |SCR:Confirm| - FRM:Confirm - TBX:Hours = 270HR - KEY:Enter, KEY:Enter - DDN:Status = CNF(Confirmed) MLST:Milestone prototype 0005 - DDN:ActDate = Now: Completing all activities auto-completes the whole WBS|Netw|Mlst struc! 12.10.3.1.2.BTN:Save - Milestone prototype bill is unlocked and on due list now!
- LO|SD|Sales|Order|Subsequent functions|DP91 Resourcerelated billing document| 12.11.2.1.SCR:Start - DDN:Sales order number = 13489 (Resorce-related WBS:SpecialExp) - DDN:PostDate = 30.CurrMo+1MO.CurrYr - BTN:Sales price 12.11.2.2.SCR:Sales price 12.11.2.2.1.FRM:Top 12.11.2.2.1.1.LIN:Debit Memo Req - LIN:Testdriver hours - LIN:Testdriver hours 8000EUR|Select 12.11.2.2.2.FRM:Down 12.11.2.2.2.1.TAB:Quantity - LIN01: 40HR - You can manually override CATS working hours entered previously here! 12.11.2.2.2.2.TAB:Conditions - LIN01:PR00 200EUR - You can manually override prevously entered price condition here! 12.11.2.2.3.BTN:Billing request - WRN:Create debit memo request?|BTN:Yes
Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. 12.11.2.3.SCR:Create debit memo request 12.11.2.3.1.TAB:Item overview - DDN:Billing block = Empty! 12.11.2.3.2.TAB:Sales - DDN:Order reason = 008(Good service) 12.11.2.3.3.BTN:Save - Customer 50005 will be debited with 40HR 200EUR/HR = 8000EUR! - Take note of debit memo request: 70000109
12.11.3.SD:Create Customer bill from Billing Request:WBS:Special expenses:VF04
- LO|SD|Billing|Billing doc|VF04 Billing due list| 12.11.3.1.SCR:Start - DDN:Billing date to = Now+4MO - DDN:SD doc = 70000109 - CHK:Order-related = True - BTN:Display Bill List 12.11.3.2.SCR:Main 12.11.3.2.1.LIN:8000EUR|Select|BTN:Individual billing doc| 12.11.3.2.1.1.BTN:Save - Take note of special expenses resource related debit memo billing doc num: 90038186
12.12.LO-PS:Info system: 12.12.1.LO-PS:Info system|Project cost/revenues:A10005:S_ALR_87013531
- LO|PS|InfSys|Financials|S_ALR_87013531 Costs/Revenues/Expenditures/Receipts| 12.12.1.1.SCR:Start - DDN:CtrArea = 1000 - DDN:DB profile = 00000001(Standard) - KEY:Enter 12.12.1.2.SCR:Main - DDN:Project = A-10005 - DDN:Plan version = 0(Plan/Actual) - CHK:Classical drilldown report = True - BTN:Run 12.12.1.3.SCR:Drilldown Report 12.12.1.3.1.FRM:Navigation 12.12.1.3.1.1.OLAP Dimension list, eg.: - ValueCategory|DoubleClick:it will be drilled down - Time|DoubleClick:it will be drilled down - Business Transact|DoubleClick:it will be drilled down 12.12.1.3.1.2.Function buttons - BTN:Chart - LineChart - 3D BarChart - BTN:CurrencyChange - BTN:Export 12.12.1.3.2.FRM:Right- Drilldown area - Here we can open up hierarchy of selected OLAP dimensions 12.12.1.3.3.FRM:Down Year PlanCostActCost PlanRevenue ActRevenue 201034200 3420050000(MilestBill) 50000(MilestBill) (T-0005:40H 100EUR) 200(ResRelBill) 8000(ResRelBill) =4000 Total34200 38200 50200 58000

Terp10 Notes

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Terp10 Notes

Uploaded by

Copyright:

Available Formats

Dr. Gbor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25.

- Mainframe, central processing

1.2.8.2008 SAP ERP 6.0

1.3.SAP ERP Organizational hierarchy: Client/Mandant (901)

1.3.1.FI, CO: Credit Control Area

1.6.SAP ERP Reporting hirearchy 1.6.1.On-Line Transaction Processing (OLTP)

1.6.2.Data Warehousing (DW)

1.6.3.On-Line Analitical Processing (OLAP)

1.4.SAP ERP Data Structure 1.4.1.DEF: Master data

1.8.2.Function button bar

1.8.8.1.KEY:F1:Cursor specific help 1.8.8.2.KEY:F4:Dropdown list of fill aid

1.5.SAP ERP Process examples 1.5.1.Purchase to pay

2.4.1.MM: Create Material Master:MM01

- DEF: Scenarios are case studies to practice business processes

2.1.Organizational environment 2.1.1.Client: 901

2.2.Setting organizational structure in customizing 2.2.1.Tools|Customizing|IMG|SPRO Execute project

2.3.Plot/Preconditions of the scenario 2.3.1.Finished product: Speedstar-0005

2.4.5.MM: Create Purchasing Info records:ME11

2.4.2.MM: Display material list: MM60

2.4.3.MM: Modify materials: MM02

2.4.4.MM: Create Vendor Master: XK01

2.5.Procurement process 2.5.1.MM: Create Purchasing Requisition:ME51N

2.5.3.MM: Display Purchasing Order:ME23N

2.5.4.MM: Display Messages:ME9F

2.5.2.MM: Create Purchasing Order:ME21N

2.5.5.MM: Processing status of purchase requisition:ME53N

2.6.Goods processing 2.6.1.DEF: Stock Usability Types:

2.6.5.MM: Post Goods Receipt:MIGO

2.6.2.DEF: Goods movement documents:

2.6.6.MM: Display Material/Accounting Document:MIGO

2.6.3.MM:Checking stock movement types:ME23N

2.6.7.MM: Material transfers in unrestricted use stock:MIGO

2.6.4.MM:Check Stock Overview:MMBE

2.7.Invoice processing 2.7.1.MM: Enter Vendor Invoice:MIRO

2.8.2.Sales&Distribution (SD): Sales order 2.8.3.Production Planning(PP): 2.8.4.Maintenance( MT):

2.8.5.Warehouse Management System (WMS)

2.7.2.MM: Display Invoice Document and Order History:MIRO

2.7.3.FI:Check subledger account of vendor:FBL1N

2.9.Reporting 2.9.1.MM:List display:ME2L

2.9.2.MM:LIS standard analysis:MCE3

3.Material Planning Scenario

3.3.Creating/Modifying master data 3.3.1.Material master: MM01

3.3.2.Bill Of Material (BOM): CS01

3.4.5.Disaggregation of Production Plan: MC75

3.4.2.Change material: MM02

3.4.3.Create Product Groups: MC84

3.4.6.Material Requirement Planning: MD02

3.4.4.Create Sales and Production Plan: MC82

PaulerSoft CANAL notes, page: 17

3.4.7.Create Sales Order: VA01

3.4.8.Material Requirement Re-Planning: MD02

4.Lifecycle Data management scenario

4.2.Plot of PLM Scenario:

4.1.3.Product structure browser

4.3.CA:Create document info records 4.3.1.DEF: Document Info Record

4.3.2.Document info record: SpeedStar-0005: CV01N

4.1.4.Engineering Change&Configuration Management

4.3.3.Link Document to Material: SpeedStar-0005: CV02N

4.5.CA:Product Structure Browser: SpeedStar-0005: CC04

4.4.CA:Classification of material 4.4.1.Create characteristics: Bike-Type-0005: CT04

4.4.2.Create characteristics: Frame-Type-0005: CT04

4.4.3.Create class: Bike0005: CL02

4.4.4.Classify material: SpeedStar-0005: MMF1