EDI_BASICS

I am giving training on Sterling Integrator and MFT concepts Contact Me

EDI Quiz

EDI Definition: EDI(Electronic Data Interchange) is a standard format for exchanging of BUSINESS DOCUMENTS between computer to computer(Bussiness to Bussiness)

OR

The process of electronically exchanging business documents in a standard format is called EDI.

Examples: Purchase Order -850
Advanced Shipment Notification -856
invoice 810

What are the advantages of EDI when compared to other data formats?

EDI is automated.
Less human intervention.
Maintains huge volumes of transactions.
Less operating cost.
Eliminates time delays.
Eliminates data entry errors.
Less time.
Security.
Higher throughput.
Reentering the repeating data can be avoided using the looping concept.

What are the different communication channels for EDI?
VAN (Value Added Network).
Internet Service Provider.
Point-To-Point (Direct Cable Network).
Proprietary Network.
E-Mail.

What do you know about VAN?
VAN is a specialized application service provider that acts as an intermediary between trading partners for sharing data or business processes.
VAN’s served as “electronic post office” for buyers and suppliers that need to exchange data, validation, and delivery monitoring.
They offered store-and-forward mailboxes that provide protocol conversion, security, and guaranteed delivery using software and hardware encryption.
Secure protocols that it supports are AS1, AS2, AS3, FTTP(S), HTTP(S), SMTP, POP3.

What does 12 represent in X12?
The number 12 represents a subcommittee of twelve.

What is EDI-INT?

A set of standards that define a common method for sending EDI messages over Internet.
EDI-INT provides guidelines for encryption, decryption, and confirmations of through Message Disposition Notifications (MDN).
Internet EDI consists of three established standards (AS1, AS2, AS3) to securely transport EDI documents over the Internet.

6) What are AS1, AS2, AS3?

Applicability Statement 1(AS1), Applicability Statement 2(AS2) are industry standards for Internet-based data exchange.
These standards simplify communication by reducing the number of technologies an organization must support and manage.
If every large organization used a different data transport standard, it would be cost-prohibitive for their smaller business partners to exchange data with them electronically.
AS1 and AS2 allow organizations to implement one solution for data exchange with all business partners using an AS1 or AS2 solution.
The AS1 the standard is a way to securely transport EDI documents over the Internet via SMTP (email).
The AS2 the standard is a way to securely transport EDI and XML, any documents over the Internet via HTTP.
The AS3 the standard is a way to securely transport EDI documents and XML over the Internet via FTP.

The below are standard EDI X12 Envelop begin and end segments.

ISA—Interchange Envelops, 106 bites/characters

GS---------Group Envelop, 82 bites/characters 82

ST-------Transaction Envelops---17 bites/characters

SE----24 bites/characters

GE--20 bites/characters

IEA---20 bites/characters

ISA:

This interchange envelope contains 106 characters.

Example Segment:

ISA*00* *00* *12*3109260947 *ZZ*AMAZON *150326*0811*U*00401*856900845*1*P*>~

FLD_ID NAME SIZE DATA REMARKS

-------------------------------------------------------------------------

ISA01 Authorization information qualifiers -- 2-- 00

ISA02 Authorization information -- 2 --BLANK

ISA03 Security information qualifiers ---2 --00

ISA04 Security information ---2 --BLANK

ISA05,07 Interchange ID qualifiers --- 2 --01 sender,receiver

ISA06 sender id 15 3109260947 type of data entered is determined by the qualifier in element ISA05

ISA08 Receiver id 15 AMAZON

ISA09 DATE 6 YYMMDD

ISA10 TIME 4 HHMM 24hours

ISA11 Repetition separator 1 ^ or U it's not data, its delimiter

ISA12 Interchange control version 5 00403its standard version, sub release num

ISA13 Interchange control number* 9 856900845 its unique identification envelop

