EDI Integration in SAP

1. 1
1
WHITE PAPER
EDI INTEGRATION IN SAP
A DEFINITIVE GUIDE

2. 2
2
2
INTRODUCTION
By helping to streamline supply chains through auto-
mation, Electronic Data Interchange (EDI) offers com-
panies many advantages. However, the work required
to implement effective EDI, from setup to go-live and
operation, should not be underestimated. One partic-
ularly important aspect here is the extent to which EDI
functionality is integrated into the existing ERP sys-
tem. The deeper the integration and the higher the ca-
pacity for self service across the business, the better.
As the market leader among ERP systems, SAP has a
special status. Many different EDI solutions have been
developed in and around SAP, with different func-
tionalities and integration options. From completely
self-managed EDI converters as software packages,
to EDI solutions managed entirely by experts, many
things are possible.
This white paper is intended to help decision-makers
in the SAP area of your company to select the right EDI
solution. Once you have finished you should hopefully
understand what is required for your company to ben-
efit from the best possible system.
If any questions remain unanswered, we
are happy to answer your questions at
edi@ecosio.com
Please note: The possibilities and functionalities
available up to January 2021 are presented, without
claiming completeness.
© 2021. SAP ERP and SAP S/4HANA are the trade-
marks or registered trademarks of SAP SE or its affili-
ates in Germany and in several other countries.
Version 1.2

3. 3
3
3
EDI AS A CENTRAL COMPONENT OF THE ERP P4
Why EDI? P4
EDI in practice - an example P6
The potential of seamless EDI integration P7
EDI integration in SAP is key if... P7
EDI-SAP INTEGRATION AT A GLANCE P7
All SAP EDI solutions compared P8
Our comparison criteria P9
THE TECHNICAL POSSIBILITIES OF EDI-SAP INTEGRATION P10
The evolution towards the ERP “Digital Core” and the third wave approach P10
Questions a decision maker should ask P11
SAP Business Connector P12
SAP PI and PO P13
SAP Cloud Platform Integration P14
e-Document Solution and Application Interface framework P14
Local EDI converter solutions P15
Local third party add-on solutions P15
Fully managed EDI P16
FULLY MANAGED EDI VIA API P17
The benefits of API integration in practice P17
What does day-to-day operation look like? P18
All advantages at a glance P19
ABOUT ECOSIO P20
TABLE OF CONTENTS

4. 4
4
4
EDI AS A CENTRAL COMPONENT OF THE ERP
Electronic Data Interchange represents a critical part
of the ERP processes in many companies today. This
chapter explains why seamless integration into SAP
systems is important and what the benefits are.
Over the last 40 years, ERP systems have developed
from pure data management to comprehensive plan-
ning, management and control instruments with which
business processes can be handled in an IT-support-
ed and digitised form. Today, companies have a kind of
digital control centre at their disposal to manage and
optimise enterprise resource planning tasks.
Internal ERP processes themselves have also changed.
Analogue and paper-based processes are being re-
placed by digital, IT-supported possibilities. This
means an immense potential for process automation,
especially concerning message exchange across sup-
ply chains. It is not without reason that more and more
companies on the procurement and sales side are fo-
cusing on automation of their purchase-to-pay or or-
der-to-cash processes. The electronic data exchange
required for this is called EDI (Electronic Data Inter-
change).
WHY EDI?
As an ERP component, EDI optimises procurement
and sales by means of automated message exchange
between all suppliers and customers in the supply
chain. With EDI, all B2B partners can be connected
to your company or SAP system and the entire B2B
message exchange of all business documents can be
automated. The image below shows an example in the
retail sphere, though this is possible for all industries.
High message volume = high automation potential!
1. Price list / catalogue (PRICAT)
2. Order (ORDERS)
4. Despatch advice (DESADV)
7. Goods receipt (RECADV)
8. Invoice (INVOIC)
DELIVERY
CUSTOMER
SUPPLIER
BANK
5. Delivery status
(IFTSTA)
3. Transport order (IFTMIN)
6. Arrival notification (IFTMAN)
10. Credit (CREMUL) 9. Payment order (PAYMUL)

