1 PACKAGE BODY CSD_LOGISTICS_CUHK AS
2 /* $Header: csdclogb.pls 120.0.12020000.3 2013/04/08 22:57:41 swai noship $ */
3 -- Start of Comments
4 -- Package name : CSD_LOGISTICS_CUHK
5 -- Purpose : User hook procedures for the logistics processing.
6 -- History : Mar-20-2011 subhat created
7 -- NOTE :
8 -- End of Comments
9 /****************************************************************************************/
10 /* Procedure: service_item */
11 /* Description: This is the user hook procedure. The call will be made to derice the */
12 /* service warranty. The procedure gets order line id and repair line id */
13 /* as parameters. When implemented this should return a non null value for */
14 /* for the service item. The service item must be valid inventory item. */
15 /****************************************************************************************/
16 PROCEDURE service_item
17 (p_order_line_id IN NUMBER,
18 p_repair_line_id IN NUMBER,
19 x_return_status OUT NOCOPY VARCHAR2,
20 x_msg_data OUT NOCOPY VARCHAR2,
21 x_msg_count OUT NOCOPY NUMBER,
22 x_service_item_id OUT NOCOPY NUMBER
23 ) IS
24
25 BEGIN
26
27 NULL;
28
29 END service_item;
30
31 /****************************************************************************************/
32 /* Procedure: source_parts */
33 /* Description: This is a user hook procedure and is called when the Request Parts */
34 /* button is clicked in the High Volume Repair UI. The API receives the */
35 /* table of details of the selected records from the UI. If one chooses to */
36 /* implement this, they would need to use this and populate the corresponding*/
37 /* out data structures. One caution to be exercised is that the order of the*/
38 /* out table should match the in table. For example if p_item_id(1) = item1 */
39 /* p_item_id(2)=item2 and p_item_id(3)=item3. Then the out table x_item_id */
40 /* should be like x_item_id = item1, x_item_id(2)=item2 anx x_item_id(3)= */
41 /* item3. In case for a particular index the in table item_id and out table */
42 /* item_id doesn't match, then the request parts program will interpret that*/
43 /* as an item substitution. If the end user implements this user hook they */
44 /* have to set x_user_custom_sourcing = 'Y'. The type of requisition can be */
45 /* specified using the x_requisition_type data structure. The possible values*/
46 /* are I for internal and V for vendor based requisitions. Even if the */
47 /* custom sourcing is applicable to only subset of the passed in data, the */
48 /* out tables have to be populated with the input values. For eg. If there */
49 /* are 2 records, and the custom sourcing would apply for 1st only, then the*/
50 /* second index of the table needs to have the values copied from the second*/
51 /* index of the input table. */
52 /****************************************************************************************/
53
54 PROCEDURE source_parts
55 (p_repair_line_id IN NUMBER,
56 p_wip_entity_id IN JTF_NUMBER_TABLE,
57 p_item_id IN JTF_NUMBER_TABLE,
58 p_quantity IN JTF_NUMBER_TABLE,
59 p_requesting_org IN NUMBER,
60 p_op_seq_num IN JTF_NUMBER_TABLE,
61 x_use_custom_sourcing OUT NOCOPY BOOLEAN,
62 x_wip_entity_id OUT NOCOPY JTF_NUMBER_TABLE,
63 x_item_id OUT NOCOPY JTF_NUMBER_TABLE,
64 x_item_desc OUT NOCOPY JTF_VARCHAR2_TABLE_100,
65 x_uom_code OUT NOCOPY JTF_VARCHAR2_TABLE_100,
66 x_quantity OUT NOCOPY JTF_NUMBER_TABLE,
67 x_source_org_id OUT NOCOPY JTF_NUMBER_TABLE,
68 x_source_subinventory OUT NOCOPY JTF_VARCHAR2_TABLE_100,
69 x_op_seq_num OUT NOCOPY JTF_NUMBER_TABLE,
70 x_requisition_type OUT NOCOPY JTF_VARCHAR2_TABLE_100,
71 x_return_status OUT NOCOPY VARCHAR2,
72 x_msg_data OUT NOCOPY VARCHAR2,
73 x_msg_count OUT NOCOPY NUMBER
74 )IS
75
76 BEGIN
77
78 NULL;
79
80 END source_parts;
81
82 END CSD_LOGISTICS_CUHK;
[Home] [Help]