SAP IDoc Integration with EDI & XML MegaXML/SAP
MegaXML/SAP is primarily designed for SAP IDoc integration with EDI, EDIFACT and XML. It provides seamless integration between B2B E-commerce Systems; e.g. X12 EDI, UN/EDIFACT, XML, flat file; and backend SAP ERP systems, such as Sales and Distribution (SD) and Materials Management (MM); using IDoc. MegaXML/SAP is used for IDoc based SAP such as R/3, mySAP, All-in-one (A1) etc.
Using MegaXML/SAP, the trading partners' documents such as Sales Orders, Invoices, Shipments, Payments etc. in EDI, EDIFACT, XML, flat files are translated and marshaled to backend using SAP IDoc. The MegaXML/SAP utilizing SAP .NET Connector issues Remote Function Call (RFC) and submits to SAP inbound IDoc(s) created by MegaXML translator and mapper for further processing.
Similarly Invoices generated from SAP SD and Purchase Orders generated by SAP MM systems are converted into IDoc(s); they are processed and delivered by MegaXML to appropriate trading partners in desired EDI, EDIFACT, XML and flat file format.
Automatic data synchronization between E-commerce trading partners and SAP is fast and accurate, saving time and cost.
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 IDoc formats and submitted to SAP. Similarly for outbound, whenever the SAP component RSEOUT00 picks up IDoc(s) from SAP which are 'Ready for Dispatch' (status 30); MegaXML pipeline gets activated and IDoc(s) are translated and mapped into required EDI or EDIFACT documents and delivered to appropriate trading partner(s).
Introduction: MegaXML/SAP uses the SAP .NET Connector to communicate with RFC (Remote Function Call) and ABAP modules in SAP to exchange both types of IDoc(s) -- document and status.
There are several advantages in using SAP .NET Connector to communicate with SAP because it uses standard components such as RFC and IDoc.
Standard Communication: SAP .NET Connector is extremely powerful mechanism to establish communication between SAP and its outside trading partners. The SAP .NET Connector provides extended functionality and empowers MegaXML with extended communication capabilities.
Portability: The IDoc library interface is largely portable between various SAP versions.
High Level Data Integrity: Inbound data goes through IDoc segments that are validated against SAP defined schemas (WE60). Therefore, there's no chance of bad data getting injected into SAP database.
No modifications are required to the SAP IDoc process in order to implement MegaXML/SAP integration. The MegaXML/SAP is a C# (sharp) .NET subsystem that communicates with SAP using SAP .NET Connector thru RFC functionality and IDoc components.
MegaXML/SAP uses XML and XSD; performing strong business logic validation features it reliably passes on the XML business document between SAP IDoc and trading partners. Using IDoc messages, the MegaXML/SAP thru the SAP .NET Connector confirms acceptance of the posted IDoc documents by SAP. It also uses SAP .NET Connector to extract IDoc related SAP transactions to move business documents for its subsequent translation and mapping process, and eventually transmission back to appropriate EDI or EDIFACT trading partner.