The following lines contain the word 'select', 'insert', 'update' or 'delete':
inserting the rows into wip_flow_schedules. It allows the user
to customize the filtering of the demand to be inserted into
wip_flow_schedules. This is called before the scheduling engine
is invoked.
IN Parameter :
- p_rule_id : the scheduling rule id
- p_line_id : the production line identifier
- p_org_id : the organization id
- p_demand_type : to identify the demand type.
2 for sales order, 100 for planned order
- p_demand_id : the identifier for demand.
For sales order, p_demand_id = sales order line id in oe_order_lines_all
For planned order, p_demand_id = transaction_id in mrp_recommendations
OUT Parameter :
- p_valid_demand : the demand will be inserted into wip_flow_schedules
if the p_valid_demand is TRUE. Otherwise it will be ignored.
*/
PROCEDURE Is_Valid_Demand (
p_api_version_number IN NUMBER,
p_rule_id IN NUMBER,
p_line_id IN NUMBER,
p_org_id IN NUMBER,
p_demand_type IN NUMBER,
p_demand_id IN NUMBER,
p_valid_demand OUT NOCOPY BOOLEAN,
x_return_status OUT NOCOPY VARCHAR2,
x_msg_count OUT NOCOPY NUMBER,
x_msg_data OUT NOCOPY VARCHAR2) IS
l_api_version_number CONSTANT NUMBER := 1.0;