Académique Documents
Professionnel Documents
Culture Documents
Contents
Overview of Electronic Data Interchange (EDI) ............................................................................................ 2 Basic Elements of an EDI System .................................................................................................................. 3 A Disciplined Approach to Defining EDI Requirements & Objectives ........................................................... 5 SAP-Based Modules, Methods & Tools for Implementing EDI ..................................................................... 5 Business-Specific EDI Interfaces & Detailed Data Mapping .......................................................................... 8 Leveraging Standards-Based Networking & Cloud Infrastructures .............................................................. 8 Comprehensive Systems Integration ............................................................................................................ 9 The Bottom Line: ........................................................................................................................................... 9 ABOUT IDHASOFT: .................................................................................................................................. 10
Page 1
Copyright 2012 Idhasoft, Inc. www.idhasoft.com/sap Phone: 877- 454-4727
The bottom line is that EDI can provide both enhanced operational efficiency and improved profitability.
Page 2
Copyright 2012 Idhasoft, Inc. & US Data Management, LLC www.idhasoft.com/sap www.usdatamanagement.com Phone: 877- 454-4727 Phone: 888-231-0816
Some major sets of EDI standards include: The US standard ANSI ASC X12 (X12) is predominant in North America. UN/EDIFACT is the international standard that is predominant outside of North America. The ODETTE standard is used primarily within the European automotive industry
Page 3
Copyright 2012 Idhasoft, Inc. & US Data Management, LLC www.idhasoft.com/sap www.usdatamanagement.com Phone: 877- 454-4727 Phone: 888-231-0816
Streamlining EDI Design and Implementation In order to facilitate the exchange of accurate and detailed information between different business systems, EDI defines a variety of specific document types to address the range of typical generic transactions that occur within any business system. In general, these EDI documents contain the same information that would normally be found in a paper document used for the same organizational function. For example an EDI 940 ship-from-warehouse order is used by a manufacturer to tell a warehouse to ship product to a retailer. It would typically include a ship to address, bill to address, a list of product numbers, UPC codes, quantities, etc. The following list contains examples of some commonly used EDI transactions.
180 - Return Merchandise Authorization on Notification 810 - Invoice 812 - Credit / Debit Adjustment 816 - Text Message 820 - Payment Order / Remittance Advice 830 - Planning Schedule 832 - Price / Sales Catalog 834 - Benefit Enrollment and Maintenance 835 - Health Care Claim Payment/Advice 837 - Health Care Claim 850 - Purchase Order 852 - Product Activity Data 855 - Purchase Order Acknowledgement 856 - Ship / Notice Manifest 860 - Purchase Order Change Request 864 - Text Message 867 - Production Transfer and Resale Report 869 - Order Status Inquiry 870 - Order Status Report 940 - Ship from warehouse order 997 - Functional Acknowledgment
Although most people think of EDI only in terms of supply chain management, EDI technology is also used to exchange inter-company information in a wide range of industries, such as medicine (patient records and laboratory results), transport (container and modal information), engineering, construction, and many other fields. In some cases, EDI can even be used to create entirely new business information flows to support new operations that were not previously existent as paper-based flows.
Page 4
Copyright 2012 Idhasoft, Inc. & US Data Management, LLC www.idhasoft.com/sap www.usdatamanagement.com Phone: 877- 454-4727 Phone: 888-231-0816
Up-Front Planning Top-down Design Detailed EDI Data Mapping Pre-Live Testing & Training Step-by-Step Go-Live Process Roll-out EDI to Trading Partners On-going Monitoring and Optimization
The following sections provide an overview of the SAP-based capabilities that can be leveraged for implementing EDI systems, with specific focus on areas where Idhasoft SAP experts have already tailored these capabilities to address customer requirements.
Streamlining EDI Design and Implementation The fundamental approach of ALE is to provide a distributed and fully integrated R/3 system that is segmented across the three distinct layers. This enables every application to be fully self-sufficient and provides an inherent level of built-in autonomy and data redundancy. The ALE architecture thus allows for applications to be easily distributed and synchronized via message-based communications. In ALE implementations, the applications in the sending system would create EDI-compliant IDOC intermediate files and validate all required IDOC data, version levels, filtering and receiver information within the SAP environment. The IDOCs are then transmitted over any communications medium and are received, unpacked, filtered, converted and processed by the receiving system.
This ALE-based methodology is also used to create an external EDI-compliant system when a non SAP system is on the other end of the communications channel. ALE communication occurs from the SAP side and EDI from the non-SAP side, with the standards-based IDOCs providing a universal mechanism to deliver the data between the ALE and EDI systems. For the exchange of data between a SAP and Non SAP system, an EDI subsystem is used to convert and deliver the IDOC data.
Page 6
Copyright 2012 Idhasoft, Inc. & US Data Management, LLC www.idhasoft.com/sap www.usdatamanagement.com Phone: 877- 454-4727 Phone: 888-231-0816
Streamlining EDI Design and Implementation Message Control (NAST) is primarily used for outbound EDI communications from the SAP application and Workflow is typically used to manage inbound EDI data.
Another key aspect of any EDI implementation project is to identify and define the roles of various business and technical staff (agents) within the customer and partner organization. From the list of possible agents, the implementation team determines the specific permitted agents for both the Business Layer and the Technical Layer, with their access and data modification permissions clearly defined.
Page 7
Copyright 2012 Idhasoft, Inc. & US Data Management, LLC www.idhasoft.com/sap www.usdatamanagement.com Phone: 877- 454-4727 Phone: 888-231-0816
ABOUT IDHASOFT:
Idhasoft Inc. is a global leader in strategic technical solutions, SAP gold channel partner and 2010 SAP Business All-in-One Partner of the Year-USA, providing innovative end-to-end business solutions to companies around the world. Idhasoft founding vision is to serve the SMB marketplace with a unique blend of business solutions and services. We help our clients drive efficiency, improve profitability and build a lasting competitive advantage. Idhasoft capabilities and services include the following: 100% commitment to SAP solutions, services and technologies SAP Gold All-in-One Solution Provider and Premier Implementation Partner Partner Center of Excellence Certified master VAR SAP Certified Industry Specific Solutions Dedicated SAP Practices- ERP, CRM, SRM, SCM, BI and Net Weaver/Portals Senior SAP experienced consulting team with both industry and SAP experience Invited expert each year at ASUG, SAPPHIRE and other SAP conferences State-of-art Solutions Center with SAP Ramp-up Applications Idhasoft's pre-configured Industry and Solutions templates Our consultants work closely with SAP COE and SAP Product Development
Page 10
Copyright 2012 Idhasoft, Inc. & US Data Management, LLC www.idhasoft.com/sap www.usdatamanagement.com Phone: 877- 454-4727 Phone: 888-231-0816