Does "Target table" and "Error Table" need to be in same DB as OWB's?

We get the following error ORA-00600: internal error code, arguments: [opixrb-3], [1036], ORA-01036: illegal variable name/number at the time of OWB execution
OWB seems to successfully log the errors rows in the error table when a) target table and it’s b) error table are in the same database as OWB’s but throws ORA-01036 error when they are in a remote database from OWB's
Any one has any information about this please...? It will be of great help
Edited by: ghiyer on Jul 20, 2009 8:42 AM

Oracle has come back to us saying that
"DML error logging feature is not supported for distributed DML."
Bug 5698887 has more information about this.

Similar Messages

Attach User define tables and view table need add to database into my add-o

Hi there,
I want to deploy an addon, there are User define tables and view table need add to database.
I need some advice on some issues..
1. Can I attach User define tables and view table need add to database into my addon.
2. I wonder which chance is properly to add them, if add these user define objects in time of install and I can't get the enough information that connect to SQL server
Thanks for any help.

Hi Weerachai,
Here's an example of how to create a user-defined table in code. My suggestion would be to check if it exists when your add-on starts up and then if not, create the tables, fields and objects.
'User Table
 Private Sub CreateTable(ByVal sTable As String, ByVal sDescription As String, ByVal oObjectType As SAPbobsCOM.BoUTBTableType)
 Dim oUserTablesMD As SAPbobsCOM.UserTablesMD
 Dim iResult As Long
 Dim sMsg As String
 oUserTablesMD = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oUserTables)
 If Not oUserTablesMD.GetByKey(sTable) Then
 oUserTablesMD.TableName = sTable
 oUserTablesMD.TableDescription = sDescription
 oUserTablesMD.TableType = oObjectType
 iResult = oUserTablesMD.Add()
 If iResult <> 0 Then
 oCompany.GetLastError(iResult, sMsg)
 MessageBox.Show("Error Creating Table: " & sTable & " Error: " & sMsg)
 End If
 End If
 System.Runtime.InteropServices.Marshal.ReleaseComObject(oUserTablesMD)
 End Sub
'User Field
 Private Sub CreateField(ByVal sTable As String, ByVal sName As String, ByVal sDescription As String, _
 ByVal iSize As Integer, ByVal aFieldType As SAPbobsCOM.BoFieldTypes, _
 ByVal aSubType As SAPbobsCOM.BoFldSubTypes, ByVal sLink As String, _
 ByVal bMandatory As SAPbobsCOM.BoYesNoEnum)
 Dim oUserFieldsMD As SAPbobsCOM.UserFieldsMD
 Dim oTable As SAPbobsCOM.UserTable
 Dim iResult As Long
 Dim sMsg As String
 Dim i As Integer
 Dim x As Integer
 Dim bFound As Boolean = False
 Dim oField As SAPbobsCOM.Field
 oTable = oCompany.UserTables.Item(sTable)
 For i = 0 To oTable.UserFields.Fields.Count - 1
 oField = oTable.UserFields.Fields.Item(i)
 'MessageBox.Show(oField.Name)
 If oField.Name = "U_" & sName Then
 bFound = True
 End If
 Next
 System.Runtime.InteropServices.Marshal.ReleaseComObject(oTable)
 If Not bFound Then
 oUserFieldsMD = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oUserFields)
 oUserFieldsMD.TableName = "@" & sTable
 oUserFieldsMD.Name = sName
 oUserFieldsMD.Description = sDescription
 oUserFieldsMD.Type = aFieldType
 If aFieldType = SAPbobsCOM.BoFieldTypes.db_Alpha Or aFieldType = SAPbobsCOM.BoFieldTypes.db_Numeric Then
 oUserFieldsMD.EditSize = iSize
 Else
 oUserFieldsMD.SubType = aSubType
 oUserFieldsMD.Mandatory = bMandatory
 End If
 oUserFieldsMD.LinkedTable = sLink
 iResult = oUserFieldsMD.Add()
 If iResult <> 0 Then
 oCompany.GetLastError(iResult, sMsg)
 MessageBox.Show("Error Creating Field: " & sTable & "." & sName & " Error: " & sMsg)
 End If
 System.Runtime.InteropServices.Marshal.ReleaseComObject(oUserFieldsMD)
 End If
 End Sub
If you want to create a View I think you would have to use the RecordSet object. This will ensure that you don't have to log in to the database again
Hope it helps,
Adele

Interface tables, Seeded program and error Table

Hi can any one let me know the interface tables, Seeded program and error tables for
1) On hand_quantity Interface
2) Sub inventory transfer conversion
Version: 11.5.10
DB: 10g
Thanks & Regards,
pallis

Hi Pallis,
Pl.refer following links for sub-inventory transfer.
Inventory API interface transaction loading
http://khalidmehmoodapps.blogspot.in/2010/08/inter-org-inventory-transfer.html
http://khalidmehmoodapps.blogspot.in/2010/08/inter-org-inventory-transfer.html
HTH
sanjay

Which tables and field I need?

Hi all,
I am new to BW. Can someone tell me which tables and fields I need if I load data (sales report;t code:MCTG; s001)from R3 to BW. Which extractor do I need in LBWE or SWIB?
I may need to answer as soon as possible. Any hlep will be appreciate. Thank you.
Koala

Hi Koala,
LBWE is a tcode for Logistics Cockpit extraction. It's a direct code. You can find it also in tcode SBIW expanding nodes.
Knowing the fields that show up in your report you can compare them with queries, cubes, infosources and datasources in a business content.
Just make a little research:
http://help.sap.com/saphelp_nw04/helpdata/en/3c/63073c52619459e10000000a114084/frameset.htm
Best regards,
Eugene

Duplicate table and Alias Table

Hi,
What is the Differnce between duplicate table and Alias table?which Situation we use these table ?
Plz tell me .
Thanks

