Beruflich Dokumente
Kultur Dokumente
Content
Overview
OAF Personalizations are an easy and fully supported way to adapt a certain page in
Oracle EBS to fit better certain business needs.
With OAF Personalizations can do a lot, but not in all cases such a change can be seen
as easy. Personalizations can be very complex, especially when you use your own
custom code to change the underlying validations.
This HowTo concentrates on the option to validate which personalizations have been
added to the screens. It allows you to get a better understanding how to read a
personalization entry.
To review if a certain page has been personalized, use the “about this page” link.
BEGIN
DBMS_OUTPUT.ENABLE(100000);
FOR R1 IN C1 LOOP
FULLNAME := JDR_MDS_INTERNAL.GETDOCUMENTNAME(R1.PATH_DOCID);
V_POS:= INSTR(FULLNAME,'/user/'); V_LEN:= LENGTH('/user/');
IF V_POS > 0 THEN
V_LEVEL := 'Single User';
V_USER_ID := SUBSTR(FULLNAME,V_POS+V_LEN,INSTR(SUBSTR(FULLNAME,V_POS+V_LEN),'/')-1);
v_user_name := who (V_USER_ID);
END IF;
V_POS:= INSTR(FULLNAME,'/responsibility/'); V_LEN:= length('/responsibility/');
IF V_POS > 0 THEN
V_LEVEL := 'Single Responsibility';
V_USER_ID := SUBSTR(FULLNAME,V_POS+V_LEN,INSTR(SUBSTR(FULLNAME,V_POS+V_LEN),'/')-1);
select responsibility_name into v_user_name from fnd_responsibility_vl where
responsibility_id = V_USER_ID;
END IF;
V_POS:= INSTR(FULLNAME,'/function/'); V_LEN:= LENGTH('/function/');
IF V_POS > 0 THEN
V_LEVEL := 'Single Function';
v_user_name := SUBSTR(FULLNAME,V_POS+V_LEN,INSTR(SUBSTR(FULLNAME,V_POS+V_LEN),'/')-1);
END IF;
V_POS:= INSTR(FULLNAME,'/site/');
IF V_POS > 0 THEN
V_LEVEL := 'Site';
v_user_name := Null;
END IF;
CHUNK := JDR_MDS_INTERNAL.EXPORTDOCUMENTASXML(FULLNAME);
IF INSTR(CHUNK,'replace with=') > 0 OR INSTR(CHUNK,'modifica') > 0
then
DBMS_OUTPUT.PUT_LINE(RPAD('-',80,'-'));
DBMS_OUTPUT.PUT_LINE('Path: '||FULLNAME);
DBMS_OUTPUT.PUT_LINE('Level: '||V_LEVEL);
IF V_USER_NAME IS NOT NULL THEN DBMS_OUTPUT.PUT_LINE('Name: '||V_USER_NAME); END IF;
DBMS_OUTPUT.PUT_LINE('Date: created='||R1.CREATION_DATE||',
last_updated='||R1.LAST_UPDATE_DATE);
DBMS_OUTPUT.PUT_LINE('Who: created='||who(r1.created_by)||',
last_updated='||who(r1.last_updated_by));
DBMS_OUTPUT.PUT_LINE(rpad('-',80,'-'));
DBMS_OUTPUT.PUT_LINE(CHUNK);
end if;
END LOOP;
-- DOCID := JDR_MDS_INTERNAL.GETDOCUMENTID(FULLNAME, TRUE, TRUE);
-- doc_id := 79030;
END;
/
In module PO, in Order area, the OrderlineDetails page has been touched 29th April
by INTERNAL (can be anyone).
In module OZF, tradeplanning, on user level (for RSPILLEM only) in the dashboard,
a default search criteria has been added to Party Name = Peugeot France.
In a custom module XXTRV, in the request area of page Request details, three fields
have been disabled.
In the Bank Area (IBY), on responsibility level ‘Purchasing Super User’, 4 fields have
been set to required.
In the supplier area, a button “Create Site” has been disabled conditionally, based on
an existing function XXPOS_ALLOW_SITE_CREA. This button will become visible
if this function is assigned to you (via menu or grant).
In this case the standard VO = View Object has been substituted with a custom VO.
Usually such a change adds additional columns, or makes the underlying view more
restrictive.
Here the standard EO = Entity Object has been substituted with a custom EO.
Oracle Corporation
Email: volker.eckardt@oracle.com
Linkedin: http://de.linkedin.com/pub/volker-eckardt/0/8a7/430