Oracle Apps R-12 Technical

Oracle is a Database Package

Database is a collection of Information
To enter the data into the Oracle, first we need to Create a Table which contains Rows and
Column.
Enter the values into the Tables, all the database tables are located at the backend only. At any
time, we can manipulate the data of tables.
Oracle Apps Technical is the ERP Package
ERP: Enterprise, Resource and Planning.
 It is a one Business Suite
 ERP is a collection of different modules:
o Oracle Financial
o Oracle SCM
o Oracle CRM
o Oracle HRMS
o Oracle Apps Technical

Technical: Technical is a backend process as a technical consultant we ae going to develop and

customize the applications
Applications:
 Oracle Financial:
o General Ledger
o Account Payable
o Account Receivable
o Fixed Assets
o Cash Management

 Oracle SCM:
o Purchasing
o Inventory
o Order Management
We are going to Develop a Form and Report in this module only
As a Technical consultant, we are going to work on the RICE components
 RICE:
R= Reports (Report is a one specified structured format only)
If you want to see the backend data into the front end in even a specified format, at the
time we are going to develop report only.
Oracle apps having different report:
Developing process are two types:
o Developing of a new report from scratch
o According to the requirement of Client, we are going to develop a new report
o How to develop new report:
o With help of the Tables
o Report Builder Tool (Standard toll provided by Oracle application), with
the help of this tool we are going to register the report only.
o After developing the report, then we have to register the report in Apps
module.
o Customization:
o Already there is a Standard report for each and every module. Any one std
report is not suitable for client requirement that time we need to go for
Customization.
o Making some changes in existing report
o After changes completed, save changes, and Re-run the report
o After Run he report, you will able to see what customization are completed.
o We can do the customization with the help of Report Builder tool only.
I = Interface (Interface is transferring the Data from one location to another location)
o Suppose client has given you the data in Text file, Flat file, Excel file means there is no
structure for the data and asked you to input this data in Oracle application only that
time we can insert that data with the help of Interface
o Using of interface whatever the non-legacy data, non-oracle data, apart from table any
type of data you can insert data into oracle application table only with help of this
Interface.
o Already there is standard interface for each and every module. Whenever you want to
move the data from flat file into oracle apps table that we are going to use this
Interface.
C= Conversion (It is a Migration / Upgradation)
o We are going to convert the data from one version to another version.
 o Version: Oracle application version is R-12. Oracle R-12 version support 11g database
and 11g database support 10g forms and 10g reports.
o We cannot covert the version directly from one to another. We have to convert the data
step by step means if the version is 11.5.10 and we want to convert it in R-12. first, we
need to covert it in 11.5.11 then 11.5.12 then R-12. (Step by step we have to covert the
data)
o Conversion / Migration is a single line process not repeated process. only one time we
are going to do the conversion of the data.
E= Extension (Files Extensions)
1. File Extension:
o In oracle application will get different type of file extension.
o At the time of developing a report or developing a form / customizing the report /forms
that time will get the extensions only.
o After developing a report using report builder tool, we are going to save the report in
specified format / specified location and at the time of saving by default it takes the
extension of RDF (Report data file)
o RDF (Report Data File): It is data file, user language file / Source code file.
o After getting the RDF file, move RDF file onto specified location and register the RDF file
into the AOL Module (Application Object Library)
o At the time of Registration, we required to follow Five (5) Steps Mandatorily:
o Executable
o Concurrent Program
o Request Group
o Responsibility
o Responsibility attached to User
o After creating all these five steps, user login to the responsibility and then call
concurrent program. After calling concurrent program, if program is successfully
executed then we will get report output and report is displayed.
o This is for development of new report, we must ensure all the steps are completed

o For Customization: Customization means report / RDF is there already, we have to open
that RDF with the help of Report Builder tool only.
o After opening the file, we are going to make required changes and save the changes in
same RDF format but this time we need not to register the report because that is
already registered report.
o We just upload the report on specified location and then re-run the report, after re-run
Whatever the changes we have completed that changes we can able to see at the time
of generating the report
 2. Forms (2nd Extension):
o Form is a one front end application.
o Using of Forms, we are going to manipulating the backend database.
o With the help of From Builder Tool, this is also a standard tool by oracle, we can
develop a form
o After developing, we have to save the form as a file name with the extension of FMB
(Form Module Builder)
o FMB (Form module builder): It is a building file only.
o After getting the FMB file, we have to go for the compilation module, once the
compilation is completed, Complier will create Executable file with same file name, but
the extension is changed from FMB to FMX (Executable file).
o After getting both the files (FMB and FMX), move the FMB file at one specified location
and FMX file at another location and register the form into the AOL Module
o To Register the Form in AOL Module, we need to follow the five (5) steps mandatorily:
o Create a Form
o Function
o Menu
o Responsibility
o Responsibility attached to the User
o After that User login to the responsibility and they can call Function, if the Function is
successfully completed you will get the run time form.
o On the Run time form, we can perform all the DML operations, whatever operations we
perform all the values are save into the backed table only.
Technical Topics which are covered in this training:
o Introduction to ERP
o Type of Roles
o Application Object Library (AOL)
o Application Development
o Registration of Custom Objects (Database Object: Tables)
o Interfaces and Conversions
o Flex Fields
o Profiles
o Value Sets
o Multi Org Concepts
o Functional Module Overview
o Reports
o Forms
Definition of ERP
Introduction of Oracle Application
Types of Data

1. Definition of ERP:

ERP: Enterprise, Resource and Planning

o Enterprise is nothing but the Organization

o Resources are the five types:
o Man
o Material
o Money
o Time
o Place
o Planning: Planning is nothing but the Pre-planned Activities (Format)
Meaning of ERP: In the Enterprise, how to utilize these five resources and using these
resources how will get maximum output.

2. Oracle Applications:

o Oracle is a Database Package

o Database is a collection of Information
o Tables is a structure of Database
o To enter the data into the Oracle, first we need to Create a Table which
contains Rows and Column.
o We have to use SQL (Structure Query Language) to create a rows and
columns
o After Inserting data into the table, table will store into the backend only.
o Oracle is divided into three (3) sections:
 SQL
 PL-SQL
 Developer 2000 (Forms & Reports Application)
o In SQL, always we have to write a single line statement i.e., Queries
 o In PL-SQL, we are going to write a program, Program is a set of instructions
in one block we can write a multiple statement.
o While developing Forms and Reports, we required some programming and
some queries also.
o After developing the database in oracle, after manipulating the database
values are saved into the backend only.
There are different types of Oracle applications available in market:
o Peoplesoft
o Siebel
o JD Edwards
o Oracle application are used to capture the Business functionality
information of the organization.
o The organization functionality given by the oracle application, they
capture the information of organization and stored it in the database
o In Oracle application there is a different types of Instances
 Instances:
 Development (vision Instance)
 Production Instance
 Test Instance

Development / Vision Instance:

