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.

Similar Messages

SOAP Data source Function module table structure different from Dev to QA

Hi All,
I have generated SOAP data source in BWD and it created a ZOXBWD0117 structure and I am using this structure for XI proxy. But when I generate the same SOAP data source in BWQ, a different structure is created ZOXPBW0110.
Because of the structure changing from development to quality system my proxy transports are failed and I am not able to import my proxy changes.
Please advice how can I get same structure across all the systems?
Thanks,
Saleem.

Need to Transport Data Source through RSA5.
Saleem.

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

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

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

Table-Structure Change

Hi Guys!!!
I have created a Z***** table n activated,now i want to change the data type from FLTP to CHAR but the thing is am getting an error "Structure change at field level (convert table Z******).what i supposed to do?
Warm Regards,
Mohandoss P.

Hi,
Along with that message i think u will get 'ok' and 'delete' button will come..
please click on delete button.
but make sure that the table field is not using any where after deleting the table. other wise dependent programs will give dump.
Regards
Aravind.

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

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

Load table structure definition from Sql server and mirroring

Hi, we have to replicate some tables from sql server
into SAP dictionary.
Is there a tool/transaction for import the table structure
from a DBRMS like sql/oracle ?
Adn is there some third part solution for replicate data
from/to sql server and Sap ?
Thanks in advance.
Riccardo Galli.

Hi,
Dont know if there are any tools for this but onething is sure you will need to create the table thru SE11.
I had done something similar, created a BDC to create table and it works.
Provide the BDC with list of fields, datatype, len, key fields and the BDC will create the table.
You will need to activate the table once its created, for some reason sap put the table in "partial active" status after creation .
Good luck.
Ravi

Table structure changes when using 'create table X as ( select * from X@remote_server )'

I need to create and copy data from a remote Oracle server to a local server. The command I use is
create table X as ( select * from X@remote_server )
with remote_server is the tns name of the remote Oracle server.
The local table is created and populated with data as expected but when I check the structure using 'desc X' it shows me all the CHAR fields of the local table are triple as large as of the remote table.
I guess the problem is the difference between the NLS_CHARACTERSET settings . The local charset is AL32UTF8 and the remote is WE8MSWIN1252.
How do I change the command to make the two tables have the same field sizes ?
Thanks,
Vu

Do you want to be able to store all the data from the remote table in the local table? Assuming you do, increasing the size of the column would be the correct behavior.
By default, a VARCHAR2(10) allocates up to 10 bytes of storage. In the Windows-1252 character set on the source, 1 character requires 1 byte of storage. So a VARCHAR2(10) has space for up to 10 characters. In the UTF-8 character set on the destination, however, 1 character can require up to 3 bytes of storage. So a VARCHAR2(10) may allow you to store as few as 3 characters. Since Oracle has no way of knowing what data you have (and will have) in the source system, it triples the size to ensure that all the data from the remote system will fit in the new table. If you want the columns to be the same size on the destination that they are on the source, it is highly probable that you'll get errors inserting the data because at least one value will be too large for the destination column.
Justin

Table Structure changed in Function Module

Hello All,
How to check the strcuture of the table " yrdb_tp10_map:
got changed in the following FM.
As its not working properly.
function yrdb_tp10_get_mapping.
""Lokale Schnittstelle:
*" IMPORTING
*"     REFERENCE(VARIANTE) TYPE YDOMAENE
*"     REFERENCE(DOMAENE) TYPE YDOMAENE OPTIONAL
*"     REFERENCE(OLD_VALUE) TYPE YOVALUE OPTIONAL
*" EXPORTING
*"     REFERENCE(NEUER_WERT) TYPE YNVALUE
*" TABLES
*"      YRDB_TP10_MAP TYPE YRDB_TP10_MAP_TYPE
*" EXCEPTIONS
*"      NOT_FOUND
*"      WRONG_IMPORT
tp10_map Feld über Zustand der globalen internen Tabelle
g_yrdbtp10_map
Wert X Tabelle gefüllt
data: import(1) type c,
        tab_in type i.
