RTL TECHNOLOGIES Oracle R12 Apps Technical

Mobile: 9885489062
Oracle Apps Technical Courses
OAF,ADF,MAF,Training Courses
Functional
Oracle Financial Courses
SCM
HRMS
1|Page
Mobile: 9885489062
www.chandraonlines.com
www.rtlonlinetraining.com
www.rtltechs.com
2|Page
Mobile: 9885489062
R U B.Tech/M.Tech/MCA Fresher?
Contact us for placement
Address
Plot 301,Bhanu Towers
Opp ESI Hosp,Erragadda
Hyderabad-38.
Contact-9885489062,8885589062
3|Page
Mobile: 9885489062
Newly Added Concepts
 SQL/PLSQL RealTime Concepts
 Performance Tuning
 Unix concepts & basics known on shellscript
 BI Publisher
 Finance & SCM Technical(AP,AR,GL,Inventory,OM,PO)
 ClassRoom Execution
 Everyweek Mock Interview
 UNIX Commands.
 Interview Tips
 Resume Preparation Tips.
D2K CONCEPTS
Report Builder Form Builder
1. Data model objects 11.Data blocks

 Summary column a. Database Data block
 Formula Column b. Control Data block
 SQL query  Canvases
2. Layout model objects  LOVs
 Frame  Record Group
 Repeating Frame  Parameters
 Text Item  Object Groups
 Field  Property Classes
3. Placeholder Column, Data Link  Visual Attributes
4. Parameters  Alerts & Popup menus
 Lexical Parameter  Editors
 Bind Parameter 2. Triggers
 Diff between Bind and Lexical  Validation Trigger
5. Triggers  When Triggers
 Report Triggers  Query Time Triggers
1|Page
Mobile: 9885489062
I. Before Parameter Form  On Triggers
II. After Parameter Form  Pre Triggers
III. Before report  Post Triggers
IV. Between pages  Navigational Triggers
V. After Report  Master Detail triggers
Lexical Parameter inTrigger  Mouse Event Triggers
 Format Triggers  Check Box, Radio Groups Radio Button.
 Validation Triggers  Stacked canvas, TAB canvas
 Action Triggers  OPEN_FORM,CALL_FORM,NEW_FORM
6. Program Units  Show Alerts from Triggers
7. Libraries  Program Units
8. SRW Package procedures  Source File and Executable File
9. Confine Mode and Flex mode
10. Header,Main,Trailer Sections
11. Select Parent Frame
Oracle Applications R12 Concepts
1. ERP concepts 4. Types Executables

1. ERP concept Introduction
 Report Development and Registration - 1
2. Software Development Life Cycle ( SDLC )
3. Differences between ERP from Scratch & Existing ERP  Report Development and Registration – 2
4. Difference between SAP & Oracle Apps 5. Report With Parameters
5. Types of Roles, Responsibilities and Modules
 Report with Lexical Parameters
6. Module Integration Documents ( Documentation )
 Default Types
2. Oracle Apps Architecture 6. Value sets and its Types
 File Structure 7. Procedures and SQL * PLUS Registration
 Database structure
3. Application Object Library (AOL Concepts)  Procedure with parameter
 Application Navigation  SQL * PLUS Registration.
 Details about System Administrator  SQL * PLUS with parameters
& Application Developer responsibilities
8. SQL * LOADER
 User Creation
 WHO Columns  SQL * LOADER in Oracle Apps.
 Table and Column Identification  SQL * LOADER with parameters.
2|Page
Mobile: 9885489062
Functional Concepts
9. Procure to Pay Cycle
1 10. Real Time Report Development
 Supplier Creation
Profiles
 Buyer Creation
 Profile Levels
 Item Creation
 Important Profiles
PO Business Flow
 Profiles in Reports
 Requisition
 Profiles in Procedures
 RFS’s
 :$PROFILE$
 Quotations
Multi Org
 Purchase Orders
 Multiorg flow
 Receipts
 MOAC
 Auto create Pos
 Diff Between 11i and R12
AP Business Flow
 Security Profile.
 AP Module Invoices
 Payments
Flex Fields
 Transfer to GL
 Descriptive Flex fields Customization
Order to Cash Cycle
 Context Field
 Customer Creation
 Key Flex Field
 Item creation
 KFF Reports and Customization
 Item Transactions
Table and Forms Registration
 Item Quantities
 Deploy custom Forms.
 Sales Rep Creation
 Check Boxes
 Sales Order Creation
 Radio Buttons
 Booking Sales Order
 Calendar attatchment
 Pick Release
 Master Detail Forms
 Pick Confirm
 LOVs attatchment
 Ship Confirm
 WHO Columns
 Order Shipping
 DFF attatchment
AR Business Flow
 Display Message Boxes
 Import Auto Invoice.
Forms Personalization
 Create Invoice
 Creating Receipts.
 Cash clearing.
 Transfer to GL.
3|Page
Mobile: 9885489062
Interfaces
Interface purpose and process
 Interface table
 Base Table
 Stage Table
Outbound Interfaces
7. UTL_Package
Inbound Interface Process

8. Create Remittance
GL Interface
GL_Interface_Journal Import
GL_JE_HEADERS
GL_JE_LINES
GL_JE_BATCHES_POSTING
GL_BALANCES
PO Interface
PO_HEADERS_INTERFACE
PO_LINES_INTERFACE
PO_DISTRIBUTIONS_INTERFACE_Import
standard Purchase Orders
PO_HEADERS_ALL
PO_LINES_ALL
PO_LINE_LOCATIONS_ALL
PO_DISTRIBUTIONS_ALL
PO_DISTRIBUTIONS_ALL
Diff between interface and conversions
Imp Interview Questions in AOL XML Publisher
XML Publisher Reports
4|Page
Oracle Apps Technical Material Ph: 9885489062
Report Builder 10G
 Report Builder is one of the Oracle GUI Tool Graphical user Interface
 By using this we can develop simple and Complex reports
 There are two ways we can develop the report
1)Wizard based 2)Manual
Models :
1)Data Model 2) Layout model
Data Model: Data Model will be used to select the data from Database.
Ex: SELECT Statement and Formulas, Summary functions and so on.......
Layout Model: Layout model will used to displays the data model fields in the desired format.
Layout Model Objects:
Text: Will be used to display the standard text information

Ex: like titles, prompts, headings, Address.
Frame: Will be used to display the layout objects only one time
Ex: like totals, titles, Headings and so on.
Repeating Frame: Will be used to display the objects multiple times
Ex: Like database columns, Sub Totals, Page Totals.
Field : Will be used to display the Data base columns, variables.
Levels:
1) Group level: Executed for every record in the group
2) Report Level: Executed only once for entire report.
Summary Column: If we want to apply summary functions then we will go for summary columns like Average, count,
min, max and so on.
Formula Columns: When we want implement some logic and return the value then we will use formula columns.
It is a PL/SQL Function. Where we can write PL/SQL code. We can return only one value.
Plot No-301,Bhanu Towers,Opp ESI Hosp,Erragadda,Hyderabad-38 Page 1

Place Holder Columns: Datatype which stores some value and we can use this across the report.
It will work like a global variable in the reports. If we want to return more than one value from the Formula
columns then it will be used.
Ex for place holder column:
Empno Ename Sal Hire_Date Comm TotalSal(SAl+Comm) Tax
Tax : if (totalsal>5000 then 7% tax
(Totalsal>3000 and <=5000 then 4%tax
(Totalsal<=3000 then 2% tax)
Empno Ename Sal Comm Tax Netsalary
Comm := 15% sal
tax : 7 % (sal+comm)
netsal : sal+comm-tax
Data link:
A data link (or parent-child relationship) relates the results of multiple queries. A data link can establish these
relationships between one query's column and another query's column between one query's group and another
query's group (this is useful when you want the child query to know about its parent's data)
A data link causes the child query to be executed once for each instance of its parent group. The child query is
executed with the values of the primary key used by the parent.


Parameters:
1) System Parameters
2) User Defined Parameters
1) Bind 2) Lexical
System Parameters :
DESFORMAT : Html, pdf.....
DESNAME : Name of the Printer, E-mail, Fax, File
DESTYPE : File, Screen, Print, Fax, E-mail
MODE : Bitmap, Character
Bind Lexical
1)To pass the Values into the WHERE Clause 1) To Replace the string in the query
2)We will use the symbol ":" 2)We will use the symbol "&"
3)Can be used only in the WHERE Clause 3) In Any Clause
4)Any Data type 4)Only Char Data type
Triggers: Trigger is a PL/SQL block which will be fired automatically whenever an event occurs.
Report Triggers - 5
Format Trigger
Validation Trigger
Action Trigger
Report Triggers: 5 Types which will fired automatically when we run the report.
Before Parameter Form

After Parameter Form
Before report
Between pages
After Report trigger
Before Parameter Form: Will execute before the parameter form is going to open. To assign any default values for
the parameter.
After Parameter Form: After the Parameters are entered in the form and submit it will be executed.
To change the Parameter values dynamically

