SAP Architect - Order to Cash & Transportation Management

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes Position Overview (we can map to About the role). Responsibilities (Key Responsibilities). Qualifications (Required Qualifications, Preferred Qualifications). Skills maybe from competencies? There's a "Key Competencies" section. Could map to Skills. Benefits, Pay, Schedule not present, so omit. Also need to include maybe a short paragraph for metadata like Job ID? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a

with Job ID: 528900 maybe. Also the first line "CRH's Americas Materials business is the leading provider..." is part of overview; we can include in About the role. We must preserve all substantive information, not invent or summarize away detail. Must not omit details. However we need to format into sections with headings and lists where appropriate. Must not create sections with filler. Must not repeat job title as heading (the page already shows it). No job title given explicitly; we can ignore. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

Job ID: 528900

About the role

CRH's Americas Materials business is the leading provider of building materials in North America. The aggregates, asphalt, ready mixed concrete, paving and construction services we deliver are critical to building our world. Our operations span 45 U.S. states and two Canadian provinces with over 30,000 employees across 1,700 operating locations. Position Overview We are seeking an experienced SAP Architect to own the technical design and solution architecture of the Order to Cash (O2C) and Transportation Management (TM) landscape. This is a hands-on, deeply technical role: the ideal candidate can design integration architecture across IDocs, APIs, and middleware, and translate complex business requirements into scalable, debug pricing and output determination at the requirement-routine level, well-governed SAP configuration and custom development. The candidate has a proven track record architecting integrations between SAP, Point-of-Sale (POS) systems, Salesforce, and eCommerce platforms, and is comfortable owning end-to-end technical design authority across SD, pricing, billing, credit management, and TM. This is also a business-facing role: the successful candidate will spend significant time with Sales, Finance, Logistics, and Customer Service leaders and technical teams, translating current- and future-state process requirements into system architecture, data models, and integration designs. As technical design owner, this person will lead architecture and design workshops, produce solution and technical specification documents, review custom developments for quality and performance, and drive continuous improvement across the order-to-cash and transportation technical stack, while guiding a team of SAP O2C and TM functional and technical resources.

But that is a huge paragraph; we might break into multiple paragraphs for readability but still preserve content. However we must not invent or summarize away detail. We can keep as one paragraph; it's okay. Then Responsibilities: we need to list duties. The responsibilities section includes many bullet-like sentences. We'll create