5. 5
5
5
This eliminates the need to send PDFs manually by
e-mail or invoices by post. Instead, the documents are
generated in a machine-readable format and auto-
matically sent/received by the SAP system. Depending
on the EDI solution, the degree of automation can be
such that no human intervention within the company
is required. This can be particularly advantageous for
extensive or international B2B networks.
However, EDI implementation and operation requires
a lot of effort and expertise. The connection of B2B
partners is complicated by industry and country-spe-
cific formats, sub-formats and protocols. Documents
must first be converted into the correct format (“map-
ping”) and then sent or received via the correct proto-
col (“routing”). In addition, there are international, le-
gal requirements, such as those concerning electronic
invoicing (e-invoicing) and the use of the Peppol net-
work, which may have to be met.
As EDI is an ongoing process and not simply a one-
time solution, it is important to consider ongoing oper-
ation and maintenance costs in addition to any setup
costs. If, for example, EDI operation is carried out and
maintained in-house, acquisition costs may be low, but
the running costs for personnel and training etc. will
quickly add up. If the EDI operation is handed over to
service providers, on the other hand, the setup costs
can be reduced and the ongoing operation becomes
more cost-efficient.

6. 6
6
6
MESSAGE MONITORING
ETC.
ELECTRONIC
INVOICING
ETC.
VAN
CONNECTIONS
X.400
This example is, of course, a fairly comprehensive one.
Companies may not have to implement all the scenari-
os depicted, or may have to do so only over time. How-
ever, as EDI integration is a long term project it is only
right that the scalability and flexibility of the solution
should play a role in the decision.
PARTNERS
WITH ERP
SYSTEM
PARTNERS
WITHOUT ERP
SYSTEM
SUPPLIERS
WITH
SCHEDULING
AGREEMENTS
REGULAR
SUPPLIERS
GXS
CLASSIC EDI
WEB
EDI
MULTIPLE
MAILBOXES
LEGAL
COMPLIANCE
EDI IN PRACTICE: AN EXAMPLE
PLUS CAPACITY
FOR EXPANSION
VENDOR
MANAGED
INVENTORY
SUPPLIERS

7. 7
7
7
THE POTENTIAL OF SEAMLESS EDI IN-
TEGRATION
For many supply chain businesses today, EDI is a cen-
tral component of their SAP systems. If the EDI solu-
tion offers seamless and deep integration into the
SAP system, the system also becomes the EDI con-
trol centre. This means that all EDI processes can be
controlled via the familiar SAP interface and message
monitoring is directly visible in the user interface.
From an order to the receipt of a payment advice note,
documents are automatically generated in the back-
ground of the SAP system, converted into the correct
format, sent via the corresponding protocol and vice
versa. Each message status can be retrieved and dis-
played within SAP, and a full text search in all SAP doc-
uments simplifies the search in the event of errors.
In conjunction with the right EDI solution, seamless
integration into the SAP system thus enables the con-
nection of new B2B partners and the operation and
monitoring of all EDI processes - all without the need
for internal EDI knowledge. How deeply the required
EDI functionalities can be integrated into the SAP sys-
tem and how seamless the experience in the user in-
terface differs according to the different possibilities.
EDI INTEGRATION IN SAP IS KEY IF...
✓ ...a company wants to automate and optimise B2B
message exchange.
✓ ...a company must comply with national or interna-
tional B2B/B2G e-invoicing regulations.
✓ ...a company wants to control or monitor EDI func-
tionalities directly in SAP and reduce pressure on
in-house teams.
EDI-SAP INTEGRATION AT A GLANCE
There is a wide range of solutions for the integration of
EDI functionalities in SAP. Some are provided by SAP
itself, others by third parties. This chapter provides an
overview of the different solutions.
The options for EDI/SAP integration differ principal-
ly in the technical functionalities and how much EDI
know-how is required internally for successful imple-
mentation/operation of the solution. The following
table displays the most important EDI functions and
which EDI solution offers what.

