Home‎ > ‎Home of all things EDI‎ > ‎

EDI Related Posts


New look to ERPGenie and EDIGenie

posted Sep 3, 2017, 11:02 AM by Kevin Wilson

Out with the old in with the new.... The fresh new ERPGenie and EDIGenie logo symbolizes the collaboration and connections between people, systems and devices of all shapes, sizes and colors... The G is the foundation on which we stand - Great People delivering Great Value!

Advantages of using B2B Managed Services - Infographic

posted Mar 1, 2017, 10:59 AM by Kevin Wilson

https://cdn2.hubspot.net/hubfs/43245/EDI%20supply%20chain%20infographic.png?t=1488389602401
Click to see the full infographic


QUICK POLL: What EDI translation tool or service are you using?

posted Oct 12, 2016, 3:57 AM by Kevin Wilson

You are either doing EDI in-house, in which case let the group know which tool your are using. It would be also interesting to know the systems you are translating for (E.g. SAP ERP) and which standards / versions you are using.
Or you are outsourcing your EDI services in which case who are you using?

Mar-Kov provides Electronic Data Interchange (EDI) Functionality to the Process Manufacturing Industry

posted Aug 5, 2015, 9:55 AM by Kevin Wilson

NEW YORK, N.Y., July 15, 2015 (GLOBE Newswire) -- via PRWEB - Mar-Kov has announced it now provides Electronic Data Interchange (EDI) functionality as an integrated part of its software suite.

Mar-Kov serves Process Manufacturers in a variety of industries including Food and Beverage, Paints and Coatings, Cosmetics, Pharmaceuticals, Flavor and Fragrance.

The core functionality provided by Mar-Kov includes inventory, traceability, and batch recording software for process manufacturers. Mar-Kov has seen a greatly increased customer base in the Food and Beverage industry over the past several years, as traceability, regulatory compliance, GMP and HACCP have increased in importance.

Mar-Kov software can be deployed either as Software as a Service (SaaS) or as an installed client/server application.

As Mar-Kov's footprint in the Food and Beverage industry has grown, adding EDI capabilities was a natural extension. Mar-Kov provides standard transactions for Customer Purchase Order (850/875), Customer Invoice (810/880), Customer Credits (810/880/812), Customer ASN (Advanced Shipping Notification) including GS1-128 labeling (856), Supplier Purchase Order (850), and Supplier Invoice (810).

Read the full release at Global News Wire.

What is the future of EDI? Is it dead?

posted Jul 23, 2015, 5:22 PM by Kevin Wilson   [ updated Jul 24, 2015, 2:09 PM ]

Take this short survey and share thoughts on this topic. In return you will receive the results for FREE. Click https://www.research.net/s/VBR7SC8 to take the short survey. 

Mapping a Customers EDI field in to and then out of SAP

posted May 18, 2015, 9:21 PM by Kevin Wilson   [ updated May 18, 2015, 9:27 PM ]

Customers that transact Orders to you via an EDI X12 850 often need you to send certain, customer specific, fields back to them on subsequent documents. This is often a requirement at both the header and item levels of the order. A common example of a header field would be the department number. It makes sense for the customer to have the department number returned on subsequent documents but we don't have any use for that number in our SAP system other than to store the details and pass it to subsequent documents.

In this example I am going to use the Internal Vendor number as my example at the header level and Customer's PO item number as my example at the item level.
Note: Best practice is to map the Customer PO number to the "Purchase Order Item" field as shown in the diagram below.


Understanding the Overall Design

Any data that your customer want to be returned to them in subsequent EDI documents, that you don't have a use for, will be passed in and out of sales order header and item text accordingly. You will need to configure an "EDI Technical Text" for the sales order header and line as well as for the billing document header and line. You will then use text copy control (shown in the diagram below) to copy the text from the sales order on to the billing document. This text will then automatically appear in the corresponding INVOIC IDoc and thus available at mapping time.

The decision tree for customer required fields is as follows:
  1. Is there a standard place for this in SAP
    1. IF "YES" then map it there
    2. IF "NO" then
      1. Do you require this data for your own process?
        1. IF "YES" then create and map to ZFIELD (custom append to VBAK, VBAP)
        2. IF "NO" then map to text field described in this paper

Following the process

To describe the process let's refer to the process diagram below and follow the steps by number.


STEP 1: Understanding the 850 message

The ANSI X12 850 from the customer has the following 2 segments:

REF*IA*115~

PO1*20*5*EA*7.00**KB*17*VA*3234~

The REF segment is qualified by the 1st field (REF01) as "IA" which implies that the customer's internal vendor number for us is "115". The customer would like for this number to be returned on the REF segment in the associated 810 Invoice. We can achieve this by updating the external reference field for this customer in master data, but for the purposes of this paper we will map it in and out of text.

The PO1 segment indicates that the customer's PO item number is "20". Once again the customer requires us to pass back this number in subsequent EDI transactions. For the purposes of this paper we will map it in and out of text.

STEP 2: Mapping the 850 to the ORDERS IDoc

