Automotive · WebEDI · Supplier Collaboration
Automotive WebEDI Supplier Portal
ESS Hub is an automotive supplier collaboration and WebEDI platform designed to connect suppliers with existing SAP, ERP and EDI processes.
Suppliers without their own EDI infrastructure can use ESS Hub through a web portal, while EDI-capable suppliers can continue using established machine-to-machine connections. This allows companies to support suppliers with different levels of digital maturity within the same structured supplier process.
ESS Hub is a standard supplier collaboration platform, developed by EDI & SAP Solutions SRL, that is configured and integrated according to the customer's supplier processes and existing system landscape.
WebEDI provides a browser-based interface for suppliers that need to participate in structured electronic business processes but do not operate their own traditional EDI connection.
Concept
What is WebEDI?
WebEDI provides a browser-based interface for suppliers that need to participate in structured electronic business processes but do not operate their own traditional EDI connection. Instead of producing EDI messages with its own software, the supplier works with business concepts — orders, delivery schedules, shipments, ASN, invoices, quality processes — in the web portal; the structured information reaches the customer's ERP through the integration layer. WebEDI products differ in scope; this page describes ESS Hub.
Architecture
EDI suppliers and non-EDI suppliers
ESS Hub does not require companies to replace working EDI connections. Existing EDI suppliers can remain on EDI, while suppliers without EDI can use ESS Hub. The communication channel can be different while the underlying business process remains structured.
Context
Why WebEDI matters in automotive
Automotive supplier networks are not uniform. They typically contain:
- large suppliers with mature EDI capabilities
- smaller suppliers without EDI infrastructure
- suppliers with low transaction volumes
- newly onboarded suppliers
- suppliers operating across different technical environments
Forcing every supplier to implement traditional EDI is not always practical, and leaving the rest on e-mail and spreadsheets breaks the structured process. ESS Hub provides a portal-based path for suppliers that need access to the business process without operating their own EDI infrastructure, so the same call-offs, ASNs, quality processes and invoice information reach every supplier in a structured form.
Scope
What suppliers can do in ESS Hub
Four areas, one supplier workspace, one sign-in. The list is limited to functionality in ESS Hub today.
- Procurement
- Purchase-order collaboration, RFQs and supplier quotations. Procurement in ESS Hub
- Logistics
- Scheduling agreements, delivery schedules and call-offs; ASN with packaging and handling units; automotive labels; returnable packaging. Logistics in ESS Hub · Scheduling agreements · ASN & DESADV · Automotive labels
- Quality
- APQP, PPAP, supplier complaints and 8D reports, supplier scorecards. Supplier Quality in ESS Hub · APQP · PPAP · 8D · Supplier Scorecards
- Finance
- Invoice information, invoice status and payment-status visibility. Invoicing in ESS Hub · Invoice & payment status
Integration
From portal action to structured integration
The supplier does not need to create an EDI message manually. The supplier works with the business process in ESS Hub; the implemented integration architecture handles the structured exchange required by the customer's backend environment. In the standard ESS Hub process, for example, the DESADV for a shipment is generated from the shipment record; the customer's integration layer transmits it and, where the implementation requires, converts it. Which side performs which transformation is defined in the implementation — ESS Hub does not necessarily perform every EDI mapping when an existing integration layer performs that role.
SAP
WebEDI and SAP
ESS Hub can operate as the supplier-facing collaboration layer for an existing SAP landscape. The SAP environment remains the system of record for purchasing, demand, inbound logistics and finance, while ESS Hub provides supplier-facing workflows and visibility. No specific SAP IDoc, API, BAPI or module is implied here; the integration is implemented per landscape. SAP Integration · Non-EDI suppliers in SAP processes · ESS Hub technical architecture
Coexistence
WebEDI and existing EDI infrastructure
ESS Hub is designed to complement an existing EDI landscape rather than requiring it to be replaced. EDI-capable suppliers can continue exchanging structured messages through existing B2B connections. ESS Hub provides an additional supplier-facing channel for suppliers that use the web portal. EDI & B2B Integration
Demand
Scheduling and call-offs
WebEDI suppliers take part in the scheduling and call-off process supported by ESS Hub: they see their scheduling agreements and call-offs — part, plant, quantity, delivery date, cumulative quantities — confirm them or propose an alternative, and the enterprise follows confirmations by supplier in the Control Tower. Demand data reaches the portal from the customer's SAP/ERP through the integration layer.
Shipping
ASN and shipping
Non-EDI suppliers create advance shipping notices in ESS Hub: they select confirmed call-offs, pack pallets and boxes, obtain the handling-unit labels and enter the dispatch data. The shipment information is transmitted to the customer's ERP through the integration; the exact message format depends on the implemented integration — in the standard process a VDA 4987 Global DESADV. ASN & DESADV · VDA 4987 · Automotive Labels
Quality
Supplier Quality through WebEDI
ESS Hub is not limited to logistics transactions. Non-EDI suppliers also take part in the supplier-quality processes available in ESS Hub — APQP, PPAP, complaints and 8D reports, supplier scorecards. These are not EDI messages: they are structured records in the same supplier portal, which extends beyond transactional EDI processes. Supplier Quality in ESS Hub
Finance
Finance visibility
Suppliers also access relevant invoice and payment information through ESS Hub: the invoice list with its status and the payment information made available by the connected finance process, in the My Invoices and Payments areas of the supplier workspace. Electronic invoices can be generated in ESS Hub from acknowledged shipments where this process is implemented. Invoice & payment status · Invoice processing · Invoicing in ESS Hub
Platform
One supplier experience across processes
Where ESS Hub functionality is implemented, the supplier does not use a separate tool for every interaction with the customer: procurement, logistics, quality and finance meet in one workspace, with one sign-in and one supplier record. Each area keeps its own process; what they share is the supplier context.
Onboarding
Supplier onboarding
How a supplier enters ESS Hub today:
- the enterprise invites the supplier into defined process scopes (for example logistics); invitations show invited, accepted or revoked, and can be revoked
- supplier users sign in with their accounts; the supplier's administrator manages colleagues and their roles in the Team & invitations area
- a getting-started checklist in the supplier workspace lists the setup steps: confirm the pending packaging data sheet, read and confirm open supplier letters and required documents, review the contact matrix
- EDI-capable suppliers have an EDI connection self-onboarding area: choice of format (VDA 4987 Global DESADV or ANSI X12 856), test parameters (endpoint, protocol, test GLN, partner ID, EDI contact) and a browser-side check of a sample DESADV or INVOIC message
Onboarding is initiated by the enterprise — invitations, process scope, required onboarding documents — and the supplier registers from its invitation and completes the requested documents before it is activated. Supplier Onboarding
Security
Security and access
Suppliers access ESS Hub through authenticated accounts, and access is controlled according to the implemented security model: business roles with a data-driven permission matrix (RBAC), supplier-level separation so that a supplier sees only its own documents, an audit trail for enterprise administrators, and HTTPS for every session. Single sign-on and multi-factor authentication are answered as part of the vendor assessment rather than described here.
Product evidence
WebEDI supplier experience in ESS Hub
Landscape
WebEDI without replacing your existing landscape
ESS Hub can be introduced as a supplier collaboration layer around an existing SAP, ERP and EDI landscape. Companies can therefore extend structured digital collaboration to additional suppliers without requiring a wholesale replacement of existing B2B integration infrastructure. Supplier Portal · Logistics in ESS Hub
FAQ
Frequently asked questions
What is WebEDI?
WebEDI provides a browser-based interface for suppliers that need to participate in structured electronic business processes but do not operate their own traditional EDI connection. The supplier works with business information — orders, schedules, shipments, invoices — in a web portal, and the structured exchange with the customer's systems is handled by the platform and the integration layer.
Is ESS Hub a WebEDI supplier portal?
Yes. ESS Hub is an automotive supplier collaboration and WebEDI platform: suppliers without EDI work in the ESS Hub web portal, connected with the customer's SAP, ERP and EDI processes.
Is ESS Hub designed for automotive suppliers?
Yes. ESS Hub is built for automotive and manufacturing supplier collaboration: scheduling agreements and call-offs, ASN with packaging and handling units, automotive labels, VDA 4987 despatch advice, supplier quality processes and invoice visibility.
Can suppliers use ESS Hub without EDI?
Yes. That is the WebEDI channel: a supplier signs in to the ESS Hub web portal and works with the business process; no EDI software or EDI infrastructure is required on the supplier side.
Can ESS Hub connect non-EDI suppliers to SAP?
Yes, through the implemented integration architecture. Demand data from SAP reaches the supplier's ESS Hub workspace through the integration layer, and the structured information the supplier creates — for example the ASN — is transmitted back into the customer's SAP process through the same architecture.
Can existing EDI suppliers continue using EDI?
Yes. EDI-capable suppliers keep exchanging messages through the customer's existing B2B integration landscape; ESS Hub adds the portal channel for the suppliers that need it.
Does ESS Hub replace EDI middleware?
No, not necessarily. ESS Hub is the supplier-facing layer and is designed to complement an existing EDI and integration landscape; the customer's integration architecture continues to transmit and, where required, convert the messages.
What supplier processes are available through ESS Hub?
Procurement (purchase orders, RFQs and supplier collaboration), logistics (scheduling agreements and call-offs, ASN with packaging and handling units, automotive labels, returnable packaging), quality (APQP, PPAP, complaints and 8D, supplier scorecards) and finance (invoice information, invoice status and payment-status visibility), in one supplier workspace.
Can suppliers create ASNs through ESS Hub?
Yes. The ESS Hub shipment wizard guides the supplier through selecting confirmed call-offs, packing, labels and dispatch; the shipment information is then transmitted to the customer's ERP through the integration.
Does ESS Hub support VDA 4987?
Yes. The DESADV generated in ESS Hub for a shipment follows the VDA 4987 Global DESADV recommendation, where this standard is part of the customer's integration landscape.
Does ESS Hub support APQP and PPAP?
Yes. APQP and PPAP are part of the ESS Hub Supplier Quality environment, together with supplier complaints, 8D reports and supplier scorecards.
Can suppliers see invoice and payment status?
Yes. Suppliers see the status of their invoices and the payment information made available by the connected finance process in the My Invoices and Payments areas of their ESS Hub workspace.
Can ESS Hub work with an existing SAP landscape?
Yes. ESS Hub operates as the supplier-facing collaboration layer for an existing SAP landscape: SAP remains the system of record, and the integration between SAP and ESS Hub is implemented per landscape, using the customer's existing EDI and integration architecture where available.