[Home] [Help]
1089: d_origination_type pls_idx_tbl ;
1090: f_origination_type pls_idx_tbl ;
1091: /* akaruppa B5007729 End*/
1092:
1093: TYPE demand_schedule IS TABLE OF msc_st_demands.demand_schedule_name%TYPE
1094: INDEX BY BINARY_INTEGER;
1095: d_demand_schedule demand_schedule;
1096: f_demand_schedule demand_schedule;
1097: e_demand_schedule demand_schedule;/* akaruppa B5007729 */
1095: d_demand_schedule demand_schedule;
1096: f_demand_schedule demand_schedule;
1097: e_demand_schedule demand_schedule;/* akaruppa B5007729 */
1098:
1099: TYPE dorder_number IS TABLE OF msc_st_demands.order_number%TYPE INDEX BY BINARY_INTEGER;
1100: d_order_number dorder_number ;
1101: f_order_number dorder_number ;
1102: e_order_number dorder_number ;/* akaruppa B5007729 */
1103:
1100: d_order_number dorder_number ;
1101: f_order_number dorder_number ;
1102: e_order_number dorder_number ;/* akaruppa B5007729 */
1103:
1104: TYPE dwip_entity_name IS TABLE OF msc_st_demands.wip_entity_name%TYPE INDEX BY BINARY_INTEGER;
1105: d_wip_entity_name dwip_entity_name ;
1106: f_wip_entity_name dwip_entity_name ;
1107: e_wip_entity_name dwip_entity_name ;/* akaruppa B5007729 */
1108:
1112:
1113: d_request_date date_idx_tbl ;
1114: f_request_date date_idx_tbl ;
1115:
1116: TYPE forecast_designator IS TABLE OF msc_st_demands.forecast_designator%TYPE
1117: INDEX BY BINARY_INTEGER;
1118: f_forecast_designator forecast_designator ;
1119: e_forecast_designator forecast_designator ;/* akaruppa B5007729 */
1120:
8460: * activity is Changed
8461: * Sridhar 31-MAR-2003 B2882286 Ensuring the Order so that if the last batch
8462: * resource requirements are written
8463: * Sridhar 30-APR-2003 B2919303 Added Operation Seq Number in msc_st_supplies
8464: * and in msc_st_demands table
8465: * Sridhar 09-MAY-2003 B2919303 Added line_no and included in order by clause
8466: * Sridhar 12-MAY-2003 B2953953 Populated BY_PRODUCT_USING_ASSY_ID with
8467: * product_line which is the assembly_item_id
8468: * Navin 21-APR-2003 B3577871 ST:OSFME2: collections failing in planning data pull.
10100: i := 1 ;
10101: log_message(d_organization_id.FIRST || '*' || d_index || '*' || d_organization_id.LAST );
10102: IF d_organization_id.FIRST > 0 THEN
10103: FORALL i IN d_organization_id.FIRST..d_organization_id.LAST
10104: INSERT INTO msc_st_demands (
10105: organization_id,
10106: inventory_item_id,
10107: sr_instance_id,
10108: using_assembly_item_id,
10768: * insert_demands
10769: *
10770: * DESCRIPTION
10771: * This procedure will take the parameter values and insert a row into
10772: * the table msc_st_demands
10773: * HISTORY
10774: * M Craig
10775: * 10/13/99 - Added deleted_flag in the insert statement
10776: * P Dong
10840: INTO t_order_number, t_wip_entity_name
10841: FROM dual ;
10842:
10843: statement_demands :=
10844: ' INSERT INTO msc_st_demands ( '
10845: ||' organization_id, inventory_item_id, sr_instance_id, '
10846: ||' using_assembly_item_id, using_assembly_demand_date, '
10847: ||' using_requirement_quantity, demand_type, origination_type, '
10848: ||' wip_entity_id, demand_schedule_name, order_number, '
10871: pbatchstep_no, /* B2919303 */
10872: 2 ;
10873: EXCEPTION
10874: WHEN OTHERS THEN
10875: log_message('Failure occured during the insert into msc_st_demands');
10876: log_message(sqlerrm);
10877: RAISE;
10878: END;
10879:
11457: * NAME
11458: * extract_inv_transfer_demands
11459: *
11460: * DESCRIPTION
11461: * This procedure will insert records into the table msc_st_demands
11462: * According to APS team (Sam Tupe < prganesh Shah etc.
11463: * The inventory transfer demand is similar to Internal Sales Order
11464: * demand hence should be added to each of the demand schedule
11465: * The specifics are
11505: pdescription := 'OPM Inventory Transfer Demands' ;
11506:
11507: return_status := TRUE ;
11508:
11509: v_sql_stmt := 'INSERT into msc_st_demands ('
11510: || ' organization_id,'
11511: || ' inventory_item_id,'
11512: || ' sr_instance_id,'
11513: || ' using_assembly_item_id,'
11640: * Extract_inventory_transfer_supplies
11641: *
11642: * DESCRIPTION
11643: * This procedure will insert records into the table msc_st_supplies
11644: * and msc_st_demands for pending inventory transfers.
11645: * HISTORY
11646: * 25-Jan-2003 B1332662 Created New procedure to insert supplies
11647: * Per discussions with APS team the specifics are
11648: * Order_type = 2
11905: * This procedure is a wrapper for the preexisting sales_forecast procedure.
11906: * This version is set up with the proper parameters to be called as from the
11907: * concurrent manager. In addition, the main difference is the table into
11908: * which demands are inserted. The standard procedure inserts into
11909: * msc_st_demands.
11910: * This new procedure inserts into gmp_demands_api. The difference between
11911: * the two tables is the addition of a schedule_id column in
11912: * gmp_demands_api. Also, this version of sales_forecast begins by
11913: * truncating gmp_demands_api and leaves it populated after
11910: * This new procedure inserts into gmp_demands_api. The difference between
11911: * the two tables is the addition of a schedule_id column in
11912: * gmp_demands_api. Also, this version of sales_forecast begins by
11913: * truncating gmp_demands_api and leaves it populated after
11914: * it completes. By contrast, msc_st_demands (which is an APS staging table)
11915: * is immediately truncated after APS reads its data. This difference allows
11916: * gmp_demands_api to be a general purpose version of msc_st_demands.
11917: *
11918: * HISTORY
11912: * gmp_demands_api. Also, this version of sales_forecast begins by
11913: * truncating gmp_demands_api and leaves it populated after
11914: * it completes. By contrast, msc_st_demands (which is an APS staging table)
11915: * is immediately truncated after APS reads its data. This difference allows
11916: * gmp_demands_api to be a general purpose version of msc_st_demands.
11917: *
11918: * HISTORY
11919: * P. Dong
11920: * 09/14/01 - Created
11966: *
11967: * DESCRIPTION
11968: * This procedure will retrieve all of the sales order lines and forecast
11969: * details for their respective schedules. The forecast will be consumed
11970: * and the all of the rows will be written to msc_st_demands. Each demand
11971: * is applied to an MDS aka designator.
11972: * HISTORY
11973: * M Craig
11974: * 10/13/99 - Sridhar Added Designator Type column in the insert statement
13107: ||' :p11, :p12, :p13, '
13108: ||' :p14,:p15,:p16 ) ';
13109:
13110: l_demands_stmt :=
13111: ' INSERT INTO msc_st_demands ( '
13112: ||' organization_id, inventory_item_id, sr_instance_id, '
13113: ||' using_assembly_item_id, using_assembly_demand_date, '
13114: ||' using_requirement_quantity,demand_class,bucket_type, '
13115: ||' demand_type, origination_type, wip_entity_id, '
13394: i := 1 ;
13395: log_message(f_organization_id.FIRST || ' *forecast*' || f_organization_id.LAST );
13396: IF f_organization_id.FIRST > 0 THEN
13397: FORALL i IN f_organization_id.FIRST..f_organization_id.LAST
13398: INSERT INTO msc_st_demands (
13399: organization_id,
13400: inventory_item_id,
13401: sr_instance_id,
13402: using_assembly_item_id,
13873: * HISTORY
13874: * Created By : Rajesh Patangya
13875: * P Dong
13876: * 09/14/01 - Added api_mode to pass to insert_demands
13877: * 05/21/03 - B2971996 - Populating request_date in msc_st_demands table
13878: ************************************************************************/
13879: PROCEDURE write_this_so(pcounter IN NUMBER,
13880: sapi_mode IN BOOLEAN)
13881: AS
13922: ELSE
13923: BEGIN
13924:
13925: statement_demands :=
13926: ' INSERT INTO msc_st_demands ( '
13927: ||' organization_id, inventory_item_id, sr_instance_id, '
13928: ||' using_assembly_item_id, using_assembly_demand_date, '
13929: ||' using_requirement_quantity, demand_type, origination_type, '
13930: ||' wip_entity_id, demand_schedule_name, order_number, '
14026: END;
14027: ELSE
14028: BEGIN
14029: statement_demands :=
14030: ' INSERT INTO msc_st_demands ( '
14031: ||' organization_id, inventory_item_id, sr_instance_id, '
14032: ||' using_assembly_item_id, using_assembly_demand_date, '
14033: ||' using_requirement_quantity, demand_type, origination_type, '
14034: ||' wip_entity_id, demand_schedule_name, order_number, '