Length of the attribute changed????

Hi All
we have a infobject(0Material as a charastics) and we have 3 attributes for this infobject.Now we added 1 attribute( ZMat_Pl)and the length of that attribute is 15 and transported to production.No data is there
Now our client requirement changed and he says for newly added attribute ( ZMat_Pl)the length shoulod be 12.(not 15)
Now if i change this in Development and if I transport this if it matters anyhting(I mean is this changes will reflect anywhere).
What should I precheck before I transport.
Regards
Balji

Hi,
As you said if there is no Data for this Attribute,you can change the length and transport it to production..However check in Quality system if everything is fine then release it to Production.
whenver you make changes to existing InfoObejcts/adding InfoObjects check the status of InfoCube ,Update rules,InfoSource,Transfer rules...etc...make sure all are active.if not,Then activate all( here its better to write changes to A TR without collecting them manually) and test with some test data and Transport.

Similar Messages

Hi i have 50 infoobjects as part of my aggregates and in that 10 infoobjects have received changes in masterdata.so in my process chain the Attribute change run in running for a long time.can i kill the job and repeat the same.

Hi i have 50 infoobjects as part of my aggregates and in that 10 infoobjects have received changes in masterdata.so in my process chain the Attribute change run in running for a long time.can i kill the job and repeat the same.

Hi,
I believe this would be your Prod system, so don't just cancel it but look at the job log. If it is still processing then don't kill it and wait for the change run to complete but if you can see that nothing is happening and it is stuck for a long time then you can go ahead and cancel it.
But please be sure, as these kind of jobs can create problems if you cancel them in the middle of a job.
Regards,
Arminder Singh

ABAP program to add in the process chain before the attribute change run

Hi
I need a ABAP program to add in the process chain before the attribute change run(process) to avoid the locks, can any one send me the program
Regards,
Satish

I am not sure of any standard program .... but you can write your own... should be a small one..
you can check if the table RSDMDENQ has entry for your InfoObject... if yes, then its locked.. if not.. its not locked

What's the attribute change run? and the common sequence of a process chain

The BW consultants of our company were gone and they used to create a complicated process chain, and we can see the sequences in the process chain is:
Load different Master data attributes -> Attribute Change Run -> Load different master text data -> Load different transaction data.
The sequence of the above process chain is pretty common, right? We are pretty new to process chain and we are appreciated if someone could elaborate this and please also let us know the functionality of the Attribute Change Run variant here.
We will reward your points and Thanks in advance!

Hi,
When ever u load the masterdata then it has to be activated so that the data will be available for the reporting. The Attribute change run will does the same thing. This will be applied to the Attributes and Hierarchies.
for creation of process chains u can refer the link..
follow the steps which is given by me..
Re: Process chain in Generic extracter
and refer these also..
http://help.sap.com/saphelp_bw32/helpdata/en/65/163d3873130057e10000009b38f842/content.htm
http://help.sap.com/saphelp_bw32/helpdata/en/8f/c08b3baaa59649e10000000a11402f/content.htm
And u can refer some of the links in help.sap.com
Regards-
MM
Dont forget to assign points if it helps, it is the right way to say thanks.
Message was edited by: vishnuC

What is the back ground job when we run an Attribute Change run ?

Dear One´s,
What is the back ground job when we run an Attribute Change run ?
Thanks in advance,
Raj

Hi Raj,
1. If the attribute change run is triggered through process chain the job name is 'BI_PROCESS_ATTRIBCHAN'
2. If the change run is triggered from RSA1> tools?Appl Heirarchy/Attribute changerun then the job name starts with BI_STRU*
3. If you trigger the program RSDDS_AGGREGATES_MAINTAIN from SE38 then the job name will be RSDDS_AGGREGATES_MAINTAIN
Hope this helps...

Attribute change run process doesn't run in the chain

Hello everyone,
I have implemented a process chain with multiple parallel processes (12, like the batch processes in the application server) and I have put for each stream a loading of master data followed by the attribute change run process. When I run my chain then I find that one o two Attribute change run process doesn't run (the InfoObject chosen seem to be random!). The chain remain in yellow color. Can you help me anyone about this question?
Regards,
Francesco

Couple of thing you should keep in mind while loading master data.
if two loads are targeted to the same infoobject they will collide and as a result the later load will fail.
it is a good practice to use only one Attribute change run in the end before you load master data. but if there are dependecies you can use several in series
Also when you set up Attribute change run make sure that Attribute change run will pickup only the particualr infoobject not all the objects in the Attribute change run list.

Effect of Full Attribute Extract on Aggregate Attribute Change Run

