Archive

Archive for the ‘EDI and B2B Integration’ Category

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: ,

“AS2, FTP, or VAN: The Race to Zero” (Part 2)

July 21st, 2010 Matt Baran No comments

With the ever-changing economy, especially now, businesses are looking for ways to reduce costs and become more efficient.  The new technologies (as previously discussed in Part 1 of this blog), coupled with the immediate need for cost cutting, have created the perfect environment to fuel another major shift in business communication.

One factor helping this shift is that technology has been developed and priced so that even small “Mom and Pop” shops can obtain affordable AS2 and/or FTP solutions.  The shift in cost of direct connections will fuel the move away from traditional Value Added Network (VAN) trading partners to having more AS2 and/or FTP partners (connection types).  This shift will increase more rapidly as a result of the constant need for companies to become more efficient to remain competitive.

Large retailers, such as Walmart, require a “direct” AS2 connection to do EDI business. This represents a key indicator that this shift to AS2 (and/or FTP) is becoming more prominent and recognized.

It is interesting to see this relationship go though another major change.  What we’re actually seeing is communications between Trading Partners coming full circle.  Initially there were leased lines and individual modems for connecting to trading partners.  Over time this became too expensive and, out of necessity to reduce communication costs, the VAN was born.  More recently the Internet was introduced, which provided a new and inexpensive means to communicate.  With expanding Internet capabilities, VANs became too expensive and too time consuming to manage.  Better, cheaper software was designed to utilize these new communication methods.  As a result, we now see more direct-connections being established in place of moving data through the traditional VANs.

This shift will require more time…it will not happen overnight.  Instead, it will be a slow migration that will occur over the next decade (possibly longer).  As new business relationships are formed, they will take advantage of these newer technologies; older methods are likely to remain with the VAN service (although the VANs often do provide other solutions and services besides merely the moving of data).  Going forward, implementations will generally see a mix of these connection options until costs and efficiency eventually eliminate those methods that restrict growth.

Categories: EDI and B2B Integration Tags: , ,

Trading Partner Setup 101: PART 1 – The Communication Protocols

June 30th, 2010 DJ Zimniski No comments

When setting up a new trading partner or business integration process, thinking through the process beforehand can greatly decrease the implementation time and help minimize problems. Many integration projects can come to a grinding halt in the middle of implementation if it’s only later realized that required data is not configured in your backend application, or if your system doesn’t support the particular communication protocol your new trading partner intends to use.  “Looking before leaping” will help alleviate potential problems later.

Read more…

Cooking Up Code

June 16th, 2010 Patrick Gombola No comments

Careful, that code is hot!

Welcome to my kitchen. I know, people tell me all the time – “This place looks more like an office than a kitchen.” I guess you would assume that with the monitors, keyboards, and mice lying around. However, this is a special kind of kitchen. This is the CODING kitchen.

If you’ve ever watched any of the wonderful cooking shows on the Food Network, you’ve no doubt seen world renowned chefs create amazing meals. Like adding ingredients to a pan, computer software is created by piecing together ingredients. Except a programmer’s ingredients are code instructions for the computer.

Allow me to explain. Read more…

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: , ,

AS2, FTP, or VAN: The Race to Zero (Part 1)

April 20th, 2010 Matt Baran No comments

The Value Added Network (VAN) business began with a simple transaction that was manually transmitted within the grocery industry.  The VAN was developed out of a necessity for companies to replace their traditional business communication methods.  These methods included human interaction and the use of the postal service and the telephone.  Communicating in this way caused severe “bottle necks” and held up the flow of data.  This problem spawned the birth of the Electronic Data Interchange (EDI) standards.  EDI was developed to help standardize the electronic flow of business documents.  As this shift from manual to electronic business communications grew it opened up a market for how to exchange this data.  Thus, VAN business emerged as a direct result of this shift in business communication.

Read more…

XML Schemas

April 15th, 2010 Jeff Inns No comments

All things are permissible, but not all things are beneficial; when developing an XML Schema, this is a good rule of thumb.  XML Schema provides many options for developing robust, flexible data structures.  One such option is the ability to define nested content model definitions.

All XML elements have a content model.  A content model defines the validation rules and structure of an element’s content.  Element content can consist of character data, child elements, or a mixture of both.  In the cases where an element contains child elements, a content model is used to define the order, cardinality and presence of the child elements. 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…