Maxonis, cost effective EDI solutions PartnerWeb Login

Maxonis: cost effective EDI solutions Maxonis, költséghatékony EDI Megoldások

Standard EDI solutions

This type of implementation covers three key areas in terms of using standards. For message processing we provide solutions for our client defined subsets of EDIFACT, VDA, Odette, SAP R/3 IDoc and ANSI X12. With using these EDI standard specifications the message translation maps can be developed and activated easily.

Connectivities are established with using high security protocols taking into account speed, stability and your additional data transfer requirements. You can even use our Maxonis Client Application for data transfer. This software controls the connection and responsible for sending and receiving EDI Messages between your IT System and Maxonis Interface Applications.

With following standard business processes and scenarios the rollout time of any EDI Implementation can be significantly reduced. We believe that the key element of a successful EDI communication is to understand the business and adding value with simply implementing business intelligence in the message processing logic. This way you can outsource development of complex but well known data processing...

BASIC SCENARIO DELIVERY FORECAST AND DAILY CALL-OFF TRANSFER


The EDI provider is responsible to translate / convert the customer generated EDI messages from any standard (EDIFACT, VDA, Odette, ANSI X12) to the supplier's EDI standard format (EDIFACT, VDA, Odette, ANSI X12). The translation is made by the map which is developed by the EDI provider based on the customer's EDI message Implementation Guideline (IG), where the subset is defined, and based on the supplier's additional requirements. The result of the translations is sent to the supplier in the expected format but still having customer data content. Supplier is responsible for processing and uploading the EDI messages and make the communicated information available for the business. Arrows show few of these cases (broken line).

Several possible translation combinations exist. Even if both trading partners use the same EDI standard and message type the translation is required. The subset, the structure and the used qualifiers all can be different.

The frequency of the EDI messages and the horizon of the delivery schedule are business decisions and both needed to be agreed between the customer and supplier.

COMPLEX SCENARIO COMMUNICATION WITH WAREHOUSE AND CUSTOMER


This scenario demonstrates possible complexity of an EDI communication when 3PL (Third Party Logistic Provider) is involved in the logistic flow. In this example both Tier1 supplier and 3PL are handled by the same EDI provider. Customer uses EDIFACT and VDA is used by Tier1 and 3PL.

5 maps are developed for the EDIFACT - VDA and even for 3PL VDA to supplier VDA message translations. Please note that VDA4913 is used for two different business functions: despatch advice (ASN) and inventory report. Several functions can be implemented with VDA4913 indicating the function in its specific segment and field (713-09 process code).

For proper shipping quantity calculations Tier1 supplier needs to take into account both the customer delivery forecast and the actual stock levels. To have optimized transports and expected costs exact stock level management is defined by logistics.

3PL has to be able to process the customer Daily Call-Offs (JIT / Just In Time calls) and use all the communicated data on shipping documents. The frequency of the shipments from 3PL to customer is normally much higher than on the 3PL inbound side (from supplier).

Specific billing process and accounts receivable payment allocation method needs to be worked out as Tier1 supplier may have to use the 3PL's shipment ID as external delivery ID.


We are always happy to answer your questions: sales@maxonis.com!
+36 (23) 421-896 or +36 (70) 38-555-28!
Call us on one of our phone numbers!


CUSTOM EDI SOLUTIONS

With using our very flexible Maxonis development applications and capabilities we are able to provide solutions for any message structure and field data format you need to use for communication. If your application uses internal (in-house) format for sending and receiving business documents our interface application can translate it to standard or even another non-standard format making you EDI capable. Your trading partners can receive and send their EDI messages taking into account and handling your company as a fully EDI Enabled partner.

Integrating partner specific business intelligence and using Maxonis message processing applications we can develop very complex calculations, using unique data processing methods and handling non standard data formats and content.

Non-standard routing to multiple destinations based on business content is also part of this type of solution. Unique message structure, envelope logic and message header can be defined and developed in the EDI interface.

NON STANDARD EDI MESSAGE STRUCTURE OVERVIEW OF HEADER AND ITEMS SECTIONS


Working out a non-standard EDI message structure is a very complex task. Several different rules have to be taken into account:

CUSTOM AND STANDARD EDI STRUCTURE COMPARISON OF POSSIBLE STRUCTURES


Custom EDI message structure not always have the same advantages as standard EDI messages have but special cases when the structure is fixed, the data content is clear, and the document itself is very simple this type of communication can have the same stability, quality and trustable result on receiver side.

If envelops are not used, and a non-standard EDI message has to transfer always only 2 records or segments with a very limited set of fields, all with mandatory status, stable EDI connection can be established.

Further and massive testing is required on all sides (sender, EDI provider, receiver) anytime when the custom definition changes to avoid further complications.


We are always happy to answer your questions: sales@maxonis.com!
+36 (23) 421-896 or +36 (70) 38-555-28!
Call us on one of our phone numbers!