Oracle Fusion Global Trade Management (GTM) Lead

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description (role), responsibilities, qualifications (required and preferred), company overview, why work at Mythics (benefits). No explicit Pay or Schedule. So we can include About the role (maybe the initial paragraph), Responsibilities, Qualifications (maybe combine required and preferred?), Skills (maybe from qualifications?), Benefits (from why work at Mythics). We must not repeat job title. No metadata like Job ID. Must preserve all substantive info, not invent. Use

• for lists. Use

  for prose. We need to extract content. Let's parse: First paragraph: "In this role you own the design and configuration of Oracle Fusion Global Trade Management — export/import compliance screening, denied-party screening, HS/ECCN classification, and licensing determination — as part of the broader Fusion ERP transformation. Export control and trade compliance requirements (ITAR, EAR, OFAC) exist as policy defined by the Federal Compliance Lead and Legal/Export Compliance teams; this role is the functional and technical owner of how those requirements get built and enforced inside Fusion GTM, and how GTM integrates with Order Management, Procurement, and Shipping to actually stop a restricted transaction before it happens. This is a functional/configuration role, not a policy-authorship role. It's also distinct from the Security & Access Architect role — that role controls who can see data inside Fusion ; this role controls whether a transaction is legally permitted to happen at all , regardless of who's requesting it." That's about the role. Then "Key Responsibilities" heading with bullet list. We need to capture each bullet. Let's list responsibilities: - Lead configuration of Oracle Fusion GTM: trade compliance rules, restricted party screening, embargo/sanctions screening, license determination, and classification workflows - Configure HS/Schedule B and ECCN classification processes and maintain classification data governance - Design and configure automated screening against denied-party lists (Entity List, SDN, Debarred Persons List, etc.) integrated into order-to-cash and procure-to-pay transaction flows - Own license determination logic — when a transaction requires an export license, which license type applies, and how that gates order/shipment processing in Fusion - Trade Compliance Process Integration: Partner with Order Management, Procurement, and Shipping/Logistics functional leads to embed GTM screening and holds into standard transaction flows (order entry, PO creation, shipment release) - Define exception-handling and manual-review workflows for flagged transactions — who reviews, what evidence is required, how holds are released - Work with the Technical Architect to define integration points between GTM and upstream/downstream systems (freight forwarders, customs brokers, banking/LC systems) where trade documentation or screening data crosses system boundaries - Regulatory Translation (GTM-specific): Translate ITAR, EAR, and OFAC requirements — as interpreted by the Federal Compliance Lead and Legal — into specific GTM configuration: screening rule sets, classification hierarchies, and license workflows - Maintain traceability between regulatory requirement and GTM configuration (rule, screening list, license condition) so the config is defensible in an audit or DDTC/BIS review - Flag where a regulatory requirement can't be met through GTM configuration alone and needs a manual control or process outside Fusion - Testing & Go-Live Readiness: Develop and execute test scenarios validating screening accuracy, false-positive/false-negative handling, and license enforcement logic - Support data conversion and validation for restricted-party lists, classification data, and historical trade transaction data - Own the GTM Configuration-to-Regulatory-Requirement traceability matrix and support go-live readiness sign-off for trade compliance specifically Now Qualifications: Required Qualifications bullet list: - Clearance/Eligibility: Must be a U.S. Person (ITAR); ability to obtain clearance - Bachelor’s degree in Computer Science, Engineering, Information Systems, or a related technical field (or equivalent experience) - 16+ years of relevant professional experience. - 6+ years hands-on Oracle Fusion GTM (or Oracle Global Trade Management / prior EBS GTM) configuration and implementation experience - Working knowledge of ITAR, EAR, and OFAC requirements as they apply to system-enforced trade compliance — enough to configure to spec and flag gaps, not to author export-control policy - Experience configuring restricted-party screening, embargo/sanctions checks, and export license determination logic in an ERP trade compliance module - Experience integrating trade compliance screening into order-to-cash and/or procure-to-pay transaction flows - Familiarity with HS classification, ECCN, and Schedule B coding - Ability to translate export-control policy (defined by Legal/Compliance) into system configuration and defend that configuration in an audit context Preferred Qualifications bullet list: - Experience in a Defense Industrial Base, aerospace, defense, or manufacturing organization with active export licensing programs - Experience with Oracle Gov Cloud or other FedRAMP-authorized environments - Experience with DDTC (ITAR) or BIS (EAR) license application processes from the business side - Familiarity with customs brokerage, freight forwarding, or trade documentation systems and their integration into ERP - Experience with Fusion Order Management and/or Procurement configuration beyond GTM specifically - Certifications: Oracle Fusion SCM Cloud Certification (with GTM configuration experience specifically called out on resume/interview), or U.S. Export Control Professional certification (e.g., ECoP), or CCP (Certified Compliance Professional) with demonstrated GTM/trade compliance implementation experience Company Overview: description of Mythics. Why work at Mythics? Benefits: list: health, dental, vision coverage, paid time off and holidays, retirement options with employer matching, well-being programs, company-sponsored events, employee committees, volunteer opportunities, referral perks, recognition programs. Also mention drug-free workplace requirement, but that's maybe boilerplate? It's part of benefits? It's a requirement; but we can include as part of benefits? It's not a benefit but a condition. Might be considered boilerplate? It's a condition of employment; but it's not generic EEO; it's specific. Might keep as part of Benefits? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The drug-free workplace requirement is a legal requirement; might be considered boilerplate? It's a condition but not exactly EEO. Might be safe to include? Probably better to omit as it's a legal requirement. The benefits list is clear. We need to output sections: About the role, Responsibilities, Qualifications, Skills?, Benefits. Could also include Skills as separate if we have skill list; but qualifications already cover skills. Could combine Qualifications and Skills? The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include Qualifications and maybe Skills separate if we have distinct skill items. But we can also put skill list under Qualifications. Safer to include Qualifications only, and maybe Skills omitted if no distinct skill section. However we have skill-like items: familiarity with HS classification, ECCN, Schedule B coding; ability to translate policy; etc. Those are qualifications. So we can just have Qualifications. We need to preserve all substantive info. So include company overview and why work at Mythics (benefits). Could put company overview under About the role? Actually About the role already covered role description. Company overview is separate; we could add a section "About Mythics" but not in allowed headings. Allowed headings are limited to those list. Could we put company overview under About the role? Might be stretching. Better to include a section "About the role" for role description, and then maybe include company overview under "Benefits"? Not appropriate. Could we add a section "Company Overview" not in allowed list? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; but does not forbid other headings? It says use

  for section headings (e.g. ...). Likely they expect only those headings. So we should map content to those headings. Company overview could go under About the role? Might be okay to include as part of About the role? But About the role is about the role, not company. However we could treat "About the role" as including both role and company overview? Might be acceptable. Alternatively we could omit company overview if not covered by allowed headings. But we must preserve ALL substantive information; cannot omit company overview. So we need to fit it somewhere. Perhaps we can include a section "About the role" and then within that include both role description and company overview as paragraphs. That would preserve info. Similarly, "Why work at Mythics?" benefits can go under Benefits heading. Thus sections: About the role (includes role description + company overview), Responsibilities, Qualifications, Benefits. We must not include Pay or Schedule as no info. Now format. We'll produce:

  About the role

  In this role you own the design and configuration of Oracle Fusion Global Trade Management — export/import compliance screening, denied-party screening, HS/ECCN classification, and licensing determination — as part of the broader Fusion ERP transformation. Export control and trade compliance requirements (ITAR, EAR, OFAC) exist as policy defined by the Federal Compliance Lead and Legal/Export Compliance teams; this role is the functional and technical owner of how those requirements get built and enforced inside Fusion GTM, and how GTM integrates with Order Management, Procurement, and Shipping to actually stop a restricted transaction before it happens. This is a functional/configuration role, not a policy-authorship role. It's also distinct from the Security & Access Architect role — that role controls who can see data inside Fusion ; this role controls whether a transaction is legally permitted to happen at all , regardless of who's requesting it.

  Mythics brings together the expertise of Mythics, SpearMC, and Smart ERP to deliver end-to-end Oracle solutions across SaaS, PaaS, IaaS, on-premises technologies, PeopleSoft, and the broader Oracle application portfolio. With decades of specialized Oracle experience, national scale, and award-winning expertise across ERP, HCM, EPM, databases, infrastructure, and cloud, we serve as a single trusted partner throughout the entire technology lifecycle, from strategy and licensing to implementation, integration, managed services, and training. Our teams support organizations in government, defense, healthcare, higher education, and commercial industries, helping customers navigate complex, mission-critical environments with secure, reliable, and transformative solutions.

  Responsibilities

  • Lead configuration of Oracle Fusion GTM: trade compliance rules, restricted party screening, embargo/sanctions screening, license determination, and classification workflows
  • Configure HS/Schedule B and ECCN classification processes and maintain classification data governance
  • Design and configure automated screening against denied-party lists (Entity List, SDN, Debarred Persons List, etc.) integrated into order-to-cash and procure-to-pay transaction flows
  • Own license determination logic — when a transaction requires an export license, which license type applies, and how that gates order/shipment processing in Fusion
  • Trade Compliance Process Integration: Partner with Order Management, Procurement, and Shipping/Logistics functional leads to embed GTM screening and holds into standard transaction flows (order entry, PO creation, shipment release)
  • Define exception-handling and manual-review workflows for flagged transactions — who reviews, what evidence is required, how holds are released
  • Work with the Technical Architect to define integration points between GTM and upstream/downstream systems (freight forwarders, customs brokers, banking/LC systems) where trade documentation or screening data crosses system boundaries
  • Regulatory Translation (GTM-specific): Translate ITAR, EAR, and OFAC requirements —