Oracle Application Framework - OAF

There are two columns already that may fits your need.

START_DATE_ACTIVE

Date when the classification becomes active for the supplier

END_DATE_ACTIVE

Date when the classification becomes inactive for the supplier

However, if you need to capture more additional informations in any standard tables, Oracle recommended to capture those additional information through out a DFF attributes. In this table you have 5 addition attributes to use them. Therefore, Oracle not recommended to add any additional physical columns on any standard table.

Hello Chandra,

To iterate through a VO in OAF by either RowSetIterator and then loop through it to fetch attributes value, or using FilteredRows this will give us an advantage of getting only rows that meets a particular condition, or using RowQualifier this is similar to  FilteredRows but instead of typing the condition using VO attribute, we are write normal SQL condition.

Now let’s see an example using the first option:

OAApplicationModule oaapplicationmodule = pageContext.getApplicationModule(webBean);
DeptEOVOImpl deptEOVO = 
(DeptEOVOImpl)oaapplicationmodule.findViewObject("DeptEOVO");

DeptEOVORowImpl deptEOVORow = null;

RowSetIterator deptRowSetIter = deptEOVO.createRowSetIterator("DeptRowSetIter");

while(deptRowSetIter.hasNext())
{
deptEOVORow = (DeptEOVORowImpl)deptRowSetIter.next();
System.out.println("DeptID-->"+ deptEOVORow.getDeptId() + " Dept Name-->"+ deptEOVORow.getDeptName());

}
deptRowSetIter.closeRowSetIterator();

Hi Chandra

You can use this query to list all customizations across all modules

SELECT   PATH.PATH_DOCID CUSTM_DOC_ID, JDR_MDS_INTERNAL.GETDOCUMENTNAME (PATH.PATH_DOCID) CUSTM_DOC_PATH
FROM     JDR_PATHS PATH
WHERE    PATH.PATH_DOCID IN (SELECT DISTINCT COMP_DOCID
                             FROM   JDR_COMPONENTS
                             WHERE  COMP_SEQ = 0
                             AND    COMP_ELEMENT = 'customization'
                             AND    COMP_ID IS NULL)
ORDER BY CUSTM_DOC_PATH;

and if you want to get only specific module you can use following query:

SELECT   PATH.PATH_DOCID PERZ_DOC_ID, JDR_MDS_INTERNAL.GETDOCUMENTNAME (PATH.PATH_DOCID) CUSTM_DOC_PATH
FROM     JDR_PATHS PATH
WHERE    PATH.PATH_DOCID IN (SELECT DISTINCT COMP_DOCID
                             FROM   JDR_COMPONENTS
                             WHERE  COMP_SEQ = 0
                             AND    COMP_ELEMENT = 'customization'
                             AND    COMP_ID IS NULL)
AND      (JDR_MDS_INTERNAL.GETDOCUMENTNAME (PATH.PATH_DOCID)) LIKE '%/ar/%'
ORDER BY CUSTM_DOC_PATH;

Hello Aashish,

There are three common means of passing parameters between pages :
Request
Transaction
Session

and you can use VO attributes for passing values
Values stored in VO attributes are available in all pages within the transaction with same Root AM.

URL Parameters : Encryption and Encoding
When we are passing parameters in URL, following need to be considered:

[code]
{@Attr} – encodes. Changes Prince Kapoor to Prince%20Kapoor
{!Attr} – encrypts. Encrypts sensitive information.
{$Attr} – plain token substitution (no encoding or encryption)
{@@RETURN_TO_MENU} – Used for E-Business Suite Personal Home Page. Same as OAWebBeanConstants.RETURN_TO_MENU_URL.
{@@RETURN_TO_PORTAL} – Return the user to a launching Portal page. Same as OAWebBeanConstants.RETURN_TO_PORTAL_URL.
[/code]