• for each essential duty. We need to capture all responsibilities. The text includes sections: Solution Architecture & Technical Design (with sub-bullets), Driving Architecture & Design Workshops, Order to Cash – Technical Ownership, Transportation Management – Technical Ownership, Customer Payment Portal – Technical Design, Integration Architecture – POS, Salesforce & eCommerce, Team & Stakeholder Management, Project & Change Management. We'll create list items for each bullet point (maybe each sentence). Must preserve all substantive info; we can break into multiple list items but ensure we don't lose any detail. We'll need to be careful not to omit any details. Let's extract responsibilities: From "Solution Archietecture & Technical Design" (typo). Points: - Act as the primary technical design authority for O2C and TM — owning the target-state system architecture, data flows, and integration blueprint across SD, pricing, billing, credit management, and TM. - Translate business requirements into functional and technical specifications, including data models, interface specs (IDoc/BAPI/API), enhancement design (user exits, BAdIs, requirement routines), and custom program specs for ABAP development teams. - Own the architecture decision log for O2C/TM: document design alternatives, trade-offs, and rationale for configuration vs. enhancement vs. custom development, and maintain a single source of truth for the solution. - Define and track technical health metrics jointly with business owners (e.g., order cycle time, DSO, freight cost per shipment, on-time delivery, batch job runtime, interface error rates) and report progress on a regular cadence. - Establish and run a standing architecture governance forum (e.g., monthly O2C/TM design review) to review custom developments, RFCs, and technical debt, and to keep design decisions transparent and traceable. "Driving Architecture & Design Workshops": - Own end-to-end workshop planning and delivery for technical design sessions: define objectives, identify the right business and technical stakeholders, build the agenda, and drive to documented, signed-off design decisions. - Plan and facilitate requirements-gathering, fit-gap, and solution/technical design workshops with cross-functional stakeholders across Sales, Finance, Logistics, Customer Service, and IT. - Present design options with clear technical trade-offs (performance, maintainability, upgrade impact, licensing) and drive alignment on configuration and custom development approaches. - Use visual facilitation techniques (process maps, data flow diagrams, sequence diagrams, whiteboarding) to help both business and technical stakeholders see and agree on the proposed design in real time. - Manage constructive conflict in workshops between functional priorities (Sales vs. Finance vs. Logistics) and technical constraints (performance, security, upgrade compatibility) to reach a workable, endorsed technical outcome. "Order to Cash (O2C) – Technical Ownership": - Own the end-to-end technical architecture of SAP O2C, including sales order management, pricing engine configuration, credit management (FSCM), billing/invoicing, and accounts receivable data flows. - Design and troubleshoot SAP SD configuration at a deep technical level: order types, item categories, schedule line categories, copy control, delivery processing, shipping point determination, and output determination (NAST/BRFplus). - Architect SAP pricing at the technical level: pricing procedures, condition tables/access sequences, condition records, requirement and formula routines (VOFM), and custom pricing logic (user exits/BAdIs) to support accurate, consistent pricing across channels. - Partner with Finance and Sales Operations to design system-level solutions that streamline order management, reduce billing errors, and improve DSO, including root-cause technical analysis of recurring order/billing exceptions. "Transportation Management ™ - Technical Ownership": - Own the technical architecture of SAP Transportation Management, including freight planning, carrier/rate determination, freight settlement and hauler payment integration. - Design the technical integration between TM, O2C, and SD (order/delivery/freight document flow, TM-ERP integration via qRFC/SAP TM embedded architecture) to ensure order, delivery, and freight data remain consistent end-to-end. - Partner with Logistics and Supply Chain teams to architect optimized transportation processes, including rate tables, and freight cost allocation rules. - Support continuous improvement initiatives by analyzing technical performance data (freight cost variance, interface latency) and driving root-cause resolution. "Customer Payment Portal – Technical Design": - Own the technical design of customer-facing payment portal integration with SAP, including data mapping, API contracts, and reconciliation logic between portal and SAP FI/AR. - Architect and troubleshoot synchronization between portal transactions (payments, invoices, statements, disputes) and SAP financial records, including error handling, retry logic, and idempotency for financial transactions. - Drive functional enhancements to improve customer self-service capabilities (invoice viewing, online payments, payment history), including API performance tuning and secure handling of payment data (PCI-DSS considerations). "Integration Architecture – POS, Salesforce & eCommerce": - Architect and support integrations between SAP and Point of Sale (POS) systems, defining message structures, interface frequency, error handling, and reconciliation logic for order, inventory, and transaction data. - Own the technical design of the SAP–Salesforce integration (e.g., via middleware, standard connectors, or custom APIs), ensuring accurate, low-latency flow of accounts, opportunities, quotes, and orders into SAP for fulfillment and billing. - Design and support integration between SAP and eCommerce platforms, including real-time and batch interfaces for payments, invoices, and statements, and defining monitoring/alerting for interface health. - Lead deep technical troubleshooting of integration issues across middleware, APIs, IDocs, and point-to-point interfaces, performing root-cause analysis (trace/debug at ABAP, IDoc, and API-log level) and coordinating resolution with technical teams and vendors. - Define and enforce integration architecture standards: error/exception handling, monitoring and alerting, idempotency, retry/backoff strategy, and data reconciliation across all O2C/TM interfaces. "Team & Stakeholder Management": - Lead, mentor, and develop a team of SAP O2C/TM functional analysts, technical consultants, and ABAP developers, reviewing designs and code for quality, performance, and standards compliance. - Act as the primary technical liaison between business stakeholders (Sales, Finance, Logistics, Customer Service) and enterprise architecture, infrastructure, and security teams. - Manage vendor and implementation partner relationships for O2C, TM, payment portal, and integration projects, including technical review of vendor-delivered designs and code. - Prepare and present technical roadmaps, architecture reviews, and risk assessments to senior leadership and enterprise architecture governance boards. "Project & Change Management": - Lead technical design and delivery of SAP O2C and TM enhancement projects, upgrades, and rollouts, including solution architecture, technical specifications, unit/integration testing strategy, and deployment planning. - Ensure proper documentation of technical architecture, configuration, custom code, and interface specifications in a maintainable, auditable form. - Drive adherence to change management, transport/release governance, and code quality standards (code review, performance testing, regression testing). - Support audits and ensure SOX/internal controls compliance across O2C/TM technical processes, including segregation of duties in custom developments and interfaces. Now Qualifications: Required Qualifications and Preferred Qualifications. Required: - Bachelor's degree in Information Technology, Computer Science, Supply Chain, or equivalent experience. - 15+ years of overall SAP experience, with 5+ years in a technical architect, lead, or senior technical design capacity. - Deep hands-on technical expertise in SAP Order to Cash (O2C) and SAP Transportation Management (TM), including order management, pricing, billing, accounts receivable, freight and hauler payments — at both configuration and technical/ABAP level. - Strong working knowledge of ABAP sufficient to read, debug, and review custom code (user exits, BAdIs, enhancement points, reports, and interfaces); does not need to be a full-time developer, but must be technically credible in code reviews. - Expert-level experience configuring SAP pricing procedures and condition technique, including condition tables, access sequences, and requirement/formula routines (VOFM). - Demonstrated experience designing customer payment portal integrations with SAP at a technical/data-architecture level. - Experience architecting integrations between SAP and Point of Sale (POS) systems, Command Alkon, Salesforce, and eCommerce platforms. - Strong technical understanding of SAP integration technologies (IDocs, BAPIs/RFCs, REST/SOAP APIs, middleware such as SAP PI/PO, CPI, or third-party iPaaS tools), including message design, error handling, and monitoring. - Excellent stakeholder management, technical communication, and leadership skills — able to flex between architecture diagrams with technical teams and process narratives with business leaders. Preferred: - Experience with SAP S/4HANA, including CDS views, embedded analytics, and Fiori/UI5 extensibility for O2C/TM. - SAP certification(s) in SD, TM, or related modules; ABAP certification