ISA14 Acknowledgement Request 1 1 or 0 it's used to know senders envelop send successfully or not.TA1-its placed between ISA ---GS (ISA14 is set to 0, so do not send a TA1. It is not supported and will cause an error)

ISA15 Usage indicator 1 I-P-T whether the data in the product.

ISA16 component Element Separator 1 > separate elements

IEA:------ IEA*1*856900845~

IEA01 NUMBER OF FUNCTION GROUP ENVELOPS 1/5

IEA02 Interchange control Number* 9 856900845 ISA13, GS6(Processing software to identify based on control number are equal)

Why should we have sender id in ISA, GS?

Using ISA/GS to identifying the Treading Partner code.

Interchange Sender ID—UNB for EDIFACT AND ISA 06 FOR X12
Application's Sender Code—UNG for EDIFACT and GS 02 for X12

Explain about TA1 Acknowledgement?

Using TA1 Acknowledgment, the sender receives the acknowledgment for receiver id is correct.

If Sender sets ISA14 Element is 1 then the sender receives an acknowledgment. if the sender sets '0' then he didn't receive any Acknowledgment.

TA1--DOCUMENT LIKE BELOW
ISA*SEGMENT~

GS*SEGEMENTS~
TA1*ACKNOWLEDGEMENT STATUS~
GE*SEGEMENTS~

IEA*SEGMENTS~

What is the Use of Control Numbers?
Processing software uniquely identifies successful and failed interchanges, groups, transactions using control numbers.

Following are control number identifies in EDI
ISA--13
GS---06
ST---02

What is a Repetition separator in ISA-11?

A repetition separator is a character that separates repeating occurrence of a data element or component elements in the same position within the same data segment context.

What is the component element separator ISA-16?

A component element separator is a character that separates subelements or component elements in a composite element.

NOTE: The above three elements are unique control numbers that easily identify a transaction.
ACKNOWLEDGEMENT 997 uses the control number to report back processing successfully.

HOW TO FIND THE NUMBER OF TRANSACTION SETS R INCLUDES IN FUN.GROUP(ST, SE)
based on ST,SE sets AND CONTROL NUMBERS
997 is a must for every document.
yes.

*********************
GS:----GS*SH*3109260947*AMAZON*20150326*0811*856900845*X*004010~
GS01 Functional ID code -2 PO,SH,IN
GS02 Application Sender's Code 2/15 3109260947
GS03 Application Receiver's Code 2/15 AMAZON
GS04 Date 8/8- CCYYMMDD
GS05 Time 4/8 -HHMM
GS06 Group Control Number 1/9 856900845 –SAME AS ISA13 BUT NOT
GS07 Responsible Agency Code 1-X
GS08 Version/Rel. Ind. ID Code 1/12 004010

GE:
GE*4*856900845~
GE01 Number of Transaction Sets Included in this Function Group---1/6 -
GE02 Group Control Number (same as GS06)------------1/9

ST-Segment
ST01 Transaction set ID code------- 3--850(po)
ST02 Transaction set control number --a unique number-
ST03 - A reference assigned to identify an Implementation Convention (not in
common use)
SE Segment:
SE01 Number of included segments----
SE02 Transaction set control number (same as ST02)

************************

What are the Basics Profile configuration for a Trading partner?

Following are the configuration to create a treading partner
1.Identities -- Primary-ID that identifies this trading partner. This can be a Data Universal Numbering System (DUNS) number, EDI interchange ID, e-mail address, or another unique string. Required.
2.Transports: Which protocol they are using to transport the data between partners. Ex: FTP,HTTP,AS2,SFTP
3.Document Exchange: Which type of documents/messages the partner using. Ex: EDI, EDIFACT,XML,CSV,Positional
4.Delivery Channel: Links a document exchange record and a transport record
5.Packaging: Describes the organization of a document and its contents
6.Profiles: Links a delivery channel record and a packaging record to a business process