8. 8
8
8
SAP EDI SOLUTIONS COMPARED
EDI status visible on the
SAP IDoc/SAP document
Full text search across all
documents
Support of all standard
EDI protocols
Out-of-the-box routing to
third-party networks
Out-of-the-box routing to
Peppol
Support of conversion for
messages in any format
Support for message split
and merge
Support for international
e-invoicing requirements
Automatic alerts when
message failure occurs
Revision-proof IDoc
processing for all teams
IDoc field conversions of
ext./int. IDs in SAP
EDI project coordination
handled externally
Ongoing support/moni-
toring handled externally
S
A
P
B
u
s
i
n
e
s
s
C
o
n
n
e
c
t
o
r
S
A
P
P
I
/
P
O
e
-
D
o
c
u
m
e
n
t
S
o
l
u
t
i
o
n
a
n
d
A
I
F
S
A
P
C
l
o
u
d
P
l
a
t
f
o
r
m
I
n
t
e
g
r
a
t
i
o
n
L
o
c
a
l
E
D
I
C
o
n
v
e
r
t
e
r
L
o
c
a
l
W
o
r
k
f
l
o
w
S
o
l
u
t
i
o
n
s
F
u
l
l
y
M
a
n
a
g
e
d
E
D
I

9. 9
9
9
OUR COMPARISON CRITERIA
The selected criteria and functions are based
on... a) the functions that are generally im-
portant for EDI in terms of implementation
and operation, and b) the degree of integra-
tion in SAP itself.
EDI status visible on the SAP IDoc/SAP document:
The current status of a sent message can be seen di-
rectly in the SAP system, either on the IDoc or on the
SAP document (e.g. invoice or purchase order). This
can be called up at any time in a traceable way.
Full text search across all documents: Message traf-
fic can be searched and filtered at any time via a full
text search. Users can search content and message
metadata such as AS2 IDs, OFTP2 transmission IDs,
etc.
Support of all standard EDI protocols: All common
EDI protocols are supported (e.g. AS2, OFTP2, SFTP,
X.400 etc.).
Out-of-the-box routing to third-party networks:
Value-added networks (VANs) can be used without
additional effort.
Out-of-the-box routing to Peppol: The Peppol net-
work, which is particularly important in the area of
legal e-billing and is becoming increasingly popular
worldwide, can be used without additional effort (as-
suming that you are either a certified Peppol access
point yourself or can obtain this as a service from a
certified partner).
Support of message conversion: The SAP standard
format IDoc can be converted into all necessary in-
bound and outbound formats for B2B/B2G partners.
Support for message split and merge: Incoming
message packages can be split into individual IDocs
and outgoing IDocs can be grouped into message
packages and provided with meta information (in-
voice list numbers for example).
Support for international e-invoicing requirements:
Country-specific legal requirements (e.g. signature,
archiving, etc.) are met without additional effort.
Automatic alerts when message failure occurs:
When message failure occurs automated alerts / noti-
fications enable the issue to be spotted and resolved
quickly.
Revision-proof IDoc processing for all teams: Every
change to the original IDoc is logged in a revision-proof
manner and can be traced at any time.
IDoc field conversion of external/internal IDs in
SAP: Associate external IDs (e.g. UNB sender ID) to
correct SAP internal IDs (e.g., debtor number) and vice
versa.
EDI project coordination handled externally: Proj-
ect coordination and B2B/B2G partner communica-
tion is handled by an external EDI service provider.
This mainly involves partner onboarding and mainte-
nance of existing partner connections.
Ongoing support/monitoring handled externally:
The ongoing support of EDI operations and monitor-
ing as well as troubleshooting is handled by an EDI
service provider. Issues are resolved proactively, with-
out the need for intervention by in-house teams and
before disruption to business.

