Extractioncockpit

7,076 views

Published on

Published in: Education, Technology, Sports
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
7,076
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
122
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • You can select the level of detail that is needed to cover reporting requirements. Characteristics from higher levels are also written on the lower levels (e.g. Customer is also written to item-level) Key-Figures will only be written on the level where they are related to (e.g. number of orders is only available in the extract structure for header data) Thus if you need only header key-figures you do not need to extract line item information. Extract-Structures and DataSources are delivered with the Standard Business Content If customer requirements can be covered with any of those existing DataSources you only have to activate: DataSource (Business Content Activation) Extract Structure (LO Extraction Cockpit) V3-Update (LO Extraction Cockpit)
  • OSS-Note 121196: Due to technical restriction it is not possible to update S261/S263 with V2-Update mode, if the picking is done at the time the document is saved (same LUW).
  • Events are just shown for your information to give a better understanding about what will be updated at what point in time, i.e. there is no customizing on event-level
  • For the allocation extract-structures in SD the selectable fields are limited to fields available in the order and the delivery. Therefore it does not make sense to enhance these extract-structures! Fields will also be hidden in other applications if: partly not filled at the event used only for internal purposes
  • Appends have to be assigned to customer development classes which have to be assigned to the right transport layer.
  • Extractioncockpit

    1. 1. Logistics Extraction Cockpit Nicolai Unterbarnscheidt BW RIG Europe SAP AG© SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 1
    2. 2. Content  Overview What is the LO Extraction Cockpit?  Advantages / Implications Why do we need it?  Procedure How does it work?  Tracking How can I check the data flow?  Caveats Migration How to get there?  Availability When is it available? (R/3, BW) Which applications are supported? © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 2
    3. 3. Overview© SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 3
    4. 4. What is the Logistics Extraction Cockpit?  New technique to extract logistics information  Consists of new  Standard Extract Structures  Standard DataSources © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 4
    5. 5. Comparison: LIS vs LO Extraction Cockpit BW BW old new Initial-Load Delta-Load Initial-Load Delta-Load R/3 R/3 ClusterInfostructure Tables S260 S260BIW1 MC11VA0ITMSETUP Delta-Queue S260BIW2 V3 Update Statistical V1 / V2 Job Setup Update Statistical Update Setup QueueInterface MCVBAK Interface MCVBAK MCVBAP MCVBAPApplication Application Sales Order VBAP Sales Order VBAP VBAK VBAK © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 5
    6. 6. Communication Structures for reporting purposes Application Database VBAP Sales VBAK Order VBEP Memory Copy Comm.Struct’s MCVBAK MCVBAP MCVBEP © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 6
    7. 7. DataFlow with new logistics extractionSales Comm. ExtractDocument Structure Structure Data/ InfoSource Cubes & Queries MC11VA0HDR 2LIS_11_VAHDR Sales MCVBAK MC11VA0ITM 2LIS_11_VAITM MC11VA0SCL 2LIS_11_VASCL 0SD_C04 Order ... MC11V_0ITM 2LIS_11_V_ITM 0SD_C04 MC11V_0SCL 2LIS_11_V_SCL 0SD_C05 MCLIKP MC12VC0HDR 2LIS_12_VCHDRDelivery ... MC12VC0ITM 2LIS_12_VCITM 0SD_C03 MC12VC0SCL 2LIS_12_VCSCL MCVBRK MC13VD0HDR 2LIS_13_VDHDR Invoice ... MC13VD0ITM 2LIS_13_VDITM R/3 BW © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 7
    8. 8. Comparison: Content of Extraction (SD-Example)Old A - - A - - - - - Header 2LIS_01_S260 A B - - B B - - - Item A B C - - - C C C ScheduleNew 2LIS_11_VAHDR A A Header 2LIS_11_VAITM A B B B Item 2LIS_11_VASCL A B C C C C Schedule © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 8
    9. 9. Benefits© SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 9
    10. 10. Benefits Performance & Usability Volume Benefits Logistics No LIS- Solution Functionality © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 10
    11. 11. Benefits (1) : Performance & Volume Detailed Extraction Extraction can be deactivated (e.g. Schedule Line Data) leads to leaner extractors with less volume Document Changes only BW-relevant data changes will be updated (less upload volume) LIS-Tables are not updated reduced data volume due to avoided redundancy Update with Batch-Process (V3) no load on daily business © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 11
    12. 12. Benefits (2) : Usability No LIS-Functionality no LIS-Know How necessary Functional Enhancements easy to be done LO Extraction Cockpit: central, uniform maintenance tool for logistics applications © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 12
    13. 13. Benefits (3) : Others No (Design-)Problems with transfer-structures no technical restrictions as in LIS (SAPNet-Note 121196) No Delta-Tables (SnnnBIW1/-2) no double update, no double Data-Storage © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 13
    14. 14. Procedure© SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 14
    15. 15. How does it work in general? Procedure 1. Activate DataSource 2. Maintain Extract Structure  (you cannot create new Extract Structures!) 3. Generate DataSource / Repl. DataSource 4. Activate Extract Structure  5. Delete Setup tables  6. Check Extractor Update (optional)  7. Perform Extractor Setup 8. Define periodic V3 update jobs . Create InfoPackage in BW for initialization .. Create InfoPackage in BW for periodic Delta 9. Delete Initialization Table ‘LBWG’ © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 15
    16. 16. Select the Level of detail  Communication-Structure Extract-Structure Field-ContentHeaderLevel MCVBAK MC11VA0HDR ItemLevel MCVBAP 1 2 3 4 5 6 7 MC11VA0ITM 1 2 3 4 5 ScheduleLine MCVBEP MC11VA0SCL © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 16
    17. 17. Logistics Extraction Cockpit  Maintain ExtractStructure  Generate DataSource   Activate ExtractStructure     Schedule Delta-Update    © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 17
    18. 18. Select relevant field-content Communication-Structure Extract-Structure Field-Content ItemLevel MCVBAP 1 2 3 4 5 6 7 MC11VA0ITM 1 2 3 4 5 6 © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 18
    19. 19. Field Selection for Extract-Structure   Grouped by Communication structure (CS)  SAP Standard Extract Structures can be enhanced (user appends on CS are available here)  Missing fields like units and compound characteristics will be filled automatically © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 19
    20. 20. Enhancements of Extract-Structures (2 Options)  Take existing fields from the  Use the User-Exit to fill your communication structure own fields  go to the customizing cockpit  add your fields to an append structure in the appropriate  maintain extract-structure Communication Structure  select the fields from the different  Identify the appropriate user-exit catalogs on the right hand side for filling the fields  move the fields to the extract- e.g. MCS10001 for Sales Orders structure on the left hand side  now the fields will also be  save your settings available in the customizing cockpit and you can therefore  system automatically creates an proceed with the steps on the left append to the delivered extract- side structure which contains the selected fields  Generate DataSource again  Reactivate Extract-Structure © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 20
    21. 21. Batch-Job to make data available for BW Background System collects data for later processing to avoid heavy load during business hours Job needs to be scheduled to define when collected data shell be processed Only processed data can be accessed by BW parallel postings possible Actions  Define job parameters  Schedule batch jobs for updating Extract Structure  DataSource © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 21
    22. 22. Batch-Job to make data available for BW Considerations  Need to be specified per application (e.g. Sales Order Processing)  Can run as often as deltas are required in BW (or more often)  Has to be finished before delta-extraction can be started in BW It might be reasonable to trigger extraction from R/3 (note:135637 )  Consider impacts on the size of ARFC-Buffer  V3 Update is not used for the initialization Stability  During the Job runs DB-Commits will be performed every 1000 calls  i.e. if the system crashes there will always be a rollback  If an error occurs during the update to the delta-queue no Log is written  the only error which has occured so far is due to extract-stucture changes (see Caveats) © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 22
    23. 23. Tracking© SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 23
    24. 24. Tools to check the data flow Data Updates  Simulation  Some Applications support Logs for Setup (e.g. SD)  Extraction Log  Log for last processed Document User Parameter: MCL=X Transaction : LBWF (shows the data being updated) Data-Queues  Update Queue  Transaction : SM13 (shows the data being updated) Doubleclick on MCEX_UPDATE_XX to see data  Delta Queue  Transaction: RSA7 (shows to be transfered data (delta) for a DataSource and a Targetsystem) Mark a line and press F2 to see data © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 24
    25. 25. Simulation Data Initialization / Simulation • Simulation: No Setup ! Check of ES LBWF: © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 25
    26. 26. Extraction Log User parameter MCL = ‚X‘ Log will be updated from the last processed document Log is written per user Transaction : LBWF (shows the data being updated) © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 26
    27. 27. Update Queue (SM13) 1. Double Click 4. View Data 2. Display 3. Double Click © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 27
    28. 28. Delta-Queue (RSA7) Mark a line and press this button View RFC-Data © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 28
    29. 29. Caveats© SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 29
    30. 30. Caveats Notes Solution  Incorrect DataSource  First activate DataSource before you customize  Difficulties when deleting  Apply PI 2000.1 Patch 3 append structure  No user defined fields  Apply PI 2000.1 Patch 3 available  Activation terminates after  Apply PI 2000.1 Patch 3 assignment of new fields  be careful with SD-  consider Notes Initialization in Batch 201207, 328534 © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 30
    31. 31. Caveats  Change to Extract Structure during operation (Note: 328181)  avoid postings / updates during the following changes  empty update-queue (SM13) with V3-Update-Job  empty Delta-Queue (RSA7) by extracting data  change extract structure  data of a former initialization run cannot be used anymore (delete data with LBWG and perform a new initialization if necessary)  old extraction log is no longer available  Multiple usage of units in Extract Structure - SD (Note: 316288) © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 31
    32. 32. Additional Information (Links)  Migration from LIS (BW and R/3) http://service.sap.com/~sapidb/011000358700007450782000E  Whitepaper for Logistic Customizing Cockpit http://service.sap.com/~sapidb/011000358700009061692000E © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 32
    33. 33. Availability© SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 33
    34. 34. Available for ... R/3 4.0B R/3 4.5B R/3 4.6B PI 2000.1 R/3 4.6C SP3 ...  Relevant for V3 Update  Requires certain Support Package-Level on R/3 dependent on the R/3 Release  An application might require an additional implementation of a SAPNet- Note © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 34
    35. 35. Availability of S2xx-Structures R/3 3.1x R/3 4.x  will be supported until 2003  Supports S2xx-Structures and Logistics Extraction Cockpit in parallel  does only contain S2xx-Structures  S2xx-Structures will be replaced by Logistics Extraction Cockpit with Plug-In 2001.2 © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 35
    36. 36. Supported Applications - DataSources (PI 2000.1) Purchasing (02) 2LIS_02_HDR Purchasing Data (Header Level) 2LIS_02_ITM Purchasing Data (Item Level) 2LIS_02_SCL Purchasing Data (Schedule Line Level) Inventory Controlling (3) 2LIS_03_BF Material Movements 2LIS_03_UM Revaluations Shop Floor Control (4) 2LIS_04_PEARBPL Reporting Points 2LIS_04_PECOMP REM Component View 2LIS_04_PEMATNR REM Material View 2LIS_04_P_ARBPL Work Center View PP 2LIS_04_P_COMP Component View PP 2LIS_04_P_MATNR Material View PP(PI) Quality Management (5) 2LIS_05_Q0ACTY Quality Notifications - Activities 2LIS_05_Q0CAUSE Quality Notifications - Causes 2LIS_05_Q0ITEM Quality Notifications - Items 2LIS_05_Q0NOTIF Quality Notifications 2LIS_05_Q0TASK Quality Notifications - Tasks 2LIS_05_QE1 Inspection result: General data 2LIS_05_QE2 Inspection result: Quantitative data © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 36
    37. 37. Supported Applications - DataSources (PI 2000.1) Shipment (8) 2LIS_08TRFKP Shipment Costs at Item Level 2LIS_08TRFKZ Shipment Costs at Delivery Item Level 2LIS_08TRTK Shipment: Header Data 2LIS_08TRTLP Shipment: Delivery Item Data per Section 2LIS_08TRTS Shipment: Section Data Sales (11) 2LIS_11_VAHDR Sales Document Header 2LIS_11_VAITM Sales Document Item 2LIS_11_VASCL Sales Document Schedule Line 2LIS_11_V_ITM Sales-Shipping Allocation Item Data 2LIS_11_V_SCL Sales-Shipping Allocation Schedule Line Shipping (12) 2LIS_12_VCHDR Delivery Header Data 2LIS_12_VCITM Delivery Item Data 2LIS_12_VCSCL Sales-Shipping Schedule Line Delivery Billing (13) 2LIS_13_VDHDR Billing Doc. Header Data 2LIS_13_VDITM Billing Document Item Data © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 37
    38. 38. Supported Applications - DataSources (PI 2000.1) Plant Maintenance (17) 2LIS_17_I0ACTY Maintenance Notifications - Activities 2LIS_17_I0CAUSE Maintenance Notifications - Causes 2LIS_17_I0ITEM Maintenance Notifications - Items 2LIS_17_I0NOTIF Maintenance Notifications 2LIS_17_I0TASK Maintenance Notifications - Tasks Customer Service (18) 2LIS_18_I0ACTY Service Notifications - Activities 2LIS_18_I0CAUSE Service Notifications - Causes 2LIS_18_I0ITEM Service Notifications - Items 2LIS_18_I0NOTIF Service Notifications 2LIS_18_I0TASK Service Notifications – Tasks Retailing (40) 2LIS_40_REVAL Revaluation at Retail Retail POS Cashier (43) 2LIS_43_POSCAS POS Data: Cashier Retail POS Receipts (44) 2LIS_44_POSREC POS Data: Receipt Data © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 38
    39. 39. Copyright 2000 SAP AG (All rights reserved)  No part of this brochure may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.  Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.  Microsoft®, WINDOWS®, NT®, EXCEL®, Word® and SQL Server® are registered trademarks of Microsoft Corporation.  IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.  ORACLE® is a registered trademark of ORACLE Corporation, California, USA.  INFORMIX®-OnLine for SAP is a registered trademark of Informix Software Incorporated.  UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of The Open Group.  HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute of Technology, 545 Technology Square, Cambridge, MA 02139.  JAVA® is a registered trademark of Sun Microssystems, Inc. , 901 San Antonio Road, Palo Alto, CA 94303 USA.  JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.  SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.com Business Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP, SAP Business Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, Management Cockpit, SEM, are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies. © SAP AG 2000 LO Extraction Cockpit (Nicolai Unterbarnscheidt BW RIG Europe) / 39

    ×