Oracle ERP Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: company description, Who We Are, etc? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The company description and "Who We Are" might be considered boilerplate? It's not exactly legal/EEO but it's generic fluff. However we need to preserve ALL substantive information; do not invent or summarize away detail. The company description and "Who We Are" might be considered substantive? It's more about culture. The instruction says we should include sections only when posting has real specific content for it. The sections we can create: About the role (maybe from "What We Are Looking For" and description), Responsibilities (from "What You Will Do"), Requirements (from "What We Require"), Qualifications (maybe Preferred Qualifications), Skills (maybe from requirements), Benefits (from "What We Provide": Salaried, DOE, Relocation available, Full-Time, Full Benefits Package Available). Pay: not specified (just "Salaried, DOE" which is vague; DOE means depends on experience; that's not a specific pay figure; we should not create Pay section unless posting actually states them. It says "Salaried, DOE" - that's not a specific number; it's vague. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "DOE" is similar to depends on experience, which is placeholder. So we should not create Pay section. Schedule: "required to be onsite at our Durham office 3 days a week." That's schedule info (onsite 3 days a week). So we can include Schedule section. Benefits: "Full Benefits Package Available" plus "Relocation available", "Full-Time". That's specific enough? It says "Full Benefits Package Available" - that's vague but indicates benefits exist. Might be considered placeholder? It's not specific like health, dental, 401k. But it's still a statement that benefits are provided. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Full Benefits Package Available" is not exactly placeholder like "varies". It's a statement that benefits are provided. I'd include Benefits section. We also need to include maybe "About the role" summarizing the role description. The posting includes "What We Are Looking For" which describes the role. That's substantive. We need to use

for section headings. Use

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

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include details from responsibilities, requirements, preferred qualifications, benefits, schedule. We must not include duplicated lines. Also remove boilerplate like company description, Who We Are, etc. Also remove EEO statements etc. Thus final HTML fragment will contain sections: About the role (maybe from "What We Are Looking For"), Responsibilities (from "What You Will Do"), Requirements (from "What We Require"), Qualifications (maybe Preferred Qualifications), Benefits (from "What We Provide"), Schedule (onsite 3 days a week). Possibly Skills could be merged into Requirements; but we can keep Requirements and Qualifications separate. We need to ensure we don't create empty sections. Let's extract content. About the role: The paragraph under "What We Are Looking For": "Aspida is seeking a skilled, self-motivated, and independent ERP professional for the role of Oracle ERP Manager. The Oracle EPM Manager leads the functional design, configuration, and support of Oracle Fusion Cloud applications (primarily Financials) across the organization. This role manages a distributed, overseas team of functional analysts and third-party consultants, ensuring the delivery of high-quality solutions, effective support operations, and continuous improvement of Oracle Fusion capabilities. The position reports to the Director, Financial Systems, and serves as a key liaison between business stakeholders, IT, and external implementation partners. This role reports to the to the Director of Finance Systems and is required to be onsite at our Durham office 3 days a week." Note duplicate "reports to". We'll keep but maybe combine. We should not repeat job title as heading; but we can include description. We'll put this in

  . Responsibilities: bullet list from "What You Will Do" sections: Functional Oracle Fusion Ownership, Project & Release Management, Support & Governance, Stakeholder Collaboration. Each has sub-bullets. We need to turn each duty into

