SAP ECC and Amazon Seller Central integration

What moves between them

The integration polls Amazon Seller Central financial events and settlement records on a schedule tied to your reconciliation cycle and maps them into SAP ECC purchase orders and cost allocations. Vendor invoices from Amazon settlements flow inbound to SAP ECC as BAPI_ACC_DOCUMENT_POST GL postings, allocated to cost centers and GL accounts matched against your master data. Orders and inventory data flow from Amazon into SAP ECC material and purchase order masters so cost allocation reflects actual marketplace activity. The flow is primarily inbound from Amazon to SAP ECC; SAP ECC vendor and PO masters are treated as the source of truth for reconciliation.

How ml-connector handles it

ml-connector maintains the on-premises RFC agent lifecycle on your behalf, accepting the RFC gateway host and port per customer and running BAPI and RFC_READ_TABLE calls through Basic Auth credentials. It refreshes Amazon OAuth2 tokens before expiry, detects the seller's region from configuration, and routes calls to the correct Selling Partner API endpoint. Financial events from Amazon Seller Central are read via polling on your settlement schedule and matched against SAP ECC purchase orders using vendor master data and invoice numbers to detect duplicates on retry. GL postings use the BAPI_ACC_DOCUMENT_POST reference document number to prevent duplicate posting if a retry occurs. The integration respects SAP ECC's 512-character RFC_READ_TABLE row width limit on classic versions and handles character encoding for non-ASCII vendor and item names. Amazon rate limits are respected with exponential backoff, and every record carries lineage from source to posting.

A real-world example

A mid-market distributor runs SAP ECC on-premises for procurement and finance, and sells through multiple Amazon marketplaces across North America and Europe. Before the integration, the finance team received Amazon settlement reports by email, manually exported vendor invoice totals into Excel, and re-entered the labor and inventory cost allocations into SAP ECC's GL by hand, delaying month-end close by three to five days and introducing keying errors. With SAP ECC and Amazon Seller Central connected, settlement events flow into SAP ECC automatically each night, allocated to the correct cost centers by region, and the invoice reconciliation step is eliminated. Month-end close starts with the AP and inventory accounts already reconciled to Amazon, and the manual re-keying step is gone.

What you can do

• •Post Amazon settlement events and vendor invoices into SAP ECC general ledger, allocated to the correct cost centers by seller and region.
• •Keep SAP ECC purchase orders aligned with Amazon order volumes and vendor invoice totals.
• •Map Amazon vendor masters to SAP ECC vendor masters so invoices post to the correct GL accounts.
• •Authenticate SAP ECC via RFC/BAPI Basic Auth with an on-premises agent, and Amazon via OAuth2 with region-aware endpoint routing.
• •Poll Amazon settlement data on a schedule tied to your reconciliation cycle, with duplicate detection via reference document numbers and a full audit trail on every posting.

Questions

How does ml-connector handle SAP ECC's requirement for an on-premises RFC agent?

ml-connector accepts the RFC gateway host and port from your SAP Basis team and manages the agent lifecycle on your behalf, running BAPI and RFC_READ_TABLE calls through Basic Auth credentials. The agent must already be installed on your network with SAP .NET Connector or Java Connector; ml-connector does not install or patch it.

Which direction does data move between SAP ECC and Amazon Seller Central?

The main flow is Amazon into SAP ECC. Settlement events, vendor invoices, and order data flow from Amazon Seller Central into SAP ECC purchase orders and GL accounts, while vendor and item masters in SAP ECC are treated as the reference for reconciliation. SAP ECC does not push procurement changes back to Amazon.

How does the integration handle Amazon's regional endpoints and OAuth2 token expiry?

ml-connector detects the seller's region from configuration and routes all calls to the correct regional Selling Partner API endpoint. It refreshes OAuth2 access tokens before expiry and retries calls that fail with a 401, so token rotation does not disrupt the sync. Every region - North America, Europe, and Far East - is supported.