Principal Systems Analyst - Supply Chain/SAP

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc as headings; can fold minor metadata into short

or drop it. We need to preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO etc). The posting includes many paragraphs about company description, flexible/hybrid schedule, location, work authorization, duties & responsibilities, qualifications, preferred qualifications, salary range, and some culture statements. We need to decide sections: About the role (maybe a summary), Responsibilities (duties), Requirements (maybe qualifications?), Qualifications (maybe separate?), Skills (maybe combine?), Benefits (maybe not explicit), Pay (salary range), Schedule (flexible/hybrid). The posting mentions "Our flexible/ hybrid work schedule includes 3 in-person days at one of our core locations and 2 remote days. Our core office location is Salisbury, NC." So schedule section. Salary range is given: $136,160-$204,240. Benefits: Not explicitly listed; there is a paragraph about culture, values, etc but not specific benefits like health insurance, 401k. Probably we should not create Benefits section unless posting actually states them. It does not list benefits, so omit. Skills: Could extract from qualifications: strong understanding of enterprise application integrations, APIs, data mapping, system interfaces; strong analytical, problem-solving, facilitation, documentation skills; ability to communicate effectively; experience supporting large-scale enterprise transformation programs; etc. Could put under Skills. Qualifications: Bachelor's degree..., 8+ years experience, etc. Also Preferred Qualifications. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info; do not invent or summarize away detail. So we need to include all duties, qualifications, preferred qualifications, schedule, salary, location, work auth, company description maybe under About the role. We must not repeat job title as heading. The job title is Principal Systems Analyst (implied). Not to repeat. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

About the role

... company description and role purpose ...

Responsibilities

• ... each duty ...

Qualifications

• ... required qualifications ...

Preferred Qualifications

• ... preferred ...

Skills

• ... skills ...

Pay

Salary range: $136,160‑$204,240.

Schedule

Flexible/hybrid schedule: 3 in‑person days at the Salisbury, NC office and 2 remote days per week.

