Seamless Integration with EDI & XML MegaXML/ESA
MegaXML MEGAXML/ESA is an Adapter subsystem designed to integrate MegaXML with SAP Enterprise Services (ES). While MegaXML provides seamless integration between B2B E-commerce Systems; e.g. X12 EDI, UN/EDIFACT, XML, flat file; and virtually every conceivable backend ERP systems (including SAP R/3 with its IDoc adapter), with the introduction of MegaXML/ESA adapter subsystem, MegaXML's integration with SAP ECC 6.0 EhP 2 (based on an Enterprise SOA) has been fully optimized.
MegaXML/ESA an SAP certified adapter subsystem is fully capable of integrating with any SAP Enterprise Services (ES) service with the most flexible deployment options. Unlike legacy adapter systems, it is no longer necessary to put all services in one box.
Based on the successful SOA principles, MegaXML/ESA's loosely coupled architecture allows the adapter (or a set of [adapter] services running on multiple servers) to be placed anywhere within the LAN, Firewall, WAN, across the globe to achieve high level of scalability and reliability leveraging the powers of SAP Enterprise Services (ES) and Microsoft .NET 3.5 WCF. This allows an obsolescence proof scaling up of transaction volume without worrying about the interface limitations and resource bottlenecks.
Using the workflow architecture of MegaXML; the MegaXML/ESA translates the trading partners' documents such as Purchase Orders, Order Confirmations, Invoices, Advance Shipment Notices, Payment Advices etc. in EDI, EDIFACT, XML, flat files and marshals between MegaXML and SAP using the SAP Enterprise Services (ES) architecture. Although most suppliers and vendors would typically use it for complete B2B automation of their SD systems, MeagXML/ESA is not limited to that - it can consume and initiate any eSOA service of even a non-SD systems such as MM, FI, CRM, SRM etc.
In a typical "Order to Cash" scenario, the MegaXML/ESA's eSOA Adapter subsystem issues a Web Service Call to SAP submitting the inbound purchase orders provided by the MegaXML by translating and mapping Purchase orders (EDI-850) transmitted by the ordering customer.
The SAP system creates Sales Orders corresponding to those POs, and returns back their numbers to MegaXML/ESA. The user (supplier) gets a notification email from MegaXML containing the list of those newly created sales order numbers.
Subsequently, based upon the business workflow configuration, the supplier transmits a list of confirmed sales orders back to MegaXML/ESA which then processes them by issuing the eSOA calls, and triggering MegaXML with their details. MegaXML turns them into Purchase Order confirmation (EDI-855) and transmits them back to the customer who placed the Purchase Order.
In addition to confirming the order, the supplier fulfills the order by production, packing, and arranging for its transport from a shipment point (plant/warehouse). When it is ready to ship, the required Delivery notes are created within SAP, and a Shipment Notice (EDI-856 ASN) generation request, consisting of delivery IDs is transmitted to MegaXML/ESA. Upon receipt of this request, the MegaXML/ESA issues a series of eSOA calls to obtain the details of these delivery documents, and their respective sales orders. It then triggers MegaXML with that info which turns them into EDI-856-ASN and transmits back to the customer who placed the Purchase Order.
Finally, invoices are produced by the SAP system, and their list is transmitted to MegaXML/ESA, which picks up all necessary background information using eSOA calls, and submits them to MegaXML for sending out EDI 810 to the buyer. Every scenario uses a set of highly optimized and re-factored composite adapters that natively support eSOA WSDLs.
Leveraging the powers of MegaXML engine, MEGAXML/ESA Adapter subsystem enables automatic B2B document transfers between E-commerce trading partners allowing a very diverse range of ERP systems and SAP. Using state of the art technologies in its architecture, design, and managed run time execution, it is highly scalable/flexible solution.
MegaXML is fully automated set of customized E-commerce Pipelines. EDI documents are automatically downloaded and uploaded between remote B2B trading partners and SAP. EDI documents are then translated and mapped by MegaXML into SAP Enterprise Services (ES) formats and submitted to SAP. MEGAXML/ESA interacts with SAP/eSOA requests to get business documents, and their dependents. They are then mapped and translated and into required EDI or EDIFACT documents and delivered to appropriate trading partner(s).
The MegaXML/SAP uses the Microsoft .NET 3.5 (WCF) to communicate with SAP eSOA services to exchange the business documents.
There are several advantages in using SAP Enterprise Services (ES) to communicate with SAP because it uses standard components such as SOAP, WSDL, and XSD. Coupled with .NET 3.5 WCF, which is often characterized as "Steroids for the Enterprise Service-Oriented Architecture", the MegaXML/SAP combines the power and flexibility of Microsoft .NET framework and the richness of SAP Enterprise Services (ES) services offerings.
- Standards compliance
- Composite Application
- Flexibility of Composite Applications
- Higher levels of re-usability
- Scalability and Agility
- Data Security and Integrity
- Native support of eSOA services WSDLs and power of .NET 3.5 WCF
- Easily configurable with several deployment options
MegaXML/ESA integration service connects the SAP Enterprise Services (ES) system with the E-commerce trading partner without requiring any change SAP. For inbound process, the business documents get automatically created in SAP and their numbers are communicated to user through email notifications. For outbound, whenever user wants to send documents to the trading partners, he just transmits a request containing their SAP IDs to MegaXML/ESA. There is no need to setup any special circuits, expensive VPNs, or punch holes in firewalls to establish a secure connectivity. MegaXML/ESA architecture offers the most flexible deployment options available in the industry.
MegaXML/ESA uses the business object type-checking at every level for conformity with both SAP GDTs and DISA B2B requirements. Additionally, user specific validation layer and business logic lookups further filter out any imperfections from the document to achieve a most reliable - fully automated B2B transfer; harnessing the power of ever increasing number of SAP enterprise services in it.
Enterprise Service Repository (ESR), particularly from Enterprise Service (ES) bundles providing enterprise services for SAP ERP Order to Cash; MegaXML/ESA achieves phenomenal success in enabling enterprise users achieve any conceivable B2B requirements.