Archive

Posts Tagged ‘EDI’

Why is Testing so Critical for Production?

August 18th, 2010 Dan Feeney No comments

After having supported many customers for the past several years, I look back at some of the more critical issues and quickly recognize that most of these could have been resolved (or certainly avoided downtime) had the customer employed reasonable and simple testing.

The one recurring theme is the amount of implementation work that is performed without equal efforts applied to testing that work.  One would expect that any configuration with impact on company reputation and revenue would be tested to its’ fullest potential before it is ever promoted to a production status.  Schedules and deadlines do not always allow for intense sessions of testing and debugging, however, there are many important yet unrecognized advantages to the testing process. Read more…

Why Should Your Company Consider EDI?

August 4th, 2010 John Coyle No comments

Being somewhat of a concerned environmentalist, I think that helping save the planet for future generations should be the priority for everyone. One small step would be to switch your company to the ecologically friendly technology called “EDI” (Electronic Data Interchange).  Workers around the world discard millions of tons of office paper every year.  Producing this paper kills an innumerable amount of trees each year.  Converting this huge quantity of paper to an electronic form would help save paper and energy.  So think green: Reduce your carbon footprint by using less paper while saving money.

EDI would save your company money by providing an alternative to data streams that require a great deal of human interaction and costly materials.  Overhead costs will be reduced by eliminating such tasks as mailroom sorting, circulation, data entry, the manual reconciliation of different documents, document mailing, faxing of information, distributing, filing and storage of documents and transportation costs.  You will save money on paper, envelopes, business forms, stamps, printing and processing fees.   Excess inventory costs would be lowered by reducing inventory levels achieved by shortening the order processing cycle time.  Companies could save money by taking advantage of early payment discounts offered by vendors for quicker supply chain turnaround.  Other cost reductions would include the handling of errors and exceptions – this could be many times more expensive than correctly processing the document in the first place.

EDI improves customer satisfaction and strengthens supplier relations.  EDI improves customer satisfaction because information is available “real time” and is more accurate. Concerns and questions of customers can be addressed in a more timely fashion.  EDI will help strengthen relations with suppliers. The mutual work required to implement EDI tends to build a good working relationship between trading partners.  The sharing of EDI information strengthens the ties between partners and encourages stronger levels of commitment.

When information is copied from one location to another there is an opportunity for error.  Electronic data transfer eliminates the need for copying information from a paper document to another format, or re-keying it into your system.  Once the information is entered correctly, there is no additional opportunity for error since it is electronically entered into all other applications without further human intervention.

One very important advantage of EDI over paper documents is the speed in which the trading partner receives and enters the information into their system.  This greatly reduces cycle and turnaround times.  For this reason, EDI can be an important component of “Just-in-Time” production systems.  Better responses to customer concerns may lead to increased sales.  Transmitting data via EDI across the country or around the world will only take a few seconds or minutes as opposed to days, when sent through manual delivery service.  Once the data is received, the information is available immediately without any time-consuming human intervention.

EDI gives companies the ability to exchange business documents electronically via a wide array of communication protocols.  This form of e-commerce is widely used throughout the world.  EDI carries millions of dollars of transactions every day for all types of businesses and government agencies.  EDI plays a very important role in the world’s economic make-up.  Many companies will not do business with vendors that cannot exchange business documents through EDI.  (Good luck trying to do business with the big retailers without EDI.)

EDI has been available for decades.  It is reliable, proven, stable, and supported by long-established standards developed and maintained by respected governing bodies (such as ANSI, EDIFACT, and ISO…to name a few).  It is highly unlikely that this will change in this lifetime.  Being EDI-capable is no longer an option; it is a business necessity!

Categories: EDI and B2B Integration Tags: ,

Demystifying AS2 Certificates

June 2nd, 2010 Joshua Watkins No comments

In Electronic Data Interchange (EDI), digital certificates can be used to secure data transfers between systems.  Certificates can encrypt the data transfer in multiple ways.  First, the data itself could be encrypted, making it unreadable by any receiving system unless it has the proper decryption key. Second, the communication channel that the data is being sent through could be encrypted.  Third, encryption could apply to both the data and communications channel.  It is common for certificates to secure AS2 communication (data encryption) or SSL connections (communication channel encryption). Read more…

Categories: EDI and B2B Integration Tags: , ,