o With the help of vision instance, we are going to create our own example.
o Database is given by oracle, with help of database we are going to create
example, we can manipulate the database and after manipulating we can save
the information to the oracle table, we can store it. No need of any permission
or privileges
Product Instance:
o Product instance is given by the client, it is a client database
o In the real time we use this instance
o We compulsory need permission / privileges to work on client database
o We can get the permission from DBA
o According to requirement, DBA will grant the permissions to access the
database
o We cannot directly manipulate the client database
Test Instance:
o Test Instance is nothing but Testing
o We can use this instance after completing of project / work, then we can do
the testing
Oracle Application has different modules:
o Oracle Financial
o Oracle SCM
o Oracle CRM
o Oracle HMRS
o Oracle Apps Technical

1. Oracle Financial:
o In financial module, we can define the company structure.
o After defining the company structure, we are going to define different type of
transaction related to the accounting.
o Type of Oracle Financial modules:
o GL – General Ledger
o AP – Account Payable
o AR – Account Receivable
o Fixed Assets
o Cash Management
o Each and every module has system defined some standard functionality
o We can customize that standard functionality or you can setup the new
functionality
o Financial Transactions: all transactions are stored at one specific location
called ledger
o With help of ledger, we can prepare the profit and loss

2. Oracle SCM:
o SCM – Supply chain Management
o Type of Oracle SCM Modules:
o Purchasing
o PO – Purchase Order
o Inventory
o OM – Order Management
o BOM – Bill of Material
o Using all these modules, we are going to manufacture the Items
 3. Oracle CRM:
o CRM – Customer Relationship and Management
o All the services / types we are using to marketing or advertising the products
that all comes under the CRM Module

4. Oracle HMRS
o HRMS – Human Resource Management System
o HR Team is maintaining all the information of employees / Payroll / Benefits /
Time and labor process
o All these are including in the HRMS Module

5. Oracle Apps Technical:

o This module is common for all the Oracle application modules
o As a technical consultant, we are going to work on the RICE components
o As a functional consultant, they are going to work on front end and as a
technical consultant, we need to work on backend only (Developing /
Customize the applications)

3. Types of Data:

Data: Data is a collection of Information

o With the help of the data, we can work on the oracle applications
o We can have a different type of datatypes
o Number (number only)
o Char (character only)
o Varchar2 (character, number)
o Number (precision, scale)
o Date (dates)
o These all are standard data types provided by oracle
o Using these data types, we can store the data into the tables
Type of Roles
1. Roles: Oracle applications has a different type of Roles
o Functional Consultant Role
o Technical Consultant Role
o DBA

 DBA: Database Administration

o Major responsibility of DBA is installing the oracle application in system.
o Applying the Patches
o Maintaining the multiple instances (Development, Product, Test)
o Assigning the privileges / Responsibilities to the users

 Functional Consultant:
o Functional consultant interacts with the client and gathering the
requirement for development and customization
o After gathering the requirement and analyses the requirement
o After analyzing they can find difference in two system (As is and To be)
o Functional people find the difference called GAPS
o After clarifying the GAPS with client
o Functional people will create one document called FDD (functional Design
Document)
o Oracle / Technical name of document is MD 50 (Module Design 50)
 It is a functional design document prepared by functional people only
with the help of client’s requirement.
 It is mandatory documents for development / customization.
 Based on the MD 50, Technical people will develop / customize the
applications

 Technical Consultant:
o Technical consultant also plays key role
o Technical consultant goes through the MD 50 created by the functional
consultant to develop / customize the applications
o After developing / customizing the applications, they will create one
document TDD (Technical Design Document) MD 70 (Module Design 70)
o Technical name of this document is MD 70
o It includes Login / Tables, Programs, Procedures, forms, packages all these
are there in the MD 70
 o After MD 70 Prepared, Test that document, Test the component and if
testing is successfully completed then it will be delivered to the client.

 Techno-functional Consultant:
o Techno functional consultant is performing both Functional / Technical
consultant roles
o They can work on front end as well as backend
o They are able to create MD 50 as well as MD 70

Type of Projects
In Oracle Application there are different type of projects
o Projects are totally four types:
o Implementation
o Customization
o Conversion
o Support

1. Implementation Projects:
o If client want to use the oracle application to packages to capture the data that
time will start the setup first
o DBA will install the oracle application
o After that they are going to prepare the new setup everything from scratch
o This type of project called as Implementation project

2. Customization Projects:
o If client is using oracle application and want to add new more modules to cover
the business that time we have to go for customization.
o This type of project we called as customization project

3. Conversion / Migration:
o We are going to convert the data from one version to another version.
o Version: Oracle application version is R-12. Oracle R-12 version support 11g
database and 11g database support 10g forms and 10g reports.
o We cannot covert the version directly from one to another. We have to convert
the data step by step means if the version is 11.5.10 and we want to convert it in
 R-12. first, we need to covert it in 11.5.11 then 11.5.12 then R-12. (Step by step
we have to covert the data)
o Conversion / Migration is a single line process not repeated process. only one
time we are going to do the conversion of the data.

4. Support:
o Once Implementation, Customization and Conversion is over, then supporting
project will be started
o We will give support for the objects which is already developed, customized and
migrated
Oracle Application Architecture:
Oracle application architecture is the Three tier architecture
o Desktop Tier
o Application Tier
o Database Tier

1. Desktop Tier:
o Using Desktop Tier, we are going to login to application for development /
customization
o URL: Uniform resource locator
o Site: is a collection of module / Application
o Module: collection of responsibilities
o Responsibility: is a type of permission

2. Application tier
o In application tier will able to different modules as well servers also
o Servers
o Forms Server
o Report server
o Concurrent processing server
o Discoverer server
o Admin server

o Form Server:
o Form server is a collection of Form builder tool and form runtime
engine
o With help of this form builder tool, we can develop / customize the
form
o After developing / customizing the form, if we want to execute the
form, we need form runtime engine
o After executing it display run time form, we can perform the DML
operations

o Report Server:
o Report server is a collection of Report builder tool and Report runtime
engine
 o With help of this Report builder tool, we can develop / customize the
report
o After developing / customizing the report, if we want to execute the
report, we need Report runtime engine

o Concurrent processing Server:

o This server is a collection of different type of concurrent program
o Concurrent program is scheduled program which is prepared by
technical consultant
o Mail purpose of concurrent program is to call the reports
o When you want to register the new report, that time technical people
will create new concurrent program and assign the report to concurrent
program and then assign to request group and then responsibility and
responsibility assign to user.
o When user login to responsibility and call request means concurrent
program is executed and will get a report
o Using of concurrent programs, we are going to call the report in AOL
module.

o Discoverer Server:
o Discover server is another type of reporting tool
o Using this tool, we can develop XML reports
o XML Reports: It displays different output (pdf, html, excel, xml)
o With help of report builder tool, we can develop XML report

