T
e
lema EDI Module.
IT perspective of
Telema EDI integration, terms
An integrated Telema customer is a customer using EDI channel for connecting to the Telema EDI
System.
Telema integrated customers use their ERP to handle and exchange
EDI Messages with trade partners via Telema EDI System.
2
Customer
ERP system
Telema
EDI system
Channel
EDI message
Telema EDI Module
3
Telema EDI Module is a functionality in an ERP system that enables exchange of EDI documents between Partner ERP software and Telema EDI System. Also it provides preliminary data validation.
ERP systems with Telema EDI Module comply with specific requirements for EDI documents exchange with Telema EDI System.
T
elema EDI Module implementation
ERP Process flow Document creation Document handling Validation of document content (codes, prices etc)Telema EDI Module
Doc conversion to/from eDoc
Communication session initiation Error handling Schema validation (.xsd) Telema API Communication Authentication Transport Documents in Telema eDoc format Documents in ERP internal format Telema EDI System Documents in Telema eDoc format
T
elema EDI Module
• Document exchange between Telema EDI System and customer ERP system.
• Error handling
• Document exchange scheduling
• Document conversion to/from Telema eDoc format
• Has user interface
Telema API
•
Helps to build Telema EDI Module
•
Supports functionality to connect ERP with Telema EDI
System
– Document exchange
– Communication error handling
– Ensures document exchange reliability
•
Ensures high level of reliability
What is not Telema EDI Module
•
Document handling process in ERP
•
Business information validation (product codes,
prices, etc)
Why Telema EDI Module?
• Fast and easy integration with Telema EDI Module
– Less stress for ERP support
– Better user experience – clear process, clear message
• Customer feels, that EDI functionality offered by ERP support is on a higher level.
– Electronic document exchange is standard functionality in modern business.
– Customers expect, that EDI functionality is available in standard configuration.
Telema EDI Module functional requirements
• Standard functionality for all Telema EDI Modules
• Requirements are applied for all new Telema EDI Module implementations
• Ensure similar user experiences in different ERP-s.
• Describe:
– Doc exchange principles
– Error processing rules
– Standard reports
• Standard functionality ensures that all
electronic data exchange requirements are met
Customers can work with no or less problems. • Standard functionality
– Enables standard process for document processing
– Ensures, that EDI process requirements are followed
Why standard Telema EDI Module?
Customer view
• Standard functionality ensures, that EDI process requirements are followed
Telema is EDI expert and offers support during implementation! • Well-monitorable document exchange process
– Less work-load for customer support – customers can understand and solve most of error situations.
•
Future-proof
– Telema informs IT partners about new EDI requirements
– ERP support companies can be sure that market requirements are sattisfied.
ERP support view
How?
• Documentation: Telema EDI Module Functional Requirements
– Functions described
– User-interface described
• Telema eDoc Implementation guidelines
– General principles of Telema eDoc handling
• XML document examples
– Examples from buyer and supplier side
• Telema eDoc specification
– Detailed description of all document types and their possible content.
Why?
• Sometimes more is less...
– More standardized functionality -> less customer inquiries
• ...and less is more
4DOC supply process is more transparent,
reliable and faster compared to 2DOC model.
-
Less mistakes
-
More security
-
+ many other business benefits
Retailers’ requirements:
similar or different?
Common:
- EDI channel
- document format
- identification of parties
- document date info
- item rows (item ID, quantities, units etc)
97% of requirements are similar
4DOC – how things really are?
Differences: delivery place, supply time,
GLN, references to rows, package units,
consolidation, batch number, best
before, etc.
Have to be considered!
ORDER
Rimi Prisma Maxima
GLN
YES
YES
NO
Delivery time requested
YES
NO
YES
Created by contact
YES
NO
NO
Packaging
YES
NO
NO
DESADV
(DESPATCH ADVICE)
Rimi Prisma Maxima
GLN YES YES NO
Consolidation** YES NO YES
LotNum, BestBefore YES YES NO
Customs Declaration Num YES NO NO
Certificate Number YES NO NO
Certificate start date YES NO NO
Created by contact NO NO YES
Item price NO NO NO
**Several orders on one despatch advice References are on desadv rows
RECADV
(RECEIVE ADVICE)
Rimi Prisma Maxima
GLN YES YES NO
Created by contact NO NO YES
Amount actual YES YES YES
Amount accepted YES YES YES
LotNum, BestBefore NO NO NO
Item price YES NO NO
VATRate NO NO NO
INVOICE
Rimi* Prisma Maxima
Currency Code NO YES YES
GLN YES NO NO
Bank account number YES NO NO
Lot Number NO NO NO
Best Before NO NO NO
Reference to RECADV NO NO YES
How to solve the 4DOC process in
ERP-s, and in implementation for
Implementation of DESADV and RECADV
• Separating the creation of DESADV and INVOICE: - business process
- ERP functionality
• Handling the RECADV and issuing the INVOICE: - separate documents and templates in ERP
- additional column on the purchase order template
• Identifying features/statuses (ordered, despatched, received)
• Issuing invoice automatically