And To populate the Lexical parameter values.
Before Report: It will be executed before report is executing and select data from database.
Between Pages: When cursor moves from one page to another page it will be executed. It will be executed (n-1)
times.
After Report: After completion of the report. Once the output is reach the destination (Printer, file, fax, e-mail) then
it will be executed.
Format Trigger: To Hide or display the layout objects dynamically it will be used.
Layout objects means frame, repeating frame, field and etc.
Action Triggers: If we want to develop drill down reports then we will use Action Triggers.
Place the Button in the layout when user press the button we can execute some PL/SQL code.
Confine Mode:
Lock mode if it is on then we cannot take the child object out of the Parent Object. If it is off then we can take out of
the parent.
Flex Mode:
If Flex mode is on. If we Incr/Decr the child object automatically parent object also incr/decr.
If it is off then Only child object will be decr/Incr.
Program Unit :
Is a PL/SQL object (Procedures, Functions, Packages) which will be stored in the Report we can use only in the
Current Report.
Program units PL/SQL Objects
1) Will be stored in the file 1) Stored in the Database.
2) Can be used only in the current report 2) we can use any report
3) Improve the Performance 3) It takes more time
4)Client side objects 4)Server side Objects
Libraries: Group of Program units and Libraries. We can attach the Attach the Library to another report and use the
Program units.

We cannot attach the Program units to another reports directly that's why we will use PL/SQL Library to attach
.pll - Source Code - Program Link Library
.plx - Executable Code - Program Link Executable

Form Builder 10G
Form Builder is one of the Oracle GUI Tool Will be used to build the Forms as per the client requirement .By using
the Forms user can INSERT/UPDATE/DELETE the records into the table. and we can select the data from the
database table and search the data in user friendly environment.
Versions: 4.5 / 6I / 9I/ 10G
When we save the Form it will be saved in the .fmb (Form Module Binary) format. It is source file again we can open
and customize it.
When we Compile the Form it will generate the .fmx Executable format. we can execute this we cannot open the
file.
Data block:
1) Database Data block: Select Data from table /Procedure/View
2) Control Data block: Without DB table we will define the data block
Database Data block: Yes
Canvas :Canvas is the areas where we will display the data block Items like Buttons,Checkboxes,Text Items ,Text and
So on.
Canvas Types: 5
 Content (Default)
 Stacked
 Horizontal Toolbar
 Vertical Toolbar
 TAB Pages
Property Type = Content


Window:
1) Model: we cannot resize, minimize , User must respond to the window to move into another option.
2) Model Less window: User Friendly we can easily navigate other forms and minimize and maximize.
Default: Model less Window
If we want to make it model window Go to Window properties: Model = Yes
Record Groups: A record group is an internal Form Builder data structure that has a column/row framework similar
to a database table
Static: Enter the values manually
Query Based: Based on the select statement get the values
Non-Query Based: Change the values dynamically.
LOV: List of Value which will be used to provide the list of values in the field’s user can select the value from the list.
Without Record group we cannot create LOV. Once LOV is created it will be attached to the field by selecting the
property called 'List of Values'
Note: CREATE_GROUP by using this procedure we can create the Record group dynamically.
Property Classes Visual Attributes
1) Group of Properties 1) Group of Look and Feel properties Font, Color, Size.....
2) We cannot change dynamically 2) Visual attributes can be changed SET_VA_PROPERTY

Procedure
3) We can define the Triggers 3) we cannot define triggers for Visuval attributes
Note: If same property given in both Property Class and then Visual Attribute will take the High priority.
Popup Menu: Will be created to populate group of menu option when we select the Right click option. Once popup
is created then it will be assigned to field or Canvas.
Alerts: Alerts are nothing but Messages which will be used to display message boxes based on the user input we can
change the Form execution.

Triggers Levels:
1. Form Level: it will be executed once for the entire Form.

2. Block Level: It will be executed when we enter into the data block.
3. Record level: It will be executed for every record.
4. Item Level : It will be executed for the Particular Item.
Types of Triggers:
1. When Triggers
2. Transactional Triggers
3. Validation Triggers
4. Query Time Triggers
5. On Triggers
6. Pre Triggers
7. Post Triggers
8. Navigational Triggers
9. Master Detail Triggers
10. Mouse Event Triggers
11. Key Triggers.
WHEN Triggers:
 WHEN-BUTTON-PRESSED
 WHEN-WINDOW-CLOSED
 WHEN-VALIDATE-ITEM
 WHEN-VALIDATE-RECORD
 WHEN-NEW-FORM-INSTANCE
 WHEN-NEW-RECORD-INSTANCE
 WHEN-NEW-ITEM-INSTANCE
 WHEN-NEW-BLOCK-INSTANCE
 WHEN-MOUSE-CLICK
 WHEN-MOUSE-DOUBLECLICK
WHEN-VALIDATE-RECORD: when user change the value in the fields then it will be fired.
WHEN-NEW-RECORD-INSTANCE: When user create new record then it will be fired.

Transactional Triggers: When user make some Transaction like (INSERT, UPDATE, DELETE, SELECT, COMMIT,
ROLLBACK, QUERY, CLOSE) that time these triggers will be fired.
PRE-INSERT ON-INSERT POST-INSERT

PRE-UPDATE ON-UPDATE POST-UPDATE
PRE-DELETE ON-DELETE POST-DELETE
PRE-QUERY POST-QUERY.............

Validation Triggers:
WHEN-VALIDATE-ITEM - At any level
WHEN-VALIDATE-RECORD - At Block Level
When we change the value in the item (or) record it will be fired.
Query Time Triggers:

Pre-Query: Trigger will be fired before query the data only once
Post-Query: Will be fired after query the data multiple time for every record once it will be fired to
Populate Non-Database Items.


Navigational Triggers:
When we navigate
 From one form to another form
 From one data block to another data block
 From one record to another record these triggers
 From one field to another field then these triggers will be fired
PRE-BLOCK WHEN-NEW-BLOCK-INSTANCE POST-BLOCK

PRE-FORM WHEN-NEW-FORM-INSTANCE POST-FORM
PRE-RECORD WHEN-NEW-RECORD-INSTANCE POST-RECORD
PRE-TEXT-ITEM WHEN-NEW-ITEM-INSTANCE POST-TEXT-ITEM
Master Detail Triggers:

When we define the master detail relationship between the Data blocks then Master - Detail triggers will be created
automatically.
Types Master Detail Relationships:

Non-Isolated : (Default) The master record cannot be deleted if associated detail records exist in
The database
Isolated : The master record can be deleted, but the associated detail records are not deleted
From the database.
Cascade : The master record can be deleted, and any associated detail records are
Automatically deleted from the database at commit time.

Master - Detail Triggers List:
1. ON-CHECK-DELETE-MASTER (Non-Isolated)
2. ON-CLEAR-DETAILS
3. ON-POPULATE-DETAILS
4. Pre-delete (Cascade)
Deptno: 10
Dname: Accounting
Empno Ename Sal Deptno

4411 Scott 12500 10
4422 Ramu 12452 10
1545 Swetha 2365 10
Deferred: yes: We must place the cursor in the detail block

Automatic Query: yes: Data will be retrieved automatically in the detail block.



Oracle Applications Introduction
Types Roles and Responsibilities:

We have 3 type of roles and responsibilities in Oracle Applications projects.
1) Oracle Applications DBA

2) Oracle Applications Functional Consultant
3) Oracle Applications Technical Consultant
DBA Functional Consultant Technical Consultant
1)Install the application 1)Interacting with the client 1) Receive the F.D from the
Linux server 2) Explain about product to the client.
2)Security groups define client. 2) Go through the document and
3) Database backup / cloning 3)GAP analysis understand the requirement.
support. 4) Gather Requirement and prepare 3)Prepare the T.D
4) Define multiple instances. F.D 4)Get the approval
Development other objects. 5) Develop the object.
Testing. 5)Define Functional setups 6) Test The object
Production 7)Move into the Production
5)Applying Patches 6)Prepare Training manuals 8) Technical Requirement:
To Solve bugs 7)Assign the Work to the team RICE
To provide new features 8) Functional Consultant Requires R-Reports
www.metalink.oracle.com I-Interfaces(SQL & PL/SQL)
Communication Skills C-Conversions
Documentation Skills E-Extensions-Forms
Presentation skills
Types of Modules:
1) What is Module?
Module is nothing but a business process which will be used maintain the business transactions
Technically it is group of Forms,
Reports, and
Programs which are required for specific Business Process

Oracle Applications E-Business Suite

ERP(Enterprise Resource Planning) CRM (Customer Relationship Management)
Oracle Oracle Oracle Oracle Oracle

Financials SCM Manufacturing HRMS CRM
Payables(AP) Purchasing(PO) Inventory (INV) Core-HR Service