o Admin Server:
o Admin Server is taking care by the DBA
o In Admin server there are five folders
o Visdata
o Visdb
o Viscom
o Visora
o Visappl
o Visappl is used by the technical consultants (Vis means
Vision/Development Instances)
o Visappl is collection of all model of specific locations
o Each module is collection of different type of extensions
 o Database Tier
o Database Tier is a collection of database tables
o We need to connect to the backend to access the database tables
Database Architecture / Structure of the Database:
o At backend, tables are located into the Schemas
o Schema: It is a collection of database objects
o Database Objects
 Table
 View
 Synonyms
 Sequence
 Indexes
o Oracle application has provided one super scheme also known as Apps Schema
o Apps Schema: Is a collection of public synonyms of all the modules
o Always we need to connect to Apps Schema at the time of developing the
application
o Applsys Schema: Is a collection of three type of table
 FND table (Foundation): FND table used at the time of AOL module
 Work flow table
 Alert table
o Applsyspub: Is a collection of all synonyms of FND tables
AOL: Application Object Library
o After developing / customizing the objects (report/forms) are going to register in
this AOL module
o This AOL module contains 2 types of responsibilities
o System Administrator
o Application Developer

1. System Administrator:
o System administrator responsibility go the features user, responsibilities, reports
dev/customization, procedure, server monitoring
o This responsibility takes care by the DBA only
o Using this responsibility they can create users, procedures, server activities
monitoring

2. Application Developer:
o We are going to register the application (Reports / forms) in AOL module using
application developer responsibility.
o With help of this, we are going to create executable concurrent program,
functions, forms, menus, Flex fields.
o As Technical consultant, you should have this responsibility to register the
objects.

How to create a new User and how to assign the responsibilities:

o Select System Administrator responsibility
o Menus: Is a collection of sub-menus and functions. For each menu sub-menu is not
mandatory but the function is mandatory for all the Menu
o Function: to call the forms
o After opening Oracle application> Go to Security> User> Define (Here Security is menu,
User is Sub Menu and Define is function)
o It displays one standard form to create a new user
o Enter User name and Password and effective of user creation
o Then go to Responsibilities tab and select any responsibilities to assign it to user
o After saving this information, details are saved into the standard table FND_USER Table
o Once login from the created user, we can see the assigned responsibility of user and
their menus
How to create a New Responsibilities:
o We can create new responsibility using System Administrator responsibility (DBA can
create a new responsibility)
o Navigation: Select System Administrator Responsibility > Security > Responsibility >
Define
o It displays one standard form to create a new responsibility
o Enter responsibility name
o Application: Means this responsibility belong to which module / application. Select
module name from list of values
o Responsibility name and Responsibility Key is same, we can enter the same name in key
as well
o Responsibility is a collection of three (3) objects
 Data Group – Data group is collection of database files. Means we have to
select Standard data group provided by oracle
 Menu – It is a mandatory for each responsibility. Select standard menu.
o Standard defined Menu (Oracle has provided standard menu
for each module)
o User defined Menu (We can create new menu)
 Request Group – Request is not mandatory for responsibility but it will be
mandatorily need to call the Reports
o Save
Registration of Tables:
o In oracle application we are going to register 3 types of objects:
o Tables
o Reports
o Forms
o Procedure
o Main Purpose of register the table is to define the Flex field in AOL module.
o Register the table using standard package and procedure
o Always register the table in backend only
o ad_dd is the standard package we used to register the table
o original table are located into the module specific location and corresponding synonyms
are located in Apps schema
o Register the table in AOL Module:
o Connect to the module schema
o Create table in module specific location
o Connect to the apps schema and create synonyms for the table
o Synonyms name and table name should be same along with module name.table
table name (e.g. CREATE PUBLIC SYNONYM SUPPLIER FOR PO.SUPPLIER)
o After creating the table and synonyms, we can go for the register the table
 We can register the package with the help of standard package AD_DD
 In the package of AD_DD, there are four (4) type of procedure:
 Register_Table
 Register_Column
 Delete_Table
 Delete_Column
 We must have to pass mandatory parameter at the time of calling
Register_Table Procedure
 Application Short Name (In which module table is located)
 Table Name (created Table Name)
 Table Type = 3 types
o Transaction T= Perform all the DML Operations
o Seeded S = Not allowed to do the DML Operations
o Interium I= Temporary Table
 Syntax: EXECUTE AD_DD.REGISTER_TABLE (‘PO’, ‘SUPPLIER’, ‘T’); COMMIT;
 After registering the table at backend, we can see the table at front end
using below navigation
 Select Application Developer Responsibility
 Go to Application > Database > Table
  Query created table by entering the table name

o Register the columns in AOL Module:

 We have to use Register_Column Procedure
 To use this procedure, we have to use total eight (8) parameter
 Application Short Name
 Table Name
 Column Name
 Column Sequence
 Data Type
 Size
 Null
 Null
 Syntax: EXECUTE AD_DD.REGISTER_COLUMN (‘PO’, ‘SUPPLIER’, ‘SID’, 1,
‘DEV’, 4, ‘N’, ‘N’); COMMIT;
 After registering the columns at backend, we can see the columns at front
end using below navigation
 Select Application Developer Responsibility
 Go to Application > Database > Table

o Delete Column from AOL Module:

 We have to use Delete_Column procedure
 To use this procedure, we have to pass three (3) Parameter
 Application Short Name
 Table Name
 Column Name
 Syntax: EXECUTE AD_DD.DELETE_COLUMN (‘PO’,’SUPPLIER’,’SID’);
COMMIT;
 After Deleting the columns at backend, we can validate whether columns
has deleted or not from front end using below navigation
 Select Application Developer Responsibility
 Go to Application > Database > Table

o Delete Table from AOL Module:

 We have to use Delete_Table procedure
 To use this procedure, we have to pass three (2) Parameter
 Application Short Name
 Table Name
 Syntax: EXECUTE AD_DD.DELETE_TABLE (‘PO’,’SUPPLIER’); COMMIT;
 After executing above procedure, table can de deleted from the front end
only but table will still be there at backend
 If we want to delete the table from backend also, we have to use DROP
TABLE command
 Select Application Developer Responsibility
 Go to Application > Database > Table
 AD_DD package is a Standard / Admin package provided Oracle used to
register the table in AOL Module.
Report Registration Steps:
o Report is a one structured formatted output
o If we want to see the backend data at front end in specific format, we need to
develop a report
o We need minimum one base table and more than one table
o Report developing process has two types
o Developing a report from scratch
o Customization
o Based on the requirement we can develop a report
o After developing a report, we need to save the report in specific format with
extension RDF (Report Data File)
o After that move a report in module specific location and register the report in AOL
Module

o To Register the Report in AOL Module we require to complete five (5) steps:
 Executable
 Concurrent Program
 Request Group
 Responsibility
 Responsibility attached to user
o All above steps are mandatory to register the report
o All steps are created in AOL module with help of Application Developer
Responsibility
o After creating all the steps all steps are saved in FND tables (Foundation Tables)
Develop a New Report:
o Open Report Builder Tool (Oracle 10g)
o Each report contains three (3) sections:
 Data Model (Mandatory section):
 Query: whenever we want to develop, we need to submit at
least one query and more than one query
o When we submit a query, query will save into the data
model section as a Q_1, Q_2, Q_3.
 Group: collection of select statement, based on the submitted
queries the group will be created automatically.
 Paper Layout (Mandatory section):
 Whenever we want to develop a report, we need to select
paper layout
Register the Report in AOL navigation:
o Before going to register the report in AOL Module, we need to move that
RDF file into module specific location mandatorily
o After that select Application Developer Responsibility > Concurrent >
Executable
o Executable:
 Executable: Enter any related name
 Short Name: Enter any related name
 Application: Select Module name
 Execution Method: Oracle Report
 Execution File Name: Select RDF file name
 After saving all details saved into standard table FND_EXECUTABLE

o Concurrent Program:
 Application Developer Responsibility > Concurrent > Program
 Program Name: Give any related name
 Short Name: Give any related name
 Application: Select module name
 Executable: Select created Executable file
 After saving all details saved into standard table
FND_CONCURRENT_PROGRAMS

o Request Group:
 System Administrator Responsibility > Security > Responsibility >
Request
 Group: Give any related name
 Application: Select module name
 Request Type: Select program from the list of values
 Name: Select concurrent program name
 After saving all details saved into the standard table
FND_REQUEST_GROUPS

o Responsibility:
 System Administrator Responsibility > Security > Responsibility >
Define
 Responsibility name: any related name
 Application: Select Module name
 Responsibility Key: any related name
  Data Group: Select Standard from list of values
 Menu: Select standard menu related to the module
 Request Group: Select created request group

o Responsibility attached to user:

 System Administrator Responsibility > Security > User > Define
 Query the created user
 Go to Responsibility tab > select created responsibility from list of
values
o To see the output of report:
 Login from the User
 Select report responsibility > It shows all the menus of the attached
module to the responsibility
 To call a concurrent program
 Go to View > Request > submit new request
 Name: select concurrent program name
 Submit > Find > click on view output
 Now the report is generated as a required format
Request Group
o Request Group is used to call a concurrent program
o In one group, we can attach more than one concurrent program
o Concurrent program
 Concurrent program is a scheduled program created by technical
consultant at the time of registering the new report in AOL Module
 Using this concurrent program, we can call the reports in AOL Module
o Request Group is mandatory while working on the reports
o Request Groups has two types
 System defined Request Group
 User defined Request Group
o To Create Request Groups:
 System Administrator responsibility > Security > Responsibility > Request
 It displays request group creation form
 Group: Enter any related name
 Application: Select related Module name
 Code:
o Type: Select program from list of values
o Name: Select concurrent program name from the list of
values
o Application: Module Name
 After creating Request Group, assign it to the responsibility
Menu Creation:
o Menu: Menu is a collection of submenus, each submenu is a collection of functions
o Using of functions, we can call the forms
o While working on responsibilities, menus are mandatory
o To Create a Menu:
o Types of Menu
 System defined menu
 User defined menu
o While working on the Forms, at that time we need to create new Menu
o Application Developer Responsibility > Application > Menu
o It displays a menu creation form
 Name: enter any related name
 For each and every menu, submenu is not mandatory, but the Function
is mandatory
 We can attach more than one submenu or functions
  Prompt: Heading of Menu
 Submenu:
 Function: Select related function
 Save
o After saving, the information will save into the standard table FND_MENU
o Before creation of menu, we need to create a form then create one function,
assign Form to the function, attach function to the Menu, attach menu to
responsibility and assign responsibility to user
Report Parameters:
o Oracle has provided two (2) type of parameters:
o System Parameters:
 System parameters is a default parameter available for each and
every report
o User Parameters:
 User parameter are user defined parameter, we can create our
own parameters
 Used defined parameter called as bind parameter
 If we want to display any specific data in report at that time only,
we are going to create a user parameters (Optional)
o Whenever we want to define parameters for a report, paper parameter form
of report builder tool is mandatory
o Parameter we can directly in the Select statement under the WHERE clause
o We can enter any parameter name but in front of parameter name we must
have to give bind operator (:)
o SELECT * FROM EMP WHERE DEPTNO=:D_NO (:D_NO is a parameter name)
o After adding the parameter in select statement, report saved into the data
module section under the User parameter
o After that, we have to run the RUN PAPER LAYOUT and it displays standard
parameter form
o We have to enter the values in field and press enter
o We can see the report is generated for specific data
o This report we called parametric report
o After that we have to add parameter in AOL module to register the report
o To Register the Parameter in AOL Module
 We can register the parameter in AOL module with help of value
sets
o Create Value Sets:
 Select Application Developer Responsibility
 Application > Validation > Set
 Value set name: Enter any related name
 List of type:
o List of Values: By default, we can store 2000 values in
value set
o Long list of values: If we want to store more than
2000 values, we have use this
o Poplist: It will create another window to enter values
  Security Type: not required any security
 Format Validation:
o Format Type: We have to select the datatype of vales
o Max Size = enter size of values
 Value Validation (Mandatory need to select one validation
type)
o Total we have eight (8) types of validation:
 Independent = No dependency on any value
set (Parent value set)
 Dependent = Depends Independent value set
(Child Value set)
 None = Not Mandatory
 Pair = Not mandatory
 Special = Not mandatory
 Table = It displays table values, provide the
database table name and column name (IMP),
we Technical people always use this value set
 Translatable Independent = It depends on
specific language
 Translatable Dependent = It depends in
independent value set
 Edit Information:
 Table Application: Module Name
 Table Name: Database Table name
 Table Column: Select column from table which
we have selected for value set

o After registering the parameter, assign the parameter to the report

 We have to attach the parameter to the concurrent program
 We have a tab for parameter on concurrent program screen
 Concurrent program parameter:
 Parameter: Enter parameter name
 Validation
o Value set: enter created value set
 Token: Token is a bind parameter name; we have to enter
same parameter name into the token
Forms:
o Form is a front-end application
o Using form, we can manipulate the backend database
o We can perform all the DML operation on backend database
o According to client requirement, we can develop / customize the forms
o While developing a new form, compulsory we need a base table
o We must use Form Builder tool; this toll is standard toll provided by oracle
o All the standard form, we can get from AU (Application Utilities) folder and open
using form builder tool
o Forms we have two type of extensions
 FMB (Form Module Building – Source File): Always move to AU
 FMX (Executable File): Always move to Module Specific location
Register the forms into the AOL Module
o Here also we need to follow five (5) mandatory steps:
o Form
o Function
o Menu
o Responsibility
o Responsibility attached to User
o With help of Application developer Responsibility, we can create all above steps
o Functions is used to run the forms in the oracle application
Create new Function:
o Select Application Developer responsibility
o Application > Function
o It displays standard function creation form
o Function: Enter any related name
o Used function name: Same as function name
o Then click on form tab to attach the form
 Form: select created / Standard form from list of values and Save
 After saving details stored in base table FND_FORM_FUNCTION
