Archive for June, 2011

Oracle ‘A.I.M. Methodology’

June 20, 2011

A.I.M. Introduction

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.

The A.I.M. methodology can actually be used for any type IT software implementations however the value of A.I.M is within the documentation template. The software includes the documentation templates, manuals and an html website to manage these templates.

This is a depiction of the A.I.M. methodology life cycle:

Here is a link for download:

A.I.M. Document Deliverables


Business Process Architecture (BP)
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

Business Requirements Definition (RD)
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

Business Requirements Mapping
BR.010 Analyze High-Level Gaps
BR.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

Application and Technical Architecture (TA)
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

Module Design and Build (MD)
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

Data Conversion (CV)
CV.010 Define data conversion requirements and strategy
CV.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

Documentation (DO)
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

Business System Testing (TE)
TE.010 Define testing requirements and strategy
TE.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

PERFORMANCE TESTING(PT)
PT.010 – Define Performance Testing Strategy
PT.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

Adoption and Learning (AP)
AP.010 – Define Executive Project Strategy
AP.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 Managers’Readiness 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

Production Migration (PM)
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

Application Implementation Method is a proven approach for all the activities required to implement oracle applications.

The scope of the AIM is focused on an enterprise as a whole.

There are eleven processes of implementation.

1. Business Process Architecture [BP]

This phase outlines:

  • Existing business practices
  • Catalog change practices
  • Leading practices
  • Future practices

2. Business Requirement Definition[RD]

This phase explains about the initial baseline questionnaire and gathering of requirements.

3. Business Requirement Mapping[BR]

In this phase the requirements of business are matched with the standard functionality of the oracle applications.

4. Application and Technical Architecture [TA]

This outlines the infrastructure requirements to implement oracle applications.

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.

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.

7. Documentation [DO]

Documentation prepared per module that includes user guides and implementation manuals.

8. Business System Testing [TE]

A process of validating the setup’s and functionality by QA(functional consultant) to certify status.

9. Performance Testing [PT]

Performance testing is the evaluation of transactions saving time, transaction retrieval times, workflow background process, database performance, etc…

10. Adoption and Learning [AP]

This phase explains the removal of the legacy system and oracle application roll out enterprise wide.

11. Production Migration [PM]

The process of “decommissioning” of legacy system and the usage(adoption) of oracle application system.

Advertisements

Oracle 11i Order management setup steps

June 15, 2011