Because we extract data that does not trigger the change pointer on 0CUST_SALES we do a FULL extract of this data daily instead of a DELTA. We recently created an aggregate which contains navigational attributes of 0CUST_SALES (namely Sales Office & Sales Group).
My question is does the system look to see if any information has changed between the new and old values or does it assume since there is a new version for every entry that 100% of the values have changed?
The reason I'm asking is BW appears to be rebuilding this aggregate from scratch each day instead of changing the aggregate for the few entries that actually changed.

I did a FULL extract for 0CUST_SALES in our QA system. It transferred 28617 records. When I look into the monitor > processing > data package 1 > update I see the following:
3 data records in table /BI0/XCUST_SALES marked for deletion
3 data records inserted in table /BI0/XCUST_SALES
3 data records n table /BI0/PCUST_SALES marked for deletion
3 data records inserted in table /BI0/PCUST_SALES
Different database operations were executed
When I run the attribute change I see the following messages:
The Change Run is executing
Attribute 0CUST_SALES__ZZROUTE for basic characteristic 0CUST_SALES: 2 changes
Attribute 0CUST_SALES__0BILLTOPRTY for basic characteristic 0CUST_SALES: 2 changes
Attribute 0CUST_SALES__0PAYER for basic characteristic 0CUST_SALES: 2 changes
Attribute 0CUST_SALES__ZZACGRP for basic characteristic 0CUST_SALES: 2 changes
0001 ZSD_C02    100016     Aggregates Will Be Adjusted by:Reconstruction
0002 ZSD_C02    100019     Aggregates Will Be Adjusted by:Reconstruction
After seeing this i revisited the documentation for threshold value in RSCUSTV8. Ours is BLANK! So according to the documents when it is blank the aggregate is reconstructed generally. Not what we want!!
I will change the setting to the suggested 20% to start and we'll work from there.
Thanks for your help Oliver.

ERROR while running attribute change run.

hi sap xperts,
I got an error while running the attribute change run in a process chain.
At first i got an error "The action is locked by a change run"
SO I DID THE FOLLOWING STEPS.
1.RUN ATTRIB CHANGE RUN MANUALLY IT RUN SUCCESSFULLY,but the process chain is still red.
Q1.Is there any way to link the manually run attrib chnage to process chain so that the process chain becomes Green?
2.SM12 - realease the locks and right click the pc and repeat.It didn't work
Q1.While removing the locks what should we remove,bcoz i removed all the locks?
3.I again removed the lock and repeat the process but still i didn't work.Now its chowing "SQL ERROR OCCURED WHILE ACCESSING"
So the Process chain got stuck,Can any body help me to run the attrib chnage run.
If possible can anybody send the Process chain monitoring documents to my email id:
<email ID removed>
please.thanks in advance,i know how to say thanks in sdn.

At any point in time only one attribute change run can run in the system. The other ACR's will fail due to locks. In your case, to set the process chain to green, try the following steps.
Open the messages of a failed step by right clicking on it and selecting 'display messages'.
In the opened popup click on the tab 'Chain'.
In a parallel session goto transaction se16 for table rspcprocesslog and display the entries with the following selections:
1. copy the variant from the popup to the variante of table rspcprocesslog
2. copy the instance from the popup to the instance of table rspcprocesslog
3. copy the start date from the popup to the batchdate of table rspcprocesslog
Press F8 to display the entries of table rspcprocesslog.
Now open another session and goto transaction se37. Enter RSPC_PROCESS_FINISH as the name of the function module and run the fm in test mode.
Now copy the entries of table rspcprocesslog to the input parameters of the function module like described as follows:
1. rspcprocesslog-log_id -> i_logid
2. rspcprocesslog-type -> i_type
3. rspcprocesslog-variante -> i_variant
4. rspcprocesslog-instance -> i_instance
5. enter 'G' for parameter i_state (sets the status to green).
Now press F8 to run the fm.
The above steps will help you continue with the rest of the process chain (thus avoiding manual runs) but the failed step might still remain red. Hope this helps.

Attribute Change Run taking very Long time.

Hi Experts:
We are daily loading Master data from one common process chain. There are 33 Infoobjects which are getting activated in Attribute Change Run Process. This process is taking almost 3 hours to run daily; due to this it is impacting our other data load process chains.
Many times it happens that there is lock on cubes due to attribute change as attributes are getting aligned to same cube on which the roll up is running.
There are local chains below the attribute change run, which are also important to run.
Please help and suggest the workaround for the same.
Cheers,
Omkar