Template:
o Template is standard form, looks like a form required starting point for all developing
new forms in Oracle application
o To develop a new form, compulsory we need a TEMPLATE.FMB file
o Template is located on the AU (Application Utilities) folder with default extension of
FMB (Form module building)
o In this AU top directory location, there is some standard FMB also available called
Template.FMB
o With help of Template.FMB file, we can develop a new form in any module of Oracle
application
o If we want to work on template, compulsory we need a Appstand.FMB
o Appstand.FMB is parent of Template and location at same location on AU top
directory
o By default, we open Template.FMB file to create a new report
o Once we open the Template.FMB in form builder tool, you will see that all the
objects are pre-defined only
o Triggers: If we want to write any PL / SQL code to the template that time
compulsory we need to use triggers
 Select any trigger to view the coding > PL/SQL Editor
o Attached Library: Library: It is a collection of standards (Packages,
procedure, function)
 APPCORE Library: It contain the package and procedure to
required to support the menu, toolbar and other required
standard Behaviour
 FNDSQF Library: It contain the package and procedure required to
support the Flex fields, Profiles, concurrent program
o Globe: It is used to define the regional setting, specifying the language
settings
o Custom: It allows extension of oracle application, forms without
modification of oracle application coding
 Basically, it used to customization purpose only
o APPDAYPK: It contains the packages that control the oracle application
calendar features
Development of New form using Template
o If we want to develop a new report using template, three (3) objects are mandatory
 Windows
 Canvas
 Data Block
o Windows:
 By default, template contains the standard windows Four (4) types:
 APPCORE_PROPERTIES
 CALENDAR
 PROGRESS_INDICATOR
 BLOCKNAME
 Out of above windows, three are standard windows and one is dummy
window. Before creating new windows, we must ensure to delete the
dummy windows from all the three objects (Delete BLOCKNAME
dummy Window from windows, canvas, data block objects)
 Select windows > click on create (+) button
o Data Block:
 Select Data Block > click on create (+) button
 It displays two options: (Always select data block wizard option)
 Use the data block wizard
 Build a new data block manually
 Using Data block wizard option, we are going to create a data block with
help of base table
 Using build a data block manually option, we are going to create a data
block without base table
 Create a data block

o Canvas:
 Layout means canvas creation
 Canvas is a background of data block
 For one form one canvas is mandatory, we can create more than one
data block in one canvas
 Type of Canvas (Important for Interview):
 Content
 Stacked
 Vertical Toolbar
 Horizontal Toolbar
 Tab
  Layout Style
 Form – It displays one record only at a time
 Tabular – It displays multiple record at a time (like Row & Column)
o After that Save this .FMB file into AU top directory and compile the file using
(CTRL+T)
o After that .FMX file will be generated, save this file into module specified location.
o After moving both the file, we can register the forms into AOL module, and we need
to follow five (5) mandatory steps:
o Form
o Function
o Menu
o Responsibility
o Responsibility attached to User
o With help of Application developer Responsibility, we can create all above steps
Flex Fields:
o There are two (2) type of flex fields
 KFF (Key Flex Fields)
 DFF (Descriptive Flex Fields)
o Main purpose of flex fields is to store some information
o KFF (Key flex field):
 Accounting Key flex filed is a standard KFF provided by Oracle
application to define company structure.
 Key flex filed is the mandatory flex field, if we want to store some
mandatory information about business that time, we are going to KFF
 Oracle application has provided standard flex field for each and every
module
 KFF is comprising of 4C’s – E.g. for General Ledger module:
 Chart of Accounts: collection of segments.
o Segments: We can store some list of values in segment. For
defining a company structure minimum, we need 3
segment and maximum upto 30 segments
 Company segment
 Department segment
 Account Segment
 Currency: Company functional currency
 Calendar:
 Convention: SLA (Sub ledger accounting method)

o DFF (Descriptive Flex Field):

 Descriptive flex fields are used to capture the Extra Information of
Business
 We can define the DFF with help of attributes
Creation of Descriptive Flex Fields:
o After creating and registering the tables we can create a descriptive flex field
o Select Application developer responsibility > Flexfield > Descriptive > Register
o It shows DFF creation form
o Application: Select module name
o Name: enter any related name for DFF
o Title: Same as Flexfield name
o Table Application: Select module Name
o Table Name: Select Table name
o Structure Column: Select Attribute_Category as a column
o Save
o Information of this DFF saved in standard table FND_DESCRIPTIVE_FLEX
o To assign extra information to the attributes:
 Select Flexfield > Descriptive > Segment
 Query created DFF > go to context field values
 Code: enter any related name
 Click on segment > enter what type of extra information we want to
capture
 We need to select attributes in the column field
 Create values set for each attribute using value set tab
 Save
 Click on the freeze flexfield definition
 Click on compile tab
 After compiling DFF information saved in FND_DESCRIPTIVE_FLEX
o To Enter the values into the Value sets:
 Go to Flexfield > Descriptive > Values
 Query your created DFF and segment
 Enter values in value tab
o All above steps we need to follow to setup the DFF in AOL module
o After defining DFF we need to assign these DFF to new template using from builder
tool
o We have to write one program to assign the DFF to template using Program unit tab
of Form builder tool:
o We have to create new package, Package is a collection of procedures and
functions
 Package Spec: means it is a declaration of package
 We can declare procedure in package
  PACKAGE test_pac IS
Procedure test_procedure (event in varchar2);
END;
 Compile the package
 Package Body:
 PACKAGE BODY test_pac IS
Procedure test_procedure (event in varchar2) IS
Begin
If event = ‘when-new-form-instance’ then
Fnd_descr_flex.define (‘table name’, ‘flexfield name’, ‘app
short name’, ‘DFF name’)
end if;
end test_proc;
END;
o We can call this package and procedure using new form instance trigger
o Click on new form instance trigger > Select PL / SQL editor to call the package
o Enter test_pac.test_proc (‘when-new-form-instance’); and compile
o Then click on new item instance trigger > Select PL/SQL editor
o Enter fnd_flex.event (‘when-new-item-instance’); and compile
o We attached the DFF to the template
o Save this template as NAME.FMB and complie and get NAME.FMX
o After that go to register the template in AOL Module.
Profile Options:
o Profile option set up by DBA with help of System Admin responsibility
o Profile option are setup changeable option that effects how the application looks and
behave
o Profile option can access three (3) levels
 User Level
 Program Level
 DBA
 Level (Important for Interview Question)
 Site: All Modules get enabled once we assign this site level
 Application: all the apps got enabled like forms, reports
 Responsibility: all the responsibilities got enabled
 User: User can access the responsibilities
 Select System Administrator Responsibility > Profile > System
