QuantityWare BCP 3.0 Implementation in Legacy Environments. Implementation Project Guidelines and Check List. Documentation of Activities

Transcription

1 QuantityWare BCP 3.0 Implementation in Legacy Environments Implementation Project Guidelines and Check List Documentation of Activities

2 Notes: Copyright 2017 QuantityWare GmbH. All rights reserved. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Microsoft, Windows, SQL-Server, Powerpoint and Outlook are registered trademarks of Microsoft Corporation. These materials and the information therein are subject to change without notice. These materials are provided by the company QuantityWare GmbH for informational purposes only. There is no implied representation or warranty of any kind, and QuantityWare GmbH shall not be liable for errors or omissions with respect to the materials provided. The only warranties for the products and services of QuantityWare GmbH are those set forth in the express warranty statements accompanying such products and services, if any. No statement within this document should be construed as constituting an additional warranty. Valid for BCS 3.0 Technical Releases: SAP Release BCS Release CSP Level ECC A 001 S/4HANA B 000 S/4HANA B 000 tba tba tba Your release level can be determined via: /o/qtyw/cockpit -> Cockpit -> Support Package Level BCP Implementation in Legacy Environments 2-15

3 Contents QUANTITYWARE BCP 3.0 IMPLEMENTATION IN LEGACY ENVIRONMENTS... 1 IMPLEMENTATION PROJECT GUIDELINES AND CHECK LIST... 1 Notes:... 2 Contents... 3 Introduction... 4 API C to QuantityWare ABAP - Migration Project Methodology... 6 Summary Appendix A Flow Chart Appendix B GANTT Project Plan Appendix C C to ABAP - Conversion Group Mapping Table BCP Implementation in Legacy Environments 3-15

4 Introduction How can a QuantityWare BCP customer easily migrate its legacy quantity conversion calculations (e.g. API c-code implementation) to the QuantityWare BCP solution? QuantityWare BCP customers fall into two categories: Type 1: Customers performing a new ERP installation with QuantityWare BCP - "Greenfield Project" Type 2: Customers adding QuantityWare BCP to their existing ERP system which already contains a legacy quantity conversion solution (e.g. with API c-codes in place) - "Brownfield Project" Type 2 customers may run their legacy quantity conversion solution in parallel with their new QuantityWare BCP solution. This flexibility is enabled by the fundamental SAP design: A conversion group is assigned to an SAP material, the conversion group defines which quantity conversion solution is utilized for the complex oil & gas conversion. Since QuantityWare delivers QuantityWare own conversion groups in a new, dedicated template client, existing material conversion group configurations are not affected by the installation of QuantityWare BCP. Type 1 customers typically have expert consultants (ideally certified QuantityWare BCP Consultants) available during the implementation project who follow the proven QuantityWare BCP Project Assessment and Implementation Guidelines. Type 2 customers typically consider QuantityWare BCP usage owing to the fact that their legacy quantity conversion routines do not fill new requirements the customer requires support for additional measurement standards, e.g. for Asphalt or LPG products. In this case, BCP implementation for new products should also follow the BCP Project Assessment and Implementation Guidelines while no special attention has to be paid to the legacy conversion group configuration and implementation. Another motivational reason for Type 2 customers to implement the QuantityWare BCP solution is a strategic decision to replace their existing legacy quantity conversion routines as part of a business process renovation project with targets in the field of quantity conversions such as: BCP Implementation in Legacy Environments 4-15

