Issue with P table and X Table of master data ZGN_PROD

Hi Experts,
I am facing issue when I carried out existence of values for navigation attributes in characteristic ZGN_PROD in RSRV. Its showing "Characteristic ZGN_PROD : 74 data records were incorrect"
Please tell me how to correct the error without deleting and reloading the masterdata.
Thanks in advance for all your help.
Regards,
Surya.

After executing all the elementary corrections on the InfoObject, It's giving me the error message
" The size check establishes that the newly created X/Y table is not the same size as the P/Q table from which it has been created.
This is caused by missing SID entries in the navigation attributes."
Please advice.

Similar Messages

I HAVE A SOURCE TABLE WITH 10 RECORDS AND TARGET TABLE 15 RECORDS. MY WUESTION IS USING WITH THE TABLE COMPARISON TRANSFORM I WANT TO DELETE UNMATCHED RECORDS FROM THE TARGET TABLE ??

I HAVE A SOURCE TABLE WITH 10 RECORDS AND TARGET TABLE 15 RECORDS. MY QUESTION IS USING WITH THE TABLE COMPARISON TRANSFORM .I WANT TO DELETE UNMATCHED RECORDS FROM THE TARGET TABLE ?? HOW IT IS ??

Hi Kishore,
First identify deleted records by selecting "Detect deleted rows from comparison table" feature in Table Comparison
Then Use Map Operation with Input row type as "delete" and output row type as "delete" to delete records from target table.

Issue with recursive join and filter records