------
Explain the inbound and outbound envelop setup?
Ans: In Sterling integrator, we have to create envelopes like ISA GS ST for both inbound and outbound flow.

Why should we create ISA, GS, ST envelops for the outbound process?
Ans: Basically, in The outbound process in the sterling integrator, We are adding the envelopes to original data. so we have added the first ST envelops then it will call GS to envelop after that ISA envelop.
so, in the creation of envelopes, we will give the ISA envelop name in GS Envelop so it can easily identify the envelopes.

What is the base envelop and why we are not select the base envelope?
Ans: Sterling B2B Integrator uses a concept of a base envelope as a starting point to create a new envelope.
The base envelope maintains a link to the new envelope that inherited its properties. If you modify the base envelope,
all related envelopes (that is, ones that inherited the base envelope properties) change, as well.

What are the envelopes in a trading partner?
Ans: Interchange (outermost) – Contains an interchange header and trailer, and all the data sent from one sender to one receiver in the same transmission.
The functional group (middle) – Contains a group header and trailer that surrounds a group of transaction sets of the same type.
Transaction set (innermost) – Contains the standard message surrounded by a header and trailer record.

5. Tell me some X12 Transactions which u worked on?
Ans: 810 invoices,
820 planning schedule for remittance advice
850 purchase order,
855 purchase order acknowledgment

6. Tell me some EDIFACT messages which u worked on?

Ans: ORDERS - Purchase order message
ORDRSP - Purchase order response message
DESADV - Dispatch advice message

TRANSACTION WISE ELEMENTS:
850-PURCHAGE ORDER:
BEG*00*NE*PO234567*19990413
SE
BEG-Beginning Segment for purchase order--
BEG03-PURCHASE ORDER NUMBER
PER-Administrative communication
PER02-BUYER NAME
ITD-to specify terms and sales
ITD03-Term discount present
FOB-specify transportation instructions relating to the shipment
FOB01-SHIPMENT METHOD TYPE

TD5-carrier details
LOOP:
N1--NAME
N2-name and address
N3--Address information
N4--Geographical information
PO1--BASELINE ITEM
PO101-Assigned Identification
PO102-Quantity Ordered (must of the transaction)
PID-Product item Description
MSG
SAC---services allowance and charges information(its contain looping)-optional
CTT-Transaction Totals
CTT01 354 Number of PO1 Items M N0 1/6
Total number of line items in the transaction set

CTT 02-PO1-02(Sum of Quantity orders)
--------------------------------------------------------------
855-PURCHASE ORDER Acknowledgement

BAK-Beginning Segment for Purchase Order Acknowledgement
BAK01-Transaction set code
BAK03-Purchase order number
DTM: Date /Time reference
FOB: To specify transportation instructions relating to the shipment
FOB01-SHIPMENT METHOD TYPE
LOOP--N1
N3
N4
PO1--BASELINE ITEM
PO101-Assigned Identification
PO102-Quantity Ordered

ACK-Line Item Acknowledgment

ACK-01 -Line Item status code

ACK -02-Qty

ACK-03 -unit basic mesurements
PID-Product item Description
SAC---services allowance and charges information(its contain looping)-optional
CTT-Transaction Totals
CTT01 354 Number of PO1 Items M N0 1/6
Total number of line items in the transaction set
CTT 02-PO1-02(Sum of Quantity orders)
------------------------------------------------------
856-Shipment notice

BSN-Beginning Segment for Ship Notice
BSN02-shipment reference code

HL-Hierarchical Level
HL-1-S SHIPMENT
HL-2-P PACKATE
HL-3-O ORDER
HL-4-I ITEM
TD5-carrier details
TD504-Transport Method
DTM
FOB. Related Instructions
FOB01-SHIPMENT METHOD TYPE
LOOP--N1
N3
N4 --DUNS NUMBER
HL-Hierarchical Level
HL02-shipment parent ID
PRF-Purchase Order Reference
PRF01-PURCHASE ORDER NUMBER
REF-------Reference Identification---
HL
LIN-line item
SN1-Item Details
SN102-NUMBER OF UNITS SHIPPED
PID -product item description
HL
MAN---marks, and numbers
CTT-TRANSACTION TOTALS
CTT 01NUMBER OF HL LINE ITEMS
CTT 02 SUM OF SN1-02
------------------------------------------------------------------------
810-INVOICE

