EDI Solution Architects ........

Crossroad launches its EDI Mission Critical Support Service

2009-02-19T21:33:00.000-08:00

EDI MCS or EDI Mission Critical Support is a one stop technical helpdesk for global EDI users. The purpose of EDI MCS is to understand and provide knowledge based technical support to EDI users arising out of issues related to EDI GAP Analysis, EDI Map development, Trading Partner setup, EDI Map Translation, Testing in the staging and production environment. It’s a Value Added Service (VAS) provided by Crossroad which goes beyond the scope of standard support offerings.

Crossroad aims to provide this service through its EDI MCS portal. The target audience of the MCS service includes EDI professionals, Consulting companies who provide EDI services to its customers and EDI end users which includes corporate in the retail, automobile, electronics, pharmaceutical and manufacturing business.

For more information on Crossroad EDI MCS visit our MCS portal click here.

Common Methods of Shipment requested by the Retailer

2009-01-09T01:37:00.000-08:00

The complex way of transportation, at times, makes delivery processing very cumbersome. Many a times it raises logistical intricacy with transporter or the supplying vendor. The shipment manifest or the shipping consignment should carry proper marking details including dispatch sequence. This process gets even more complicated when the Retailer wants abnormal dispatch sequencing. To cater these requirements, we use particular segment or set of segments to facilitate during EDI transmission. While transmission of such data we have to keep in mind whether the VAN’s EDI support system can handle the complex scenario properly or not. Through our experience we have found that faulty support created transmission bottleneck and improper routing sequence.

The most used shipment methods with x12 data samples are given below :

Basic Shipment

Basic orders when a quantity of product is ordered without specific mention of which store location is to ultimately receive the merchandise. The entire lot is shipped to the distribution facility and will be distributed to the various stores as needed. A Basic Purchase Order can be identified by an occurrence of the header level N1 segment with a “BY” qualifier in N101 to specify the buying party, and the absence of an SDQ segment in the Detail Segment of the Order. The N1 Segment will identity the distribution facility location issued in the Global Location Number format.

ISA*00* *00* *12*9086880888T *12*to be filled up len 15*060525*1248*U*00401*000000166*0*P*>
GS*PO*9086880888T*to be filled up*20060607*1248*1*X*004010
ST*850*10002
BEG*00*SA*DH48130**20050406
REF*IA*6 digit vendor#
CSH*SC
SAC*A*E750****3*5**ZZ*0*30
DTM*001* 20050701
DTM*010* 20050609
N1*BY*SCHAUMBURG*92* 0145
PO1**24*EA*3.78**UP*081492463009
PO1**48*EA*1.2**UP*081492389002
PO1**36*EA*2.79**UP*081492462392
CTT*3
SE*13*10002
GE*1*1
IEA*1*000000166

Spreadsheet Shipment

Spreadsheet Orders are those in which the product is ordered for multiple store location and shipped directly to those store locations. A Spreadsheet Purchase Order can be identified by an occurrence of a header level N1 segment with a “FR” qualifier in N101, and the presence of an SDQ found in the Detail section of the Purchase Order that specifies the various Store Numbers in the Global Location Number format.

ISA*00* *00* *12*9732397773T *12*to be filled up len 15*060525*1248*U*00401*000000170*0*P*>
GS*PO*9732397773T*to be filled up*20060607*1248*1*X*004010
ST*850*10003
BEG*00*SA*DX45902**20050614
REF*IA*6 digit vendor#
DTM*001* 20050722
DTM*010* 20050630
N1*FR*Ferari*92* 0145
PO1**600*EA*6.5**UP*053124549801
SDQ*EA*92*0008*120*0020*180*0023*60*0024*60*0025*90*0026*90
PO1**400*EA*2.6**UP*053124549818
SDQ*EA*92*0008*80*0020*120*0023*40*0024*40*0025*60*0026*60
PO1**250*EA*3.9**UP*053124549788
SDQ*EA*92*0008*50*0020*75*0023*24*0024*25*0025*38*0026*38
CTT*3
SE*14*10003
GE*1*1
IEA*1*000000170

Cross-Dock Shipment

Cross-Dock orders are used when the product ordered is pre-sorted by the vendor by store location, but shipped to a distribution facility rather than to a store location. A Cross-Dock Purchase Order can be identified by having an N1 Segment with ST in N101 and the SDQ Segment listing the store locations in the detail

ISA*00* *00* *01*245588694*01*VENDORDUNS*060525*1248*U*00401*000000001*0*T*>
GS*PO*245588694*VENDORDUNS*20060525*1248*1*X*004010
ST*850*0001
BEG*00*SA*COSTCO001**20060525
REF*VR*VEN01
REF*DP*C001*COSTCO DEPARTMENT
REF*19*C9*COSTCO REGION
REF*ZZ*COSTCOV999*COSTCO BUYER VENDOR NUMBER
FOB**ZZ*LOCATION DESCRIPTION
SAC*A*ZZZZ***990*******02***ALLOWANCE DESCRIPTION
ITD***3*20060601********TERMS OF SALES DESCRIPTION
DTM*175*20060725
DTM*002*20060620
DTM*010*20060613
TD5*****ROUTING INSTRUCTION
N9*H7*SPECIAL INSTRUCTION
MSG*SPECIAL INSTRUCTION TEXT
MSG*SPECIAL INSTRUCTION TEXT
MSG*SPECIAL INSTRUCTION TEXT
N9*H5*LEGAL DISCLAIMER
MSG*LEGAL DISCLAIMER TEXT
MSG*LEGAL DISCLAIMER TEXT
MSG*LEGAL DISCLAIMER TEXT
N1*ST*COSTCO WH CN*9*2455886942222
N3*112 ABC 1# LANE
N4*VANCUVER*VA*9988528
PER*RE**TE*2244558
PO1*01*90*CA*200**UA*12345679124*IN*COSTCO'S ITEM NUMBER
PID*F****VIM DETERGENT
SAC*C*ZZZZ***10*******06***CHARGE DESCRIPTION
SDQ*EA*92*0008*50*0020*10*0023*10*0024*15*0025*05
PO1*02*90*CA*200**UI*12345679125*IN*COSTCO'S ITEM NUMBER
PID*F****ICI SNOWSAME EXTERIOR PAINT
SAC*C*ZZZZ***10*******06***CHARGE DESCRIPTION
SDQ*EA*92*0008*50*0020*20*0023*20
PO1*03*90*CA*200**UP*12345679126*IN*COSTCO'S ITEM NUMBER
PID*F****ICI SNOWSAME EXTERIOR PAINT
SAC*C*ZZZZ***10*******06***CHARGE DESCRIPTION
CTT*3*270
SE*38*0001
GE*1*1
IEA*1*000000001.

