Senior Oracle Data Conversion & Technical SME

SENIOR ORACLE DATA CONVERSION & TECHNICAL SME Center of Excellence | Working alongside Tessera AI Agents Location: India-based (offshore). Remote: Yes, within India, with a daily overlap of US business hours (at least 3–4 hours) and occasional travel as needed. Experience: 10+ years Employment type: Contractor through a staffing partner; conversion to a permanent role is possible later. Positions: 2 — one Order-to-Cash data SME and one Procure-to-Pay and Product Master data SME (see Position Profiles). Start date: Immediate. Engagement model: Multi-engagement technical delivery role. Approximately 80% hands-on data conversion work across several concurrent Oracle customer engagements (E-Business Suite and Fusion), 20% platform enablement, pre-sales support and product input. Works from India with a daily overlap of US business hours alongside customers, Oracle functional architects and the Principal Architects. ABOUT TESSERA LABS Tessera is an AI-native platform for enterprise transformation. The multi-agent platform delivers governed execution across ERP, CRM, HCM, and finance systems, cutting timelines from years to weeks and costs by more than half. Built on deep expertise across Oracle, SAP, Salesforce, Workday, and other systems of record, Tessera address the scope a system integrator would have traditionally taken up with the speed of execution and efficiency of an AI-native platform. For decades, enterprises have struggled with fragmented business systems, where migrations have consumed hundreds of millions of dollars, data stayed inconsistent and unreliable, and business processes slowed under manual review. Tessera was founded to change that, for Oracle and every other system enterprises depend on. The name itself — a tessera, a single tile in a mosaic — reflects our mission: unifying the disparate pieces of the enterprise into a coherent whole. Tessera is an AI-powered, multi-agent platform that harmonizes systems and lets teams work in plain English. ROLE SUMMARY We are looking for two Senior Oracle Data Conversion & Technical SMEs to own how data gets into Oracle — across several customer engagements at the same time. Our Oracle functional architects decide what the target should look like; you decide how the legacy data actually arrives there: through which interface, in what order, under what access, and how everyone knows it arrived correctly. Your centre of gravity is Oracle E-Business Suite: the open interface tables and import programs, the public PL/SQL APIs, Web ADI and the concurrent manager. Much of our pipeline is migration into EBS — from SAP ECC, JD Edwards and older EBS instances — and our customers rarely give a vendor direct database access. You need to know what can be loaded through which door, and why each door rejects what it rejects. You will also need real Oracle Fusion loading depth — FBDI, HDL and the Fusion import processes — because many of our customers run EBS and Fusion side by side, or are part-way from one to the other, and the same master data has to land correctly in both. You will do this work with Tessera’s AI agents, not instead of them. The platform profiles the source data, proposes mappings, generates transformation logic and load files, and runs the reconciliations. What it cannot do is decide whether a customer with forty bill-to sites is a data problem or a business reality, or why Order Import rejects lines that look perfectly valid. That judgment is the role, and every time you exercise it we expect it to go back into the platform. Two outcomes define the job. The first is converted data the business trusts on day one: counts, balances and open items that reconcile to the source, with evidence the customer signs. The second is that the next conversion goes faster — load templates, validation rules and playbooks captured in the platform rather than in your head. The second is what makes the first repeatable, and it is the measure you will be held to. POSITION PROFILES We are hiring two SMEs with the same technical foundation but different business data depth. Each candidate should be clear which profile they are applying for. POSITION 1 — ORDER-TO-CASH (OTC) DATA SME - Customer master in the Trading Community Architecture (TCA) model: parties, accounts, account sites and site uses (bill-to, ship-to), contacts, customer profiles and credit limits — through the Customer Interface and the TCA public APIs. - Pricing: price lists, modifiers and qualifiers in Advanced Pricing. - Open sales orders and returns through Order Import and OE_ORDER_PUB, including holds, partial shipments and order types. - Open receivables: invoices, credit and debit memos through AutoInvoice, and unapplied or on-account receipts through the receipt APIs or Lockbox. - Supporting objects: payment terms, salesreps, transaction types and customer bank accounts. - Oracle Fusion equivalents: customer import (FBDI/REST), Order Management order import, and Receivables AutoInvoice and receipt imports. POSITION 2 — PROCURE-TO-PAY (P2P) AND PRODUCT MASTER DATA SME - Supplier master: suppliers, supplier sites and site assignments, contacts and supplier bank accounts — through the Supplier Open Interface and the supplier APIs. - Product master: items and organization assignments, item templates, categories and catalogs, units of measure and conversions, item cross-references, and bills of material where in scope. - Sourcing and purchasing: approved supplier lists, sourcing rules, blanket and contract agreements, and open purchase orders through the Purchasing Documents Open Interface (PDOI). - Open payables and receiving: open AP invoices through the Payables Open Interface, and open receipts through the Receiving Open Interface. - Inventory: on-hand balances, lots and serials through the Inventory Transactions Interface. - Oracle Fusion equivalents: supplier import, item import (Product Hub), purchase order and agreement import, and Payables invoice import (FBDI). KEY RESPONSIBILITIES 1. DATA CONVERSION DESIGN ACROSS ENGAGEMENTS (30%) - Own the conversion approach on several concurrent engagements: the object inventory, load sequence and dependencies, the number of mock loads, and the cutover plan. - Choose and defend the load method for each object — open interface and import program, public API, Web ADI, FBDI or HDL — based on volume, validation, restart needs and the access the customer will actually grant. - Lead source-to-target mapping with the Oracle functional architects: SAP ECC customer master and partner functions to the TCA model, material master to items and inventory organizations, pricing conditions to price lists, and JD Edwards address book and item master to their Oracle equivalents. - Settle the environment and access model with the customer’s IT and security teams before the first load — staging schemas, API users, application-level access only — rather than discovering it in mock load one. 2. HANDS-ON LOADING INTO ORACLE E-BUSINESS SUITE AND FUSION (35%) - Build and run loads through the open interfaces and standard import programs: Customer Interface, Item Import, Order Import, AutoInvoice, Payables Open Interface, Journal Import, Mass Additions, and the Receiving and Inventory transaction interfaces. - Develop API-based loads where the interfaces fall short — TCA party, account, site and contact APIs, OE_ORDER_PUB, supplier, item, BOM, pricing and receipt APIs — with application context, MOAC initialisation and API error handling done properly. - Configure Web ADI integrators for user-maintained data and restricted-access engagements, and use FNDLOAD or iSetup to move configuration between instances. - Load Oracle Fusion through FBDI via UCM and ESS jobs, ADFDI, HDL where HCM is in scope, and REST where volumes allow — and know where Fusion import processes behave differently from their EBS counterparts. - Sequence