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.PQP_GB_OSP_FUNCTIONS dependencies on SSP_MATERNITIES

Line 690: -- of the column from table SSP_MATERNITIES

686: --
687: END pqp_get_ssp_medical_addnl_attr;
688:
689: -- pqp_get_ssp_matrnty_details is the main function to get the value
690: -- of the column from table SSP_MATERNITIES
691: FUNCTION pqp_get_ssp_matrnty_details(
692: p_absence_attendance_id IN NUMBER
693: ,p_col_name IN VARCHAR2
694: ,p_error_code OUT NOCOPY NUMBER

Line 703: l_maternity_id ssp_maternities.maternity_id%TYPE;

699: l_val VARCHAR2(2000);
700: l_proc_step NUMBER(38,10):=0;
701: l_proc_name VARCHAR2(61):=
702: g_package_name||'pqp_get_ssp_matrnty_details';
703: l_maternity_id ssp_maternities.maternity_id%TYPE;
704: BEGIN
705:
706: IF g_debug THEN
707: debug_enter(l_proc_name);

Line 733: ,p_table => 'SSP_MATERNITIES'

729: l_val :=
730: pqp_utilities.get_col_value(
731: p_col_nam => p_col_name
732: ,p_key_val => l_maternity_id
733: ,p_table => 'SSP_MATERNITIES'
734: ,p_key_col => 'MATERNITY_ID'
735: ,p_where => NULL
736: ,p_error_code => p_error_code
737: ,p_message => p_message

Line 763: -- from the flex filed SSP_MATERNITIES

759: END IF;
760: END pqp_get_ssp_matrnty_details;
761:
762: -- pqp_get_ssp_matrnty_addnl_attr returns the value of the items
763: -- from the flex filed SSP_MATERNITIES
764: FUNCTION pqp_get_ssp_matrnty_addnl_attr(
765: p_business_group_id IN NUMBER
766: ,p_effective_date IN DATE
767: ,p_absence_attendance_id IN NUMBER

Line 779: l_maternity_id ssp_maternities.maternity_id%TYPE;

775: l_val VARCHAR2(2000);
776: l_proc_step NUMBER(38,10):=0;
777: l_proc_name VARCHAR2(61):=
778: g_package_name||'pqp_get_ssp_matrnty_addnl_attr';
779: l_maternity_id ssp_maternities.maternity_id%TYPE;
780: BEGIN
781:
782: IF g_debug THEN
783: debug_enter(l_proc_name);

Line 814: ,p_tab_name => 'SSP_MATERNITIES'

810: l_val :=
811: pqp_utilities.pqp_get_concat_value(
812: p_key_col => 'MATERNITY_ID'
813: ,p_key_val => l_maternity_id
814: ,p_tab_name => 'SSP_MATERNITIES'
815: ,p_view_name => 'SSP_MATERNITIES_DFV'
816: ,p_message => p_message
817: );
818: --

Line 815: ,p_view_name => 'SSP_MATERNITIES_DFV'

811: pqp_utilities.pqp_get_concat_value(
812: p_key_col => 'MATERNITY_ID'
813: ,p_key_val => l_maternity_id
814: ,p_tab_name => 'SSP_MATERNITIES'
815: ,p_view_name => 'SSP_MATERNITIES_DFV'
816: ,p_message => p_message
817: );
818: --
819: ELSE

Line 824: p_flex_name => 'SSP_MATERNITIES'

820: --
821: debug(l_proc_name, 30);
822: l_val :=
823: pqp_utilities.get_df_value(
824: p_flex_name => 'SSP_MATERNITIES'
825: ,p_flex_context => NULL
826: ,p_flex_field_title => p_segment_name
827: ,p_key_col => 'MATERNITY_ID'
828: ,p_key_val => l_maternity_id

Line 829: ,p_tab_name => 'SSP_MATERNITIES'

825: ,p_flex_context => NULL
826: ,p_flex_field_title => p_segment_name
827: ,p_key_col => 'MATERNITY_ID'
828: ,p_key_val => l_maternity_id
829: ,p_tab_name => 'SSP_MATERNITIES'
830: ,p_effective_date => p_effective_date
831: ,p_eff_date_req => 'N'
832: ,p_business_group_id => p_business_group_id
833: ,p_bus_group_id_req => 'N'

Line 1521: -- of the column from table SSP_MATERNITIES

1517:
1518: END ben_get_ssp_medical_addnl_attr;
1519:
1520: -- ben_get_ssp_matrnty_details is the main function to get the value
1521: -- of the column from table SSP_MATERNITIES
1522: FUNCTION ben_get_ssp_matrnty_details(
1523: p_assignment_id IN NUMBER
1524: ,p_effective_date IN DATE
1525: ,p_col_name IN VARCHAR2

Line 1578: -- from the flex filed SSP_MATERNITIES

1574: END IF;
1575: END ben_get_ssp_matrnty_details;
1576:
1577: -- ben_get_ssp_matrnty_addnl_attr returns the value of the items
1578: -- from the flex filed SSP_MATERNITIES
1579: FUNCTION ben_get_ssp_matrnty_addnl_attr(
1580: p_business_group_id IN NUMBER
1581: ,p_effective_date IN DATE
1582: ,p_assignment_id IN NUMBER

Line 2002: -- ssp_maternities. Inputs are absence_attendance_id and the title

1998: END IF;
1999: END get_medical_details;
2000:
2001: -- get_matrnty_details Returns the value of the column in table
2002: -- ssp_maternities. Inputs are absence_attendance_id and the title
2003: -- of the column in the absence form.The mapping of form title to the DB
2004: -- column is done in Lookup and the same is fetched by calling
2005: -- get_lookup_code function.
2006: FUNCTION get_matrnty_details(

Line 3459: l_maternity_id ssp_maternities.maternity_id%TYPE;

3455: IS
3456: l_proc_step NUMBER(38,10):=0;
3457: l_proc_name VARCHAR2(61):=
3458: g_package_name||'pqp_get_maternity_id';
3459: l_maternity_id ssp_maternities.maternity_id%TYPE;
3460: BEGIN
3461: IF g_debug THEN
3462: debug_enter(l_proc_name);
3463: debug('p_absence_id:'||p_absence_id);

Line 4868: -- ssp_maternities. Input is title of the column in the absence form.

4864: --
4865: --
4866: --
4867: -- ben_matrnty_details Returns the value of the column in table
4868: -- ssp_maternities. Input is title of the column in the absence form.
4869: -- The mapping of form title to the DB column is done in Lookup and the
4870: -- same is fetched by calling get_lookup_code function.
4871: -- assignment_id and effective Date are contexts.
4872: --