10. 10
10
10
SAP is the market leader among ERP systems
and has developed into a comprehensive
and highly specialised “Digital Core”. So what
options do companies now have in detail to
extend this core system with EDI functional-
ities?
THE DEVELOPMENT OF THE ERP
“DIGITAL CORE” AND THE THIRD WAVE
APPROACH
Early ERP systems were individual monolithic pieces of
software containing all relevant modules (from account-
ing and human resources tosales and distribution). How-
ever, these were anything but flexible in use - so further
developments and the so-called “Second Wave” quickly
followed. ERPs were given a core system (containing, for
THE TECHNICAL POSSIBILITIES OF EDI-SAP
INTEGRATION
example, elements for human resources, procurement
and sales and development) as well as separate mod-
ules (which can also come from third-party providers)
for other common areas such as customer relationship
management (CRM) and production planning and con-
trol.
First wave ERP systems Second wave ERP systems
These independent modules are then integrated into the
core system via Enterprise Application Integration (EAI).
Companies thus first select the appropriate system for
certain additional ERP functions and only integrate it
afterwards. The problem with this approach, however,
is that subsequent integrations can prove difficult. De-
pending on resources and internal expertise, such sec-
ond-generation ERP systems may require considerable
effort to set-up and maintain.
For this reason, ERP systems were further modernised
- and “third wave” systems were born. In these envi-
ronments too, a core system is being expanded with
additional elements. However, instead of managing the
systems on-premise (i.e. within the company itself),
the modules are operated in the cloud by specialised
third-party providers.
Access to modules is achieved via an API (one of several
EAI methods). This approach makes it easier to set up
and maintain the ERP systems and their elements and
is ultimately the prerequisite for seamless EDI/ERP inte-
gration. Unlike in-house solutions, no internal expertise is
required. Updates and integration processes for ongoing
operations can be outsourced to the third-party provider.

11. 11
11
11
Which external modules or services (i.e. EDI
functionalities) do I need now and in the future (see
overview table on page 8)?
How deeply do I want to integrate EDI into the
existing Digital Core of SAP?
How flexible, scalable and user-friendly do I want the
EDI system to be?
Do I have sufficient internal resources (personnel,
know-how, budget and time) to ensure EDI setup
and ongoing operation is successful?
Do I want to use the advantages of the "Third Wave"
and transfer EDI operation to my own cloud service
provider, or do I trust in the EAI approach of the
"Second Wave" and handle everything on-premise?
Third wave ERP systems
Questions a decision maker should ask:
11

12. 12
12
12
Companies can exchange IDocs and XML files with
business partners using the communication protocols
HTTP(S), FTP or e-mail (SMTP/POP3/IMAP). However,
modern protocols that are increasingly used in electron-
ic data interchange (EDI), such as AS2, OFTP2, or Pep-
pol, are not supported.
Any company with a valid SAP license can operate the
Business Connector free of charge, which contributes
to the wide distribution of the software. However, since
SAP Business Connector 4.8 is due to come to an end of
maintenance at the end of 2025, companies must find a
successor. Otherwise, smooth data exchange with cus-
tomers and suppliers cannot be guaranteed.
SAP Business Connector Message Exchange
SAP Business Connector
RFC Connection
Process logic
Mapping
Validation
SAP System
IDoc, BAPI Web
RFC
HTTP(S)
FTP
E-mail
SAP BUSINESS CONNECTOR
The SAP Business Connector is a standalone software
component based on the webMethods B2B Integration
Server that is installed and managed independently of
the SAP system. This enables third-party software and
other B2B partners to be connected to the SAP system,
whereby different connection variants are possible.
For example, the Business Connector can provide an
XML interface for existing SAP BAPIs (Business Applica-
tion Programming Interface). This enables external part-
ners and third-party applications to address BAPIs using
XML messages. Another option is to call SAP Remote
Function Calls (RFCs) from the Business Connector.
Using the Business Connector, external applications can
communicate with the SAP system without supporting
the RFC protocol or having knowledge of the ABAP rou-
tines or ABAP structures mapped in SAP. Communica-
tion is possible in both directions - that is, the SAP sys-
tem can also use the Business Connector to control an
external application. The SAP Business Connector also
offers a range of options for mapping and routing IDoc
messages.
For example, the SAP-internal IDoc format can be con-
verted into an external format of the customer or vendor
(for example, XML or EDIFACT) and delivered using var-
ious protocols.
12
Many different technological solutions and approaches have now developed around
SAP to make EDI functions usable - some from SAP itself, others from specialised
third-party providers. We will explore these in the following sections...

