Interface Certification Based on ICC Integration Assessment Test Report SAP Integration and Certification Center SAP Integration and Certification Center Page 1
2013 SAP AG. All rights reserved. No part of this publication 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. All other product and service names mentioned are the trademarks of their respective companies. Please refer to http://www.sap.com/corporateen/legal/copyright/index.epx Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. SAP Integration and Certification Center Page 2
Interface Certification #30330988 SAP Interface incl. Release: Based on ICC Integration Assessment SAP Product incl. Release used for test: SAP ERP 6.0 Hardware used for SAP test system: PC-Pentium, x64 Operating System of SAP test system: Windows 7 Name of Vendor: AdapChain Inc Vendor Number (SAP internal): 12869575 Vendor Product Name: AdapLink Objects Release Vendor Product: 3.0 Vendor Product Number (SAP internal): 9257937 Vendor Interface Software Name: AdapLink Objects Release Vendor Interface Software: 3.0 Hardware used for Vendor Test System: PC-Pentium Operating System of Vendor Test System: Windows 7 Tools used for the technical integration: SAP Connector JCo 3.0 Certification Date: November 21, 2014 Expiration Date: November 20, 2017 Location: Bangalore Building / Room: SAP Labs Remote via SAP Connect Persons present - Vendor: Ranjan MR Persons present - SAP: Saathvik K V Certified Functions: Upload planned supply data to SAP through BAPIs Upload planned independent demand data to SAP through BAPIs Extract Supply Chain data (Master Data,Firm Demand, Firm Supply,Planned Orders, Planned Supply) from SAP through BAPIs Compile planning situation overview in Excel worksheet based on SAP data SAP Solution Manager Ready SAP Integration and Certification Center Page 3
1. Vendor Company and Product Information Product information Product web page: Which releases of the SAP Business Solutions does the third-party s software support? Please name the corresponding version of the software. www.adapchain.com SAP ERP 6.0 corresponding version of vendor product: 3.0 other corresponding version of vendor product: For which databases is the software available? Not Applicable On which server platform(s) does the software run? All Windows Platform from XP onwards 2. Functional Overview Supported Functions and Business Processes General Description Overview on the functionality and the purpose of the thirdparty product. AdapLink Objects for SAP are object oriented representations of complex SAP data objects like materials master, or sales and production orders. AdapLink Objects are designed to provide access to the rich underlying data in the many ways organizations want to consume them through a representation that is easy to implement, install and support. All AdapLink Objects share three key features. They are Intuitive, Comprehensive, and Delta-capable. 1. Intuitive: All elements and attributes are named based on a combination of natural and technical language. As an example, the technical field name containing the material number in an SAP object is typically MATNR. In the AdapLink Object this is named Material_MATNR, mixing natural language with SAP technical terms. Through this naming convention it becomes intuitively obvious what the data represents (the Material) and how it relates to the technical SAP architecture (field MATNR). 2. Comprehensive: As AdapChain creates new objects they are designed to include all the data relevant to the SAP object, not just what is required for a particular scenario. By designing the objects with a comprehensive mindset the objects can be used in many different integration scenarios without modification. This is the key to ensuring consistent high quality and plug-and-play implementation. 3. Delta-Capable: AdapLink Objects are designed to track the underlying SAP through their life cycle from initial object creation, through ongoing object maintenance to deletion. No need to worry about AdapLink Objects getting out of sync with the underlying SAP data. SAP Integration and Certification Center Page 4
How it benefits our customers and complements SAP? 1. AdapLink Objects are designed to be easy to integrate with. By leveraging AdapLink Objects organization achieve solutions that are easier to understand, easier to maintain and perform at much high level compared to in-house developed solutions integrated directly to SAP without the use of AdapLink Objects. 2. AdapChain leverages our growing list of AdapLink Objects when constructing integration templates for integration between SAP and non-sap systems. Visit the AdapChain partner listing to see who has developed system integrated through AdapLink Integration templates based on AdapLink Objects. http://adapchain.com/partners How are organizations using AdapLink Objects for SAP Integration? Organizations use AdapLink Objects for integration of SAP ECC to non- SAP system in two ways. 1. Custom integration: Some organizations leverage AdapLink Objects as the starting point for custom integration projects. By leveraging AdapLink Objects they reduce implementation time, resource requirements, solution complexity and ultimately cost of ownership compared to building custom integration all the way back into SAP. Template integration: AdapChain is collaborating with leading 3rd-party software companies in standardizing integration between their applications and the rich SAP ECC source systems. Starting an integration effort with an AdapLink Integration Template is like starting with the integration already 80% done. Only the business specific field mappings remain. the finalto develop integration between functionality rich and comprehensive systems it is critically important to understand how the required data is stored in the underlying systems. ERP systems will often hold thousands of database tables containing tens of thousands of fields. To develop integration it is necessary to understand what structures and fields are relevant to the integration task. This level of domain expertise can be hard to find. Integration Technology Use of SAP s Integration Technologies SAP Business Application Programming Interfaces (BAPIs): yes BAPI_MATERIAL_STOCK_REQ_LIST BAPI_REQUIREMENTS_GETDETAIL BAPI_REQUIREMENTS_CHANGE BAPI_REQUIREMENTS_CREATE BAPI_MATERIAL_GETALL BAPI_PLANNEDORDER_GET_DET_LIST SAP Integration and Certification Center Page 5
Remote Function Call (RFC): Yes If you use RFC, what kind of functions do you use? No Customer-released RFCs by SAP according to ABAP Workbench transaction SE37 Self-developed RFCs Others BAPI_PLANNEDORDER_GET_DET_LIST BAPI_PLANNEDORDER_DELETE BAPI_PLANNEDORDER_DELETE BAPI_PLANNEDORDER_CREATE BAPI_PLANNEDORDER_CREATE (End-user developed RFCs) SAP Intermediate Documents (IDocs) via EDI or Application Link Enabling (ALE). If you use IDocs, what kind of IDocs do you use? Standard Idocs created by SAP and sent as messages by standard SAP components according to transaction WE81 Extended or self-developed IDocs Others yes No (End-user developed IDocs) 3. Performance 3.1 Performance and Scalability Overview on the architecture and design of the third-party product including performance and scalability. AdapLink is AdapChain s proprietary Rules Based integration and data management tool and a key element in our service oriented business model. AdapChain through AdapLink, is able to resolve Data Management and Integration challenges faced in many projects with a level of quality, speed, and cost effectiveness that few have imagined possible. Rules Based AdapLink toolset offers high performance interfaces to connect and transform data from different systems and platforms. At the heart of the platform is the business-rules-engine that has incrementally been improved through more than 15 years of R&D and customers / partners feedback. AdapLink is developed under Service-client model. SAP Integration and Certification Center Page 6
3.2 Quality Assurance Overview on Quality Assurance procedures by the third-party vendor to assure that the interface design and performance consistently conform to specified requirements. AdapLink has been developed under standard software practices complying to strict software quality that assures that the standards, processes, and procedures are appropriate for the project and are correctly implemented. Adapchain follows Process improvement approach to software development, called AdapWay methodolgy. A breif outline on Adapway Methodology. What is the AdapWay? AdapChain Inc. created the AdapWay in order to eliminate 3 of the 4 biggest waste categories often experienced during implementation of software Projects: Opportunity Waste, Realization Waste and Business Performance Waste. The result is a methodology that not only eliminates those waste categories, but also delivers a number of other tangible benefits: Low cost: Small project teams mean low project burn rate and minimal impact of business operations. Early benefits, Low risk: Iterative implementation approach ensures focus, minimal implementation risk and early realization of tangible business benefits. SAP Integration and Certification Center Page 7
Superior change management: By ensuring direct involvement of key users in design and testing, change management is rarely a problem. The AdapWay is continuously being enhanced by AdapChain Inc. AdapWay Lab-to-Live (LTL) methodology Each LTL-iteration defined during the Exploration phase is a small project. The scope is clearly defined and typically limited to the smallest amount of additional scope that will deliver noticeable value towards meeting the business need. By keeping the scope of each LTL-iteration small, it becomes natural that the project team size also will be small and the implementation time normally will be less than 4 months. During the LTL iteration, a full-scale prototype is built in a test environment. This full-scale prototype is kept aligned with production through periodic imports of relevant production data. By keeping the prototype updated with production data it is possible to see if the prototype design is producing results similar or better than the official production system. The LTL environment allows the LTL-team to test design changes on full scale data. Because the LTL environment contains current data,it is fairly easy to keep supply chain planners from the business involved in the effort. And while business users work on testing and improving the model, they also learn the new functionality. This makes change management MUCH easier. AdapWay Sustain and improve: Once an LTL iteration has been completed and implemented, the scope is transferred to the sustain and improve phase. During sustain and improve, the focus is on eliminating errors and SAP Integration and Certification Center Page 8
finding additional improvement opportunities. These opportunities may then be added to a subsequent LTL iteration, result in a new LTL iteration or be noted and eliminated. 4. Software Product Assessment 4.1 Review Existing Documentation Functional Documentation yes Comments: Installation Documentation yes Comments: Maintenance Documentation yes Comments: End User Documentation yes Comments: Test Plan Documentation yes Comments: Test Report Documentation yes Comments: Included in Test Plan Documentation Benchmark Results Documentation yes Comments: Not Applicable 4.2 Install and Configure Product for SAP Integration How is the installation and setup of the product integration part done? Remarks good average poor 5. Test Cases 5.1 Test steps executed during Test-Drive 5.1.1 Test case - 01 : Get Material and its description from SAP OK 5.1.2 Test case - 02 : Get "Current Inventory" from SAP OK 5.1.3 Test case - 03 : Get "Firm Demand" from SAP OK 5.1.4 Test case - 04 : Get "Firm Supply" from SAP OK 5.1.5 Test case - 05 : A simple scenario explaining Supply Planning and Demand Planning OK SAP Integration and Certification Center Page 9
5.1.6 Test case - 06 : Create PIR's and Planned orders in SAP OK 5.2 Performance load test steps executed during Test-Drive Not Applicable 6. Additional Service and Support Does the third-party vendor offer consulting services for this product? Remarks yes no Does the third-party vendor offer training classes for this product? Remarks yes no Does the third-party vendor offer general problem support for this product? Remarks yes no 7. Vendor Confirmation Vendor states that by following the guidelines of the ICC Integration Assessment or ICC Integration Guide, only the integration technologies listed in this document and in the Technical Product Profile are used in the described interface software. Certification is only valid for the SAP release and vendor product release noted in this document; in the event of SAP component or third-party product release changes SAP offers re-certification of the interface software. SAP Integration and Certification Center Page 10