From on-prem to public cloud
Our standard extensions for your SAP® ERP. For ECC and S/4HANA.
Optimize your customs, global trade, and logistics processes with AEB extensions for SAP. Without a costly implementation project. With very little IT effort.
From on-prem to public cloud
Our standard extensions for your SAP® ERP. For ECC or S/4HANA.
Optimize your customs, global trade, and logistics processes with AEB extensions for SAP. Without a costly implementation project. With very little IT effort.
Quickly find the right solution for your SAP ecosystem
The best solutions? Are our standard. AEB integrations for SAP automate your customs, global trade, and logistics processes - while freeing you from costly, time-consuming maintenance.
Different standard extensions are available depending on your ecosystem and IT strategy.
And best of all: You will only need a minimum of IT resources.
On average a maximum of 1 day.
Clean core extensions for SAP
Theoretically suitable for all system landscapes
Our clean core extensions consistently follow the current SAP product strategy: The extension logic is implemented outside the SAP core and connected via standardized interfaces and event-based processes,for example.
The SAP core remains completely "clean", extensions can be developed, deployed, and scaled independently, and SAP upgrades are not affected.
This option is suitable for organizations with a high focus on standardization. Typically, these are companies that
- consistently rely on the SAP standard and the SAP Cloud ERP strategy (public cloud).
- deliberately want to keep the extension logic outside the SAP core.
- generally prioritize maximum upgrade stability and decoupling from extensions.
The implementation effort is divided into the following areas and depends on the support you require from us.
Our recommendation:
What you should do yourself:
- Your IT needs to enable the designated standard interfaces and events in S/4HANA and on the BTP and connect the system to the AEB Cloud service via event mesh.
- Your specialist departments define the relevant processes that are to be supported by the add-on.
How we support you:
- AEB provides support with best practices, comprehensive documentation, and assistance with the complete implementation.
Clean core extensions for SAP
Theoretically suitable for all system landscapes
Our clean core extensions consistently follow the current SAP product strategy: The extension logic is implemented outside the SAP core and connected via standardized interfaces and event-based processes,for example.
The SAP core remains completely "clean", extensions can be developed, deployed, and scaled independently, and SAP upgrades are not affected.
This option is suitable for organizations with a high focus on standardization. Typically, these are companies that
- consistently rely on the SAP standard and the SAP Cloud ERP strategy (public cloud).
- deliberately want to keep the extension logic outside the SAP core.
- generally prioritize maximum upgrade stability and decoupling from extensions.
The implementation effort is divided into the following areas and depends on the support you require from us.
Our recommendation:
What you should do yourself:
- Your IT needs to enable the designated standard interfaces and events in S/4HANA and on the BTP and connect the system to the AEB Cloud service.
- Your specialist departments define the relevant processes that are to be supported by the add-on.
How we support you:
- AEB provides support with best practices, comprehensive documentation, and assistance with the complete implementation.
Add-ons for SAP
Suitable for SAP ECC, SAP S/4HANA on-premise and private edition
Our add-ons add AEB-specific functions to processes directly in the SAP system. They are designed to retain the system's capability for upgrades and maintenance. The add-ons are installed via transport orders without modifying the standard and use different technologies (messages, user exits, BAdIs,...) to call the AEB functions.
Add-ons are particularly useful where SAP needs to be adapted more closely to company-specific requirements. Typically, this option is chosen by companies that:
- need to map individual or industry-specific processes directly in the SAP system
- pursue an on-premise strategy with greater system customization
- want to benefit from the (still possible) advantages of very deep integration in the core, but still want to avoid complete individual core development
Implementation is carried out using the standard SAP procedure and is divided into clearly defined areas of responsibility. The actual effort required depends on the ecosystem and scope of features.
Our recommendation:
What you should do yourself:
- You IT needs to install the add-on using the standard SAP procedure (e.g. SAINT/SPAM or transport) and is responsible for setting up the technical basics.
- Your specialist departments define the relevant processes and material data that are to be supported by the add-on.
How we support you:
- AEB provides support with best practices, comprehensive documentation, and a clear implementation structure.
- AEB supports you in customizing, mapping, and testing and is available to answer your subject-matter and technical questions.
Add-ons for SAP
Suitable for SAP ECC, SAP S/4HANA on-premise and private edition
Our add-ons add AEB-specific functions to processes directly in the SAP system. They are designed to retain the system's capability for upgrades and maintenance. The add-ons are installed via transport orders without modifying the standard and use different technologies (messages, user exits, BAdIs,...) to call the AEB functions.
Add-ons are particularly useful where SAP needs to be adapted more closely to company-specific requirements. Typically, this option is chosen by companies that:
- need to map individual or industry-specific processes directly in the SAP system
- pursue an on-premise strategy with greater system customization
- want to benefit from the (still possible) advantages of very deep integration in the core, but still want to avoid complete individual core development
Implementation is carried out using the standard SAP procedure and is divided into clearly defined areas of responsibility. The actual effort required depends on the ecosystem and scope of features.
Our recommendation:
What you should do yourself:
- You IT needs to install the add-on using the standard SAP procedure (e.g. SAINT/SPAM or transport) and is responsible for setting up the technical basics.
- Your specialist departments define the relevant processes and material data that are to be supported by the add-on.
How we support you:
- AEB provides support with best practices, comprehensive documentation, and a clear implementation structure.
- AEB supports you in customizing, mapping, and testing and is available to answer your subject-matter and technical questions.
Contact our expert
Markus Strohm
Team Leader SAP Sales and Projects at AEB
Discuss your request with our SAP enhancements expert without obligation.