SAP ECC (SAP ERP Central Component) is the on-premises predecessor to S/4HANA, running financials, procurement, manufacturing, and HR for a large installed base of enterprises that have not yet migrated to the cloud. External integrations reach ECC through NetWeaver Gateway (OData) or SAP PI/PO middleware.
Pull open and completed sales orders through the SAP Sales Order OData service (API_SALES_ORDER_SRV). Create new orders and update delivery dates or quantities from your product.
Read vendor master records including payment terms, bank details, and purchasing org assignments from the SAP Vendor service. Write back updated contact or address data from your supplier portal.
Pull General Ledger account balances and FI document postings via the SAP FI OData services. Askel handles SAP's fiscal-year and period structure so your analytics product sees correctly dated financial data.
Pull approved purchase orders, open goods receipt items, and three-way match status from the SAP MM module. Useful for AP automation products that need to validate invoices against POs.
Read material master records, plant stock levels, and storage location quantities. Askel normalizes SAP's plant and storage location hierarchy into a flat inventory view your product can display.
Pull active employees, org units, and position assignments from the SAP HCM OData services. Useful for workforce tools connecting to customers who have not yet moved to SuccessFactors.
Aldermoor Chemicals runs their procurement and manufacturing on SAP ECC and has selected your supplier portal product to give vendors visibility into open purchase orders and expected delivery schedules. Aldermoor's procurement team has asked suppliers to confirm delivery dates directly in the portal, which then writes back to ECC.
Aldermoor's SAP Basis team activates the Purchasing OData service (MM_PUR_PO_MAINT_V2_SRV) in SAP NetWeaver Gateway using transaction /IWFND/MAINT_SERVICE. They note the Gateway host URL, the SAP client number (e.g. 100), and create a dedicated user with Purchasing display and change authorizations.
Aldermoor's IT admin enters the Gateway host URL, SAP client number, username, and password into the Askel setup screen inside your supplier portal. Askel composes the Basic auth header and adds the sap-client header to every request, then confirms connectivity by fetching one open PO.
Askel reads the available OData entity sets and function imports from the activated services on Aldermoor's Gateway. Your CS team sees a mapping draft covering PO header and line item fields, delivery dates, vendor details, and goods receipt status within minutes.
Aldermoor uses an SAP user exit to populate a custom field with a preferred-carrier code. A CS rep maps this to the portal's carrier preference attribute and runs a dry-run against 100 open POs to confirm the data looks correct.
Suppliers log into the portal and see their open POs from ECC. When a supplier confirms a delivery date in the portal, Askel writes the confirmation back to the relevant PO in Aldermoor's ECC using the OData PATCH endpoint. Aldermoor's buyers see updated delivery commitments in ECC the same day.
The customer's SAP Basis team creates a dedicated user with the required ECC authorizations and activates the needed OData services in SAP NetWeaver Gateway. They provide the Gateway host URL, SAP client number, username, and password. Askel composes Basic auth and adds the sap-client header on every request. For customers routing through SAP PI/PO, the PI/PO endpoint URL is entered instead of the Gateway URL.
© 2025 Askel.ai. All rights reserved.