Data Integration 101 Using the EXTOL Business Integrator

May 20th, 2010 Mike Coyle No comments

Data Integration is defined as, “the combining of fragmented data residing in different sources and locations which are aligned to support business goals”.  There are many reasons to bring data of different types (flat file, DB2, or even spreadsheets), possibly residing on different servers, to one main location to be integrated together.  If you do Electronic Data Interchange (EDI), translating data between an EDI fixed format and application variable format files, then you have already been doing a piece of the data integration puzzle. Read more…

SQL and XML

May 13th, 2010 Dan Brown No comments

In my previous blog post I talked about the SQL standard.  It is tempting to visualize a standard as a list of rules nailed to a wall.  However things in this industry have a habit of becoming a moving target.   Read more…

Best Practices for Mapping: Application Files and Fields

May 11th, 2010 Andrew Mihalick No comments

Successful EDI implementations must begin with the development and employment of efficient object naming conventions using “best practices”.  This will avoid aggravation and redevelopment at a later time.  “Doing it correctly the first time” is a most-relevant piece of advice.  This is of particular advantage when creating files (tables) to store EDI data (the implementation and deployment of EDI interface / staging files and in support of both inbound and outbound EDI transactions).

Read more…

What’s SAP’nin’?

April 29th, 2010 Pete Stetson 2 comments

“Not much, what’s SAP’nin’ with you?”  That’s just a little “inside joke” when we’re working with customers who use our SAP interface with EXTOL products.  And yes, EXTOL does have an interface that enables EXTOL products to work with the SAP application.

But, what actually is SAP and why is it necessary to have an EXTOL interface? Read more…

What Is EDI “Enveloping” All About?

April 14th, 2010 John Coyle 1 comment

The primary reasons for EDI “enveloping” are to manage EDI Interchange routing, and to enable your EDI system know how to process inbound transmissions (this also applies to the enveloping data you send to your trading partners). Your EDI software needs to know where a transaction (message) begins and ends. It also needs to determine which trading partner transmitted the data and what type of transactions were received, for example, Purchase Orders or Invoices.

When transmitting EDI data to trading partners, it is necessary to “wrap” the individual transactions using “envelopes”. There are various envelope types and each representing different levels.  Each “envelope” has one beginning and one ending segment that carries certain control information.  Read more…

What is a “Staging Database” and Why Consider It For EDI?

March 23rd, 2010 EXTOL Services No comments

For this discussion, a “Staging Database” refers to any intermediate database that would fill the gap between Electronic Data Interchange (EDI) transactions and the backend business application. Whether obtained through a third party or developed in-house, some applications provide interface files that are “EDI Intelligent” and support the required EDI transactions. For applications that do not, the Staging Database should be considered for the following reasons and with the following purposes:

Data Grouping/Restructuring: Spreadsheet-type (SDQ) orders, where a single purchase order describes multiple ship-to destinations, might not be supported in the application because many applications define an order as a single ship-to destination. In this case, the single spreadsheet order needs to be broken down into separate orders by ship-to destination prior to insertion into the application. A multi-line order could have the same ship-to destination repeated several times. Therefore, data grouping would be required for later reorganization of all lines (for each ship-to) and transforming into a single order within the application.

The Staging Database would provide sorting/grouping functionality to support such reorganization. For example, an order with two lines, each having three SDQ pairs (defines the “ship-to location” and “quantity” breakdowns), and where one location is repeated on both lines, might result in six orders instead of five without such grouping.

Read more…

Too Many EDI Segment Occurrences? Table Them!

March 12th, 2010 Troy Lunt No comments

The problem: Often, EDI data elements of the same type may occur multiple times.  One common example is “Dates”.  The number of Dates needed (or sent) is generally limited [only] to the number of Dates required by the business application of the party who “calls the shots”.  If the customer expects to retain a trading partner’s business, they will make every attempt to comply with that trading partner’s requirements.  The trading partner might send the supplier Dates such as “Scheduled Shipment Date”, “Expected Delivery Date”, “Cancel Date”, or a host of other possible dates.  The same is true for Reference Numbers, Notes/Comments, Product Item Numbers, Addresses, and so on…they all represent EDI data that could be sent in abundance.  The question is, “what is the most efficient way to configure the EDI system to accommodate these repeating (and sometimes redundant) pieces of data?” Read more…

Categories: EDI and B2B Integration Tags: