EP_LOAD_ITEM And EP_LOAD_LOCATION Procedures Fail (Doc ID 1629083.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Demantra Demand Management - Version and later
Information in this document applies to any platform.


On : version, DM-Gen

ep_load_item and ep_load_locations procedures fail because the column dm_item_code in t_src_item_templ has been used for two different Demantra objects; item (t_ep_item) & i_att_1 (t_ep_i_att_1). As a result the procedures are generating duplicate declarations, eg; in ep_load_items;

vs_dm_item_code VARCHAR2(500);
  vs_dm_item_code VARCHAR2(500);
  vs_p_dm_item_code VARCHAR2(500) := NULL;
  vs_p_dm_item_code VARCHAR2(500) := NULL;

  vs_sql := 'SELECT DISTINCT

  FETCH rec_load INTO

The issue can be reproduced at will with the following steps:
1. Run ep_load_item and ep_load_locations procedures



Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms