APPS.CS_SERVICEREQUEST_UTIL dependencies on CS_SR_PROB_CODE_MAPPING_PKG

Line 2906: -- validation api cs_sr_prob_code_mapping_pkg.validate_problem_code

2902: -- agains cs_lookups
2903: -- --------------------------------------------------------------------------------
2904: -- DJ API Cleanup
2905: -- Changed the validation of Problem code to invoke the problem code
2906: -- validation api cs_sr_prob_code_mapping_pkg.validate_problem_code
2907: PROCEDURE Validate_Problem_Code (
2908: p_api_name IN VARCHAR2,
2909: p_parameter_name IN VARCHAR2,
2910: p_problem_code IN VARCHAR2,

Line 2921: l_pc_rec cs_sr_prob_code_mapping_pkg.probcode_search_rec;

2917:
2918: l_api_name CONSTANT VARCHAR2(30) := 'Validate_Problem_Code';
2919: l_api_name_full CONSTANT VARCHAR2(61) := G_PKG_NAME||'.'||l_api_name;
2920:
2921: l_pc_rec cs_sr_prob_code_mapping_pkg.probcode_search_rec;
2922:
2923: lx_msg_count NUMBER;
2924: lx_msg_data VARCHAR2(2000);
2925:

Line 2941: cs_sr_prob_code_mapping_pkg.validate_problem_code (

2937: -- problem code is valid for the given mapping criteria. This API call
2938: -- is introduced in 11.5.10 and replaces the SQL logic that was present
2939: -- pre 11.5.10
2940:
2941: cs_sr_prob_code_mapping_pkg.validate_problem_code (
2942: p_api_version => 1.0,
2943: p_init_msg_list => FND_API.G_TRUE,
2944: p_probcode_criteria_rec => l_pc_rec,
2945: p_problem_code => p_problem_code,