We might also include location and work auth under About the role or a separate section like "Location & Eligibility". But we only have headings list; we could add a short paragraph under About the role. We must not create sections with filler. Ensure we include all substantive info from duties, qualifications, preferred qualifications, skills, schedule, pay. Let's extract duties from the "Duties & Responsibilities:" paragraph. It's a long sentence with many items separated by periods. We need to break into list items preserving detail. We'll parse: - Lead requirements gathering workshops with Supply Chain, Distribution, Transportation, Procurement, Inventory Management, and Planning stakeholders to document current-state and future-state business processes. - Analyze, document, and maintain business requirements, process flows, user stories, functional specifications, and system interaction diagrams supporting SAP S/4HANA and boundary applications. - Partner with business teams, architects, developers, and system integrators to define scalable solutions supporting procurement, inventory management, replenishment, warehouse operations, transportation, and store supply processes. - Support integration analysis and design activities across SAP, Planning systems, Manhattan WMS, TMS, EDI platforms, and other supply chain applications by documenting interfaces, data mappings, business rules, and exception handling requirements. - Strong understanding of negative inventory processes, including business use cases, inventory accuracy implications, replenishment impacts, ATP considerations, Allocation, Reverse Logistics, financial valuation impacts, and inventory control governance. - Strong knowledge of intercompany and intracompany stock transfer processes, including DC-to-DC, DC-to-Store, cross-company code transfers, ownership changes, inventory valuation impacts, and associated financial postings. - Experience working in coexistence environments where legacy applications and SAP S/4HANA operate simultaneously, including process ownership, data synchronization, inventory reconciliation, and integration management across boundary systems. - Experience facilitating current-state, coexistence-state, and future-state process design workshops, including identification of process gaps, system ownership, integration dependencies, transition strategies, and business readiness requirements. - Strong understanding of Supply Chain master data dependencies and their impact on replenishment, procurement, inventory management, warehouse operations, transportation, and financial processes. - Experience with retail supply chain planning solutions such as RELEX and integration with SAP, WMS, TMS, EDI, and other boundary applications. - Conduct impact assessments for process, master data, configuration, and integration changes to ensure alignment across supply chain systems and business functions. - Collaborate with Product Owners, Functional Leads, Enterprise Architects, and Development teams to prioritize requirements, manage dependencies, and support solution delivery. - Develop and execute test strategies, test scenarios, and business validation activities, including System Integration Testing (SIT), User Acceptance Testing (UAT), and defect triage support. - Support master data governance activities related to Business partners, Article, Vendor, Location, Transportation, and Inventory Planning data to ensure data quality and process consistency. - Identify opportunities for process optimization, automation, inventory accuracy improvements, and operational efficiencies through technology and process enhancements and AI Capabilities. - Participate in strategic transformation programs by supporting Process Design Documents (PDDs), Key Design Decisions (KDDs), RICEFW requirements, solution reviews, and go-live readiness activities. - Ensure compliance with project governance standards, documentation requirements, change management processes, and enterprise architecture principles. That's a lot; we need to keep all. Qualifications: Bachelor's degree in information systems, Computer Science, Supply Chain, Business Administration, or equivalent work experience. 8+ years of experience as a Business Systems Analyst, Functional Analyst, Systems Analyst, or related role. Experience gathering and documenting complex business and system requirements. Strong understanding of enterprise application integrations, APIs, data mapping, and system interfaces. Experience working with cross-functional teams in Agile, Waterfall, or hybrid delivery environments. Strong analytical, problem-solving, facilitation, and documentation skills. Ability to communicate effectively with business stakeholders, technical teams, and senior leadership. Experience supporting large-scale enterprise transformation programs. Preferred Qualifications: Experience with SAP S/4HANA, particularly OTC, PTP, Inventory Management, or Supply Chain processes. Experience with Retail, Grocery, Distribution, Supply Chain, Warehouse Management, or Transportation Management environments. Familiarity with planning and replenishment solutions such as RELEX, Blue Yonder, or similar platforms. Experience with WMS, TMS, EDI, middleware, or integration platforms. Knowledge of master data governance, data management, and business process modeling. Experience creating process flows using Visio, Signavio, or similar tools. Experience supporting enterprise transformation programs involving multiple boundary systems and cross-functional processes. Skills: Could be derived from qualifications and responsibilities: strong understanding of enterprise application integrations, APIs, data mapping, system interfaces; strong analytical, problem-solving, facilitation, documentation skills; ability to communicate effectively; experience supporting large-scale enterprise transformation programs; etc. We'll list them. Now About the role: Should include company description and role purpose. The posting includes: "Ahold Delhaize USA, a division of global food retailer Ahold Delhaize, is part of the U.S. family of brands, which includes five leading omnichannel grocery brands - Food Lion, Giant Food, The GIANT Company, Hannaford and Stop & Shop. Our associates support the brands with a wide range of services, including Finance, Legal, Sustainability, Commercial, Digital and E-commerce, Technology and more. The Principal Systems Analyst is responsible for leading the analysis, design, and continuous improvement of supply chain business processes and technology solutions. This role enables end-to-end integration across SAP S/4HANA, and Boundary systems such as planning, warehouse, transportation, and vendor systems to support efficient inventory flow from supplier to distribution center and store. Working closely with business and IT stakeholders, the analyst ensures solutions are scalable, integrated, and aligned with strategic transformation objectives. The position contributes to operational excellence through strong process knowledge, system expertise, and effective stakeholder collaboration." Also location and work auth: "Our flexible/ hybrid work schedule includes 3 in-person days at one of our core locations and 2 remote days. Our core office location is Salisbury, NC. Applicants must be currently authorized to work in the United States on a full-time basis." We could put location and auth under About the role or separate. Since we have Schedule section, we can mention location there. Work auth maybe also in About the role. Let's craft About the role paragraph: combine company description and role purpose. Now produce HTML. Be careful to escape any special characters like &, <, >. Use & for &, etc. In text we have "S/4HANA" includes slash, fine. "OTC, PTP". "DC-to-DC". Use hyphens fine. "RICEFW". No issues. We need to ensure we don't accidentally include HTML tags inside text that could be misinterpreted. We'll just output as plain text inside

or

. Let's construct. We'll start with

About the role

...

Then

Responsibilities

...

Then

Qualifications

...

Then

Preferred Qualifications

...

Then

Skills

...

Then

Pay

Salary range: $136,160‑$204,240.

(use en dash or hyphen? Use hyphen.) Then

Schedule

Flexible/hybrid schedule: 3 in‑person days at the Salisbury, NC office and 2 remote days per week.

We must not include any extra sections like Benefits. Now ensure we didn't miss any substantive info: The company description about values etc at end: "At Ahold Delhaize USA, we provide services ... We thrive on supporting great local grocery brands and their strategies. Our associates are the heartbeat of our organization. We are committed to offering a welcoming work environment where all associates can succeed and thrive. Guided by our values of courage, care, teamwork, integrity (and even a little humor), we are dedicated to being a great place to work. We believe in collaboration, curiosity, and continuous learning in all that we think, create and do. While building a culture where personal and professional growth are just as important as business growth, we invest in our people, empowering them to learn, grow and deliver at all levels of the business." This is substantive but maybe could be part of About the role or a separate section like "Culture". However we only have allowed headings list; we could add a section "About the company" but not in list. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

for section headings (e.g. About the role, Responsibilities,