|
I have deleted unwanted Update rules and InfoSources
(that have already been transported to QA system) in my DEV system. How
do I get them out of my QA system? I cannot find the deletions in any transports
that I have created. Although they could be buried somewhere. Any help
would be appreciated.
I had the same problem with you. And I have been told
there is a way to delete the unwanted objects. You may request the
Basis team to open up test box temporarily to remove the obsolete Update
rules and InfoSources. Remember to delete the request created in test after
you have removed the Update rules and InfoSources.
When I tried to delete the master data, get the following message"Lock NOT set for: Deleting master data attributes". What I need to do in order to allow me can delete the master data. Since, technically, the master data tables are not locked via SAP locks but via a BW-specific locking mechanism, it may occur in certain situations, that a lock is retained after the termination of one of the above transactions. This always happens if the monitor no longer has control, for example in the case of a short dump. If the monitor gets the control back after an update termination (regular case), it analyzes whether all update processes (data packets) for a request have been updated or whether they have terminated. If this is the case, the lock is removed. Since the master data table lock is no SAP lock, this can neither be displayed nor deleted via Transaction SM12. There is an overview transaction in the BW System, which can display and delete all currently existing master data table locks. Via the button in the monitor with the lock icon or via Transaction code RS12 you can branch to this overview. A maximum of two locks is possible for each basis characteristic: Lock of the master data attribute tables
Changed by, Request number, Date and Time is displayed for every lock. Furthermore, a flag in the overview shows whether locks have been created via master data maintenance or master data deletion. During a loading process the first update process starting to update data into the BW System (several processes update may update in parallel for each data request), sets the lock entry. All other processes only check whether they belong to the same data request. The last process, which has either been updated or has terminated, causes the monitor to trigger the deletion of the lock.
Fast Links:
Get help for your SAP BW problems
SAP Books
Best regards,
All the site contents are Copyright © www.erpgreat.com
and the content authors. All rights reserved.
|