I am having an issue with recursive join and filtering records for the following rules. The table, sample records, test script and rules are as below
drop table PC_COVKEY_PD;
create table PC_COVKEY_PD (
PC_COVKEY varchar(50),
COVERAGE_NUMBER varchar(3),
SEQUENCE_ALPHA varchar(3),
TRANSACTION_TYPE varchar(3),
COV_CHG_EFF_DATE date,
TIMESTAMP_ENTERED timestamp
delete from PC_COVKEY_PD;
commit;
Insert into PC_COVKEY_PD values ('10020335P8017MT0010012','001','001','02',to_date('01/FEB/2010','DD/MON/RRRR'),to_timestamp('02/JAN/2010 01:55:59.990216 AM','DD/MON/RRRR HH12:MI:SS.FF6 AM'));
Insert into PC_COVKEY_PD values ('10020335P8017MT0050012','005','001','02',to_date('01/FEB/2010','DD/MON/RRRR'),to_timestamp('02/JAN/2010 01:56:00.268099 AM','DD/MON/RRRR HH12:MI:SS.FF6 AM'));
Insert into PC_COVKEY_PD values ('10020335P8017MT0010032','001','003','03',to_date('14/JAN/2011','DD/MON/RRRR'),to_timestamp('14/JAN/2011 04:25:19.018217 PM','DD/MON/RRRR HH12:MI:SS.FF6 AM'));
Insert into PC_COVKEY_PD values ('10020335P8017MT0010042','001','004','03',to_date('21/JAN/2011','DD/MON/RRRR'),to_timestamp('21/JAN/2011 04:00:31.719444 PM','DD/MON/RRRR HH12:MI:SS.FF6 AM'));
Insert into PC_COVKEY_PD values ('10020335P8017MT0050022','005','002','03',to_date('21/JAN/2011','DD/MON/RRRR'),to_timestamp('21/JAN/2011 04:02:48.953594 PM','DD/MON/RRRR HH12:MI:SS.FF6 AM'));
commit;
--select * from PC_COVKEY_PD order by COV_CHG_EFF_DATE,TIMESTAMP_ENTERED;
PC_COVKEY          COVERAGE_NUMBER     SEQUENCE_ALPHA     TRANSACTION_TYPE     COV_CHG_EFF_DATE     TIMESTAMP_ENTERED
10020335P8017MT0010012          001     001                  02                          01/FEB/2010            02/JAN/2010 01:55:59.990216 AM
10020335P8017MT0050012          005     001                  02                      01/FEB/2010            02/JAN/2010 01:56:00.268099 AM
10020335P8017MT0010032          001     003                  03                      14/JAN/2011            14/JAN/2011 04:25:19.018217 PM
10020335P8017MT0010042          001     004                  03                      21/JAN/2011            21/JAN/2011 04:00:31.719444 PM
10020335P8017MT0050022          005     002                  03                      21/JAN/2011             21/JAN/2011 04:02:48.953594 PM
*/Rule;
Every PC_COVKEY, query should recursively join and generate set of records depending on latest SEQUENCE_ALPHA for the coverage number at that point of time. For ex,
for 10020335P8017MT0010042 (4 row) should generate 2 records
1. 10020335P8017MT0010042001004 (PC_COVKEY || COVERAGE_NUMBER || latest SEQUENCE_ALPHA--004 for cover 001), SEQUENCE_ALPHA 001 for cover 001 is not the latest for 10020335P8017MT0010042.
2. 10020335P8017MT0010042005001 (coverage number 005, and latest sequence alpha-001 for cover 005).
SEQUENCE_ALPHA 002 for cover 005 is not the latest for 10020335P8017MT0010042 as it happened later stage.
for 10020335P8017MT0050022 (5 row) should generate 2 records as
1. 10020335P8017MT0050022001004 (PC_COVKEY || COVERAGE_NUMBER || latest SEQUENCE_ALPHA--004 for cover 001),
2. 10020335P8017MT0010042005002 (coverage number 005, and latest sequence alpha-002 for cover 005)
WITH SNAPSHOT_CVR_CTP as (
SELECT pcd1.PC_COVKEY,
       pcd1.PC_COVKEY||pcd2.COVERAGE_NUMBER||pcd2.SEQUENCE_ALPHA as cov_key,
       pcd2.COVERAGE_NUMBER,
       pcd2.SEQUENCE_ALPHA,
       pcd2.COVERAGE_NUMBER||pcd2.SEQUENCE_ALPHA as CVRSEQ,
       max(pcd2.COVERAGE_NUMBER||pcd2.SEQUENCE_ALPHA) over (partition by pcd1.PC_COVKEY, pcd1.COVERAGE_NUMBER
       order by pcd2.COV_CHG_EFF_DATE, pcd2.TIMESTAMP_ENTERED) as MaxSeq,
       pcd2.COV_CHG_EFF_DATE,
       pcd2.TIMESTAMP_ENTERED
FROM
PC_COVKEY_PD pcd1,
PC_COVKEY_PD pcd2
select * from SNAPSHOT_CVR_CTP SC
WHERE sc.PC_COVKEY = '10020335P8017MT0010042' -- 4 row
--AND COVERAGE_NUMBER||SC.MAXSEQ = COVERAGE_NUMBER||SEQUENCE_ALPHA
ORDER BY TIMESTAMP_ENTERED
PC_COVKEY     COV_KEY     COVERAGE_NUMBER     SEQUENCE_ALPHA     CVRSEQ          MAXSEQ     COV_CHG_EFF_DATE     TIMESTAMP_ENTERED
10020335P8017MT0010042     10020335P8017MT0010042001001     001     001     001001     001001     01/FEB/2010     02/JAN/2010 01:55:59.990216 AM
10020335P8017MT0010042     10020335P8017MT0010042005001     005     001     005001     005001     01/FEB/2010     02/JAN/2010 01:56:00.268099 AM
10020335P8017MT0010042     10020335P8017MT0010042001003     001     003     001003     005001     14/JAN/2011     14/JAN/2011 04:25:19.018217 PM
10020335P8017MT0010042     10020335P8017MT0010042001004     001     004     001004     005001     21/JAN/2011     21/JAN/2011 04:00:31.719444 PM
10020335P8017MT0010042     10020335P8017MT0010042005002     005     002     005002     005002     21/JAN/2011     21/JAN/2011 04:02:48.953594 PM
I am trying to filter row using MAXSEQ but at the moment MAXSEQ values are not coming as expected. I expect following value for COV_KEY combination
COV_KEY                                         MAXSEQ
10020335P8017MT0010042001001     001004
10020335P8017MT0010042005001     005001 -- match
10020335P8017MT0010042001003     001004
10020335P8017MT0010042001004     001004 -- match
10020335P8017MT0010042005002     005001Would appreciate if anyone can get MAxSEQ as expected.

Something like..
with dist_cov_numbers as
select distinct coverage_number cov_number
from PC_COVKEY_PD
all_data as
select pcd.*,d.cov_number new_coverage_number,
         max(decode(coverage_number,d.cov_number,sequence_alpha))
              over( partition by d.cov_number
                    order by COV_CHG_EFF_DATE,TIMESTAMP_ENTERED
                              ) max_seq
from PC_COVKEY_PD pcd,dist_cov_numbers d
select pc_covkey,pc_covkey||new_coverage_number||max_seq new_key,
       pc_covkey||coverage_number||sequence_alpha actual_key
from all_data
order by COV_CHG_EFF_DATE, TIMESTAMP_ENTERED;
PC_COVKEY                   NEW_KEY                           ACTUAL_KEY
10020335P8017MT0010012      10020335P8017MT0010012001001      10020335P8017MT0010012001001
10020335P8017MT0010012      10020335P8017MT0010012005         10020335P8017MT0010012001001
10020335P8017MT0050012      10020335P8017MT0050012001001      10020335P8017MT0050012005001
10020335P8017MT0050012      10020335P8017MT0050012005001      10020335P8017MT0050012005001
10020335P8017MT0010032      10020335P8017MT0010032001003      10020335P8017MT0010032001003
10020335P8017MT0010032      10020335P8017MT0010032005001      10020335P8017MT0010032001003
10020335P8017MT0010042      10020335P8017MT0010042005001      10020335P8017MT0010042001004
10020335P8017MT0010042      10020335P8017MT0010042001004      10020335P8017MT0010042001004
10020335P8017MT0050022      10020335P8017MT0050022005002      10020335P8017MT0050022005002
10020335P8017MT0050022      10020335P8017MT0050022001004      10020335P8017MT0050022005002
10 rows selected Edited by: jeneesh on Nov 22, 2012 10:54 AM

Backup and restore georaster table and rdt table by image id

Hellow everyone,
I want to backup my georaster table and rdt table by the Specified image id and also can use these georater rows to restore? How can I do? the geraster table structure is as follows:
image_table
id NUMBER,
filename VARCHAR2(255),
raster SDO_GEORASTER
Best Regards,
Lin

ylin wrote:
Hellow everyone,
I want to backup my georaster table and rdt table by the Specified image id and also can use these georater rows to restore? How can I do? the geraster table structure is as follows:
image_table
id NUMBER,
filename VARCHAR2(255),
raster SDO_GEORASTER
Best Regards,
LinIf I understand you correctly, There is no specific issue if you want to export table with spatial data - It is the same as with normal tables.

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...

Difference between Temp table and Variable table and which one is better performance wise?

Hello,
Anyone could you explain What is difference between Temp Table (#, ##) and Variable table (DECLARE @V TABLE (EMP_ID INT)) ?
Which one is recommended to use for better performance?
also Is it possible to create CLUSTER and NONCLUSTER Index on Variable table?
In my case: 1-2 days transactional data are more than 3-4 Millions. I tried using both # and table variable and found table variable is faster.
Is that Table variable using Memory or Disk space?
Thanks Shiven:) If Answer is Helpful, Please Vote

Check following link to see differences b/w TempTable & TableVariable: http://sqlwithmanoj.com/2010/05/15/temporary-tables-vs-table-variables/
TempTables & TableVariables both use memory & tempDB in similar manner, check this blog post: http://sqlwithmanoj.com/2010/07/20/table-variables-are-not-stored-in-memory-but-in-tempdb/
Performance wise if you are dealing with millions of records then TempTable is ideal, as you can create explicit indexes on top of them. But if there are less records then TableVariables are good suited.
On Tables Variable explicit index are not allowed, if you define a PK column, then a Clustered Index will be created automatically.
But it also depends upon specific scenarios you are dealing with , can you share it?
~manoj | email: http://scr.im/m22g
http://sqlwithmanoj.wordpress.com
MCCA 2011 | My FB Page

Fact Table and Dimension Tables

Hi Experts, I'm creating custom InfoCubes for data coming from non-SAP source systems. I have two InfoCubes. Tha data is coming from like 10 tables. I have 10 DataSources created fo this and the data will be consolidated in Standard DSO before it will flow into 2 InfoCubes.
Now client wants to know before how much data will be there in InfoCubes in Fact table nad Dimension tables in both the InfoCubes. I have the total size of all the 10 tables from the sources given to me by the DBA. I wan not sure how I can convert that info for Fact table and Dimension table as I have not yet created these Infocubes.
Please help me with this on how I should address this.

hi,
The exact data will be hard to give however you can reach at a round figure in your case.
You are consolidating the data from the tables that means that there is relation between the tables. Arrive at a rough figure based on the relation and the activity you are performing while consolidating the data of the tables.
For example, let us say we want to combine data for sales order and deliveries in a DSO.
Let Sales order has 1000 records and Delivery has 2000 records. Both the tables have a common link (Sales Order).In DSO you are combining the data that means the data will be at the most granular level consist of Delivery data, so the maximum no of records which the consolidated DSO can have is 2000.
regards,
Arvind.

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.

Check table and value table -Example

Hi Experts
Please give me the step by step procedure to create the check table and value table, and how to work on it.
Thanks in advance.
Regards
Rajaram

Hi
Check Table is for Field level Validation whereas Value table is for Domain Level Validations.
Value Table proposes table for check table.
I think you are clear with this.
more elaborate.
Check Table
The Check Table is the table used by system to check if a data exist or not exist.
While creating a table if you want to be sure that a field can have some values
and these are in a certain table, you can give IT this table as CHECK TABLE.
Value Table
This is maintained at Domain Level.
When ever you create a domain , you can entered allowed values. For example you go to Domain SHKZG - Debit/credit indicator.
Here only allowed values is H or S.
When ever you use this Domain, the system will forces you to enter only these values.
This is a sort of master check . .
To be maintained as a customization object.
This mean that if you want to enter values to this table you have to create a development request & transport the same.
Differences:
1)check table will carry out the check for input values for the table field being entered in any application
and value table will provide values on F4 help for that table field.
2)The check table defines the foreign keys and is part of the table definition.
The value table is part of the domain definition.
check table is validation at field level.
value table is at domain level.
Value table is defined at the domain level and is used to provide F4 help for all the fields which refer to that domain.
Check table is defined against a field in SE11 if you want the values in that field to be checked against a list of valid values. For e.g. if you are using the field matnr in a table you could define MARA as the check table.
Also while defining a check table SAP proposes the value table as check table by default. Referring to the previous example if you tried to define a check table for the matnr field SAP would propose MARA as the check table.
1. what is the purpose / use ?
-- so that the user can select values
from some master table , for that field !!!!
2. This is done by
CHECK TABLE (foreign key concept)
(and not value table)
3. When we create a check table for a field,
then
some DEFAULT table is PROPOSED
4. that DEFAULT table is nothing
but PICKED up from the domain of that field,
and shown from the value of VALUE TABLE.
CHECK TABLE -it is a parent table.
for example..
i have two tables ZTAB1 and ZTAB2.
I have one common field in both the tables,i can make any ztable to be the check table .If i make Ztab1 to be the check table then when i have to make an entry in ztab2 i will check whether ztab1 is having that value or not..
its also field level checking..
Valuetable-It is nothing but default check table.
one parent can have n number of child tables.For example
For ztable we have zchild1 and zchild2 tables r there.
Its domain level checking..When zchild2 uses the same domain as used by zchild1 then the system automatically generates a popup saying a check table already exists would u want to maintain it.
go to domain and then press the value tab u can see the valuetable at the end...
Please refer the links below,
d/r b/n check and value table?
wjhat is the exct difference between check table and value table
what is the check table and value table
check table and value table
Re: wjhat is the exct difference between check table and value table
http://www.sap-img.com/abap/difference-between-a-check-table-and-a-value-table.htm

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.