13. 13
13
13
SAP PI AND PO
SAP Process Integration (PI) is another software
component created by SAP itself that enables data
exchange between the SAP system and internal / ex-
ternal systems. To do this, SAP PI uses the SAP inter-
nal programming language ABAP and a Java stack, as
well as various adapters that can be used to convert
transport protocols and format conversions.
SAP Process Orchestration (PO) is a combination of
various SAP solutions, including SAP PI. It allows for
simpler and more comprehensive representation of
business processes (SAP Business Process Manage-
ment and SAP Business Rules Management are also
part of PO).
Since SAP PI or PO is installed and operated by the
customer himself, an appropriately trained team must
be available. If EDI operations are to be monitored
24/7, these employees must be available around the
clock. In addition, the EDI connections require regu-
lar maintenance. For example, digital certificates (e.g.
for AS2 and OFTP2) must be renewed or connection
parameters adjusted. This requires independent coor-
dination with all relevant B2B partners.
New connections can also present challenges with
different protocols and settings. In order to implement
the mapping and routing processes, the company
needs trained employees. Monitoring, troubleshooting
and error correction (with the respective B2B partner)
must be handled internally, while SAP PI or PO must
also be licensed accordingly.
Incidentally, those who only want to work with SAP PI
have to accept a major restriction - namely that only
flat file formats via SFTP/SOAP/REST/HTTP protocols
are allowed. To use flat file formats and XML via “clas-
sic” EDI formats (e.g. EDIFACT or ANSI ASC X12) and
protocols (e.g. AS2 or X.400), you must have either a
special package from a third-party manufacturer or
the “B2B Add-on” from SAP - but this is only avail-
able with the SAP PO license (even if no other SAP PO
functions are required).

14. 14
14
14
E-DOCUMENT SOLUTION AND
APPLICATION INTERFACE
FRAMEWORK
To enable SAP to better support its customers - es-
pecially in the area of e-invoicing - the e-Document
Solution (also known as SAP Document Compliance)
was developed for SAP ECC and SAP S/4HANA. This
solution helps companies to meet the requirements of
electronic invoicing in different countries.
Documents from logistics, sales and distribution and
accounting can be converted into common e-invoice
formats (e.g. XML files) using the e-Document Solution.
In order to meet the special requirements of individual
countries, the SAP Application Interface Framework
(SAP AIF) can be used, which converts generated
e-documents into the required target format, such as
XRechnung for Germany or FatturaPA for Italy. To be
able to map country-specific requirements in the AIF,
individual “Packaged Solutions” can be imported.
After conversion, however, the e-invoices must still be
sent via a corresponding protocol or network (such
as Peppol). In the case of government-mandated e-in-
voicing procedures such as FatturaPA in Italy, the ex-
change must also be carried out via a central service.
This is not possible with the e-Document Solution
alone. Here, companies can either take out an addi-
tional subscription to the SAP Cloud Platform men-
tioned above, or enlist the help of a specialised EDI
provider.
14
SAP CLOUD PLATFORM INTEGRATION
The SAP Cloud Platform, a Platform-as-a-Service solu-
tion developed by SAP, enables in-house developers to
program their own applications or extend existing ap-
plications within a cloud-supported software frame-
work. This includes in particular SAP Cloud Platform
Integration, which offers users various connectivity
options for integrating cloud and on-premise solu-
tions.
This also makes it possible to map EDI functionalities
forbuilding a B2Bnetwork. However,this again requires
internal EDI knowledge. The entire setup, ongoing op-
eration and monitoring must either be implemented by
an internal team or supported by an SAP consultant. In
the initial phase, this means corresponding resource
and cost expenditure, which will continue to add up
during ongoing operation when maintaining or setting
up new EDI connections. The SAP Cloud Platform is
therefore an extremely comprehensive toolset for SAP
developers, for which a corresponding license agree-
ment must be concluded with SAP.
Again, however, use of certain EDI protocols and EDI
formats requires a special license, meaning additional
costs.

