This appendix provides information about the Flow Manufacturing client extensions.
This appendix covers the following topics:
Calculates kanban size and quantity.
Package Name: MRP_PUB_KANBAN_QTY_CAL
Procedure Name: CALCULATE_KANBAN_QUANTITY
Custom Kanban Quantity Calculation enables the extension of Kanban Quantity Calculation to suit the need of different business requirements. The Kanban planning engine will use the resulting kanban quantity and size returned by this client extension. The table below provides the specifications:
Parameter | Usage | Type | Required | Derived | Optional |
---|---|---|---|---|---|
p_version_number | IN | NUMBER | x | - | - |
p_average_demand | IN | NUMBER | x | - | - |
p_minimum_order_quantity | IN | NUMBER | x | - | - |
p_fixed_lot_multilier | IN | NUMBER | x | - | - |
p_safety_stock_days | IN | NUMBER | x | - | - |
p_replenishment_lead_time | IN | NUMBER | x | - | - |
p_kanban_flag | IN | NUMBER | x | - | - |
p_kanban_size | IN/OUT | NUMBER | - | - | - |
p_kanban_number | IN/OUT | NUMBER | - | - | - |
p_return_status | OUT | VARCHAR2 | - | - | - |
The Custom Schedule enables you to extend the line scheduling algorithms that are seeded with the product.
Package Name: MRP_CUSTOM_LINE_SCHEDULE
Procedure Name: CUSTOM_SCHEDULE
The Custom Schedule enables the extension of the Line Scheduling algorithm to suit the need of different business requirements. The following table provide specifications:
Parameter | Usage | Type | Required | Derived | Optional |
---|---|---|---|---|---|
p_api_version_number | IN | NUMBER | x | - | - |
p_rule_id | IN | NUMBER | x | - | - |
p_line_id | IN | NUMBER | x | - | - |
p_org_id | IN | NUMBER | x | - | - |
p_flex_tolerance | IN | NUMBER | x | - | - |
p_scheduling_start_date | IN | DATE | x | - | - |
p_scheduling_end_date | IN | DATE | x | - | - |
x_return_status | OUT | VARCHAR2 | - | - | - |
x_msg_count | OUT | NUMBER | - | - | - |
x_msg_data | OUT | VARCHAR2 | - | - | - |
Selected flow schedules are converted to flow schedules before calling the scheduling and sequencing procedure. All rows that are to be sequenced or scheduled in this call are contained in the table wip_flow_schedules. All of these rows have the column Request_id set to USERENV('SESSIONID'). The procedure should operate on these rows, sequence and schedule them based on user defined algorithms, and update the rows in the flow schedule table.
New rows that are created should have the following columns populated.
wip_entity_id
Scheduled_flag
Inventory_item_id
Organization_id
Line_id
Last_update_date
Last_update_by
Creation_date
Created_by
Class_code
Planned_quantity
Quantity_completed
Scheduled_start_date
Scheduled_completion_date
Status
Schedule_number
The calling functions set a save point, before a call to the Custom Schedule. In case of a failure message from this procedure, the program will rollback to the save point and return an error message to the calling routines.
Package Name: MRP_CUSTOM_LINE_SCHEDULE
Procedure Name: IS_VALID_DEMAND
This procedure is being called from Line Scheduling Workbench before inserting the rows into wip_flow_schedule. 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.
Parameter | Usage | Type | Required | Derived | Optional |
---|---|---|---|---|---|
p_api_version_number | IN | NUMBER | x | - | - |
p_rule_id | IN | NUMBER | x | - | - |
p_line_id | IN | NUMBER | x | - | - |
p_org_id | IN | NUMBER | x | - | - |
p_demand_type | IN | NUMBER | x | - | - |
p_demand_id | IN | NUMBER | x | - | - |
p_valid_demand | OUT | BOOLEAN | - | - | - |
x_return_status | OUT | VARCHAR2 | - | - | - |
x_msg_count | OUT | NUMBER | - | - | - |
x_msg_data | OUT | VARCHAR2 | - | - | - |
p_demand_type
To identify the demand type. 2 for sales order, 100 for planned order.
p_demand_id
The identifier for the 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.
p_valid_demand
The demand will be inserted into wip_flow_schedules, if the p_valid_demand is TRUE, otherwise it will be ignored.
The Flow Sequencing Customization and Extension is used by Flow Sequencing.
Package Name: FLM_SEQ_CUSTOM
Procedure Name: GET_ATTRIBUTE_VALUE
The Flow Sequencing Customization and Extension enables the extension of all seeded attribute types to suit the need of different business requirements. The Sequencing engine uses the resulted attribute value returned by this client extension. There are three different types of customized attributes: Item, Sales Order and Planned Order.
Parameter | Usage | Type | Required | Derived | Optional |
---|---|---|---|---|---|
p_api_version_number | IN | NUMBER | Y | - | - |
p_org_id | IN | NUMBER | Y | - | - |
p_id | IN | NUMBER | Y | - | - |
p_attribute_id | IN | NUMBER | Y | - | - |
p_attribute_type | IN | NUMBER | Y | - | - |
p_other_id | IN | NUMBER | - | - | Y |
p_other_name | IN | VARCHAR2 | - | - | Y |
x_value_num | OUT | NUMBER | - | - | - |
x_value_name | OUT | VARCHAR2 | - | - | - |
x_return_status | OUT | VARCHAR2 | - | - | - |
x_msg_count | OUT | NUMBER | - | - | - |
x_msg_data | OUT | VARCHAR2 | - | - | - |
p_id
Values passed depending on the type of the customized attributes:
Item attribute, p_id = inventory_id from MTL_SYSTEM_ITEMS table
Sales Order attribute, p_id = line_id from OE_ORDER_LINES_ALL table
Planned Order attribute, p_id = transaction_id from MRP_RECOMMENDATIONS table
p_attribute_type
Attribute Type. Value passed depending on the type of the customized attributes:
Item attribute, p_attribute_type = 11
Sales Order attribute, p_attribute_type = 12
Planned Order attribute, p_attribute_type = 13
x_value_num
Return attribute value of type number or date. The Julian number is returned for date type.
Package Name: FLM_SEQ_CUSTOM
Procedure Name: NAME: POST_PROCESS_DEMAND
This procedure provides post-process demands for a task. The demands for a specific sequencing run are stored in FLM_SEQ_TASK_DEMANDS table identified by seq_task_id. The sequencing engine uses the demands stored to create flow schedules. To modify the demands, the API needs to either modify the quantity values (to increase or decrease demand), or delete the row (to remove the demand).
Parameter | Usage | Type | Required | Derived | Optional |
---|---|---|---|---|---|
p_api_version_number | IN | NUMBER | Y | - | - |
p_seq_task_id | IN | NUMBER | Y | - | - |
x_return_status | OUT | VARCHAR2 | - | - | - |
x_msg_count | OUT | NUMBER | - | - | - |
x_msg_data | OUT | VARCHAR2 | - | - | - |
The Flow Execution Workstation Customization and Extension is used by the Flow Execution Workstation.
Package Name: FLM_EXECUTION_UTIL
Procedure Name: GET_ATTRIBUTES
The procedure retrieves the information to display on the custom Property region of the Flow Execution Workstation, providing additional information for completing the work at a particular line operation or event. As an input parameter, the procedure takes wip_entity_id, operation sequence id, and operation type (line operation or event). This indicates the operation displaying the information. It returns a table of name value pairs to be rendered on custom Property region of Flow Execution Workstation.
Parameter | Usage | Type | Required | Derived | Optional |
---|---|---|---|---|---|
p_api_version_number | IN | NUMBER | Y | - | - |
p_wip_entity_id | IN | NUMBER | Y | - | - |
p_op_seq_id | IN | NUMBER | Y | - | - |
p_op_type | IN | NUMBER | Y | - | - |
p_cust_attrib_tab | OUT | FLM_CUST_ATTRIBUTE_TBL | - | - | - |
x_return_status | OUT | VARCHAR2 | - | - | - |
x_msg_count | OUT | NUMBER | - | - | - |
x_msg_data | OUT | VARCHAR2 | - | - | - |
p_op_seq_id
Operation Sequence ID of this operation/event
p_op_type
Operation Type: 1=Event, 2=Process, 3=Line Operation
p_cust_attrib_tab
PL/SQL table to keep attributes. The table is based on record type FLM_CUST_ATTRIBUTE
x_msg_data
Standard Oracle API output parameter
Parameter | Type |
---|---|
attribute_name | VARCHAR2(240) |
attribute_value | VARCHAR2(2000) |