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.OKC_RTV_PVT dependencies on OKC_RESOLVED_TIMEVALUES_V

Line 88: -- FUNCTION get_rec for: OKC_RESOLVED_TIMEVALUES_V

84: BEGIN
85: RETURN(get_rec(p_rtv_rec, l_row_notfound));
86: END get_rec;
87: ---------------------------------------------------------------------------
88: -- FUNCTION get_rec for: OKC_RESOLVED_TIMEVALUES_V
89: ---------------------------------------------------------------------------
90: FUNCTION get_rec (
91: p_rtvv_rec IN rtvv_rec_type,
92: x_no_data_found OUT NOCOPY BOOLEAN

Line 106: FROM Okc_Resolved_Timevalues_V

102: CREATION_DATE,
103: LAST_UPDATED_BY,
104: LAST_UPDATE_DATE,
105: LAST_UPDATE_LOGIN
106: FROM Okc_Resolved_Timevalues_V
107: WHERE okc_resolved_timevalues_v.id = p_id;
108: l_okc_ttvv_pk okc_ttvv_pk_csr%ROWTYPE;
109: l_rtvv_rec rtvv_rec_type;
110: BEGIN

Line 107: WHERE okc_resolved_timevalues_v.id = p_id;

103: LAST_UPDATED_BY,
104: LAST_UPDATE_DATE,
105: LAST_UPDATE_LOGIN
106: FROM Okc_Resolved_Timevalues_V
107: WHERE okc_resolved_timevalues_v.id = p_id;
108: l_okc_ttvv_pk okc_ttvv_pk_csr%ROWTYPE;
109: l_rtvv_rec rtvv_rec_type;
110: BEGIN
111: x_no_data_found := TRUE;

Line 139: -- FUNCTION null_out_defaults for: OKC_RESOLVED_TIMEVALUES_V --

135: RETURN(get_rec(p_rtvv_rec, l_row_notfound));
136: END get_rec;
137:
138: ---------------------------------------------------------------
139: -- FUNCTION null_out_defaults for: OKC_RESOLVED_TIMEVALUES_V --
140: ---------------------------------------------------------------
141: FUNCTION null_out_defaults (
142: p_rtvv_rec IN rtvv_rec_type
143: ) RETURN rtvv_rec_type IS

Line 183: -- Validate_Attributes for:OKC_RESOLVED_TIMEVALUES_V --

179: -- 1. Moved all column validations (including FK) to Validate_column
180: -- and is called from Validate_Attributes
181: -- 2. Validate_Records will have tuple rule checks.
182: -------------------------------------------------------
183: -- Validate_Attributes for:OKC_RESOLVED_TIMEVALUES_V --
184: -------------------------------------------------------
185: ---------------------------------------------------------------------------
186:
187: PROCEDURE Validate_Tve_Id (

Line 371: -- Validate_Record for:OKC_RESOLVED_TIMEVALUES_V --

367: ---------------------------------------------------------------------------
368: -- PROCEDURE Validate_Record
369: ---------------------------------------------------------------------------
370: ---------------------------------------------------
371: -- Validate_Record for:OKC_RESOLVED_TIMEVALUES_V --
372: ---------------------------------------------------
373: FUNCTION Validate_Record (
374: p_rtvv_rec IN rtvv_rec_type
375: ) RETURN VARCHAR2 IS

Line 425: -- validate_row for:OKC_RESOLVED_TIMEVALUES_V --

421: ---------------------------------------------------------------------------
422: -- PROCEDURE validate_row
423: ---------------------------------------------------------------------------
424: ------------------------------------------------
425: -- validate_row for:OKC_RESOLVED_TIMEVALUES_V --
426: ------------------------------------------------
427: PROCEDURE validate_row(
428: p_api_version IN NUMBER,
429: p_init_msg_list IN VARCHAR2,

Line 674: -- insert_row for:OKC_RESOLVED_TIMEVALUES_V --

670: '_PVT'
671: );
672: END insert_row;
673: ----------------------------------------------
674: -- insert_row for:OKC_RESOLVED_TIMEVALUES_V --
675: ----------------------------------------------
676: PROCEDURE insert_row(
677: p_api_version IN NUMBER,
678: p_init_msg_list IN VARCHAR2,

Line 708: -- Set_Attributes for:OKC_RESOLVED_TIMEVALUES_V --

704: l_rtvv_rec.LAST_UPDATE_LOGIN := FND_GLOBAL.LOGIN_ID;
705: RETURN(l_rtvv_rec);
706: END fill_who_columns;
707: --------------------------------------------------
708: -- Set_Attributes for:OKC_RESOLVED_TIMEVALUES_V --
709: --------------------------------------------------
710: FUNCTION Set_Attributes (
711: p_rtvv_rec IN rtvv_rec_type,
712: x_rtvv_rec OUT NOCOPY rtvv_rec_type

Line 994: -- lock_row for:OKC_RESOLVED_TIMEVALUES_V --

990: '_PVT'
991: );
992: END lock_row;
993: --------------------------------------------
994: -- lock_row for:OKC_RESOLVED_TIMEVALUES_V --
995: --------------------------------------------
996: PROCEDURE lock_row(
997: p_api_version IN NUMBER,
998: p_init_msg_list IN VARCHAR2,

Line 1302: -- update_row for:OKC_RESOLVED_TIMEVALUES_V --

1298: '_PVT'
1299: );
1300: END update_row;
1301: ----------------------------------------------
1302: -- update_row for:OKC_RESOLVED_TIMEVALUES_V --
1303: ----------------------------------------------
1304: PROCEDURE update_row(
1305: p_api_version IN NUMBER,
1306: p_init_msg_list IN VARCHAR2,

Line 1393: -- Set_Attributes for:OKC_RESOLVED_TIMEVALUES_V --

1389: END IF;
1390: RETURN(l_return_status);
1391: END populate_new_record;
1392: --------------------------------------------------
1393: -- Set_Attributes for:OKC_RESOLVED_TIMEVALUES_V --
1394: --------------------------------------------------
1395: FUNCTION Set_Attributes (
1396: p_rtvv_rec IN rtvv_rec_type,
1397: x_rtvv_rec OUT NOCOPY rtvv_rec_type

Line 1637: -- delete_row for:OKC_RESOLVED_TIMEVALUES_V --

1633: '_PVT'
1634: );
1635: END delete_row;
1636: ----------------------------------------------
1637: -- delete_row for:OKC_RESOLVED_TIMEVALUES_V --
1638: ----------------------------------------------
1639: PROCEDURE delete_row(
1640: p_api_version IN NUMBER,
1641: p_init_msg_list IN VARCHAR2,

Line 1787: p_view_name => 'OKC_RESOLVED_TIMEVALUES_V');

1783: -----------------------------------------------------------
1784: BEGIN
1785: -- call OKC_UTIL.ADD_VIEW to prepare the PL/SQL table to hold columns of view
1786: OKC_UTIL.ADD_VIEW(x_return_status => g_return_status,
1787: p_view_name => 'OKC_RESOLVED_TIMEVALUES_V');
1788: END OKC_RTV_PVT;