Oracle E-Business Suite and Walmart Marketplace integration

What moves between them

Orders flow from Walmart Marketplace into Oracle E-Business Suite. ml-connector polls the Walmart Marketplace orders endpoint on a schedule you set and reads orders placed in the last 180 days. Each order becomes a PO_HEADERS and PO_LINES record in EBS, written to the open interface tables along with vendor and GL account mappings. The concurrent program imports the interface records into the base tables and validates GL code combinations. Returns and refund requests poll similarly but write to AP interface tables when vendor credit memos are needed. Inventory and pricing from EBS do not flow back to Walmart in this direction.

How ml-connector handles it

ml-connector manages two separate credential sets. On the Walmart side, it refreshes the OAuth 2.0 access token every 15 minutes (before expiry) and includes the WM_SEC.ACCESS_TOKEN header and required correlation and service-name headers on every request. On the EBS side, it accepts the customer's hostname, port, and context headers (responsibility, organization, language), logs in with Basic auth to get a session token, and re-authenticates when the token expires. Orders from Walmart are mapped to an existing EBS vendor at setup time. Each order line maps to an EBS GL code combination using category fields and optional item lookups. Because EBS write operations are asynchronous (the concurrent program takes time to validate and post), ml-connector tracks the import status via the interface table and can replay failed orders if the import fails. Walmart orders older than 180 days are not available through the API, so polling always respects that window.

A real-world example

A mid-sized national retailer sells through Walmart Marketplace alongside their own direct channels. Before the integration, store operations exported orders from Walmart twice daily and entered them into their EBS procurement system by hand, using a spreadsheet to map each order to the correct vendor and cost center. The finance team had no visibility until month end when they reconciled payables against the manual entry list. With Oracle E-Business Suite and Walmart Marketplace connected, each order lands automatically in the EBS interface tables within minutes of placement on Walmart. Finance runs the import concurrent program on a schedule, GL accounts post automatically, and the Walmart channel becomes as visible and auditable as the direct channel.

What you can do

• •Sync Walmart Marketplace orders into Oracle E-Business Suite as purchase orders and interface records, mapped to existing vendors and GL accounts.
• •Refresh OAuth 2.0 tokens automatically before expiry and present the required WM_SEC.ACCESS_TOKEN header on every Walmart API call.
• •Authenticate to EBS with HTTP Basic credentials or session tokens and include application context headers (responsibility, organization, language) on all ISG requests.
• •Map Walmart order categories and SKUs to EBS GL code combinations and vendor accounts at setup, and apply the mapping to every incoming order.
• •Poll Walmart and EBS on a schedule you control, with full audit trail and replay capability if an order import fails in the EBS concurrent program.

Questions

How does ml-connector handle the 15-minute expiry of Walmart OAuth 2.0 tokens?

ml-connector refreshes the token every 15 minutes (before it expires) by exchanging the Client ID and Client Secret at the POST https://marketplace.walmartapis.com/v3/token endpoint. The new token is then used on the next API call. If a call returns a 401, the connector immediately requests a fresh token and retries the request.

What happens if an order fails to import into EBS after being written to the interface table?

ml-connector tracks the status of each order in the EBS interface tables by monitoring the concurrent program import log. If an import fails (for example, because a GL code combination does not exist), the order record is flagged and can be replayed after the underlying issue is fixed, without re-polling Walmart.

Why does ml-connector need application context headers for EBS, and how are they set?

EBS requires ctx_responsibility, ctx_respapplication, ctx_securitygroup, ctx_orgid, and other application context headers to route each API call to the correct ledger, company, and user role. These headers are configured at setup time based on your EBS environment and included on every ISG request. Incorrect headers will cause the API to reject the call or return incomplete data.