33 info objects in one ACR(attribute change run) is not a good idea.
Better to split the info objects and use multiple ACR.
During your ACR if transaction data load was on then lock issues always occurs.
Thats why we need to run master data loads first and later transaction data loads.
Which info object change run was troubling, better to note the info objects which are causing and try to put them in separate ACR and trigger it before start of your transaction data loads. so that it won't raise the same issue again.

Process chain best practice - attribute change runs

When building attribute change runs into Process Chains I see that there are potentially two main options to consider:
1. One to One mapping. Incorporate a separate attribute change run object type after each InfoObject has been loaded.
2. Many to One mapping. Build the process chain so that one single attribute change run occurs after all the InfoObjects have been loaded.
I would be interested to see how other people have incorporated their attribute loading into Process Chains.
any info appreciated.
Mike

We run the attribute change run twice in our daily process chain, here's our order:
- Load all master data
- Attrib change run
- Load all tx data
- Run ABAP programs that generate master data
- Attrib change run
I doubt there will be much of a performance difference if you do the change run after each master data load, but it makes the process chain a lot easier to read.

Attribute change run

Hi all,
As Iu2019m very new to SAP BW, can u plz tell me how to complete the attribute change run that has failed in a process chain?

Hi
Goto T-code: SE38, Run program: RSDDS_CHANGERUN_MONITOR.
It will show the staus of change runs. Here you will get execute button option to execute it again.
Note: It might take bit long time to open.
Thanks,
Jitender.
Edited by: Jitenderkumar Danduvia on Mar 30, 2010 11:00 AM

Height of the scrollbar changes in AdvancedDataGrid

Hi Forum Members,
I am facing one issue with the length of the scrollbar of advanced datagrid in flex. I will explain you the scenario
- Advance datagrid has variable row heights. Each row can have different heights.
- When the event Scroll Up is fired, I have to modify the itemrenderer's height of the advance datagrid. For this, I am looping through the FirstVisibleItem's itemrenderer, till the end.
The problem I face here is, the moment I set the height to first visible item renderer, the advance datagrid's scrollbar height is re calculated and the length of the scrollbar changes. The scrollbar length changes mainly because, itemrenderes' height are set starting from the first Visible item.
How can I loop through all the item rendrers of the advance datagrid ? I did not see any parameter to access the itemrenderer at Index 0. I tried reading the same, via the method indexToItemRenderer() it was returning null, when index 0 item is out of visible area.
Any help in this area would be appreciated
Thanks and Regards,
Nithin

You can use app builder to specify the banner height either as fixed size in pixels(between 1-1280pixels) or as a relative/percentage based size. If you defined as pixels, design your html/css to that exact size or 100% width/height if relative/percentage based size

Attribute Change Run in BW 3.5

Hi,
In RSA1 ->Monitoring ->Reallignment Run,
When I click on the InfoObject List button, I can see one InfoObject.
1) Does it mean the attribute Change Run is not yet perform for this InfoObject?
2) If yes, then I would just need to select this InfoObject, then click one the Execute button, correct?
3) If not, then why I have that InfoObject in the InfoObject List button?
Please advise, thank you.

Hi,
For your last quesdtion, why the infoobject is there in the list is it could be that the master data was changed/new records in to BW for this infoobject, hence requires the change run to be executed.
Regards.
Srini

Regarding Attribute Change Run failure.

Dear All,
We have a process chain which contains many meta chains.
Now in each chain i mean meta chain there are attribute change runs
We have desegregated the attribute change run. is tere any method to place a check for attribute change run locks because at the last i have another attribute change run which is failing every day because of the attribute change run is still happenign in some chain.
how do i implement it?
Thanks in advance
Janardhan Kumar.

Hi Janardhan,
In master data process chain where you have added process of attribute change, just insert a program before this process:
The program is: RSDDS_CHANGERUN_MONITOR
This program will check for any another attr change run running at that time and if there's any other attr change run runnning locking the object which your next attr change run requires then this program will not allow your attr change run to run.
Once all the locks all cleared for attr change run it will trigger the next node.
This program has a do loop which keeps on checking until unless locks are cleared.
Regards,
Vij

Roll Up & Attribute Change Run

Which is first -- Roll Up / Attribute Change Run.
Why?
Pls help me.

Hello Indira,
http://help.sap.com/saphelp_nw04/helpdata/en/9a/33853bbc188f2be10000000a114084/content.htm
That link provides information that explains 'Roll Up'
Here is a link to another thread that says as stated to do the Attribute Change run then do the Roll up.
Re: Attribute Change Run
It may help you,
Nick
Message was edited by:
Nick Bertz

Length of the attribute changed????

Similar Messages

Maybe you are looking for