How Asprova APS connects to SAP ECC
Partner interface (Aimtec)
Aimtec delivers Asprova in Europe with an interface to SAP. Ask Aimtec for the current interface scope, supported SAP releases and what it exchanges.
Flat file or OLE DB
Asprova is commonly integrated by file exchange or database access. For SAP, files or staging tables are typically produced by ABAP extracts and read back by an import job. Treat this as general practice and confirm the method with Aimtec.
What data moves
| From | To | Data | When |
|---|---|---|---|
| SAP ECC | Asprova | Demand, planned and production orders, BOMs, routings, work centres | Scheduled export or on demand |
| SAP ECC | Asprova | Stock and open purchase orders | Before each scheduling run |
| Asprova | SAP ECC | Start and finish dates, sequence, work centre assignment | Schedule released by planner |
| SAP ECC | Asprova | Order confirmations and actual progress | Shop floor confirmation posted |
Setting it up
- 1Define the planning splitDecide what MRP in SAP still decides and what Asprova takes over: sequencing, finite capacity and resource assignment.
- 2Model resources and constraintsBuild work centres, calendars, setup matrices, tooling and labour constraints in Asprova.
- 3Build the interfaceSet up the extracts and imports for orders, BOMs and routings, and the write-back of dates.
- 4Align master dataCheck routings, standard times and lead times. A schedule is only as good as these numbers.
- 5Run in shadow modeSchedule in parallel with current practice and compare adherence before releasing to the floor.
- 6Establish a release cycleAgree when the planner publishes the schedule and how late changes are handled.
What usually breaks
- !Routing times in SAP that are optimistic, producing schedules the shop cannot hit.
- !Frozen horizon unclear, so SAP and Asprova move the same order differently.
- !Order changes in SAP arriving after the schedule has been released.
- !Unit of measure or work centre code mismatches between the two systems.
- !Assuming S/4HANA certification exists without checking the current status.
A private AI layer across both systems
Late order explanations
Explain why an order slipped, using schedule versions, material availability and confirmations from both systems.
Master data sanity checks
Compare routing standards in SAP to confirmed actual times and suggest where standards look off, for a planner to review.
Scenario questions
Let planners ask what happens if a machine is down, answered by reading the schedule and drafting options. Any change is approved by a person.
When something else fits better
- SAP's own planning tools such as PP/DS may be enough if you already license them and your constraints are modest.
- A well-maintained spreadsheet or visual board can handle small, stable shops.
- Other APS products with SAP connectors are worth comparing for your process type.
Frequently asked questions
Does Asprova replace SAP MRP?
Generally no. The source describes it as a complement to SAP. MRP still drives material requirements, while Asprova handles finite-capacity scheduling and sequencing. Decide the split in writing at the start of the project.
How does it connect to SAP?
The source mentions a partner interface from Aimtec and flat file or OLE DB. Ask Aimtec for the current interface scope. In practice you will build and monitor extracts and an import job.
Does it support S/4HANA?
Aimtec says certification for an S/4HANA private cloud interface is in progress. That is a statement from the source, not a guarantee, so confirm the current status and supported releases before you decide.
Where can AI help a planner?
As a read-only assistant explaining why orders are late and checking routing data across SAP and Asprova. Run it on premises if schedules and costs are sensitive, and keep release decisions with the planner.
Pairing documented at insights.aimtecglobal.com/en/asprova-aps-a-proven-conductor-in-a-new-tuxedo-plan . Asprova APS is a product of Asprova (delivered with Aimtec in Europe); Netray is independent and not affiliated with either vendor.