Skip to main content

Use CUSTOM.pll for forms customization

By

What is the CUSTOM Library
- Standard oracle liabrary supplied with Oracle Applications
- Allows customer to enhance standard functionality of the oracle Applications
- Every forms based screen will access CUSTOM.pll
- Ideal point to create business rule which affects entire organization
- This is the Only method supported by Oracle for Oracle Applicaitons enhancements



How to Use the CUSTOM Library
Since the CUSTOM library is a typical Forms PL/SQL library, it can include standard PL/SQL logic, Oracle Forms
built-in commands and may have other Forms PL/SQL libraries attached to it. The base CUSTOM library is located
in the $AU_TOP/resource directory on your forms server.

Explore the CUSTOM.pll using the Oracle Forms Designer module to examine the sample code that exists in library. Once any enhancements are made, the library must be generated into an executable library (CUSTOM.plx) that then can be used by the Oracle Applications Forms runtime module. Since the CUSTOM library is loaded once for a given session, a user must log out of the application and sign-on again before any changes will become apparent. It is suggested that you also place a copy of the CUSTOM library in your customization directory as a safety precaution.

Since the CUSTOM library’s standard location is in the $AU_TOP/resource, it can be
overwritten during an upgrade of the Applications. Once enhancements are implemented, the CUSTOM library is accessed by the Oracle Applications based upon ‘events’. The ‘events’ define the occasions when the Applications will look into the CUSTOM library for additional code to execute.
Some events are generic:
        WHEN-NEW-FORM-INSTANCE – initially entering a form
        WHEN-NEW-BLOCK-INSTANCE – entering a zone (or block) within a form
        WHEN-NEW-ITEM-INSTANCE – moving into a new field within the form
        WHEN-NEW-RECORD-INSTANCE - creating a new record
        WHEN-FORM-NAVIGATE – navigating thru a form using the mouse
        WHEN-VALIDATE-RECORD – saving (committing) the information to the database
        EXPORT – triggered by using the Export feature

Some events are field specific
        ZOOM – Pre -11 feature for moving to another form and querying up specific records

Some events are form specific
       SPECIALn - (where n is a number between 1 and 45) used to generate entries in the ‘Special’ menu of the
                         tool bar and the code is triggered by selecting a menu choices from the ‘Special’ option on the toolbar
       KEY-Fn – (where n is a number between 1 and 8) triggered by pressing the corresponding function key

Some events are application specific:
       Application Object Library
           WHEN-LOGIN-CHANGED – when a user logs on as a different user
           WHEN-RESPONSIBILITY-CHANGED – when a user changes responsibilities
           WHEN-PASSWORD-CHANGED – when a user changes their password



Comments

Post a Comment

Popular posts from this blog

Use of Who Columns in Oracle APPS table

By
Oracle APPS : WHO COLUMNS WHO columns are used to track the information updated or inserted by the users against the tables. FND_STANDARD package is used for this purpose. FND_STANDARD.SET_WHO Procedure is used to update the WHO columns in a Table when a DML operation s (i.e. INSERT, UPDATE) performed. Steps required to Track WHO Information in our form   1. ALTER the table by adding WHO columns in the table.   2. Open TEMPLATE.fmb in form Builder.   3. Perform all the pre‐requisites to develop a form.   4. Include all the WHO columns in the Data Block with NULL Canvas.   5. Call FND_STAND.SET_WHO procedure in Pre‐Insert and Pre‐Update triggers       at Block Level.   6. Save and Compile the Form.   7. Perform all the pre‐requisites to register the form Note: 1. WHO Columns need not register with the table registration option.           2. Table registration will be done only for KFF and DFF col...
Post a Comment
Read more

Oracle APPS Create Responsibility and User in Oracle EBS

By
How to create Responsibility and User in Oracle EBS How to Create a Responsibility? Step 1: Connect to Oracle Application with APPSADMIN/APPSADMIN User. Step 2: Go to Application Administrator. Step 3: Go to Security then Responsibility then Define Step 4: Enter the Data in the opened Window. Note: Above Information of Responsibility is stored in FND_RESPONSIBILITY Table. How to Create a User? Step 1: Connect to Oracle Application with APPSADMIN/APPSADMIN User. Step 2: Go to Application Administrator. Step 3: Go to Security then User then Define Step 4: Enter the Data in the opened Window. Note: Above Information of User is stored in FND_USER Table. User Responsibilities stored in FND_USER_RESP_GROUPS Table.
2 comments
Read more

Setup steps for Drop Shipments in Oracle EBS

By
  Oracle Order Entry and Oracle Purchasing integrate to provide drop shipments. Drop shipments are orders for items that your supplier ships directly to the customer either because you don't stock or currently have the items in inventory, or because it's more cost-effective for the supplier to ship the item to the customer directly SETUP A) Associate drop shipments with a receiving location. B) Drop shipments support a Destination Type of Expense or Inventory only. C) We can handle returns of drop shipments using standard Order Entry/Shipping or Purchasing functionality. There are different ways you may want to handle returns depending on whether the customer returned the item to you or directly to the supplier. We have to consider the following setup: 1- Inventory Setup  Inventory Setup : (Define and Maintain The Item) The drop ship inventory organization, item and subinventory must be setup prior to creating any drop ship orders. All drop ship ...
3 comments
Read more