There are many more types of dispatch requirement. For further queries, mail me at ambarnath@crossroadtechnologies.in

Classified POs in EDI

2008-12-30T23:33:00.000-08:00

An EDI 850 Purchase Order is an electronic version of a paper Purchase Order, generally referred as “PO”. Companies use EDI to reduce the errors and costs associated with the manual keying of data, and to speed up the process of sending and receiving Purchase Orders. A buyer will use the 850 Purchase Order to communicate to a supplier the specific items, price, and quantities they wish to have delivered.

One of the important aspects of PO is the different types of Purchase Orders which is passed through the BEG02 Segment of 850 EDI data transmission depending upon the customer’s requirement. This topic is put up to throw some light on the Purchase Order Type Codes.

Standalone [SA]: A discrete, one-time commitment to a supplier for material.

Rush Order [RO]: Requisition requiring issuance of a Purchase Order in less than 5 days. In order to avoid costly disruption of pre-planned programs, or to eliminate a significant safety or security problem, order must be accompanied by the Purchasers, justifying explanation. Here invoice can be sent after some time but the delivery should happen immediately. Generally this happens in the festive seasons.

Blanket order [BE] / [BK]: A blanket order is defined as an order the customer negotiates with its supplier. This order contains multiple delivery dates scheduled over a period of time for specific goods, sometimes at predetermined prices. It is normally used when there is a recurring need for expendable goods. Hence, items are purchased under a single purchase order rather than processing a separate P.O. each time new supplies is effected.
Types of Blanket Order
There are two types of Blanket Orders, one with firm quantity and the other with Estimated quantity.

Blanket order (firm quantity)[BK]: The Type Code of "BK" will identify a bulk Purchase Order, with store/quantity allocations. The same purchase order number in the bulk "BK" order will be transmitted in the release "RL" order.

Blanket order (Estimated quantity)[BE]: The Type Code of "BE" will identify a bulk Purchase Order, without store/quantity allocations ie Not Firm Commitment. The same purchase order number in the bulk "BK" order will be transmitted in the release "RL" order.

Advantages of Blanket Orders
For the customers, negotiating a blanket order will dispense him from holding large inventories of goods, while letting him avoid the administrative expense of processing frequent purchase orders. Also, it will often give him access to favorable discount pricing through volume commitments.
As for supplier, the advantage in signing blanket orders include better management of its own supplies, as well as better planning of delivery and production cycles. Also, signing blanket orders can ensure a steady workflow, rather than producing / supplying large quantities of products at irregular intervals.

Usage of Blanket Orders

Blanket purchase orders should be used when
• There is repetitive purchase of specific goods and service from the same supplier, which are paid in a predictable manner.
• Orders require numerous shipment / excessive storage.
• Enable the purchaser to obtain favorable pricing through volume discount.
• Supports a long-term relationship between the purchaser and the supplier.

Blanket purchase orders generally should not be used when
• No benefits will be derived over use of a regular Purchase Order (i.e. volume discount).
• Quality of services and goods supplied by vendor are questionable.
• No relationships exist between the purchaser and the supplier

Content of a Blanket Order
Blanket orders format usually include the following information:
• The beginning and ending time period for the blanket order;
• A cancellation clause;
• Items and/or categories of items to be covered by the blanket purchase order;
• The estimated quantity including a maximum (if any);
• Prices and pricing arrangements;
• Terms and billing arrangements;
• Personnel authorized to issue order releases;

Release Order [RL]: An order for goods and services placed against a pre-existing contract or blanket order The Type Code of "RL" will identify a release of a bulk order, with the store/quantity allocations transmitted in the SDQ segment. The same purchase order number transmitted in the bulk "BK" order will be transmitted in the release "RL" order.

Dropship [DS]: Dropshipping is a very common phenomenon in the Retail Industry. It gained popularity for its usefulness and commercial viability. We will discuss about it and also how should do we handle it in EDI ANSI X12.

What is Dropshipping And How Does it Work?
Drop-shipping means shipping products from a wholesale supplier directly to your retail customer. In other words, you sell products in your online store, and ship the goods to your customers directly from the warehouse of your drop-ship wholesale supplier.

Why would you want to do this? Well, you only BUY a product after you already SOLD it to your customer. There's no risk of having piles of unwanted stock in your inventory.

And if you've ever sold anything and sent the products to your customers, you'll know there's a lot of time, effort, and costs involved in packing and shipping things. When you're drop-shipping, the drop-ship supplier takes care of all that for you.

Won't the customers just go direct to my wholesaler and not buy from me any more?
With a good drop-shipper, your customer only has contact with you, not with the supplier. The wholesale products will be sent "blind" by the supplier so that your customers cannot trace the name and address of the drop-ship source.

Why Consider Drop Ship Wholesale Sourcing?
• You can start a business selling products without a large initial investment;
• You don't have to buy electronics in bulk - just order after you get paid by your customers;
• You can 'stock' your online shop with a huge range of the latest products;
• All the item descriptions and pictures, you can just copy from your supplier;
• You can list items for sale, and if they aren't popular, you didn't lose anything;
• No warehouse costs and no risk of 'dead' stock;
• You don't have to worry about packing materials, shipping labels, paying couriers for delivery, or customising the product contents for different regions;
• You can sell and ship to customers anywhere in the world;
• You set your own prices and profit every time you sell something!

Who can avail the benefit of Drop-ship Selling ?
• Anyone who wants to start a home based business
• Anyone who wants to start an online business
• Anyone who has an eBay business
• Anyone who doesn't want to hold inventory
• Anyone who doesn't like overhead costs