Receivables(AR) Inventory(INV) Work In process(WIP) Payroll Contracts
General Ledger(GL) Order Bills Of Material SSHR(Self
Fixed Assets(FA) Management(OM) (BOM) Service) Service
Cash Management(CE) Production OTI Requests
Projects(PA) Capacity OAB
MRP planning Customer
relation
managemen
t
Types of Documents:
AIM - Application Implementation Methodology
MD050 Functional design document F.D.D -F.C
MD070 Technical Design document T.D.D -T.C
MD0120 Migration document T.C

(Reports and Forms)
MD020 Testing Document F.C

TE020
CV040 Conversion functional document F.C
CV060 Conversion Technical document T.C

(Interface and conversion)
CR documents Change Request document Client

F.C
T.C


MDModule Design BRD- Business requirement
CVConversion RD - Requirement design
Types of Projects:
1) Implementation
2) Customization
3) Migration/Conversion/Upgrade
4) Support/Maintenance
Modules Integration
INV
WIP
PO
BOM
AP
QA
CE
GL
OM
AR



Database Architecture :
PO OM
 Tables  Tables
 Views  Views
 Index  Index
 Sequences  Sequences
INV HRMS
 Tables  Tables
 Views Apps Schema  Views
 Index  Index
 Sequences  Sequences
 Tables
 Tables
 Views
 Views
 Index
 Index
 Sequences
 Sequences
AP AR

File Architecture :
Appl_TOP
PO CUSTOM TOP
12.0.0 12.0.0
Admin Bin Forms Reports Log sql Bin Log Reports Forms
US US US US


Application Object Library ( AOL )
Application : It is a combination of development and customization
Object :These are developed and customized objects
Library: It is a registry
AOL is a key where we are going to complete Technical and Functional aspects.
It involves two aspects
1) System Administrator
2) Application Developer
System Administrator : Application Developer :
 Creation of users  Forms

 Security Groups  Reports
 Responsibility  Menus
 Profiles  Form function
 Programs  Messages
 Application
 Tables
These are object registry by the application developer
Creation of a user
1) Start Browser for login : http://apps.ora.com:8000

User Name : operations
Password : welcome
2) System Administrator ( single click ) ( left side pane )

3) Go to right side pane

Security : User
Define ( click )
4) Users form
User Name : rtltechs (Any User Name of your wish, which is not existing)
Password : xxxxxx ( at least 5 chars )
( re-enter password ) ( it shows on the status bar of the form )
Description : any one ( purpose of user ) ( is an optional )
Responsibility Application Description Security Group From To

Application Developer Application object Sysdate Auto
library
System Administrator Application object

library
Place the cursor in the responsibility cell and click ( right side …)
Find : appl% enter key and select application developer , then OK
Place the cursor in the responsibility next row and click ( right side …)
Find : system administrator % enter key and select application developer, then OK
Save the form ( save button )
Status bar shows that : Transaction complete : 3 records applied and saved.
Close the form
1) Checking for User

1st way
Go to Oracle Application Home for checking weather the user created or not
Security : user
Define
Users form : press f11  to query
When pressed F11, users forms enters into the query mode
User Name : rtltechs% and Ctrl + F11 , it shows user details
2nd way
Using query
Select * from FND_USER ;
Using Toad Utility :
User name : apps
Password : apps
Database : vis
Click on Connect
Go to editor then execute following query ( Ctrl + Enter  to execute query )


Select * from FND_USER where trunc(creation_date)=trunk(sysdate)
Creation of one more user
Users form:
New button ( + ) ( 1st one on the tool bar with green color )
Repeat the above procedure and save it.
For checking users form : F11  to get into query mode,
User Name : rtltechs% : Ctrl + F11  it queries for the users starting with user
Down arrow key display the users one by one .
Find button : ( 2nd one in the tool bar )
To display users
Click and find : user % ( enter key )
Close Form : to close the form
Clear form : to clear the current form
Delete : this will be in the disabled position, to disable the user set effective dates
From :
To :
Set the To date same as the form date.

Finding Table Name
Go to users form F11 query the user ( user name : ctrl + F11 )
After getting user details go to Help menu  Record History
It shows as below
Created By: OPERATIONS
Creation Date: 04-MAR-2011 17:24:42
Table Name: FND_USER
Updated By: OPERATIONS
Update Date: 04-MAR-2011 17:24:42
The above details will be obtained from the Table called FND_USER
Column names
Help  diagnostics  examine 
Block : USER
Filed : USER_NAME, to see the more fields click at right side, it shows all the columns in thetable
(or)
using toad utility we can query the fields
Select * from FND_USER
Value : rtltechs
To find the current login user
Help  about application
Oracle Applications
Copyright (c) 2004 Oracle Corporation,
Redwood Shores, California.
All Rights Reserved.
Site: UNKNOWN
Application: System Administration
Responsibility: System Administrator

Security Group: Standard
User Name: OPERATIONS
Types of executables:
These are programs Oracle Application supports 12 types of languages
Older version supports only 11 languages
Apps 11i version supports 12 languages.
1) Oracle Reports  .rdf

2) Sql * Plus  .sql
3) PL/SQL Procedures  .proc
4) Sql * Loader  .ctl
5) Unix shell script  .sh
6) C – Language  .C
7) Pro - C  .prc
8) Java Programs  .java
9) Java Serve Pages (OAF)  .jsp
10) PERL scripting  .perl
11) Java Server Faces(ADF)  .JSF
Once the above programs have been transferred to oracle application, then these are called as concurrent programs.

Concurrent program: Instance of executable file along with input parameters and incompatible programs.
Development of sample report and Move to oracle apps and execution
Report Registration Steps:

1) Develop the report (.rdf) as per client requirement by using Reports 6i Builder
2) Move the report from the local machine in to the server
a. CUS_TOP\11.5.0\reports\US .rdf (or)
b. PO_TOP\11.5.0\reports\US .rdf
3) Select System Administrator
a. Create Executable
b. Executable name
c. Application Name
d. Execution Method
e. Report (.rdf) file name
4) Create Concurrent Program and attach
a. Executable
b. Parameters
c. Incompatibilities
5) Create Request group and attach Concurrent Programe
6) Create Responsibility
a. Request Group – Collection of Concurrent Programs
b. Data Group – Collection of User IDs
c. Menu – Collection of forms
7) Create user attach Responsibility to the user
8) Switch responsibility and go to SRS (Standard Request Submission)
Window submit the request
Executable => Concurrent Program => Request Group => User=> SRS


Default Types:
Current Date: Will be used to pass the Sysdate as default value
Current Time: Will be used to pass the Systime as default value
Constant: Will be used to pass the constant number or date or string as default value
Segment: Will be used to get the Previous parameter value as default to the next parameter then we will use this.
SQL Statement: We can pass the SELECT statement result as default value
Profile: This will be used to pass the user profile value as default like userid , username, respid, respname and so on.
Reports with Parameters:
1. If we have parameters in the report we are supposed to define those parameters while defining the
Concurrent Program
2. Select Parameters button enter the following Fields
Seq no: Any +ve number no duplicates are allowed
Parameter Name: Any User defined parameter name
Value set: 10/NUMBER or 100 Charachters or FND_STANDARD_DATETIME
Token: Enter the Bind Variable name
Token: It is one of the field in parameter form to map the Concurrent Program parameter with Report bind Variable.
Value Set: Is nothing but list of values with validations which will be used to restrict the user without entering the
invalid data.
Required Check Box: When we want to make the parameter as mandatory or Optional we will use this check box. If
we enable it will be mandatory disable it will be optional.
Display Check Box: When we want to hide the parameter we will use this check box user cannot find the parameter
at SRS window. we can pass default values internally by using Default types.
Enabled Check Box: We can delete the parameter. Instead of deletion we can also disable the parameter. Whenever
we required again we can enable.
Range: This option will be used to set the values as Low and as well as High.

Value Set: Value set is nothing but list of values with validations which will be used to restrict the user without
entering the invalid data in the Parameters. We will use value sets in two locations.
1) Concurrent Program parameters
2) Flex Fields
Notes: 1) Once we create the Value set we cannot delete if we would like to delete we have to release the value set
from the all the concurrent program. Parameters then only we can delete.
2) Value set name is case sensitive
3) Once we create Value set we can use for multiple Program parameters.
Navigation:
System administrator => Application=>Validation=>set=>
Enter value set name, format type, max size.
Value Set Types:
NONE: We are not providing any LOV, we can apply some format conditions as per that conditions user should enter
the data.
Select validation type = "None" to create None type of Value sets.
Independent: When we would like to provide list of values to the user then we will go for selection of Independent
value set. Where we will provide LOV. User must select the Value from the list otherwise values are not accepted.
Open the Value set form create value set by selecting the validation type = Independent
Go to Values screen enter the value set name, Select Find Button enter the values whatever we would like to display
as LOV. Attach the value set to the Parameter.
Note: 1) Once we enter the values we cannot delete instead of that we can disable by selecting the Enabled check
box or Effective Dates.
Dependent value Set: This is another LOV which will be used to displays the list of values which are depending on
the previous parameter value. Before going to create Dependent first we have to create Independent then we have
to create dependent value set. First parameter will be Independent. Second parameter will be Dependent.