BIG--BIGINING SEGMENT FOR INVOICE
BIG02-INVOICE NUMBER
BIG03-PURCHAGE ORDER NUMBER
N1
N3
N4
TID: Terms of Sale/Deferred Terms of Sale
DTM
FOB
IT1--Baseline item data
PID -product item description
SAC---services allowance and charges information(its contain looping)-optional
TDS Total Monetary Value Summary
TXI Tax Information
CAD Carrier Detail
SAC---services allowance and charges information(its contain looping)-optional
CTT Transaction Totals
CTT01--NUMBER OF LINE ITEMS
IT1-01

-------------------------------------------------
820--------SHIPMENT/REVEN.
BPR-Beginning Segment for Payment Order/Remittance Advice
TRN Trace-------
CUR Currency----
REF Reference Identification------
DTM Date/Time Reference
ENT Entity
RMR Remittance Advice Accounts Receivable Open Item Reference
ADX Adjustment
PER--

----------------------------------------
204 ---- Load Tender
**Load Tender Require at least one load request
The shipment ID number(SID)
**Ship-From Location (Address, City, State, ZIP)
**Ship-To Location (Address, City, State, ZIP)
** Total Handling Units
** Total Weight
** Requested Pickup Date – current or future-dated only
** Freight Ready and Dock Close Times
** Pickup Contact Information (Name, Phone Number)

204:

B2--Beginning Segment
B202--SCAC Code
B204 --SIN (Shippment Identification Number)
B206 -- Payment Method

B2A--Set Purpose
B2A01--TransactionSetPurpose Code ADD or Update or Cancel
B2A02--Application Type --BL or LT
L11--Reference Number

S5--Stop-Off Details
S501-Stop Sequence Number
S502-- STOP REASON CODE(PICKUP/DROP)
S503-WEIGHT
S505-NUMBER OF UNITS SHIPPED
OID--Order Identification Information
OID02-Purchase Order Number

G62- DATE/TIME
N1 --Name
N3--Address
N4--Geographic location
G61 Contact
L3 -- Total weight and charges
L3-01 - Total weight charges
L3-05 - Charges
L3-09-VOLUME
LH- Hazard Information

LOGISTIC FLOW

---------------
AFTER 856

CUSTOMER-----CARRIER(LOGISTIC)
107 ------>
<------ 106
204------->
<--------990
<--------214
<--------210
820--------->

107--Request for Motor Carrier Rate Proposal:
106--response for 107
204--load tender
990---ack
214-shipment status message(Road)
210--Freight Details and Invoice
820--Payment Order/Remittance Advice:

211-Bill of landing
212--Delivery trailer manifest

315-Status details (Ocean)

114-Air shipment status message

214 Status Codes:

AA: Appointment set for Pickup Location
AB: Appointment set for Drop Location
X3: Arrived at PickUp Location
CP: Complete Loading
AF: Departed from the Pickup location
X6: Enroute to Drop Location (Sent every one hour )
X1: Arrived at Drop Location
CD: Departed from Drop Location
D1: Complete Unloading

-------------------------
Retail Flow :
------------
https://en.wikipedia.org/wiki/X12_EDIFACT_Mapping

Buyer ----------- Seller
--------------------------
Reqest for quote(840)(REQOTE) -- Response for quote(843) (QUOTES)
PURCHASE Order(850)(ORDERS) --Purchase order ACK(855)(ORDRSP)
------------------------------seller sends Shipment notice(856)(DESADV)
------------------------------seller send an invoice(810)(INVOIC)
820(payment order/Remittance)(REMADV)----------->