Multiple Organization:
o If we have multiple company operations that time, we need this Multi organization
concept
o This is also called as a Business group setup
o Business Group: It is corporate headquarter, group businesses under one name
(Need to define in HRMS Module by finance functional consultant)
o Legal Entity: It is a government entity required for tax purpose
o Flex field structure: KFF & DFF
o Operating Units: Different companies (HRMS module)
o Inventory Organization: Location, where your company is location (HRMS Module)
o This setup is done by functional consultant only, but as technical consultant we
must know the tables behind all these steps:
o In this setup there is a two (2) Cycles at operating unit level
 P2P – Procure to pay cycle
 O2C – Order to Cash cycle
o Define Multi org Structure / Business Group:
o Login to HRMS Module > Human Resource, Vision Enterprises
o Go to work Structure > Organization > Description
o Click on new > Enter Business group organization name
o Select type as “Corporate Headquarter” > Select Effective date
o Go to Organization classification and select Business Group from list of values
and click on Enable
o Save the
o After that go to others > Select Business Group Infor and enter all the
additional information of business group
 Short Name: enter short name of Business group
 Employee number generation: Select “Automatic”
 Applicant number generation: Select “Automatic”
 Contingent worker number generation: Select “Automatic”
 Grade Flexfield structure: “Grade Flexfield”
 Group Flexfield structure: “People Group Flexfield”
 Job Flexfield structure: “Job Flexfield”
 Position Flexfield structure: “Position Flexfield”
 Costing Flexfield structure: “Cost allocation Flexfield”
 Competence Flexfield structure: “Competence Flexfield”
 Legislation code: Select company location (India)
 Currency: Select default currency (INR)
o After saving the details, it will be saved in HR_ORGANIZATION_INFORMATION
o Define Company Structure/ Flexfield in General ledger (GL) module:
o Login to General ledger Module > General Ledger, Vision Operations
o First, we need to define Chart of account:
 Setup > Financial > Flexfields > Key > Segments
 Query using module name General Ledger
o Using Accounting Flexfield, we can create company structure
 Add chart of account name in list of value like Test_Acc_Structure
 Click on segments
o We need to define three (3) segments mandatorily to define company
structure
 Company segment:
 Name: Company
 Column: segment1
 Value set: create value set of Segement1
 Department Segment:
 Name: Dept
 Column: Segment2
 Value Set: create Value set for Segment2
 Account Segment:
 Name: Account
 Column: Segment3
 Value Set: create Value set for Segment3
o Save this structure
o After saving go to Flexfield Qualifiers: Natural account and balancing qualifires
are mandatory
 Click on company segment > assign “Balancing segment” qualifier always
to the company segment > Click on enable
 Click on Account segment > assign “Natural account segment” qualifier
always to the account segment > Click on enable
o Click on “Allow Dynamic Insets” and “Freeze Flexfield Definition” tab
o Compile and save
o After creating company structure, we need to enter the values
o Go to Values > Query created all three (3) segments
o Enter values what we want to display and make qualifiers “yes”
o Save
o Define currency:
 Company always maintain one Functional currency (Based on the
location)
 Company can have multiple reporting currency
 Login to General ledger Module > General Ledger, Vision Operations
 Setup > Currencies > Define
 Enter Currency code - Enter any related name like Test_INR
 Name – Indian Rupees
 Issuing Territory – Location (India)
 Symbol - Rs.
 Precision – decimal point (2)
 Save

o Define Calendar:
 There are two (2) types of calendar in oracle application
 Fiscal calendar – Yearly calendar (Jan to Dec)
 Financial calendar – Financial year calendar (Apr to Mar)
 Login to General ledger Module > General Ledger, Vision
Operations
 Setup > Financial > calendar > Types
 Enter period Type: Enter related name
 Select 12 period from list of values
 Year type: Fiscal calendar
 Save
 After that go to define 12 period calendar
o Setup > Financial > calendar > Accounting
o Calendar: select calendar name
o Prefix: Jan to Dec
o Type: select calendar name
o Year: select current year
o From: 01-Jan-2018
o To: 31-Jan-2018
o Name: Jan-2018
o Enter all the months one by one in list of values
o Save
o Define Legal Entity:
o Go to Setup > Financial > Accounting setup manager > Accounting Setup
o Click on create accounting setup > Create Legal Entity
o Territory: Select your country name
o Legal entity name: enter any related name
o Organization name: select organization name
o Legal entity identifier: Enter any related name
o PAN: Enter PAN number of Organization in India (TIN: for other countries)
o Legal Address: Enter organization address
o Remaining fields are not mandatory
o Click on apply to save
o Legal entity is created, now will have to assign this to accounting setup
 Click on add another row
 Select legal entity
o Now click on next button to setup Primary Ledger
 Ledger is a collection of charts of accounts, Currency and calendar
 Name: Enter any related name
 Chart of Account: Select chart of account
 Accounting calendar: select calendar
 Currency: select defined functional currency
 Click on next and finish to save the details
 Click on Define accounting options
 Go to Ledger option > click on Update
 4 pages will display > Click next on 1st page
 On 2nd Page, Select retained existing account mandatorily
 Click on create button, It will create once code combination
 Click on Finish
 Check the status and click on complete

o Define Operating Units:

o Login to HRMS Module > Human Resource, Vision Enterprises
o Go to Work Structure > Organization > Description
o Click on New > It display operating unit creation form
o Name: Enter company name
o Type: Not mandatory
o From date: Enter effective date
o Click on save
o Under organization classification > Select “Operating Unit” > Enable and save
 o Click on others > Select operating unit information
o Primary Ledger: select created primary ledger
o Default Legal context: select Legal entity name
o Short code: enter any related name
o Save the details
o After creating operating unit, we must have to run the standard program
 Select System Administrator responsibility > Directly call concurrent
program
 View > Request > Submit New request > “Replicate Seed Date” >
Operating Unit > Enter operating unit name and submit

o Define Inventory organization:

o Inventory organization is nothing, but the location of your operating unit is
located
o Login to HRMS Module > Human Resource, Vision Enterprises
o Work Structure > Organization > Description
o Click on new > Enter inventory name > and enter effective date
o Under organization classification > Select “Inventory Orgaanization” > Enable
and save
o Click on others to save additional information of inventory organization
 Accounting Information: Enter Primary Ledger name, legal entity name
and operating unit
 Inventory Information:
 Inventory parameters:
o Organization code: Enter related code
o Item master organization: select Inventory org
o Calendar: select Inventory calendar
 Costing Information:
o Costing Method: Select Standard method
o Transfer to GL: Always select “Yes”
o Valuation account: Select material inventory account
 Other accounts:
o Receiving account
o Profit and loss account
o Other account

o Define Sub-Inventory organization:

o Login to HRMS Module > Inventory, Vision operations
o Setup > Organization > Sub inventories
o Select Inventory and click on new tab
o Just enter sub Inventory name and save
Multi organization Tables:
o Multi org tables contain multiple organization data
o Multi org table ends with “All keyword”
o At the time of working on organization unit cycles (P2P & O2C), Multi org table gets
enabled
o In these tables common column is ORG_ID
o There are two (2) type of cycles at operating unit level

