List of AIM Documents

Oracle A.I.M. Methodology encompasses a project management methodology with documentation

templates that support the life cycle of an implementation. The life cycle methodology and
documentation templates allows A.I.M. to be a very useful tool for managing implementation projects
successfully.
This is a depiction of the A.I.M. methodology life cycle:
Application Implementation Method is a proven approach for all the activities required to implement
oracle applications. there are eleven processes of implementation.

1. Business Process Architecture [BP] This phase outlines:

Existing Business Practices

Catalog change practices
Leading practices
Future practices

BP.010 Define Business and Process Strategy

BP.020 Catalog and Analyze Potential Changes
BP.030 Determine Data Gathering Requirements
BP.040 Develop Current Process Model
BP.050 Review Leading Practices

BP.060 Develop High-Level Process Vision

BP.070 Develop High-Level Process Design
BP.080 Develop Future Process Model
BP.090 Document Business Procedure

2. Business Requirement Definition [RD] - This phase explains about the initial baseline questionnaire
and gathering of requirements.
RD.010 Identify Current Financial and Operating Structure
RD.020 Conduct Current Business Baseline
RD.030 Establish Process and Mapping Summary
RD.040 Gather Business Volumes and Metrics
RD.050 Gather Business Requirements
RD.060 Determine Audit and Control Requirements
RD.070 Identify Business Availability Requirements
RD.080 Identify Reporting and Information Access Requirements

3. Business Requirement Mapping [BR] In this phase the requirements of business are matched with
the standard functionality of the oracle applications.
BR.010 Analyze High-Level GapsBR.020 Prepare mapping environment
BR.030 Map Business requirements
BR.040 Map Business Data
BR.050 Conduct Integration Fit Analysis
BR.060 Create Information Model
BR.070 Create Reporting Fit Analysis
BR.080 Test Business Solutions
BR.090 Confirm Integrated Business Solutions

BR.100 Define Applications Setup

BR.110 Define security Profiles

4. Application and Technical Architecture [TA] This outlines the infrastructure requirements to
implement oracle applications.
TA.010 Define Architecture Requirements and Strategy
TA.020 Identify Current Technical Architecture
TA.030 Develop Preliminary Conceptual Architecture
TA.040 Define Application Architecture
TA.050 Define System Availability Strategy
TA.060 Define Reporting and Information Access Strategy
TA.070 Revise Conceptual Architecture
TA.080 Define Application Security Architecture
TA.090 Define Application and Database Server Architecture
TA.100 Define and Propose Architecture Subsystems
TA.110 Define System Capacity Plan
TA.120 Define Platform and Network Architecture
TA.130 Define Application Deployment Plan
TA.140 Assess Performance Risks
TA.150 Define System Management Procedures

5. Build and Module Design [MD] This phase emphasizes the development of new functionality
(customization) required by the client. It mainly details how to design the required forms, database and
reports.
MD.010 Define Application Extension Strategy
MD.020 Define and estimate application extensions
MD.030 Define design standards

MD.040 Define Build Standards

MD.050 Create Application extensions functional design
MD.060 Design Database extensions
MD.070 Create Application extensions technical design
MD.080 Review functional and Technical designs
MD.090 Prepare Development environment
MD.100 Create Database extensions
MD.110 Create Application extension modules
MD.120 Create Installation routines

6. Data Conversion [CV] Data Conversion is the process of converting or transferring the data from
legacy system to oracle applications. Ex. Transferring customer records from the legacy to the Customer
Master.
CV.010 Define data conversion requirements and strategyCV.020 Define Conversion standards
CV.030 Prepare conversion environment
CV.040 Perform conversion data mapping
CV.050 Define manual conversion procedures
CV.060 Design conversion programs
CV.070 Prepare conversion test plans
CV.080 Develop conversion programs
CV.090 Perform conversion unit tests
CV.100 Perform conversion business objects
CV.110 Perform conversion validation tests
CV.120 Install conversion programs
CV.130 Convert and verify data