840--Request for quote
--------------------------
ST****
BQT**Request for Quote Reference Number*
PO1*
==========================================
EDIFACT(Request for quote(REQOTE) )

BGM*
PAI*

--------------------------------
843--response FOR QUOTE(QUOTES)

BQR**RRF NUMBER***
PO1*
--------------------------------
850(PURCHASE ORDERS)(ORDERS)
BGM*
PO1*0(PURCHASE ORDER NUMBER)*
FOB*01(SHIPMENT METHOD OF PAYMENT)*
--------------------------
855(PURCHASE ORDER ACK)(ORDRSP)

990/999/997 acknowledgment

990--ACKNOWLEDGEMENT is used in logistics response for 204 load tender.
999-Acknowledgment is used in Healthcare response for
997--Acknowledgement for orders like 850 or any EDI

861--RECEIVING ADVICE/ACCEPTANCE CERTIFICATE.

BRA--BEGINNING SEGMENT FOR RECEIVING ADVICE/ACCEPTANCE CERTIFICATE.

====== BRA04--if goods are receiving its contain value of 1-Receiving Dock Advice.

Transportation
-----------------
ANSI -214 --Transportation Carrier Ship. Status Message
ANSI -315--315 Status Details (Ocean)
IFTMIN -EDIFACT
IFCSUM-EDIFACT IFCSUM D 93A---FORWARDING AND CONSOLIDATION SUMMARY MESSAGE
859 Freight Invoice --
110 Air Freight Details and Invoice
210 Motor Carrier Freight Details and Invoice
310--310 Freight Receipt and Invoice (Ocean)
410-410 Rail Carrier Freight Details and Invoice
204 Motor Carrier Load Tender

X12M Supply Chain
---------------------------
856--856 Ship Notice/Manifest--DESADV(Dispatch advice)
861 --861 Receiving Advice/Acceptance Certificate
860--purchase order change request.
832 Price/Sales Catalog
940 Warehouse Shipping Order
944 Warehouse Stock Transfer Receipt Advice
945 Warehouse shipping advice
iftsta--EDIFACT IFTSTA D 93A--INTERNATIONAL MULTIMODAL STATUS REPORT MESSAGE
iftmbf--EDIFACT IFTMBF D 97A---Firm booking message
846--Inventory inquiry --INVRPT

ORDER CHANGE

RosettaNet--
3B2-- Notify of Advance Shipment --
3B12 Request Shipping Order
3B14 Request Shipping Order Cancellation
3B13 --Notify of Shipping Order Confirmation
4B2 -- Notify of Shippment status
4C1 -- Inventory Report Notification

315----Status Details (Ocean)
Manadetory Segments ---B4,Q2
B4--
B403--Shipment status code
Q2---status details ocean
Q201--Vessel code
Q209--flight number

R4--Port of Terminal
R401-Port functional code
R402--Location Qualifier
Q404-Port number

APAC--Asia Pacific and Australasian Continent
EMEA--Europe, the Middle East and Africa
America comprises the totality of North America and South America.

EDI has two process

1. Outbound process
2. Inbound process

outbound process:
-------------------
OP: idoc >>>>>>>>>>>>>EDI

1. Application document is created.
2. IDOC is generated
3. IDoc is transferred from SAP to the Operating system layer
4. Idoc is converted into EDI standards
5. EDI document is transmitted to the business partner
6. The Edi Subsystem report status to SAP

Inbound process:
--------------
IP: EDI >>>>>>>>IDOC

1. EDI transmission received
2. EDI document is converted into an IDOC
3. IDOC is transferred to the SAP layer
4. The application document is created
5. The application document can be viewed.

7) Mention the advantages of the Internet EDI over VAN EDI.

Low cost.
Zero transaction fees.
Easy to use.
Minimal Infrastructure.
Industry Standard.
Real-time.
Entire supply chain.
All data transport.
Interoperability.
Speed and Quality
Web browser.

8) Mention some of the EDI standards.

Accredited Standards Committee X12 (ASC X12).
American National Standards Institute X12 (ANSI X12).
United Nations Center for Trade Facilitation and Electronic Business (UN/CEFACT).
Electronic Data Interchange for Administration, Commerce, And Transport (EDIFACT).
Health Insurance Portability and Accountability Act (HIPPA).

9) What are the different EDI communication protocols.

HyperText Transfer Protocol (HTTP).
Simple Mail Transfer Protocol (SMTP).
File Transfer Protocol (FTP).

10) Which industry is first to use EDI.

The Transportation industry was one of the first to use EDI concepts. The organization also named as Transportation Data Coordinating Committee (TDCC).

11) What is Translation software?

Translation software translates business documents into a common EDI standard for transmission to a trading partner. It also translates EDI standard data into a format suitable for application processing.

12) What does 12 represent in X12?

The number 12 represents a subcommittee of twelve.

13) What are the twelve subcommittees?

X12A - Education Administration
X12C - Communications and Control
X12E - Product Data
X12F - Finance
X12G - Government
X12H - Materials Management
X12I - Transportation
X12J - Technical Assessment
X12K - Purchasing
X12L - Industry Standards Transition
X12M - Distribution and Warehousing
X12N – Insurance

14) What is a standard?

A standard is a usable, well-defined generic language format that enables organizations to communicate documents without human interpretation or intervention.

15) What is a transaction?

A transaction refers to one valid or original document. A transaction is a collection of segments in a standard sequence.

16) What is a segment?

A segment is a record in a standard transaction or message. Each segment is identified with two or three characters identifier at the beginning of the segment.

17) What is an element and what is the maximum no of elements a segment

can contain.

An element is an individual data field within each segment. The element represents one piece of information in a document. An element may be also thought of as a field.

An segment can contain a maximum no of 24 elements.

18) What is a composite element.

If an element consists of component elements or sub-elements then it is a composite element.

19) What does an element contains.

An element contains a numeric ID, a data type, and minimum and maximum length.

20) Mention the data types of EDI.

A-Alphabetic.
AN-Alphanumeric.
B-Binary.
CD-Composite Data element.
CH-Character.
DT-Date.
FS-Fixed-length String.
ID-Identifier.
IV-Incrementing Value.
Nn-Numeric.
PW-password.
R-Decimal Number.
TM-Time.

21) What is a delimiter.

A delimiter is an element separator character. The separate can be any character that is not used in the data or control character.

22) What is a terminator.

A terminator is the last character in the segment that indicates the end of the segment.

23) What are the most commonly separators used in the ANSI X12.

Simple data element – asterisk(*)
Composite data element – backslash(\)
Repeating data elements – caret(^)
Segment terminator – tilde(~)

24) What is the standard separator characters used in the UN/EDIFACT.

Data element separator – plus(+)
Component element separator – colon(:)
Segment terminator – Apostrophe(‘)

25) What is the element requirement designators in EDI.

M – Mandatory - If the segment is present, this element must be present.
O - Optional (C – Conditional in EDIFACT) – The use of this element is at the discretion of the trading partners.
X – Relational (Not used in EDIFACT) – The requirement for this element is dependent upon the absence or presence of another element.

26) What are the parts of the transaction.

The transaction can be divided into three parts

Header (Table 1).
Detail (Table 2).
Summary (Table 3).

27) What does Header level contains.

The Header generally includes all segments that provide information about the entire transaction or message.

For e.g., for a Purchase Order, the header will contain the purchase order number, date, names, addresses, and reference information.

28) What does Table 2 contains.

Table 2 normally provides detailed information for the transaction.

For PO e.g., this would be the repeating line item information and would be defined as a loop.

29) What does Table 3 contains.

Table 3 contains the summary information about the transaction.

30) What is an envelope.

