5:
6: -- this is to workaround the JDBC bug regarding IN DATE of value GMiss
7: function rosetta_g_miss_date_in_map(d date) return date as
8: begin
9: if d = rosetta_g_mistake_date then return fnd_api.g_miss_date; end if;
10: return d;
11: end;
12:
13: function rosetta_g_miss_num_map(n number) return number as
10: return d;
11: end;
12:
13: function rosetta_g_miss_num_map(n number) return number as
14: a number := fnd_api.g_miss_num;
15: b number := 0-1962.0724;
16: begin
17: if n=a then return b; end if;
18: if n=b then return a; end if;
104: , x_msg_data out nocopy VARCHAR2
105: , x_return_status out nocopy VARCHAR2
106: , x_choice_id out nocopy NUMBER
107: , p3_a0 NUMBER := 0-1962.0724
108: , p3_a1 VARCHAR2 := fnd_api.g_miss_char
109: , p3_a2 NUMBER := 0-1962.0724
110: , p3_a3 NUMBER := 0-1962.0724
111: , p3_a4 VARCHAR2 := fnd_api.g_miss_char
112: , p3_a5 VARCHAR2 := fnd_api.g_miss_char
107: , p3_a0 NUMBER := 0-1962.0724
108: , p3_a1 VARCHAR2 := fnd_api.g_miss_char
109: , p3_a2 NUMBER := 0-1962.0724
110: , p3_a3 NUMBER := 0-1962.0724
111: , p3_a4 VARCHAR2 := fnd_api.g_miss_char
112: , p3_a5 VARCHAR2 := fnd_api.g_miss_char
113: )
114:
115: as
108: , p3_a1 VARCHAR2 := fnd_api.g_miss_char
109: , p3_a2 NUMBER := 0-1962.0724
110: , p3_a3 NUMBER := 0-1962.0724
111: , p3_a4 VARCHAR2 := fnd_api.g_miss_char
112: , p3_a5 VARCHAR2 := fnd_api.g_miss_char
113: )
114:
115: as
116: ddp_one_choice cs_tp_choices_pvt.choice;
324: , x_return_status out nocopy VARCHAR2
325: , x_freetext_id out nocopy NUMBER
326: , p3_a0 NUMBER := 0-1962.0724
327: , p3_a1 NUMBER := 0-1962.0724
328: , p3_a2 VARCHAR2 := fnd_api.g_miss_char
329: , p3_a3 NUMBER := 0-1962.0724
330: , p3_a4 VARCHAR2 := fnd_api.g_miss_char
331: )
332:
326: , p3_a0 NUMBER := 0-1962.0724
327: , p3_a1 NUMBER := 0-1962.0724
328: , p3_a2 VARCHAR2 := fnd_api.g_miss_char
329: , p3_a3 NUMBER := 0-1962.0724
330: , p3_a4 VARCHAR2 := fnd_api.g_miss_char
331: )
332:
333: as
334: ddp_one_freetext cs_tp_choices_pvt.freetext;