SAP EHS

Client is running a 4.6C box from Dupont, but their EHS is spread across 4.6C and an ECC box.  There were certain things you could not do in 4.6C and the is why they stood up the ECC box.  The job detail below reads 4.6C, but as I mentioned above, it is split between 4.6C and ECC.
 

• Provide functional and technical ownership for SAP EHS solutions supporting environmental, health, safety, product compliance, and manufacturing-related processes.
• Partner with EHS, manufacturing, site operations, engineering, and IT stakeholders to translate business requirements into supportable SAP solutions.
• Participate in workshops and presentations to validate and improve system design, process controls, data quality, and user experience.
• Configure, test, document, deploy, and support SAP EHS functionality in the SAP 4.6c environment, following applicable change-management and validation practices.
• Analyze incidents and recurring system issues; coordinate resolution across internal teams and external service providers; and support root-cause and corrective-action activities.
• Maintain solution documentation, functional specifications, configuration records, test evidence, operating procedures, and knowledge-transfer materials.
• Support integrations and data flows between SAP EHS, SAP manufacturing processes, and connected applications, including investigation of interface and master-data issues.
• Plan and execute unit, integration, regression, and user-acceptance testing in partnership with business stakeholders.
• Assess requested enhancements for business value, risk, architectural fit, supportability, and alignment with application-lifecycle priorities.
• Support audit, compliance, access-control, and data-retention needs by providing accurate system documentation and evidence within the role’s area of responsibility.
• Provide production support, participate in major incident response when required, and help ensure reliable service for global business and site users.
• Build internal capability through cross-training, knowledge sharing, and clear escalation paths to reduce single-person dependency.