The document discusses the history and architecture of SAP systems including SAP ERP. It also describes SAP ERP organizational hierarchy, data structure, processes and reporting.
The main components of SAP ERP discussed are organizational hierarchy, data structure including master and transactional data, and process examples such as purchase to pay, order to cash, and produce a service.
Examples of SAP ERP business processes given are purchase to pay, order to cash, and produce a service.
Dr. Gábor 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, ID- UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor 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-Modul2- 5.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: SpeedStar- 7.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:Speedstar- 8.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|SD- 7.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, Secret- 7.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-DC- 7.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|Manage- Chn10, Div00:XD01......................................................................................29 0005=50%/Acquise-0005=50%, MA-DC-0005|Manage-0005=50%/Advert- 7.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, ID- UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 3 KnowlExcel≥AboveAvg: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-MF- 9.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-MT- 9.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-MT- 9.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-MF- 9.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:113000BankDebit: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-MT- 9.7. Accounts Payable.....................................................................................47 0005MT0005=1000HCC-MF-0005:KP06.............................................53 9.7.1. FI:Enter Vendor Invoice:Vend100268 10000EUR to CCMSD- 10.6.10. CO:Check Planning:CC-CA-0005, CC-MT-0005, CC-MF- 0005: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|CAF- Vend100268: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=200HCC- 9.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|CAF- LimCredContArea1000: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-MF- 9.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, ID- UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 4 10.8.6. FI:Post expenses: CC-MF-0005|CostElmt420000=1845EUR, CC- 12.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-0005SpeedStarlett- 12.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 5×8HR: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:A- MaintOrder: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:T- CSE100: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, ID- UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 5 1.Introduction - Grouping of the above by corporate functions (SD, FI, CO, 1.1.DEF: Enterprise Resource Planning (ERP) etc.) 1.2.8.1.3.6.Packed Composite application - Manage all business processes inside a company and external - Distrubuted software package grouping of above by SAP links 1.2.8.1.3.7.xApps - On standardized computing platform consisting of separately - Same as above by SAP or external company. Not every part installable modules of SAP is transformed to xApp yet! - Supported by central data warehouse 1.2.8.2.Technology layer: SAP NetWeaver 1.2.SAP Architecture History - Opennes towards .Net, IBM, etc. 1.2.1.1972 SAP R/1, R/2 - Instant integration, incereases Return on investment (ROI) - Mainframe, central processing - Lower total cost of ownment (TCO): easier upgrading 1.2.2.1992 SAP R/3 1.2.8.2.1.People integration: - Client-server, 2 layer architecture 1.2.8.2.1.1.SAP Enterprise Portal: - Real time appliaction - GUI - Did not support full integration of supply chain (suppliers/ - User accounts vendors) - Roles/Rights - 2 layers can be upgraded only together! - Collaboration - Monolithic, applications are linked to business logic - Multi channel access (web, mobile) 1.2.2.1.Technology layer: SAP R/3 Basic 1.2.8.2.2.Information integration: 1.2.2.2.Application layer: 1.2.8.2.2.1.Master Data Management (MDM): 1.2.2.2.1.Finance modules - Central data warehouse - FI: Finance - Imp/Exp interfaces - CO: Controlling 1.2.8.2.2.2.Knowledge Management (KM) - TR: Treasury - Storing unstructured external text/image/sound, etc. Files - IM: Investment management 1.2.8.2.2.3.Business Intelligence (BI) - PS: Project system - Reporting from MDM 1.2.2.2.2.Logistic modules 1.2.8.2.3.Process integration: - SD: Sales distribution 1.2.8.2.3.1.Integration Broker - MM: material management - Synchronization of internal SAP components via ESA - PP: Production planning 1.2.8.2.3.2.Business Process Manager - QM: Quality management - Eclipse-based Business Process Diagrams (BPD) - PM: Plant management - Process monitioring - HR: Human resource 1.2.8.2.3.3.Exchange Infrastructure (XI) - IS: Industry solutions - DEF: Integration Repository : dictionary of protocls 1.2.3.1994 Win NT porting - DEF: Proxy: simulation of a protocol/document format in a 1.2.4.1998 EnjoySAP: user friendly GUI given programming language 1.2.5.1999 MySAP: e-business - SAP-SAP: Idoc, remote function call (RFC) - SAP-External: Files, Java , http, SOAP, .Net 1.2.6.2002 SAP B1: for small companies - B2B: EDIFACT 1.2.7.2003 SAP ERP 1.2.8.2.4.Application integration: - Full supply chain integration with external partners 1.2.8.2.4.1.Web Application Server (Web AS) - Better management of upgrading layers - Handles basic applications of SAP can be found in all 1.2.7.1.Technology layer: SAP NetWeaver distributed SAP packages 1.2.7.2.Application layer: 1.2.8.2.4.2.Development tools: 1.2.7.2.1.SAP R/3 Enterprise - Java 1.2.7.2.2.Additional applications - ABAP - Self service 1.2.8.2.4.3.Lifecycle management: for SAP components - Internet sales 1.2.8.3.Application layer: - Strategic enterprise 1.2.8.3.1.SAP ERP Central Component (ECC) Solution Map: 1.2.8.2008 SAP ERP 6.0 - Analitics flow: 1.2.8.1.DEF: Service-oriented architecture (SOA) - StrategicFinancialOperationsWorkforce 1.2.8.1.1.DEF: Service: - Financial flow: - Small, reusable part of business logic functionality - SCM financeFinac AcctMan AcctCorp.Gover - Often encapsulates parts of original R/3 modules/submodules - HR/HCM flow: 1.2.8.1.2.Protocols used in automatic communication of - TalentWorkforce processWorkforce deploy services - Logistics flow: - In order of usage, from top to down in hierarchy: - ProcurementSupplierInventoryI/O logistTrans 1.2.8.1.2.1.Universal Description Discovery Integration - Manufacturing flow: (UDDI): - PPManuf exeAsset manProd devLifecyc - Dictionary of business services to search a requested service - Sales/Service flow: eg. Credit-worthiness checking - OrderSalesServiceIncentives 1.2.8.1.2.2.Web Service Description Language (WSDL): - Corporate service flow: - Stores I/O structures of the given service - RealestProjectTravelEnvironQM 1.2.8.1.2.3.Simple Object Access Protocol (SOAP): 1.2.8.3.2.Additional applications - Organizes function calls among services - Self service 1.2.8.1.2.4.Extended Markup Language (XML) - Internet sales - Content of I/O communication of function calls - Strategic enterprise 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 Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage,Aaa|Bbb|-Menu/Submenu, SCR-Screen, FRM-Frame, ID- UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 6 1.2.8.4.SAP Product packages: Goods Receipt FI: Invoice Receipt, verification FI: 1.2.8.4.1.SAP Business Suite Payment 1.2.8.4.1.1.ERP: Common basic applications 1.5.2.Order to Cash 1.2.8.4.1.2.PLM: Project Lifecycle management 1.5.2.1.Ex stock sales 1.2.8.4.1.3.SCM: Supply Chain Management - SD: Sales order 1.2.8.4.1.4.SRM: Supplier Resource Management 1.5.2.2.Sales on order 1.2.8.4.1.5.CRM: Customer Relationship Management - SD: Delivery note SD: Transport order MM: Goods receipt 1.3.SAP ERP Organizational hierarchy: Client/Mandant (901) FI: Billing FI: Post payment - Separate enterprise: 1.5.3.Produce a service - Legally, - SD: Cost bearer SD: Sales order FI: Billing FI: Order - Database structure, settlement - Work area 1.6.SAP ERP Reporting hirearchy 1.3.1.FI, CO: Credit Control Area - From down to top - Group of companies where creditworthiness of a customer is 1.6.1.On-Line Transaction Processing (OLTP) checked together - Operative environment: SD, MM, PP, FI, HR 1.3.1.1.FI, CO: Company (1000) 1.6.2.Data Warehousing (DW) - Self contained set of bookkeeping accounts - Administrator Workbench (AWB): Monitoring 1.3.1.1.1.FI, CO: Business Area - Product-based subgrouping of a company 1.6.3.On-Line Analitical Processing (OLAP) 1.3.1.1.2.FI, CO: Controling Area - Information environment - Group of companies sharing costs and revenues 1.6.3.1.Logistic Information System (LIS) 1.3.1.1.2.1.FI, CO: Operating Concerns - Aggregate transaction data by - Standatdized sets of controling measures in a controling area - Time periods reported together - Key figures 1.3.1.1.3.LO: Plant 1.6.3.2.Sales Information Syste (SIS) - One company can have several branch plants 1.7.SAP model company: Internet demonstration and - Central unit of logistics evaluation system (IDES) 1.3.1.1.3.1.MM: Storage location 1.7.1.Organizational structure - Basic unit of inventory management 1.7.2.Customizing 1.3.1.1.4.MM: Purchasing organization 1.7.3.Master data - Part of a company - Negotiates procorement and conditions with vendors 1.7.4.Transaction data 1.3.1.1.5.SD: Sales organization (1000-Frankfurt) 1.7.5.Business processes - Part of a company, accounted at company level 1.7.6.Tutorials - Can sell products from multiple plants 1.8.SAP GUI 7.2 For Win7 - Divided usually by regions 1.8.1.Menu bar 1.3.1.1.5.1.SD: Sales Office 1.8.1.1.Extras| - There can be more sales office for a sales organization 1.8.1.1.1.Settings| 1.3.1.1.6.SD: Distribution Channel (10-Final customers) 1.8.1.1.1.1.Display technical names: - There can be more chanels - Shows transaction codes in SAP menu 1.3.1.1.7.LO: Division/Product group (02-Bike, 03-Paint, 05- 1.8.1.2.Help| Food) 1.8.1.2.1.Application help: Local - Producs subject to common delivery and pricing terms for a 1.8.1.2.2.SAP Library: On-line given customer 1.8.2.Function button bar - Sold in a given distribution channel 1.8.2.1.TBX:Transaction code box 1.3.1.1.7.1.SD,LO:Sales Area(1000-10-02,1000-10-03,1000-10- 1.8.2.1.1.SEARCH_SAP_MENU 05) 1.8.2.2.BTN:Back screen - Combination of Sales Org × Distribution channel × Division 1.8.2.3.BTN:Up screen 1.3.1.1.8.HR: Personell Area 1.8.2.4.BTN:Abort transaction - HR Admin 1.8.2.5.BTN:New modus - Time management 1.8.2.6.BTN:Shortcut - Billing - Place shortcut of transaction on desktop 1.3.1.1.8.1.HR: Personell Subarea 1.8.2.7.BTN:Help - HR: Employee group: 1.8.2.8.BTN:Settings - Retirement and other conditions 1.8.2.8.1.Options| - HR: Employee subgroup: 1.8.2.8.1.1.Design visualization| 1.4.SAP ERP Data Structure - Show keys in dropdown lists: displays technical codes in 1.4.1.DEF: Master data dropdown lists! - Permanent data in time, mor general 1.8.3.Application title bar 1.4.1.1.Customer data 1.8.4.Application function button bar - ID 1.8.5.SAP Easy Access menu - Client 1.8.5.1.Favorites - Company - Sales area 1.8.6.Application work area - Bookkeeping account 1.8.7.Status bar 1.4.1.2.Material data 1.8.8.Hot keys 1.4.1.3.Vendor data 1.8.8.1.KEY:F1:Cursor specific help 1.4.2.Transactions data 1.8.8.2.KEY:F4:Dropdown list of fill aid 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.5.SAP ERP Process examples - Algorithms of transactions involving several modules 1.5.1.Purchase to pay - MM: Material requirement MM: Purchase Order MM:
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 9 2.5.Procurement process - Vendor 2.5.1.MM: Create Purchasing Requisition:ME51N - Info record 2.5.1.1.DEF: Standard Purchase Requisition Process 2.5.2.1.3.Content: - Quantified requirement for purchasing a given material 2.5.2.1.3.1.Header: Whole order related data - Coming from the following sources: 2.5.2.1.3.2.Items: Material related data 2.5.1.1.1.Manual entry - Item category: - By procurement agent of material (Purchasing group = 000) - ALT:Standard 2.5.1.1.2.Material Requirement Planning (MRP) - ALT:Subcontract: vendor delivers finished goods - If MRP method = PD set for the material, SAP automatically - ALT:Consignment: Vendor keeps inventory of finshed calculates material requirement from its requisition quantity with goods in our stock, liability arises taking out from it the help of Bill Of Material (BOM) - ALT:Stock-transport: goods movement between two of our - And considers possible sources of material: plant stock locations - 1. Stock available - ALT:Third paty : Vendor will directly deliver to third party - 2. Own production if Method = X (both external/internal end costumer production) is set - Material - 3. Then purchasing requirement is computed and reqest for - Quantity quotation (RFQ) is sent to vendors - UnitPrice 2.5.1.1.3.Supply Chain Management (SCM)|Advanced Planning - Conditions Optimization (APO) 2.5.2.1.4.Purchase order can be sent to: - This module sold separately from SAP ERP - ALT:Vendor 2.5.1.1.4.Supplier Relationship Management (SRM)|Enterprise - ALT:Another plants stock transfer Buyer Professional (EBP) 2.5.2.1.5.Goods can be delivered to: - This module sold separately from SAP ERP - ALT: Plant 2.5.1.2.DEF: Special Purchase Requirement: Consumable goods - ALT: Place of consumption for consumable goods - DEF: Purchased materials do not form valuated inventory, 2.5.2.2.LO|MM|Purchasing|Purchasing order|Create|ME21N - Their value is booked manually/automatically directly to some Vendor known| Account assignment category: 2.5.2.2.1.SCR:Main - A: Asset 2.5.2.2.1.1.BTN: Document overview on - K: Cost center 2.5.2.2.1.2.FRM:Document overview(left panel) - P: Project - BTN: Selection variant |My purchase requisitions - F: Production order - LIN: Previously created purchase requistiton: 10013838 Do - C: Sales order not doubleclick to read contents! - Within that, a manually/automatically assigned - BTN: Adopt: Copies data to purchase order stock/consumption account 2.5.2.2.1.3.ERR:Data missing 2.5.1.2.1.ALT:Without material master record - DDN:Vendor = 100268 - All these fields are entered at order manually: - DDN:PurchOrg = 1000 - Text, Material group, Order measure unit, 2.5.2.2.1.4.WRN:Discount available from 500:Skip! - Account assignment and its category, 2.5.2.2.1.5.BTN:Items detail:Check items are there! 2.5.1.2.2.ALT:With material master record 2.5.2.2.1.6.BTN:Save - It always has automatic account assignment in material master 2.5.2.2.1.7.WRN:Message cannot be issued: Skip! 2.5.1.2.2.1.ALT:Material type: Non-stock material (NLAG): - Take note of assigned Purchase order ID: 4500017337 - quantity and value are not updated 2.5.3.MM: Display Purchasing Order:ME23N 2.5.1.2.2.2.ALT:Material type: Non-valuated material (UNBW): 2.5.3.1.LO|MM|Purchasing|Purchasing order|ME23N Display - quantity is updated, but value is not. 2.5.3.1.1.SCR:Main 2.5.1.3.LO|MM|Purchasing|Purchasing requisition|ME51N Create| 2.5.3.1.1.1.BTN: Document overview on 2.5.1.3.1.SCR:Main 2.5.3.1.1.2.FRM:Document overview(left panel) 2.5.1.3.1.1.BTN:Item oveview on - BTN: Selection variant |My purchase orders - Fill columns linewise left to right otherwise will not work! - LIN: Previously created purchase order: 4500017337 LI AccAss Material Q Date Pla 2.5.3.1.1.3.FRM:Header: N Cat u nt - TAB:Status:Check status of order! a 2.5.3.1.1.4.FRM:Item: nt - TAB:Delivery schedule: 1 - Gearing- 10 Now+1 10 - LIN1:PurchaseReq.=10013838Check correct reference! 0005 0 wk 00 - TAB:Purchase order history: here one can see history of all 2 K(Cost Gearing- 10 Now+1 10 operations done with the item later cent) 0005 wk 00 This is purchased as commodity, therefore setting 2.5.4.MM: Display Messages:ME9F the account assignment is required! - DEF: Appearence of a purchasing order in a given communica- FRM:Item tion channel (e-mail, fax, etc). It can be customized channelwise TAB:Account assignment - LO|MM|Purchasing|Purchasing order|Message|ME9F Print| DDN:Cost center = 4298(Engineering test bench) - SCR:Start - WRN:If dates on weekend: Ignore, weekend will work! - DDN:Purchase order = 4500017337 2.5.1.3.1.2.BTN:Save - DDN:PurchOrg = 1000 - Take note of assigned Purchase requisition ID: 10013838 2.5.4.1.SCR:Main - LIN:Purchase order = 4500017337 2.5.2.MM: Create Purchasing Order:ME21N 2.5.2.1.DEF:Purchasing Order(PO): - BTN:Display message - Document detailing materials to purchase in given quantities at 2.5.5.MM: Processing status of purchase given prices/conditions from given vendors requisition:ME53N 2.5.2.1.1.Ways of creation: - DEF: The purchaser can track purchasing process in time 2.5.2.1.1.1.ALT:Manually by purchaser - LO|MM|Purchasing|Purchasing requistion|ME53N Display| 2.5.2.1.1.2.ALT:From rference to purchasing requisition: - SCR:Main - Purchaser/ or SAP automatically selects best price bidding - FRM:Overview vendors by their Purchase Info Record|Conditons, for others - LIN: Purchase requistion = 10013838 rejection letter is posted automathically - FRM:Items - Or Purchaser creates individual Outline Agreement with - TAB:Status:Observe status of orders! 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
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 10 2.6.Goods processing - Can be displayed in several layouts set in customizing 2.6.1.DEF: Stock Usability Types: 2.6.4.2.LO|MM|Inventory|Environment|Stock|MMBE Stock 2.6.1.1.ALT:Unrestricted Overview| 2.6.1.2.ALT:Quality inspection 2.6.4.2.1.SCR:Start 2.6.1.2.1.ALT:Material master-based: - DDN:Material = Gearing-0005 - Material regularly inspected, set at: - DDN:Plant = 1000, BTN:Run - MM01|TAB:Purchasing|CHK:Post to insp. Stock = True 2.6.4.2.2.SCR:Main:Check out stock types/levels! 2.6.1.2.2.ALT:Purchase/Production order-based: 2.6.5.MM: Post Goods Receipt:MIGO - Material inspected only once, set at: - DEF:Acknowledgement that vendor delivered the order - Purchase/Production Order|Stock type|Quality inspection - LO|MM|Inventory|Goods movement|Goods receipt|For 2.6.1.3.ALT:Blocked purchase order|MIGO PO number known| 2.6.2.DEF: Goods movement documents: 2.6.5.1.SCR:Main: 2.6.2.1.DEF: Material documents 2.6.5.1.1.FRM:Header: - At least one is created for all types of material movement - DDN:Operation = A01(Create goods receipt) - Primary key: MatDocNumber + MaterialYear - DDN:Reference doc type = R01(Purchase order) - Header: contains general data - TBX:Reference doc number = 4500017337 - Items: contain material related data 2.6.5.1.1.1.TAB:General: 2.6.2.1.1.ALT:Goods receipt: - TBX:Document date = Now - Comes from a vendor or internal production - TBX:Delivery date = Now - Increases stock - DDN:Delivery note = * (No delivery note) - Performs important auxiliary functions: 2.6.5.1.2.FRM:Items: - The system proposes quantity of materials ordered from 2.6.5.1.2.1.LIN1:100pc Gearing-0005 rferenced purchase/production order - FRM:Item Detail - The receiving department checks under/over delivery and - TAB:Where vendor/producing plant is dunned if there is any - DDN:Stock type = 2(Quality inspection) – 100pc - Order history updated gearings are quality inspected before putting on - Quality inspection lot defined unrestricted stock - Warehouse transport requirement created - DDN:StoreLoc = 0001 - Output is printed: eg. Goods receipt as pallet label - CHK:ItemOK = True - Stock level updated 2.6.5.1.3.BTN:Save - Vendor/producing plant notified back - Take note of assigned Goods receipt ID: 5000012369 2.6.2.1.2.ALT:Goods issue: 2.6.6.MM: Display Material/Accounting Document:MIGO - For material issue from stock/consumption/consignment - LO|MM|Inventory|Goods movement|Goods receipt|For - Decreases stock purchase order|MIGO PO number known| 2.6.2.1.3.ALT:Stock transfer: 2.6.6.1.SCR:Main: - Inter-plant physical stock movement 2.6.6.1.1.FRM:Header: 2.6.2.1.4.ALT:Transfer posting: - DDN:Operation = A04(Display) - Non-physical stock movement within one plant’s storages - DDN:Reference doc type = R02(Material document) - Among different usability types - TBX:Reference doc number = 5000012369 2.6.2.2.DEF: Accounting documents - BTN:Run - They created only if valued stock moves, simultaneously with 2.6.6.1.1.1.TAB:DocInfo material document - BTN:FI Documents - But they are independent documents. Corresponding material - DDN:Documents in accounting = Accounting document and accounting documents are linked through they are - Check booked accounts! referencing the same source document (eg. Delivery Note) 2.6.6.1.2.FRM:Items: - Primary key: Company+AcctDocNum+FiscalYear 2.6.6.1.2.1.LIN1:100pc Gearing-0005 - Header: contain general data - FRM:Item Detail: - Items: contain General ledger (G/L) account numbers and - TAB:Where: amounts - BTN:View:Shows stock overview with changes 2.6.3.MM:Checking stock movement types:ME23N 2.6.7.MM: Material transfers in unrestricted use 2.6.3.1.DEF: Stock movement type stock:MIGO - 3-digit codes of all stock movement (material/nonmaterial, - DEF: It is necessary after the delivery inspected and found OK. valued/nonvalued) which control accounting and material - LO|MM|Inventory|Goods movement|Goods receipt|For document display layout. They can be set at: purchase order|MIGO PO number known| 2.6.3.2.LO|MM|Purchasing|Purchasing order|ME23N Display 2.6.7.1.SCR:Main: 2.6.3.2.1.FRM:Item| 2.6.7.1.1.FRM:Header: 2.6.3.2.1.1.LIN##| - DDN:Operation = A08(Transfer posting) - TAB:Delivery| - DDN:Reference doc type = R10(Other) - Transaction type = - DDN:Movement type = 321 - (101)Goods receipt for purchase order 2.6.7.1.1.1.TAB:Transfer posting - (122)Return delivery to vendor - FRM:From and FRM:Dest : - (201)Goods receipt for a cost center - DDN:Material = Gearing-0005 - (301)Transfer posting - DDN:Plant = 1000 - (321)QualInspectUnrestricted - DDN:Storage Location = 0001 - (322) UnrestrictedQualInspect - DDN:Unit of Entry = 100pc, KEY:Enter - (343) Blocked Unrestricted 2.6.7.1.2.BTN:Post:MIGO may give false errors if you do not - (344) Unrestricted Blocked click things EXACTLY in the sequence above, restart it! - (349) Blocked QualInspect - Take note of assigned Material movement ID: 4900038343 - (350) QualInspect Blocked 2.6.8.MM: Display new Material Document:MIGO - (501)Goods receipt without purchase order 2.6.9.MM: Display Stock Overview:MMBE 2.6.4.MM:Check Stock Overview:MMBE 2.6.10.MM: Display Order History:ME23N 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) Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage,Aaa|Bbb|-Menu/Submenu, SCR-Screen, FRM-Frame, ID- UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 11 2.7.Invoice processing 2.7.4.FI: Payment:F58 2.7.1.MM: Enter Vendor Invoice:MIRO 2.7.4.1.DEF:Payment - Plot: Vendor submits an invoice of 55.000 EURO (500 € * 110 - ALT:Manual outgoing payment PC Gearing-0005) plus 10.450 EURO (19 % VAT) - Select payment method and bank 2.7.1.1.PRC: Invoice verification - Select items to pay - Invoice is checked formally and by content (quantity, unit price, - Calculate pay amount with cash discounts tax) comparing: - Post payment document - Vendor invoice - Print payment medium - Referenced document. It can be: - ALT:Automatic outgoing payment - ALT:Purchase Order: Always settles the whole order, 2.7.4.2.Accounting|FI|Accounts payable|Document entry| irrespective to partial delivery Outgoing|F58 Post+Print Forms - ALT:Delivery Note: 2.7.4.2.1.SCR:Header data - ALT:Goods Receipt: Always settles only that part of the - DDN:Company code = 1000 order what was received on it, quantity cannot be more! - DDN:Payment method = C(Check) - ALT:In case of variance, invoice gets blocked - DDN:House bank = 1000 - ALT:If material is moving average price valued: in material - DDN:Check lot number = 0001 master, moving average price is recalculatedInvoice is re- - DDN:Printer for forms = LOCL(Standard local printer) valued with new price × altered quantity - CHK:Print immediately = True - ALT:If material is standard valuedInvoice is re-valued with 2.7.4.2.1.1.BTN:Enter payments: altered quantity - TBX:Amount = 59500 - ALT:If everything is OK, invoice is posted to SAP FI and CO: - DDN:Vendor = 100268 - Provisional liability stored in Goods Receipt (GR)/Invoice 2.7.4.2.1.2.BTN:Process open items: Receipt (IR) account from issuing goods receipt is cleared - Check open positions list! as 2.7.4.2.1.3.BTN:Save - Invoice Receipt is issued as proof of liability towards - Take note of assigned Payment document ID: 1500000001 vendor 2.7.5.Checking paid items:FBL1N - Vendor account will have a new open item 2.8.Cross-module integration of MM:Procurement - Accounting document is prepared 2.8.1.Financial accounting (FI): Invoice accounting - Purchase Requistion History is updated with invoice document documents: 2.7.1.2.LO|MM|Logistics invoice verification|Document entry| - Account 160000:Reconciliation account for all vendors, paired MIRO Enter Invoice| with that 2.7.1.2.1.SCR:Start: - Sub-ledger creditor accounts are defined for each vendor at - DDN:Company = 1000 vendor master 2.7.1.2.2.SCR:Main: 2.8.2.Sales&Distribution (SD): Sales order 2.7.1.2.2.1.TAB:Basic data: - Can result in purchase requisition if sold finished products and - TBX:Invoice date = Now its parts through BOM ar not in stock - TBX:Posting date = Now 2.8.3.Production Planning(PP): - TBX:Amount = 59500 EUR - Can result purchase requistions if semi-finished goods or raw - CHK:Calculate tax = True material are not in stock - DDN:Tax code = VA(domestic input tax 19%) 2.8.4.Maintenance( MT): 2.7.1.2.2.2.TAB:PO Reference - Goods receipt can contain reference to a BOM: eg. a raw - DDN:Reference document = 1(Purchase order) material is ordered andelivered because BOM of finished - TBX:Reference document number = 4500017337 product requires it - KEY:Enter:amount with tax recomputed correctly - Maintenance can hold back spare parts from these 2.7.1.2.2.3.BTN:Save 2.8.5.Warehouse Management System (WMS) - Take note of assigned Invoice document ID: 5105608892 - While inventory management only contains material type and 2.7.2.MM: Display Invoice Document and Order quantity info History:MIRO - It adds handling and storage place allocation data 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.FI:Check subledger account of vendor:FBL1N 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!
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 12 2.9.Reporting 2.9.2.2.LO|LO controlling|Purchasing information system| 2.9.1.MM:List display:ME2L Standard analyses|MCE3 Vendor| 2.9.1.1.DEF:List dislay tools in SAP: 2.9.2.2.1.SCR:Start - ListView: Character-based table display tool, simple, older - DDN:PurchOrg = 1000 - ALV Grid: Flexible graphic table display with standardized - DDN:Months = 01.2004..Now controls - BTN:Run 2.9.1.2.LO|MM|Purchasing|Purchase order|List display|ME2L By 2.9.2.2.2.SCR:ListView vendor| 2.9.2.2.2.1.COL:Vendor(Characteristics column) 2.9.1.2.1.SCR:Start - Settings|Characteristic display| - DDN:Plant = 1000 - |Key and text:Shows vendor Ids also - DDN:Purchasing organization = 1000 - DobleClick|Change column width:extend column - DDN:Document date = 01.01.2003 .. Now 2.9.2.2.2.2.Edit| - DDN:Scope of list = BEST_ALV:Information structure to show - Choose key figures:select fields to show - BTN:Run 2.9.2.2.2.3.COL:PO Value(Key figure column) 2.9.1.2.2.SCR:ALV Grid - Edit| 2.9.1.2.2.1.Simple operations: Toolbar controls: - ABC-analysis:classifies vendors by: - BTN:Show detail - DDN:Strategy = Total % PO value - BTN:Filter - In 3 categories: - BTN:Short - A = 70%, - BTN:Totals - B = 20%, - BTN:Subtotals - C = 10% - BTN:Change layout - BTN:Graphics:Draws diagram - BTN:Save layout - Record most important vendor: 1235 K.F.W.London 2.9.1.2.2.2.Complex operations: Settings|Layout|Change| 2.9.2.2.2.4.Extras| - TAB:Short order - |Select log: shows which information structures were usied - BTN:Add/Remove field by which reporting operation 2.9.1.2.2.3.BTN:Save - TBX:Name = myLayout-0005 2.9.2.MM:LIS standard analysis:MCE3 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)
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 13 3.Material Planning Scenario - DDN:Reference = Basis-module-0005 3.1.Organizational background 3.3.1.3.2.SCR:Main 3.3.1.3.2.1.BTN:Organization - Same as Procurement scenario - DDN:Plant = 1000 Copy from plant = 1000 - But Production Planning(PP) is in focus - DDN:Storage = 0001 Copy from Storage = 0001 3.2.Plot/Preconditions of Scenario 3.3.1.3.2.2.BTN:Select views: - A lighter version of Speedstar-0005 is defined in Company 1000 - Basic, Sales, MRP, WorkSched, Accounting, Costing Plant 1000 Storage 0001 called Speedstarlett-0005 3.3.1.3.2.3.MM:TAB:Basic1: - It has 1pc of Basis-modul2-0005 - DDN:Description = Basis-modul2-0005 - Which has 1pc of Alu-frame-0005 3.3.1.3.2.4.SD:TAB:Sales general: - Everything will be assembled by work center 1420(Assembly IV) - TBX:Grossweight = 15KG 3.3.Creating/Modifying master data - TBX:Netweight = 13KG 3.3.1.Material master: MM01 3.3.1.3.2.5.FI:TAB:Accounting1: - Some of the iportant views are maintained solely by PP, but - TBX:Standard price = 1500 others are in shared processing 3.3.1.3.2.6.BTN:Save - Some views are general for company, others ar-plant related 3.3.1.4.Create Alu-frame-0005:MMR1 - There are several specialized versions of MM01 to create - LO|MM|Material master|Material|Create(special)|MMR1 Raw certain types of material (eg. FERT, HALB, ROH) with preset of material| the settins below 3.3.1.4.1.SCR:Start 3.3.1.1.Modify Speedstar-0005:MM02 - DDN:Material = Alu-frame-0005 - LO|MM|Material master|Material|MM02 Modify current| - DDN:Industry = Mechanical engineering 3.3.1.1.1.SCR:Start - DDN:Reference = Carb-frame-0005 - DDN:Material = Speedstar-0005 3.3.1.4.2.SCR:Main 3.3.1.1.2.SCR:Main 3.3.1.4.2.1.BTN:Organization - BTN:Organization levels - DDN:Plant = 1000 Copy from plant = 1000 - DDN:Plant = 1000 - DDN:Storage = 0001 Copy from Storage = 0001 - DDN:Storage = 0001 3.3.1.4.2.2.BTN:Select views: - BTN:Select views: - Basic, Purchasing, MRP, WorkSched, Accounting, Costing 3.3.1.1.2.1.PP|Plant:TAB:MRP1 3.3.1.4.2.3.MM:TAB:Basic1: - DDN:MRP type = PD(MRP planning) - DDN:Description = Alu-frame-0005 - ALT: = No planning 3.3.1.4.2.4.FI:TAB:Accounting1: - ALT: = Consumption based - TBX:Standard price = 250 - ALT: = MPS(Master Production Scheduling) 3.3.1.4.2.5.BTN:Save - DDN:Lot size = EX(Exact order quantity) 3.3.2.Bill Of Material (BOM): CS01 - ALT: = Week lots 3.3.2.1.DEF: BOM: 3.3.1.1.2.2.PP|Plant:TAB:MRP2 - Describes list of materials necessary to produce Base quantity - DDN:Procurement type = E(Own production) from a given material - ALT: = F(External) 3.3.2.1.1.BOM content is always single-leveled: - ALT: = X(Both) 3.3.2.1.1.1.Header: contains all general settings: - TBX:In-house production = 5days:Own production, Does not - Described material ID depend on order - BOM usage - ALT: TBX:Planned delivery time = 5days:External, Does - Business applications of BOM not depend on order - Lot size range where BOM valid - TBX:Safety stock = 0:If stock goes under: - Validity dates - ALT:Notification issued - Status of BOM(Planned/Actual/Archuved) - ALT: Planned Production Order issued at ownprod. 3.3.2.1.1.2.Items list: - ALT:Purchase requisition issued at external - ALT: Components: 3.3.1.1.2.3.PP|Plant:TAB:MRP3 - Raw material ID - DDN:Strategy group = 40(Pre-Planning with final assembly) - Description - DDN:Availability check = 02(Individual requirement) - Quantity 3.3.1.2.Create Speedstarlet-0005:MMF1 - Control code - LO|MM|Material master|Material|Create(special)|MMF1 - Item category: Finished product| - Stock items: fix quantity warehoused material 3.3.1.2.1.SCR:Start - Non-stock items: non-warehoused item - DDN:Material = Speedstarlet-0005 - No material master record necessary, instead of that it - DDN:Industry = Mechanical engineering can be stored in material groups - DDN:Reference = Speedstar-0005 - Can be ordered directly to Production Order (PO) 3.3.1.2.2.SCR:Main - eg. Consumable goods 3.3.1.2.2.1.BTN:Organization - Variable size items : their quantity may change with final - DDN:Plant = 1000 Copy from plant = 1000 product size eg. Area of steel plate - DDN:Storage = 0001 Copy from Storage = 0001 - Text items: - DDN:SalesOrg = 1000 Copy from SalesOrg = 1000 - Document items : documentation of manufacturing - DDN:Channel = 10 Copy from Channel = 10 algorithm 3.3.1.2.2.2.BTN:Select views: - Class items: - Basic, Sales, MRP, WorkSched, Accounting, Costing - Intra materials: 3.3.1.2.2.3.MM:TAB:Basic1: - ALT: Assemblies: they are materials composed from - DDN:Description = Speedstarlett-0005 componets according to their own BOM 3.3.1.2.2.4.SD:TAB:Sales general: - So multi-level hierearchy can be built from several - TBX:Grossweight = 20KG interlinked BOMs! - TBX:Netweight = 17KG - We define chain of BOMs always from simplest 3.3.1.2.2.5.FI:TAB:Accounting1: assebly made from raw materials towards finished - TBX:Standard price = 2500 product up! 3.3.1.2.2.6.BTN:Additional data 3.3.2.1.1.3.Alternative items list at multiple BOMs: - DDN:Language = DE - different lot sizes of production may require different material 3.3.1.2.2.7.BTN:Save composition 3.3.1.3.Create Basis-modul2-0005:MMB1 3.3.2.2.Create BOM:Basis-module-0005:CS01 - LO|MM|Material master|Material|Create(special)|MMB1 Semi - LO|PP|Master|BOM|BOM|Material BOM|CS01 Create| finished product| 3.3.2.2.1.SCR:Start 3.3.1.3.1.SCR:Start - DDN:Material = Basis-module-0005 - DDN:Material = Basis-modul2-0005 - DDN:Plant = 1000 - DDN:Industry = Mechanical engineering Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage,Aaa|Bbb|-Menu/Submenu, SCR-Screen, FRM-Frame, ID- UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor 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-frame- 1 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 Gearing- 1 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-frame- 1 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 Gearing- 1 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-module- 1 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 ory ntity 3.3.3.3.Create routing:Basis-modul2-0005:CA01 0010 L(Stock Basis-modul2- 1 - LO|PP|Master|Routing|Routing|Normal routing|CA01 item) 0005 PC Create| 0020 L(Stock Pedal 2 3.3.3.3.1.SCR:Start item) PC - DDN:Material = Basis-modul2-0005 0030 L(Stock Brakes 2 - DDN:Plant = 1000 item) PC - TBX:Key date = 01.01.CurrYear 0040 L(Stock Handlebar 1 3.3.3.3.2.SCR:Head item) PC - BTN:Copy 0050 L(Stock Saddle 1 - Routing = 50001319 item) PC - DDN:Reference material = Basis-module-0005 - BTN:Save 3.3.3.3.2.1.BTN:Save 3.3.2.6.Check multi-level BOM: CS12 - Take note of Routing ID: 50001320 - DEF: Hierachic view of network of interlinked BOMs 3.3.3.4.Create routing:Speedstar-0005:CA01 - LO|PP|Master|BOM|Reporting|BOM Explosion|Material - LO|PP|Master|Routing|Routing|Normal routing|CA01 BOM|SC12 Multi level BOM| Create| 3.3.2.6.1.SCR:Start 3.3.3.4.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, ID- UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 15 - DDN:Plant = 1000 - Occouring at delivery deadline – production time - TBX:Key date = 01.01.CurrYear 3.4.1.3.2.3.Planning strategies: 3.3.3.4.2.SCR:Head - They make balance among stock, production, froecast, - BTN:Copy orders - Routing = 50001319 - Make-to-Stock : - DDN:Reference material = Basis-module-0005 - Can be done with finished product or easy to assemble 3.3.3.4.2.1.BTN:Save subassemblies - Take note of Routing ID: 50001321 - More consistent production capacity usage 3.3.3.5.Create routing:Speedstarlett-0005:CA01 - More expensive inventory - LO|PP|Master|Routing|Routing|Normal routing|CA01 - Make-to-order: Create| - Mainly for finished product 3.3.3.5.1.SCR:Start - Low inventory costs - DDN:Material = Speedstarlett-0005 - Uneven capacity usage - DDN:Plant = 1000 - Planning with final assembly:40 - TBX:Key date = 01.01.CurrYear - Independent requirement is designed as make-to-stock 3.3.3.5.2.SCR:Head - But if sales orders consume all the planned quantity, the - BTN:Copy difference is incorporated in planned independent - Routing = 50001319 requirement of future time periods. How it is done can be - DDN:Reference material = Basis-module-0005 set in Material master or MRP group: 3.3.3.5.2.1.BTN:Save - Consumption periods: by default it is days - Take note of Routing ID: 50001322 - 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 consumption×replenishment 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, ID- UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 16 Newspaper) - Production is computed from sales plan and safety stock - Simple automated ordering 3.4.4.2.Create Plan: MC82 - Higher cost of inventory - LO|PP|SOP|Planning|Product group|MC82 Change| 3.4.1.4.4.MRP Run levels 3.4.4.2.1.SCR:Start - Total for Plant and reevaluates BOMs:NEUPL - DDN:Group = Racing-Bike-0005 - MRP group - DDN:Plant = 1000 - Refined manual selection - BTN:Active version: creates A00(Active) plan - Single Material 3.4.4.2.2.SCR:Create rough plan - For net changes only:NETCH Month No No No No No No - For a given time period (usually 30days):NETPL w+ w+ w+ w+ w+ w+ - Online/Background job 2 3 4 5 6 7 3.4.1.4.5.MRP Outputs Sales 20 15 10 15 20 17 3.4.1.4.5.1.Types: 00 00 00 00 00 50 - Stock/requirement list: TargetDaysSupp 3 3 3 3 3 3 - Dynamic list summing up results from all Stocks, Orders, ly and MRP runs - KEY:Enter: - MRP lists : - LIN:Stock level:calculated automatically with negative - Static list with the results of 1 MRP run quantities - Can contain error list of inconsistencies in BOMs - Edit|Create production plan|Target days supply| 3.4.1.4.5.2.Content: - LIN:Production: calculated automatically (may vary little bit - SCR:Top: Variable header because different lenght of the months) - SCR:Left: Material BOM tree - LIN: Stock level:shifts to positive - SCR:Right: MRP items requirement/stock 3.4.4.2.3.BTN:Save 3.4.1.5.PP/MM:Production/Procurement Execution 3.4.5.Disaggregation of Production Plan: MC75 3.4.1.5.1.MRP Consequence Documents 3.4.5.1.DEF: Disaggregation: 3.4.1.5.1.1.At internal products it creates: - Breaks up aggregate plans to individual products by their - Planned order proportion factor - Production order - Transfers them to demand management as planned - Planned reservation for dependents independent requirement 3.4.1.5.1.2.At external materials it creates: - But no dependent requirements are created - If there is no scheduling agrrement in source list of material: 3.4.5.2.Disaggregate group: Racing-Bike-0005: MC75 - Purchase requisitions: No vendor yet - LO|PP|SOP|Disaggregate|MC75 Transfer Product Group| - Purchase orders: Vendor assigned 3.4.5.2.1.SCR:Start - If there is Scheduling agrrement in Source list of material: - DDN:Product group = Racing bike-0005 - Schedule Line Release - DDN:Plant = 1000 - Schedule Line - DDN:Version = A00 3.4.2.Change material: MM02 - CHK:Prod. plan for mat. as a proportion = True 3.4.2.1.DEF: Consumption setting of material - DDN:From date = Now - Set that Planned orders will consume (will be subtracted from) - CHK:Invisible transfer = False(Show manual override screen) Planned independent requirement: the plan should be reduced, - CHK:Active = True if one part of it becomes actual order - BTN:Transfer now - Set the direction of consumption in time 3.4.5.2.2.SCR:Manual override plan 3.4.2.2.Set consumption: SpeedStar-0005: MM02 - Take note of 5th months production quantity of Speedstar-0005: - LO|PP|Master data|Material master|Material| MM02 Change| 1232 3.4.2.2.1.SCR:Start 3.4.5.2.3.BTN:Save:Speedstar-0005 - DDN:Material = SpeedStar-0005 3.4.5.2.4.BTN:Save:Speedstarlett-0005 - BTN:Organiz 3.4.5.3.Display Stock/Requirements list: SpeedStar-0005: MD04 - Plant = 1000 - LO|PP|MRP|Evaluations|MD04 Stock/Requirements list| - Storage = 0001 3.4.5.3.1.SCR:Start - BTN:View = MRP3 - DDN:Product = SpeedStar-0005 3.4.2.2.2.MM:TAB:MRP3 - DDN:Plant = 1000 - DDN:Consumption mode = 2(Consume) 3.4.5.3.2.SCR:Main - TBX:Backward period = 30 - COL:MRP Element,Reqirement,Available are updated - TBX:Forward period = 30 3.4.5.4.Display Stock/Requirements list: SpeedStarlett-0005: 3.4.2.2.3.BTN:Save MD04 3.4.2.3.Set consumption: SpeedStarlett-0005: MM02 - Same as above - Same as above - Take note of last months unrestriced use stock of Speedstarlett- 3.4.3.Create Product Groups: MC84 0005: -3966 3.4.3.1.DEF: Product Group: 3.4.6.Material Requirement Planning: MD02 - Groups similar products into common maintenance 3.4.6.1.DEF:MRP 3.4.3.2.Create product group: Racing-Bike-0005: MC84 - Create dependent requirement for independent requirement - LO|PP|SOP|Product group|MC84 Create| - After BOM explosion 3.4.3.2.1.SCR:Start 3.4.6.2.MRP Run: SpeedStar-0005: MD02 - DDN:Product Group = Racing-Bike-0005 - LO|PP|MRP|Planning|MD02 Single item, multi level| - TBX:Product Group = Racing-Bicycle-0005 3.4.6.2.1.SCR:Start - DDN:Plant = 1000 - DDN:Material = SpeedStar-0005 - DDN:Unit = PC - DDN:Plant = 1000 - RAD:Members = Material - DDN:Processing key = NETCH(Only net change) 3.4.3.2.2.SCR:Main - DDN:Create purchase req. = 2(In opening period) Material Aggregation Proportio - DDN:Delivery schedules = 3(Apply) but now there isn’t any factor n - DDN:Create MRP list = 1(Create list) SpeedStar-0005 0 60 - DDN:Planning mode = 1(New plan) SpeedStarlett- 0 40 - DDN:Scheduling = 1(Basic dates will be determined) 0005 - CHK:Also plan unchanged components = False 3.4.3.2.3.BTN:Save - CHK:Display results before they are saved = False 3.4.4.Create Sales and Production Plan: MC82 - CHK:Display material list = False 3.4.4.1.DEF: Sales and Production Plan content: - CHK:Simulation mode = False - Aggregated plans for product groups broken up by months - KEY:Enter,Enter - Target Days Supply:How many days production should be kept 3.4.6.2.2.SCR:MRP Summary on safety stock - Dependent components not in stock will generate exceptions
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 17 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.Create Sales Order: VA01 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.Material Requirement Re-Planning: MD02 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
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 18 4.Lifecycle Data management scenario 4.1.4.2.Tools 4.1.DEF: Product Life Cycle Management (PLM) 4.1.4.2.1.Engineering Change Management (ECM) - Enables to store historic steps of content object changes - Manages products and projects lifecycle - Grouped into Change groups described by Change Master - From planning to phase out Record: - Integrated with CRM and SCM - Header - Has limeted activity when product/project is on peak - Change number ID - Consists of following components: - Reason 4.1.1.Integration - Validity dates 4.1.1.1.Content objects handled (Import/export): - Status - CAD systems - Items: Object management records - GIS systems - References of changed objects or extra documents - Office systems - Their change can be effected by: - Classification systems - Validity dates 4.1.1.2.Tools: - Validity conditions - ALT:Remote function call (RFC) of Business Application - Propagates through whole LO process programming Interface (BAPI) 4.1.4.2.2.Engineering Configuration Management - ALT:Java Connector - Configuration Folder: Enables to store cotents assigned to 4.1.1.3.GUI: different replicates of product structure - ALT:Without SAP GUI: uses RFC-base dialog templates - Configuration folders are assigned to product lifecycle phases - ALT:With SAP GUI - For different purposes: engineering/production 4.1.2.Document management 4.1.4.3.GUI 4.1.2.1.Content objects handled: 4.1.4.3.1.Engineering Workbench (EWB) - Paper - Can process BOMs and Routings simultaneously in Worklists - Folder - Multi user environment: does not lock all the BOMs/Routings, - Electronic just that part of hierarchy, which is maintained 4.1.2.2.Tools:Document Info Record: 4.1.4.3.2.Releasing changes has 2 alternative ways: - Document fuction description - ALT: By 1 user in 1 step: Release Change Master Record - Secure Storage Area access - ALT: By multiple user in more steps with status change - Versioning (allocates responsibility and rights): Engineering Change Record - Status (ECR) Engineering Change Order (ECO) - Classification 4.2.Plot of PLM Scenario: - Bidirectional Links with SAP ECC parts: what will use it? - Add SpeedStar-0005 BOM picture BOMSpeedStar- - Bidirectional Links with PLM and ArchiveLink interfaces: how to 0005.JPG as document info record import/export? - Product class Bike-0005 will be defined with 2 characteristics: 4.1.2.3.GUI: - Bike-Type-0005: Possible values: Men,Women 4.1.2.3.1.Easy Document Management System (DMS) interface: - Simplified tool no need to learn SAP GUI - Frame-Type-0005: Possible values: Carbon,Aluminium 4.1.2.3.2.EAI Viewer: - Our finished products will be configurable materials classified - View CAD Animated into Bike-0005 class with characteristic values: 4.1.2.3.3.MS Office: - SpeedStar-0005: - View office documents - Bike-Type-0005 = Men 4.1.2.3.4.WorkFlow: - Frame-Type-0005 = Carbon - Organize documents into process flows - SpeedStarlett-0005: 4.1.3.Product structure browser - Bike-Type-0005 = Women 4.1.3.1.Content object handled: - Frame-Type-0005 = Aluminium - Material masters 4.3.CA:Create document info records - BOM 4.3.1.DEF: Document Info Record - Routings - It connects material with its complex documentation - Documents - Now we will store only BOM in that 4.1.3.2.Tools 4.3.2.Document info record: SpeedStar-0005: CV01N 4.1.3.2.1.Product classification - LO|Central functions|Document management|Document| - Define Attributes/Characteristics: Data fields with given name, CV01N Create| type, range 4.3.2.1.SCR:Start - Define Class Hierarchy: Attribute/Characteristics are assigned - DDN:Material = SpeedStar-0005 for each class - DDN:Document type = DRM - Objects are assigned to class: - DDN:Document part = 000 - Their Attribute/Characteristics values are determined - DDN:Document version = 00 - A material and its document can go in separate classes 4.3.2.2.TAB:Document data 4.1.3.2.2.Variant Configuration for Configurable materials: - TBX:Description = Speedstar-BOM-0005 - Define Attributes/Characteristics: Data fields with given name, - DDN:Lab./Office = KB1 type, range 4.3.2.2.1.FRM:Original - Assign characteristic values to variants of configurable material - BTN:Create new - General BOM and Super routing will contain all possible 4.3.2.2.1.1.SCR:Create doc:Basics components/work steps for all versions - TBX:Log = Document Attachment - Dependencies defined in BOM/Routing by characteristic values 4.3.2.2.1.2.SCR: Create doc:Details store Dynamic BOM/Routing of product versions - DDN:WS-Appl. = JPG - Different type of BOMs can be defined: - TBX:Description = BOM - Production BOM: Normal production - DDN:Data carrier = INTERNET - Order BOM: specific variant assigned to 1 order - TBX:Original = BOMSpeedStar-0005.JPG 4.1.3.3.GUI: 4.3.2.3.BTN:Save - SCR:Left:Product hierarchy - SCR:Right:Component detail 4.1.4.Engineering Change&Configuration Management 4.1.4.1.Content objects handled: - Material master - BOM - Routing - Documents
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 20 5.Manufacturing Execution Scenario - Setup 5.1.Plot of scenario - Processing - Fixed time element 5.1.1.Plot of master data - Variable time element - In routing for SpeedStar-0005, its BOM-components Pedal, - Tear down Brakes, Handlebar, Saddle should be assigned to - HR Position responsible operation 0020 instead of the default 0010, as these - Required qualifications components are needed only at final assembly - Employees assigned 5.1.2.Plot of Production-On-Order Preparation - DEF:Production Resources&Tools (PRT): 5.1.2.1.Product costing: - Material, Equipment, Document - Do product costing, price mark, price release: 5.2.1.1.4.DEF:BOM-Routing assignment: - Basis-Module-0005: 1588EUR - By default BOM components of a material are assigned to 1st - SpeedStar-0005: 2377EUR operation of materials routing - Basis-Modul2-0005: 1088EUR - But this can be changed if components has to arrive Just in - SpeedStarlett-0005: 1877EUR Time (JIT) to a given operation in routing 5.1.2.2. Re-run MRP - Also routed resources can be assigned to a given operation - As routings changed, re-run MRP for SpeedStar-0005 5.2.2.Display Work Center: 1420: CR03 5.1.3.Production Order Process - LO|PP|Master|Work center|Work center|CR03 Display| 5.1.3.1.Production orders 5.2.2.1.SCR:Start - Planned orders of (semi)finished should be converted to - DDN:WorkCenter = 1420 production orders: - DDN:Plant = 1000 - Basis-Module-0005: 1371PC 5.2.2.2.SCR:Main - SpeedStar-0005: 1371PC 5.2.2.2.1.TAB:Basic: 5.1.3.2.Purchase orders - DDN:WorkCenterCategory = 0003(Labor) - Planned orders of raw materials should be converted to 5.2.2.2.2.TAB:Costing: production orders: - DDN:CostCenter = 4210(Motocycle assembly) - Gearing-0005: 1371(for Basis-Module-0005)+914(for Basis- - DDN:ControlingArea = 1000(Europe) Modul2-0005)-100(Already on stock) = 2185PC - FRM:ActivityTypes - Wheel-0005: 2742(for Basis-Module-0005)+1828(for Basis- 5.2.2.2.3.TAB:Capacities: Modul2-0005) = 4570PC - FRM.Capacities - Chain-0005: 1371(for Basis-Module-0005)+914(for Basis- CategoryDescriptionCapacity Formula Modul2-0005) = 2285PC 002 Labor ### BTN:View Form - Carb-Frame-0005: 1371PC(for Basis-Module-0005) Machine 5.1.3.3.Post goods receipts Person - All purchased material arrives on same day to inventory - DDN:FactoryCalendarID = 01(German standard) 5.1.3.4.Goods Issue - LIN:WorkingDay - Issue all components from inventory on same day to - TBX:StartHour = 06.00 manufactoring of: - TBX:EndHour = 22.00 - Basis-Module-0005 5.2.2.2.4.TAB:Default values: - SpeedStar-0005 5.2.2.2.5.TAB:Scheduling : - Manually modify quantity of Breaks from 2742 to 2942PC 5.2.3.Display Routing: SpeedStar-0005: CA02 becasue 200 Breaks destroyed - LO|PP|Master|Routing|Routing|Standard|CA02 Change| 5.1.3.5.Confirm production order 5.2.3.1.SCR:Start - Confirm production orders on same day for: - DDN:Material = SpeedStar-0005 - Basis-Module-0005 - DDN:Plant = 1000 - SpeedStar-0005 5.2.3.2.SCR:Main 5.2.3.2.1.FRM:Head 5.1.4.Production Closing Operations - DDN:Status = 04(Released) 5.2.Modify BOM and Routing master data - DDN:TaskListGroup = 50001321(Purpose of routing) 5.2.1.Processed data structures - TBX:GroupCounter = 1(Unique ID of routing inside group) 5.2.1.1.1.Material master - TBX:LotSizeRange = 0 - 99.999.999 (Lot size range in which - Material ID current routing is valid, operation sequence may depend on lot - Measure unit size) 5.2.1.1.2.BOM - BTN:Sequences 5.2.1.1.2.1.Header 5.2.3.2.2.SCR:Sequence types: - For Material ID - LIN:Standard - BOM type:Production/Order - BTN:Operation 5.2.1.1.2.2.Item 5.2.3.2.3.SCR:Standard sequence operations: - Type:Material/Document 5.2.3.2.3.1.LIN:0010|Detail|Operation| - Material ID - TBX:BaseQuantity = 1 - Quantity - DDN:UnitOfMeasure = PC 5.2.1.1.3.DEF:Task lists: - FRM:Standard values 5.2.1.1.3.1.ALT:Rate routings - LIN:Personell time 5.2.1.1.3.2.ALT:Master recipe - TBX:BaseQuantity = 45 5.2.1.1.3.3.ALT:Equipment task list - DDN:UnitOfMeasure = MIN 5.2.1.1.3.4.ALT:Inspection plan 5.2.3.2.4.BTN:CompAlloc|SCR:ComponentAssignment 5.2.1.1.3.5.ALT:Routing groups|Routings: - LIN:Pedal, Breaks, Handlebar, Saddle select - Head - BTN:New assignment|SCR:New assignment| - For Material ID - DDN:Operation = 0020 - Standard/alternative sequences: 5.2.3.2.5.BTN:Save - 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:
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 21 5.3.Production-On-Order Preparation - Material 5.3.1.DEF: Production types - Accounting 5.3.1.1.ALT:Order controlled - Cost accounting - It needs Sales Order 5.3.2.9.Auto:Material withdrawal posting 5.3.1.1.1.1.ALT: With Production Order 5.3.2.10.Upload from PDC system - Involves manufacturing Lots: series of fully identical products 5.3.2.11.Auto:Confirmatioon 5.3.1.1.1.2.ALT: With Process Order 5.3.2.11.1.ALT:Order related - Involves continous manufacturing process, eg. Chemicals 5.3.2.11.2.ALT:Operation related 5.3.1.2.ALT:Repetitive manufacturing - ALT:Time ticket - No order related - ALT:Collective - Assembly line - ALT:Milestone 5.3.1.3.ALT:Project - ALT:Progress - Given unique featured lot - ALT:Time event - Completed on given deadline 5.3.2.12.Work-in-Process (WIP) determination 5.3.1.4.ALT:Kanban 5.3.2.13.Auto:Movement:101 Goods receipt - Procurement driven - Issue documents - Self controlled cycles of - Material - Unique identified kanban-containers - Accounting - Alternating between full/empty states - Cost accounting - Carrying given lots - Print Goods Issue Document - Involves: - Delivered quantity updated - External procurement - Receipt evaluated, credit amount is added to orders credit - In-house production - Results in Stock Receipt - Stock transfer among storage 5.3.2.14.Variance calculation 5.3.2.15.Order settlement, Cost Debit/Credit 5.3.2.PROC:Production on Order 5.3.2.15.1.Result 5.3.2.1.Production Order request - Production order is a Cost object in Cost Object Controlling 5.3.2.2.Production Order creation (COC) 5.3.2.2.1.Ways - After settlement cost is allocated to General Ledger Accounts - ALT:Without routing and BOM manually and it will be no more cost object, can be closed - ALT:With routing only 5.3.2.15.2.Types - ALT:With routing and BOM 5.3.2.15.2.1.ALT:Order related - ALT:With planned order - Flexible manufacturing of valuable complex products 5.3.2.2.2.Production Order Content 5.3.2.15.2.2.ALT:Product related 5.3.2.2.2.1.Head 5.3.2.15.3.Controled by Settlement Profile - Status:CreatedReleased - Settlement period - Type:PP01/.. - Price control - Cost summary - Settlement receiver(s) and their account(s) - Cost settlement rule in Cost Object Controlling (COC) - Distribution rules - Links to Document Management System (DMS) - Plant activity accounts 5.3.2.2.2.2.Items - Difference account - Standard/parallel/alternate operation sequences - Settlement parameters - Operations: tehre should be at least 1 routing operation 5.3.2.16.Archive/delete - Material BOM components: by default all components of BOM are attached to first operation 5.3.3.CO:Product Costing - PRTs 5.3.3.1.DEF:Product Costing Data Structure - Trigger Points 5.3.3.1.1.DEF:Standard price: - Confirmations - Cost estimate in material master - Work centers - Of a material purchased/produced in one time - Cost calculation 5.3.3.1.2.DEF:Moving average price: - Capacity splits - Lot size-weighted moving average cost - Persons - Of a material purchased/produced in more lots in time - Machinery 5.3.3.1.3.DEF:Planned price: 5.3.2.3.Availability check - Material/Manufacturing cost of (semi)finished product Cost 5.3.2.3.1.ALT:Manual: objects - If OrderType = PP01 - Calculated by Cost Object Controlling (COC) Product costing 5.3.2.3.2.ALT:Auto 5.3.3.1.3.1.Data sources: 5.3.2.4.Machine reservation - BOM: 5.3.2.5.Order release - Standard material prices 5.3.2.5.1.Scope - Moving material prices - ALT:Single order - Routing|Operations|Workstations: - ALT:Mass release - Setup/machine/labour cost 5.3.2.5.2.Source data - Based on the utilized activity types: - BOM - Tariffs - Routing - Standard quantities - Work center capacity scheduling 5.3.3.1.3.2.PROC: 5.3.2.5.3.Launch - Always goes upward in BOM/Routing hierarchy from simplest - ALT:Auto semifinished product towards finished product - 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
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 23 5.4.3.PP:Create Production Order (Semi-Finished):Basis- finished product Module-0005 1371PC:MD04 - DDN:DelivNote = * - LO|PP|MRP|Eavuation|MD04 Stock/Req list| 5.4.9.1.2.FRM:Item detail 5.4.3.1.SCR:Start - CHK:ItemOk = True - DDN:Material = Basis-Module-0005 - TAB:Where - DDN:Plant = 1000 - DDN:Storage = 0001 5.4.3.2.SCR:Main 5.4.9.1.3.BTN:Save - LIN:PlOrd:Basis-Module-0005 1370PC|DoubleClick| - Take note of goods receipt number: 5000012423 - SCR:Additional data of MRP element 5.4.10.MM:Post Goods Receipt: Wheel-0005:MIGO - BTN:Prod.Order|SCR:New Production Order (Ignore - Take note of goods receipt number: 5000012424 document not valid warning!) 5.4.11.MM:Post Goods Receipt: Chain-0005:MIGO - BTN:Material|SCR:Availability check - Take note of goods receipt number: 5000012425 - BTN:Missing parts|SCR:Missing Parts Overview 5.4.12.MM:Post Goods Receipt: Carb-Frame-0005:MIGO - BTN: Components:Auto-ordered dependent compo- - Take note of goods receipt number: 5000012426 nents by BOM can be seen: they will change from 5.4.13.MM:Goods Issue: Basis-Module-0005: MB1A Dependent requirement Reserved Order - LO|MM|Inventory|Goodsmovement|MB1A Goods issue| - BTN: Operations:Auto-ordered operations by routing 5.4.13.1.SCR:Start can be seen (The last has to have StadardKey = P00005 - BTN:To order to initiate auto-goods issue) - DDN:OrderNum = 60003525 (Basis-Module-0005) - BTN: Release:Status shifts from CRTD REL 5.4.13.2.SCR:Main - BTN:Save, Take note of prod.order number:60003525 - FRM:Items:Check that all components issued from inventory - BTN:Update:MRP element shifts from LIN:PlOrd 5.4.13.3.BTN:Save - LIN:ProdOrd Basis-Module-0005 1370PC - Take note of document number: 4900038401 5.4.4.PP:Create Production Order (Finished):SpeedStar- 5.4.14.PP:Confirm production order: Basis-Module-0005: 0005 1371PC:MD04 CO15 - Same as above, Take note of prod.order number:60003526 - LO|PP|Production control|Confirmation|Enter|CO15 For 5.4.5.MM:Create Purchase Order (RawMat):Gearing-0005 order| 2185PC:MD04 5.4.14.1.SCR:Start - LO|PP|MRP|Eavuation|MD04 Stock/Req list| - DDN:OrderNum = 60003525 (Basis-Module-0005) 5.4.5.1.SCR:Start - RAD:Final Confirmation = True - DDN:Material = Gearing-0005 5.4.14.2.SCR:Main - DDN:Plant = 1000 - Check goods movement list: it will show only Basis-Module- 5.4.5.2.SCR:Main 0005, but as this finishes with PP03 Milestone type operation: - LIN:PlOrd:Gearing-0005 2185PC|DoubleClick| - All components will be auto-confirmed - SCR:Additional data of MRP element - Their warehouse goods receipt will be auto-issued - BTN:Purch.Req.|SCR:New Purchase Requisition 5.4.14.3.BTN:Save - TBX:Converted Quantity = 2185 (In case of numeric 5.4.15.MM:Check production confirmation: Basis-Module- diference, its possible to manually override quantity 0005:MD04 here!) - LO|PP|MRP|Evaluation|MD04 Stock/Req list| - BTN:Save, Take note of purch.req number: 5.4.15.1.SCR:Start 1001389000010 - DDN:Material = Basis-Module-0005 - BTN:Update:MRP element shifts from LIN:PlOrd - DDN:Plant = 1000 - LIN:PurchReq Gearing-0005 2185PC|DoubleClick| 5.4.15.2.SCR:Main - SCR:Additional data of MRP element - LIN:OrdRes, Basis-Module-0005, Demand=1371, - BTN:Purch.Ord.|SCR:New Purchase Order Available=1371(Should be equal!) - FRM:Left - LIN:Components:available stock should be reduced - LIN:All open purchase requisitions select - BTN:Copy(copies them to a purchase order) 5.4.16.MM:Goods Issue: SpeedStar-0005: MB1A - FRM:Right:Observe order Header|Item|Item detail - Manually modify quantity of Breaks from 2742 to 2942PC - BTN:Save, Take note of purch.ord number: becasue 200 Breaks destroyed 4500017392 - Take note of document number: 4900038403 - BTN:Update:MRP element shifts from LIN:PurchReq 5.4.17.PP:Confirm production order: SpeedStar -0005: - LIN:PurchOrd Gearing-0005 2185PC CO15 5.4.6.MM:Create Purchase Order (RawMat):Wheel-0005 5.4.18.MM:Check production confirmation: SpeedStar 4570PC:MD04 -0005:MD04 - 4386PC, Take note of purch.req number: 1001389100010 - Take note of purch.ord number: 4500017393 5.4.7.MM:Create Purchase Order (RawMat):Chain-0005 2285PC:MD04 - 2193PC, Take note of purch.req number: 1001389200010 - Take note of purch.ord number: 4500017394 5.4.8.MM:Create Purchase Order (RawMat):Carb-Frame- 0005 1371PC:MD04 - 1370PC, Take note of purch.req number: 1001389300010 - Take note of purch.ord number: 4500017395 5.4.9.MM:Post Goods Receipt: Gearing-0005:MIGO - 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, ID- UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 24 5.5.Production Closing Operations Individal processing| 5.5.1.MM:Check Goods Movement Documents: 5.5.4.2.SCR:Start - DDN:ControllingArea = 1000 SpeedStar-0005: MB51 - DDN:Order = 60003526 (Speedstar-0005) - LO|MM|Inventory|Environment|List displays|MB51 Material docs| - DDN:Period = Current month 5.5.1.1.SCR:Start - DDN:Fiscal year = Current year - DDN:Material = SpeedStar-0005 - DDN:ProcessType = Auto - DDN:Plant = 1000 - CHK:Test run = False 5.5.1.2.SCR:Material document list - BTN:Run 5.5.1.2.1.FRM:Head 5.5.4.3.SCR:List - LIN: SpeedStar-0005, Take note of document number: 5.5.4.3.1.BTN:Column selector 4900038404 |DoubleClick| 5.5.4.3.1.1.SCR:Detailed list: - BTN:Sender:Observe senders 5.5.1.2.2.FRM:Item detail - BTN:Receiver:Observe receivers 5.5.1.2.2.1.TAB:DocInfo - BTN:FI Documents 5.5.5.PP:Order Completion and Closing: SpeedStar-0005: - LIN:Costing document| CO02 - Observe actual costing = 2377EUR 5.5.5.1.DEF:OrderStatus = TECO(Technical completion) - LIN:Accounting document| - Staus takes out order from MRP, but not dlete it - Observe actual stock value = 1371PC × 2377EUR - However, all its dependents documents are deleted 5.5.2.PP:Variance and cost analysis: SpeedStar-0005: - Order reservations - Capacity requistions CO03 - Purchase requistions - LO|PP|Prod control|Order|CO03 Display| 5.5.5.2.DEF:OrderStatus = CLSD(Closed) 5.5.2.1.SCR:Start 5.5.5.2.1.Prerequisites: - DDN:ProdOrder = 60003526 ( SpeedStar-0005) - Order status: CRT REL TECO 5.5.2.2.SCR:Production order header - Balance is 0 5.5.2.2.1.BTN:Components - No open dependent documents: purch req. 5.5.2.2.1.1.LIN:Breaks 5.5.5.2.2.Properties: - Component|Component details| - Cannot be changed together with all existing dependents - TBX:Requirement quantity = 2742 - LO|PP|Prod contr|Order|CO02 Change| - TBX:With drawal quantity = 2942 (Observe difference!) 5.5.5.3.SCR:Start 5.5.2.2.2.BTN:Operations - DDN:Order = 60003526 (Speedstar-0005) 5.5.2.2.2.1.LIN:0010 5.5.5.4.SCR:Main - Operation|Operation details| 5.5.5.4.1.Goto|Costs|Analysis|SCR:Target/Actual comparison| - TAB:Quantities/Activities - TBX:Confirmed yield = 1371 Cost PlannedActualVariance - TBX:Opertaion quant = 1371(Should be equal!) Material 5.5.2.2.3.Goto|Cost|Analysis|SCR:Target/Actual comparison| Goods Issue Cost Planned Actual Variance Operations Material Setup Goods Issue Machine Labor Operations Setup Total 9,905- 0- 9,905 Machine 5.5.5.4.2.Functions|Restrict processing| Labor 5.5.5.4.2.1.|Complete technically Total 3,249,976- 19,862- 3,230,113- 5.5.5.4.2.2.|Close 5.5.5.5.BTN:Save 5.5.2.2.4.Header|Settlement rule| 5.5.2.2.4.1.LIN:SpeedStar-0005 5.6.Order Information System - Cat = Mat(Costs are debited on material) 5.6.1.PP:Production Order Report: SpeedStar-0005: - Price control = COOIS - V:Cost variation is spread over entire stock with moving - LO|PP|Shop floor control|Information system|COOIS Order average information system| - S:Cost variation is incorporated only in current standard 5.6.1.1.SCR:Start price - DDN:List = PPIOH000(Order Headers) 5.5.3.FI:Period end summary of cost variances by - DDN:Layout = 000000000001(Standard layout) category: SpeedStar-0005: KKS2 - DDN:Material = SpeedStar-0005 - LO|PP|Prod contr|Period end closing|Variations|KKS2 - DDN:Production Plant = 1000 Individal processing| - CHK:Plnnd orders = True 5.5.3.1.SCR:Start - BTN:Run - DDN:ControllingArea = 1000 5.6.1.2.SCR:ALV Grid - DDN:Order = 60003526(Speedstar-0005) - Realign columns: Material number, Material description - DDN:Period = Current month - BTN:Sum:Add Sum to column Target quantity - DDN:Fiscal year = Current year - BTN:SaveLayout - CHK:Selected Target Cost Version 000 = True - TBX:Save layout = Manu-0005 - CHK:Test run = False - TBX:Name = Manufacturing 0005 Layout - CHK:Detail list = True - CHK:User-specific = 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.PP:Order Settlement: SpeedStar-0005: KO88 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 Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage,Aaa|Bbb|-Menu/Submenu, SCR-Screen, FRM-Frame, ID- UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 25 6.Warehouse Management Scenario 6.2.3.2.1.3.ALT:Inter-Company Stock to Stock 6.1.Plot of Scenario - Same as above - Just 2 accounting documents are created: 6.1.1.MM:Material master: - Issuing Company’s G/L account: - Create material SpeedStar-0005 at new organizational level: - Offset entry - Plant = 1200(Dresden) - Moving stock valuated - Storage location = 0140 - Receiving Company’s G/L account - Warehouse number = 140 6.2.3.2.1.4.ALT:Without Stock Transport Order - Storage type = 002 - Manual handling 6.1.2.LO:Warehouse management: 6.2.3.2.1.5.ALT:With Stock Transport Order - Make stock transfer order 1000PC of SpeedStar-0005 To: - Provides integrated handling: - Plant = 1200(Dresden) - Can be auto-created from Purchase Orders - Storage location = 0140 - Can store carrier and freight cost data - Warehouse number = 140 - Goods receipt can be directed to - Storage type = 002 - Warehouse:(Unrestricted/QualInsp/Blocked) - From: - Directly for Consumption - Plant = 1000(Hamburg) - Creates Order history entry - Storage location = 0001 - Has separate control codes: - Warehouse number = 001 - 351:UnrestrictedInTransfer with Transport order 6.1.3.LO:Physical inventory management - 101:InTransfer Unrestricted/QualInsp/Blocked with - Perform PI for material SpeedStar-0005, Plant1000, Transport order Storage0001: 6.2.3.2.2.ALT:Transfer posting - Minus 21 difference (350 instead 371) found, post it - Results in change of Stock ID, Stock Category, - Set cycle counting for all FERT materials at Plant 1000 based - But does not necessarily involves physical movement on consumption from 2004 6.2.3.2.2.1.Material to Material 6.2.DEF:Goods Movements 6.2.3.2.2.2.Blocked Quality inspection Unrestricted 6.2.1.DEF:Goods receipt 6.2.3.2.2.3.Consigment to Warehouse - Increase of warehouse stock from vendor, production, stock 6.3.DEF:Organizational hierarchy transfer 6.3.1.Client 6.2.2.DEF:Goods issue 6.3.1.1.Company - Decrease of warehouse stock to customer, production, stock 6.3.1.1.1.DEF:Transportation planning point: transfer - Settlement of transportation costs/profits 6.2.3.DEF:Inter Stock Transfer - Can be assigned only one company - Transferring stock from one storage to another 6.3.1.1.1.1.DEF:Shipping point: 6.2.3.1.PROC: - Can serve multiple plants 6.2.3.1.1.ALT:Single step 6.3.1.1.1.2.Plant: - Two documents created simultaneously - Can have multiple shipping points and 6.2.3.1.1.1.Goods Issue - DEF:Storage: 6.2.3.1.1.2.Goods Receipt - Site of quantitative inventory management 6.2.3.1.2.ALT:Two step - Assigned to one plant - Two documents created separately - Can be assigned to maximum one warehouse, but it is not 6.2.3.1.2.1.Goods Issue compulsory to assign any - Creates accounting document, stock is valuated at issuing 6.3.1.1.2.DEF:Warehouse: storage - PK: Warehouse Number 6.2.3.1.2.2.Stock is „In transfer” status - Can be assigned to multiple Plant|Shipping point|Strorage - Cannot be opened at Inventory Times, as this cannot be combination accounted there 6.3.1.1.2.1.DEF:Storage type:(Goods receipt/issue) 6.2.3.1.2.3.Goods Receipt - DEF:Storage area 6.2.3.2.Types: - DEF:Picking area 6.2.3.2.1.ALT:Stock Transfer - DEF:Storage section - Always involves physical movement - DEF:Storage bin: Form master dat recors 6.2.3.2.1.1.ALT:Intra-Plant Stock to Stock 6.4.DEF:LO:Logistics Execution process, Warehouse Mngmt. - One step - Connects MM and SD in LO module - 2 documents simultaneously 6.4.1.Goods Receipt - Goods issue document 6.4.1.1.ALT: Initiated by Delivery - Goods receipt document 6.4.1.1.1.Purchase order - No accounting document, except material valuation changes 6.4.1.1.2.Inbound delivery - Can transfer all Stock categories: 6.4.1.1.3.Putaway with transfer order - 311:UnrestrictedUnrestricted 6.4.1.1.4.Confirm transfer order - 323:QualInspQualInsp 6.4.1.1.5.Goods receipt posting - 325:RestrictedRestricted 6.4.1.2.ALT: Initiated by Document Posting - 321: QualInspUnrestricted 6.4.1.2.1.Goods receipt posting - 349: RestrictedQualInsp - Examines whether Plant|Shipping point|Storage combination 6.2.3.2.1.2.ALT:Inter-Plant Stock to Stock is assigned to warehouse. If yes, then: - Two step 6.4.1.2.2.Transfer Requirement - 2 documents separately - Material is placed in goods receiving area of warehouse with - Goods issue document: Removal from storage registered Quant quantity - Transfers stock into receiving location 6.4.1.2.3.Putaway with Transfer order - But „in transfer” status - Destination Storage type|Area|Section|Bin is determined - Creates 1 accounting document if 2 plants are not in the 6.4.1.2.4.Confirm transfer order same valuation area:Moving stock is valuated at the 6.4.2.Goods Issue price of issuing storage 6.4.2.1.ALT: Initiated by Delivery - Goods receipt document: Putaway/Placement in storage 6.4.2.1.1.Sales order - At receiving location changes in transfer status to 6.4.2.1.2.Outbound delivery unrestricted usage 6.4.2.1.3.Picking with transfer order - Does not create accounting document 6.4.2.1.4.Confirm transfer order - Can transfer only unrestriced stock throgh in transfer state: 6.4.2.1.5.Goods issue posting - 303:UnrestrictedInTransfer 6.4.2.2.ALT: Initiated by Document Posting - 305:InTransferUnrestricted 6.4.2.2.1.Goods issue posting - 301:UnrestrictedUnrestricted 6.4.2.2.2.Transfer Requirement Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage,Aaa|Bbb|-Menu/Submenu, SCR-Screen, FRM-Frame, ID- UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 26 6.4.2.2.3.Picking with transfer order - CHK:ItemOK = True 6.4.2.2.4.Confirm transfer order 6.6.3.1.2.BTN:Save 6.5.MM:Maintain master data - Take note of material document number: 4900038468 6.5.1.MM:Extend material master to new plant:Speedstar- - 371PC will stay unrestricted stock in Plant 1000 0005 Plant1200:MM01 - 1000PC will be stock on order in Plant 1200 - LO|MM|Master|Material|Material|Create|MM01 6.6.4.LO:Display material document:4900038468:MB03 6.5.1.1.SCR:Start - LO|MM|Inventory|material doc|MB03 Display - DDN:Material = SpeedStar-0005 6.6.4.1.SCR:Start - DDN:Sector = Mechanical engineering - DDN:Material doc number = 4900038468 - DDN:Type = FERT(Finished product) - DDN:Year = Current - DDN:Copy from = SpeedStar-0005 6.6.4.2.SCR:Main - BTN:SalesOrg: Item Material PlantStorageMovCodeSign - FRM:Organizational level 01 SpeedStar-0005 1000 0001 351 - - DDN:plant = 1200(Dresden) 02 SpeedStar-0005 1200 351 + - DDN:storage location = 0140 6.6.4.2.1.BTN:Accounting documents - DDN:warehouse number = 140 6.6.4.2.1.1.SCR:List documents in accounting - DDN:storage type = 002 - LIN:Accounting document|DoubleClick - FRM:Copy from AccountAmount - DDN:plant = 1000(Hamburg) 792000 2.377.740,00- - DDN:storage location = 0001 792000 2.377.740,00 - DDN:warehouse number = 001 6.6.5.LO:Display material document: 4900038468: MIGO - BTN:Views: General plant1-2, Warehouse1-2, Accounting1 - LO|MM|Inventory|Goods movement|Goods receipt|For 6.5.1.2.SCR:Main purchase order|MIGO PO number known 6.5.1.2.1.TAB:General plant1: 6.6.5.1.SCR:Main - KEY:Enter to copy - DDN:Document = Display 6.5.1.2.2.TAB:General plant2: - DDN:Reason = Material document - KEY:Enter to copy - DDN:Document number = 4900038468 6.5.1.2.3.TAB:Warehouse1: 6.6.5.1.1.FRM:Item - KEY:Enter to copy 6.6.5.1.1.1.TAB:Transfer posting 6.5.1.2.4.TAB:Warehouse2: - FRM:Destination - KEY:Enter to copy - BTN:View|SCR:Item detail screen 6.5.1.2.5.TAB:Accounting1: - LIN: 0140 LE Dresden|BTN:Detailed Display - KEY:Enter to copy - Take note of on-order stock quantity: 1000 6.5.1.2.6.BTN:Save 6.6.LO:Warehouse management 6.6.6.LO:Post Goods Receipt: SpeedStar-0005: Plant1200, 6.6.1.LO:Display stock overview: SpeedStar-0005: MMBE Storage0140, 1000PC: MIGO 6.6.6.1.SCR:Main - LO|LO Ex|Inernal Warehouse Proc|Bins and Stock|Display| - DDN:Document = Goods receipt MMBE Total stock per material - DDN:Reason = Purchase order 6.6.1.1.SCR:Start - DDN:Stock transport order number = 4500017440 - DDN:Material = SpeedStar-0005 - DDN:Plant = Empty! - DDN:Plant = 1000 – 1200 6.6.6.1.1.FRM:Head 6.6.1.2.SCR:Main - TBX:Delivery note = * - SpeedStar-0005 6.6.6.1.2.FRM:item detail - Hamburg 6.6.6.1.2.1.TAB:Material - 1371PC - DDN:Material = SpeedStar-0005 6.6.2.LO:Create stock transport order: SpeedStar-0005: 6.6.6.1.2.2.TAB:Quantity 1000PC: ME21N - TBX:Quantity = 1000 - LO|MM|Purchase|Purchase Order|Create|ME21N 6.6.6.1.2.3.TAB:Where Vendor/Plant known - DDN:Plant = 1200 6.6.2.1.SCR:Main - DDN:Storage = 0140 - DDN:Document = GST(GTS Stock Transf Ord) - CHK:ItemOK = True - DDN:Suppl Plant = 1000 6.6.6.1.3.BTN:Save 6.6.2.1.1.FRM:Head - Take note of material document number2: 5000012473 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
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 27 6.6.7.LO:Display Accounting Document:5000012473: - Storage bin/Material group MB03 - Batch - LO|MM|Inventory|material doc|MB03 Display 6.7.2.1.2.Content 6.6.7.1.SCR:Start 6.7.2.1.2.1.Header - DDN:Material doc number = 5000012473 - PK: PI Document number - DDN:Year = Current - FK: PI Number:groups PI documents in processing groups 6.6.7.2.SCR:Main - Status:(Preprocess,Count,Post,Recount) 6.6.7.2.1.BTN:Accounting documents - Planned count date - No accounting doc here, as this is the recieving side! - Deleted flag - Posting block indicator: 6.6.8.LO:Display target storage type and transfer req. - Block stock any direction transfer of material in SMU number:5000012473: MIGO - Updating Material master|Storage location|Block = 6.6.8.1.SCR:Main X(Blocked by PI) - DDN:Document = Display - Freeze book inventory flag: - DDN:Reason = Material document - If full blocking is not feasible for the material during recount - DDN:Document number = 5000012473 (eg. Production needs it continously) - DDN:Plant = Empty! - It freezes book inventory for a time period, collecting 6.6.8.1.1.FRM:item detail changes in the meantime separately 6.6.8.1.1.1.TAB:WM(Warehouse management) - Then at the end it summarizes differences - Take note of storage type1: 902(GR Area External 6.7.2.1.2.2.Items Receipts) - Stock type - Take note of TR number: 12 - Material 6.6.9.LO:Convert Transfer req. into Transfer order - Batch (Putaway): 12: LB11 - Quantity - LO|LO Exec|Inbound proc|Goods receipt|Putaway|Create - Status:(Preprocess,Count,Post,Recount) transfer order|LB11 For material - Deleted flag 6.6.9.1.SCR:Start 6.7.2.2.Enter count results - DDN:Warehouse number = 140 - Can be done with or without reference to PI document - DDN:Material = SpeedStar-0005 - Variance % can be set for automatic difference warning - DDN:Plant = Empty! - Zero count can be set: default value of uncounted items 6.6.9.2.SCR:Main - Differences from book inventory balances are computed at - LIN: TR Number = 12|Select saving - BTN:TO in Foreground|SCR:Create TR and TO: - List of differences is a report of - Edit|Putaway|Background| Item×(counted,book,difference)×( quantity,value) with the - SCR:Prepare for putaway following functions: - LIN:10 - Display PI document - Take note of new storage type: 002 - Re-count PI Document|Item at important SMUs - Take note of storage bin: 01-03-02 - Post PI Document 6.6.9.2.1.BTN:Save 6.7.2.3.Post inventory differences - Take note of transfer order number: 0000000012 6.7.2.3.1.Create material document 6.6.10.LO:Check total stock: SpeedStar-0005, - Update stock quantity - Update stock value Warehouse0140: LS26 - Reason of difference:(Theft, etc.) - LO|LO Exec|Internal Warehouse Proc|Storage and Bin| - Inventory tolerance group of user Display|LS26 Total stock per material - Document tolerance: exceeding blocks all posting activity of 6.6.10.1.SCR:Start user - DDN:Warehouse = 140 - Item tolerance: exceeding blocks only posting current - DDN:Material = SpeedStar-0005 document 6.6.10.2.SCR:Main 6.7.2.3.2.Create accounting document - Take note of putaway type: 002 - Update stock G/L accounts - Take note of pick type: 902 - Posting date is automatically set to Counting date (Back-posting 6.6.11.LO:Confirm transfer order: 0000000012: LT12 should be allowed in customizing) - LO|LO Exec|Inbound Proc|Goods receipt|Putaway|Confirm - All posting should be within the current fiscal year + 1 months transfer order|Single document|LT12 In one step tolerance 6.6.11.1.SCR:Start 6.7.3.PROC:Cycle Counting - DDN:Transfer order number = 0000000012 6.7.3.1.Determine Cycle Count Indicator (CCI) of materials - DDN:Warehouse number = 140 - Time period to launch periodic PIs 6.6.11.2.SCR:Main 6.7.3.1.1.ALT:ABC analysis 6.6.11.2.1.BTN:Save - More frequently consumed materials in consumption frequency - Plant 1000 Hamburg: 371PC SpeedStar-0005 Unrestricted distribution of historic data at storage will get more frequent stock inventory - Plant 1200 Dresden: 1000PC SpeedStar-0005 Unrestricted 6.7.3.1.2.ALT:Actual consumption analysis stock, type 002 - The same, from actual consumption data of material master 6.7.Physical inventory management 6.7.3.1.3.ALT:Requirement analysis 6.7.1.DEF:Stock Management Unit (SMU) - Use all planned MRP items data for analysis - Indivisible part of material inventory 6.7.3.1.4.ALT:Manual set - Separate inventory item in bookkeeping - Overrides automatic settings - Their inventory differences are posted to: 6.7.3.2.Launch Periodic PIs: - MRP: Modify planning - For all materials, date of last inventory is stored - Accounting: Correct value of Current assets - PI Documents are created by batch input session taking in 6.7.2.PROC: Physical inventory (PI) consideration cycle lenght and last inventory date of materials 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
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 28 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 6.7.5.MM:Carry out PI Count:100001240:MI04 - 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.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 6.7.7.MM:Display PI Doc/statistics:100001240:MI03 - 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.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
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 30 7.3.4.SD:Display Customer Master:50005:XD03 - 01:Daily check - LO|SD|Master data|Business parners|Customer|Display| - 02:Individual reqirement: recommended for finished products XD03 Complete 7.4.1.3.2.Scope 7.3.4.1.SCR:Start - Current stock - DDN:Customer = 50005 - Available To Promise (ATP) - DDN:Company = 1000 7.4.1.4.MRP - DDN:Sales organization = 1000 - Material Availability Date = Loading Date – Max(Pick/Pack - DDN:Distribution channel = 12 Time, Transp.Lead Time) - DDN:Division = 00 7.4.1.5.Procurement 7.3.4.2.SCR:Main 7.4.1.5.1.ALT:Production 7.3.4.2.1.BTN:Sales area data - Production Order Datei = Material Availability Datej – 7.3.4.2.1.1.TAB:Sales Production Timei - Take note of code and function of customer group: Empty, - Where: i, j = 1..m – components, j-main component, i-sub Identifies a particular group of customers component for the purpose of pricing or generating 7.4.1.5.2.ALT:Purchasing statistics - Purchase Order Datei = Material Availability Datej – Inbound 7.3.4.2.1.2.TAB:Billing documents Delivery Timei - Take note of code and function of terms of paymt: Sets - Where: i, j = 1..m – components, j-main component, i-sub cash discount and payment periods component 0001,Payable immediately due net 7.4.1.6.Shipping 7.3.4.2.2.BTN:Company code data - Transport Plan Date = Loading Date – Transp.Lead Time 7.3.4.2.2.1.TAB:Account management - Loading Date = Goods Issue Date – Loading Time - Take note of code and function of reconciliation account: - Goods Issue Date = Required Delivery Date – Transit Time account which is updated parallel to the - Required Delivery Date subledger account for normal postings, 140000 7.4.1.7.Billing 7.4.1.8.Payment 7.3.5.SD:Create Product-specific condition:SpeedStarlett- 7.4.2.DEF:Sales Order Document Flow by Milestones 0005:MM02 - All documents have header and item parts - LO|SD|Master data|Products|Material|Other|MM02 Change - They inherit data from each other through the process 7.3.5.1.SCR:Start - One ascendant document can have multiple descendants (eg. 1 - DDN:Material = SpeedStarlett-0005 sales order can generate more deliveries) formin a document - BTN:OrgLevel|SCR:OrgLevel hierarchy - DDN:Plant = 1000 7.4.2.1.Optional pre-sales documents - DDN:SalesOrg = 1000 - Contact - DDN:Channel = 10 Valid only for this channel! - Inquiry - BTN:View = SalesOrg1 - Quotation 7.3.5.2.SCR:Main - Contract 7.3.5.2.1.TAB:SalesOrg1 - Sceduling Agreement - DDN:Division = 00 7.4.2.2.Sales Order 7.3.5.2.1.1.BTN:Conditions|SCR:Condition PR00 7.4.2.2.1.Header - DDN:Valid from = Now - Reference to ascendent pre-salesdocument - DDN:Valid to = 31.12.9999 - Sales area - FRM:Scales - Customer Master QuantAmount - Shipping 1 2500 - Billing 500 2300 7.4.2.2.2.Item 7.3.5.2.2.BTN:Save - Material Master 7.3.6.SD:Create Customer-specific condition:50005:VK31 - Conditions - LO|SD|Master data|Conditions|VK31 Create 7.4.2.2.3.Schedule lines 7.3.6.1.SCR:Main - Date, Quantity 7.3.6.1.1.FRM:Left 7.4.2.2.4.Incompletion log 7.3.6.1.1.1.LIN:Prices - Mandantory fields set at customizing - LIN:Individual|DoubleClick - Left empty by user 7.3.6.1.2.FRM:Right 7.4.2.3.Shipping 7.3.6.1.2.1.FRM:Head 7.4.2.3.1.1.Create Outbound Delivery: - LIN:Cnty Sorg Dchl Cust Mater|BTN:New - Header 7.3.6.1.2.2.FRM:Item - Can reference 1 or more sales orders - DDN:SalesOrg = 1000 - Shipping point - DDN:Channel = 10 - Due date - DDN:Customer = 50005 - Ship-to-party - FRM:Customer/Material with release status - Item Cond Mat AmntPerUnitValid fromValid to - Material, Quantity, Stock type/Area/Bin to pick from PR00SpeedStarlett-0005 2400 1 PC Now 31.12.9999 7.4.2.3.1.2.Picking: - BTN: Scales|FRM:Scales - Header QuantAmount - Can reference 1 or more outbound deliveries 1 2400 - Assign warehouse to delivery 500 2200 - Create Transfer Requests Transfer Order MM:Good movements 7.3.6.1.3.BTN:Save - Item 7.4.SD:Sales order process - Material, Quantity, Stock type/Area/Bin to pick from 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
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 43 9.Financial Accounting Scenario - FK:Cost type 9.1.Plot of Scenario - FK:Cost center - Free fields 9.1.1.General Ledger - Created date 9.1.1.1.FI:Create G/L account in Chart of Account: - Modified date - CONS|312600|900005INT - Viewed date 9.1.1.2.FI:Create G/L account: - Status: Supress/Display, Required/Optional - Company1000|900005 9.2.1.2.DEF:Collective Positions 9.1.1.3.FI:Enter G/L Account Document: 9.2.1.3.DEF:Reconciliation accounts - Credit:113000BankDebit:900005 5000EUR - Connects balance of subledgers into general ledger real time 9.1.2.Accounts Payable - Items cannot be posted manually here 9.1.2.1.FI:Enter Vendor Invoice 9.2.2.DEF:FI-GL:General Ledger (G/L) - Vendor = 100268 - An instance of Chart of Accounts class - Amount = 10000EUR - 1:1 related wity Company - CostCtr = CCMSD-0005 9.2.2.1.Contains subledgers - ReconAcct = 470000 9.2.2.1.1.FI-AP:Accounts Payable - Date = Yesterday - Mainly used by MM to pay vendors 9.1.2.2.FI:Automatic payment run: 9.2.2.1.1.1.Account - Company = 1000 - Credit - Vendor = 100268 - Debit - Date = next month 9.2.2.1.2.FI-AR:Accounts Receiveabe 9.1.3.Accounts Receiveable - Mainly used by SD to receive payment from customers 9.1.3.1.FI:Create Credit Management Master: 9.2.2.1.2.1.Account - Customer = 50005, - Credit - TotLim = 500000EUR, - Debit - IndivLim = 100000 EUR, 9.2.2.1.3.FI-AA:Asset Accounting - CredContArea = 1000: - Mainly used by Treasury (TR) to track financial resources - IndivLim = 10000 EUR 9.2.2.1.3.1.Account 9.1.3.2.SD:Create Sales Order: - Credit - Customer = 50005, - Debit - Plant = 1000, 9.2.2.1.4.FI-BL:Bank Ledger - SalOrg = 1000, - Cash-flow movement - Chnl = 10 9.2.2.1.4.1.Account - Division = 00 - Credit - SpeedStarlett-0005, 10PC - Debit 9.1.3.3.FI:Release Blocked SD Document 9.2.2.2.Contains reports - Customer = 50005 9.2.2.2.1.FI:DEF:Balance Sheet Report 9.1.4.Asset Accounting - Account-based period-end closing of a company inkey date 9.1.4.1.FI:Create Asset Master Record: - Assembled from subledger by Countrywise-defined standards: - Asset = 3414 0 (Forklift-0005) US-GAAP, IAS - CostCtr = CCMSD-0005 9.2.2.2.1.1.DEF:Assets:Application of funds 9.1.4.2.FI:Post Asset Acquisition: - FI-AA:Assets - Buy asset = 3414 0 (Forklift-0005) - MM:Material - Vendor = 1000 - SD:Recieveables - Amount = 35000EUR+10%Tax: - FI-BL:Bank 9.1.5.Balance Sheet and Profit&Loss Statement 9.2.2.2.1.2.DEF:Liabilities:Source of funds 9.1.5.1.FI:Create Balance Sheet and P&L Report - TR:Equity capital 9.2.DEF:Structures of FI - TR:Loans - FI-AP,MM:Liabilities 9.2.1.DEF:Chart of Accounts 9.2.2.2.1.3.OrgLevels - 1:m related with Company - Operational/Country Charts of Accounts:CAUS,GKR,INT - Object class describes fixed level-number hierarchy of: - Company 9.2.1.1.DEF:G/L Accounts Master - Business Area 9.2.1.1.1.Header - Cost center:only in new system! 9.2.1.1.1.1.Account specific part - Profit center:only in new system! - PK:ID - Functional area:only in new system! - Description - Planned data - Account type: P&L/Balance Sheet - Actaual data - FK:Superior category in General Ledger(G/L) - Variance - FK:Superior category in Balance Sheet 9.2.2.2.1.4.GUI Transactions - FK:Superior category in Profit&Loss Report (P&L) - Old ABAP Report:RFBILA00: - FK:Account Group: user defined free grouping - Less flexible 9.2.1.1.1.2.Company specific part - New G/L Accounts Info System:Fin.Statm:Act/ActCompar: - Account control/management - More detailed OLAP-like filtering - Financial/interest details 9.2.2.2.2.FI:DEF:Profit&Loss Statement - Joint ventures sharing - Comparison of a revenue and expenditure of a compny in a - Document control given period - Created date 9.2.2.2.2.1.Expenditure - Modified date 9.2.2.2.2.2.Revenue - 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 Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage,Aaa|Bbb|-Menu/Submenu, SCR-Screen, FRM-Frame, ID- UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 44 9.2.3.DEF:New SAP General Ledger 9.3.2.DEF:FI-CO:Managerial accounting/Controlling 9.2.3.1.Extended data structure of G/L accounts and their - Internal planning and evaluation prurpose standard reporting - International standard - Functional area - Communicates with financial accounting through reconciliation - Profit center accounts - Partner Profit center - Uses P&L statement from financial accounting - Cost type 9.3.2.1.Parts - Cost center 9.3.2.1.1.Cost center accounting - Segment 9.3.2.1.2.Profitability accounting - Free fields 9.3.2.1.3.Product Costing 9.2.3.2.Document split: 9.3.2.1.4.Job Costing - All lines of accounting documents can be split along the 9.3.2.2.Organization following structure 9.3.2.2.1.Client - For split lines, a zero balance option can be set with extra 9.3.2.2.1.1.Operational Chart of Account balance row - Company × - Enables real time data entry segmentwise, insead of adjustment - Controling Area in period end closing in the old system - Cost accounting unit 9.2.3.2.1.Project/Cost center/Internal order - Can collect revenues and costs 9.2.3.2.1.1.Profit center - m:m related with companies using the same chart of - Segment accounts with same version of fiscal year 9.2.3.3.Real time COFI data transfer 9.3.2.2.1.2.Operating Concern 9.2.3.3.1.DEF:Types of CO documents: - 1:m with controling areas 9.2.3.3.1.1.Has no consequence in FI 9.4.PROC:Accounting - Allocation 9.4.1.G/L Account posting document 9.2.3.3.1.2.Has consequence in FI 9.4.1.1.Work template - Assessments, - Screen variants - Distributions, - Account assignment template - Confirmations, - Held docs template - CO-internal settlements 9.4.1.2.Header 9.2.3.3.2.Handling CO docs with FI consequence - ID - These are automatically transferred with FICO transaction - Date - Related FICO documents can be accessed from both - Control info direction - Scanned paper documents reference - Document lines can be split in following structure: - Show only balance or lines - Project/Cost center/Internal order 9.4.1.3.Line - Profit center - Posting key - Segment - Valid account types 9.2.3.3.3.Scope of data transfer can be delimited by OrgUnit: - Credit/Debit - Company - Sales relevant - Business Area - Screen selectionEntry check rules - Functional area - Amount - Public Fund - Account - Public Grant - Payment terms 9.2.3.4.Multiple Books in GL - Cost center 9.2.3.4.1.DEF:Leading ledger - Explanatory text - 1:1 related for Client 9.4.1.4.Information section - Controls the: - Credit/debit balance 9.2.3.4.1.1.General ledgers - Attached scanned documents - 1:1 related for Companies in different Countries 9.4.2.FI-AP:Accounts payable handling - With different charts of accounts: US:US-GAAP, DE:HGB 9.4.2.1.DEF:Vendor master data - With different fiscal year version 9.4.2.1.1.Client specific part 9.3.TYPES:Accounting - Name 9.3.1.DEF:FI-FI:Financial accounting - Address - External legal obligation 9.4.2.1.1.1.Company specific part - Changes countrywise 9.4.2.1.1.2.PurchaseOrg specific part 9.3.1.1.Parts: 9.4.2.2.PROC:Procurement 9.3.1.1.1.FI-GL 9.4.2.2.1.Transactions - FI-AP/AR StepCredit Debit - FI-AA 1 Material GoodsReceipt - FI-BL 2 GoodsReceipt(GR/IR) Liabilities 9.3.1.1.2.Cash journal 3 Bank Alloc Bank 9.3.1.1.3.Inventory 4 Liabilites Bank Alloc 9.3.1.1.4.Tax accounting 9.4.2.2.2.Documents 9.3.1.1.5.Accrual accounting 9.4.2.2.2.1.Purchase Order 9.3.1.2.Organization - MM:ID, Amount 9.3.1.2.1.Client - FI:- 9.3.1.2.1.1.Operational Chart of Account 9.4.2.2.2.2.Goods receipt - Company × - MM:Material doc - Smallest organizational units having Balance Sheet - FI:Cred:MaterialDeb:GR/IR - Country:Company is strictly 1:m 9.4.2.2.2.3.Invoice receipt - Business Area - MM:Invoice verification - Optional, it is created only if it is required by legal ruling - FI:Cred:GR/IRDeb:Vendor,Tax - Or required internally for partial balance sheets - Can represent subsidiaries or product lines - m:m related with companies
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 49 10.Managerial Accounting Scenario - Allocated costs are shared as overhead cost on product units 10.1.Plot of Scenario - Recives data mainly from: - FI-GL:Stock, 10.1.1.Create master data - FI-AP:Vendor invoice, 10.1.1.1.CO:Create Cost centers: - FI-AA:Depreciations - CC-CA-0005(Cafeteria) 10.2.1.1.1.1.Cost Element Accounting (CO-OM-CEL) - CC-MT-0005(Maintenance) - Receives detailed data from: CO-OM-CCA - CC-MF-0005(Manufacturing) - Aggregates cost occoured at cost centers in Cost elements 10.1.1.2.CO:Create Statistical key Figure: - Reconcialtes costs and revenues with FI-GL - EM0005(Employees) 10.2.1.1.1.2.Activity Based Costing (CO-OM-ABC) 10.1.1.3.CO:Create Secondary Cost Element: - Cost can collected by Activity types|Work Centers - CAF-0005(Cafeteria, for assessment) - Recives data mainly from: HCM:Personell costs - MNT-0005(Maintenance, for allocation) 10.2.1.1.2.Internal Orders (CO-OM-OPA) - MFT-0005(Manufacturing, for allocation) - Jobs and tasks given in Internal order can also serve as cost 10.1.1.4.CO:Create Activity Types: collectors - MT0005(for allocation Maintenance) 10.2.1.2.Product Cost Controlling (CO-PC) - MF0005(for allocation Manufacturing) - Collects allocated planned/actual costs from: 10.1.1.5.CO:Create Cost Center Gropup: - CO-OM-CCA:Cost centers|SubCostCenters - Group-0005:Containing: - CO-OM-ABC:Activities|WorkStation - CC-MT-0005(Maintenance) - CO-OM-OPA:Internal Orders - CC-MF-0005(Manufacturing) - And all they possible cross-cost-flow combinations 10.1.2.Cost Center Planning - Receives other data from: 10.1.2.1.CO:Planning number of employees: - PP:BOMs - EM0005=20 at CC-MF-0005 - Allocates it to product/service units of production orders - EM0005=5 at CC-MT-0005 - Transfers back data to: MM:Product cost 10.1.2.2.CO:Planning Activity Output: 10.2.1.3.Profitability Analysis (CO-PA) - MT0005=10000H at CC-MT-0005 - Recives data mainly from: - MF0005=40000H at CC-MF-0005 - FI:Expense/revenue postings 10.1.2.3.CO:Planning Primary Cost Input: - SD:Revenue postings - 417000(PurchServ)=150000EUR at CC-CA-0005 - Measures efficiency in external market segmentwise - 430000(Salaries)=150000EUR at CC-MT-0005 10.2.1.4.Profit Center Accounting (EC-PCA) - 420000(DirectLabour)=600000EUR at CC-MF-0005|MF0005 - Recives data mainly from: 10.1.2.4.CO:Planning Activity Input transfer: - FI:Expense/revenue postings - CC-MT-0005MT0005=1000HCC-MF-0005:KP06 - SD:Revenue postings 10.1.2.5.CO:Plan cafeteria cost assessment: - Measures efficiency in internal market of company - CC-CA-0005|CAF-0005=150000EURGroup-0005|by EM0005 10.2.1.5.Organization 10.1.2.6.CO:Auto price calculation of activity types: 10.2.1.5.1.Client - Group-0005 10.2.1.5.1.1.Operating Concern - Represents market segments in CO-PA 10.1.3.Manual Expenses Posting - Controling Area × 10.1.3.1.CO:Direct activity allocation: - Cost accounting unit - CC-MT-0005MT0005=200HCC-MF-0005 - Revenues and costs can be collected and allocated within 10.1.3.2.FI:Post external expenses: that - 417000(ExternServic)=12500EUR at CC-CA-0005 - m:m related with companies using the same Operating 10.1.3.3.CO:Period-end closing assesment cycle: chart of accounts with same Version of fiscal year - CC-CA-0005|CAF-0005Group-0005|by EM0005 - Works in Controlling Area Currency, eg. EUR 10.1.4.Internal Orders - Business Area × 10.1.4.1.CO:Create internal order: - Company × - 100291 at 4500(R&D) - Can have parallely different Local charts of accounts also 10.1.4.2.MM:Purchase order to internal order: - Works with Company/Cost object currency: eg. USD - 100PC Gearing-0005 from 100268 - Purchasing/Sales Organization 10.1.4.3.MM:Goods Receipt for Order: - Plant - 4500017613 - Transaction 10.1.4.4.CO:Direct activity allocation: - Works with Transaction currency: eg. GBP - CC-MF-0005MF0005=100H100291 10.3.CO:Data structures 10.1.4.5.FI:Post expenses: 10.3.1.DEF: CO-OM Master Data Groups - CC-MF-0005|CostElmt420000=1845EUR, CC-MT-0005| 10.3.1.1.Controling area CostElmt430000=3600EUR 10.3.1.1.1.Standard hierarchy (compusory) 10.1.4.6.CO:Add cost element to allocation cost element group: - No-fixed level hierarchy containing master data cost objects 1:m - MF-0005OAS_ORDERS related (cannot contain twice the given master data) 10.1.4.7.CO:Settle internal order: - With unique ID name - 100291 10.3.1.1.2.Custom hierearchies (optional) 10.1.5.CO-PC:Product Costing - Alternaive non-fixed level hierarchies for reporting purpose, 1 10.1.5.1.PP:Create new Work Center: master data can be assigne to m alternative hierarchies - PL-0005 - With unique ID name 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.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
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 50 10.3.2.DEF:CO-OM Master Data: Cost objects 10.4.3.PROC:CO:Cost Allocation 10.3.2.1.DEF:Cost Element - CO Posting occours among Secondary cost elements - Classification of production factors within controlling area - There is no related FI docoment and G/L Accounts 10.3.2.1.1.Primary cost elements - Types: - Created at external service providers/vendors 10.4.3.1.Manual allocation: - Have G/L account (in Class 4 Expenses) in operating chart of - Costs: Actual accounts - Date: Manual, executed at period-end closing - Number of G/L account and primary cost category is the - Sender (credited): Cost center same! - Receiver (debited): Usually an external order without automatic 10.3.2.1.2.Revenue cost elements processing - Have G/L account (in Class 8 Revenue) in operating chart of - Amount: Manualy entered cost accounts 10.4.3.2.Direct activity allocation: 10.3.2.1.3.Secondary cost elements - Can happen among cost objects containing the same activity - CO Internal category type with activity prices determined - Do not have G/L account in operating chart of accounts, - Costs: Planned/Actual internal operations - Date: 10.3.2.2.DEF:Cost Center × - For planned costs: Auto-Assesment cycles|Segments - Delimited location of cost occourence, OrgUnit in ContrArea - For actual costs: Period-end closing assesment cycle - Cost can be originated and reallocated among them - Sender (credited): Only 1 Cost center - They form non-feyed level hierarchy based on geography| - Receiver (debited): Can be 1 or more real (not statistical) cost Corporate functions|Subfunctions objects 10.3.2.3.DEF:Activity Type - Amount: Cost calculated by manually entered activity amounts × - Activities of cost centers activity prices of master data - Tracing factor of cost allocation among them 10.4.3.3.Periodic/indirect allocations: - Internall allocation is done with the help of secondary cost 10.4.3.3.1.Assessment elements - Can happen among cost objects containing the same: - 1 activity type can be assigned to max 8 cost centers - Statistical key figure: with its values determined (eg. Number 10.3.2.3.1.For Cost centers×Activity type we determine: of employees), it will be base of allocation, the „tracing factor” 10.3.2.3.1.1.Activity output - Cost element: can be primary/secondary - Manual allocation - Costs: Planned/Actual - Automatic allocation - Date: 10.3.2.3.1.2.Activity price: always by sender activity - For planned costs: Auto-Assesment cycles|Segments - Planned - For actual costs: Period-end closing assesment cycle - Actual - Sender (credited): can only be 1 cost center/business process 10.3.2.4.DEF:Statistical key figures - Receiver (debited): Can be 1 or more real (not statistical) cost - Scalar variables assigned to cost center objects (eg. Cost Center Group) - Tracing factors: serving as the basis of cost allocation - Amount can be: - They ar objects in Logistic Information System - Auto-proportionated, sender can hold back Residual% - Types: optionally: 10.3.2.4.1.1.Fixed value: - CostElemt(Receiver) = - Cannot be changed over time - StatKeyVal(Receiver) × (CostElemt(Sender)-Residual%) 10.3.2.4.1.2.Total vatue: / ΣReciverStatKeyVal(Receiver) - Has to be entered manually in each time period - Given by percentages or portions 10.3.3.DEF:Statistical objects - Manually entered amounts to override automatic ones - Cost objects, which can receive only costs from other sender - Tracback cost elements: we cannot navigate back from reciver objects for statistical/analysis prurpose cost element to sender cost element) - But cannot send costs themselves: - Except if primary cost elments are grouped into assesment 10.3.3.1.Statistical order cost element group, and it is used as cost element of 10.3.3.2.Statistical object assesment, 10.3.3.3.Profit center - However this eats up lot of machine resources 10.4.CO:Processes 10.4.3.3.2.Indirect Activity Allocation 10.4.1.CYC:CO-OM:Cost Center Planning Overview - Same as direct allocation, just activity outputs and activity 10.4.1.1.CO-PA,SD:Sales Plan prices are determined automatically 10.4.1.2.PP:Required Activity|Process input planning 10.4.3.3.3.Distribution 10.4.1.3.CO-OM:Allocation of requirement among cost centers 10.4.3.3.4.Template Allocation 10.4.1.4.CO-OM:Computing Activity|Process prices 10.4.3.3.5.Periodic Reposting 10.4.1.5.CO-PC:Product costing 10.4.4.PROC:CO:Internal Orders 10.4.1.6.CO-PA:Measuring profitability, back to sales plan - Flexible tool for planning/allocation/monitoring costs 10.4.2.PROC:CO:Posting 10.4.4.1.TYPE:Validity 10.4.2.1.FI:Accounting document 10.4.4.1.1.Real - Always has both credit-debit sides! 10.4.4.1.2.Statistical 10.4.2.2.CO:Related CO document 10.4.4.2.TYPE:Scope - Created only if primary or revenue cost elemnts are affected by 10.4.4.2.1.Overhead Orders FI operation - Handles hard to allocate overhead costs (eg. Trade fair) - Related documents can be drilled down from each other 10.4.4.2.2.Investment Orders - PK:Unique ID - Handles costs producing a fixed assed (eg. Warehouse) - Posted amount 10.4.4.2.3.Accrual Orders - FK:Cost element (optionally ref. to a reconciliation G/L acct) - Used for offset postings from secondary costs elements - FK:Receiver:Cost object debited calculated internally in CO - FK:Sender:Cost object credited (optional): usually there is no 10.4.4.2.4.Orders with Revenue credit side, it is a one-sided journal, except if at transfer - Handles revenues/costs not processed by SD between 2 cost objects: 10.4.4.3.TYPE:Planning of Internal Orders - Initiated by credit-debit FI document - Plans long lifecycle internal orders only - Or internal CO operation 10.4.4.3.1.Overall planning - FK:Reference to accounting document 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
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 51 10.4.4.4.PROC:Posting Internal Order - With Value Fields of StatKeyFigs: - One sided line item debited at cost centers in a given cost - Sales quantity element - × Standard Material Price 10.4.4.5.PROC:Commitment at Internal Order - = Sales revenue: - Special type of posting at overhead internal orders: - + Revenue 10.4.4.5.1.MM-PUR:Pruchase requisition Purchase Order - - Discounts 10.4.4.5.2.Attached Overhead Internal Order - - Comissions - It stores Commitment/Obligo: planned costs of an order - - Direct Sales Costs 10.4.4.5.3.Goods Receipt - = Net Revenue: - Orders arriving consume this planned commitment - - Direct material - Until it goes to zero - - Production variable cost - And actual costs of ggods receipt are posted to Internal Order - = Contribution margin I: 10.4.4.6.PROC:Settlement of Internal Order - - Material overhead - Posting cost of internal order to final receiver cost centers - - Fixed costs periodically - = Contribution margin II: - Arranged by Internal Order master|Settlement rule - +/- Variances of actual/planned standard material prices - Cost can be settled to any type of cost object allowed by - = Contribution margin III: customizing - - Other overhead 10.4.5.PROC:CO-PC:Product Costing - = Operative Profit 10.4.5.1.DEF:Product Costing - /Cost of capital: - Estimates cost of a product or service - + FI-AP:Payables 10.4.5.2.Cost data sources: - + FI-AR:Receivables 10.4.5.2.1.With quantity structure: BOM - + FI-AA:Fixed Assets 10.4.5.2.2.Manual entry - + FI-AA,MM:Inventory 10.4.5.2.3.External import - = Return On Investment (ROI) 10.4.5.3.PROC:Product costing 10.4.7.PROC:EC-PCA:Profit center accounting 10.4.5.3.1.MM:Material master|Production version 10.4.7.1.DEF:Profit Center Accounting: 10.4.5.3.1.1.Multi-level BOM - Internal evaluation of 1 year profitability on OLAP reporting GUI 10.4.5.3.1.2.Routing - Based on StatKeyFigs: 10.4.5.3.1.3.Material prices - (same as CO-PA) - Types: 10.4.7.2.DEF:Profit Center: - Planned 1/2/3:Rawmat - Autonom part of Company can be grouped by product line × - Tax based and commercial prices:Semi/Finshed geography × corporate function - Price control: 10.4.7.3.PROC:Profit Center posting - Standard - Profit centers are not real but statistical accounting objects, - Moving average therefore: - Process(once in a period): 10.4.7.3.1.FI-AP,FI-AR:Accounting Doc Entry - CalculatedMarkedReleasedStandard cost estimate - Debit Real Expenses 10.4.5.3.2.FI:Post Real expenses of Material G/L Accunts - Credit Real Revenues - FI settles actual material costs with the help of Invoice Receipts 10.4.7.3.2.CO-OM:Posted first on real cost objects - Variances are posted to CO-PA:Profitability Analysis - CostCtr/InternalOrder/Projec/BusinessProc| 10.4.5.3.3.CO:Debit cost objects (CostCtr/Proj/IntOrd) - CostElemnt/Activity type - Done at period end closing: - CO-PA:Collects external revenues, profits 10.4.5.3.3.1.Cost structure/split 10.4.7.3.3.EC-PCA: Assigned profit centers statistically posted - Product - Evaluates internal profitability of profit centers - Cost Component:(Material, Labour, Process, Overhead) 10.5.CO-OM:Create master data - Cost Element/Activity type 10.5.1.CO:Create Cost center:CC-CA-0005(Cafteria):KS01: - Itemization:from BOM and Routing - FI|CO|CostCtr Acct|Master|CostCtr|Individ Proc|KS01 - Cost splits Create| 10.4.5.3.3.2.Plan/Actual/Variance computation 10.5.1.1.SCR:Start - Compares Standard price of material at period end closing - DDN:ContrArea = 1000 - With real costs entered - TBX:Cost center = CC-CA-0005 - Variances are posted in CO-PA:Profitability Analysis - DDN:Validity from = 01.01.CurrYr 10.4.5.3.3.3.Standard price estimate of material is created - DDN:Validity to = 31.12.9999 - Inventory movements are valuated on this price 10.5.1.2.SCR:Main 10.4.6.PROC:CO-PA:Profitability Analysis - TBX:Name = Cafeteria-0005 10.4.6.1.DEF:Profitability Analysis - TBX:Description = Cafeteria-0005 - Analysis of external profitability on OLAP GUI of - DDN:Person Responsible = Gabor Pauler - Grouping by Market Segments defined by Chacteristics: - DDN:Cost Center Category = 2(service cost center) - Company| - DDN:Hierarchy area = H10005 - Business Area× - DDN:Company Code = 1000 - SalesOrg| - DDN:Business Area = 9900(Corporate/other) - SalesGrp| - DDN:Profit Center = PROF-0005 - SalesRep× 10.5.1.2.1.BTN:Save - Region× 10.5.2.CO:Create Cost center: CC-MT-0005(Maintenance): - CustGroup| - Customer× KS01: - Same as above, except: - ProdCat| - TBX:Name = Maintenance-0005 - Product× - 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)
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 57 11.Enterprise Asset and Service Management Scenario 11.3.1.1.3.1.PK:Compound with fields auto assigned: 11.1.Plot of Scenario - Coding template:max. 40char string mask to generate PK, assembled from: 11.1.1.LO-PM:Corrective Maintenance - A:Alphabetic wildcard 11.1.1.1.LO-PM:Create Maintenance Request: - N:Numeric wildcard - 00-B01 pump station| - X:Alphanumeric wildcard - TEY-00 electric pump| - Hierarchy level signal - Frame broken, weld it - Example: C.1|C.1.1|C.1.1.1, etc. 11.1.1.2.LO-PM:Create Maintenance Order from request: 11.3.1.1.3.2.TAB:General - 817854 - Object Class 11.1.1.2.1.LO-PM:Run Plan/Actual Cost Analysis, Release - Object Instance 11.1.1.2.2.LO-PM:Planned Material Withdrawal: - Manufacturer - 100-600(Support base) 1PC - Linked docs/drawings/permits/manuals 11.1.1.2.3.LO-PM:Maint.Order Confirmation 11.3.1.1.3.3.TAB:Location 11.1.1.2.4.LO-PM:Technical Completion and Cost Analysis - Address 11.1.1.2.5.CO-OM:Cost Settlement - Coordinate 11.1.1.2.6.LO-PM:Business Completion 11.3.1.1.3.4.TAB:Organization 11.1.1.2.7.LO-PM:Cost Reporting - Company 11.1.1.3.LO-PM:Location Reporting: - CostCtr - MaintPlant = 1000 - Planning/Operational Plant 11.1.2.LO-CS:Service Order Processing 11.3.1.1.3.5.TAB:Structure 11.1.2.1.LO-CS:Create Service Order: - FK:Equipment - 502732:T-CSE100(server down) - FK:Construction type:references to a material number with 11.1.2.2.LO-PM:Service Order Confirmation: BOM defined to describe structure 11.1.2.2.1.Time confirmation - FK:MainFunctLoc in hierarchy Act. Act. Final Clear NoWork 11.3.1.2.DEF:Pieces of Equipment|Serial numbers Operat WorkCtr Plant Type Work Conf Reserv Remain - Independent physical objects 0010 PC-SERV 1200 1410 3HRTrue True True - Can be installed in functional locations 0010 PC-SERV 1200 1413 1HRTrue True True - Can be linked with material master if equipment needs inventory 11.1.2.2.2.Goods movements for operation 0010 management (eg. more numerous) MaterialQuantityPlantStorageMovement 11.3.1.2.1.Used for: R-1120 1PC1200 0001 261 - Data collection, 11.1.2.3.LO-CS:Service Order Billing: - Monitoring, 11.2.Organizational levels of Maintenance and Service - Costing, - Efficiency analysis 11.2.1.Client 11.3.1.2.2.Described by Equipment master data: 11.2.1.1.Company 11.3.1.2.2.1.PK:Compound:Material num,Serial Number (S/N) 11.2.1.1.1.Plant - ALT:Can be adopted from manufacturer S/N, but it should 11.2.1.1.1.1.DEF:Planning Plant: form compound unique ID with ameterial number! - Planning unit of maintenance/service - ALT:Own serial numbering - Maintenance Planning Group is resposible for that, in 2 ways: 11.3.1.2.2.2.TAB:Serial data - DEF:Plant specific maintenance : Plan.Plant:Oper.Plant = - Plant 1:1 - Storage - DEF:Cross-Plant maintenance: Plan.Plant:Oper.Plant = - Customer sold to 1:m - Batch number 11.2.1.1.1.2.DEF:Operating Plant: - FK:Material number - Physical place where Operation systems installed - FK:Stock item - DEF:Plant Sections: 11.3.1.2.2.3.TAB:General - Part of plant with separated maintenance contact person - Object Class - Locations - Object Instance - Buildings - Manufacturer - Coordinates - Linked docs/drawings/permits/manuals - DEF:Maintenance/Service Work Centers: 11.3.1.2.2.4.TAB:Location - Organizational units of operating system - Address - With types : - Coordinate - ALT:Machine group|Machine 11.3.1.2.2.5.TAB:Organization - ALT:Person group|Person - Company - With functions: - CostCtr - Capacity Planning:compares requirement with number of - Planning/Operational Plant employees in work center hierarchy 11.3.1.2.2.6.TAB:Structure - Scheduling:WorkCtr|Formulas|Standard values of time - FK:FunctLocation where installed - Costing:by CostCtr|WorkCtr|ActType|ActPrice×ActInput - FK:Construction type:references to a material number with - With Employees assigned BOM defined to describe structure 11.3.Data Structures of Maintenance and Service - Status:(Installed/Dismantled) 11.3.1.DEF:Technical Objects Master - 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: Legenda:DEF:-definition, PRC:-process, ALT:-alternatives, CYC:-cycle, -follows, -(dis)advantage,Aaa|Bbb|-Menu/Submenu, SCR-Screen, FRM-Frame, ID- UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 58 11.3.1.3.Maintenance Bill of Materials (BOM) 11.4.2.2.4.Materials Required list - Describes the assemblies of location and equipment - FK:Material or BOM - These are not related to production as normal BOMs - Quantity 11.3.1.3.1.ALT:Can describe class of technical objects with - FK:Storage identical internal structure 11.4.2.2.4.1.Auto-checks availability: - Create a material master record representing a certain class of - ALT:Stock items: equipment - Creates Stock Reservations - Create a BOM for the material - ALT:Out of stock items - Reference the material number at each instaces of technical - Creates Purchase Requisitions objects at Equipment/FunctLoc Master|Structure|Construction 11.4.2.2.5.Tools required list field 11.4.2.2.6.Settlement rule 11.3.1.3.1.1.Material BOM: - FK:Cost bearer object 11.3.1.3.1.2.Equipment BOM - Percentage 11.3.1.3.1.3.Functional location BOM 11.4.2.2.7.Costing views 11.3.1.3.2.ALT:Can describe spare parts assembly for a - Estimated/Planned/Actual costs in technical object 11.4.2.2.7.1.LO-PM view 11.3.1.3.2.1.For Maintenace orders - By Value categories 11.3.1.3.2.2.For Task Lists 11.4.2.2.7.2.CO view 11.3.2.Equipment Install/Dismantle Goods movements - By Value categories|Cost elements - Equipment should reference to a material number with inventory 11.4.3.Scheduling 11.3.2.1.DEF:Installing: 11.4.3.1.Capacity check - Withdraw from stock as material 11.4.3.2.Final material availability check - Install in functional location 11.4.3.3.Release (can be done with missing parts also!) 11.3.2.2.DEF:Dismantling: - Status:REL(Released) - Dismantle from functional location 11.4.3.4.Withdraws materials from stock - Put stock as material 11.4.3.4.1.Planned issues 11.4.PROC:LO-PM:Corrective Maintenance 11.4.3.4.1.1.ALT:Stock items: 11.4.1.Notification list - Stock ReservationGoods Issue references to that 11.4.1.1.Header 11.4.3.4.1.2.ALT:Out of stock items: - CreationDate - Purchase RequisitionPurchase Order references to - Creator thatGoods ReceiptInvoice receiptAccounting Doc 11.4.1.2.Items Credit/debit Maintenance Order - FK:Functional location (optional) 11.4.3.4.2.Unplanned issues - FK:Equipment S/N (optional) 11.4.3.4.2.1.ALT:Stock items: - FK:Material number (optional) - Maintenance orderGoods Issue references to that - FK:BOM assembly (optional) 11.4.3.5.Print Paper-based Docs - Description of malfunction 11.4.3.5.1.Job ticket: - Cause - Contains Maint.Order|Header data for monitor person - Required activites 11.4.3.5.2.Operation control ticket - Required tasks - Contains Maint.Order|Header data for responsible person 11.4.3.5.3.Material pick list 11.4.2.Create Maintenance Order - Summary list for inventory clerk 11.4.2.1.Ways of creation 11.4.3.5.4.Object list 11.4.2.1.1.Automatic: - Summary list for inventory clerk - At maintenance plan period, notif.item:maint.order = 1:1 11.4.3.5.5.Material withdrawal slip 11.4.2.1.2.Combined: - Authorizes responsible person to obtain materials - At maintenance plan period,Notif.item:maint.order = m:1 11.4.3.5.6.Time ticket 11.4.2.1.3.Direct: - Standard times and deadlines of operations for workers - Manually entered in same time, notif.item:maint.order = 1:1 11.4.3.5.7.Confirmation slip 11.4.2.1.4.Unnoticed: - Entering actually worked hours for workers - Order entered without preliminary notification 11.4.2.1.5.Urgent: 11.4.4.Execution and Completion - Order entered after maintenance with technical completion 11.4.4.1.SCR:Individual 11.4.2.2.Content - Time confirmation 11.4.2.2.1.Header - Activity reports - PK:Number - Status:PCNF(Partially confirmed) - FK:Type 11.4.4.2.SCR:Collective - Description 11.4.4.2.1.Enter Measurement readings - ScheduledDate 11.4.4.2.2.Technical confirmation - Responsible person for monitor - Status:CNF(Fully confirmed) - Creator 11.4.4.2.3.Technical completion at reference date - Creationdate - Status:TECO(Technically completed) - LastModifier - Still can debit Invoice receipts 11.4.2.2.2.Object list - But open stock/capacity reservations and purchase - FK:FuncLoc requisitions are closed! - FK:Eqipmt - If there is any problem with maintenance, TECO can be - FK:Assembly reversed back to REL status, re-opening reservations and - FK:S/N requisitions - The assigned object themselves do not create control of 11.4.4.3.SCR:Cross Application Time Sheets (CATS) costs automatically, see settlement rule! - CO order settlement 11.4.2.2.3.Operation/Task list - FK:Reference to notification item - FK:Responsible WorkCtr|ActType|ActPrice×ActInput
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 62 12.Project Management Scenario - Different elements can involve different organization levels (see 12.1.Plot of scenario: below) 12.1.1.Enter master data: 12.3.LO-PS:Project Master Data: 12.1.1.1.MM:Create Dummy material for project: 12.3.1.DEF:LO-PS: Project: - Techno-0005, - Unique hierarchy of tasks involving multiple corporate functions - Item type = 0005(Milestone billing) - With given goal, budget and deadline - Disposition = ND(No dispo) - Incurring separable cost/revenues/results 12.1.1.2.CO:Create activity types: - Should be done only once or in small number of times - T-0005(Test driver) 12.3.1.1.Possible OrgLevels 12.1.1.3.CO:Planning Activity Output/Prices: - ContArea - T-0005=100EUR/H at 4280(QualContr) - Company 12.1.1.4.CO:Assign Act.Type: - BusiArea - T-0005 to Group TestDriver - ProfCtr 12.1.1.5.HCM:Create personell master record: - Plant - 9900005 12.3.2.DEF: Work Breakdown Structure (WBS) 12.1.1.6.HCM:Maintain Personell master data: Element: - OrgUnit = 1300 - Optional element of project (some of them have only Networks) - CostCtr = 4280(QualContr) - Basic building blocks of project structure forming non-fixed level - ActType = T-0005(Test driver) hierarchy with max. 99 levels, max.10000 WBS 12.1.2.LO-PS:Create project structure - Used for controlling purposes 12.1.2.1.PROJ:Techno-doping-0005 12.3.2.1.Possible OrgLevels 12.1.2.1.1.WBS:Development-fixed price 0005: - Company Plan/Bill/AcctAssign - BusiArea 12.1.2.1.1.1.WBS:Blueprint 0005: Plan/Bill/AcctAssign - ProfCtr - MLST:Blueprint 0005: Finish specif, CreateSalesDate, - Plant Bill=30% - CostCtr 12.1.2.1.1.2.WBS:Prototype 0005: Plan/Bill/AcctAssign - FunctLoc - NETW:Prototype-network 0005 - Equipmt - ACT|Internal:Specification 0005 12.3.2.2.WBS Content: - REL:FS(Follow) 12.3.2.2.1.Hierachy by: - ACT|Internal:Construction 0005 - ALT:Time phases of project - MLST:Milestone prototype 0005: Close, Milestone, - ALT:Product functions of project CreateSalesDate, Bill=70% - ALT:Corporate functions/OrgUnits 12.1.2.1.2.WBS:Special expenses 0005: Bill/AcctAssign 12.3.2.2.2.Operative Indicators: 12.1.3.LO-PS:Project Planning 12.3.2.2.2.1.OPT:Planning Element 12.1.3.1.LO-PS:Auto Schedule Project - Allows costs to be assigned 12.1.3.2.LO-PS:Manual Easy Cost Planning: 12.3.2.2.2.2.OPT:Account Assignment Element - WBS Blueprint by template ZPS101(Elevator) - Allows Network|Activities, Sales Orders to be assigned 12.1.3.3.LO-PS:Automatic Network Costing: 12.3.2.2.2.3.OPT:Billing Element - Prototype network - Allows revenues and partial billing to be assigned 12.1.3.4.LO-PS:Project release 12.3.2.2.2.4.OPT:Statistical - Virtual WBS for reporting, cannot work without related real 12.1.4.SD:Project Orders WBS 12.1.4.1.SD:Create Sales Order Milestone Billing: - 13488: Proj A-10005 1PC 50000EUR for Cust 50005 12.3.2.2.3. Milestones: - Represents an Event in WBS hierarchy: 12.1.4.2.SD:Create Sales Order Resorce-related Billing: - PK:Auto ID - 13489: Mat=Testdriver1 1HR, 200EUR for Cust 50005 - Short text - An internal ActType = T-0005(TestDriver-0005) - Long text Price=100EUR/H is also created as: - Planned Date - SD:Marketable dummy material = Testdriver1, Standard price - Actual Date (if set, event is considered occoured) = 200EUR/H previously. - Can be refereced by several operations (eg. partial billing) - At a given WBS = A-10005-2(Special expenses), 12.3.2.2.4.Documentation: - Customer 50005 orders it 1HR amount - Linked to Document Management System (DMS) 12.1.4.3.FI:Credit Management|Release orders manually: - PS:SAP Script text, Word, Excel, CAD, etc. files - Cust50005 12.3.2.3.WBS functions (supports all planning process): 12.1.5.LO-PS:Project execution 12.3.2.3.1.Budgeting 12.1.5.1.LO-CO:Manual Actual cost Allocation: 12.3.2.3.2.Deadlines/Scheduling - CostCtr4290|ActTyp1429WBS:Blueprint 420H 12.3.2.3.3.Cost planning - CostCtr4290|ActTyp1430WBS:Blueprint 180H 12.3.2.3.4.Purchase Req.Order planning 12.1.5.2.LO-PS:Confirm&Release bill: 12.3.2.3.5.Revenue planning - WBS Blueprint 12.3.2.3.6.Payment/Billing planning 12.1.5.3.LO-PS:Auto entry Actual cost&Confirm&Bill: 12.3.2.3.7.Period end closing - Netw:Prototype| 12.3.2.3.8.Aggregated evaluation and reporting - Act:Specification=180HR 12.3.2.4.WBS GUI:Hierarchy Chart - Act:Construction=270HR - Horizontally aligned hierarchic block diagram 12.1.5.4.HCM:Project hours: - Displays selected WBS properties, which can be edited - CostCtr:4280|ActTyp:T-0005|Emp:9900005 - WBS:Special expenses 5×8HR 12.1.5.5.HCM:Transfer project hours to CO: - Emp:9900005 12.1.6.SD:Billing: 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 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, ID- UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 63 12.3.3.DEF: Network: 12.3.3.2.3.3.ALT:FF - Optional elements of project (Some of them have only WBS) - Ancestor(FinishDate)≤Successor(FinishDate) - Describing logistic process flow of the project with: 12.3.3.2.3.4.ALT:SF 12.3.3.1.Possible OrgLevels - Ancestor(StartDate)≤Successor(FinishDate) - BusiArea 12.3.3.2.4.DEF:Multi-networked projects - ProfCtr - When WBS Element|Activities are linked to more than one - Plant network with relationships 12.3.3.2.Network content: - LO-PS executes Critical Path Method (CPM)-type optimization 12.3.3.2.1.Header: to determine feasible start/finish dates of activities in all of the - FK:Company networks simultaneously - FK:ContrArea 12.3.3.3.Network functions: - FK:Plant 12.3.3.3.1.Budgeting - Network type and profile 12.3.3.3.2.Deadlines/Scheduling 12.3.3.2.2. Activities: 12.3.3.3.3.Cost planning - Represent process steps 12.3.3.3.4.Purchase Req. Order planning - Can be connected to: 12.3.3.3.5.Revenue planning - OPT:Netwok:Activity = m:m (max. m:500) with Relationships 12.3.3.3.6.Payment/Billing planning - OPT:WBS Element:Activity = 1:m directly in WBS hierarchy 12.3.3.3.7.Period end closing - Activity level costs are aggregated into WBS Element, checked 12.3.3.3.8.Aggregated evaluation and reporting against its budget 12.3.3.4.Network GUI:Network Structure Graphic - Only one activity per network can be processed simultaneosly in 12.3.3.4.1.FRM:Process flowchart SAP Network Manager! - Mouse drag&drop edit 12.3.3.2.2.1.PS:Activity Categories|Functions: - Process cycle checking function - Iternal processing 12.3.3.4.2.FRM:Activity details form - Deadline, 12.3.3.4.3.FRM:Insertable Activity template list - Cost 12.3.4.Related SD documents - FK:OrgLevel - Project is always related with: - BusiArea 12.3.4.1.DEF:Dummy material - ProfCtr - Material symbolizing result of the project - Plant 12.3.4.2.Sales Order - CostCtr - Assigns Customer to bill for a project - WrkCtr 12.4.PROC:LO-PS:Project: - External processing 12.4.1.Scheduling - Deadline, 12.4.1.1.WBS Elements: - Cost - Their dates are not strictly related as they are not connected - Purchase Requisition with relationships! - FK:OrgLevel 12.4.1.1.1.ALT:Manual entry: - PurchOrg - Project Start/End, WBS dates - PurchGrp 12.4.1.1.2.ALT:Inheritance of dates in hierarchy:top down - Plant 12.4.1.1.3.ALT:Extrapolation:down top - BuisArea 12.4.1.2.Networks: - ProfCtr - Auto-scheduled with CPM algorithm along relationship types - Service 12.4.1.2.1.Types: - Deadline, 12.4.1.2.1.1.Forward: - Cost - From earliest possible start date - Purchase Requisition - Of starting activities (no predessor) - FK:OrgLevel - Determines earliest start date of activities - PurchOrg 12.4.1.2.1.2.Backward: - PurchGrp - From latest possible end dates - Plant - Of closing activities (no successor) - BuisArea - Determines latest start date of activities - ProfCtr 12.4.1.2.2.Scope: - Material Components - Single network - Material number - Related networks - Required quantity - Related networks of WBS Element|Activity - Material Availability, 12.4.2.Resource and Cost planning - Purchase Requisition - Requests a certain budget for the project - FK:OrgLevel - Building it ip from down to top - PurchOrg 12.4.2.1.WBS Elements: - PurchGrp - Only manual cost planning - Plant 12.4.2.1.1.ALT:Overall hierarchic planning - Storage - Period|WBS|TotalCost - Miscellaneous costs 12.4.2.1.2.ALT:Detailed planning - Most of them are unplanned (eg. unexpected travel) - Period|WBS|CostElement|ActivityType|InputQuant 12.3.3.2.2.2.Activities can contain: 12.4.2.1.3.ALT:Unit Costing - Activity Elements - Period|WBS|CostElement|ActivityType|InputQuant×UnitPrice - For further detailing Activities 12.4.2.1.4.ALT:Easy Cost Planning Tool - Has the same Categories|Functions - Provides cost plant templates by - But cannot be connected with relationships - Period|WBS|CostElement|Quant×UnitPrice - Documentation: - From template or former projects - 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)
UniqueID, BTN-Button, TXB-Textbox, DDN-Dropdown, TAB-Pagetab, CHK/RAD-Check/Radiobox, LIN-Tableline, KEY-Hotkey, WRN/ERR-Warning/Errorbox Dr. Gábor Pauler |SAP TERP10 Notes |Date: 2013. 06. 25. PaulerSoft™ CANAL™ notes, page: 64 12.4.2.2.Networks: 12.4.5.2.1.2.ALT:Internal processing: - Automatic cost planning - Storage Reservation - Transferable to other project - Commit assigned project element 12.4.2.2.1.ALT:Internal Process - Record actual cost - WrkCtr| - It consumes from budget - ActType| - Production Order - Employee| - Goods Issue - Capacity, - Accounting doc debiting assigned project element - Planned output (Actual output will consume it) 12.4.5.2.2.Confirmation - Price - By any level of hierarchy Network|Activity|ActivityElement 12.4.2.2.2.ALT:External Process - Puts project element in Status = CNF(Confirmed) 12.4.2.2.2.1.Purchasing Info Record 12.4.5.2.2.1.ALT:Collective - Prices 12.4.5.2.2.2.ALT:Individual - Delivery times - ALT:Internal: Cross Application Time Sheet (CATS) 12.4.2.2.2.2.Purchase Requisition - ALT:Internet - Purchasing Group - ALT:From Palm/PocketPC - Material - ALT:Open PS interface - Quantity - ALT:Process data Capturing (PDC) inerface - Unit 12.4.6.Project Billing - Deadline 12.4.6.1.DEF:Milestone billing: 12.4.2.2.2.3.Purchase Order - When a project element closed with milestone is completed 12.4.2.2.2.4.Goods Receipt - Blocking status of partial bills are released 12.4.2.2.2.5.Invoice Receipt 12.4.6.2.DEF:Resource-related billing: 12.4.2.2.3.ALT:Services 12.4.6.2.1.DEF:Dummy material for resource-related billing - Same as external process, except at good receipt service has to - A previously created internal ActType be accepted - Is also created as SD:Marketable dummy material, even with 12.4.2.2.4.Material planning different, higher unit price! 12.4.3.Assigning Orders to project - It is assigned to a given WBS of project 12.4.3.1.WBS - And sold to the customer of the project in a given amount 12.4.3.1.1.SD:Sales Order - On a separate sales order from Sales Order of Project material: 12.4.3.2.Networks 12.4.6.2.2.DEF:Sales Order of Resource-related billing: 12.4.3.2.1.Assign to Network Header - Contains: 12.4.3.2.1.1.SD:Sales Order 12.4.6.2.2.1.DEF:Dynamic Items 12.4.3.2.2.Assign to Network Item - Non-fixed data (Dynamic) item of bills summarized during 12.4.3.2.2.1.CO:Internal Order billing process 12.4.3.2.2.2.PP:Production Order - May be influenced by differences of plan/actual at confirming 12.4.3.2.2.3.PM:Maintence Order billed activities 12.4.4.CYC:Budgeting Approval 12.4.6.2.2.2.Dynamic Item Processor (DIP) Profile: - Approves budget limit for the project - Controls their aggregation trough following (m:1) relations: - Breaking it up top to down - CATS|WorkHourEmployeeWBS| 12.4.4.1.Create original budget ActivityActTypAcTypGroupDIP ProfileDummy - Creates consistent budget hierarchy by material - Period|WBS|Original costs - Pricing condition PR00Dummy material - Determines rights of user groups to modify - Dummy materialSales OrderResource-related Bill 12.4.4.2.Budget update - Computes Resource-related Bill|Dynamic Item|Value = CATS| - Compares original WorkHour × Pricing condition PR00 - With budget consumers: - It does not use original ActTyp|Unit price for - Actually incurred costs computation! - Future commitments, orders 12.4.7.PS:Project Period end closing - Takes eavsive action: 12.4.7.1.DEF:Full credit/debit settlement of project 12.4.4.2.1.Supplement - Periodically settles costs, which are hard to relate to any activity 12.4.4.2.2.Return 12.4.7.1.1.Source data of costs/rebenues 12.4.4.2.3.Transfer - MM:Goods receipt, Stock withdrawal 12.4.4.3.Budget release - FI-AR: Vendor Invoices, 12.4.4.4.Budget carryforward between time periods - SD: Customer Billing 12.4.5.Project Execution - CO-OM: Activity allocations/assesments, Overheads 12.4.5.1.WBS|Activity and - PS: Confirmations 12.4.5.2.Network|Activity|ActivityElemt: 12.4.7.1.2.Setlement rule 12.4.5.2.1.Record document flows - Sender 12.4.5.2.1.1.ALT:External process/Service/Material: - Receivers - Purchase Requisition - Distribution percentages - Request vendor Quotation/Bid Invitation - Type: - Quotation Entry - Direct:Project elemnt is settled against a cost object directly - Vendor selection - Multiple:Project element is settled with its superior project - Commit assigned project element element with assigned cost object - Record actual cost 12.4.7.1.3.Receivers can be - It consumes from budget - FI-GL:G/L Accoutnts - Purchase Order - FI-AA:Assets - Goods Receipt - CO-PA:Profit cost bjects - At service:Entry - LO-PS:Other projects - At service:Acceptance - Invoice receipt/verifivation - Accounting doc debiting assigned project element - ALT:Automatic by project structure - ALT:Manual entry for special expenses