Cross client database tables

Hi ,
can someone please let me know any cross client database tables in SAP R/3..
Thanks,
Raghav

Hi Raghavendra Manchippa ,
Any table which have a field MANDT and it should be Primary Key so that table be Cross Client Table..
If satisfied,,,rewards me..
Kind Regards
Yogesh Gupta

Similar Messages

Split database to client specific and cross client

Hi
Do we have a known method to split an existing MaxDB database into two .
1. Client Specific database
2. Cross client database
Thanks and Regards
Sri

What you can do is to use TDMS (Test Data Migration Server), it´s a separate product and it enable you to setup test/training systems with a reduced amount of production data.
This system makes use of technologies to determine, whether a table is client depend and client independent.
Your problem is, that the client specific data NEEDS the cross client data, it relies on the customizing, that is cross client.
If your pupose is to e. g. extract some kind of data because parts of your company was sold or if you bought a new company, then you should contact the SLO group (http://service.sap.com/slo) that does those kinds of "separations" too.
From a technical level, it´s certainly possible but wihtout knowing your initial intent why you want to do that, one can give just advises, what we "think" what the reason might be.
Markus

How to disable Cross client Table Access

Hi All,
i have created a Sand box client and i have set its cross client object value to
"No Changes to repository and cross client customizing objs"
but still users are able to run transactions like SR13 which are cross client tables
please help

HI Zeeshan,
Once u run the Tcode like SR13, the users would be able to enter the Tcode and have a new entry varinat created..but during SAVE the system would sure prompt the message... " Changes to Repository or cross-client Customizing are not allowed. Please press DISPLAY or CANCEL" ..
so the changes would not be saved hence forth and have to be cancelled out..
hope this is what u have been looking for..
Br,
Sri
Award points for helpful answers

How to delete a row from database table in facade client

Hi all,
I followed the tutorial in creating a persistence entity from database table, then a session facade. Then I followed the tutorial to create a sample client to test the model. In the session facade, I could use persistEntity method to insert a record to the database. I am just thinking of an extension to the tutorial, i.e., being able to delete the record too. So I created a new method removeEntity in the session facade
public void removeEntity(Object entity) {
entity=em.merge(entity);
em.remove(entity);
em.flush();
and called it in the sample client. It was executed without any error, but the record in the table still exists.
I tried to look around for a solution, but I did not find one. Would anybody here please help out? Many thanks in advance!

Hi Frank,
I tried the code snippet, but I got the following exception when executing this code:
javax.ejb.EJBException: EJB Exception: ; nested exception is:
     java.lang.IllegalStateException: The method public abstract javax.persistence.EntityTransaction javax.persistence.EntityManager.getTransaction() cannot be invoked in the context of a JTA EntityManager.; nested exception is: java.lang.IllegalStateException: The method public abstract javax.persistence.EntityTransaction javax.persistence.EntityManager.getTransaction() cannot be invoked in the context of a JTA EntityManager.
java.lang.IllegalStateException: The method public abstract javax.persistence.EntityTransaction javax.persistence.EntityManager.getTransaction() cannot be invoked in the context of a JTA EntityManager.
     at weblogic.deployment.BasePersistenceContextProxyImpl.validateInvocation(BasePersistenceContextProxyImpl.java:121)
     at weblogic.deployment.BasePersistenceContextProxyImpl.invoke(BasePersistenceContextProxyImpl.java:86)
     at weblogic.deployment.TransactionalEntityManagerProxyImpl.invoke(TransactionalEntityManagerProxyImpl.java:91)
     at weblogic.deployment.BasePersistenceContextProxyImpl.invoke(BasePersistenceContextProxyImpl.java:80)
     at weblogic.deployment.TransactionalEntityManagerProxyImpl.invoke(TransactionalEntityManagerProxyImpl.java:26)
     at $Proxy141.getTransaction(Unknown Source)
     at model.SessionEJBBean.removeEntity(SessionEJBBean.java:60)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
     at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:55)
     at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
     at $Proxy143.removeEntity(Unknown Source)
     at model.SessionEJB_qxt9um_SessionEJBImpl.removeEntity(SessionEJB_qxt9um_SessionEJBImpl.java:142)
     at model.SessionEJB_qxt9um_SessionEJBImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
javax.ejb.EJBException: EJB Exception: ; nested exception is:
     java.lang.IllegalStateException: The method public abstract javax.persistence.EntityTransaction javax.persistence.EntityManager.getTransaction() cannot be invoked in the context of a JTA EntityManager.; nested exception is: java.lang.IllegalStateException: The method public abstract javax.persistence.EntityTransaction javax.persistence.EntityManager.getTransaction() cannot be invoked in the context of a JTA EntityManager.
     at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.unwrapRemoteException(RemoteBusinessIntfProxy.java:109)
     at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:91)
     at $Proxy0.removeEntity(Unknown Source)
     at model.SessionEJBClient.main(SessionEJBClient.java:71)