Hi,
If u duplicate the table the join conditions will carry with respective tables , same name appending (Table_Name#1)
If you duplicate a table in metadata, then that new table (with its new name) must map to a table in the physical database that has new name. If it doesn't exist, the SQL issued will generate an error.
An alias is a reference to a table that already exists, not a separate database object.
In case of Alias you need to specify joins conditions explicitly, we can use same table with different constrains to the same dim/fact table
Alias used, if you need to replicate a physical table and not create multiple tables with the same data or schema
Thanks,
Balaa...

Wat is the exact differences between clustered table and pooled table

hi,
can you tell me ravi...wat is the exact differences between clustered table and pooled table
with regards//
anilreddyg

Hi Anil Reddy
Pooled Tables, Table Pools, Cluster Tables, and Table Clusters
These types of tables are not transparent in the sense that they are not legible or manageable directly using the underlying database system tools. They are managed from within the R/3 environment from the ABAP dictionary and also at runtime when they are loaded into application memory.Pool and cluster tables are logical tables. Physically, these logical tables are arranged as records of transparent tables. The pool and cluster tables are grouped together in other tables, which are of the transparent type. The tables that group together pool tables are known as table pools, or just pools; similarly, table clusters, or just
clusters, are the tables which group cluster tables.Not all operations that can be performed over transparent tables can be executed over pool or cluster tables.
For instance, you can manage these tables using Open SQL calls from ABAP, but not Native SQL.These tables are meant to be buffered and loaded in memory, because they are commonly used for storing internal control information and other types of data with no external (business) relevance. SAP recommends that tables of pool or cluster type be used exclusively for control information such as
program parameters, documentation, and so on. Transaction and application data should be stored in transparent tables.
Table Pools
From the point of view of the underlying DBMS as from the point of view of the ABAP dictionary, a table pool is a transparent table containing a group of pooled tables which, when created, were assigned to this table pool.
Field Type Description
TABNAME CHAR(10) Table name
VARKEY CHAR(n) Maximum key length n =< 110
DATALN INT2(5) Length of the VARDATA record returned
VARDATA RAW(m) Maximum length of the data varies according to DBMS
Table Clusters
Similarly to pooled tables, cluster tables are logical tables which, when created, are assigned to a table cluster. Therefore, a table cluster, or just cluster, groups together several tables of type clusters.Several logical rows from different cluster tables are brought together in a single physical record. The records
from the cluster tables assigned to a cluster are thus stored in a single common table in the database.A cluster contains a transparent cluster key which must be located at the start of the key of all logical cluster tables to be included in the cluster. As well, a cluster contains a long field (VARDATA), which contains the
data of the cluster tables for this key. If the data does not fit into a field, continuation records are created.
Field Type Description
CLKEY1 CHAR(*) First key fields
CLKEY2 CHAR(*) Second key field
CLKEYN CHAR(*) nth key field
PAGENO INT2(5) Number of the next page
TIMESTMP CHAR(14) Time stamp
PAGELG INT2(5) Length of the VARDATA record returned
VARDATA RAW(*) Maximum length of the data section; varies according to database system
Working with Tables
The dictionary includes many functions for working with tables. There are five basic operations you can perform on tables: display, create, delete, modify, copy. Please do not confuse displaying a table with displaying the table entries (table contents). In order to display a table, it must previously exist; otherwise the system will display an error message in the status bar. For the following example, the table TABNA is used. To display this table, from the main dictionary screen, enter the table name in the Object name
input field with the radio button selected next to Tables. Then, click on the Display button at the bottom of the screen, or press the F7 function key, or, alternatively,
select Dictionary object Display from the menu.
In this screen, you can see table information such as
¨ Table type, shown next to the name of the object. In the example, it is a transparent table.
¨ Short text description.
¨ Name of the user who made the last change, and the date of the change.
¨ Master language.
¨ Table status. On the screen, you can see this table is saved and active.
¨ Development class. For information on development classes, refer to Chap. 6.
Delivery class, which sets the maintenance group for the table. It controls how tables will behave during client copy procedures, upgrades, and so forth.¨
Tab. Maint. Allowed flag, which indicates whether you can generate a screen for maintaining table entries.
¨Then, on the lower part of the screen, you can see the table fields with all associated characteristics such as:
¨ Field name.
¨ Key indicator. When set, this field is the primary key, or part of it.
¨ Data element.
¨ Basic data type.
¨ Length.
¨ Check table.
¨ Short text, describing the field.
Additional information about the table can be displayed by selecting the corresponding functions from the menu or directly from the application toolbar, such as keys, indexes, or technical settings
Standard table:
The key access to a standard table uses a sequential search. The time required for an access is linearly dependent on the number of entries in the internal table.
You should usually access a standard table with index operations.
Sorted table:
The table is always stored internally sorted by its key. Key access to a sorted table can therefore use a binary search. If the key is not unique, the entry with the lowest index is accessed. The time required for an access is logarithmically dependent on the number of entries in the internal table.
Index accesses to sorted tables are also allowed. You should usually access a sorted table using its key.
Hash table:
The table is internally managed with a hash procedure. All the entries must have a unique key. The time required for a key access is constant, that is it does not depend on the number of entries in the internal table.
You cannot access a hash table with an index. Accesses must use generic key operations (SORT, LOOP, etc.).
Index table:
The table can be a standard table or a sorted table.
Index access is allowed to such an index table. Index tables can be used to define the type of generic parameters of a FORM (subroutine) or a function module.
Just have a look at these links:
http://help.sap.com/saphelp_nw04/helpdata/en/90/8d7304b1af11d194f600a0c929b3c3/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/74/83015785d811d295a800a0c929b3c3/frameset.htm
Regards
Sreeni

How can I get data in flat file from Pool table and cluster table ?

Hi,
I am working in one Achiving project. My requirement is to get data into flat file from Cluster table and pool table.
Is there any tool avilable to download data into flat file from pool table and cluster table ?
if table name given in the selection screen then data will be downloaded into flat file.
waiting for quick response.
Best Regards,
Bansidhar

Data cannot be retrived directly form the cluster table
as the Cluster results are stored in Cluster Key say for example PCLkey
and form that Key we need to fetch the data
these clustes are not the part of PNP or PNPCE tables
for ur info kindly check

Reg: Fact table and Dimension table in Data Warehousing -

Hi Experts,
I'm not exactly getting the difference between the criteria which decide how to create a Fact table and Dimension table.
This link http://stackoverflow.com/questions/9362854/database-fact-table-and-dimension-table states :
Fact table contains data that can be aggregate.
Measures are aggregated data expressions (e. Sum of costs, Count of calls, ...)
Dimension contains data that is use to generate groups and filters.
This's fine but how does one decide which columns to consider for Fact table and which columns for Dimension table?
Any help is much appreciated.
Pardon me if this's not the correct place for this question. My first question in the new forum.
Thanks and Regards,
Ranit Biswas

ranitB wrote:
But my main doubt was - what is the criteria to differentiate between columns for Fact tables and Dimension tables? How can one decide upon the design?
Columns of a fact table will often be 'scalar' attributes of the 'fact' data item. A dimension table will often be 'compound' attributes of a 'fact'.
Consider employee information. The EMPLOYEE table can be a fact table. It might have scalar attribute columns such as: DATE_HIRED, STATUS, EMPLOYEE_ID, and so on.
Other related information that can't be specified as a single attribute value would often be stored in a 'dimension' table: ADDRESS, PHONE_NUMBER.
Each address requires several columns to define it: ADDRESS1, ADDRESS2, CITY, STATE, ZIP, COUNTRY. And an employee might have several addresses: WORK_ADDRESS, HOME_ADDRESS. That address info would be stored in a 'dimension' table and only the primary key value of the address record would be stored in the EMPLOYEE 'fact' table.
Same with PHONE_NUMBER. Several columns are required to define a phone number and each employee might have several of them. The dimension tables are used to help 'normalize' the data in the employee 'fact' table.
And that EMPLOYEE table might also be a DIMENSION table for other FACT tables. A DEVELOPER table might have an EMPLOYEE_ID column with a value that points to a 'dimension' row in the EMPLOYEE dimension table.

DATA BASE TABLE AND INTERNAL TABLE

Dear Friends,
please help me out in getting complete information about database table and internal table.
you can email me at < Removed by moderator - please maintain e-mail iDs in Business Card>
Message was edited by:
Arun Varadarajan

Hi Hazi,
DATABASE Tables :
This are the tables which are stored in the database (eg Oracle , informix , DB2 etc..) Physically. u can view it from T-codes SE11 or SE16. here in SE11 u can create ur own Transparent table.
for more information...
http://www.sapbrainsonline.com/TUTORIALS/TECHNICAL/dictionary_tutorial.html
Internal Tables.
While generating reports or other objects we are not modifying the database tables directly first we are selecting the data of the database table into the internal tables... so that we can reduce the database access time and network traffic .. which is highly needed in R/3 system..
internal tables are not exist phyiscally in the system. its like a array. the existance of the internal tables is upto the program execution in which u r declaring nd using it...
for more information..
http://www.sapbrainsonline.com/TUTORIALS/TECHNICAL/internaltables_tutorial.html
Hope it will solve ur problem..
Reward points if useful..
Thanks & Regards
ilesh 24x7

Inforation on Pool tables and cluster tables required.

I want to know about the pool tables and cluster tables like how to create them and how to look the tables associated with the given tables. Like for the table BSEG we have other tables linked BSID etc. I'm new to this concept please guide me.

Pooled Table:
A pooled table in R/3 has a many-to-one relationship with a table in the database (see Figures 3.1 and 3.2). For one table in the database, there are many tables in the R/3 Data Dictionary. The table in the database has a different name than the tables in the DDIC, it has a different number of fields, and the fields have different names as well. Pooled tables are an SAP proprietary construct.
When you look at a pooled table in R/3, you see a description of a table. However, in the database, it is stored along with other pooled tables in a single table called a table pool. A table pool is a database table with a special structure that enables the data of many R/3 tables to be stored within it. It can only hold pooled tables.
R/3 uses table pools to hold a large number (tens to thousands) of very small tables (about 10 to 100 rows each). Table pools reduce the amount of database resources needed when many small tables have to be open at the same time. SAP uses them for system data. You might create a table pool if you need to create hundreds of small tables that each hold only a few rows of data. To implement these small tables as pooled tables, you first create the definition of a table pool in R/3 to hold them all. When activated, an associated single table (the table pool) will be created in the database. You can then define pooled tables within R/3 and assign them all to your table pool.
Pooled tables are primarily used by SAP to hold customizing data.
Cluster Table:
A cluster table is similar to a pooled table. It has a many-to-one relationship with a table in the database. Many cluster tables are stored in a single table in the database called a table cluster.
A table cluster is similar to a table pool. It holds many tables within it. The tables it holds are all cluster tables.
Like pooled tables, cluster tables are another proprietary SAP construct. They are used to hold data from a few (approximately 2 to 10) very large tables. They would be used when these tables have a part of their primary keys in common, and if the data in these tables are all accessed simultaneously.
Table clusters contain fewer tables than table pools and, unlike table pools, the primary key of each table within the table cluster begins with the same field or fields. Rows from the cluster tables are combined into a single row in the table cluster. The rows are combined based on the part of the primary key they have in common. Thus, when a row is read from any one of the tables in the cluster, all related rows in all cluster tables are also retrieved, but only a single I/O is needed.
A cluster is advantageous in the case where data is accessed from multiple tables simultaneously and those tables have at least one of their primary key fields in common. Cluster tables reduce the number of database reads and thereby improve performance.
Restrictions on Pooled and Cluster Tables
1. Pooled and cluster tables are usually used only by SAP and not used by customers, probably because of the proprietary format of these tables within the database and because of technical restrictions placed upon their use within ABAP/4 programs. On a pooled or cluster table:
2. Secondary indexes cannot be created.
3. You cannot use the ABAP/4 constructs select distinct or group by.
4.You cannot use native SQL.
5.You cannot specify field names after the order by clause. order by primary key is the only permitted variation.
For creation of pooled /cluster table, have a look at below link.
http://help.sap.com/saphelp_erp2004/helpdata/en/81/415d363640933fe10000009b38f839/frameset.htm
For creation of table pool /cluster, have a look at below link.
http://help.sap.com/saphelp_erp2004/helpdata/en/81/415d363640933fe10000009b38f839/frameset.htm
Have a look at below link.
http://www.sap-img.com/abap/the-different-types-of-sap-tables.htm
Best Regards,
Vibha
*Please mark all the helpful answers

Oracle Data Compression on SID tables and Dimension Tables

Hello Community,
We have had great success with Oracle compression on ODS tables that are no longer loaded.
We'd now like to move on to other types of BW tables that are very large.
OSS Note 701235 provides answers to questions concerning the possible use of Oracle compression together with SAP BW.
But the Note does not give suggestions for (or against) Oracle compression on SID tables or Dimension tables.
I believe both table types would exhibit the same behaviour : mostly inserts of new SID IDs and new DIM IDs, but few updates to existing SID or Dimension records. If this is true, then both are good candidates for oracle compression.
Do you also agree that this is the typical behaviour for SID tables and dimension tables ? And that these types of tables are good candidates for Oracle compression in a large BW system ?
Thanks kindly!
Keith Helfrich

Hi all,
Although this is an old thread I stumbled on during my own investigations I can provide some answers to your questions.
Table candidates for compression are found by these criteria
 - Table size big enough?
 - Long lifetime of object planned ?
 - No or only rare structural changes for the table ?
 - u201EUpdateu201C rate low : is your data mostly kind of u201Cread onlyu201D ?
-- for the wideley used rolling window partition techniques of
 tables in BW this is not a problem: mostly INSERTu2019s in the
 current partition not affecting other partitions
BW tables that can benefit from compression (see SAP notes 105047,701235)
 - PSA tables with data that must be saved for a longer time
 - ODS change log (no Updates of old data, only Inserts of new data)
 - u201Ehistoricalu201C cubes wich get no changes in table structure anymore
Limitations
 - normal Insert or Update statements are stored ALWAYS in uncompressed
 format and must be compressed separately ( <= Oracle10g )
 - Slight CPU overhead of compression, butu2026
 -- CPU consumption is more than compensated by doing less I/O as
 for Bulk loads or parallel processing
 -- SAP BW transformations took a significant amount of CPU for
 overall load-time into cubes caused by the application server not
 the database
 - Table must have not more than 255 fields
 - Adding columns with an initial value or dropping columns require
 uncompression of the complete table (strongest limitation)
Consider all this above and you can decide that tables that going through UPDATE's are
not good candidates for compression or tables that can change it's structure (like
Fact- or DIM tables) .
Now, my questions to you:
Wich Oracle version do you use?
Wich tool do you use for Oracle compression?
BRspace (can you give an example ?)
ALTER ... MOVE COMPRESS
bye
yk

