205: -- p_application_id IN NUMBER Required
206: -- p_profile_id IN NUMBER Required
207: -- p_profile_name IN VARCHAR2 Optional
208: -- p_profile_type IN VARCHAR2,
209: -- p_profile_attrib_tbl IN JTF_PERZ_PROFILE_PUB.PROFILE_ATTRIB_TBL_TYPE Optional
210: -- p_parent_id IN NUMBER Required
211: -- p_object_id IN NUMBER Optional
212: -- p_object_name IN VARCHAR2 Required
213: -- p_object_description IN VARCHAR2 Optional
283:
284: p_profile_id IN NUMBER,
285: p_profile_name IN VARCHAR2,
286: p_profile_type IN VARCHAR2,
287: p_profile_attrib_tbl IN JTF_PERZ_PROFILE_PUB.PROFILE_ATTRIB_TBL_TYPE
288: := JTF_PERZ_PROFILE_PUB.G_MISS_PROFILE_ATTRIB_TBL,
289:
290: p_application_id IN NUMBER,
291: p_parent_id IN NUMBER,
284: p_profile_id IN NUMBER,
285: p_profile_name IN VARCHAR2,
286: p_profile_type IN VARCHAR2,
287: p_profile_attrib_tbl IN JTF_PERZ_PROFILE_PUB.PROFILE_ATTRIB_TBL_TYPE
288: := JTF_PERZ_PROFILE_PUB.G_MISS_PROFILE_ATTRIB_TBL,
289:
290: p_application_id IN NUMBER,
291: p_parent_id IN NUMBER,
292: p_object_type_id IN NUMBER,
449: --
450: -- 1. looks up the the profile for the give profile data.
451: -- It is highly recommended for performance reasons to bring the user's
452: -- PERSONALIZATION profile at log on time using
453: -- JTF_PERZ_PROFILE_PUB.Get_Profile() by passing the PERSONALIZATION
455: -- 2. looks up the object type, if it exists
456: -- 3. the procedure will then create a LF object in the framework
457: --
617: --
618: -- 1. looks up the the profile for the give profile data. It is highly
619: -- recommended for performance reasons to bring the user's
620: -- PERSONALIZATION profile at log on time using
621: -- JTF_PERZ_PROFILE_PUB.Get_Profile() by passing the PERSONALIZATION
623: -- 2. the procedure will then check if a personalized LF object with the
624: -- specified name exists. Again, specifying object_id will improve
625: -- performance.