o Flow of P2P Cycle: Procure to Pay cycle

 In this cycle the main source is Supplier
 Modules: Purchasing, payables, inventory
 P2P cycle requires when company wants to purchase any item
 First, we need to create a supplier and Item then only we can work on
this cycle
 First step is to create a Purchase Requisition
 Requisition: It is a requirement document prepared by purchasing
department in the organization
 Requisition details are saved in three (3) tables
o PO_REQUISITION_HEADERS_ALL
o PO_REQUISITION_LINES_ALL
o PO_REQUISITION_DISTRIBUTION_ALL
 After creating requisition document, we can call quotation from
supplier using RFQ (Request for Quotation) document
 Against the RFQ, supplier will raise the quotation and send it back
to organization
 After getting multiple quotation, organization will select best
quotation (quotation analysis) and raise the PO (Purchase order)
 Purchase Order has four (4) types
o Standard Purchase order
o Blanket Purchase Agreement
o Contract Purchase Agreement
o Planned Purchase Agreement
 After raising the PO, three (3) tables are get enabled
o PO_HEADERS_ALL
o PO_LINES_ALL
o PO_DISTRIBUTION_ALL
 PO send to supplier and supplier will supply the material against
the PO
  We can receive the material with help of creating receipt against
the PO
 Through the receipt, we can validate and confirm the quantities
we have received
 After creating receipt, three (3) tables are get enabled
o RCV_SHIPMENT_HEADERS
o RCV_SHIPMENT_LINES
o RCV_TRANSACTION
 Then we have to make payment to the supplier
 For this we have raise an invoice in AP Module
 We have to raise standard invoice to make payment as per
payment terms
 After raising the invoice against the PO, three (3) tables are get
enabled
o AP_INVOICE_ALL
o AP_INVOICE_DISTRIBUTION_ALL
o AP_CHECKS_ALL
o AP_INVOICE_PAYMENTS_ALL
o AL_PAYMENTS_SCHEDULES_ALL
 Once the payment completed, system will generate one
accounting journal (sub-leger)
 Journal created in sub-ledger and filed transfer to GL
 Once transfer to GL done, three (3) tables get affected
o GL_PERIOD
o GL_PERIOD_STATUS
o GL_CODE_COMBINATION
 Check the availability of Items into the Inventory

o Flow of O2C Cycle: Order to Cash cycle

 In this cycle the main source is customer
 Modules: Order Management, Account receivable, Inventory
 Inventory Module is a common module in both the cycle
 In this cycle, supplier going to raise the Sales order in Order
management
 After raising the SO, two (2) tables are get enabled
 OE_ORDER_HEADERS_ALL
 OE_ORDER_LINES_ALL
 After that supplier can Book the order
  Then supplier will have to do the material reservation under Inventory
module
 Once material reserved, three (3) tables are get enabled
 MTL_MATERIAL_TRANSACTION
 MTL_MATERIAL_QUANTITIES
 MTL_SERIAL_NUMBERS
 After confirming the material, they are going to ship the material
 Ship the material to the customer location using standard shipping
method DHL
 Once the shipping is completed, shipping tables are get enabled
 WSH_DELIVERY_DETAILS
 WSH_DELIVERY_ASSIGNMENT_STATUS
 After shipping is completed, commercial invoice is generated in AR
(Account Receivable) module
 Along with Invoice Items are sent to the customer
 Once customer receives the material, they will make the payment and
generate the journals
 All journals are transferred to the GL module
 Closed

o Important base tables will get affected while working on both the cycles
Interface:
o Interface is program used to transfer the data from flat files to Oracle apps tables
o We will validate the data from flat file first, only after that we can transfer the data
from flat files to oracle apps table. This is nothing but a Interface
o Oracle has provided standard interface for each and every module
o There are two (2) types of Interface
 Inbond Interface: transferring the data from flat file to Oracle apps
Tables
 Outbond Interface: transferring the data from Oracle tables to flat files

o Inbond Interface (companies used only Inbond Interface mostly)

 We can work on Inbond interface with help of SQL*Loader
 SQL*Loader is one of the data loaders used to load the data
o Outbond Interface
 We can work on the Outbond interface with help of UTL Files
 UTL Files is also one loader used to transfer the data

o Inbond Interface Flow:

o For any interface, we must require three (3) types of tables
 Database Table:
 Database table is a standard table provided by oracle application
only
 Database table always contain a structured data
 For Reports and other things, we always use database tables

 Interface Table:
 Interface table is also a standard table available for each and
every module
 Interface table is empty table, no data is populated
 Interface table are used only at the time of working on interface

 Staging table (1st Stage):

 Staging table is created by users when they want to work on the
any one interface
 With help of Mandatory columns, user will create a staging table
 We can identify the mandatory columns using primary Key
columns and Not null columns
  Once we receive that data in flat file from client, then will create
one control file
 Control File: It is one SQL*Loader program
 In this control file, we can write statements to transfer the data
from flat file to staging table
 Control file is created by users with some executing statements
 After creating control file, we have to save the file using any
related file name with extension .CTL file
 Go to run the SQL*Loader
 SQL*Loader: It is used to upload the data from flat file to Oracle
tables
 When the SQL*Loader run successfully completed, then only data
will be transferred from flat file to staging table
 In staging table, we can validate the data whether data meets our
requirement or not
 To validate the data, we have to write PL/SQL procedure with
validation conditions
 Once these procedure / conditions are run successfully, data will
be transferred from staging table to Interface Table
 After that, we have to use one standard import program
 Once Import program run successfully, data will be transferred
from Interface table to Database table.
o SQL*Loader
o SQL*Loader is one data loader used to upload the data from flat files to oracle
application table
o While working with SQL*Loader, total five (5) different files are created
 Flat File: It contains data in specific format received from client only
(.DAT, .TXT, .CSV)
 Control File: It contains loader program created by user with some
executable statement to insert data in staging table (.CTL)
 Bat File: It contains the records rejected by the SQL*Loader
 Discard File: It contains the records rejects by control file
 Log File: It contains the complete log information
Working of Interface using one example of GL Module
o GL Interface
o While working on Interface, we compulsory needs three (3) tables
 Database Table: GL_DAILY_RATES
 Interface Table: GL_DAILY_RATES_INTERFACE
 Staging Table: Created by User only
o Create Staging Table:
 Login to SQL*Plus or SQL Developer
 Query database & Interface Table DESC GL_DAILY_RATES; and DESC
GL_DAILY_RATES_INTERFACE;
 You will find some mandatory filed in this table defined by NOT NULL
 With help of mandatory fields, we are going to create staging table
 Create Table GL_Stage
(
From_Currency varchar2 (10),
To_Currency varchar2 (10),
From_Conversion_Date Date,
To_Conversion_Date Date,
Conversion_Rate Number (2),
);
 After creating Staging table, we are going to create Control file
 Ed Test_con
 Enter program to insert the data
