[Home] [Help]
3249: IF api_mode
3250: THEN
3251: BEGIN
3252: statement_demands_api :=
3253: ' INSERT INTO gmp_demands_api ( '
3254: ||' organization_id, schedule_id, inventory_item_id, demand_date, '
3255: ||' demand_quantity, origination_type, doc_id, selling_price ) '
3256: ||' VALUES '
3257: ||' ( :p1, :p2, :p3, :p4, '
3268: pnet_price;
3269:
3270: EXCEPTION
3271: WHEN OTHERS THEN
3272: log_message('Failure occured during the insert into gmp_demands_api');
3273: log_message(sqlerrm);
3274: RAISE;
3275: END;
3276: ELSE
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
4035: * it completes. By contrast, msc_st_demands (which is an APS staging table)
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
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.
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
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: *
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
4057: instance => NULL,
4058: run_date => p_run_date,
4059: return_status => lv_cp_enabled );
4060:
4061: DELETE FROM gmp_demands_api;
4062:
4063: lv_cp_enabled := p_cp_enabled;
4064:
4065: sales_forecast(
5400: IF sapi_mode
5401: THEN
5402: BEGIN
5403: statement_demands_api :=
5404: ' INSERT INTO gmp_demands_api ( '
5405: ||' organization_id, schedule_id, inventory_item_id, demand_date, '
5406: ||' demand_quantity, origination_type, doc_id, selling_price ) '
5407: ||' VALUES '
5408: ||' ( :p1, :p2, :p3, :p4, '
5423: gso_cnt := pcounter + 1 ;
5424:
5425: EXCEPTION
5426: WHEN OTHERS THEN
5427: log_message('Failure occured during the insert into gmp_demands_api');
5428: log_message(sqlerrm);
5429: RAISE;
5430: END;
5431: ELSE
5504: IF fapi_mode
5505: THEN
5506: BEGIN
5507: statement_demands_api :=
5508: ' INSERT INTO gmp_demands_api ( '
5509: ||' organization_id, schedule_id, inventory_item_id, demand_date, '
5510: ||' demand_quantity, origination_type, doc_id, selling_price ) '
5511: ||' VALUES '
5512: ||' ( :p1, :p2, :p3, :p4, '
5527: gfcst_cnt := pcounter + 1 ;
5528:
5529: EXCEPTION
5530: WHEN OTHERS THEN
5531: log_message('Failure occured during the insert into gmp_demands_api');
5532: log_message(sqlerrm);
5533: RAISE;
5534: END;
5535: ELSE