High Sierra — Oracle EBS Proposal & SAPA Reference Implementation Support

Client	High Sierra
Industry	Manufacturing — Consumer Goods
Oracle Version	Oracle E-Business Suite R12
Modules	PO AP GL
Engagement Period	2009
Project Type	Oracle EBS Proposal Development & Reference Implementation Support
Complexity	Low-Medium · Proposal Phase · Manufacturing Context · SAPA Reference Materials

Executive Summary

High Sierra — a consumer goods manufacturer — engaged William Delaney Consulting in a proposal and pre-implementation phase for Oracle EBS R12 services in 2009. Three proposal iterations (v1.0, v1.1, v2.0) reflect an active scoping process, negotiating the scope, approach, and commercial terms of the Oracle engagement. The engagement folder also contains an extensive set of SAPA Oracle R12 configuration reference materials — AP and PO configuration guides, BR100 purchasing setup documentation, custom workflow designs, Vertex tax integration documentation, and Oracle buyer training materials — that were developed and used in the concurrent SAPA engagement as reference artifacts for scoping and estimating the High Sierra Oracle work.

The overlap between the High Sierra engagement period (July 2009) and the active SAPA implementation (2008–2010) in a similar manufacturing vertical reflects a common consulting practice: reference implementations in comparable client environments are the most reliable basis for estimating and scoping new Oracle engagements. SAPA's manufacturing Oracle configuration provided both a functional template for what High Sierra would need and a credibility reference for demonstrating Oracle manufacturing EBS delivery capability.

Engagement Context

Consumer goods manufacturers considering Oracle EBS R12 in 2009 were entering a mature market for Oracle EBS implementation services — R12 had been available since 2006, and experienced R12 implementers were available, but R12 implementations remained more complex than 11i due to the Subledger Accounting engine, E-Business Tax module, and legal entity configurator changes. A manufacturing client evaluating Oracle R12 needed a services partner who could demonstrate specific R12 manufacturing experience, not just Oracle experience generally.

Manufacturing Oracle EBS implementations in the consumer goods vertical share consistent characteristics: a vendor base of raw material suppliers and finished goods manufacturers under toll manufacturing agreements, PO structures that accommodate blanket agreements for high-volume commodity materials and standard POs for capital and MRO, and AP processing that handles high-volume supplier invoices with three-way match against receiving. The SAPA configuration reference materials in the folder — AP USA Configuration Guide, PO BR100, custom workflow designs for PO approval and Account Generator — represented exactly this type of manufacturing Oracle knowledge base.

The Vertex Use Tax integration documentation (three versions of the Vertex-Oracle technical specification) is particularly relevant for a consumer goods manufacturer: use tax on purchases (tax assessed on goods purchased for business use when sales tax was not charged by the vendor) is a significant compliance requirement for manufacturers with multi-state operations, and Oracle R12's E-Business Tax module with Vertex integration is the standard solution for automating use tax determination.

Proposal Scope

Proposal Development (v1.0 → v2.0)

Three proposal iterations represent a standard commercial negotiation cycle: the initial proposal (v1.0) establishes the baseline scope and commercial terms, client feedback drives scope adjustments and clarifications in v1.1, and the final proposal (v2.0) reflects negotiated terms ready for client acceptance. The three-version iteration indicates an engaged client review process — passive clients accept or reject v1.0; actively interested clients drive the negotiation that produces a v2.0.

Reference Configuration Assets

The SAPA Oracle R12 configuration materials used as reference in this engagement included: AP Mexico Configuration Guide (for international entity setup), AP USA Configuration Guide (for domestic AP operations), BR100 Purchasing setup document (Oracle AIM configuration specification), custom workflow designs for PO approval, requisition approval, and Account Generator modifications, Vertex Use Tax integration specifications, and AP PreNote (bank prenote validation for electronic payments). These materials provided the estimating baseline and demonstrated capability to a client evaluating Oracle R12 implementation services in a comparable manufacturing context.

The "Metal Buying" customization document (NEP-059) and the ALCOA PO/Requisition Account Generator modification references reflect procurement-specific customizations developed for SAPA that were relevant as reference for assessing whether High Sierra's procurement processes would require similar customizations. Metal buying process management — tracking commodity prices, managing open market purchasing, and integrating commodity hedging with PO pricing — is a specialized procurement requirement that Oracle PO does not address natively.

Key Deliverables

Deliverable	Type	Purpose
Oracle EBS R12 Proposal (v1.0, v1.1, v2.0)	Business Development	Three-iteration proposal for Oracle EBS R12 implementation services at High Sierra, manufacturing context
SAPA AP Configuration Reference	Reference Material	AP USA and Mexico configuration guides used as reference for scoping High Sierra AP requirements
SAPA PO BR100 Reference	Reference Material	Oracle AIM PO configuration specification used as reference for estimating High Sierra purchasing scope
Vertex Use Tax Integration Reference	Reference Material	Vertex-Oracle E-Business Tax integration specification used as reference for High Sierra tax requirements

Consultant Insights

On Reference Implementations in Proposal Development: The most persuasive Oracle EBS proposals combine a documented approach with evidence of comparable delivery. A proposal that describes what will be done, supported by reference materials from a comparable implementation already completed, is substantially more credible than a proposal that describes the approach theoretically. The SAPA Oracle manufacturing reference materials — configuration guides, workflow designs, training materials — served this function: they demonstrated that the approach proposed for High Sierra had already been successfully implemented in a comparable manufacturing environment.

On Vertex Integration in Oracle R12: Oracle R12's E-Business Tax (EBTax) module replaces 11i's tax code approach with a rules-based tax engine that is more powerful but also more complex. For manufacturers with multi-state use tax obligations, integrating Vertex (or Avalara) with EBTax provides automated use tax determination by jurisdiction — replacing the manual lookup process that finance teams use when EBTax is configured without a third-party tax engine. The Vertex integration requires careful configuration of the EBTax Tax Regime structure to align with Vertex's jurisdiction hierarchy. Three versions of the integration specification reflect the iterative nature of getting this configuration right.

On Proposal Iteration as a Client Signal: The progression from v1.0 to v2.0 in a proposal is diagnostic — it tells the consultant something important about the client. Clients who drive multiple proposal revisions are either serious buyers negotiating toward engagement (good signal) or serial proposal collectors who use proposal processes to extract consulting knowledge without committing (risk signal). The distinction is usually apparent by v1.1: serious buyers provide specific, constructive feedback that improves the scope; collectors request scope expansions without discussing commercial terms or moving toward decision.