[Home] [Help]
1270: select effective_date
1271: from fnd_sessions
1272: where session_id = userenv('sessionid');
1273: --
1274: l_route_id ff_routes.route_id%type;
1275: l_db_item_name ff_database_items.user_name%type;
1276: l_dbitem_def_text ff_database_items.definition_text%type;
1277: l_dbi_function pay_balance_dimensions.database_item_function%type;
1278:
1924: l_last_login ff_user_entities.last_update_login%type;
1925: l_user_entity_name ff_user_entities.user_entity_name%type;
1926: l_ent_bg_id ff_user_entities.BUSINESS_GROUP_ID%type;
1927: l_ent_lc ff_user_entities.LEGISLATION_CODE%type;
1928: l_route_name ff_routes.route_name%type;
1929: l_route_cd varchar2(60);
1930: l_route_lud varchar2(60);
1931: l_route_lub number;
1932: BEGIN
1985: into l_route_name,
1986: l_route_cd,
1987: l_route_lud,
1988: l_route_lub
1989: from ff_routes
1990: where route_id = l_route_id;
1991:
1992: hr_utility.trace('route_name: ' || l_route_name);
1993: hr_utility.trace('route creation date: ' || l_route_cd);
2420: and one that uses its own local p_record_inserted paramter (whose
2421: values is subsequently ignored).
2422: The parameters passed are:
2423: p_route_name - the route name to be used, this must already be
2424: seeded in the table ff_routes.
2425: p_user_entity_name - The name of the user entity.
2426: p_entity_description- The description of the entity.
2427: p_not_found_flag - Y/ N, Y= the database item may not be found in
2428: some cases, N= it will ALWAYS return a value.
2608: BEGIN
2609:
2610: SELECT route_id
2611: INTO l_route_id
2612: FROM ff_routes
2613: WHERE route_name = p_route_name;
2614:
2615: EXCEPTION WHEN OTHERS THEN
2616: hrrbdeib_trace_on;
2975: database items have '_DP' appended to the database name. To create date
2976: earned DB items, set the paramater 'p_date_p' to null. To create date
2977: paid DB items, set it to '_DP'.
2978: The routes must have already been defined in the
2979: database (in table ff_routes). The procedure will search for the
2980: routes in this table by using the route name, which is hard coded below.
2981: The procedure processes each route in turn, creating a user entity and
2982: route parameter values, and then inserting each database items for that
2983: particular route.
3831: database items have '_DP' appended to the database name. To create date
3832: earned DB items, set the paramater 'p_date_p' to null. To create date
3833: paid DB items, set it to '_DP'.
3834: The routes must have already been defined in the
3835: database (in table ff_routes). The procedure will search for the
3836: routes in this table by using the route name, which is hard coded below.
3837: The procedure processes each route in turn, creating a user entity and
3838: route parameter values, and then inserting each database items for that
3839: particular route.
5916: --
5917: DESCRIPTION
5918: This procedure is the main entry point for creating database items for
5919: either grades or spines. The routes must have already been defined in the
5920: database (in table ff_routes). The procedure will search for the
5921: routes in this table by using the route name, which is hard coded below.
5922: The procedure processes each route in turn, creating a user entity and
5923: route parameter values, and then inserting each database items for that
5924: particular route.
6719: -- declare a cursor to check whether the route uses a parameter
6720: --
6721: cursor c_chk_route_parameter (p_route_name varchar2) is
6722: select data_type
6723: from ff_route_parameters rpm, ff_routes rt
6724: where rt.route_name = p_route_name
6725: and rpm.route_id = rt.route_id;
6726:
6727: l_routes c_routes%rowtype;
7150: --
7151: DESCRIPTION
7152: This procedure is the main entry point for creating absence type
7153: database items. The routes must have already been defined in the
7154: database (in table ff_routes). The procedure will search for the
7155: routes in this table by using the route name, which is hard coded below.
7156: The database items use the absence type name. The following
7157: database item is created:
7158: --
7432: --
7433: DESCRIPTION
7434: This procedure is the main entry point for creating key
7435: flexfield database items. The routes must have already been defined
7436: in the database (in table ff_routes). The procedure will search for the
7437: routes in this table by using the route name, which is hard coded below.
7438: The parameters passed in are the business group id and the name of the
7439: key flexfield. To create all the key flexfield database items for a
7440: particular business group pass the name parameter as '%'. To create an
7602: --
7603: DESCRIPTION
7604: This procedure is the main entry point for creating External Account Key
7605: flexfield database items. The routes must have already been defined
7606: in the database (in table ff_routes). The procedure will search for the
7607: routes in this table by using the route name, which is hard coded below.
7608: The parameter passed in is the id_flex_num of the keyflex.
7609: --
7610: The database items use the segment name column from the foundation