Important Interview Questions

Difference between per_all_people_f ,per_people_f and per_people_x
per_all_people_f-contain all employee
per_people_x- show effective employee on sysdate
per_people_f- show u all employee according to security profile options of logged in user

Oracle AIM

HI All i am sharing some of my useful notes on AIM

AIM is comprised of well-defined processes that can be managed in several ways to guide you through an application implementation project. AIM provides the tools needed to effectively and efficiently plan, conduct, and control project steps to successfully implement new business systems.
Aim implement in phase.check points coordinate project activities

1. Definition
2. Operations
3. Analysis
4. Solution Design Build Transition Production

List Of processes Done in AIM Phases

1. Business Process Architecture
2. Business Requirements Definition
3. Business Requirements Mapping
4. Module Design and Build
5. Application and Technical Architecture
6. Data Conversion
7. Documentation
8. Business System Testing
9. Performance Testing
10. Adoption and Learning
11. Production Migration

AIM is very broad in its support of all of the activities within your implementation project including:

1. • planning
2. • requirements definition
3. • business process alignment and modeling
4. • customization
5. • interfaces and integration between systems
6. • data conversion
7. • organization change management including specific support for
8. executive, management, and user groups
9. Oracle Method Introduction to AIM 1 - 3
10. • application and technical architecture including network and
11. server design
12. • reporting and information access systems
13. • security and access control

AIM defines an organization’s business needs at the beginning of the
project and maintains their visibility throughout the implementation. It
defines internal, external, and time-sensitive business events, and maps
each event to the corresponding business and system processes. Using
this method, the business community gains an accurate understanding
of the business requirements to be met by the final system. Where
appropriate, business process techniques are employed within AIM to
assist the project team in identifying the need for business process
changes and designing the changes.
predefined
approaches, such as Fast Forward, or allows you to tailor your own
approach to match your organization’s specific needs.
AIM is adaptable extend able and sacalable
download from web up to date versions

During Definition, you plan the project, review the organization’s
business objectives, understand the business processes, and evaluate the
feasibility of meeting those objectives under time, resource, and budget
constraints. The emphasis is on building an achievable workplan and
introducing guidelines on how the organization will work to achieve
common objectives. Establishing scope early in the implementation
gives the team a common reference point and an effective way to
communicate. Strategies, objectives, and approaches are determined for
each AIM process, providing the basis for the project plan.
baselining and process modeling during this phase.
if fature expection change than u design high level fature modeling and design.RD050 deliverable of Definition pahse

Operation Analysis
RD050 deliverable of Definition Phase
Solution and proposed
gap analysis
Description of solution
Future design of app requirement.
more details is done in solution design
To develop models of future business operations, you must verify your
initial assumptions regarding proposed functionality for gaps. The new
system may require only minor modifications to forms, reports, and
programs. The team should explore workarounds to application gaps
before considering custom modifications or new developments. If the
new system requires custom development, the team prepares high-level
design documents. These documents include general descriptions of
the required features and a work estimate for each customization. The
approach to be taken for the customizations and estimates are approved
before detailed design begins during Solution Design.
Finally, a Transition Strategy (PM.010) is developed for migrating the
organization from the current system to the new production system.

Definition phase of AIM has 11 Processes

1. Business Process Architecture
2. Business Requirements Definition
3. Business Requirements Mapping
4. Module Design and Build
5. Application and Technical Architecture
6. Data Conversion
7. Documentation
8. Business System Testing
9. Performance Testing
10. Adoption and Learning
11. Production Migration

Business Process Architecture (BP)

Business Process Architecture addresses understanding of the  organization’s business processes and aligns them with the business requirements and applications to be implemented

Scope the processes and other aspects of the business that are included

in the AIM project.determine the potential for making improvements.

The critical success factors of the Definition phase are as follows:

1. • sponsorship of senior management that is clear and visible to the project stakeholders
2. • clear definition of the business objectives
3. • active participation by key management and knowledgeable users and technical representatives from the areas of the business affected by the project’s objectives • access to information related to the existing business processes and systems affected by the project

Definition phase processes
The processes used in this phase follow:
Business Process Architecture (BP)

1. Align the business processes according to the organization.
2. Find the processes to be changed.
3. High Level process design. BP070.

Business Requirements Definition (RD)

1. Get the complete idea of org business processes and definitions.

Application and Technical Architecture (TA)

1. Identify the requirements that influence the architecture and define the
2. strategy for satisfying those requirements.
3. Create an initial integrated conceptual model of the application and technical architecture.

Module Design and Build (MD)

1. Define a strategy for extending and customizing the applications and developing custom interface software.

Data Conversion (CV)

1. Identify the data conversion requirements and define the strategy for converting the legacy data.

Documentation (DO)

1. Doc standard and procedures.

Documentation (DO)
Testing Strategy

1. Overview of testing approach.
2. type of test script to be developed.
3. schedule of testing resources and responsibilities
4. testing tools and environments required, and a discussion of the problem management process.

Definition Phase deliverable



Communication
Communication must remain a focus across the entire project and throughout the entire project organization from the steering committee to the user. Effective communication enables sharing of the business imperatives driving the change, a clear definition of the objectives, and the performance measures used to measure progress
Risk

1. Unclear expectations- Take Time to clear objective and performance.  Regular communication to manage expectations.
2. Lack Of involvement  or sign Off by senior key management  -Discuss on conceptual (Domain Model )architecture and as appropriate.

Integration Management
Focus on integration issues between teams, business processes,
organizations, and applications and identify and resolve integration
issues through communication and definition of standards and
procedures. Integration tasks are done in following

1. business processes design
2. systems testing strategies
3. integration between functional and technical teams
4. interfaces between Oracle Applications and third-party or
5. legacy systems
6. data cleanup and conversion strategies

Consider business requirements and functional mapping as well as technical requirements as drivers for the optimal configuration and deployment of the applications being implemented.
Have both functional and information processing management review and agree upon volume and processing windows.
Planning
Planning is critical for maintaining project focus and direction. Initially
the overall project plan is developed and the implementation strategy
defined. As each phase progresses, subsequent phases are planned in
detail. Plans include the people, tools, strategies, and procedures for
accomplishing the objectives of the phase.

Project Organization/Leadership
The executive leadership of the organization must actively and visibly support the implementation effort.


Module Design and Build (MD)
A worthwhile goal of any implementation is to use the Applications as they were designed; in other words, without customization. However, most projects include custom development, even if it is limited to interfaces and custom reports. Descriptive flexfields and alerts are also
customizations, even though you can implement them without traditional coding. The Application Extension Strategy (MD.010) outlines the customization philosophy, suh as minimizing customization as much as possible. It also describes the development tools developers will use for each type of module. An important part of the strategy is how much overlap is acceptable between phases. For example, some of the functional teams may
complete their mapping earlier than others. Should designers begin writing design documents for required application extensions before other teams have completed their mapping? After the

team approves An important part of the strategy is how much overlap is acceptable between implementation phases it increases the risk ofrework since approaches arrived at later may affect earlier decisions



Operations Analysis phase of AIM. The goal of the Operations Analysis phase is to determine the high-level business and information system requirements necessary to meet a set of defined business objectives. The Operations Analysis phase results in a clear definition of a project’s functional scope.

Custom AME Implementation for Payment approval

HI
In this post i will explain how to implement custom payment approval with the help of AME.