Generic extractors on pool table and Cluster tables

Good Afternoon all,
Can we create generic extractors on Cluster or pool Table. If yes Let me know how?
I am trying to create a Generic Extractor on BSEC Table but it is not allowing me to do this. It throws error that"Extraction from pool tables and cluster tables is not permitted"
Kindly guide me on this
Thanks,
Vaishali.

Hi
you cannot do generic extraction directly on pooled or cluster tables.
You can create a function module, then you can create a Generic Data source based on this..
Hope it helps,
Thanks,
Teja
Edited by: Teja badugu on Apr 15, 2008 12:24 PM

Deleted and adjusted the Master data table, sid table and text table

Deleted and adjusted the master data table, sid table and text table of an zinfoobject after removing and adding attributes to that zinfoobject and was trying to activate it and system was giving me messages that cannot activate infoobject something like this.
So, i deleted and adjusted the master data table, sid table and text table. Since then getting messages right after executing the query because in that query that infoobject is getting used.
So the messages i am getting is:
SID 9 for characteristic Zinfoobject could not be converted CL_RSDM_READ_MASTER_DATA->_SIDVAL_DIRECT_READ2
System error in program SAPLRRK0 and form MEGA_SORT_M_02-02- (see long text)
Please help me in fixing this whole thing.
Thanks
SAPBW

