APPS.CS_SERVICEREQUEST_UTIL dependencies on CS_SR_PROB_CODE_MAPPING_PKG

Line 2904: -- validation api cs_sr_prob_code_mapping_pkg.validate_problem_code

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

Line 2919: l_pc_rec cs_sr_prob_code_mapping_pkg.probcode_search_rec;

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

Line 2939: cs_sr_prob_code_mapping_pkg.validate_problem_code (

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