Benefits which can be derived from Drop ship consignment
• Eliminates cost of faxing, mailing, or overnighting packing slips
• Eliminates hard copy printing
• Increases availability and accuracy of up-to-date order status, shipping, and invoice information
• Improves customer service
• Reduces labor requirements
• Supports a broader selection of merchandise without additional inventory costs
• Enables faster revenue recognition
• Enhances revenue generation by extending peak/holiday selling seasons
• Improves supplier management

Direct ship—direct shipping [DR] and drop shipping are two terms generally used interchangeably. They describe a process whereby three parties interact with the sales transaction (the buyer, the seller, and the supplier). The buyer initiates a purchase from the seller who then arranges with the supplier to ship the product directly to the seller. The seller does not carry inventory of the product and the supplier does not have any direct communication with the buyer. The buyer pays the seller and the seller pays the supplier. Though both terms (direct ship and drop ship) are generally used to describe the same process, I've always considered a small distinction between the two that relates two where you are in the supply chain. To the seller, direct shipping describes both the process and an inventory/sales strategy, however, the supplier will frequently just use the term "drop ship" to describe the process whereby he is shipping the product to an address other than that of his customer (the business that is paying him for the product). Sometimes the term drop ship also describes the process of shipping to any location that is different from the customer's normal shipping location. This subtle distinction is sometimes evident in the terminology used in software documentation.

There are many more types of POs passed through BEG02, like, New Order [NE], Special Order [OS], Reorder [RE] etc which are also commonly used.

For any other info, mail me at madhurima@crossroadtechnologies.in

Importance and transmission process of Packing details

2008-12-29T03:00:00.000-08:00

In the retail industry packaging plays a key role in the business transaction. Product gets packed in intricate packaging process to facilitate logistic and customers’ ease of operation. This has to be passed properly through EDI segments in various documents to transmit properly between the Trading Partners. A few technical jargons are used to handle the packaging scenario and also used in EDI transaction. A brief discussion is presented below.

Most commonly used terms are :
Pack: The purchased unit which contains a specified quantity.
Pack ID: A unique alpha numeric code provided by the Vendor to represent a unique Case Pack
Inner Pack: A packing unit inside a Pack.
Inner Pack ID: A unique number that represents the packing unit inside a Pack.

Pack and Inner Pack related data transmission:
The PO4 Segment is used to transmit information about the packaging of the product being ordered in the case or carton. Two level of packaging may be specified. The first level, specified using PO401(Pack) which is Data Element 365, may be actual items, e.g., consumer units or may be the number of smaller containers within the case. The second level , specified using PO414(Inner Pack) which is Data Element 810 , is the number of eaches in each inner container when Data Element 356 is the number of smaller containers within the case.

Variation of Data Element Definition:

As defined in 3070
Data Element 356 : Pack-Number of inner pack units per outer pack unit
Data Element 810 : Inner Pack- Number of units in each selling pack or inner item

As defined in 4010
Data Element 356 : Pack-Number of inner containers, or numbers of each if there are no inner containers, per outer container.
Data Element 810 : Inner Pack- Number of eaches per inner container. Data Elements 356 and 810 (Pack) may be used to specify the packaging of the items in the case or carton.

Example A: No inner pack , ordering quantities specified in the cases.
In the Purchase Order, the item U.P.C . is specified and the unit of measure is Case. Data Element 356 is used and Data Element 810 is not used. The absence of Data Elements 810 indicates that the inner packs are not used.

VICS EDI example
Data Element Value
PO102              20
PO103              CA
PO401              10
PO414             Not Used

The total number of cases ordered is 20. The total number of eaches ordered is 150, case quantity ordered multiplied by Pack quantity (20*10=200)

Example B: No inner pack, ordering quantities specifics are in Eaches:
In the Purchase Order, the item U.P.C . is specified and the unit of measure is Each. Data Element 356 is used and Data Element 810 is not used. The absence of Data Element 810 indicates that inner packs are not present.

VICS EDI example
Data Element Value
PO102              20
PO103              EA
PO401              10
PO414             Not Used
The total number of eaches ordered is 200. The total number of cases ordered is 10, eaches quantity ordered divided by Pack quantity (200/10=20).

Example C: Inner Packs, ordering quantities specified in Cases:
In the Purchase Order, the items U.P.C. is specified and the unit of measure is Case. Data Element 356 and 810 are both used. The presence of Data Element 810 indicates that the inner packs are used, i.e., each case contains 6 small containers and each smaller container contains 4 of the units specified by the item U.P.C.

VICS EDI example
Data Element Value
PO102              10
PO103              CA
PO401              6
PO414              4

The total number of cases ordered is 10. The total number of eaches ordered is 240, case quantity ordered multiplied by the product of Pack quantity and Inner Pack quantity (10*(6*4)=240).

Example D: Inner Packs, ordering quantities specified in Eaches:
In the Purchase Order, the items U.P.C. is specified and the unit of measure is Each. Data Element 356 and 810 are both used. The presence of Data Element 810 indicates that the inner packs are used, i.e., each case contains 6 small containers and each smaller container contains 4 of the units specified by the item U.P.C.

VICS EDI example
Data Element Value
PO102              240
PO103              EA
PO401              6
PO414              4

The total number of eaches ordered is 240.The total number of cases ordered is 10, eaches quantity ordered divided by the product of Pack quantity and Inner Pack quantity (240/(6*4)=10).

Live Scenarios of usage of Pack/Inner Pack

Example 1: No inner Pack
Household cleaning product is the item in the example, packed 12 to a case. The shipping container is marked with a case U.P.C. and the items is marked with the consumer U.P.C. The product size is 5 ounces

Example 2: Simple Inner Packs
Cosmetic is the item in this example. The product is shipped using inner containers. There are 2 inner containers per shipping container and each inner container holds 6 consumer units. The shipping container is marked with a case U.P.C., the inner containers are not marked with any U.P.C. marking, and the item is marked with the consumer U.P.C. The product size is 3 ounces.

Example 3: Complex Inner Packs
Canned Vegetable is the item in the example. The product is shipped using inner containers. There are 6 inner containers per shipping containers and each inner containers holds 4 consumer units. The shipping container is marked with a case U.P.C., the inner containers are marked with a consumer U.P.C.(U.P.C.1 → considered as saleable item), and the item is marked with the consumer U.P.C. .(U.P.C.2 → also considered as saleable item). The product size is 8 ounces.

For any query, mail me at :
madhurima@crossroadtechnologies.in

Crossroad EDI Process : in a nut shell

2008-12-26T03:30:00.000-08:00

The EDI Process for Crossroad Technologies has been complied to provide a comprehensive guideline for the EDI team to undertake and perform any activities, which is directly or indirectly related with EDI. The process aims to detail all functional steps which needs to be complied with, documents that needs to be prepared and maintained and communication protocols that needs to be adhered to.

Scope of EDI Process

- Understanding of Functional Business requirement of Trading Partner(s)
- Study of Application Layout
- GAP Analysis
- Mapping Service
- Event Setup
- Map Translation
- Comprehensive Map Testing

We at Crossroad Technologies, India operation intends to undertake end-to-end functional EDI process activities based on specific customer requirement. The scope of this requirement may involve one or more of the process activities mentioned hereinabove. Keeping in tune with the customer requirement, the EDI team needs to plan and follow certain mandatory steps to make the execution process uniform. Crossroad’s scope of EDI process involves the following process activities.

GAP Analysis

GAP Analysis for EDI signifies identification of deficiencies in process processes and data. It involves comparing of data ie Application Layout available electronically in an existing system with data required as per a defined and agreed EDI standard (ANSI X12,EDIFACT,VDA,App to App etc.) between Trading Partners.

Typical GAP Analysis steps involves the following :

• Identification of all fields on paper claims

• Identification of all fields in Application File or Database or Parser File

• Identification of Manual Intervention within Process

• Determination of data fields which are required

• Determination of how to automate the transition process

Mapping Services

Mapping services involves steps which are necessary to code logic, to be followed for interchanging of an electronic document from one format to another. A code for mapping is typically done using a mapping workbench. The scope of mapping services includes detailed understanding of the GAP analysis document or Field Mapping Document (FMD) and coding the map as per the instruction of FMD. During the mapping process, the map developer may raise logical issues pertaining to mapping which needs to be clarified from VAN or Customer and included in the mapping process.

Typical Mapping steps involve the following :

Detailed study of FMD

Coding of map using workbench

Identification and raising of logical issues

Sought clarification regarding the raised issues

Incorporation of clarifications with regards to the issues

Translation of map

End to end testing of output generated per approved Test Plan

Comprehensive Testing

Comprehensive EDI Testing involves testing of GAP documents and Maps. All activity of the EDI process should be tested functionally by the testing team to ensure that the deliverables meet the stringent quality standard defined by the process.

The testing activities include :

Communication Testing

Data/ Business Logic and Data content/ Offset Testing

Validation and Code Testing

EDI Functional Blocks

We at Crossroad perform all its EDI related tasks in 4 distinct phases. This forms the building blocks of our EDI process. All the phases are independent and should stricktly adhered to conform to the process guidelines of the process.

Phase 1 : Analysis phase

It includes a) Identification of business process flow for the EDI document concerned (ie 850,810,856 etc) b) Development of Cross-reference spreadsheet to populate application layout.

Phase 2 : Setup phase

It covers a) Clear understanding of development tools and its Set up b) Preparation of stages for coding, translation and testing.

Phase 3 : Development phase

It includes a) Pre map GAP analysis, test data, EDI standard and versions b) Understanding the requirement of external cross reference table and exploring the inclusion of scripting possibility c) Coding on the work bench d) Consulting VAN/ Trading Partner for any technical/ non-technical clarification and e) Translation for getting the required output.

Phase 4 : Testing phase

It includes a) Communication testing b) Data/ Business logic testing c) Data content/ Offset testing d) Validation testing e) Code testing f) Bar code level testing and lastly g) Moving from staging to production scenario.

Documenting and reporting of EDI Process

As applicable for any technical process, the need of documenting activities related to EDI is of primary importance. Documents in different forms should be maintained at different levels and stages to enable retrieval of project related information as and when required. Documentation in EDI process covers maintenance of periodical reports, which should be prepared by the Project Managers and customary process related activity forms generally maintained by the EDI team.
The primary objective of documentation of EDI Process is to set a standard, which forms the SOP (Standard Operating Procedure) of Crossroad. All documents of EDI process should be following a conventional numbering system, which is easily understandable and referred to as and when required.

Listed below a few reports which are commonly used

Map Request form

Log Sheet

Map Status Report

Map Kit Issue List

GAP Analysis document (FMD)

FMD Issue Lists

Map Study and Mapping Issue list

Testing Issue Sheet

Map Code

Mapping Report

Minutes of Meeting

Ramping up a EDI Process

The ramping up process defines the necessary steps that need to be followed to start up a new EDI Project. Considering the nature of EDI Project, the ramping up steps may be adjusted or fine tuned to address specific project-centric need. The generic rules are as follows :

Identification of scope of the EDI Project : EDI Team

Techno Commercial Project proposal preparation : PM & Management

Signing of SLA : Management

Designing of Project-centric SOPs (Standard Operating Procedure) : PM

Identification of Resource : PM

Assigning responsibility, roles and service level expectation of Management : PM

Scheduling Training session for members for if required : PM

Training session of EDI Team on Technology and Tools to be used in the Project : PM & VAN

Appraisal of Team members and ascertaining comfort level in using Technology and tools to be used for the project.

Project Enunciation

The above mentioned process is a guideline to execute EDI process flawlessly. With the emergence of new technologies on daily basis, the existing process needs continual addition and improvement to accommodate new procedure which may me more efficient and robust. Thus a sustain and consistent effort is provided by Crossroad EDI Team to accumulate such new trends, practices and challenges which would be beneficial to process and continually present them to the QA department to update and accommodate them to the existing EDI process.

For any further query contact me at ambarnath@crossroadtechnologies.in

Segmentorial difference - VICS vs AIAG

2008-12-23T02:28:00.000-08:00

While studying Field Mapping Document for different clients and performed mapping, we came across many segments and elements which have specific usage. We analyzed a few doc types of VICS and AIAG and found significant difference so far segments is concerned. The difference is also found version-wise. The variation in segments is all need based and tool based patches are available to upgrade the work bench.

VICS
850 VER:4010

AIAG
850 VER:3010

Elements like Invoice Type Code, Contract Type
Code, Purchase Category, Security Level Code, Transaction Type Code of BEG segment are present.

These elements of BEG are not defined in the AIAG.

Composite element, Reference Identifier and its
sub/composite elements are present, in the REF segment under Header and Detail level.

These are not present in the REF segment.

Number of elements in PER segment is more.

Number of elements is less in PER Segment.

The element Customs Entry Type Group Code in the
TAX segment is present.

This element is not present in the TAX segment.

The CTP
segment is not present in the Header level, but in the Detail level.

The CTP
segment is present both in Header and Detail section

The CSH
segment comes after FOB segment in header level.

The CTP
segment comes after FOB segment in
header level, and the CSH comes in
the detail level only.

The SSS
segment is not Present at both the levels.

SSS segment is
Present at the header level after CTP
segment

TC2 Segment is
present at header level

TC2 is not
present here.

SAC segment is
present both in header and detail levels.

SAC segment is
not present here.

ITD segment is
present both in header and detail level

ITD segment is
present only in header level.

ITA segment is
not present

ITA segment is
present only in header level

Elements like Date Time Period Format Qualifier,
Date time period are present in DTM
Segment in both header and detail levels.

Date Time Period Format Qualifier, Date time
period are not present in the DTM

segments.

PID segment is
present in header and detail level.

PID segment is
present in detail level only.

PWK segment is
present in both header and detail levels.

PWK segment is
present only in header segment.

PKG segment is
present both in header and detail levels.

PKG segment is
present only in header level.

TD1 segment is
not present.

TD1 segment is
present in header level.

TD3 is present
in header level.

TD3 is not
present.

TD5 is present
in both header and detail levels.

TD5 is present
in only header level.

PCT segment is
present in header level.

PCT segment is
not present.

CTB segment is
present in header level.

CTB segment is
not present.

TD4 segment is
present in N1 group but TD5,TD1,PKG is absent in HEADER level.

TD1,TD3,TD5 segments
are present in N1 group.(HEADER LEVEL)

CTP segment in
detail level comes before CUR

PCT segment in
detail level comes after CUR

MEA segment in
detail level comes after CUR

MEA segment in
detail level comes after CTP

PO3 is absent
in PO1 group

PO3 is present
in PO1 group

SDQ segment is
present in detail level.

SDQ segment is
absent in detail level

SLN group is
present in detail level

SLN has no
group.

Let us see segment wise difference between VICS 856 VER:3050 and AIAG 850 VER:3050

VICS 856 3050 version	AIAG 856 3050 version
NTE,DTM segments come after BSN segment	Only DTM segment comes after BSN
PER segment comes under HL level	PER segment is absent
LH1 group comes under HL group	LH1 group is absent
MAN segment comes under HL group	MAN is absent
N2,N3,N4,REF,PER, FOB come under N1 group	Only N2, REF come under N1 group
SDQ comes under HL level	SDQ is absent.
GF segment comes under HL	GF is absent
LM group is present under HL	LM group is absent under HL

For any other query mail me at ambarnath@crossroadtechnologies.in

Anatomy of DUNS#

2008-12-22T03:33:00.000-08:00

Numbering system has always played a key role in our life. It has offered us many ways to handle complicated data handling with help of unique key concept. When companies multiplexed in numbers with associated warehouses and departments, it’s become important for the controlling authority to assign unique identity and hence DUNS # was born. It helped them to find out relevant information and keep track of activities.

The Data Universal Numbering System, abbreviated as DUNS or D-U-N-S is a unique nine- digit identification number, developed and regulated by Duns & Bradstreet (D&B) in 1962 to identify unique business establishments. The D-U-N-S Numbering system was recommended in 1992 by the United Nations as a global standard for business identification and endorsed by more than 50 global industry associations.

Features of DUNS#

· The DUNS Number is assigned to each business location in the D&B database having a unique, separate, and distinct operation to businesses for the purpose of identifying them.

· The DUNS Number is site-specific. Therefore, each distinct physical location of an entity (such as branches, divisions, and headquarters) may be assigned a DUNS number. Organizations should try and keep DUNS numbers to a minimum. In many instances, a central DUNS number with a DUNS number for each major division/department/agency that applies for a grant may be sufficient.

· In order to provide on-the-spot DUNS number assignment, the requestor should do this by telephone.

Benefit of DUNS#

- Helps businesses around the world identify potential trading partners.
- Eliminates duplicate file entries
- Link companies within the same corporate family.
- Enhances the credibility of your business in the marketplace
- Enables potential customers, suppliers and lenders to easily identify and learn about your company
- Several Governments and many major corporations globally require their suppliers and contractors to have a D&B D-U-N-S® Number

DUNS# path of success

1.Its recognition as a global business identification standard for:

American National Standards Institute ANSI ASC X12 -- since 1989
United Nations/Electronic Data Interchange for Administration, Commerce and Transport/UN EDIFACT Council -- since 1991
European Commission (EDIRA)
International Standards Organization (ISO) -- since 1993
United States Federal Government

Electronic Commerce Acquisition Team (ECAT) -- since 1994
Federal Energy Regulatory Commission (FERC)
United States Postal Service (USPS)
North American Free Trade Agreement (NAFTA)

2. The federal government has adopted the D&B D-U-N-S Number as a principal contractor identification code.

Facilities provided by DUNS# to the users

Identify cross-selling opportunities within the same corporate 'family'
Eliminate duplicate file entries in your own customer and supplier information warehouses
Streamline your transactions and simplify communications with e-commerce
Act as a common classifier or identifier for invoices, requisitions, payments, shipping, customs clearances and other business documentation
Reduce operating costs by linking interrelated suppliers and increasing purchasing power
Tap revenue and customer service opportunities by uncovering prospects and linking related customer accounts to support a 'one-customer' view
Integrate your internal systems by rolling up payables and receivables

Significance of DUNS# in EDI

The D-U-N-S Number system fits within the electronic data interchange (EDI) scheme adopted by the EDI Registration Authorities Project (EDIRA).

The European Commission is the third major international organization to recognize the D-U-N-S Number as a standard for electronic data interchange (EDI). The United Nations and the International Standards Organization previously extended recognition.

The D&B D-U-N-S Number is an internationally recognized common company identifier in EDI and global electronic commerce transactions.

Scenarios of using DUNS# in the ISA/UNB record

DUNS (Dun & Bradstreet) numbers are assigned to each of our facilities to differentiate shipping addresses. DUNS Plus numbers will be assigned to our service facilities to differentiate releases to different organizations, usually service and production, with the same ship-to address. These unique identifiers are comprised of the number used for the production facility with the addition of the suffix "XYZ". The "....XYZ" numbers should be used ONLY for determining the ship-to address for a purchase order release. Do not use the DUNS plus numbers for invoicing or correspondence.

Location of the DUNS number in the EDI set

In ANSI X12 test data, DUNS # can be used in ISA, N1 and SDQ segments. The usage depends on the Retailer’s requirement and VAN’s support. EDI segments are so designed that it can carry DUNS # easily to handle various scenario.

In ANSI X12, N1 is the Name segment in which N103 is the Identification Code Qualifier

The DUNS number will be in the ship-to address in the N1 segment, coded "ST".

If N103=1 then it is a D-U-N-S Number

If N103=9 then D-U-N-S+4, D-U-N-S Number with Four Character Suffix Dun & Bradstreet DUNS Number with a four-digit suffix identifying a specific location within a company, e.g., a distribution center or a store. This number may or may not contain the nine digits associated with the parent company

IN EDIFACT, NAD is the Name and Address segment in which NAD0202=Code List Qualifier

If NAD0202=46 and NAD0203=16 then it is a D-U-N-S Number authored by Duns & Bradstreet

Some useful links on DUNS #

http://www.grants.gov/applicants/request_duns_number.jsp
http://www.nea.gov/grants/apply/DUNS.html
http://www.beallsinc.com/vendor/bealls/edi_mapping_requirements.htm

Popular product coding convention in EDI

2008-12-18T03:41:00.000-08:00

UPC Code
There are a variety of different types of bar codes. However, the U.P.C. symbol is the most recognized bar code in the United States, established in 1970’s, since it appears on almost every retail product. The U.P.C. symbol is the bar code representation of the GTIN-12. (Universal Product Number) which consists of twelve numeric characters that uniquely identify a company's individual product. Although, the initial U.P.C. usage was focused on retail point of sale (POS), many other industries have adopted this coding structure This code is designed to uniquely identify a product and its manufacturer and allows it to be scanned and read in virtually any major retail establishment.

Pattern of UPC Code Formation
The first 6 digits represent the manufacturer of the labeled item, as assigned by the Uniform Code Council. The next 5 digits identify a particular product assigned by the manufacturer. The twelfth digit is a check character, based on an algorithm using the previous 11 digits.

Variations of UPC Code:

UPC/EAN Case Code(2-5-5)
A 12 digit number identifying the manufacturers shipping unit. The code division is 2-5-5. Its qualifier is UA The code is formatted as: 2 digit number system character(U.S. Grocery and General Merchandise=00,06 or 07; US Drug=03)(EAN=2 digit country flag); 5 digit manufacturing identification number; 5 digit item number

