Skip to Content
Author's profile photo Kamal Kumar

Information Steward |Cleansing Package Builder Tips and Tricks- Part-1(Lock/Unlock)

Cleansing Package | Lock IssueCPB.JPG

Causes :-

  • System is idle for long time in Cleansing Package Read_Write mode
  • When your Rule is updating large data then there is more chances of Package locking :-


              1.  When adding Any Regular expression in Context Related attribute and its updating large sample Data .

              2.  Changing the output  format of Cleansing Package and if it is effecting  large data.

Tips to minimize the losing Cleansing Package Data and Locking Risk

1. Start Cleansing Package building with less sample data record .

2. Publish the cleansing Package after adding Data(Without any Rule also you can).

3. After adding Complex  or large data effective rule —-> go to Cleansing Package Builder Main screen  —>  Republish the Package(Repeat this step whenever you are adding Large Data effective attributes/Rule ).

4. Reasons:- If your private package got corrupted you can import the related Published Cleansing Package and you can use it as Private package. If you are Publishing Cleansing Package after small-small update also then you can use  Published cleansing Package as Backup of your private cleansing Package also.

For more information refer the SAP Note 1569008 .

How to unlock the Cleansing Package(SAP Note 1569008) :-

  1. Log in to the Central Management Console (CMC).
  2. Select Information Steward.
  3. Expand the “Cleansing Package” node and select Private or Published.
  4. Right-click the desired cleansing package, and choose Properties.
  5. Change the state to ERROR and click Save.
  6. Verify the condition of the cleansing package prior to further use.
  7. Data steward) When notified that the cleansing package is unlocked and moved to the ERROR
    state, do the following:
  8. From the “Cleansing Package Tasks” screen, open the cleansing package.
  9. Verify the condition of the cleansing package and that it displays information as expected.
  10. Close the cleansing package.
  11. If the cleansing package is returned to a READY state and its condition was as you expected,
    you may use it.
  12. If the cleansing package returns to the ERROR state or the condition was not as expected, the
    cleansing package is corrupt and should be deleted.

Please comment if you have any query , Idea or suggestions.


Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.