I have used Gentran Server NT's mapping tool to demonstrate what I am doing here.

Header Mapping

Referring to the diagram below you can see that when I am mapping the REF segment I am looking at the first field (the qualifying field for the segment). If I find the value to be "IA" then I know that I am dealing with the Internal Vendor number so I need to map field REF02 to my EDI technical text with the prefix of "Internal Vendor:" (stored in temporary element REF_IA). The prefix is important because we will be looking for this text exactly as is when we map the outbound INVOIC IDoc to the 810 in STEP 7. Element REF_IA is mapped to TDLINE in the E1EDKT2 segment.

Item Mapping

Referring to the diagram below you can see that I am mapping the PO1 segment element 1 (Item number of the customer) to my EDI technical text for the item, with the prefix of "PO101:". The prefix is important because we will be looking for this text exactly as is when we map the outbound INVOIC IDoc to the 810 in STEP 7.

STEP 3: The ORDERS IDoc

The resulting ORDERS IDoc Header text segment looks like this:

And the resulting ORDERS IDoc item text segment looks like this:

STEP 4: The Sales Order

The resulting Sales Order EDI technical header text looks like this:

And the resulting Sales Order EDI Technical Item text looks like this:

STEP 5: Create the Invoice / Billing Document

Now it's time to create the subsequent document for the sales order, namely the billing document. Because of the Text copy control from the sales order to the invoice we now have the following text on the billing document at the header level:

And the following text on the Invoice / Billing Document item level:

STEP 6: The INVOIC IDoc

The creation of the INVOIC IDoc is typically triggered through output determination. Once the INVOIC IDoc for the invoice has been created the EDI Technical text for the header looks like this:

And the item text looks like this:

STEP 7: Mapping the INVOIC IDoc to the 810

Header Text Mapping

IF E1EDKT2-TDLINE(16) = “Internal Vendor:” then map the following:
REF01 = “IA”;
REF02 =  E1EDKT2-TDLINE+17(20); "Starting at position 17 read for 20 chars

Item Text Mapping

IF E1EDPT2-TDLINE(6) = “PO101:” then map the following:
IT101 = E1EDPT2-TDLINE+7(10); "Starting at position 7 read for 10 chars

STEP 8: Reviewing the 810 message

The resulting ANSI X12 810 message now has the data that was sent in via the 850 in STEP 1.
REF*IA*115~

IT1*20*5*EA*7.99*VA*3234~

Advantages of doing it this way?

With this technique you can do this for any fields that the customers needs back for any outbound EDI message to them that come from SAP and linked to the Sales Order document flow. I.e. The requirement for an ASN 856 can be met the same way. Advantages of this approach include:

  • No custom fields required to store the data
  • No custom code required to implement the solution
  • Once the config of the EDI Technical text types are in place any further changes needed can be completely handled by the EDI mapping team. This is desirable because it really is a pure EDI requirement to return a value to the customer that we actually have no interest in

Other considerations

  • Since the EDI technical text is really only utilized by the EDI mapping team and really should not be seen or at least changed by anyone, consider implementing some change control or authorizations in order to ensure the integrity of the text is maintained (i.e. it is not changed)
  • You cannot allow for the manual creation of line items on EDI orders as they will not contain the EDI text - It is bad practice to allow for the creation of line items on EDI orders so refrain from that practice.

If you have any comments or suggestions just leave a comment below.

Looking for EDI experts to contribute to EDIGenie.COM

posted May 18, 2015, 11:11 AM by Kevin Wilson   [ updated May 18, 2015, 11:16 AM ]


"Hey there folks - I have created many informational portals and communities over the past 20 years (yes, that is correct - 20 years!!!) - My first web portal was scripted in raw HTML and hosted on a Unix server where page views were stored by means of a UNIX script accessing a file on the file system... Crazy what we had to do back then ;)
It is now so much easier to create and share content with a broad audience and it's with this in mind that I reach out to you, the EDI community...
I am looking for EDI technical experts that are willing to share their tips and tricks with a greater audience. No sales pitches, just raw content with you as the author. If folks like what you put out there they will contact you directly for clarification or potentially setting up an engagement. The first part of getting your next contract is to get noticed. By publishing quality articles on EDIGenie.COM you can get that exposure that you need.
If you have the skills in EDI and wish to get involved in the EDI community then shoot me an email and I'll take it from there - Good luck!" Kevin Wilson - Founder EDIGenie.COM



EDI X12 mapped to EDIFACT

posted May 15, 2015, 12:32 PM by Kevin Wilson   [ updated May 15, 2015, 12:34 PM ]

If anyone has changes to be made or updates to this list just leave a comment and we will update it.
X12 vs EDIFACT
TRANSACTION
X12 EDIFACT
Product and Pricing

Price Sales Catalog 832 PRICAT
Price Authorization Acknowledgement/Status 845 ATHSTS
Specification/Technical Information 841 PRDSPE
Request For Quotation 840 REQOTE
Response To Request For Quotation 843 QUOTES
Electronic Bid Form 833 --

