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.WMS_XDOCK_CUSTOM_APIS_PUB dependencies on WSH_PR_CRITERIA

Line 54: (p_wdd_release_record IN WSH_PR_CRITERIA.relRecTyp,

50: -- this will be interpreted as 'Not Implemented'. The pegging logic will then call the rules
51: -- engine to determine a valid crossdock criteria instead.
52: --
53: PROCEDURE Get_Crossdock_Criteria
54: (p_wdd_release_record IN WSH_PR_CRITERIA.relRecTyp,
55: x_return_status OUT NOCOPY VARCHAR2,
56: x_msg_count OUT NOCOPY NUMBER,
57: x_msg_data OUT NOCOPY VARCHAR2,
58: x_api_is_implemented OUT NOCOPY BOOLEAN,

Line 325: (p_wdd_release_record IN WSH_PR_CRITERIA.relRecTyp,

321: -- never have more. Additionally, (very important!!!) there should not be multiple entries
322: -- in x_sorted_order_tb pointing to the same index value. If an invalid sorted order table
323: -- is returned, the custom logic will not be used to sort the shopping basket table.
324: PROCEDURE Sort_Supply_Lines
325: (p_wdd_release_record IN WSH_PR_CRITERIA.relRecTyp,
326: p_prioritize_documents IN NUMBER,
327: p_shopping_basket_tb IN WMS_XDock_Pegging_Pub.shopping_basket_tb,
328: x_return_status OUT NOCOPY VARCHAR2,
329: x_msg_count OUT NOCOPY NUMBER,