Manager, IT Business Architect – SAP SD
Revvity · Waltham, MA · 4 wk ago
Information Technology$124k–$165k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarized away detail. Remove boilerplate etc.
We need to parse the posting and extract content for each heading.
Let's identify sections:
- About the role: The first paragraph(s) describing role: "The Manager, IT Business Architect - SAP SD is central to our ERP transformation program. The SME will serve as the functional and architectural authority for the SAP SD - owning the module end-to-end, translating complex business requirements into scalable SAP solutions. The role will provide day-to-day support to the critical sales processes to ensure issues are resolved as a priority and there is no business impact. The role will be guiding Revvity through its SAP transition with precision and strategic foresight. This role oversees the development, validation, implementation, and day-to-day performance of the SAP SD module. These activities are performed in compliance with industry regulations, site operating procedures, quality/safety policies and cost/processing time standards. The role will work closely with key stakeholders in Commercial, Operations, Trade Compliance and Finance functions. The role will be directly responsible for managing and maintaining the current ECC landscape and perform critical role in any upgrade, implementations, changes, rollouts, etc. that the organization decides on."
That seems like About the role.
- Responsibilities: The posting includes "Day-to-Day Support Responsibilities" bullet list, then "Solution Architecture & Design", "ERP Transformation & Implementation", "Configuration, Development & Governance", "Stakeholder Engagement & Program Leadership", "Post Go-Live & Continuous Improvement". All these are responsibilities. So we can combine them under Responsibilities with subheadings? But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot create custom headings like Solution Architecture etc. So we need to put all responsibilities under
- items. We should preserve the details. Could group them as list items, each bullet maybe a responsibility. We'll need to extract each bullet point.
Let's list responsibilities from the text:
Day-to-Day Support Responsibilities:
- Assist end-users with SAP SD-related problems, troubleshoot issues, and provide quick solutions to minimize downtime.
- Log, prioritize, and resolve support tickets related to sales, shipping, billing, and pricing functionalities.
- Conduct testing for new functionalities, support patches/upgrades, and validate data accuracy post-implementation.
- Monitor sales order processing, delivery, billing, and related workflows to ensure smooth operations.
- Provide end-user training, update user manuals, and create documentation for new or modified processes.
- Collaborate with MM, FI, CO, and WM modules to resolve inter-module issues impacting sales and distribution.
- Assist in implementing minor enhancements, user exits, and custom reports to meet evolving business needs.
- Regularly review system performance metrics and troubleshoot bottlenecks affecting SD processes.
Solution Architecture & Design:
- Architect end-to-end SAP SD solutions aligned with Revvity's complex global business requirements, ensuring scalability, compliance, and performance
- Lead solution design workshops with business stakeholders, translating requirements into functional specifications, process flows, and configuration blueprints
- Define the target-state architecture for SD within the S/4HANA Private Cloud environment, including integration touchpoints with E4H and adjacent modules (MM, FI/CO, WM/EWM, PP) subject to project initiation.
- Evaluate and recommend Greenfield, Brownfield, or Bluefield migration approaches based on business complexity, data quality, and transformation goals
- Design and govern SAP Fiori application strategy for SD user personas, ensuring intuitive UX aligned with SAP best practices (subject to project initiation).
ERP Transformation & Implementation:
- Lead and deliver 3–4 full lifecycle SAP SD implementations as the functional SME - from project initiation through go-live and hypercare
- Drive the ECC to S/4HANA migration for SD, including delta analysis, simplification item assessment, and business process re-engineering
- Own the fit-gap analysis between current ECC processes and S/4HANA standard capabilities, recommending configurations or enhancements as appropriate
- Ensure seamless ECC-GTS integration continuity
Configuration, Development & Governance:
- Perform and oversee SAP SD configuration across the full module scope: Order Management, Pricing & Conditions, Billing, Credit Management, Shipping & Transportation, Intercompany, Revenue Recognition, and Returns/Complaints
- Define and enforce configuration standards, naming conventions, and change management governance across the SD landscape
- Collaborate with ABAP/technical teams to design custom enhancements, BAdIs, user exits, and BDC (Batch Data Conversion) programs where standard configuration is insufficient
- Leverage SAP BTP (Business Technology Platform) capabilities — including Integration Suite, Extension Suite, and SAP Build — to extend and integrate SD processes where applicable
- Oversee data migration strategy for SD master data (customer master, material master, pricing conditions, open orders) using LSMW, BAPI, or SAP Data Services
Stakeholder Engagement & Program Leadership:
- Act as the primary functional liaison between business stakeholders, IT leadership, and implementation partners for all SD
- Facilitate business process workshops, design reviews, and sign-off sessions with regional and global process owners
- Provide functional leadership and mentoring to junior SAP SD consultants and business analysts on the program team
- Prepare and present solution design documents, functional specifications, and executive-level status updates to IT and business leadership
- Support testing strategy and execution — including SIT, UAT, regression, and performance testing — ensuring defect resolution and sign-off readiness
- Contribute to training material development and end-user enablement programs for SD processes
Post Go-Live & Continuous Improvement:
- Lead hypercare support post go-live, managing critical issue resolution and stabilization
- Identify and drive continuous improvement opportunities within the SD landscape, leveraging SAP innovations (e.g., Advanced ATP, Output Management, Intelligent Trade Claims)
- Monitor SAP roadmap updates and advise leadership on relevant new capabilities, deprecations, and upgrade impacts
We'll include all these as list items under Responsibilities.
Now Requirements: The posting has "Basic Qualifications:" and "Preferred Qualifications:" sections. According to instruction, we have headings: Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements = basic qualifications (mandatory). Qualifications = preferred qualifications? Skills maybe separate? But we have both Requirements and Qualifications headings available. We could put Basic Qualifications under Requirements, and Preferred Qualifications under Qualifications. Skills could be derived from the qualifications (like analytical, communication). But we must not invent or summarize away detail; we must preserve all substantive info. If we put skills under Skills heading, we need to extract skill statements from the posting. There are statements like "Exceptional analytical and problem-solving skills with the ability to decompose complex business scenarios into structured SAP solutions", "Strong communication and stakeholder management skills - able to present to both technical teams and C-suite executives", "Proven ability to lead without authority in a matrixed, global program environment", "High degree of ownership and accountability - comfortable driving decisions in ambiguous situations", "Collaborative mindset with experience working across onshore/offshore delivery models", "Experience in life sciences, diagnostics, or medical device industry SAP implementations is highly desired". Those could go under Skills. However, we also have Preferred Qualifications that include many items like Bachelor's degree, experience across methodologies, ABAP understanding, BDC, LSMW, BAPI, IDocs, SAP BTP, SAP E4H exposure, SAP RAR/IFRS15, SAP certification, global multi-org multi-currency experience, etc. Those could go under Qualifications.
We must not create sections with filler text. Ensure each heading has real specific content.
Pay: The posting includes base salary range: "$124,000 - $165,000." Also description about base pay etc. That's substantive. So we include Pay section with that info.
Benefits: The posting includes "What do we offer? We provide competitive and comprehensive benefits to our employees. Below are some highlights of our benefits: Medical, Dental, and Vision Insurance Options Life and Disability Insurance Paid Time-Off Parental Benefits Compassionate Care Leave 401k with Company Match Employee Stock Purchase Plan Learn more about Revvity’s benefits by visiting our Bswift page. Log-In instructions are provided towards the bottom of the Bswift page. For benefit-eligible roles only. Part-time and temporary roles may not be eligible for all benefits listed. Please reach out to your recruiter for more information."
We need to preserve all substantive info. So we can list benefits as bullet list.
Schedule: Not mentioned. No info about schedule (full-time? It says full-time position). Actually earlier: "The base salary range for this full-time position is $124,000 - $165,000." So schedule is full-time. That's substantive. So we can include Schedule section with "Full-time". However we must not create placeholder like "not specified". Since we have explicit full-time, we can include.
Now we need to output HTML fragment only, no /. Use
for section headings. Use
- for any list of duties/requirements/benefits, and
for prose. We need to decide which content goes as prose vs list. For About the role: It's prose paragraphs. Could be one or two
elements. For Responsibilities: It's a list of duties, so
- .
For Requirements (Basic Qualifications): It's a list of items (each line). Could be
- .
For Qualifications (Preferred Qualifications): Also list.
For Skills: Could be list.
For Benefits: list.
For Pay: Could be prose (maybe
). For Schedule: Could be prose (
Full-time). We must not repeat job title as heading. Already not. We must not include Job ID/requisition numbers. We must remove boilerplate like cookie/navigation/legal/EEO etc. Not present. Now let's craft the HTML. We'll start with
About the role
then...
. We need to preserve all substantive information from About the role paragraph. Let's copy the paragraph(s) exactly as in posting, maybe split into two paragraphs for readability but must preserve all info. We'll combine into onemaybe long but okay. Paragraph: "The Manager, IT Business Architect - SAP SD is central to our ERP transformation program. The SME will serve as the functional and architectural authority for the SAP SD - owning the module end-to-end, translating complex business requirements into scalable SAP solutions. The role will provide day-to-day support to the critical sales processes to ensure issues are resolved as a priority and there is no business impact. The role will be guiding Revvity through its SAP transition with precision and strategic foresight. This role oversees the development, validation, implementation, and day-to-day performance of the SAP SD module. These activities are performed in compliance with industry regulations, site operating procedures, quality/safety policies and cost/processing time standards. The role will work closely with key stakeholders in Commercial, Operations, Trade Compliance and Finance functions. The role will be directly responsible for managing and maintaining the current ECC landscape and perform critical role in any upgrade, implementations, changes, rollouts, etc. that the organization decides on." We'll put that in a
. Now Responsibilities: We'll create
Responsibilities
then- with each bullet as
- . Need to ensure we include all bullet points from the sections. Let's compile list items: From Day-to-Day Support Responsibilities: - Assist end-users with SAP SD-related problems, troubleshoot issues, and provide quick solutions to minimize downtime. - Log, prioritize, and resolve support tickets related to sales, shipping, billing, and pricing functionalities. - Conduct testing for new functionalities, support patches/upgrades, and validate data accuracy post-implementation. - Monitor sales order processing
- .
For Qualifications (Preferred Qualifications): Also list.
For Skills: Could be list.
For Benefits: list.
For Pay: Could be prose (maybe
- .
For Requirements (Basic Qualifications): It's a list of items (each line). Could be
- for any list of duties/requirements/benefits, and