15. 15
15
15
Converter solutions are individually adaptable, but po-
tentially cost-intensive due to individual license costs
for various functionalities, formats and upgrades in
combination with long-term binding maintenance
contracts. For example, support for protocols such as
X.400 or services such as VAN connectivity must be
purchased separately.
Local converter solutions, like the solutions mentioned
above, must also be operated entirely by internal
teams. This includes particularly time-consuming pro-
cesses such as mapping, testing and 24/7 monitoring.
This requires appropriately trained employees.
It should also be borne in mind that both the soft-
ware itself and the individual mappings age. In oth-
er words, over time new versions of the converter will
be released, which do not necessarily allow existing
versions and accompanying mappings to be updated.
This results in corresponding migration projects that
have to be realised internally or with the help of an
external consulting company.
LOCAL THIRD PARTY ADD-ON
SOLUTIONS
Modular extensions are not only offered by SAP itself,
but also by various third-party providers. These can be
integrated into the existing SAP system to enable or
optimise individual steps in the EDI workflow, e.g. in
the area of e-invoicing or electronic ordering.
The advantage is the high degree of specialisation of
the individual modules and the existing know-how of
the providers. Companies can thus precisely extend
their SAP (for example, processes for approval, dual
control, release, etc.). Also, such modules can usually
be used out-of-the-box. This means that no dedicated
trained personnel is required.
Some special requirements, such as e-invoice proto-
cols and signatures at Peppol or FatturaPA, must in
turn be obtained separately (e.g. from another service
provider). In most cases, workflow solutions are also
strictly tailored to one type of document (e.g. invoice
only) - the desired modules must therefore be precise-
ly selected when purchasing.
15
LOCAL EDI CONVERTER SOLUTIONS
Another possibility is to use an EDI converter. This software needs to be installed locally
and converts documents from SAP internal IDoc format to and from partner formats.
Local EDI Converter
ERP System
Routing
Conversion
Signature
Monitoring
On-premise EDI
Solution
Company EDI Architecture
Clients
with EDI capability
Suppliers
with EDI capability
Suppliers
without EDI capability
Other platforms
and networks
Defined Protocols
and Formats
EDI Partners

16. 16
16
16
FULLY MANAGED EDI
Fully Managed EDI involves a cloud-based approach
in which a company is connected to a specialised EDI
service provider (e.g. ecosio) via a single connection.
This service provider can take over all EDI functions
and processes as required.
In such a solution, the provider is essentially a B2B
network, creating and ensuring the success of all
technical elements, such as routing via various proto-
cols, VANs and Peppol, and conversion into all com-
mon and necessary formats, including e-invoicing
requirements. Crucially, however, a fully managed EDI
solution provider also oversees EDI operation. For ex-
ample, ecosio provides 24/7 monitoring and provides
each client with a dedicated project manager to han-
dle partner onboarding.
New updates, protocol certifications and SAP versions
(such as SAP S/4HANA) are easily taken over and im-
plemented/supported. Fully managed EDI offers com-
panies the possibility to use all EDI functions in their
company without an expiration date - all while reliev-
ing internal teams.
The most efficient way to use fully managed EDI seam-
lessly in the familiar user interface of SAP systems is
through integration via API (Application Programming
Interface). This allows you to display the status of a
sent message directly on the SAP IDoc or SAP docu-
ment, for example, or to perform a full text search in all
documents - for more information on what this means,
see the following section.
ecosio’s Integration Hub
ecosio’s Integration Hub
YOUR BUSINESS YOUR PARTNERS

17. 17
17
17
Fully managed EDI is the easiest way to ex-
perience all the benefits of automated B2B
messaging. Integration via API takes EDI
operation in SAP systems to a new level.
In cooperation with the SAP partner EPO
Consulting, ecosio has created a unique
technology to seamlessly integrate fully
managed EDI into SAPsystems. Ratherthan
offering an array of advantages and disad-
vantages, ecosio’s solution provides the full
spectrum of electronic data exchange (in-
cluding compliance with international e-in-
voice specifications) in a future-proof and
flexible way.
THE BENEFITS OF API INTEGRATION IN
PRACTICE
✓ Self-service is possible for different teams - no
longer a need to rely on IT to answer questions etc.
✓ End-to-end data transparency in existing SAP
interface
✓ IDoc can be worked on directly by the business
department (independent of IT teams)
✓ Full text search in all messages and documents
✓ Automatic alerts/notifications if messages are
incorrect or cannot be delivered
✓ Revision-proof processing of IDocs, including the
ability to change the status of, and reprocess, IDocs
✓ IDoc field conversions
✓ Future-proof EDI integration without an expiration
date (independent of updates or new SAP releases)
✓ Full EDI functionality via a single connection to
ecosio’s Integration Hub
Based on the EPO Connector developed by EPO Con-
sulting for easy data exchange and certified by SAP for
SAP ECC and SAP S/4HANA, ecosio has created a mod-
ern SAP/EDI solution that integrates all EDI functional-
ities directly into SAP via a REST-API. This allows users to
send and receive messages automatically directly in SAP.
FULLY MANAGED EDI VIA API
Incoming messages can either be retrieved regularly or
forwarded proactively from the ecosio Integration Hub.
In addition, the EPO Connector enables message moni-
toring that is fully integrated into SAP ERP or S/4HANA.
Additional login via a web platform is no longer neces-
sary.
A comprehensive full text search makes finding individ-
ual messages or IDocs easy. Tasks that previously could
only be carried out with the help of the IT team can now
be carried out independently by the respective business
department. For example, these tasks might include...
✓ Working on and monitoring IDocs. IDocs with
errors can be edited and the status changed as
required. In particular error logs are visible in an easy
to read and clearly structued manner. This makes it
easy for the business to inform itself without a need
to get in touch with IT. The IDoc can be displayed as
a PDF and finalised in the workflow. This processing
can be performed in a revision-proof manner.
✓ Make extensive changes to the IDoc view. Display
all IDocs on the overview page in as much or as little
detail as you wish. Configure the ALV-based IDoc
overview page as required.