<b>Pooled Table:</b>
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.
<b>Cluster Table:</b>
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

To find the size of the fact table and dimension table

Hi experts,
Can anyone plz tell me if i want to find size of the fact table and size of the dimension table to find cardinality and line item do we first build statistics then find size by transaction DB02 or any other method we have?
Thanks in advance

Hi ,
Please go to Tcode DB02 >Space>Table and Indexes.Give your table name or pattern (like /BIC/F* for gettinf all the Fact tables)
.This will give you sizes of all the table.
Also if you want to get list like TOP 30 Fact tables and Dimension Table.Please use TCode ST14, this will give a desired output with all the required details.
-Vikram

What is FACT table and FLAT table?

Hello,
         Kindly tell me what is mean by FACT table and FLAT table and how it is use in the BI system ?also tell me can i see these table in the system ?if yes then please tell me the procedure to see the content of the FACT and FLAT table.   And also tell me about the SID table and how to see it.

Cube consists of Fact tables and Dimension tables.
The structure of these tables are "Flat".
Cube consists of two factables... 'F' - Fact table and 'E' - Fact table.
The naming convention will be..
/BIC/F<..Cube name..>   for F Fact table
/BIC/E<..Cube name..>   for E Fact table
Eg: for cube "EMPLOYEE" the names are..
/BIC/FEMPLOYEE
/BIC/EEMPLOYEE
The dimention tables have naming convention..
/BIC/D....
You can check these tables in SE11 or you can use the transaction LISTSCHEMA and then provide the Cube name.
SID's tables are used to link the master data with the dimention tables.

