Modules
Still on ECC
Maintenance End
Supported
Timeline
Why SAP ECC customers add Payment Hub, don't wait for the S/4HANA migration to capture value
SAP ECC (SAP ERP Central Component) is SAP's long-standing enterprise ERP, designed to unify finance, supply chain, production, human resources, and customer service into a single integrated platform, and the backbone of many of the world's largest enterprises for decades. ECC's strength lies in supporting multi-site, multi-national operations with real-time data integration across departments and global subsidiaries. In-depth industry-specific functionality for sectors including manufacturing, utilities, oil and gas, retail, and life sciences, and the ability to simplify operations, ensure regulatory compliance, and maintain visibility across complex supply chains.
SAP ECC is built on the SAP NetWeaver platform, which provides the foundation for application development, integration, and system management. Its business processes are powered by ABAP (Advanced Business Application Programming), SAP's proprietary programming language, which allows for extensive customization and automation. On the database side, ECC is database-agnostic, meaning it can run on several leading relational databases, Oracle, IBM DB2, Microsoft SQL Server, SAP ASE (formerly Sybase), and in later versions also SAP HANA. This flexibility gave enterprises freedom to align ECC with their existing IT landscapes over the past two decades. The result: enterprises commonly run ECC across 25-500+ Company Codes globally, with decades of ABAP customizations accumulated through Z-tables, user-exits, BAdIs, customer-namespace function modules, and append structures.
SAP has announced that mainstream support for SAP ECC will end in 2027 (with limited extended support until 2030). Enterprises currently running ECC are encouraged to begin planning their migration to SAP S/4HANA, SAP's next-generation ERP system built on the in-memory HANA database. Per SAPinsider's 2025 Buyer's Guide, 35,000+ customers remain on ECC or SAP Business Suite ahead of the deadline. Migration projects typically run 12-24 months. Customers facing this migration timeline have a choice: wait for the migration to modernize payments (deferring the value), or modernize payments today on ECC and carry the configuration forward through the migration. Payment Hub is designed for the second path. Deploy on ECC today through SAP's published BAPI / RFC / IDoc / SAP Gateway / NetWeaver PI integration paths. Capture L3 interchange savings, SEPA SDD adoption, dunning automation, and customer-portal modernization immediately. Carry the configuration forward through the eventual S/4HANA migration without re-implementation.
The six SAP ECC functional modules, all served by Payment Hub
SAP ECC unifies finance, supply chain, production, HR, and customer service into a single integrated platform across six core functional modules. Each has different payment characteristics. Payment Hub adapts to each.
Financial Management
Complete framework for managing both statutory accounting and internal cost control. Primary surface for Payment Hub, Incoming Payment cash application, GL impact, multi-currency, Cost Center attribution.
Materials Management
Manages flow of materials across the supply chain, from purchasing raw materials to handling inventory and consumption. AP-side, coexists with Payment Hub's AR focus. Procurement deposits where applicable.
Sales &, Order Management
Manages the entire order-to-cash process, from initial customer inquiry through order fulfillment, shipping, billing, and payment. Drives the O2C flow that Payment Hub completes via Incoming Payment.
Production Management
Long-term capacity planning to shop floor execution. Drives manufacturing-specific patterns: BOM-driven deposits, milestone billing on production-status events, partial-shipment captures from Production Order completion.
Supply Chain Management
Integrates procurement, production, warehousing, logistics, and quality control into a single smooth flow. Drives shipment-triggered captures via Outbound Delivery events. Warehouse-aware Payment Hub routing.
Customer Relationship Management
For SAP ECC customers running SAP CRM 7.0 alongside ECC (the typical pre-S/4HANA C/4HANA pattern). Drives sales-pipeline-aware payment flows and CRM-side customer-master enrichment for stored credentials.
Each module drives a distinct Payment Hub fit. Financial Management (FI / CO) is the primary surface, every Payment Hub-driven Incoming Payment lands in BSEG / BSAS / BKPF with full document-line-item granularity, feeding GL impact through ECC's standard accounting framework with multi-Currency revaluation and Cost Center attribution. Materials Management (MM) is AP-side, coexists with Payment Hub's AR focus through Procurement-to-Pay flows. Sales &, Order Management (SD) drives the order-to-cash flow, Sales Order (VBAK / VBAP) → Outbound Delivery (LIKP / LIPS) → Customer Invoice (VBRK / VBRP) → Incoming Payment (Payment Hub). Production Management (PP) drives manufacturing patterns, BOM-driven deposits, Production Order milestone captures, partial-shipment captures. Supply Chain Management (SCM) drives shipment-triggered captures via Outbound Delivery events with warehouse-aware MID routing. Customer Relationship Management (CRM): for the typical pre-S/4HANA C/4HANA pattern of SAP CRM 7.0 alongside ECC, drives sales-pipeline-aware payment flows and CRM-resident customer-master enrichment for stored-credential automation.
The ECC → S/4HANA migration bridge, deploy today, carry forward tomorrow
35,000+ enterprises remain on SAP ECC ahead of the 2027 mainstream-maintenance deadline. Migration projects typically run 12-24 months. Customers don't have to defer payment modernization until after the migration. Payment Hub deploys on ECC today and carries the configuration forward through any of the three SAP-supported migration paths.
Deploy Payment Hub on SAP ECC
Through SAP's published integration paths, BAPI / RFC, IDoc, SAP Gateway / OData (EHP 7+), NetWeaver PI / PO. Respects decades of ABAP customizations.
- L3 enrichment from VBAP / VBRP
- Multi-Company-Code routing
- SEPA SDD via DMEE
- Customer-portal modernization
- Dunning automation
Migration project runs in parallel
SAP migration team focuses on the SAP core: data harmonization, custom code adaptation, role redesign, process redesign. Payment Hub continues to deliver value uninterrupted.
- L3 savings continuing
- Customer portal active
- SEPA SDD active
- Dunning automation active
- Migration team unburdened
Configuration carries forward to S/4HANA
Brownfield, greenfield, or selective data transition, Payment Hub re-points to the destination S/4HANA tenant. Gateway connections, routing rules, surcharging all carry across.
- Universal Journal posting
- BTP-side extensions
- Embedded Analytics on payments
- Fiori UX-aligned portal
- Hyperscaler-agnostic
The bridge is what makes Payment Hub distinctive for SAP ECC customers. Three migration paths to S/4HANA, brownfield system conversion, greenfield new implementation, selective data transition: all supported with Payment Hub configuration carrying forward. The integration surface evolves (BAPI / RFC / IDoc on ECC → OData / SAP Gateway / BTP on S/4HANA), but the application configuration carries forward without re-implementation: gateway connections preserved, routing rules preserved, surcharging policies preserved, dunning ladders preserved, customer-portal customizations preserved, L3 mappings preserved. The migration team continues to focus on the SAP core (where the heavy lifting happens, data harmonization, custom-code adaptation, role redesign, process redesign). Payment Hub is a clean overlay that survives the cutover. For customers in earlier migration-planning stages who haven't yet committed to brownfield vs greenfield vs selective data transition, Payment Hub's deployment doesn't constrain the choice.
SAP NetWeaver, ABAP, and database-agnostic deployment, the platform Payment Hub plugs into
SAP ECC's longevity comes from its platform foundation, SAP NetWeaver for application services, ABAP for customization, and database-agnostic architecture spanning Oracle, IBM DB2, Microsoft SQL Server, SAP ASE, and SAP HANA. Payment Hub plugs into the platform regardless of database choice or NetWeaver release.
The SAP ECC platform foundation has implications for Payment Hub. SAP NetWeaver: Payment Hub uses NetWeaver-published integration paths exclusively (SAP Gateway / OData, BAPI / RFC, IDoc, NetWeaver PI / PO). No NetWeaver release-level constraints. The integration works on NetWeaver 7.0 through 7.5x. ABAP customization respect: decades of accumulated Z-tables, user-exits, BAdIs, customer-namespace function modules, append structures, SAPGUI modifications all preserved through Payment Hub's API-based integration. Payment Hub never modifies ABAP code. Database-agnostic deployment: Payment Hub integration is identical across Oracle, IBM DB2, Microsoft SQL Server, SAP ASE, and SAP HANA backends. The integration operates on the application layer regardless of underlying database. 2027 mainstream maintenance end: Payment Hub is migration-bridging-ready. Deploy on ECC today, the configuration carries forward to S/4HANA without re-implementation.
SAP ECC module map, all touched by Payment Hub
SAP ECC's module breadth covers the full enterprise functional reach. Payment Hub integrates across the modules. Primary touch points are FI / CO and SD. Supporting touch points across the rest.
Financial Management (FI / CO)
Sales &, Distribution (SD)
Materials &, Supply Chain (MM / SCM)
Production &, Quality (PP / QM / PM)
Human Resources (HCM)
Platform &, Integration
The integration touches every module category. Financial Management (FI / CO) is the primary surface, Customer master, AR Invoice, Incoming Payment, GL impact, multi-currency revaluation, FSCM (Financial Supply Chain Management) collections all flow through Payment Hub via BAPI / RFC and SAP Gateway / OData. Sales &, Distribution (SD) drives the order-to-cash flow with Order Management, Outbound Delivery, Billing, Credit Management. Materials &, Supply Chain (MM / SCM) coexists on AP-side, warehouse-aware Payment Hub routing for Outbound Delivery events. Production &, Quality (PP / QM / PM) drives manufacturing-specific patterns (BOM-driven deposits, Production Order milestone captures). Human Resources (HCM) coexists, Payroll on AP-side, Travel Management feeds T&E-billed AR through Payment Hub on the receivable side. Platform &, Integration tools are the path Payment Hub uses (NetWeaver, BAPI / RFC, IDoc, NetWeaver PI / PO, SAP Gateway / OData on Enhancement Package 7+, plus the SAP Web Channel and SAP Customer Checkout for customer-facing surfaces).
Payment Hub vs SAP ECC's legacy certified-PSP integrations, enterprise modernization comparison
SAP ECC has multiple generations of certified Payment Service Provider integrations accumulated over the decades. They work for simple invoice-payment scenarios but constrain enterprise-scale modernization. Payment Hub is the gateway-agnostic alternative, and migration-ready to S/4HANA.
| Capability | Legacy Certified-PSP Add-ons | Payment Hub on SAP ECC |
|---|---|---|
| Gateway / processor choice | ● SAP-certified PSPs (Worldline / ConCardis / regional acquirers), switching = re-config | ● 19+ gateways (Worldpay, Adyen, Fortis, PayTrace, Stripe, Authorize.Net, NMI, USAePay, plus regional acquirers, plus SAP-certified gateways if you keep them) |
| BSEG / BSAS / BKPF posting integration | ● Native, PSP creates Incoming Payment journal entries | ● Same, Payment Hub creates Incoming Payment via BAPI / RFC. Full document-line-item granularity preserved |
| Multi-Company-Code routing | ● Single-MID typical at enterprise scale. Multi-CoCd support varies by PSP | ● Per-Company-Code / per-Country / per-Currency routing, scales to 500+ entities |
| Level III interchange enrichment | ● Not auto-enriched, enterprise volume non-qualified or partial-qualified | ● Auto-enriched from VBAP / VBRP / AFKO / PROJ line records, 20+ fields per transaction. Enterprise L3 yield $1M-$10M+/yr |
| SEPA SCT and SDD direct debit | ● Native to ECC European localizations via DMEE | ● Augmented, multi-bank SEPA SDD routing, B2B vs CORE scheme selection, return automation, ACH bridging on same Customer master |
| ABAP customization respect | ● Some PSPs deploy ABAP-side modifications that complicate upgrades | ● API-based integration only, zero ABAP modifications. Respects Z-tables, user-exits, BAdIs, append structures |
| Migration-readiness to SAP S/4HANA | ● Some PSPs require complete re-implementation post-migration | ● Configuration carries forward to S/4HANA through brownfield / greenfield / selective data transition |
| Multi-invoice consolidation across Company Codes | ● Per-invoice flow per certified PSP | ● Batch pay across multiple invoices, multiple Company Codes, multiple currencies, single capture, line-level postings |
| Surcharging / convenience fees | ● Not native | ● Compliant surcharging engine (per-state, per-country, per-card-brand, per-merchant, auto-disabled where illegal) |
| Customer portal payment surface | ● SAP Web Channel / Customer Checkout / partner portal. Basic payment via certified PSP | ● Modernized embedded payment surface, multi-invoice batch pay, stored credentials, multi-currency, surcharging disclosure |
| Dunning automation | ● Standard SAP dunning levels (F150), not gateway-aware retry | ● Augmented, gateway-aware retry intelligence, per-Company-Code / per-Country / per-Language |
| Database-agnostic deployment | ● Some PSPs database-specific, varies | ● Same integration on Oracle / DB2 / SQL Server / SAP ASE / HANA |
The Missing LinkBetween Paymentsand Your ERP
Clarity Payment Hub closes that gap, connecting your orders, invoices, and payment channels into one flow.
Speak to a Platform ArchitectHow the integration works, BAPI + RFC + IDoc + SAP Gateway + NetWeaver PI
Payment Hub plugs into SAP ECC through SAP's published integration paths. BAPI / RFC for traditional programmatic interface. IDoc for legacy partner messaging. SAP Gateway / OData for modern REST-style integration on Enhancement Package 7+. SAP NetWeaver PI / PO as the middleware orchestration layer. ABAP append-structure / BAdI extension points where required. Zero ABAP modifications, respects decades of customizations. Eight features that come online when SAP ECC gets Payment Hub:
BAPI / RFC programmatic interface
Traditional SAP programmatic interface, full access to ECC's Business Object Repository (BOR) and Function Module library. Used for real-time scenarios, token, charge, refund, void, BAPI_INCOMINGINVOICE_POST or BAPI_PAYMENT_CREATE for Incoming Payment, customer master lookups.
IDoc for legacy partner messaging
Traditional EDI-style messaging where partner integrations require IDoc-based flows. Payment Hub generates and processes IDocs (PEXR2002 for payment instructions, FIDCC1 for FI document creation, etc.) where appropriate. Works with existing IDoc-routing infrastructure.
SAP Gateway / OData (EHP 7+)
Modern REST-style integration available on Enhancement Package 7 and later. Provides JSON / XML payloads via OData services. Same integration pattern that S/4HANA uses. The configuration ports forward through the migration without re-implementation.
SAP NetWeaver PI / PO middleware
Where customers run NetWeaver PI / PO as their integration backbone (common in larger ECC enterprises with established SAP integration practices), Payment Hub registers as another integration scenario alongside existing iDoc / BAPI / RFC adapters.
Enterprise-scale L3 enrichment
Pulls 20+ required L3 fields from SAP ECC Sales Order line items (VBAP), Customer Invoice line items (VBRP), Production Order line records (AFKO / AFPO), and Project line records (PROJ / PRPS). Enterprise customers with $250M-$1B+ commercial-card volume recover $1M-$10M+/yr.
Multi-Company-Code routing at scale
Each ECC Company Code (BUKRS) gets its own gateway / MID / bank account / currency / language / tax setup / surcharging policy / compliance overlay. Routing decisions on Company Code + Country (LAND1). Scales naturally to 25-500+ Company Codes across enterprises.
SEPA SCT / SDD via DMEE augmentation
Builds on SAP ECC European localizations' native SEPA support via the DMEE (Data Medium Exchange Engine). Multi-bank SEPA SDD routing per Company Code / country, mandate management, B2B vs CORE scheme selection, return automation via DMEE format-tree extensions.
ABAP customization respect (zero modifications)
Payment Hub uses SAP ECC's published integration paths exclusively, zero ABAP modifications. Decades of accumulated Z-tables, user-exits, BAdIs, customer-namespace function modules, and append structures all preserved. User-exits on financial events fire normally.
The integration workflow, an industrial-equipment manufacturer on SAP ECC across 18 countries, modernizing payment ahead of S/4HANA migration
Walk through one realistic SAP ECC scenario. Calderwood Industrial Equipment, a $3.8B global industrial-equipment manufacturer of compressors and turbines for oil &. Gas, power generation, and chemical-processing markets, headquartered in Houston, Texas with operations in 18 countries (US, Canada, Mexico, Brazil, UK, Germany, France, Italy, Netherlands, Norway, Saudi Arabia, UAE, India, Singapore, Australia, China, Japan, South Korea). Running SAP ECC 6.0 with Enhancement Pack 8 since 2008. 9,200 employees. 42 Company Codes globally (multiple per country for legal-entity structures). Heavy ABAP customization accumulated over 16 years, 340+ Z-tables, ~600 user-exits, dozens of BAdIs, SAPGUI screen modifications across customer/vendor/sales/billing transactions. Multi-currency footprint: USD primary, plus EUR, GBP, NOK, BRL, MXN, AED, INR, SGD, AUD, CNY, JPY, KRW. Currently uses one Worldline-certified PSP integration globally (deployed 2014) plus native SEPA SCT/SDD via DMEE for European receivables. Plans a 24-month brownfield S/4HANA migration starting Q2 2026. Payment modernization can't wait. Eight steps showing how Payment Hub deploys today on ECC and bridges to the eventual migration.
OEM order, $2.8M USD compressor package from a Texas-based oil-services major
Calderwood's Houston sales team takes a $2,800,000 USD order from one of the major US oil-services companies for a compressor-package assembly: 8 line items including the main compressor, motor, controls, skid, and installation services. SAP ECC creates Sales Order in Company Code US01-Calderwood-Houston, currency=USD. SD module creates the Sales Document (VBAK / VBAP). Credit-management workflow auto-approves given the customer's investment-grade rating. Multi-year project record opens in PS (Project System) for the multi-month delivery and installation. Existing Z-table ZCALDERWOOD_PROJ continues to log internal project metadata as it has for 16 years.
SO-US-2026-04217 · USD 2.8MCoCd=US01-Calderwood-Houston8 lines · 4-month project30% deposit at order, customer AP elects Visa Purchasing card for the $840K deposit
Calderwood's standard heavy-equipment terms: 30% deposit at order, 50% at shipment, 20% at commissioning sign-off. ECC SD generates a deposit Customer Invoice (VBRK / VBRP) for $840,000. Customer's AP team elects to pay via their corporate Visa Purchasing card (working-capital optimization through their card-issuer's extended-billing program). Payment Hub catches the deposit-due event via SAP Gateway / OData subscription. Sends a payment link to customer's AP via the Calderwood customer portal (replacing the limited Worldline-PSP-driven portal that existed previously). Customer AP authorizes via stored card.
Deposit $840K · 30%Visa Purchasing (commercial)Payment Hub modern portalL3 enrichment + Company-Code routing, 8 line items, USD capture, Worldpay US (replacing legacy Worldline)
L3 enrichment fires from 8 Sales Order line items in ECC VBAP. Avalara state-tax data flows in cleanly via ECC's tax engine (Texas state tax handling). All 22 L3 fields packaged. Routing matrix: Company Code=US01-Calderwood-Houston, Country=US, Currency=USD → Worldpay US merchant account (Calderwood replaced the legacy Worldline-certified gateway with Worldpay for North American operations as part of the pre-migration payment modernization), USD capture, settlement to Calderwood's JPMorgan Chase USD account. Capture posts at large-ticket commercial-card interchange. L3 savings on this single deposit transaction: ~$2,400.
Worldpay US · USD · ChaseL3 from 8 line itemsL3 saved $2,400Incoming Payment via BAPI, BSEG / BSAS / BKPF posting. Existing user-exits fire correctly
Capture confirms at Worldpay. Payment Hub creates Incoming Payment in SAP ECC via BAPI_PAYMENT_CREATE: $840,000 against deposit Customer Invoice INV-US-04217-DEP, Worldpay reference attached as gateway transaction reference (custom field on BSEG via existing append structure ZCALDERWOOD_BSEG_APPEND), Company Code=US01-Calderwood-Houston set. The journal entry posts into BSEG (line items), BSAS (cleared items), BKPF (header) with full document-line-item granularity. Calderwood's existing user-exit USEREXIT_DOCUMENT_CHANGED on AC_DOCUMENT BAdI fires: notification to assigned Project Manager that the deposit landed and engineering-design phase can proceed. Z-table ZCALDERWOOD_PROJ continues to be updated by the existing user-exit logic. Existing FB05-driven manual-cash-application workflow retired for this customer's Company Code (cleaner automated flow now).
Incoming Payment via BAPIBSEG / BSAS / BKPF postedExisting user-exits fireManufacturing + cross-border SEPA SDD adoption for European customers
Production scheduling kicks off across Calderwood's manufacturing footprint. Houston handles final assembly. German subsidiary (DE01 Company Code) handles motor windings (cost-advantaged regional manufacturing). ABAP-customized Inter-Company billing flows via FB05 cross-Company-Code postings transfer COGS correctly. Same week, Calderwood's German team activates SEPA SDD for 78 European Tier-2/Tier-3 customers via Payment Hub (replacing manual wire/check collections). Multi-bank SDD routing through Adyen Europe (replacing Worldline EU). B2B-scheme mandates for the larger industrial customers, CORE-scheme for smaller. €1.2M of European AR moves from wire/check to SEPA SDD in the first month.
DE01 cross-Company-CodeSEPA SDD adoption €1.2MWorldline EU retiredMulti-Company-Code rollout, all 42 Company Codes live across 18 countries
Over 8 months pre-migration, Calderwood completes Payment Hub rollout to all 42 Company Codes across 18 countries. Each Company Code routes to its currency-matched merchant account: Worldpay US for USD, Worldpay UK for GBP, Adyen Europe for EUR / NOK, Cielo for BRL, Conekta for MXN, regional acquirers for AED / INR / SGD / AUD / CNY / JPY / KRW. The legacy Worldline-certified PSP integration (deployed 2014) fully retires across all entities. Year 1 cumulative L3 savings across all 42 Company Codes: $2.4M against Calderwood's $186M global B2B card volume. SEPA SDD fee savings vs wire/check: additional $620K. Customer portal usage doubles as the modernized embedded portal becomes the preferred way for industrial customers to pay multi-Company-Code invoices.
42 Company Codes live · 18 countriesL3 saved $2.4M · SDD saved $620KWorldline integration retiredS/4HANA brownfield migration kicks off, Payment Hub continues delivering value uninterrupted
Q2 2026, Calderwood's 24-month brownfield S/4HANA migration project begins. The SAP migration team focuses on the SAP core: data harmonization across 16 years of accumulated configurations, custom-code adaptation (340+ Z-tables, 600+ user-exits to assess), role redesign, process redesign, ABAP custom-code remediation for the new ABAP-Cloud-friendly extensibility model. Throughout the 24-month migration, Payment Hub continues to deliver value uninterrupted: L3 savings continuing, customer portal active, SEPA SDD active, dunning automation active, multi-Company-Code routing functional. The migration team is unburdened by payment-side concerns, Payment Hub's API-based integration sits cleanly on top of the running ECC system regardless of the migration project's stage.
24-mo migration startsPayment Hub uninterruptedValue continues during migrationMigration cutover Q2 2028, Payment Hub configuration carries forward to S/4HANA without re-implementation
Q2 2028, Calderwood completes S/4HANA migration (brownfield system conversion completed). Payment Hub re-points to the converted S/4HANA tenant in 72 hours. Gateway connections, routing rules, surcharging policies, dunning ladders, customer-portal customizations, L3 mappings, all carry across without re-implementation. The integration surface evolves underneath (BAPI / RFC / IDoc → OData / SAP Gateway / BTP), but the application configuration is preserved. Payment Hub gains the S/4HANA-specific capabilities (Universal Journal posting via ACDOCA, Embedded Analytics via CDS views, Fiori KPI tiles, BTP-side extensibility on the Azure-hosted RISE deployment Calderwood chose). Cumulative Year 1+2+3 (pre-migration + migration + post-migration) impact: $9.4M savings + improved working-capital terms + faster customer-pay rates. The 16-year ECC investment was preserved through the migration. The modernized payment layer continued delivering value the entire time.
Q2 2028 · S/4HANA cutover72hr re-point · zero re-implementation3-year cumulative $9.4MUse cases that light up on SAP ECC
All eleven Payment Hub use cases run on SAP ECC at enterprise scale. These are the patterns where the SAP ECC integration shines, and where ECC enterprises modernize payment ahead of (or alongside) the eventual S/4HANA migration.
Real-time line-level cash application via BAPI / RFC posting into ECC's classic financial document tables. Full document-line-item granularity preserved. F-28 manual-cash-application workflows retire as Payment Hub automates.
Interchange Enterprise-scale Level III cost reductionAuto-enrichment from VBAP / VBRP / AFKO / PROJ line records via BAPI / RFC. Tax data via ECC's tax engine. Enterprise customers with $250M-$1B+ commercial-card volume recover $1M-$10M+/yr.
Multi-Company-Code Multi-Company-Code / multi-Country routingPer-Company-Code / per-Country / per-Currency routing, different gateways, MIDs, currencies, languages, surcharging policies, compliance overlays. Maps directly to ECC's enterprise multi-entity model. Scales to 500+ Company Codes globally.
SEPA SEPA SCT / SDD via DMEE augmentationBuilds on ECC European localizations' native SEPA via DMEE, multi-bank SDD routing per Company Code / country, mandate management, B2B vs CORE scheme selection, return automation. Bridges SEPA SDD (EU) with ACH (NA) on same Customer master.
O2C End-to-end order-to-cashEnd-to-end O2C through ECC Sales Order (VBAK / VBAP) → Outbound Delivery (LIKP / LIPS) → Customer Invoice (VBRK / VBRP) → Incoming Payment (BSEG / BSAS / BKPF). Project System integration for milestone billing.
Customer Portal Modernized customer portalReplaces SAP Web Channel / Customer Checkout / partner-portal payment surfaces with modernized embedded payment surface. Multi-invoice batch pay across multiple Company Codes, multi-currency, stored credentials, surcharging disclosure, L3 enrichment.
Collections Dunning &, collections automationAugments ECC's standard dunning levels (transaction F150) with gateway-aware retry intelligence. Configurable dunning ladder per Company Code / country / language. Bad debt and AR write-off automation. FSCM Collections Management coexistence.
Tax / Compliance Multi-jurisdiction tax complianceEU VAT / Intrastats / GDPR for European Company Codes. Avalara + state surcharging for North America. Country-specific tax for APAC. Brazilian NFe / Mexican CFDI / Argentine AFIP for LATAM. Built on ECC's localization framework.
ACH ACH / eCheck automationSame-day ACH for North American Company Codes. Bridges with SEPA SDD for European Company Codes on the same Customer master. NACHA validation, returns handling. Best fit for B2B distribution and recurring service contracts.
Cost Recovery Compliant surcharging where legalPer-state, per-country, per-card-brand, per-merchant-class rules. Auto-disabled in jurisdictions where surcharging is illegal. Auto-disclosure on the modernized customer portal in the recipient's language.
Manufacturing O2C Production Order milestone billingFor ECC customers running PP (Production Planning): milestone-based captures from Production Order status events (AFKO / AFPO), partial-shipment captures from Outbound Delivery, BOM-driven deposits, multi-project consolidated billing.
Migration Bridge ECC → S/4HANA migration-readyConfiguration developed today on ECC carries forward through any of the three S/4HANA migration paths (brownfield / greenfield / selective data transition) without re-implementation. Gateway connections, routing rules, surcharging all preserved.
If you're running SAP ECC (any Enhancement Package, any database, any Company Code count), Clarity will run a guided demo on your system, your gateways, your multi-Company-Code routing, and your migration-readiness story. Pilot one Company Code live in 48 hours.
Technical details, for the SAP ECC Basis teams, ABAP developers, and migration architects
For SAP Implementation Partners, certified consultants, SAP Basis administrators, ABAP developers, and ECC-running enterprise IT teams: the connection model, record surface, ABAP customization respect, security posture, and migration-readiness story.
Integration paths in detail
BAPI / RFC: traditional SAP programmatic interface. Full Business Object Repository (BOR) and Function Module library access. Primary path for ECC integration. IDoc: traditional EDI-style messaging for partner integrations and legacy flows. PEXR2002, FIDCC1, ACC_DOCUMENT and others. SAP Gateway / OData: modern REST-style integration available on Enhancement Package 7 and later. Same pattern S/4HANA uses. SAP NetWeaver Process Integration / Process Orchestration (PI / PO): middleware orchestration tier for complex integration scenarios. SAP Web Services / SOAP: for SOAP-style scenarios. BAdIs (Business Add-Ins): in-system extension points respected on Payment Hub-driven postings. Append structures: on standard tables (KNA1, BSEG, VBAK, VBRP) preserved through API introspection. Authentication via SAP communication users, RFC destinations, X.509 certificates, or SAP Single Sign-On.
SAP ECC records consumed and posted
- KNA1 / KNB1 / KNVV (Customer master, General / Company Code / Sales), read/write via BAPI. Stored credentials linked back via append structure custom field.
- VBAK / VBAP (Sales Document header / line items), read for order-state events and L3 enrichment.
- LIKP / LIPS (Outbound Delivery header / line items), read for delivery-triggered captures.
- VBRK / VBRP (Customer Invoice header / line items), read for invoice payment + L3 enrichment. Full multi-currency / localized-tax context.
- BSEG / BSAS / BSAD (document line items / cleared customer items / customer document items), written via BAPI on every Incoming Payment capture. Full document-line-item granularity preserved.
- BKPF (Accounting Document header), written for Incoming Payment headers.
- BSID (open AR receivable items), read for open-item lookup during cash application.
- FAGLFLEXA (general ledger flex table), written for FI postings.
- AFKO / AFPO (Production Order header / item), subscribed for production-completion events.
- PROJ / PRPS (Project / Project WBS), subscribed for project-milestone events. Read for project-billing cash application.
- T001 / T001W (Company Code / Plant master), read for routing rule lookup.
- TCURR / TCURF (Currency / Exchange Rate tables), read for cross-currency routing and capture conversion.
- T007A / T007S (Tax Codes / Tax Code Names), read for tax engine integration. Country localization applies automatically.
ABAP customization respect (zero modifications)
- Payment Hub uses SAP ECC's published integration paths exclusively, zero ABAP modifications.
- Decades of accumulated Z-tables continue to function without conflict. Payment Hub doesn't write to customer-namespace tables.
- User-exits on financial events (USEREXIT_DOCUMENT_CHANGED on AC_DOCUMENT BAdI, OPEN_FI_PERFORM events) fire normally on Payment Hub-driven postings.
- BAdIs (Business Add-Ins) implementations preserved. Payment Hub-driven postings trigger them as designed.
- Append structures on standard tables (KNA1, BSEG, VBAK, VBRP) preserved through API introspection. Custom fields visible to Payment Hub.
- Customer-namespace function modules (Z-functions) coexist. Payment Hub doesn't conflict with custom-namespace.
- SAPGUI screen modifications (transaction-level customizations) preserved. Payment Hub-driven data appears correctly in standard transactions.
- SmartForms / SAPscript custom forms continue to render Payment Hub-aware data.
Multi-Company-Code posture
- Per-Company Code (BUKRS) / per-Country (LAND1) / per-Currency / per-Language gateway routing through Company Code + tax-jurisdiction lookup.
- Cross-currency capture: authorize in one currency, capture in another, settle through ECC's standard exchange-rate revaluation.
- Scales to 500+ Company Codes, typical large-enterprise ECC deployments run 25-500+ Company Codes globally.
- Group reporting currency conversion handled natively through ECC's parallel-currency capability per Company Code.
- Inter-Company Sales / Inter-Company Stock Transfer flows preserved for cross-Company-Code production / services flows.
- FB05 cross-Company-Code journal entries respected for manual intercompany scenarios.
Migration-readiness (ECC → S/4HANA)
- Configuration developed today on ECC carries forward through brownfield (system conversion), greenfield (new implementation), or selective data transition migration to S/4HANA.
- Gateway connections, routing rules, surcharging policies, dunning ladders, customer-portal customizations, L3 mappings all carry across without re-implementation.
- Integration surface evolves (BAPI / RFC / IDoc on ECC → OData / SAP Gateway / BTP on S/4HANA), but application configuration is preserved.
- Post-migration on S/4HANA, Payment Hub gains S/4HANA-specific capabilities (Universal Journal posting via ACDOCA, Embedded Analytics via CDS views, Fiori KPI tiles, BTP-side extensibility for RISE deployments).
- 72-hour re-point post-cutover for brownfield migrations. New-system blueprint inclusion for greenfield. Destination-system deployment for selective data transition.
Security and compliance
- SAP communication users + RFC destinations + appropriate per-Company-Code authorizations. OAuth via SAP Gateway for OData scenarios. X.509 certificates for hardened production. SAP Single Sign-On for federated scenarios.
- PCI DSS Level 1 service provider, with PCI scope minimized via tokenization at gateway.
- Card data never lands in SAP ECC. Tokens stored as append-structure custom field on KNA1 (Customer master).
- SOC 2 Type II (Clarity).
- 3DS2 / SCA support natively across all gateways for European compliance (PSD2).
- GDPR-aligned data handling for EU Company Codes. Right-to-be-forgotten cascades from ECC Customer master deletion.
- Country-specific compliance overlays per Company Code (EU VAT / Intrastats, UK MTD. US sales tax via Avalara, APAC GST/SST, Brazilian NFe / SPED, Mexican CFDI, Indian GST).
- SAP Audit Information System (AIS) integration where applicable.
Deployment scenarios
- SAP ECC 6.0 EHP 0-6 (older deployments): BAPI / RFC / IDoc integration. NetWeaver PI / PO middleware. Pre-SAP Gateway integration patterns.
- SAP ECC 6.0 EHP 7-8 (modern deployments): adds SAP Gateway / OData services for REST-style integration. Same pattern S/4HANA uses.
- SAP ECC on Oracle / DB2 / SQL Server / SAP ASE: Payment Hub integration identical regardless of database.
- SAP ECC on SAP HANA ('Suite on HANA'): Payment Hub gains HANA-accelerated query performance, same integration paths.
- SAP ECC + SAP CRM 7.0: typical pre-S/4HANA C/4HANA pattern. Payment Hub coexists with CRM-driven customer master.
- SAP ECC + SuccessFactors / Concur / Ariba: Payment Hub coexists with cloud-side SAP integrations on the AR side.
- Pre-migration (ECC → S/4HANA project planning stage): Payment Hub deploys on ECC. Configuration designed for migration carry-forward.
- During migration (24-month project in flight): Payment Hub continues to deliver value uninterrupted on the running ECC system.
- Post-migration (cutover to S/4HANA complete): Payment Hub re-points to S/4HANA in 72 hours, configuration preserved.
SAP Business One vs Business ByDesign vs ECC vs S/4HANA
SAP ECC sits at the enterprise tier of the SAP ERP portfolio, the long-standing on-premise / private-cloud ERP that has been the backbone of the world's largest enterprises for decades. SAP S/4HANA is the migration target, SAP's next-generation enterprise digital core. SAP Business ByDesign and SAP Business One serve the mid-market and SMB tiers respectively. For ECC enterprises eventually migrating to S/4HANA, Payment Hub's configuration carries forward through the migration without re-implementation, the integration surface evolves (BAPI / RFC / IDoc on ECC → OData / SAP Gateway / BTP on S/4HANA), but the application configuration (gateway connections, routing rules, surcharging, dunning, customer portal, L3 mappings) is preserved. For ECC enterprises also evaluating SAP Business ByDesign for divisional rollouts or new entities, Payment Hub spans both with the same orchestration layer.
Frequently asked questions about SAP ECC + Payment Hub
Answers to the most common questions from SAP ECC customers, SAP Implementation Partners, SAP Basis administrators, ABAP developers, and enterprise IT teams planning payment modernization for their ECC deployments and the eventual S/4HANA migration.
Does Clarity Payment Hub integrate with SAP ECC?
Yes. Clarity Payment Hub integrates with SAP ECC (SAP ERP Central Component) through SAP's published integration paths: SAP Gateway / OData services (available on Enhancement Package 7+ deployments), BAPI / RFC for traditional programmatic interface to ECC's full object model, IDoc-based partner messaging for legacy EDI scenarios, SAP NetWeaver Process Integration / Process Orchestration (PI / PO) for middleware orchestration, and ABAP append-structure / BAdI extension points where required to respect decades of customer customizations.
Authentication via SAP communication users, RFC destinations, X.509 certificates for hardened production, or SAP Single Sign-On. Every transaction posts to ECC in real time. Customer master (KNA1, KNB1, KNVV), Sales Orders (VBAK, VBAP), Customer Invoices (VBRK, VBRP), Incoming Payments (BSEG, BSAS), and the multi-Company-Code data stay as the single source of truth.
Does Payment Hub support all six functional pillars of SAP ECC?
Yes. SAP ECC unifies finance, supply chain, production, human resources, and customer service into a single integrated platform across six core functional areas. Financial Management (FI / CO modules), General Ledger, Accounts Payable, Accounts Receivable, Asset Management, Bank Accounting, Cost Center Accounting, Profitability Analysis, is the primary cash-application surface. Materials Management (MM), Procurement, Inventory Management, Vendor Management, Invoice Verification, coexists on the AP side.
Sales &, Order Management (SD), Order Management, Pricing and Discounts, Delivery and Shipping, Billing and Invoicing, Credit and Risk Management, drives the order-to-cash flow. Production Management (PP), Material Requirements Planning, Production Orders, Capacity Planning, Bill of Materials, Routing, drives manufacturing-specific patterns. Supply Chain Management (SCM), Warehouse Management, Logistics Execution, Quality Management, drives shipment-triggered captures. Customer Relationship Management (CRM), for customers running SAP CRM alongside ECC, drives sales-pipeline-aware payment flows.
Is Payment Hub on SAP ECC a migration-blocker for the eventual S/4HANA upgrade?
No, and this is a deliberate design decision. With 35,000+ SAP customers still running SAP ECC or SAP Business Suite ahead of the 2027 mainstream-maintenance deadline, Payment Hub is built to be migration-ready. Configuration developed today on SAP ECC carries forward through any of the three SAP-supported migration paths to SAP S/4HANA.
Brownfield (system conversion), Payment Hub re-points to the converted S/4HANA tenant. Gateway connections, routing rules, surcharging, dunning, customer portal, L3 mappings all carry across. Greenfield (new implementation), Payment Hub deploys on the new S/4HANA system using the same configuration model. Selective Data Transition, Payment Hub deploys on the destination S/4HANA system. Transitioned cleared invoice history retains payment-allocation links. The integration surface evolves (BAPI / RFC / IDoc on ECC → OData / SAP Gateway / BTP on S/4HANA), but the application configuration carries forward without re-implementation.
Does Payment Hub support SAP ECC's multi-Company-Code architecture?
Yes. Multi-Company-Code is SAP's foundational architectural pattern across both ECC and S/4HANA, the enterprise's legal-entity structure modeled as Company Codes (BUKRS) with their own currencies, fiscal years, charts of accounts (often shared via the Group Chart), and country-specific tax / localization configurations. Large enterprises commonly run 50–500+ Company Codes across global operations on SAP ECC.
Payment Hub maps directly: each ECC Company Code routes to its own gateway / merchant account / settlement bank / currency / surcharging policy / compliance overlay. Cross-Company captures handle SAP's intercompany flows correctly via cross-Company posting (transactions like FB05 cross-Company-Code journal entry). Routing decisions happen on the originating Sales Order / Customer Invoice's Company Code (BUKRS) and Country (LAND1). The routing matrix is identical to S/4HANA's, so the configuration carries forward through migration.
Does Payment Hub respect SAP ECC ABAP customizations and the decades of accumulated user-exits?
Yes. SAP ECC customers commonly have decades of ABAP customizations accumulated through Z-tables, user-exits, BAdIs, customer-namespace function modules, append structures on standard tables, and SAPGUI screen modifications. Payment Hub uses SAP ECC's published integration paths exclusively (BAPI / RFC / IDoc / SAP Gateway / NetWeaver PI), it doesn't bypass your customizations.
Custom fields on KNA1 / KNB1 / VBAK / VBAP / VBRK / VBRP / BSEG via append structures are visible through BAPI / RFC introspection and carry through to Incoming Payment postings. Z-tables continue to function. User-exits on financial events (e.g., AC_DOCUMENT BAdI, OPEN_FI_PERFORM events) fire normally on Payment Hub-driven postings. SAPGUI customizations continue to render. The integration is non-invasive on the customization layer. Your decades of ECC investment are preserved through the modernization and through the eventual S/4HANA migration.
How is this different from SAP ECC's legacy certified-PSP integrations?
SAP ECC has multiple generations of certified Payment Service Provider integrations accumulated over the decades, typically Worldline (formerly First Data SIPS / Atos Worldline), ConCardis, regional acquirers, plus the native SEPA SCT/SDD support via DMEE bank-format extracts for European operations. These work for simple invoice-payment scenarios but have several constraints at enterprise scale: most are tied to a single PSP / single MID, no Level III interchange enrichment, no surcharging where legal, dunning limited to ECC's standard dunning levels (no gateway-aware retry intelligence), customer portal payment surface limited to what's available through SAP Web Channel / SAP Customer Checkout / partner portals.
Payment Hub is the gateway- and processor-agnostic alternative: pick any of 19+ gateways behind one consistent integration. Existing merchant accounts, processors, and negotiated rates stay. The integration is designed to coexist during phased rollouts, legacy certified-PSP integrations can run in parallel during transition.
Does Level III interchange optimization work for SAP ECC customers?
Yes, and the use is enterprise-scale. SAP ECC enterprises in Wholesale Distribution, Industrial Manufacturing, Automotive, Aerospace &. Defense, Chemicals, Oil &. Gas, Utilities, High Tech, and B2B services typically have hundreds of millions to billions of dollars in annual B2B commercial-card volume that the legacy certified-PSP layer handles at non-qualified or partially-qualified interchange.
Payment Hub automatically pulls line-item data from SAP ECC's Sales Order line items (VBAP), Customer Invoice line items (VBRP), Production Order line records (AFKO / AFPO), and Project line records (PROJ / PRPS), through BAPI / RFC for traditional ECC integration plus OData / SAP Gateway where Enhancement Packages 7+ enable it, then packages the 20+ required L3 fields per gateway / card-brand spec. Tax data flows in cleanly through ECC's tax engine with country-specific localizations. Typical enterprise SAP ECC customer with $250M in annual B2B card volume recovers $1M–$3M annually. Larger globally-diversified ECC customers with $1B+ commercial-card volume recover $4M–$10M+/yr.
Does Payment Hub use SEPA SCT and SDD via DMEE bank-format extracts on SAP ECC?
Yes. SAP ECC's European localizations ship with native SEPA support, SEPA Credit Transfer (SCT) for outgoing payments and SEPA Direct Debit (SDD) for incoming receivables, with mandate management, XML bank-file generation via the DMEE (Data Medium Exchange Engine), and integration into the standard A/R Invoice / Incoming Payment / F-28 cash-application flows.
Payment Hub augments this for European SAP ECC customers: multi-bank SEPA SDD routing per Company Code / country, mandate management with proper consent capture and right-to-be-forgotten cascading from SAP ECC's standard data-protection framework, automatic mandate renewal flows, B2B vs CORE SEPA scheme selection per customer, return-handling and rejection automation via DMEE format-tree extensions, and bridging between SEPA SDD (for European receivables) and ACH (for North American receivables) on the same Customer master. SEPA SDD is often the highest-use payment method for European SAP ECC enterprises, typically 35–55% of European AR by value flows through SDD when properly automated.
Does Payment Hub work with SAP NetWeaver PI / PO middleware orchestration on SAP ECC?
Yes. SAP NetWeaver Process Integration (PI) and Process Orchestration (PO) are SAP's traditional middleware tier for SAP ECC, the orchestration layer for complex integration scenarios across SAP and non-SAP systems. Where customers run NetWeaver PI / PO as their integration backbone (common in larger ECC enterprises with established SAP integration practices), Payment Hub registers as another integration scenario alongside the existing iDoc / BAPI / RFC adapters.
Pre-built integration content templates speed deployment. For customers planning to migrate from NetWeaver PI / PO to SAP Integration Suite (the modern cloud middleware) as part of their broader SAP modernization, Payment Hub re-registers cleanly on the new middleware tier without configuration loss. The integration approach respects whatever middleware investment the enterprise has made.
Does Payment Hub support SAP ECC's database-agnostic deployment (Oracle, IBM DB2, SQL Server, SAP ASE, HANA)?
Yes. SAP ECC is database-agnostic, running on Oracle, IBM DB2, Microsoft SQL Server, SAP ASE (formerly Sybase), and on later versions also SAP HANA. This flexibility gave enterprises freedom to align ECC with their existing IT landscapes over the past two decades. Payment Hub's primary integration paths, BAPI / RFC, IDoc, SAP Gateway / OData, NetWeaver PI / PO, are database-agnostic. They operate on the application layer regardless of the underlying database.
For customers running ECC on SAP HANA (the typical pre-S/4HANA HANA deployment via the 'Suite on HANA' configuration), the OData services available via SAP Gateway provide the modern integration path with HANA-accelerated performance. Other database backends use the same BAPI / RFC / IDoc / NetWeaver PI paths with identical Payment Hub feature set. Database choice has no impact on the integration capabilities.
Does Payment Hub help bridge the move from SAP ECC to SAP S/4HANA?
Yes, Payment Hub is designed as a migration-bridging layer. Customers planning a 24-36 month ECC → S/4HANA migration project shouldn't have to wait for the migration to capture payment-modernization value. Payment Hub deploys on SAP ECC today through the published integration paths, captures L3 savings + SEPA SDD savings + dunning automation + customer-portal modernization immediately, and then carries forward through the eventual S/4HANA migration without re-implementation.
The migration team continues to focus on the SAP core (data harmonization, custom code adaptation, role redesign, process redesign). Payment Hub is a clean overlay that survives the cutover. For customers in earlier migration stages (still finalizing approach: brownfield vs greenfield vs selective data transition), Payment Hub doesn't constrain the choice, all three paths are supported on the destination S/4HANA system.
What's the implementation timeline for SAP ECC?
A typical Payment Hub + SAP ECC integration goes live in 48 hours once Clarity receives ECC test environment access (BAPI / RFC user, OData service activation if using Enhancement Package 7+, communication user with appropriate per-Company-Code authorizations provisioned, X.509 certificates configured if used, NetWeaver PI / PO scenarios registered if used as the middleware tier), gateway credentials, and your baseline routing configuration.
SAP ECC enterprise customers typically have decades of operational ECC experience, Payment Hub deploys substantially faster than any historical PSP-add-on rollout because it uses standard SAP integration paths rather than ABAP-side modifications. For multi-Company-Code SAP ECC enterprises (the typical large-customer deployment runs 25-500+ Company Codes), pilot with one Company Code / country in the first 48 hours, then add additional Company Codes in subsequent batches over 6–12 weeks. For customers in the middle of an ECC → S/4HANA migration project, Payment Hub deploys on the current ECC system. The configuration ports forward through the migration cutover.