5 Legal compliance ROI extension Definition of business Best Practices Introduce transparency of all calculation data GRC support at a fundamental level Or, Type 2 customers may run into the situation that their legacy API c-code implementation stops working, e.g. due to hardware / OS changes of their system landscape. For these two types of projects (strategic replacement or emergency replacement), QuantityWare provides a clear and simple migration project methodology, which utilizes the QuantityWare BCP Petroleum Measurement Cockpit to easily accomplish implementation with a minimum effort and a maximum of quality assurance. This migration project methodology can be divided into two major project steps: The methodology described in the CTP (Compliance and Transparency Petroleum) PAIG documentation the recommended first phase of the migration project The methodology defined in this document Migration from API C to QuantityWare ABAP the second phase once the decision has been made to replace legacy c-code implementations QuantityWare has validated that the BCP - ABAP based - ASTM D calculation results are identical when compared with the legacy API c-code results, and documented the validation results in a working paper available in our Knowledge Base at BCP Implementation in Legacy Environments 5-15

6 API C to QuantityWare ABAP - Migration Project Methodology The QuantityWare Petroleum Measurement Cockpit contains a sophisticated and unique Test Scenario Tool, which enables the definition of thousands of single automated test scenarios based on a conversion group. Details on the Test Scenario Tool can be found in the CTP or BCP Documentation Reference Manual. When deciding to replace your legacy quantity conversion solution with BCP, simply install BCP in your development system and perform the following high-level 10-point plan: (The average effort estimates for each step are based on project experience) 1. Validation Definition Development: Hours - Depending on number of conversion groups defined for your legacy quantity conversion Define 20 to 50 test scenarios in your development system for each legacy conversion group since the results must have been validated beforehand, simply utilize the actual results as expected results. If your legacy (e.g. API c-code) implementation is no longer working -> use quantity conversion data from your productive system to define these scenarios and proceed with step 3 If you have already performed a CTP (Compliance and Transparency Petroleum) PAIG project where test scenarios have already been defined in your systems - proceed with step 3 BCP Implementation in Legacy Environments 6-15

7 2. Run Validation Development: 15 Minutes Run the test scenarios in your development system. All lights should be green. 3. Use Migration Tool Development: 15 Minutes - 8 Hours (Depending on complexity - SAP legacy standard utilized for legacy conversion groups are simple and fast, customer-specific conversion groups take longer). Use the QuantityWare BCP Migration Tool (accessible via the Petroleum Measurement Cockpit) to change the configuration of your legacy quantity conversion - conversion groups to the appropriate QuantityWare BCP conversion group - Read Appendix C for manual mapping information. BCP Implementation in Legacy Environments 7-15

8 4. Run Validation Development 15 Minutes 16 Hours (from no issues, to complex issue resolution) Run the test scenarios in your development system. All lights should be green, since QuantityWare conversion groups are validated to produce the identical results as with e.g. the API c-codes. If errors are encountered, they can be readily analyzed and rectified by petroleum measurement experts in conjunction with application team members. BCP Implementation in Legacy Environments 8-15

9 5. Validation & Install BCP Quality Assurance 2 Hours 16 Hours (from no issues, to complex issue resolution) Now that the migration has been successfully performed in your development system, install BCP, transport and run the proven test scenarios into your QAS (Quality Assurance System). All test scenario results should be green. If errors are encountered, they can be readily analysed and rectified by the petroleum measurement experts of the consulting team. The most probable cause of any error detected at this stage will be pre-existing basic configuration mismatches between Development and the QAS. If all test scenario results are green, and import new conversion group configuration from development to your QAS. 6. Run Validation Quality Assurance 15 Minutes Run the test scenarios in your quality assurance system. All results should be green. 7. Define Plan Production Time required dependent on internal processes Define cutover day and time for the production system switch and organise a production system backup (snapshot). 8. Install BCP & Transport Test Scenarios Production 2 Hours Now that the migration has been successfully completed in your quality assurance system, at the pre-defined time, BCP must be installed in production and the proven test scenarios imported. 9. Run Validation Production 15 Minutes Run the test scenarios in your production system. All results should be green. If this is not the case, there is a fundamental inconsistency in the existing QAS / production configuration. This is a serious situation which is not usually expected and must be resolved using your standard landscape and project GRC procedures. 10. Transport Settings - Production 15 Minutes Transport the new conversion group configuration to production in a small downtime and run the Test scenarios in your production system again. All lights will be green. BCP Implementation in Legacy Environments 9-15