18. 18
18
18
SO WHAT DOES EVERYDAY OPERATION LOOK LIKE?
End-to-end monitoring of all messages directly in your
ERP system
The EPO IDoc Monitor shows all sent and received messages. The
monitor can be accessed with a single click from the ALV overview.
Login is done automatically in the background - no additional login
credentials must be memorized by the user.
As part of the EPO Connector solution, the IDoc Monitor allows easy
tracking of sent and received IDocs directly in the SAP GUI. The sta-
tus of an EDI message and the status of the IDoc are automatically
synced in the background - e.g. a failed outbound EDI message will
put the IDoc to status 40 (Application document not generated in
the target system). The status of a failed IDoc can also easily be
changed and the IDoc reprocessed.
Where needed, IDocs can be easily edited using the IDoc
editor (example pictured below).
Clicking on a message
here brings up the
following screen

19. 19
19
19
ALL ADVANTAGES AT A GLANCE
SEAMLESS AND FUTURE-PROOF EDI
INTEGRATION IN SAP
Use the full spectrum of automated message
exchange seamlessly in your own SAP system
using the SAP-certified EPO Connector.
END-TO-END DATA VISIBILITY
Display the status of all EDI messages directly
in the SAP interface and configure your ALV
overview page as required.
19
NO MORE BOTTLENECKS
Create, modify or finalise IDocs independently
of IT teams. Revision-proof processing and
simple field conversion of IDocs directly in SAP.
FULL TEXT SEARCH
Find messages by entering any search terms
(for example, IDoc number, reference number,
factory name, and so on).
EDI VIA A SINGLE CONNECTION
The ecosio Integration Hub allows you to use all
EDI formats and protocols and to create legally
compliant e-invoices.
DEDICATED EDI PROJECT MANAGER
Each client is assigned a dedicated ecosio
project manager to oversee the entire integration
process, from onboardings and EDI operation.
AUTOMATED ALERTS IN SAP
Receive automated alerts and notifications
when errors occur. Never miss a faulty
message again!

20. 20
20
20
At ecosio our aim is to make EDI as efficient and pain-free
for our customers as possible.
Through our comprehensive service, which includes building
and testing all required mapping and routing, providing a ded-
icated project manager to streamline partner onboardings, and
round the clock monitoring, we ensure that minimal internal effort
is required to achieve successful EDI integration in your SAP system.
In short, our EDI experts take care of everything so you can focus on
what you do best! This way, we not only save you time and money, but
also stress.
At ecosio we are EDI integration experts and have implemented our unique
solution in hundreds of SAP systems. Whether you are looking to consoli-
date complex existing processes or are interested in implementing an EDI
solution for the first time, our unique Integration Hub will allow you to benefit
from full EDI functionality and unparallelled data visibility from within your exist-
ing SAP user interface!
Connections That Work
FIND OUT MORE
For more information on ecosio’s services and to find out how we can help your business in
particular, email edi@ecosio.com or give us a ring on +44 20 3369 5760.
ABOUT ECOSIO