7. Documentation [DO] Documentation prepared per module that includes user guides and
implementation manuals.
DO.010 Define documentation requirements and strategy
DO.020 Define Documentation standards and procedures
DO.030 Prepare glossary
DO.040 Prepare documentation environment
DO.050 Produce documentation prototypes and templates
DO.060 Publish user reference manual
DO.070 Publish user guide
DO.080 Publish technical reference manual
DO.090 Publish system management guide

8. Business System Testing [TE] A process of validating the setups and functionality by QA(functional
consultant) to certify status.
TE.010 Define testing requirements and strategyTE.020 Develop unit test script
TE.030 Develop link test script
TE.040 Develop system test script
TE.050 Develop systems integration test script
TE.060 Prepare testing environments
TE.070 Perform unit test
TE.080 Perform link test
TE.090 perform installation test
TE.100 Prepare key users for testing
TE.110 Perform system test
TE.120 Perform systems integration test
TE.130 Perform Acceptance test

9. Performance Testing [PT] Performance testing is the evaluation of transactions saving time,
transaction retrieval times, workflow background process, database performance, etc
PT.010 Define Performance Testing StrategyPT.020 Identify Performance Test Scenarios
PT.030 Identify Performance Test Transaction
PT.040 Create Performance Test Scripts
PT.050 Design Performance Test Transaction Programs
PT.060 Design Performance Test Data
PT.070 Design Test Database Load Programs
PT.080 Create Performance Test TransactionPrograms
PT.090 Create Test Database Load Programs
PT.100 Construct Performance Test Database
PT.110 Prepare Performance Test Environment
PT.120 Execute Performance Test

10. Adoption and Learning [AP] This phase explains the removal of the legacy system and oracle
application roll out enterprise wide.
AP.010 Define Executive Project StrategyAP.020 Conduct Initial Project Team Orientation
AP.030 Develop Project Team Learning Plan
AP.040 Prepare Project Team Learning Environment
AP.050 Conduct Project Team Learning Events
AP.060 Develop Business Unit ManagersReadiness Plan
AP.070 Develop Project Readiness Roadmap
AP.080 Develop and Execute CommunicationCampaign
AP.090 Develop Managers Readiness Plan
AP.100 Identify Business Process Impact onOrganization

AP.110 Align Human Performance SupportSystems

AP.120 Align Information Technology Groups
AP.130 Conduct User Learning Needs Analysis
AP.140 Develop User Learning Plan
AP.150 Develop User Learningware
AP.160 Prepare User Learning Environment
AP.170 Conduct User Learning Events
AP.180 Conduct Effectiveness Assessment

11. Production Migration [PM] The process of decommissioning of legacy system and the
usage(adoption) of oracle application system.
PM.010 Define Transition Strategy
PM.020 Design Production Support Infrastructure
PM.030 Develop Transition and Contingency Plan
PM.040 Prepare Production Environment
PM.050 Set Up Applications
PM.060 Implement Production Support Infrastructure
PM.070 Verify Production Readiness
PM.080 Begin Production
PM.090 Measure System Performance
PM.100 Maintain System
PM.110 Refine Production System
PM.120 Decommission Former Systems
PM.130 Propose Future Business Direction
PM.140 Propose Future Technical Direction

Oracle Inventory: Inventory Organizations

Inventory Organizations

An inventory organization is a facility where you store and transact items. Before you can use
Oracle Inventory, you must define one or more inventory organizations. Inventory
organizations represent distinct entities in your enterprise and can be one of the following:
A physical entity such as a manufacturing facility, warehouse, or distribution centre.
A logical entity such as an item master organization, which you use to define items.
An inventory organization may have the following attributes: An inventory organization can
have its own location, ledger, costing method, workday calendar, and items.
An inventory organization can share one or more of these characteristics with other
organizations.

Inventory Organization Structure

An inventory organization, where you store and transact items can have one or more
subinventories. Subinventories are unique physical or logical separations of material inventory,
such as raw material inventory, finished goods inventory, or defective goods inventory. In
Oracle Inventory, all material within an organization is held in a subinventory. You must define
at least one subinventory for every organization. You can track item quantities by subinventory
as well as restrict items to specific subinventories. The subinventories in an inventory
organization may be made up of one or more locators. You use locators to identify physical
areas where you store inventory items. You can track items by locator and restrict items to a
specific locator. Locator control is optional in Oracle Inventory.