Ex : Country 1).IND
2).US
3). UK
City a). Bangalore b). Chennai c). Delhi d). Mumbai e). Pune
a). Chicago b). California c). Anderson
a). London b). Hungrant
1. We have to create Independent value set and enter the values.

2. Create Dependent value set attach independent and then enter values.
Navigation: Open the Value set form create Value set by selecting the validation type =Independent
 Open the Values screen enter the Values.

 Open the value set form enter Dependent value set by select validation type=Dependent
 Select the Button called Edit Information button enter the Independent value set
 Open the values form enter the Dependent value set=>Find
 Enter the values based on the Independent values.
Table Value set: Table value set will be used to displays the list of values from the oracle apps base tables. We have
to give the table name and column name which will automatically displays the values.
Note: If values are not stored in the database table then we have to go for Independent value set.
If values are there in the table then we will create table value set.
1. Open the value set form Select validation type as table select the button called Edit Information enter table
name and column name in the value field.
2. Use where / Order by clause to implement Where/Order By clause.
3. Use Additional Columns field to displays extra columns for reference purpose.
4. Use the ID column to pass the internally other columns data.
5. If multiple tables are required then enter the table names in the table name field with alias name and enter
the Join Condition in the where clause field.
6. If we know the table name we can find the Table application name from application Developer responsibility
Application Developer => Application => Database => table
Query the records based on the table Name.
Note: If we are displaying additional Columns we are supposed to give the Alias Name
Translated Independent and Translated Dependent : Both value sets will work like Independent and Dependent
value sets will be used to displays the translation values which will be enabled if there is multi language
implementation.
Special and Pair: Both Value sets will be used to displays the Flex Field data as LOV to the User.

Procedure Registration
1) Develop the procedure and compile at SQL prompt
2) Connect application select system administrator Responsibility create.
3) Executable by selecting the Execution Method as 'PL/SQL Stored Procedure'
4) Create Concurrent Program and attach Executable to the Program and add the Parameters and incompatible
programs.
5) Create Request group attach concurrent Program
6) Attach Request group to the responsibility
7) Responsibility will be added to the user.
8) User will submit the request from SRS Window.
Procedure Syntax:
Create Or Replace Procedure <ProcedureName> (Errbuf OUT varchar2,

Retcode OUT varchar2,
P1 IN NUMBER,
P2 IN VARCHAR2,
P3 IN DATE) AS
Local variable,Cursor,Collections Declare;
Begin
If statement
For Loop
Procedure Calling
DBMS_OUTPUT.Put_Line - This will not be used instead of this Fnd_File API will be used
FND_FILE.PUT_LINE(Fnd_File.Log ,'Message'||Variable Name);
FND_FILE.PUT_LINE(Fnd_File.Output,'Message'||Variable Name);
Exception
When Other then
-Exception Statements;
End <Procedure Name>;
PL/SQL Procedure with Parameter:
If we have any user defined Parameters then we have to register these parameters at the time of creating the
Concurrent Program by selecting the Parameter button
enter the Seqno
Parameter Name2
Value Set
Note : Token Field will be disabled.
Here First Parameter value will be passed to the first variable, Second Parameter will be passed to the second
variable and so on. When we are registering the report as C.P then only we required TOKEN field. Because report
builder bind variables may or may not be in the sequence that's why we have to map with Token field. Where as in
Procedure variables position is fixed then TOKEN field will be disabled.

SQL * Loader:
It is one of the Oracle Tool will be used to transfer the data from Flat files into Oracle Base tables. When we are
developing the Interfaces or Conversion program in Oracle Applications then we will be using the SQL Loader
Programs. While working with SQL * Loader we will come across 5 Files.
1. Flat File OR Data File:
Data file contains the data in the specific format which we will receive from the client. This file will be generated by
the legacy system (Other Systems) program.
It may be either .txt, .dat or in .csv (Comma Separated View) Excel sheet. Most of the times we will receive in the
(.csv) format
2. Control File:
Control file is nothing but a SQL*Loader Program will be used to load the data from file into table. we will develop
the control File
Execute the Control File. While developing the Control file we will specify following things.
1. Data File path

2. Database Table Name
3. Column Mapping.
Control file Extension is (.ctl)
3. Bad File:
When we execute the Control file if any records are rejected by SQL *Loader then we will find those rejected record
in the Bad file. SQl loader rejects the records if there are any datatype mismatch.
Error be like: Internal Errors, Data file Format problem and Bad File Extension is (.bad).
4. Discard File:
When we execute the Control file if any records are rejected by Control File then we will find those rejected record in
the Discard file. Control file Rejects the record when the record is not satisfying the record which are not satisfied
the condition specified in the Control file. Discard File Extension is (.dis)
5. Log File:
It contains the Log information like Program start time, End Time No.of successfully records upload Rejected Records
into the Bad file Rejected records into the Discard file. Any errors are there in the Control file those error message
details we will find. Log file Extension is (.log).

Control File Syntax:
LOAD DATA
INFILE 'Data File Path'
Insert into table <Table Name>
FIELDS TERMINATED by ',' OPTIONALLY ENCLOSED BY'"'
TRAILING NULLCOLS
(Column1 ,
column2 ,
Column3 and etc.)
Ex:
Load data
infile 'C:\22\LOAD\EMP.txt'
INSERT INTO TABLE EMP_DETAILS22

Fields terminated by ','
(empno,
ename,
sal,
job,
comm,
deptno ,
hiredate)
Note: Save the file extension as ".ctl" and move the control file to CUSTOM TOP, Bin Folder in the server. And now
create a Executable in Oracle Apps by specifying the Execution Method as
SQL * Loader, after this creating concurrent program and everything is same as report registration.
Execution of Control File in command prompt:

Go to Command Prompt where the SQl loader is installed.
Connect to following path and execute the control file
D:\Oracle\Proddb\8.1.7\Bin\SQLLDR Scott/Tiger@PROD
Control = C:\22\LOAD\emp_details.ctl


Purchase Order Cycle

Item: Item is physical Goods or Service which required in a company or organization.
Item Tables: MTL_SYSTEM_ITEMS_B (When we create Item in oracle apps will be stored in this table)
Segment1 (Item Name), Inventory_Item_id (Item Number)
MTL_ONHAND_QUANTITIES (To check the quantity in inventory)
Inventory_item_id (Foreign key)
We can assign the Item to the Multiple organizations. Then we will find multiple records in the table with diff
Organization_ID.
Supplier: The Person or a company who ever supply the goods to our organization is called supplier.
Supplier Table: AP_SUPPLIERS (Supplier Data will be stored this table)
Vendor_id (Primary Key), Vendor_name
Supplier Sites: Is nothing but supplier branches
Table: AP_SUPPLIER_SITES_ALL
Vendor_site_id (Primary Key), Vendor_id (Foreign Key)
Supplier Contacts: Contact person details for the specific supplier site.
Supplier Contact Table: AP_SUPPLIER_CONTACTS_ALL
Vendor_contact_id (Primary Key), Vendor_site_id (Foreign Key)
Supplier AP_SUPPLIERS
AP_SUPPLIERS_SITES_ALL
Supplier Sites Supplier Sites
Supplier Contacts Supplier Contacts Supplier Contacts

AP_SUPPLIER_CONTACTS_ALL
Buyer: The Person who authorized to buy goods or items behalf of the organization is buyer, buyer is also employee
of an organization.
First we have to create the employee. To get the employee details table name PER_ALL_PEOPLE_F.
Person_id (Primary key)
Then we will define the Username and Password for every employee in System Administrator.
We will find user details in the FND_USER table.
Then make the employee as buyer in purchasing module. Then we will find the data in PO_AGENTS table

Purchasing Cycle Brief:
Whenever employee requires materials he will create the requisition. After requisition is approval RFQ (Request for
Quotation) will be created. This RFQ will be sent to multiple suppliers. After that we will receiving the quotation from
supplier then company will do the quote analysis, one quotation will be selected as purchase order will send this PO
to the supplier, as per PO terms & conditions supplier will supply the material while receiving the material we will
create the document called the receipt. After the creation of receipt AP & Inventory Interfaces will be affected,
which are going to update both AP & Inventory Modules. The given below is the representation of the PO Flow.
Internal
REQUISITION
Purchase
RFQ (Request for quote)
BID
BID
Catalog
Catalog QUOTATIONS
Standard
Standard
Standard
PO
Planned
Blanket
Receipts
Contract
Inventory AP
Requisition: We have two types of requisitions

 Internal and
 Purchase
Internal Requisition: Internal Requisition will be created whenever we are receiving the material from another
organization in the company.
Purchase Requisition: Purchase Requisition will be created whenever company is purchasing material from
suppliers.


Requisition information will be entered in 3 Levels
1. Headers
2. Lines and
3. Distributions
Creating Requisition Navigation:
1. Go to Purchasing, Vision Operations (USA) Responsibility.
2. Go to Requisitions Requisitions Navigation.
3. Enter the header and line details fields item, quantity that Represent how much you required to
Purchase and what you want to purchase.
4. This is one-to-many Relationships, after completion of the document, select Approve Button, then
requisition will be sent for the approval.
Distributions: Whenever we click on the Distributions button on the Requisitions window then we will
Get this distributions window
Approval Screen: When we click on the Approve button on the Requisition Screen we will get this
Window. Here we will check the Submit for Approval check box then click on Ok button.
Requisition Summary: To check whether the requisition is approved or not we will go with the Navigation:
Requisitions Requisitions Summary
Enter the requisition number and press find button.
Requisition Headers Summary: Whenever we press the find button will get summary screen. Here we
Can check the approval status of the requisition.
Note: Once the Requisition is approved then only we will go for RFQ.
The Tables that effect Requisitions are:
1. Header level Information -> PO_REQUISITION_HEADERS_ALL

Select * from PO_REQUISITION_HEADERS_ALL where segment1=’5646’
--requisition_header_id=56635
Here segment1 is the Requisition Number. And REQUISITION_HEADER_ID is Primary column
2. Line Level Information-> PO_REQUISITION_LINES_ALL

Select * from PO_REQUISITION_LINES_ALL where requisition_header_id=56635;
--requisition_line_id = 60546
3. Distribution Level Information -> PO_REQ_DISTRIBUTIONS_ALL
RFQ (Request for Quotation): Once the requisition has approved RFQ will be created and this RFQ will
Be sent to suppliers if suppliers are agreed with the terms & conditions, which we have specified
In RFQ document, they will send the quotations to the company, we have 3 types of RFQ’s
Bid: BID RFQ will be created for the large & expensive items where you will not find any discount means
No price breaks.
Catalog: Catalog RFQ will be created for the items, which we are purchasing frequently where we can
Get the price breaks and terms & conditions.

Standard: This will be created for the items, which we will purchase only once not very often.
If we are sending Bid RFQ, to the suppliers then we will receive the bid quotation from the suppliers for the catalog
RFQ’s we will be receiving quotations and for standard RFQ, standard quotation will be sent by the suppliers.
RFQ information will be entered at 3 levels
Headers: In Header level we will specify RFQ number, type & ship to, bill to location
Lines: In Line Level we will specify the items.
Shipment: At Shipment level we will specify discount details.
The table that effect this RFQ are
1. HEADER LEVEL: PO_HEADERS_ALL
Select * from PO_HEADERS_ALL
where segment1=’312
’and type_lookup_code=’RFQ’
and ORG_ID = 204
-- Po_header_id=32560
2. LINE LEVEL: PO_LINES_ALL
Select * from PO_LINES_ALL where po_header_id=32560
--po_line_id=37768 37769
3. SHIPMENT or PRICE BREAKS: PO_LINE_LOCATIONS_ALL
Select * from PO_LINE_LOCATIONS_ALL where po_line_id=37768
PURCHASE ORDER:
After receiving the quotations from supplier then we will create the purchase order. We will approve that purchase
order will send po to the supplier. As per the po document terms and conditions supplier will supply the material.
We have 4 types of Purchase Order
1. Standard PO
2. Planned PO
3. Blanket Purchase Agreement
4. Contract Purchase Agreement
Standard PO: For all the Purchase Orders we will use Standard PO as the PO type where we will specify terms &
conditions items, price, quantity, delivery Schedule and so on.
Planned PO: if delivery schedule is not confirmed then we will create planned PO
Blanket Agreement: Supplier and Buyer will have the agreements where we will find terms & conditions
And items price may or may not. Whenever buyer is required material he will release the order as per that supplier
will supply material.
Contract PO: we will have only terms and conditions buyer can purchase any item from the supplier.
Purchase order Information will be entered at 4 Levels:
1. Header level
2. Line Level
3. Shipments
4. Distributions
Purchase Order Navigation:

1. Go to Purchasing, Vision Operations (USA) Responsibility.
2. Go to Purchase Orders Purchase Orders.


Purchase Order Table:
1. HEADER LEVEL: PO_HEADERS_ALL
Select * from PO_HEADERS_ALL where segment1=4465 and type_lookup_code=’Standard’
---po_header_id=32588
2. LINE LEVEL: PO_LINES_ALL
Select * from PO_LINES_ALL where po_header_id=32588
--- po_line_id=37797
3. SHIPMENT LEVEL: PO_LINE_LOCATIONS_ALL
Select * from po_line_locations_all where po_line_id=37797
---line_location_id=72173
4. DISTRIBUTIONS LELVEL: PO_DISTRIBUTIONS_ALL
Select * from PO_DISTRIBUTIONS_ALL where line_location_id=72174
Po Auto Create:
It is one of the Purchasing feature to create the RFQ and PO documents automatically by using requisition lines.
1. Create Requisition and approve
2. Open the Auto Create form
3. Select Clear button enter the Requisition NO
4. Select find button which will shows all the requisition lines
5. select the lines whatever we want to include into the RFQ
6. Select Action = Create to create new RFQ
AddTo to add lines to existing to RFQ
7. Select Document Type = RFQ
8. Select Automatic button which will create RFQ document automatically.
Receipts:
After receiving the goods we will create the Receipt with the reference of corresponding Purchase Order number, so
after creating the receipts automatically On Hand Quantities in the inventory will be increased.
Navigation: Purchasing, Vision Operations USA => Receiving => Receipts
Tables: RCV_SHIPMENT_HEADERS
RCV_SHIPMENT_LINES
RCV_TRANSACTIONS
Purchase Order Report
=====================
POno : Buyer:
Potype : Supplier:
ShipTo : Supplier Site:
BillTo : Contact :
Cdate : Status : POTotal :
payment Terms: Fright Charges: FOB: Carrier:
Lineno Item Desc Qty price Shipno ShiptoLoc ShipToOrg Qty Distno Distqty Requestor
----- ---- ---- --- ----- ------ -------- --------- --- ----- ------ ------
Order Management and AR

Normally standard sales order can be split into sub steps. This jointly carried out by some modules like INV, OM,
Pricing, Shipping and AR. Let’s take each sub steps with data flow conditions.
Navigation: Switch to responsibility Order Management Super user vision operations
Orders, Returns => Sales Order
Order Entry: This is first stage when Order in enter in system. When the order is entered it basically create a record
in order headers and Order Lines table.
 Oe_order_headers_all ( flow_status_code as entered)

 Oe_oreder_lines_all (flow_status_code as entered)( Order number is generated.
Order Booking: This is next stage, when Order which is entered in step1 is booked and flow status changed from
entered to Booked. At this stage these table get affected.
 Oe_order_headers_all (flow_status_code as booked, booked_flag updated).

 Oe_order_lines_all (flow_status_code as awaiting shipping, booked_flag updated).
 wsh_new_deliverries (status_code OP open).
 Wsh_delivery_details (released_status ‘R’ ready to release).
Shipping:
Navigation: Shipping => Release Sales Orders => Release Sales Orders
1. Pick Release :
Ideally pick release is the process which is defined in which the items on the sales order are
taken out from inventory. Normally pick release SRS program runs in background. Once the
program get completed these are the table get affected.
 Oe_order_lines_all (flow_status_code ‘PICKED’)

 wsh_delivery_details ( released_status ‘S’ ‘submitted for release’)
 mtl_txn_request_headers
 mtl_txn_request_lines ( move order tables , Here request is generated to move item
from saleable to staging sub inventory).
 Mtl_material_transactions_temp ( link to above tables through
move_order_header_id/line_id.
2. Pick Confirm: Items are transferred from Inventory to staging Sub inventory
 Mtl_material_transactions
 Mtl_transaction_accounts
 Wsh_delivery_details (released_status ‘Y’ ‘Released’).
 Wsh_delivery_assignments.
Navigation: Shipping => Transactions


3. Ship Confirm :
Here ship confirm Interface program runs in background. Data removed from
wsh_new_deliverries.
 Oe_order_line_all ( flow_status_code ‘Shipped’)

 wsh_delivery_details ( released_status ‘C’ ‘Shipped’)
 mtl_transaction_interface
 mtl_material_transactions ( linked through Transaction source header id)
 mtl_transaction-accounts
 Data deleted from mtl_demand, mtl_reservations
 Item deducted from mtl_onhand_quatnities.
4. Enter invoice :
This is also called Receivable interface, that mean Information moved to accounting area for
invoicing details. To generate Automated Invoice to the previous sales order in AR run the
“Workflow Background Process“ in SRS window, and now switch to “Receivables”
Responsibility and go to
Interfaces=> Auto Invoice=> Auto Invoice Master Program mention proper operating unit
and GL dates and run the program. After successfully completion of the program go to
Transactions => Transactions ,now query with order number at reference field and gl
date(Query with to fields is mandatory)
 Invoicing workflow activity transfers shipped item information to Oracle

Receivables.
 Ra_interface_lines_all (interface table into which the data is transferred from order
management) T.
 Then Auto Invoice Program Imports data from this
 Table which get affected into this stage are receivables base table.
o Ra_customer_trx_all (cust_trx_id is primary key to link it to trx_lines tables
and trx_number is invoice number).
o Ra_customer_trx_lines_all (line_number_1 and line_attribute_6 are linked
to header_id ( or order_number) and line_id of the orders).
5. Complete Line :
This is stage order line level table get updated with Flow status and Open flag.
 Oe_order_lines_all (flow_status_code ‘Shipped’, open_flag ’N’).

6. Close Order :
This is last step of Order Processing. In this stage only oe_order_lines_all table get updated.
These are the table get affected in this step.
 Oe_order_lines_all (flow_status_code ‘Closed’, open_flag ‘N’).

These are the typically data flow of a order to cash model for a standard order.

Profiles,Multi Org,Flex Fields
Profile: Profile is one of the changeable option it will change the way of application execution.
When User Log in to the application and select the the resp or Appl system will automatically captures all the profile
value as per the profile values application will run.
Ex: If client have three Organizations 1)Hyd
2)Ban
3)Chn
If "hyd" users connect to the Application system will retrieve the data from database which is related to the
Hyderabad branch. If user is working for 'CHN' branch then Chennai branch setups or data will be retrieved.
For every user we will assign the Profile value Ex: Operation
Position - Profile Name
Profile Values:
1. Manager
2. Supervisor
3. Clerk
4. Operator
5. Trainees
When we want assign any profile value we have four levels we have to select any one of the level.
Profile Level Profile Profile Value