UPC Consumer Package Code(1-5-5)
The 11 digit Universal Product Code that uniquely identifies each customer unit. The code division is 2-5-5. Its qualifier is UI. Multipacks should use qualifier UB. The code is formatted as: 1 digit number system character(U.S. Grocery and General Merchandise=0,6,7; US Drug=3; 5 digit manufacturing identification number; 5 digit item number

UPC Consumer Package Code(1-5-5-1)
The 12 digit Universal Product Code that uniquely identifies each customer unit. The code division is 2-5-5. Its qualifier is UP. The code is formatted as: 1 digit number system character(U.S. Grocery and General Merchandise=0,6,7; US Drug=3; 5 digit manufacturing identification number; 5 digit item number; 1 digit check digit

UPC/EAN Shipping Container Code(1-2-5-5-1)
The 14 digit code that identifies the manufacturer’s shipping unit, including the packaging indicator and check digit. The code is formatted as: 1 digit packaging indicator; 2 digit number system character (U.S.Grocery and General Merchandise=00,06,07; U.S.Drug=3; 5 digit manufacturing identification number; 5 digit item number; 1 digit check digit

Benefits of UPC
Provides Item Identification
Speed at retail checkout
Reduce data entry costs
Reduced errors

Check digit calculation
In the UPC-A system, the check digit is calculated as follows: 1. Add the digits in the odd-numbered positions (first, third, fifth, etc.) together and multiply by three. 2. Add the digits in the even-numbered positions (second, fourth, sixth, etc.) to the result. 3. Find the result modulo 10 (i.e. the remainder when the result is divided by 10). 4. If the result is not zero, subtract the result from ten. For example, a UPC-A barcode (in this case, a UPC for a box of tissues) "03600029145X" where X is the check digit, X can be calculated by adding the odd-numbered digits (0+6+0+2+1+5 = 14), multiplying by three (14 × 3 = 42), adding the even-numbered digits (42+3+0+0+9+4 = 58), calculating modulo 10 (58 mod 10 = 8), subtracting from ten (10 - 8 = 2). The check digit is thus 2.

UPC Case Code
A barcode symbol for physical distribution in U.S., which is the prototype of Standard Symbology for Physical Distribution. On concentrated packages, like the cardboard case, adding 0 before UPC code of content product, for correspondence with EAN; and more, adding before that a 1-digit distinction code for indicating quantities, to display both content product and quantities in the package.

Contribution of EDI in UPC generation/transportation
An EDI 832 Transaction Set can be used to load the catalogs with UPC information or by the registration number ie maufacturer’s block ID, UPC can be generated and loaded in the catalogs. A supplier can load their product codes one time and all of their retailers can pull the information.

EAN Code
The European Article Number is the European version of the UPC (Universal Product Code) bar code of retail food packaging that enables this linear bar code to be used internationally. Like the U.S. equivalent UPC code, there are two different types of EAN codes, EAN-8 and EAN-13

EAN-8:
EAN-8 has a left-hand guard pattern, four odd parity digits, a center guard pattern, four even parity digits, and a right hand guard pattern with a total of eight symbols.

EAN-13:
EAN-13 has 13 characters or symbols. It is very much like the UPC code and has the 13th character as a means of identifying in what country the product will be used.

European Article Number(EAN) (2-5-5-1)
13 digit code used by countries, other than the United States and Canada, to identify each consumer unit. Code is formatted as: 2 digit country flag; 5 digit company identification number (assigned by European Coding authorities); 5 digit article identification number (assigned by the company); 1 digit check digit.

NDC Code
The National Drug Code (NDC) serves as a universal product identifier for human drugs and biologics. The NDC is presented in several formats. The 11-position format was adopted as the standard. The NDC is divided into 3-segments. The 11-digit format is the format adopted by the Final Rule as noted in the Preamble: “We are adopting the 11-digit NDC in order that the format is distinctive and will be in place until the Secretary decides to adopt a new code system.” The first segment is the labeler code that identifies any firm that manufactures, repacks/distributes a drug product. The second segment is the product code. It identifies the strength, dosage form and formulation. The third segment is the package code. This segment identifies package size. P0106=ND*11-Digit code

ISBN Number
An ISBN is assigned to each edition and variation (except reprintings) of a book. The ISBN is 13 digits long if assigned after January 1, 2007, and 10 digits long if assigned before 2007. An International Standard Book Number consists of 4 or 5 parts: 1. For a 13 digit ISBN, a GS1 prefix: 978 or 979 2. the group identifier code, (group of countries sharing a language) [3] 3. the publisher code, 4. the item number, and 5. a checksum character or check digit.

By using variable block lengths, a large publisher will have few digits allocated for the publisher number and many digits allocated for titles; like-wise countries publishing much will have few allocated digits for the group identifier code number, and many for the publishers and titles. Here are some sample ISBN-10 codes, illustrating block length variations.

Check digit in ISBN-13
The 2005 edition of the International ISBN Agency's official manual[10] covering some ISBNs issued from January 2007, describes how the 13-digit ISBN check digit is calculated. The calculation of an ISBN-13 check digit begins with the first 12 digits of the thirteen-digit ISBN (thus excluding the check digit itself). Each digit, from left to right, is alternately multiplied by 1 or 3, then those products are summed modulo 10 to give a value ranging from 0 to 9. Subtracted from 10, that leaves a result from 1 to 10. A zero (0) replaces a ten (10), so, in all cases, a single check digit results.

Purpose of an ISBN
The purpose of the ISBN is to establish and identify one title or edition of a title from one specific publisher and is unique to that edition, allowing for more efficient marketing of products by booksellers, libraries, universities, wholesalers and distributors.

Format of the ISBN
Every ISBN consists of ten digits and whenever it is printed it is preceded by theletters ISBN. The ten-digit number is divided into four parts of variable length, each part separated by a hyphen.

Meaning of ISBN numbers
The four parts of an ISBN are as follows: Group or country identifier which identifies a national or geographic grouping of publishers; Publisher identifier which identifies a particular publisher within a group; Title identifier which identifies a particular title or edition of a title; Check digit is the single digit at the end of the ISBN which validates the ISBN.

SKU
SKU (stockkeeping unit, sometimes spelled "Sku") is an identification, usually alphanumeric, of a particular product that allows it to be tracked for inventory purposes. Typically, an SKU (pronounced with the individual letters or as SKYEW) is associated with any purchasable item in a store or catalog. An SKU is not the same as a product model number from a manufacturer, although the model number could form all or part of the SKU. The SKU is established by the merchant. Successful inventory management systems assign a unique SKU for each product and also for its variants, such as different flavours or models of product or different bundled packages including a number of related products. This allows merchants to track, for instance, whether blue shirts are selling better than green shirts.

Example SKU system
An imaginary product, called a widget, has a part number of 1234. It is packed 20 to a box, and the box is marked with the same part number 1234. The box is then placed in the warehouse. The box of widgets is the stock keeping unit (SKU), because it is the stocked item. Even though the part numbers are interchangeable to mean either a widget or a box of widgets, the box of widgets is the stocked unit. There may be three different colors of widgets; each of these colors will be a separate SKU. When the product is shipped, there may be 50 boxes of the blue widgets, 100 boxes of the red widgets, and 70 boxes of the yellow widgets shipped. That shipment would be said to have been a shipment of 220 boxes, across three SKUs. Another example is a product given an article number 4321. Within the last 2 years Vendor X has been making article number 4321. Vendor X is going out of business, yet the plans for making article 4321 still belong to the selling company. The selling company now has two companies making the same product during the transition phase. Instead of tracking variants by maker, it uses UPCs, and possibly "color" or "dye" or similar. It will still hold the same article number for daily, weekly, monthly, quarterly, and yearly profit margins. SKUs link UPCs from the vendor to the retail company. A single SKU can have many UPCs. Makers use UPCs to see if it is worth making green when red accounts for 99% of the market. Selling companies use SKUs to see which company performs better with the same item. Another example is if a particular product has an MRP of x & there is a revision in price, say the price now becomes y. Then x & y will have to be stocked separately & billed separately so they become two different SKUs

For any query, mail me at :
madhurima@crossroadtechnologies.in

Enable EDI Test Plan creation and the Testing process

2008-12-15T21:35:00.000-08:00

It was a rare occasion in my life to work for a Project when everything was unknown what we were supposed to do. My senior called me up just to say “We have to do this as a challenge, i have already signed the Contract ..... “ and I just replied “Yes Boss .. “.

The Project had two parts, in one part we had to generate the mapping instruction and application set up, on the other part complete test plan creation and testing. When the developer used to complete the code development, and the basic backend set up was done, we used to start testing as per approved test plan. I like to discuss about the typical testing process and test plan creation which was devised by us and appreciated by the client.

The testing process approach was as follows :

Installation & Registration Testing
Installation test will check the configuration path for starting testing.

Entry Criteria: Registration setup configuration, Source path of test data loading and corresponding populated inbound and outbound flat file path, Error Notification mail configuration, scheduler configuration should be completed. Trade Gateway application should be also completed.
Activities: Execute following steps for various actions

- Registration of new Vendor
- Checking of PO, ASN, Invoice and other docs using vendor ID & password (created in earlier step)
- Loading PO (850) on TG web EDI application
- Getting inbound flat files (Successful Translation)
- Getting inbound flat files (Unsuccessful Translation)
- Getting outbound flat files
- Getting outbound ‘X12’ file

For all these activities we had to either logged into a particular staging server or look into a predefined folder for the output.

Deliverable: Test Plan with test log and Ramp Issue Log
Proof of Execution: Loading of PO through registered Vendor’s Login ID/ Password
Exit Criteria: Successful loading of PO in TG web application through Vendor’s Login/ Password. Collecting populated Flat Files and x12, if applicable.

Build Acceptance Testing
Build acceptance test is a check to ensure that the retailer’s mapping specification match the TG web EDI functionality in order to determine if further testing can be executed.

Unit Testing
Unit testing is a verification effort on the smallest unit of the software component or module like 850, 856, 810, 860, 855 etc. Unit testing is mainly focused on following areas

Entry Criteria: Availability of Modules with stable build
Activities: Preparation of Unit Test cases, Testing with provided test data, in case of insufficiency, have to build test data for checking and execution of test cases.
Deliverable: Test plan document with test results, test data used, inbound flat files/ outbound flat files/ X12, screen shots of front end page (if required), Ramp Issue Log and test status report.
Proof of Execution: Review of Test Plan document, Traceability Matrix for all test cases, review of test data/flat files/x12 documents, PO#/ASN#/Invoice# for passed test cases and screen shot with explanation for failed test cases.
Exit Criteria: Sign off test plan, Sign off Unit testing

Integration Testing
The primary objective of integration testing is to discover errors in the interfaces between Modules / sub systems like 856 web.htm-856 web-confirm.htm /810 web-confirm.htm-810 web.htm / 856 web.htm-856 pick pack.htm / 850 web.htm-850 SAC detail / 850-856-810 chain.

Entry Criteria: Availability of Modules with stable build
Activities: Preparation of Unit Test cases, Testing with provided test data, in case of insufficiency, have to build test data for checking and execution of test cases.
Deliverable: Test plan document with test results, test data used, inbound flat files/ outbound flat files/ X12, screen shots of front end page (if required), Ramp Issue Log and test status report.
Proof of Execution: Review of Test Plan document, Traceability Matrix for all test cases, review of test data/flat files/x12 documents, PO#/ASN#/Invoice# for passed test cases and screen shot with explanation for failed test cases.
Exit Criteria: Sign off test plan, Sign off Unit testing

End to end Testing
The primary objective of End-To-End testing is to discover errors when the system is tested as a whole. End-To-End testing is mainly focused on following areas

- Identifying the End-To-End / Business Life Cycles.
- Design the test and data.
- Optimize the End-End / Business Life Cycles.

Entry Criteria: Successful completion of Integration testing
Activities: Preparation of End to end test scenarios and execution of the same
Deliverable: Complete Test plan document with test results, all the tested input and output files, Ramp Issue Log and test status report.
Proof of Execution: Review of test plan document with traceability matrix for all the test cases transaction set wise for passed test scenarios and screen shot of failed Test Case scenario.
Exit Criteria: Sign off test plan document as “Testing complete at staging and its ready to go live”

Regression Testing
Testing the new build to ensure enhancements implemented correctly and existing functionalities are stable and not corrupted.

Entry Criteria: Testing of change requirements are signed off
Activities: Execution of regression test scenario
Deliverable: Regression Test with defect report along with Ramp Issue Log.
Proof of Execution: PO#/ASN#/Invoice# for passed test scenario and screen shots of failed scenario
Exit Criteria: All regression cases should be executed and test reports should be updated accordingly

Reliability Testing
Reliability Testing is a property, which defines how well the results match the specifications. Reliability is considered as the probability of failure-free operation for a specified time in a specified environment.

Reliability Testing helps you to confirm: Business logic conformity, proper controls (Buttons, Labels, Captions etc.) display on front end, Reliable hyper links navigation, correctness of generated outbound X12 etc.

Entry Criteria: Functionality testing is signed off
Activities: Preparation and execution of test scenario
Deliverable: Test plan document with test result, Ramp Issue log (if applicable), Test status report
Proof of execution: PO#/ASN#/Invoice# for passed test scenario and screen shots of failed scenario
Exit criteria: Stability of the application

Test Scenarios
Test scenarios will be identified for each module Test scenarios will be associated with both positive and negative data optimization of test scenarios will be taken care as the test cycles increase

Test Cycle
- Test cases and Test scenarios will be base lined for each test cycle
- Test execution reports and metrics will be maintained independently for each cycle

Dependencies
Every testing scenario has a few operational dependencies. As in this case we used to access ICC’s remote boxes with other required inputs I am spelling them out.

() Retailer specific TG screen shots should be available for desired field display and content testing
() Map specification template
() Servers availability with super-user rights
() Scheduler should be available and tuned properly
() Staging setup should be available
() Map development should be complete and released into the proper path with publicacy.

Complete test data (850 X12) should be made available before testing

Status Reporting
The service agency will provide the status reports frequently to ICC. The status report will contain the following items:

-Daily status reports will be provided with the progress of task.
-Weekly status report will be provided with the Planned/Actual/Pending tasks and also forecast for the coming week.
- Monthly status report will be maintained to understand Planned task progress Issues related to the task Need for the allocation/de-allocation of resource.

For any query, please mail me at ambarnath@crossroadtechnologies.in