Sample Inventory Organization

Receiving Subinventory
Raw material subinventory
Manufacturing subinventory
Finished goods subinventory
Inspection subinventory
Defective goods subinventory
Shipping Subinventory

Multi-Organization Structure

Multi-Organization structure enables you to model multiple business units in an enterprise

using a single installation of Oracle applications. In a multi-organization architecture you can
keep data secure and separate from each business unit.
The following are the benefits of multi-organization structure:
You can use a single installation of any Oracle Applications product to support any number of
business units, even if those business units use a different ledger.
Secure access to data so users can access only relevant information.
You can define a organizational model that best suits your business requirements.

In Oracle Inventory, you can fulfil any sales order or purchase order regardless of them being
booked from any Inventory organization. You can also determine if any intercompany invoicing
needs to occur based on if the Sales Order or Purchase Order was booked in a different
Operating Unit other than the one to which the Inventory organization is assigned.

Setting Up Locations

Define information describing the physical locations of employees and organizations.

Locations are shared between Oracle Inventory, Oracle Purchasing, and Oracle Human
Resource Management Systems. Locations flagged as global locations are available to all
business groups. You can associate each organization with only one location; however, you can
associate more than one organization with the same location.
Physical locations are defined in Oracle Human Resource Management Systems.

Defining Organizations

Classify the Organization

Choose an organization classification to describe the general purpose of your organization.
Examples of organization classifications are inventory organization, legal company, and HR
organization.
Choose inventory organization as your organization classification to use your organization for
inventory management
Ledger
Tie each inventory organization to an operating unit. Each operating unit is associated to a legal
entity and a primary ledger.
Inventory Parameters
Organization Features
You must enter organization information such as the organization code, and the item master
organization. The system defaults this field to the current organization. You must change this

for any organization that is not an item master organization. The item master organization
should be the first inventory organization you create.
Note: The Manufacturing Partner Organization functionality is only available in Japan, Taiwan
and Korea.
Products and Features
You can enable specific products on the Inventory Parameters tab. These include Oracle
Warehouse Management, Oracle Process Execution, and Oracle Enterprise Asset Management.
If you have Oracle Warehouse Management installed, then you can enable the Warehouse
Control System.
Costing Parameters
Standard costing: A costing method where a predetermined standard cost is used for charging
material, resource, overhead, period close, job close, and cost update transactions and valuing
inventory. Any deviation in actual costs from the predetermined standard is recorded as a
variance.
Average costing: A costing method which can be used to cost transactions in both inventory
only and manufacturing (inventory and work in process) environments. As you perform
transactions, the system uses the transaction price or cost and automatically recalculates the
average unit cost of your items.
LIFO costing: Costing method where it is assumed that items that were received most recently
are transacted first.
FIFO costing: Costing method where it is assumed that items that were received earliest are
transacted first.
Revision, Lot, Serial, and License Plate Number (LPN) Parameters
You determine the starting revision for all items in the organization when you define your
inventory organization. You can also choose to set lot control and serial control parameters at
the organization level. Revision control is discussed in the Defining and Maintaining Items
module. Lot control and serial control is discussed in the Lot and Serial Control module.
LPN Generation Options
If you have Oracle Warehouse Management installed, and you are working with a Warehouse
Management enabled organization, you can define License Plate Number (LPN) Generating
Options. LPNs must be unique across organizations. Setting the parameters on the Revision,
Lot, Serial, and LPN tab enables the system to generate LPNs on demand, or through a
concurrent request. As long as the number is unique, Oracle Warehouse Management also
enables you to generate your own LPNs.

ATP, Pick, Item-Sourcing Parameters

This enables to
Set the available to Promise (ATP) default rule for the organization
Set the picking default for the organization
Set the item sourcing default for the organization
Inter-organization Parameters

This enables to determine the parameters the organization uses when it transfer the material
between organization.
Other Account Parameters
This enables to setup receiving information, profit and loss account information, and other
additional account details.