SAP BW,
After adjusting your Master Data IOBJ and deleting and reloading the data - run a change run to adjust the references to the SIDs and then see if your query runs - run program RSDDS_AGGREGATES_MAINTAIN from se38 and select your IOBJ in the next screen..
Arun
Assign points if useful
P.S I did notice that in your earlier post for the same topic - you have had 12 answers / suggestions Please maintain only one thread as previously suggested..
My 0.02
Message was edited by:
Arun Varadarajan

Import Table and Template Table

Hi all,
I have a question regarding Data Services Component. What are the difference between "Import Table" and "Template Table"?
Thanks,

Hi,
Template table means temporary table. It will take all the input data. We don't need to create this table. Import table means you are importing already created table. That means you had already defined the field names and field lengths. Hope this helps.
Thanks,

Relate Text Table and Value Table

hi all,
How to relate Text Table and Value Table ?
I need step by step process.
Thanks in advance.
Regards
Raj

Hi,
Text table - If you want to create TEXT table for any table then just need to create table with the key fields of the other table along with that we need to create 2 more fields - those are language field & description.
Value table - Any table can be attached as value table for the table, only thing is field relations should be there in that table.
for step by step process to create tables - check the below -
Go to SE11,
given ZTABLE name and Create.
In Delivery Maintainance Tab..
Choose Delivery class A
and Display/Maintaintance Allowed
Go to Fields tab.
Provide ur table fields with MANDT is first field for client dependent.
If there is QUAN, CURR type fields then u must provide reference to them.
Save and Activate.
Click on Technical Settings
Data Class APPLO
Size .. 0 (as per ur requirement.)
SAVE and Back.
Click on Utilities --> Table Maintainance Generator.
Authorization Group &NC&.
and provide function group for table maintainance ( u can create a function group in se37 )
click on Find Scr Number button.
select Propose Screen Number and Continue.
then Create...
Save and Back
Activate the table.
go to tcode SM30
give the table name and click on Maintain.
there u can enter values manually too.
Regards,
*DJ
Reward, if its useful

Does "Target table" and "Error Table" need to be in same DB as OWB's?

Similar Messages

Maybe you are looking for