• . Could group under headings? But we only have

  for section headings, not subheadings. We can just list all responsibilities as

  items. Let's extract each bullet: Functional Oracle Fusion Ownership: - Serve as the functional subject matter expert for Oracle Fusion Cloud modules (e.g., General Ledger, Accounts Payable, Fixed Assets, Cash Management, Procurement, or other relevant modules). - Lead requirements gathering, functional design, configuration, and testing for enhancements, projects, and quarterly Oracle releases. - Translate business requirements into functional specifications and oversee their technical implementation in partnership with IT/technical teams. - Own the functional roadmap for Oracle Fusion applications, identifying opportunities to improve processes, automate workflows, and increase system adoption. Project & Release Management: - Manage project plans, timelines, and deliverables for Oracle Fusion-related initiatives, including new module rollouts, integrations, and process improvements. - Coordinate Oracle quarterly update testing and regression testing cycles with the team and business stakeholders. - Manage relationships with Oracle and third-party implementation/consulting partners, including contract deliverables and SOWs. Support & Governance: - Oversee day-to-day functional support operations across the financial systems landscape — including Oracle Fusion (GL, AP, Procurement, Cash Management) and other finance-related applications and integrations — ensuring timely resolution of incidents and service requests (SLAs/KPIs). - Establish and enforce change control, configuration governance, and documentation standards across all financial systems, not limited to Oracle Fusion. - Partner with the Director, Financial Systems, on budget planning, resource forecasting, and reporting on team performance and project status across the broader financial systems portfolio. - Monitor the health and performance of interfaces and integrations between Oracle Fusion and other upstream/downstream financial systems (e.g., banking platforms, expense management, tax, treasury, or reporting tools), coordinating with relevant system owners as needed. - Support audit, compliance, and internal controls requirements as they relate to financial systems configuration, access, and data integrity. Stakeholder Collaboration: - Act as the primary point of contact between Finance business users, IT, and external consultants for Oracle Fusion functional matters. - Present project updates, risks, and recommendations to senior leadership as needed. - Ensure alignment between global process standards and local/regional business requirements where applicable. We'll put these as

  under a

  . Requirements: from "What We Require:" list: - Bachelor's degree in Finance, Accounting, Information Systems, Business Administration, or related field (or equivalent experience). - 7+ years of experience with Oracle Fusion Cloud Applications (Financials preferred), including at least 3+ years in a functional lead or managerial capacity. - Demonstrated experience managing teams and/or consultants located in different time zones/geographies. - Strong knowledge of Oracle Fusion Financials modules configuration, testing, and support processes. - Experience managing full project lifecycles, including requirements gathering, design, testing, and deployment. - Excellent communication skills, with experience presenting to and influencing senior stakeholders. - Strong vendor/consultant management experience, including SOW and deliverable oversight. We'll put as
  • . Qualifications (Preferred): from "Preferred Qualifications": - Oracle Fusion certifications in relevant Financials modules. - Experience with Oracle Fusion integrations (e.g., OIC, FBDI/ADFdi, REST/SOAP APIs). - Experience with Agile or hybrid project management methodologies. - Prior experience in a shared services or global business services (GBS) environment. - Familiarity with related Oracle Cloud modules (Procurement, Financial Management) a plus. We'll put as
    • . Benefits: from "What We Provide": "Salaried, DOERelocation availableFull-TimeFull Benefits Package Available". The text seems concatenated: "Salaried, DOERelocation availableFull-TimeFull Benefits Package Available". Likely missing spaces. We need to parse: Salaried, DOE; Relocation available; Full-Time; Full Benefits Package Available. We'll create
      • Salaried (DOE)
      • Relocation available
      • Full-Time
      • Full Benefits Package Available
      . But DOE is placeholder; we might avoid Pay section but we can include Salaried, DOE as part of Benefits? Actually Salaried is compensation type; but we decided not to create Pay section because it's vague. However we can still mention Salaried within Benefits? The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits section is allowed because they state "Full Benefits Package Available". Salaried, DOE is compensation; but we could include it in Benefits? Might be considered Pay. Safer to not include Salaried, DOE anywhere? But we need to preserve ALL substantive information. If we omit Salaried, DOE we lose info. However we could include it in a

      within Benefits section? The rule says never create Pay section unless posting actually states them. It does state "Salaried, DOE". That's a statement about pay type (salaried) and that it's DOE (depends on experience). That's still somewhat vague but it's a statement. The rule about placeholder text: "commensurate with experience", "not specified", "N/A", "varies", "TBD". "DOE" is similar to depends on experience, which is arguably placeholder. Might be considered filler. Safer to not create Pay section, but we could still mention "Salaried" in a

      under Benefits? Might be confusing. Alternatively we could include a short

      that says "Position is salaried (DOE)." That's not a heading; it's just prose. The rule about sections: we should not create Pay section heading. So we can include that info in a paragraph within Benefits or maybe in About the role. Let's add a

      under Benefits: "Position is salaried (DOE)." That preserves info without a Pay heading. Schedule: "required to be onsite at our Durham office 3 days a week." We'll create Schedule section with

      or

      . Since it's a single statement, use

      . Now we need to output only HTML fragment, no /, no markdown. Let's craft:

      About the role

      Aspida is seeking a skilled, self-motivated, and independent ERP professional for the role of Oracle ERP Manager. The Oracle EPM Manager leads the functional design, configuration, and support of Oracle Fusion Cloud applications (primarily Financials) across the organization. This role manages a distributed, overseas team of functional analysts and third-party consultants, ensuring the delivery of high-quality solutions, effective support operations, and continuous improvement of Oracle Fusion capabilities. The position reports to the Director, Financial Systems, and serves as a key liaison between business stakeholders, IT, and external implementation partners. This role reports to the Director of Finance Systems and is required to be onsite at our Durham office 3 days a week.

      Responsibilities

      • Serve as the functional subject matter expert for