1 PACKAGE AS_SCN_FORECAST_PUB AUTHID CURRENT_USER as
2 /* $Header: asxppems.pls 115.6 2004/07/13 09:34:24 gbatra ship $ */
3 G_SUBMITTED VARCHAR2(30) := 'SUBMITTED';
4 G_SAVED VARCHAR2(30) := 'SAVED';
5
6 -- Note: The meaning of some of the fields in this record type has changed in 11.5.10.
7 -- Here are the differences:
8 -- Pre-11.5.10
9 -- ===========
10 -- Pre 11.5.10, the fields Interest_Type_Id, Pri_Interest_Code_Id and Sec_Interest_Code_Id
11 -- store the interest type id, primary interest code id and secondary interest code id
12 -- respectively. The field Interest_Type stores the mapping type that is a lookup with
13 -- 3 values: TYPE, PCODE and SCODE. The mapping type indicates whether the plan element
14 -- is defined for an interest type or primary interest code or secondary interest code
15 -- respectively.
16 -- 11.5.10
17 -- =======
18 -- In 11.5.10, the fields Interest_Type_Id and Pri_Interest_Code_Id will store product
19 -- category id and product category set id respectively. The fields Sec_Interest_Code_Id
20 -- and Interest_Type will not be used any more and will be passed as null. The reason for
21 -- not passing a value to Interest_Type field is that mapping type has been obsoleted in
22 -- 11.5.10. The descriptions associated with the product category id can be obtained from
23 -- the concat_cat_parentage column in view ENI_PROD_DEN_HRCHY_PARENTS_V.
24 -- For more details, please refer the design doc.
25 TYPE forecast_Rec_Type IS RECORD (
26 INTEREST_TYPE_ID NUMBER ,
27 PRI_INTEREST_CODE_ID NUMBER ,
28 SEC_INTEREST_CODE_ID NUMBER ,
29 INTEREST_TYPE VARCHAR2(80) ,
30 WORST_FORECAST_AMOUNT_FLAG VARCHAR2(1) ,
31 WORST_FORECAST_AMOUNT NUMBER ,
32 FORECAST_AMOUNT_FLAG VARCHAR2(1) ,
33 FORECAST_AMOUNT NUMBER ,
34 BEST_FORECAST_AMOUNT_FLAG VARCHAR2(1) ,
35 BEST_FORECAST_AMOUNT NUMBER );
36
37 G_MISS_FORECAST_REC Forecast_Rec_Type;
38
39 TYPE Forecast_Tbl_Type IS TABLE OF Forecast_Rec_Type INDEX BY BINARY_INTEGER;
40
41 G_MISS_FORECAST_TBL Forecast_Tbl_Type;
42
43
44 -- Start of Comments
45 -- API name: Get_Forecast_Amounts
46 -- Type: Public
47 -- Description:
48 --
49 -- Pre-reqs:
50 --
51 -- IN PARAMETERS:
52 -- p_api_version_number IN NUMBER (Standard)
53 -- p_init_msg_list IN VARCHAR2 := FND_API.G_FALSE (Standard)
54 -- p_check_access_flag IN VARCHAR2 (Standard - "Y" by default) to verify the access.
55 -- p_resource_id IN NUMBER (resource_id for which forecast needs to be collected
56 -- p_quota_id IN NUMBER (Plan Element ID )
57 -- p_period_name IN VARCHAR2 ( period name as in OSO)
58 -- p_to_currency_code IN VARCHAR2 ( currency code in which you want to see the amounts)
59
60 -- OUT PARAMETERS
61 -- x_return_status: (API standard)
62 -- x_msg_count: (API standard)
63 -- x_msg_data: (API standard)
64 -- x_forecast_amount_tbl - forecast out put for every sales category
65 --
66 -- Version: Current version 2.0
67 --
68 -- Note:
69 -- This API is supposed to be used by Sales Comp for Income planner for individual
70 -- when calling this api, user needs to pass in p_resource_id ,p_quota_id ,
71 -- p_period_name and p_to_currency_code
72 --
73 -- End of Comments
74
75 PROCEDURE Get_Forecast_Amounts (
76 p_api_version_number IN NUMBER,
77 p_init_msg_list IN VARCHAR2 := FND_API.G_FALSE,
78 p_check_access_flag IN VARCHAR2,
79 p_resource_id IN NUMBER,
80 p_quota_id IN NUMBER,
81 p_period_name IN VARCHAR2,
82 p_to_currency_code IN VARCHAR2,
83 x_return_status OUT NOCOPY VARCHAR2,
84 x_msg_count OUT NOCOPY NUMBER,
85 x_msg_data OUT NOCOPY VARCHAR2,
86 x_forecast_amount_tbl OUT NOCOPY FORECAST_TBL_TYPE);
87
88
89 END AS_SCN_FORECAST_PUB;
90