Problem changing table structure CDS

I created a table using a .hdbdd file.  I was then able to import data from a csv file.  Everything worked like a charm.  Later I tried to add a field to the table but when I tried to save the updated hdbdd and csv files I get an error that the number of columns in the table and csv file don't match.  So, I tried to delete the entry for the table from the hdbti table.  It allowed me to save the file but still get the column mismatch error. 
Then I deleted the database table but now I get an error: Table import target table cannot be found. Table import target table cannot be found.
Finally, I tried to delete the csv file but the file appears in the list of files but I can't open it and I still get the same error.
Now I can't change any part of the data model with getting the error.  Is there no way out of this maze?
Ross

My package structure:
The hdbdd file (The customers file is the one I want to delete):
If I activate this file, it activates fine but if I delete the customer table definition I get the error "Error while activating /f14e/S001/GBI/data/GBI_S001.hdbdd:Unknown object name "f14e.S001.GBI.data::GBI_S001.CUSTOMERS"."
namespace f14e.S001.GBI.data;
@Schema: 'F14E_STUDENT_001'
context GBI_S001 {
    @Catalog.tableType: #COLUMN
  entity SALES_ORG {
  key SALES_ORG  : String(4);
  DESCRIPTION : String(16);
@Catalog.tableType: #COLUMN
  entity CUSTOMERS {
  key ID : String(10);
  COMPANY_NAME : String(35);
  CITY : String(20);
  key SALES_ORG : String(4);
  COUNTRY: String(2);
  @Catalog.tableType: #COLUMN
  entity PRODUCTS {
  key product : String(8);
  product_name : String(40);
  product_category : String(3);
  division : String(2);
  internal_price: Decimal(17,3);
  price: Decimal(17,3);
  color: String(10);
  product_group: String(20);
  @Catalog.tableType: #COLUMN
  entity SALES_ORDERS {
         created_at : LocalDate;
         created_by : String(20);
     customer_number : String(10);
  key order_number : String(10);
     gross_amount : Decimal(17,3);
     discount : Decimal(17,3);
     currency : String(3);
     status : String(15);
    @Catalog.tableType: #COLUMN
  entity SALES_ORDER_DETAILS {
  key order_number : String(10);
  key order_item : String(3);
     product : String(8);
     quantity : Integer;
     unit_of_measure : String(3);
     revenue : Decimal(17,3);
     currency : String(3);
     discount : Decimal(17,3);
Tables in the catalog
Customer table structure
hdbti file (with other tables removed)
import = [
  table = "f14e.S001.GBI.data::GBI_S001.CUSTOMERS";
  schema = "F14A_STUDENT_001";
  file = "f14e.S001.GBI.data:customers2.csv";
  header = false;
If I attempt to activate this file I get the error "Error while activating /f14e/S001/GBI/data/importdata.hdbti:Table import target table cannot be found. Table import target table cannot be found."
I appreciate your help on this.
Ross

Similar Messages

  • Using ADF against changing table structures

    Hello,
    We are developing a JSP app that will hit the same tables in different dbs/scheams, but the attributes (columns) of the tables could change (all except the primary key and name of the table). I want to write the app once and allow it to hit the same tables even if they have different columns (depending on what db is connected). As an example, using ResultSetMetaData I can easily "loop" thru through all column "labels" and then loop thru the ResultSet to display the data.
    I am assume that ADF would NOT be a good fit for this type of application but I wanted to see what others had to say.
    Thanks.

    The biggest problem is that the number of columns in the tables could differ. Is it possible/feasible to create dynamic ViewObjects based on the structure of the currently connect db? As in, once the app initially connects, it dynamically build the ViewObjects and then allows the app to access these ViewObjects as needed.

  • Last time the table structure changed

    What is the best way to find out as to when a table structure was last changed? (Like adding or modifying a column) ?
    I queried LAST_DDL_TIME in the dba_objects view but the problem is that it stores the last time the table was truncated (using TRUNCATE TABLE table_name), as we do truncates often. I was interested in find out when the table was altered. Any ideas ?

    Hi,
    i think database trigger will do better according to your need....
    its simple and best.
    Just create a new table and database trigger.
    Like
    create table db_ddl_log
    username varchar2(30),
    ddl_date date,
    ddl_type varchar2(30),
    object_type varchar2(18),
    owner varchar2(30),
    object_name varchar2(128)
    create or replace trigger db_DDL_Trigger
    AFTER DDL ON DATABASE
    BEGIN
    insert into db_ddl_log
    username,
    ddl_date,
    ddl_type,
    object_type,
    owner,
    object_name
    VALUES
    ora_login_user,
    sysdate,
    ora_sysevent,
    ora_dict_obj_type,
    ora_dict_obj_owner,
    ora_dict_obj_name
    END;
    now check it.
    SQL> select * from db_ddl_log;
    no rows selected
    SQL> desc a
    Name Null? Type
    NO NUMBER
    SQL> alter table a add (name varchar2(1));
    Table altered.
    1* select * from db_ddl_log
    USERNAME DDL_DATE DDL_TYPE OBJECT_TYPE OWNER OBJECT_NAME
    SYS 06-MAR-06 ALTER TABLE SYS A
    SQL> truncate table a;
    Table truncated.
    sql> select * from db_ddl_log
    USERNAME DDL_DATE DDL_TYPE OBJECT_TYPE OWNER OBJECT_NAME
    SYS 06-MAR-06 ALTER TABLE SYS A
    SYS 06-MAR-06 TRUNCATE TABLE SYS A
    Thanks
    Kuljeet Pal Singh

  • Demantra PTP table structure changed in 7.3.X.X

    The staging tables structure is changed in Demantra version 7.3 onwards as compared to Demantra 7.2.X.X. Some of the "Required" columns in "BIIO_Promotion" table which is used to load promotion data`has been removed in Demantra 7.3. And some more "Required" columns are added in "BIIO_Promotion" table.
    The disappointing thing is that the implementation and user guide doesn't speak about it. How the implementer know, what type of values to load in these mandatory columns to populate the promotion data in Demantra.
    Regards,
    Milind...

    go to tables statements -
    > double click on the structure----> it will takes you to that structure

  • Change of structure of database table

    A custom database table has been created and is already in use by 10 programs. Now a new requirement has come to add a field i.e. a check box to the database table to be used by one of the 10 programs. Can we change the structure of the database table after activating it and when the table is in use? Please provide me inputs on this.
    Thanks and regards
    Radhika

    Yes. U can change it. But I suggest u to do it through the process of 'Append Structure'.
    If u have any probelm after changing follow this process.
    Goto Utilities > Database Utilities> Activate and Adjust Database
    Awrd Points if useful
    Bhupal

  • How to Change S012  Table Structure ..?

    Hi MM Experts,
    How to copy and how to create new structure  and new caracterstics and MAterial type from  table S012 .
    T-code for execute MCE1 .
    How to Change S012  Table Structure ..?
    Regards,
    Anthyodaya.
    Edited by: anthyodaya Reddy Nagaram on Jul 7, 2010 12:44 PM

    Anthyodaya,
    Values?  Your newly created infostructure will have no data until you define how to update the underlying tables, and then execute the update.
    You need to be a bit more specific.  Are you saying that you attempted a 1-to-1 copy of S012 into a new structure, and you got a failure?  What failure?  What error message?  If you have saved your new infostructure, you can run the consistency utility to see what if anything is missing/misconfigured  MCSCHECK.
    If you have no experience with infostructures, I suggest you enlist the services of an experienced person to assist you.  Especially if you intend to implement non-standard characteristics and values, this can be a complex task.
    SAP help in this area
    Creating new IS
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/c1/3754f7449a11d188fe0000e8322f96/frameset.htm
    Purchasing Info system
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/c1/375504449a11d188fe0000e8322f96/frameset.htm
    Rgds,
    DB49

  • Table structure changed in testing system after system refresh.

    Hi Team,
    Recently we underwent a system refresh in Testing System where the Testing data is filled with Production data. But now we find that in one table some fields which we had deleted they are again found there. The version history of table is also gone. The table object was under testing in testing system and after which it was supposed to be transported to production. I believe System refresh only means refresh of data and it has nothing to do with table structure. Please correct me if I am wrong. Please also let me know what could be the reason of those changes in table if it is not System Refresh.
    Regards,
    Amit

    I believe System refresh only means refresh of data and it has nothing to do with table structure.
    Alas, you were wrong, after all table definition are data too, as program sources...
    You have to re-import every transport request which was not yet transported to production in your test system.
    Regards,
    Raymond

  • Suggestion required in target table structure change

    Hi all good morning,
    I have one requirement. I have a target table T with some coulmns. Now I need to add one additional column to T and one procedure is there to populate the data for new column. This target table T is used by 50 mappings.my questions is if we change the structure of the table do we need to import(I think we must import). If we import what could be the impact of this re-import. do we need to rebound and validate alla the mappings and then deploy?
    the other possibility what I can do is I will create a replica of T as T1 with one additional column. I will create a new mapping which dumps data from T to T1and I will replace my T with T1 in my reporting environment.
    pls suggest which is good one. it is urgent.
    thanks in advance.
    Viki

    Hello, if you don't need the new column in the 50 mappings, you can temporarily leave them alone (you say it's urgent), and just feed the new col..
    When you have more time, you should reconcile the mappings with table T and re-deploy them. OMBPlus scripting is ideal for this task.
    Hope this helps, Antonio

  • Oracle Data Pump - Table Structure change

    Hi,
    we have daily partitioned table, and for backup we are using data pump (expdp). we policy to drop partition after backup (archiving).
    we have archived dump files for 1year, few days back developer made changes with table structure they added one new column to table.
    Now we are unable to restore old partitions is there a way to restore partition if new column added / dropped from currect table.
    Thanks
    Sachin

    If a new column has been added to the table, you can import only the the data from the old structure to the new structure. Use the parameter CONTENT=DATA_ONLY.

  • Table structure changes from PS HRMS 8.3 & 8.8 to PS 9.1

    Hi,
    Is there any delivered report (or) excel sheet explaining the table structure changes from PS HRMS 8.3 & 8.8 to PS 9.1
    Any help on this highly appreciated.
    Thanks
    Soundappan
    Edited by: Soundappan on Nov 1, 2012 7:04 PM

    I'm not sure to understand what kind of module you're talking about.
    Anyway, there are several docs available in MOS which shows the features differences over the versions, have a look :
    PeopleTools Cumulative Feature Overview Tool ID 793143.1*
    But I didn't find any starting by your (very old) Peopletools version.
    Nicolas.

  • Table structure changes

    Assuming that an OraLite 10g is now running on CE.Net and Msync is working fine to do data synchronization between Oralite 10g and an enterprise 9i database. If I make structure changes to a table on the enterprise database, how do I reflect the changes to the OraLite database on the CE.net device.
    Thank you.

    There's a good post about this on metalink...
    A) Add column
    1. Upload all client data. Clients should not add new data until they are told by the administrator to sync again!!
    2. Stop Mobile Server listener
    3. Change the Oracle8i/9i database schema (add column)
    4. Create a Java program to call the Consolidator Admin API AlterPublicationItem()
    5. Start Mobile Server
    6. Execute a sync from the client
    7. The new column should be seen on the client. Use MSQL to check snapshot definitions.
    B) Drop column
    1. Upload all client data. Clients should not add new data until they are told by the administrator to sync again!!
    2. Stop Mobile Server listener
    3. Delete column of the base table in the Oracle database schema
    4. Create a Java program to call the Consolidator Admin API DropPublicationItem()
    5. Create a Java program to call the Consolidator Admin API CreatePublicationItem() and AddPublicationItem().
    6. Start Mobile Server
    7. Execute a sync from the client
    8. The new column should be seen on the cliet. Use MSQL to check snapshot definitions.
    C) Change column datatype
    Changing datatypes in a repliatated system is not an easy task. You have to follow certain procedures in order to make it to work. Use DropPublicationItem, CreatePublicationItem and AddPublicationItem methods from the Consolidator Admin API. You must stop/start Mobile Server listener to refresh the cache.
    1. Client syncs. Clients should not add new data until they are told by the administrator to sync again!!
    2. Stop Mobile Server listener
    3. Drop/create column (do not use conversion procudures) at the base table
    4. Call DropPublicationItem(). Check if the ErrorQueue and InQueue no longer exist.
    5. Call CreatePublicationItem() and AddPublicationItem(). Check if the ErrorQueue and InQueue reflect the new column datatype
    6. Start Mobile Server. This automatically resumes application
    7. Client executes sync. This should drop the old snapshot and recreate the new snapshot. Use MSQL to check
    snapshot definitions.
    D) Drop table
    1. Client syncs. Clients should not add new data until they are told by the administrator to sync again!!
    2. Stop Mobile Server listener
    3. Drop base table
    4. Call DropPublicationItem(). Check if the ErrorQueue and InQueue no longer exist.
    5. Start Mobile Server. This automatically resumes application
    6. Client executes sync. This should drop the old snapshot. Use MSQL to check snapshot definitions.
    E) Add table
    1. Client syncs. Clients should not add new data until they are told by the administrator to sync again!!
    2. Stop Mobile Server listener
    3. Add new base table
    4. Call CreatePublicationItem() and AddPublicationItem() method
    5. Start Mobile Server. This automatically resumes application
    6. Client executes sync. This should add the new snapshot. Use MSQL to check snapshot definitions.
    F) Changing Primary Keys
    Chaning PK is a severe operation which must be executed manually. A snapshot must be deleted and recreated to propagate the changes to the clients. This causes a full refresh on this snapshot.
    1. Client syncs. Clients should not add new data until they are told by the administrator to sync again!!
    2. Stop Mobile Server listener
    3. Drop the snapshot using DropPublicationItem() method o
    4. Alter the base table
    5. Call CreatePublicationItem()and AddPublicationItem() methods for the altered table
    6. Start Mobile Server. This automatically resumes application
    7. Client executes sync. The old snapshot will be replaced by the new snapstot using a full refresh. Use MSQL to check snapshot definitions.
    G) To Change a Table Weight =>
    Follow the procedure below to change the Table Weight parameter. The table weight is used by the Mobile Server/Synchronization to determin the sequence in which client records are applied to the Oracle database.
    1. Run MGP to apply any changes in the InQueue to the Oracle databse
    2. Change table weight using SetTemplateItemMetadata() method
    3. Add/change constraint on the the base table which reflects the change in table weight
    4. Synchronize

  • Change internal table structure dynamically

    Dear Experts , I have a requirement to add an attribute to already declared internal table which is declared in standard SAP code, is it possible to change internal table structure dynamically.
    my internal table is of type merel_t_grid2 which is standard table type in SAP , now I want to add an attribute of type  LVC_T_STYL in my internal table so that I can modify the cell property of ALV grid.
    I cant append LVC_T_STYL in standard structure because enhancement category of merel_t_grid2 is of type char and not deep
    my internal table contains data to be displayed in ALV.
    please help

    Dear Experts , I have a requirement to add an attribute to already declared internal table which is declared in standard SAP code, is it possible to change internal table structure dynamically.
    my internal table is of type merel_t_grid2 which is standard table type in SAP , now I want to add an attribute of type  LVC_T_STYL in my internal table so that I can modify the cell property of ALV grid.
    I cant append LVC_T_STYL in standard structure because enhancement category of merel_t_grid2 is of type char and not deep
    my internal table contains data to be displayed in ALV.
    please help

  • Ho to track table structure changes ?

    Hi
    I need to know how to track the table structure changes ?
    I mean how to know when , which column was added/dropped/altered by which user for a table.
    Is there any DD view for the same in Oracle??

    user572632 wrote:
    Hi
    I need to know how to track the table structure changes ?
    I mean how to know when , which column was added/dropped/altered by which user for a table.
    Is there any DD view for the same in Oracle??refer auditing
    what is your oracle version?
    refer
    http://download.oracle.com/docs/cd/B10500_01/server.920/a96524/c25audit.htm
    http://www.oracle-base.com/articles/10g/Auditing_10gR2.php
    also check trigger,
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_7004.htm

  • Conversion Table Questions: problems converting tables to structured

    I'm in the process of converting unstructed FM8 docs to structured docs using FM10 and DITA structure. Right now I'm trying to build a conversion table to structure the docs, but I'm having a lot of trouble with the tables. The main problem seems to be with the tgroup element since I can't figure out how to get the thead and tbody to wrap in the tgroup element.
    Here is an example of one of the tables I'm trying to structure:
    This is the Table section of the conversion table I've had the most success with:
    And this is the result:
    As you can see, the thead and tbody elements are not wrapped in tgroup and the structure is invalid. I've been playing around with the conversion table for several days now and can't seem to figure out how to fix this. If anyone has any suggestions, they would be greatly appreciated!
    Thanks,
    D'Arcy

    D'Arcy,
      Here are a few observations that might help:
    1) The structure you use within FM (which is what the conversion table helps create) need not be exactly the same as the structure you use in XML.
    2) Do not confuse the element named table with a FrameMaker table.
    3) As Michael has pointed out, the CALS table model used by DITA is a five-level structure:
    table
      tgroup
        tbody
           row
             entry
    while the FrameMaker table model has 4 levels:
    table
      tbody
        row
          cell
    4) FrameMaker can map between the 5-level structure and the 4-level structure in one of two ways, controlled by the element definitions (usually specified in an EDD), the read/write rules, and the DTD:
    a) The element named table can be a container while the element named tgroup is the actual table. This model has a closer correspondence between the FrameMaker and the DITA table structure. Michael has pointed out one of its biggest weaknesses. If a FrameMaker table (regardless of its element name) has a title, then FrameMaker repeats the title on each page of a multipage table. However, if the element named table is a container and the actual table is an element named tgroup, the title is a container preceding the table and this automatic repetition does not happen.
    b) If you are sure that your tables will always consist of a single tgroup, you don't have to use the tgroup element within FrameMaker. Make the element named table a FrameMaker table and include the read/write rule:
    element "tgroup" unwrap;
    FrameMaker will recreate the tgroup element whenever you save a document as XML. This model allows you to make the table title a FrameMaker table. However, you cannot use the element named title as both a FrameMaker table title and a container. Typically, therefore, people use the element named title as a container that is the title of things like chapters and sections and use an element named something like tabletitle for the title of tables.
    Read/write rules like:
    element "title" is fm element:
    element "title" is fm table title element "tabletitle"'
    let you save your documents as XML with both title and tabletitle represented as <title> in XML. You'll need to use a custom client or XSLT to map the XML element named title to either title or tabletitle depending on whether the XML element occurs within a table or not.
    5) Your conversion table had one row with T: in column 1 and another with T:Format A in column 1; one mapped to table and the other to tgroup. The row with T:Format A would apply to all tables with the specified format, the other row would apply to all tables with other formats. These conversion table rows do not define a relationship between table and tgroup. Map T: to table if you want the model in 4b) above and to tgroup if you want the model in 4a). In the latter case, use an additional row with:
    title?, tgroup
    in column 1 and  table in column 2.
         --Lynne

  • Changing database structure

    I have to add a tabel a mailalerttext and link that to mailalertypes which is linked to mailalerts. I had some problems with the selectlists, underneath you will find something that will solve that problem I thought, but it may be easier to solve it simpler, but thats apex stuff.
    If a default user and default applicationcode would exist, it would be possible to use them in the mailalert table which has following colums:
    MAILALERTID,APPLICATIECD,GEBRUIKERID,MAILALERTTYPEID,SENDMAILIND
    gebruikerid means userid.
    The defaultuser and application code would then be used in the mailalerts table and the column mailalertype would be replaced by mailalerttypecode. These are defined they can't change.
    The reason is that if mailalerttext is linked to maillalerts using the mailalertid as the foreign key, then that allows to find the correct text, or select it straightaway by using the mailtextid. All the selects would then be made on the mailalert table.
    The numbers used as default are just those that are free, a default user can be filled in like that in te gebruikers table, and a default application code in the apps table.
    Only the standard user and the mailalerttypecode are important, the standard applicationcode could be used as an extra check but might not be necessary.
    A select could then be made on that applicationcode, that user, that typecode if not found select standarduser and typecode.
    Applicationcode is only filled in to stick to the table definitions. To solve a problem with a select list on a page in apex i think this is overkill, as it requires more changes then does the first solution, It means changing tables, dropping columns adding them, changing triggers, changing code in apex pages, a lot of work.
    But I was wondering if concerning a database structure, starting from scratch this is something that would be considered good, not so good, bad, something to not do ?
    I'm not sure this is the right group, but it isn't strictly apex, and it isn't really sql/plsql either. More database structure.
    I'm just beginning, so i'd like to know your opinions and why it would be bad, or possibly good.
    Message was edited by: Floris Vermeir
    Removed the spelling mistakes.
    Floris

    I'm still not sure I understand your existing data model properly. The following is my interpretation of what I think your're trying to achieve.
    There are four core data tables -
    * APPLICATIONS - holds information relating to the programs you administer
    * MAIL_TEXT - holds boilerplate text for each type of e-mail (I'm assuming this text can be shared across applications)
    * MAIL_TYPES - the different kinds of e-mail alerts which can be sent
    * USERS - holds information about the support staff.
    I think you need two intersection tables
    * APP_MAIL_TYPES - application X uses text Y for e-mails of type Z (candidate key: app id and type id)
    * USER_MAIL_REGS - user Joe gets e-mails of type Z from application X (candidate key: app id, type id and user id)
    NB If the registration is just done against alert type for all apps, then the USER_MAIL_REGS table shoudl intersect USERS and MAIL_TYPES.
    |                      |
    |  applications        |
    |                      |
           |
           |
          /|\
    |                      |                |                      |
    |  app_mail_types      |>---------------|  mail types          |
    |                      |                |                      |
             \|/     |
              |      |
                |      ---------------------------------          
                |                            |
                |                              /|\
    |                      |                |                      |    
    |  mail text           |                |  user_mail_regs      |    
    |                      |                |                      |    
                                             \|/
                                              |
                                                       |
                                            |                      |                       
                                            |       users          |                       
                                            |                      |                       
                                            ----------------------                        I think USER_MAIL_REGS corresponds to your "overview" table. (It's a good idea to use names which convey as much info as possible. I acknowledge the difficulty of doing this in another language). Changing the users' registrations would simply be a matter of inserting or deleting rows from the USER_MAIL_REGS.
    If this doesn't help you then I'm afraid you will need to give me more info. Specifically, what tables you have, the role they play and the relationships between them.
    Cheers, APC

Maybe you are looking for