Caused by: java.lang.IllegalStateException: The method public abstract javax.persistence.EntityTransaction javax.persistence.EntityManager.getTransaction() cannot be invoked in the context of a JTA EntityManager.
     at weblogic.deployment.BasePersistenceContextProxyImpl.validateInvocation(BasePersistenceContextProxyImpl.java:121)
     at weblogic.deployment.BasePersistenceContextProxyImpl.invoke(BasePersistenceContextProxyImpl.java:86)
     at weblogic.deployment.TransactionalEntityManagerProxyImpl.invoke(TransactionalEntityManagerProxyImpl.java:91)
     at weblogic.deployment.BasePersistenceContextProxyImpl.invoke(BasePersistenceContextProxyImpl.java:80)
     at weblogic.deployment.TransactionalEntityManagerProxyImpl.invoke(TransactionalEntityManagerProxyImpl.java:26)
     at $Proxy141.getTransaction(Unknown Source)
     at model.SessionEJBBean.removeEntity(SessionEJBBean.java:60)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
     at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:55)
     at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
     at $Proxy143.removeEntity(Unknown Source)
     at model.SessionEJB_qxt9um_SessionEJBImpl.removeEntity(SessionEJB_qxt9um_SessionEJBImpl.java:142)
     at model.SessionEJB_qxt9um_SessionEJBImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Process exited with exit code 0.

How to create a cross-client table maintenance dialog?

Hello everybody,
I have a client specific table (mandt is the first key field) that should be maintained cross-client: In the table maintenance dialog, I want to change/create/insert values belonging to clients other than the current logon client. Can I do this with a generated maintenace dialog? If yes, how?
Thank you for your help, regards, Kathrin!

Hi Kathrin,
I think you can't, you must create your own dialog maintenance program.
They are some program to copy data from client to others .. but never seen any dialog cross client. (or remove the mandt in your key).
Regards
Frédéric

Merging SAP Clients - Reporting on Cross Client Table Compare Results

Hey folks,
We are trying to merge two clients into one (on the cheap), i think that cross client table comparision is the best way to find differences and possible issues and clashes with the two systems configuration, but i was wondering if there is anyway to report on these differences, so we can pull them out to word/excel document to anaylse and document them prior to making the changes.
Does anyone know if this possible?
Thanks a lot,
Greg

Hello Mr. Newman,
I think using SCU0 is going to be the way to go but the output is not always the best. However you should be able to show the differences and download to excel to analyse further. If this doens't fit then I think you will have to look at copying the tcode / report and improving the output to meet your needs.
Alternatively post to basis folks and see if they have some better ideas!
Hope this helps,
Cheers,
Dan
Edited by: Danny boy on Mar 31, 2010 3:00 PM

Cross client tables

Hi,
I am trying to authorize a user for maintaining the cross client tables with SM30.
I have added the Authorization object S_TABU_CLI with the change permission and regenerated
the profile and assigned to the user. But the user is still unable to maintain the cross client tables
like V_DDAT. How to enable a user to maintain cross client tables.
Thanks in Advance,
Ramakrishna.

One thing. I saw in your response that you have not assigned an authorization group on S_TABU_DIS?
This is necessary, as the system always checks on the auth group.
If the table is not classified in TDDAT, it will check against &NC&.
Tables are protected through S_TABU_DIS for client-dependant tables AND S_TABU_CLI as extra protection fro cross-client tables.

Use of client dependent tables

Hi Gurus,
I have read many threads on difference between client dependent and independent data/objects etc.
But, someone tell me please, wheat exactly the 'Use or Advantage' of client dependent tables/data.
Thanks in advance.
V

HI,
The use of client dependent tables is that if data in one table of a particular client is updated then that data wont be seen in any other clent it provides a security to the data we retrict users with their authorizations in differen clients
When you log on to an SAP System, you log on to a particular client of this system. Any activities you carry out in the system are always carried out in one client. When you plan your SAP system landscape, you must consider which clients you need for which activities.
By assigning activities to be performed in a client, you give each client a particular role. This section describes the most important client roles.
Since you need to adapt the SAP software for your own business needs, each SAP system landscape requires a client where Customizing settings, and possibly ABAP Workbench developments, can be made. This client is known as the Customizing and development client, or Customizing client for short. The abbreviation CUST is used for this client.
Before you can use the Customizing settings and Workbench developments productively, you need to test them extensively for errors. Any faulty settings can seriously disrupt productive operations, and at worst, lead to the loss of productive data. The integrated nature of the various SAP applications means that there are many dependencies between the different Customizing settings. Even an experienced Customizing developer may not discover these dependencies immediately. The correctness of the settings can only be guaranteed with extensive testing. The client where these tests are made is the Quality Assurance Client, QTST for short.
A separate client is required for productive use of the SAP System. So that this client can be used without disruption, it is essential that no Customizing settings or Workbench developments are made here, and also that no tests are carried out. This client is known as the Production Client, PROD for short.
These three clients, CUST, QTST and PROD, are the central clients that exist in every system landscape. Standard system landscapes have precisely one client for each of these client roles.
We recommend that you make all your Customizing settings in a single Customizing client, and then use the CTS to transport them to the other clients.
We also recommend that you do not make any Customizing settings or Workbench developments in the quality assurance or production clients. You can make sure of this by making appropriate client settings.
In addition to the central clients, you can also set up other clients for other tasks. However, you must remember that each extra client takes up additional system resources (main memory and database space). They also need to be administrated. For example, you need to set up and administrate access authorization for the users, and also distribute any changes to other clients with the CTS. You must weigh up the advantages and disadvantages of setting up other clients.
Examples of other client roles are:
Development test client (TEST): Developers can use this client to test their Customizing settings and Workbench developments, before they release their change requests. In this client the developers can create test application data for realistic tests. If they discover errors, they can remove them in the Customizing client. A development test client is always set up in the same SAP System as the Customizing client. This means that any changes that are made to cross-client data in the Customizing client are also immediately visible in the development test client. Changes to client-specific data are copied from the Customizing client to the development test client using a special client copy function. The client copy function uses the unreleased change requests from the Customizing client to do this. The development test client is set so that you cannot make changes to Customizing data and Repository objects.
Prototype or sandbox client (SAND): You can use this client to test any client-specific Customizing settings if you are not sure whether you want to use them in this form. Any settings that you want to keep are then entered in the Customizing client. To prevent conflicts between the prototype client settings and real settings in the Customizing client, you cannot make changes to cross-client Customizing data and Repository objects in the prototype client. The CTS does not record changes made to client-specific Customizing data, and does not transport them from the prototype client. You can make sure of this by making appropriate client settings.
Training client (TRNG): To prepare end users for new functions that are to be transported into the production client, you can set up a training client. The users can use the new functions in this client with specially created application data. This client is set so that you cannot make changes to Customizing data and Repository objects.'''
plzz reward if this information is usefull to u plaa dont forget to reward

Cross client data read

Hi Experts
select * from zemp
into corresponding fields of table itab
where sy-mandt = 391.
Can we read data of database table from cross clients.
i used abv query, says error.
regards
Rajaram

Hi
I trid as follows
SELECT * FROM zemp CLIENT SPECIFIED INTO table itab
WHERE MANDT = '392'.
But am getting the error as follows,
The work area "ITAB" is not long enough. long enough.
What could be the reason,
regards
Rajaram

What is meant by cross client

hai
waht is meant by cross client while defining new table?
hav a nice time

Hi,
The changes that you make in the ABAP Workbench are placed in the Repository tables of the SAP database. The contents of these tables are known as Repository data or Repository objects. Apart from a few exceptions, the Repository data is cross-client. As with cross-client Customizing, changes to Repository objects affect all clients of an SAP System
Tables which are having MANDT field is called as client dependent tables. Tables which are not having MANDT field is called as client dependent tables.
Client independent
a table/object that is valid for all clients in a system. E.g table SCC4. This table will be the same no matter which client you view it from. If you try to make changes in SCC4, you'll get a popup with a warning that the table is cross client.
Client dependent
a table/object that is only valid for the client it is changed in. E.g the user tables USR*. You have to create users in each client.
Hope it helps. Please reward if useful.
Thanks & Regards
Sadhu Kishore

Swapping between client database and web database

Hi i have completed tutorials etc so can now create the
sqlite database for my application which is downloaded by the user
and will run on thier desktop so i am calling it the "client
database" which contains data they are working with but there is
another database containing identical tables which i am calling the
"global database" the idea of this is to transfer data between the
different clients and backup that information.
so i am looking for a tutorial or a sample app where the app
takes information from a web based database and copy's that rob
into a sqlite database on the clients machine?
this is the main problem im having and seen people mentioning
blaze DS and stuff like that, ideally i wouldn't like to use PHP
but atm is looking like i may have to.
i will sell my soul to anyone who can help with this lol
(also i am using FLEX 3.0)

Hi,
Yes, if you use LCDS everything is there already for you, so
that you can complete this application in very less time. Since you
want to use PHP, you can use Zend PHP, which will support Remoting
using AMF. Using Zend PHP, write PHP classes which will help you to
synchronize data between server and client and just invoke those
from your Flex application when required.
Hope this helps.

Steps to follow while creating Database table in notes or paperwork

what are the steps to follow while creating Database table in notes or paperwork
Thank you,
Regards,
Jagrut Bharatkumar Shukla

hi,
1. Goto Transaction SE11.
2. Enter the table name to be created. It should start with a Y or Z.
3. Press Create
4. Enter the Short description for the table
5. Enter the Delivery class for the table. It can be 'A', 'C' or other.
6. In the Fields tab, specify the table fields and the corresponding data elements or the built-in data types.
7. If the table needs to be made a client-depenedent table, the first field should be MANDT.
8. Goto Technical settings of the table and sepcify the Data Class and Size for the table. Also, there u can specify if buffering for the table should be allowed or not.
9. Now, activate the table.
if helpful reward some points.
with regards,
Suresh Aluri.

GTC Error While Provisioning to Oracle Database Tables

I'm trying to setup GTC connector to provisioning/reconcile users into database tables, but during the provisionig gtc fails. check the lines above to see the error
ERROR,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBProvisioningTransportProvider/sendData encounter some problems: Attribute: matricula does not exist in the specified parent table/view: xladm.usuarios_view
com.thortech.xl.gc.exception.DBException: Attribute: matricula does not exist in the specified parent table/view: xladm.usuarios_view
matricula is the primary key
I'm using OIM 9102 with bundle patch 12 appled. connector version is 9105. Oracle database version is 11.1.0.7. My platform is Windows 2003.
database table's ddl
create table usuarios (
matricula varchar2(10) primary key,
nome varchar2(80),
status varchar2(20),
ultima_atualizacao date,
senha varchar2(20));
create view usuarios_view as select * from usuarios;
GTC Connector Setup
Provide Basic Information View
Name INFO
Reconciliation
Transport Provider Database Application Tables Reconciliation
Format Provider Database Application Tables Reconciliation
Trusted Source Reconciliation No
Provisioning
Transport Provider Database Application Tables Provisioning
Format Provider Database Application Tables Provisioning
Specify Parameter Values Change
Database Driver oracle.jdbc.driver.OracleDriver
Database URL jdbc:oracle:thin:@localhost:1521:orcl
Database User ID xladm
Database Password ********
Customized Query
Use Native Query No
Connection Properties
Parent Table/View Name usuarios_view
Child Table/View Names
Unique Attribute matricula
Timestamp Attribute ultima_atualizacao
Database Date format
Status Attribute status
Status Lookup Code Lookup.InfoGolden.Status
Is Primary Key Auto Incremented No
Target Date Format yyyy-MM-dd hh:mm:ss.fffffffff
Batch Size All
Stop Reconciliation Threshold None
Stop Threshold Minimum Records None
Source Date Format yyyy/MM/dd hh:mm:ss z
Reconcile Deletion of Multivalued Attribute Data Yes
Reconciliation Type Full
error log
Running GENERICADAPTER
Target Class = com.thortech.xl.gc.runtime.GCAdapterLibrary
DEBUG,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Class/Method: DBReconFormatProvider/formatData entered.
DEBUG,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Class/Method: DBProvisioningTransportProvider/initialize entered.
DEBUG,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Class/Method: DBProvisioningTransportProvider/initialize - Data: driver - Value: oracle.jdbc.driver.OracleDriver
DEBUG,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Class/Method: DBProvisioningTransportProvider/initialize - Data: url - Value: jdbc:oracle:thin:@localhost:1521:orcl
DEBUG,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Class/Method: DBProvisioningTransportProvider/initialize - Data: username - Value: xladm
DEBUG,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Class/Method: DBProvisioningTransportProvider/initialize - Data: password - Value: *******
DEBUG,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Class/Method: DBProvisioningTransportProvider/initialize - Data: parentContainerName - Value: usuarios_view
DEBUG,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Class/Method: DBReconTransportProvider/convertCSVToArraylist entered.
DEBUG,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Class/Method: DBReconTransportProvider/convertCSVToArraylist - Data: Run Time Parameters - Value: []
DEBUG,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Class/Method: DBProvisioningTransportProvider/initialize - Data: childContainerTableNames - Value: []
DEBUG,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Class/Method: DBProvisioningTransportProvider/initialize - Data: parentContainerUniqueKey - Value: matricula
DEBUG,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Class/Method: DBProvisioningTransportProvider/initialize - Data: statusField - Value: status
DEBUG,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Class/Method: DBProvisioningTransportProvider/initialize - Data: statusFieldLookup - Value: Lookup.InfoGolden.Status
DEBUG,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Class/Method: DBProvisioningTransportProvider/initialize left.
DEBUG,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Class/Method: DBProvisioningTransportProvider/initialize - Data: dbDateFormat - Value:
DEBUG,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Class/Method: DBProvisioningTransportProvider/sendData entered.
INFO,07 Nov 2010 20:18:37,086,[OIMCP.DATC],Within PROV_OPERATION_ADDUSER::statusField=status
DEBUG,07 Nov 2010 20:18:37,117,[OIMCP.DATC],Class/Method: DBFacade/getConnectionProp entered.
DEBUG,07 Nov 2010 20:18:37,117,[OIMCP.DATC],Class/Method: DBFacade/setUpSSLPropertiesForDB2 entered.
DEBUG,07 Nov 2010 20:18:37,117,[OIMCP.DATC],ExitingMethodDebug
INFO,07 Nov 2010 20:18:37,148,[OIMCP.DATC],dbType:::: = Oracle
DEBUG,07 Nov 2010 20:18:37,148,[OIMCP.DATC],Class/Method: DBFacade/getMatchingSchemaName - Data: found matching schema - Value: XLADM
DEBUG,07 Nov 2010 20:18:37,148,[OIMCP.DATC],Class/Method: DBFacade/getMatchingTableName - Data: found exact matching schema:- - Value: XLADM
DEBUG,07 Nov 2010 20:18:37,227,[OIMCP.DATC],Class/Method: DBFacade/getMatchingTableName - Data: found matching tables - Value: USUARIOS_VIEW
DEBUG,07 Nov 2010 20:18:37,227,[OIMCP.DATC],Class/Method: DBFacade/getMatchingTableName - Data: found exact matching table:- - Value: USUARIOS_VIEW
INFO,07 Nov 2010 20:18:37,258,[OIMCP.DATC],dbType:::: = Oracle
DEBUG,07 Nov 2010 20:18:37,273,[OIMCP.DATC],Class/Method: DBFacade/getMatchingSchemaName - Data: found matching schema - Value: XLADM
DEBUG,07 Nov 2010 20:18:37,273,[OIMCP.DATC],Class/Method: DBFacade/getMatchingTableName - Data: found exact matching schema:- - Value: XLADM
DEBUG,07 Nov 2010 20:18:37,336,[OIMCP.DATC],Class/Method: DBFacade/getMatchingTableName - Data: found matching tables - Value: USUARIOS_VIEW
DEBUG,07 Nov 2010 20:18:37,336,[OIMCP.DATC],Class/Method: DBFacade/getMatchingTableName - Data: found exact matching table:- - Value: USUARIOS_VIEW
INFO,07 Nov 2010 20:18:37,445,[OIMCP.DATC],dbType:::: = Oracle
INFO,07 Nov 2010 20:18:37,445,[OIMCP.DATC],dbType:::: = Oracle
DEBUG,07 Nov 2010 20:18:37,445,[OIMCP.DATC],Class/Method: DBFacade/getMatchingSchemaName - Data: found matching schema - Value: XLADM
DEBUG,07 Nov 2010 20:18:37,445,[OIMCP.DATC],Class/Method: DBFacade/getMatchingTableName - Data: found exact matching schema:- - Value: XLADM
DEBUG,07 Nov 2010 20:18:37,523,[OIMCP.DATC],Class/Method: DBFacade/getMatchingTableName - Data: found matching tables - Value: USUARIOS_VIEW
DEBUG,07 Nov 2010 20:18:37,523,[OIMCP.DATC],Class/Method: DBFacade/getMatchingTableName - Data: found exact matching table:- - Value: USUARIOS_VIEW
DEBUG,07 Nov 2010 20:18:38,367,[OIMCP.DATC],Class/Method: DBFacade/getPrimaryKeys - Data: Primary Keys - Value: []
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Column Name: - Value: MATRICULA
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Column Dataype integer value: - Value: 12
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Column Size: - Value: 10
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Table Name: - Value: USUARIOS_VIEW
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getClumns - Data: Column Datatype Name: - Value: VARCHAR2
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Database Type Name: - Value: Oracle
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Column Name: - Value: NOME
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Column Dataype integer value: - Value: 12
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Column Size: - Value: 80
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Table Name: - Value: USUARIOS_VIEW
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getClumns - Data: Column Datatype Name: - Value: VARCHAR2
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Database Type Name: - Value: Oracle
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Column Name: - Value: STATUS
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Column Dataype integer value: - Value: 12
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Column Size: - Value: 20
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Table Name: - Value: USUARIOS_VIEW
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getClumns - Data: Column Datatype Name: - Value: VARCHAR2
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Database Type Name: - Value: Oracle
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Column Name: - Value: ULTIMA_ATUALIZACAO
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Column Dataype integer value: - Value: 93
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Column Size: - Value: 7
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Table Name: - Value: USUARIOS_VIEW
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getClumns - Data: Column Datatype Name: - Value: DATE
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Database Type Name: - Value: Oracle
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Column Name: - Value: SENHA
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Column Dataype integer value: - Value: 12
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Column Size: - Value: 20
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Table Name: - Value: USUARIOS_VIEW
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getClumns - Data: Column Datatype Name: - Value: VARCHAR2
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getColumns - Data: Database Type Name: - Value: Oracle
DEBUG,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBFacade/getClumns - Data: Columns: - Value: [com.thortech.xl.gc.impl.common.Column@187f99a, com.thortech.xl.gc.impl.common.Column@1428b7, com.thortech.xl.gc.impl.common.Column@17d39b5, com.thortech.xl.gc.impl.common.Column@57cf27, com.thortech.xl.gc.impl.common.Column@e1319f]
ERROR,07 Nov 2010 20:18:38,383,[OIMCP.DATC],Class/Method: DBProvisioningTransportProvider/sendData encounter some problems: Attribute: matricula does not exist in the specified parent table/view: xladm.usuarios_view
com.thortech.xl.gc.exception.DBException: Attribute: matricula does not exist in the specified parent table/view: xladm.usuarios_view
     at com.thortech.xl.gc.impl.common.DBFacade.validateAttrExistence(Unknown Source)
     at com.thortech.xl.gc.impl.common.DBFacade.getSchema(Unknown Source)
     at com.thortech.xl.gc.impl.prov.DBProvisioningTransportProvider.getSchema(Unknown Source)
     at com.thortech.xl.gc.impl.prov.DBProvisioningTransportProvider.sendData(Unknown Source)
     at com.thortech.xl.gc.runtime.GCAdapterLibrary.executeFunctionality(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpINFO_GTC.GENERICADAPTER(adpINFO_GTC.java:125)
     at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpINFO_GTC.implementation(adpINFO_GTC.java:70)
     at com.thortech.xl.client.events.tcBaseEvent.run(Unknown Source)
     at com.thortech.xl.dataobj.tcDataObj.runEvent(Unknown Source)
     at com.thortech.xl.dataobj.tcScheduleItem.runMilestoneEvent(Unknown Source)
     at com.thortech.xl.dataobj.tcScheduleItem.eventPostInsert(Unknown Source)
     at com.thortech.xl.dataobj.tcDataObj.insert(Unknown Source)
     at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
     at com.thortech.xl.ejb.beansimpl.tcProvisioningOperationsBean.retryTasks(Unknown Source)
     at com.thortech.xl.ejb.beans.tcProvisioningOperationsSession.retryTasks(Unknown Source)
     at com.thortech.xl.ejb.beans.tcProvisioningOperations_b03yxm_EOImpl.retryTasks(tcProvisioningOperations_b03yxm_EOImpl.java:2719)
     at Thor.API.Operations.tcProvisioningOperationsClient.retryTasks(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at Thor.API.Base.SecurityInvocationHandler$1.run(Unknown Source)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.security.Security.runAs(Security.java:41)
     at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Source)
     at Thor.API.Base.SecurityInvocationHandler.invoke(Unknown Source)
     at $Proxy93.retryTasks(Unknown Source)
     at com.thortech.xl.webclient.actions.ResourceProfileProvisioningTasksAction.retryTasks(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:280)
     at com.thortech.xl.webclient.actions.tcLookupDispatchAction.execute(Unknown Source)
     at com.thortech.xl.webclient.actions.tcActionBase.execute(Unknown Source)
     at com.thortech.xl.webclient.actions.tcAction.execute(Unknown Source)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at com.thortech.xl.webclient.security.CSRFFilter.doFilter(Unknown Source)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at com.thortech.xl.webclient.security.SecurityFilter.doFilter(Unknown Source)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)

What I usually do in situations like this is that I connect to the database using a sql client and the same connection information as I specified to OIM and see if the attribute is present.
Perhaps you got the wrong db name? Or schema name?
Everything looks good so most probably there simply is some little typo somewhere.
Hope this helps
/Martin

To find out user who has created or deleted entries in a database table

Hi,
I have a scenario where i have many entries for t001w table and somehow a new plant is created and existing plant is deleted , Now I need to know
how to find out which user on what date has done these changes to the database table.
Thanks
Srikanth

Hi,
Go to the transcation SCU3   and click on evaluate the changes log click yes and then
evalute log then enter ur table name ,don't forget to check the radio button evaluate for "TABLES" and then execute
you will find details like this
arameters for Analysis:
        System ID:            D60
        SAP Release:          700
        Client:               730
        Date :                28.04.2010
        Time:                 16:09:09
        User:                 DEVELOPER01
elected Period:
        From (date/time)      22.04.2010 00:00:00
        To (date/time)        28.04.2010 16:07:51
o logs found for the selected period
o authorization group containing the following tables:
zFEED_QUES_MASTR

Where can we validate the MANDT field in a database table.

Hi All,
In any database table we will be having MANDT field. In the program while populating the table we never populate the field MANDT. But still in the database table, it automatically takes the current clinet number.
Could any body tell me where can we validate this. I have a requirement in my program, in which I need to populate one of the field with one constant value.
Thanks,
srinivas.

hi table T000 is for the Clients master table ....
the client is the special field for all the master tables...
for validating the field you need to do like this..
data: v_mandt type sy-mandt .
tables:t000.
select-options:s_mandt for t000-mandt.
select mandt
         from t000
         into v_mandt
          where mandt in s_mandt.

Cross client database tables

Similar Messages

Maybe you are looking for