eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.OE_DUAL_UOM_UTIL dependencies on OE_ORDER_PUB

Line 10: -- p_line_rec : The function will take OE_Order_PUB.Line_Rec_Type record

6: -- Function get_fulfillment_eligible
7: --
8: -- API to determine whether fulfillment_base should be calculated or not for current line_id
9: -- IN parameters -
10: -- p_line_rec : The function will take OE_Order_PUB.Line_Rec_Type record
11: -- containing line_id as input and return Boolean value Indicating, whether FB
12: -- on line should be calculated as per new functionality or not.
13: -- Boolean TRUE implies : Yes, calculate FB
14: -- Boolean FALSE implies : No, not eligible to calculate FB

Line 23: ( p_line_rec IN OE_Order_PUB.Line_Rec_Type ,

19: -- we use thi swuery to fetch other required parameters like primary uom of item (to be used later in derive_fulfillment_base API).
20: ---------------------------------------------------------------------
21:
22: Function get_fulfillment_eligible
23: ( p_line_rec IN OE_Order_PUB.Line_Rec_Type ,
24: p_inventory_item_rec OUT NOCOPY Inventory_Item_Rec_Type
25: ) RETURN BOOLEAN
26: IS
27:

Line 192: -- p_line_rec : The function will take OE_Order_PUB.Line_Rec_Type record contains line_id , org_id ,ship_from_org_id ,

188: --(only when new profile OM: Default Fulfillment Base is set to YES)
189: --This API will also be called from OE_Bulk_Process_Line.Populate_Internal_Fields to populate fulfillment_base
190: --column from HVOP flow (for dual uom items only when new profile OM: Default Fulfillment Base is set to YES).
191: -- IN parameters -
192: -- p_line_rec : The function will take OE_Order_PUB.Line_Rec_Type record contains line_id , org_id ,ship_from_org_id ,
193: -- inventory_item_id etc as input and return CHAR value (Null, 'P' or 'S') .
194: -- 'P' implies : Primary
195: -- 'S' implies : Secondary
196: -- Null implies: line not eligible for FB field.

Line 202: ( p_line_rec IN OE_Order_PUB.Line_Rec_Type

198: ------------------------------------------------------------------------------------------------------
199: ---It is PVT API as per FDD 3.1.3.3
200:
201: Function derive_fulfillment_base
202: ( p_line_rec IN OE_Order_PUB.Line_Rec_Type
203: ) RETURN varchar2
204: IS
205: l_fulfillment_base varchar2(1);
206: l_inventory_item_rec Inventory_Item_Rec_Type;

Line 421: -- p_line_rec : The proeudre will for validation of fulfillment_base field from OE_Order_PUB.Line_Rec_Type

417: --This api will be called from oe_line_util.apply_attribute_changes procedure when
418: -- FB on a line is changing form null/P to S or vice versa. The API will validate
419: -- if the change should be allowed on FB field...if not it will raise error
420: -- IN parameters -
421: -- p_line_rec : The proeudre will for validation of fulfillment_base field from OE_Order_PUB.Line_Rec_Type
422: ---------------------------------------------------------------------
423: PROCEDURE validate_fulfillment_base
424: ( p_line_rec IN OE_Order_PUB.Line_Rec_Type
425: )

Line 424: ( p_line_rec IN OE_Order_PUB.Line_Rec_Type

420: -- IN parameters -
421: -- p_line_rec : The proeudre will for validation of fulfillment_base field from OE_Order_PUB.Line_Rec_Type
422: ---------------------------------------------------------------------
423: PROCEDURE validate_fulfillment_base
424: ( p_line_rec IN OE_Order_PUB.Line_Rec_Type
425: )
426: IS
427: l_pick_status VARCHAR2(1);
428: l_ret_exists VARCHAR2(1);