eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.HRDYNDBI dependencies on DUAL

Line 885: from sys.dual;

881: --
882: -- create user entity
883: select ff_user_entities_s.nextval
884: into p_user_entity_id
885: from sys.dual;
886:
887: BEGIN
888: insert into ff_user_entities
889: (user_entity_id,

Line 908: from dual

904: p_db_item_name,
905: p_defined_balance_id,
906: p_creator_type,
907: p_description
908: from dual
909: where not exists (
910: select null
911: from ff_user_entities a
912: where a.user_entity_name = p_db_item_name

Line 955: from sys.dual;

951: ELSE -- g_triggers_altered is FALSE so use existing trigger validation
952: --
953: select ff_user_entities_s.nextval
954: into p_user_entity_id
955: from sys.dual;
956: --
957: insert into ff_user_entities
958: (user_entity_id,
959: business_group_id,

Line 1935: from dual;

1931: -- get the user entity id to be used:
1932: --
1933: select ff_user_entities_s.currval
1934: into l_user_entity_id
1935: from dual;
1936: --
1937: -- get the relevant information for the user entity we are using
1938: --
1939: BEGIN

Line 2096: from dual;

2092: l_user_entity_id:=p_user_entity_id;
2093: else
2094: select ff_user_entities_s.currval
2095: into l_user_entity_id
2096: from dual;
2097: end if;
2098:
2099: --
2100: -- get the relevant information for the user entity we are using

Line 2539: FROM dual;

2535: --
2536: begin
2537: SELECT ff_user_entities_s.nextval
2538: INTO l_user_entities_seq
2539: FROM dual;
2540: end;
2541: --
2542: l_user_entity_name := p_user_entity_name;
2543: --

Line 2654: from dual

2650: p_created_by,
2651: p_last_login,
2652: p_created_by,
2653: sysdate
2654: from dual
2655: where not exists (
2656: select null
2657: from ff_user_entities a
2658: where a.user_entity_name = l_user_entity_name

Line 3130: from dual;

3126: -- Fetch the user_entity_id.
3127: --
3128: select ff_user_entities_s.currval
3129: into l_user_entity_id
3130: from dual;
3131: --
3132: -- insert the element type id for the where clause filler
3133: --
3134: insert_parameter_value (p_element_type_id, 1);

Line 3364: from dual;

3360: -- Fetch the user_entity_id.
3361: --
3362: select ff_user_entities_s.currval
3363: into l_user_entity_id
3364: from dual;
3365: --
3366: -- insert the element type id for the where clause filler
3367: --
3368: insert_parameter_value (p_element_type_id, 1);

Line 3573: from dual;

3569: -- Fetch the user_entity_id.
3570: --
3571: select ff_user_entities_s.currval
3572: into l_user_entity_id
3573: from dual;
3574: --
3575: -- insert the element type id for the where clause filler
3576: --
3577: insert_parameter_value (p_element_type_id, 1);

Line 4116: from dual;

4112: -- Fetch the user_entity_id.
4113: --
4114: select ff_user_entities_s.currval
4115: into l_user_entity_id
4116: from dual;
4117: --
4118: -- insert the input value id for the where clause filler
4119: --
4120: insert_parameter_value (p_input_value_id, 1);

Line 4223: from dual;

4219: -- Fetch the user_entity_id.
4220: --
4221: select ff_user_entities_s.currval
4222: into l_user_entity_id
4223: from dual;
4224: --
4225: -- insert the input value id for the where clause filler
4226: --
4227: insert_parameter_value (p_input_value_id, 1);

Line 4351: from dual;

4347: -- Fetch the user_entity_id.
4348: --
4349: select ff_user_entities_s.currval
4350: into l_user_entity_id
4351: from dual;
4352: --
4353: -- insert the input value id for the where clause filler
4354: --
4355: insert_parameter_value (p_input_value_id, 1);

Line 4484: from dual;

4480: -- Fetch the user_entity_id.
4481: --
4482: select ff_user_entities_s.currval
4483: into l_user_entity_id
4484: from dual;
4485: --
4486: -- insert the input value id for the where clause filler
4487: --
4488: insert_parameter_value (p_input_value_id, 1);

Line 4625: from dual;

4621: -- Fetch the user_entity_id.
4622: --
4623: select ff_user_entities_s.currval
4624: into l_user_entity_id
4625: from dual;
4626: --
4627: -- insert the input value id for the where clause filler
4628: --
4629: insert_parameter_value (p_input_value_id, 1);

Line 4689: from dual;

4685: -- Fetch the user_entity_id.
4686: --
4687: select ff_user_entities_s.currval
4688: into l_user_entity_id
4689: from dual;
4690: --
4691: -- insert the input value id for the where clause filler
4692: --
4693: insert_parameter_value (p_input_value_id, 1);

Line 6126: as '%'. To delete an individual descriptive flexfield pass the title

6122: DESCRIPTION
6123: This procedure is the main entry point for deleting descriptive
6124: flexfield database items. To delete all the descriptive flexfield
6125: database items for a given legislation code, pass the title parameter
6126: as '%'. To delete an individual descriptive flexfield pass the title
6127: of the flexfield.
6128: NOTES
6129: Since the legislation code for a descriptive flexfield could be null
6130: a nvl function is required as part of the SQL statement.

Line 6555: Since there is no desciptive flex id to identify an individual row in

6551: 'fnd_descr_flex_column_usages'. For a given descriptive flexfield there
6552: could be several database items.
6553: --
6554: NOTES
6555: Since there is no desciptive flex id to identify an individual row in
6556: the ff_user_entities table, the title of the descriptive flex is used
6557: instead, holding it in the user_entity_name column.
6558: --
6559: It is intended that this flexfield creation procedure be run from the

Line 6677: Since there is no desciptive flex id to identify an individual row in

6673: Extra Position Info DDF and Extra Person Info DDF. The
6674: context passed for these 3 flexfields is the appropriate
6675: information type.
6676: NOTES
6677: Since there is no desciptive flex id to identify an individual row in
6678: the ff_user_entities table, the title of the descriptive flex is used
6679: instead, holding it in the user_entity_name column.
6680: --
6681: It is intended that this flexfield creation procedure be run from the

Line 7019: Since there is no desciptive flex id to identify an individual row in

7015: 'end_user_column_name' from the foundation table
7016: 'fnd_descr_flex_column_usages'. For a given descriptive flexfield there
7017: could be several database items.
7018: NOTES
7019: Since there is no desciptive flex id to identify an individual row in
7020: the ff_user_entities table, the title of the descriptive flex is used
7021: instead, holding it in the user_entity_name column.
7022:
7023: Added rtrim to title select below, due to Reserved word problem, ie

Line 7364: individual key flexfield the following key flexfields are supported:

7360: routes in this table by using the route name, which is hard coded below.
7361: The parameters passed in are the business group id and the name of the
7362: key flexfield. To create all the key flexfield database items for a
7363: particular business group pass the name parameter as '%'. To create an
7364: individual key flexfield the following key flexfields are supported:
7365: --
7366: JOB for 'p_keyflex_name' pass in : 'JOB'
7367: POSITION for 'p_keyflex_name' pass in : 'POS'
7368: GRADE for 'p_keyflex_name' pass in : 'GRD'

Line 8009: from dual

8005: end if;
8006:
8007: select null
8008: into l_exists
8009: from dual
8010: where exists
8011: (
8012: select /*+ INDEX(a FF_DATABASE_ITEMS_PK)
8013: INDEX(b FF_USER_ENTITIES_PK) */ null

Line 8715: from dual

8711: end if;
8712:
8713: select null
8714: into l_exists
8715: from dual
8716: where exists
8717: (
8718: select /*+ INDEX(a FF_DATABASE_ITEMS_PK)
8719: INDEX(b FF_USER_ENTITIES_PK) */ null