Business Analyst Oracle R12

Job Title: Business Analyst Work Arrangement: Fully Remote Duration: 6 months Previous Cisco Experience: Preferred JOB DESCRIPTION About the Role This client is undertaking a significant cross-functional transformation of its Service Supply Chain (SSC) ecosystem under the National Defense Authorization Act (NDAA) 851 mandate, known internally as Project RD50. This initiative touches nearly every layer of our client’s service operations — from how installed assets are tracked to how service contracts are written, how parts are managed, how orders flow, and how returns are processed. We are looking for a Supply Chain Business Analysts who can operate at the intersection of business process and technical delivery. You will be embedded in the SSC System Operations team, working directly with business architects, functional SMEs, and IT engineering to make sure RD50 requirements are correctly implemented, thoroughly tested, and stable in production. This is hands-on, high-accountability work. You will own your test scenarios end to end — from writing them to executing them to defending their quality in daily defect reviews. The engagement spans two quarters and covers six SSC modules: InstallBase, Service Contract, PDMT (Product Data Management Tool), SPM (Service Parts Management), New Buys Integration, and CDM/RMA. You need to understand not just how to write a test case, but why the business logic matters and what breaks if you miss something. What You'll Do Analysis & Test Planning Before a single test case is written, you will dig into the RD50 requirements and MD50 design documents across all impacted functional areas. You will build the Test Scenario Matrix — the foundation that every subsequent test case depends on — by synthesizing Jira features and stories against the RD50 and MD50 specs. If the matrix is incomplete, defects slip into production. This phase sets the quality bar for everything that follows. Test Case Development: You will write detailed test cases with step-by-step instructions and clear acceptance criteria, then load them into qTest. Before execution, you will run scenario reviews with Business Architects and validate UAT scenarios directly with the business PM and functional SMEs. These conversations are where ambiguities get resolved — you are expected to drive them, not just attend them. You will also build the daily execution plan that keeps the BAT cycle on track. BAT Execution & UAT Support You will execute Business Acceptance Testing across all six modules, record results in qTest, and support the parallel UAT cycle. Every day during execution you will be in defect triage — reviewing new defects with IT, confirming which are real versus environment issues, and holding the team accountable to resolution SLAs. Your defect identification rate and false-positive rate are tracked as performance metrics. Quality here directly affects whether the client’s release normalization goes smoothly. Production Normalization After go-live, the work is not over. You will join the daily normalization checkpoint meetings, test any defects that surface in production through the Point Release or Emergency Bug Fix process, and conduct formal 5Why root cause analyses for defects logged in the client’s ESP Non-production incident system. You are accountable for zero Severity 1 or 2 production defects attributable to missed BAT scenarios. What We're Looking For Oracle R12 This is the core of the role. You need at least 5 years of direct, hands-on experience in Oracle Applications R12 across the full suite of modules relevant to service supply chain operations. Knowing one or two modules is not enough — you need to understand how they connect. • Application Object Library (AOL) • Inventory Management, Shipping, and Receiving • Financials • Order Management • Purchasing • Depot Repair Service Parts Management (SPM) At least 1 year of practical experience in SPM. You understand how service part workflows operate, how inventory aligns to service commitments, and how changes upstream in Oracle affect parts availability and fulfillment downstream. Pega At least 2 years of practical Pega experience. You do not need to be a developer, but you need to understand Pega workflows well enough to analyse requirements, write meaningful test scenarios, and speak credibly with the engineering team about what you are testing and why. Certified System Architect (CSA) is a plus but not required. B2B Integration At least 2 years of experience working with B2B integration technologies. The client’s SSC ecosystem is deeply integrated with external partners — understanding how data moves between systems is critical to testing New Buys Integration and other integration-dependent modules correctly. • MuleSoft and API integration • RosettaNet Partner Interface Processes (PIPs) • Data Transfer Gateways — E2Open preferred • Reverse Logistics (RL) business process knowledge • SQL / PL-SQL at an intermediate level How Performance is Measured This engagement carries formal performance metrics tracked quarterly against the client's ESP system and Asana. You will be held to the following standards: • Zero Severity 1 or 2 production defects attributable to missed BAT scenarios • No more than 1–3 Severity 3 or below production defects attributable to missed BAT scenarios per quarter • No more than 1–3 BAT-tested defects that pass testing but fail normalization per quarter • ERMO deadline extensions caused by the BAT team not to exceed 4% of releases • BAT-identified defects later determined 'Not a Defect' by IT not to exceed 2.5% of raised defects