Credit check can be applied at two levels
1. Operating Unit level 2. Customer level (including main n site )
The sales order transaction type only help in placing holds at the below four level,
1. Ordering 2. Picking 3. Packing 4. Shipping
The above only determines the time at which the sales order will apply hold in the otc.
Credit check has got 5 steps. The steps are detailed below :
At Customer Header Level :
Step 1 : Query the Customer at Customer - Standard navigation. At its header level go to Profile-Amounts tabbed region and set "Order Credit Limit" as say 1000 USD and if required, set the "Credit Limit" ( for all order put together) as 10,000 USD.
Step 2 : Go to Profile - Transaction tabbed region and enable Credit Check ( Check box) and save.
At Customer's Site Level :
Step 1 : Query the Customer at Customer - Standard navigation. Choose the address for which you want to perform the credit check and click "Open" button. At this site level go to Profile-Amounts tabbed region and set "Order Credit Limit" as say 1000 USD and if required, set the "Credit Limit" ( for all order put together) as 10,000 USD and save.
Step 2 : Go to Profile - Transaction tabbed region in this site level and enable Credit Check ( Check box) and save.
Steps 3,4 and 5 are common for both the scenarios :
Step 3:Open Sales order and Populate the Customer. If credit check to be done at site level, populate the ship to site. Go to others tabbed region and take a copy of the payment terms. Go to Setup - Orders - Payment terms and query the PT just copied from SO. Enable Credit Check ( Check box) and save.
Step 4 :Create a Credit Check rule at setup - Rules - Credit. Make holds to be applied at SO line level. Ensure that in "Exposure" tabbed region, enable "Applicable for Uninvoiced Sales Order" and save.
Step 5 :Open the Order Transaction Type of your Customer and in the bottom, populate our CC rule at the time of Booking the order. Now make a check by booking a Sales order for above 1000 USD. We can observe that a Credit hold applied for the Customer. This can be seen at Actions - Additional Information in SO.
Friday, July 3, 2009
Some Basics on Data Access Speed
Internet Access Speed is measured in Bits per second.
128Kbps means 128 Kilobits per second.
File sizes are in Bytes - tens/hundreds of bytes, thousands of bytes (Kilobytes), millions of bytes (Megabytes).
A word document of 500b means 500 bytes A pdf document of 50KB means 50 Kilobytes A mp3 song of 5MB means 5 Megabytes.
4 Bits = 1 Nibble
8 Bits = 1 Byte
1000 Bytes = 1 Kilo Bits ............KB/Sec ( in data communication )
1024 Bytes = 1 KB ( Kilo Bytes) ......... ( while in data storage )
1024 KB = 1 MB ( Mega Bytes)
1024 MB = 1 GB ( Giga Bytes)
1024 GB = 1 TB ( Terra Bytes)
1024 TB = 1 PB ( Petabyte)
1024 PB = 1 EB ( Exabyte )
1024 EB = 1 ZB ( zettabyte)
1024 ZB = 1 YB ( yottabyte)
While downloading a file from a website, the speed shown in the dialogue box is in KB/sec, which is Kilobytes per second.
To decipher the internet access speed (at that instance), the speed shown in the box needs to be multiplied by 8.
If the box is displaying speed of 4.2 KB/ sec, the access speed is 4.2 x 8 = 33.6 Kbps i.e., approx. 33 Kilobits per second or 33 Kbps.
128Kbps means 128 Kilobits per second.
File sizes are in Bytes - tens/hundreds of bytes, thousands of bytes (Kilobytes), millions of bytes (Megabytes).
A word document of 500b means 500 bytes A pdf document of 50KB means 50 Kilobytes A mp3 song of 5MB means 5 Megabytes.
4 Bits = 1 Nibble
8 Bits = 1 Byte
1000 Bytes = 1 Kilo Bits ............KB/Sec ( in data communication )
1024 Bytes = 1 KB ( Kilo Bytes) ......... ( while in data storage )
1024 KB = 1 MB ( Mega Bytes)
1024 MB = 1 GB ( Giga Bytes)
1024 GB = 1 TB ( Terra Bytes)
1024 TB = 1 PB ( Petabyte)
1024 PB = 1 EB ( Exabyte )
1024 EB = 1 ZB ( zettabyte)
1024 ZB = 1 YB ( yottabyte)
While downloading a file from a website, the speed shown in the dialogue box is in KB/sec, which is Kilobytes per second.
To decipher the internet access speed (at that instance), the speed shown in the box needs to be multiplied by 8.
If the box is displaying speed of 4.2 KB/ sec, the access speed is 4.2 x 8 = 33.6 Kbps i.e., approx. 33 Kilobits per second or 33 Kbps.
India Localization Set up Steps
Step 1: Define Organization Additional Information
Step 2: Define Organization Trading Information
Step 3: Define Organization Accounting Information
Step 4: Define Tax Calendar
Step 5: Define Excise Invoice Generation
Step 6: Define Sub-Inventory Locations
Step 7: Define Item Localization Information
Step 8: Define Tax Codes
Step 9: Define Tax Categories
Step 10: Define Item Categories
Step 11: Define VAT and Service Tax Regime
Step 12: Define Claim Terms
Step 13: Define VAT Invoice Sequence
Step 14: Enable Triggers (steps to be followed by new customers only)
Step 15: Define Supplier Additional Information
Step 16: Define Organization Income Tax Registration Info
Step 17: Define Income Tax Authority
Step 18: Define TDS Sections
Step 19: Define TDS Tax Codes
Step 20: Define TDS Year
Step 21: Define Supplier Additional Information - TDS Details
Step 22: Define Customs Authority
Step 23: Define BOE Agent
Step 24: Define Excise Authority
Step 25: Define VAT Authority
Step 26: Enable India Distributions Global Descriptive Flexfield segment
Step 27: Define Bond Registers
Step 28: Define Assessable Price Lists
Step 29: Define Customer Additional Information
Step 30 Define E-Business Tax Regime to Rates Setup
Step 1: Define "Party Tax Profiles"
Step 2: Define Regime
Step 3: Create Tax
Step 4: Create Tax Status
Step 5: Create Tax Rate
Step 6: Update Tax Configuration Options
Step 2: Define Organization Trading Information
Step 3: Define Organization Accounting Information
Step 4: Define Tax Calendar
Step 5: Define Excise Invoice Generation
Step 6: Define Sub-Inventory Locations
Step 7: Define Item Localization Information
Step 8: Define Tax Codes
Step 9: Define Tax Categories
Step 10: Define Item Categories
Step 11: Define VAT and Service Tax Regime
Step 12: Define Claim Terms
Step 13: Define VAT Invoice Sequence
Step 14: Enable Triggers (steps to be followed by new customers only)
Step 15: Define Supplier Additional Information
Step 16: Define Organization Income Tax Registration Info
Step 17: Define Income Tax Authority
Step 18: Define TDS Sections
Step 19: Define TDS Tax Codes
Step 20: Define TDS Year
Step 21: Define Supplier Additional Information - TDS Details
Step 22: Define Customs Authority
Step 23: Define BOE Agent
Step 24: Define Excise Authority
Step 25: Define VAT Authority
Step 26: Enable India Distributions Global Descriptive Flexfield segment
Step 27: Define Bond Registers
Step 28: Define Assessable Price Lists
Step 29: Define Customer Additional Information
Step 30 Define E-Business Tax Regime to Rates Setup
Step 1: Define "Party Tax Profiles"
Step 2: Define Regime
Step 3: Create Tax
Step 4: Create Tax Status
Step 5: Create Tax Rate
Step 6: Update Tax Configuration Options
Friday, January 16, 2009
Business Requirements Mapping (BR)
BR.010 - Prepare Mapping Environment
During this task, you either install a new application or prepare an existing application environment for mapping activities.
Deliverable
The deliverable for this task is a Configured Mapping Environment.
BR.020 - Map Business Requirements
In this task you assess the fit of standard application and system features to detailed business requirements.
Deliverable
A Business Requirements Mapping Form (BRM) is the deliverable for this task. There is one BRM per key business requirement or gap. The BRM is an extension of the BRS, since it shows the result of the mapping activity.
BR.030 - Map Business Data
For this task you map the data elements from the legacy system to the target application module(s), business objects, and attributes. The primary purpose of this task is to discover at an early point in the project life cycle whether any business objects or attributes in the legacy system are not being stored in the application. This task should also determine whether the application stores any required attributes that the legacy system does not currently store.
Deliverable
The deliverable for this task is the Business Data Mapping Form. The deliverable records the standard application module, business object, and attribute. Also record the legacy system file name and fields for each business object in the table provided in the deliverable template.
BR.040 - Conduct Integration Fit Analysis
In this task you identify the new integration points that you require, based on your conceptual architecture and the mapping of the new applications onto the existing architecture. This mapping may also include distributed data external integration points between standard applications and other third party applications. Once you agree on the business solution for each integration point gap, this task will result in a complete listing of all new integration points for which you must design and build interfaces. At this stage there has been no specification of interfaces; this task is merely a recognition that an integration point exists and requires attention.
Deliverable
The deliverable for this task is the Integration Fit Analysis document.
BR.050 - Develop Information Flow Model
This task specifies the future information usage and flow requirements across business functions, business organizations, applications and data centers. The information flow model visually depicts information flows in the business, resulting from and driven by the business events and business processes that form the business model. This task, together with the Develop Information Access Model task, creates an information view of the business.
Deliverable
The deliverable for this task is an Information Flow Model for the business.
BR.060 - Develop Information Access Model
In this task you analyze and define the Information Access Model, which describes information sharing and information partitioning requirements across organizations for the key business objects and business process information. This will assist in the definition of how information will be controlled from a security standpoint and what information can be accessed for reporting and consolidation. This task, together with the previous Develop Information Flow Model task, creates an information view of the business.
Deliverable
The deliverable for this task is a model for the information access requirements of the business. It is described in an Information Access Model document and analyzes the business organization access and security requirements. It is a major source document for these requirements for any of the processes in the project.
BR.070 - Conduct Reporting Fit Analysis
This task requires you to analyze and map every reporting requirement to both a Future Business Process and standard application report, determine the final disposition of every report requirement, and reduce the number of potential reporting customizations through requirement reduction analysis.
Deliverable
The deliverable for this task is an updated Master Report Tracking List.
BR.080 - Test Business Solutions
In this task you perform an extended test of the proposed business solutions and validate integrated business processes based on the mapping decisions. Demonstrate the BRSs and BRMs for each business process, and demonstrate integration across processes to be feasible.
Deliverable
The deliverable for this task is the Mapping Scenario document.
BR.090 - Confirm Integrated Business Solutions
In this task you secure approval for proposed business solutions. It is a prerequisite to estimating and developing detailed designs.
Deliverable
The deliverable for this task is a signed Acceptance Certificate for each set of related Business Requirements Scenarios.
BR.100 - Create Process Narratives
In this task you create narrative, job-level descriptions of business process designs.
Deliverable
The deliverable for this task is a series of Process Narratives.
BR.110 - Define Application Setups
As you map business requirements to application features, you also begin to define the configuration you need to support the solution. Your solution may include a number of user-defined codes, system and application level parameters, and enabled features. During this task, you capture the setup decisions and implement them in the appropriate environment.
Deliverable
The deliverable for this task is an Application Setup Document.
BR.120 - Design Security Profiles
As business requirements are established and mapped to application features, you also begin to define the user security necessary to support the solution in a controlled environment. During this task, you gather role and function information and relate them to application security and responsibilities.
Deliverable
The deliverable for this task is a Security Profiles document.
Business Requirements Definition - in Brief
List of AIM Deliverables
Business Requirements Definition (RD)
RD.010 - Identify Financial and Operating Structure
In this task, the project team develops a complete picture of the organization’s financial and operating structure.
Deliverable
The deliverable for this task is the Financial and Operating Structure. This document portrays the legal entity structure, business organizations, financial operating environment, revenue (and/or cost) centers, and consolidation path. It may also catalog other business entities.
RD.020 - Conduct Current Business Baseline
In this task, the project team examines current processes and practices to identify how the existing business system meets current business requirements.
Deliverable
The deliverable for this task is the Current Business Baseline. It consists of the Current Business Process model, Process Questionnaires, and the Process Improvement and Redesign List. You may need to include other business process documentation as well.
RD.030 - Develop Future Process Model
This task defines the future business model in the form of integrated process flows built upon the business processes supported by the new applications. Identify the complete set of events to which the business function responds in order to meet its objectives, describe the future processes that the business performs in order to respond to each of the events, and identify each of the steps in those processes.
Deliverable
The deliverable for this task is the Future Process Model. It consists of the Event Catalog, Process Listing and Descriptions, and Process Flow Diagrams. Optionally, it may include Process Step Catalogs.
RD.040 - Develop Future Business Function Model
In this task you create a hierarchical model of the functions identified by the Future Process Model. This classification process assists you in checking the completeness of your future business process model You usually conduct this task in parallel with and in support of Develop Future Process Model (RD.030).
Deliverable
The deliverable for this task is the Future Business Function Model. The Future Business Function Model deliverable shows all the business functions arranged in a hierarchy diagram. It also specifies the data usage at each function.
RD.050 - Establish Process and Mapping Summary
During this task you create the repository for key project findings and decisions that occur during the implementation.
Deliverable
The deliverable for this task is the Process and Mapping Summary. It provides a single source of information on key implementation decisions for new project members and executive management. The Project Manager can also use it to maintain a status on the progress of deliverables in requirements definition through build and test.
RD.060 - Gather Business Volumes
In this task you research the current business volumes and estimate the future projected operational processing volumes, transaction patterns, and data storage volume requirements. This information provides the basis for determining the size and performance of the new production system.
Deliverable
The deliverable for this task is the Business Volume Requirements.
RD.070 - Create Business Requirements Scenarios
In this task you define detailed business requirements and perform an initial assessment of application fit to these requirements.
Deliverable
The deliverable for this task is the Business Requirements Scenarios (BRS). At least one BRS is created for each business process, linking requirements to process steps.
RD.080 - Determine Audit and Control Requirements
This task identifies the high levels and policies that affect business and system security, control, and procedures.
Deliverable
The deliverable for this task is the Audit and Control Requirements.
RD.090 - Identify Business Availability Requirements
This task identifies the business operating requirements that the operating functions and information systems functions agree are necessary to support the business processes. It also summarizes contingency situations the company must guard against and documents the approach to managing delay, failure, or other unexpected results that could imperil daily business operations.
Deliverable
The deliverable for this task is the Business Availability Requirements document.
RD.100 - Develop Reporting Requirements
In this task you develop the reporting requirements. Reports are typically outputs of business processes that are used as tools in support of business process operations.
Deliverable
The deliverable for this task is the Master Report Tracking List. It is the primary repository for all information collected about a report requirement. It should contain system and report name, business purpose, frequency, priority, user name and contact information.
Business Requirements Definition (RD)
RD.010 - Identify Financial and Operating Structure
In this task, the project team develops a complete picture of the organization’s financial and operating structure.
Deliverable
The deliverable for this task is the Financial and Operating Structure. This document portrays the legal entity structure, business organizations, financial operating environment, revenue (and/or cost) centers, and consolidation path. It may also catalog other business entities.
RD.020 - Conduct Current Business Baseline
In this task, the project team examines current processes and practices to identify how the existing business system meets current business requirements.
Deliverable
The deliverable for this task is the Current Business Baseline. It consists of the Current Business Process model, Process Questionnaires, and the Process Improvement and Redesign List. You may need to include other business process documentation as well.
RD.030 - Develop Future Process Model
This task defines the future business model in the form of integrated process flows built upon the business processes supported by the new applications. Identify the complete set of events to which the business function responds in order to meet its objectives, describe the future processes that the business performs in order to respond to each of the events, and identify each of the steps in those processes.
Deliverable
The deliverable for this task is the Future Process Model. It consists of the Event Catalog, Process Listing and Descriptions, and Process Flow Diagrams. Optionally, it may include Process Step Catalogs.
RD.040 - Develop Future Business Function Model
In this task you create a hierarchical model of the functions identified by the Future Process Model. This classification process assists you in checking the completeness of your future business process model You usually conduct this task in parallel with and in support of Develop Future Process Model (RD.030).
Deliverable
The deliverable for this task is the Future Business Function Model. The Future Business Function Model deliverable shows all the business functions arranged in a hierarchy diagram. It also specifies the data usage at each function.
RD.050 - Establish Process and Mapping Summary
During this task you create the repository for key project findings and decisions that occur during the implementation.
Deliverable
The deliverable for this task is the Process and Mapping Summary. It provides a single source of information on key implementation decisions for new project members and executive management. The Project Manager can also use it to maintain a status on the progress of deliverables in requirements definition through build and test.
RD.060 - Gather Business Volumes
In this task you research the current business volumes and estimate the future projected operational processing volumes, transaction patterns, and data storage volume requirements. This information provides the basis for determining the size and performance of the new production system.
Deliverable
The deliverable for this task is the Business Volume Requirements.
RD.070 - Create Business Requirements Scenarios
In this task you define detailed business requirements and perform an initial assessment of application fit to these requirements.
Deliverable
The deliverable for this task is the Business Requirements Scenarios (BRS). At least one BRS is created for each business process, linking requirements to process steps.
RD.080 - Determine Audit and Control Requirements
This task identifies the high levels and policies that affect business and system security, control, and procedures.
Deliverable
The deliverable for this task is the Audit and Control Requirements.
RD.090 - Identify Business Availability Requirements
This task identifies the business operating requirements that the operating functions and information systems functions agree are necessary to support the business processes. It also summarizes contingency situations the company must guard against and documents the approach to managing delay, failure, or other unexpected results that could imperil daily business operations.
Deliverable
The deliverable for this task is the Business Availability Requirements document.
RD.100 - Develop Reporting Requirements
In this task you develop the reporting requirements. Reports are typically outputs of business processes that are used as tools in support of business process operations.
Deliverable
The deliverable for this task is the Master Report Tracking List. It is the primary repository for all information collected about a report requirement. It should contain system and report name, business purpose, frequency, priority, user name and contact information.
AIM Process - Quick Reference
"AIM methodology is a set of guidelines or principles that can be tailored and applied to a specific situation." In a project environment, these guidelines might be a list of things to do. A methodology could also be a specific approach, templates, forms, and even checklists used over the project life cycle. Therefore that was the driving factor for bringing AIM's as methodology which was initially used by Oracle consulting, which is now most acceptable methodology for oracle application roll out. The AIM Advantage product gives you all the tools you need to make your implementation successful by providing guidelines for:
* Business Process Architecture
* Business Requirements Definition
* Business Requirements Mapping
* Application and Technical Architecture
* Module Design and Build
* Data Conversion
* Documentation
* Business System Testing
* Adoption and Learning
* Performance Testing
* Production Migration
AIM Processes
A process in AIM represents a related set of objectives, resource skill requirements, inputs, and deliverable outputs. A task can belong to only one process. Project team members are usually assigned to a process according to their specialization and background. A brief description of the AIM processes are given below:
1. Business Requirements Definition: Business Requirements Definition defines the business needs that must be met by the implementation project. You document business processes by identifying business events and describing the steps that respond to these events.
2. Business Requirements Mapping: Business Requirements Mapping compares the business requirements to standard application software functionality and identifies gaps that must be addressed to fully meet business needs. As gaps between requirements and functionality emerge, they are resolved by documenting workarounds, alternative solutions, application extensions, or by changing the underlying business process.
3. Application and Technical Architecture: During the Application and Technical Architecture you design an information systems architecture that reflects your business vision. Using the business and information systems requirements, this process facilitates development of a plan for deploying and configuring the hardware required for a successful implementation.
4. Module Design and Build: Module Design and Build produces custom software solutions to gaps in functionality identified during Business Requirements Mapping. Custom software solutions include program modules that must be designed, built, and tested before they can be incorporated into the system.
5. Data Conversion: Data Conversion defines the tasks and deliverables required to convert legacy data to the Oracle Applications tables. The first step of this process explicitly defines the business objects that are required for conversion and the legacy source systems that store these objects. The converted data may be needed for system testing, training, and acceptance testing as well as for production.
6. Documentation: Documentation begins with materials created early in the project. Using detailed documents from the project, the writing staff develops user and technical material that are tailored to the implementation.
7. Business System Testing: Business System Testing focuses on linking test requirements back to business requirements and securing project resources needed for testing. It supports utilizing common test information including data profiles to promote testing co-ordination and to minimize duplication of test preparation and execution effort.
8. Performance Testing: Performance Testing enables you to define, build, and execute a performance test. Use the results to make decisions on whether the performance is acceptable for the business and to help propose tactical or strategic changes to address the performance quality shortfall. Performance Testing is closely related to Application and Technical Architecture; they are interdependent.
9. User Training: Training prepares both users and administrators to assume on the tasks of running the new application system. It includes development of materials and methods as well as administration. Instructors and course ware developers orient their material toward roles and jobs, and not toward application modules.
10. Production Migration: Production Migration moves the company, system, and people to the new enterprise system. Following production cut over, it monitors and refines the production system and plans for the future. The Production Migration process encompasses transition to production readiness, production cut over, and post-production support
AIM Phases:
An AIM project is conducted in phases that provide quality and control checkpoints to co-ordinate project activities that have a common goal. During a project phase, your project team will be executing tasks from several processes. A brief description of the AIM processes are given below:
1. Definition: This consist of review the organization's business objectives, evaluate the feasibility of meeting those objectives under time, resource, and budget constraints. Moreover this can be best consider as SOW(statement of work) preparation phase.
2. Operations Analysis: During Operations Analysis, the project team develops Business Requirements Scenarios based on deliverables from Definition that are used to assess the level of fit between the business requirements and standard application functionality. Gaps are identified and corresponding solutions developed. The analysis results in a proposal for conducting business operations under the envisioned application technical architecture. Solutions for gaps evolve into detailed designs during Solution Design.
3. Solution Design: The purpose of Solution Design is to develop the detailed designs for the optimal solutions to meet the future business requirements. During this phase, project team members create detailed narratives of process solutions developed during Operations Analysis. Supporting business requirements may require building application extensions to standard features; several alternative solutions may have been defined during Operations Analysis. The project team carefully scrutinizes these solutions and chooses the most cost effective alternatives.
4. Build: The coding and testing of all customizations and other custom software including enhancements, data conversions, and interfaces is done during Build. Policy and procedure changes relating to business process modifications are developed. Business system testing is performed to validate that the developed solutions meet business requirements. If customizations, extensions, or conversions are not required, Build is still important because it includes the business system test, which is commonly conducted as a formal conference room pilot. The business system test validates the solutions and is performed in an environment that closely resembles production.
5. Transition: During Transition, the project team deploys the finished solution into the organization. All the elements of the implementation must come together to transition successfully to actual production. The project team trains the end users while the technical team configures the production environment and converts data. Transition ends with the cutover to production, when end users start performing their job duties using the new system.
6. Production: Production begins immediately with the production cutover. It marks the last phase of the implementation, and the beginning of the system support cycle. Included in this final phase is a series of refinements and performance measurement steps. The in house MIS/IT Department personnel work quickly to stabilize the system and begin regular maintenance. They will provide the ongoing support to the organization for the remaining life of the system. During Production, you compare actual results to project objectives.
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 template 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 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
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 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
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 setup’s and functionality by QA (functional consultant) to certify status.
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
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 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 Transaction Programs
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 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 Communication Campaign
AP.090 - Develop Managers’ Readiness Plan
AP.100 - Identify Business Process Impact on Organization
AP.110 - Align Human Performance Support Systems
AP.120 - Align Information Technology Groups
AP.130 - Conduct User Learning Needs Analysis
AP.140 - Develop User Learning Plan
AP.150 - Develop User Learning ware
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
* Business Process Architecture
* Business Requirements Definition
* Business Requirements Mapping
* Application and Technical Architecture
* Module Design and Build
* Data Conversion
* Documentation
* Business System Testing
* Adoption and Learning
* Performance Testing
* Production Migration
AIM Processes
A process in AIM represents a related set of objectives, resource skill requirements, inputs, and deliverable outputs. A task can belong to only one process. Project team members are usually assigned to a process according to their specialization and background. A brief description of the AIM processes are given below:
1. Business Requirements Definition: Business Requirements Definition defines the business needs that must be met by the implementation project. You document business processes by identifying business events and describing the steps that respond to these events.
2. Business Requirements Mapping: Business Requirements Mapping compares the business requirements to standard application software functionality and identifies gaps that must be addressed to fully meet business needs. As gaps between requirements and functionality emerge, they are resolved by documenting workarounds, alternative solutions, application extensions, or by changing the underlying business process.
3. Application and Technical Architecture: During the Application and Technical Architecture you design an information systems architecture that reflects your business vision. Using the business and information systems requirements, this process facilitates development of a plan for deploying and configuring the hardware required for a successful implementation.
4. Module Design and Build: Module Design and Build produces custom software solutions to gaps in functionality identified during Business Requirements Mapping. Custom software solutions include program modules that must be designed, built, and tested before they can be incorporated into the system.
5. Data Conversion: Data Conversion defines the tasks and deliverables required to convert legacy data to the Oracle Applications tables. The first step of this process explicitly defines the business objects that are required for conversion and the legacy source systems that store these objects. The converted data may be needed for system testing, training, and acceptance testing as well as for production.
6. Documentation: Documentation begins with materials created early in the project. Using detailed documents from the project, the writing staff develops user and technical material that are tailored to the implementation.
7. Business System Testing: Business System Testing focuses on linking test requirements back to business requirements and securing project resources needed for testing. It supports utilizing common test information including data profiles to promote testing co-ordination and to minimize duplication of test preparation and execution effort.
8. Performance Testing: Performance Testing enables you to define, build, and execute a performance test. Use the results to make decisions on whether the performance is acceptable for the business and to help propose tactical or strategic changes to address the performance quality shortfall. Performance Testing is closely related to Application and Technical Architecture; they are interdependent.
9. User Training: Training prepares both users and administrators to assume on the tasks of running the new application system. It includes development of materials and methods as well as administration. Instructors and course ware developers orient their material toward roles and jobs, and not toward application modules.
10. Production Migration: Production Migration moves the company, system, and people to the new enterprise system. Following production cut over, it monitors and refines the production system and plans for the future. The Production Migration process encompasses transition to production readiness, production cut over, and post-production support
AIM Phases:
An AIM project is conducted in phases that provide quality and control checkpoints to co-ordinate project activities that have a common goal. During a project phase, your project team will be executing tasks from several processes. A brief description of the AIM processes are given below:
1. Definition: This consist of review the organization's business objectives, evaluate the feasibility of meeting those objectives under time, resource, and budget constraints. Moreover this can be best consider as SOW(statement of work) preparation phase.
2. Operations Analysis: During Operations Analysis, the project team develops Business Requirements Scenarios based on deliverables from Definition that are used to assess the level of fit between the business requirements and standard application functionality. Gaps are identified and corresponding solutions developed. The analysis results in a proposal for conducting business operations under the envisioned application technical architecture. Solutions for gaps evolve into detailed designs during Solution Design.
3. Solution Design: The purpose of Solution Design is to develop the detailed designs for the optimal solutions to meet the future business requirements. During this phase, project team members create detailed narratives of process solutions developed during Operations Analysis. Supporting business requirements may require building application extensions to standard features; several alternative solutions may have been defined during Operations Analysis. The project team carefully scrutinizes these solutions and chooses the most cost effective alternatives.
4. Build: The coding and testing of all customizations and other custom software including enhancements, data conversions, and interfaces is done during Build. Policy and procedure changes relating to business process modifications are developed. Business system testing is performed to validate that the developed solutions meet business requirements. If customizations, extensions, or conversions are not required, Build is still important because it includes the business system test, which is commonly conducted as a formal conference room pilot. The business system test validates the solutions and is performed in an environment that closely resembles production.
5. Transition: During Transition, the project team deploys the finished solution into the organization. All the elements of the implementation must come together to transition successfully to actual production. The project team trains the end users while the technical team configures the production environment and converts data. Transition ends with the cutover to production, when end users start performing their job duties using the new system.
6. Production: Production begins immediately with the production cutover. It marks the last phase of the implementation, and the beginning of the system support cycle. Included in this final phase is a series of refinements and performance measurement steps. The in house MIS/IT Department personnel work quickly to stabilize the system and begin regular maintenance. They will provide the ongoing support to the organization for the remaining life of the system. During Production, you compare actual results to project objectives.
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 template 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 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
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 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
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 setup’s and functionality by QA (functional consultant) to certify status.
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
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 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 Transaction Programs
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 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 Communication Campaign
AP.090 - Develop Managers’ Readiness Plan
AP.100 - Identify Business Process Impact on Organization
AP.110 - Align Human Performance Support Systems
AP.120 - Align Information Technology Groups
AP.130 - Conduct User Learning Needs Analysis
AP.140 - Develop User Learning Plan
AP.150 - Develop User Learning ware
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
Subscribe to:
Posts (Atom)
