SAP · WebEDI · Supplier Integration
Connecting Non-EDI Suppliers to SAP
ESS Hub connects suppliers without traditional EDI capability to existing SAP and ERP supplier processes through a web-based supplier collaboration platform.
Non-EDI suppliers work with business information in ESS Hub, while the implemented integration architecture exchanges structured data with the customer's backend systems. Existing EDI suppliers can continue using their established EDI connections.
This allows companies to extend structured digital collaboration across a wider supplier base without requiring every supplier to operate its own EDI infrastructure. ESS Hub is a supplier collaboration platform that is configured and integrated with the customer's existing processes and system landscape — not a portal developed separately for each customer.
Scenario
The non-EDI supplier problem
A manufacturer or automotive Tier-1 typically has suppliers already connected through EDI, and a larger group without EDI infrastructure: smaller suppliers, low-volume suppliers, newly onboarded suppliers, suppliers working with e-mail, spreadsheets or PDFs, suppliers with very different technical capabilities. The backend organization already runs a structured SAP or ERP process; the communication channel with the second group is manual. ESS Hub addresses this supplier-facing gap.
Architecture
The ESS Hub approach
ESS Hub provides an additional supplier interaction channel. It does not require all suppliers to use the same technical connection. EDI suppliers can remain on EDI. Non-EDI suppliers can use ESS Hub. The customer's SAP / ERP process remains structured.
Supplier experience
What the supplier sees
The non-EDI supplier does not work with EDIFACT syntax, VDA message structures, IDocs, mappings or integration protocols. It works with the business process in the ESS Hub web portal — the processes confirmed in the product are listed below. Available processes depend on the modules and integration scope implemented for the customer.
- Procurement
- Purchase-order collaboration, RFQs and supplier quotations. Procurement in ESS Hub
- Logistics
- Scheduling agreements, delivery schedules and call-offs; ASN; packaging and handling units; automotive labels. Logistics in ESS Hub · Scheduling agreements · ASN & DESADV · Automotive labels
- Quality
- APQP, PPAP, 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
Backend
What SAP sees
ESS Hub is the supplier-facing collaboration layer; SAP or another ERP can remain the backend system of record for the relevant processes. The integration layer handles the technical exchange required by the implemented architecture — ESS Hub does not necessarily communicate with SAP directly, and no specific IDoc type, BAPI, RFC, API, SAP module or table is implied on this page. SAP Integration
Coexistence
Use your existing integration landscape
ESS Hub is designed to work with an existing enterprise integration landscape. A company does not need to replace functioning EDI connections simply because additional suppliers need a web-based collaboration channel. The objective is channel flexibility with a structured backend process. EDI & B2B Integration
Demand
Scheduling agreements and call-offs
Demand information from the customer's SAP/ERP can be made available to non-EDI suppliers through ESS Hub according to the implemented integration. The supplier sees scheduling agreements and call-offs with part, plant, quantity, delivery date and cumulative quantities, confirms them or proposes an alternative date and quantity; the enterprise follows confirmations by supplier in the Control Tower. No SAP object or message type is implied.
Shipping
ASN from a supplier without EDI
A supplier without its own EDI infrastructure can create an ASN through ESS Hub. The supplier works with shipment and packaging information in the portal, while the implemented integration architecture converts and routes the resulting structured information into the customer's backend process. ASN & DESADV · VDA 4987 · Automotive Labels
Standards
Automotive standards without exposing EDI complexity
ESS Hub can support automotive processes using standards such as VDA/EDIFACT where implemented, without requiring the portal user to work with the message syntax. In the product today: the DESADV generated for a shipment follows VDA 4987 (Global DESADV), and the handling-unit labels are GTL labels based on VDA 4994 plus an AIAG B-10 label type. Which standards a customer uses is part of the implementation.
Scope
Beyond logistics
Connecting a supplier digitally should not stop at orders and ASN. In ESS Hub the same non-EDI supplier also works on quality — APQP, PPAP, 8D, Supplier Scorecards — and sees its invoice and payment status; procurement covers purchase orders and RFQs.
Onboarding
Supplier onboarding
How a non-EDI supplier becomes a portal supplier in 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 accounts linked to the supplier's portal profile; an account without a linked profile cannot enter the portal
- the supplier's administrator manages colleagues and their roles in the Team & invitations area; business roles and a permission matrix define what each role can see and do
- a getting-started checklist guides the first steps: confirm the pending packaging data sheet, read and confirm open supplier letters and required documents, review the contact matrix
Onboarding is initiated by the enterprise — invitation, process scope, required onboarding documents — and the supplier registers from its invitation and completes the requested documents before it is activated (Supplier Onboarding). Single sign-on and multi-factor authentication are answered in the vendor assessment rather than described here. Supplier Portal · Security & Architecture
Requirements
What ESS Hub does not require
For portal use, ESS Hub does not require the non-EDI supplier to operate its own:
- EDI translator
- EDI mapping environment
- B2B gateway
- SAP system
The supplier needs access to the ESS Hub web application and the appropriate account and permissions for the implemented customer process.
Comparison
WebEDI vs traditional EDI
| Traditional EDI | ESS Hub WebEDI | |
|---|---|---|
| Supplier interaction | Machine-to-machine | Web portal |
| Supplier EDI infrastructure | Required | Not required |
| Human interaction | Usually limited | Primary interaction |
| Structured backend process | Yes | Yes, through integration |
| Suitable for | EDI-capable suppliers | Suppliers without EDI / portal users |
This is a conceptual comparison, not a claim that one approach is universally better. The two approaches can coexist in the same supplier landscape.
Due diligence
Architecture principles
Four responsibilities, kept separate — the basis for technical due diligence of an ESS Hub implementation.
- Supplier experience
- ESS Hub: the web portal the supplier works in.
- Business process
- ESS Hub plus the customer's configuration: which modules, scopes and rules apply.
- Integration / transformation
- The integration layer: transmission and, where required, conversion of structured data between ESS Hub and the backend.
- System of record
- SAP / ERP: purchasing, demand, inbound logistics and finance remain there.
Product evidence
Non-EDI supplier collaboration in ESS Hub
Approach
A phased supplier digitization approach
Companies do not have to migrate every supplier at once. Existing EDI suppliers remain connected; selected non-EDI suppliers are onboarded to ESS Hub; additional processes are enabled over time according to the implementation scope. The point is architectural flexibility, not a fixed timeline.
FAQ
Frequently asked questions
How can I connect non-EDI suppliers to SAP?
Give them a supplier-facing collaboration layer instead of an EDI connection: with ESS Hub the supplier works with the business process in a web portal, and the implemented integration architecture exchanges the structured data with SAP. Existing EDI suppliers stay on EDI; the SAP process stays structured.
Can ESS Hub connect suppliers without EDI 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.
Do suppliers need EDI software to use ESS Hub?
No, not for ESS Hub portal use. The supplier needs access to the ESS Hub web application and the appropriate account and permissions; EDI translator, mapping environment and B2B gateway are not required on the supplier side.
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 our existing EDI middleware?
No, not necessarily. ESS Hub is the supplier-facing layer and is designed to work with an existing integration landscape; the customer's integration architecture continues to transmit and, where required, convert the messages.
Can non-EDI suppliers receive scheduling and call-off information?
Yes. Scheduling agreements and call-offs from the customer's SAP/ERP are shown in the supplier's ESS Hub workspace — part, plant, quantity, delivery date, cumulative quantities — where the supplier confirms them or proposes an alternative.
Can non-EDI suppliers create ASNs?
Yes. A supplier without EDI creates the ASN in the ESS Hub web portal — confirmed call-offs, packing into pallets and boxes, labels, dispatch data — and the shipment information enters the customer's integration process.
Can ESS Hub convert portal information into structured EDI processes?
Yes, within the implemented integration architecture: in the standard ESS Hub process the DESADV for a shipment is generated from the shipment record and transmitted; the customer's integration layer transmits it and, where required, converts it to the customer-specific format. Which side performs which transformation is defined in the implementation.
Does ESS Hub support VDA 4987?
Yes. The DESADV generated in ESS Hub follows the VDA 4987 Global DESADV recommendation, where this standard is part of the customer's integration landscape.
Can non-EDI suppliers generate automotive labels?
Yes. After packing a shipment in ESS Hub, the supplier generates the handling-unit labels — GTL master and single labels based on VDA 4994 and an AIAG B-10 label type — as PDF and ZPL.
Can non-EDI suppliers use APQP, PPAP and 8D in ESS Hub?
Yes. APQP, PPAP, complaints and 8D reports and supplier scorecards are part of the same ESS Hub supplier workspace; they are structured records worked on by buyer and supplier, not EDI messages.
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 ESS Hub.
Does ESS Hub replace SAP?
No. SAP — or another ERP — remains the system of record for purchasing, demand, inbound logistics and finance. ESS Hub is the supplier-facing collaboration layer in front of it.