Step 1
Flexfields
Define key and descriptive flexfields to capture additional information about orders
and transactions.
This step is required for Key Flexfields, and optional if you plan on using the
functionality surrounding Descriptive Flexfields. Several defaulting values are
provided.
Step 2
Multiple Organizations
Define multiple organizations in Oracle Inventory. This step is optional.
See
Overview of Inventory Structure, Oracle Inventory User’s Guide.
Step 3
Inventory Organizations
Define inventory organizations (warehouses), parameters, subinventories, and
picking rules in Oracle Inventory.
You must define at least one item validation organization and at least one
organization that acts as an inventory source for orders fulfilled internally. If you
plan to drop ship some orders, you must also define at least one logical
organization for receiving purposes. Your item validation organization can be the
same as your inventory source or your logical receiving organization, but you
cannot use one organization for all three purposes. See Step 5 for setting your item
validation organization.
This step is required.
See
Overview of Inventory Structure, Oracle Inventory User’s Guide
Defining Picking Rules, Oracle Inventory User’s Guide
Setup Steps
2-8 Oracle Order Management Implementation Manual
Step 4
Profile Options
Define profile options to specify certain implementation parameters, processing
options, and system options.
This step is required.
See
Profile Options
Step 5
Parameters
Set your Order Management Parameters to validate items, enable customer
relationships, and operating unit defaults.
This step is required.
Step 6
Invoicing
Define invoicing information, including payment terms, invoicing and accounting
rules, Autoaccounting parameters, territories, and invoice sources.
This step is required if you plan on transferring invoicing information to Oracle
Receivables. Several defaulting values are provided.
See
Payment terms, Oracle Receivables User’s Guide
Invoice with Rules, Oracle Receivables User’s Guide
Transaction Types, Oracle Receivables User’s Guide
AutoAccounting, Oracle Receivables User’s Guide
Territories, Oracle Receivables User’s Guide
Invoice Batch Sources, Oracle Receivables User’s Guide
Invoice Processing, Order Management User’s Guide
Setup Steps
Oracle Order Management Setup 2-9
Step 7
Salespersons
Define information on your sales representatives.
This step is optional.
See
Salespersons, Oracle Receivables User’s Guide.
Step 8
Tax
Define tax features, such as codes, rates, exceptions, and exemptions.
This step is required.
See
Overview of Tax, Oracle Receivables User’s Guide.
Step 9
QuickCodes
Define QuickCodes that provide custom values for many lists of values throughout
Order Management.
This step is required if you plan on creating user defined Quickcodes for utilization
within Order Management. Defaulting values are provided.
See
Define QuickCodes
Step 10
Workflow
Define order and line processing flows to meet different order and line type
requirements.
This step is required.
Setup Steps
2-10 Oracle Order Management Implementation Manual
See
Using Workflow in Order Management
Step 11
Document Sequences (Order Numbering)
Define Document Sequences for automatic or manual numbering of orders.
This step is required.
See
Defining Document Sequences for Order Numbering
Step 12
Order Import Sources
Define sources for importing orders into Order Management.
This step is required if you plan on importing orders or returns into Order
Management.
See
Order Import
Step 13
Units of Measure
Define the units of measure in which you supply items.
This step is required.
See
Defining Unit of Measure, Oracle Inventory User’s Guide.
Step 14
Item Information
Define item information, including item attribute controls, categories, and statuses.
Setup Steps
Oracle Order Management Setup 2-11
This step is required.
See
Defining Item Attribute Controls, Oracle Inventory User’s Guide
Defining Categories, Oracle Inventory User’s Guide
Defining Item Status Codes, Oracle Inventory User’s Guide
Step 15
Items
Define the items that you sell, as well as container items.
This step is required.
See
Overview of Item Setup and Control, Oracle Inventory User’s Guide.
Step 16
Configurations
Define the configurations that you sell.
This step is required if you plan on generating orders or returns for configured
items. Several defaulting values are provided.
See
Primary and Alternate Bills of Material, Oracle Bills of Material User’s Guide.
Step 17
Pricing
Define price lists for each combination of item and unit of measure that you sell.
Optionally, you can define pricing rules and parameters to add flexibility.
For more information about pricing setup and implementation, refer to the Oracle
Advanced Pricing Implementation Manual.
This step is required.
Setup Steps
2-12 Oracle Order Management Implementation Manual
See
Basic Pricing Setup
Step 18
Customer Classes
Define customer profile classes.
This step is required if you plan on using the functionality surrounding Customer
Profiles. Several defaulting values are provided.
See
Defining Customer Profile Classes, Oracle Receivables User’s Guide.
Step 19
Customers
Define information on your customers.
This step is required.
See
Entering Customers, Oracle Receivables User’s Guide.
Step 20
Item Cross References
Define item cross references for ordering by customer part number, UPC, or any
generic item number.
This step is required if you plan on using the functionality surrounding item cross
referencing. Several defaulting values have been provided.
See
Using Item Cross Referencing in Order Management
Defining Customer Item Cross References, Oracle Inventory’s User’s Guide
Defining Cross Reference Types, Oracle Inventory’s User’s Guide
Setup Steps
Oracle Order Management Setup 2-13
Step 21
Sourcing
Define your sourcing rules for scheduling supply chain ATP functions.
This step is optional.
See
Setting up the Supply Chain, Oracle Advanced Supply Chain Planning User’s Guide
Step 22
Order Management Transaction Types (Order and Line Types)
Define Order Management transaction types to classify orders and returns. For
each order type, you can assign a default price list, defaulting rules, order lines,
return lines, line types, workflow assignments, payment terms, and freight
terms.
This step is required.
See
Transaction Types
Note: Previous versions of this user’s guide referred to Order
Management Transaction Types as either transaction types or order or
line transaction types. In an effort to distinguish between the various
Oracle Transaction types available, Order Management Transaction
types will now be referred to as either OM Order or Line
Transaction Types.
Note: Order Management provides NO seeded OM transaction
types. For existing Oracle Order Entry customers, Order
Management will update existing Order Types to OM transaction
type during the upgrade process.
Setup Steps
2-14 Oracle Order Management Implementation Manual
Step 23
Cost of Goods Sold (COGS)
Set up your Cost of Goods Sold Accounting Flexfield combination (COGS Account)
in Oracle Inventory.
This step is required if you plan on utilizing the functionality surrounding COGS.
See
Oracle Inventory User’s Guide.
Step 24
Processing Constraints
Define processing constraints to prevent users from adding updating, deleting,
splitting lines, and cancelling order or return information beyond certain points in
your order cycles. Use the constraints Order Management provides, which prevent
data integrity violations, or create your own.
This step is optional. Several default values for processing constraints have been
defined.
See
Processing Constraints
Step 25
Defaulting Rules
Define defaulting rules to determine the source and prioritization for defaulting
order information to reduce the amount of information you must enter manually in
the Sales Orders window.
This step is optional. Several Defaulting rules and corresponding values for have
been defined.
See
Order Management Defaulting Rules
Setup Steps
Oracle Order Management Setup 2-15
Step 26
Credit Checking
Define your credit checking rules.
This step is required if you plan on performing any type of order credit checking.
See
Credit Cards and iPayment
Step 27
Holds
Define automatic holds to apply to orders and returns.
This step is required if you plan on performing automatic hold for orders or returns.
See
Hold Management
Step 28
Attachments
Define standard documents to attach automatically to orders and returns.
This step is optional.
Step 29
Freight Charges and Carriers
Define freight charges and freight carriers to specify on orders.
This step is required if you plan on charging customers for freight or additional
order charges.
See
Freight and Special Charges
Defining Freight Costs, Oracle Shipping Execution User’s Guide
Profile Options
Defining Freight Carriers, Oracle Shipping Execution User’s Guide
Step 30
Shipping
Define shipping parameters in Oracle Shipping Execution.
This step is required.

