What are Steps for Report Development in Apps?

What are Steps for Report Development in Apps?

Steps for Report Development....

1. Develop the report as per client requirement using the Report-6i tool.

2. Move the report (.rdf) file from local machine to respective path in the server. If client have the CUST_TOP then move into Cust_Top else move it to the related Standard Top.Custom Top - CUST_TOP/ 11.5.0/ Report/ US/ .rdf Standard Top - PO_TOP/ 11.5.0/ Report/ US/ .rdf (For PO report)

3. Create “Executable” for that report (After log on to Oracle Applications and Select “System Administrator” responsibility)

4. Create “Concurrent Program” and attach Executable to Conc. Prgm. and define Parameters and Incompatibles if any.Concurrent Program: It is an instance of the executable file along with parameters & incompatible.

5. Create “Request Group” and attach Conc. Prgm. to Request Group.Request Group is nothing but a collection of Conc. Prgms.

6. Create “Responsibility” and attach the Request Group to Responsibility.

7. Create “User” attach Responsibility to User”
             so that the user can run this Conc. Prgm. form the “SRS Window” (Standard Request Submission).

Note: All the Conc. Prgms. should run from the SRS window (Even if we run from Back-End)By default the user has the rights of System Administrator or Application Developer responsibilities

Every form in Oracle Applications contains 3-Types of Fields.
    1. Yellow color – Mandatory2. Green Color – Read-Only3. White Color – Optional

How to Create New User in Oracle Apps?
User Creation: Open IE and type path of Oracle Application in address bar enter User Name and Password

User Name: OPERATIONS  Password: WELCOME

Select System Administrator Responsibility
Select Security / User / Define  Give the required information and Save.
 Switch the user to newly created  User.
 Note: When we create any User, the User stored at FND_USER.

How we can find the Table names of Apps Screen?
We can find through Help => Record-History => FND_USER

How to find Column Name from front end Apps Screen :
To find all column names: Help => Diagnostics => Examine

What is WHO Columns and How many WHO Columns in Oracle Apps?
Ans : 4 types of who columns for each table in Oracle Applications
Created By  Creation Date  Updated By  Updated Date

What are Types of Documents in Oracle Applications :

AIM (Application Implementation Maintenance) developed by Oracle Applications.
MD050 - Module Design - By Functional Consultants
MD070 - Technical Document Design - By Technical Consultants
MD020 - Testing Document Design - By Functional Consultants
MD0120 - Migration/ User Training - By Technical Consultants
CV040 - Conversion of Functional Document - By Functional Consultants
CV060 - Conversion of Technical Document - By Technical Consultants
Note: Conversion means, moving data from old Database to new Database.
Example: Conversion from IBM to ORA APPS


AIM Document List



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 Archtecture

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

What is Multi Org?

Q. What is Multi Org Architecture?
A. The Multiorg Architecture is meant to allow multiple companies
or subsidiaries to store their records within a single database.
The multiple Organization architecture allows this by partitioning data
through views in the APPS schema. Multiorg also allows you to maintain
multiple sets of books. Implementation of multiorg generally includes
defining more than one Business Group.

Q. How can I know if I am using Multi Org?
A. Run the SQL statement:
select multi_org_flag
from fnd_product_groups;
The result 'Y' means your database is setup for multiorg.

Q. What are the relationships I can define in a multi org environment?
A. You define the relationships among inventory organizations,
operating units, legal entities, Business Groups, and sets of books to
create a multilevel company structure:
. Business Groups separate major segments of a business. Each can have
it's own set of books. Each Group will also have a structure of other
organizations classifications assigned to it.
· Legal Entities post to a Set of Books
· Operating Units are part of a Legal Entity
· Inventory Organizations are part of an Operating Unit
· Inventory Organizations define and maintain items used by other
manufacturing modules (Order Entry, Purchasing, MRP, etc.). They also
collect and pass data to the Financials modules.

Q. I want to Setup Additional Organizations, do I have to setup Multiorg?
A. No, you do not need to setup multiorg. You do not have to be
multi-org to have multiple organizations only if you intend to have multiple
sets of books.

Q. Is there any documentation on how to setup an organization?
A. · Refer to "Oracle Manufacturing Implementation Manual" part#A50765.
· Refer to "Multiple Organizations in Oracle Applications"
part#A58478 for Release 11 and part#50771 for Release 10.
· Also refer to note 76440.1 for Organization setup steps.

Q. When my organization hierarchy changes, can I move an organization from
one set of books or legal entity to another?
A. No, you should not try to move an organization from one set of books
or legal entity to another because your data may not be valid for the
new set of books or legal entity. Instead, you should disable the old
organization and create a new organization for the appropriate set of
books or legal entity. The new organization will contain your new data,
and the disabled organization will act as an "old" or "history" entity
that stores past transactions.