Load Data
Infile *
Insert into GL_Stage (Staging table name)
Fields terminated by ‘,’ optionally enclosed ‘ “ ’
Trailing nullcos
(From_Currency, To_Currecny, From_Conversion_Date,
To_Conversion_date, Conversion_Rate)
Begindata
“USD”, “INR”, ’01-Jan-2021’, ’31-Dec-2021’, 65
“USD”, “INR”, ’01-Jan-2021’, ’31-Dec-2021’, 65
“USD”, “INR”, ’01-Jan-2021’, ’31-Dec-2021’, 65

 Save this File using .CTL extension at specified location

 Now we have to run the SQL*Loader
 Open CMD > Go to .CTL file location
 Enter SQLLDR Apps/Apps/Instance name
 Enter Control file name GL_Test.CTL
 It displays that Commit point reached – Logical record count is 5
 Now the data is inserted into the Staging table
 Now We have to move the data from staging table to Interface
table. For this we have to write PL/SQL Procedure
 Ed Test_proc
 Write Procedure
Create or Replace Procedure Test_Proc is
Cursor c1 is select * from GL_Stage;
Begin
For x in c1 loop
Insert into GL.GL_DAILY_RATES_INTERFACE (From_Currency,
To_Currecny, From_Conversion_Date, To_Conversion_date,
Conversion_Rate) Values (x.From_Currency, x.To_Currency, x.
From_Conversion_Date, x. To_Conversion_Date, x.
Conversion_Rate);
End Loop
End Test_Proce;
/
 Create the Procedure
 Execute the Procedure Execute Test_Proc;
 Then Query the Interface Table to see the data
 Last step is to move the data from Interface table to Database
table
 Select Application Developer Responsibility
 Select Module > View > Submit New Request
 Enter Program name > Program – Daily Rates Import and
Calculation > Submit
 Using this program our data from Interface table to database
table.
Conversions:
o Conversion is a one-time process
o We are going to convert the data from old version to new version
o When oracle invented a new version at that time only, we need a conversion
o For conversion also we need three (3) types of tables
 Database Table
 Interface Table
 Staging Table
o Similar process like Interface, we have to follow for conversion also
o Prepare Staging Table using mandatory columns (Not Null Columns)
o Create Control file (.CTL) with some insert statements to insert the data
o Run the Control file (.CTL) file using SQL*Loader
o After that we have to write SQL*Loader Script for converion
o Once the loader run successfully, data is transferred from Flat file to Staging
Table
o After that, we have to write procedure to transfer the data from staging table
to Interface table
o Execute the procedure to transfer the data in Interface table
o After that, we have to run standard program to transfer the data from
Interface table to Database table
AIM Documentation:
o AIM Document means Application Implementation Methodology
o This methodology has been developed by Oracle Corporation
o It is an end to end Implementation process
o Different types of processed are included in AIM
 Business Requirement Definition (It Includes Requirements, Plan,
Resources, Timeline, Budget of projects)
 BR-010, BR-020
 Business Requirement Mapping
 Application and Technical Architecture (TA010, TA020, TA030)
 High Level Design (Flow Chart)
 Build PL/SQL Program
 Data conversion
 Business System Testing
 Performance Testing
 Support
 Production
o MD 50 – Module Design documents prepared by functional consultant only
o MD 70 – Module design documents prepared by Technical consultant
o MD 120 – Technical design document prepared by the technical consultant to
migrate the forms & Reports
o MD 70 – Technical design document prepared by technical consultant for migration
o CR (Change Request) documents – Document prepared by Technical consultant to
provide support
o For Migration we need to prepare two (2) documents
o Installation process: Development/Testing/Production (Done by DBA only)
o Execution process: Function/Procedure/Packages with screenshots
Business Documents
o MD 50
 MD 50 is a Module design document prepared by the functional
consultant
 This document specifies functional specification required for techies to
understand the functional requirement of Forms & Reports
customization and Design

o MD 70:
 MD 70 is technical design document prepared by the Technical consultant
 This is technical specification prepared by programmer based on MD 50
 This document contains PL/SQL code, Validations, SQL Statements for the
Reports and Forms

o MD 120:
 MD 120 is also technical design documents
 Installation steps will be prepared by the programmer for Data migration
 MD 120 Mainly consist of below steps
 Pre-Installation Steps
  Installation Steps
 Verification Checklist

XML Reports:
o If we want to get the output of Reports in different formats like PDF, Excel, Word,
HTML that time we are going to develop XML Reports
o XML is Template based application
o Using XML data, we are going to develop a template
o How to develop XML Report:
 First, we need to create Report (.RDF) file using report builder tool
 Select Web layout option only
 Enter query to select the table and columns
 Save the reports as .RDF format
 Before registering the RDF file in AOL module, we have to generate the
XML file using this RDF file
 Click on file > Generate to file > select file type as XML
 By default, it will take same file name with extension .XML file
 Save this file at same location
 Now we have to register the file in AOL module with help of five (5) steps
 Executable
 Concurrent Program
  Request Group
 Responsibility
 Responsibility attached to the user
 Before registrarion, move the .RDF file into Module specific location and
register the .RDF in AOL module
 Select Application Developer Responsibility > Concurrent > Executable
 Create Executable file
 Then Go to Concurrent > Program
 Create Concurrent Program > Select Format as XML and Style as
Landscape
 After that, switch responsibility to System Administrator > assign the
concurrent program to request group
 Security > Responsibility > Request
 Create request group > assign concurrent program to request group
 Now, create responsibility and assign it to user
 Security > Responsibility > Define
 Assign responsibility to user
 Security > User > Define > Query user
 Login from the user and run the concurrent program
 In the output file you will get a XML data > Copy the data and save it as a
.XML File
 Before registering the XML file, we need to move the XML file in MS word
document
 With help of MS word document, we have to create a template file
 Using template builder option in word file > We can load the XML file in
MS word document
 Insert the table structure using insert tab of template builder and save
the file with extension of .RTF (Rich Text file)
 After getting .RTF file, we have to register the XML file in AOL Module
 To register the XML file, we have to follow the two (2) steps:
 Data Definition
 Template
 Select “XML Publisher Administrator” Responsibility
 Home > Data Definition
 Data definition form will open > Create Data Definition
o Name: Any related name
o Code: Select concurrent program short code
o Application: Select Module name
 o Start date: effective date
o Click on apply
o After that, click on add file tab of Data Template and assign
the template file (select .XML File)
o Click on apply

 Define the Template > Create Template

o Name: enter any name
o Code: Select concurrent program short code
o Application: Module name
o Data Definition: assign Data definition template
o Type: RTF
o Start date: Effective date
o Go to Template file tab
 File: Select .RTF file
 Language: Select English as default language
o Click on apply
o Finally, login to the user and call concurrent program
o Go to View > Select concurrent program
o Click on options > you will see the format as RTF
o You can see the output in multiple formats (PDF, Excel,
Word, HTML)