Modify Dimension table record

Hi,
I want to modify master record ie Dimension table record. I am using READ_MBR_DATA method of if_uja_dim_data to get the records and modifying the records and passing the same internal table to WRITE_MBR_DATA method, i get sy-subrc as 0 and no error is returned but when i check the dimension table it is not updated.
After execution of WRITE_MBR_DATA method i used READ_MBR_DATA method to read the dimentions again i got the modified record, but when checked in master data table i found record with old data.
Has any one modified the master data before , request you to guide me in this regard.
Regards,
Ganesha
Edited by: ganesha.g_09 on Jul 21, 2011 8:13 PM

Hi,
If my guess is correct its just a refresh problem. The method you have chosen is a correct one. Once you run the method.... I think you are opening dimension member sheet to find out your newly modified/added member. Before you open your dimension member sheet click on refresh dimension member which you can find on the action pane. only then you click on dimension member sheet.... and now... you should be able to see the modified/added member IDs.
Hope this helps....
Happy to help always!!!
Regards,
Surya tamada

Similar Messages

Modify the standard records in database table

hi folks,
could u say me , how to modify the standard records(values) in database table.
For example in VBAP is one field like ZWERT(target value) , I wnat to modify the values of this field .
THANKS
KUMAR

Hi,
It's not advisable to modify the standard tables through program. If you want you can do using MODIFY.
MODIFY database_table FROM TABLE itab.
Thanks,
Sri.

Problem in modifying the existing record in table control

Hi Experts,
I have one table control.I have entered one record and save it.When I am modifying the same record a duplicate record is created.I need if I modify the same record that record should only modify.How to delete the duplicate record.

Hi,
In Flow logic.
LOOP .
MODULE tbc_modify ON CHAIN-REQUEST.
MODULE tbc_mark.
ENDLOOP.
In module.
MODULE tbc_modify INPUT.
MODIFY t_data
    FROM fs_data
   INDEX tbc-current_line.
IF sy-subrc NE 0.
    APPEND fs_data TO t_data.
ENDIF.
ENDMODULE.
MODULE tbc_mark INPUT.
DATA: tbc_wa2 LIKE LINE OF t_data.
IF tbc-line_sel_mode = 1
AND fs_data-mark = 'X'.
    LOOP AT t_data INTO tbc_wa2
     WHERE mark = 'X'.
      tbc_wa2-mark = ''.
      MODIFY t_data
        FROM tbc_wa2
        TRANSPORTING mark.
    ENDLOOP.                          .
ENDIF.
MODIFY t_data FROM fs_data
    INDEX tbc-current_line
    TRANSPORTING mark.
ENDMODULE.
Edited by: sapabap403 on Aug 31, 2011 9:29 AM

Change/modify Purchase info records (EINE table)

Hi,
Could you pls help to in providing FM to change/modify purchase info record.
I have tried to use FM - > ME_UPDATE_INFORECORD
and ME_DB_UPDATE_INFORECORDS. but, it's not working .
Kindly advice.
Regards,
Bharat

hi,
try report RM06IBI0 and read docu to that abap
A.

Dimension Table populating data

Hi
I am in the process of creating a data mart with a star schema.
The star schema has been defined with the fact and dimension tables and the primary and foreign keys.
I have written the script for one of the dimensions and would like to know when the job runs on a daily basis should the job truncate the table every day and rebuild the dimension table or should it only add new records to the table. If it should add only
new records to the table how do is this done?
I assume that the fact table job is run once a day and only new data is added to it?
Thanks

It will depend on the volume of your dimensions. In most of our projects, we do not truncate, we update only updated rows based on a fingerprint (to make the comparison faster than column by column), and insert for new rows (SCD1). For SCD2 we apply
similar approach for updates and inserts, and expirations in batch (one UPDATE for all applicable rows at the end of the package/ETL).
If your dimension is very large, you can consider truncating all data or deleting only affected modified rows (based on nosiness key) to later reload those, but you have to be carefully maintaining the same surrogate keys reference by your
existing facts.
HTH,
Please, mark this post as Answer if this helps you to solve your question/problem.
Alan Koo | "Microsoft Business Intelligence and more..."
http://www.alankoo.com

How to show current date in a column of dimension table in ssas

Hi,
I have 2 dimension tables (ALLWORK and YOURWORK) and 1 measure table (STATS). In ALLWORK dim table, I have 4 columns, one of them is END_DATE. Based on END_DATE and current date I want to create a named calculation field. To achieve this, I
want to show the current date in 5th column (of ALLWORK dim table) as calculated member (as named calculation wont show me correct date).
Problem is, I am not able to create the column in the dimension table. While creating the calculated member, I am not able to select the ALLWORK dimension table, it always selects MEASURE by default. Please help.
thanks
Tarique
thanks and regards Tarique Aslam

