[Home] [Help]
411: f_demand_type number_idx_tbl;
412: d_origination_type number_idx_tbl;
413: f_origination_type number_idx_tbl;
414:
415: TYPE demand_schedule IS TABLE OF msc_st_demands.demand_schedule_name%TYPE
416: INDEX BY BINARY_INTEGER;
417: empty_demand_schedule demand_schedule;
418: d_demand_schedule demand_schedule;
419: f_demand_schedule demand_schedule;
417: empty_demand_schedule demand_schedule;
418: d_demand_schedule demand_schedule;
419: f_demand_schedule demand_schedule;
420:
421: TYPE dorder_number IS TABLE OF msc_st_demands.order_number%TYPE INDEX BY BINARY_INTEGER;
422: empty_dorder_number dorder_number ;
423: d_order_number dorder_number ;
424: f_order_number dorder_number ;
425:
422: empty_dorder_number dorder_number ;
423: d_order_number dorder_number ;
424: f_order_number dorder_number ;
425:
426: TYPE dwip_entity_name IS TABLE OF msc_st_demands.wip_entity_name%TYPE INDEX BY BINARY_INTEGER;
427: empty_dwip_entity_name dwip_entity_name ;
428: d_wip_entity_name dwip_entity_name ;
429: f_wip_entity_name dwip_entity_name ;
430:
433:
434: d_request_date date_idx_tbl;
435: f_request_date date_idx_tbl;
436:
437: TYPE forecast_designator IS TABLE OF msc_st_demands.forecast_designator%TYPE
438: INDEX BY BINARY_INTEGER;
439: f_forecast_designator forecast_designator ;
440:
441: f_sales_order_line_id number_idx_tbl;
794: * activity is Changed
795: * Sridhar 31-MAR-2003 B2882286 Ensuring the Order so that if the last batch
796: * resource requirements are written
797: * Sridhar 30-APR-2003 B2919303 Added Operation Seq Number in msc_st_supplies
798: * and in msc_st_demands table
799: * Sridhar 09-MAY-2003 B2919303 Added line_no and included in order by clause
800: * Sridhar 12-MAY-2003 B2953953 Populated BY_PRODUCT_USING_ASSY_ID with
801: * product_line which is the assembly_item_id
802: * Navin 21-APR-2003 B3577871 ST:OSFME2: collections failing in planning data pull.
2548: i := 1 ;
2549: log_message(d_organization_id.FIRST || '*' || d_index || '*' || d_organization_id.LAST );
2550: IF d_organization_id.FIRST > 0 THEN
2551: FORALL i IN d_organization_id.FIRST..d_organization_id.LAST
2552: INSERT INTO msc_st_demands (
2553: organization_id,
2554: inventory_item_id,
2555: sr_instance_id,
2556: using_assembly_item_id,
3209: * insert_demands
3210: *
3211: * DESCRIPTION
3212: * This procedure will take the parameter values and insert a row into
3213: * the table msc_st_demands
3214: * HISTORY
3215: * M Craig
3216: * 10/13/99 - Added deleted_flag in the insert statement
3217: * P Dong
3281: INTO t_order_number, t_wip_entity_name
3282: FROM dual ;
3283:
3284: statement_demands :=
3285: ' INSERT INTO msc_st_demands ( '
3286: ||' organization_id, inventory_item_id, sr_instance_id, '
3287: ||' using_assembly_item_id, using_assembly_demand_date, '
3288: ||' using_requirement_quantity, demand_type, origination_type, '
3289: ||' wip_entity_id, demand_schedule_name, order_number, '
3312: pbatchstep_no, /* B2919303 */
3313: 2 ;
3314: EXCEPTION
3315: WHEN OTHERS THEN
3316: log_message('Failure occured during the insert into msc_st_demands');
3317: log_message(sqlerrm);
3318: RAISE;
3319: END;
3320:
3679: * NAME
3680: * extract_inv_transfer_demands
3681: *
3682: * DESCRIPTION
3683: * This procedure will insert records into the table msc_st_demands
3684: * According to APS team (Sam Tupe < prganesh Shah etc.
3685: * The inventory transfer demand is similar to Internal Sales Order
3686: * demand hence should be added to each of the demand schedule
3687: * The specifics are
3713: pdoc_type := 'XFER';
3714:
3715: return_status := TRUE ;
3716:
3717: v_sql_stmt := 'INSERT into msc_st_demands ('
3718: || ' organization_id,'
3719: || ' inventory_item_id,'
3720: || ' sr_instance_id,'
3721: || ' using_assembly_item_id,'
3774: * Extract_inventory_transfer_supplies
3775: *
3776: * DESCRIPTION
3777: * This procedure will insert records into the table msc_st_supplies
3778: * and msc_st_demands for pending inventory transfers.
3779: * HISTORY
3780: * 25-Jan-2003 B1332662 Created New procedure to insert supplies
3781: * Per discussions with APS team the specifics are
3782: * Order_type = 2
4026: * This procedure is a wrapper for the preexisting sales_forecast procedure.
4027: * This version is set up with the proper parameters to be called as from the
4028: * concurrent manager. In addition, the main difference is the table into
4029: * which demands are inserted. The standard procedure inserts into
4030: * msc_st_demands.
4031: * This new procedure inserts into gmp_demands_api. The difference between
4032: * the two tables is the addition of a schedule_id column in
4033: * gmp_demands_api. Also, this version of sales_forecast begins by
4034: * truncating gmp_demands_api and leaves it populated after
4031: * This new procedure inserts into gmp_demands_api. The difference between
4032: * the two tables is the addition of a schedule_id column in
4033: * gmp_demands_api. Also, this version of sales_forecast begins by
4034: * truncating gmp_demands_api and leaves it populated after
4035: * it completes. By contrast, msc_st_demands (which is an APS staging table)
4036: * is immediately truncated after APS reads its data. This difference allows
4037: * gmp_demands_api to be a general purpose version of msc_st_demands.
4038: *
4039: * HISTORY
4033: * gmp_demands_api. Also, this version of sales_forecast begins by
4034: * truncating gmp_demands_api and leaves it populated after
4035: * it completes. By contrast, msc_st_demands (which is an APS staging table)
4036: * is immediately truncated after APS reads its data. This difference allows
4037: * gmp_demands_api to be a general purpose version of msc_st_demands.
4038: *
4039: * HISTORY
4040: * P. Dong
4041: * 09/14/01 - Created
4087: *
4088: * DESCRIPTION
4089: * This procedure will retrieve all of the sales order lines and forecast
4090: * details for their respective schedules. The forecast will be consumed
4091: * and the all of the rows will be written to msc_st_demands. Each demand
4092: * is applied to an MDS aka designator.
4093: * HISTORY
4094: * M Craig
4095: * 10/13/99 - Sridhar Added Designator Type column in the insert statement
4642: ||' :p11, :p12, :p13, '
4643: ||' :p14,:p15,:p16 ) ';
4644:
4645: l_demands_stmt :=
4646: ' INSERT INTO msc_st_demands ( '
4647: ||' organization_id, inventory_item_id, sr_instance_id, '
4648: ||' using_assembly_item_id, using_assembly_demand_date, '
4649: ||' using_requirement_quantity,demand_class,bucket_type, '
4650: ||' demand_type, origination_type, wip_entity_id, '
4922: i := 1 ;
4923: log_message(f_organization_id.FIRST || ' *forecast*' || f_organization_id.LAST );
4924: IF f_organization_id.FIRST > 0 THEN
4925: FORALL i IN f_organization_id.FIRST..f_organization_id.LAST
4926: INSERT INTO msc_st_demands (
4927: organization_id,
4928: inventory_item_id,
4929: sr_instance_id,
4930: using_assembly_item_id,
5384: * HISTORY
5385: * Created By : Rajesh Patangya
5386: * P Dong
5387: * 09/14/01 - Added api_mode to pass to insert_demands
5388: * 05/21/03 - B2971996 - Populating request_date in msc_st_demands table
5389: ************************************************************************/
5390: PROCEDURE write_this_so(pcounter IN NUMBER,
5391: sapi_mode IN BOOLEAN)
5392: AS
5431: ELSE
5432: BEGIN
5433:
5434: statement_demands :=
5435: ' INSERT INTO msc_st_demands ( '
5436: ||' organization_id, inventory_item_id, sr_instance_id, '
5437: ||' using_assembly_item_id, using_assembly_demand_date, '
5438: ||' using_requirement_quantity, demand_type, origination_type, '
5439: ||' wip_entity_id, demand_schedule_name, order_number, '
5534: END;
5535: ELSE
5536: BEGIN
5537: statement_demands :=
5538: ' INSERT INTO msc_st_demands ( '
5539: ||' organization_id, inventory_item_id, sr_instance_id, '
5540: ||' using_assembly_item_id, using_assembly_demand_date, '
5541: ||' using_requirement_quantity, demand_type, origination_type, '
5542: ||' wip_entity_id, demand_schedule_name, order_number, '