An envelope contains control or service segments.

31) What is a Transaction Envelope.

A Transaction envelope contains transactions that are enclosed in segment pairs.

32) What is a Group Envelope.

A Group Envelope contains the same set of transactions grouped in a pair of segments that are sent to a trading partner.

33) What is an Interchange Envelope.

An Interchange Envelope is a collection of Groups and/or Transactions destined for one trading partner.

34) What is an Interchange Acknowledgment (TA1).

TA1 reports receipt by the recipient of an interchange and syntactical analysis of the interchange control header and trailer only.

35) What is Grade of Service Request (ISB).

ISB requests a priority higher or lower than normally provided.

36) What is Deferred Delivery Request (ISE).

ISE specifies the earliest time the interchange can be delivered.

37) What is Interchange Delivery Notice (TA3).

TA3 reports the successful or unsuccessful delivery and retrieval of Interchanges between Service Request Handlers.

38) What is Functional Acknowledgment and what does it contains.

A Functional Acknowledgment is an acknowledgment generated by the receiver’s translator. It provides end-to-end acknowledgment of receipt of functional groups. It must be coordinated with Trading Partner.

It contains

Functional Group.
Transaction Set.
Segment Errors.
Element Errors.
Transaction Set Errors.
Functional Group Errors.

39) What does “004030” indicates in EDI.

It indicates Version, Release, Sub release and Industry Association

Version - 004

Release – 03

Sub release – 1

Industry – VICS

It is commonly referred as “ 4031 VICS “

40) Difference between X12 and EDIFACT.

ANSI X12 is used in the US and EDIFACT are used in the outside of United States.
In ANSI X12 a group of segments is said to be Transaction and in EDIFACT it is Message.
ANSI X12 is developed by Accredited Standards Committee (ASC X12 Committee) and EDIFACT is internationally agreed-upon standards.

EDIFACT(Electronic Data Interchange For Administration, Commerce, and Transport).
UNA----> Service string Adviser (It contain variable delimiters) optional segment
UNB----> Interchange Header
UNG---->Functional Group
UNH---->Message Header
UNT---->Message Trailer
UNE---> Functional Group Trailer
UNZ---->Interchange Trailer

1. Explain EDI flow?
Answer:
There are two types of flows are there in EDI.
1. INBOUND flow
2. Outbound FLOW.
EXAMPLE: let's take EDI FILE to APPLICATION FILE mapping.

Coming to Inbound flow:
--------------------------

1) The inbound, EDI data needs to be collected from a directory
2) The collected data should be De-enveloped (removing the headers) to get the message part also.
3) Using the header information (Interchange, Group, Message, and version) the Envelope setup (Trading Partner setup) will be identified.
4) The Envelope setup contains (points) the Map which can be used to translate the data.
5) The translated data can be extracted to the specified directory.
Let's take APPLICATION FILE to EDI FILE mapping.

Coming to Outbound flow:
--------------------------
1. Collect the APPLICATION files from the Collection folder.
2.Translate the file using Map to EDI.
3. After Translation, we can add envelopes to the Extracted EDI data using EDI Envelop Service.
4. Extract the data to the specified directory.
EDI standard:
We can create
INBOUND ISA,GS,ST,SE,GE,IEA.
OUTBOUND ISA, GS, ST, SE, GE, IEA In INBOUND/OUTBOUND We can give map names in ST Envelops.
****In the outbound process we give post-process BP in ISA.
****In outbound flow we can create envelops ISA, GS, ST but it calls ST, GS, IEA because we give the next envelop option in st, gs envelopes.
***iN WHICH SEGMENT we can use accumulator function --CTT segment
--------------------

EDI_EXAMPLES

Search This Blog

EDI_BASICS

EDI Definition: EDI(Electronic Data Interchange) is a standard format for exchanging of BUSINESS DOCUMENTS between computer to computer(Bussiness to Bussiness)

Comments

Post a Comment