SAP PP/QM Consultant
- ).
List of responsibilities:
1. Lead the IT Application team providing S/4 HANA functional support for Business teams on production issues within the MAKE business function (Plant Maintenance, Quality Management, and Production Planning and Execution).
2. Work closely with business stakeholders and operations.
3. Provide functional expertise in troubleshooting Support Incidents and Service Requests; ensure resolutions meet defined SLAs.
4. Coordinate and collaborate with business, product, development, integration, and Basis teams to resolve issues.
5. Monitor application and integration errors; maintain strong understanding of SAP S/4HANA messaging and AIF monitoring frameworks to proactively detect, triage, and route issues.
6. Review built solutions and incoming enhancements before production deployment; ensure support teams receive continuous knowledge transfer and up-to-date runbooks.
7. Mentor and coach junior consultants; organize formal knowledge-transfer sessions and maintain the knowledge base / runbooks.
8. Drive root-cause analysis (RCA) and permanent fixes for recurring issues; track and report on problem-management actions and improvements.
9. Maintain close oversight of change/transport processes and ensure appropriate rollback/mitigation plans for production risks.
10. Participate in workshops, prepare and review functional specifications, and guide technical teams on functional design and conversion of requirements into solutions.
11. Lead or support system testing, user acceptance testing (UAT), cutover, golive and hypercare activities.
- Requirements: Must-have bullet list:
- 8-12 years of SAP experience with 3+ full-cycle implementations in PP, QM and PM and proven hands-on support experience.
- Strong experience in any two of the above three functional areas is required.
- Deep understanding of production order lifecycle: order types, number ranges, release/confirmation profiles, settlement rules, master data (material master (MRP/Work Scheduling), BOMs, routings, production versions), MRP types, lot sizing, planning strategies, MRP Live.
- Experience of Integration with MM/QM/FICO/EWM/MES: procurement, inspection lots/usage decisions, settlement postings and common interfaces.
- Troubleshoot production issues, analyze MD04/MRP logs, and drive corrective actions.
- Experience with application support activities: incident triage, root-cause analysis, problem management, and SLA-driven delivery.
- Practical understanding of integration points with MM, SD and FICO and experience working with API Interfaces with other eco systems (internal and external applications).
- Client-facing experience with strong communication and leadership skills; ability to coordinate across business and technical stakeholders.
- Nice-to-have bullet list:
- Exposure/Experience with Fiori Applications, Clean Core Implementation approach
- Exposure to SAP Solution Manager / ChaRM or other ALM tools and ITIL practices.
- Familiarity with other cross-functional areas within SAP and ability to work with development teams.
- Experience with S/4HANA conversions/migrations and embedded analytics (CDS views, S/4 reporting).
- Understanding of ABAP debugging and ability to read logs/traces.
- Understanding of automated testing of any Jira X-Ray, Work soft, Client ALM tools and test-case management.
- Benefits paragraph: Danta offers a compensation package to all W2 employees that are competitive in the industry. It consists of competitive pay, the option to elect healthcare insurance (Dental, Medical, Vision), Major holidays and Paid sick leave as per state law. The rate/ Salary range is dependent on numerous factors including Qualification, Experience and Location.
We should not create Pay section because no explicit range. Benefits section includes mention of competitive pay etc.
Schedule section: "Note This position is based in Raritan, New Jersey, and requires 5 days per week working from the office." Also mention only US candidates considered; but that's eligibility. Could include location and schedule.
We also need About the role paragraph: combine eligibility statement and job description summary? The job description paragraph is separate; we could treat that as About the role. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have About the role containing the job description summary (the paragraph after Job Description). Also include eligibility statement maybe there. Thus sections:
About the role
Employment Eligibility Statement Due to specific project and client requirements, this position is open to U.S. Citizens and U.S. Lawful Permanent Residents (Green Card holders). Sponsorship is not available at this time. Danta Technologies evaluates all candidates in compliance with the Immigration and Nationality Act (INA) and EEOC guidelines. All hiring decisions are made without regard to race, color, religion, sex, gender identity, sexual orientation, national origin, age, disability, veteran status, or any other protected characteristic. Note This position is based in Raritan, New Jersey, and requires 5 days per week working from the office. Only candidates who are currently located within the United States will be considered. Applications from candidates residing outside the USA will not be accepted. Lead the IT Application team that provides Tier2/3 SAP functional support for MAKE business processes (PP/QM/Sub-contracting/PM), own production incident and change resolution, ensure knowledge transfer, and drive continuous improvement. The role requires strong functional configuration skills, hands-on process knowledge, and cross-module integration experience in ECC and/or S/4HANA.
Then ResponsibilitiesResponsibilities
with- ... each bullet.
Then Requirements
Requirements
with- ... Must-have bullets.
We could also separate Nice-to-have as maybe under Requirements? But we could include them as part of Requirements list, but they are nice-to-have. Could create a separate section "Qualifications" but not needed. The instruction says prefer few substantive sections over many thin ones. Could combine Must-have and Nice-to-have under Requirements, but we need to preserve all info. Could make two sub-sections? Not allowed headings besides those listed. Could embed nice-to-have as part of Requirements list with a note. Probably okay to include them as part of Requirements list.
Then Benefits
Benefits
with paragraph. Then ScheduleSchedule
with paragraph about location and 5 days office. We must not repeat job title as heading. Not include Job ID etc. We must output only HTML fragment. Let's craft. Check for any boilerplate: EEO statements we kept as part of About the role; they are substantive? They are boilerplate but maybe considered required? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove EEO statements. Indeed we need to remove EEO boilerplate. The eligibility statement about US Citizens is not EEO; it's specific requirement. The EEO lines: "All hiring decisions are made without regard to race, color, religion, sex, gender identity, sexual orientation, national origin, age, disability, veteran status, or any other protected characteristic." and later similar lines. Those are boilerplate EEO; we should remove them. Also the later Notes about All qualified applicants will receive consideration... also EEO boilerplate; remove. Thus About the role should contain: Employment Eligibility Statement (US Citizens etc), note about location and schedule, and job description summary. Remove EEO lines. Let's rewrite About the role paragraph: "Employment Eligibility Statement Due to specific project and client requirements, this position is open to U.S. Citizens and U.S. Lawful Permanent Residents (Green Card holders). Sponsorship is not available at this time. Danta Technologies evaluates all candidates in compliance with the Immigration and Nationality Act (INA) and EEOC guidelines. Note This position is based in Raritan, New Jersey, and requires 5 days per week working from the office. Only candidates who are currently located within the United States will be considered. Applications from candidates residing outside the USA will not be accepted. Lead the IT Application team that provides Tier2/3 SAP functional support for MAKE business processes (PP/QM/Sub-contracting/PM), own production incident and change resolution, ensure knowledge transfer, and drive continuous improvement. The role requires strong functional configuration skills, hands-on process knowledge, and cross-module integration experience in ECC and/or S/4HANA." We kept the Danta evaluates line (mention of INA and EEOC guidelines) - that's not EEO boilerplate but a statement about compliance; it's okay. Now Responsibilities list as above. Requirements list: include Must-have bullets and Nice-to-have bullets. We'll combine. Benefits paragraph: as given. Schedule paragraph: "Note This position is based in Raritan, New Jersey, and requires 5 days per week working from the office." But we already included that note in About the role; we might duplicate. Better to keep location/schedule only in Schedule section, and move eligibility statement to About the role. Let's split: About the role includes eligibility statement and job description summary (without location). Schedule includes location and 5 days office. Also note about US candidates only considered could be in About the role or Schedule? It's about eligibility; maybe keep in About the role. Thus: About the role paragraph: Employment Eligibility Statement (US Citizens etc), Danta evaluates..., Lead the IT Application team..., The role requires... Schedule paragraph: Note This position is based in Raritan, New Jersey, and requires 5 days per week working from the office. Only candidates who are currently located within the United States
- ... Must-have bullets.
We could also separate Nice-to-have as maybe under Requirements? But we could include them as part of Requirements list, but they are nice-to-have. Could create a separate section "Qualifications" but not needed. The instruction says prefer few substantive sections over many thin ones. Could combine Must-have and Nice-to-have under Requirements, but we need to preserve all info. Could make two sub-sections? Not allowed headings besides those listed. Could embed nice-to-have as part of Requirements list with a note. Probably okay to include them as part of Requirements list.
Then Benefits
- ... each bullet.
Then Requirements