Fixed_Asset_Module_Customizations_Document.pdf

Fixed Asset Module Customizations Document

Purpose The purpose of this document is to provide a clear, authoritative summary of all required customizations for migrating from AC150 and MAIS to the Oracle EBS Fixed Asset Module.

This addendum does not introduce new requirements; instead, it consolidates and references existing requirements already documented and approved in the Requirements Specification. By isolating the three business-identified customizations and mapping them to their corresponding requirement IDs, this document enables accurate vendor scoping, ensures shared understanding across stakeholders, and supports successful implementation planning.

Summary of Required Customizations This section consolidates the three customizations required for the Fixed Asset Module Implementation. Each customization represents functionality that is not provided out-of-the-box by Oracle EBS Fixed Assets and therefore requires custom development or integration work to support WSSC Water’s business processes.

Customization #1 — CIP to Fixed Asset Cost Allocation (Critical Customization) WSSC Water requires a custom allocation engine that distributes accumulated CIP project costs from the General Ledger to individual asset records based on each asset’s replacement value. Oracle EBS does not perform this type of allocation natively.

Requirement Requirement Description FR225516 – Request Asset Cost Allocation

The system shall allocate actual project costs from the General Ledger to each asset record associated with the project.

FR227164 – Provide Asset Cost Allocation

The General Ledger System shall provide asset costs to the Fixed Asset Module.

FR225431 – Upload Fixed Asset Excel File

The system shall upload the completed fixed asset Excel file to a secure staging area.

FR225443 – Request Fixed Asset Information

The system shall request fixed asset data from Engineering & Construction team.

RULE228723 – Allocation Use Project Costs from General Ledger

Asset cost allocations shall be performed using the actual accumulated project costs imported from Oracle General Ledger.

RULE228724 – Allocation Basis for Asset Costs

The distribution of costs across assets shall be determined by each asset’s replacement cost percentage relative to the total replacement cost for the project.

RULE225445 – Fixed Asset Information Review

When requesting asset creation data, Capital Accounting will be responsible for reviewing submitted data.

RULE225444 – Fixed Asset Information Ownership

Engineering and Construction must supply asset registry upon project closeout to IT Fixed Asset team.

DATA225435 – Fixed Asset Upload Fields

This requirement describes all the required fields for bulk upload of fixed asset data.

The fields are:

• AC150 ACCT NO.

• FUND

• ACCT NO.

• DATA SOURCE

• SUBSTANTIAL COMPLETION DATE

• FINAL ACCEPTANCE DATE

• JOB DESCRIPTION

• FACILITY NAME

• SIZE

• COUNTY

• YEAR INTO SERVICE

• LIFE

• FEET

• COST

• LAPSE YEARS

• CURRENT DEPRECIATION (AC150)

• ACCUMULATED DEPRECIATION (AC150)

• NET BOOK VALUE (NBV)

• SUBSYSTEM

• PROCESS

• SUBPROCESS

• ASSET GROUP

• SOURCE ASSET ID

• ASSET NAME

• REPLACEMENT COST

• INSTALLED DATE

• ASSET STATUS

• CONSTRUCTION CONTRACT / JOB NUMBER

• REPLACEMENT COST % TO TOTAL

• ALLOCATED COST

Customization #2 — Pipe Size and Pipe Asset Data Integration Pipe assets must include fields such as pipe size, footage, county code, and abandonment attributes, which do not exist in Oracle FA. These values originate from WAM or supplemental accounting sources and must be loaded into the system via a custom interface and custom flex fields.

Requirement Requirement Description FR227450 – Request Horizontal Pipe Information

The system shall request horizontal pipe information from Capital Accounting.

FR227456 – Request Horizontal Pipe Cost Information

The system shall request horizontal pipe cost information from the General Ledger.

DATA227461– Horizontal Pipe Asset Fields

This requirement describes the fields required for horizontal pipe asset records.

The fields are:

• Asset Account

• Pipe Size

• County Code (A, PG, M)

• In-Service Year

• Asset Life

• Abandonment Year

• Footage

• Original Cost

• Current Year Depreciation

• Accumulated Depreciation

• Substantial Completion Date

• Project Number

FR227601 – Request Generate Pipe Study Report Decision

The system shall request a generate pipe study report decision.

DATA227626 – Pipe Study Report Fields

This requirement describes the fields in the pipe study report.

The fields are:

• Job Number

• Pipe Size

• Feet

• Cost

• CPF (Cost per Foot)

• Fund/Asset Account

• Utility Type

• Totals (by group)

Customization #3 — Water Meter Intake and Disposal Data from C2M The Fixed Asset module must receive meter intake (meter size, unit price, number of units, year of addition) from Oracle inventory module, and disposal information from the C2M system. Because Oracle FA does not integrate with C2M natively, a custom interface is required to support meter lifecycle processing.

Requirement Requirement Description FR225541– Request Meter Intake Information

The system shall request meter intake information from Oracle inventory module.

FR227163

– Provide Meter Intake Information

The Oracle inventory module shall provide meter intake information.

FR225557 – Request Meter Disposal Information

The system shall request meter disposal information from the C2M system.

DATA225545 – Meter Information Fields

This requirement describes all the fields for meter data information request.

The fields are:

• Txn Date

• Item No.

• Description

• Source Type

• Quantity

• Unit of measure

• Unit Cost

• Txn Value

• Warehouse

• Meter Size

DATA225556 – Meter Disposal Information Fields

This requirement describes the meter disposal information fields.

The fields are:

• Account ID

• Start Date

• End Date

• Meter Size

• Removal Date

• Retired Date

RULE225555 – Meter Information Frequency

When requesting meter information, the system must request the information monthly.