Difference between a Change-run and Activate master data

Hi experts,
Could you tell me what is the difference between making a change-run on a masterdata (rsa1 --> Tools --> Apply Hierarchy/Attribute Change...), and making a right-click on this masterdata and click on "Activate master data" ?
The result seems to be the same, all rows in version M (Revised) are changed in version A (Active)...
Thanks for your help.
Tempka.

Hi
Change run will update the master data changes in Aggregates and update the object master data as well.
Activate master data will only activate the new records and it will not update the aggregates.
check out the below thread
Attribute Change Run VS Master data activation
Regards,
Vekatesh

Similar Messages

  • Difference between on change of and at end of :

    Hi Can any one explain me what is the exact difference between on change of and at end of .
    I know the basic differences.
    But i would like to know in which case we can use the above two statemetns.
    Suppose :
    Matnr   plant       sloc       movementype      date                          qty
    12       001          002           261                12/11/08                    10
    12      001          002            261               12/11/08                      11
    12      002          003            261               12/11/08                      12
    Here i need to add the quantity based up on the material,
    If the materials is maintained in different plants then it should give the total for for that particular plant.
    Please help me how to build logic to this :
    Regards,
    Vinay.

    ok sure i will give it to u.
    MATNR       PLANT          SLOC            BWART           BUDAT         QTY1           QTY2           QTY3             QTY4            QTY5
    127874     2501     3025     200906     201     0.000     0.000     0.000     0.000     0.000
                         QTY6           QTY7             QTY8             QTY9           QTY10         QTY11            QTY12
         0.000     0.000     0.000     0.000     0.000     0.364     0.000
    127874     2501     3025     200905     201     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     7.000     0.000     0.000
    127874     2501     3025     200905     202     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     1.000     0.000     0.000
    127874     2501     3025     200905     261     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     35.000     0.000     0.000
    127874     2501     3025     200905     551     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     5.000     0.000     0.000
    Here i need to write the logic for that material usage :
    This material usage will be caliculated based upon the movement types in that particular month :
    The formula is :
    AT END OF BUDAT.
         FINAL_VALUE_WA-KWMENG12 =   ( W_QTY261 -   W_QTY262 ) + ( W_QTY201 - W_QTY202 ) + ( W_QTY551 - W_QTY552 ).
          CLEAR : W_QTY261,W_QTY262,W_QTY201,W_QTY202,W_QTY551,W_QTY552.
        ENDAT.
    Here iam writting the logic as at end of the month iam caliculating.
    But what my question is if we have same material in different plant and the usage is in the same month
    then i think this query is going to fail.
    Edited by: vinay raj on Jul 6, 2009 2:02 PM
    Edited by: vinay raj on Jul 6, 2009 2:03 PM

  • Impacts in COPA of changing material and customer master data

    Dear experts,
    In my company we are considering following scenario:
    Currently mySAPerp 6.0 is implemented for all modules for the mother company.
    We have developed a new global template where there are significant changes versus the existing system, especially in the SD processes. Material and customer master also change significantly in terms of content in the tables/fields and/or values in the fields.
    The idea was to build the template from scratch in a new machine and roll-out all group affiliates, but now we are considering the possibility of making an evolutionary of the current system and try to stretch it to the processes defined in the global template.
    The scenario we want to analyze is: Keeping same organizational structure in terms of Company code, CO area and Operating Concern in existing SAP client and make an evolutionary of the existing settings to the global template processes.
    The doubts we are having are the following:
    Changing material & customer master data: Impact in COPA
    Option 1: Material master data and customer master data codes are maintained but content in the tables/fields is changed substantially, both in terms of logical content of specific fields and/or the values in the specific fields. We have following examples of changes.
    Case 1: source field in material master changes logical content. E.g. Material master field MVGR1 is currently used for product series (design line) and the content changes to be the Market Segment. The product series will be moved to a classification field. At least 5 other fields are affected by this. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
    Case 2: the source field is not changed so that the logical content of the field remains but the values change, i.e. for the same concept there will be different codifications. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
    Case 3: Characteristics where currently the source material master field is a Z field and the derivation is via table look up and where the Z field changes to a classification field. How can you convert the existing COPA line items to ensure that attributes are aligned? Should new characteristics be created or just change the derivation logic of the characteristic?
    Option 2: Material master data and customer data codes are re-created (codification of records is changed), meaning that new material and customer codes will exist and content in tables/fields is changed (as in option 1)
    Case: material and customer codes are changed. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
    Iu2019ve never phased a similar scenario and I fear that maintaining operating concern while changing source master data and also SD flows (we have new billing types, item categories, sales doc. Types, order reasons) may lead to inconsistencies and problems in COPA.
    I would like to ask you experts if you have come across a similar scenario and if from your experience, it is something feasible to do or there are many risks involved. What can be the impact of this scenario in existing Operating Concern for both option 1 and 2 and what would be the key activities to perform to adapt the existing operating concern. What will be the impact of the needed conversions on P&L reporting?
    Sorry for the long story. I hope you can help me out.
    Thanks and Regards,
    Eric

    Hi,
       First i think you will need to test if it works for new COPA documents created via billing.
      If it works fine then the issue is if you wish to apply these changes to the historical data already posted.
      Normally there are transactions like KE4S where you can repost the billing document to COPA
      However this may not be viable for bulk postings
      You can perform realignment (KEND) but this only works at the PA segment level (table CE4XXXX)
    regards
    Waman

  • Difference between Delta "Change Log" and "Active Table (Without Archive)"?

    In BI7.0 environment, we perform our Delta loads (the DTP settings under the Extraction tab, there is a field called Extraction Mode and it's value is selected as "Delta") every day among all our DSOs.
    There is a section called "Delta Init. Extraction From..." under the same tab in DTP, there are four radio buttons:
    Active Table (With Archive)
    Active Table (Without Archive)
    Archive (Full Extraction Only)
    Change Log
    Then what is the difference between "Change Log" and "Active Table (Without Archive)" if both Extraction Mode is "Delta" for two Delta loads?
    Thanks!

    Hi ,
    The new options SP16 has are:(Chk Note 1096771)
    Active Table (with Archive)
    The data is read from the active table and from the archive or from a near-line storage if one exists. You can choose this option even if there is no active data archiving process yet for the DataStore object.
    Active Table (Without Archive)
    The data is only read from the active table. If there is data in the archive or in a near-line storage at the time of extraction, this data is not extracted.
    Archive (Only Full Extraction)
    The data is only read from the archive or from a near-line storage. Data is not extracted from the active table.
    Change Log
    The data is read from the change log of the DataStore object.
    Delta will always be picked from change log table.Only during intialization you can choose between getting data from change log or active table.If you are doing the load first time and are initializzing delta in subsequent data targets, then pulling data from active table will get lesse volume of data then it would have got from change log table....All subsequent deltas will be picked up from the change log.  And when we need to reload data into the data target (which would be a full load) - we use active table.
    From change log : you can take below ones as targets
    1) Cube 2) DSO with Addition as the update for the Keyfigures
    From Active table: you can take below ones as targets
    1) Cube ,if and only if, the records are never changes in the source once after creation
    2) DSO with Addition as the update for the Keyfigures ,if and only if, the records are never changes in the source once after creation
    3) DSO with Overwrite as the update for the Keyfigures ( incase deletions is not happening in the source system)
    Pls check this link
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/47/e8c56ecd313c86e10000000a42189c/frameset.htm
    Regards,
    CSM Reddy

  • Difference between extraction collective run and a V3 collective run

    Hello Roberto.
    As per your weblog can you elaborate on the difference between a Extraction collective run and a V3 collective run for Queued delta and V3 Update respecively,
    Regards,
    pravin

    Hello Roberto,
    Fine Roberto I have 3 more questions with regards to Queued delta-
    1.     In case of Queued deltas how does the data come to the LBWQ ex. MCEX02 queue from the application technically when a transaction is posted in R/3.
    2.     What role does the Function Module MCEX_UPDATE_02_QRFC play in getting the data in LBWQ.
    3.     Does the extraction Queue read the update tables VBHDR,VBMOD eventually like the V3 collective run.
    Regards,
    Pravin

  • Can we apply attribute change run for datatarget (Master data )

    hi,
    can we apply attribute change run for datatarget like masterdata where for example i am loading 0pm_order_attr to 0pm_order data target (master data). after successful loading of data, do i have to apply attribute change run for <i>info object</i> 0pm_order or apply attribute change run for 0pm_order in <i>info providers</i> because after successful loading of pm order data, i am trying to load transactional data and it is showing error "No SID value found for xxx record"
    pls advice how not to make the error repeat even after successful loading of master data.
    Thanks in advance, quick responce is greatly appreciated.

    Hi all,
    i am in production server and cannot activate the master data 0pm_order which is in info providers directly, is there any chance of activating it with any other option.
    coming to attribute change run, i understand that we can apply for master data objects which are there in info providers, am i correct?
    i ran attribute change run yesterday for the info object 0pm_order but even after doing that i tried to load transactional data but it was failure with the same error "No SID value found", why i am getting when i found master data loading successful and ran attribute change run for infoobject.

  • Attribute Change Run and Editing BI data

    Hello Experts,
    I have two questions.(They are not related to each other).
    Can BI data(Infocube data) be edited?
      For eg GL account in R/3 is changed from 100 to 2100. I want to know how can this be handled in BI.
    Attribute Change Run in the process chain ends with error.
      "Master data characteristic ZACCTNUM activated in 6 seconds. Error while activating characteristic   ZACCTNUM ". There are no more information.
       The BWREMOTE user has the authorisation to Execute Change Run.
       What could be the possible reasons for this failure.
    Thanks in advance.
    Regards
    Meenakshi

    Hi Meenakshi,
    Regarding your questons:
    1. You can't edit the data directly in the cube. If you have incorrect data in the cube and the data is still in the PSA you can edit the incorrect data in the PSA and you can then delete the incorrect requests from the cube. You can then reload the correct data from the PSA. If its not an option to delete individual requests you could delete the incorrect data using the selective deletion option (if you can select on the incorrect data in the cube). You could then reload the correct data from PSA or source system.
    2. Please check the infoobject ZACCTNUM is active in RSD1. If it is there may be an inconsistency with the data in the infoobject ZACCTNUM, please check if the solution part of the SAP note 1033721 can help you in this case.
    Best Regards,
    Des.

  • Difference between normal Costing run and Costing run in Material Ledger

    Hi everybody,
    I have a question i wanted to know why we implement Material Ledger .
    If material ledger is for settling variances on material then that is also possible without material ledger
    Please clear the doubt what is different in ML as compared to normal costing run
    thanks in advance
    Regards
    Deepa

    Costing run is to calculate the std cost estimate of materials and Material Ledger costing run is to calculate Actual cost of production of materials.

  • In Request type, what is the difference between action 'Change user' and 'Assign object'

    Dear All,
    I have used only 'Assign Object' for my 'Change User' request type. But the standard request type has 'Change user'. So, could you suggest , what additional purpose does Change Object serve
    Regards
    Plaban

    HI Plaban
    not sure if you answered your own question here?
    Change User - by itself would allow update of address data, user parameters, defaults, etc
    Assign Object - as you mentioned roles and profiles.
    However, if assigning, I think you need to have both actions: change and assign
    I recall (ages ago) that change was only the user details and not the role or profiles. As a result, there were a few threads where people had to update the action for the request type of provisioning would not occur.
    This is something you could test
    Regards
    Colleen

  • In Reports what  is the difference between the AT NEW and ON CHANGE Event

    Hi,
            Could you tell the differences of AT NEW and ON CHANGE events in Repors

    Hi raghava,
    The Major Difference is :
    a) When AT NEW occurs,
    the alpha-numeric fields have ******* in their value,
    b) where as in case of ON CHANGE,
    the alpha-numeric fields have their corresponding value,
    of that particular record,
    where the Event gets fired.
    Other differences are :
    ON CHANGE OF can be used any where in the program..
    on change of differs from at new in the following respects:
    1.It can be used in any loop construct, not just loop at. For example, it can be used within select and endselect, do and enddo, or while and endwhile, as well as inside get events.
    2.A single on change of can be triggered by a change within one or more fields named after of and separated by or. These fields can be elementary fields or field strings. If you are within a loop, these fields do not have to belong to the loop.
    3.When used within a loop, a change in a field to the left of the control level does not trigger a control break.
    4.When used within a loop, fields to the right still contain their original values; they are not changed to contain zeros or asterisks.
    5.You can use else between on change of and endon.
    6.You can use it with loop at it where . . ..
    7.You can use sum with on change of. It sums all numeric fields except the one(s) named after of.
    8.Any values changed within on change of remain changed after endon. The contents of the header line are not restored as they are for at and endat.
    while
    AT NEW can be used only within a loop of an INTERNAL TABLE..
    5. Sample program to get the taste of it
    (just copy paste)
    6.
    REPORT ABC.
    DATA : BEGIN OF ITAB OCCURS 0,
    bukrs like t001-bukrs,
    f1(10) type c,
    end of itab.
    itab-bukrs = '1000'.
    itab-f1 = '1111111'.
    append itab.
    itab-bukrs = '1100'.
    itab-f1 = '3333333'.
    append itab.
    itab-bukrs = '1200'.
    itab-f1 = '555555'.
    append itab.
    AT NEW
    loop at itab.
    at new bukrs.
    write :/ itab-bukrs , itab-f1.
    endat.
    endloop.
    AT ONCHANGE
    loop at itab.
    ON CHANGE OF ITAB-BUKRS.
    write :/ itab-bukrs , itab-f1.
    ENDON.
    endloop.

  • Difference between Consolidation, Harmonization and Central master data man

    Hi ..Expertise
    Consolidation is use to identify duplicate records and merge them into one record.
    Harmonization is the process of pushing the new cleansed data back out to your partner systems.
    Central master data management means you create records within MDM and then you distribute (Syndicate) this centrally created data to your Remote Systems.
    My Question is her after Consolidation both Harmonization and Central master data management is doing the same thing i.e. sending the clean data to the other system. What is the difference between these two? Please explain me with an example or scenario..

    Hi Yugandhar,
    There are three basic scenarios that we follow in MDM:
    Data Consolidation
    Data Harmonization
    Central Master Data Management
    Consolidation :
    Conolidation (matching , normalization, cleansing) and storage of master data imported from client system. Entails capabilities to identify identical and similar objects spread across the local systems , build consolidated master data.
    Key Capabilities:
    1. Cleansing and de-duplication
    2. Data normalization including categorization and taxonomy management
    3. New interactive consolidation capabilities
    Data Harmonization :
    In case of Harmonization we generally aim at reaching high quality master data within heterogeneous system landscapes. Here the main focus is on ensuring high quality of master data within the connected systems and then distributing the Master data
    Key Capabilities:
    1. Automated synchronization of globally relevant master data information
    2. New Interactive distribution capabilities
    Central Master Data Management :
    In case of CMDM, it is not always the scenario that the Client wants to go for the above two scenario`s, but CMDM is always required as it helps us to maintain the Business data effectively and efficiently.
    After MDM is put into the business scenario all the operations related to the Master records are done in MDM only. For Eg: Creating a record, Deleting a record, Distributing a record etc.
    Now it is the work of CMDM to centrally maintain the data and check that no duplicate enteries can be created.
    And all the various systems that are attached to MDM gets the updates from CMDM with the help of Syndication Process or Distribution Process.
    Key Capabilities:
    1. Central creation and maintenance of data
    2. Ongoing master data quality
    Hope this would be helpful !!!!!!!!!
    Regards,
    Parul

  • Any difference between Master data and User master data ?

    Any difference between Master data and User master data ?

    hi
    A user master record defines the authorizations assigned to a user. Based on these authorizations one can access the master data.
    Master data - it is the data which is used long term in SAP r/3 system such as vendor master , material master, customer master,
    there is no such thing like user master data to the best of my knowledge
    hope this helps
    regds
    Manan

  • Difference Between OTL Retro Entry and Salary Change Retro Entry in Payroll

    Hi Everyone,
    We are developing a custom interface from Payroll to Projects which will post all the entries from OTL.
    OTL->Payroll->Projects
    We are stuck with identifying the Difference Between OTL Retro Entry and Salary Change Retro Entry when we process Retropay in Payroll.
    After retropay, we come we would see the retro element entries for both them with same name and creator_type is either EE or RR for both them.
    In our interface we have to treat retro entries through OTL and Salary Change in differentway.
    Has anyone can give some suggestions on this please asap as we are heading towards UAT very soon.
    Thanks in Advance..!!
    Anand

    Hi Anand,
    Element with creator_type RR are created/generated by Retropay.
    Elements with creator_type EE are regular element entries.

  • Master Data basis-- difference between a Xportation zone and tariff zone?

    What is the difference between a transportation zone and tariff zone, & why would a transportation zone be different from a tariff zone?

    What is the difference between a transportation zone and tariff zone, & why would a transportation zone be different from a tariff zone?

  • CHANGE RUN and ROLL UP.

    Dear  all experts,
    I am a sap-bw trainee.
    Can anybody will please tell what is difference between CHANGE RUN and ROLL UP.
    Warm regards
    Vinay S. Joshi

    Change Run:
    When you load master data attribute you have to run attribute change run to activate the changes of attribute; athoerwise you'll get the old value.
    You can do it by right click on the infoobject an chose Activate data or in massive way from RSA1->Tools->Attribute change run.
    RollUp:
    It is done for the infocube has Aggregates.
    Its done when you update ur Cube with fresh data it must reflect in aggregates of that with that fresh data.
    For More On RollUp Check this link,
    http://help.sap.com/saphelp_nw04/helpdata/en/9a/33853bbc188f2be10000000a114084/content.htm

Maybe you are looking for