REG:Internal table and Database table

Hi Xperts,
Can you tell me /give me a sample code so as to
Compare the data present in the database table and internal table.i.e
Wheher the data in the db table matches with the data in the internal table
Thanks.

Hello,
First make sure that data is there in the internal table
TABLES : Declare your table example MARA, VBAK etc
TYPES: BEGIN OF ITAB1,
Declare your fields here
example
v_mat(10) type c,
v_code(5) type I,
END OF ITAB1.
IF NOT ITAB[] is INITIAL.
LOOP AT
END IF.
To compare the data with DB tables, read the database table and copy into the internal table ITAB2
Then compare the ITAB and ITAB1
IF ITAB1[] = ITAB2[]
END IF
See these links for [Creating Internal Tables|http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3660358411d1829f0000e829fbfe/content.htm]
[Comparing Internal Tables|http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3841358411d1829f0000e829fbfe/content.htm]
See this for more about [Processing Internal Tables|http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb36ae358411d1829f0000e829fbfe/content.htm]
Declaring the internal table in ABAP objects
[Thanks|http://chandranonline.blogspot.com/]
[Chandran|http://chandranonline.blogspot.com/]

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

Ratio between Fact table and Dimention table for a Infocube

Hi All,
How can we reduce the Ratio between Fact table and Dimention table for a Infocube below 20%.??
please give suggestions

Hi
Reduce Ratio??
The Ratios are dependent on the Fact Table, and the Dimension table that is modeled for your Cube.
You cannot change ratio individually, but can set the Line Item Dimension , provided you have only one char object is taking much space and bulky with much percentage, based on your requirement. You can always use fine tuning objects.
Please be more specific while posting, to get right help from sdn.
Hope it helps

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

Issue with P table and X Table of master data ZGN_PROD

Similar Messages

Maybe you are looking for