[Home] [Help]
1069: d_origination_type number_idx_tbl ;
1070: f_origination_type number_idx_tbl ;
1071: /* akaruppa B5007729 End*/
1072:
1073: TYPE demand_schedule IS TABLE OF msc_st_demands.demand_schedule_name%TYPE
1074: INDEX BY BINARY_INTEGER;
1075: d_demand_schedule demand_schedule;
1076: f_demand_schedule demand_schedule;
1077: e_demand_schedule demand_schedule;/* akaruppa B5007729 */
1075: d_demand_schedule demand_schedule;
1076: f_demand_schedule demand_schedule;
1077: e_demand_schedule demand_schedule;/* akaruppa B5007729 */
1078:
1079: TYPE dorder_number IS TABLE OF msc_st_demands.order_number%TYPE INDEX BY BINARY_INTEGER;
1080: d_order_number dorder_number ;
1081: f_order_number dorder_number ;
1082: e_order_number dorder_number ;/* akaruppa B5007729 */
1083:
1080: d_order_number dorder_number ;
1081: f_order_number dorder_number ;
1082: e_order_number dorder_number ;/* akaruppa B5007729 */
1083:
1084: TYPE dwip_entity_name IS TABLE OF msc_st_demands.wip_entity_name%TYPE INDEX BY BINARY_INTEGER;
1085: d_wip_entity_name dwip_entity_name ;
1086: f_wip_entity_name dwip_entity_name ;
1087: e_wip_entity_name dwip_entity_name ;/* akaruppa B5007729 */
1088:
1092:
1093: d_request_date date_idx_tbl ;
1094: f_request_date date_idx_tbl ;
1095:
1096: TYPE forecast_designator IS TABLE OF msc_st_demands.forecast_designator%TYPE
1097: INDEX BY BINARY_INTEGER;
1098: f_forecast_designator forecast_designator ;
1099: e_forecast_designator forecast_designator ;/* akaruppa B5007729 */
1100:
7940: * activity is Changed
7941: * Sridhar 31-MAR-2003 B2882286 Ensuring the Order so that if the last batch
7942: * resource requirements are written
7943: * Sridhar 30-APR-2003 B2919303 Added Operation Seq Number in msc_st_supplies
7944: * and in msc_st_demands table
7945: * Sridhar 09-MAY-2003 B2919303 Added line_no and included in order by clause
7946: * Sridhar 12-MAY-2003 B2953953 Populated BY_PRODUCT_USING_ASSY_ID with
7947: * product_line which is the assembly_item_id
7948: * Navin 21-APR-2003 B3577871 ST:OSFME2: collections failing in planning data pull.
9476: i := 1 ;
9477: log_message(d_organization_id.FIRST || '*' || d_index || '*' || d_organization_id.LAST );
9478: IF d_organization_id.FIRST > 0 THEN
9479: FORALL i IN d_organization_id.FIRST..d_organization_id.LAST
9480: INSERT INTO msc_st_demands (
9481: organization_id,
9482: inventory_item_id,
9483: sr_instance_id,
9484: using_assembly_item_id,
10123: * insert_demands
10124: *
10125: * DESCRIPTION
10126: * This procedure will take the parameter values and insert a row into
10127: * the table msc_st_demands
10128: * HISTORY
10129: * M Craig
10130: * 10/13/99 - Added deleted_flag in the insert statement
10131: * P Dong
10195: INTO t_order_number, t_wip_entity_name
10196: FROM dual ;
10197:
10198: statement_demands :=
10199: ' INSERT INTO msc_st_demands ( '
10200: ||' organization_id, inventory_item_id, sr_instance_id, '
10201: ||' using_assembly_item_id, using_assembly_demand_date, '
10202: ||' using_requirement_quantity, demand_type, origination_type, '
10203: ||' wip_entity_id, demand_schedule_name, order_number, '
10226: pbatchstep_no, /* B2919303 */
10227: 2 ;
10228: EXCEPTION
10229: WHEN OTHERS THEN
10230: log_message('Failure occured during the insert into msc_st_demands');
10231: log_message(sqlerrm);
10232: RAISE;
10233: END;
10234:
10770: * NAME
10771: * extract_inv_transfer_demands
10772: *
10773: * DESCRIPTION
10774: * This procedure will insert records into the table msc_st_demands
10775: * According to APS team (Sam Tupe < prganesh Shah etc.
10776: * The inventory transfer demand is similar to Internal Sales Order
10777: * demand hence should be added to each of the demand schedule
10778: * The specifics are
10818: CLOSE ex_code_ref;
10819:
10820: return_status := TRUE ;
10821:
10822: v_sql_stmt := 'INSERT into msc_st_demands ('
10823: || ' organization_id,'
10824: || ' inventory_item_id,'
10825: || ' sr_instance_id,'
10826: || ' using_assembly_item_id,'
10884: * Extract_inventory_transfer_supplies
10885: *
10886: * DESCRIPTION
10887: * This procedure will insert records into the table msc_st_supplies
10888: * and msc_st_demands for pending inventory transfers.
10889: * HISTORY
10890: * 25-Jan-2003 B1332662 Created New procedure to insert supplies
10891: * Per discussions with APS team the specifics are
10892: * Order_type = 2
11155: * This procedure is a wrapper for the preexisting sales_forecast procedure.
11156: * This version is set up with the proper parameters to be called as from the
11157: * concurrent manager. In addition, the main difference is the table into
11158: * which demands are inserted. The standard procedure inserts into
11159: * msc_st_demands.
11160: * This new procedure inserts into gmp_demands_api. The difference between
11161: * the two tables is the addition of a schedule_id column in
11162: * gmp_demands_api. Also, this version of sales_forecast begins by
11163: * truncating gmp_demands_api and leaves it populated after
11160: * This new procedure inserts into gmp_demands_api. The difference between
11161: * the two tables is the addition of a schedule_id column in
11162: * gmp_demands_api. Also, this version of sales_forecast begins by
11163: * truncating gmp_demands_api and leaves it populated after
11164: * it completes. By contrast, msc_st_demands (which is an APS staging table)
11165: * is immediately truncated after APS reads its data. This difference allows
11166: * gmp_demands_api to be a general purpose version of msc_st_demands.
11167: *
11168: * HISTORY
11162: * gmp_demands_api. Also, this version of sales_forecast begins by
11163: * truncating gmp_demands_api and leaves it populated after
11164: * it completes. By contrast, msc_st_demands (which is an APS staging table)
11165: * is immediately truncated after APS reads its data. This difference allows
11166: * gmp_demands_api to be a general purpose version of msc_st_demands.
11167: *
11168: * HISTORY
11169: * P. Dong
11170: * 09/14/01 - Created
11216: *
11217: * DESCRIPTION
11218: * This procedure will retrieve all of the sales order lines and forecast
11219: * details for their respective schedules. The forecast will be consumed
11220: * and the all of the rows will be written to msc_st_demands. Each demand
11221: * is applied to an MDS aka designator.
11222: * HISTORY
11223: * M Craig
11224: * 10/13/99 - Sridhar Added Designator Type column in the insert statement
12322: ||' :p11, :p12, :p13, '
12323: ||' :p14,:p15,:p16 ) ';
12324:
12325: l_demands_stmt :=
12326: ' INSERT INTO msc_st_demands ( '
12327: ||' organization_id, inventory_item_id, sr_instance_id, '
12328: ||' using_assembly_item_id, using_assembly_demand_date, '
12329: ||' using_requirement_quantity,demand_class,bucket_type, '
12330: ||' demand_type, origination_type, wip_entity_id, '
12602: i := 1 ;
12603: log_message(f_organization_id.FIRST || ' *forecast*' || f_organization_id.LAST );
12604: IF f_organization_id.FIRST > 0 THEN
12605: FORALL i IN f_organization_id.FIRST..f_organization_id.LAST
12606: INSERT INTO msc_st_demands (
12607: organization_id,
12608: inventory_item_id,
12609: sr_instance_id,
12610: using_assembly_item_id,
13079: * HISTORY
13080: * Created By : Rajesh Patangya
13081: * P Dong
13082: * 09/14/01 - Added api_mode to pass to insert_demands
13083: * 05/21/03 - B2971996 - Populating request_date in msc_st_demands table
13084: ************************************************************************/
13085: PROCEDURE write_this_so(pcounter IN NUMBER,
13086: sapi_mode IN BOOLEAN)
13087: AS
13128: ELSE
13129: BEGIN
13130:
13131: statement_demands :=
13132: ' INSERT INTO msc_st_demands ( '
13133: ||' organization_id, inventory_item_id, sr_instance_id, '
13134: ||' using_assembly_item_id, using_assembly_demand_date, '
13135: ||' using_requirement_quantity, demand_type, origination_type, '
13136: ||' wip_entity_id, demand_schedule_name, order_number, '
13232: END;
13233: ELSE
13234: BEGIN
13235: statement_demands :=
13236: ' INSERT INTO msc_st_demands ( '
13237: ||' organization_id, inventory_item_id, sr_instance_id, '
13238: ||' using_assembly_item_id, using_assembly_demand_date, '
13239: ||' using_requirement_quantity, demand_type, origination_type, '
13240: ||' wip_entity_id, demand_schedule_name, order_number, '