Hi Tarique,
According to your description, you want to add a column to your dimension to show the current date, right?
In data source view, we can add named calculation to your table. A named calculation is a SQL expression represented as a calculated column. This expression appears and behaves as a column in the table. A named calculation lets you extend the relational
schema of existing tables or views in a data source view without modifying the tables or views in the underlying data source.
Reference
http://msdn.microsoft.com/en-in/library/ms174859.aspx
http://devmau5.wordpress.com/2010/03/25/the-getdate-of-mdx/
If I have anything misunderstand, please point it out.
Regards,
Charlie Liao
TechNet Community Support

Should my dimension table be this big

Im in the process of building my first product dimension for a star schema and not sure if im doing this correctly. A brief explanation of our setup
We have products (dresses) made by designers for specific collections each of which has a range of colors and each color can come in many sizes. For our UK market this equates to some 1.9 million
product variants. Flattening the structure out to Product+designer+collection gives about 33,000 records but when you add all the colors and then all the colors sizes it pumps that figure up to 1.9million. My “rolled own” incremental ETL load runs
ok just now, but we are expanding into the US market and our projections indicate that our products variants could multiple 10 fold. Im a bit worried about performance of the ETL just now and in the future.
Is 1.9m records not an awful lot of records to incrementally load (well analyse) for a dimension table nightly as it is never mind what that figure may grow to when we go to US?
I thought of somehow reducing this by using a snowflake but would this not just reduce the number of columns in the dimensions and not the row count?
I then thought of separating the colors and size into their own dimension, but this doesn’t seem right as they are attributes of products and also I would lose the relationship between products, size & color I.e. I would have to go through the
fact table (which ive read is not a good choice.) for any analysis.
Am I correct in thinking these are big numbers for a dimension table? Is it even possible to reduce the number somhow?
Still learning so welcome any help.
Thanks

Hi Plip71,
In my opinion, It is always good to reduce the Dimension Volume as much as possible for better performance.
Is there any Hierarchy in you product Dimension?.. Going for a snowflake for this problem is a bad idea..
Solution 1:
From the details given by, It is good to Split the Colour and Size as seperate dimension. This will reduce the vloume of dimension and increase the column count in the fact(seperate WID has to be maintained in the fact table). but, this will improve the
performance of the cube. before doint this please check the layout requirement from the business.
Solution 2:
Check the distinct count of Item varient used in fact table. If it is very less, they try creating a linear product dimension. i.e, create an view for the product dimension doing a inner join with the fact table. so that only the used Dimension member will
be loaded in the Cube Product Dimension. hence volume is reduced with improvement in performance and stability of the cube.
Thanks in advance, Sorry for the delayed reply ;)
Anand
Please vote as helpful or mark as answer, if it helps Regards, Anand

What is '#Distinct values' in Index on dimension table

Gurus!
I have loaded my BW Quality system (master data and transaction data) with almost equivalent volume as in Production.
I am comparing the sizes of dimension and fact tables of one of the cubes in Quality and PROD.
I am taking one of the dimension tables into consideration here.
Quality:
/BIC/DCUBENAME2 Volume of records: 4,286,259
Index /BIC/ECUBENAME~050 on the E fact table /BIC/ECUBENAME for this dimension key KEY_CUBENAME2 shows #Distinct values as 4,286,259
Prod:
/BIC/DCUBENAME2 Volume of records: 5,817,463
Index /BIC/ECUBENAME~050 on the E fact table /BIC/ECUBENAME for this dimension key KEY_CUBENAME2 shows #Distinct values as 937,844
I would want to know why the distinct value is different from the dimension table count in PROD
I am getting this information from the SQL execution plan, if I click on the /BIC/ECUBENAME table in the code. This screen gives me all details about the fact table volumes, indexes etc..
The index and statistics on the cube is up to date.
Quality:
E fact table:
Table   /BIC/ECUBENAME
Last statistics date                  03.11.2008
Analyze Method               9,767,732 Rows
Number of rows                         9,767,732
Number of blocks allocated         136,596
Number of empty blocks              0
Average space                            0
Chain count                                0
Average row length                      95
Partitioned                                  YES
NONUNIQUE Index   /BIC/ECUBENAME~P:
Column Name                     #Distinct
KEY_CUBENAMEP                                  1
KEY_CUBENAMET                                  7
KEY_CUBENAMEU                                  1
KEY_CUBENAME1                            148,647
KEY_CUBENAME2                          4,286,259
KEY_CUBENAME3                                  6
KEY_CUBENAME4                                322
KEY_CUBENAME5                          1,891,706
KEY_CUBENAME6                            254,668
KEY_CUBENAME7                                  5
KEY_CUBENAME8                              9,430
KEY_CUBENAME9                                122
KEY_CUBENAMEA                                 10
KEY_CUBENAMEB                                  6
KEY_CUBENAMEC                              1,224
KEY_CUBENAMED                                328
Prod:
Table   /BIC/ECUBENAME
Last statistics date                  13.11.2008
Analyze Method                      1,379,086 Rows
Number of rows                       13,790,860
Number of blocks allocated       187,880
Number of empty blocks            0
Average space                          0
Chain count                              0
Average row length                    92
Partitioned                               YES
NONUNIQUE Index /BIC/ECUBENAME~P:
Column Name                     #Distinct
KEY_CUBENAMEP                                  1
KEY_CUBENAMET                                 10
KEY_CUBENAMEU                                  1
KEY_CUBENAME1                            123,319
KEY_CUBENAME2                            937,844
KEY_CUBENAME3                                  6
KEY_CUBENAME4                                363
KEY_CUBENAME5                            691,303
KEY_CUBENAME6                            226,470
KEY_CUBENAME7                                  5
KEY_CUBENAME8                              8,835
KEY_CUBENAME9                                124
KEY_CUBENAMEA                                 14
KEY_CUBENAMEB                                  6
KEY_CUBENAMEC                                295
KEY_CUBENAMED                                381

