Showing posts with label Forms. Show all posts
Showing posts with label Forms. Show all posts

Tuesday, 28 August 2012

Calling one form to another form


1)Develop both forms and register in application.
2)Place the Button in first from
3)Write the following code in WHEN-BUTTON-PRESSED Trigger.

Fnd_FunCtion.execute(function_name => 'Second form function Name',
            open_flag     => 'Y'    ,        
                     OTHER_PARAMS  => 'P1 = '||:PO_VENDORS.VENDOR_ID);

P1 is Second form parameter

4)Open the Second foRm and define the Parmaeter called P1

5)goto PRE-QUERY trigger and write the following code to change the query dynamically.

 :PO_VENDOR_SITES_ALL.VENDOR_ID  := :PARAMETER.P1;
 --:Blockname  .fieldname          := :PARAMETER.Parametername

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
======================================================

1)Develop the form
2)Register the form
3)Create Two functions for the same form.
  first function without parameters
  second function is with parameter called 'QUERY_0NLY="YES" '
enter the paraneter in the field called Parameter field.


SubMenu Creations:
==================

1)Copy the Functions whatever we would like to define as submenu
  delete from the main menu.
2)Create new menu and attach the functions whatever we have copied.

3)Copy the menu whatever we have created attach to the main menu by selecting the
  field called submenu.

Hiding the forms and Menus at Responsibility level=
===================================================


1)Open the Responsibility Form attach the menu
2)By default we will get all the forms and as well we menus will be displayed.
3)Select the Tab called Menu Exclusions Tab
  Select the  type = Function  to hide the funtion.
  select the  type = Menu name to hide the menu.


Calling SRS Window from Menu:
=============================


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.


Attach the Request group to the SRS Function:
===============================================

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"

3)Pass the follwoing Parameters while creation of the function.
REQUEST_GROUP_CODE="CUSTOMERCODE1"
REQUEST_GROUP_APPL_SHORT_NAME="AR"
TITLE="23CUSTOMERS"

4)Attch the function to the Menu , Menu to Responsibility , Responsibility to user

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.


Display the Message Boxes in the Forms:
=======================================

1)Create the Message in Application Developer
2)Run the Concurrent Program called "Generate Messages"
  by passing  language code and as well as application name
3)Call the message from form triggers by using FND_MESSAGE API's.

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();

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 al the Flexfield,profile,WHO Columns functionality.



       

CANVAS_FORM



2)CREATE ANOTHER CANVAS ,OPEN PROPERTY PALLET OF IT
NAME   ==SCAN
CANVAS TYPE==STACKED
VIEW X POSITION  -100
VIEW Y POSITION-100

===============================================
3)CREATE ANOTHER DATA BLOCK

SELECT * FROM AP_INVOICES_ALL

VENDOR_ID,INVOICE_NUM,INVOICE_AMOUNT,AMOUNT_PAID,DISCOUNT_AMOUNT_TAKEN,INVOICE_DATE

ALONG WITH RELATION OF EXISTING BLOCK OF COOMON COLUMN OF VENDOR_ID OF SCAN CANVAS

4)Place a buttuon in STACKED CANVAS====NAME AND LABLE AS  SCAN
==============================================
WRITE- WHEN BUTTON PRESSED-TRIGGER OF  STACKED CANVAS
====================================

HIDE_VIEW('SCAN');
GO_ITEM('PO_VENDORS.VENDOR_ID');


OPEN KEY NEXT ITEM TRIGGER OF VENDOR_NAME IN CCNA CANVAS
===========================================

IF :PO_VENDORS.VENDOR_NAME IS NOT NULL THEN
SHOW_VIEW('SCAN');
GO_ITEM('AP_INVOICES_ALL.INVOICE_NUM');
ELSE
NEXT_ITEM;
END IF;

5)CREATE ANOTHER DATA BLOCK
===============================(RCV_SHIPMENT_HEADERS)

vendor_id,receipt_num,ship_to_org_id,shipped_date,invoice_date


ALONG WITH RELATION OF EXISTING BLOCK OF COOMON COLUMN OF VENDOR_ID OF SCAN1 CANVAS

CANVAS GETS CREATED NAME IT AS  CCAN

2)CREATE ANOTHER CANVAS ,OPEN PROPERTY PALLET OF IT
NAME   ==SCAN1
CANVAS TYPE==STACKED
VIEW X POSITION  -100
VIEW Y POSITION-100

4)Place a buttuon in STACKED CANVAS====NAME AND LABLE AS  HIDE

HIDE_VIEW('SCAN1');
GO_ITEM('AP_INVOICES_ALL.VENDOR_ID');

OPEN KEY NEXT ITEM TRIGGER OF INVOICE_NUM
===========================================

if :ap_invoices_all.invoice_num is not null then
show_view('SCAN1');
GO_ITEM('RCV_SHIPMENT_HEADERS.RECEIPT_NUM');
ELSE
NEXT_ITEM;
END IF;

Using DFF Process in Forms



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.

Sunday, 8 April 2012

Oracle From Questions


1) What is Data Block?
Ans) Data Block contains the Table and Columns. Will be used to INSERT/UPDATE/DELETE the records from the Form.


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.

Tab canvases are displayed on top of a content canvas


Toolbar Canvas A toolbar canvas often is used to create toolbars for individual windows.

1. Horizontal toolbar canvases are displayed at the top of a window,
2. Vertical toolbars are displayed along the far left edge of a window.

Window:

A window is a container for all visual objects that make up a Form Builder application, including canvases.

A single form can include any number of windows.

Windows also can be displayed and closed programmatically.

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.

Modeless window requires no such response.
You can display multiple modeless windows at the same time

Modal property to Yes or No   No: Modeless Yes: Model

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.

Data blocks can also be Master Block and Detail Block

All blocks are either single-record or multi-record blocks

5) What are Master-detail Relation ship types?

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.

On-Check-Delete-Master (Block Level)
On-Clear-Details              (Form Level)
On-Populate-Details        (Block Level)
 
Deferred:  (Yes) we have to execute detail block manually.
Automatic Query: No

(Deferred = Yes, Automatic Query = Yes)

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.

2 types of record groups we have

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.

5) How to set the block as Control Block?
Create Data Block
Change the property Database Data block: No