← Back to Engagement Library

Cellular South — DataLoader-Driven Financial Migration & Oracle EBS Functional Setup

ClientCellular South (now C Spire)
IndustryTelecommunications — Regional Wireless Carrier
Oracle VersionOracle E-Business Suite 11i
Modules PO AP GL DataLoader
Engagement Period2005 – 2006
Project TypeOracle EBS Implementation with DataLoader Migration
ComplexityMedium · 222 Files · 10 Subfolders · Telecom Functional Specs

Executive Summary

Cellular South — a regional wireless carrier headquartered in Mississippi, now known as C Spire — implemented Oracle EBS 11i to modernize its financial operations and procurement processes. The engagement combined a standard Oracle functional implementation (PO, AP, GL) with a significant DataLoader-based data migration workstream, reflecting the need to transition historical financial data from a legacy system into Oracle without a gap in financial records continuity.

Dedicated DataLoad and Functional subfolders in the project structure indicate distinct workstreams for the migration technical work and the Oracle functional configuration — a sound project organization that prevents the two workstreams from interfering with each other while maintaining coordination at integration test points. The Sign Offs subfolder reflects a formal approval process for each functional design area — a governance practice that protects the engagement scope and provides legal protection for the consultant.

Training materials were developed specifically for the telecom context, with Cellular South's specific business processes and Oracle data reflected in training scenarios — a higher-investment but more effective approach than generic Oracle training.

Engagement Context

Regional wireless carriers in the mid-2000s were in a period of rapid growth — expanding coverage areas, adding subscribers, and scaling network infrastructure — while operating with back-office systems that had not kept pace with their operational growth. Cellular South's Oracle implementation was part of a broader operational modernization, with the procurement and financial systems needing to support both the carrier's retail operations and its capital-intensive network infrastructure spending.

Telecom procurement has specific characteristics that influence Oracle PO configuration: high-volume equipment purchases with long lead times, service contracts with telecommunications network vendors, and procurement categories aligned to capital vs. operating expense classification for regulatory reporting purposes. These telecom-specific requirements were captured in the functional specifications.

Oracle Implementation Scope

DataLoader Migration

The DataLoader workstream used Oracle's SQL*Loader technology to migrate historical financial data — supplier master records, open AP invoices, historical GL balances, and purchasing data — from the legacy system to Oracle. DataLoader control files defined the data mapping and transformation rules, with validation scripts confirming migration completeness and data integrity before production cutover.

Functional Setup (PO, AP, GL)

Oracle functional configuration was driven by functional design documents capturing Cellular South's specific procurement and financial requirements. The functional specifications addressed telecom-specific scenarios: network equipment purchases on blanket purchase agreements, service vendor management, and capital expenditure classification in the procurement category structure.

Sign-Off Process

Each functional design area was formally signed off by the appropriate Cellular South business owner before configuration began. This governance gate prevented configuration rework caused by design changes after build had started, and created a formal record of the client's acceptance of each design decision.

Training

Role-based training was developed and delivered for buyers, AP clerks, and GL accountants, with Cellular South-specific scenarios used throughout — telecom equipment purchase scenarios for buyers, telecom vendor invoice processing for AP, and network capex GL coding scenarios for accountants.

Key Deliverables

DeliverableTypePurpose
Functional Design SpecificationsFunctional DesignDetailed Oracle functional design for PO, AP, and GL covering telecom-specific requirements
Functional Design Sign-Off RecordsGovernanceFormal client approval of each functional design document before configuration begins
DataLoader Control FilesMigration ArtifactSQL*Loader scripts for supplier, AP invoice, and GL balance migration from legacy system
Migration Validation ScriptsMigration ArtifactPost-migration validation queries confirming record counts and key field integrity
Training Materials — Telecom ScenariosTrainingRole-based Oracle training with Cellular South-specific purchasing, invoicing, and GL scenarios
Diagrams — Process FlowsProcess DocumentationOracle process flow diagrams for procurement-to-payment and financial posting cycles

Consultant Insights

On Functional Design Sign-Off: The sign-off process used at Cellular South is a best practice that should be standard on every Oracle implementation. A signed functional design document establishes that: the client understood the proposed configuration, the client approved it, and scope changes after sign-off require a formal change request. Without signed designs, "that's not what I wanted" is a support issue with no resolution mechanism; with signed designs, it is a change request with a cost and timeline.
On Telecom-Specific Training Scenarios: Generic Oracle training materials describe Oracle features; telecom-specific training materials describe how Cellular South's staff will use those features on their actual transactions. The investment in scenario customization pays back in reduced post-go-live support calls and faster user competency development. The ratio is approximately 2:1 — custom training takes twice as long to prepare but produces half the post-go-live support volume.
On Parallel DataLoader and Functional Workstreams: Running data migration and functional configuration in parallel is efficient but requires explicit coordination at integration test time — the migrated data must be validated against the configured Oracle environment, and any functional configuration change after migration may require data re-migration. Establish a configuration freeze date for the test environment before migration testing begins.

Related Engagements