Please enable JavaScript.

Coggle requires JavaScript to display documents.

Oracle Application Framework (Different Projects (1) Development of OAF…

- - - - a) Entity object (EO) and Entity Association (AO)
        
        Entity Association (AO)
        
        1) Association is relationship between two entity objects having common column (Attribute) between two EO’s
        
        2) All the entity association naming convention end with AO. Example: SupplierSitesAO
        
        3) When you create entity association OAF will generate 1 file Example: SupplierSitesAO.xml
        
        4)This association contains SupplierEO.SidSitesEO.sid
        
        5) To perform the DML operations on master and child tables will go for Entity Association
        Example: on delete cascade—delete the parent corresponding child also will delete.
        On update keys – if u update corresponding child also will update
        On update who columns -- (Creation date, created by) --
        
        Entity object (EO)
        
        1) Entity object represents table/view/synonyms and snapshots.
        2) All the Entity object naming convention end with EO.
        Example : AP_SUPPLIER – ApSupplierEO , AP_SUPPLIER_SITES – ApSupplierSitesEO
        3) Performing the DML operations on the page must have to create an entity object.
        4) When u create the entity object OAF will create BY DEFAULT two files.
        ApSupplierEO.xml and ApSupplierEOImpl.java
        
        Types of Entity Object:
        
        1) Java based entity object – perform the DML operations on oracle custom tables will go for java based entity object.
        Example : Xx_emp_tab ( insert on custome table )
        
        2) PLSQLbased entity object: perform the DML operations on oracle Std tables will go for plsql based entity object.
        Example : ap_suppliers ( insert on Std table )
        
        Note: Oracle apps we have custom tables(custom tables provided by client) and std table(provided by oracle)
        
        4 Sections
        
        2) Create method Public void create()
        {
        // at the time creation of new record create method will invoke
        setSupplierId(“SEQ NAME”);
        }
        
        3)Remove method
        Public void remove()
        {
        // at the delete the record this remove method will execute
        setStuas(“Inactive”);
        }
        
        1) Setter and getter
        Public number getSupplierId()
        {
        Return SupplierId
        }
        Public void setSupplierId()
        {
        }
        Public String getSupplierName()
        {
        Return SupplierName
        }
        Public void setSupplierName()
        {
        }
        
        4) Validate method Pubic void validate()
        {
        Date dsdate=get sdate();
        Date dedate=getedate();
        If(dedate.getTime()>dsdate.gettime())
        {
        }
        }
        
        Example: AP_Supplier—SUPPLIER ID, Supplier Name, SupplierType(3 attributes), status, sdate and end date
      - b) View object (VO)and View links (VL)
        
        View links (VL):
        
        3) When u create the view link OAF will generate one xml file
        DeptEmpVL.xml
        EmpVO – deptno
        DeptVO – deptno
        
        2) All the view link objects naming convention end with VL .
        Example :DeptEmpVL
        
        1) Relationship between two view objects having common column between two VOs EmpVO – deptno and DeptVO – deptno Note : Jdeveloper tool have a option to perform join with the help of viewlink
        
        4) Display the master and child data to avoid the duplications
        
        View Objects (VO) :
        
        1) View objects access all the SQL QUERIES
        2) All the view objects naming convention end with VO
        Example : EmployeeVO
        3) When u create the view objects oaf will generate 2 files mandatory and one file is optional
        Example : EmployeeVO.xml (Mandatory) – query columns will convert into attributes, attribute Data types, attribute precision
        Select * from emp;
        Method 1: Vo.setwhereclause(empid); Method 2: Vo.setwhereclause(deptid);
        EmployeeVORowimpl.java(optional) – to process multiple rows
        Page1 -- emp full data
        Page2—filter the emp data by emp id
        Page3 – filter the emp data by dept id
        
        Types of view objects
        
        1)AutomaticVO - always link with EOS(then only u can perform DML operations on the page)
        
        2)ManualVO - Manually u have to write the sql queries(display the DATA AND SEARCH OPERATIONS)
      - c) Application module (AM)(OADB Transactions, connection open , connection close)
        
        4) When you create the application module OAF will generate two files.
        1) EmployeeAM.xml (It will create the view objects instances in am.xml file)
        2) EmployeeAMImpl.java (voimpl and row impl info will be there in am impl.java)
        
        Types of Application modules:
        
        b) Nested Application Module: When you attach am to the sub region of the called as Nested application module
        
        a) Root Application Module: When you attach AM to the main region of the page called as Root application module
        
        Note: When you create the page by default one main region will be creates (default region for any page), Every region we have property called AM Definition, If you want to run the page u need to map the AM to the page.
        
        3) All the Application module objects naming convention end with AM .
        Example: EmployeeAM
        
        1) DB Connections open and close will be taken care Application module
        
        2) Interface between all the DB objects and transactions with OAF page called as Application module.
  - - - Public void processrequest(OAPageContext, OAWebBean)
        {
        Http get
        }
      - Public void procesformrequest(OAPageContext x, OAWebBean y)
        {
        http post
        opc
        }
      - Public void Processformdata()
        Optional method in the controller—I have third-party data (soa service, web service and excel data) to be processed into MY oaf page
    - - OAPageContext – is one of the built in class in OAF
        
        Context values - Org id,User name,User id,Resp name,Resp id. All the AOL related from EBS will access from OAPageContext java class.
        
        1) To get the apps context values.
        Opc.getUserName() (void method or data type method)
        Opc.getorgid()
        Opc.getrespname()
        
        2) To get the value non db value from the page.
        SupplierName
        Opc.getParameter(“SupplierName”);
        
        3) Call one page to another page.
        Page1 --> page2
        Opc.setforwardurl(“page2 url”);
      - OAWebBean -- is one of the built in class in OAF
        
        OAWebBean:owb
        Bean = item = field
        Represents the properties of the Items (fields)
        25+ item styles are there in OAF
        CHECK BOX, RADIO BUTTON, BUTTON, TEXT INPUT ETC