Q. How can I setup a child org to be its own costing organization?
A. Steps:
· Change the attribute control for "default category set" to organization level
· Change the attribute control for "costing enabled" to organization level
· Change the attribute control for "inventory asset value" to organization control
Then you can make a child organization it's own costing organization by
entering the organization name in the column labeled "Costing Organization"

Q. How can I define organization restriction?
A. Use the Organization Access form (INVSDORA) to restrict the list of organizations
displayed for each responsibility level.
Refer to Oracle Inventory User's Guide for steps and important notes.
*WARNING* If you populate any rows in this form, you MUST populate a row for
EACH responsibility that you wish to have access to that Organization.

Q. What responsibility do I need to use to setup organization?
A. Use the General Ledger responsibility to define the Set of Books
Use the Inventory Responsibility to define Organizations and other related
information such as Inventory Key Flexfields, Locations, Workday calendar,
other Organization Classifications, and other inventory information.

Q. What are the main profile options relating to Organization setup and
what are they used for?
A. · HR:User Type = HR User
This is necessary to allow the Inventory responsibility to complete
the organization setup. Setting the profile to a value of 'User' as
opposed to 'Payroll & User' will restrict the Inventory user from
accessing any Payroll information if Oracle Payroll is installed.
· HR: Business Group = {the users Business Group name}
This points the responsibility to the appropriate Business Group.
When multiple Business Groups are defined, you must associate
each responsibility with one and only one Business Group.
A responsibility can not see organization data from more than
one Business Group.
· MO: Operating Unit = {the users Operating Unit name}
Used primarily in a multiorg environment.
This points the responsibility to the appropriate Operating Unit.
Set the site level to the desired default operating unit.
If there is more than 1 Operating Unit Defined,
this profile option must be set at the responsibility level
for each responsibility.

Which are Concurrent Executables in Oracle Apps? How many Types of Concurrent Programs?

There are 11 types of executables

1. Reports - .rdf

2. SQL * Plus - .SQL

3. PL/SQL Procedures - .pkb / .pks

4. SQL * Loader file - .ctl

5. Java Structured Procedure - .java / .class

6. Host(UNIX) - .sb

7. Spawned

8. Immediate

9. Java Concurrent Program

10. Request set stage Function

11. Multi-Language Function.

Note: Once moving are programs to Oracle Applications they will be convert to “CONCURRENT PROGRAM”.

Concurrent Process: Simultaneously executes program running in the background with online operations to fully utilize the hardware capacity.

Concurrent Program: Can write a program that runs as a concurrent process. Use concurrent program for long running, data-intensive tasks.

Major features: On-line requests
Automatic scheduling
Concurrent processing
Online request review
Concurrent manager
Simultaneous queuing

On-line Request: You and end-user can submit requests from forms to start any concurrent program.

Automatic Scheduling: Oracle Application Object Library automatically schedules requests based on when they were submitted, their priority, and their compatibility with programs those are already running.

Concurrent Manager: Cocurrent Managers are components of concurrent processing that monitors and run, time-consuming, non-interactive tasks without tying up your terminal.

Concurrent manager processes requests and does the work in the background, giving the ability to run multiple tasks simultaneously.

Internal Concurrent Manager starts up, verifies the status of, resets, and shuts down the individual managers.

Simultaneous Queuing: It lets requests wait in many queues at once to ensure that the first available concurrent manager starts the request.

Concurrent Program Executable: Links an execution file and the method used to execute it with defined concurrent program. This mathod may be a program written in standard language, a reporting tool, or an operating system language.

A Concurrent program execution file is an operating system file or database stored procedure.

Concurrent Program Definition: A concurrent program is an instance of an execution file, along with parameter definitions and incompatibilities. Concurrent programs use concurrent program executables to locate the correct execution file.

Concurrent Program written in: Oracle reports, PL/SQL package procedures, SQL *Loader, SQL *Plus, Host script.

Parent request: A parent request is a concurrent request that submits another concurrent request.

Child request: A child request is a concurrent request submitted by another concurrent request.

Concurrent Manager: Concurrent Managers are components of Concurrent Processing that monitor and run, time-consuming,non-interactive tasks without tying up terminal.

Whenever request submits to run a task, a concurrent manager processes that request and does the work in background, giving the ability to run multiple tasks simultaneously.

Introduction :

This Blogs for all Oracle Apps Lovers.....

To gain competitive advantage or to support new business requirements, organizations may have the requirement to extend the Oracle E-Business Suite with their own modules. Oracle development tools, together with Headstart for Oracle Applications, provide this flexibility. With this mature tool stack you can generate extensions from Oracle Designer in a very productive and flexible manner.