Attribute ChangeRun issue

Hi All
I can not able to run Attribute Change run because it is locked with 1 Infoobject and save button got vanished from past few days it is got dump message In the monitor is showing change run was terminated and characterstics to be activated. This is major impact in my project since we can not able to load any data to this Master data object ofcourse we can able to activate data for other Infoobjects using Right click on Infoobject and activate.
Why this is happend I have tried to load data into this after few records got red and showing message like Infoobject is locked.
I can not able to do anything with this Object. I have checked in SM12 we dont have any locks.
Can anyone have the solution please help me.
Thanks
Vani

Hi,
You can try going to the monitor for Attribute change run from RSA1 >> tools >> apply change run or from Transaction RSATTR which will schedule/display attribute change run. Here you can have an option called change run monitor (Monitor icon). this wil show the status of change run including which all info objects are affected, and if its hitting the aggregates of any cubes.
Also you can try Tcode CHANGERUNMONI/program RSDDS_CHANGERUN_MONITOR to view this data.
Attribute change run Infoobjects locked
Refer OSS notes 903886
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=903886
1) Some times the infoobjects are not released from the previous change run.
So go to the FM RSDDS_AGGR_MOD_CLOSE and run it it will release all the locks on the infoobjects by the ACR.
Now re run the ACR.
OR
If your last change run was unsuccessful then, Go to table RSDDAGGRMODSTATE. Failed change run might have left a record in this table with field CLOSEDFL = ' ' (false).
Change this field CLOSEDFL to 'X' and the infoobjects will got unlocked.
This should be used only as as last resort and is not advicable to use frequently.
Also there are scenarios where the attribute change run failed with message that it was hitting/affecting aggregates of some infocubes. In case we had to switch off aggregates and trigger the change run again and then swtich on the aggregates after the change run is over.Most of the times we have problem with the Attribute Change Run(ACR) running because ACR and the Roll Up's for Aggregates cannot run in parallel.
And sometimes ACR goes on running for a long time in such case we need to check which Aggregate the ACR is currently changing and need to deactivate that aggregate.
But before deactivating an aggregate you need to check the data present in that and the usage of the aggregate.
This may not be the exact issue you are facing.
thanks,
JituK

Similar Messages

Aggregate DB index problems in Attribute changerun

Dear All,
The attribute changerun in Process chain is hanging regularly and if I check the SM50 process overview
I am able to see the SQL statement " CREATE BITMAP INDEX "SAPR3"."/BIC/F200378~080"
ON "/BIC/F200378" ( "KEY_1003788" ) PCTFREE 10" which is running in loops for hours.
We tried the SAP Note 728922 but only few days it worked and remaining days till we deactivate the aggregates the Attribute changerun will be hanging.
We can't afford deactivating and refilling of the aggregates as we have 7years of data
kindly suggest me how to Avoid this.
Regards,
Ugendhar

Dear Ajeet ,
The issue is coming most of the times with two aggregates which have just 2117144 and 4022462 records respectively.
I will try creating the copy of the aggregates yearwise but this may hinder the performance of the query when we view for several years as it may have to split across many aggregates.
Dear Krishna,
The problem is not with the Cube indexes and facing the issue in ACR which is not related to cube but the aggregates of it.
Thanks for ur suggestions and please guide with more inputs if possible.
Regards,
Ugendhar

What is attribute changerun and process chain?

hi experts,
what is attribute changerun and processchain. pl explain these two with a business case.
thanks & regards
venkat