Also Refer
Oracle Shipping Execution User’s Guide.
Oracle Training Administration Users
Please refer to the Oracle Training Administration User’s Guide for additional
Order Management Setup Steps.
Also Refer
Using Oracle Training Administration with Order Management
Oracle Process Manufacturing Users
Please refer to the Oracle Process Manufacturing User’s Guide for additional Order
Management Setup Steps.

UPK 3.1.6

June 15, 2011

Oracle has released another update to the User Productivity Kit to version 3.1.6 from the previous version 3.1.6

See below for the change document for UPK 3.1.6:

1:- MULTI-USER DEVELOPER AND USAGE TRACKING CHANGES
Added support for Oracle Databases v9i, v10g, and v11g.

2:- STANDARD JAVA CHANGES
Added support for Sun Java Runtime Environment (JRE) version 1.6.0_05.

3:- JD EDWARDS ENTERPRISEONE CHANGES
Added support for tools version 8.97 on application version 8.12.

SIEBEL CHANGES
4:- Added support for Siebel 7.7.2.9, 7.8.2.7, and 8.0.0.2.

 

Context ID’s implementation Question for Oracle Support

August 6, 2008 by nasirh

I had an issue where our organization was developing UPK content creation in a lower DEV instance with Context ID’s implemented and wanted to know whether the content would be effective in the PROD environment.  The main issue is that when a user clicks on Help in a specific area the Context ID is passed to UPK and it shows the applicable help content.  So, I sent an SR to Oracle:

QUESTION
=========
If I capture content on the Development Instance where Context ID’s are implemented, is this translated to the Production Instance(context Id’s implemented) once we go live? OR do I have to recreate/recapture UPK content again?

ANSWER
========
The context ids that are captured are the context information used by Oracle help to load the correct help page. For example on the profiles query form the context id might be FNDPOMPV_PROFILE_QF. As long as both instances are at the same apps version then the same form should have the same context id as this is independent of the instance. Therefore, you should be able to use your content recorded on the Development instance to provide help content on the production instance.