Oracle E-Business Suite Financials Developer

Job Description

Location is Central New Jersey with a hybrid on-site expectation; candidates should be within commuting range or open to relocation.

\n

\n

Work authorization for U.S.-based employment will be confirmed as part of screening.

\n

\n

Oracle E-Business Suite Financials Developer

\n

\n

Manufacturing Client

\n

\n

Reports to: IT / ERP Delivery Lead | Location: Central New Jersey (hybrid) |

\n

\n

About the role

\n

A technical Oracle E-Business Suite team is building and extending the Financials platform that runs the business — the ledgers, payables, receivables, assets, and cash processes that have to be right and have to be on time. This is a hands-on development role . You will write production code against a live R12 Financials environment, build the interfaces that connect it to the rest of the enterprise, and work shoulder-to-shoulder with the functional team to turn business requirements into working, supportable software.

\n

\n

We are looking for a developer who already lives in Oracle EBS Financials — someone who can open a package, trace a problem across GL, AP, AR, and the sub-ledgers, and ship a fix or an enhancement with confidence. The strongest people we talk to treat Financials as an engineering discipline: clean PL/SQL, well-behaved interfaces, and changes you can stand behind.

\n

\n

The opportunity

\n

You will own real development across the Financials footprint — RICE/CEMLI components, conversions, interfaces, reports, and extensions — and partner with functional analysts to deliver change that customers of the system feel directly. The work is varied: a payables interface this sprint, an AutoInvoice or Lockbox issue the next, a BI Publisher statement after that. The core requirement is strong Oracle EBS Financials engineering judgment and the discipline to deliver it reliably.

\n

\n

This is a seat for someone energetic who takes a hard problem and drives it to completion.

\n

Three essential qualifications

\n

\n
1. You have recently done hands-on Oracle EBS Financials development. You work directly in R12 Financials — General Ledger, Accounts Payable, Accounts Receivable, Fixed Assets, Cash Management, and Sub-ledger Accounting — and can point to RICE/CEMLI components, interfaces, conversions, or extensions you personally built or fixed.
\n
2. You are a strong programmer, with PL/SQL and SQL at the core. You write clean, performant PL/SQL and SQL every day, and you can build and troubleshoot the surrounding stack — packages, concurrent programs, Forms/Reports, BI/XML Publisher, OAF, Workflow/AME, WebADI. You can also work in Java and Python where the job calls for it.
\n
3. You build external interfaces with the functional team. You translate business requirements into working integrations — including REST API interfaces to and from EBS — and you collaborate closely with functional analysts rather than working in isolation.
\n

\n

\n

What you will own

\n

Financials development and modules

\n

\n
• Design, build, and maintain RICE/CEMLI components across GL, AP, AR, FA, CM, and SLA — interfaces, conversions, extensions, custom packages, and reports.
\n
• Handle the Financials work that has to be right: AutoInvoice, Lockbox, bank and payment interfaces, period-close support, reconciliations, and statement/BI Publisher reporting.
\n
• Diagnose and resolve issues that cross modules and components, from the application layer down to the data.
\n

\n

\n

Interfaces and integration

\n

\n
• Build and maintain inbound and outbound interfaces, including REST API integrations with enterprise and third-party systems, working from requirements set with the functional team.
\n
• Ensure interfaces are reliable, restartable, and observable — with sensible error handling and clear evidence of what moved and what failed.
\n

\n

\n

Quality, delivery, and collaboration

\n

\n
• Turn functional specifications into scoped, estimated, deliverable work, and take direct ownership of difficult or time-sensitive items.
\n
• Follow sound source control, code review, and migration practice; write for maintainability so the next developer can pick up your work.
\n
• Partner with functional analysts, DBAs, and business users through build, test, and release.
\n

\n

\n

Product and technical context

\n

The environment is Oracle E-Business Suite R12 Financials , with the full developer toolset: PL/SQL, Forms and Reports, BI/XML Publisher, OAF, Workflow and AME, WebADI, concurrent programs, and ORDS/REST web services. You will lead hands-on delivery across the Financials modules with support from functional and DBA colleagues. Deep expertise in every peripheral technology is not required; strong EBS Financials engineering and the ability to learn the surrounding stack carry the most weight.

\n

\n

Supporting technical skills

\n

\n
• Strong fundamentals in Oracle EBS R12 Financials development: PL/SQL, SQL, RICE/CEMLI, interfaces, conversions, extensions, concurrent programs.
\n
• Reporting and UI extension: BI/XML Publisher, Forms/Reports, OAF; Workflow/AME; WebADI.
\n
• Integration: REST/ORDS web services, Integrated SOA Gateway or equivalent; inbound/outbound interface design.
\n
• Working ability in Java and Python; comfort with source control and standard migration/release practice.
\n
• The judgment to balance speed with reliability, and to explain technical tradeoffs clearly to a functional audience.
\n

\n

\n

Preferred experience

\n

These are advantages, not prerequisites. Demonstrated hands-on EBS Financials delivery and current coding ability carry the most weight.

\n

\n
• AI / Google Cloud Platform workflow automation — interest and aptitude in using AI to set up or improve workflow processes (e.g., GCP / Vertex AI). We will support the right person in growing this; appetite to learn matters more than prior depth.
\n
• Oracle ERP Cloud (Fusion) Financials exposure — a significant advantage.
\n
• Oracle APEX; additional integration or middleware experience.
\n
• Financial-services, healthcare, or other regulated or high-volume transaction environments.
\n
• Experience improving delivery in a lean team supporting live, business-critical systems.
\n

\n

\n

Working relationships

\n

You report to the ERP delivery lead and work day-to-day with the functional/business -analyst team, DBAs, and business users. You own implementation decisions within agreed architecture and standards, code quality, and the engineering readiness of what you ship. Priorities and business acceptance are set with functional and business leadership; you translate those into executable development.

\n

\n

What success looks like

\n

First 30 days: Learn the Financials footprint, the codebase, and the team's delivery and migration practices; begin contributing production code and resolving assigned issues across the modules.

\n

By 60 days: Own a meaningful slice of Financials development end-to-end — from functional spec through build, test, and release — with clean, reviewable code and dependable interfaces.

\n

By 90 days: Deliver consistently against commitments with fewer defects and reliable interfaces, and be the person the team trusts with difficult or time-sensitive Financials work.

\n

\n

How we will assess fit

\n

Please be ready to walk through a recent Oracle EBS Financials deliverable, your direct contribution to it, and how you verified it worked — ideally a RICE/CEMLI component, an interface (AutoInvoice/Lockbox/bank/payment), or a sub-ledger or period-close issue you resolved. Our process will include a technical and delivery discussion and may include a short, practical exercise relevant to R12 Financials development.

\n