if tp10_map eq space.      "interne Tabelle leer.
    select * from yrdb_tp10_map into table g_yrdbtp10_map.
    sort g_yrdbtp10_map.
    tp10_map = 'X'.
endif.
prüfen der importparameter.
wenn import = 'initial' beide Importparameter sind leer
wenn import = 1 domaene gefüllt
wenn import = 2 domaene und old value gefüllt
wenn import = 3 nur old value gefüllt --> raise Exception wrong_import
if domaene(1) ne space.
    import = '1'.
endif.
if old_value(1) ne space.
    if import = 1.
      import = 2.
    else.
      raise wrong_import.
    endif.
endif.
Vorbereitung der Rückgabe
wenn import = 'initial' Rückgabetabelle vorbereiten Ebene VARIANTE
wenn import = 1 Rückgabetabelle vorbereiten Ebene Domaene
wenn import = 2 Einzelwert zurückgeben new_value
case import.
    when space.
      loop at g_yrdbtp10_map into yrdb_tp10_map
                         where variante = variante.
        append yrdb_tp10_map to yrdb_tp10_map.
      endloop.
      describe table yrdb_tp10_map lines tab_in.
      if tab_in le 0.
        raise not_found.
      endif.
    when '1'.
      loop at g_yrdbtp10_map into yrdb_tp10_map
                         where VARIANTE    = VARIANTE
                         and   domaene     = domaene.
        append yrdb_tp10_map to yrdb_tp10_map.
      endloop.
      if tab_in le 0.
        raise not_found.
      endif.
    when '2'.
      read table g_yrdbtp10_map into yrdb_tp10_map
        with key     VARIANTE    = VARIANTE
                     domaene     = domaene
                     old_value   = old_value.
      if sy-subrc eq space.
        neuer_wert = yrdb_tp10_map-new_value.
      else.
        raise not_found.
      endif.
endcase.
endfunction.

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

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 9i Lite: Table structure changed

Hello,
how do I add a new column to a database table? I mean what actions to I have to take to add the column to the database on the server and how is this change transferred to the clients? Are these changes impossible to do with Oracle Lite?
Stefan

Yes, this is possible. There are two ways you can update the clients...
1) repackage the app with the packaging wizard
2) use the consolidator API - see the javadoc.

Have tables names changed from CF6/7 to CF 8/9?

<<Edit>>I might have just answered my question, sort of. I had already exported the data from the hosted SQL 2000 DB to my local SQL 2000 DB and then backed up and restored it to an empty DB in SQL 2008 Express. The tables have the dbo. prefix instead of the "xx." prefix in the other DB which went from SQL 2000 to SQL 2008. The site runs with the dbo. prefix. Any links to articles/videos/summaries of simple differences between version still appreciated."<</Edit>>
I built a CF6/7 based site about 5 years ago and I'm trying to move it to the current versions of MSSQL (2008R2 Express) and CF9. I believe the SQL DB is fine, I have setup the site on the local server, and am getting the following error when trying to view a page that access the DB.
[Macromedia][SQLServer JDBC Driver][SQLServer]Invalid object name 'client_info'.
I exported the DB data from the live DB server into my local SQL 2008 Express and tables now have names like "xx.client_info" Is it correct to assume that this is a new naming convention so that you can access easily access tables in multiple DBs? Would I simply need to rename the tables to exclude the "xx." at the begining? Or would it be advised to export the data into SQL 2000 and then backup/restore the DB to SQL 2008 Express?
Thanks for any help, and if there's a video or link to simple differences/improvements in CF from 6/7 to 8/9 any link would be greatly appreciated.

It's not CF-related, it's a SQLServer thing. In SQL 2008 they introduced the concept of Schemas, which I think is what you're seeing here. Rather than dbo.tablename, you now have schema.tablename.
I don't know the details to be honest, but that's what you need to be looking at.
O.

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

Similar Messages

Maybe you are looking for