|
For custom data, and application either the OAF / ADF technology is used to create the user interface, and the traditional older method is forms.
Even though Oracle EBS is slowly moving towards http(s) protocol, still forms are preferred because of resource availability, and the flexibility.
Some of the custom forms implemented
- Order to Shipping Solution: The main order entry was done in Mainframe application, and interfaced to Oracle EBS. From Creating the Order to Shipping the Order, user needs a single screen to display the history.
- Commission Management: Commission calculation for one of the client is a complex calculation and not handled by the standard Oracle EBS.
This application used to calculate the commission to make the payment to the distributors.
|
| |
Forms Personalization |
|
|---|
|
Forms personalization is very dynamic.
Few of the Form level triggers are New Form Instance, New Block Instance, New Record Instance, New Item Instance, When Validate Item,
and When Validate Record are used in personalization. Conditionally the triggers can be called in Application, Responsibility, and User level.
Available Tool Menu also can be enabled or disabled by forms personalization.
There are some limitations in the forms personalization, and modify the CUSTOM.pll. In that case, modification of the form is considered.
Modified form is registered under custom application, and called in the required menu. If a standard form is modified, then each upgrade or patch
affected that particular form needs to be rebuild with the custom code.
|
| | |
| |
Note: Before installing the Developer Suite, make sure that System Properties - Advanced - Virtual Memory is set to
Initial Size(MB)2046, and Maximum Size(MB)4092.
If your computer have 8GB RAM, then you may set Initial Size(MB): 2046, and Maximum Size(MB): 8103. Minimum Initial Size required is 256MB.
|
| |