0006249: Location reference cannot be used on new tables

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0006249

Openbravo ERP

00. Application dictionary

public

2008-11-28 12:05

2009-04-21 11:06

Reporter

roklenardic

Assigned To

alostale

Priority

normal

Severity

critical

Reproducibility

always

Status

closed

Resolution

fixed

Platform

OS Version

Ubuntu 8.10

Product Version

2.50alpha-r1

Target Version

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Web browser

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0006249: Location reference cannot be used on new tables

Description

When entering a new table belonging to a new module, I could not use the Location reference. After using the Create Columns from DB button, the process correctly detected the Location reference for one of the fields, however it was listed as **Location, with the two asterisks and also the compilation fails.

Steps To Reproduce

1) enter a new table into the database
CREATE TABLE bpsc_c_order
(
  bpsc_c_order_id character varying(32) NOT NULL,
  ad_client_id character varying(32) NOT NULL,
  ad_org_id character varying(32) NOT NULL,
  isactive character(1) NOT NULL DEFAULT 'Y'::bpchar,
  created timestamp without time zone NOT NULL DEFAULT now(),
  createdby character varying(32) NOT NULL,
  updated timestamp without time zone NOT NULL DEFAULT now(),
  updatedby character varying(32) NOT NULL,
  issotrx character(1) NOT NULL DEFAULT 'Y'::bpchar,
  documentno character varying(30) NOT NULL,
  c_bpartner_id character varying(32) NOT NULL,
  c_bpartner_location_id character varying(32) NOT NULL,
  CONSTRAINT bpsc_c_order_key PRIMARY KEY (bpsc_c_order_id),
  CONSTRAINT adclient_corder FOREIGN KEY (ad_client_id)
      REFERENCES ad_client (ad_client_id) MATCH SIMPLE
      ON UPDATE NO ACTION ON DELETE NO ACTION,
  CONSTRAINT adorg_bpsccorder FOREIGN KEY (ad_org_id)
      REFERENCES ad_org (ad_org_id) MATCH SIMPLE
      ON UPDATE NO ACTION ON DELETE NO ACTION,
  CONSTRAINT cbpartner_bpsccorder FOREIGN KEY (c_bpartner_id)
      REFERENCES c_bpartner (c_bpartner_id) MATCH SIMPLE
      ON UPDATE NO ACTION ON DELETE NO ACTION,
  CONSTRAINT cbpartnerlocation_bpscsoheader FOREIGN KEY (c_bpartner_location_id)
      REFERENCES c_bpartner_location (c_bpartner_location_id) MATCH SIMPLE
      ON UPDATE NO ACTION ON DELETE NO ACTION,
  CONSTRAINT bpsc_c_order_isactive_check CHECK (isactive = ANY (ARRAY['Y'::bpchar, 'N'::bpchar])),
  CONSTRAINT bpsc_c_order_issotrx_check CHECK (issotrx = ANY (ARRAY['Y'::bpchar, 'N'::bpchar]))
);

2) create a new module with BPSC as the DB prefix.

3) create a new table, name and db name = BPSC_C_Order

4) use the Create Columns from DB button to create the columns. check the c_bpartner_location_id column to see the reference set to **Location.

Proposed Solution

Additional Information

Tags

No tags attached.

Relationships

has duplicate	defect	0005012		closed	alostale	Problems with C_LOCATION_ID columns while seting up the AD
related to	backport	0005065		closed	alostale	Problems with C_LOCATION_ID columns while seting up the AD