An OAF page consists of 2 Deployable Regions – SharedRegion and Page and they are with the naming convention RN.xml and PG.xml. The technology is designed such a way that , the definition of RN/PG gets stored in the below MDS (Meta Data Service) – DB tables, whey get deployed on the server. If they are stored in DB, how will they shown in the browser as a graphical HTML components, If you observe carefully any OAF page which gets opened in the browser will have : OA.jsp which considers OAF page path as input and it is the rendering engine, which converts xml content in MDS into HTML at run Time. This is the rendering concept of OAF page.
|Stores document paths, packages and there parent child relationship.
Primary Key: PATH_DOCID
|Stores components on documents and OA Framework pages.
Primary Key: COMP_DOCID, COMP_SEQ
|Stores attribute/properties of components on documents and OA Framework pages.
Primary Key: ATT_COMP_DOCID, ATT_COMP_SEQ, ATT_SEQ
|Stores translated attribute values of document components or OA framework pages.
Primary Key: ATL_COMP_DOCID, ATL_LANG, ATL_COMP_REF, ATL_NAME
jdr_utils.deletedocument(p_document => '/oracle/apps/per/server/customizations/employeeDetailsAM');