User OPERATIONS Print 10(This is for Operations)
Responsibility 22Responsi Print 5(This is for 22resp users)
Application GL Applica Print 4(This is for GL App Users)
Site --- Print 2(This is for ALL Users)
Site: this is lowest level to assign the Profile values site values are applicable for all the users. When we install
Application by default site level values will be assigned.
Application: These values are applicable for the users who are having the access for the application. If user is eligible
for both application and site level values then application level value will override the site level value.
Responsibility: We will select the responsibility name assign the value which is applicable only for the users who are
having the access for specified responsibility. Responsibility level value will override both application and site level
values.
User: This is highest level in the profile option. We will select the user name and assign the profile value which is
applicable only for this user. User level value will override all other profile level values.
Diff between Application and Responsibility:

Application is nothing Collection of Forms, Reports and Program which are related for specific business functionality.
Responsibility is nothing but Collection of Forms, Reports and Program which are related for specific Position in the
Organization.
Ex: We have to create One Responsibility for the Clerk. Which is accessible by all the Clerks. It Contains the Forms
and Reports which are required for the Clerk.
Whereas Application includes all the Forms, Reports and Programs. If we assign the application to the user he will
access all the forms and Reports. Instead of that we will create the responsibility and we will assign to the User.


Note: Most of the profile values will be assigned at Responsibility Level.

Common Profiles:
Gl: Ledger Name: Which is Financial Profile option will be used to assign Ledgers
HR: Business Group: Which will used to assign the Business Group
MO: Operating Unit: To assign the Operating Unit (Branch) to the users.
MFG_ORGANIZATION_ID: Will be used to assign the Manufacturing Organization ID.
We can find all the Profile details in Application Developer Responsibility.

We can assign the Profile values in System Administrator Responsibility.
Navigation: Application Developer=>Profile =>Press CTRL+F11 we can find all the profiles.
System administrator=>profile=>System=> Select Profile name, Level =>Find button then assign the Profile value.
Example Procedure:
Create Or Replace Procedure ven_update (Errbuf OUT varchar2,
Retcode OUT varchar2,
v_id IN number,
v_name IN varchar2) as
l_name varchar2 (100);
begin
l_name:=Fnd_Profile.value('USERNAME');
If l_name = 'OPERATIONS' then
UPDATE PO_VENDORS
SET VENDOR_NAME = v_name
WHERE VENDOR_ID =v_id;
commit;
Fnd_File.Put_line (Fnd_File.Output,'vendor name has updated succesfully');
Else
Fnd_File.Put_line (Fnd_File.Output,'Access Denied for updation');
End If;
End;
Multiorg:
Use a single installation of any Oracle Applications product to support any number of organizations, even if those
organizations use different sets of books.
Business Group (HRMS=>Work structure=>Organization=Description)

Set of Books (GL=>Setup=>Financials=>Books=>Define)
Legal Entity
Operating Unit
Inventory Organization
Sub Inventory (Inventory=.Setup=>organizations=>Sub Inventories)
Stock Locations (Inventory=.Setup=>organizations=>Stock locators)
Items

Major Features:
1) Multiple Organizations in a Single Installation
2) Secure Access, You can assign users to particular organizations. This ensures accurate transactions in the correct
operating unit.
3) Multiple Organizations Reporting
You can set up your Oracle Applications implementation to allow reporting across operating units by setting up the
top reporting level. You can run your reports at the set of books level, legal entity level, or operating unit level.
Business Group: The business group represents the highest level in the organization structure, such as the
consolidated enterprise, a major division, or an operation company. The business group secures human resources
Information. For example, when you request a list of employees, you see all employees assigned to the business
group of which your organization is a part.
Set of Books: A financial reporting entity that uses a particular chart of accounts, Functional currency, and
accounting calendar. Oracle General Ledger secures transaction information (such as journal entries and balances)
by set of books. When you use Oracle General Ledger, you choose a responsibility that specifies a set of books. You
then see information for that set of books only.
Legal Entity: A legal company for which you prepare fiscal or tax reports. You assign tax identifiers and other legal
entity information to this type of organization.
Operating unit: An organization that uses Oracle Cash Management, Order Management and Shipping Execution,
Oracle Payables, Oracle Purchasing, and Oracle Receivables. It may be a sales office, a division or a department. An
operating unit is associated with a legal entity. Information is secured by operating unit for these applications. Each
user sees information only for their operating unit.
Inventory Organization: An organization for which you track inventory transactions and balances, and/or an
organization that manufactures or distributes products. Examples include (but are not limited to manufacturing
plants, warehouses, distribution centers, and sales offices.
The following applications secure information by inventory organization:
Oracle Inventory, Bills of Material, Engineering, Work in Process, Master Scheduling/MRP, Capacity, and purchasing
receiving functions.
Sub inventory: Which is another organization inside of the Inventory organization will be used to define the
locations under these location items will be placed.
Multiorg Table:
It is a table contains the data which is related to multiple operating units all the multi org table names will be end
with '_ALL'.
Like PO_HEADER_ALL
PO_LINES_ALL
AP_CHECKS_ALL and so on
Note: In all these tables we will find one common column called "ORG_ID" This column will be populated internally
by the system as per the User Operating_Unit_ID
Client_Info: It is one the RDBMS variable which contains the User Operating Unit value (ORG_ID)


Multiorg View: It is a view which is created based on the Multiorg table which contains the WHERE
Clause WHERE Org_ID = :Client_Info.
Note: While development of RICE Components we are supposed to Use Multiorg Views not Multi Org Tables.
Because if we use Multiorg tables we will get all the operating units data if we use multi org view we will get the
operating units data which is related for that particular user.
What is the Diff between ORG_ID and ORGANIZATION_ID?

Ans) ORG_ID is at Operating Unit Level and ORGANIZATION_ID is at Inventory Organization level.
OrganizationName Table Profile Column Modules

Business Group hrfv_business_groups HR:Business Group ID business_group_id HRMS
Set Of Books gl_sets_of_books GL: set of books name set_of_books_id GL
Legal Entity hr_legal_entities
Operating Unit hr_operating_units MO:Operating Unit ORG_ID PO,AP,OM,AR,PA,
CM
Inventory org_organization_definit mfg_organization_id organization_id INV,WIP,PROD,BO
Organization ions M,
ENG,MRP PO
Receipts
Sub Inventory mtl_secondary_inventor
ies
Stock Locations mtl_item_locations
Items mtl_system_items
FLEX FIELDS:
Flex field are made up with Attribute columns or Segment columns. Which are more flexible than the normal fields.
We have two type of flex fields
1) DFF (Descriptive Flex Field)
2) KFF (Key Flex Field)
DFF: It will be used to capture the Extra information from the end user without change the code in the form and
without Alter the DB object. ATTRIBUTE Columns will be used to capture the DFF data.
KFF: it will be used to capture the Key information from the User in code language for every code there will be a
specific meaning. SEGMENT Columns will be used Capture the KFF Data
We can find all the flexfield details in Application Developer

