SAP Master Data Lead

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must include a section only when posting has real specific content for it. We need to parse the posting. The posting includes: - Intro paragraph about GAF culture (maybe "About the role"? Actually "Job Summary" is a section. Could map to "About the role". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide which sections to include based on content. We have: - Job Summary (description of role). Could be "About the role". - Essential Duties (list of duties). That's "Responsibilities". - Qualifications Required (list). That's "Qualifications" maybe "Requirements"? The instruction includes both Requirements and Qualifications as possible headings. We need to decide. The posting has "Qualifications Required" and "Qualifications Preferred". Could combine into "Qualifications" section with required and preferred subpoints? But we must not invent sections with filler. We can have a "Qualifications" section containing both required and preferred bullet lists. Or we could have "Requirements" for required and "Qualifications" for preferred? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid using both Requirements and Qualifications. We'll include both if content exists. We have "Qualifications Required" and "Qualifications Preferred". So we can make a

Requirements

for required qualifications, and

Qualifications

for preferred qualifications. Or we could combine but better to follow instruction. We also have "Skills" maybe not explicitly listed; but we have technical mastery etc. Could be considered skills. However we already have qualifications covering skills. Might be redundant. Better to not add Skills if no explicit skills list separate. We have Pay: Base Salary Range: $144,000-$198,000. So we need a Pay section. We have Benefits: list under "How We Protect What Matters Most:" with numbered list of benefits. So Benefits section. Schedule: Not mentioned. So we should not include Schedule. We also have maybe "About the role" from the introductory paragraph and Job Summary. We'll include About the role. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: EEO, disability, accommodation, etc. Also remove "We are proud to be an equal opportunity workplace..." etc. Also remove "If applying for positions in the U.S., must be eligible to work in the U.S. without need for employer sponsored visa". Also remove "We believe our employees are our greatest resource..." etc. Also remove "GAF complies with federal, state, and local disability laws..." etc. Also remove "If a reasonable accommodation is needed..." etc. Also remove "We offer competitive salary, benefits, 401k, and vacation packages for all full time permanent positions." That's somewhat benefits but we already have benefits; but it's generic; we could keep but it's somewhat duplicate. Might be considered boilerplate. Safer to remove generic statements not specific. The specific benefits list is under "How We Protect What Matters Most:" which we will keep. We also need to preserve all substantive information: job summary, essential duties, qualifications required/preferred, pay range, benefits list. We must not invent or summarize away detail. So we need to keep the exact details as much as possible, but we can reformat into HTML. We need to use

• for any list of duties/requirements/benefits, and

  for prose. Thus: - About the role: prose from Job Summary and maybe intro paragraph? The intro paragraph about GAF culture is not directly about the role but could be considered "About the role"? Might be considered company overview. But we can include it as part of About the role prose. However we must not invent filler. The intro paragraph is substantive about company values; it's not boilerplate. It's okay to include. Thus About the role

  containing the intro paragraph plus Job Summary? The Job Summary is a separate paragraph: "The SAP Master Data Lead guides enterprise data quality, workflow design, and large-scale data migration for GAF SAP landscape. This role drives end-to-end data cleansing, constructs governance workflows within SAP Master Data Governance tools (Incture Cheeryworks), and leads cross-functional migration activities from legacy systems into SAP S/4HANA." We could combine them into one

  or separate

  s. The instruction: use

  for prose. So we can have multiple

  elements. Thus:

  About the role

  At GAF, we cover more than buildings. We cover each other. No matter what role, tenure, or track, under this roof you are empowered to be there for your teammates, your customers, and especially your community. Under this roof, we don’t back down from hard work– we support one another in pursuit of something bigger. We define the future while leading the present. And under this roof, we own our opportunities. Becoming the market leader only happens when everyone feels they have the opportunity, and the support, to thrive. We are GAF. And under this roof, we protect what matters most.

  The SAP Master Data Lead guides enterprise data quality, workflow design, and large-scale data migration for GAF SAP landscape. This role drives end-to-end data cleansing, constructs governance workflows within SAP Master Data Governance tools (Incture Cheeryworks), and leads cross-functional migration activities from legacy systems into SAP S/4HANA.

  Next Responsibilities: Essential Duties list. We need to turn each duty into
• . The duties are: - Data Migration & ETL: Define the enterprise data migration strategy, rules, and field mappings from legacy systems to SAP S/4HANA using SAP Data Services (BODS), Migration Cockpit, or SAP Advanced Data Migration (ADM). - MDG Workflow & Governance: Architecture and configuration of SAP MDG workflows, change requests, data validation rules, and custom data models across core domains (Customer, Vendor, Material, Financials). - Data Cleansing & Quality Management: Design automated data quality rules, profiling routines, and deduping methodologies to drive legacy data enrichment and remediation. - Cross-Functional Leadership: Partner with business process owners, functional consultants, and IT security teams to align master data design with operational requirements and regulatory compliance. - Execution & Testing: Lead data mock cuts, unit testing, integration testing (UAT), and cutover execution during go-live phases. We'll put under

  Responsibilities

  with each as
  • . Next Requirements: Qualifications Required list. We have: - Bachelor’s Degree Information Technology, Computer Science, Business Analytics, or equivalent practical experience. - 8+ years of hands-on experience in SAP Master Data Management, with at least 2 full-lifecycle SAP S/4HANA implementation or migration projects as a Lead. - Technical Mastery: Deep hands-on experience with SAP master data, SAP Migration Cockpit, SAP BODS/Information Steward, and legacy data transformation. Add on tools like Incture Cheeryworks. Experience of ALteryx as ETL is good to have. - Domain Expertise: Strong understanding of business processes surrounding Master Data domains (BP/Vendor/Customer, Material/MM, Finance/FI-CO). - Workflow Architecture: Proven ability to configure complex workflow, custom change request types, and dynamic routing in SAP MDG. We'll put each as
  • under

    Requirements

    . Next Qualifications: Qualifications Preferred list. We have: - SAP Master data migration tools - Experience with cloud data integration (SAP Integration Suite, BTP). - Knowledge of Agile project management frameworks (Scrum/SAFe). - SAP MDG or S/4HANA certifications. We'll put under

    Qualifications

    . Next Benefits: list under "How We Protect What Matters Most:" with numbered list. We need to convert to
    • . The list items: 1. We offer a wide range of health insurance options that include medical, dental, and vision for you and your family. 2. Our Family-Building benefits support the many different journeys to fertility and parenthood. 3. Our robust 401K plan includes an employer match contribution with your pre-tax and/or Roth contributions. 4. Other exciting programs and perks are available to help employees achieve work-life balance, including (but not limited to) a wellness program, free financial coaching, a referral program, and product rebates when purchased for an employee’s primary residence. 5. Professional growth and development are very important to us! We offer internal training programs and courses, as well as a generous tuition reimbursement program. 6. We're committed to fostering a culture that reflects our values to connect, empower, evolve, and inspire. We offer many opportunities for employees to connect with one another, including through our Employee Resource Groups who focus on education and allyship for all of our employees. We'll put under

      Benefits

      . Next Pay: Base Salary Range: $144,000-$198,000. We need a Pay section. The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. We have specific pay range, so we include Pay. We'll put

      Pay

      Base Salary Range: $144,000-$198,000

      . We should not include Schedule. We must not include any boilerplate like EEO, disability, accommodation, visa, etc. Also remove statements like "We believe our employees are our greatest resource..." etc. We also need to remove duplicated lines: there may be duplicate sentences about offering competitive salary etc. We'll omit. Now ensure we only output HTML fragment, no markdown fences. Let's craft final HTML. Check for any stray content: The intro paragraph includes "Under this roof, we don’t back down from hard work– we support one another in pursuit of something bigger." There's an en dash; fine. Make sure to escape any HTML special characters? The text includes apostrophes, etc. It's okay as plain text. We'll output:

      About the role

      At GAF, we cover more than buildings. We cover each other. No matter what role, tenure, or track, under this roof you are empowered to be there for your teammates, your customers, and especially your community. Under this roof, we don’t back down from hard work– we support one another in pursuit of something bigger. We define the future while leading the present. And under this roof, we own our opportunities. Becoming the market leader only happens when everyone feels they have the opportunity, and the support, to thrive. We are GAF. And under this roof, we protect what matters most.

      The SAP Master Data Lead guides enterprise data quality, workflow design, and large-scale data migration for GAF SAP landscape. This role drives end-to-end data cleansing, constructs governance workflows within SAP Master Data Governance tools (Incture Cheeryworks), and leads cross-functional migration activities from legacy systems into SAP S/4HANA.

      Responsibilities

      • Data Migration & ETL: Define the enterprise data migration strategy, rules, and field mappings from legacy systems to SAP S/4HANA using SAP Data Services (BODS), Migration Cockpit,