Beruflich Dokumente
Kultur Dokumente
5) goto PRE-QUERY trigger and write the following code to change the query dynamically.
6) Goto the WHEN-NEW-FORM-INSTANCE Trigger at form level. write the following code
GO_BLOCK('PO_VENDOR_SITES_ALL');
EXECUTE_QUERY;
queryig form:
SubMenu Creations:
1) Create the Function for the User form name called "Run Reports"
2) Attach the Function to the menu.
3) Attach the menu to the responsibility
so that user can call the form from the menu.
1)Create the Request group in System administrator by specifying the request group
code
Copy the Request group name
application short name
request group code
2)Goto the Appllication developer create the fucntion for the user form name called
" Run Reports"
5)when we open the form we can get the programs which are there in the request
group.
note: We will follow this prcocedure to attach the multiple request groups to the
single Responsibility.
begin
FND_MESSAGE.SET_NAME ('PO', 'NEW MESSAGE');
fnd_message.show();
end;
Libraries:
APPDAYPK: This Library will support for all the Date and Time functionality in the
application.
FNDSQF : This Library will support for all the flexfield,Curency,WHO Coluns,Log File
Message functionalities.
APPCORE : It will support for all the Menu and Tool Bar functionality in the application.
CUSTOM : Will be used to make small customizations in the standard forms without
downloading the (.fmb)
Note: 1)We can download all these libraries from the AU_TOP\11.5.0\Resource Folder
where we will find all the Libraries both (.pll) and (.plx).
.pll = Program Link Library
.plx = Program link Executable
2)we are not suppose to customize any of these libraries we can utilize the existing
API's
3)We can Customize only one Library that is CUSTOM.pll
Attach Calendar:
----------------------
1) Select the Field properties and select the property called
List of Values : ENABLE_LIST_LAMP
2)Goto the Item level Trigger called KEY-LIST-VAL trigger call the following API
CAlendar.Show();
APPDAYPK : It will Support for All CAlendar and Date time Functions
FNDSQF : It Will support for al the Flexfield,profile,WHO Columns functionality.
CANVAS_FORM
===============================================
3)CREATE ANOTHER DATA BLOCK
VENDOR_ID,INVOICE_NUM,INVOICE_AMOUNT,AMOUNT_PAID,DISCOUNT_AMOUNT_TAKEN,INVO
ICE_DATE
HIDE_VIEW('SCAN');
GO_ITEM('PO_VENDORS.VENDOR_ID');
vendor_id,receipt_num,ship_to_org_id,shipped_date,invoice_date
HIDE_VIEW('SCAN1');
GO_ITEM('AP_INVOICES_ALL.VENDOR_ID');
DFF Process:
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
END;
2) Types of Canvases?
Ans) a canvas is a surface inside a window. Where we can place the Layout objects like (Text, Radio button, Check
box)
1) Content (Default)
2) Stacked
3) Vertical Tool bar
4) Horizontal Tool Bar
5) Tab
Content:
A content canvas is the "base" view that occupies the entire content pane of the window in which it is displayed.
You must define at least one content canvas for each window you create.
Stacked Canvas:
A stacked canvas is displayed on the content canvas assigned to the current window.
It takes some part of content canvas.
We can hide this canvas programmatically .
We can display more than one canvas at time in the window.
Tab Canvas
A tab canvas made up of one or more tab pages
Allows you to group and display a large amount of related information on a single dynamic Form Builder canvas
object.
Ex: we want to display Customer information, sites, tax, and bank account …..
We can use Tab canvas.
Toolbar Canvas
A toolbar canvas often is used to create toolbars for individual windows.
Window:
A window is a container for all visual objects that make up a Form Builder application, including canvases.
1) Model Windows.
2) Modeless Windows.
A modal window (often a dialog) requires the end user to respond before continuing to work in the current
application.
4) Types of Blocks?
1) Data block: Data blocks are associated with data (table columns) within a database.
2) Control Block: a control block is not associated with the database.
The items in a control block do not relate to table columns within a database.
1) Isolated
2) Non-Isolated (Default)
3) Cascade
Cascading The master record can be deleted, and any associated detail records are automatically
deleted from the database at commit time.
Isolated The master record can be deleted, but the associated detail records are not deleted from the database.
Non-Isolated The default setting. The master record cannot be deleted if associated detail records exist in the
database.
Form Builder defers fetching the associated detail records until the end user navigates to the detail block.
Prevent Master less operation: Specifies whether end users should be allowed to query or insert records in a block
that is a detail block in a master-detail relation.
When set to Yes, Form Builder does not allow records to be inserted in the detail block
Record Group:
A record group is an internal Form Builder data structure that has a column/row framework similar to a database
table.
1) Static
2) Query based
LOV: An LOV is a scrollable popup window that provides the end user with either a single or multi-column
selection list.
END zoom_available;
b) Pre-Block
c) Pre-Record
d) Pre-Text-Item
e) When-New-Form-Instance
f) When-New-Block-Instance
g) When-New-Record-Instance
h) When-New-Item-Instance
i) Post-Text-Item
j) Post-Record
k) Post-Block
l) Post-Form
Q. What is the process of Form registration in Oracle Apps?
In Brief,
We need to follow the following steps in your form:
a) Create a displayed field to hold your concatenated segment values (the [ ] field).
b) Create fields (normally hidden) for each of the flexfield columns in your table (the
one used for your flex).
c) In the form-level WHEN-NEW-FORM-INSTANCE,
call FND_DESCR_FLEX.DEFINE,
setting BLOCK parameter to the name of the block containing your [ ] field,
the FIELD parameter to the name of your [ ] field,
the APPL_SHORT_NAME parameter to the short name of your application and the
DESC_FLEX_NAME parameter to the name of your descriptive flex.
WHEN-VALIDATE-ITEM,
PRE-INSERT,
PRE-UPDATE,
POST-QUERY and
PRE-QUERY triggers place a call to FND_FLEX.EVENT as follows:
FND_FLEX.EVENT ( ‘TRIGGER_NAME’);
where TRIGGER_NAME is the name of the trigger,
If user needs to personalize any details in a form like changing field names, adding some validations, etc,
then Form Personalization can provide the way out in few simple steps.
Steps:
Step – 1:
Go to the specific form where you need the changes
Then we need to note down the block and field name which is needed in next steps.
So keep the cursor on the required field and then Go to Help Diagnostics Examine
Note down the Block and Field value.
Step -2:
Now the step to do the personalization
1. Rule
2. Condition
3. Actions
4. Context
Step – 3:
Rule:
This is the section where you need to create the rules how your requirement is going to be executed.
This section contains 4 segments, Seq, description, Level and Enabled flag.
Seq : Need to give the Sequence how the rule will execute (a number)
Description: Write a sort description of the rule which you are going to create
Level: Select the level where you want the rule to execute
Enabled: This is the flag which will enable or disable the rule.
Example:
Step – 4:
Condition:
Now need to set the condition.
This is the section where you will define when the rule will be executed.
This section contains 4 segments, Trigger Event, Trigger Object, Condition and Processing mode.
Trigger Event: This specifies where the rule will be executed. There are mainly 5 types of event which
decided the trigger of the rule.
Trigger Object: This is the Object in the form which decides at what level the rule will be executed.
Condition: Here mention any SQL statement to control the execution of the rule when the mentioned
criterion is met.
Processing Mode: This is the mode where you want the rules to be executed.
Example:
Step – 5:
Actions:
This decides what will happen when the rule will execute.
According to this the right section will come and need to fill the detailed actions.
Right Sectionis a dynamic section; it appears depending on the Type field value in Left section.
Action Types:
Property
The action type “Property” is used to set the properties of the objects. The various objects include
“Item, Window, and Block etc.”. Actual object name defined in the form should be entered after
selecting the object type.
The current value of the property will be displayed when clicked on the “Get Value” button.
Example:
The value is interpreted at runtime, so you can use SQL functions and operators. Any value started with
“=” operator will be interpreted at runtime; otherwise the value is treated as is entered in the value field
Message:
The action type “Message” is used to display custom messages during runtime. Message Type and
Description should be entered after selecting the action type as “Message”. The available message types
are “Error, Warning, Hint, Question and Debug”. Depending on the response expected from the user,
the appropriate message type should be selected.
Example:
Builtin:
The action type “Builtin” is used to execute the form and AOL API’s. Depending on the API type selected,
the parameters should be entered.
Example:
Argument = http://www.oracle.com
Menu:
The action type “Menu” is used to activate the available special menus on the Tools menu.
Oracle Applications provide 45 special menus under Tools menu which can be used by customers based
on their requirements.
Select the SPECIAL menu which is not used by the form. Menu label is the prompt which appears to the
users when Tools menu is invoked, block specifies the blocks for which the special menu should be
activated and Icon name is the .ico file name.
A separator can be created above the activated special menu by selecting the “Render line before
menu” checkbox.
Example:
Step – 6:
Context:
Context manages to whom the personalization should apply. This is similar to the concept of using
profile options in Oracle Applications. The various levels are Site, Responsibility, Industry and User.
During runtime, the values provided in the context are evaluated and personalization rules will be
applied. Usage of context is very vital in implementing the personalization to prevent the inappropriate
users accessing these customizations of the form.
Example:
Context = Responsibility
Solution:
Step -1:
Here in this case this will be the Sales Orders form and then Line Items tab.
Then we need to note down the block and field name which is needed in next steps.
So keep the cursor on the required field and then Go to Help Diagnostics Examine
Note down the Block and Field value.
Step -2:
Step – 4:
Step – 5:
Step – 6:
Save this.
Log out of the application and login again, then in Sales Order line item tab enter Qty field value as 1 and
try to save, you can see the message.