Responsibility=>Flexfield=>Descriptive=>register=> CTRL+F11 for all DFF
Flexfield=>Key =>register=> CTRL+F11 for all KFF

DFF Customization:
1. Open the form where DFF is implemented. and Query the Data
2. Find the DFF name from Help Menu =>Diagnostics =>Examine
a. Select $DESCRIPTIVE_FLEXFIELD$ in the Block field
b. select DFF name in the "Field"
c. We will get the DFF Title in the Value field. Copy the DFF title
3. Go to Application Developer Responsibility. flexfield=>Descriptive=>register
4. Query the records by using the DFF Title. Select columns button and find whether Attribute columns are
enabled or disabled.
5. Go to Segments form and Query the records by using Title.
6. Uncheck the Check box called "freeze Flexfield Definition"
7. Select Segments button and enter the new fields and save transactions.
8. Check the check box called "freeze Flexfield Definition" and click the Compile Button.
9. System will change the DFF structure and creates a descriptive flexfield View.
KFF (Key Flex Fields)
KFF will be used to capture the Key Information in code language for every code there will be specific meaning in the
application.
For Ex: we can find some of the fields like follows
Code Combination 01-001-1540-1234-0000
01 -Operations
001 -HRMS
1540 -Furniture
1234 -Sales Account
0000 -No Product
Description : Operations-HRMS-Furniture-Sales Account-No Product.
Like this we can find the meaning in the application for every code.
We will use the Segment Columns to Capture the KFF Data. We can find the Segment columns in most of the Tables
like SEGMENT1, SEGMENT2, SEGMENT3,..........SEGMENT30.
Difference between DFF and KFF

DFF KFF
1) DFF Will be used to capture the Extra 1) KFF will be used to Capture the Key
Information. Information
2) ATTRIBUTE Columns will be used 2) SEGMENT columns will be used
3) We can have max DFF in the Application 3) we have 30KFF already defined by Oracle
There is no Limit we can customize existing KFF. We are not
Suppose to define the new KFF. We will not
Get support from Oracle.
4) In DFF we will Context Field to define 4) In KFF we will define Structure Column
Multiple Structures to define the Multiple Structures.


KFF Description:
P_FLEXDATA: Is a Lexical parameter will be used to store the default value as concatenation of all the segment
columns. This is required because if client changes the segment structure from front end again we have to change all
the structure. Instead of that we can concatenate all the segments.
Lexical parameter means datatype: char width : min 600
P_STRUCT_NUM: It will be used to store the kff structure number which is required if KFF is having the multiple
structures.
Ex: 101 default value
FNDFLEXSQL: This is One of the User exit will be used to retrieve the segment values from database and will be used
in the before report trigger.
Parameters:
CODE -KFF Code
Num -KFF structure Number
Appl_short_name -KFF Application Short Name
Output -Lexical parameter Name
Display -Display all the segments
Mode -'SELECT'
FNDFLEXIDVAL:
This user exit we will define inside of the formulas column to display the data in the layout.
define the formula column call the user exit with following parameters
Parameters:
CODE -KFF Code
Num -KFF structure Number
Appl_short_name -KFF Application Short Name
OutpuT -Lexical parameter Name
Display -Display all the segments
Mode -'SELECT'
Data -Lexical Parameter Name
Value -Formula Column Name
Note:
To Display the KFF description we will define one more formula column and we will call again 'FND FLEXIDVAL' user
exit with parameter called 'Description' instead of 'Value' Parameter.

Oracle Apsps Forms

TEMPLETE.fmb: It is pre-defined form file contains the existing functionality which will support for all the Menu,
Toolbar, and Other Oracle Applications features. To start form development manually then we have to download the
.fmb file and start form development.
1. We will download the TEMPLETE.fmb from AU_TOP\Resource Folder

2. Open with Forms6i builder and delete the existing Block, Canvas and Window.
3. Create New Block, Canvas, Window attach oracle apps Property classes
4. Develop the form as per client requirement.
Note: We will change the Property called "First Navigation Data Block" as Data block Name in the Module Properties.
a. Customize following two triggers 1) Pre-Form -New Window Name

2) WHEN-NEW-FORM-INSTANCE -New form Name
3) APP_Custom package -New Window Name
5. Save the form we will get (.fmb)
6. Compile the form we will get(.fmx) (File => Administration => Compile File)
7. Move the .fmb into au_top\11.5.0\Forms\US\ .fmb
8. Move the .fmx into CuS_top\11.5.0\Forms\US\ .fmx
9. Go to Application Developer and create Form
10. create Function attach form to the function
11. Create Menu attach function menu
12. Attach Menu to the responsibility, Responsibility will be attached to the user so that user can open the form
and enter/Query the Data.
Implement Check Boxes:

1). Define the check Box in the Canvas
2). Attach following Property Classes
a. Subclass Information = Checkbox
b. Enter Value when Checked = whatever value we want to insert into Column
c. Enter Value when Unchecked = whatever value we want to insert into Column
d. Initial Value = Default Value
e. Label = Whatever the Name we would like to display
f. Column Name = Database Column Name
Implement Radio Buttons:
1). Define the Radio Buttons under Same Group
2). Attach following Properties
a. Subclass Information = Radio Button
b. Label = Whatever the Name we would like to display
c. Radio Button Value = whatever value we want to insert into Column
3). Go to Object Navigator Select Radio Group Properties
4). Attach following Properties
a. Subclass Information = Radio Group
b. Initial Value = Default Value
c. Column Name = Database Column Name


Form Creation:
Application Developer=> Application=>Form
Form Name : .fmx name
Application Name : Application name where .fmx is located
User Form Name : We can give any form Name
Function Creation:
For single form we can create Multiple Functions and we can pass the Parameters.
Function Name : Enter any unique Name
User Function Name : Enter any unique Name
Go to Properties tab select Form type = FORM
Go to the form tab attach the Form whatever we have created.
Save and Copy the User function name attach to the Menu.
Menu Creation:
Enter Menu Name: Any valid Name
User Menu Name: Any valid Name
Enter the Seq no: Unique Number
Prompt : Any Text
Function: Attach the User Function Name whatever we have created.
Copy the User menu name and attach to the Responsibility in system administrator.
Attach Calendar:
1). Select the Field properties and select the property called
List of Values: ENABLE_LIST_LAMP
2). Go to the Item level Trigger called KEY-LIST-VAL trigger call the following API Calendar.Show();
Attach the LOV:
1) Define the Record Group Either Static Values or by using the Query
2) Create LOV and attach the Record Group
3) Attach the LOV to field in the property called list of Values.
Implement WHO Columns:
1). Select All the WHO Columns in the Datablock
2). Define following Two Triggers at DataBlock level 1)Pre-Insert
2)Pre-Update
3). Call the following API from both the Triggers FND_STANDARD.SET_WHO():
Standard Libraries Contains all these API's. We can download all these Libraries from Resource folder in AU_TOP.
APPDAYPK : It will Support for All Calendar and Date time Functions
FNDSQF : It will support for all the Flex field, Profile, WHO Columns functionality.

DFF Process:
1). Define the field in the canvas change the field property database items as "no"
2). Define the Package like follows.
Package Specification:
PACKAGE DFF_PKG IS
PROCEDURE DFF_PROC(EVENT VARCHAR2);
END;
Package Body:
PACKAGE BODY DFF_PKG IS

PROCEDURE DFF_PROC(EVENT VARCHAR2) AS
BEGIN
IF (EVENT = 'WHEN-NEW-FORM-INSTANCE' ) THEN
FND_DESCR_FLEX.DEFINE( BLOCK => 'WIP_ITEMS10',
FIELD => 'DFF_TEXT',
APPL_SHORT_NAME => 'WIP',
DESC_FLEX_NAME => 'WIPDFF');
END IF;
END DFF_PROC;
END;
3). Call this Package from WHEN-NEW-FORM-INSTANCE Trigger

Packagename.Procedure name ('WHEN-NEW-FORM-INSTANCE');
DFF_PKG.DFF_PROC ('WHEN-NEW-FORM-INSTANCE');
4). Call another API from WHEN-NEW-ITEM-ISNATCE Trigger
fnd_flex.event ('WHEN-NEW-ITEM-INSTANCE');
-It will populate the DFF in the Form.
Form Personalization:
Form Personalization is a feature in Oracle E-Business Suite 11.5.10 onwards that allows you to change the behavior
of Forms-based screens. Prior to this release if we need to change the behavior of Oracle Forms we need to change
the "custom.pll". That's indeed requires lot of effort and time compared to Forms Personalization which gives you a
interactive user interface to implement the changes needed on the forms.
With the help of Form Personalization we can change properties of form, executing built-ins functions, display
custom messages, add menu entries to call another forms, add rules, conditions and actions.


Why personalization?
 Oracle Supports personalization unlike customization

 Personalization are stored in tables rather than files
 Will not have a bigger impact when you upgrade or apply patches to the environment
 Can be moved easily through FNDLOAD from one instance to other
 Can be restricted at site/responsibility/user level
 Easy to disable/enable with click of a button.
 Personalization will store who columns with which we have the ability to track who created/modified it
