SAP Consultant Skills Assessment: Mapping Configuration, Analysis and Development Work
“SAP Consultant” describes a technology ecosystem, not a single ACS occupation.
A comparable ecosystem-label problem appears when mapping a Salesforce Consultant to Australian migration and ACS occupations.
A SAP implementation can contain three distinct professional stories. The consultant configuring pricing conditions may own business-process configuration, the developer writing ABAP enhancements may own application behaviour, and a Basis engineer may own system availability and upgrades. Collect a separate deliverable and decision for each role before proposing an ACS occupation. If the same applicant changed from functional configuration to integration design, split the dates and examples; calling all of it ‘SAP consulting’ erases the evidence needed to distinguish those occupations.
The broader rule is to assess duties rather than job titles in an ACS assessment.
One SAP consultant translates finance requirements into system behaviour. Another writes ABAP and custom applications. Another designs integrations. Another manages a large ERP implementation. The product name is shared; the professional function is not. For the underlying rule, see ACS IT occupations and ANZSCO codes.
Start by removing SAP from the sentence
How certifications should enter the story
A SAP credential can support familiarity with a platform but should not replace employment proof. ACS explains the status of qualifications through its qualification-evidence guidance, and its assessment-process page describes review of closely related employment. Verify any vendor-specific certification category before assuming it earns independent assessment credit. For SAP specialists considering multiple occupations, first choose the occupation supported by sustained work products; then use training evidence to explain technical currency, not to compensate for unrelated duties.
Describe a representative project without the product name. If the story becomes “analysed order-to-cash requirements, documented functional specifications and validated the solution through UAT”, the occupation signal is different from “developed ABAP interfaces, debugged code and implemented enhancements”.
Four common SAP work patterns
Split a SAP implementation into actual technical roles
A SAP project may have functional consultants, ABAP developers, integration specialists, security administrators, basis engineers, testers and delivery managers. The shared platform says little about their occupations. Ask what the consultant designed and controlled: business-process mapping, custom code, middleware interfaces, access controls, infrastructure or workstream delivery. Map these outputs against the ACS occupation information, not a vendor badge. The person who configured FI/CO workflows after requirements workshops is building a different evidence story from someone who wrote ABAP classes and optimised database queries, even if both employers used the same title.
| Dominant SAP work | Occupation direction to investigate | Evidence that should be visible |
|---|---|---|
| Requirements, process analysis, functional specifications, UAT | ICT Business Analyst 261111 | Business needs, process change, functional requirements, validation. |
| System behaviour, integration analysis, technical system changes | Systems Analyst 261112 | System analysis, constraints, integration, specifications. |
| ABAP/custom code, application development, debugging/testing | Developer Programmer 261312 / Software Engineer 261313 | Code, system/program needs, technical specifications, testing, engineering responsibility. |
| Program governance, scope, schedule, risk, resources | ICT Project Manager 135112 where accountability is substantial | Defined ICT project, delivery control, milestones, dependencies and outcomes. |
Configuration is not automatically business analysis
Look for work products that reveal responsibility
Do not mistake business-process expertise for software development
SAP basis versus SAP development
Basis work can involve installation, patching, transport administration, landscape monitoring, disaster recovery and performance operations. ABAP development centres on code, interfaces, testing and changes to application behaviour. Functional consulting may be closer to business process analysis. A company may rotate staff between those functions, but the migration narrative should not describe them all as a continuous single occupation without justification. Before selecting a code, map one representative change from request to release and note which technical decisions belonged to the applicant. This can reveal the real professional centre much more clearly than a generic SAP implementation certificate.
An employer reference is most useful when it distinguishes support tasks from original engineering decisions. Were upgrades carried out according to vendor scripts, or did the candidate personally design downtime and recovery approaches? Did the person create an interface or simply test one? These are factual distinctions that a former supervisor can often verify. The goal is to avoid erasing genuine expertise with vague wording while also avoiding occupation inflation.
An SAP specialist may understand business workflows deeply without routinely producing application code. That is not a defect; it may simply be evidence of a different professional activity. A consultant who maps procurement processes, identifies gaps and translates business needs into functional specifications should demonstrate the analysis behind those decisions. A developer who implements enhancements should show design, coding and testing responsibility. Distinguish both from an administrator who mainly maintains user roles, parameters and routine system operations. An impressive SAP project name does not erase these differences.
For consultants spanning several modules, focus on a small number of representative changes rather than listing every product acronym. Take one change request from user problem to technical or functional resolution. Who identified the root cause? Who decided how the system should behave? Which document was approved? What was tested after deployment? The answers help distinguish professional depth from team participation. If a consultant received a promotion into project management, consider describing the old and new periods separately. The assessment should reflect a coherent career, not flatten all work into a title chosen retrospectively.
A credible functional-analysis record might include process models, workshop decisions, fit-gap assessments, functional specifications and UAT sign-off. For a development-focused role, examine technical designs, change logs, interfaces, code ownership and defect resolution. The ACS experience standards call for professional complexity and occupation relevance. Do not overstate access to a repository as ownership of software development. Likewise, do not describe ordinary ticket administration as systems architecture merely because the software is enterprise-scale. The document should explain the decisions the individual was authorised to make.
Configuration can be driven by deep requirements analysis, by technical system design, or by routine administration. The evidence needs to explain why the configuration decision was made, which requirements or constraints drove it, and how the applicant validated the result.
Functional does not mean non-technical
Describe an implementation without copying the job advertisement
Suppose a consultant supported a migration from ECC to S/4HANA. Instead of listing product modules, describe a specific reconciliation problem, how mismatched master data was identified, who decided the remediation rule and what the consultant delivered. Ask the employer to reflect those actual duties in a dated reference complying with ACS letter requirements. If the applicant shifted from support to solution design halfway through the project, record the transition. References copied from generic occupation definitions undermine precisely the professional distinction the assessment needs.
A functional consultant can still demonstrate substantial ICT depth through data structures, integration constraints, system behaviour, access design, configuration dependencies and testing. The question is not whether the person writes code every day; it is which professional function the recurring responsibility supports.
Technical does not automatically mean Software Engineer
Writing ABAP or integration code creates a software signal, but occupation selection still requires the whole employment episode. Developer Programmer and Software Engineer overlap in tools and code; responsibility for system needs, design and broader engineering decisions can matter to the boundary. Preserve that comparison for the dedicated software-occupation pages rather than forcing it into SAP alone.
Map career phases separately
SAP careers often move from support to functional consulting, then solution design or delivery leadership. Do not let the current senior title rewrite the earlier years. References should preserve the actual chronology and duties for each role.
A SAP occupation decision in six questions
- What problem do stakeholders bring to you?
- What do you personally analyse or design?
- What artifact or output do you produce?
- How much of the role is code versus requirements/configuration/system analysis?
- Do you own project delivery or only contribute to it?
- Which current ACS occupation description fits the recurring work with the fewest forced assumptions?
The strongest SAP assessment story is usually the least branded one. When the product name is removed, the professional function should still be obvious.