Hi Venkata,
For attribute changerun,
It's used after you change (add/delete/modify) attribute in the master data. You've to make it in order to have an effect after you modify it.
To get it :
1. tcode : RSA1.
2. Tools -> Apply Hierarchy/Attribute Change
3. tap on Info-object list button (checking what master data you've modified before).
4. tap on selection button for type of job
5. Execute.
link(s):
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a67ece07211d2acb80000e829fbfe/frameset.htm
For process chain,
Using this you can make a flow of process sequentially.
e.g.
the flow :
1. generate program YWS001
2. get the data from table zcrm001
3. load data to ods : zods_001
link(s):
http://help.sap.com/saphelp_nw04/helpdata/en/8f/c08b3baaa59649e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/6e/192756029db54192427cf6853c77a7/content.htm
Hopefully it can helps you a lot ..
Regards,
Niel
(Many thanks for any points you choose to assign).

Can anyone explain me what is Attribute Changerun, in detail, Urgent

Can anyone explain me what is Attribute Changerun, in detail

If you assign the process type Attribute Change run to a process chain you must define a variant. With this variant you have to define the InfoObjects for which you want to activate the master data. There are four different possibilities:
     HIERARCHY: direct selection of the hierarchy which need to be activated
     INFOOBJECT: direct selection of the infoobjects which need to be activated
     LOADING: indirect selection: reference to an InfoPackage, which must be loaded before in the process chain. Combined with the meta data of these objects and the instance information the system derives the affected InfoObjects and hierarchies. If the chosen LOADING object is not in the process chain, the system automatically inserts the chosen infopackage in process chain.
     REPORTVARIANT: indirect selection: reference to a change run variant which you can define with RSDDS_AGGREGATES_MAINTAIN (SE38) or TCode RSATTR Executing the Attribute/hierarchy change run with Variant:
Instead of applying the InfoObjects or hierarachies directly to the process variant in RSPC you can create a central variant for the report RSDDS_AGGREGATES_MAINTAIN. You can assign InfoObjects and hierarchies to this report variant. This central variant could be used by several process variants in RSPC. The benefits are central maintenance, ..

Attribute Mapping Issue - Pls help

Hi am a newbie......in XML-Java related issue.
Am trying to map an XML with Java objects.
Take this XML for example:
<test>
<root type="star">
<player>
<name>Thierry Henry</name>
<rating>10</rating>
</player>
<player>
<name>Rooney</name>
<rating>0</rating>
</player>
</root>
<root type="medium">
<player>
<name>nistelrooy</name>
<rating>-1</rating>
</player>
<player>
<name>xyz</name>
<rating>0</rating>
</player>
</root>
</test>
My question is, how do i refer to the attribute "type" in the <Root> element in my corresponding class to be mapped with this xml......kindly help me writing the mapping xml for this also.

Oops, just realised this is the SES forum and not the Oracle Text forum ... ignore my last post!
The answer to this depends on whether you're using the table crawler or the database crawler, and what the datatypes are for job_name and vacancy_name.
If we assume they're VARCHAR2 it's quite straightforward...
If using the TABLE crawler, then recreate your join so that instead of two columns job_name and vacancy_name, you concatenate the two together in the join into a column called (for example) CONTENT, and use that as the text column to index.
If using the DATABASE crawler, then simply concat these columns as part of your SELECT into the column named CONTENT.

Customer Attribute restrict issue in BEx

Dear All,
I have added lot of 'Z' attributes to 0Customer and i have loaded the data. Now for queries i have created InfoSet which contains 2 DSOs and 0CUSTOMER.
In a query i need to restrict particular Display attribute but in restrict screen it is not showing any values for this attribute.
So is it mandatory to make this attribute as navigational though i have created InfoSet??
Please help on the issue.
Regards,
Sohil Shah.

Hi Sohil,
If you can drag the char but not able to see any values and that is the reason you are not able to restrict, then you can do two things.
1. If you know the values you want to restrict, directly type it in the restriction window and press Right Arrow Key to add it into restriction.
2. If you want to select from the list only, make sure you have attribute change run executed for 0customer and this particular display attribute. Once you run this, you should be able to see the values in the list.
- Danny

Reg: Master Data Attribute SID issue

Hi,
In 0MATERIAL i found some inconsistency in the P & X tables for reference SIDs, when i check the data at info cube by selecting a nav attribute of 0material then it is showing wrong data. I tried to check the consistency of this object at RSRV by selecting combined master data test then i found the below log
Characteristic 0MATERIAL: 144,290 values from table /BI0/PMATERIAL do not exist in table /BI0/XMATERIAL
Characteristic 0MATERIAL : Tables /BI0/PMATERIAL, /BI0/XMATERIAL are not consistent: 144,290 deviation(s)
Any inputs regarding this issue will be appreciated.
Thanks in advance.
Prabhakar.

Hi,
I tried to repair the error from there, but after doing so the same error was getting displayed.
Even i have checked the number range also, it was ok.
Any more suggestions.
Regards,
Prabhakar.

ABAP Objects-attribute accessability issue

Hi,
Let me introduce the problem.
I have a class c1 which has a public attribute a1.
a1 is of table type which refers to a class c2. c2 has an attribute a2 which is public.
With the object o1 of class c1 I need to access a2.
Please help me solve the problem.
Regards,
Ravi
Message was edited by: Ravi Prasad Reddy L

HI,
Check the below code....
Hope it solves your purpose.
class b definition deferred.
class a definition.
public section.
    data : obj2 type ref to b.
    methods : write_data.
endclass.
class b definition.
public section.
    data : v_num type i.
      methods : assign_value.
endclass.
class a implementation.
method write_data.
    create object obj2.
    call method obj2->assign_value.
    write:/1 'Hello Everybody'.
endmethod.
endclass.
class b implementation.
method assign_value.
    v_num = 100.
endmethod.
endclass.
data : obj1 type ref to a.
start-of-selection.
create object obj1.
call method obj1->write_data.
write:/1 obj1->obj2->v_num.
Regards,
Vara

What is t.code of attribute changerun

hi all give postings

hi
changerunmoni- this is for monitoring Hierarch attribute change run...No other functionality
Go to > RSA1>Tools_-> Hierarch attribute/Change run
Here you can see more options
Assign points if useful
Regards
N Ganesh

Attribute change run cancelled - Reg

Hi,
Can we run master data Job if attribute change run has cancelled for the same Master data Object?
Thanks,
Ajay

Hi,
if the attribute changerun is cancelled then you cannt run thw masterdata.. because it wil agian fail with the message :
locked by terminated changerun .. so first run the chaingerun succssfully to release the masterdata..
check the link to release the lock ..
Attribute ChangeRun issue
hope this helps you .
Reagrds,
Shikha.
Edited by: Shikha Goel on Oct 14, 2008 10:09 PM

CSI: update_item_instance issues while creating extended attributes

Hello,
For our customer's data conversion, installed base instances have already been created, there is only need to create extended attributes.
Issues I have encountered are:
- Whenever an error is encountered in the API call, all following records are rejected with the same error (even the same instance ID/primary key/attribute ID) as the first error record.
- Extended attributes are randomly entered in the wrong fields (as if one field had gone missing and the others had been updated)
- Date formats have been changed from DD/MM/YYYY to DD-MON-YYYY when consulting from Installed Base (but this happened only once)
Other information: There are 14 extended attributes to be added for each item instance, I removed some of the attributes to make the code more readable.
I followed the metalink note that shows the implementation method for this API and only added the recursive elements that we needed for the 14 attributes + functions to retrieve item_id and such.
The "message()" function replaces is defined as FND_FILE.PUT_LINE(which =>fnd_file.log,buff => p_msg);
PROCEDURE main (errbuf OUT VARCHAR2
                    ,retcode OUT NUMBER
IS
     vl_status                BOOLEAN;
     vl_item_id                NUMBER;
     vl_instance_id           NUMBER;
     v_count               NUMBER;
     v_err_rec CSI_DATASTRUCTURES_PUB.TRANSACTION_ERROR_REC;
     v_trx_id number ;
     v_ret varchar2(240);
     v_msg_count number;
     v_msg_data varchar2(2000);
     v_date date;
     t_msg_dummy NUMBER;
     t_output VARCHAR2(2000);
     vl_attribute_id NUMBER;
     v_inst_rec csi_datastructures_pub.instance_rec;
     v_ext_attr csi_datastructures_pub.extend_attrib_values_tbl;
     v_party_tbl csi_datastructures_pub.party_tbl;
     v_account_tbl csi_datastructures_pub.party_account_tbl;
     v_pr_tbl csi_datastructures_pub.pricing_attribs_tbl;
     v_org_as s_tbl csi_datastructures_pub.organization_units_tbl;
     v_asset_as s_tbl csi_datastructures_pub.instance_asset_tbl;
     v_trx csi_datastructures_pub.transaction_rec;
     v_inst_id_lst csi_datastructures_pub.id_tbl;
BEGIN
     APPS.FND_GLOBAL.Apps_Initialize(FND_PROFILE.value('user_id')
,FND_PROFILE.value('resp_id')
,FND_PROFILE.value('resp_appl_id'));
     IF cur_iea_attributes%ISOPEN
     THEN
          CLOSE cur_iea_attributes;
     END IF;
     IF get_trx_id
     THEN
          message('Transaction ID '||to_char(gv_trx_id));
          FOR v_cur_iea_attributes IN cur_iea_attributes
          LOOP
               v_count:=0; -- Initialisation du compteur du ligne. Attention, le nb de lignes dans interface = 14 x nb lignes dans stg
               IF check_unique_serial(v_cur_iea_attributes.numero_serie)
               -- Recuperation de l'item ID
               THEN
                    get_item_id(p_serial_number => v_cur_iea_attributes.numero_serie
                                   ,p_item_id => vl_item_id
                                   ,p_status => vl_status
                    message('Resultat get_item_id: '||to_char(vl_item_id));
                    get_instance_id(p_item_id => vl_item_id
                                        ,p_serial_number => v_cur_iea_attributes.numero_serie
                                        ,p_instance_id => vl_instance_id
                                        ,p_status => vl_status
                    IF vl_status
                    THEN
                         v_trx.TRANSACTION_DATE:=trunc(SYSDATE);
                         v_trx.SOURCE_TRANSACTION_DATE:=trunc(SYSDATE);
                         v_trx.TRANSACTION_TYPE_ID:=gv_trx_id;
                         message('Entrance v_count'||to_char(v_count));
                         v_inst_rec.instance_id:=vl_instance_id;
                         v_inst_rec.object_version_number := 1;
                         IF v_cur_iea_attributes.IAE_GUARANTEE_END_DATE IS NOT NULL
                         THEN
                              v_count:=v_count+1;
                              v_ext_attr(v_count).instance_id := vl_instance_id;
                              message('v_ext_attr(v_count).instance_id: '||to_char(v_ext_attr(v_count).instance_id));
                              message('vl_instance_id: '||to_char(vl_instance_id));
                              get_attribute_id(p_attribute_code =>'GUARANTEE_END_DATE'
                                                  ,p_attribute_id => vl_attribute_id);
                              message('vl_attribute_id: '||to_char(vl_attribute_id));
                              v_ext_attr(v_count).attribute_id := vl_attribute_id;
                              v_ext_attr(v_count).attribute_value := v_cur_iea_attributes.IAE_GUARANTEE_END_DATE ;
                              message('v_cur_iea_attributes.IAE_GUARANTEE_END_DATE: '||v_cur_iea_attributes.IAE_GUARANTEE_END_DATE);
                              message('');
                         END IF;
                         IF v_cur_iea_attributes.IAE_LAST_CTRL_DATE IS NOT NULL
                         THEN
                              v_count:=v_count+1;
                              message('v_count'||to_char(v_count));
                              -- Les 6 champs obligatoires a remplir pour un update
                              v_ext_attr(v_count).instance_id :=vl_instance_id;
                              get_attribute_id(p_attribute_code =>'LAST_CTRL_DATE'
                                                  ,p_attribute_id => vl_attribute_id);
                              v_ext_attr(v_count).attribute_id := vl_attribute_id;
                              v_ext_attr(v_count).attribute_value := v_cur_iea_attributes.IAE_LAST_CTRL_DATE ;
                         END IF;
                         CSI_ITEM_INSTANCE_PUB.update_item_instance
                                   p_api_version => 1
                                   ,p_commit => fnd_api.g_false
                                   ,p_init_msg_list => fnd_api.g_true
                                   ,p_validation_level => fnd_api.g_valid_level_full
                                   ,p_instance_rec => v_inst_rec
                                   ,p_ext_attrib_values_tbl => v_ext_attr
                                   ,p_party_tbl => v_party_tbl
                                   ,p_account_tbl => v_account_tbl
                                   ,p_pricing_attrib_tbl => v_pr_tbl
                                   ,p_org_assignments_tbl => v_org_ass_tbl
                                   ,p_asset_assignment_tbl => v_asset_ass_tbl
                                   ,p_txn_rec => v_trx
                                   ,x_instance_id_lst => v_inst_id_lst
                                   ,x_return_status => v_ret
                                   ,x_msg_count => v_msg_count
                                   ,x_msg_data => v_msg_data
                              -- Output the results
                              if v_msg_count > 0
                              then
                                   for j in 1 .. v_msg_count
                                   loop
                                        fnd_msg_pub.get ( j , FND_API.G_FALSE , v_msg_data , t_msg_dummy );
                                        t_output := ( 'Msg' || To_Char ( j ) || ': ' || v_msg_data );
                                        message( SubStr ( t_output , 1 , 255 ) );
                                   end loop;
                              end if;
                    ELSE
                         message('Update not performed for '||v_cur_iea_attributes.numero_serie||' and '||vl_item_id);
                    END IF;
               ELSE
                    message('Erreur sur '||v_cur_iea_attributes.numero_serie);
               END IF;
               commit;
               message('Commit done for update loop');
          END LOOP;
     ELSE
          message('No Transaction ID - EOP');
     END IF;
EXCEPTION
     WHEN OTHERS
     THEN
          ROLLBACK;
          message('Error in main program, rolling back');
END main;
Thanks!

Todd
The issue seems to because this:
x_instance_rec.inventory_item_id := ib_rec3.inventory_item_id;
You are selecting the item id from your staging table. But the serial number in the csi_item_instances is associated with the instance is a different item id than ib_rec3.inventory_item_id. Hence this error. You cannot change the item in the IB once the instance is created.
You have two choices: comment this out or change the inventory_item_id in staging table to match with the csi_item_instances.
Also a lot depends on what is your serial number uniqueness. If you are using the same serial number for two different items (uniqueness with item_Id) you need to be careful which one you are picking (based on serial number).
Thanks
Nagamohan

Attribute change run fails - "Error when deleting the data record /B05/X.."

Hello,
I get the error message "Error when deleting the data record /B05/X.." on doing the change run.
I have already done RSRV on this objects and found no errors, but still the activation fails.
please give your suggestions ASAP to fix the issue as it is on production system.
Thanks.

Attribute change run could fails due to 2 reasons-
(1) attribute xchange run is already runnnig for any toher object(monitor lock) (check by thi prog-RSDDS_CHANGERUN_MONITOR)
(2) data is loading deleting from the object on which attribut changerun is running.(go in a manage tab and check)
check this two conditions and rerun the attribute changrun again from program - RSDDS_AGGREGATES_MAINTAIN and give the master data name in the selection.
Hope it helps you.

Navigational Attribute is not properly displaying

Hello,
We have a "Sales Group" navigational attribute YCUST_SAL-YSALE_GRP in a BW report. We have adjusted a sales group for a customer in R3 from F10 to E49 and hte same has been pulled to BW side,.
we have activated the master data manually and we are able to see the new data is available against the customer.
But when we refresh teh report, for that customer we are able to see only F10 as the sales group,.
For cross check, we have sales group display property also. where we are able to see E49.
Please let us know why we are seeing inconsistency between display and navigational attribute for a same infoobject.
Thanks. Karthik

Hello,
It seems Master data is not activated properly....
Whether the query is fetching data from Aggregates, if so you have to do Attribute changerun for this infoobject
goto SE38 and run this program RSDDS_AGGREGATES_MAINTAIN it will Info object name...Provide your info object and execute...
Your problem will solve.
Regards,
pavan.

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

Filesystem issues while updating

I can't upgrade community repository because some file on my harddisk does not like to be removed.
[root@senna frank]# pacman -Sy
:: Synchronizing package databases...
core is up to date
extra is up to date
community 366.9K 1084.6K/s 00:00:00 [###########################################################################] 100%
error: could not remove database entry communitygnomebaker
error: failed to update community (could not remove database entry)
testing is up to date
When I manually try to remove this file:
[root@senna gnomebaker-0.6.2-1]# pwd
/var/lib/pacman/sync/community/gnomebaker-0.6.2-1
[root@senna gnomebaker-0.6.2-1]# ls
depends
[root@senna gnomebaker-0.6.2-1]# rm -vRf depends
rm: cannot remove `depends': Operation not permitted
Strace:
[root@senna gnomebaker-0.6.2-1]# strace rm -vRf depends
execve("/bin/rm", ["rm", "-vRf", "depends"], [/* 35 vars */]) = 0
brk(0) = 0x8c11000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=53084, ...}) = 0
mmap2(NULL, 53084, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7eea000
close(3) = 0
open("/lib/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0 h\1\0004\0\0\0\200"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1554407, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7ee9000
mmap2(NULL, 1336912, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7da2000
mprotect(0xb7ee2000, 4096, PROT_NONE) = 0
mmap2(0xb7ee3000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x140) = 0xb7ee3000
mmap2(0xb7ee6000, 9808, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7ee6000
close(3) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7da1000
set_thread_area({entry_number:-1 -> 6, base_addr:0xb7da16c0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0
mprotect(0xb7ee3000, 8192, PROT_READ) = 0
mprotect(0xb7f14000, 4096, PROT_READ) = 0
munmap(0xb7eea000, 53084) = 0
brk(0) = 0x8c11000
brk(0x8c32000) = 0x8c32000
ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
lstat64("/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
lstat64("depends", {st_mode=S_IFREG|0644, st_size=115, ...}) = 0
unlink("depends") = -1 EPERM (Operation not permitted)
write(2, "rm: "..., 4rm: ) = 4
write(2, "cannot remove `depends'"..., 23cannot remove `depends') = 23
write(2, ": Operation not permitted"..., 25: Operation not permitted) = 25
write(2, "\n"..., 1
) = 1
close(0) = 0
close(1) = 0
close(2) = 0
exit_group(1) = ?
Does anyone have a clue what I can do about this?
It's been a while since I updated community now

lucasdemarchi wrote:
I believe it's related to this file's attributes. Issue "lsattr" in this file and see if there's an "i" attribute. If so, change it:
chattr -i filename
From chattr's man page:
A file with the `i' attribute cannot be modified: it cannot be deleted or renamed, no link can be created to this file
and no data can be written to the file. Only the superuser or a process possessing the CAP_LINUX_IMMUTABLE capability
can set or clear this attribute.
regards
You are my hero
Worked like a charm.
Now I can update community again

Attribute ChangeRun issue

Similar Messages

Maybe you are looking for