[Home] [Help]
360: begin
361: select 1
362: into l_temp
363: from MTL_PARAMETERS MP ,
364: WSM_PARAMETERS WSM,
365: HR_ALL_ORGANIZATION_UNITS ORG,
366: WIP_PARAMETERS WP
367: where MP.ORGANIZATION_ID = WSM.ORGANIZATION_ID
368: and ORG.ORGANIZATION_ID = WSM.ORGANIZATION_ID
735:
736: l_stmt_num := 40;
737: select nvl(OP_SEQ_NUM_INCREMENT, 10)
738: into l_op_seq_incr
739: from wsm_parameters
740: where ORGANIZATION_ID = p_org;
741:
742: l_job_seq_num := 0;
743:
1710: end if;
1711:
1712: select nvl(OP_SEQ_NUM_INCREMENT, 10)
1713: into l_op_seq_incr
1714: from wsm_parameters
1715: where ORGANIZATION_ID = p_organization_id;
1716:
1717:
1718: l_stat_num := 10;
2565: -- kanban size. E.g. Say kanba size is 20. User chooses an inv lot of quantity 1000, component per
2566: -- is 2, i.e. a work order is generated for 500. If this api returns 1, the work order will be
2567: -- generated for 20 only.
2568: -- Ideally, the option to specify a value for this parameter should be provided when the user creates
2569: -- a pull sequence. For DM_FP I user will see this as an option on wsm parameters screen. Thus of all
2570: -- the parameters passed to the api, only the organization id will be used to query wsm_parameters.
2571:
2572: function honor_kanban_size (
2573: p_org_id IN NUMBER,
2566: -- is 2, i.e. a work order is generated for 500. If this api returns 1, the work order will be
2567: -- generated for 20 only.
2568: -- Ideally, the option to specify a value for this parameter should be provided when the user creates
2569: -- a pull sequence. For DM_FP I user will see this as an option on wsm parameters screen. Thus of all
2570: -- the parameters passed to the api, only the organization id will be used to query wsm_parameters.
2571:
2572: function honor_kanban_size (
2573: p_org_id IN NUMBER,
2574: p_item_id IN NUMBER,
2580: begin
2581:
2582: select honor_kanban_size
2583: into l_hon_kanban_size
2584: from wsm_parameters
2585: where organization_id = p_org_id;
2586:
2587: if l_hon_kanban_size is null then
2588: return 2;