Arun,
The cube in QA and PROD are compressed. Index building and statistics are also up to date.
But I am not sure what other jobs are run by BASIS as far as this cube in production is concerned.
Is there any other Tcode/ Func Mod etc which can give information about the #distinct values of this Index or dimension table?
One basic question, As the DIM key is the primary key in the dimension table, there cant be duplicates.
So, how would the index on Ftable on this dimension table show #distinct values less than the entries in that dimension table?
Should the entries in dimension table not exactly match with the #Distinct entries shown in
Index /BIC/ECUBENAME~P on this DIM KEY?

Dimension key 16 missing in dimension table /BIC/DZPP_CP1P

Hi all,
I have a problem with an infocube ZPP_CP1. I am not able to delete nor load any data. It was working fine till some time back.
Below is the outcome of running RSRV check on this cube. I tried to run the error correction in RSRV. But n o use
Please help.
Dimension key 16 missing in dimension table /BIC/DZPP_CP1P
Message no. RSRV018
Diagnosis
The dimension key 16 that appears as field KEY_ZPP_CP1P in the fact table, does not appear as a value of the DIMID field in the dimensions table /BIC/DZPP_CP1P.
There are 17580 fact records that use the dimension key 16.
The facts belonging to dimension key 16 are therefore no longer connected to the master data of the characteristic in dimension.
Note that errors that are reported for the package dimension are not serious (They are thus shown as warnings (yellow) and not errors (red). When deleting transaction data requests, it can arise that the associated entries in the package dimension have already been deleted. As a result, the system terminates when deleting what can be a very large number of fact records. At the moment, we are working on a correction which will delete such data which remains after deletion of the request. Under no circumstances must you do this manually. Also note that data for request 0 cannot generally be deleted.
The test investigates whether all the facts are zero. If this is the case, the system is able to remove the inconsistency by deleting these fact records. If the error cannot be removed, the only way to re-establish a consistent status is to reconstruct the InfoCube. It may be possible for SAP to correct the inconsistency, for which you should create an error message.
Procedure
This inconsistency can occur if you use methods other than those found in BW to delete data from the SAP BW tables (for example, maintaining tables manually, using your own coding or database tools).

Hi Ansel,
There has been no changes in the cube. I am getting this problem in my QA server. So I retransported the cube again from Dev to QA. But did not help me..
Any other ideas??
Regards,
Adarsh

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.

How to design fact and dimension tables

Hi Team,
Please provide me some useful links!!
I have a Parent & Child table each has around 8 Million records (1 to many relation). These two tables need relation with many other master tables to generate any report.
I want to desing a fact and dimension(s) for this parent & Child tables.
Please help me what are the things I have to keep in mind when desingning datawarehouse fact and dimension tables?
Thanks,
Ali

Hi, any update on this?

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.

Modify database table from internal table

Hi All,
I need to update database table from internal table which is having around 30000 records.
I am using MODIFY tabname FROM TABLE int_tabname...
Using this statement, I can modify the databse records very well. But user has some additional requirement.
He wants that the table should be modified from the internal table and after modification we should have the erroneous records to be displayed if any.
e.g. if 1500 records out of 30000 are erroneous then only 28500 records should be updated and 1500 records should be displayed as erroneous records so that the user can correct them and use them again for executing the program.
Is there any FM which imports the database table name and internal table, modifies the database and exports an internal tanle with erroneous records?
Any help will be appriciated,
Regards,
Neha

Hi
modifying datbase table useing internal table
advises before updating this datbase table plz lock that table to avoid incosistency
write the logic for modifying
Modify the database table as per new dunning procedure
MODIFY fkkvkp FROM TABLE lt_fkkvkp .
and finally unlock the table
example
*To lock table for further operations
constants: lc_tabname TYPE rstable-tabname VALUE 'FKKVKP' . "FKKVKP
CALL FUNCTION 'ENQUEUE_E_TABLE'
 EXPORTING
 tabname = lc_tabname
 EXCEPTIONS
 foreign_lock = 1
 system_failure = 2
 OTHERS = 3.
IF sy-subrc EQ 0.
To fetch all the contract accounts for customers of the segment
Households/SME.
 PERFORM fetch_contract_accounts using lc_tabname .
ENDIF. " IF sy-subrc EQ 0.
*wrote the logic
Modify the database table as per new dunning procedure from internal table
MODIFY fkkvkp FROM TABLE lt_fkkvkp .
*unlock the tbale
CALL FUNCTION 'DEQUEUE_E_TABLE'
 EXPORTING
 TABNAME = uc_tabname .
Reward if usefull

Another User Modified the table

Hi,
I have a user defined form, which is bound to Master-Data UDO.
I have matrices in the form which is bound to its child objects.
Following problem happens once in a while:
When I press update button, I get the error message 'Another User Modified the table'.
This is not consistent, but happens once in a while.
My SBO version is 2007.
In what situations you will get the error - "Another User Modified the table" ?
Please help me with this.
I'll appreciate your help.
Thanks.
-Geetha

Hi Mahendra,
Thanks for your reply.
In my case, I take back-up of the database from client site and bringing into our in-house.
If clients complained about record# 25, then the same record# has the 'Another user' issue in in-house also. (By record# I mean the Master UDO DocEntry#).
So, I think the locking is stored in the database, rather than in a PC specific place.
Please tell me any ideas you get in this angle.
Regards,
Geetha

Problem in modifying a table through modify statement

Hi,
I am trying to update a 'Z' table in which there are 5 fields comprising of primary key. Out of them 2 key fields are defined as a part of seconadry index with 'Unique' option selected.
As per the requirement, I am trying to update the table using modify statement so whenever this statement occurs it will check the primary keys and accordingly try to modify a record or insert a new record.
But as there is Unique Index defined on 2 of the key fields the Modify query is

Hi,
Your syntax for MODIFY is not correct.
As other friends suggested you can have index and you can modify the internal table.
Whenever we are modifying internal table inside LOOP, we can omit index as system will take current row by default. So MODIFY statement should be written as follows:
MODIFY T_ITPO5 from W_ITPO5 transporting AUFNR
You can LOOP FROM INDEX also for the same to improve performance.
data: wv_index like sy-tabix.
sort T_ITPO5 by aufnr.
sort T_ITPO4 by aufnr.
wv_index = 1.
LOOP AT T_ITPO5 INTO W_ITPO5.
     LOOP AT T_ITPO4 INTO W_ITPO4 from wv_index.
     if W_ITPO4-aufnr eq W_ITPO5-aufnr.
          IF ITPO4-NTGEW 0 .
              CALL FUNCTION 'ZGET_ITEM_WEIGHT'
                EXPORTING
                   P_BUID = W_ITPO4-WERKS
                   P_ITEMID = W_ITPO4-MATNR
                   P_QTY = 1
                   P_UOM = W_ITPO4-MEINS
                   P_UOM1 = 'KG'
               IMPORTING
                  P_RETVAL = W_ITPO4-WTKG.
TOTWT1 = W_ITPO4-WTKG * W_ITPO4-MENGE.
IF W_ITPO4-BWART = '261'.
W_ITPO5-I_QTY = W_ITPO5-I_QTY + TOTWT1.
ELSEIF W_ITPO4-BWART = '101' OR W_ITPO4-BWART = '531'.
W_ITPO5-I_QTY = W_ITPO5-I_QTY - TOTWT1.
ENDIF.                    " IF W_ITPO4-BWART = '261'.
endif.
elseif W_ITPO4-aufnr gt W_ITPO5-aufnr.
   move sy-tabix to wv_index.
   exit.
endif.                      " if W_ITPO4-aufnr eq W_ITPO5-aufnr.
ENDLOOP.
MODIFY T_ITPO5 FROM W_ITPO5 transporting aufnr.
ENDLOOP.

Modify Dimension table record

Similar Messages

Maybe you are looking for