10 Congratulations! You have successfully converted your legacy quantity conversion solution to QuantityWare BCP. BCP Implementation in Legacy Environments 10-15

11 Summary In an SAP Oil & Gas system, it is possible to migrate standard API C bulk material calculations to QuantityWare BCP calculations, in around five days elapsed time, increasing transparency, security, reliability and enforcing GRC. In this document we have, at a high level, described the proven project methodology which can be used to migrate your legacy quantity conversion solution to the QuantityWare BCP quantity conversion solution. Detailed effort estimates are provided in a template project GANTT chart (Appendix). In this project, the quality and flexibility of the QuantityWare Petroleum Measurement Test Scenario Tool is leveraged to allow execution based upon four major motivators : Simplicity Transparency Quality assurance Future proofing BCP Implementation in Legacy Environments 11-15

12 Appendix A Flow Chart SAP Oil&Gas Customer using API C external calculation routines for bulk calculation movements QuantityWare BCP/BCG usage? No In-house staffing, design, development, validation, maintenance, re-engineering, restaffing (cyclic process) Calculation standard requirements: - Change / must be extended - Demand transparency, GRC compliance - OR calculations stop working Yes Basis & Application representatives study comprehensive Documentation, Install BCP/BCG and Implement via: Learning by doing Attend training classes (recommended) Using QW certified consultants (recommended) No All material / standards / GRC / Transparency requirements satisfied? Using QuantityWare project plan, tools and partner consulting; perform safe passage project to convert existing configuration to use QuantityWare standard implementation. (NO MASS DATA CONVERSION REQUIRED.) Existing Standards / materials / processes to be supported? New Yes Configure new materials to use new standard or process, Test, Implement through all systems. EXISTING CONFIGURATION AND MATERIALS REMAIN UNCHANGED Yes Leverage benefits seen in new configuration for existing materials? No Changing Requirements? E.g. new standards, materials, GRC Yes No Target achieved - All requirements fulfilled, secured via QuantityWare Maintenance Future proof through QuantityWare BCS BCP Implementation in Legacy Environments 12-15

13 Appendix B GANTT Project Plan In the Knowledge Base at a PDF-format high-level GANTT time-line for the project is available. The plan must be amended for customer lead-times and internal procedures. It defines the minimum time example required in a procedurally low-overhead organization. The timelines are identical between BCP 10B and BCP 3.0. The original Microsoft Project file can be downloaded from the QuantityWare support portal DataLounge -area. BCP Implementation in Legacy Environments 13-15

14 Appendix C C to ABAP - Conversion Group Mapping Table The QuantityWare BCP C to ABAP Migration Tool is designed to automatically map and convert SAP template "C" conversion groups to the corresponding QuantityWare ABAP conversion groups (configuration change). If customers utilize their own Z* "C" conversion groups, this mapping and conversion needs to be done manually, still following the migration methodology described in this document methodology. To support the manual process, the following table provides the mapping of the template conversion groups (C to ABAP): SAP QCI legacy API C QuantityWare SAP QCI "German rounding" Relative Density, 60 F: 234A 60RA 234B 60RB 234C 60RC 234D 60RD Q105 Q109 Q205 Q209 Q303 Q307 Q405 Q409 Density, 15 C: 534A Q100 Q101 15DA Q B Q200 Q201 15DB 534C 15DC Q206 Q300 Q D Q400 Q401 15DD Q406 API Gravity, 60 F: 56A 60GA 56B Q104 Q108 Q204 BCP Implementation in Legacy Environments 14-15

15 60GB 56C 60GC 56D 60GD Q208 Q302 Q306 Q404 Q408 Density, 20 C: 596A Q102 Q103 20DA Q B Q202 Q203 20DB 596C 20DC Q207 Q301 Q D Q402 Q403 20DD Q407 Read QuantityWare notes and for additional details. BCP Implementation in Legacy Environments 15-15