The document provides steps to customize an Oracle Forms application. It involves copying template files, PL/SQL libraries, designing a new form in Forms Builder, deploying and compiling the form, registering the form in Oracle Applications, attaching it to a menu responsibility, and viewing the customized form. Key steps include renaming the template form, creating new windows, canvases, and datablocks, modifying triggers to reference the new objects, deploying and compiling the form, registering the form and linking it to a menu responsibility for users to access.
The document provides steps to customize an Oracle Forms application. It involves copying template files, PL/SQL libraries, designing a new form in Forms Builder, deploying and compiling the form, registering the form in Oracle Applications, attaching it to a menu responsibility, and viewing the customized form. Key steps include renaming the template form, creating new windows, canvases, and datablocks, modifying triggers to reference the new objects, deploying and compiling the form, registering the form and linking it to a menu responsibility for users to access.
The document provides steps to customize an Oracle Forms application. It involves copying template files, PL/SQL libraries, designing a new form in Forms Builder, deploying and compiling the form, registering the form in Oracle Applications, attaching it to a menu responsibility, and viewing the customized form. Key steps include renaming the template form, creating new windows, canvases, and datablocks, modifying triggers to reference the new objects, deploying and compiling the form, registering the form and linking it to a menu responsibility for users to access.
The document provides steps to customize an Oracle Forms application. It involves copying template files, PL/SQL libraries, designing a new form in Forms Builder, deploying and compiling the form, registering the form in Oracle Applications, attaching it to a menu responsibility, and viewing the customized form. Key steps include renaming the template form, creating new windows, canvases, and datablocks, modifying triggers to reference the new objects, deploying and compiling the form, registering the form and linking it to a menu responsibility for users to access.
>Open Oracle Forms Builder >Open the form TEMPLATE.fmb >Rename the form (ex XX_abcd1) >Delete the followings from object nevigator. >Go to Data Blocks and delete BLOCKNAME, DETAILBLOCK >Go to Windows and delete BLOCKNAME >Go to Canvases and delete BLOCKNAME b) Create a new Window (ex WINDOW10) c) Create a new Canvas (ex CANVAS10) and attached it to the new Window via Property Palate d) Create a new Datablock (ex CUSTOMERS) wth items from a table. e) Create a frame in the Canvas and attached the items f) Modify the PRE-FORM Trigger >Go to triggersPREFORM >Original Code:
> Go to APP_CUSTOM*(Package Body) >Type your First window name in place of <your first window> > Compile the code h) If any Item in the Datablock is of Date type and you want to attach a standard calender to it (ex Orderdate item of Customers datablock), do the following > Go to Orderdate > Property palate > Subclass Information > Property Class > Give property class name as TEXT_ITEM_DATE > Attach LOV as ENABLE_LIST_LAMP > Create KEY-LISTVAL item level trigger & add following code into it calendar.show; and compile the trigger.
Step 3: DEPLOY THE FORM IN THE SERVER
> Upload your .fmb file
Step 4: CREATE THE .fmx FILE IN THE SERVER
>Type the code $ORACLE_HOME/bin/frmcmp_batch module=$XXAR_TOP/forms/US/CUSTOMERS.fmb userid=<username>/<password> output_file=$XXAR_TOP/forms/US/ CUSTOMERS.fmx module_type=form compile_all=special
Step 5: REGISTARING THE FORM IN ORACLE APPS
a) Registaring the FORM in Oracle Apps
> Go to Application Developer > Application > Form > Give the details:
FORM: CUSTOMERS(name of the custom form)
APPLICATION: Custom AR Application User Form Name: CUSTOMERS_DETAIL Description: Customer Detail form > save
b) Registaring the FORM to a form function
> System Administrator ->Application -> Function > Give the details:
Form->form:CUSTOMERS_DETAIL Function:XX_CUSTOMER_DETAIL APPLICATION: Custom AR Application Properties > Type: Form User Function Name: CUSTOMERS_DETAIL_FUNCTION
> save c) Finding the menu to which the above form function is to be attached. Again the menu is attached to a responsibilty. So we have go in the reverse order to find the menu name. > System Administrator ->Security -> Responsibility ->Define > Press F11 > Responsibility Name: %US%Rec (searching for US Receivables Super User) > Press Ctrl + F11
> This things will come in the form
Responsibility Name: US Receivables Super User Application:Receivables (will come automatically )
>Take the Menu name >AR_NAVIGATE_GUI
d) Attaching the function to a Submenu of the above Main menu
> System Administrator ->Application > Menu > Press F11 > Menu: AR_NAVIGATE_GUI > Press Ctrl+F11
> Promt: Custom Interfaces
> Submenu: XXAR_CUSTOM
>System Administrator ->Application > Menu
> Press F11 > Menu: XXAR_CUSTOM > Press Ctrl+F11 > Create a new > Promt: Customer Detail Form (It will display in the nevigator) >Function: CUSTOMERS_DETAIL_FUNCTION (Attach the function to the submenu) > save >One request has been submitted to recompile your menus in the database e) Viewing the request submitted in the background to recompile the menus to attach the function > Go to View>Requests>Find >The status should be :Compiled Normal
Step 6: VIEWING THE FORM IN ORACLE APPLICATION:
>Go to Oracle apps front end.
>Login with username and password >Go to US Receivables Super User>Custom Interfaces >Customer Detail Form
FND_STANDARD.SET_WHO doesn't work / not working
Even though FND_STANDARD.SET_WHO is set in pre-insert and pre-update data block triggers it fails to show record history.
Use app_special.enable('ABOUT', PROPERTY_ON) in WHEN-NEW-BLOCK-INSTACE trigger of
