SAP practice
SAP transformation, implementation and specialist consulting
We help organizations move from ECC to S/4HANA, implement and extend SAP, and staff the architects, functional consultants, ABAP developers and Basis engineers a program needs. This page goes module by module so you can see what we do in each.
Where SAP programs get stuck
Most SAP delays are not caused by SAP. They come from decisions that were made late: how much history to migrate, which custom code to keep, who owns the master data, which interfaces are still alive. The software is the easy part to schedule.
We start with those decisions. On a conversion, that means the simplification items that apply to your system, a custom-code review driven by usage data, a Business Partner clean-up that starts months before cutover, and an interface inventory with an owner against every line. On a new implementation, it means fit-to-standard workshops that end with a written decision for each deviation.
The maintenance dates add pressure. SAP has published that mainstream maintenance for ECC 6.0 ends at the close of 2027, with extended maintenance at a premium through 2030 and a separate private-edition transition option beyond that. The terms have conditions, so confirm the current position with your SAP account team before you plan around any date.
What we deliver on SAP
-
Greenfield
S/4HANA implementation
New implementation on SAP Activate: fit-to-standard workshops, a clean-core design, configuration, extension, data migration, testing and cutover.
-
Brownfield
ECC to S/4HANA migration
System conversion or selective data transition, run from readiness check to hypercare. Includes the custom-code and data work that decides the timeline.
-
Assess
System assessment
A written look at your landscape: usage, custom code, interfaces, data quality and licenses, ending in a recommended path and a risk list.
-
Improve
Process optimization
Finance close, order to cash, procure to pay or warehouse flows reviewed against standard functions, with changes ranked by effort and benefit.
-
Experience
Fiori implementation
Role-to-app mapping, launchpad and spaces, custom Fiori elements and freestyle apps, and front-end server setup.
-
Extend
SAP BTP development
Side-by-side extensions with ABAP Cloud and CAP, connectivity, identity and delivery pipelines.
-
Integrate
Integration Suite and Cloud Integration
Interface inventory, integration flows, API management, EDI and event-driven patterns.
-
Specialize
Specialist modules
EWM, TM, IBP, QM, PM, SuccessFactors, Ariba, Analytics Cloud and GRC, each with its own consultants and test approach.
-
Platform
Basis, security and ABAP
Landscape build, conversions with SUM/DMO, role design, performance tuning and custom development.
-
Data
SAP data migration
Business Partner conversion, Migration Cockpit loads, cleansing and a reconciliation for every object.
-
Run
Application management
Production support, enhancements and release management after go-live, with defined response targets.
-
Staff
SAP staffing
Contract, direct hire and dedicated teams, with technical screening before any resume reaches you.
SAP modules, one by one
Choose an area to see what it covers, what a consultant does in it on a real project, where projects tend to go wrong, and which roles we staff. This is the working detail behind the service list above.
Finance
SAP S/4HANA Finance is built around the Universal Journal. Most design decisions follow from it: ledgers, account structure, controlling objects and the close.
FI-GL General ledger and the Universal Journal The single line-item table ACDOCA, which now holds financial, controlling, asset and Material Ledger postings in one pl…
- What it covers
- The single line-item table
ACDOCA, which now holds financial, controlling, asset and Material Ledger postings in one place. Leading and additional ledgers, document splitting, currency types, chart of accounts and fiscal-year variants. - What we do on projects
- Decide the ledger approach (a leading ledger plus additional ledgers for IFRS or local GAAP), redesign the chart of accounts and document-splitting characteristics, set account determination and posting periods, and reconcile migrated balances line by line, not just in total.
- Where projects go wrong
- Carrying the ECC chart of accounts forward untouched, then finding that secondary cost elements need redesign. Turning on document splitting late. Reconciling only at balance level.
- Roles we staff
- SAP FICO consultant, S/4HANA finance functional lead, finance data migration analyst
FI-AP Accounts payable Vendors as Business Partners, invoice processing (logistics invoice verification in MM and direct FI invoices), payment…
- What it covers
- Vendors as Business Partners, invoice processing (logistics invoice verification in MM and direct FI invoices), payment runs, payment media files, withholding tax, vendor open items and their reconciliation to the ledger.
- What we do on projects
- Configure payment methods, the payment run (
F110) and house-bank determination. Build duplicate-invoice checks and tolerances. Agree bank file formats and test them with the bank. Connect Ariba or an invoice-capture tool when one is in scope. - Where projects go wrong
- Vendor data that fails the Business Partner conversion because customer and vendor records were never cleaned. Payment files first tested in production.
- Roles we staff
- SAP FICO consultant (AP), payments and banking specialist
FI-AR Accounts receivable, credit and collections Customer open items, dunning, incoming payments and lockbox, SAP Credit Management, dispute management and collections…
- What it covers
- Customer open items, dunning, incoming payments and lockbox, SAP Credit Management, dispute management and collections, and the hand-off from SD billing.
- What we do on projects
- Move credit rules from the old SD credit functions to SAP Credit Management, set up dunning procedures and automatic clearing, configure bank statement processing, and prove that billing documents land in the receivables ledger with the right accounts.
- Where projects go wrong
- Classic credit-management transactions that no longer exist in S/4HANA. Bank statement rules that depend on reference fields nobody documented.
- Roles we staff
- SAP FICO consultant (AR), SAP SD consultant for billing integration
FI-AA Asset accounting Asset master data, acquisitions, retirements, depreciation areas mapped to ledgers, parallel valuation, assets under co…
- What it covers
- Asset master data, acquisitions, retirements, depreciation areas mapped to ledgers, parallel valuation, assets under construction and their settlement, and the year-end depreciation run.
- What we do on projects
- Redesign depreciation areas for the new asset accounting, which posts to the Universal Journal. Migrate asset balances and transactions with a reconciliation back to the ledger, and rehearse the year-end run before it matters.
- Where projects go wrong
- Assuming ECC asset configuration converts untouched. A go-live in the middle of the year adds catch-up depreciation work that is easy to underestimate.
- Roles we staff
- SAP FICO consultant (asset accounting)
CO-OM Cost centers, internal orders and profit centers Cost-center and internal-order accounting, allocations (assessment and distribution), profit centers and segments. Cont…
- What it covers
- Cost-center and internal-order accounting, allocations (assessment and distribution), profit centers and segments. Controlling postings now sit in the same journal as financial postings.
- What we do on projects
- Rebuild the organizational structure (controlling area, operating concern, profit-center hierarchy), recreate allocation cycles, and align cost objects so finance no longer reconciles FI to CO by hand.
- Where projects go wrong
- Designing around the old reconciliation ledger, which no longer exists. Copying allocation cycles across without checking they still behave the same.
- Roles we staff
- SAP CO consultant, SAP FICO consultant
CO-PC / ML Product costing and the Material Ledger Standard cost estimates, cost-component split, production variances, actual costing, and multiple-currency valuation. T…
- What it covers
- Standard cost estimates, cost-component split, production variances, actual costing, and multiple-currency valuation. The Material Ledger is always active in S/4HANA; actual costing is a choice.
- What we do on projects
- Set up costing runs and variance categories, decide whether the business needs actual costing, and validate inventory valuation against the ledger before cutover.
- Where projects go wrong
- Treating Material Ledger activation as a switch rather than a data migration. Costing runs that were never timed on production volumes.
- Roles we staff
- SAP CO consultant (product costing), SAP MM consultant for valuation
CO-PA Profitability analysis (margin analysis) Account-based profitability inside the Universal Journal, costing-based CO-PA where value fields are still needed, and…
- What it covers
- Account-based profitability inside the Universal Journal, costing-based CO-PA where value fields are still needed, and the flow from billing and cost of goods sold.
- What we do on projects
- Map existing characteristics and value fields to the new model, decide between account-based, costing-based or both, and rebuild the profitability reports and Fiori analytics.
- Where projects go wrong
- Expecting costing-based reports to match account-based numbers exactly. They differ in timing and structure, so finance has to agree on the definitions early.
- Roles we staff
- SAP CO consultant (CO-PA), reporting analyst
CLOSE Financial close Period-end tasks and their order: foreign-currency valuation, GR/IR and accrual clearing, allocations, depreciation, in…
- What it covers
- Period-end tasks and their order: foreign-currency valuation, GR/IR and accrual clearing, allocations, depreciation, intercompany reconciliation and sign-off. Advanced Financial Closing for scheduling and tracking.
- What we do on projects
- Write down the close calendar that finance really follows, configure the period-end programs and task lists, set up intercompany matching, and run two or three parallel closes during testing so the numbers are proven before go-live.
- Where projects go wrong
- The first real close happening in production. Close steps that relied on custom reports nobody retested.
- Roles we staff
- SAP FICO consultant, finance process lead
REPORTING Financial reporting and group reporting Fiori apps and embedded analytics on CDS views, SAP Analytics Cloud, group reporting and consolidation, and statutory o…
- What it covers
- Fiori apps and embedded analytics on CDS views, SAP Analytics Cloud, group reporting and consolidation, and statutory outputs such as e-documents.
- What we do on projects
- List the reports finance actually opens, replace them with standard apps where they fit, build CDS views and Fiori tiles for the remainder, and set up group reporting data flows.
- Where projects go wrong
- Rebuilding every ECC report one for one when most were never used. Custom reads against tables that no longer hold the data.
- Roles we staff
- SAP analytics consultant, S/4HANA finance functional lead
Supply chain
Procurement, inventory, sales, manufacturing, warehouse, transport, planning, quality and maintenance. Several of these (EWM, TM, IBP) are products with their own design and test effort, not just configuration.
MM-PUR Procurement and purchasing Requisitions, purchase orders, contracts, scheduling agreements, source lists and info records, release strategies, and…
- What it covers
- Requisitions, purchase orders, contracts, scheduling agreements, source lists and info records, release strategies, and the link to Ariba and supplier invoice management.
- What we do on projects
- Configure document types, release strategies and account assignment. Design source-of-supply logic. Integrate with Ariba for sourcing or guided buying when in scope. Migrate open purchase orders with the correct goods-receipt status.
- Where projects go wrong
- Release strategies copied across without testing who approves what. Open purchase orders whose quantities do not match goods receipts.
- Roles we staff
- SAP MM consultant, SAP Ariba consultant
MM-IM Inventory management and valuation Goods movements and the simplified material document (MATDOC), batch and serial numbers, valuation classes, physical in…
- What it covers
- Goods movements and the simplified material document (
MATDOC), batch and serial numbers, valuation classes, physical inventory, stock transfers and consignment. - What we do on projects
- Check movement types and valuation settings, migrate stock by plant, storage location and batch, and reconcile stock value to the ledger before go-live. Run the physical inventory process end to end in test.
- Where projects go wrong
- Stock migrated by quantity only, with value and batch data fixed later. Custom code that reads the old material document tables directly.
- Roles we staff
- SAP MM consultant, SAP WM/EWM consultant
MRP Material requirements planning MRP Live (MD01N) running on the HANA database, planning strategies, lot sizing, planned orders, MRP areas, and the opti…
- What it covers
- MRP Live (
MD01N) running on the HANA database, planning strategies, lot sizing, planned orders, MRP areas, and the optional 40-character material number. - What we do on projects
- Move to MRP Live, tune planning parameters, and compare planning results with the old system on a copy of production data. Extend interfaces and labels that assume 18-character material numbers.
- Where projects go wrong
- Interfaces hard-coded to 18 characters. Planning results that shift because default handling changed.
- Roles we staff
- SAP MM or PP consultant, supply planner
SD Sales and distribution (order to cash) Inquiry to billing: sales orders, pricing with the condition technique, availability checks including advanced ATP, del…
- What it covers
- Inquiry to billing: sales orders, pricing with the condition technique, availability checks including advanced ATP, deliveries, billing, output management, rebates and settlement management.
- What we do on projects
- Design pricing procedures, copy controls and output determination. Move rebate processing to settlement management. Test billing-to-FI account determination. Rebuild EDI and portal order interfaces.
- Where projects go wrong
- Pricing procedures with decade-old custom routines. Output determination built on the older NACE conditions that needs rework for the new output management.
- Roles we staff
- SAP SD consultant, EDI analyst
PP Production planning (discrete and repetitive) Bills of material, routings and work centers, production orders, capacity planning, Kanban, repetitive manufacturing, s…
- What it covers
- Bills of material, routings and work centers, production orders, capacity planning, Kanban, repetitive manufacturing, shop-floor confirmations and production variances.
- What we do on projects
- Clean BOM and routing data before migration, configure order types and confirmations, connect to shop-floor or MES systems, and test backflushing and costing from order release to settlement.
- Where projects go wrong
- Obsolete BOMs and routings carried across. Shop-floor interface timing under real load.
- Roles we staff
- SAP PP consultant, manufacturing process lead
PP-PI Production planning for process industries Master recipes, process orders, batch management with classification, process messages, and the documentation that regu…
- What it covers
- Master recipes, process orders, batch management with classification, process messages, and the documentation that regulated plants need.
- What we do on projects
- Rebuild master recipes and resources, configure process order confirmation, set batch derivation and shelf-life rules, and support validation documentation where the plant is regulated.
- Where projects go wrong
- Batch and classification data underestimated in the migration plan. Validation evidence treated as an afterthought.
- Roles we staff
- SAP PP-PI consultant, validation lead
EWM Extended Warehouse Management Warehouse structure (storage types, sections, bins), putaway and picking strategies, wave management, handling units, R…
- What it covers
- Warehouse structure (storage types, sections, bins), putaway and picking strategies, wave management, handling units, RF and mobile tasks, labor, slotting, yard management and material-flow systems. Embedded in S/4HANA or decentralized.
- What we do on projects
- Derive the structure from the physical layout, configure strategies and warehouse-order creation rules, set up delivery interfaces with the ERP, build RF screens, and run volume tests against the real peak day.
- Where projects go wrong
- Over-engineered strategies. RF devices and label printers left until the end. Message volume between ERP and EWM never tested at peak.
- Roles we staff
- SAP EWM consultant, EWM technical lead (ABAP), RF specialist
TM Transportation Management Freight units and freight orders, carrier selection, planning and optimization, charge calculation, freight settlement…
- What it covers
- Freight units and freight orders, carrier selection, planning and optimization, charge calculation, freight settlement, and carrier collaboration.
- What we do on projects
- Design planning profiles and the hand-off from sales and purchase deliveries, configure charge management and settlement, and connect carriers through EDI or APIs.
- Where projects go wrong
- Master data (locations, lanes, rate tables) underestimated. Trying to optimize before the basic shipping flow is stable.
- Roles we staff
- SAP TM consultant, logistics analyst
IBP Integrated Business Planning Cloud supply-chain planning: demand planning and sensing, sales and operations planning, supply planning, inventory opt…
- What it covers
- Cloud supply-chain planning: demand planning and sensing, sales and operations planning, supply planning, inventory optimization, and the Excel planning interface.
- What we do on projects
- Model the planning area, design key figures and time profiles, build the data integration with S/4HANA, and train planners in the Excel add-in.
- Where projects go wrong
- Poor sales history feeding the statistical forecast. Planning-area design changed after data has been loaded.
- Roles we staff
- SAP IBP consultant, demand planner
QM Quality management Inspection plans, inspection lots, usage decisions, quality notifications, certificates and sampling procedures, linked…
- What it covers
- Inspection plans, inspection lots, usage decisions, quality notifications, certificates and sampling procedures, linked to goods receipt, production and delivery.
- What we do on projects
- Configure inspection types and sampling schemes, migrate inspection plans with their master inspection characteristics, set certificate profiles, and connect lab or measurement equipment.
- Where projects go wrong
- Inspection plans moved without the catalogs they depend on.
- Roles we staff
- SAP QM consultant, quality systems analyst
PM / EAM Plant maintenance and asset management Functional locations, equipment, notifications, maintenance orders, maintenance plans, task lists, and costing of maint…
- What it covers
- Functional locations, equipment, notifications, maintenance orders, maintenance plans, task lists, and costing of maintenance work.
- What we do on projects
- Rebuild the technical-object hierarchy, migrate equipment history, configure order types and work clearance, and integrate mobile maintenance apps.
- Where projects go wrong
- A technical-object hierarchy nobody trusts. Maintenance plans that all come due on the day of go-live.
- Roles we staff
- SAP PM consultant, reliability engineer liaison
Integration
Every SAP program has interfaces that were built once and never documented. This group covers the classic mechanisms and the newer ones, and how we choose between them.
IDOC / ALE IDocs and ALE Message types and basic types such as ORDERS05, DESADV and INVOIC02, partner profiles, ports, process codes, and status…
- What it covers
- Message types and basic types such as
ORDERS05,DESADVandINVOIC02, partner profiles, ports, process codes, and status monitoring (WE02,WE05,BD87) with reprocessing. - What we do on projects
- List every inbound and outbound IDoc, rebuild partner profiles and ports for the new system, retest with each trading partner, and set up monitoring so a failed IDoc raises an alert.
- Where projects go wrong
- Partner profiles copied with the wrong system IDs. No alerting, so failed IDocs sit unnoticed for days.
- Roles we staff
- SAP integration consultant, EDI analyst
RFC / BAPI RFC and BAPI interfaces Synchronous, asynchronous, transactional and queued RFC, SM59 destinations, and BAPIs such as BAPI_PO_CREATE1 and BAPI_…
- What it covers
- Synchronous, asynchronous, transactional and queued RFC,
SM59destinations, and BAPIs such asBAPI_PO_CREATE1andBAPI_SALESORDER_CREATEFROMDAT2, including commit handling. - What we do on projects
- Find every RFC destination and BAPI caller, replace function modules removed in S/4HANA, and add authorization checks and error handling to each call.
- Where projects go wrong
- Callers that depend on removed tables or function modules. Calls that look successful but never commit.
- Roles we staff
- SAP integration consultant, SAP ABAP developer
API OData, REST and SOAP services OData V2 through SAP Gateway, OData V4 from the ABAP RESTful Application Programming Model, SOAP services managed in SO…
- What it covers
- OData V2 through SAP Gateway, OData V4 from the ABAP RESTful Application Programming Model, SOAP services managed in
SOAMANAGER, and ABAP calls to external REST APIs. - What we do on projects
- Agree the API contract first, expose released APIs rather than internal tables, secure endpoints with OAuth or certificates, version them, and document them in an API portal.
- Where projects go wrong
- Exposing internal CDS views straight to outside consumers. No versioning and no rate limits.
- Roles we staff
- SAP integration consultant, SAP BTP developer
INT-SUITE SAP Integration Suite Cloud Integration (integration flows), API Management, Open Connectors, Integration Advisor and Trading Partner Managem…
- What it covers
- Cloud Integration (integration flows), API Management, Open Connectors, Integration Advisor and Trading Partner Management, event brokering, and monitoring.
- What we do on projects
- Move interfaces from older SAP middleware where they are in scope, build reusable flows and one error-handling pattern, apply API policies, and design transport and CI/CD for integration content.
- Where projects go wrong
- Rebuilding every old scenario one for one instead of retiring the dead ones. No error-handling standard, so every flow handles failure differently.
- Roles we staff
- SAP Integration Suite developer, integration architect
EVENTS Event-driven integration Business events from S/4HANA, event brokers, publish-subscribe patterns, asynchronous processing, idempotency and repla…
- What it covers
- Business events from S/4HANA, event brokers, publish-subscribe patterns, asynchronous processing, idempotency and replay.
- What we do on projects
- Choose events or APIs for each integration, define event schemas and topics, handle duplicates and ordering, and monitor consumers.
- Where projects go wrong
- Events used where a plain API call would do. Consumers that break on duplicate messages.
- Roles we staff
- Integration architect, SAP BTP developer
B2B / EDI EDI and trading partners X12 and EDIFACT messages (for example 850, 855, 856, 810, 997) mapped to IDocs or APIs, partner onboarding, acknowledge…
- What it covers
- X12 and EDIFACT messages (for example 850, 855, 856, 810, 997) mapped to IDocs or APIs, partner onboarding, acknowledgements, and AS2 or VAN connectivity.
- What we do on projects
- Inventory trading partners and maps, rebuild connectivity for the new system, run partner test cycles, and set cutover timing so partners are not left without a connection.
- Where projects go wrong
- Partners given too little notice. Acknowledgement handling nobody owns.
- Roles we staff
- EDI analyst, SAP integration consultant
Technical
Custom code, user interface, extension strategy, the platform underneath, security and performance. The decisions here set how painful the next upgrade will be.
ABAP ABAP and custom code Classic and object-oriented ABAP, ABAP Cloud (development limited to released APIs), ABAP Unit, enhancements and BAdIs…
- What it covers
- Classic and object-oriented ABAP, ABAP Cloud (development limited to released APIs), ABAP Unit, enhancements and BAdIs, and the custom code lifecycle.
- What we do on projects
- Review custom code with the ABAP Test Cockpit (ATC) and the S/4HANA readiness checks, use usage data (the ABAP Call Monitor,
SCMON, and usage logging) to find code nobody runs, delete it, fix what breaks, and write new code in the clean-core style: released APIs and BAdIs, no modifications. - Where projects go wrong
- Fixing every finding, including code no user has called in two years. Modifications that make each upgrade harder than the last.
- Roles we staff
- SAP ABAP developer, ABAP lead, code-remediation specialist
CDS CDS views and the virtual data model Core Data Services view entities, associations, annotations, access controls (DCL), transactional and analytical views…
- What it covers
- Core Data Services view entities, associations, annotations, access controls (DCL), transactional and analytical views, and the released virtual data model views from SAP.
- What we do on projects
- Model reusable views over released VDM views, add access controls, and push calculation to the database instead of looping in ABAP.
- Where projects go wrong
- Views that join too many tables to tune. Authorization added after the first security review.
- Roles we staff
- SAP ABAP developer (CDS/RAP), analytics developer
RAP ABAP RESTful Application Programming Model Business objects with behavior definitions, managed and unmanaged implementations, draft handling, determinations and v…
- What it covers
- Business objects with behavior definitions, managed and unmanaged implementations, draft handling, determinations and validations, OData V4 service bindings, and Fiori elements UIs.
- What we do on projects
- Build custom business objects and extensions the standard way so Fiori elements generates the UI, write behavior tests, and keep the model portable between on-premise and BTP.
- Where projects go wrong
- Unmanaged implementations where managed would do. Draft enabled without thinking through locking.
- Roles we staff
- SAP ABAP developer (RAP), SAP BTP developer
FIORI Fiori and SAPUI5 Fiori launchpad and spaces, Fiori elements, freestyle SAPUI5 apps, role-based catalogs and groups, app configuration an…
- What it covers
- Fiori launchpad and spaces, Fiori elements, freestyle SAPUI5 apps, role-based catalogs and groups, app configuration and theming.
- What we do on projects
- Map roles to standard Fiori apps, configure launchpad content and spaces, build freestyle apps only where standard apps cannot cover the process, and set up the front-end server and caching.
- Where projects go wrong
- Treating the SAP GUI as the main interface and Fiori as an extra. Tiles copied from old role groups.
- Roles we staff
- SAP Fiori/UI5 developer, SAP security consultant (catalogs)
BTP SAP BTP extensions The ABAP environment for side-by-side development, the Cloud Application Programming Model (CAP), SAP Build, connectivi…
- What it covers
- The ABAP environment for side-by-side development, the Cloud Application Programming Model (CAP), SAP Build, connectivity through Cloud Connector and destinations, and identity services.
- What we do on projects
- Decide what stays in the core, what is a key-user extension and what is a side-by-side extension, then set up subaccounts, connectivity and CI/CD for the extensions.
- Where projects go wrong
- Moving every custom object to BTP, which just relocates the mess. Nobody owning the subaccounts.
- Roles we staff
- SAP BTP developer, BTP architect
BASIS Basis and platform operations System landscape, HANA administration, kernel and support-package maintenance, transport management, system copies, mon…
- What it covers
- System landscape, HANA administration, kernel and support-package maintenance, transport management, system copies, monitoring (Cloud ALM or Solution Manager), backup and recovery.
- What we do on projects
- Size and build the S/4HANA landscape, run SUM/DMO conversions, define the transport strategy, set up monitoring, and test disaster recovery.
- Where projects go wrong
- Sizing taken from the ECC database size without allowing for HANA compression. The first conversion rehearsal being the first time anyone times the downtime.
- Roles we staff
- SAP Basis administrator, HANA DBA, cloud infrastructure engineer
AUTH Authorization design Role design with PFCG, authorization defaults (SU24), Fiori catalog and group alignment, segregation of duties, firefig…
- What it covers
- Role design with
PFCG, authorization defaults (SU24), Fiori catalog and group alignment, segregation of duties, firefighter access, and user lifecycle. - What we do on projects
- Rebuild roles for S/4HANA transactions and Fiori apps, clean up
SU24, test with real users in each role, and wire segregation-of-duties rules into GRC. - Where projects go wrong
- Copying ECC roles and adding broad access to get past test failures. Authorization gaps first found in user acceptance testing.
- Roles we staff
- SAP security consultant, GRC consultant
PERF Performance optimization SQL and ABAP trace analysis (ST05, SAT), HANA PlanViz, expensive-statement analysis, code pushdown, batch scheduling an…
- What it covers
- SQL and ABAP trace analysis (
ST05,SAT), HANA PlanViz, expensive-statement analysis, code pushdown, batch scheduling and load testing. - What we do on projects
- Baseline the critical transactions and batch jobs before the conversion, find regressions afterwards, and tune the worst offenders. Test month-end and peak-day volumes on a copy of production.
- Where projects go wrong
- Testing on a thin sandbox, then learning at go-live that month-end batch runs longer than the weekend.
- Roles we staff
- SAP performance engineer, SAP Basis administrator
Data migration
Data is the work most plans underestimate. The tools matter less than the rehearsals, the data owners and the reconciliation.
BP / CVI Business Partner and customer/vendor integration The Business Partner as the leading object for customers and vendors, Customer/Vendor Integration (CVI) that keeps old…
- What it covers
- The Business Partner as the leading object for customers and vendors, Customer/Vendor Integration (CVI) that keeps old master tables in step, number ranges, roles, and the pre-conversion check reports.
- What we do on projects
- Run the pre-check reports early, resolve duplicates and inconsistent addresses and tax data, align number ranges, and test CVI on a copy of production.
- Where projects go wrong
- Starting CVI two weeks before the conversion. Parties that exist as both vendor and customer with different details.
- Roles we staff
- SAP master data consultant, SAP FICO consultant
MIGRATE Migration Cockpit and data loads The SAP S/4HANA Migration Cockpit with staging tables or direct transfer, predefined migration objects with room for cu…
- What it covers
- The SAP S/4HANA Migration Cockpit with staging tables or direct transfer, predefined migration objects with room for custom ones, used for new implementations and for loading data in selective transitions.
- What we do on projects
- Select the objects, build field and value mapping rules, load in rehearsal cycles, and give data owners readable error logs.
- Where projects go wrong
- Too few rehearsals. Mapping rules kept in spreadsheets nobody maintains.
- Roles we staff
- SAP data migration consultant, ETL developer
CLEANSE Data profiling, cleansing and archiving Profiling source data, duplicate detection, standardization, and deciding what history crosses over and what is archive…
- What it covers
- Profiling source data, duplicate detection, standardization, and deciding what history crosses over and what is archived.
- What we do on projects
- Profile each object, agree cleansing rules with data owners, archive what the business will not need online, and measure quality before and after.
- Where projects go wrong
- Treating cleansing as a technical task. Data owners not named until the second rehearsal.
- Roles we staff
- Data quality analyst, SAP data migration consultant
RECON Reconciliation and sign-off Counts, quantities and values compared between source and target by object: open items, balances, stock, assets, open o…
- What it covers
- Counts, quantities and values compared between source and target by object: open items, balances, stock, assets, open orders. Sign-off by the business owners.
- What we do on projects
- Define the reconciliation for each object before the first load, automate it, and make sign-off a gate in the cutover plan.
- Where projects go wrong
- Reconciling at the end of the cutover weekend, when a failure leaves no time to react.
- Roles we staff
- Data migration lead, finance and supply chain analysts
Cloud solutions
SAP solutions that sit around the core: people, procurement, analytics and governance.
SF SAP SuccessFactors Employee Central, recruiting, onboarding, performance and goals, compensation, learning and succession, with role-based…
- What it covers
- Employee Central, recruiting, onboarding, performance and goals, compensation, learning and succession, with role-based permissions and integration to payroll and S/4HANA.
- What we do on projects
- Design the data model and picklists, build position and organization structures, configure role-based permissions, set up Integration Center feeds, and load employee data in rehearsal cycles.
- Where projects go wrong
- Role-based permissions designed last. Picklists changed after data was loaded.
- Roles we staff
- SAP SuccessFactors consultant (Employee Central, recruiting)
ARIBA SAP Ariba Sourcing, contracts, buying and invoicing, guided buying, supplier lifecycle and performance, and the Ariba Network.
- What it covers
- Sourcing, contracts, buying and invoicing, guided buying, supplier lifecycle and performance, and the Ariba Network.
- What we do on projects
- Integrate Ariba with S/4HANA, set up catalogs and approval flows, and plan supplier onboarding as a project in its own right.
- Where projects go wrong
- Supplier onboarding effort underestimated. Catalog content with no owner.
- Roles we staff
- SAP Ariba consultant, procurement analyst
SAC SAP Analytics Cloud Stories, planning, data models, live connections to S/4HANA through CDS views, and predictive scenarios.
- What it covers
- Stories, planning, data models, live connections to S/4HANA through CDS views, and predictive scenarios.
- What we do on projects
- Choose between live and imported data per use case, model dimensions, build planning versions and security, and keep business logic in one place.
- Where projects go wrong
- The same calculation defined in the CDS view and again in the story. Access control added late.
- Roles we staff
- SAP Analytics Cloud consultant, BI developer
GRC SAP GRC Access control (segregation-of-duties analysis, access requests, emergency access), process control and risk management.
- What it covers
- Access control (segregation-of-duties analysis, access requests, emergency access), process control and risk management.
- What we do on projects
- Tailor the rule set, define mitigating controls, set up firefighter access with logging, and connect access requests to the identity process.
- Where projects go wrong
- Default rule sets never tuned, so the reports fill with noise nobody reads.
- Roles we staff
- SAP GRC consultant, SAP security consultant
Three ways to get to S/4HANA
| Path | What it is | It fits when | Watch for |
|---|---|---|---|
| Greenfield | A new S/4HANA system configured to standard, with selected data and open items loaded from the old system. | Processes have drifted far from standard, the business wants to redesign them, or the old system carries years of custom code and bad data. | Business change effort, longer design phase, and data load rehearsals. Everything old that people rely on has to be rebuilt or deliberately dropped. |
| Brownfield (system conversion) | The existing ECC system is converted in place with SUM, with the database migration (DMO) when moving to HANA in the same run. | Processes work, the business wants continuity, and the custom code is in reasonable shape. | Simplification items, custom-code remediation, Business Partner conversion and the downtime window. Old problems come across too. |
| Selective data transition | A new system or a converted copy, with chosen companies, years or objects moved. Sometimes described as bluefield. | Parts of the business move at different times, an acquisition or split is involved, or only some history should carry over. | It needs specialist tooling and planning. Fewer references exist, so scope and cost need careful validation. |
Choosing the path is a decision for the business, not a default. We write the recommendation, the alternatives we rejected and why. Deployment (on-premise, private cloud or public cloud edition, and which hyperscaler) is a separate decision with its own constraints.
An ECC to S/4HANA migration, in 18 steps
This is how we plan a conversion or migration end to end. Not every tool appears on every path: SUM and DMO belong to system conversion, the Migration Cockpit to new implementations and selective loads, and Business Partner conversion to any path that carries customers and vendors across.
Discover and assess
Know what you have before you choose how to move it.
-
1
Existing landscape discovery
Systems, clients, add-ons, industry solutions, databases, interfaces, users and data volumes. We also record which business units use which functions, because that decides scope later.
-
2
Readiness assessment
Run the SAP Readiness Check for SAP S/4HANA on the productive system. It reports on simplification items, custom code, add-ons, sizing and functional fit, and gives the team a shared baseline.
-
3
Simplification item analysis
Go through the catalog items that apply to your system. Some are informational; others block the conversion until you act, such as the Business Partner approach, Material Ledger, the new Asset Accounting and removed credit and rebate functions.
-
4
Custom code assessment
Use the ABAP Test Cockpit with the S/4HANA readiness checks, and add usage data from the production system so you remediate what runs and delete what does not. Plan this early; it can take as long as a small project.
-
5
Business process analysis
Walk the main processes with their owners: finance close, order to cash, procure to pay, plan to produce, warehouse. Record what changes with S/4HANA, what can move to standard and what needs an extension.
Plan and design
Make the decisions that set scope, risk and cost.
-
6
Master and transactional data strategy
Decide what crosses over: open items, balances, history, closed documents, archived data. Name an owner for every object, because someone from the business has to sign it off.
-
7
Data cleansing
Profile and clean customers, vendors, materials, BOMs, assets and open documents in the source. Business Partner and CVI pre-checks start here, not in the last month.
-
8
Conversion or implementation path selection
Choose greenfield, system conversion or selective data transition using the discovery findings, and record why. This is also where the target release and deployment option are fixed.
-
9
Target architecture design
Decide the clean-core approach: what stays standard, what is a key-user extension, what is a side-by-side extension on BTP, and which Fiori apps replace which transactions. Design landscape, transports and sizing.
-
10
Integration remediation
Work through the interface inventory. Retire dead interfaces, rebuild live ones for the new system, and move middleware content where it makes sense. Trading partners get a test schedule.
Build and prove
Find problems in rehearsal, not in production.
-
11
Migration rehearsals
Run the full conversion or load on production-sized copies at least two or three times. Time every step, including the technical downtime, and fix the issues each run reveals. Reconcile every object.
-
12
Functional testing
System integration tests across processes, user acceptance with named business testers, and regression on what must not change. Automate the repeatable parts so each rehearsal can be re-tested.
-
13
Security and role testing
Test with real role assignments, including Fiori catalogs and spaces. Review segregation-of-duties conflicts before they reach auditors.
-
14
Performance validation
Compare critical transactions, reports and batch jobs with the baseline taken before the project. Tune expensive SQL and code, and test month-end and peak volumes.
Cut over and stabilize
Go live with a plan the team has already run.
-
15
Cutover planning
A minute-by-minute runbook, a freeze calendar, role assignments, rollback criteria and a go/no-go checklist. At least one mock cutover is timed against the real window.
-
16
Go-live
Execute the runbook, run reconciliations as gates, and hold the go/no-go review with business owners and the program lead before users log in.
-
17
Hypercare
A defined period with extra support on site or remote, a triage routine, daily defect review, and clear rules on what is a defect and what is a new request.
-
18
Post-migration optimization
Remove temporary code, retire old interfaces, tune what hypercare surfaced, and plan the next wave: more Fiori adoption, further simplification, analytics and extensions.
The 18 steps overlap on a real program. What matters is that each has an owner, an exit check and a place in the plan.
The SAP landscape we work across
A program touches more than the ERP. These are the layers where we place consultants and where the design decisions sit.
Experience
- SAP Fiori launchpad
- Fiori elements
- SAPUI5
- Work Zone
- SAP GUI for legacy transactions
Role-based access to apps, replacing transactions step by step.
Applications
- S/4HANA Finance
- Supply chain
- EWM
- TM
- IBP
- SuccessFactors
- Ariba
The business processes and their configuration.
Extension
- In-app key-user extensibility
- ABAP Cloud
- BTP side-by-side
- CAP
- Custom Fiori apps
Where custom needs live, kept away from the core.
Integration
- Integration Suite
- API Management
- Event brokering
- IDoc / RFC / BAPI
- OData / REST / SOAP
- EDI
Everything between SAP and the rest of the business.
Data and analytics
- CDS views
- Embedded analytics
- Analytics Cloud
- BW/4HANA
- Datasphere
Reporting, planning and the data model underneath.
Platform
- SAP HANA
- Basis
- CTS and ChaRM
- Cloud ALM / Solution Manager
- Cloud Connector
- Identity
Operations, transports, monitoring and security.
Infrastructure
- On-premise
- Private cloud
- AWS
- Microsoft Azure
- Google Cloud
Where the landscape runs.
How we would approach a real conversion
Illustrative scenario. Not a real client engagement. No outcomes are claimed.
A manufacturer runs ECC 6.0 with a large library of custom reports and a dozen EDI partners. The CFO wants S/4HANA with a reliable close; operations cannot accept a long outage over month-end.
- First two weeks
- Run the readiness check, pull usage data for custom code, inventory interfaces and trading partners, and review customer and vendor data quality. Produce a one-page risk list.
- Path decision
- Custom code and processes are mostly sound, so a system conversion is the default. A selective transition is considered only if one plant or company must move separately.
- Data
- Business Partner pre-checks begin immediately. Open items, stock and assets get an owner each and a reconciliation defined before the first rehearsal.
- Custom code
- Remediate what the usage data shows is in use, retire the rest with business sign-off, and rebuild the most-used reports as Fiori apps over CDS views.
- Testing
- Parallel close in the test system, automated regression for order to cash, and role tests with real users, including month-end volumes.
- Cutover
- Three timed rehearsals before the window. A go/no-go meeting with reconciliation results on the table, and a rollback point agreed in advance.
SAP consultants we place
We staff SAP roles on contract, direct hire and dedicated teams. Candidates are screened technically before submission and must be authorized to work in the United States without sponsorship.
-
SAP Solution Architect
Owns the end-to-end design across modules, integration and extension. Makes clean-core, landscape and deployment decisions and explains them to executives and engineers.
- S/4HANA
- Clean core
- BTP
- Integration
- Landscape
We screen for: Can defend a greenfield or conversion recommendation with trade-offs, and has run a cutover.
-
SAP S/4HANA Functional Consultant
Leads fit-to-standard workshops, configures processes, writes specifications and supports testing across one or more modules.
- SAP Activate
- Fit-to-standard
- Config
- UAT
We screen for: Process depth in their module and what changed from ECC.
-
SAP EWM Consultant
Designs and configures warehouse structure, strategies and RF flows, and integrates with ERP deliveries.
- EWM
- RF
- Wave management
- Handling units
We screen for: Putaway and picking strategy design, and ERP delivery integration, not just terminology.
-
SAP FICO Consultant
Configures the ledger, AP, AR, asset accounting and controlling, and supports close and reconciliations.
- FI-GL
- FI-AP/AR
- FI-AA
- CO
- Universal Journal
We screen for: Can explain document splitting, account determination and how they close the books.
-
SAP MM Consultant
Configures procurement, inventory and valuation, and integrates with finance and production.
- MM-PUR
- MM-IM
- MRP
- Valuation
- Ariba
We screen for: Release strategies, GR/IR, valuation and migration of open POs.
-
SAP SD Consultant
Configures order to cash: pricing, availability, delivery, billing and output.
- Pricing
- ATP
- Billing
- Output
- Rebates
We screen for: Pricing procedure design and billing-to-FI account determination.
-
SAP ABAP Developer
Builds and remediates custom code, enhancements, CDS views, RAP services and interfaces.
- ABAP
- CDS
- RAP
- BAdI
- ABAP Unit
We screen for: Reads and writes real code in screening, including performance and clean-core practices.
-
SAP BTP Developer
Builds side-by-side extensions and integrations on the SAP Business Technology Platform.
- ABAP Cloud
- CAP
- Node.js
- Fiori
- OData
We screen for: How they decide between in-app, on-stack and side-by-side extension.
-
SAP Basis Administrator
Builds and runs the landscape: HANA, kernel and patches, transports, monitoring and conversions.
- HANA
- SUM/DMO
- Transports
- Monitoring
- DR
We screen for: Has timed a conversion, handled a failed import, and tuned a system.
-
SAP Security Consultant
Designs roles and authorizations for S/4HANA and Fiori, and supports segregation of duties and audits.
- PFCG
- SU24
- Fiori catalogs
- GRC
- SoD
We screen for: Role redesign approach, and how they fix an authorization failure without widening access.
-
SAP Program Manager
Runs the program: plan, budget, risks, vendors, business readiness and go/no-go decisions.
- SAP Activate
- Cutover
- Risk
- Vendors
- Change
We screen for: Has delivered an SAP go-live and can describe what went wrong and what they changed.
Project delivery or consultants in your team
We deliver the project
Tetra Connects leads a defined scope with a plan, a team and a reporting rhythm.
- Fixed scope or time and materials, agreed in writing
- A named delivery lead and weekly status
- Suits assessments, migrations, rollouts and extensions with a clear end
- You approve scope, design and acceptance
Our consultants join your team
You run the program. We provide screened specialists who work under your direction.
- Contract, contract-to-hire or direct hire
- Individual consultants or a dedicated team
- Suits programs that already have a lead and a plan
- Technical screening before any resume reaches you
Many programs use both: a delivery team for the migration and extra consultants for peak testing or cutover.
Methods and tooling we work with
These are tools and methods our consultants use. They do not imply SAP partner status or certification.
Questions people ask
Should we choose greenfield or brownfield?
It depends on how far your processes have drifted from standard, how much custom code is in use, and how much change the business can absorb. A conversion keeps continuity and shortens the design phase but carries old problems. A new implementation resets them at the cost of change effort. We write down the recommendation and the options we rejected.
What is the clean-core approach?
Keeping the SAP core close to standard and putting custom needs in extensions that use released interfaces, so upgrades stay manageable. In practice that means key-user extensibility for small changes, ABAP Cloud for larger ones, and side-by-side extensions on BTP where it makes sense.
What happens to our custom code?
We use the ABAP Test Cockpit with S/4HANA readiness checks and production usage data. Code that is not used is deleted with business sign-off, code that breaks is remediated, and the remainder is reviewed for performance and for a better standard alternative.
How long does a migration take?
There is no honest single answer. Timelines are driven by custom code volume, data quality, number of interfaces, testing scope and the cutover window. After a readiness check and a data review we can give a range with the assumptions behind it.
Do you do Basis, security and ABAP work separately from functional work?
Yes. Many clients bring us in for one of those roles inside a larger program, either as consultants on a contract or as a short assessment.
Can you staff a full SAP team?
We can staff a team across functional, technical and program roles, including dedicated team arrangements. Availability depends on the role and location, so we confirm it before committing.
Do your SAP consultants require visa sponsorship?
No. We do not sponsor work visas. Candidates must be authorized to work in the United States without sponsorship. Some roles on public-sector programs also require US citizenship.
What does SAP say about ECC support dates?
SAP has published that mainstream maintenance for ECC 6.0 ends at the close of 2027, with extended maintenance for an additional fee through 2030 and a separate private-edition option that has conditions. Terms change, so confirm the current position with SAP.
Starting an SAP program, or short of a role?
Tell us which: a technical lead replies about the project, or a recruiter confirms the requirement before any sourcing starts.
Related
-
Oracle
Oracle Fusion Cloud ERP, SCM and HCM implementations, EBS to Fusion migration, Oracle Integration, reporting and analytics, OCI and database work.
-
ERP implementation
SAP, Oracle, Dynamics 365 and Workday implementations covering design, configuration, data migration, integration, testing and hypercare.
-
Legacy modernization
Assess and modernize aging applications and platforms: rehost, replatform, refactor, replace or retire, with a plan that keeps the business running.
-
Implementations and migrations
How we take responsibility for complex transformation programs: twelve migration types, a seven-stage method and the deliverables you receive at each stage.
-
IT and technology
Software developers, data engineers, SAP and Oracle consultants, cloud and DevOps, QA and security roles on contract or direct hire.
-
Project readiness check
Thirty-one planning questions across ten areas. See which ones you have answered, which are still open, and what to do about each.
Have a technology challenge? Let’s work out the approach.
Discuss a project
Tell us the current system, the target and the timeline. A technical lead replies to talk about scope.
Start the project briefRequest technical talent
Need consultants inside your team rather than a project owner? Send the requirement.
Request talentBecome a partner
Delivery firm, staffing supplier or consulting partner? Register your company.
Register as a partner