APPS.PO_ONLINE_AUTHORING_WF_ACTIONS dependencies on WF_DIRECTORY

Line 453: WF_DIRECTORY.CreateAdHocRole( l_role_name, -- role_name

449: -- Create a role
450: IF PO_LOG.d_stmt THEN
451: PO_LOG.stmt(d_mod,'Creating l_role_name',l_role_name );
452: END IF;
453: WF_DIRECTORY.CreateAdHocRole( l_role_name, -- role_name
454: l_role_display_name , -- role_display_name
455: null, -- language
456: null, -- territory
457: null, -- role_description

Line 504: -- the user and the dsp name will be the one listed in WF directory

500: --Locks:
501: -- None
502: --Function:
503: -- If lock owner is cat admin, then wf role will be the user name of
504: -- the user and the dsp name will be the one listed in WF directory
505: -- If lock owner is supplier, then we need to create a adhoc user if one
506: -- does not exist. This is because we want to the role to have the display
507: -- name equal to vendor name, which may not exist in the system
508: --Parameters:

Line 598: WF_DIRECTORY.CreateAdHocRole

594: d_position := 50;
595:
596: x_wf_role_name := l_expected_wf_role_name;
597:
598: WF_DIRECTORY.CreateAdHocRole
599: ( x_wf_role_name,
600: x_wf_role_name_dsp,
601: NULL,
602: NULL,

Line 614: WF_DIRECTORY.setAdHocRoleAttr

610: );
611: ELSE
612: -- if a role already exists, make sure that the role display name
613: -- is up to date
614: WF_DIRECTORY.setAdHocRoleAttr
615: ( x_wf_role_name,
616: x_wf_role_name_dsp,
617: NULL,
618: NULL,