where as in CUSTOM.PLL we don’t have that ability.
 Can be applied to new responsibilities/users easily.
 Can be restricted to function or form.
What can be done through personalization?
 Zoom from one form to another

 Pass data from one form to another through global variables
 Change LOV values dynamically
 Enable/Disable/Hide fields dynamically
 Display user friendly messages when required
 Launch URL directly from oracle form
 Execute PL/SQL programs through FORM_DDL package
 Call custom libraries dynamically
Process flow:
 Initialize the menu/icon in source form
 Initialize the global variables
 When the menu/icon is clicked copy the order number from source form filed to global variable and then
launch the destination form
 In the destination form copy the value from global variable to destination form field.
Navigation: Help =>Diagnostics =>Custom Code => Personalize

Interfaces
Interface is one of the Program which will be used to transfer the data from Oracle database tables in to
flat file (or) flat files into database tables. We have two types of Interfaces.
1) Inbound Interface
2) Outbound Interface
Outbound Interface will be used to extract the data from oracle Database tables into the flat files.
Inbound Interface will be used to upload the data from legacy system (Flat files) into Oracle Applications
base tables.
While developing the outbound Interface we will use UTL_File to Extract the data.
While Developing the Inbound interface we will use SQL * loader to import the data into base taqbles.
UTL_FILE Package:
This is one of the PL/SQL Package which will be used to transfer the data from table to files from files to
tables
But when we are working for file to table we will use SQl *Loader to transfer from table to file we have no
alternative we have to use UTL_FILE. We will use following three functions to generate the file.
1)Utl_File.fopen = To open (or) Create the file

2)Utl_File.Put_line = To Transfer the data into the File.
3)Utl_File.fclose = To close the File after Data transfer.
Outbound Interface Process:

1) Develop the PL/SQL Program (Either Procedure or Package)
2) Write the Cursor to retrieve the data from database tables.
3) Create file or Open the File by using UTL_File.fopen().
4) Open the Cursor
5) If any validations are there write the validations
6) Transfer the Data into File by using UTL_File.Put_Line().
7) Close the Cursor.
8) Close the File by using UTL_File.fclose();
9) Register the Procedure or Package as Concurrent Program and submit from SRS Window.


Inbound Interface:
1) We have received flat file from client
2) We have created Staging table as per flat file structure
3) Developed Control file and uploaded data
4) Developed PL/SQL Program to upload the data from stage into interface table
a) Declare Cursor
b) Open cursor
c) Validate each record
d) If no invalid record then insert into interface table.
General Ledger Interface Process:
Flat File from the client
-SQL Loader Program => transferring data from flat file to staging table
SELECT * FROM XX_TEST
PL/SQL Program => Develop pl/sql program to validate and transfer the data from staging table to interface table
SELECT * FROM GL_INTERFACE
-Journal Import
SELECT * FROM GL_JE_HEADERS
SELECT * FROM GL_JE_LINES
SELECT * FROM GL_JE_BATCHES
Errors:
Journal execution report
-Actions
1) Stage table creation
2) SQl loader program
3) PL/SQL Program
PO Inbound Interface:
Flat File => Data Load from Flat File to Staging table WHEN Command File => multiple tables
SELECT * FROM XX_H
SELECT * FROM XX_L
SELECT * FROM XX_D
-PO Data Transfer from staging table to Interface table
SELECT * FROM PO_HEADERS_INTERFACE
SELECT * FROM PO_LINES_INTERFACE
SELECT * FROM PO_DISTRIBUTIONS_INTERFACE
-Import Standard Purchase Orders
SELECT * FROM PO_HEADERS_ALL
SELECT * FROM PO_LINES_ALL
SELECT * FROM PO_LINE_LOCATIONS_ALL
SELECT * FROM PO_DISTRIBUTIONS_ALL
-Errors
SELECT * FROM PO_INTERFACE_ERRORS
Actions:
1) Stage Table Creation
2) SQl Loader Program development and Registration
3) PL/SQL Program development and Registration
4) Standard Program Submission

XML Steps:
1) Develop the Report (.rdf) only in Data Model
2) Save the report and Compile and generate the data in .xml Format
File=>Generate to File => XML
3) Open the MS-Word document Design the Layout, Include the following Tool Bar options called Form and Template
builder
4) Define the Table and Specify the Titles and Labels whatever we would like to print
5) Include 'Text Form Field' Double Click => Add Help Text button enter the following syntax
<?for-each:G_USER_ID?> : Here G_USER_ID is Group name from .rdf Data Model
Note: It means Indirectly Repeating Frame starting
6) Define the Fields which we would like to display, Include 'Text Form Field' Double CLick => Add Help Text button
enter the following syntax
<?Column Name?>
Note: Define all the fields like this
7) We have to close the Repeating Frame (For each Loop)
Include 'Text Form Field' Double CLick => Add Help Text button enter the following syntax
<?end for-each?>
8) Save the document in .rtf (Rich Text File format)
9) Load the .xml file data and generate the Output in pdf Format
Data=>Load XMl Data=>Load the .xml File=>Once Data is loaded successfully
10) Generate the Preview as per this Preview=>PDF






RTL TECHNOLOGIES Oracle R12 Apps Technical

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RTL TECHNOLOGIES Oracle R12 Apps Technical

Uploaded by

Copyright:

Available Formats

Mobile: 9885489062

Oracle Apps Technical Courses

Contact us for placement

 Unix concepts & basics known on shellscript

 Finance & SCM Technical(AP,AR,GL,Inventory,OM,PO)

 Everyweek Mock Interview

 Resume Preparation Tips.

1. Data model objects 11.Data blocks

Oracle Applications R12 Concepts

1. ERP concepts 4. Types Executables

Inbound Interface Process

Ex: SELECT Statement and Formulas, Summary functions and so on.......

Layout Model Objects:

Text: Will be used to display the standard text information

1) Group level: Executed for every record in the group

2) Report Level: Executed only once for entire report.

Plot No-301,Bhanu Towers,Opp ESI Hosp,Erragadda,Hyderabad-38 Page 1

Ex for place holder column:

Empno Ename Sal Hire_Date Comm TotalSal(SAl+Comm) Tax

Tax : if (totalsal>5000 then 7% tax

(Totalsal>3000 and <=5000 then 4%tax

(Totalsal<=3000 then 2% tax)

Empno Ename Sal Comm Tax Netsalary

Comm := 15% sal

Plot No-301,Bhanu Towers,Opp ESI Hosp,Erragadda,Hyderabad-38 Page 2

Plot No-301,Bhanu Towers,Opp ESI Hosp,Erragadda,Hyderabad-38 Page 3

2) User Defined Parameters

DESFORMAT : Html, pdf.....

DESNAME : Name of the Printer, E-mail, Fax, File

DESTYPE : File, Screen, Print, Fax, E-mail

MODE : Bitmap, Character

3)Can be used only in the WHERE Clause 3) In Any Clause

4)Any Data type 4)Only Char Data type

Before Parameter Form

To change the Parameter values dynamically

Plot No-301,Bhanu Towers,Opp ESI Hosp,Erragadda,Hyderabad-38 Page 4

Layout objects means frame, repeating frame, field and etc.

If it is off then Only child object will be decr/Incr.

Program units PL/SQL Objects

1) Will be stored in the file 1) Stored in the Database.

3) Improve the Performance 3) It takes more time

4)Client side objects 4)Server side Objects

Plot No-301,Bhanu Towers,Opp ESI Hosp,Erragadda,Hyderabad-38 Page 5

.pll - Source Code - Program Link Library

.plx - Executable Code - Program Link Executable

Plot No-301,Bhanu Towers,Opp ESI Hosp,Erragadda,Hyderabad-38 Page 6

Versions: 4.5 / 6I / 9I/ 10G

1) Database Data block: Select Data from table /Procedure/View

Database Data block: Yes

Property Type = Content

Plot No-301,Bhanu Towers,Opp ESI Hosp,Erragadda,Hyderabad-38 Page 7

Plot No-301,Bhanu Towers,Opp ESI Hosp,Erragadda,Hyderabad-38 Page 8

Default: Model less Window

If we want to make it model window Go to Window properties: Model = Yes

Static: Enter the values manually

Query Based: Based on the select statement get the values

Non-Query Based: Change the values dynamically.

Property Classes Visual Attributes

2) We cannot change dynamically 2) Visual attributes can be changed SET_VA_PROPERTY

Plot No-301,Bhanu Towers,Opp ESI Hosp,Erragadda,Hyderabad-38 Page 9

1. Form Level: it will be executed once for the entire Form.

WHEN-NEW-RECORD-INSTANCE: When user create new record then it will be fired.

Plot No-301,Bhanu Towers,Opp ESI Hosp,Erragadda,Hyderabad-38 Page 10