Orders and Contracts


Purchase Order 850 ORDERS
Purchase Order Acknowledgement 855 ORDRSP
Purchase Order Change 860 ORDCHG
Purchase Order Change Acknowledgement 865 ORDRSP
Order Status Inquiry 869 ORSSTA
Order Status Report 870 ORDREP
Contract Award 836 --
Product Activity Data 852 SLSRPT

Material Management


Planning Schedule/Material Release 830 DELFOR
Shipping Schedule 862 DELJIT
Production Sequence 866 --
Ship Notice/manifest (ASN) 856 DESADV
Report of Test Results 863 QALITY
Material Safety Data Sheet 848 --
Contract Award 836 --

Shipping


Shipment Information (Bill of Lading) 858 IFTMCS
Receiving Advice 861 RECADV
Non-conformance Information-Disposition Transaction, Cause/Correction 842 NONCON

Inventory Management


Inventory Inquiry/Advice 846 INVRPT
Product Transfer and Resale Report 867 --
Product Transfer Account Adjustment 844 SSDCLM
Response To Product Transfer Account Adjustment 849 --

Finance


Invoice 810 INVOIC
Freight Invoice 859 IFTMCS
Payment order/Remittance Advice (EFT) 820 REMADV
Lockbox 823 --
Financial Information Reporting 821 --

Healthcare


Eligibility Inquiry 270 --
Eligibility Inquiry Response 271 --
Claim Status Inquiry 276 --
Claim Status Response 277 --
Service Review Request 278-13 --
Service Review Response 278-11 --
Premium Payment and Deduction 820 --
Benefit Enrollment and Maintenance 834 --
Claim Remittance Advice 835 --
Claim (Professional, Institutional, Dentist) 837 --

EDI Control


Functional Acknowledgement 997 CONTRL
Application Advice 824 APERAK
Trading Partner Profile 838 PARTIN

EDI and the Internet of Things (IoT)

posted May 4, 2015, 9:21 AM by Kevin Wilson

I read this great post by Faith Lamprey on how EDI is very suited to connecting to the Internet Of Things...
With devices and gadgets being Internet, RFID and GPS enabled you can imagine there would be enough information to control every aspect of that device. Faith uses the vending machine as an example. Normal IoT says that a vending machine can take payments and sense the preference of drinks that the current user is looking for. You can offer discounts and provide up-sell or cross-sell opportunities... So how does EDI play a role? Well the vending machine can also manage it's own inventory and potentially place an order for items that have reached their safety stock level. The vending machine has a GPS physical location and the machine itself can have it's own GLN (Global Location Number)  assigned, which can be used as the PO ship to address. This is all the information needed to send out a simple X12 850 or EDIFACT ORDERS message to the supplier to replenish the inventory. Once the machine receives the inventory I would imagine it would also be used to send a Goods Receipt (MBGMCR) message to the ERP system managing the Vending machine which would release payment against the invoice for the order. No human touches, no errors, ... plenty of challenges though to get around all the nuances that would be involved in making this seamless. Standards, shortages / overages, incorrect product received, ... Check out Faith's take on it here.

What Wikipedia Won't Tell You About EDI

posted May 4, 2015, 9:03 AM by Kevin Wilson

I found this interesting blog post written by Kristen Kearns, Manager of EDI Services for Aurora Technologies. She quite correctly describes some of the nuances in EDI that is overlooked by folks that aren't too engaged in the implementation of EDI. The theory of EDI with it's communication protocols, standards, elements, segments, separators is all good and fine but at some stage it runs in to the brick wall called REALITY!!!
To summarize the points that Kristen has made I have compiled the following bullet points:
  1. Wikipedia tells you about EDI standards
    • Reality = Standards are a "suggested ruleset" that are loosely followed by those implementing them - Improper use of segments and elements are commonplace
  2. Wikipedia tells you about how large EDI users publish their specifications and are unwilling to change
    • Reality = You better get your ERP implementation in shape to align with these specifications - The supplier will not change their process but can you integrate their needs in to your standard process - Wikipedia doesn't talk about how this is a critical part of the puzzle - I have integrated many suppliers unique requirements in to SAP and there are several standard techniques to do this where you don't have to adapt the customer's process to meet the supplier's EDI requirements... This is key.
  3. Wikipedia does not call out the importance of timely change notifications - E.g. We are changing the qualifier from A to B from Monday onwards... EDI changes can be slow to make because the testing cycle is not a trivial one. Ensuring that good, timely communication is in place between trading partners, both ways, is critical to a successful EDI process
  4. Wikipedia tells you about communications and the way data is to be transmitted
    • Reality = Sometimes you simply don't have the tools to communicate in the way the supplier or customer needs it. E.g. You don't have AS2 capabilities to communicate with Walmart. It then becomes a key issue to figure out exactly how you will accomplish this otherwise you run the risk of losing the business.

There are many nuances in an EDI implementations and these are but a few key ones. Check out Kristen's article.

1-10 of 18